Source: linux Followup-For: Bug #953680 I just got the email that notified me that this bug report was closed because kernel 5.5 (5.5.13 in fact) has reached unstable. Kernel 5.6 was released yesterday from upstream, so isn't it a bit late now for 5.5?
Normally, I install it as soon as it hits the repo, then I let dkms fail in building nvidia legacy 340 for it, so I file a bug report for the driver, along with the needed patches. I think I will skip it this time and wait for 5.6, sorry. On top of that, I think that you should have built at least one minor update of 5.4 all that time, because the 5.4 is now at 5.4.28, 9 minor versions ahead than the one on the repo. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-4-amd64 (SMP w/2 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:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
