step 1 phasing our bumblebee (free drivers) #23

Closed
philm wants to merge 0 commits from unknown repository into master
philm commented 2017-10-15 10:26:52 +00:00 (Migrated from gitlab2.manjaro.org)

Created by: Tids

sorry for the 4 commits in there, it really is bad luck sunday for me.

However with this change, the user will be not able to install the intel-ati;neovou-bumblebe config anymore.

It will still start the installation and then fails with:


=======================================================
Bumblebee is not supported for Intel and radeon anymore
please use
        * video-hybrid-intel-radeon-prime
        * video-hybrid-intel-amdgpu-prime
=======================================================

Error: script failed!

The reason is that bumblebee is not working anymore for a longer time, while prime is fully supported on all the free drivers.

We can not remove the scripts yet, because we have still some users who use them and they will be not able to uninstall them if they are removed. So for now the important part it to prevent new users to install them and remove the scripts in step 2, in 2018 (hopefully together with nvidia-bumblebee ;))

*Created by: Tids* sorry for the 4 commits in there, it really is bad luck sunday for me. However with this change, the user will be not able to install the intel-ati;neovou-bumblebe config anymore. It will still start the installation and then fails with: ``` ======================================================= Bumblebee is not supported for Intel and radeon anymore please use * video-hybrid-intel-radeon-prime * video-hybrid-intel-amdgpu-prime ======================================================= Error: script failed! ``` The reason is that bumblebee is not working anymore for a longer time, while prime is fully supported on all the free drivers. We can not remove the scripts yet, because we have still some users who use them and they will be not able to uninstall them if they are removed. So for now the important part it to prevent new users to install them and remove the scripts in step 2, in 2018 (hopefully together with nvidia-bumblebee ;))
philm commented 2017-12-24 08:27:26 +00:00 (Migrated from gitlab2.manjaro.org)

Created by: philmmanjaro

The question here is if this is the right approach. On new install medias we should disable those profiles completely. On running systems it makes sense. What is the output of mhwd listing the available profiles and how does auto-install act for it?

*Created by: philmmanjaro* The question here is if this is the right approach. On new install medias we should disable those profiles completely. On running systems it makes sense. What is the output of **mhwd** listing the available profiles and how does auto-install act for it?
philm commented 2017-12-24 09:25:58 +00:00 (Migrated from gitlab2.manjaro.org)

Created by: Tids

@philmmanjaro Is it possible to disable profiles on the installation medias, but keep them on the installed systems?
Auto-install will default to the newer *-prime profiles. Thats luckily not a problem anymore. Only 2 groups of users still have this installed at all:

  • long time keepers (those who have installed manjaro with 0.8.*
  • new users who wants to try out bumblebee

thats why it would be nice to

  • step 1 - deactivate the installation of free-driver-bumblebee
  • step 2 - use a small migration script instide of a manjaro update to remove radeon/nouveau bumblebee and run mhwd autoinstal only for users who have these bumblebee still installed
  • step 3 - remove free-driver-bumblebee completely
*Created by: Tids* @philmmanjaro Is it possible to disable profiles on the installation medias, but keep them on the installed systems? Auto-install will default to the newer `*-prime` profiles. Thats luckily not a problem anymore. Only 2 groups of users still have this installed at all: * long time keepers (those who have installed manjaro with 0.8.* * new users who wants to try out bumblebee thats why it would be nice to * step 1 - deactivate the installation of free-driver-bumblebee * step 2 - use a small migration script instide of a manjaro update to remove radeon/nouveau bumblebee and run mhwd autoinstal only for users who have these bumblebee still installed * step 3 - remove free-driver-bumblebee completely
philm commented 2017-12-25 07:50:33 +00:00 (Migrated from gitlab2.manjaro.org)

Created by: philmmanjaro

I can blank them out in manjaro-tools on creation. However, if mhwd -a uses prime, that step is not needed. Do you have an output for me on how it might look like? Else I try with the Lancaster soon. It has an hybrid Nvidia setup.

*Created by: philmmanjaro* I can blank them out in **manjaro-tools** on creation. However, if **mhwd -a** uses prime, that step is not needed. Do you have an output for me on how it might look like? Else I try with the **Lancaster** soon. It has an hybrid Nvidia setup.
philm commented 2017-12-29 13:53:13 +00:00 (Migrated from gitlab2.manjaro.org)

Created by: Tids

Would be good if you could test that. I'm not sure when I'm able to test.

*Created by: Tids* Would be good if you could test that. I'm not sure when I'm able to test.
philm commented 2018-01-07 19:13:46 +00:00 (Migrated from gitlab2.manjaro.org)

Created by: philmmanjaro

@Tids: didn't had time yet to test this. So it will take a little longer until merged ...

*Created by: philmmanjaro* @Tids: didn't had time yet to test this. So it will take a little longer until merged ...

Pull request closed

Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
applications/mhwd-db!23
No description provided.