Bob Lockie wrote:
I did something to break it (maybe installing a new kernel).
What's "it"? :-)
2.4.20-ac2 kernel.
Did you run "make oldconfig" after copying your config into that kernel?
Some config options may have changed.
# insmod videodev
Using /lib/modules/2.4.20-ac2/kernel/drivers/media/video/videodev.o
# insmod ov511
Using /lib/modules/2.4.20-ac2/kernel/drivers/usb/ov511.o
# dmesg
Linux video capture interface: v1.00
usb.c: registered new driver ov511
ov511.c: USB OV511+ video device found
ov511.c: model: Creative Labs WebCam 3
ov511.c: Sensor is an OV7620
ov511.c: Device at usb-00:02.2-3 registered to minor 0
usb.c: ov511 driver claimed interface d7e351c0
ov511.c: v1.64 : ov511 USB Camera Driver
Looks OK so far, unless you were trying to insmod the driver from the
current directory. You must include the ".o" extension, otherwise,
insmod will load it from /lib/modules/ (as you can see above).
What version of the kernel do you use with the ov511-2.21 driver?
2.4.20, although I don't think there are any changes in 2.4.20-ac2 that
would break it. It's possible though.
What happens when you try to compile/install/load/use it?
# more /proc/bus/usb/drivers
usbdevfs
hub
usb-storage
ov51
# ll /proc/bus/usb/devices
-r--r--r-- 1 root root 0 Feb 18 11:06
/proc/bus/usb/devices
I don't think that is supposed to be empty.
It always shows up that way (since it's not a "real" file). What happens
when you try to cat it?
# ll /proc/bus
total 0
-r--r--r-- 1 root root 0 Feb 18 16:23 i2c
dr-xr-xr-x 4 root root 0 Feb 18 16:23 pci
dr-xr-xr-x 1 root root 0 Feb 18 11:06 usb
The time for /proc/bus was not updated, shouldn't it be?
Nope. It only changes when usbdevfs is mounted/unmounted.
# ll /dev/video
lr-xr-xr-x 1 root root 11 Feb 18 11:05 /dev/video ->
/dev/video0
# ll /dev/video0
crw-r--r-- 1 root sys 81, 0 Feb 18 11:05 /dev/video0
These have old dates too.
Unless you are using devfs (not to be confused with usbdevfs), that's
normal. Apparently that file got created at bootup. It shouldn't matter
either way though.
--
Mark McClelland
mark@xxxxxxxxxxxxxxxx
