From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0) Description of problem: Current Hardware: Compaq Proliant 5000 1024M memory Compaq Smart/2 RAID Controller - Slot 5 Symbios Embedded Controller Symbios Controller in Slot 3 ----00---- This bios doesn't support the 2.8M boot image, so I created a boot floppy using boot.img. I receive a Kernel Panic, please add root= How reproducible: Always Steps to Reproduce: 1. Curse old bioses (biosi?) that dont support 2.8M images 2. boot floppy 3. receive error Actual Results: Unable to boot from floppy to start install of 7.1 Here are some lilo options Ive used: linux noprobe expert expert noprobe linux dd Expert mode doesn't seem to do anything...It's like it doesn't even matter. Expected Results: Smooth install of RH 7.1 Additional info: Here are some kernel messages I get: PCI: Device 00:78 Not Found by BIOS PCI: Device 00:a0 Not Found by BIOS PCI: Device 00:c8 Not Found by BIOS PCI: Device 00:d0 Not Found by BIOS PCI: Device 02:78 Not Found by BIOS Auto detecting RAID Arrays Autorun ... ... Autorun done VFS: Can't open root device "" or 08:41 Please append a correct "root=" boot option Kernel panic: VFS: Unable to mount root FS on 08:41
This is a DUP of 37218 -- Sorry, Im going to try to download a new ISO. somebody check the CRC value of the ISO on ftp.redhat.com because that is where I downloaded the original. -Bill *** This bug has been marked as a duplicate of 37218 ***
The MD5s are all OK, so its not the ISO image that is a problem ---Yours edc2d5e1ab6093e3d486cc38dc12511a seawolf-i386-SRPMS.iso 596b1575773e88e066326f6741312a6f seawolf-i386-disc1.iso f27b912299572a542cd663b712444445 seawolf-i386-disc2.iso 59f3333435378fb1645700731c91bc54 seawolf-i386-powertools.iso --Mine 596b1575773e88e066326f6741312a6f *seawolf-i386-disc1.iso f27b912299572a542cd663b712444445 *seawolf-i386-disc2.iso Why?
This seems like a kernel problem. Changing component.
This is a Compaq BIOS bug. Please see the end of bug 36940 for how to work around this. Please confirm if this makes it work for you.
*** This bug has been marked as a duplicate of 36940 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.