Fedora 13 installation, does not boot
darr at core.com
Tue Jul 20 22:25:03 UTC 2010
On Tuesday, 20 July, 2010 @17:22 zulu, Vincent Onelli scribed:
>> 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 18.104.22.168-85.fc13.i.686.PAE 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.
# mv /boot/initramfs-22.214.171.124-85.fc13.i.686.PAE.img
# dracut /boot/initramfs-126.96.36.199-85.fc13.i.686.PAE.img
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
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-188.8.131.52-85.fc13.i.686.PAE.img
file, by the way?
More information about the users