Bug#1035312: minetest: New upstream version available (5.7.0)

[Danfun360]

5.8.0 has just been released.
https://blog.minetest.net/2023/12/04/5.8.0-released/

The most important change for Debian would be Minetest Game no longer being
included by default. I'm not sure how this will be handled with Debian
specific customizations and the Debian repository.

Bug#924704: bumblebee-nvidia: nvidia-driver 410 doesn't appear to allow the unloading of the nvidia module

[Danfun360]

I've given up on solving this issue. I hope that, if someone else was in
the same boat I was in, the issue gets resolved.

On Mon, Mar 18, 2019 at 8:52 PM  wrote:

> [image: BitBounce]
>
>
>
> Thanks for emailing me! No, I haven’t been hacked :)
>
> I signed up for a spam filter service called BitBounce. To deliver your
> shotgun email to my inbox, please click the link below and pay the small
> Credo (coin) fee. Thanks!
>
> *$0.90* to deliver your email.
>
> We’ve never met — I’ll pay your fee.
> 
>
> I know you — Add me to your whitelist.
> 
>
>
>
> *BitBounce*  is powered by the
> *Credo*  cryptocurrency
>
> *I’m from a business* —  what are my *delivery options*
> 
>
> BitBounce and Credo are transacted through *CredoEx*
> 
> Made by Turing Technology Inc. in San Mateo, California *Sign Up for
> BitBounce* 
>

Bug#924704: bumblebee-nvidia: nvidia-driver 410 doesn't appear to allow the unloading of the nvidia module

[Danfun360]

I've done some serious troubleshooting. Here's a new xorg log. Notable
issues include "ACPI: failed to connect to the ACPI event daemon", (EE)
kbd: : failed to set us as foreground .pgrp
(Inappropriate ioctl for device), and (EE) /dev/dri/card0: failed to set
DRM interface version 1.4: Permission denied

On Mon, Mar 18, 2019 at 2:04 PM Luca Boccassi  wrote:

> Check the issues on the upstream repositories for suggestions
>
> On Mon, 2019-03-18 at 12:51 -0400, Danfun360 wrote:
> > 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"
> >
> > I've been following the guide
> > https://gist.github.com/Misairu-G/616f7b2756c488148b7309addc940b28 (w
> > ith some differences. Debian doesn't have nvidia-prime for instance).
> >
> > On Mon, Mar 18, 2019 at 9:53 AM Luca Boccassi 
> > wrote:
> > > There are other threads on the upstream repositories with people
> > > suggesting various acpi values for the kernel command line, have a
> > > look
> > > if one of the combinations work for your hardware
> > >
> > > On Sun, 2019-03-17 at 19:13 -0400, Danfun360 wrote:
> > > > Having set PMMethod to "none" and AlwaysUnloadKernelDriver to
> > > "true",
> > > > I still get the bug involving the inability to unload the
> > > > nvidia module for the purpose of VGA Passthrough. I wonder if my
> > > > issue is connected to
> > > > https://github.com/Bumblebee-Project/bbswitch/issues/173 as
> > > "lsmod |
> > > > grep nvidia" gives the result
> > > >
> > > > nvidia  16670720  9
> > > > ipmi_msghandler65536  2 ipmi_devintf,nvidia
> > > >
> > > > Any new suggestions?
> > > >
> > > > On Sun, Mar 17, 2019 at 12:29 PM Luca Boccassi 
> > > > wrote:
> > > > > As mentioned your hardware might not work with bbswitch and
> > > might
> > > > > instead work with the kernel PM. Remove bbswitch and set
> > > > > AlwaysUnloadKernelDriver=true in bumblebee's config file.
> > > > >
> > > > > On Sat, 2019-03-16 at 22:22 -0400, Danfun360 wrote:
> > > > > > Well, the good news is, the GLX alternative bug with legacy-
> > > 390xx
> > > > > > appears
> > > > > > to have been fixed.
> > > > > >
> > > > > > The bad news is that the main bug of bumblebeed failing to
> > > load
> > > > > at
> > > > > > startup
> > > > > > for whatever reason is still there. Have any suggestions for
> > > > > > troubleshooting? (Also, since this bug affects both the
> > > latest
> > > > > > nvidia-driver (410) as well as nvidia-driver-legacy-390xx,
> > > I'd
> > > > > prefer
> > > > > > trying to work with 410)
> > > > > >
> > > > > > On Sat, Mar 16, 2019 at 5:48 PM Luca Boccassi <
> > > bl...@debian.org>
> > > > > > wrote:
> > > > > >
> > > > > > > That's not the case anymore in buster, 390xx works fine
> > > with
> > > > > other
> > > > > > > packages
> > > > > > >
> > > > > > > On Sat, 16 Mar 2019, 21:03 Danfun360  > > > > wrote:
> > > > > > >
> > > > > > > > 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).
> > > > > > > >
> > > > > > > > If I was to remove bbswitch, would I be unable to use
> > > PRIMUS?
> > > > > > > > Also how
> > > > > > > > would I go about with my VG

