From: Robin Atwood <robin@binro.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Initial console messages garbled
Date: Sun, 28 Jun 2020 21:20:06 +0700 [thread overview]
Message-ID: <20200628212006.5379606c@binro.org> (raw)
In-Reply-To: <20200625135518.474074d0@binro.org>
On Thu, 25 Jun 2020 13:55:18 +0700
> > Robin,
> > are you comfortable just going with a bare-bones console and build
> > a new kernel where you _disable_ CONFIG_FB? That might do it.
> >
> > Alternately, you can hook up a serial cable to another computer and
> > set "console=ttyS0,115200n8".
>
> I will try that, if it works it will at least give me a chance to look
> at the error messages.
I couldn't disable CONFIG_FB in the kernel, only select "module" or
"built-in" mode. I guess there is another parameter which needs
disabling. Researching that, I discovered you can disable frame-buffer
on the kernel command line. Also, that there might be an option in the
BIOS to set but I checked that and found nothing. So I rebooted and
used Grub to edit the kernel parameters and set "VGA=NORMAL NOMODESET".
This resulted in the usual initial garbage which was not cured by
loading the frame-buffer module. So disabling frame-buffer support made
things worse, which is rather what I was expecting. :(
Given the almost total lack of response to my post, I guess I am stuck
with this problem.
Thanks
Robin
--
next prev parent reply other threads:[~2020-06-28 14:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 15:30 [gentoo-user] Suspend-to-ram freezing tasks failed Серега Филатов
2020-06-24 16:39 ` [gentoo-user] Initial console messages garbled Robin Atwood
2020-06-24 16:54 ` Jack
2020-06-25 6:50 ` Robin Atwood
2020-06-24 17:31 ` tedheadster
2020-06-25 6:55 ` Robin Atwood
2020-06-28 14:20 ` Robin Atwood [this message]
2020-06-28 16:29 ` Dale
2020-06-28 14:51 ` Rich Freeman
2020-06-28 16:03 ` Sid Spry
2020-06-24 17:02 ` [gentoo-user] Suspend-to-ram freezing tasks failed Michael
2020-06-24 17:26 ` Серега Филатов
2020-06-24 17:35 ` Michael
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=20200628212006.5379606c@binro.org \
--to=robin@binro.org \
--cc=gentoo-user@lists.gentoo.org \
/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