topic Re: kmod:failed to exec /sbin/modprobe in Operating System - Linux

kmod:failed to exec /sbin/modprobe

Ronald Cogen — Wed, 18 Feb 2004 05:21:20 GMT

I Have installed SuSELinux EnterpriseEdition8.
During the boot process I get the following message: kmod: failed to exec /sbin/modprobe -s -k scsl host adapter, error=2.
What does this mean? Is it dangerous?

Re: kmod:failed to exec /sbin/modprobe

Mark Grant — Wed, 18 Feb 2004 06:03:57 GMT

error 2 means that the file doesn't exist. See if you actually have a "modprobe" in /sbin.

If you don't, it means you haven't installed a package that perhaps you should have.

Re: kmod:failed to exec /sbin/modprobe

Stuart Browne — Wed, 18 Feb 2004 18:47:18 GMT

Does this system use an 'initrd' boot process?

If it does, it might be that it's missing in there.

It's also possible that the modules 'scsi host adapter' is missing (are you sure there's spaces, and not _'s?). Check for references in '/etc/modules.conf' for this.

Re: kmod:failed to exec /sbin/modprobe

Martin P.J. Zinser — Wed, 18 Feb 2004 22:53:41 GMT

Just checked my SuSE system. modprobe does live in /sbin, so either the installation is broken or the module that it tries to insert has not been installed. -s means reporting to syslog -k is a mode used by the kernel. So the real interesting part would be the next and that looks garbled in your post ;-) Try to get a good error please.

Greetings, Martin

Re: kmod:failed to exec /sbin/modprobe

Ronald Cogen — Thu, 19 Feb 2004 03:24:39 GMT

Thank you Mark and STuart, I'll look into that as soon as I'm at that site.

Martin: I'm not sure about what you meant by 'garbled'. I'm pretty sure I wrote the error message down the way it came. If you have a moment, could you fill me in?