This is wierd. I've got a multicard reader installed on my Fedora 14 system. If I insert an SD card, it gets recognized and mounted right away. If I unmount the card, remove it, and reinsert it, the system does nothing. No entries in the messages file about the device or anything. If I want to use the SD card again, I have to reboot.
Has anyone seen something like this before? Ideas on how to debug the problem?
Gordon Charrick <gordonmc <at> cox.net> writes:
This is wierd. I've got a multicard reader installed on my Fedora 14 system. If I insert an SD card, it gets recognized and mounted right away. If I unmount the card, remove it, and reinsert it, the system does nothing. No entries in the messages file about the device or anything. If I want to use the SD card again, I have to reboot.
Has anyone seen something like this before? Ideas on how to debug the problem?
If you could provide some more info it would be helpful.
Regarding your multicard reader - is it a built-in device or an external device (USB I assume) ? Start from the very beginning by rebooting your machine with the reader. Show us that part of dmesg where the reader got recognized. Also, if a USB device, show us: $ lsusb $ lsusb -v -d vendor:productID where vendor:productID obtained from lsusb
Now, insert your SD (it gets mounted, you say). Show us: $ mount
Then, when you say you unmount it, do you do it in Nautilus or manually in term ?
After that, check once again: $ mount and check if your card reader is still recognized by the system: $ lsusb Also check anything related in: # tail /var/log/messages
JB
On Sunday, March 06, 2011 01:49:20 pm Gordon Charrick wrote:
This is wierd. I've got a multicard reader installed on my Fedora 14 system. If I insert an SD card, it gets recognized and mounted right away. If I unmount the card, remove it, and reinsert it, the system does nothing. No entries in the messages file about the device or anything. If I want to use the SD card again, I have to reboot.
Has anyone seen something like this before? Ideas on how to debug the problem?
Yes, I have seen it, in GNOME and in KDE, a few times. I predominantly use KDE, and it seems to be working in KDE now. As in I just put an SD card into the reader, opened it in dolphin, and used the dolphin 'safely remove' option; pulled the SD card from the reader, waited a few seconds (10 or so; log tells me it was 9), plugged the card back in, and it came right up.
A client of mine who is still at Fedora 13 and is a GNOME user saw this issue, and found this was the way to get it working on his system: "I've tried something different and after 4 times, it's worked every time. What I'm doing now to remove a flash card from the reader, instead of usual - logical "safe to remove" option, try using the "eject" option. Thus far, it seems to be working."
Can you try that and see what happens? (assuming you have an eject option; I'm not a GNOME user, and don't have the full GNOME installed on this box)
I've also found that at least with KDE it seems to always be best to wait until you're logged in and the system has become somewhat quiescent before hotplugging any removable storage; at least my USB 3 external wasn't recognized at all when I booted with it plugged in, and the system refused to see it even after unplugging and replugging, but restarting with it not plugged in, then plugging it in after logging in worked ok. Made me a little nervous at first!
(note for those who didn't see or have forgotten my first message on this: no, USB 3 does not work 'out of the box' with Fedora 14, you do have to do something special, and that something special is documented on the fedoraproject.org website, so if you need the info, go find it there or in the archives of this list.)
(Also note that, yes, I do know my kernel is a rev old; I have installed the updates since, but since i use the nvidia driver, and there was a little bit of delay in delivery of the kmod-nvidia for the update, I set this particular kernel to boot in grub.conf; yes, I do need to set that back now that the updated kmod-nvidia is out there.....)
Here's the relevant /var/log/messages sections (which, since it spanned 5AM, spanned two files, /var/log/messages, and /var/log/messages-20110307) for my SD card swap a few minutes ago: ++++++++++ Mar 7 04:56:31 localhost kernel: [ 1177.005191] sd 2:0:0:0: [sdb] 3842048 512-byte logical blocks: (1.96 GB/1.83 GiB) Mar 7 04:56:31 localhost kernel: [ 1177.005935] sd 2:0:0:0: [sdb] Assuming drive cache: write through Mar 7 04:56:31 localhost kernel: [ 1177.007432] sd 2:0:0:0: [sdb] Assuming drive cache: write through Mar 7 04:56:31 localhost kernel: [ 1177.007438] sdb: sdb1 Mar 7 04:56:40 localhost hald: mounted /dev/sdb1 on behalf of uid 501 Mar 7 05:04:24 localhost hald: unmounted /dev/sdb1 from '/media/disk' on behalf of uid 501 Mar 7 05:13:35 localhost kernel: [ 2200.994365] sd 2:0:0:0: [sdb] 3842048 512-byte logical blocks: (1.96 GB/1.83 GiB) Mar 7 05:13:35 localhost kernel: [ 2200.995227] sd 2:0:0:0: [sdb] Assuming drive cache: write through Mar 7 05:13:35 localhost kernel: [ 2200.999476] sd 2:0:0:0: [sdb] Assuming drive cache: write through Mar 7 05:13:35 localhost kernel: [ 2200.999487] sdb: sdb1 Mar 7 05:13:48 localhost hald: mounted /dev/sdb1 on behalf of uid 501 ++++++++
Log sections dealing with the USB 3 drive's issue:
lspci line: 0d:00.0 USB Controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 03)
lsusb line (current working): Bus 006 Device 002: ID 1058:0730 Western Digital Technologies, Inc.
lsusb tree section for bus 6: Bus# 6 `-Dev# 1 Vendor 0x1d6b Product 0x0003 `-Dev# 2 Vendor 0x1058 Product 0x0730
/var/log/messages lines for first, unsuccessful try with disk plugged in at powerup: ++++++++++++++++ Mar 7 04:27:51 localhost kernel: [ 8.509681] xhci_hcd 0000:0d:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19 Mar 7 04:27:51 localhost kernel: [ 8.509925] xhci_hcd 0000:0d:00.0: xHCI Host Controller Mar 7 04:27:51 localhost kernel: [ 8.510650] xhci_hcd 0000:0d:00.0: new USB bus registered, assigned bus number 6 Mar 7 04:27:51 localhost kernel: [ 8.510877] xhci_hcd 0000:0d:00.0: irq 19, io mem 0xdcdfe000 Mar 7 04:27:51 localhost kernel: [ 8.514183] usb usb6: No SuperSpeed endpoint companion for config 1 interface 0 altsetting 0 ep 129: using minimum values Mar 7 04:27:51 localhost kernel: [ 8.514195] usb usb6: New USB device found, idVendor=1d6b, idProduct=0003 Mar 7 04:27:51 localhost kernel: [ 8.514198] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1 Mar 7 04:27:51 localhost kernel: [ 8.514200] usb usb6: Product: xHCI Host Controller Mar 7 04:27:51 localhost kernel: [ 8.514202] usb usb6: Manufacturer: Linux 2.6.35.10-74.fc14.x86_64 xhci_hcd Mar 7 04:27:51 localhost kernel: [ 8.514204] usb usb6: SerialNumber: 0000:0d:00.0 Mar 7 04:27:51 localhost kernel: [ 8.514399] hub 6-0:1.0: USB hub found Mar 7 04:27:51 localhost kernel: [ 8.514404] hub 6-0:1.0: 4 ports detected ++++++++++++
This is the /var/log/messages section when I unplugged the USB3 drive and plugged it back in (into a different port): ++++++++++++ Mar 7 04:32:34 localhost kernel: [ 304.507251] usb 6-3: new high speed USB device using xhci_hcd and address 0 Mar 7 04:32:34 localhost kernel: [ 304.711925] usb 6-3: Device not responding to set address. Mar 7 04:32:34 localhost kernel: [ 304.912293] usb 6-3: Device not responding to set address. Mar 7 04:32:34 localhost kernel: [ 305.113097] usb 6-3: device not accepting address 0, error -71 Mar 7 04:32:34 localhost kernel: [ 305.164158] hub 6-0:1.0: unable to enumerate USB device on port 3 +++++++++++++
And the successful startup of the USB 3 system, including the hotplug of the drive: +++++++++++++ Mar 7 04:37:12 localhost kernel: [ 9.039109] xhci_hcd 0000:0d:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19 Mar 7 04:37:12 localhost kernel: [ 9.039144] xhci_hcd 0000:0d:00.0: xHCI Host Controller Mar 7 04:37:12 localhost kernel: [ 9.039857] xhci_hcd 0000:0d:00.0: new USB bus registered, assigned bus number 6 Mar 7 04:37:12 localhost kernel: [ 9.040097] xhci_hcd 0000:0d:00.0: irq 19, io mem 0xdcdfe000 Mar 7 04:37:12 localhost kernel: [ 9.043389] usb usb6: No SuperSpeed endpoint companion for config 1 interface 0 altsetting 0 ep 129: using minimum values Mar 7 04:37:12 localhost kernel: [ 9.043400] usb usb6: New USB device found, idVendor=1d6b, idProduct=0003 Mar 7 04:37:12 localhost kernel: [ 9.043403] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1 Mar 7 04:37:12 localhost kernel: [ 9.043406] usb usb6: Product: xHCI Host Controller Mar 7 04:37:12 localhost kernel: [ 9.043408] usb usb6: Manufacturer: Linux 2.6.35.10-74.fc14.x86_64 xhci_hcd Mar 7 04:37:12 localhost kernel: [ 9.043410] usb usb6: SerialNumber: 0000:0d:00.0 Mar 7 04:37:12 localhost kernel: [ 9.043604] hub 6-0:1.0: USB hub found Mar 7 04:37:12 localhost kernel: [ 9.043610] hub 6-0:1.0: 4 ports detected Mar 7 04:38:57 localhost kernel: [ 123.347410] usb 6-1: new SuperSpeed USB dev ice using xhci_hcd and address 2 Mar 7 04:38:57 localhost kernel: [ 123.359856] xhci_hcd 0000:0d:00.0: WARN: sh ort transfer on control ep Mar 7 04:38:57 localhost kernel: [ 123.360351] xhci_hcd 0000:0d:00.0: WARN: sh ort transfer on control ep Mar 7 04:38:57 localhost kernel: [ 123.360723] xhci_hcd 0000:0d:00.0: WARN: sh ort transfer on control ep Mar 7 04:38:57 localhost kernel: [ 123.361219] xhci_hcd 0000:0d:00.0: WARN: sh ort transfer on control ep Mar 7 04:38:57 localhost kernel: [ 123.361372] usb 6-1: New USB device found, idVendor=1058, idProduct=0730 Mar 7 04:38:57 localhost kernel: [ 123.361380] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Mar 7 04:38:57 localhost kernel: [ 123.361387] usb 6-1: Product: My Passport 0730 Mar 7 04:38:57 localhost kernel: [ 123.361391] usb 6-1: Manufacturer: Western Digital Mar 7 04:38:57 localhost kernel: [ 123.361396] usb 6-1: SerialNumber: YOUDIDNTTHINKIDLEAVETHISHERE Mar 7 04:38:57 localhost kernel: [ 123.368437] scsi3 : usb-storage 6-1:1.0 Mar 7 04:38:59 localhost kernel: [ 125.434300] scsi 3:0:0:0: Direct-Access WD My Passport 0730 1012 PQ: 0 ANSI: 6 Mar 7 04:38:59 localhost kernel: [ 125.434796] scsi 3:0:0:1: Enclosure WD SES Device 1012 PQ: 0 ANSI: 6 Mar 7 04:38:59 localhost kernel: [ 125.435917] sd 3:0:0:0: Attached scsi generic sg3 type 0 Mar 7 04:38:59 localhost kernel: [ 125.436161] scsi 3:0:0:1: Attached scsi generic sg4 type 13 Mar 7 04:39:03 localhost kernel: [ 128.718774] sd 3:0:0:0: [sdc] 976707584 512-byte logical blocks: (500 GB/465 GiB) Mar 7 04:39:03 localhost kernel: [ 128.719326] sd 3:0:0:0: [sdc] Write Protect is off Mar 7 04:39:03 localhost kernel: [ 128.719333] sd 3:0:0:0: [sdc] Assuming drive cache: write through Mar 7 04:39:03 localhost kernel: [ 128.721317] sd 3:0:0:0: [sdc] Assuming drive cache: write through Mar 7 04:39:03 localhost kernel: [ 128.721326] sdc: sdc1 Mar 7 04:39:03 localhost kernel: [ 128.773814] sd 3:0:0:0: [sdc] Assuming drive cache: write through Mar 7 04:39:03 localhost kernel: [ 128.773820] sd 3:0:0:0: [sdc] Attached SCSI disk Mar 7 04:39:03 localhost kernel: [ 128.849379] ses 3:0:0:1: Attached Enclosure device Mar 7 04:39:03 localhost kernel: [ 128.907884] xhci_hcd 0000:0d:00.0: WARN: Stalled endpoint Mar 7 04:39:07 localhost kernel: [ 133.052043] EXT4-fs (sdc1): mounted filesys tem with ordered data mode. Opts: (null) Mar 7 04:39:07 localhost hald: mounted /dev/sdc1 on behalf of uid 501 +++++++++++++
Honestly, I'd file a bug report if I knew which component to file against. I'm thinking udev here, but I'm not at all sure. I'm going to dig for it, just not today, too many other things on my plate today.
On Monday, March 07, 2011 06:01:10 am Lamar Owen wrote:
Here's the relevant /var/log/messages sections (which, since it spanned 5AM, spanned two files, /var/log/messages, and /var/log/messages-20110307) for my SD card swap a few minutes ago: ++++++++++ Mar 7 04:56:31 localhost kernel: [ 1177.005191] sd 2:0:0:0: [sdb] 3842048 512-byte logical blocks: (1.96 GB/1.83 GiB)
Of course, I forgot a few lines; also, note that some dedicated SD readers aren't hot-swap on the SD side, but only on the USB side; my Targus reader does do hotswap on the SD side: ++++++++++++++++++ Mar 7 04:37:12 localhost kernel: [ 0.952883] ehci_hcd: USB 2.0 'Enhanced' Ho st Controller (EHCI) Driver Mar 7 04:37:12 localhost kernel: [ 0.952914] ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 20 (level, low) -> IRQ 20 Mar 7 04:37:12 localhost kernel: [ 0.952937] ehci_hcd 0000:00:1d.7: EHCI Hos t Controller Mar 7 04:37:12 localhost kernel: [ 0.952997] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1 Mar 7 04:37:12 localhost kernel: [ 0.953026] ehci_hcd 0000:00:1d.7: using br oken periodic workaround Mar 7 04:37:12 localhost kernel: [ 0.953038] ehci_hcd 0000:00:1d.7: debug po rt 1 Mar 7 04:37:12 localhost kernel: [ 0.956943] ehci_hcd 0000:00:1d.7: irq 20, io mem 0xffa80000 Mar 7 04:37:12 localhost kernel: [ 0.966019] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00 Mar 7 04:37:12 localhost kernel: [ 0.966045] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 Mar 7 04:37:12 localhost kernel: [ 0.966048] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 Mar 7 04:37:12 localhost kernel: [ 0.966050] usb usb1: Product: EHCI Host Controller Mar 7 04:37:12 localhost kernel: [ 0.966052] usb usb1: Manufacturer: Linux 2.6.35.10-74.fc14.x86_64 ehci_hcd Mar 7 04:37:12 localhost kernel: [ 0.966054] usb usb1: SerialNumber: 0000:00:1d.7 Mar 7 04:37:12 localhost kernel: [ 1.588066] usb 1-4: new high speed USB device using ehci_hcd and address 4 Mar 7 04:37:12 localhost kernel: [ 1.704395] usb 1-4: New USB device found, idVendor=058f, idProduct=6366 Mar 7 04:37:12 localhost kernel: [ 1.704399] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Mar 7 04:37:12 localhost kernel: [ 1.704403] usb 1-4: Product: Mass Storage Device Mar 7 04:37:12 localhost kernel: [ 1.704405] usb 1-4: Manufacturer: Generic Mar 7 04:37:12 localhost kernel: [ 1.704407] usb 1-4: SerialNumber: 058F63666471 Mar 7 04:37:12 localhost kernel: [ 1.763519] Initializing USB Mass Storage driver... Mar 7 04:37:12 localhost kernel: [ 1.763706] scsi2 : usb-storage 1-4:1.0 Mar 7 04:37:12 localhost kernel: [ 1.763816] usbcore: registered new interface driver usb-storage Mar 7 04:37:12 localhost kernel: [ 1.763819] USB Mass Storage support registered. Mar 7 04:37:12 localhost kernel: [ 2.764068] scsi 2:0:0:0: Direct-Access Multi Flash Reader 1.00 PQ: 0 ANSI: 0 Mar 7 04:37:12 localhost kernel: [ 2.764831] sd 2:0:0:0: Attached scsi gener ic sg2 type 0 Mar 7 04:37:12 localhost kernel: [ 2.767418] sd 2:0:0:0: [sdb] Attached SCSI removable disk [and then the lines I've already posted] +++++++++
On 03/06/2011 12:49 PM, Gordon Charrick wrote:
This is wierd. I've got a multicard reader installed on my Fedora 14 system. If I insert an SD card, it gets recognized and mounted right away. If I unmount the card, remove it, and reinsert it, the system does nothing. No entries in the messages file about the device or anything. If I want to use the SD card again, I have to reboot.
Has anyone seen something like this before? Ideas on how to debug the problem?
Dumb question - are you unmounting it, or using safely remove hardware. In the later case, it is not uncommon for the entire reader to be turned off.
For an external reader, you can unplug it, and plug it back in. For an internal reader, you may be able to get it working again by running, as root:
modprobe -r usb_storage ; modprobe usb_storage
If you have other devices using the usb_storage module, it is not going to let you remove the module.
Mikkel
-
Gordon Charrick -
JB -
Lamar Owen -
Mikkel