Bug#924704: bumblebee-nvidia: nvidia-driver 410 doesn't appear to allow the unloading of the nvidia module

[Danfun360]

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"

I've been following the guide
https://gist.github.com/Misairu-G/616f7b2756c488148b7309addc940b28 (with
some differences. Debian doesn't have nvidia-prime for instance).

On Mon, Mar 18, 2019 at 9:53 AM Luca Boccassi  wrote:

> There are other threads on the upstream repositories with people
> suggesting various acpi values for the kernel command line, have a look
> if one of the combinations work for your hardware
>
> On Sun, 2019-03-17 at 19:13 -0400, Danfun360 wrote:
> > Having set PMMethod to "none" and AlwaysUnloadKernelDriver to "true",
> > I still get the bug involving the inability to unload the
> > nvidia module for the purpose of VGA Passthrough. I wonder if my
> > issue is connected to
> > https://github.com/Bumblebee-Project/bbswitch/issues/173 as "lsmod |
> > grep nvidia" gives the result
> >
> > nvidia  16670720  9
> > ipmi_msghandler65536  2 ipmi_devintf,nvidia
> >
> > Any new suggestions?
> >
> > On Sun, Mar 17, 2019 at 12:29 PM Luca Boccassi 
> > wrote:
> > > As mentioned your hardware might not work with bbswitch and might
> > > instead work with the kernel PM. Remove bbswitch and set
> > > AlwaysUnloadKernelDriver=true in bumblebee's config file.
> > >
> > > On Sat, 2019-03-16 at 22:22 -0400, Danfun360 wrote:
> > > > Well, the good news is, the GLX alternative bug with legacy-390xx
> > > > appears
> > > > to have been fixed.
> > > >
> > > > The bad news is that the main bug of bumblebeed failing to load
> > > at
> > > > startup
> > > > for whatever reason is still there. Have any suggestions for
> > > > troubleshooting? (Also, since this bug affects both the latest
> > > > nvidia-driver (410) as well as nvidia-driver-legacy-390xx, I'd
> > > prefer
> > > > trying to work with 410)
> > > >
> > > > On Sat, Mar 16, 2019 at 5:48 PM Luca Boccassi 
> > > > wrote:
> > > >
> > > > > That's not the case anymore in buster, 390xx works fine with
> > > other
> > > > > packages
> > > > >
> > > > > On Sat, 16 Mar 2019, 21:03 Danfun360  > > wrote:
> > > > >
> > > > > > 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).
> > > > > >
> > > > > > If I was to remove bbswitch, would I be unable to use PRIMUS?
> > > > > > Also how
> > > > > > would I go about with my VGA Passthrough setup?
> > > > > >
> > > > > > On Sat, Mar 16, 2019 at 4:12 PM Luca Boccassi <
> > > bl...@debian.org>
> > > > > > wrote:
> > > > > >
> > > > > > > Control: severity -1 minor
> > > > > > >
> > > > > > > Try switching to legacy-390xx, or removing bbswitch and
> > > using
> > > > > > > the
> > > > > > > kernel's power management, with these laptops it's always a
> > > > > > > dice roll
> > > > > > > on what will actually work
> > > > > > >
> > > > > > > On Sat, 2019-03-16 at 14:19 -0400, Danfun360 wrote:
> > > > > > > > The graphics card in my laptop is an Nvidia Geforce GTX
> > > 1050.
> > > > > > > >
> > > > > > > > On Sat, Mar 16, 2019 at 7:20 AM Luca Boccassi
> > >  > > > > > > > gmail.co
> > > > > > > > m>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > What Nvidia card does your laptop have?
> > > > > > > > >
> > > > > > > > > On Sat, 16 Mar 2019, 03:42 Daniel

Bug#924704: bumblebee-nvidia: nvidia-driver 410 doesn't appear to allow the unloading of the nvidia module

