*BSD News Article 22652


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!swrinde!cs.utexas.edu!not-for-mail
From: mike.long@analog.com (Mike Long)
Newsgroups: alt.sys.pc-clone.gateway2000,comp.os.386bsd.questions
Subject: Re: FreeBSD install problems on Gateway2000 DX66V
Date: 20 Oct 1993 10:32:21 -0500
Organization: UTexas Mail-to-News Gateway
Lines: 53
Sender: daemon@cs.utexas.edu
Message-ID: <9310201531.AA10660@cthulhu>
References: <199310201510.JAA15583@bsd.coe.montana.edu>
Reply-To: Mike Long <Mike.Long@analog.com>
NNTP-Posting-Host: cs.utexas.edu

>From: nate@bsd.coe.montana.edu (Nate Williams)
>Date: Wed, 20 Oct 1993 09:10:52 -0600
>
>> 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)

How can you tell the difference? ;)

I did suspect the keyboard; there were no panic messages, or anything.

>> 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.

Never thought of that.  Another thing that happens during both FreeBSD
and NetBSD boot processes is that the NumLock LED gets turned off, but
I think that is normal.  What is a keyboard probe, and why is it necessary?

>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.

When FreeBSD froze at the login: prompt it had booted off of the
kernel on my hard drive.

>Nate

PS: With NetBSD, I get the "wdc0: extra interrupt" messages that some
others have reported.  They don't seem to affect anything, but I
wonder where they come from.  They occur during autoconfiguration at
boot time and when I modify the disklabel on the disk.  I only have
one IDE drive, on my motherboard's built-in controller.  Thoughts?
--
Mike Long                                         Mike.Long@Analog.com
VLSI Design Engineer                              voice: (617)461-4030
Analog Devices, SPD Div.                            FAX: (617)461-3010
Norwood, MA 02062                            *this = !opinion(Analog);