From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows 98; Win 9x 4.90)
Description of problem:
I am trying to install Red Hat 7.3 on an ICP ROCKY-3732EVS Single Board
Computer (SBC). This features a Compact Flash (CFII) socket that accepts IBM's
1GB Microdrive. This appears as a secondary master on the IDE and is recognised
by Linux on boot-up, but when the OS tries to carry out a partition check, the
screen just freezes after displaying "hdc".
I have successfully installed Mandrake 8.1 on this Microdrive, plus I have been
told by our PC supplier that they have successfully installed Red Hat 7.2.
If I fit a standard hard disk on the primary IDE channel, then Red Hat 7.3
installs and boots up OK, but only when the Microdrive is removed or I issue
the boot parameter "linux hdc=noprobe".
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Insert microdrive in CFII socket
2. Insert Red Hat 7.3 Installation CDROM in CD drive
3. Turn on PC
Actual Results: Linux successfully recognises IBM microdrive on hdc, but when
it attempts a partition check, the system hangs.
Expected Results: Linux should have displayed the existing partitions and
continued with installation process.
I have attached a screenshot from the installation process.
Created attachment 74564 [details]
Screenshot from installer
This is hanging in the kernel at the start, the installer has not begun to run yet.
You might want to check that there is a valid partition table on the microdrive.
The microdrive came formatted with a FAT partition. I have subsequently
installed Mandrake Linux 8.1 on it, which obviously repartitioned and formatted
the drive successfully.
Installation Red Hat 7.3 hangs on 'partition check' on Ultra DMA 4
drive, but pass fine Ultra DMA 2 and Ultra DMA 5 drives.
Award BIOS 6 version, Sony Vayo desktop PC - PCV-RX650.
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases,
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/