From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Cc: Mark Knecht <markknecht@gmail.com>
Subject: Re: [gentoo-user] Re: about boot with framebuffer
Date: Mon, 04 Jul 2011 22:40:45 +0200 [thread overview]
Message-ID: <1678969.Rfgp9b7j66@nazgul> (raw)
In-Reply-To: <CAK2H+ed8Wb608Va0aJOV1mvt4NeQp+2DTZgTwWT-UqDWfwU-3Q@mail.gmail.com>
On Monday 04 July 2011 11:20:43 Mark Knecht did opine thusly:
> > The way I've been doing this only required `vesa' or `uvesa' and
> > some special kernel line stuff. None of the X related stuff is
> > necessary.
> >
> > From covici's post... I think I may need to say uvesa where I've
> > been saying vesa.
> >
> > I'm going to try that some time today. Its already enabled in
> > my kernel
>
> I'm a little confused by his post also, but I've never run a machine
> without Xorg so maybe it's a technical point. With a framebuffer I
> believe you can get a boot screen like the Install CD - a bunch of
> little Tux's across the top - so you're doing graphics at that
> point but you're not running X?
>
> I was curious about this topic awhile back wondering if you could
> run a Gentoo VM with only a framebuffer and get any graphics at
> all, or is it just that the framebuffer is used to give you more
> control over the console font/height/width selection.
>
> (I've never run a framebuffer, if that's not obvious!)
bootsplash does not run under X (well, on redhat it used to, but you
really don't want to go there) - this should be obvious as you don't
see the X start-up sequence happening at early boot time.
There are many things boot splash could use for displaying images
(fbcon etc etc) or even something of it's own invention. I'm not
familiar enough with it to say how it really does it.
--
alan dot mckinnon at gmail dot com
next prev parent reply other threads:[~2011-07-04 20:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-03 21:39 [gentoo-user] about boot with framebuffer Harry Putnam
2011-07-03 22:07 ` Albert Hopkins
2011-07-04 3:07 ` [gentoo-user] " Harry Putnam
2011-07-04 3:33 ` covici
2011-07-04 18:12 ` Harry Putnam
2011-07-04 18:46 ` covici
2011-07-04 4:18 ` Albert Hopkins
2011-07-04 18:10 ` Harry Putnam
2011-07-04 18:20 ` Mark Knecht
2011-07-04 20:40 ` Alan McKinnon [this message]
2011-07-04 20:47 ` Mark Knecht
2011-07-04 20:57 ` Alan McKinnon
2011-07-04 21:15 ` Mark Knecht
2011-07-04 21:34 ` Alan McKinnon
2011-07-04 22:25 ` Neil Bothwick
2011-07-04 23:45 ` Mark Knecht
2011-07-05 0:52 ` Joshua Murphy
2011-07-04 19:07 ` Nikos Chantziaras
2011-07-05 0:48 ` Harry Putnam
2011-07-05 1:41 ` Nikos Chantziaras
2011-07-04 19:35 ` Albert Hopkins
2011-07-05 15:27 ` covici
2011-07-05 22:50 ` Albert Hopkins
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=1678969.Rfgp9b7j66@nazgul \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
--cc=markknecht@gmail.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