Bug 120366
Summary: | Hard Lockup after RH9 install on Gateway E-4100 | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Doug Cudaback <deadmeat_69> |
Component: | installer | Assignee: | Michael Fulbright <msf> |
Status: | CLOSED WORKSFORME | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-04-15 21:17:35 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
Doug Cudaback
2004-04-08 02:38:16 UTC
Where did you install the boot loader? Does this happen with fC1? Jeremy: Boot Loader was installed on boot, then on root partition. Got same results. That was last Thursday. Read on... UPDATE: When we got to the screen that says Automatic or Manual Partitioning, we chose Automatic, then on the next screen it lists current partitioning. Apparently, if you just click Next and accept what is defaulted and continue the load the drive becomes null for some reason. (i.e. it doesn't even show up in BIOS when you slave the drive to re-wipe it) When we deleted /dev/hda2 and /dev/hda3 partitions and recreated them using the Free space partition that it generated, it worked fine, and the load completed and the reboot worked. It also works when we select Manual Partitioning and do it all by hand...go figure. This makes us believe it has something to do with the Gateway systems themselves, rather than with the Boot Loader on Red Hat, since a co- worker has RH9 loaded on a Compaq at home with no difficulty. He tried the install the same way we did it on the Gateways, and his still worked fine. I believe we are calling this issue closed on our end, but feel free to research and make comments for future reference as other users may be experiencing this issue...Thanks for the assist! Doug |