From: "D.J.J. Ring, Jr." <n1ea@arrl.net>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Console Resolution with GRUB2
Date: Sat, 2 Mar 2013 01:56:32 -0500 [thread overview]
Message-ID: <CADO5RbhY=vx_H5WSsb61yCohwDGnDPzoaCE7dYitn4eMWL9L_Q@mail.gmail.com> (raw)
In-Reply-To: <4ECA22CA-4356-4352-81DC-DDD59B8FA635@colorremedies.com>
[-- Attachment #1: Type: text/plain, Size: 2454 bytes --]
Chris,
That doesn't explain why if I go back to grub-legacy everything works. I
would agree with you if it were so, but everything else is the same. But
with grub-legacy being discontinued we need to have grub2 have this feature.
To the group:
In addition to thanking you all for your patience and cooperation, I want
to ask you to do one little search and you will see the problem.
Open up your favorite web browser, go to http://www.google.com and search
for:
change console resolution grub2
You will find many results and most of them have the word "problem" in the
results.
Here is a typical result and it talks about grub2.
As usual, everything in grub is just a bit harder than it should be.
Replacing the old linux kernel boot arg vga=791 (for example), which is
grub/console gfx resolution: 1024x768
with the new harder and less user friendly grub2 method is done like this
src 1: forums.debian.net/viewtopic.php?f=5&t=41881
src 2:
harrison3001.blogspot.com/2009/09/grub-2-graphical-boot-tips-to-set.html
http://techpatterns.com/forums/about1795.html
As I said these methods no longer work, and why are they so complex?
Certainly if grub could do it easily, why can't grub2 do so also?
Thank you very much!
DR
On Sat, Mar 2, 2013 at 1:41 AM, Chris Murphy <lists@colorremedies.com>wrote:
>
> On Mar 1, 2013, at 11:20 PM, "D.J.J. Ring, Jr." <n1ea@arrl.net> wrote:
>
> We need grub to set console resolution, show the grub menu in that
> resolution, keep that resolution while the computer boots up, then when I
> type startx I have high resolution in X gui.
>
> GRUB is responsible only for GRUB. As soon as the kernel and initramfs are
> loaded and executed, the console resolution is up to that distribution's
> behavior (init for most, and systemd for others including Fedora, not sure
> about Debian). Once those are running, GRUB is totally dropped and has no
> say in the matter and as far as I know it never has.
>
> There is a limited time inheritance of GRUB's setting, but the OS itself
> can override this early on in the boot process. I see that turning text
> only boot with at least Fedora, CentOS, and SUSE, so I'm guessing that what
> you attribute to GRUB2 is actually a concomitant change in behavior of your
> distribution's init process.
>
> Chris Murphy
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>
>
[-- Attachment #2: Type: text/html, Size: 3602 bytes --]
next prev parent reply other threads:[~2013-03-02 6:57 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-02 4:07 Console Resolution with GRUB2 Gerard Butler
2013-03-02 6:08 ` D.J.J. Ring, Jr.
2013-03-02 6:20 ` D.J.J. Ring, Jr.
2013-03-02 6:41 ` Chris Murphy
2013-03-02 6:56 ` D.J.J. Ring, Jr. [this message]
2013-03-02 8:14 ` Jordan Uggla
2013-03-06 20:00 ` D.J.J. Ring, Jr.
2013-03-07 9:38 ` Jordan Uggla
2013-03-02 8:34 ` Andrey Borzenkov
-- strict thread matches above, loose matches on Subject: below --
2013-02-05 4:35 D.J.J. Ring, Jr.
2013-02-05 5:32 ` Chris Murphy
2013-02-05 7:36 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-02-05 15:10 ` D.J.J. Ring, Jr.
2013-02-05 15:18 ` D.J.J. Ring, Jr.
2013-02-06 4:02 ` D.J.J. Ring, Jr.
2013-02-06 5:28 ` Chris Murphy
2013-02-06 15:27 ` D.J.J. Ring, Jr.
2013-02-06 22:44 ` Pete Appleton
2013-02-07 21:49 ` D.J.J. Ring, Jr.
2013-02-21 21:59 ` D.J.J. Ring, Jr.
2013-02-21 22:19 ` Bruce Dubbs
2013-02-28 23:44 ` D.J.J. Ring, Jr.
2013-03-01 0:13 ` Bruce Dubbs
2013-03-01 1:31 ` D.J.J. Ring, Jr.
2013-03-01 1:48 ` Bruce Dubbs
2013-03-01 2:30 ` Gerard Butler
2013-03-01 2:42 ` Andrey Borzenkov
2013-03-01 2:42 ` Andrey Borzenkov
2013-03-01 18:25 ` Chris Murphy
2013-03-01 18:47 ` D.J.J. Ring, Jr.
2013-03-02 0:43 ` Jordan Uggla
2013-03-02 4:03 ` Andrey Borzenkov
2013-02-05 6:47 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-02-05 7:29 ` David J. J. Ring, Jr.
2013-02-05 7:32 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-02-05 7:35 ` Chris Murphy
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='CADO5RbhY=vx_H5WSsb61yCohwDGnDPzoaCE7dYitn4eMWL9L_Q@mail.gmail.com' \
--to=n1ea@arrl.net \
--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).