Unfortunately, there is no good way to programmatically detect this failure condition. It's only obvious when you know that it's SD-like media (no way to detect that), that the media is large (no way to detect that), and you see one of several unusual behaviors (not all of which are detectable). As for recognizing the vendor -- there are 3 separate places where this information is encoded. One is as the idVendor value, which you can see in lsusb; I don't recall if lsusb will translate that number into names (ala lspci), but you should address this with the lsusb people. The 2nd place is in the device descriptor strings. Those appear to be blank on this device. The 3rd place is in the INQUIRY command response. Those appear to say "Direct Access" as the vendor name (which is not terribly uncommon). Matt On Sun, Dec 23, 2012 at 1:24 PM, rh <richard_hubbe11@xxxxxxxxxxx> wrote: > On Sun, 23 Dec 2012 11:45:31 -0800 > Matthew Dharm > <mdharm-usb@xxxxxxxxxxxxxxxxxx> wrote: > >> The breakpoint between SDSC and SDHC is, in fact, 4GB for 512-byte >> sectors. So, your data supports my theory that your cardreader is >> non-SDHC compatible. > > I tried the 4GB microSD and the symptoms were the same as for the > 16GB. It's not graceful but at least it doesn't crash the box. > Trying to mount just hangs there for a long time. Might be merciful > to print out a useful message when this situation is encountered, > if that's possible. > > Why isn't the vendor recognized? It was in the past. > i.e. plugging in the card reader with no cards inserted returned > the correct vendor in the past. > >> >> Matt >> >> On Sun, Dec 23, 2012 at 11:19 AM, rh >> <richard_hubbe11@xxxxxxxxxxx> wrote: >> > On Sun, 23 Dec 2012 11:01:28 -0800 >> > Matthew Dharm >> > <mdharm-usb@xxxxxxxxxxxxxxxxxx> >> > wrote: >> > >> >> If I had to guess, it looks like you have an SDHC card in an older >> >> SDSC reader. The older readers can't read the higher-capacity SDHC >> >> cards. >> >> >> >> Try the reader/card combo on a recent windows system to see if they >> >> are compatible. Or, look for a specific SDHC or SDXC compatibility >> >> marking on the reader. >> > >> > I tried to read it on a mac but "disk utility" wasn't able to do >> > anything. I forget the specifics but I could do nothing with it on >> > the mac. >> > >> > But I was able to read a 2GB microSD so is it a ~4GB issue? >> > Hmm I might have a 4GB microSD, will try that. >> > >> > Something else I realized is that at some point in the past the >> > kernel recognized the vendor as Phison but does not anymore. >> > >> > >> >> >> >> Matt >> >> >> >> On Sun, Dec 23, 2012 at 10:26 AM, rh >> >> <richard_hubbe11@xxxxxxxxxxx> wrote: >> >> > I don't use this device often so I don't know if this combination >> >> > ever worked in previous kernels. I was trying to read a 16GB >> >> > microSD card. The hub claims to be able to read MicroDrive, >> >> > SmartMedia, CompactFlash, Memory Stick, Multimedia and Secure >> >> > Digital. (reading from the label on the device) >> >> > >> >> > FWIW 16GB == 16*1000*1000*1000 >> >> > >> >> > From http://www.linux-usb.org/usb.ids: >> >> > (couldn't find this in the kernel source) >> >> > >> >> > 0d7d Phison Electronics Corp. >> >> > 0240 I/O-Magic/Transcend 6-in-1 Card Reader >> >> > >> >> > >> >> > kernel version 3.6.7 >> >> > >> >> > [367851.023224] usb 3-1: new full-speed USB device number 13 >> >> > using ohci_hcd [367851.180145] usb 3-1: New USB device found, >> >> > idVendor=0d7d, idProduct=0240 [367851.180145] usb 3-1: New USB >> >> > device strings: Mfr=1, Product=2, SerialNumber=3 [367851.180145] >> >> > usb 3-1: Product: USB Reader [367851.180145] usb 3-1: >> >> > Manufacturer: >> >> > >> >> > [367851.183145] scsi7 : usb-storage 3-1:1.0 >> >> > [367852.191812] scsi 7:0:0:0: Direct-Access USB Card >> >> > Reader 1.01 PQ: 0 ANSI: 0 CCS [367852.199885] scsi 7:0:0:1: >> >> > Direct-Access USB Card Reader 1.01 PQ: 0 ANSI: 0 >> >> > CCS [367852.207145] scsi 7:0:0:2: Direct-Access USB >> >> > Card Reader 1.01 PQ: 0 ANSI: 0 CCS [367852.214146] scsi 7:0:0:3: >> >> > Direct-Access USB Card Reader 1.01 PQ: 0 ANSI: 0 >> >> > CCS [367852.216145] sd 7:0:0:0: Attached scsi generic sg2 type 0 >> >> > [367852.216565] sd 7:0:0:1: Attached scsi generic sg3 type 0 >> >> > [367852.216565] sd 7:0:0:2: Attached scsi generic sg4 type 0 >> >> > [367852.216565] sd 7:0:0:3: Attached scsi generic sg5 type 0 >> >> > [367856.886551] sd 7:0:0:2: [sdd] 1 512-byte logical blocks: (512 >> >> > B/512 B) [367856.923227] sd 7:0:0:2: [sdd] Write Protect is on >> >> > [367856.923227] sd 7:0:0:2: [sdd] Mode Sense: 43 00 80 00 >> >> > [367856.963227] sd 7:0:0:2: [sdd] No Caching mode page present >> >> > [367856.963227] sd 7:0:0:2: [sdd] Assuming drive cache: write >> >> > through [367856.987033] sd 7:0:0:0: [sdb] Attached SCSI removable >> >> > disk [367857.026551] sd 7:0:0:1: [sdc] Attached SCSI removable >> >> > disk [367857.046033] sd 7:0:0:3: [sde] Attached SCSI removable >> >> > disk [367857.073217] sd 7:0:0:2: [sdd] No Caching mode page >> >> > present [367857.073217] sd 7:0:0:2: [sdd] Assuming drive cache: >> >> > write through [367888.136553] usb 3-1: reset full-speed USB >> >> > device number 13 using ohci_hcd [367903.259389] usb 3-1: device >> >> > descriptor read/64, error -110 [367918.479883] usb 3-1: device >> >> > descriptor read/64, error -110 [367918.705930] usb 3-1: reset >> >> > full-speed USB device number 13 using ohci_hcd [367933.823216] >> >> > usb 3-1: device descriptor read/64, error -110 [367949.046547] >> >> > usb 3-1: device descriptor read/64, error -110 [367949.269880] >> >> > usb 3-1: reset full-speed USB device number 13 using ohci_hcd >> >> > [367954.286566] usb 3-1: device descriptor read/8, error -110 >> >> > [367959.406541] usb 3-1: device descriptor read/8, error -110 >> >> > [367959.626547] usb 3-1: reset full-speed USB device number 13 >> >> > using ohci_hcd [367964.643891] usb 3-1: device descriptor >> >> > read/8, error -110 [367969.760640] usb 3-1: device descriptor >> >> > read/8, error -110 [367969.863211] usb 3-1: USB disconnect, >> >> > device number 13 [367969.863211] sd 7:0:0:2: Device offlined - >> >> > not ready after error recovery [367969.863211] sd 7:0:0:2: [sdd] >> >> > Unhandled error code [367969.863211] sd 7:0:0:2: [sdd] >> >> > [367969.863211] Result: hostbyte=0x05 driverbyte=0x00 >> >> > [367969.863211] sd 7:0:0:2: [sdd] CDB: [367969.863211] cdb >> >> > [0]=0x28: 28 00 00 00 00 00 00 00 01 00 [367969.863211] >> >> > end_request: I/O error, dev sdd, sector 0 [367969.863211] Buffer >> >> > I/O error on device sdd, logical block 0 [367969.863211] sd >> >> > 7:0:0:2: rejecting I/O to offline device [367969.863211] sd >> >> > 7:0:0:2: rejecting I/O to offline device [367969.863211] sdd: >> >> > unable to read partition table [367969.863211] sd 7:0:0:2: [sdd] >> >> > Attached SCSI removable disk [367969.986545] usb 3-1: new >> >> > full-speed USB device number 14 using ohci_hcd [367985.106543] >> >> > usb 3-1: device descriptor read/64, error -110 [368000.333203] >> >> > usb 3-1: device descriptor read/64, error -110 [368000.553209] >> >> > usb 3-1: new full-speed USB device number 15 using ohci_hcd >> >> > [368015.673576] usb 3-1: device descriptor read/64, error -110 >> >> > [368030.896541] usb 3-1: device descriptor read/64, error -110 >> >> > [368031.120164] usb 3-1: new full-speed USB device number 16 >> >> > using ohci_hcd [368036.137539] usb 3-1: device descriptor >> >> > read/8, error -110 [368038.334981] usb 3-1: device descriptor >> >> > read/8, error -62 [368038.489866] hub 3-0:1.0: unable to >> >> > enumerate USB device on port 1 >> >> > >> >> > -- >> >> > 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 >> >> >> >> >> >> >> >> -- >> >> Matthew Dharm >> >> Maintainer, USB Mass Storage driver for Linux >> >> -- >> >> 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 >> >> >> > >> > >> > -- >> > >> > >> > -- >> > 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 >> >> >> >> -- >> Matthew Dharm >> Maintainer, USB Mass Storage driver for Linux >> -- >> 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 >> > > > -- > > > -- > 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 -- Matthew Dharm Maintainer, USB Mass Storage driver for Linux -- 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
