Intel ICH4 ide not working for 2.4.19 and 2.4.20

Intel ICH4 ide not working for 2.4.19 and 2.4.20

[Bill Metzenthen]

I have a machine with a Gigabyte 8IEX motherboard.  This MB uses an Intel 845E 
chipset with an Intel ICH4.  I'm using a 2.4 GHz P4 with it, and 1 GByte of 
memory.

I have been using RedHat kernels, initially 2.4.18-14 from RedHat 8.0, which 
works o.k.

Then I tried some kernels from rawhide, first 2.4.19-0.pp18, then 
2.4.19.pp.20, and finally 2.4.20-0.pp.3.  These all failed to identify 
anything attached to the ide ports.

Finally, I grabbed a copy of the original 2.4.20 kernel sources, applied the 
2.4.20-ac2 patches, and compiled these with a similar config to that used by 
the RedHat kernels.  This failed in a similar way to the redhat kernels.

I don't have another machine hooked up to the serial port at the moment, but a 
hand copied version of the on-screen messages leading up the point of failure 
is:

Uniform Multi-Platform E-IDE driver Revision: 7.00beta-2.4
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ICH4: IDE controller at PCI slot 00:1f.1
PCI: Found IRQ 5 for device 00:1f.1
ICH4: chipset revision 1
ICH4: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xcc00-0xcc07, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xcc08-0xcc0f, BIOS settings: hdc:DMA, hdd:DMA

There is a delay of a second or two here while the ide devices are failed to 
be detected.  The boot process then continues until it fails because it 
cannot open the root device.

I've looked through the archives and there doesn't appear to be anyone else 
with this particular problem.  Does anyone have an idea about what I should 
do to fix my problem?

Bill

ps: apologies for sending a subscribe message to the list in error.

Re: Intel ICH4 ide not working for 2.4.19 and 2.4.20

[Alan Cox]

On Sat, 2002-12-14 at 07:48, Bill Metzenthen wrote:
> I've looked through the archives and there doesn't appear to be anyone else 
> with this particular problem.  Does anyone have an idea about what I should 
> do to fix my problem?

I'm pretty sure I know what this is, if so it'll be fixed fairly soon