Bug 13174

Summary: 3.- branch hardware probe does not detect primary IDE controller
Product: Base System Reporter: andrew.lofthouse <andrew.lofthouse>
Component: kernAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 3.2-STABLE   
Hardware: Any   
OS: Any   

Description andrew.lofthouse 1999-08-16 14:10:01 UTC
3.2-RELEASE (and 3.0-STABLE, for that matter), do not detect the primary IDE controller (wdc0). When the BIOS settings are changed to "hard drive auto-detect" and then saved, the controller is detected that time. This work-around only works one time. If the machine is rebooted, I need to enter BIOS setup and save settings, then the controller is detected again. 

NOTE: problem report KERN/11513 MAY be a related problem. In that problem report, the dmesg output showed that the primary IDE controller was not detected ("wdc0 not found at 0x1f0"). The submitter also uses the Intel 430TX chipset (or at least one that uses the same PIIX4 controller):
"chip0: <Intel 82443BX host to PCI bridge> rev 0x03 on pci0.0.0
chip1: <Intel 82443BX host to AGP bridge> rev 0x03 on pci0.1.0
chip2: <PCI to PCI bridge (vendor=1011 device=0024)> rev 0x03 on pci0.2.0
chip3: <Intel 82371AB PCI to ISA bridge> rev 0x02 on pci0.7.0
ide_pci0: <Intel PIIX4 Bus-master IDE controller> rev 0x01 on pci0.7.1
chip4: <Intel 82371AB Power management controller> rev 0x02 on pci0.7.3"

How-To-Repeat: Install 3.2-RELEASE (or -STABLE) on the machine. Attempt to boot without re-setting BIOS settings each time.
Comment 1 andrew.lofthouse 1999-08-17 13:28:50 UTC
>>Additional Information: I have two hard drives connected to the primary
IDE controller (wdc0),
a 1.27 GB Samsung as master and a 6.54 GB Seagate as slave. I have an ATAPI
CD-ROM
drive as master on the secondary controller (wdc1). wdc1 is detected
correctly every time I boot
the machine. wdc0 is not detected unless I enter BIOS setup and save
settings as I mentioned
above. This is only a problem with 3.- branch (I've had 2.2.8-RELEASE on the
same machine
with no problems). The critical nature of this bug refers to the fact that
the root filesystem cannot
be mounted without the primary controller being detected (I have no SCSI
drives on the system).
Comment 2 Sheldon Hearn freebsd_committer freebsd_triage 1999-10-01 13:04:21 UTC
State Changed
From-To: open->feedback

Any news on this one? 
Comment 3 Sheldon Hearn freebsd_committer freebsd_triage 1999-10-04 14:40:53 UTC
State Changed
From-To: feedback->closed

Originator moved two disks, which he now suspects didn't like each 
other, onto separate channels and has had things working 
with  that configuration since then.