From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1UBgNp-0002fB-Bm for mharc-grub-devel@gnu.org; Sat, 02 Mar 2013 01:57:25 -0500 Received: from eggs.gnu.org ([208.118.235.92]:36345) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UBgNi-0002eH-9d for grub-devel@gnu.org; Sat, 02 Mar 2013 01:57:23 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UBgNd-00038A-9t for grub-devel@gnu.org; Sat, 02 Mar 2013 01:57:18 -0500 Received: from mail-oa0-f44.google.com ([209.85.219.44]:46117) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UBgNd-000379-2v for grub-devel@gnu.org; Sat, 02 Mar 2013 01:57:13 -0500 Received: by mail-oa0-f44.google.com with SMTP id h1so7001344oag.31 for ; Fri, 01 Mar 2013 22:57:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type; bh=CpsL/mi0U91/LY/pQb7syzFBURcdi4ygb178NArakhM=; b=01wSWhuKtI0zli5VfoqEkvvMqCJfDssUTBkpzSo6YlFSMnhgY5e6LkBYwMNddMUxSt VCJXJ02IQPy/kD00lW0zDBtl8Y/Elm+oiM50FnV6us4isEf5Ts+e186TCcxULdDJH5Js ea/XtZZ7CPlIlDQ1pvkJKacjbYhgnSvlZweJjb5Yv/piASMhAOOF+KrOG7oVtD43dLNq /iRDLbcmijV1YGkCDwm17GMengzrD8Mf/MxG5XGcZigKjc7zqieY3zuycSIzBXxtDQjM KTjUf21MWNuzPDzMMglt5Pr54vPsc/r6Taa8lmkjSFyMkEp0jgVIf556tYoAVF3GiFTz S1aw== X-Received: by 10.182.40.71 with SMTP id v7mr10394786obk.85.1362207432140; Fri, 01 Mar 2013 22:57:12 -0800 (PST) MIME-Version: 1.0 Sender: djringjr@gmail.com Received: by 10.76.87.5 with HTTP; Fri, 1 Mar 2013 22:56:32 -0800 (PST) In-Reply-To: <4ECA22CA-4356-4352-81DC-DDD59B8FA635@colorremedies.com> References: <4ECA22CA-4356-4352-81DC-DDD59B8FA635@colorremedies.com> From: "D.J.J. Ring, Jr." Date: Sat, 2 Mar 2013 01:56:32 -0500 X-Google-Sender-Auth: 0FhrgVDyPc_QTga2NmVyQVePFZE Message-ID: Subject: Re: Console Resolution with GRUB2 To: The development of GNU GRUB Content-Type: multipart/alternative; boundary=f46d04446c111a70a604d6eba2eb X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy] X-Received-From: 209.85.219.44 X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: The development of GNU GRUB List-Id: The development of GNU GRUB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Mar 2013 06:57:23 -0000 --f46d04446c111a70a604d6eba2eb Content-Type: text/plain; charset=UTF-8 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 wrote: > > On Mar 1, 2013, at 11:20 PM, "D.J.J. Ring, Jr." 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 > > --f46d04446c111a70a604d6eba2eb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Chris,

That doesn't explain why if I go back to grub-legacy ever= ything works.=C2=A0 I would agree with you if it were so, but everything el= se is the same.=C2=A0 But with grub-legacy being discontinued we need to ha= ve 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 m= ost of them have the word "problem" in the results.

Here i= s 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=3D791 (for example), which = is grub/console gfx resolution: 1024x768
with the new harder and less user friendly grub2 method is done like th= is

src 1: forums.debian.net/viewtopic.php?f=3D5&t=3D41881
src 2: harrison3001.blogspot.com/2009/09/grub-2-graphi= cal-boot-tips-to-set.html

http://techpa= tterns.com/forums/about1795.html

As I said these methods no long= er work, and why are they so complex?=C2=A0 Certainly if grub could do it e= asily, why can't grub2 do so also?

Thank you very much!

DR

On Sat, Mar 2, 2013 at 1:41 AM, C= hris 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, sh= ow the grub menu in that resolution, keep that resolution while the compute= r 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 ini= tramfs are loaded and executed, the console resolution is up to that distri= bution's behavior (init for most, and systemd for others including Fedo= ra, 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 setti= ng, 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&#= 39;m guessing that what you attribute to GRUB2 is actually a concomitant ch= ange 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


--f46d04446c111a70a604d6eba2eb--