-- Le (On) 2013-10-01 -0700 à (at) 13:04:24 Akemi Yagi écrivit (wrote): --
> On Tue, Oct 1, 2013 at 10:00 AM, Franchisseur Robert > <rob...@franchisseur.fr> wrote: > > Hello, > > <snip> Hello Akemi and Steven, and thanks for your fast answer. > > What kernel module(s) is your dkms supposed to build? This may depend > on what they are for but try renaming the initrd file by removing the > .dup_orig and see if that allows the system to boot. > The modules are for my graphic card and wireless broadcom-wl nvidia.ko wl.ko I could not boot with those .dup_orig initrd files as Steven assume. As I have colleague with the same laptop (Dell latitude E6500) with the same system I copy his initrd-2.6.18-348.12.1.el5.img with a live USB and I could boot. > An attempt to rebuild initrd will probably reveal what went wrong. > /sbin/weak-modules created those .dup_orig files. I suspect the > problem is related to the module(s) built by dkms. > Then I ran : [root@demeol ~]# /sbin/new-kernel-pkg -v --package kernel --mkinitrd --depmod --install 2.6.18-348.18.1.el5 and everything was OK. initrdfile is /boot/initrd-2.6.18-348.18.1.el5.img making it the default based on config running depmod for 2.6.18-348.18.1.el5 creating initrd /boot/initrd-2.6.18-348.18.1.el5.img using 2.6.18-348.18.1.el5 found /boot/initrd-2.6.18-348.18.1.el5.img and using it with grubby adding 2.6.18-348.18.1.el5 to /boot/grub/grub.conf /etc/lilo.conf does not exist, not running grubby Then I did : [root@demeol ~]# /sbin/weak-modules --verbose --dry-run --add-kernel 2.6.18-348.18.1.el5 [root@demeol ~]# /sbin/weak-modules --verbose --add-kernel 2.6.18-348.18.1.el5 which did nothing /lib/modules/2.6.18-348.18.1.el5/weak-updates/ # is empty [root@demeol ~]# dkms autoinstall --verbose --kernelver 2.6.18-348.18.1.el5 did nothing either as the modules were already there and OK #### demeol:/home/bob/PB_boot_demeo > ll /lib/modules/2.6.18-348.18.1.el5/kernel/drivers/video/nvidia/ -rw-r--r-- 1 root root 17049680 Sat Sep 28 18:13:22 2013 nvidia.ko -rwxr--r-- 1 root root 91696 Thu Sep 26 19:21:11 2013 nvidiafb.ko #### demeol:/home/bob/PB_boot_demeo > ll /lib/modules/2.6.18-348.18.1.el5/kernel/drivers/net/wireless/ ... -rw-r--r-- 1 root root 2450160 Sat Sep 28 18:13:13 2013 wl.ko ... To summarize : ============ yum update kernel Sep 28 04:04:52 # OK reboot Sep 28 18:12 dkms_autoinstaller # build the modules correctly # but destoy all initrd files and grub.conf next reboot ==> kernel panic Trying to see the content of the dup_orig initrd files, I also notice that : gunzip: /boot/initrd-2.6.18-348.18.1.el5.img.dup_orig: decompression OK, trailing garbage ignored I already had this problem on my desktop with dkms modules nvidia and virtualbox. the kernel has also been updated on Sep 28 but I did not reboot it yet. I notice I have 2 dup_orig files -rw------- 1 root root 2731227 Fri Aug 23 18:34:23 2013 /boot/initrd-2.6.18-348.12.1.el5.img.dup_orig -rw------- 1 root root 2731102 Mon Aug 19 19:38:30 2013 /boot/initrd-2.6.18-348.6.1.el5.img.dup_orig and gunzip -c /boot/initrd-2.6.18-348.12.1.el5.img.dup_orig |cpio -idmv gives error : cpio: warning: skipped 408 bytes of junk gunzip: /boot/initrd-2.6.18-348.12.1.el5.img.dup_orig: invalid compressed data--crc error gunzip: /boot/initrd-2.6.18-348.12.1.el5.img.dup_orig: invalid compressed data--length error gunzip -c /boot/initrd-2.6.18-348.6.1.el5.img.dup_orig |cpio -idmv is OK !!! I will reboot this laptop tomorrow and tell you. I wonder why /sbin/weak-modules touch the old kernel and can make the machine unbootable ? What is strange is that my colleagues with the same hardware, same kickstart and same post_install don't have this problem. -- Le (On) 2013-10-01 -0700 à (at) 13:27:45 Steven J. Yellin écrivit (wrote): -- > You said initrd lines were erased in grub.conf and the initrd* files > in /boot/grub were renamed. That's weird! I assume you have already > tried editing grub.conf to adapt it to the renamed initrd files, and since > you didn't say so, I assume that vmlinuz-2.6.18-348.18.1.el5 was not > renamed. If I'm mistaken, grub.conf should be edited accordingly, or the > files should be renamed back so as to be consistent with grub.conf. > I've no experience with a problem like yours, so I'll just guess that > something interfered with installation of the kernel rpm at an especially > bad step in the process. Check with rpm (within chroot to your normal > root file system from, say, a Live USB) that it thinks > kernel-2.6.18-348.18.1.el5.x86_64 is installed. Verify that there's a > directory /lib/modules/2.6.18-348.18.1.el5 with over 100 MB in it, and > that in addition to the strangely renamed initrd file, /boot has files > config-2.6.18-348.18.1.el5, symvers-2.6.18-348.18.1.el5.gz, > System.map-2.6.18-348.18.1.el5, and vmlinuz-2.6.18-348.18.1.el5. If the > latest SL5 kernel rpm is not installed, or even if it already is, you > could try installing or reinstalling it or an older one. > > Steven Yellin > > On Tue, 1 Oct 2013, Franchisseur Robert wrote: > > >Hello, > > > >after kernel update I almost have trouble caused by dkms (I think > >it is since the last mkinird package). > > > >After the update when rebooting there were many error messages > >but I can boot. > > > >But at next reboot I got a kernel panic. > >Kernel panic - not sncing VFS : Unable to mount root fs on > >unknown-block(0,0) > > > > > >This is often due to the fact that the file grub.conf has been > >erased, so it is easy to repair whith a Live USB, but this time it > >was because all the lines > > > > initrd /initrd-2.6.18-x.y.z.el5.img > > > >have been erased in grub.conf > > > >and all the > > > >initrd-2.6.18-x.y.z.el5.img > > > >were renamed > > > >initrd-2.6.18-x.y.z.el5.img.dup_orig > > > > > >Is it possible to do an mkinitrd from a live rescue USB disk as > >I cannot boot with any of my 4 previous initrd files : > > > >initrd-2.6.18-348.6.1.el5.img.dup_orig > >initrd-2.6.18-348.12.1.el5.img.dup_orig > >initrd-2.6.18-348.16.1.el5.img.dup_orig > >initrd-2.6.18-348.18.1.el5.img.dup_orig > > > >Thanks for your help. > > -- Best regards, Robert FRANCHISSEUR ____ Apollo_gist :-)_______________________________________________ | Robert FRANCHISSEUR Phone : +33 (0)950 635 636 | | 30 rue René Hamon Phone : +33 (0)1 46 78 37 29 | | F-94800 VILLEJUIF e-mail : Robert at Franchisseur . fr | -------------------------------------------------------------------