From: lucio@proxima.alt.za
To: 9fans@cse.psu.edu
Subject: Re: [9fans] keyboard problems after aux/vga
Date: Mon, 20 Nov 2006 05:57:46 +0200 [thread overview]
Message-ID: <cd6cfa11abc5ad68bcae0c9108403786@proxima.alt.za> (raw)
In-Reply-To: <2cee08563904ec4e6458c65ec233eaf8@coraid.com>
[-- Attachment #1: Type: text/plain, Size: 1070 bytes --]
Don't count on HCF. I have a Plan 9 server that loses the keyboard
quite a long way into (idle) operation and eventually also loses the
serial console keyboard, but is still accessible via telnet/ssh and
cpu. And that is strictly in text display mode. Mind you, I ought to
refresh my memory, in case it's making that up.
While on the subject of erratic keyboard behaviour, I have long last
seen the console keyboard strangeness where on an arbitrary sixteen
character boundary the keyboard handler seems to insert a character
from the previous line. More likely, it's an off-by-one error that
skips past an existing character on input. Here, backspace seems,
strangely, to be a contributing factor, but one seldom remembers what
exactly had happened on the previous line. I use the console a lot
less than I used to, for totally external reasons, so it's been a
while since this bit me.
I also have a workstation that frequently doubles keystrokes (in RIO),
if anyone is interested in such oddities. VESA does not feature here
at all.
++L
[-- Attachment #2: Type: message/rfc822, Size: 2834 bytes --]
From: erik quanstrom <quanstro@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] keyboard problems after aux/vga
Date: Sun, 19 Nov 2006 22:21:45 -0500
Message-ID: <2cee08563904ec4e6458c65ec233eaf8@coraid.com>
a sure sign your kernel has executed the dread HCF instruction. ;-)
i don't know if this applies but you may want to check the xorg
drivers for references to your particular machine.
- erik
On Sun Nov 19 22:11:07 EST 2006, tim@nop.cx wrote:
> yeah, i did set that up recently. interesting thing is that input is also
> lost on the console when i start vga.
>
> X/vesa does indeed work on this machine. so i guess i'll have to
> start looking at the vesa specs.
>
> tim
next prev parent reply other threads:[~2006-11-20 3:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-19 17:06 Tim Wiess
2006-11-19 17:45 ` erik quanstrom
2006-11-19 19:05 ` Tim Wiess
2006-11-20 1:51 ` ron minnich
2006-11-20 3:10 ` Tim Wiess
2006-11-20 3:21 ` erik quanstrom
2006-11-20 3:57 ` lucio [this message]
2006-11-27 4:09 ` Tim Wiess
2006-11-20 4:04 ` Tim Wiess
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=cd6cfa11abc5ad68bcae0c9108403786@proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@cse.psu.edu \
/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).