Your message dated Sun, 28 Nov 2010 20:39:43 +0100
with message-id <[email protected]>
and subject line Re: nvidia-kernel-source: monitor EDID stopped working
has caused the Debian Bug report #462139,
regarding nvidia-kernel-source: monitor EDID stopped working
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 [email protected]
immediately.)
--
462139: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=462139
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: nvidia-kernel-source
Version: 169.07-2
Severity: grave
Justification: renders package unusable
After upgrading, I get the follow in Xorg.log:
(WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-1
Which somehow causes X11 to run in a 640x480 mode making it completely
unusable. Likely the real bug is how X11 chooses 640x480 as fallback, but
still, the cause apparently is this EDID thing whatever it is.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.23-2008-01-21 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages nvidia-kernel-source depends on:
ii debhelper 6.0.3 helper programs for debian/rules
ii dpatch 2.0.28 patch maintenance system for Debia
ii make 3.81-3 The GNU version of the "make" util
ii sed 4.1.5-5 The GNU sed stream editor
Versions of packages nvidia-kernel-source recommends:
pn devscripts <none> (no description available)
ii kernel-package 11.001-0.1 A utility for building Linux kerne
ii nvidia-glx 169.07-2 NVIDIA binary Xorg driver
-- no debconf information
--- End Message ---
--- Begin Message ---
On Wednesday, 25. August 2010 06:05:25 Andreas Beckmann wrote:
> Please test if this is working again in the current driver version,
> 195.36.31-2 entered unstable yesterday.
Since we haven't heard from the submitter since we asked for more information
a few months ago, I assume the problem does no longer exist and I'm closing
this report now.
If the problem is still reproducible with current driver versions (195.36.31-6
in testing/unstable or 260.19.21-1 in experimental), feel free to reopen this
bug report.
Andreas
--- End Message ---
