| |||||||||||||
Um, what's the problem?Um, what's the problem?Posted Jul 8, 2010 7:30 UTC (Thu) by dwmw2 (subscriber, #2063)Parent article: Ask a kernel developer There's one really important thing missing from this — WHAT IS THE ACTUAL PROBLEM? Is the kernel misbehaving? Do you get a correct picture? Does your screen run at the wrong resolution? Or are you just trawling through the logs looking for something that offends your sensibilities? I've often had this kind of report from users, and the 'solution' has been to remove the nasty scary printk. There's not really been anything wrong at all.
(Log in to post comments)
Um, what's the problem? Posted Jul 8, 2010 8:15 UTC (Thu) by Los__D (guest, #15263) [Link]
If the kernel bitches for no reason, the kernel has a bug.
Um, what's the problem? Posted Jul 8, 2010 9:12 UTC (Thu) by pfavr (subscriber, #38205) [Link]
The problem that led me to ask this question is that I'm using a Lenovo X201 laptop (with ultrabase X200 dockingstation) to drive my HP LP3065 30" monitor (2560x1600). It sort of works, but occasionally (approx. 20 times a day) the screen goes black for half a second then comes back on again.
I've tried replacing the monitor (HP sent me a replacement) as well as cables, and the HP DisplayPort-to-dual-link-DVI-adapter used in my setup.
The X201 has a core i5 CPU with integrated Intel HD graphics (which also drives the DisplayPort output on the dockingstation.
I use Debian GNU/Linux "sid" 64bit and have had the best result using the stock Debian kernel.
As can be seen from the dmesg output there is a problem with parsing the EDID info coming from the monitor. Looking a bit closer it seems all bytes are repeated 4 times: HHHHPPPP and so on.
So I thought I might be able to help solving this problem, but where to start? I did know that grepping kernel sources would be a start but I think the article is really good because now I feel more "safe" posting an email to the relevant people and mailing list :-)
Um, what's the problem? Posted Jul 10, 2010 12:58 UTC (Sat) by alankila (subscriber, #47141) [Link]
This is interesting. I have a 30" monitor at 2560x1600, and it also goes black for about half a second once after a cold boot. It takes variable time for it to occur, usually in the order of 10 minutes, so it interrupts my work, but after it does it once, it works for the rest of the session.
I've never seen any clues for this strange behavior. I've not considered replacing the monitor, because this one works otherwise and I already played the warranty dance for a few months thanks to severe quality problems with Samsung SyncMaster 305T+.
|
|||||||||||||