Bug 29760
Summary: | [via/promise] Kernel Panic when booting from boot.img floppy | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Derrick Hamner <derrickh> |
Component: | kernel | Assignee: | Michael K. Johnson <johnsonm> |
Status: | CLOSED WORKSFORME | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-03-23 22:24:22 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Derrick Hamner
2001-02-27 16:23:52 UTC
Can you try a recent kernel from Rawhide? (version 2.4.2-0.1.25 or later); lot's of bad problems with via chipsets have been fixed in that. I'm unfamiliar with creating a new boot floppy with a different kernel that will start the RedHat install routine. I created a boot floppy from the Rawhide images/boot.img file and used it with the Wolverine CD's. It fails while trying to create the RAID 1 devices. The apparently relevant error messages are: <6> RAID level 65536 does not need chunksize! Continuing anyway. <3> md.c: personality 3 is not loaded! These messages are repeated for each RAID device. Well mixing different installers versus the CD won't work unfortionatly. Also, setting the bios to "normal performance" instead of "optimal performance" tends to fix this. We believe there are some chipset bugs in play here. The Normal performance option results in the exact same error message for me. Would you like to expand on your instructions for using a Rawhide kernel or create a boot.img with that kernel for me to try? Please re-open this bug report if you have reproduced this bug in the official release of Red Hat Linux 7.1, thanks! |