Fedora 13 installation, does not boot

Vincent Onelli vonelli at optonline.net
Tue Jul 20 23:48:29 UTC 2010

> From: "Darr" <darr at core.com>

> >> Hmmmm... if grub's boot menu never appears, how do you know
> >> there's only 1 kernel listed in it?
> >>
> >> If grub's boot menu never appears, how do you choose to run
> >> windows or fedora?
> >>
> > By looking in the directory /lib/modules, while I am in the command
> Just because there is only one subdirectory in /lib/modules doesn't
> mean there is (or was, now) only one kernel listed in the boot menu.
> > line in rescue mode. After reinstall again I now have in this
> > directory only if run dracut it
> > doesn't find because the PAE extension.
> So you reinstalled, but it still won't boot from the initial
> kernel that anaconda gives you. What messages do
> you see when you remove the rhgb and quiet from
> the kernel arguments at boot time?
> i.e. we don't know that the initramfs file is bad...
> that was something someone said *could* be wrong.
> Still, if you've convinced yourself that's the problem and want to
> remake that file system, just don't use the $(uname -r) variable.
> Run e.g.
> # mv /boot/initramfs- 
> /boot/initramfs-
> # dracut /boot/initramfs- 
dracut ran OK
rebooted, still no change
> instead (both of those commands should be single lines that
> begin with the root-access prompt '#'... the email programs wrap
> them at arbitrary lengths... typically between 65 and 72 characters in 
> length).
> The first command 'moves' the original file to having the
> extension "old" so you can compare it to the new one
> after it's created by the second command.
> What size is the current /boot/initramfs- 
> file, by the way? 
The new 11883506 	
The old 11883371

More information about the users mailing list