Fedora Linux Support Community & Resources Center

Go Back   FedoraForum.org > Other Versions > EOL (End Of Life) Versions
FedoraForum Search

Forgot Password? Join Us!

EOL (End Of Life) Versions This is a Forum to discuss problems and workarounds for versions of Fedora that have passed End of Life.

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 3rd June 2007, 01:23 AM
caduceus Offline
Registered User
 
Join Date: Jun 2007
Posts: 3
Latest FC6 update makes system non-bootable

I know everyone's hot about FC7, but I'm not quite ready to upgrade to it yet (this system only has a CD, and it doesn't appear I can upgrade easily without a DVD reader at this time).

Today, my FC6 test system (370DER mboard with dual P-III 866, 768MB), which has been working fine for months, failed to boot after a "yum update". The update included a kernel update (was 2948, new 2952). 2948 had been working).

After I rebooted, it stuck forever at "Starting udev:", never printing the "OK".

I tried rebooting the previous kernel, and it did the same thing.

I tried adding "acpi=off", and it would at least print the "OK", and then hang immediately afterwards.

I used the rescue CD and changed udev_log="debug", and could see it was hanging on something to do with the hotplug modules. Since I didn't think I needed them, I moved that rules file aside, and tried again - and it booted! But only once. Attempts afterwards yielded the exact same results as before - I have no idea why it booted.

I started researching, and remembered that way-back-when trying to install FC4 originally, I had to use "agp=off" on the command line because of the motherboard. So I tried that - and it booted!!! Once. It's driving me mad. I've tried combinations of the old and new kernels, acpi=off, and agp=off, and I can't get it to finish booting again. With acpi=off it seems get past udev, but then hang. I can't tell what it is supposed to be doing after that.

Anybody able to offer some ideas here? I even tried to boot an Ubuntu Feisty CD, and it hung checking the hardware, probably because I needed acpi and or agp off.
Reply With Quote
  #2  
Old 3rd June 2007, 01:42 AM
ppesci's Avatar
ppesci Offline
Registered User
 
Join Date: May 2006
Location: Caracas, Venezuela
Posts: 1,828
Sounds to me you have a hardware problem. May be you can start from a rescue cd and see the /var/log/messages file from your hard disk.

HTH
__________________
Pietro Pesci Feltri

PowerBook 15" G4 and
MacBook Pro 17" Intel Core 2 Duo
Intel I5 Desktop
Reply With Quote
  #3  
Old 3rd June 2007, 01:59 AM
caduceus Offline
Registered User
 
Join Date: Jun 2007
Posts: 3
Quote:
Originally Posted by ppesci
Sounds to me you have a hardware problem. May be you can start from a rescue cd and see the /var/log/messages file from your hard disk.

HTH
Well, if it could boot to the point of writing to /var/log/messages, perhaps something would be there?

The only data is from the last time it did boot, with all the udev debug messages.

What is the next item after udev to start? I don't have a system to muck with at the moment.
Reply With Quote
  #4  
Old 3rd June 2007, 06:51 PM
ppesci's Avatar
ppesci Offline
Registered User
 
Join Date: May 2006
Location: Caracas, Venezuela
Posts: 1,828
The answer is in the same file, check wath is executing after udev.

HTH
__________________
Pietro Pesci Feltri

PowerBook 15" G4 and
MacBook Pro 17" Intel Core 2 Duo
Intel I5 Desktop
Reply With Quote
  #5  
Old 3rd June 2007, 06:52 PM
ppesci's Avatar
ppesci Offline
Registered User
 
Join Date: May 2006
Location: Caracas, Venezuela
Posts: 1,828
The answer is in the same file, check what is executing after udev.

HTH
__________________
Pietro Pesci Feltri

PowerBook 15" G4 and
MacBook Pro 17" Intel Core 2 Duo
Intel I5 Desktop
Reply With Quote
  #6  
Old 3rd June 2007, 06:57 PM
caduceus Offline
Registered User
 
Join Date: Jun 2007
Posts: 3
Actually, I managed to get it to boot reliably with only the "noapic" option. I've never needed that before, so I don't know why I needed it now. "noapic" also worked to get Ubuntu to boot from the CD all the way through.

In the process, I discovered I totally messed up the disk config way back when (not redundant), so I'll be starting from scratch anyways...sigh...
Reply With Quote
Reply

Tags
fc6, latest, makes, nonbootable, update

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
GNOME Mplayer makes the system unresponsive... silverblackvoid Using Fedora 3 6th August 2009 03:20 PM
latest fc10 kernal update broke my system D_bot Using Fedora 6 27th May 2009 03:03 AM
System not bootable after VGA drivers (NVidia) update grezman Using Fedora 0 16th December 2008 11:55 AM
System Tray Empty After Latest Qt Update (KDE 4.1) g8keepR Using Fedora 10 27th August 2008 12:23 PM
USB Drive disconnection makes my system freeze da644 Hardware & Laptops 3 15th May 2005 07:00 PM


Current GMT-time: 06:52 (Wednesday, 22-05-2013)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat