Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!uunet!kithrup!sef From: sef@kithrup.COM (Sean Eric Fagan) Subject: Re: Micronics 486VL 386BSD 0.1 keyboard input Organization: Kithrup Enterprises, Ltd. Date: Tue, 20 Oct 1992 20:00:12 GMT Message-ID: <1992Oct20.200012.14095@kithrup.COM> References: <1992Oct12.061945.530@kithrup.COM> <1992Oct19.183325.6828@kithrup.COM> <1992Oct20.151516.16454@alliant.com> Lines: 17 In article <1992Oct20.151516.16454@alliant.com> dufault@alliant.com (Peter Dufault) writes: >I have found that it invariably boots up OK if you hit the carriage >return when the boot up messages start to show up on the screen, >and watch for them to start to echo. Once you see a single echo >you're home free. We've also been able to get the keyboard to come back to life by logging in over the network and causing a message to be sent to the console (by, for example, su'ing). Strange but true. -- Sean Eric Fagan | "You can't get lost in one room, no matter how sef@kithrup.COM | little effort you make to learn your way around." -----------------+ -- William E Davidsen (william@crd.GE.COM) Any opinions expressed are my own, and generally unpopular with others.