I'm having some difficulties in getting my digital camera to work consistently under Linux. What's the best source of information on hotplugging USB devices? Paul Abrahams
* Paul W. Abrahams <abrahams@acm.org> [01-27-04 16:31]:
I'm having some difficulties in getting my digital camera to work consistently under Linux. What's the best source of information on hotplugging USB devices?
Best strategy, IMNSHO, is a card-reader (usb2 is faster). They are almost all compatible, don't waste your camera batteries, and are portable, will work on *most* machines, even those from redmon. This makes *all* camera's compatible (depending on memory chip type). -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org
On Tuesday 27 January 2004 4:37 pm, Patrick Shanahan wrote:
* Paul W. Abrahams <abrahams@acm.org> [01-27-04 16:31]:
I'm having some difficulties in getting my digital camera to work consistently under Linux. What's the best source of information on hotplugging USB devices?
Best strategy, IMNSHO, is a card-reader (usb2 is faster). They are almost all compatible, don't waste your camera batteries, and are portable, will work on *most* machines, even those from redmon. This makes *all* camera's compatible (depending on memory chip type).
Actually my camera is a USB mass storage type, so as far as Linux is concerned it does look like a card reader. The issues troubling me have to do with the intermittency of the mount. My impression is that the USB device, which happens to be a camera but need not be, should be automounted soon after it's connected. But that's not happening (I can mount it explicitly, though). So there's some piece of setup I need to do but I don't know what it is, nor do I know where to read about it. Paul Abrahams
* Paul W. Abrahams <abrahams@acm.org> [01-27-04 18:06]:
Actually my camera is a USB mass storage type, so as far as Linux is concerned it does look like a card reader. The issues troubling me have to do with the intermittency of the mount. My impression is that the USB device, which happens to be a camera but need not be, should be automounted soon after it's connected. But that's not happening (I can mount it explicitly, though). So there's some piece of setup I need to do but I don't know what it is, nor do I know where to read about it.
I observe the same phenomenon. Sometimes a desktop object appears and other times it doesn't. I use kwikdisk to mount/umount my card reader. My camera is also recognized as a usb mass storage device, but I prefer the card reader. A work-around would be to add the possible devices to your /etc/fstab. Then they would always be available. *** Until you unplug one w/o umounting - then you are lost (at least that has been my experience). -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org
On Tuesday 27 January 2004 6:37 pm, Patrick Shanahan wrote:
* Paul W. Abrahams <abrahams@acm.org> [01-27-04 18:06]:
Actually my camera is a USB mass storage type, so as far as Linux is concerned it does look like a card reader. The issues troubling me have to do with the intermittency of the mount. My impression is that the USB device, which happens to be a camera but need not be, should be automounted soon after it's connected. But that's not happening (I can mount it explicitly, though). So there's some piece of setup I need to do but I don't know what it is, nor do I know where to read about it.
I observe the same phenomenon. Sometimes a desktop object appears and other times it doesn't. I use kwikdisk to mount/umount my card reader. My camera is also recognized as a usb mass storage device, but I prefer the card reader.
To track down what's happening, I opened a shell window and did: tail -f /var/log/messages so I could see what was being entered into the system log. I then plugged in the camera, waited a bit, and unplugged it. Here's what I saw in the log: Jan 27 20:50:33 suillus kernel: hub.c: connect-debounce failed, port 2 disabled Jan 27 20:50:34 suillus kernel: hub.c: new USB device 00:10.0-2, assigned address 8 Jan 27 20:50:34 suillus kernel: WARNING: USB Mass Storage data integrity not assured Jan 27 20:50:34 suillus kernel: USB Mass Storage device found at 8 Jan 27 20:50:34 suillus kernel: Device not ready. Make sure there is a disc in the drive. Jan 27 20:50:37 suillus last message repeated 4 times Jan 27 20:50:38 suillus kernel: SCSI device sdb: 256000 512-byte hdwr sectors (131 MB) Jan 27 20:50:38 suillus kernel: usb-uhci.c: interrupt, status 2, frame# 764 Jan 27 20:50:38 suillus kernel: sdb: test WP failed, assume Write Enabled Jan 27 20:50:39 suillus kernel: sdb: sdb1 Jan 27 20:50:39 suillus kernel: Device not ready. Make sure there is a disc in the drive. Jan 27 20:50:39 suillus kernel: Device not ready. Make sure there is a disc in the drive. Jan 27 20:51:13 suillus kernel: usb.c: USB disconnect on device 00:10.0-2 address 8 Jan 27 20:51:16 suillus kernel: Device not ready. Make sure there is a disc in the drive. Jan 27 20:51:16 suillus kernel: sdb : READ CAPACITY failed. Jan 27 20:51:16 suillus kernel: sdb : status = 1, message = 00, host = 0, driver = 08 Jan 27 20:51:16 suillus kernel: Info fld=0xa00 (nonstd), Current sd00:00: sense key Not Ready Jan 27 20:51:16 suillus kernel: sdb : block size assumed to be 512 bytes, disk size 1GB. Jan 27 20:51:16 suillus kernel: sdb: test WP failed, assume Write Enabled Jan 27 20:51:16 suillus kernel: sdb: I/O error: dev 08:10, sector 0 Jan 27 20:51:16 suillus kernel: I/O error: dev 08:10, sector 0 Jan 27 20:51:16 suillus kernel: I/O error: dev 08:10, sector 2097144 Jan 27 20:51:16 suillus kernel: I/O error: dev 08:10, sector 2097144 Jan 27 20:51:16 suillus kernel: I/O error: dev 08:10, sector 0 Jan 27 20:51:16 suillus kernel: I/O error: dev 08:10, sector 0 Jan 27 20:51:16 suillus kernel: unable to read partition table Jan 27 20:51:16 suillus kernel: I/O error: dev 08:10, sector 0 You can see the messages showing the connection and disconnection of the device, though I don't know what to make of all the errors and failures. I can certainly put an entry into /etc/fstab associating /dev/sdb1 with / media/camera (some piece of software once put a /media/camera entry into fstab but I don't know who). But what should be in such an entry to cause detection of the device to cause the mount, I wonder? Paul Abrahams
* Paul W. Abrahams <abrahams@acm.org> [01-27-04 21:22]:
I can certainly put an entry into /etc/fstab associating /dev/sdb1 with / media/camera (some piece of software once put a /media/camera entry into fstab but I don't know who). But what should be in such an entry to cause detection of the device to cause the mount, I wonder?
??, but you did have the camera turned on (after plugging in) ??? and turned it off before unplugging. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org
I've observed now that it can take several minutes after activating the camera (plugging it in and turning it on, the order doesn't seem to matter) for the camera icon to appear on my desktop and for the mount to take place. It also appears that the mount works even if there's no entry in fstab, though I haven't yet checked to see if that holds after a reboot. With no fstab entry the camera shows up as sdb1 rather than as camera. Which leads to the next question: is it better to have a /media/camera entry in fstab or not? On the surface it seems to work either way. Paul Abrahams
On Wed, 2004-01-28 at 13:48, Paul W. Abrahams wrote:
I've observed now that it can take several minutes after activating the camera (plugging it in and turning it on, the order doesn't seem to matter) for the camera icon to appear on my desktop and for the mount to take place. It also appears that the mount works even if there's no entry in fstab, though I haven't yet checked to see if that holds after a reboot. With no fstab entry the camera shows up as sdb1 rather than as camera.
Which leads to the next question: is it better to have a /media/camera entry in fstab or not? On the surface it seems to work either way.
Paul Abrahams
I've noticed that even though the camera doesn't appear right away on the desktop, it's still active. I use digikam with my camera. I plug it in, wait for the beep, turn it on, start Digikam, then connect to the camera...taking about 5 seconds. As soon as digikam picks up the camera and connects, I get the icon on my desktop. I've tried doing what you did. Plug in the camera, turn it on and wait for the icon to appear. Took quite a long time. To me it doesn't matter since I use digikam all the time. Thanks for the info though. Also, I don't have any fstab entries for the camera either. Tom -- Tom Nielsen Neuro Logic Systems 805.389.5435 x18 www.neuro-logic.com
On Wednesday 28 January 2004 5:02 pm, Tom Nielsen wrote:
I've noticed that even though the camera doesn't appear right away on the desktop, it's still active. I use digikam with my camera. I plug it in, wait for the beep, turn it on, start Digikam, then connect to the camera...taking about 5 seconds. As soon as digikam picks up the camera and connects, I get the icon on my desktop.
Where is that beep coming from? Not the camera, I assume, since you said the camera isn't yet turned on. And is there a significant delay for Digikam (which I use also) to pick up the camera?
I've tried doing what you did. Plug in the camera, turn it on and wait for the icon to appear. Took quite a long time. To me it doesn't matter since I use digikam all the time.
Would you conclude that having Digikam running speeds up the response time, then?
Thanks for the info though. Also, I don't have any fstab entries for the camera either.
How does the camera show up on your desktop? Depending on whether I have an fstab entry, it shows up either as "sdb1" or "camera". Paul Abrahams
On Wed, 2004-01-28 at 15:43, Paul W. Abrahams wrote:
On Wednesday 28 January 2004 5:02 pm, Tom Nielsen wrote:
Where is that beep coming from? Not the camera, I assume, since you said the camera isn't yet turned on.
The beep I think comes from the computer...about 2 seconds after I turn on the camera to play mode.
And is there a significant delay for Digikam (which I use also) to pick up the camera?
From connection of the camera to the system to Digikam picking it up is about 5-7 seconds. I can try the whole process faster.
I've tried doing what you did. Plug in the camera, turn it on and wait for the icon to appear. Took quite a long time. To me it doesn't matter since I use digikam all the time.
Would you conclude that having Digikam running speeds up the response time, then?
Yes. I don't know why, but I think it does. Again, I don't access the camera from Konq or anything else....just DigiKam
Thanks for the info though. Also, I don't have any fstab entries for the camera either.
How does the camera show up on your desktop? Depending on whether I have an fstab entry, it shows up either as "sdb1" or "camera".
I haven't notice. I'll look tonight and get back to you. It will happen in another 6 hours or so. Tom -- Tom Nielsen Neuro Logic Systems 805.389.5435 x18 www.neuro-logic.com
Hey, Any resolutions to this issue? I have this problem with all my USB devices--camera, palm pilot, usb keychain drive, usb mouse. I have resorted to rebooting with the device plugged in on start up for it to work with virtually any degree of success. And I agree, I get a beep or other indication the computer knows the device is plugged in. It seems as it's SUSE that takes it's time to decide to use the new device........ Thanks much! -m Paul W. Abrahams wrote:
On Wednesday 28 January 2004 5:02 pm, Tom Nielsen wrote:
I've noticed that even though the camera doesn't appear right away on the desktop, it's still active. I use digikam with my camera. I plug it in, wait for the beep, turn it on, start Digikam, then connect to the camera...taking about 5 seconds. As soon as digikam picks up the camera and connects, I get the icon on my desktop.
Where is that beep coming from? Not the camera, I assume, since you said the camera isn't yet turned on. And is there a significant delay for Digikam (which I use also) to pick up the camera?
I've tried doing what you did. Plug in the camera, turn it on and wait for the icon to appear. Took quite a long time. To me it doesn't matter since I use digikam all the time.
Would you conclude that having Digikam running speeds up the response time, then?
Thanks for the info though. Also, I don't have any fstab entries for the camera either.
How does the camera show up on your desktop? Depending on whether I have an fstab entry, it shows up either as "sdb1" or "camera".
Paul Abrahams
On Thursday 29 January 2004 09:32, Matt Jurcich wrote:
Hey,
Any resolutions to this issue? I have this problem with all my USB devices--camera, palm pilot, usb keychain drive, usb mouse. I have resorted to rebooting with the device plugged in on start up for it to work with virtually any degree of success.
And I agree, I get a beep or other indication the computer knows the device is plugged in. It seems as it's SUSE that takes it's time to decide to use the new device........
Thanks much!
This is another case of something in Suse linux 9.0 that worked for awhile, quit working and nothing I do fixes it. I have compact flash readers, usb thumb drives, and external hard drives that worked for a while then stopped never to work again. My mouse, keyboard, palm pilot and Jpilot are the only usb devices that conistantly work although sometimes with a lot of research and time to get the right modules to load. My external card readers are paperwieghts now. Hotplugging seems to be a work in progress that will not consistantly perform. DLM
-m
Paul W. Abrahams wrote:
On Wednesday 28 January 2004 5:02 pm, Tom Nielsen wrote:
I've noticed that even though the camera doesn't appear right away on the desktop, it's still active. I use digikam with my camera. I plug it in, wait for the beep, turn it on, start Digikam, then connect to the camera...taking about 5 seconds. As soon as digikam picks up the camera and connects, I get the icon on my desktop.
Where is that beep coming from? Not the camera, I assume, since you said the camera isn't yet turned on. And is there a significant delay for Digikam (which I use also) to pick up the camera?
I've tried doing what you did. Plug in the camera, turn it on and wait for the icon to appear. Took quite a long time. To me it doesn't matter since I use digikam all the time.
Would you conclude that having Digikam running speeds up the response time, then?
Thanks for the info though. Also, I don't have any fstab entries for the camera either.
How does the camera show up on your desktop? Depending on whether I have an fstab entry, it shows up either as "sdb1" or "camera".
Paul Abrahams
Yeah, I hear you there. Any suggestions (from anyone) on how to manually stop and start the usb subsystem? I found these commands but have had only limited success: sudo rmmod usb-uhci ehci-hcd hid sudo modprobe usb-uhci hid I believe it's supposed to unload the module for USB and then reload it in the second command. I still had to reboot to connect a USB mouse to my laptop this morning. :( Thanks much! -m David L Moss wrote:
On Thursday 29 January 2004 09:32, Matt Jurcich wrote:
Hey,
Any resolutions to this issue? I have this problem with all my USB devices--camera, palm pilot, usb keychain drive, usb mouse. I have resorted to rebooting with the device plugged in on start up for it to work with virtually any degree of success.
And I agree, I get a beep or other indication the computer knows the device is plugged in. It seems as it's SUSE that takes it's time to decide to use the new device........
Thanks much!
This is another case of something in Suse linux 9.0 that worked for awhile, quit working and nothing I do fixes it. I have compact flash readers, usb thumb drives, and external hard drives that worked for a while then stopped never to work again. My mouse, keyboard, palm pilot and Jpilot are the only usb devices that conistantly work although sometimes with a lot of research and time to get the right modules to load. My external card readers are paperwieghts now.
Hotplugging seems to be a work in progress that will not consistantly perform.
DLM
-m
Paul W. Abrahams wrote:
On Wednesday 28 January 2004 5:02 pm, Tom Nielsen wrote:
I've noticed that even though the camera doesn't appear right away on the desktop, it's still active. I use digikam with my camera. I plug it in, wait for the beep, turn it on, start Digikam, then connect to the camera...taking about 5 seconds. As soon as digikam picks up the camera and connects, I get the icon on my desktop.
Where is that beep coming from? Not the camera, I assume, since you said the camera isn't yet turned on. And is there a significant delay for Digikam (which I use also) to pick up the camera?
I've tried doing what you did. Plug in the camera, turn it on and wait for the icon to appear. Took quite a long time. To me it doesn't matter since I use digikam all the time.
Would you conclude that having Digikam running speeds up the response time, then?
Thanks for the info though. Also, I don't have any fstab entries for the camera either.
How does the camera show up on your desktop? Depending on whether I have an fstab entry, it shows up either as "sdb1" or "camera".
Paul Abrahams
participants (5)
-
David L Moss -
Matt Jurcich -
Patrick Shanahan -
Paul W. Abrahams -
Tom Nielsen