On Sat, Sep 13, 2008 at 9:27 AM, Andy Walls <[EMAIL PROTECTED]> wrote:
> On Sat, 2008-09-13 at 00:13 -0400, Rob Rosenfeld wrote:
>> I have a system with a PVR-150 in it and I recently had to replace the
>> hard drive and reinstall OS and apps from scratch. Now that I'm done,
>> I'm having problems with the PVR-150 card. The three "failed to load"
>> modules listed below are built and can be modprobe'd individually.
>
> OK. ivtv calls
>
> kernel/kmod.c:request_module()
>
> Here's some interesting comments around that function:
>
> /*
> modprobe_path is set via /proc/sys.
> */
> char modprobe_path[KMOD_PATH_LEN] = "/sbin/modprobe";
>
> /**
> * request_module - try to load a kernel module
> ...
> * Load a module using the user mode module loader. The function returns
> * zero on success or a negative errno code on failure.
> ...
> * If module auto-loading support is disabled then this function
> * becomes a no-operation.
> */
> int request_module(const char *fmt, ...)
> {
> ...
> char *argv[] = { modprobe_path, "-q", "--", module_name, NULL };
> static char *envp[] = { "HOME=/",
> "TERM=linux",
> "PATH=/sbin:/usr/sbin:/bin:/usr/bin",
> NULL };
>
>
> Check to make sure that you don't have a path problem or some sort of
> userland problem with modprobe or it's configuration or auto-loading of
> modules.
Bingo! CONFIG_KMOD was not set. Thanks so much for such a clear explanation.
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
