FBdev remains in unusable state
Quoted 5 lines · Pozsar Balazs
Quoted 2 lines · Petr Vandrovec
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?
Documentation/fb/vesafb.txt, X11 paragraph, last sentence:
-------8<-----
The X-Server must restore the video mode correctly, else you end up with a broken console (and vesafb cannot do anything about this). -------8<-----
Quoted 7 lines
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.
Sorry. arch/i386/boot/video.S loader
Quoted 6 lines
Quoted 3 lines
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?
I have no idea. I know that atyfb does not work on ATIs I have, and I have no idea how X11 behaves on them. I do not have other hardware at all.
Quoted 6 lines
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...
With driver "mga" and option "usefbdev" you should get 'real' X, they'll use acceleration. Only difference is that they'll use kernel fbdev to set videomode (in XF4.0 there is a bug that DGA mode in X11 mga driver will go directly to hardware even if usefbdev is specified, but with XF4.1 you should be safe).
Best regards,
Petr Vandrovec [email protected]
Quoted 5 lines · [email protected] said:
Documentation/fb/vesafb.txt, X11 paragraph, last sentence:
-------8<-----
The X-Server must restore the video mode correctly, else you end up with a broken console (and vesafb cannot do anything about this). -------8<-----
This isn't strictly true. We could just call the VESA BIOS to set it up again for us. The 'vesa' XFree86 driver manages to do this perfectly well from userspace, even.
--
dwmw2
Quoted 11 lines · David Woodhouse
Quoted 5 lines · [email protected] said:
Documentation/fb/vesafb.txt, X11 paragraph, last sentence:
-------8<-----
The X-Server must restore the video mode correctly, else you end up with a broken console (and vesafb cannot do anything about this). -------8<-----This isn't strictly true. We could just call the VESA BIOS to set it up again for us. The 'vesa' XFree86 driver manages to do this perfectly well from userspace, even.
Then why not include this set up code into vesafb?
Signature · 1 line
Balazs Pozsar
Quoted 1 line · [email protected] said:
Then why not include this set up code into vesafb?
Because nobody's got round to porting it into the vesafb driver yet. And it may turn out to be prohibitively ugly if you do.
--
dwmw2