<div dir="auto">What Nvidia card does your laptop have?</div><br><div class="gmail_quote"><div dir="ltr">On Sat, 16 Mar 2019, 03:42 Daniel O. <<a href="mailto:danfun360@gmail.com">danfun360@gmail.com</a> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Package: bumblebee-nvidia<br>
Version: 3.2.1-20<br>
Severity: grave<br>
Justification: renders package unusable<br>
<br>
Dear Maintainer, I write this bug report because this bumblebee/bumblebeed<br>
doesn't work as it should.<br>
<br>
* What led up to the situation? Bumblebee used to work correctly when the<br>
nvidia driver was at 390. A few days ago it was upgraded to 410. At the time I<br>
was running Debian Buster (testing as of this writing). That's where things<br>
started to get problematic. It appears that the nvidia module couldn't be<br>
unloaded or something. bbswitch reported as "ON" without optirun, and as the<br>
nvidia drivers were considered in use, I was unable to unbind the nvidia driver<br>
for VGA Passthrough as I had been doing before.<br>
* What exactly did you do (or not do) that was effective (or<br>
ineffective)? I uninstalled every bumblebee and nvidia package. I then<br>
reinstalled everything. No luck. I then uninstalled everything and went for the<br>
legacy 390 package. Unfortunately there were problems with that: nvidia-cuba-<br>
toolkit and nvidia-cuba-dev require the latest nvidia driver installed. On top<br>
of that, bumblebee refused to see the legacy 390 drivers as a glx alternative.<br>
I uninstalled all the nvidia stuff again, switched to Debian Sid, and installed<br>
the latest nvidia drivers again (they were slightly more up to date on Sid than<br>
in Buster). Still no change.<br>
* What was the outcome of this action? Bumblebee should be able to blacklist<br>
the nvidia driver and isolate it from the operating system in such a way that<br>
the system would run on the integrated GPU and run the discrete GPU for<br>
applications when called for.<br>
* What outcome did you expect instead? The nvidia driver is not blacklisted,<br>
and the discrete GPU is in control.<br>
<br>
On a different note, I tried posting a bug report upstream. It has some<br>
information this report might not have (vice versa is definitely the case,<br>
unfortunately). It can be found at <a href="https://github.com/Bumblebee-" rel="noreferrer noreferrer" target="_blank">https://github.com/Bumblebee-</a><br>
Project/Bumblebee/issues/1023<br>
<br>
<br>
<br>
-- System Information:<br>
Debian Release: buster/sid<br>
APT prefers unstable<br>
APT policy: (500, 'unstable')<br>
Architecture: amd64 (x86_64)<br>
Foreign Architectures: i386<br>
<br>
Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores)<br>
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE<br>
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)<br>
Shell: /bin/sh linked to /usr/bin/dash<br>
Init: systemd (via /run/systemd/system)<br>
LSM: AppArmor: enabled<br>
<br>
Versions of packages bumblebee-nvidia depends on:<br>
ii bumblebee 3.2.1-20<br>
ii glx-alternative-nvidia 0.9.1<br>
ii nvidia-driver 410.104-1<br>
ii nvidia-kernel-dkms 410.104-1<br>
<br>
bumblebee-nvidia recommends no packages.<br>
<br>
bumblebee-nvidia suggests no packages.<br>
<br>
-- no debconf information<br>
<br>
_______________________________________________<br>
pkg-nvidia-devel mailing list<br>
<a href="mailto:pkg-nvidia-devel@alioth-lists.debian.net" target="_blank" rel="noreferrer">pkg-nvidia-devel@alioth-lists.debian.net</a><br>
<a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-nvidia-devel" rel="noreferrer noreferrer" target="_blank">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-nvidia-devel</a></blockquote></div>