From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Pozsar Balazs <pozsy@sch.bme.hu>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: FBdev remains in unusable state
Date: Wed, 12 Dec 2001 21:55:36 MET-1 [thread overview]
Message-ID: <BCF7BFC1D50@vcnet.vc.cvut.cz> (raw)
On 12 Dec 01 at 21:42, Pozsar Balazs wrote:
> On Wed, 12 Dec 2001, Petr Vandrovec wrote:
> > 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<-----
> > > 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
> > 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.
>
> 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.
> > 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.
>
> 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
vandrove@vc.cvut.cz
next reply other threads:[~2001-12-12 20:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-12 21:55 Petr Vandrovec [this message]
2001-12-13 11:35 ` FBdev remains in unusable state David Woodhouse
2001-12-13 13:29 ` Pozsar Balazs
2001-12-13 16:11 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2001-12-13 18:00 Petr Vandrovec
2001-12-13 17:03 ` David Woodhouse
2001-12-12 21:32 Petr Vandrovec
2001-12-12 20:42 ` Pozsar Balazs
2001-12-12 20:13 Petr Vandrovec
2001-12-12 20:14 ` Pozsar Balazs
2001-12-12 18:49 Pozsar Balazs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BCF7BFC1D50@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=pozsy@sch.bme.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox