Description of problem: After a successfull completed installation of FC5 test1 and reboot, system fails to load. I see a black grub screen instead of the default blue one that boots the system. I manage to boot the system after entering in rescue mode and editing /boot/grub/device.map in order to reflect my real setup. I saw that device.map file contained only hd0 (floppy) hd1 (windows) and not containing hd1 (FC5test1) and hd2 (empty drive) So i added the missing devices and with grub-install /dev/hda i am now able to boot my freshly installed FC5 test1. This case is not easy to be handled by a novice user. My motherboard is ASUS s48x/sis648. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: Same behaviour appeared in my FC4 installation on the same system
These bugs are being closed since a large number of updates have been released after the FC5 test1 and test2 releases. Kindly update your system by running yum update as root user or try out the third and final test version of FC5 being released in a short while and verify if the bugs are still present on the system .Reopen or file new bug reports as appropriate after confirming the presence of this issue. Thanks
Does this still occur with FC5 test3?
i have tested again fc5 final release. It also fails to detect my drives. device.map contains only hd0 /dev/hda and nothing else...
I have tested fc6 final release. It fails again to detect my hard disks (again) device.map contains only hd0 /dev/hda and nothing else...(again) My configuration is similar (same asus motherboard 3 ide drives and one floppy) I can resolve this in a couple of minutes, but a new user will be confused...
Fedora Core 6 is no longer maintained. Is this bug still present in Fedora 7 or Fedora 8?
I didnt see this problem again. I have upgraded my hardware though so i cant test it in the same environment. We can close it for now.
Fedora apologizes that these issues have not been resolved yet. We're sorry it's taken so long for your bug to be properly triaged and acted on. We appreciate the time you took to report this issue and want to make sure no important bugs slip through the cracks. If you're currently running a version of Fedora Core between 1 and 6, please note that Fedora no longer maintains these releases. We strongly encourage you to upgrade to a current Fedora release. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained and closing them. http://fedoraproject.org/wiki/LifeCycle/EOL If this bug is still open against Fedora Core 1 through 6, thirty days from now, it will be closed 'WONTFIX'. If you can reporduce this bug in the latest Fedora version, please change to the respective version. If you are unable to do this, please add a comment to this bug requesting the change. Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we are following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. And if you'd like to join the bug triage team to help make things better, check out http://fedoraproject.org/wiki/BugZappers