(I am not subscribed to the list, so please CC your replies to me.)
Hello,
Recently I've been giving the 2.6.0-test kernels a try. With all of
them I've encountered screen corruption problems with matroxfb on my
G400. Let me explain:
Right now I have 2.6.0-test4 compiled (I've also used -test1-ac1,
-test2 and -test3), and of course I've compiled in support for
matroxfb. In particular, I have the following framebuffer related
options enabled:
CONFIG_FB=y
CONFIG_FB_MATROX=y
CONFIG_FB_MATROX_G450=y
CONFIG_FB_MATROX_G100=y
In addition, matrofb gets initialised by the following boot
parametre:
video=matroxfb:pixclock:10582,xres:1024,right:48,hslen:96,left:208,\
yres:768,lower:1,vslen:3,upper:36,sync:0,depth:8
So at boot-time I get a nice 128x48 character (1024x768 pixel)
display. By the way, when matroxfb first initialises, there is a
white-filled area on top, that soon disappears because of scrolling.
But this is purely cosmetic; it would be nice if it wasn't there, but
it doesn't concern me. But I digress.
If I don't start X, everything is working just fine. But once I've
started it (XFree86 4.3.0), if I switch back to the VCs I start
getting screen corruption. It occurs when some area of the screen is
cleared or scrolled down, and it manifests in the form of semi-random
pixels (they seem to originate from existing or previous characters)
being drawn all over the screen. The problem persists even after X has
been shut down.
Well, that's all. I'm willing to try out experimental patches, and
generally help in any way I can to have the problems I'm seeing fixed.
Thanks in advance,
Vasilis
P.S. There's another set of display problems I'm experiencing with
2.4's matroxfb and XFree86 on my G400 (and I know I'm not the only
one). These are much more obscure, but if anyone is interested in
dealing with them, I can post a description for starters.
--
Vasilis Vasaitis
vv...@ha...
+306976604701
|
