From: Grigore Lupescu <grigore@arista.com>
To: grub-devel@gnu.org
Subject: Re: Boot Linux through GRUB2 on AMD DB-FT3b-LC
Date: Fri, 2 Dec 2016 17:06:10 +0000 [thread overview]
Message-ID: <CAC=inJg_Q_+cdeJxUG30tWKFnHTMPgA92ij71YNXctoa+XhrXg@mail.gmail.com> (raw)
In-Reply-To: <CAC=inJjUyodZ5xBBiXthpndVEdq=MP9bCtwZ2hkJUP0TQUx7aA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]
Restarting the config from scratch in Coreboot and setting Keep Vesa
framebuffer I am able to enter gfxterm in GRUB2.
So at this point *gfxterm* is selected not *vga_text. *Linux is booting
without any issue now. Apparently the vga_text mode was the source of all
problems/limitations.
On Fri, Dec 2, 2016 at 3:28 PM, Grigore Lupescu <grigore@arista.com> wrote:
> Hello Andrei,
>
> I managed to improve the status of the *vga_text* mode. So GRUB2 was
> restarting when reaching the end of the screen. I traced this to the
> *screen_read_char* which is issued when the *inc_y* == ROWS (this call
> would break GRUB2). I didn't go even further with the debug though. I just
> clear the screen and set grub_curr_pos.y to 0 and by using set pager=1 I
> can browse with enter through all the output page by page. It's not ideal
> but it was fast and practical.
>
> Linux though still doesn't boot. I am currently looking why the vga_text
> mode is selected over gfxterm which is not even configured properly.
>
> Thanks,
> Grigore
>
[-- Attachment #2: Type: text/html, Size: 2094 bytes --]
next prev parent reply other threads:[~2016-12-02 17:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 15:28 Boot Linux through GRUB2 on AMD DB-FT3b-LC Grigore Lupescu
2016-12-02 17:06 ` Grigore Lupescu [this message]
2016-12-02 17:26 ` Andrei Borzenkov
-- strict thread matches above, loose matches on Subject: below --
2016-12-03 7:52 Grigore Lupescu
2016-11-30 15:59 Grigore Lupescu
2016-11-30 16:53 ` Andrei Borzenkov
2016-11-28 18:19 Grigore Lupescu
2016-11-29 17:55 ` Andrei Borzenkov
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='CAC=inJg_Q_+cdeJxUG30tWKFnHTMPgA92ij71YNXctoa+XhrXg@mail.gmail.com' \
--to=grigore@arista.com \
--cc=grub-devel@gnu.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;
as well as URLs for NNTP newsgroup(s).