Bug#966557: Blacklist nvidia-modeset and nvidia-drm

[Joel Johnson]

On 2020-08-04 15:47, Andreas Beckmann wrote:
> On 8/4/20 1:49 AM, Felix Dörre wrote:
>> I've got a slight clue, what could be wrong here:
>> 
>> The posted update-glx --display glx shows the following line:
> [...]
>> but none libGLX_nvidia.so.0. From the maintainer-script however having
> [...]
>> I hope this helps to understand what's wrong in this case.
> 
> Good point!
> 
> Does anyone remember why bumblebee-nvidia depends on
>   nvidia-driver* | nvidia*-kernel-dkms
> 
> (complete Depends: bumblebee (= 3.2.1-25), glx-alternative-nvidia (>=
> 0.6.92), nvidia-driver | nvidia-tesla-450-driver |
> nvidia-tesla-440-driver | nvidia-tesla-418-driver |
> nvidia-legacy-390xx-driver | nvidia-legacy-340xx-driver |
> nvidia-driver-any | nvidia-kernel-dkms | nvidia-tesla-450-kernel-dkms |
> nvidia-tesla-440-kernel-dkms | nvidia-tesla-418-kernel-dkms |
> nvidia-legacy-390xx-kernel-dkms | nvidia-legacy-340xx-kernel-dkms)
> 
> That allows for a broken bumblebee-nvidia installation
>     nvidia-kernel-dkms + bumblebee-nvidia
> but we need at least the following additional driver components:
> * xserver-xorg-video-nvidia
> * nvidia-driver-libs
> 
> Joel, if you install the nvidia-driver metapackage, everything should 
> be
> fine for you.

Thanks, I'll comment out the additional blacklist entries and test with 
that package installed. Those lines aren't harmful in any other way that 
I see, but just unexpected from your original response?

Joel