9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jeffrey Comstock jrc@brainiac.mn.org
Subject: Locked keyboard with new pcdist
Date: Tue, 21 Nov 1995 00:37:39 -0500	[thread overview]
Message-ID: <19951121053739.VbcLPZ3OoAXYru05PuziCUqaHrZEmwL4BiJ0JSMh1HU@z> (raw)

hornbac@gate.NET (Cecil Hornbaker) wrote:
>
> I've checked the FAQ and browsed the newsgroup and didn't find 
> anything about keyboard problems.  I got the pcdist version 
> from 11/14/95 (and the updated to 11/15/95).  When I boot the 
> floppy for installation it gets to the Configuration & 
> Installation window but the keyboard is locked such that power 
> has to be cycled to clear it.
> 
> I got the .orig version from pcdist and it installs fine.
> 
> Any clues?

I am having the same problem.  I have a Suntouch 101 keyboard.  It
isn't one of those really cheap ones either.  I put an old keyboard
in, a Northgate Omnikey 102 and it acts differently, but still does
not completely work.  I found out that depressing Num Lock during
different times during the boot process changes it's behavior.

Basically it appears that the system is hung.  The initial menu
comes up with a selection of two partitions to install the 1.44 meg
part of plan9 onto, but cursor down, tab, any key at all does not
do anything.  If I turn off Num Lock right after it starts loading,
I can press the cursor down key, then it waits about five seconds
and goes to another menu selection, but stops there.
  
If someone at AT&T fixes this, please post here.  I was going to
buy a new computer to get around the problem, but buying a new 
keyboard would be much more cost effective :-)






             reply	other threads:[~1995-11-21  5:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-11-21  5:37 Jeffrey [this message]
  -- strict thread matches above, loose matches on Subject: below --
1995-11-16 12:37 Cecil

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=19951121053739.VbcLPZ3OoAXYru05PuziCUqaHrZEmwL4BiJ0JSMh1HU@z \
    --to=9fans@9fans.net \
    /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).