Retrofitting a Device File for a Mass Storage Device?
Dear usb driver experts,
here we have an older digicam (Jenoptik/Exakta Model "DC 22", if someone might want to know) that can be switched between some "PC Camera mode" and "Mass storage mode". Unfortunately, if attached to USB, it is always recognized as Code:
UDEV [1262910483.475886] add /class/video4linux/video0 (video4linux) Code:
Bus 005 Device 008: ID 0d64:3108 DXG Technology Corp. Digicam Mass Storage Device Code:
Model: "DXG DIGITAL CAMERA USB" Code:
Driver Info #0: How can one manually recreate it, or: Can udev's recognition be changed in order to "find" something like '/class/scsi_disk/' instead of '/class/video4linux/video0' only? It still seems quite promising, but out of ideas now we would appreciate any advice. |
the message seems to be saying that your camera can act as a webcam as well as ums.
udev will usually put a ums device in /media - have you looked? before adding the camera do dmesg > before.log after adding camera do dmesg > after.log diff before after > changes.log look at the changes.log file. It should tell you what is going on. |
Hello Simon,
thanks for your quick reply! Well, diff before.log after.log gives us: Code:
> ap: 60000000:9ec00000) Code:
brw-rw---- 1 root floppy 8, 17 8. Jan 02:28 /dev/sdb1 Bottom line: _ s t r a n g e _ ... (but all right for us ,-) ) |
Well done - now you have a powerful new trick.
|
Solution for missing mass storage devices
Just to summarize: if you have a digital camera recognized as video for linux device and miss it as mass storage device, just unload/remove its v4l driver.
|
All times are GMT -5. The time now is 04:14 PM. |