FBdev remains in unusable state
Quoted 6 lines · Pozsar Balazs
Quoted 3 lines
No. vesafb does not work together with mga driver in X (although I believe that vesafb works with XFree mga driver, only Matrox driver is binary bad citizen).
I don't clearly understand you. I am using mga driver which is in the official xfrr86 release.
In that case even xfree mga driver cannot return hardware back to previous state. It is expected and documented.
Quoted 6 lines
Quoted 3 lines
Neither. X restore R/W registers to their previous values, while write-only registers to their values for normal text mode. Yes, there is a 'workaround'. Use (much faster) matroxfb.
What if setting those W-only registers to their appropiate values on console-switches?
It is hardware dependent and undocumented. matroxfb does it...
Quoted 1 line
Why isn't it done by the vesafb driver?
vesafb is VBE2.0 based. It does not know how to touch hardware, it uses LILO to do all this dirty work.
Quoted 1 line
How is the mga fb driver handle handling this situation better?
Because of it actually drives hardware, instead of touching it once before boot, and then trusting all citizens that it will work. So it can restore any mode it wants, on any head it wants.
Quoted 3 lines
ps: My problem is that I have to use exactly the same kernel on different machines, and I need fb. If not all machines have mga, than mga fb is no-go.
I do not understand. If you'll compile both vesafb & matroxfb into kernel, and you'll boot with
Linux vga=769 video=matrox:vesa:769
on computers with Matrox inside you'll have /dev/fb0 accelerated fb, and /dev/fb1 VESAFB 'do not use' (maybe vesafb even will not load as framebuffer will be already acquired by matroxfb, but I never tested it). On computers without Matrox you'll have /dev/fb0 VESAFB and /dev/fb1 will not exist at all.
Petr Vandrovec [email protected]
P.S.: Also try 'Option "UseFBDev"' in /etc/X11/XF86Config-4 driver section. I think that with this option X11 mga driver will not stomp on your hardware, and instead it will refuse any videmode != vesafb one.
Quoted 10 lines · Petr Vandrovec
Quoted 6 lines · Pozsar Balazs
Quoted 3 lines
No. vesafb does not work together with mga driver in X (although I believe that vesafb works with XFree mga driver, only Matrox driver is binary bad citizen).
I don't clearly understand you. I am using mga driver which is in the official xfrr86 release.
In that case even xfree mga driver cannot return hardware back to previous state. It is expected and documented.
Sorry I didn't know that. Btw, where is it documented?
Quoted 4 lines
Quoted 1 line
Why isn't it done by the vesafb driver?
vesafb is VBE2.0 based. It does not know how to touch hardware, it uses LILO to do all this dirty work.
I think got the point, but I don't really understand how lilo comes here, because I boot using grub or syslinux.
Quoted 7 lines
Linux vga=769 video=matrox:vesa:769
on computers with Matrox inside you'll have
/dev/fb0accelerated fb, and/dev/fb1VESAFB 'do not use' (maybe vesafb even will not load as framebuffer will be already acquired by matroxfb, but I never tested it). On computers without Matrox you'll have/dev/fb0VESAFB and/dev/fb1will not exist at all.
Thanks for this. Are there similar issues with other cards? Which fb drivers should I compile in?
Quoted 4 lines
P.S.: Also try 'Option "UseFBDev"' in/etc/X11/XF86Config-4driver section. I think that with this option X11 mga driver will not stomp on your hardware, and instead it will refuse any videmode != vesafb one.
I need 'real' X running, not X using fbdev...
Much thanks for you help,
Signature · 1 line
Balazs Pozsar