Description of problem: I'm using this machine: <<< My primary machine is a desktop machine with a: Pentium 4, 2.4 GHz CPU. 2.5 GB of RAM. An ATI Radeon HD 2600 card. One 160 GB Hard-disk and two smaller ones of 80 GB or so. A 19×´ LCD Screen by ViewSonic. A standard built-in ACâ97 sound-card. >>> When I boot it from grub2 and using kernel-3.0.0 as installed from my Debian partition I'm getting "Cannot handle kernel" and the system freezes. I think I see the Init process starting there. Kernel "3.0.0-desktop586-0.rc7.2.1.mga2" boots fine. My /boot directory is as follows: <<<<< shlomif:~$ ls -l /boot/ total 22292 -rw-r--r-- 1 root root 440 Jun 28 05:48 boot.backup.sda lrwxrwxrwx 1 root root 38 Jul 23 12:39 config -> config-3.0.0-desktop586-0.rc7.2.1.mga2 -rw-r--r-- 1 root root 131629 Jul 15 19:20 config-3.0.0-desktop586-0.rc7.2.1.mga2 -rw-r--r-- 1 root root 131632 Jul 22 13:15 config-3.0.0-desktop586-1.mga2 -rwxr-xr-x 1 root root 535552 Jul 19 17:34 gfxmenu drwxr-xr-x 2 root root 4096 Jul 23 02:29 grub -rw------- 1 root root 4289053 Jun 28 20:23 initrd-2.6.38.8-desktop586-2.mga2.img-bak -rw------- 1 root root 4522829 Jul 19 17:35 initrd-3.0.0-desktop586-0.rc7.2.1.mga2.img -rw------- 1 root root 4335871 Jul 23 02:29 initrd-3.0.0-desktop586-1.mga2.img lrwxrwxrwx 1 root root 34 Jul 23 02:29 initrd-desktop586.img -> initrd-3.0.0-desktop586-1.mga2.img lrwxrwxrwx 1 root root 34 Jul 23 02:29 initrd.img -> initrd-3.0.0-desktop586-1.mga2.img -rw-r--r-- 1 root root 209298 Jul 15 19:20 symvers-3.0.0-desktop586-0.rc7.2.1.mga2.gz -rw-r--r-- 1 root root 209290 Jul 22 13:15 symvers-3.0.0-desktop586-1.mga2.gz lrwxrwxrwx 1 root root 42 Jul 16 15:08 System.map -> System.map-3.0.0-desktop586-0.rc7.2.1.mga2 -rw-r--r-- 1 root root 1617170 Jul 15 19:20 System.map-3.0.0-desktop586-0.rc7.2.1.mga2 -rw-r--r-- 1 root root 1617341 Jul 22 13:15 System.map-3.0.0-desktop586-1.mga2 lrwxrwxrwx 1 root root 31 Jul 23 02:29 vmlinuz -> vmlinuz-3.0.0-desktop586-1.mga2 -rw-r--r-- 1 root root 2558960 Jul 15 19:20 vmlinuz-3.0.0-desktop586-0.rc7.2.1.mga2 -rw-r--r-- 1 root root 2559664 Jul 22 13:15 vmlinuz-3.0.0-desktop586-1.mga2 lrwxrwxrwx 1 root root 31 Jul 23 02:29 vmlinuz-desktop586 -> vmlinuz-3.0.0-desktop586-1.mga2 >>>>> And the grub 2 definitions are: <<<<<<<<<<<<<<< menuentry "mageia1" { insmod part_msdos insmod ext2 set root=(hd2,msdos1) search --no-floppy --fs-uuid --set=root c6376f86-cd7d-4aa6-9e0f-80c19fa11178 linux /boot/vmlinuz root=UUID=c6376f86-cd7d-4aa6-9e0f-80c19fa11178 radeon.agpmode=-1 radeon.modeset=1 initrd /boot/initrd.img } menuentry "mageia1 nofb" { insmod part_msdos insmod ext2 set root=(hd2,msdos1) search --no-floppy --fs-uuid --set=root c6376f86-cd7d-4aa6-9e0f-80c19fa11178 linux /boot/vmlinuz root=UUID=c6376f86-cd7d-4aa6-9e0f-80c19fa11178 vga=normal nofb radeon.agpmode=-1 radeon.modeset=1 initrd /boot/initrd.img } menuentry "mageia1-old" { insmod part_msdos insmod ext2 set root=(hd2,msdos1) search --no-floppy --fs-uuid --set=root c6376f86-cd7d-4aa6-9e0f-80c19fa11178 linux /boot/vmlinuz-3.0.0-desktop586-0.rc7.2.1.mga2 root=UUID=c6376f86-cd7d-4aa6-9e0f-80c19fa11178 radeon.agpmode=-1 radeon.modeset=1 initrd /boot/initrd-3.0.0-desktop586-0.rc7.2.1.mga2.img } >>>>>>>>>>>>>>>>>>
Hi all, today urpmi gave me: <<<<< The following packages: kernel-desktop586-devel-3.0.0-0.rc7.2.1.mga2-1-1.mga2.i586 libboost_program_options1.46.1-1.46.1-1.mga2.i586 libcamel23-3.0.2.1-1.mga2.i586 libcamel27-3.1.3-3.mga2.i586 libcogl1-1.7.2-5.mga2.i586 libebook10-3.0.2.1-1.mga2.i586 libgck0-3.1.1-4.mga2.i586 libgcr-3_1-3.1.1-4.mga2.i586 liblzo-devel-2.04-3.mga1.i586 libnet-snmp25-5.6.1-9.mga2.i586 perl-Test-Exception-0.310.0-2.mga1.noarch are now orphaned, if you wish to remove them, you can use "urpme --auto-orphans" >>>>> As one can see it asks me to remove the previous kernel, but I would rather not because it's the only kernel I can use to boot the system. Can anyone look into this bug and help me?
OK, I solved this problem by running as root: # mkinitrd -f /boot/initrd-3.0.0-desktop586-1.mga2.img 3.0.0-desktop586-1.mga2 I don't know why the rpm mkinitrd failed. I'm resolving this bug, but next time, please try to be more responsive.
Status: NEW => RESOLVEDResolution: (none) => FIXED