[udev] load-modules.sh error when plugging in camera

Meson · 05-24-2010, 11:03 PM

When I plug in my camera via usb I see this error

Code:

load-modules.sh: 'usb:v22B8p2B44d0001dcFFdscFFdp00icFFiscFFipFF' is not a valid module or alias name

This is happening on multiple machines. My udev version is 153. I don't think this is a permissioning issue because I've tried playing around with the udev rules/

JZL240I-U · 05-31-2010, 01:15 AM

Yes. It rather looks like you misplaced a UUID (e.g. disk denominator) somewhere in your rules -- but not necessarily in udev as your error messages states: "load-modules.sh: [...] is not a valid module or alias name". What did you do to your (kernel)-modules loading scheme

?

Meson · 06-01-2010, 11:14 AM

Apparently it's this rule:

Code:

DRIVER!="?*", ENV{MODALIAS}=="?*", RUN+="/lib/udev/load-modules.sh $env{MODALIAS}"

which I think comes from udev itself (rather than my distribution). load-modules.sh is provided by Arch.

Looking through my logs, there are a lot of similar errors which seem to be harmless. However, this particular device is not recognized by my system. Maybe there is another error somewhere and this is just a Red Herring.

catkin · 06-01-2010, 11:32 AM

Quote:

Originally Posted by Meson

Apparently it's this rule:

Code:

DRIVER!="?*", ENV{MODALIAS}=="?*", RUN+="/lib/udev/load-modules.sh $env{MODALIAS}"

The equivalent on Slackware 13.0 is in /lib/udev/rules.d/80-drivers.rules:

Code:

DRIVER!="?*", ENV{MODALIAS}=="?*", RUN{ignore_error}+="/sbin/modprobe -b $env{MODALIAS}"

Perhaps the difference is a fix.

Meson · 06-02-2010, 09:17 PM

I tried it, doesn't help. That error message is no longer there, but the camera still doesn't show up (in lsusb for example). I tried removing that ignore_error bit to see if I'd get more output, but nothing new showed up.

catkin · 06-03-2010, 04:55 AM

To get a bit more information you could replace the rule with

Code:

DRIVER!="?*", ENV{MODALIAS}=="?*", RUN+="/<full_path_to>/myscript.sh $env{MODALIAS} $%k %m <and all the other printf-like string substitutions listed in the udev man page>"

and write myscript.sh so that it writes its command line to a log file. Then post the log file.