Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!zombie.ncsc.mil!news.mathworks.com!europa.chnt.gtegsc.com!howland.reston.ans.net!sol.ctr.columbia.edu!hanna!wpaul From: wpaul@ctr.columbia.edu (Bill Paul) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Newbie boot floppy problem -Help me! Date: 20 Aug 1995 16:14:12 GMT Organization: Columbia University Center for Telecommunications Research Lines: 67 Message-ID: <417n0l$cpq@sol.ctr.columbia.edu> References: <415o9p$526@newsbf02.news.aol.com> NNTP-Posting-Host: hanna.ctr.columbia.edu X-Newsreader: TIN [version 1.2 PL2] Daring to challenge the will of the almighty Leviam00se, BillPaul (billpaul@aol.com) had the courage to say: ^^^^^^^^ AAAAAAAAHHHHHHHHHH!!!!!! The pod people are coming! They're coming, do you hear?! They've already replaced me!! You could be next!! _YOU_ could be next!!! : I am trying to install freeBSD 2.0.5 and am having some problems with the : boot floppy. I created the floppy with rawrite.exe from a DOS machine. : When I boot the target computer with the disk, it starts out OK, "Probing : for devices on the ISA bus" finding everything correctly until "wdc1 not : found at 0x0170". After this message, it hangs. No key press does : anything, and the floppy and hard disk are silent. I assume it is looking : for a second harddisk. No, it's looking for a second hard disk _controller_. wdc1 is the secondary IDE controller. Few people actually have two IDE controllers in their systems (and know how to set them up right) but FreeBSD supports them for those that do. First thing I would do: Wait a while longer. The timeout can be long sometimes. Second thing I would do: Boot with the -c flag (type -c at the Boot: prompt) and disable wdc1, along with any other hardware that could be causing trouble (CD-ROM controller drivers, other ethernet adapters, SCSI controllers, etc...). If you have a math co-processor, then do _NOT_ disable npx0 (that's the math co-processor driver). If this gets you to the point where you can do the install, remember that you'll need to use the -c flag and siaable the same devices at least one more time, namely when your machine boots from the hard disk for the first time. When the system boots this time, the -c information will be saved and you won't have to type it again. Later, you can make a custom kernel if you want that doesn't have the unneeded drivers compiled in. : Any suggestions are greatly appreciated. : Thanks Hope this helps. : -Bill Paul : ************************************ : Bill Paul (that was my last name!) : billpaul@aol.com : San Diego, CA : ************************************ AAAAAAAHHHHHHHH!!!!!!! Run for the hills!!! Run for the hills!!!!!! Is this weird or what?! :) -Bill -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~T~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -Bill Paul (212) 854-6020 | System Manager Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The Møøse Illuminati: ignore it and be confused, or join it and be confusing! ~~~~~~ "Welcome to All Things BSDish! If it's not BSDish, it's crap!" ~~~~~~~