From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: kbd@lists.altlinux.org
Subject: [kbd] unicode_start and hvc consoles
Date: Tue, 5 Apr 2011 13:53:16 -0400 [thread overview]
Message-ID: <20110405175316.GA2464@zod.rchland.ibm.com> (raw)
Hi,
While trying to run unicode_start on a POWER machine, we ran into the
following error:
[root@elm17d211 ~]# tty
/dev/hvc0
[root@elm17d211 ~]# unicode_start
unicode_start skipped on /dev/hvc0
[root@elm17d211 ~]#
It seems the unicode_start script checks for a valid tty device by
looking for /dev/console, /dev/vc*, or /dev/tty*. On POWER machines,
the console device is often provided by /dev/hvc0. I believe that can
also be true on Xen guests and in some cases ARM installations today as
well.
Do you know of a valid reason the /dev/hvc0 would be excluded, or is
this simple a case of someone not reporting the issue as of yet. I
would appreciate any thoughts you have. Please CC me on reply.
josh
next reply other threads:[~2011-04-05 17:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-05 17:53 Josh Boyer [this message]
2011-04-06 22:04 ` [kbd] unicode_start and hvc consoles Alexey Gladkov
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=20110405175316.GA2464@zod.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc=kbd@lists.altlinux.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 read-only IMAP folder(s) and NNTP newsgroup(s).