Bug#976056: nvidia-legacy-340xx-driver: Fails to build with kernel 5.9.11 (package linux-image-5.9.0-4-amd64)

2020-12-07 Thread Paolo Inaudi
About that rule, the only way to prevent breaking testing would have been
marking this bug as release critical not for this package, but for the
linux kernel package.
Which in turn would mean holding off new kernel releases from debian until
a proprietary legacy driver is fixed, which might never happen since nvidia
officially discontinued this driver.
Also remember that this package is in non-free, which is considered to be
not part of debian.

AFAIU it depends on turning a flag in kernel compilation, and I don't
understand what it does but I trust it was shutdown for good reason.

Just saying IMHO we shouldn't be mad at debian for what happened, just hope
someone will find a way to fix it.

Paolo


Il lun 7 dic 2020, 02:12 Del Fernandes  ha scritto:

> It was quite disappointing to see (or not see) the GUI/WM stop working
> after a causal system update (not upGrade).
>
> I was able to get the system somewhat back to  normal by using the
> NOUVEAU driver instead of NVIDIA. BTW, even that was kind of tricking
> because the Nvidia driver blacklisted Nouveau at
> /etc/modprobe.d/nvidia-blacklists-nouveau.conf which remained  even
> after purging everything related to Nvidia via APT.
>
> PS.: For some reason, the laptop no longer revived with Nouveau after
> a suspend (closing the laptop's lid). That was "bypassed" in the
> meantime by editing /etc/systemd/logind.conf and replacing all
> "suspends" with "ignores".
>
> Again, that was very disappointing !8-(. What happened with the golden
> 'Do no harm, don't break users' rule?!
>
> On Sun, Dec 6, 2020 at 1:33 PM Paolo Inaudi  wrote:
> >
> > @jim_p Is it possible for you to avoid putting all system information
> > and Xorg logs in every message?
> > It makes the thread very difficult to follow on the online bug tracker.
> >
> > I too rolled back to linux-image-5.9.0-3-amd64 which works, hope it
> > won't be my very last kernel version.
> >
> > --
> > To unsubscribe, send mail to 976056-unsubscr...@bugs.debian.org.
>
> --
> To unsubscribe, send mail to 976056-unsubscr...@bugs.debian.org.
>


Bug#976056: nvidia-legacy-340xx-driver: Fails to build with kernel 5.9.11 (package linux-image-5.9.0-4-amd64)

2020-12-06 Thread Del Fernandes
It was quite disappointing to see (or not see) the GUI/WM stop working
after a causal system update (not upGrade).

I was able to get the system somewhat back to  normal by using the
NOUVEAU driver instead of NVIDIA. BTW, even that was kind of tricking
because the Nvidia driver blacklisted Nouveau at
/etc/modprobe.d/nvidia-blacklists-nouveau.conf which remained  even
after purging everything related to Nvidia via APT.

PS.: For some reason, the laptop no longer revived with Nouveau after
a suspend (closing the laptop's lid). That was "bypassed" in the
meantime by editing /etc/systemd/logind.conf and replacing all
"suspends" with "ignores".

Again, that was very disappointing !8-(. What happened with the golden
'Do no harm, don't break users' rule?!

On Sun, Dec 6, 2020 at 1:33 PM Paolo Inaudi  wrote:
>
> @jim_p Is it possible for you to avoid putting all system information
> and Xorg logs in every message?
> It makes the thread very difficult to follow on the online bug tracker.
>
> I too rolled back to linux-image-5.9.0-3-amd64 which works, hope it
> won't be my very last kernel version.
>
> --
> To unsubscribe, send mail to 976056-unsubscr...@bugs.debian.org.



Bug#976056: nvidia-legacy-340xx-driver: Fails to build with kernel 5.9.11 (package linux-image-5.9.0-4-amd64)

2020-12-06 Thread Paolo Inaudi
@jim_p Is it possible for you to avoid putting all system information 
and Xorg logs in every message?

It makes the thread very difficult to follow on the online bug tracker.

I too rolled back to linux-image-5.9.0-3-amd64 which works, hope it 
won't be my very last kernel version.




Processed: Re: Bug#976056: nvidia-legacy-340xx-driver: Fails to build with kernel 5.9.11 (package linux-image-5.9.0-4-amd64)

2020-11-30 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 serious
Bug #976056 [nvidia-legacy-340xx-driver] nvidia-legacy-340xx-driver: Fails to 
build with kernel 5.9.11 (package linux-image-5.9.0-4-amd64)
Ignoring request to change severity of Bug 976056 to the same value.
> retitle -1 nvidia-legacy-340xx-driver: requires DRM_LEGACY, disabled from 
> Linux 5.9.11 onwards
Bug #976056 [nvidia-legacy-340xx-driver] nvidia-legacy-340xx-driver: Fails to 
build with kernel 5.9.11 (package linux-image-5.9.0-4-amd64)
Changed Bug title to 'nvidia-legacy-340xx-driver: requires DRM_LEGACY, disabled 
from Linux 5.9.11 onwards' from 'nvidia-legacy-340xx-driver: Fails to build 
with kernel 5.9.11 (package linux-image-5.9.0-4-amd64)'.
> tag -1 upstream wontfix
Bug #976056 [nvidia-legacy-340xx-driver] nvidia-legacy-340xx-driver: requires 
DRM_LEGACY, disabled from Linux 5.9.11 onwards
Added tag(s) upstream and wontfix.

-- 
976056: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976056
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#976056: nvidia-legacy-340xx-driver: Fails to build with kernel 5.9.11 (package linux-image-5.9.0-4-amd64)

2020-11-30 Thread Andreas Beckmann
Control: severity -1 serious
Control: retitle -1 nvidia-legacy-340xx-driver: requires DRM_LEGACY, disabled 
from Linux 5.9.11 onwards
Control: tag -1 upstream wontfix

On 11/29/20 1:37 PM, Salvatore Bonaccorso wrote:
> Some background: In the 5.9.11-1 upload for src:linux we disabled
> NOUVEAU_LEGACY_CTX_SUPPORT which was keeping DRM_LEGACY enabled (cf.
> #975038). The intention of disabling DRM_LEGACY was actually already
> much earlier in 5.5.17-1, but due to the above it was kept enabled
> until noticed now.

Thanks for that information.

Andreas



Bug#976056: nvidia-legacy-340xx-driver: Fails to build with kernel 5.9.11 (package linux-image-5.9.0-4-amd64)

2020-11-29 Thread jim_p
Package: nvidia-legacy-340xx-driver
Version: 340.108-8
Followup-For: Bug #976056
X-Debbugs-Cc: pitsior...@gmail.com

What does this mean for a simple user like me? Is it the end for nvidia 340xx
on debian? I do not want to move to nouveau at all!



-- Package-specific info:
uname -a:
Linux mitsos 5.9.0-3-amd64 #1 SMP Debian 5.9.9-1 (2020-11-19) x86_64 GNU/Linux

/proc/version:
Linux version 5.9.0-3-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 
10.2.0-17) 10.2.0, GNU ld (GNU Binutils for Debian) 2.35.1) #1 SMP Debian 
5.9.9-1 (2020-11-19)

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 11 11:06:58 
PST 2019
GCC version:  gcc version 10.2.0 (Debian 10.2.0-16) 

lspci 'display controller [030?]':
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT218 [GeForce 
210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. GT218 [GeForce 210] [1043:8490]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: nvidia
Kernel modules: nvidia

dmesg:
[0.152829] Console: colour VGA+ 80x25
[0.588999] pci :01:00.0: vgaarb: setting as boot VGA device
[0.588999] pci :01:00.0: vgaarb: VGA device added: 
decodes=io+mem,owns=io+mem,locks=none
[0.588999] pci :01:00.0: vgaarb: bridge control possible
[0.588999] vgaarb: loaded
[0.774373] Linux agpgart interface v0.103
[3.313635] nvidia: loading out-of-tree module taints kernel.
[3.313648] nvidia: module license 'NVIDIA' taints kernel.
[3.36] nvidia: module verification failed: signature and/or required 
key missing - tainting kernel
[3.377540] nvidia :01:00.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=none:owns=io+mem
[3.380024] [drm] Initialized nvidia-drm 0.0.0 20150116 for :01:00.0 on 
minor 0
[3.380037] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 
11 11:06:58 PST 2019
[3.857599] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client
[3.946126] input: HDA NVidia HDMI/DP,pcm=3 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input10
[3.946211] input: HDA NVidia HDMI/DP,pcm=7 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input11
[3.946298] input: HDA NVidia HDMI/DP,pcm=8 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input12
[3.946400] input: HDA NVidia HDMI/DP,pcm=9 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input13
[   11.072539] caller _nv000788rm+0xe4/0x1c0 [nvidia] mapping multiple BARs

Device node permissions:
crw-rw+ 1 root video 226,   0 Nov 30 06:54 /dev/dri/card0
crw-rw-rw-  1 root root  195,   0 Nov 30 06:55 /dev/nvidia0
crw-rw-rw-  1 root root  195, 255 Nov 30 06:55 /dev/nvidiactl

/dev/dri/by-path:
total 0
lrwxrwxrwx 1 root root 8 Nov 30 06:54 pci-:01:00.0-card -> ../card0
video:*:44:jim

OpenGL and NVIDIA library files installed:
lrwxrwxrwx 1 root root   15 Jun  8 11:36 /etc/alternatives/glx -> 
/usr/lib/nvidia
lrwxrwxrwx 1 root root   44 Jun  8 11:36 
/etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libEGL.so.1
lrwxrwxrwx 1 root root   43 Jun  8 11:36 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   43 Jun  8 11:36 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   25 Jun  8 11:36 
/etc/alternatives/glx--linux-libglx.so -> /usr/lib/nvidia/libglx.so
lrwxrwxrwx 1 root root   42 Jun  8 11:36 
/etc/alternatives/glx--nvidia-blacklists-nouveau.conf -> 
/etc/nvidia/nvidia-blacklists-nouveau.conf
lrwxrwxrwx 1 root root   36 Jun  8 11:36 
/etc/alternatives/glx--nvidia-bug-report.sh -> 
/usr/lib/nvidia/nvidia-bug-report.sh
lrwxrwxrwx 1 root root   39 Jun  8 11:36 
/etc/alternatives/glx--nvidia-drm-outputclass.conf -> 
/etc/nvidia/nvidia-drm-outputclass.conf
lrwxrwxrwx 1 root root   28 Jun  8 11:36 
/etc/alternatives/glx--nvidia-load.conf -> /etc/nvidia/nvidia-load.conf
lrwxrwxrwx 1 root root   32 Jun  8 11:36 
/etc/alternatives/glx--nvidia-modprobe.conf -> /etc/nvidia/nvidia-modprobe.conf
lrwxrwxrwx 1 root root   29 Jun  8 11:36 
/etc/alternatives/glx--nvidia_drv.so -> /usr/lib/nvidia/nvidia_drv.so
lrwxrwxrwx 1 root root   28 Jan  5  2020 /etc/alternatives/nvidia -> 
/usr/lib/nvidia/legacy-340xx
lrwxrwxrwx 1 root root   57 Jan  5  2020 
/etc/alternatives/nvidia--libEGL.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/legacy-340xx/libEGL.so.1
lrwxrwxrwx 1 root root   56 Jan  5  2020 
/etc/alternatives/nvidia--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/legacy-340xx/libGL.so.1
lrwxrwxrwx 1 root root   56 Jan  5  2020 

Bug#976056: nvidia-legacy-340xx-driver: Fails to build with kernel 5.9.11 (package linux-image-5.9.0-4-amd64)

2020-11-29 Thread Salvatore Bonaccorso
Hi,

On Sun, Nov 29, 2020 at 07:17:06AM +0200, jim_p wrote:
> Package: nvidia-legacy-340xx-driver
> Version: 340.108-8
> Severity: normal
> X-Debbugs-Cc: pitsior...@gmail.com
> 
> Dear Maintainer,
> 
> That was unexpected! I noticed that kernel 5.4.11 reached unstable today, so I
> upgraded to it and nvidia 340 fails to build again! Here is the log.
> 
> https://gist.github.com/pitsi/aed70f236a7169d270cfc92099096b20
> 
> p.s. Because the log is too big (1+MB) for any pastebin service, I uploaded it
> as a gist on my github account.

Some background: In the 5.9.11-1 upload for src:linux we disabled
NOUVEAU_LEGACY_CTX_SUPPORT which was keeping DRM_LEGACY enabled (cf.
#975038). The intention of disabling DRM_LEGACY was actually already
much earlier in 5.5.17-1, but due to the above it was kept enabled
until noticed now.

Regards,
Salvatore