From: Pavel Machek <pavel@ucw.cz>
To: Michael Shell <list1@michaelshell.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Standard VGA console with DRI/DRM under X?
Date: Sun, 30 Nov 2014 23:31:01 +0100 [thread overview]
Message-ID: <20141130223101.GA2322@amd> (raw)
In-Reply-To: <20141028023208.320b777b6ad97c7c9a815300@michaelshell.org>
On
> One reason I do not wish to use the framebuffer console is because of the
> small font. 160 columns makes it difficult to tell which [OK] belongs with
> which service. The selection of console fonts should always include a
> set that gives us an 80 column screen and the docs should point this
>out.
Take a look at kernel config, and select a bigger font.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2014-11-30 22:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 6:32 Standard VGA console with DRI/DRM under X? Michael Shell
2014-10-28 15:48 ` Bjorn Helgaas
2014-10-28 15:56 ` Christian König
2014-10-28 16:07 ` Deucher, Alexander
2014-11-30 22:31 ` Pavel Machek [this message]
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=20141130223101.GA2322@amd \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=list1@michaelshell.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