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. Everything seems fine for the CD and DVD drives, and I think for floppies (works normally, anyway). And it always has been. I'm pleased that someone somewhere is trying to fix the problems. I hope that the following might be helpful.... Or perhaps someone might spot that my problem isn't with submount at all... BTW, I know I've mentioned problems with these devices on this list before, but I have not previously been as thorough as what follows in providing information. Here goes... 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. 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. 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? 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 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 Steve Dundee, UK
On Monday 09 August 2004 12:59, 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.
My understanding was that it was the hotplug update that broke it, and it was since withdrawn for fixing. I'm running hotplug-0.44-32 and it works with my camera mem card. That should be the version on the SUSE 9.1 distro disk... Cheers, J.C. -- John Coldrick www.axyzfx.com Axyz Animation Houdini/Renderman/Discreet 425 Adelaide St W 416-504-0425 Toronto, ON Canada jc@axyzfx.com M5V 1S4 ----------------------------------------------------------------------- Ah say, son, you're about as sharp as a bowlin' ball.
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
Kastus wrote:
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.
It doesn't here.
On Mon, Aug 09, 2004 at 06:19:02PM -0400, James Knott wrote:
Kastus wrote:
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.
It doesn't here.
Sorry, my crystal ball is at repair now, I cannot read your /var/log/messages remotely. Seriously, if you need help diagnosing your problem, please provide more details. Regards, -Kastus
On Monday 09 August 2004 3:19 pm, James Knott wrote:
Kastus wrote:
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.
It doesn't here.
My camerea works, but not my card reader. Rich
On Monday 09 August 2004 21:21, Kastus wrote:
You don't need to add anything to /etc/fstab An entry is created dynamically by hotplug.
That's part of the mystery. I can tell from other people's posts that this should be happening, and also I recall it from trying the Live CD. But no directories get created when I connect the camera.
If you changed HOTPLUG_USE_SUBFS to no they wouldn't be created.
I suppose not, but setting to "yes" doesn't behave any differently.
It looks like hardware error on your creative nomad.
It works fine with SuSE 9.0. And within the past few weeks has worked fine on SuSE 7.3 and Redhat 9 (but of course they are too far in the past to prove it is OK today).
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)
Tried that just now. There is no /media/usb... directory. As I mentioned, I think I remember such directories did used ot get created, but not since I made the current installation. When they did exist, I got the same "could not enter" message as I am getting with my home-grown mount points.
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
Any attempt to mount /dev/sda1 results n the command hanging "forever". AT closedown, hda7 cannot be unmounted! Thanks for your feedback, Kastus. Much appreciated. I think maybe there could be some configuration problems with mounting my USB hotplug devices. (My scanner is USB too and that works fine; though I did have to edit the /etc/hotplug/usb/desktopdev file; but note that I was having mount problems before I changed that.) With the fstab entries I tried, something (I presume submount) did seem to try to mount the directory when I tried to enter it but it cannot mount it any more than I can mount it with a mount command; the only difference being at least submount returns an error rather than hanging. The amazing thing is that the system can clearly communicate with the devices. It knows all about them and how much disk space they have. My only reason for doubting it is as simple as configuration is that Mandrake 10 behaves the same way; so it could be something about 2.6 and my hardware. Any more thoughts? Is there any kind of diagnostic process I could follow - I know that it is very difficult to figure out a problem on a distant PC. Steve Dundee, UK
Hi Just installed today's hardware rpm update. Restarted machine with Muvo plugged in and now it shows up in "My Computer" plus one of those funny-named directories is created. So far so good... except that I get "Could not enter folder /media/usb-storage-odd-CreativeTech-NOMADMuVo:0:0:0p1" I've left this plugged in before, but the boot up on those occasions seemed to pause "forever". This time it paused for just a couple of minutes. What I am getting at is, today's differences may not be related to the new rpm. The reason I am posting this is because the messages in /var/log/messages are more interesting today. Anyone got any idea what they imply? <Start of lines> Aug 11 21:41:38 linux kernel: Initializing USB Mass Storage driver... Aug 11 21:41:38 linux kernel: scsi0 : SCSI emulation for USB Mass Storage devices Aug 11 21:41:38 linux kernel: Vendor: CREATIVE Model: NOMAD_MUVO Rev: 0001 Aug 11 21:41:38 linux kernel: Type: Direct-Access ANSI SCSI revision: 02 Aug 11 21:41:38 linux kernel: USB Mass Storage device found at 2 Aug 11 21:41:38 linux kernel: usbcore: registered new driver usb-storage Aug 11 21:41:38 linux kernel: USB Mass Storage support registered. Aug 11 21:41:38 linux kernel: SCSI device sda: 126977 512-byte hdwr sectors (65 MB) Aug 11 21:41:38 linux kernel: sda: assuming Write Enabled Aug 11 21:41:38 linux kernel: sda: assuming drive cache: write through Aug 11 21:41:38 linux kernel: sda:end_request: I/O error, dev sda, sector 126976 Aug 11 21:41:38 linux kernel: Buffer I/O error on device sda, logical block 126976 Aug 11 21:41:38 linux /etc/hotplug/block.agent[4083]: new block device /block/sda Aug 11 21:41:41 linux kernel: hdc: ATAPI 32X DVD-ROM drive, 512kB Cache Aug 11 21:41:41 linux kernel: Uniform CD-ROM driver Revision: 3.20 Aug 11 21:41:42 linux kernel: hdd: ATAPI 52X CD-ROM CD-R/RW CD-MRW drive, 2048kB Cache Aug 11 21:41:42 linux /etc/hotplug/block.agent[4606]: grep: /sys/class/scsi_host/ide1/proc_name: No such file or directory Aug 11 21:41:42 linux /etc/hotplug/block.agent[4606]: grep: /sys/class/scsi_host/ide1/proc_name: No such file or directory Aug 11 21:41:42 linux /etc/hotplug/block.agent[4643]: grep: /sys/class/scsi_host/ide1/proc_name: No such file or directory Aug 11 21:41:42 linux /etc/hotplug/block.agent[4643]: grep: /sys/class/scsi_host/ide1/proc_name: No such file or directory Aug 11 21:41:42 linux /etc/hotplug/block.agent[4606]: waiting for /var/lock/block.agent.lock, process 4083 holds it Aug 11 21:41:42 linux /etc/hotplug/block.agent[4643]: waiting for /var/lock/block.agent.lock, process 4083 holds it Aug 11 21:41:44 linux kernel: PCI: Found IRQ 10 for device 0000:00:14.5 Aug 11 21:41:44 linux kernel: PCI: Setting latency timer of device 0000:00:14.5 to 64 Aug 11 21:41:51 linux kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for Generic Aug 11 21:41:51 linux kernel: usbcore: registered new driver usbserial Aug 11 21:41:51 linux kernel: drivers/usb/serial/usb-serial.c: USB Serial Driver core v2.0 Aug 11 21:41:55 linux /etc/hotplug/block.agent[4606]: new block device /block/hdc Aug 11 21:41:55 linux /etc/hotplug/block.agent[4643]: new block device /block/hdd Aug 11 21:41:57 linux kernel: Non-volatile memory driver v1.2 Aug 11 21:41:57 linux kernel: end_request: I/O error, dev fd0, sector 0 Aug 11 21:41:57 linux kernel: end_request: I/O error, dev fd0, sector 0 Aug 11 21:41:57 linux kernel: st: Version 20040318, fixed bufsize 32768, s/g segs 256 Aug 11 21:42:58 linux kernel: drivers/usb/core/hub.c: USB device not accepting new address (error=-71) Aug 11 21:42:58 linux kernel: scsi: Device offlined - not ready after error recovery: host 0 channel 0 id 0 lun 0 Aug 11 21:42:58 linux kernel: SCSI error : <0 0 0 0> return code = 0x50000 Aug 11 21:42:58 linux kernel: end_request: I/O error, dev sda, sector 126976 Aug 11 21:42:58 linux kernel: Buffer I/O error on device sda, logical block 126976 Aug 11 21:42:58 linux kernel: unsupported disk (sda) Aug 11 21:42:58 linux kernel: sda1 Aug 11 21:42:58 linux kernel: Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0 Aug 11 21:42:58 linux kernel: Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0 Aug 11 21:42:58 linux /etc/hotplug/block.agent[5483]: new block device /block/sda/sda1 Aug 11 21:42:58 linux kernel: BIOS EDD facility v0.13 2004-Mar-09, 2 devices found Aug 11 21:43:01 linux /etc/hotplug/block.agent[5483]: mount by-path/usb-storage-odd-CreativeTech-NOMADMuVo:0:0:0p1 Aug 11 21:44:56 linux kernel: ISO 9660 Extensions: Microsoft Joliet Level 1 Aug 11 21:44:57 linux kernel: ISOFS: changing to secondary root Aug 11 21:45:03 linux submountd: unable to determine filesystem type Aug 11 21:45:03 linux submountd: mount failure, Success Aug 11 21:45:03 linux kernel: subfs: unsuccessful attempt to mount media (256) Aug 11 21:45:12 linux submountd: unable to determine filesystem type Aug 11 21:45:12 linux submountd: mount failure, Success Aug 11 21:45:12 linux kernel: subfs: unsuccessful attempt to mount media (256) <end of lines> I have removed lines that clearly have no bearing on the issue, but have left in some which I think may relate to other hotplug-type devices, such as the DVD drive. The bit I am most interested in are the lines at 21:42:58. Also the one at 21:43:01, which looks to explain the long pause during boot up. I created an /events directory as suggested by Kastus and sure enough lots of interesting stuff in there. What do I make of it all? Also I've looked for "/sys/class/scsi_host/ide1/proc_name". It does not exist, but "/sys/devices/pci0000:00/0000:00:14.2/usb1/1-2/1-2:1.0/host0/0:0:0:0" and it contains loads of stuff that seem to refer to the Muvo. So I seem to have loads of clues, just no idea what to do with them... Steve Dundee, UK
On Monday August 9 2004 12:59 pm, 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's STILL broken! [snip] Use the old version. Fred -- "Running Windows on a Pentium is like getting a Porsche but only being able to drive it in reverse with the handbrake on."
Fred Miller writes:
On Monday August 9 2004 12:59 pm, Steve King wrote:
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's STILL broken! Use the old version.
That may be the case, but it's now less broken than the previous update. My Sony digital camera now works again with the latest update. -Ti
On Monday August 9 2004 5:23 pm, Ti Kan wrote:
Fred Miller writes:
On Monday August 9 2004 12:59 pm, Steve King wrote:
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's STILL broken! Use the old version.
That may be the case, but it's now less broken than the previous update. My Sony digital camera now works again with the latest update.
'Couldn't read my card reader, so I went back to the old config file. Fred -- "Running Windows on a Pentium is like getting a Porsche but only being able to drive it in reverse with the handbrake on."
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 It's still doesn't work for me either. The messages log shows it, can run fdisk -l on /dev/sda and it shows the partition info., suseplugger can see it. When I run mount by itself, nothing shows. I can mount it by hand. Below is tail of my messages log after inserting the flash drive. Aug 11 09:27:01 shadowcat kernel: usb 3-2: new high speed USB device using address 6 Aug 11 09:27:01 shadowcat kernel: usb 3-2: Product: USB 2.0 Flash Drive Aug 11 09:27:01 shadowcat kernel: usb 3-2: Manufacturer: Super Talent Falsh Aug 11 09:27:01 shadowcat kernel: usb 3-2: SerialNumber: 00000000000000002715 Aug 11 09:27:01 shadowcat kernel: scsi4 : SCSI emulation for USB Mass Storage devices Aug 11 09:27:01 shadowcat /etc/hotplug/usb.agent[433]: need a device for this command Aug 11 09:27:01 shadowcat kernel: Vendor: S Talent Model: Flash Drive 2.0 Rev: 2010 Aug 11 09:27:01 shadowcat kernel: Type: Direct-Access ANSI SCSI revision: 02 Aug 11 09:27:01 shadowcat kernel: SCSI device sda: 1014784 512-byte hdwr sectors (520 MB) Aug 11 09:27:01 shadowcat kernel: sda: assuming Write Enabled Aug 11 09:27:01 shadowcat kernel: sda: assuming drive cache: write through Aug 11 09:27:01 shadowcat /etc/hotplug/block.agent[501]: try 1 while waiting for /block/sda's bus_id 4:0:0:0 Aug 11 09:27:01 shadowcat kernel: sda: sda1 Aug 11 09:27:01 shadowcat kernel: Attached scsi removable disk sda at scsi4, channel 0, id 0, lun 0 Aug 11 09:27:01 shadowcat kernel: Attached scsi generic sg0 at scsi4, channel 0, id 0, lun 0, type 0 Aug 11 09:27:01 shadowcat kernel: USB Mass Storage device found at 6 Aug 11 09:27:01 shadowcat /etc/hotplug/block.agent[523]: new block device /block/sda/sda1 Aug 11 09:27:02 shadowcat /etc/hotplug/block.agent[501]: waiting for /var/lock/block.agent.lock, process 523 holds it Aug 11 09:27:03 shadowcat /etc/hotplug/block.agent[501]: new block device /block/sda John -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFBGiAa5JB+bPW3+KwRAlCYAKC6qt5v7EijDS+PxFGkgZssX/boOQCcCj11 isrAK2rLBuOurMvMyGZk3ZY= =zEfS -----END PGP SIGNATURE-----
On Wed, Aug 11, 2004 at 09:33:14AM -0400, John Scott wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
It's still doesn't work for me either. The messages log shows it, can run fdisk -l on /dev/sda and it shows the partition info., suseplugger can see it. When I run mount by itself, nothing shows. I can mount it by hand. Below is tail of my messages log after inserting the flash drive.
That means mount point had not been created. To see what goes wrong try increasing verbosity of messages by changing HOTPLUG_DEBUG="no" to HOTPLUG_DEBUG="yes" in /etc/sysconfig/hotplug. Also if you create a /events directory then some useful debugging information shows up there. Regards, -Kastus
***Warning - Long Post*** After the recent hwinfo and hotplug updates, flash drive still isn't automounted. Can mount it manually, but could do that before. Here's output of messages afer setting DEBUG="yes" Aug 11 14:07:10 shadowcat kernel: usb 3-2: new high speed USB device using address 7 Aug 11 14:07:10 shadowcat kernel: usb 3-2: Product: USB 2.0 Flash Drive Aug 11 14:07:10 shadowcat kernel: usb 3-2: Manufacturer: Super Talent Falsh Aug 11 14:07:10 shadowcat kernel: usb 3-2: SerialNumber: 00000000000000002715 Aug 11 14:07:10 shadowcat /sbin/hotplug[18795]: add usb Aug 11 14:07:10 shadowcat /sbin/hotplug[18795]: LOGPID=18795 OLDPWD=/ DEVPATH=/devices/pci0000:00/0000:00:02.2/usb3/3-2 PATH=/sbin:/usr/sbin:/bin:/usr/bin ACTION=add PWD=/etc/hotplug SHLVL=1 HOME=/ SEQNUM=271 _=/usr/bin/env Aug 11 14:07:10 shadowcat /sbin/hotplug[18796]: add usb Aug 11 14:07:10 shadowcat /sbin/hotplug[18796]: LOGPID=18796 OLDPWD=/ DEVPATH=/devices/pci0000:00/0000:00:02.2/usb3/3-2/3-2:1.0 PATH=/sbin:/usr/sbin:/bin:/usr/bin ACTION=add PWD=/etc/hotplug SHLVL=1 HOME=/ DEVICE=/proc/bus/usb/003/007 INTERFACE=8/6/80 PRODUCT=90c/1000/2010 TYPE=0/0/0 SEQNUM=272 _=/usr/bin/env Aug 11 14:07:10 shadowcat kernel: scsi5 : SCSI emulation for USB Mass Storage devices Aug 11 14:07:10 shadowcat /sbin/hotplug[18822]: add scsi_host Aug 11 14:07:10 shadowcat /sbin/hotplug[18822]: LOGPID=18822 OLDPWD=/ DEVPATH=/class/scsi_host/host5 PATH=/sbin:/usr/sbin:/bin:/usr/bin ACTION=add PWD=/etc/hotplug SHLVL=1 HOME=/ SEQNUM=273 _=/usr/bin/env Aug 11 14:07:10 shadowcat kernel: Vendor: S Talent Model: Flash Drive 2.0 Rev: 2010 Aug 11 14:07:10 shadowcat kernel: Type: Direct-Access ANSI SCSI revision: 02 Aug 11 14:07:10 shadowcat kernel: SCSI device sda: 1014784 512-byte hdwr sectors (520 MB) Aug 11 14:07:10 shadowcat kernel: sda: assuming Write Enabled Aug 11 14:07:10 shadowcat kernel: sda: assuming drive cache: write through Aug 11 14:07:10 shadowcat /sbin/hotplug[18833]: add scsi Aug 11 14:07:10 shadowcat /sbin/hotplug[18833]: LOGPID=18833 OLDPWD=/ DEVPATH=/devices/pci0000:00/0000:00:02.2/usb3/3-2/3-2:1.0/host5/5:0:0:0 PATH=/sbin:/usr/sbin:/bin:/usr/bin ACTION=add PWD=/etc/hotplug SHLVL=1 HOME=/ SEQNUM=274 _=/usr/bin/env Aug 11 14:07:10 shadowcat /sbin/hotplug[18834]: add block Aug 11 14:07:10 shadowcat /sbin/hotplug[18834]: LOGPID=18834 OLDPWD=/ DEVPATH=/block/sda PATH=/sbin:/usr/sbin:/bin:/usr/bin ACTION=add PWD=/etc/hotplug SHLVL=1 HOME=/ SEQNUM=275 _=/usr/bin/env Aug 11 14:07:10 shadowcat /etc/hotplug/usb.agent[18796]: need a device for this command Aug 11 14:07:11 shadowcat /etc/hotplug/block.agent[18834]: try 1 while waiting for /block/sda's bus_id 5:0:0:0 Aug 11 14:07:11 shadowcat /etc/hotplug/scsi_host.agent[18822]: Unknown scsi_host type Aug 11 14:07:11 shadowcat kernel: sda: sda1 Aug 11 14:07:11 shadowcat kernel: Attached scsi removable disk sda at scsi5, channel 0, id 0, lun 0 Aug 11 14:07:11 shadowcat /sbin/hotplug[18886]: add block Aug 11 14:07:11 shadowcat /sbin/hotplug[18887]: add scsi_device Aug 11 14:07:11 shadowcat /sbin/hotplug[18887]: LOGPID=18887 OLDPWD=/ DEVPATH=/class/scsi_device/5:0:0:0 PATH=/sbin:/usr/sbin:/bin:/usr/bin ACTION=add PWD=/etc/hotplug SHLVL=1 HOME=/ SEQNUM=277 _=/usr/bin/env Aug 11 14:07:11 shadowcat /sbin/hotplug[18888]: add scsi_generic Aug 11 14:07:11 shadowcat /sbin/hotplug[18888]: LOGPID=18888 OLDPWD=/ DEVPATH=/class/scsi_generic/sg0 PATH=/sbin:/usr/sbin:/bin:/usr/bin ACTION=add PWD=/etc/hotplug SHLVL=1 HOME=/ SEQNUM=278 _=/usr/bin/env Aug 11 14:07:11 shadowcat kernel: Attached scsi generic sg0 at scsi5, channel 0, id 0, lun 0, type 0 Aug 11 14:07:11 shadowcat kernel: USB Mass Storage device found at 7 Aug 11 14:07:11 shadowcat /sbin/hotplug[18886]: LOGPID=18886 OLDPWD=/ DEVPATH=/block/sda/sda1 PATH=/sbin:/usr/sbin:/bin:/usr/bin ACTION=add PWD=/etc/hotplug SHLVL=1 HOME=/ SEQNUM=276 _=/usr/bin/env Aug 11 14:07:11 shadowcat /etc/hotplug/block.agent[18886]: line P: /block/sda/sda1 Aug 11 14:07:11 shadowcat /etc/hotplug/block.agent[18886]: line N: sda1 Aug 11 14:07:11 shadowcat /etc/hotplug/block.agent[18886]: ncookie sda1 Aug 11 14:07:11 shadowcat /etc/hotplug/block.agent[18886]: line M: 0660 Aug 11 14:07:11 shadowcat /etc/hotplug/block.agent[18886]: line S: by-path/not by-path/handled by-id/1 Aug 11 14:07:11 shadowcat /etc/hotplug/block.agent[18886]: scookie by-path/not Aug 11 14:07:11 shadowcat /etc/hotplug/block.agent[18886]: line O: root Aug 11 14:07:11 shadowcat /etc/hotplug/block.agent[18886]: line G: disk Aug 11 14:07:11 shadowcat /etc/hotplug/block.agent[18886]: line Aug 11 14:07:11 shadowcat /etc/hotplug/block.agent[18886]: new block device /block/sda/sda1 Aug 11 14:07:12 shadowcat /etc/hotplug/block.agent[18834]: line P: /block/sda Aug 11 14:07:12 shadowcat /etc/hotplug/block.agent[18834]: line N: sda Aug 11 14:07:12 shadowcat /etc/hotplug/block.agent[18834]: ncookie sda Aug 11 14:07:12 shadowcat /etc/hotplug/block.agent[18834]: line M: 0660 Aug 11 14:07:12 shadowcat /etc/hotplug/block.agent[18834]: line S: by-path/not by-path/handled Aug 11 14:07:12 shadowcat /etc/hotplug/block.agent[18834]: scookie by-path/not Aug 11 14:07:12 shadowcat /etc/hotplug/block.agent[18834]: line O: root Aug 11 14:07:12 shadowcat /etc/hotplug/block.agent[18834]: line G: disk Aug 11 14:07:12 shadowcat /etc/hotplug/block.agent[18834]: line Aug 11 14:07:12 shadowcat /etc/hotplug/block.agent[18834]: waiting for /var/lock/block.agent.lock, process 18886 holds it Aug 11 14:07:13 shadowcat /etc/hotplug/block.agent[18834]: new block device /block/sda Aug 11 14:07:16 shadowcat /etc/hotplug/usb.agent[18796]: No drivers for 'USB product 90c/1000/2010' (from /etc/hotplug/usb.handmap) Aug 11 14:07:16 shadowcat /etc/hotplug/usb.agent[18796]: Setup 'usb-storage ' for 'USB product 90c/1000/2010' (from /lib/modules/2.6.5-7.104-default/modules.usbmap) Aug 11 14:07:16 shadowcat /etc/hotplug/usb.agent[18796]: No drivers for 'USB product 90c/1000/2010' (from /etc/hotplug/usb.usermap) Aug 11 14:07:16 shadowcat /etc/hotplug/usb.agent[18796]: No drivers for 'USB product 90c/1000/2010' (from /etc/hotplug/usb/alsasound.usermap) Aug 11 14:07:16 shadowcat /etc/hotplug/usb.agent[18796]: No drivers for 'USB product 90c/1000/2010' (from /etc/hotplug/usb/sane-hardcoded.usermap) Aug 11 14:07:16 shadowcat /etc/hotplug/usb.agent[18796]: No drivers for 'USB product 90c/1000/2010' (from /etc/hotplug/usb/tascam_fw.usermap) Aug 11 14:07:16 shadowcat /etc/hotplug/usb.agent[18796]: No drivers for 'USB product 90c/1000/2010' (from /etc/hotplug/usb/usbcam.usermap) Here's the contents of debug add files in /events (there are several): The block.add file see my drive file: debug.00271.usb.add.18797 /sbin/hotplugeventrecorder usb LOGPID=18795 DEVPATH=/devices/pci0000:00/0000:00:02.2/usb3/3-2 PATH=/sbin:/bin:/usr/sbin:/usr/bin ACTION=add PWD=/ SHLVL=1 HOME=/ SEQNUM=271 _=/sbin/hotplugeventrecorder file: debug.00272.usb.add.18812 /sbin/hotplugeventrecorder usb LOGPID=18796 DEVPATH=/devices/pci0000:00/0000:00:02.2/usb3/3-2/3-2:1.0 PATH=/sbin:/bin:/usr/sbin:/usr/bin ACTION=add PWD=/ SHLVL=1 HOME=/ DEVICE=/proc/bus/usb/003/007 INTERFACE=8/6/80 PRODUCT=90c/1000/2010 TYPE=0/0/0 SEQNUM=272 _=/sbin/hotplugeventrecorder file: debug.00273.scsi_host.add.18823 /sbin/hotplugeventrecorder scsi_host LOGPID=18822 DEVPATH=/class/scsi_host/host5 PATH=/sbin:/bin:/usr/sbin:/usr/bin ACTION=add PWD=/ SHLVL=1 HOME=/ SEQNUM=273 _=/sbin/hotplugeventrecorder file: debug.00274.scsi.add.18835 /sbin/hotplugeventrecorder scsi LOGPID=18833 DEVPATH=/devices/pci0000:00/0000:00:02.2/usb3/3-2/3-2:1.0/host5/5:0:0:0 PATH=/sbin:/bin:/usr/sbin:/usr/bin ACTION=add PWD=/ SHLVL=1 HOME=/ SEQNUM=274 _=/sbin/hotplugeventrecorder file: debug.00275.block.add.18843 /sbin/hotplugeventrecorder block LOGPID=18834 DEVPATH=/block/sda PATH=/sbin:/bin:/usr/sbin:/usr/bin ACTION=add PWD=/ SHLVL=1 HOME=/ SEQNUM=275 _=/sbin/hotplugeventrecorder file: debug.00276.block.add.18889 /sbin/hotplugeventrecorder block LOGPID=18886 DEVPATH=/block/sda/sda1 PATH=/sbin:/bin:/usr/sbin:/usr/bin ACTION=add PWD=/ SHLVL=1 HOME=/ SEQNUM=276 _=/sbin/hotplugeventrecorder file: debug.00277.scsi_device.add.18896 /sbin/hotplugeventrecorder scsi_device LOGPID=18887 DEVPATH=/class/scsi_device/5:0:0:0 PATH=/sbin:/bin:/usr/sbin:/usr/bin ACTION=add PWD=/ SHLVL=1 HOME=/ SEQNUM=277 _=/sbin/hotplugeventrecorder file: debug.00278.scsi_generic.add.18909 /sbin/hotplugeventrecorder scsi_generic LOGPID=18888 DEVPATH=/class/scsi_generic/sg0 PATH=/sbin:/bin:/usr/sbin:/usr/bin ACTION=add PWD=/ SHLVL=1 HOME=/ SEQNUM=278
participants (8)
-
C. Richard Matson -
Fred Miller -
James Knott -
John Coldrick -
John Scott -
Kastus -
Steve King -
ti＠amb.org