Re: Hard Crash Xserver on Powerbook (Pismo) Sid
Hi, Brian Morris wrote: Hey I just did an update today at the console, and starting up the window system after, the Xserver hangs. There is a cursor but no menu action and no out via function keys, plus the cursor doesn't move anyway, so I had no choice other than a hard reset restart (Clover-Option-Power keys). I can try reconfiguring the server first (I have a very plain system here, just openbox wm with a startx manual start), and/or I can test it by ssh line in case it is just the server/ keyboard hanging. My macmini here dies whenever I try to launch an opengl application (like glxgears, glxinfo alone is alright though). When I say it dies, its: hard freeze, cannot ping the poor thing throught network and it just stand frozen here until the hard reset. I didn't have time to investigate, but if you have a composite desktop manager, you may want to desactivate that to see if your Tibook survives the X start up. Hope that helps, -- Luigi -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Hard Crash Xserver on Powerbook (Pismo) Sid
On Mon, Nov 16, 2009 at 12:27 PM, Stephane Louise luigi+onl...@nerim.netluigi%2bonl...@nerim.net wrote: Hi, Brian Morris wrote: Hey I just did an update today at the console, and starting up the window system after, the Xserver hangs. I can try reconfiguring the server first (I have a very plain system here, just openbox wm with a startx manual start), and/or I can test it by ssh line in case it is just the server/ keyboard hanging. My macmini here dies whenever I try to launch an opengl application (like glxgears, glxinfo alone is alright though). When I say it dies, its: hard freeze, cannot ping the poor thing throught network and it just stand frozen here until the hard reset. I didn't have time to investigate, but if you have a composite desktop manager, you may want to desactivate that to see if your Tibook survives the X start up. Openbox I run is just a simple window manager. However I could try turning off acceleration of the server driver or even using a generic driver. These things have happened before and sometimes it was a bug and sometimes it was requiring to reconfigure the server options. but its interesting you can't even ping in. I wonder if that could be a kernel bug, the driver problem shouldn't kill the whole OS, should it ? however if you start the server remotely you may see error messages which otherwise are covered up and lost. I did that before too. just lazy now and a bit discouraged around obsolence issues in Debian in general not knowing if it is powerpc or debian or what. Anyway it has been a rather disappointing year for me with Debian and LInux with breakages over incompatibilities. Now I understand why some people keep a copy of old-stable around (which is Etch right now). brian
Re: Hard Crash Xserver on Powerbook (Pismo) Sid
Brian == Brian Morris cymraeg...@gmail.com writes: Brian but its interesting you can't even ping in. I wonder if that Brian could be a kernel bug, the driver problem shouldn't kill the Brian whole OS, should it ? It certainly will if the video driver is living in kernel space. It's almost definitely living in kernel space. Brian however if you start the server remotely you may see error Brian messages which otherwise are covered up and lost. I did that Brian before too. Brian just lazy now and a bit discouraged around obsolence issues Brian in Debian in general not knowing if it is powerpc or debian Brian or what. Anyway it has been a rather disappointing year for Brian me with Debian and LInux with breakages over Brian incompatibilities. Now I understand why some people keep a Brian copy of old-stable around (which is Etch right now). I'm worried about the PPC platform too, but I've got this G5, and it still works... Also Brian -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
suspend/off on a G5
Well I suspend and power-off doesn't seem to work quite right on my g5. suspend looks like it's trying but it wakes up immediately: Initial commandline parameters: Sun Nov 15 22:29:46 PST 2009: Running hooks for suspend. /usr/lib/pm-utils/sleep.d/00clear suspend: success. /usr/lib/pm-utils/sleep.d/05led suspend: not applicable. /usr/lib/pm-utils/sleep.d/10NetworkManager suspend: success. /usr/lib/pm-utils/sleep.d/49bluetooth suspend: not applicable. /usr/lib/pm-utils/sleep.d/50modules suspend: not applicable. /usr/lib/pm-utils/sleep.d/90clock suspend: success. /usr/lib/pm-utils/sleep.d/94cpufreq suspend: success. /usr/lib/pm-utils/sleep.d/95led suspend: not applicable. /usr/lib/pm-utils/sleep.d/98smart-kernel-video suspend: not applicable. /usr/lib/pm-utils/sleep.d/99video suspend: success. Sun Nov 15 22:29:48 PST 2009: performing suspend ioctl: Invalid argument at - line 4. Sun Nov 15 22:29:48 PST 2009: Awake. Sun Nov 15 22:29:48 PST 2009: Running hooks for resume /usr/lib/pm-utils/sleep.d/99video resume: success. /usr/lib/pm-utils/sleep.d/98smart-kernel-video resume: success. /usr/lib/pm-utils/sleep.d/95led resume: not applicable. /usr/lib/pm-utils/sleep.d/94cpufreq resume: success. /usr/lib/pm-utils/sleep.d/90clock resume: success. /usr/lib/pm-utils/sleep.d/50modules resume: success. /usr/lib/pm-utils/sleep.d/49bluetooth resume: not applicable. /usr/lib/pm-utils/sleep.d/10NetworkManager resume: success. /usr/lib/pm-utils/sleep.d/05led resume: not applicable. /usr/lib/pm-utils/sleep.d/00clear resume: success. Sun Nov 15 22:29:49 PST 2009: Finished. Is this a kernel problem, or maybe something which can be helped with some configuration magic ? Thanks, Brian -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
