<p dir="ltr">Hello Vincent,</p>
<p dir="ltr">I'm really sorry for the troubles caused by that patch I backported.</p>
<p dir="ltr">Since it is causing troubles on Ubuntu, yes please revert it.</p>
<p dir="ltr">I suspect, as you suggested, the cause is the lack of the alias on Ubuntu.</p>
<p dir="ltr">Please bear in mind that I think 793386 is not enough to fix 793389 for Cuda users, and they'll have the exact same problem the Ubuntu users are seeing now I'm afraid. I'm writing from my phone as I'm on the move at the moment, so I cannot check right now.</p>
<p dir="ltr">In general, since the packaged drivers differ quite a bit between Ubuntu and Debian, do you think it would be worth having separate branches for bumblebee, to avoid issues due to the difference like this?</p>
<p dir="ltr">Kind regards,<br>
Luca Boccassi</p>
<div class="gmail_quote">On Aug 7, 2015 09:08, "Vincent Cheng" <<a href="mailto:vcheng@debian.org">vcheng@debian.org</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Luca,<br>
<br>
(cc-ing upstream and original bug reporter)<br>
<br>
It seems that your fix for #793389 (the rmmod->modprobe patch you<br>
committed as [1]), which I recently backported to the bumblebee PPA<br>
[2] (source at [3]) to keep the PPA packages in sync with the packages<br>
in Debian/Ubuntu, is likely the source of a regression for Ubuntu<br>
users using that PPA (see conversation below, and [4]), i.e. the<br>
nvidia kernel module isn't being automatically unloaded using modprobe<br>
for some reason (but apparently worked with rmmod previously). I'm not<br>
sure why this happens; I suspect it has something to do with Ubuntu's<br>
nvidia packages not including an alias even though they rename the<br>
module like Debian's packages. Since it does cause a regression in<br>
Ubuntu, and just by skimming #793389 I don't quite understand whether<br>
this fixes anything in Debian (isn't the fix for #793386 enough to fix<br>
module unloading?), would you be ok with me reverting [1]? Upstream is<br>
also suggesting that the patch be reverted.<br>
<br>
Regards,<br>
Vincent<br>
<br>
[1] <a href="http://anonscm.debian.org/cgit/pkg-nvidia/bumblebee.git/commit/?id=61813829f0d1b2b6134cd7b6d30a2dd071cae5ad" rel="noreferrer" target="_blank">http://anonscm.debian.org/cgit/pkg-nvidia/bumblebee.git/commit/?id=61813829f0d1b2b6134cd7b6d30a2dd071cae5ad</a><br>
[2] <a href="https://launchpad.net/~bumblebee/+archive/ubuntu/stable" rel="noreferrer" target="_blank">https://launchpad.net/~bumblebee/+archive/ubuntu/stable</a><br>
[3] <a href="https://github.com/Bumblebee-Project/bumblebee-ppa" rel="noreferrer" target="_blank">https://github.com/Bumblebee-Project/bumblebee-ppa</a><br>
[4] <a href="https://github.com/Bumblebee-Project/bumblebee-ppa/commit/2d3983e3d70db409c930ae5af2b3d538877854cf#commitcomment-12562494" rel="noreferrer" target="_blank">https://github.com/Bumblebee-Project/bumblebee-ppa/commit/2d3983e3d70db409c930ae5af2b3d538877854cf#commitcomment-12562494</a><br>
<br>
On Mon, Aug 3, 2015 at 2:33 PM, Cristian Moraru <<a href="mailto:mcrsro@gmail.com">mcrsro@gmail.com</a>> wrote:<br>
><br>
> Hi Peter,<br>
><br>
> I am coming back with the result of your suggestions:<br>
><br>
> FACTS:<br>
><br>
> - I enabled again the existing ppa:bumblebee/stable launchpad containing<br>
> version 3.2.1-91~trustyppa1<br>
> - I updated the cache and upgraded the proposals<br>
> - I installed nvidia-346 driver (before as I mentioned, I had the nvidia-331<br>
> driver which worked with version 3.2.1-90~trustyppa1)<br>
> - I created nvidia-alias.conf as instructed by you<br>
> - Rebooted the machine and checked the effects.<br>
> - All operations were done under basic kernel 3.16.0-38-generic, to rebuild<br>
> the dkms for all kernels.<br>
><br>
> I also have to mention I used to install a Mint Cinnamon Applet, named<br>
> "Bumblebee and Nvidia Display", which displays continuously the status of<br>
> Nvidia discrete card and Nvidia GPU Temperature (for details see<br>
> <a href="http://cinnamon-spices.linuxmint.com/applets/view/167" rel="noreferrer" target="_blank">http://cinnamon-spices.linuxmint.com/applets/view/167</a>)<br>
><br>
> RESULTS:<br>
><br>
> - The Nvidia card status is ON all the time and doesn't go OFF if I run in a<br>
> CLI optirun %application% in the manner you mentioned<br>
> - If I start Nvidia X Server Settings, I cannot set the PRIME setting to<br>
> select the as GPU Nvidia, I receive a window with "forbidden" sign.<br>
><br>
> CONCLUSION:<br>
><br>
> The actual executables from ppa:bumblebee/stable repository mislead an<br>
> Ubuntu user. A least my machine (which is a pretty representative for a<br>
> business work machine) will not work with bumblebee provided by this<br>
> "stable" repository. I suppose that it might work for Debian BUT IS NOT<br>
> SUITABLE for Ubuntu and its derivatives. I advise the users of Mint 17.x and<br>
> Ubuntu NOT TO USE IT.<br>
><br>
><br>
> LATER, I restored my machine GIVING UP the actual ppa:bumblebee/stable<br>
> repository, as follows<br>
><br>
> - Purged all nvidia installation with the command<br>
> sudo apt-get purge nvidia*<br>
> - Purged bumblebee installation with the command<br>
> sudo apt-get purge bumblebee<br>
> - Removed the existing executables in cache with<br>
> sudo apt-get clean<br>
> - Removed the actual ppa:bumblebee/stable repository and refreshed the<br>
> apt-cache<br>
> - Installed bumblebee and basic Nvidia driver in the Ubuntu repositories<br>
> sudo apt-get install bumblebee-nvidia virtualgl virtualgl-libs-ia32<br>
> primus primus-libs-ia32 nvidia-settings libcuda1-304 nvidia-libopencl1-304<br>
> nvidia-opencl-icd-304<br>
> - After this, I recovered the desired bumblebee status and Nvidia driver<br>
> behavior. However I couldn't setup Nvidia as default card with "Nvidia X<br>
> server Settings" facility<br>
> - Installed sequentially with the Mint facility "Driver Manager" nvidia-331,<br>
> nvidia-331-updates<br>
> - Checked the entire functionality; the only thing which didn't work was to<br>
> set PRIME to select Nvidia discrete card to be standard choice.<br>
> - Installed with the Mint facility "Driver Manager" nvidia-346 and checked<br>
> the entire functionality. The result was FULLY POSITIVE: I could select with<br>
> "Nvidia X server Settings" facility what card to use as prime choice at boot<br>
> time. The change could be also done without booting, but logging out and<br>
> logging in the user account.<br>
><br>
> - All operations were done under basic kernel 3.16.0-38-generic, to rebuild<br>
> the dkms for all kernels. After that I checked the functionality for all<br>
> other installed kernels.<br>
><br>
> The final status of bumblebee and Nvidia installed executables are shown in<br>
> the pictures attached to this email.<br>
><br>
> I also recommend to update the existing information from Bumblebee project<br>
> which is Ubuntu related to avoid damages to actual Mint and Ubuntu machines.<br>
> Please recommend users which access the official Bumblebee Project Web pages<br>
> to install first the version of Bumblebee and Nvidia drivers available on<br>
> the official Ubuntu repositories. The ppa must be used only in case of<br>
> failure with official repositories.<br>
><br>
> Kind regards<br>
><br>
> Cristian Moraru<br>
><br>
><br>
><br>
><br>
><br>
> On 07/29/2015 09:48 PM, Cristian Moraru wrote:<br>
>><br>
>> Hi Peter,<br>
>><br>
>> First of all, thank you for your prompt email!<br>
>><br>
>> I am not a programmer, but only an advanced Linux user, which appreciate<br>
>> very much the work done by people like you and Vincent for the benefit of<br>
>> Linux users.<br>
>> I am especially devoted to increase the adoption of Linux (I prefer Ubuntu<br>
>> and particularly Mint) by professional engineers (Industry, Oil & Gas)<br>
>> because of acquired stability of the LTS Linux versions. I had already some<br>
>> success and I was surprised how a small change can derail a good and<br>
>> appreciated system.<br>
>><br>
>> By nature of my work, I was obliged to guide myself to avoid proposing a<br>
>> solution and to put in practice without a comprehensive check. At least I<br>
>> didn't present a solution without warning about the potential of additional<br>
>> problems and how to overcome them under specific conditions.<br>
>><br>
>> When I update my system I believe that all the updating proposals marked<br>
>> with "3" (believed as being OK but not tested) do not create further bad<br>
>> effects to the poor user (which is not a programmer!). I believe this<br>
>> because I have to trust and appreciate the work of the people working on the<br>
>> respective updates.<br>
>><br>
>> Bumblebee is a very serious project which I appreciated very much from the<br>
>> beginning. The fact that it worked out of the box allowed me to demonstrate<br>
>> the quality of Linux (particularly Linux Mint since version 16) and to<br>
>> convince the Windows guys to switch to Linux.<br>
>><br>
>> Now, with this unhappy fact I had to restore the functionality going for a<br>
>> solution which I presented to you.<br>
>> I am convinced that this could be avoided with some precautions. My email<br>
>> wants to convince you, the developers, to implement a philosophy which could<br>
>> bring us (developers and users) a substantial increase of Linux installation<br>
>> base in the professional users field.<br>
>><br>
>> Coming back to your proposal: I will check your workaround. What I don't<br>
>> understand is why in the version 3.2.1-90~trustyppa1 it was not necessary to<br>
>> do anything to obtain a good bumblebee behavior, even with nvidia-304 and<br>
>> nvidia-346, and after Vincent pushed the update, I have to modify the Linux<br>
>> installation (which is not in the power usual Linux user) as you explained.<br>
>><br>
>> For the common Linux success, which I believe you and Vincent agree,<br>
>> developers and users must be on the same side when an upgrade is to be<br>
>> promoted.<br>
>><br>
>> Kind regards<br>
>><br>
>> Cristian Moraru<br>
>> (a stubborn user of Bumblebee Project)<br>
>><br>
>><br>
>> On 07/29/2015 08:00 PM, Peter Wu wrote:<br>
>>><br>
>>> Hi Cristian,<br>
>>><br>
>>> Vincent is the Debian maintainer of Bumblebee and has recently indeed<br>
>>> published changes for the benefit of Ubuntu users (and derivatives).<br>
>>><br>
>>> What you are basically experiencing is the inability to turn off the<br>
>>> graphics card after using optirun. This problem can be caused by a<br>
>>> configuration issue in Ubuntu (which probably does not exist in Debian).<br>
>>><br>
>>> Workaround for version 3.2.1-91~trustyppa1:<br>
>>><br>
>>> Determine your nvidia module version (say, nvidia-346) and create<br>
>>> /etc/modprobe.d/nvidia-alias.conf containing:<br>
>>><br>
>>> alias nvidia nvidia-346<br>
>>><br>
>>> Besides this, you do not have to restart any services, just trigger<br>
>>> optirun again (optirun true).<br>
>>><br>
>>> Vincent, what do you think of the proposed patch at<br>
>>><br>
>>> <a href="https://github.com/Bumblebee-Project/Bumblebee/commit/edd81b063ec1bda63ae8a3b10d8051e02eec282b" rel="noreferrer" target="_blank">https://github.com/Bumblebee-Project/Bumblebee/commit/edd81b063ec1bda63ae8a3b10d8051e02eec282b</a><br>
>><br>
>><br>
><br>
><br>
<br>
_______________________________________________<br>
pkg-nvidia-devel mailing list<br>
<a href="mailto:pkg-nvidia-devel@lists.alioth.debian.org">pkg-nvidia-devel@lists.alioth.debian.org</a><br>
<a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-nvidia-devel" rel="noreferrer" target="_blank">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-nvidia-devel</a><br>
</blockquote></div>