Menu
▾
▴
Re: [Linux-fbdev-users] matroxfb: screen messes up after so
|
From: Petr V. <VAN...@vc...> - 2004-06-08 18:42:20
|
On 8 Jun 04 at 16:03, Jonas Meurer wrote:
> > (depends on seconds being displayed or not), but other apps running
> > in your X can trigger that too.
>
> oh, so i used DRI in X until now, with the XFree86 mga driver, both
> enabled in kernel and XF86Config.
> I use fb driver for X now, and no DRI support any longer. Let's see if
> the problems stay away now.
I think that it is too drastic if you switched to fbdev driver. mga driver
with DRI disabled will be much faster.
> > Only 100% fix is to stop using DRI, or disabling acceleration on console
> > (fbset -accel false). Or you can just decrease likelihood of corruption
> > by using same color depth and same resolution in both X and on the console -
> > then usually only one line on screen gets printed with wrong color from
> > time to time instead of massive corruption.
>
> yea, then my current configuration should work. Is DRI support a
> recommented feature for better performance/lookout/...?
DRI is mainly for 3D performance.
> and what about these two matroxfb drivers in kernel 2.6.6, one for
> G100/G200/G400/G450/G550, and the other only for G100/G200/G400.
>
> I failed to get any information about which one to use for my G400.
> what's the difference of these drivers?
As helptext says, if you have G100, G200 or G400, you can toss a coin. If you
have ~8KB free memory, or if you plan upgrade to G450/G550, select G100-G550
driver. If you have G400, and you are ABSOLUTELY sure that you'll rebuild
your kernel with G450/G550 support BEFORE plugging G450 into the box,
you can select G100-G400 choice, but I recommend it only for embeded box
where you do not plan any upgrade. (Main problem is that G400 and G450
use same PCI device ID while they are completely different - G400 driver
will drive G450 as G400 - and so very bad things happen... hopefully
your monitor switches itself off when driven with 300Hz vertical sync)
Petr
|
