After kernel upgrade "file not found"

Question

I upgraded to kernel version 3 and I rebooted but I didn't do anything in menu.lst, because I thought symlinks would work, so I rebooted but it didn't work. I tried to boot changing names in grub menu but I'm always getting same error "file not found" and I don't know what else to do. I can see the vmlinuz-linux but I can't see initramfs-linux file in /boot from a Live CD. Can you share your menu.lst to try them please.

Answer 1

tbuitenh wrote:
I ran into the same problem. I bookmarked this thread earlier, sorry if the problem has been solved in another one and I didn't notice it.
After putting back the kernel and ramdisk from a backup (using different filenames) and downgrading the kernel (mkinitcpio doesn't work, that's why I had to take the ramdisk from a backup), I was able to get back into my system.
I found a mkinitcpio.conf.pacnew, but no significant changes in there. Applied them anyway.
So let's try that again...
sudo pacman -Syu
(3/5) installing linux [######################] 100%
>>> Updating module dependencies. Please wait ...
/tmp/alpm_kwQ6VA/.INSTALL: line 10: depmod: command not found
>>> Generating initial ramdisk, using mkinitcpio. Please wait...
/tmp/alpm_kwQ6VA/.INSTALL: line 12: mkinitcpio: command not found
Optional dependencies for linux
crda: to set the correct wireless channels of your country
That doesn't look healthy. Perhaps a path problem?
[tb@progress ~]$ su -
Password:
[root@progress ~]# pacman -S linux
warning: linux-3.0.1-1 is up to date -- reinstalling
resolving dependencies...
looking for inter-conflicts...
Targets (1): linux-3.0.1-1
Total Download Size: 0.00 MB
Total Installed Size: 54.55 MB
Proceed with installation? [Y/n]
(1/1) checking package integrity [######################] 100%
(1/1) checking for file conflicts [######################] 100%
(1/1) upgrading linux [######################] 100%
>>> Updating module dependencies. Please wait ...
>>> Generating initial ramdisk, using mkinitcpio. Please wait...
==> Building image from preset: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 3.0-ARCH
-> Parsing hook: [base]
-> Parsing hook: [udev]
-> Parsing hook: [autodetect]
-> Parsing hook: [sata]
-> Parsing hook: [resume]
-> Parsing hook: [filesystems]
-> Parsing hook: [consolefont]
==> Generating module dependencies
==> Creating xz initcpio image: /boot/initramfs-linux.img
6472 blocks
==> Image generation successful
==> Building image from preset: 'fallback'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 3.0-ARCH
-> Parsing hook: [base]
-> Parsing hook: [udev]
-> Parsing hook: [sata]
-> Parsing hook: [resume]
-> Parsing hook: [filesystems]
-> Parsing hook: [consolefont]
==> Generating module dependencies
==> Creating xz initcpio image: /boot/initramfs-linux-fallback.img
13946 blocks
==> Image generation successful
[root@progress ~]# ls -l /boot
total 12484
drwxr-xr-x 2 root root 4096 Aug 15 12:18 grub
-rw-r--r-- 1 root root 5216044 Aug 15 12:41 initramfs-linux-fallback.img
-rw-r--r-- 1 root root 1460104 Aug 15 12:41 initramfs-linux.img
drwxr-xr-x 2 root root 4096 Jan 26 2011 memtest86+
-rw-r--r-- 1 root root 1453292 Jul 11 19:22 offmylawn.img
-rw-r--r-- 1 root root 2333056 Aug 6 16:22 vmlinuz-linux
-rw-r--r-- 1 root root 2305152 Jul 9 15:00 vmlinuz-offmylawn
That's better. I'll reboot now and see what happens.
@tbuitenh: I encountered this same situation today when I tried to update linux-ck-corei7 from 3.0.4-1 to 3.0.4-2. Like you, running pacman after "su -" (instead of "su") permitted me to complete the update.
I figure this has to do with default login path, right? What exactly is going on here, and how can I fix it? I don't normally run pacman this way.
Last edited by dhave (2011-09-22 23:07:53)