On Wed, Apr 13, 2005 at 10:21:42AM +1000, Benjamin Herrenschmidt wrote: > On Tue, 2005-04-12 at 18:43 +0200, Paul van Tilburg wrote: > > The first time I had this, I thought it was a glitch, and several > > reboots seems to remedy the problem, but now, I can't a normal working > > display working. I have booted with video=ofonly (actually > > video=radeonfb video=ofonyl, since the first video entry is hardcoded in > > my yaboot.conf) and that works... but since I can't adjust the > > brightness and stuff this is not exactly ideal. > > > > I've used OS X a few days ago, maybe it changed something in the > > firmware... from dmesg I can't see anything different from other > > Powerbook outputs and since I don't see a thing, it's hard to find the > > problem and I have no idea where to start... > > Any ideas/hints/pointers? > > > > This is weird. I have the same model and no problem at all ... can you > send me the dmesg log when the problem occurs ? Also, what if you use > fblevel 0 to bring it down, then fblevel 15 to bring it back up (15 is > the max value). Does it help ?
I tried the fblevel thing back then, something happens, but it just gives the nice white-glowing-to-purple/black display. Anyway, when I booted this morning (one can not suspend with video=ofonly, the backlight stays on in suspend?) the fb seemed to work again, except for X, that didn't work as before... I went to the university, remembered that backlight would stay on so did a remote `sudo radeontool light off` and hoped it worked. When I got back home and rebooted to produce the dmesg log you requested, everything worked again. So, I hope I'll never have it again, if I do, you'll get that dmesg log :) Thanks a lot anyway! Regards, Paul -- Student @ Eindhoven | email: [EMAIL PROTECTED] University of Technology, The Netherlands | JID: [EMAIL PROTECTED] >>> Using the Power of Debian GNU/Linux <<< | GnuPG key ID: 0x50064181 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
