From: Martin Michlmayr <tbm@cyrius.com>
To: Frans Pop <elendil@planet.nl>
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 00:27:08 +0100 [thread overview]
Message-ID: <20080322232708.GA32209@deprecation.cyrius.com> (raw)
In-Reply-To: <200803222035.08897.elendil@planet.nl>
* Frans Pop <elendil@planet.nl> [2008-03-22 20:35]:
> > > Can you use vesafb instead of vga16fb? That should be far more
> > > reliable.
> > vesafb is built into the Debian kernel, so presumably that works.
> > I've no idea why debian-installer loads vga16fb. Frans, any idea?
>
> For the graphical installer we force the use of vesafb by directfb, but we
> don't do anything like that for the regular installer. So you could try
> booting installgui and see if that does work.
installgui works, but that also passes vga=788 and when I pass that to
the normal installer it also works.
Anyway, you didn't answer my original question which was why the
text-based d-i loads vga16fb.
> Other option could be to boot with 'install video=vga16fb:off', but
> I'm not sure if that's supported.
That doesn't seem to work.
--
Martin Michlmayr
http://www.cyrius.com/
-------------------------------------------------------------------------
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/
next prev parent reply other threads:[~2008-03-22 23: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 [this message]
2008-03-23 1:26 ` Frans Pop
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=20080322232708.GA32209@deprecation.cyrius.com \
--to=tbm@cyrius.com \
--cc=elendil@planet.nl \
--cc=keith.packard@intel.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).