All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Dubbs <bruce.dubbs@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Console Resolution with GRUB2
Date: Thu, 28 Feb 2013 19:48:45 -0600	[thread overview]
Message-ID: <513008FD.6030400@gmail.com> (raw)
In-Reply-To: <CADO5Rbi9Fbh-WD+902b6Eu_grERdzqQDXfjoCz_F9G+7gh0n0w@mail.gmail.com>

D.J.J. Ring, Jr. wrote:
> This is way too complicated for the average user.

Yes.  I have to agree with that.  My comments were directed at advanced 
users.

> Also some distro's don't have menu.list - I have none for example with Arch
> Linux.

menu.lst was the configuration file for Grub Legacy.  GRUB2 uses grub.cfg.

> GRUB used to have a way of just adding at the grub menu the vga mode.  It
> was simple.
>
> Can't that be done with GRUB2?

I believe that's a distro issue.  They all do the grub configuration a 
little differently.  You either do a custom configuration file or use 
the distro's method of building it.

    -- Bruce

> On Thu, Feb 28, 2013 at 7:13 PM, Bruce Dubbs <bruce.dubbs@gmail.com> wrote:
>
>> D.J.J. Ring, Jr. wrote:
>>
>>> Hello Bruce,
>>>
>>> The "problem" with this is that grub.cfg says "Do Not Edit this File".
>>>
>>
>> The reason it says this is that it is embedded in the script
>> grub-mkconfig.  It overwrites the grub.cfg, but if you don't run that and
>> only do manual edits, then it's not there.  The problem is that many
>> distros think they know more than the user (usually true, but not always)
>> and always run grub-mkconfig every time the they update the kernel whether
>> you want that or not.
>>
>>
>>   Why cannot grub2 have an easy way to change console resolution?
>>>
>>
>> I believe that's hardware dependent.
>>
>>
>>   When I open console programs, the display is tiny.  Also console programs
>>> with ncurses graphics are tiny.  These would be full screen if I could
>>> make
>>> console mode 640x480.
>>>
>>
>> That's probably because the kernel is configured to use a framebuffer by
>> default.  It's not a grub issue at that point.
>>
>> To disable the freamebuffer, see the advice in https://wiki.ubuntu.com/**
>> FrameBuffer <https://wiki.ubuntu.com/FrameBuffer>
>>
>>
>>   Grub had an easy way to do this.  I haven't tried Bruce's method because
>>> it
>>> says not to edit the file.
>>>
>>> Also when I upgrade a kernel and regenerate the grub menu, the settings
>>> will be overwritten.
>>>
>>
>> Keep a backup of /boot/grub/grub.cfg and restore it after upgrading the
>> kernel.  Then edit the file to add the new kernel.
>>
>>
>>    -- Bruce
>>
>> ______________________________**_________________
>> Grub-devel mailing list
>> Grub-devel@gnu.org
>> https://lists.gnu.org/mailman/**listinfo/grub-devel<https://lists.gnu.org/mailman/listinfo/grub-devel>
>>
>
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>




  reply	other threads:[~2013-03-01  1:48 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-05  4:35 Console Resolution with GRUB2 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2013-03-02  4:07 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.
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

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=513008FD.6030400@gmail.com \
    --to=bruce.dubbs@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.