Hi,
> but you can tell the Matrox driver that the LCD is there
> vs a monitor and see if that cleans it up.
>
I am not sure what the option to tell it's an LCD is.
> What does your config file and your log looklike?
My kernel (2.4.18) is compiled and configured manually, I did enable
dri and matrox (mga.o) support in the kernel as modules. But I notice
that they are never needed - lsmod claims that they aren'tunused.
mga 102480 0 (unused)
agpgart 15776 1
But anyway, I am using the mga drivers from Matrox. In my XF86Conf4.
I have these 3 lines that I am not really sure what they do
Section "Module"
# Load "GLcore" # is this needed for matrox ?
Load "dri" #
# Load "glx"
I have problems with the glx, according to Matrox readme,
it should be on. But when I enable it, I can't start X.
Here's a portion of the X log
(==) MGA(0): Backing store disabled
(==) MGA(0): Silken mouse enabled
(**) MGA(0): DPMS enabled
(II) MGA(0): Using overlay video
(==) MGA(0): Direct rendering disabled
(II) [GLX]: Calling GlxExtensionInit
Fatal server error:
Caught signal 11. Server aborting
- From this, I can tell that DRI is disabled - why?
and something with GLX that crashed the server.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