[Danfun360]

Having set PMMethod to "none" and AlwaysUnloadKernelDriver to "true", I
*still* get the bug involving the inability to unload the nvidia module for
the purpose of VGA Passthrough. I wonder if my issue is connected to
https://github.com/Bumblebee-Project/bbswitch/issues/173 as "lsmod | grep
nvidia" gives the result

nvidia  16670720  9
ipmi_msghandler65536  2 ipmi_devintf,nvidia

Any new suggestions?


On Sun, Mar 17, 2019 at 12:29 PM Luca Boccassi  wrote:

> As mentioned your hardware might not work with bbswitch and might
> instead work with the kernel PM. Remove bbswitch and set
> AlwaysUnloadKernelDriver=true in bumblebee's config file.
>
> On Sat, 2019-03-16 at 22:22 -0400, Danfun360 wrote:
> > Well, the good news is, the GLX alternative bug with legacy-390xx
> > appears
> > to have been fixed.
> >
> > The bad news is that the main bug of bumblebeed failing to load at
> > startup
> > for whatever reason is still there. Have any suggestions for
> > troubleshooting? (Also, since this bug affects both the latest
> > nvidia-driver (410) as well as nvidia-driver-legacy-390xx, I'd prefer
> > trying to work with 410)
> >
> > On Sat, Mar 16, 2019 at 5:48 PM Luca Boccassi 
> > wrote:
> >
> > > That's not the case anymore in buster, 390xx works fine with other
> > > packages
> > >
> > > On Sat, 16 Mar 2019, 21:03 Danfun360  > >
> > > > 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).
> > > >
> > > > If I was to remove bbswitch, would I be unable to use PRIMUS?
> > > > Also how
> > > > would I go about with my VGA Passthrough setup?
> > > >
> > > > On Sat, Mar 16, 2019 at 4:12 PM Luca Boccassi 
> > > > wrote:
> > > >
> > > > > Control: severity -1 minor
> > > > >
> > > > > Try switching to legacy-390xx, or removing bbswitch and using
> > > > > the
> > > > > kernel's power management, with these laptops it's always a
> > > > > dice roll
> > > > > on what will actually work
> > > > >
> > > > > On Sat, 2019-03-16 at 14:19 -0400, Danfun360 wrote:
> > > > > > The graphics card in my laptop is an Nvidia Geforce GTX 1050.
> > > > > >
> > > > > > On Sat, Mar 16, 2019 at 7:20 AM Luca Boccassi  > > > > > gmail.co
> > > > > > m>
> > > > > > wrote:
> > > > > >
> > > > > > > What Nvidia card does your laptop have?
> > > > > > >
> > > > > > > On Sat, 16 Mar 2019, 03:42 Daniel O.  > > > > > > wrote:
> > > > > > >
> > > > > > > > Package: bumblebee-nvidia
> > > > > > > > Version: 3.2.1-20
> > > > > > > > Severity: grave
> > > > > > > > Justification: renders package unusable
> > > > > > > >
> > > > > > > > Dear Maintainer, I write this bug report because this
> > > > > > > > bumblebee/bumblebeed
> > > > > > > > doesn't work as it should.
> > > > > > > >
> > > > > > > >* What led up to the situation? Bumblebee used to work
> > > > > > > > correctly when
> > > > > > > > the
> > > > > > > > nvidia driver was at 390. A few days ago it was upgraded
> > > > > > > > to 410.
> > > > > > > > At the
> > > > > > > > time I
> > > > > > > > was running Debian Buster (testing as of this writing).
> > > > > > > > That's
> > > > > > > > where
> > > > > > > > things
> > > > > > > > started to get problematic. It appears that the nvidia
> > > > > > > > module
> > > > > > > > couldn't be
> > > > > > > > unloaded or something. bbswitch reported as "ON" without
> > > > > > > > optirun,
> > > > &g

Bug#924704: bumblebee-nvidia: nvidia-driver 410 doesn't appear to allow the unloading of the nvidia module

[Danfun360]

Well, the good news is, the GLX alternative bug with legacy-390xx appears
to have been fixed.

The bad news is that the main bug of bumblebeed failing to load at startup
for whatever reason is still there. Have any suggestions for
troubleshooting? (Also, since this bug affects both the latest
nvidia-driver (410) as well as nvidia-driver-legacy-390xx, I'd prefer
trying to work with 410)

On Sat, Mar 16, 2019 at 5:48 PM Luca Boccassi  wrote:

