Note, I took the lazy way out changed hardware around. I think that
motherboard and video card could be available for me to mess with it if
need be and time permits... but... unless my help is really needed...
I've taken the "if it doesn't work when I do that, then don't do that"
approach... I don
I will try all the suggestions, I tried for a while with no DRI Accel
etc. without it crashing, but not long enough to be sure. Probably
tomorrow I could put it back in. For today, I need to get work done, so
have stuck an NV in there for today...
Actually, I guess this is a useful test, too, if
I need to have the machine stay up in X for a while, so I've swapped out
the ATI for an NV for now, later I can make it crash again for debugging
when someone is ready to help look at it, or when a driver update
appears... the card that freezes btw is a Sapphire ATI Radeon 9550 R9550
256M DDR AGP V
Welp... I think I'm up to about 20 hours of text console with dstat
running, without a lockup. So I guess you are right, something in the
video driver or whatever... Guess I can stick a different video card in
it and the problem will go away...
--
Jaunty locks up
https://bugs.launchpad.net/bugs
Guess I should probably turn off GLX, too, then if it doesn't crash in
X, turn the options on one by one.
--
Jaunty locks up
https://bugs.launchpad.net/bugs/374831
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
__
Well, it made it overnight in console mode! Of course, it has made it
through 8 hours of jaunty-X, (but never 24 hours of jaunty-X ...) I'll
continue to leave it in text mode for another 30-40 hours to be more
sure, then I'll start playing with the acceleration options and leave it
in X again. U
I'm going to do a simple test for if it is an X bug. I'm going to do
"/etc/init.d/gdm stop", and go to bed with it on a linux text console.
If it stays up for a couple days using it in console mode only, it must
be an X bug. If it locks up without X running, I guess it wouldn't
be...
--
Jaunty
** Attachment added: ".xsession-errors"
http://launchpadlibrarian.net/26744286/.xsession-errors
--
Jaunty locks up
https://bugs.launchpad.net/bugs/374831
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
___
** Attachment added: "Xorg.0.log"
http://launchpadlibrarian.net/26744256/Xorg.0.log
--
Jaunty locks up
https://bugs.launchpad.net/bugs/374831
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
___
Hmmm, not sure you read the earlier description carefully...
ctrl+alt+f1 as I said no keyboard input works. Including alt-sysrq-b etc.
ctrl+alt+backspace see above
mouse pointer - there has never still been a mouse pointer. About 20 crashes
so far have been 18 black screen and 2 some remnant of
10 matches
Mail list logo