https://qa.mandrakesoft.com/show_bug.cgi?id=730
------- Additional Comments From [EMAIL PROTECTED] 2003-01-24 21:19 ------- Grr. I had to reboot this morning after X locked up. X would not start after rebooting, but as soon as I re-enabled ForceInit it worked again. Last time I had switched it off, I had done it after already running with ForceInit. So I'm not sure if there was some hardware function that had been set up that a fresh reboot didn't reset. It looks like the Red Hat 8.1beta users are running into the same thing though. They are recommending using Tim's test 1.2.27 driver like Hoyt suggested. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=80346 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=82394 Maybe we could move up to that version? ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: __UNKNOWN__ description: XFree86-4.2.99.3-1.20021223.3mdk (I am up to date with cooker as of Jan 2). The Savage driver will partially load, but the mouse becomes dreadfully slow and GNOME cannot fully load (i.e. the panel never even shows up). It basically gets to the point where it feels almost locked up. Sawfish doesn't get any further. Window Maker will load but there are lots of screen artifacts and you can't even see what you are typing in an xterm. Eventually it gets to that semi-locked up state. Switching to the 'vesa' driver is a temporary work-around.
