On Thu, 19 Apr 2012, gene heskett wrote: > On Thursday, April 19, 2012 12:27:43 PM Alan Stern did opine: > > > On Thu, 19 Apr 2012, gene heskett wrote: > > > I bought one last night, a 4Gb Sandisk, that isn't accessible in the > > > device it is supposed to work in, nor is it configured beyond the > > > discovery that something got plugged into my card interface, an > > > FCR22. > > > > > > Bad card, or no support? > > > > > > I need a clue if there are any here. > > > > Not all card readers can handle SDHC cards. Older ones work only with > > SD cards. > > > > But without debugging info, there's no way to tell if that's really > > your problem. > > > > Alan Stern > > Plugging the whole reader assembly with the card pre-inserted, dmesg > fiddles around for 2-3 minutes and finally does this: What happens during those 2-3 minutes? > ehci_hcd 0000:00:02.1: port 5 full speed --> companion > ehci_hcd 0000:00:02.1: GetStatus port:5 status 003001 0 ACK POWER OWNER > sig=se0 CONNECT > hub 1-0:1.0: port 5 not reset yet, waiting 50ms > hub 1-0:1.0: state 7 ports 10 chg 0000 evt 0020 > ehci_hcd 0000:00:02.1: GetStatus port:5 status 001002 0 ACK POWER sig=se0 > CSC > hub 1-0:1.0: logical disconnect on port 5 > hub 1-0:1.0: state 7 ports 10 chg 0020 evt 0020 > hub 1-0:1.0: port 5, status 0100, change 0000, 12 Mb/s > usb 1-5: USB disconnect, device number 53 > usb 1-5: unregistering device > usb 1-5: unregistering interface 1-5:1.0 > usb 1-5: usb_disable_device nuking all URBs This looks like the aftermath of a failed reset. > Device #53 was in the first line or so of the discovery output, way back up > the dmesg output by 100 lines or more. Unplugging the sd card and > replugging it, doesn't generate any more output at all. > > I've had this card reader for 4 or 5 years, so I'll get another after > reading the fine print. Yeah. You might first want to try making sure this reader still works with a card you know it was able to read in the past. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
