Bug 103828
Summary: | Gateway Profile 2, with grub kernel doesn't boot all the way, with lilo it works fine | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Matthew Lenz <matthew> |
Component: | grub | Assignee: | Peter Jones <pjones> |
Status: | CLOSED WORKSFORME | QA Contact: | Mike McLean <mikem> |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | ||
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: | 2005-01-27 19:16:56 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
Matthew Lenz
2003-09-05 13:48:31 UTC
Does adding 'apm=off' help? Assuming all I need to do is type 'a' at the grub menu and add the params to the existing list of params (ro, and root) then no, it doesn't help. It doesn't seem to hang on the 'apm' kernel message it seems to hang right after the 'apm' kernel message. I tried a whole bunch of different combinations. Even if I do a 'apm=off' it will still show the kernel message right? Its just strange that it works with lilo and not grub, that almost seems like a grub issue to me, but if that was the case you wouldn't think it would beable to boot at all since it reads the kernel directly from the boot partion (so it must beable to find the drive) By some miracle I encountered this issue with friends system just this evening. He didn't have his keyboard hooked up and it locked in the exact same position during the kernel boot (right after the APM message line). His was a dell system P3-9xx MHz (don't know the model number). The Difference is that I _had_ a keyboard hooked up, BUT its a usb keyboard (the gateway profile boxes don't support ps2). It is almost like the kernel/grub didn't like the fact that we didn't have "hardware"/ps2 mice hooked up when booting. Hopefully this helps identify this as a known problem. This sounds like a BIOS fault. Either way, with no activity in more than a year, I'm going to close this bug. If it pops up again with a more current distro, feel free to open a new bug. |