ubuntu-x-swat team mailing list archive

["John S. Gruber" <JohnSGruber@xxxxxxxxx>]

@Jamie: Rats.

We don't need the plymouth:debug anymore. Would deleting it help? Can
you simply go back to where you were last night when you were getting
logs (albeit with the tty1 bug). If you can, maybe you can try Seth's
new gdm fix.

modeset and nomodeset are other possible things to try (I can't tell
from the log what it is doing, and I don't even know if the nvidia
driver supports kernel mode setting).

In grub the linux cmdline parameters matter, but nothing else should.
Grub should be loading the same kernel and initramfs into memory and
passing control to linux. The linux command line is the only way to tell
the kernel it just loaded to do anything different. The other parameters
just tell grub how to behave before it loads the kernel.

The xorg.0.log doesn't help. I can't tell if it is the same kind of
problem as in this and bug #626723 or not since it just says it's going
to give a backtrace and then doesn't.

A dmesg or syslog from when the crash occurs may contain more
information, you might look there. Attach them if you want us to take a
look. Is there an X log in something like :n.log.n that shows the error
with more output? It's one thing after another, I'm afraid.

-- 
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.net/bugs/625239
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.