"Thomas Backlund" <[EMAIL PROTECTED]> writes: > I checked out the kernel mailing list and found the reason for the > 'kmod: failed to exec /sbin/modprobe -s -k ... ' > > It seems that kmod is not perfectly happy with the module-loading, > initrd, and ramfs..., and modprobe is not in the initrd, > so the line above is it's way of complaining...
Yes. We always had this problem, it's why in our initrd the "nash" program has a softlink from "/sbin/modprobe"; and "nash" itself silently "exit 0" when it sees that it has been called with the name "modprobe". This has always worked in the past. Now at a certain point between the 8.2 kernel and now, it broke. I've spent a bunch of time experimenting, trying to use absolute or relative symlink, trying to have an hardlink, but no way. I've read the kernel source in the hope that I could understand, but nothing. So I've passed the request to our kernel team (around one month ago). I'm skeptical it will be fixed at all for 9.0. -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
