Using the latest xorg's (xorg-x11-6.8.0-r4.ebuild) mga_drv.o module for a Matrox G450 causes the second head's display to show very unstable wavy lines in Xinerama mode -cannot read screen easily. Can be fixed by installing a known good mga_drv.o module into the /usr/X11R6/lib/modules/drivers directory. I used the mgs_drv.o module from the latest Mepis distro that uses XFree86 Version 4.3.0.1 (Debian 4.3.0.dfsg.1-10 20041215174925) and this worked well. Reproducible: Always Steps to Reproduce: 1.Install the xorg-x11-6.8.0-r4.ebuild with a Matrox G450 (probably same for 550, 650 series also). 2. Setup the dual monitors in Xinerama mode 3. Actual Results: The second head on the card displays very unstable wavy lines in Xinerama mode. Expected Results: Should have a clear crisp screen with no wavy lines on the second head. Can be fixed by installing a known good mga_drv.o module into the /usr/X11R6/lib/modules/drivers directory to replace the faulty one. I used the mgs_drv.o module from the latest Mepis distro that uses XFree86 Version 4.3.0.1 (Debian 4.3.0.dfsg.1-10 20041215174925) and this worked well. Can be fixed by installing a known good mga_drv.o module into the /usr/X11R6/lib/modules/drivers directory to replace the faulty one. I used the mgs_drv.o module from the latest Mepis distro that uses XFree86 Version 4.3.0.1 (Debian 4.3.0.dfsg.1-10 20041215174925) and this worked well.
Can you please try 6.8.1.904 and report back? Reopen when you do.
I had (have) this same problem. I found that by setting the virtual sizes in the Screen section the monitor cleared up. However now this setup has problems on a reboot, either cold or warm. Now on reboot the second head will be completely out of sync. To clear this up I must logout ==> End Current Session in KDE. At that point the second monitor is fine. I am configured as follows: amd64 matrox 450 kernel 2.6.9-r14 xorg 6.8.0-r4 KDE 3.3.2 Since xorg 6.8.1 is masked for amd64 I am waiting to find out if the original person that reported this had any luck with 6.8.1.
I just tried to install that latest masked version 6.8.2-r1 to see if the resolved the problem. It did not. Does anyone have an idea when we will have a fix for this?
