On Wed, 27 Nov 2002, Panagiotis Papadakos wrote: >I have the following two problems with my Matrox... > >a) The new cursor with the whiteglass theme, sometimes is rendered with a > dark red colour, especially when the cursor is over a textbox or the > edjes of a button.
Yes, this is easily reproduceable, and has been present since whiteglass went in. It is most noticeable in Red Hat Linux 8.0 when running Evolution and using the calendar views. This is a cursor bug, whoever created the cursors used redglass as a base, but didn't finish it off properly it seems, so redglass gets used sometimes. > Also because I am using my Matrox dualheaded, sometimes the cursor is > drawn on the second head despite the fact that the mouse cursor is on > the first head. This probably has nothing to do with the colour of the > cursor (if the cursor is rendered dark red or white). So sometimes my > second screen may get corrupted with many cursors drawn on it, and I > have to place a window over them, in order to clear it. I've also heard this reported. I believe this is due to the Matrox driver's render acceleration being broken if Xinerama is used. I've got a test driver on ftp://people.redhat.com/mharris/test-drivers/mga_drv.o that resolves this. If you test it, please let me know if it also resolves the cursor issue for you as I suspect. >b) Also sometimes the same happens and with anti-aliased fonts, especially > when I am doing something which for example scrolls down very fast my > terminal which uses anti-aliased fonts. For example if I run configure > on my anti-aliased kosnole. Most of the times the fonts are drawn at > the left side of my second screen, which has a smaller resolution than > my first head (1024x768 instead of 1280x1024). Also the fonts which > are drawn in the second head are whole lines from the application > which scrolls very fast on the first head. Most of the times this > happens with some mouse cursors around him, as I described in problem > a). Yep, my above driver was created to test fix this problem. Actually, it isn't a fix, it is a workaround for now. >I am using mga_hal_drv.o, but probably this is not the problem, >because I tried once an Xserver without loading mga_hal_drv.o >and the cursor again changed colours. Without mga_hal_drv.o I >can't have dualhead mode, so I don't know for the other >problems. No, it's definitely not a hallib bug. Easily reproduceable in 4.2.0 and higher at least using the stock mga driver with Xinerama, and anything that uses Xrender, with G400, G450, G550 >When I used Option "NoAccel" "1", everything works fine, but the server is >too slow.... Yes that will work around the problem also, but there is a faster workaround. I won't tell you what though, because I want you to test my driver, so I can troubleshoot the true cause of this and hopefully fix it. ;o) >As I can understand this is probably a Xrender problem for the >mga driver. I would like to search a bit, but I don't know how >Xrender is used by the mga driver. Yep, it definitely is a Xinerama+Render bug on the mga driver. I've received countless bug reports on this. Worst case scenario if I can't figure out the root cause and fix it is to simply disable Render acceleration in the mga driver when Xinerama is used, until someone can fix it. Let me know how testing goes with my above driver. TTYL -- Mike A. Harris ftp://people.redhat.com/mharris OS Systems Engineer XFree86 maintainer Red Hat Inc. _______________________________________________ Render mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/render
