--Signature_Thu__23_Jun_2005_11_21_27_-0400_P0qxpJ.cFQ_Cy7NJ
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hello,

apparently the screen blanking code either in XFree86 or in our ffb
driver causes some corruption with some ffb boards. Not always though.
Usually it happens after blanking the screen ( xset s noexpose; xset s
blank to turn on blanking / no logo display, then xset s activate to
start the built-in screensaver. Be fast, releasing the key too late may
end the screensaver ). It doesn't happen with screensavers that display
something and therefore need a complete redraw on unblank anyway.  So
far this has been observed on FFB1 boards with PAC1 DAC only - I can't
reproduce it on my FFB2+ ( PAC2 DAC), and apparently no one else can
either. It doesn't always happen, you might have to try a few times.
So - does anyone else have this problem? If so - what kind of hardware?

I suspect this problem to be either FFB1 or PAC1 specific but I need
more information to be sure. /var/log/XFree86.0.log will tell you what
kind of board / DAC you have. The relevant part of mine looks like this:

(II) /dev/fb0: Detected FFB2+/vertical, Z-buffer, Double-buffered.
(II) /dev/fb0: BT498 (PAC2) ramdac detected
(II) /dev/fb0: Detected Creator/Creator3D

have fun
Michael

--Signature_Thu__23_Jun_2005_11_21_27_-0400_P0qxpJ.cFQ_Cy7NJ
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (NetBSD)

iQEVAwUBQrrTd8pnzkX8Yg2nAQLRIQf/V69s7bti7rTVcqThwDFn5UeRESG8ap7T
vXB1tD4NnBXOGj0ulMyFhG86I3S9swmvMUzeGxjv33jH3UqKfUHB2IeN4v4k6g1D
3JxbNYlQFlMsmMoCArtnSXSUgoFpQHUAMklW9isC0oT1TPoPgE/Msv5c9CPRiqB/
kWItyvnHYcyywgTmw2qnJhTONX8n0pXrdFywhSoY+W/UAvZz4Uuzp+2OQwCAZqdZ
yusy8Y+lfkgW6ZAl1AC3LE7nbDGIwZPWNSFarg72czS/Wz/B9mwVnjEOcf2L+ShM
tD6LzcCj4W/TgoHSmjnurtElcGuhPjAPrDy2nqYXhehvBTeJerR/Sg==
=ISdR
-----END PGP SIGNATURE-----

--Signature_Thu__23_Jun_2005_11_21_27_-0400_P0qxpJ.cFQ_Cy7NJ--