From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020827
Description of problem:
installer hangs during partition check on Compaq 1690 laptop. Redhat 6.2 was
able to install successfully.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot either from CD or boot.img or pcmcia.img
Actual Results: ide-floppy driver 0.99.newide
Expected Results: Should have continued on after this point, instead it hangs
Are you referring to the kernel's partition check right at the beginning?
Yes, its while I'm trying to boot off the install CD so I upgrade.
I would *really* like to get this laptop upgraded to RH7.3! Please can you offer
any suggestions of how to accomplish this? Is there a way to do this via some
form of "rpm -F" command after I've booted into RH6.2? Are there any versions
of the boot.img available anywhere that either bypass the partition check, or
do it differently than the RH7.3 boot.img file?
The RedHat 8.0 pcia.img yields the exact same results as 7.3, the computer
PCI No IRQ known for interrupt pin A of device 00:10.0. Please try using
ALI15X3: chipset revision 32
hda: FUJITSU MHR2020AT D, ATA DISK drive
ide: Assuming 33 MHz...
hdc: TOSHIBA DVD-ROM SD-C2202, ...
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: 39070080 sectors (20004 MB) w/2048KiB Cache, CHS-2432/255/63, (U)DMA
hdc: ATAPI 24X DVD-ROM drive, 128kB Cache
Uniform CD-ROM driver Revision 3.12
ide-floppy driver 0.99.newide
The RH 7.0 pcmcia.img boot image works, but of course will not install 7.3 and
I can't download 7.0 via a 40kb connection.
The RH 7.2 pcmcia.img and pcmciadd.img combination boots successfully, and
lauches anaconda. It appears to be working!
OK, 7.3 is loaded, but now it hangs at the same partition check during a
normal boot. I'm now assuming this is a kernel problem. Is there a way to
use the 7.2 boot disk to load a different kernel via a rescue mode?
Adding "ide=nodma" seems to fix the problem. I found this in the RH8.0 online docs.
Should be fixed in RH9 and errata kernels nowdays. The updated ALi driver knows
about specific chip limitations and handles them properly.