On Thu, 2008-01-24 at 23:57 -0500, Kevin J. Cummings wrote:
> Teo Fonrouge wrote:
> > On Thursday 24 January 2008 07:47:10 pm Kevin J. Cummings wrote:
> >> Is anyone else seeing this:
> >>> Installing: kernel #########################
> >>> [1/4] /sbin/mkinitrd: line 186: 12264 Segmentation fault $ldso
> >>> --verify $bin > /dev/null 2>&1
> >> It happens when I try and install the new kernel-2.6.23.14-107.fc8.i686
> >
> > I have just installed the same kernel version without problems.
> >
> > It's possible that mkinitrd is having trouble building the initial image
> > needed by the new kernel with your specific hardware configuration.
>
> Nope.
>
> mkinitrd has the following function in it:
>
> > get_dso_deps() {
> > bin="$1" ; shift
> > DSO_DEPS=""
> >
> > declare -a FILES
> > declare -a NAMES
> >
> > # this is a hack, but the only better way requires binutils or elfutils
> > # be installed. i.e., we need readelf to find the interpretter.
> > if [ -z "$LDSO" ]; then
> > for ldso in /lib*/ld*.so* ; do
> > [ -L $ldso ] && continue
> > [ -x $ldso ] || continue
> > $ldso --verify $bin >/dev/null 2>&1 || continue
> > LDSO="$ldso"
> > done
> > fi
>
> The line that fails is $ldso --verify $bin > /dev/null 2>&1 || continue
>
> While invoking one of the files that match /lib*/ld*.so* the sigsegv
> occurs. The comments claim that this is a hack. I think a better hack
> is needed....
>
> My list of files that match:
>
> > -rwxr-xr-x 1 root root 128952 2007-10-18 04:49 /lib/ld-2.7.so
> > lrwxrwxrwx 1 root root 17 2006-10-31 23:41 /lib/ld-linux.so.1 -> ld-linux.so.1.9.5
> > -rwxr-xr-x 1 root root 25386 2000-02-03 09:14 /lib/ld-linux.so.1.9.5
> > lrwxrwxrwx 1 root root 9 2007-11-09 19:36 /lib/ld-linux.so.2 -> ld-2.7.so
> > lrwxrwxrwx 1 root root 13 2006-09-14 16:09 /lib/ld-lsb.so -> ld-linux.so.2
> > lrwxrwxrwx 1 root root 13 2007-11-13 18:41 /lib/ld-lsb.so.3 -> ld-linux.so.2
> > -rwxr-xr-x 2 root root 99660 2000-02-03 09:14 /lib/ld.so
> > -rwxr-xr-x 2 root root 99660 2000-02-03 09:14 /lib/ld.so.1.9.5
>
> I think that mkinitrd is at fault, not the kernel.
>
> > You can try downloading the new rpm kernel and then install it without
> > executing the POSTIN script:
> >
> > #rpm -Uvh --nopost kernel-2.6.23.14-107.fc8.i686.rpm
> >
> > and then run the mkinitrd manually with verbose param to try to get more info
> > for the error:
> >
> > #mkinitrd -v -k /boot/vmlinuz-2.6.23.14-107.fc8 -i /boot/initrd-2.6.23.14-107.fc8
> >
> > Of course, if the above has success, then you need to modify too your
> > grub.conf file in order to reboot with the new kernel.
>
> See above, we already know what is failing. The question is *why* is it
> failing?
>
> > I have not tried the above procedure, but feel free to give it a try if you
> > wish :)
>
> Thanks for answering.
----
try running mkinitrd for an existing kernel, not the new kernel.
i.e. (I'm on my F7 system so you'll have to adjust)
mkinitrd -v initrd-2.6.23.12-52.test 2.6.23.12-52.fc7
does mkinitrd work for an existing kernel?
Craig
