On Sun, 8 Oct 2006, Michael Gerdau wrote: > > The log doesn't show any errors at all. > > > > It does show the camera being in more or less constant use. Apparently > > some program was trying to access it repeatedly. Possibly hald, possibly > > an automounter, possibly something else. > > A hald based automounter is running.
Likely that is the source of your problem. You could try disabling it or even turning hald off altogether. You can mount the camera filesystem by hand. > > You might try booting into single-user mode so that no extra troublesome > > programs are running. Then what happens when you plug in the camera? > > Done that. The console output is: > usb 1-1: new full speed USB device using uhci_hcd and address 4 > usb 1-1: configuration #1 chosen from 1 choice > scsi2 : SCSI emulation for USB Mass Storage devices > Vendor: OLYMPUS Model: SP510UZ Rev: 1.00 > Type: Direct-Access ANSI SCSI revision: 02 > SCSI device sda: 2047815 512-byte hdwr sectors (1048 MB) > sda: Write Protect is off > sda: assuming drive cache: write through > SCSI device sda: 2047815 512-byte hdwr sectors (1048 MB) > sda: Write Protect is off > sda: assuming drive cache: write through > sda:<7>usb-storage: queuecommand called > sda1 > sd 2:0:0:0: Attached scsi removable disk sda > sd 2:0:0:0: Attached scsi generic sg0 type 0 > > I've attached the corresponding output from /var/log/messages. That all looks normal. > The output of lsusb at that point in time is: > Bus 004 Device 001: ID 0000:0000 > Bus 003 Device 001: ID 0000:0000 > Bus 002 Device 003: ID 046d:c025 Logitech, Inc. MX500 Optical Mouse > Bus 002 Device 001: ID 0000:0000 > Bus 001 Device 001: ID 0000:0000 I don't understand this. What do you see in /proc/bus/usb/devices and in /proc/bus/usb/001/ ? (You may need to mount /proc/bus/usb before you can see anything: "mount -t usbfs none /proc/bus/usb".) > Both 'ls /dev/sd*' and 'ls /dev/sg*' yield no files. Presumably because udevd isn't running and so the files aren't getting created. > I then returned to multiuser and issued > "udevinf -a -p `udevinfo -q path -n /dev/sda`" > The output is attached as well. It looks normal as well. > Last not least this time lsusb yields: > Bus 004 Device 001: ID 0000:0000 > Bus 003 Device 001: ID 0000:0000 > Bus 002 Device 003: ID 046d:c025 Logitech, Inc. MX500 Optical Mouse > Bus 002 Device 001: ID 0000:0000 > Bus 001 Device 005: ID 07b4:0109 Olympus Optical Co., Ltd SP-510UZ Camera > Bus 001 Device 001: ID 0000:0000 Odd. Still, for now it's better to avoid the added complexity of lsusb and just see for yourself what the /proc/bus/usb directory tree contains. > Anything else I could try ? This seems to boil down to two separate problems. One is the misbehavior of the device, probably caused by the automounter. The second is the odd behavior of lsusb. Alan Stern ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
