https://qa.mandrakesoft.com/show_bug.cgi?id=730
------- Additional Comments From [EMAIL PROTECTED] 2003-01-03 23:54 ------- I can confirm that using the ForceInit option fixes the driver for me as well. Looking at the driver homepage it appears that ForceInit was designed to fix the X-to-console switching garbage though. So it should be optional. I guess XFree86 CVS just doesn't have all of Tim's bits from the latest .26t driver yet then. ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] 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.
