I have a a multi monitor configuration as follows:
/dev/fb0 - PCI matrox G200
/dev/fb1 - PCI matrox G200
/dev/fb2 - AGP matrox Millennium G400 MAX
/dev/fb3 - AGP matrox Millennium G400 MAX (second head)

all are using the fbdev drivers in 2.4.0-test9.  I have "matrox G200/G400",
"matrox multiheading", "i2c support", and the matrox G400 i2c multi-heading
thing switched on.  (compiled in the kerenel).

The second head on my G400 card (/dev/fb3) works alone just fine with
startx -- -targets fbdev:/dev/fb3 -modes 800x600x32
(running XGGI)


however, i get freakyness when i do:
startx -- -targets (fbdev:/dev/fb0):(fbdev:/dev/fb1):(fbdev:/dev/fb3) -modes 
(1024x768x32):(1024x768x32):(800x600x32)

(i.e. i'm using a normal monitor and the second head on the G400 at the same 
time)

freakyness means that i have a "ghost image" when i'm in 640x480 on that
monitor, and when i'm in 800x600 i get vertical stripes about a half inch
high, that span a horizontal bar across the screen.  the bar then runs up
the screen, (another bar is every 2 inches), and every 3 seconds a get
artifacts on the screen, untill it's done with it's run.  Then it will
stop and be fine for a while.  It seems to trigger when i bring the mouse
cursor over to that screen but will die down while the mouse is still there.
Do these sound like fbdev driver problems, ggi problems, or XGGI problems?  

Corey


(this head works fine when i run it alone, with nothing on the "coupled" 
G400 head)

Reply via email to