Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!saimiri.primate.wisc.edu!usenet.coe.montana.edu!news.u.washington.edu!ns1.nodak.edu!plains.NoDak.edu!ortmann From: ortmann@plains.NoDak.edu (Daniel Ortmann) Subject: Re: Gateway 2000 keyboards Sender: usenet@ns1.nodak.edu (Usenet login) Message-ID: <C52s1u.JJC@ns1.nodak.edu> Date: Tue, 6 Apr 1993 18:44:18 GMT References: <C4zCB9.3Hz@bcstec.ca.boeing.com> Nntp-Posting-Host: plains.nodak.edu Organization: North Dakota Higher Education Computing Network Lines: 20 rjw9917@bcstec.ca.boeing.com (Robert J. Willard) writes: )I tried to load 386bsd on two Gateway 2000 local bus machines lately. )One was a 486-66 and the other a 486SX-33. On the SX-33, boot )occurred, but the keyboard was dead. Subsequent boots resulted in a )dead keyboard about 3 out of four times. Keyboard was dead on the 66. )I only tried two times. I was able to get 386bsd loaded on the SX-33 )and am able to boot from the hard disk, but still have a dead keyboard )about 60-75% of the time. Has any one else had this problem and is )there a fix for it? I have a Gateway EISA system and have been running 386BSD since mid-December. Last night was the first time I have had any keyboard problems, and even then I did not have to reboot...just terminate that particular X session. (The mouse input was still working.) I was able to log in again and evrything was fine. No problems. -- Daniel Ortmann NDSU Electrical Engineering ortmann@plains.nodak.edu Fargo, North Dakota