Branden Robinson writes: > On Sat, Nov 30, 2002 at 10:09:17PM -0500, Jerry Quinn wrote: > > Chris Halls writes: > > > I read this in Kernel Traffic #192. Could this be your problem? > > > > > Marcelo Tosatti announced 2.4.20-rc1 and included the BitKeeper > > summary. He > > > said, "Several networking fixes, net drivers fixes, devfs root boot > > option > > > fixed, and more." Carl-Daniel Hailfinger reported that his system would > > come > > > back up with a blank screen after a hardware suspend and resume. > > Switching > > > to another console and back again would fix it. He traced the problem to > > > 2.4.18-pre7, in the power management code; and Marcelo asked if he'd > > > actually reverted the part of the code he'd identified. Carl tried this > > and > > > found that his initial assessment was wrong. Instead, he traced the > > problem > > > all the way back to some framebuffer changes in 2.4.18-pre1. He posted a > > > > I don't think so. The problem below occurs as a result of fbdev > > suspending and shows up after resume. My problem is when the screen > > blanks after being idle for a while, and doing suspend/resume fixes > > it. Also, I don't use fbdev, because I don't get a working display at > > all with it. > > > > That said, I can pull down this kernel and give it a try. > > Did this have any effect on the problem?
Unfortunately no. I'm now running 2.4.21-4-686 and I still have the same problem. I haven't yet tried playing with X 4.3, though. BTW, I can also restore the screen by switching to a virtual console, pressing Fn-F3 which tells the bios? to blank the screen, wait a couple of seconds, hit any key such as Alt to turn the screen back on, then shift back to VC7 to return to my X display. This is the workaround I've been living with. Jerry
