Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!nntp.coast.net!news.sprintlink.net!nwnews.wa.com!uw-coco!uw-beaver!news.u.washington.edu!news.alt.net!news.serv.net!solaris.cc.vt.edu!csugrad.cs.vt.edu!csugrad.cs.vt.edu!not-for-mail From: jaitken@csugrad.cs.vt.edu (Jeff Aitken) Newsgroups: comp.unix.bsd.freebsd.misc Subject: wdc0 not found during bootup Date: 25 Nov 1995 23:48:36 -0500 Organization: Virginia Tech Computer Science Dept, Blacksburg, VA Lines: 47 Message-ID: <498rj4$ftg@csugrad.cs.vt.edu> Reply-To: jaitken@vt.edu NNTP-Posting-Host: csugrad.cs.vt.edu X-Newsreader: TIN [version 1.2 PL2] I've got a 2.1.0R system that can't find wdc0 during bootup. The machine is a 486 clone with the following hardware: Diamond Speedstar 64 (PCI) video card, in PCI slot "3" SC200 NCR SCSI controller (53c810) in PCI slot "2" CMD-640 IDE (EIDE?) controller in PCI slot "1" Generic ISA multi-function board (serial/parallel/etc) SMC8013EWC (ISA) ethernet card ProAudioSpectrum (with SCSI) ISA card I Run FreeBSD off of a 1GB Micropolis SCSI-2 disk (attached to the NCR controller). I run Windows 95 off of two IDE drives (both Conner drives). Windows '95 works fine (I'm using it to post this message ;) but FreeBSD cannot seem to find the IDE controller at boot time. It complains that "wdc0 not found at 0x170" during the probe. I know that this hardware can work, because I used to mount my DOS partitions. But I've been changing things around quite a bit hardware wise, swapping a few cards here and there, and I can't remember when exactly I first noticed the problem. I booted the 2.0.5R boot floppy to see if perhaps something had changed with the 2.1 release, but encountered the same problem. I've got one of the older PCI motherboards where you have to set a jumper to indicate what IRQ each PCI device corresponds to, and all of those jumpers are (as far as I can tell) set properly (the IDE controller is set to 14, of course). I'm not sure whether or not the device is a busmaster (I'm not even sure what a "busmastering device" really is) but I've tried setting it one way then the other, and had the same result both times. FWIW, Windows 95 reports that the IDE controller is working properly (duh!) and has an I/O address of 0x1f0 - 0x1f7. One other piece of relevant information: when the machine boots (I'm running the 2.1 GENERIC kernel) during the probe of the PCI bus, I get a message that looks something like this (I'm typing this from memory, so it may not be exact) pci0:3 CMD class=storage (no driver assigned) that's not quite right, but it appears that it finds the device, but assigns no driver to it. Do I need to do anything to correct this? I don't believe I ever had to do anything in the past. Thanks for any pointers. -- Jeff Aitken jaitken@vt.edu