<div dir="ltr">I already tried legacy-390xx. As I said before, there doesn't seem to be equivalents of nvidia-cuda-toolkit and nvidia-cuda-dev that don't try to force the latest nvidia drivers. Also, bumblebee doesn't recognize the legacy-390xx drivers as a GLX alternative (I get an error stating such).<br><br>If I was to remove bbswitch, would I be unable to use PRIMUS? Also how would I go about with my VGA Passthrough setup?</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Mar 16, 2019 at 4:12 PM Luca Boccassi <<a href="mailto:bluca@debian.org">bluca@debian.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Control: severity -1 minor<br>
<br>
Try switching to legacy-390xx, or removing bbswitch and using the<br>
kernel's power management, with these laptops it's always a dice roll<br>
on what will actually work<br>
<br>
On Sat, 2019-03-16 at 14:19 -0400, Danfun360 wrote:<br>
> The graphics card in my laptop is an Nvidia Geforce GTX 1050.<br>
> <br>
> On Sat, Mar 16, 2019 at 7:20 AM Luca Boccassi <<a href="mailto:luca.boccassi@gmail.co" target="_blank">luca.boccassi@gmail.co</a><br>
> m><br>
> wrote:<br>
> <br>
> > What Nvidia card does your laptop have?<br>
> > <br>
> > On Sat, 16 Mar 2019, 03:42 Daniel O. <<a href="mailto:danfun360@gmail.com" target="_blank">danfun360@gmail.com</a> wrote:<br>
> > <br>
> > > 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<br>
> > > bumblebee/bumblebeed<br>
> > > doesn't work as it should.<br>
> > > <br>
> > > * What led up to the situation? Bumblebee used to work<br>
> > > correctly when<br>
> > > the<br>
> > > nvidia driver was at 390. A few days ago it was upgraded to 410.<br>
> > > At the<br>
> > > time I<br>
> > > was running Debian Buster (testing as of this writing). That's<br>
> > > where<br>
> > > things<br>
> > > started to get problematic. It appears that the nvidia module<br>
> > > couldn't be<br>
> > > unloaded or something. bbswitch reported as "ON" without optirun,<br>
> > > and as<br>
> > > the<br>
> > > nvidia drivers were considered in use, I was unable to unbind the<br>
> > > nvidia<br>
> > > 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<br>
> > > package. I<br>
> > > then<br>
> > > reinstalled everything. No luck. I then uninstalled everything<br>
> > > and went<br>
> > > for the<br>
> > > legacy 390 package. Unfortunately there were problems with that:<br>
> > > nvidia-cuba-<br>
> > > toolkit and nvidia-cuba-dev require the latest nvidia driver<br>
> > > installed.<br>
> > > On top<br>
> > > of that, bumblebee refused to see the legacy 390 drivers as a glx<br>
> > > alternative.<br>
> > > I uninstalled all the nvidia stuff again, switched to Debian Sid,<br>
> > > and<br>
> > > installed<br>
> > > the latest nvidia drivers again (they were slightly more up to<br>
> > > date on<br>
> > > Sid than<br>
> > > in Buster). Still no change.<br>
> > > * What was the outcome of this action? Bumblebee should be<br>
> > > able to<br>
> > > blacklist<br>
> > > the nvidia driver and isolate it from the operating system in<br>
> > > such a way<br>
> > > that<br>
> > > the system would run on the integrated GPU and run the discrete<br>
> > > GPU for<br>
> > > applications when called for.<br>
> > > * What outcome did you expect instead? The nvidia driver is<br>
> > > not<br>
> > > blacklisted,<br>
> > > and the discrete GPU is in control.<br>
> > > <br>
> > > On a different note, I tried posting a bug report upstream. It<br>
> > > has some<br>
> > > information this report might not have (vice versa is definitely<br>
> > > the case,<br>
> > > unfortunately). It can be found at <a href="https://github.com/Bumblebee-" rel="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,<br>
> > > TAINT_UNSIGNED_MODULE<br>
> > > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),<br>
> > > 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">pkg-nvidia-devel@alioth-lists.debian.net</a><br>
> > > <a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-nvid" rel="noreferrer" target="_blank">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-nvid</a><br>
> > > ia-devel<br>
> > <br>
> > <br>
-- <br>
Kind regards,<br>
Luca Boccassi<br>
</blockquote></div>