Good day, I'm getting an error every time I plug-in my webcam as a result the corresponding module is not being loaded automatically so I have to load it by myself. Any one knows a way to fix this? This is the error: load-modules.sh: 'usb:v0AC8p305Bd0100dcFFdsc00dp00icFFiscFFipFF' is not a valid module or alias name Thanks
On Tue, 2010-06-08 at 15:16 +0900, Juan Diego Tascón wrote:
Good day,
I'm getting an error every time I plug-in my webcam as a result the corresponding module is not being loaded automatically so I have to load it by myself. Any one knows a way to fix this?
This is the error:
load-modules.sh: 'usb:v0AC8p305Bd0100dcFFdsc00dp00icFFiscFFipFF' is not a valid module or alias name
There's no kernel module for your webcam installed. You'll have to find out what driver it uses and udev will load the driver when you hotplug your webcam. All modules have device aliases for the devices it supports. Udev just tries to load a module by devicename and gives your error if it can't succeed.
On Tue, Jun 8, 2010 at 3:41 PM, Jan de Groot <jan@jgc.homeip.net> wrote:
On Tue, 2010-06-08 at 15:16 +0900, Juan Diego Tascón wrote:
Good day,
I'm getting an error every time I plug-in my webcam as a result the corresponding module is not being loaded automatically so I have to load it by myself. Any one knows a way to fix this?
This is the error:
load-modules.sh: 'usb:v0AC8p305Bd0100dcFFdsc00dp00icFFiscFFipFF' is not a valid module or alias name
There's no kernel module for your webcam installed. You'll have to find out what driver it uses and udev will load the driver when you hotplug your webcam.
Actually it is installed, it is called gspca_zc3xx, if I load it the webcam works, the thing is it is not being loaded automatically
All modules have device aliases for the devices it supports. Udev just tries to load a module by devicename and gives your error if it can't succeed.
Should I report this to the udev developers?
On Tue, 2010-06-08 at 15:49 +0900, Juan Diego Tascón wrote:
Actually it is installed, it is called gspca_zc3xx, if I load it the webcam works, the thing is it is not being loaded automatically
All modules have device aliases for the devices it supports. Udev just tries to load a module by devicename and gives your error if it can't succeed.
Should I report this to the udev developers?
When I run "modinfo gspca_zc3xx", I get an alias for your device (usb:v0AC8p305Bd*dc*dsc*dp*ic*isc*ip* matches). This is with kernel 2.6.34 from testing. What kernel do you use? Older versions might not have the device alias assigned to the module.
On Tue, Jun 8, 2010 at 3:55 PM, Jan de Groot <jan@jgc.homeip.net> wrote:
On Tue, 2010-06-08 at 15:49 +0900, Juan Diego Tascón wrote:
Actually it is installed, it is called gspca_zc3xx, if I load it the webcam works, the thing is it is not being loaded automatically
All modules have device aliases for the devices it supports. Udev just tries to load a module by devicename and gives your error if it can't succeed.
Should I report this to the udev developers?
When I run "modinfo gspca_zc3xx", I get an alias for your device (usb:v0AC8p305Bd*dc*dsc*dp*ic*isc*ip* matches). This is with kernel 2.6.34 from testing. What kernel do you use? Older versions might not have the device alias assigned to the module.
I just updated my kernel to the testing version that you mentioned but I am still getting the same message. Do you know where these rules are stored?
On Tue, 8 Jun 2010 18:55:33 +0900 Juan Diego Tascón <juantascon@gmail.com> wrote:
On Tue, Jun 8, 2010 at 3:55 PM, Jan de Groot <jan@jgc.homeip.net> wrote:
On Tue, 2010-06-08 at 15:49 +0900, Juan Diego Tascón wrote:
Actually it is installed, it is called gspca_zc3xx, if I load it the webcam works, the thing is it is not being loaded automatically
All modules have device aliases for the devices it supports. Udev just tries to load a module by devicename and gives your error if it can't succeed.
Should I report this to the udev developers?
When I run "modinfo gspca_zc3xx", I get an alias for your device (usb:v0AC8p305Bd*dc*dsc*dp*ic*isc*ip* matches). This is with kernel 2.6.34 from testing. What kernel do you use? Older versions might not have the device alias assigned to the module.
I just updated my kernel to the testing version that you mentioned but I am still getting the same message. Do you know where these rules are stored?
The aliases are generated from device and id lists in the relevant source file during the kernel build process. in your case that would be: {USB_DEVICE(0x0ac8, 0x305b), DVNM("Z-star Vimicro zc0305b")}, in drivers/media/video/gspca/zc3xx.c That id is in that file since it's creation somewhere between 2.6.26 and 2.6.27_r1. Are you sure, you have a recent udev and it's properly configured? --
On Tue, Jun 8, 2010 at 7:16 PM, Alexander Duscheleit <jinks@archlinux.us> wrote:
On Tue, 8 Jun 2010 18:55:33 +0900 Juan Diego Tascón <juantascon@gmail.com> wrote:
On Tue, Jun 8, 2010 at 3:55 PM, Jan de Groot <jan@jgc.homeip.net> wrote:
On Tue, 2010-06-08 at 15:49 +0900, Juan Diego Tascón wrote:
Actually it is installed, it is called gspca_zc3xx, if I load it the webcam works, the thing is it is not being loaded automatically
All modules have device aliases for the devices it supports. Udev just tries to load a module by devicename and gives your error if it can't succeed.
Should I report this to the udev developers?
When I run "modinfo gspca_zc3xx", I get an alias for your device (usb:v0AC8p305Bd*dc*dsc*dp*ic*isc*ip* matches). This is with kernel 2.6.34 from testing. What kernel do you use? Older versions might not have the device alias assigned to the module.
Ive tried the kernel 2.6.34 and I get the same result, the thing is that I remember it used to work well, and suddenly in a kernel update (not sure which one) it stop working
I just updated my kernel to the testing version that you mentioned but I am still getting the same message. Do you know where these rules are stored?
The aliases are generated from device and id lists in the relevant source file during the kernel build process.
in your case that would be: {USB_DEVICE(0x0ac8, 0x305b), DVNM("Z-star Vimicro zc0305b")}, in drivers/media/video/gspca/zc3xx.c
That id is in that file since it's creation somewhere between 2.6.26 and 2.6.27_r1.
Are you sure, you have a recent udev and it's properly configured?
well I haven't changed anything in udev configuration, I've tried reinstalling udev but still the same error
--
2010/6/8 Juan Diego Tascón <juantascon@gmail.com>:
On Tue, Jun 8, 2010 at 3:41 PM, Jan de Groot <jan@jgc.homeip.net> wrote:
On Tue, 2010-06-08 at 15:16 +0900, Juan Diego Tascón wrote:
Good day,
I'm getting an error every time I plug-in my webcam as a result the corresponding module is not being loaded automatically so I have to load it by myself. Any one knows a way to fix this?
This is the error:
load-modules.sh: 'usb:v0AC8p305Bd0100dcFFdsc00dp00icFFiscFFipFF' is not a valid module or alias name
There's no kernel module for your webcam installed. You'll have to find out what driver it uses and udev will load the driver when you hotplug your webcam.
Actually it is installed, it is called gspca_zc3xx, if I load it the webcam works, the thing is it is not being loaded automatically
All modules have device aliases for the devices it supports. Udev just tries to load a module by devicename and gives your error if it can't succeed.
Should I report this to the udev developers?
adding the module name to modules part of /etc/rc.conf might help. it will be loaded automatically then.
On 06/08/2010 02:41 AM, Jan de Groot wrote:
On Tue, 2010-06-08 at 15:16 +0900, Juan Diego Tascón wrote:
Good day,
I'm getting an error every time I plug-in my webcam as a result the corresponding module is not being loaded automatically so I have to load it by myself. Any one knows a way to fix this?
This is the error:
load-modules.sh: 'usb:v0AC8p305Bd0100dcFFdsc00dp00icFFiscFFipFF' is not a valid module or alias name
There's no kernel module for your webcam installed. You'll have to find out what driver it uses and udev will load the driver when you hotplug your webcam. All modules have device aliases for the devices it supports. Udev just tries to load a module by devicename and gives your error if it can't succeed.
I've been having these problems with my webcam (which as a built-in mic) and my digital camera. What has changed that makes these issues happen all of the sudden? Also, does anyone know of a good site to lookup drivers for these devices?
Am 09.06.2010 02:38, schrieb Matthew Monaco:
On 06/08/2010 02:41 AM, Jan de Groot wrote:
On Tue, 2010-06-08 at 15:16 +0900, Juan Diego Tascón wrote:
Good day,
I'm getting an error every time I plug-in my webcam as a result the corresponding module is not being loaded automatically so I have to load it by myself. Any one knows a way to fix this?
This is the error:
load-modules.sh: 'usb:v0AC8p305Bd0100dcFFdsc00dp00icFFiscFFipFF' is not a valid module or alias name
There's no kernel module for your webcam installed. You'll have to find out what driver it uses and udev will load the driver when you hotplug your webcam. All modules have device aliases for the devices it supports. Udev just tries to load a module by devicename and gives your error if it can't succeed.
I've been having these problems with my webcam (which as a built-in mic) and my digital camera. What has changed that makes these issues happen all of the sudden? Also, does anyone know of a good site to lookup drivers for these devices?
In the above case, you would run: modprobe --resolve-alias usb:v0AC8p305Bd0100dcFFdsc00dp00icFFiscFFipFF
On Wed, Jun 9, 2010 at 4:17 PM, Thomas Bächler <thomas@archlinux.org> wrote:
Am 09.06.2010 02:38, schrieb Matthew Monaco:
On 06/08/2010 02:41 AM, Jan de Groot wrote:
On Tue, 2010-06-08 at 15:16 +0900, Juan Diego Tascón wrote:
Good day,
I'm getting an error every time I plug-in my webcam as a result the corresponding module is not being loaded automatically so I have to load it by myself. Any one knows a way to fix this?
This is the error:
load-modules.sh: 'usb:v0AC8p305Bd0100dcFFdsc00dp00icFFiscFFipFF' is not a valid module or alias name
There's no kernel module for your webcam installed. You'll have to find out what driver it uses and udev will load the driver when you hotplug your webcam. All modules have device aliases for the devices it supports. Udev just tries to load a module by devicename and gives your error if it can't succeed.
I've been having these problems with my webcam (which as a built-in mic) and my digital camera. What has changed that makes these issues happen all of the sudden? Also, does anyone know of a good site to lookup drivers for these devices?
In the above case, you would run: modprobe --resolve-alias usb:v0AC8p305Bd0100dcFFdsc00dp00icFFiscFFipFF
I ran that and it didn't return anything, are these ids stored inside the modules (*.ko)?
On Wed, Jun 9, 2010 at 11:18 PM, Thomas Bächler <thomas@archlinux.org> wrote:
Am 09.06.2010 15:11, schrieb Juan Diego Tascón:
In the above case, you would run: modprobe --resolve-alias usb:v0AC8p305Bd0100dcFFdsc00dp00icFFiscFFipFF
I ran that and it didn't return anything, are these ids stored inside the modules (*.ko)?
Yes, visible with modinfo.
ok, I ran: modinfo gspca_zc3xx and I got this line among a lot more: alias: usb:v0AC8p305Bd*dc*dsc*dp*ic*isc*ip* which obviously matches with mine: usb:v0AC8p305Bd0100dcFFdsc00dp00icFFiscFFipFF however when I run modprobe --resolve-alias v0AC8p305Bd0100dcFFdsc00dp00icFFiscFFipFF or modprobe --resolve-alias usb:v0AC8p305Bd0100dcFFdsc00dp00icFFiscFFipFF it shows nothing. any suggestions? should I report this? who should I report this to?
Am 09.06.2010 16:45, schrieb Juan Diego Tascón:
modinfo gspca_zc3xx
and I got this line among a lot more:
alias: usb:v0AC8p305Bd*dc*dsc*dp*ic*isc*ip*
which obviously matches with mine:
usb:v0AC8p305Bd0100dcFFdsc00dp00icFFiscFFipFF
however when I run
modprobe --resolve-alias v0AC8p305Bd0100dcFFdsc00dp00icFFiscFFipFF
This is wrong.
or
modprobe --resolve-alias usb:v0AC8p305Bd0100dcFFdsc00dp00icFFiscFFipFF
This is correct.
it shows nothing.
any suggestions? should I report this? who should I report this to?
These matches are done in modprobe using the standard C function fnmatch IIRC. This looks like a bug in glibc, I'll have to verify this later.
Am 09.06.2010 16:45, schrieb Juan Diego Tascón:
modprobe --resolve-alias usb:v0AC8p305Bd0100dcFFdsc00dp00icFFiscFFipFF
it shows nothing.
This works for me on 2.6.34-ARCH. Maybe something went wrong during depmod. See if the problem persists if you run 'depmod' as root.
participants (6)
-
Alexander Duscheleit
-
Jan de Groot
-
Juan Diego Tascón
-
Madhurya Kakati
-
Matthew Monaco
-
Thomas Bächler