于 2013-3-11 17:31, Harald Hoyer 写道:
Am 10.03.2013 10:29, schrieb yeyouqun:
于 2013-3-8 15:02, Harald Hoyer 写道:
Am 08.03.2013 05:11, schrieb yeyouqun:
Recently I upgraded linux kernel to 3.6.10 and upgrade dracut version to 024,
system starts up OK on 3.6.10. But when I upgraded kernel from 3.6.10 to 3.8.2,
dracut failed to start up the system. Message when start up reads:
......
dracut: dracut-dracut-024-
rpcbind: cannot create socket for udp6
rpcbind: cannot create socket for tcp6
mount: unknoun filesys
udev: starting version 147
systend-udevd (139): /proc/139/oom_adj is deprecated, please use
/proc/139/oom_score_adj instead.
dracut Warning: Could not boot.
dracut Warning: Could not boot.
Dropping to debug shell.
/bin/sh: can't access tty; job control turned off
......
But when I unpack the initrd-3.8.2.img, the /lib/modules directory shows as
below:
modules ---- 3.8.2
|
|__ 3.6.10
all the kernel modules reside in "3.6.10" directory and other files, such as
"modules.dep" and etc. reside in 3.8.2, I think this is the reason why system
can't start up.
I upgraded kernel by the steps as(in kernel source tree of 3.8.2):
make
make modules_install
make install
Any one can tell how to fix this behavior of dracut?
What's the output of:
output is two big, I appende it.
# dracut --debug test.img 3.8.2
/usr/lib/dracut/dracut-functions.sh@1377(dracut_kernel_post): xargs -r modprobe
-a -d / --ignore-install --show-depends --set-version 3.8.2
/usr/lib/dracut/dracut-functions.sh@1382(dracut_kernel_post): [[ insmod = insmod ]]
/usr/lib/dracut/dracut-functions.sh@1383(dracut_kernel_post): echo
///lib/modules/3.6.10/kernel/arch/x86/crypto/crc32c-intel.ko
This looks fishy...
What is the output of:
# modprobe -a --ignore-install --show-depends --set-version 3.8.2 xor
[root@localhost mnt]# modprobe -a --ignore-install --show-depends
--set-version 3.8.2 xor
insmod /lib/modules/3.8.2/kernel/crypto/xor.ko
--
To unsubscribe from this list: send the line "unsubscribe initramfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
