Hello there,
This is my first time posting to the mailing list, but I've been searching
on google for a solution to this problem for a couple of weeks and so far,
found nothing. Also tried the latest patches from andre and the rc1 and rc2
patches from kernel.org...
The problem is this.
The P4B533 has the intel 801DB IDE controller (stated as supported in rc1)
but in every 2.4 kernel I've seen so far, this appears in the bootup.
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PCI_IDE: unknown IDE controller on PCI bus 00 device f9, VID=8086, DID=24cb
PCI: Device 00:1f.1 not available because of resource collisions
PCI_IDE: (ide_setup_pci_device:) Could not enable device.
hda: Maxtor 2B020H1, ATA DISK drive
hdc: ASUS CD-S520/A, ATAPI CD/DVD-ROM drive
I've tried Redhat 7.2, 7.3, Mandrake 8.2 and SuSE 8 stock kernels.
In the later kernels, this means no DMA is possible, although in the earlier
2.4s (stock redhat 7.2 [2.4.7-10] for example) it's possible to turn on DMA,
at the risk of nuking your filesystem...
I even resorted to trying the 2.2.21 kernel, which didn't report a resource
conflict, but enabling DMA again nuked the filesystem.
(I imagine resource conflict isn't an error message in 2.2?)
Just wondered if this problem had been brought up before, and what causes
it (and of course, if there's a workaround before a patch arrives that fixes
it). I noticed on google that a similar problem with a different
motherboard was fixed in one of andres patches a month or so ago.
Thanks,
Andrew Halliwell
On Thu, 2002-07-18 at 13:45, Andrew Halliwell wrote:
> The P4B533 has the intel 801DB IDE controller (stated as supported in rc1)
> but in every 2.4 kernel I've seen so far, this appears in the bootup.
>
> Uniform Multi-Platform E-IDE driver Revision: 6.31
> ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
> PCI_IDE: unknown IDE controller on PCI bus 00 device f9, VID=8086, DID=24cb
> PCI: Device 00:1f.1 not available because of resource collisions
> PCI_IDE: (ide_setup_pci_device:) Could not enable device
Blame your BIOS vendor
The -ac tree has workarounds for the BIOS forgetting to set up the chip.
Let me know if rc1-ac7 works for you
Replying to an old thread:
On Thu Jul 18 2002 - 06:12:02 Alan Cox wrote :
> On Thu, 2002-07-18 at 13:45, Andrew Halliwell wrote:
> > The P4B533 has the intel 801DB IDE controller (stated as supported in rc1)
> > but in every 2.4 kernel I've seen so far, this appears in the bootup.
> >
> > Uniform Multi-Platform E-IDE driver Revision: 6.31
> > ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
> > PCI_IDE: unknown IDE controller on PCI bus 00 device f9, VID=8086, DID=24cb
> > PCI: Device 00:1f.1 not available because of resource collisions
> > PCI_IDE: (ide_setup_pci_device:) Could not enable device
>
> Blame your BIOS vendor
> The -ac tree has workarounds for the BIOS forgetting to set up the chip.
> Let me know if rc1-ac7 works for you
Hi, I have this motherboard and the same problem, I've naively looked for the string
in the kernel sources and commented the line, and it works fine (hdparm can make
the driver use DMA again, no corruption after applying this patch on successive
kernels for months)
The test must be here for a reason, I'm just saying it works in my case if some
people need a workaround.
Alain
--- linux-2.4.20-rc3/arch/i386/kernel/pci-i386.c.orig 2002-11-28 20:42:57.000000000 +0100
+++ linux-2.4.20-rc3/arch/i386/kernel/pci-i386.c 2002-11-28 20:44:05.000000000 +0100
@@ -315,7 +315,8 @@
r = &dev->resource[idx];
if (!r->start && r->end) {
printk(KERN_ERR "PCI: Device %s not available because of resource collisions
\n", dev->slot_name);
- return -EINVAL;
+ printk(KERN_ERR " MY FIX : IGNORE PREVIOUS ERROR\n");
+ // return -EINVAL;
}
if (r->flags & IORESOURCE_IO)
cmd |= PCI_COMMAND_IO;
The exact warning is :
kernel: PCI: Device 00:1f.1 not available because of resource collisions
And the lspci output in case you're interested :
:00.0 Host bridge: Intel Corp. 82845 845 (Brookdale) Chipset Host Bridge (rev 11)
00:01.0 PCI bridge: Intel Corp. 82845 845 (Brookdale) Chipset AGP Bridge (rev 11)
00:1d.0 USB Controller: Intel Corp.: Unknown device 24c2 (rev 01)
00:1d.1 USB Controller: Intel Corp.: Unknown device 24c4 (rev 01)
00:1d.2 USB Controller: Intel Corp.: Unknown device 24c7 (rev 01)
00:1d.7 USB Controller: Intel Corp.: Unknown device 24cd (rev 01)
00:1e.0 PCI bridge: Intel Corp. 82801BA/CA PCI Bridge (rev 81)
00:1f.0 ISA bridge: Intel Corp.: Unknown device 24c0 (rev 01)
00:1f.1 IDE interface: Intel Corp. 82801DB ICH4 IDE (rev 01) <----------------------------
01:00.0 VGA compatible controller: nVidia Corporation NV20 [GeForce3 Ti500] (rev a3)
02:09.0 Multimedia audio controller: Ensoniq 5880 AudioPCI (rev 02)
02:0a.0 SCSI storage controller: LSI Logic / Symbios Logic (formerly NCR) 53c810 (rev 11)
02:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C (rev 10)
Alain,
I really have to sleep now but I'll look into this tomorrow morning.
On Fri, 29 Nov 2002, Alain Tesio wrote:
> Replying to an old thread:
>
> On Thu Jul 18 2002 - 06:12:02 Alan Cox wrote :
>
> > On Thu, 2002-07-18 at 13:45, Andrew Halliwell wrote:
> > > The P4B533 has the intel 801DB IDE controller (stated as supported in rc1)
> > > but in every 2.4 kernel I've seen so far, this appears in the bootup.
> > >
> > > Uniform Multi-Platform E-IDE driver Revision: 6.31
> > > ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
> > > PCI_IDE: unknown IDE controller on PCI bus 00 device f9, VID=8086, DID=24cb
> > > PCI: Device 00:1f.1 not available because of resource collisions
> > > PCI_IDE: (ide_setup_pci_device:) Could not enable device
> >
> > Blame your BIOS vendor
> > The -ac tree has workarounds for the BIOS forgetting to set up the chip.
> > Let me know if rc1-ac7 works for you
>
> Hi, I have this motherboard and the same problem, I've naively looked for the string
> in the kernel sources and commented the line, and it works fine (hdparm can make
> the driver use DMA again, no corruption after applying this patch on successive
> kernels for months)
>
> The test must be here for a reason, I'm just saying it works in my case if some
> people need a workaround.
>
> Alain
>
>
>
> --- linux-2.4.20-rc3/arch/i386/kernel/pci-i386.c.orig 2002-11-28 20:42:57.000000000 +0100
> +++ linux-2.4.20-rc3/arch/i386/kernel/pci-i386.c 2002-11-28 20:44:05.000000000 +0100
> @@ -315,7 +315,8 @@
> r = &dev->resource[idx];
> if (!r->start && r->end) {
> printk(KERN_ERR "PCI: Device %s not available because of resource collisions
> \n", dev->slot_name);
> - return -EINVAL;
> + printk(KERN_ERR " MY FIX : IGNORE PREVIOUS ERROR\n");
> + // return -EINVAL;
> }
> if (r->flags & IORESOURCE_IO)
> cmd |= PCI_COMMAND_IO;
>
>
> The exact warning is :
>
> kernel: PCI: Device 00:1f.1 not available because of resource collisions
>
> And the lspci output in case you're interested :
>
> :00.0 Host bridge: Intel Corp. 82845 845 (Brookdale) Chipset Host Bridge (rev 11)
> 00:01.0 PCI bridge: Intel Corp. 82845 845 (Brookdale) Chipset AGP Bridge (rev 11)
> 00:1d.0 USB Controller: Intel Corp.: Unknown device 24c2 (rev 01)
> 00:1d.1 USB Controller: Intel Corp.: Unknown device 24c4 (rev 01)
> 00:1d.2 USB Controller: Intel Corp.: Unknown device 24c7 (rev 01)
> 00:1d.7 USB Controller: Intel Corp.: Unknown device 24cd (rev 01)
> 00:1e.0 PCI bridge: Intel Corp. 82801BA/CA PCI Bridge (rev 81)
> 00:1f.0 ISA bridge: Intel Corp.: Unknown device 24c0 (rev 01)
> 00:1f.1 IDE interface: Intel Corp. 82801DB ICH4 IDE (rev 01) <----------------------------
> 01:00.0 VGA compatible controller: nVidia Corporation NV20 [GeForce3 Ti500] (rev a3)
> 02:09.0 Multimedia audio controller: Ensoniq 5880 AudioPCI (rev 02)
> 02:0a.0 SCSI storage controller: LSI Logic / Symbios Logic (formerly NCR) 53c810 (rev 11)
> 02:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C (rev 10)
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
> On Thu Jul 18 2002 - 06:12:02 Alan Cox wrote :
>
> > On Thu, 2002-07-18 at 13:45, Andrew Halliwell wrote:
> > > The P4B533 has the intel 801DB IDE controller (stated as supported in rc1)
> > > but in every 2.4 kernel I've seen so far, this appears in the bootup.
> > >
> > > Uniform Multi-Platform E-IDE driver Revision: 6.31
> > > ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
> > > PCI_IDE: unknown IDE controller on PCI bus 00 device f9, VID=8086, DID=24cb
> > > PCI: Device 00:1f.1 not available because of resource collisions
> > > PCI_IDE: (ide_setup_pci_device:) Could not enable device
> >
> > Blame your BIOS vendor
> > The -ac tree has workarounds for the BIOS forgetting to set up the chip.
> > Let me know if rc1-ac7 works for you
The ICH4 IDE on my ASUS P4PE had the exact same problem, but the -ac pathes
make it hum along very nicely. Requring the PIIX driver, though, seems a
little wonky. Without -ac, the controller is detected as "ICH4" and doesn't
work. With the -ac patches, it works, but is detected as PIIX. Rather
confusing. Perhaps the the Configure.help should mention the ICH4?
2.4.19-vanilla didn't work. The first patch tried was 2.4.19-ac4, and that
worked. Now on 2.4.20-rc4-ac1 and all is still good.
I hope the workarounds for this get merged into 2.4.21-preX.
Regards,
Ian Morgan
--
-------------------------------------------------------------------
Ian E. Morgan Vice President & C.O.O. Webcon, Inc.
[email protected] PGP: #2DA40D07 http://www.webcon.ca
* Customized Linux network solutions for your business *
-------------------------------------------------------------------
On Fri, 2002-11-29 at 04:09, Ian Morgan wrote:
> The ICH4 IDE on my ASUS P4PE had the exact same problem, but the -ac pathes
> make it hum along very nicely. Requring the PIIX driver, though, seems a
> little wonky. Without -ac, the controller is detected as "ICH4" and doesn't
> work. With the -ac patches, it works, but is detected as PIIX. Rather
> confusing. Perhaps the the Configure.help should mention the ICH4?
Just a labelling difference. ICH4 is the chipset, it contains a PIIX IDE
controller
On Fri, 29 Nov 2002, Alan Cox wrote:
> On Fri, 2002-11-29 at 04:09, Ian Morgan wrote:
> > The ICH4 IDE on my ASUS P4PE had the exact same problem, but the -ac pathes
> > make it hum along very nicely. Requring the PIIX driver, though, seems a
> > little wonky. Without -ac, the controller is detected as "ICH4" and doesn't
> > work. With the -ac patches, it works, but is detected as PIIX. Rather
> > confusing. Perhaps the the Configure.help should mention the ICH4?
>
> Just a labelling difference. ICH4 is the chipset, it contains a PIIX IDE
> controller
Yes, I know that, but many people probably won't, was my point. Then again,
I guess anybody building their own kernel probably will have some clue about
what hardware is in their box, so it's probably not a big deal.
Regards,
Ian Morgan
--
-------------------------------------------------------------------
Ian E. Morgan Vice President & C.O.O. Webcon, Inc.
[email protected] PGP: #2DA40D07 http://www.webcon.ca
* Customized Linux network solutions for your business *
-------------------------------------------------------------------