On Thu, Oct 29, 2009 at 03:12:49PM -0000, Martin Pitt wrote: > It wouldn't help for this particular problem, since you need X for > jockey.
Actually, there is a command line version of jockey -- I've had to use it when the open source drivers didn't cope well with the hardware I've got. For this specific issue, however, if you've got access to a shell (and gdm restarting repeatedly isn't preventing you from typing into it), the easiest thing to do is to just delete the xorg.conf entirely; then X will come up in VESA mode quite happily. That's the other weird aspect to this bug that ought to be fixed is X's differing behavior around a mildly bogus xorg.conf versus a non-existent one. > However, it does sound like a good idea anyway. Can you please open a > new jockey bug about this? Please assign it to me, jockey bugs are a > mess right now. Bug 463464 opened, thanks. -- Steve Beattie <[email protected]> http://NxNW.org/~steve/ -- No "safe" fallback on broken xorg.conf or missing driver https://bugs.launchpad.net/bugs/457443 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
