On Mon, Aug 09, 2004 at 05:59:26PM +0100, Steve King wrote:
Folks
Anyone know whether the SuSE 9.1 submount update was supposed to fix the problems many of us have with USB devices: memory sticks and cameras? Just that nothing has changed on my box. I still cannot access either device.
It works here.
Both my memory stick and camera device are detected correctly when I plug them in: I get the device make, model, etc in the messages log.
But then I get "Could not enter folder /media/sda1" if I try to enter the directory.
I have tried this with fstab entries that say:
/dev/sda1 /media/sda1 subfs fs=floppyfss:cdfss,sync 0 0 or /dev/sda1 /media/sda1 subfs fs=auto,sync 0 0 or /dev/sda1 /media/sda1 subfs fs=floppyfss,sync 0 0
Same outcome in all cases. I rebooted the machine after each change to fstab.
You don't need to add anything to /etc/fstab An entry is created dynamically by hotplug.
I tried the suggestion about changing the sysconfig variable HOTPLUG_USE_SUBFS from yes to no. Running "rchotplug restart" did not activate the change: if I tried to enter /media/sda1, I still got the "cannot enter" message which I presume is related to submount. I rebooted and this message went away.
But still no joy. I changed fstab to say "/dev/sda1 /media/sda1 auto noauto,user,sync 0 0". Then I tried to mount /media/sda1. That was several minutes ago and the command prompt has not come back yet... Experience makes me suspect that when I shutdown I am going to get a message about not being able to unmount one of the hard disk partitions.
This is just like if I use the mount command when subfs is selected... Which makes me think that perhaps submount is doing what it can but that something else is preventing these devices from being mounted.
There are suggestions in this list and elsewhere that some funny-named directories should get created automatically when I plug in a device - they do not.
If you changed HOTPLUG_USE_SUBFS to no they wouldn't be created.
I've looked at my sysconfig/hotplug file from SuSE 9.0 (where my devices worked perfectly) and it contains many more variables, including some that seem to relate to USB devices. Does anyone know if there would be mileage in trying them, or has the set up changed too much to make them relevant now?
I haven't changed anything there.
Finally, here is some information from the messages log. You'll see I have been experimenting using two devices (not both together). I am not sure that the NOMAD got successfully noticed at all on this occasion.
Aug 8 22:17:06 linux kernel: usb 1-2: new full speed USB device using address 4 Aug 8 22:17:06 linux kernel: usb 1-2: Product: NOMAD MuVo Aug 8 22:17:06 linux kernel: usb 1-2: Manufacturer: Creative Tech Aug 8 22:17:06 linux kernel: usb 1-2: SerialNumber: 000000000000 Aug 8 22:17:06 linux /etc/hotplug/usb.agent[6254]: need a device for this command Aug 8 22:17:12 linux kernel: Initializing USB Mass Storage driver... Aug 8 22:17:12 linux kernel: scsi0 : SCSI emulation for USB Mass Storage devices Aug 8 22:17:12 linux kernel: Vendor: CREATIVE Model: NOMAD_MUVO Rev: 0001 Aug 8 22:17:12 linux kernel: Type: Direct-Access ANSI SCSI revision: 02 Aug 8 22:17:12 linux kernel: SCSI device sda: 126977 512-byte hdwr sectors (65 MB) Aug 8 22:17:12 linux kernel: sda: assuming Write Enabled Aug 8 22:17:12 linux kernel: sda: assuming drive cache: write through Aug 8 22:17:13 linux kernel: sda:end_request: I/O error, dev sda, sector 126976 Aug 8 22:17:13 linux kernel: Buffer I/O error on device sda, logical block 126976 Aug 8 22:17:13 linux /etc/hotplug/block.agent[6374]: new block device /block/sda Aug 8 22:17:29 linux kernel: SCSI error : <0 0 0 0> return code = 0x70000 Aug 8 22:17:29 linux kernel: end_request: I/O error, dev sda, sector 126976 Aug 8 22:17:29 linux kernel: Buffer I/O error on device sda, logical block 126976
It looks like hardware error on your creative nomad.
Aug 8 22:17:29 linux kernel: sda1 Aug 8 22:17:29 linux kernel: Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0 Aug 8 22:17:29 linux kernel: Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0 Aug 8 22:17:29 linux kernel: USB Mass Storage device found at 4 Aug 8 22:17:29 linux kernel: usbcore: registered new driver usb-storage Aug 8 22:17:29 linux kernel: USB Mass Storage support registered. Aug 8 22:17:29 linux kernel: usb 1-2: USB disconnect, address 4 Aug 8 22:17:30 linux /etc/hotplug/usb.agent[6495]: need a device for this command Aug 8 22:17:40 linux /etc/hotplug/block.agent[6414]: new block device /block/sda/sda1 Aug 8 22:18:05 linux kernel: usb 1-2: new full speed USB device using address 5 Aug 8 22:18:06 linux kernel: usb 1-2: Product: NIKON DSC E2000 Aug 8 22:18:06 linux kernel: usb 1-2: Manufacturer: NIKON Aug 8 22:18:06 linux kernel: scsi1 : SCSI emulation for USB Mass Storage devices Aug 8 22:18:06 linux /etc/hotplug/usb.agent[6716]: need a device for this command Aug 8 22:18:06 linux kernel: Vendor: NIKON Model: DSC E2000 Rev: 1.00 Aug 8 22:18:06 linux kernel: Type: Direct-Access ANSI SCSI revision: 02 Aug 8 22:18:06 linux kernel: SCSI device sda: 63489 512-byte hdwr sectors (33 MB) Aug 8 22:18:06 linux kernel: sda: assuming Write Enabled Aug 8 22:18:06 linux kernel: sda: assuming drive cache: write through Aug 8 22:18:06 linux /etc/hotplug/block.agent[6776]: new block device /block/sda
Nothing bad with camera, I think. This is what I would try to debug the problem. Reinstate HOTPLUG_USE_SUBFS to yes and restart hotplug. Connect camera, look in /var/log/messages for camera to be recognized. After that, issue mount command without parameteres to see what mount point is created for camera. It should look something like: /dev/sda1 on /media/usb-storage-0000022176:0:0:0p1 type subfs (rw,noexec,nosuid,nodev,sync,fs=floppyfss,procuid,iocharset=utf8) Try accessing mount point, e.g. ls /media/usb-storage-0000022176:0:0:0p1 If this produces an error "media not found", try to mount it manually with differnet subfs options. First unmount it with umount /media/usb-storage-0000022176:0:0:0p1 (of course, the name will be different in your case) and then mount manually with different options: mount -t subfs -o rw,noexec,nosuid,nodev,sync,fs=floppyfss,procuid,iocharset=utf8 \ /dev/sda1 /media/usb-storage-0000022176:0:0:0p1 Or try mount it with vfat (I believe your camera card is formatted with FAT): mount -t vfat /dev/sda1 /media/usb-storage-0000022176:0:0:0p1 In my case, fs=auto didn't work, empty fs= didn't work either. Only floppyfss works for me for camera/xD card Regards, -Kastus