<div dir="ltr"><div dir="ltr"><div dir="ltr">Exactly what acpi values should I try? My GRUB_CMDLINE_LINUX_DEFAULT reads "quiet nogpumanager acpi_osi=! acpi_osi=Linux acpi_osi=\"Windows 2015\" pcie_port_pm=off intel_iommu=on,igfx_off kvm.ignore_msrs=1 default_hugepagesz=1G hugepagesz=1G hugepages=8 transparent_hugepage=never"<br><br>I've been following the guide <a href="https://gist.github.com/Misairu-G/616f7b2756c488148b7309addc940b28">https://gist.github.com/Misairu-G/616f7b2756c488148b7309addc940b28</a> (with some differences. Debian doesn't have nvidia-prime for instance).</div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Mar 18, 2019 at 9:53 AM 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">There are other threads on the upstream repositories with people<br>
suggesting various acpi values for the kernel command line, have a look<br>
if one of the combinations work for your hardware<br>
<br>
On Sun, 2019-03-17 at 19:13 -0400, Danfun360 wrote:<br>
> Having set PMMethod to "none" and AlwaysUnloadKernelDriver to "true",<br>
> I still get the bug involving the inability to unload the<br>
> nvidia module for the purpose of VGA Passthrough. I wonder if my<br>
> issue is connected to <br>
> <a href="https://github.com/Bumblebee-Project/bbswitch/issues/173" rel="noreferrer" target="_blank">https://github.com/Bumblebee-Project/bbswitch/issues/173</a> as "lsmod |<br>
> grep nvidia" gives the result <br>
> <br>
> nvidia 16670720 9<br>
> ipmi_msghandler 65536 2 ipmi_devintf,nvidia<br>
> <br>
> Any new suggestions?<br>
> <br>
> On Sun, Mar 17, 2019 at 12:29 PM Luca Boccassi <<a href="mailto:bluca@debian.org" target="_blank">bluca@debian.org</a>><br>
> wrote:<br>
> > As mentioned your hardware might not work with bbswitch and might<br>
> > instead work with the kernel PM. Remove bbswitch and set<br>
> > AlwaysUnloadKernelDriver=true in bumblebee's config file.<br>
> > <br>
> > On Sat, 2019-03-16 at 22:22 -0400, Danfun360 wrote:<br>
> > > Well, the good news is, the GLX alternative bug with legacy-390xx<br>
> > > appears<br>
> > > to have been fixed.<br>
> > > <br>
> > > The bad news is that the main bug of bumblebeed failing to load<br>
> > at<br>
> > > startup<br>
> > > for whatever reason is still there. Have any suggestions for<br>
> > > troubleshooting? (Also, since this bug affects both the latest<br>
> > > nvidia-driver (410) as well as nvidia-driver-legacy-390xx, I'd<br>
> > prefer<br>
> > > trying to work with 410)<br>
> > > <br>
> > > On Sat, Mar 16, 2019 at 5:48 PM Luca Boccassi <<a href="mailto:bluca@debian.org" target="_blank">bluca@debian.org</a>><br>
> > > wrote:<br>
> > > <br>
> > > > That's not the case anymore in buster, 390xx works fine with<br>
> > other<br>
> > > > packages<br>
> > > > <br>
> > > > On Sat, 16 Mar 2019, 21:03 Danfun360 <<a href="mailto:danfun360@gmail.com" target="_blank">danfun360@gmail.com</a><br>
> > wrote:<br>
> > > > <br>
> > > > > I already tried legacy-390xx. As I said before, there doesn't<br>
> > > > > seem to be<br>
> > > > > equivalents of nvidia-cuda-toolkit and nvidia-cuda-dev that<br>
> > don't<br>
> > > > > try to<br>
> > > > > force the latest nvidia drivers. Also, bumblebee doesn't<br>
> > > > > recognize the<br>
> > > > > legacy-390xx drivers as a GLX alternative (I get an error<br>
> > stating<br>
> > > > > such).<br>
> > > > > <br>
> > > > > If I was to remove bbswitch, would I be unable to use PRIMUS?<br>
> > > > > Also how<br>
> > > > > would I go about with my VGA Passthrough setup?<br>
> > > > > <br>
> > > > > On Sat, Mar 16, 2019 at 4:12 PM Luca Boccassi <<br>
> > <a href="mailto:bluca@debian.org" target="_blank">bluca@debian.org</a>><br>
> > > > > wrote:<br>
> > > > > <br>
> > > > > > Control: severity -1 minor<br>
> > > > > > <br>
> > > > > > Try switching to legacy-390xx, or removing bbswitch and<br>
> > using<br>
> > > > > > the<br>
> > > > > > kernel's power management, with these laptops it's always a<br>
> > > > > > 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<br>
> > 1050.<br>
> > > > > > > <br>
> > > > > > > On Sat, Mar 16, 2019 at 7:20 AM Luca Boccassi<br>
> > <luca.boccassi@<br>
> > > > > > > <a href="http://gmail.co" rel="noreferrer" target="_blank">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. <<br>
> > <a href="mailto:danfun360@gmail.com" target="_blank">danfun360@gmail.com</a><br>
> > > > > > > > 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<br>
> > work<br>
> > > > > > > > > correctly when<br>
> > > > > > > > > the<br>
> > > > > > > > > nvidia driver was at 390. A few days ago it was<br>
> > upgraded<br>
> > > > > > > > > to 410.<br>
> > > > > > > > > At the<br>
> > > > > > > > > time I<br>
> > > > > > > > > was running Debian Buster (testing as of this<br>
> > writing).<br>
> > > > > > > > > That's<br>
> > > > > > > > > where<br>
> > > > > > > > > things<br>
> > > > > > > > > started to get problematic. It appears that the<br>
> > nvidia<br>
> > > > > > > > > module<br>
> > > > > > > > > couldn't be<br>
> > > > > > > > > unloaded or something. bbswitch reported as "ON"<br>
> > without<br>
> > > > > > > > > optirun,<br>
> > > > > > > > > and as<br>
> > > > > > > > > the<br>
> > > > > > > > > nvidia drivers were considered in use, I was unable<br>
> > to<br>
> > > > > > > > > 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<br>
> > > > > > > > > effective (or<br>
> > > > > > > > > ineffective)? I uninstalled every bumblebee and<br>
> > > > > > > > > nvidia<br>
> > > > > > > > > package. I<br>
> > > > > > > > > then<br>
> > > > > > > > > reinstalled everything. No luck. I then uninstalled<br>
> > > > > > > > > everything<br>
> > > > > > > > > and went<br>
> > > > > > > > > for the<br>
> > > > > > > > > legacy 390 package. Unfortunately there were problems<br>
> > > > > > > > > with that:<br>
> > > > > > > > > nvidia-cuba-<br>
> > > > > > > > > toolkit and nvidia-cuba-dev require the latest nvidia<br>
> > > > > > > > > driver<br>
> > > > > > > > > installed.<br>
> > > > > > > > > On top<br>
> > > > > > > > > of that, bumblebee refused to see the legacy 390<br>
> > drivers<br>
> > > > > > > > > as a glx<br>
> > > > > > > > > alternative.<br>
> > > > > > > > > I uninstalled all the nvidia stuff again, switched to<br>
> > > > > > > > > Debian Sid,<br>
> > > > > > > > > and<br>
> > > > > > > > > installed<br>
> > > > > > > > > the latest nvidia drivers again (they were slightly<br>
> > more<br>
> > > > > > > > > up to<br>
> > > > > > > > > date on<br>
> > > > > > > > > Sid than<br>
> > > > > > > > > in Buster). Still no change.<br>
> > > > > > > > > * What was the outcome of this action? Bumblebee<br>
> > > > > > > > > should be<br>
> > > > > > > > > able to<br>
> > > > > > > > > blacklist<br>
> > > > > > > > > the nvidia driver and isolate it from the operating<br>
> > > > > > > > > system in<br>
> > > > > > > > > such a way<br>
> > > > > > > > > that<br>
> > > > > > > > > the system would run on the integrated GPU and run<br>
> > the<br>
> > > > > > > > > discrete<br>
> > > > > > > > > GPU for<br>
> > > > > > > > > applications when called for.<br>
> > > > > > > > > * What outcome did you expect instead? The nvidia<br>
> > > > > > > > > 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<br>
> > > > > > > > > upstream. It<br>
> > > > > > > > > has some<br>
> > > > > > > > > information this report might not have (vice versa is<br>
> > > > > > > > > definitely<br>
> > > > > > > > > the case,<br>
> > > > > > > > > unfortunately). It can be found at <br>
> > <a href="https://github.com/Bum" rel="noreferrer" target="_blank">https://github.com/Bum</a><br>
> > > > > > > > > blebee-<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,<br>
> > > > > > > > > TAINT_OOT_MODULE,<br>
> > > > > > > > > TAINT_UNSIGNED_MODULE<br>
> > > > > > > > > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8<br>
> > > > > > > > > (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>
> > > > > > > > > <br>
> > <a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/" rel="noreferrer" target="_blank">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/</a><br>
> > > > > > > > > pkg-nvid<br>
> > > > > > > > > ia-devel<br>
> > > > > > > > <br>
> > > > > > > > <br>
> > > > > > <br>
> > > > > > --<br>
> > > > > > Kind regards,<br>
> > > > > > Luca Boccassi<br>
> > > > > > <br>
-- <br>
Kind regards,<br>
Luca Boccassi<br>
-----BEGIN PGP SIGNATURE-----<br>
<br>
iQEzBAABCgAdFiEE6g0RLAGYhL9yp9G8SylmgFB4UWIFAlyPovMACgkQSylmgFB4<br>
UWKVMgf/UXABd/WBwvP28vZewitzWl3ygnqfq+bfKmLtdx7QTk1XOtPnKNsarMzA<br>
1tGa4RxPrqEphNyzDusQj2fvuDrXwD2fNtOlRYUjLxzTOvAUPXz3sne91m8hx9or<br>
SV3MGuL9asfFoXwNKcjYpBD7ppk2Jb0xP+YfBsxtwR4wI4o7i8GZq46srfRyaLS4<br>
v3kSspN4ObO5OkkOQT015PGr6reAzcUFcRTjkJ4dF+C867UffoZvzD7U47fmen1a<br>
mAtCvTBHEyq72TjMc7K8Ug3v1yaEyQn0TThHbu/IPubKH9qm6/L6c+ROscEFQA1w<br>
spmY0mnT+HzhlVV+BI/FFyeDJw3ZZw==<br>
=LydK<br>
-----END PGP SIGNATURE-----<br>
</blockquote></div>