Re: [Freevo-users] matrox framebuffer problems

[Bernard J. <bjo...@sy...>]

Maybe it's some weirdness between you having a G400-DH and me a G400-TV, but
I am able to see and read the complete boot process (no weird colors or
anything) up until the point that X starts and the tv out is disabled.  Then
running the tv-out-init script displays X on my TV.  The only weirdness mine
has is occasionally it will lose sync in certain places, like between the
BIOS post and grub, and then between grub and the kernel boot.

As far as what triggers the maven client, I ran through steps by hand to see
when that was printed in the log and when I did a 'modprobe matroxfb_maven'
and the following two lines appeared:
i2c-core.o: driver maven registered.
client [maven client] registered to adapter [MAVEN:fb0 on i2c-matroxfb](pos.
0).

You've brought up the issue of having it working in non-framebuffer mode a
couple of times.  That's useful in knowing that the hardware is not broken,
but not for anything else in framebuffer mode. (That's where I started too -
except :1 display).

Not a lot of terribly useful information here...

As a final offer, I can send you my kernel.config file and you could check
it against yours or try building from it.  Only problem is it's not a
baseline kernel (remember i said it was based on redhat which has a lot of
patches added? - which is sure to change the config too).  Or, if you'd
like, I can build you a kernel with a target of athlon that you could try.



----- Original Message -----
From: "Stephen Mathezer" <mat...@ya...>
To: <fre...@li...>
Sent: Sunday, January 12, 2003 5:53 PM
Subject: Re: [Freevo-users] matrox framebuffer problems


> Well, I've tried everything that I can think of.
>
> Bottom line is that I never see this message
>
> > i2c-core.o: client [maven client] registered to adapter [MAVEN:fb0 on
i2c-matroxfb](pos. 0)
>
> I still get ioctl failed: Invalid argument when I do the matroxset -m 3
> What triggers the 'maven client'? any ideas?
>
> I have flashed the BIOS on the card and set the DOS mode to NTSC.  Now
> when I boot, the very first screen shows up on the TV and is unreadable
> on the monitor, then when it shows interrupts etc the monitor is
> readable and the TV is white text on green background.  The first touch
> of fb0 makes the TV go solid green.
>
> I did build a 2.4.18 kernel with the patches for my ide controller (I
> have an AMD so your kernel wouldn't work anyways and I get data
> corruption without the patch) and still no luck.
>
> I can use mgapdesk and non-framebuffer mode to create a 'clone' config
> for X and see the desktop on both screens, but then xawtv and mplayer
> blank out the output on the tv.
>
> I am starting to run out of ideas.  I'm going to try just using the TV
> cable on head 1 and if I can't make that work well I will have to try
> another video card.
>
> -Steve
>
>
> -------------------------------------------------------
> This SF.NET email is sponsored by:
> SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
> http://www.vasoftware.com
> _______________________________________________
> Freevo-users mailing list
> Fre...@li...
> https://lists.sourceforge.net/lists/listinfo/freevo-users
>