Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!bunyip.cc.uq.oz.au!harbinger.cc.monash.edu.au!yeshua.marcam.com!usc!cs.utexas.edu!uunet!caen!usenet.coe.montana.edu!bsd.coe.montana.edu!nate From: nate@bsd.coe.montana.edu (Nate Williams) Newsgroups: comp.os.386bsd.questions Subject: Re: console lockup when booting floppies Date: 4 Jan 1994 23:09:20 GMT Organization: Montana State University - Bozeman MT Lines: 32 Message-ID: <2gcsv0$606@pdq.coe.montana.edu> References: <RIM.94Jan4103314@roadrunner.bme.ri.ccf.org> NNTP-Posting-Host: bsd.coe.montana.edu In article <RIM.94Jan4103314@roadrunner.bme.ri.ccf.org>, Robert M. Cothren <rim@bme.ri.ccf.org> wrote: >I am trying to install FreeBSD 1.0R on my system at home, but am >having problems with the floppy system. I have a 66MHz DX2 with a 34F >and an ATI Ultra Pro LB, 3 serial lines (2 16550As), an LPT, and 1.44 >and 1.2 floppies. The kcopy-bt kernel floppy appears to boot fine and >probes my hardware correctly. However, whether I use the filesystem >floppy or stay with the kernel copy floppy when prompted for a >filesystem, the keyboard does not respond after I get a prompt. It >works fine when I have to inform the system that the filesystem floppy >is inserted. See the previous article I wrote with the subject of FreeBSD floppies or something like that. Basically, the keyboard probe has problems when booting off the floppy. Bounce on the num-lock key when the kernel starts to execute (the copyright and probe commands are printed out) until the LED blinks and you should be able to install onto your hard-drive. Once that is done your problems *should* go away. 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