FedoraThis forum is for the discussion of the Fedora Project.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I just ran software updater in Fedora Core 5. I noticed that some applications updated the kernel during install. After Software Updater finished, it recommended reboot of the system. When I clicked OK, the system hung on Grub during the reboot. I've run Red Hat since v3 and switched to Fedora Core beginning with v2. I've done both system and software updates, but have never had the system fail to reboot. Can someone suggest how I repair the boot failure? I've run linux for some time but consider myself a novice. Thanks for your help! --wade
what is the message of the kernel? And, have you do any changes on the partition table?
You stuck at grub, can you see the nice GUI grub screen or a black screen writing grub> ?
Regards,
Ks
Did you edit your Grub configuration file to point to the newly installed kernel before rebooting? If not try booting into an older kernel from the grub screen and then editing the grub.conf file.
Sorry for not responding sooner. I was waiting for an email saying I had a response and I never received one. I will check my profile.
I've had no changes to the partition. I upgraded to Fedora Core 5 several months ago from Fedora Core 3. At that time I did update all the software then using Software Updater. I had no problems.
I had previously updated the kernel while trying to install trial versions of VMware and Win4Lin. (I need Windows only so that I can connect MS FrontPage to a Windows Web Server and Wine does runs FrontPage, but does not allow connection to a MS server). But, I had no problems with the distrobution after installations.
Then last week I ran Software Updater again for the most current releases. It took 48 hours to download all the software updates in three sessions. After the second and third sessions, I received a message that I needed to reboot the system, so I can only assume that the kernel was updated both times. I believe that I actually did a kernel update on the second session download.
After the last reboot, BIOS ran and found my two SCSI hard drives (that Fedora Core 5 is installed on). Next, while the screen was still black, the word GRUB appears and the boot stops.
It will be really difficult to install Fedora Core 5 on another hdd and boot the system as the internal SCSI controller will default. I do not have another SCSI drive, though I could install on an ATA drive and disable the SCSI boot in the controller BIOS.
I have a ton of data on two SCSI drives -- about 140-Gb -- I was just getting back into Linux and was only using Windows XP (on a serial ATA drive which is not powered on during Fedora boot) when I need to work on my FrontPage enabled webs.
Thanx everyone for your responses, but can you help me with the best way to proceed. I'm confused about what the problem might be.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.