Militantly FREE software support.
Militantly FREE software support.
NavigationUser loginSpam?See spam posts on this site? If so, please don't reply to the spam! Instead, just report the URL to the webmaster. Cost of War |
Can't get digital camera/ USB to work.Hi, all. I have just been given a new digital camera (manufactured by Trust), and I have been unabe to get digikam to recognize it. /var/log/messages seems to detect that a device has been added to the USB port, and the camera is powered-up. I don't know anything about USB, but know that an entry does not exist in my /etc/fstab. Could this be the problem? Is KDE's Digikam the best software to use? Many thanks, Chris. Bookmark/Search this post with: 
|
• Debian Weekly News - Essential reading for any Debian fan. • Documentation - Debian's own authoritative documentation, including installation docs. • FAQ - Got questions about Debian GNU/Linux? • From Windows to Debian - Tips for converting from Windows to Debian GNU/Linux • Package of the Day. • Security - Security information and alerts! • Bug System - Bug tracking and instructions on reporting bugs. • CD Images - Where/how to get Debian GNU/Linux CD images. • Mailing List Subscription - Dozens of Debian-specific support mailing lists! • Mailing List Archives - Searchable archives of Debian's mailing lists. • Free Software Guidelines - Learn Debian's idea of what "free" software really is. • Package Listings - A very valuable tool: searchable, integrated with bug reports. • Apt-Get Sources - Sources for *.debs which are not official Debian packages. • Backports - Unofficial new software packages that have been "back-ported" to work with the Debian stable/official release. • Developer's Corner - Info about the people behind Debian, policies, and how to package *.deb files.
a little experimentation...
It will show up as a /dev/sd?? device. If you have 'udev' that's great because the only visible devices will be the ones which exist, so there are fewer to choose from.
These systems all use a FAT partition scheme - on most USB sticks you can 'reformat' to a different type, but don't do that with your camera or it will become very confused. SO - assuming it's '/dev/sda' you can try:
mount /dev/sda /mnt
Many newer devices will appear as "sda1" rather than "sda":
mount /dev/sda1 /mnt
If you don't have certain modules compiled/loaded, you need to specify the partition type:
mount -t vfat /dev/sda /mnt
or
mount -t vfat /dev/sda1 /mnt
The 'vfat' driver will handle everything from FAT12 to FAT32.
Hmmm, Thanks for that, will
Hmmm,
Thanks for that, will have a look when I get home.
Cheers,
Chris.
General USB storage device?
Hi Chris
Some digital cameras use their own protocol to transfer the pictures taken whereas others (most) cameras just export a standard USB storage device (that is, you access it like a USB flash drive/key).
I can't say what cameras manufactured by Trust actually use. If it is the former, than you shouldn't have had a problem anyway (like on Windows or Mac, those hot-pluggable devices are recognized (and mounted) automatically). But in case it didn't, try what pinniped suggested.
On the other hand, it might be that your camera uses a proprietary protocol. The tool 'gphoto2' may be able to recognize this camera then. I guess that KDE's Digikam already uses it underneath to access such cameras, but I'm not sure.
Just to be sure, please post the few lines that appear if you plug it in (from /var/log/messages). There it should say whether the USB device is a general USB storage device or not. In addition you can post the output of 'lsusb -v'.
Good luck,
Georg
Cheers, Georg. Will get the
Cheers, Georg. Will get the ouput, tonight.
Re: General USB storage device?
Georg,
I am using the latest debian squeeze, after the latest update I started getting errors concerning the I/O library and other device busy. I just did apt-get install gphoto2 and after the installation all is back to normal, Must be a library problem.
Gerry
automount?
If it autoomount (as stated it might) does this mean you need a line in your fstab to casue this to happen?
Hi, Sorry about the
Hi,
Sorry about the delay.
Output from lsusb -v looks like this:
Bus 004 Device 001: ID 0000:0000
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 1 Single TT
bMaxPacketSize0 64
idVendor 0x0000
idProduct 0x0000
bcdDevice 2.06
iManufacturer 3 Linux 2.6.15-27-386 ehci_hcd
iProduct 2 EHCI Host Controller
iSerial 1 0000:00:10.3
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0002 1x 2 bytes
bInterval 12
Hub Descriptor:
bLength 9
bDescriptorType 41
nNbrPorts 6
wHubCharacteristic 0x000a
No power switching (usb 1.0)
Per-port overcurrent protection
TT think time 8 FS bits
bPwrOn2PwrGood 10 * 2 milli seconds
bHubContrCurrent 0 milli Ampere
DeviceRemovable 0x48
PortPwrCtrlMask 0xc0
Hub Port Status:
Port 1: 0000.0000
Port 2: 0000.0100 power
Port 3: 0000.0100 power
Port 4: 0000.0100 power
Port 5: 0000.0100 power
Port 6: 0000.0100 power
Device Status: 0x0001
Self Powered
Bus 001 Device 001: ID 0000:0000
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0000
idProduct 0x0000
bcdDevice 2.06
iManufacturer 3 Linux 2.6.15-27-386 uhci_hcd
iProduct 2 UHCI Host Controller
iSerial 1 0000:00:10.0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0002 1x 2 bytes
bInterval 255
Hub Descriptor:
bLength 9
bDescriptorType 41
nNbrPorts 2
wHubCharacteristic 0x000a
No power switching (usb 1.0)
Per-port overcurrent protection
bPwrOn2PwrGood 1 * 2 milli seconds
bHubContrCurrent 0 milli Ampere
DeviceRemovable 0xc0
PortPwrCtrlMask 0xc0
Hub Port Status:
Port 1: 0000.0101 power connect
Port 2: 0000.0100 power
Device Status: 0x0003
Self Powered
Remote Wakeup Enabled
Bus 002 Device 001: ID 0000:0000
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0000
idProduct 0x0000
bcdDevice 2.06
iManufacturer 3 Linux 2.6.15-27-386 uhci_hcd
iProduct 2 UHCI Host Controller
iSerial 1 0000:00:10.1
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0002 1x 2 bytes
bInterval 255
Hub Descriptor:
bLength 9
bDescriptorType 41
nNbrPorts 2
wHubCharacteristic 0x000a
No power switching (usb 1.0)
Per-port overcurrent protection
bPwrOn2PwrGood 1 * 2 milli seconds
bHubContrCurrent 0 milli Ampere
DeviceRemovable 0x38
PortPwrCtrlMask 0xc1
Hub Port Status:
Port 1: 0000.0100 power
Port 2: 0000.0100 power
Device Status: 0x0003
Self Powered
Remote Wakeup Enabled
Bus 003 Device 001: ID 0000:0000
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0000
idProduct 0x0000
bcdDevice 2.06
iManufacturer 3 Linux 2.6.15-27-386 uhci_hcd
iProduct 2 UHCI Host Controller
iSerial 1 0000:00:10.2
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0002 1x 2 bytes
bInterval 255
Hub Descriptor:
bLength 9
bDescriptorType 41
nNbrPorts 2
wHubCharacteristic 0x000a
No power switching (usb 1.0)
Per-port overcurrent protection
bPwrOn2PwrGood 1 * 2 milli seconds
bHubContrCurrent 0 milli Ampere
DeviceRemovable 0xf0
PortPwrCtrlMask 0x00
Hub Port Status:
Port 1: 0000.0300 lowspeed power
Port 2: 0000.0100 power
Device Status: 0x0003
Self Powered
Remote Wakeup Enabled
And, tail -f /var/log/messages looks like this:
Sep 30 19:27:19 aslan kernel: [17222201.736000] usb 1-1: new full speed USB device using uhci_hcd and address 9
Does this help?
Thanks,
Chris.
Udev after 0.105-4 sucks
Udev after 0.105-4 seams to suck when it comes to cameras. I could not mount my Nikon D80 after upgrading. (But I can mount my MP3-player.) Therefor I hold on to Udev 0.105-4 until I found a solution somethere.
If you run Udev after 0.105-4: Downgrade!