On Mon, Jan 07, 2019 at 03:15:50PM -0800, Paul Rogers wrote:
> > The problem is that Tux doesn't appear at boot time! (-: I mean that the
> > resolution is smaller than expected (lets say bigger font size...). In fact
> > you
> > can't see the usual change of resolution shortly before Tux pops in.
>
> I rarely see it myself and that's OK because I don't much care for non-VESA,
> but it does depend on frame buffers, boot parameters, which can include
> kernel mode setting and vga= or video=, and just which driver is in control.
> IME it takes a bit of fiddling to get it, and after you've seen it once or
> twice, who cares?
To be pedantic, surely s/it/them/ ? (one penguin per CPU). But yes,
on some hardware the penguins are not visible for long, and on
anything where the KMS framebuffer needs firmware (radeon, almost
certainly amdgpu, maybe skylake and later intels) they will barely be
visible before disappearing.
But to the OP: For the general problem of not being in a framebuffer
(if in doubt, check dmesg or syslog) follow Pierre's suggestion.
After that, if dmesg says that firmware is needed look at the BLFS
books (preferably, the development version).
Framebuffers are good on modern screens (people still use 80x24?),
but as Paul said, it does take some setting up - and maybe passing
video= if the text is too small (or using a bigger console font).
ĸen
--
Take three of these a minute for four minutes. Don't take with
alcohol or you'll grow an extra head.
-- The Doctor
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Do not top post on this list.
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
http://en.wikipedia.org/wiki/Posting_style
