Hi,
I cannot help you much with your main problem. However I noticed that you could have a 
    Load        "speedo"
in your module section...
Lionel

--- [EMAIL PROTECTED] wrote:
> This is my XF86Config File for the Red Hat 7.2 box running XFree 4.1.0 that 
> is driving me nuts.  I have this within a Compaq W6000 which is a dual Pentium4 
>1.8GHz box with
> 512MB L3 RAM, with a Matrox PCI G200 Dual head card (8MB per head) and the kernel 
>that is being
> run is 2.4.15-pre4 (with /dev/agpgart and then the bit for the Matrox suppourt, dual 
>head
> suppourt, G100, G200, G400 and then Millenium I and II support all built into the 
>kernel) though
> it looks as though I'll be going back to my old favourite 2.4.9 due to problems with 
>the
> 2.4.15-pre4 kernel and/or trying out 2.4.16.  For a windows manager, I'm using FVWM2 
>2.2.5.  The
> PCI Steering of this Compaq box keeps everything at IRQ 11, just like its 
>predecessor 
> What happens is that with the following XF86Config File, the upgrades in the Matrox 
>drivers and
> their Power Desk software, I'm only able to get the main screen to work!  The second 
>monitor
> acts as though it is getting signal, however, it is not being detected by the Matrox 
>Power Desk
> software, nor is it allowing me to switch to it.  If I remove the Screen option 
>within the
> Device Section then both monitors remain blackened out, and I have to give a three 
>finger salute
> in order to reboot so I can get signal back to both monitors.  I know that normally 
>a Matrox
> G450 requires the same BusID numbers and then separate Screen Options within their 
>relative
> Device sections and that the G200 should not need such.  Help?!  


__________________________________________________
Do You Yahoo!?
Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month.
http://geocities.yahoo.com/ps/info1
_______________________________________________
Newbie mailing list
[EMAIL PROTECTED]
*** To unsubscribe , or change message options, see:
http://XFree86.Org/mailman/listinfo/newbie

Reply via email to