Bug 140078
Summary: | Installation is very ... very long | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Pierre Fumery <pierre.fumery> |
Component: | kernel | Assignee: | Jason Baron <jbaron> |
Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.0 | CC: | knoel, pierre.fumery |
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: | 2012-06-20 16:07:43 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
Pierre Fumery
2004-11-19 17:09:28 UTC
can you remove the 'quiet' boot parameter, and see if there are any kernel messages during the 'pause' ? the 'blank screen with a mouse pointer' sounds suspicious, this sounds to me like you're in X, so this is possibly not a kernel problem, but something in userspace thats broken. Can you ctrl-alt-f1 and see if you can diagnose whats going on if thats the case ? We'll try a new installation with recommended boot parameters and we'll let you know. I apologize to not have answered sooner but I didn't get notification of your comment, or I missed it ? I just added my E-mail address in the "CC" to be sure I'll get further comments. Was this still a problem with the final release ? Any debug output as requested in comment #1 would be useful if so. Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. Please See https://access.redhat.com/support/policy/updates/errata/ If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue. |