From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Console Resolution with GRUB2
Date: Tue, 05 Feb 2013 08:36:54 +0100 [thread overview]
Message-ID: <5110B696.6040705@gmail.com> (raw)
In-Reply-To: <7BA83AD3-3A95-48E9-A48D-32A2EA555D7C@colorremedies.com>
[-- Attachment #1: Type: text/plain, Size: 1384 bytes --]
On 05.02.2013 06:32, Chris Murphy wrote:
>
> On Feb 4, 2013, at 9:35 PM, "D.J.J. Ring, Jr." <n1ea@arrl.net> wrote:
>
>> Hello everyone,
>>
>> I thought I'd post here as my post is not exactly help, but that also will be welcome.
>>
>> Prior to GRUB2 it was quite easy to change virtual console resolution.
>>
>> There are some of us who still use console without X windows. One such group is older persons who cannot see at anything except 640x480 resolution.
>
> Well technically that's a terrible resolution for reading due to pixelization. The better way to deal with this is setting a larger font size for the higher resolution of the display. I can't even think of any laptop or desktop LCD's with a native resolution of 640x480. So to force it to a lower, and thus non-native resolution, makes the problem worse.
>
Agreed. To increase font size regenerate unicode.pf2 using grub-mkfont with appropriate -s option. E.g.
grub-mkfont -s 24 -o unicode.pf2 /usr/share/fonts/X11/mis/unifont.pcf.gz
Put resulting file in /boot/grub/unicode_24.pf2 and add
GRUB_FONT_PATH=/boot/grub/unicode_24.pf2
to /etc/default/grub
> Chris Murphy
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
next prev parent reply other threads:[~2013-02-05 7:37 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 [this message]
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
-- 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=5110B696.6040705@gmail.com \
--to=phcoder@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 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).