https://qa.mandrakesoft.com/show_bug.cgi?id=730





------- Additional Comments From [EMAIL PROTECTED]  2003-01-07 20:40 -------
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


A similar thing happened to me, in that it was highly pixelated, but it
did not resize the screen, rather, about 3 out of 4 pixels per square
seemed to be off (blank).  I run IceWM and the nv driver.  It also
showed up after a reboot, but I let it sit for about an hour and it
worked normally after that.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+Gyqvlp7v05cW2woRAo8qAJ9X/GGDDZeK4y2LcLYPUxtMLmQBDgCgo7rq
5Xk3aTippPQ7O/s7eMv22aU=
=mMfX
-----END PGP SIGNATURE-----


------- Additional Comments From [EMAIL PROTECTED]  2003-01-14 05:27 -------
With the XFree86-4.2.99.4-0.20030110.1mdk update, the Savage driver is totally
hosed now. With or without the ForceInit option you get nothing but garbage on
the screen. Again switching to vesa driver is a temporary work-around.



------- 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.

Reply via email to