From: Frans Pop <elendil@planet.nl>
To: Martin Michlmayr <tbm@cyrius.com>
Cc: linux-fbdev-devel@lists.sourceforge.net,
Keith Packard <keith.packard@intel.com>
Subject: Re: vga16fb: blank screen with Intel GM965/GL960 on HP 2510p notebook
Date: Sun, 23 Mar 2008 02:26:37 +0100 [thread overview]
Message-ID: <200803230226.38587.elendil@planet.nl> (raw)
In-Reply-To: <20080322232708.GA32209@deprecation.cyrius.com>
[-- Attachment #1.1: Type: text/plain, Size: 1552 bytes --]
On Sunday 23 March 2008, Martin Michlmayr wrote:
> Anyway, you didn't answer my original question which was why the
> text-based d-i loads vga16fb.
The installer only modprobes vga16fb if vesafb is not active (well, it
actually does modprobe vga16fb when vesafb and/or fbcon are compiled in
[1], but that's the general idea), but that's not the problem here.
The kernel config is:
CONFIG_FB_VGA16=m
CONFIG_FB_VESA=y
CONFIG_VGA_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
So VESA is compiled in.
The problem here is that /proc/fb doesn't show VESA when the regular
installer is booted, AFAICT because we boot with vga=normal. vesafb seems
to only be actually activated by the kernel during boot if you boot with a
vga mode that requires it.
The installer then runs its init scripts, specifically
/lib/debian-installer-startup.d/S40framebuffer-module-linux-x86, and that
ends up loading vga16fb because loading vesafb fails (as it's compiled in).
And thus you end up with vga16fb, basically because it's the only
framebuffer available _despite_ the fact that vesafb is compiled in...
Is there is a way to activate vesafb post-boot even when the system was
booted with vga=normal? If there is this could probably be avoided.
Also, does anyone know a way to test whether fbcon is compiled in or not?
We can of course test if fbcon is available as a module and assume it's
compiled in if not, but that's not a proper test that it _is_ present.
Cheers,
FJP
[1] I've got a patch to fix that in D-I's rootskel.
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 228 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
[-- Attachment #3: Type: text/plain, Size: 182 bytes --]
_______________________________________________
Linux-fbdev-devel mailing list
Linux-fbdev-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-fbdev-devel
next prev parent reply other threads:[~2008-03-23 1:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-21 16:39 vga16fb: blank screen with Intel GM965/GL960 on HP 2510p notebook Martin Michlmayr
2008-03-21 17:03 ` Keith Packard
2008-03-22 11:25 ` Martin Michlmayr
2008-03-22 16:40 ` Keith Packard
2008-03-22 16:58 ` Martin Michlmayr
2008-03-22 19:35 ` Frans Pop
2008-03-22 23:27 ` Martin Michlmayr
2008-03-23 1:26 ` Frans Pop [this message]
2008-03-23 9:05 ` Geert Uytterhoeven
2008-03-24 12:51 ` Frans Pop
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=200803230226.38587.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=keith.packard@intel.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=tbm@cyrius.com \
/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;
as well as URLs for NNTP newsgroup(s).