Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!darwin.sura.net!haven.umd.edu!umd5.umd.edu!roissy.umd.edu!mark From: mark@roissy.umd.edu (Mark Sienkiewicz) Newsgroups: comp.os.386bsd.questions Subject: Re: 486DX2 and Tiny BSD? Date: 15 Jun 1993 19:39:03 GMT Organization: University of Maryland Lines: 19 Distribution: world Message-ID: <1vl8gn$5km@umd5.umd.edu> References: <1va1b7$5qg@genesis.MCS.COM> <1993Jun14.194018.443@nhqvax.hq.nasa.gov> NNTP-Posting-Host: roissy.umd.edu In article <1993Jun14.194018.443@nhqvax.hq.nasa.gov> mnewell@lupine.nsi.nasa.gov. writes: > >I had the sampe problem. Fortunately I was able to use the 386 >system to debug the 486; the problem for me turned out (apparently) >to be a timing problem in the keyboard initialization code; I added >some idling code immediately after the keyboard reset and it >cleared the problem up. This is fixed in the first patch kit to 386bsd. The hard part is you have to get it to work before you can apply the patches. :) If your machine has a FAST/SLOW speed switch, set it to SLOW (or the lowest clock speed it supports) and disable _all_ cache memory. You might be able to get it to boot. (worked for me a long time ago) -OR- Get Netbsd. It doesn't have this problem. (worked for me recently :)