Bug 181324 - Installer hangs when attempting a soft reboot.
Summary: Installer hangs when attempting a soft reboot.
Status: CLOSED DUPLICATE of bug 181319
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda   
(Show other bugs)
Version: 4
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Mike McLean
Depends On:
TreeView+ depends on / blocked
Reported: 2006-02-13 14:24 UTC by Robert MacRae
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-13 14:41:29 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Robert MacRae 2006-02-13 14:24:33 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)

Description of problem:
During the bootup process, the installer undertakes to override a jumper setting on one of my harddrives that limits the capacity to 32GB. This setting is necessary because the bios does not recognize drives larger than this. The net effect is that the system cannot perform a soft reboot - it hangs at the point where the bios attempts to query the drives. A hard reboot usually works immediately, but sometimes requires a delay of about 30 seconds before the hardware will reset itself.

The reset mentioned above is explicitly detailed in the bootlog.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Install FC4
2. Attempt a soft reboot.

Actual Results:  The soft reboot fails.

Expected Results:  The reboot should have succeeded.

Additional info:

This is clearly a hardware problem having to do with a fairly old bios. The point, however, is that the installer should respect the user's bios settings since they are there for a reason. The behavior of FC4 is quite different from that of FC3 which works just fine and does not attempt to reset the reported size of the drive.

Comment 1 Chris Lumens 2006-02-13 14:41:29 UTC

*** This bug has been marked as a duplicate of 181319 ***

Note You need to log in before you can comment on or make changes to this bug.