Re: Fedora 13 installation, does not boot

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 07/18/2010 04:24 PM, Vincent Onelli wrote:
>> From: "Darr"<darr@xxxxxxxx>
>> On Saturday, 17 July, 2010 @23:56 zulu, Vincent Onelli scribed:
>>
>>> I used the rescue disk typed: chroot /mnt/sysimage
>>> then dracut -f /boot/initramfs-$(uname -r).img $(uname -r) and got the
>>> fallowing answer:
>>> find:'/lib/modules/2.6.33.3-85.fc13.i686/':no such file or directory
>>
>> Follow that same rescue procedure and after chroot, run
>> # depmod -a
>>
>> Then repeat the dracut command, i.e.
>> # dracut -f /boot/initramfs-$(uname -r).img $(uname -r)
>>
> By runing depmod -a I got the following:
> WARNING: Couldn't open directory /lib/modules/2.6.33.3-85.fc13.i686: no
> such file or directory.
> FATAL: could not
> open /lib/modules/2.6.33.3-85.fc13.i686/modules.dep.temp for writing: no
> such file or directory.
> I log in "modules" directory and found only
> "2.6.33.6-147.fc13.i686.PAE." Does this means that I need to do some
> kind of update?
>
>

Just call dracut with the correct kernel version! $(uname -r) would take the 
version of the current running kernel. It seems the rescue system is running a 
different kernel, than your system will do. So you just have to run dracut:

# export KVER=2.6.33.6-147.fc13.i686.PAE
# dracut -f /boot/initramfs-${KVER}.img $KVER
-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux