Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!aardvark.ucs.uoknor.edu!ns1.nodak.edu!netnews.nwnet.net!news.clark.edu!spool.mu.edu!howland.reston.ans.net!math.ohio-state.edu!cs.utexas.edu!not-for-mail Newsgroups: alt.sys.pc-clone.gateway2000,comp.os.386bsd.questions Subject: Re: FreeBSD install problems on Gateway2000 DX66V Message-ID: <199310201552.JAA17673@bsd.coe.montana.edu> From: nate@bsd.coe.montana.edu (Nate Williams) Date: 20 Oct 1993 10:50:13 -0500 Sender: daemon@cs.utexas.edu Organization: UTexas Mail-to-News Gateway NNTP-Posting-Host: cs.utexas.edu Lines: 58 > >> 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? ;) You got a prompt. A hang would not have gotten the machine that far. > > I did suspect the keyboard; there were no panic messages, or anything. A keyboard problem doesn't panic the system. It just doesn't recognize th keyboard. > 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? Quick and dirty explanation is that it's there to verify that a keyboard is there and to place it in a 'known-state'. (More technical explanations are welcome IF you think it's necessary) > >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. Was the kernel one that was configured and compiled with only the hardware of the machine taken into account, or was it the GENERICAH kernel? Only when I removed the non-relevant devices and created my own kernel with an edited config file did the machine boot correctly. > 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? I'll let the NetBSD questions be answered by NetBSD folks. Nate -- nate@bsd.coe.montana.edu | Freely available *nix clones benefit everyone, nate@cs.montana.edu | so let's not compete with each other, let's work #: (406) 994-4836 | compete with folks who try to tie us down to home #: (406) 586-0579 | proprietary O.S.'s (Microsloth) - Me