Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!sdd.hp.com!cs.utexas.edu!not-for-mail From: nate@bsd.coe.montana.edu (Nate Williams) Newsgroups: alt.sys.pc-clone.gateway2000,comp.os.386bsd.questions Subject: Re: FreeBSD install problems on Gateway2000 DX66V Date: 20 Oct 1993 10:09:19 -0500 Organization: UTexas Mail-to-News Gateway Lines: 35 Sender: daemon@cs.utexas.edu Message-ID: <199310201510.JAA15583@bsd.coe.montana.edu> NNTP-Posting-Host: cs.utexas.edu > I tried installation first with internal and external CPU caches on, > and it hung on the first "Do you want to install FreeBSD (y/n)" > question, after I put in the filesystem-floppy. Is it hung or does the keyboard not respond? (I suspect that the keyboard is not working. I know we fixed it, but it's not fixed) > > When I turned both caches off, I managed to get all the way through > the install process, reboot, fsck cleans up filesystem, reboot, get > login: prompt. The machine would ALWAYS hang at this point. I have a very strong clue that if you bounce on the keyboard when booting up you'll get the machine to quit 'hanging'. I have been having problems on PC's here with the problem, and by bouncing on a key (I use num-lock so I can see the LED's flicker when the keyboard is back on line) I can guarantee the KB probe to work correctly. This problem is independent of the cache. The caches off probably messed with the timing of the probe code enough to make it work. Since it appears NetBSD still works, we need to figure out why the keyboard stuff doesn't work in FreeBSD. Something bad is being done, and I'm getting lots of cases where once we get the machine installed and running a local kernel all of the keyboard problems go away here. This behavior (locked up keyboards) has happened on ALL of the DEC machines I've installed FreeBSD on lately. Nate