Bug#794973: marked as done (Upgrade to Jessie kernel 3.16 breaks Xserver early in boot process with old nVidia card[Quadro NVS 440])
Your message dated Sun, 09 May 2021 05:19:32 -0700 (PDT)
with message-id <6097d354.1c69fb81.62544.2fdc@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #794973,
regarding Upgrade to Jessie kernel 3.16 breaks Xserver early in boot process with old nVidia card[Quadro NVS 440]
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
794973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794973
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: Upgrade to Jessie kernel 3.16 breaks Xserver early in boot process with old nVidia card[Quadro NVS 440]
- From: Barry Say <barry15@nspipes.co.uk>
- Date: Sat, 08 Aug 2015 21:47:52 +0100
- Message-id: <55C66AF8.6060906@nspipes.co.uk>
Package: linux-image-3.16
Version: 3.16.7
Upgrading to Jessie (kernel 3.16) lost my display. Early in the boot
process, (when the resolution changes) no further output occurs. The
boot process is successful in that I can access via ssh.
Reverting to kernel 3.2 avoids the problem. An installation of testing
(kernel 4.0) works well, as does unstable (4.1).
--- End Message ---
--- Begin Message ---
Hi
This bug was filed for a very old kernel or the bug is old itself
without resolution.
If you can reproduce it with
- the current version in unstable/testing
- the latest kernel from backports
please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.
Regards,
Salvatore
--- End Message ---
Reply to: