Is it possible that this is caused by the particular kernel settings that handle power saving? I have had a long going problem, with a rather antiquated Radius monitor, that the monitor has clicked off (not powered down, but the LED turned orange, and there was no picture) if left a long time. The only way to get the picture back was to turn off the monitor and hit a key or the mouse, then turn on the monitor again.
When powering up, there is a click (I thought the video card?) after which the monitor can be turned on. If the monitor is turned on before that, there will not be a picture, until the monitor is powered down, the keyboard touched, and the monitor powered up again. After extensive study of the kernel parameters, while learning Gentoo, I have the same system working without the monitor clicking off any more: I do have to hit the space bar, etc., if the monitor is left a while, though, and when powering up I am still careful to wait until after the click from the CPU region before turning the monitor on. The previous behavior was exhibited with Ubuntu, Debian (Knoppix), and MEPIS, before moving to Gentoo. Alan Davis On 3/9/06, Daniel da Veiga <[EMAIL PROTECTED]> wrote: > On 3/8/06, A.R.S. KA9QLQ Alvin Koffman <[EMAIL PROTECTED]> wrote: > > --- Daniel da Veiga <[EMAIL PROTECTED]> wrote: > > > > > > > Well, it would be the safest way. But now that you mentioned it, I > > > only tested in my machine (ATI, old one) and another server (NVidia, > > > FX5200), both loaded without Direct Rendering and using VESA (but that > > > could be result of failed autodetection). I think I'll ask at the devs > > > list. > > > > > The fx 5200 is what I have but live cd kills the display. > > Well, NVidia opensource drivers are know for reliability, that > excludes a weird driver/device configuration, VESA or NV, both drivers > should work OK. > > Holly's theory, > > "That certainly would explain things, but how broken would autodetection > then be (or the monitor's EDID?? support) if it couldn't even > detect/report its own Vsync range?" > > Its my best bet by now. I would try another monitor and see what > happens. May be a hardware problem after all... > > > Alvin > > > > For the best jerky you've ever had go to > > http://alk.jerkydirect.com/ > > My home page > > http://ka9qlq.tripod.com > > This PC is windows free with Mepis Linux 3.4-3 > > http://www.mepis.org/ > > 1(747)632-4973 SIP > > Get Gizmo 1 cent per minuet calling > > http://www.gizmoproject.com/ > > -- > > gentoo-user@gentoo.org mailing list > > > > > > > -- > Daniel da Veiga > Computer Operator - RS - Brazil > -----BEGIN GEEK CODE BLOCK----- > Version: 3.1 > GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V- > PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++ > ------END GEEK CODE BLOCK------ > > -- > gentoo-user@gentoo.org mailing list > > -- gentoo-user@gentoo.org mailing list
