Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!mips!mips!think.com!cayman!brad From: brad@Cayman.COM (Brad Parker) Newsgroups: comp.unix.bsd Subject: Re: Keyboard Message-ID: <BRAD.92Jul18152309@haiti.Cayman.COM> Date: 18 Jul 92 19:23:09 GMT References: <IeO2l3y00WB3Eu60oZ@andrew.cmu.edu> Sender: news@cayman.COM Organization: Cayman Systems Inc., Cambridge, MA Lines: 31 Nntp-Posting-Host: haiti In-reply-to: tj2n+@andrew.cmu.edu's message of 18 Jul 92 14:35:47 GMT In article <IeO2l3y00WB3Eu60oZ@andrew.cmu.edu> tj2n+@andrew.cmu.edu (Tao Jiang) writes: I just installed 386bsd0.1 yesterday. This morning, when I tried to reboot the system, everything is OK, but after that,( after the prompt login appeared), I can not enter anything from keyboard. Then I tried to reboot, things were the same till the 5th reboot. Is this a bug or I have done something wrong when I installed 386bsd? Any clues? I have the same problem with my 486/33 laptop. If I type a few chars on the keyboard as it's booting (during the bios banner, and again during the probes) it seems to work fine. As this is clearly voodoo, I suspect timing in the code which talks to the keyboard cpu; I'm going to re-read the messages from this newsgroup on that subject and play around with the keyboard init code. On another note, when booting Tiny 386BSD on my stock T5200 (which runs 0.0 great!) after a while the shell seems to stop understanding what I am typing. Commands (like "pwd") generate "bin/pwd not found" and general keyboard input seems to be ignored (it's like the line buffering is working but then ignored, i.e. the keys are echo'd but not passed on) (if I boot off the 0.0 kernel on the T5200 and *then* run install, everything is fine, but this won't work for long) -brad -- A metaphor is like a simile. Brad Parker Cayman Systems, Inc., Cambridge, Ma. brad@cayman.com