From: "Damian Kołkowski" <deimos@deimos.one.pl>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [BUG] 2.5.69 - no setfont and loadkeys on tty > 1
Date: Fri, 9 May 2003 13:33:58 +0200 [thread overview]
Message-ID: <20030509113358.GA14798@deimos.one.pl> (raw)
Hi,
I'am wondering why setfont and loadkeys in setting only on first tty.
It works (setting font map on all six tty) in 2.{2,4}.x.
I'am using _radeonfb_ with rv250if, could it be the reason?
Take care.
P.S. Do I need to attaah the config file?
--
# Damian *dEiMoS* Kołkowski # http://deimos.one.pl/ #
next reply other threads:[~2003-05-09 11:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-09 11:33 Damian Kołkowski [this message]
2003-05-11 17:38 ` [BUG] 2.5.69 - no setfont and loadkeys on tty > 1 Pavel Machek
2003-05-12 21:25 ` James Simmons
2003-05-13 13:06 ` Damian Kołkowski
2003-05-14 12:09 ` Pavel Machek
2003-05-14 22:19 ` James Simmons
2003-05-14 22:42 ` Pavel Machek
2003-05-14 23:16 ` James Simmons
2003-05-15 0:10 ` Pavel Machek
2003-05-14 22:45 ` Pavel Machek
2003-05-15 2:44 ` Andries Brouwer
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=20030509113358.GA14798@deimos.one.pl \
--to=deimos@deimos.one.pl \
--cc=linux-kernel@vger.kernel.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).