> That's not the case anymore in buster, 390xx works fine with other packages
>
> On Sat, 16 Mar 2019, 21:03 Danfun360 
>> 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).
>>
>> If I was to remove bbswitch, would I be unable to use PRIMUS? Also how
>> would I go about with my VGA Passthrough setup?
>>
>> On Sat, Mar 16, 2019 at 4:12 PM Luca Boccassi  wrote:
>>
>>> Control: severity -1 minor
>>>
>>> Try switching to legacy-390xx, or removing bbswitch and using the
>>> kernel's power management, with these laptops it's always a dice roll
>>> on what will actually work
>>>
>>> On Sat, 2019-03-16 at 14:19 -0400, Danfun360 wrote:
>>> > The graphics card in my laptop is an Nvidia Geforce GTX 1050.
>>> >
>>> > On Sat, Mar 16, 2019 at 7:20 AM Luca Boccassi >> > m>
>>> > wrote:
>>> >
>>> > > What Nvidia card does your laptop have?
>>> > >
>>> > > On Sat, 16 Mar 2019, 03:42 Daniel O. >> > >
>>> > > > Package: bumblebee-nvidia
>>> > > > Version: 3.2.1-20
>>> > > > Severity: grave
>>> > > > Justification: renders package unusable
>>> > > >
>>> > > > Dear Maintainer, I write this bug report because this
>>> > > > bumblebee/bumblebeed
>>> > > > doesn't work as it should.
>>> > > >
>>> > > >* What led up to the situation? Bumblebee used to work
>>> > > > correctly when
>>> > > > the
>>> > > > nvidia driver was at 390. A few days ago it was upgraded to 410.
>>> > > > At the
>>> > > > time I
>>> > > > was running Debian Buster (testing as of this writing). That's
>>> > > > where
>>> > > > things
>>> > > > started to get problematic. It appears that the nvidia module
>>> > > > couldn't be
>>> > > > unloaded or something. bbswitch reported as "ON" without optirun,
>>> > > > and as
>>> > > > the
>>> > > > nvidia drivers were considered in use, I was unable to unbind the
>>> > > > nvidia
>>> > > > driver
>>> > > > for VGA Passthrough as I had been doing before.
>>> > > >* What exactly did you do (or not do) that was effective (or
>>> > > >  ineffective)? I uninstalled every bumblebee and nvidia
>>> > > > package. I
>>> > > > then
>>> > > > reinstalled everything. No luck. I then uninstalled everything
>>> > > > and went
>>> > > > for the
>>> > > > legacy 390 package. Unfortunately there were problems with that:
>>> > > > nvidia-cuba-
>>> > > > toolkit and nvidia-cuba-dev require the latest nvidia driver
>>> > > > installed.
>>> > > > On top
>>> > > > of that, bumblebee refused to see the legacy 390 drivers as a glx
>>> > > > alternative.
>>> > > > I uninstalled all the nvidia stuff again, switched to Debian Sid,
>>> > > > and
>>> > > > installed
>>> > > > the latest nvidia drivers again (they were slightly more up to
>>> > > > date on
>>> > > > Sid than
>>> > > > in Buster). Still no change.
>>> > > >* What was the outcome of this action? Bumblebee should be
>>> > > > able to
>>> > > > blacklist
>>> > > > the nvidia driver and isolate it from the operating system in
>>> > > > such a way
>>> > > > that
>>> > > > the system would run on the integrated GPU and run the discrete
>>&g

Bug#924704: bumblebee-nvidia: nvidia-driver 410 doesn't appear to allow the unloading of the nvidia module

[Danfun360]

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).

If I was to remove bbswitch, would I be unable to use PRIMUS? Also how
would I go about with my VGA Passthrough setup?

On Sat, Mar 16, 2019 at 4:12 PM Luca Boccassi  wrote:

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

Bug#924704: bumblebee-nvidia: nvidia-driver 410 doesn't appear to allow the unloading of the nvidia module

[Danfun360]

The graphics card in my laptop is an Nvidia Geforce GTX 1050.

On Sat, Mar 16, 2019 at 7:20 AM Luca Boccassi 
wrote:

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

Bug#924704:

[Danfun360]

In case you don't want to click on the Github link (which for some reason
has an additional space that needs to be removed before entering it on your
URL bar), here is the bumblebee-bugreport.
https://github.com/Bumblebee-Project/Bumblebee/files/2973323/bumblebee-bugreport-20190315_204845.tar.gz