From: gl@dsa-ac.de
To: Matthew Garrett <mgarrett@chiark.greenend.org.uk>,
"Antonino A. Daplas" <adaplas@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: who sets boot_params[].screen_info.orig_video_isVGA?
Date: Tue, 6 Sep 2005 09:32:07 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.63.0509060918310.11341@pcgl.dsa-ac.de> (raw)
In-Reply-To: <431CEEAF.5090701@gmail.com>
On Mon, 5 Sep 2005, Matthew Garrett wrote:
> Yup. You probably want to take a look at Documentation/fb/vesafb.txt -
> the modes are the same.
Great, thanks! I tried VESA 0x111 (Linux 0x311) - it is also what is used
by xfree86 vesa driver, after I've followed the suggestion from Tony
(cc'ed and quoted below) and tried X with vesa. The kernel boots, intelfb
driver doesn't exit, I can even start X over fb and it runs! But:
1) both screens - LCD and CRT bocome black as soon as intelfb takes over
and stay that way also under X
2) kernel logs fill with
intelfb: the cursor was killed - restore it !!
intelfb: size 8, 16 pos 0, 464
Buggy video BIOS?...
On Tue, 6 Sep 2005, Antonino A. Daplas wrote:
> One good method is to use the "vesa" driver of Xorg/Xfree86. Check
> /var/log/X*.log and it should have a nice list of vesa mode id's that
> are supported.
>
> Then add 0x200 to any of them and use it in your vga= parameter.
Thanks
Guennadi
---------------------------------
Guennadi Liakhovetski, Ph.D.
DSA Daten- und Systemtechnik GmbH
Pascalstr. 28
D-52076 Aachen
Germany
next prev parent reply other threads:[~2005-09-06 7:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-05 15:01 gl
2005-09-05 15:29 ` Matthew Garrett
2005-09-05 15:45 ` gl
2005-09-05 15:58 ` Matthew Garrett
2005-09-06 1:19 ` Antonino A. Daplas
2005-09-06 7:32 ` gl [this message]
2005-09-06 8:33 ` Antonino A. Daplas
2005-09-06 9:20 ` input/touchscreen (was Re: who sets boot_params[].screen_info.orig_video_isVGA?) gl
2005-09-06 9:33 ` gl
2005-09-06 10:41 ` gl
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=Pine.LNX.4.63.0509060918310.11341@pcgl.dsa-ac.de \
--to=gl@dsa-ac.de \
--cc=adaplas@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgarrett@chiark.greenend.org.uk \
/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
all inboxes | Powered by JetHome®