From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
Organization: CC CTU Prague
To: nick black <dank@suburbanjihad.net>
Date: Mon, 21 Jul 2003 20:44:29 +0200
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: 2.6.0-test1 + matroxfb = unuusable VC
Cc: linux-kernel@vger.kernel.org
Message-ID: <7E1E5890331@vcnet.vc.cvut.cz>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1651
Lines: 31

On 21 Jul 03 at 14:33, nick black wrote:
> Petr Vandrovec assumed the extended riemann hypothesis and showed:
> > I do not think that it has anything to do with AGP, as matroxfb does not
> > initiate any AGP transfers. 
> 
> indeed, the issue would only happen after switching from x back to
> console.  regardless, not building agp worked aorund the 2.4 problem for
> me.

In this case, does it happen if you exit X, or only if you are switching
to the console while X are active? If it happens only in second case, then
it is bug (I believe fixed long ago) in XFree mga driver: it was sometime
reprogramming color depth and line length in the accelerator even when
inactive (Gnome1 clock applet running in top right corner was known to
trigger this, depending on clock settings matroxfb would cease to
work in one second or (up to) one minute after VT switch, depending on clock
applet setting... it is possible that it happened only with kernel mga dri
driver active, but I'm not 100% sure).

I know no other workaround than using same color depth and same xres_virtual
(vxres on fbdev & desktop width in X) in X and on the console.
                                                    Best regards,
                                                        Petr Vandrovec
                                                        vandrove@vc.cvut.cz
                                                        

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/