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