1 |
Am Thu, 26 May 2011 16:28:46 -0700 |
2 |
schrieb "Kevin O'Gorman" <kogorman@×××××.com>: |
3 |
|
4 |
> It looks like it's time to take Gentoo off of my main machine. I feel a |
5 |
> little sad about it, or I'd just quietly go away. |
6 |
> |
7 |
> A few months ago, an update made the machine headless -- well, it could no |
8 |
> longer bring up X but I could use the console-mode for admin, and log in via |
9 |
> SSH from my laptop and run GUI programs. I was busy at the time, first |
10 |
> deciding and then implementing my retirement, so I let it go. |
11 |
> |
12 |
> Now, a couple of months into my retirement, I'm trying to fix things up, and |
13 |
> the latest Gentoo live disk cannot talk to my monitor at all. Whatever it's |
14 |
> trying is unacceptable to the HD monitor I've had on there for a year, and I |
15 |
> can't even run the consoles. The video card is an ATI Rage XL on the |
16 |
> motherboard. Like the rest of the machine, it's vintage 2000, so maybe |
17 |
> support got dropped. |
18 |
[...] |
19 |
|
20 |
(I realise your decision is made, but if this is the bug I think it is, this |
21 |
has nothing to do with Gentoo in particular.) |
22 |
|
23 |
I wonder which kernel version you use, because in 2.6.36/37 I was hit by a nasty |
24 |
EDID parsing bug. Actually, IIRC the code for parsing EDIDs was updated to |
25 |
understand more features or something, and that triggered errors that didn't |
26 |
come up before because those parts of the response from the monitor were simply |
27 |
ignored until then (or something like that). This lead to my own monitor not |
28 |
responding for over a minute at a time (sometimes going blank in between) and |
29 |
other people complained that it left theirs permanently blank. |
30 |
|
31 |
I think this is the original bug: |
32 |
|
33 |
https://bugs.freedesktop.org/show_bug.cgi?id=31943 |
34 |
|
35 |
which contains a workaround (with patch): |
36 |
|
37 |
"The drm EDID checker is pretty strict about what EDIDs it will accept. Try |
38 |
this patch and add drm.edid_strict=0 to your kernel command line." |
39 |
|
40 |
For me, upgrading to 2.6.38 helped, I don't see the problem anymore (though |
41 |
other people report otherwise). |
42 |
|
43 |
*If* this is the bug, it makes me wonder why you don't see it under Ubuntu. |
44 |
|
45 |
Good luck with Ubuntu! |
46 |
-- |
47 |
Marc Joliet |
48 |
-- |
49 |
"People who think they know everything really annoy those of us who know we |
50 |
don't" - Bjarne Stroustrup |