(Please CC me in replie,s if it's not too much trouble.)
I had this issue with previous kernels, but I don't know when the
problem
started. I once was able to read this card.
Not sure what filesystems are on either card, not sure if it matters.
The cards are not mounted automatically so I am guessing that the
file system doesn't become an issue until mount time.
The device is a Phison 6-in-1 and has no problems with
other cards.
When inserted this card causes no problems:
This is a 128MB card:
Jan 10 10:47:06 kernel: uba: uba1
When the next card is inserted the keyboard partially locks up, the
special laptop keys work still.
e.g. the fn-contrast up/dn works still but not other keys work
Removing the card returns things to as before insertion.
This is a 64MB card from a phone:
Jan 10 10:54:44 kernel: ubc: ubc1
Jan 10 10:54:44 kernel: usb 3-1: reset full speed USB device using
ohci_hcd and address 4
Jan 10 10:54:51 kernel: usb 3-1: reset full speed USB device using
ohci_hcd and address 4
Jan 10 10:54:52 kernel: __ratelimit: 22 callbacks suppressed
Jan 10 10:55:00 kernel: usb 3-1: reset full speed USB device using
ohci_hcd and address 4
Jan 10 10:55:16 kernel: ubc: ubc1
Jan 10 10:55:16 kernel: usb 3-1: reset full speed USB device using
ohci_hcd and address 4
Jan 10 10:55:23 kernel: usb 3-1: reset full speed USB device using
ohci_hcd and address 4
Jan 10 10:55:24 kernel: __ratelimit: 9 callbacks suppressed
Jan 10 10:55:32 kernel: usb 3-1: reset full speed USB device using
ohci_hcd and address 4
Jan 10 10:55:56 kernel: usb 3-1: reset full speed USB device using
ohci_hcd and address 4
Jan 10 10:56:44 kernel: ubc: ubc1
Jan 10 10:56:44 kernel: usb 3-1: reset full speed USB device using
ohci_hcd and address 4
Jan 10 10:56:51 kernel: usb 3-1: reset full speed USB device using
ohci_hcd and address 4
Jan 10 10:56:52 kernel: __ratelimit: 22 callbacks suppressed
Jan 10 10:57:00 kernel: usb 3-1: reset full speed USB device using
ohci_hcd and address 4
lspci:
00:02.0 USB Controller: nVidia Corporation nForce3 USB 1.1 (rev a5)
00:02.1 USB Controller: nVidia Corporation nForce3 USB 1.1 (rev a5)
00:02.2 USB Controller: nVidia Corporation nForce3 USB 2.0 (rev a2)
rhubbell wrote:
> (Please CC me in replie,s if it's not too much trouble.)
>
> I had this issue with previous kernels, but I don't know when the
> problem
> started. I once was able to read this card.
>
> Not sure what filesystems are on either card, not sure if it matters.
> The cards are not mounted automatically so I am guessing that the
> file system doesn't become an issue until mount time.
>
> The device is a Phison 6-in-1 and has no problems with
> other cards.
>
> When inserted this card causes no problems:
>
> This is a 128MB card:
>
> Jan 10 10:47:06 kernel: uba: uba1
Looks like your kernel is configured to use the ub "low performance USB
storage" driver, you could try the normal USB storage driver instead..
>
>
> When the next card is inserted the keyboard partially locks up, the
> special laptop keys work still.
> e.g. the fn-contrast up/dn works still but not other keys work
>
> Removing the card returns things to as before insertion.
>
> This is a 64MB card from a phone:
>
> Jan 10 10:54:44 kernel: ubc: ubc1
> Jan 10 10:54:44 kernel: usb 3-1: reset full speed USB device using
> ohci_hcd and address 4
> Jan 10 10:54:51 kernel: usb 3-1: reset full speed USB device using
> ohci_hcd and address 4
> Jan 10 10:54:52 kernel: __ratelimit: 22 callbacks suppressed
> Jan 10 10:55:00 kernel: usb 3-1: reset full speed USB device using
> ohci_hcd and address 4
> Jan 10 10:55:16 kernel: ubc: ubc1
> Jan 10 10:55:16 kernel: usb 3-1: reset full speed USB device using
> ohci_hcd and address 4
> Jan 10 10:55:23 kernel: usb 3-1: reset full speed USB device using
> ohci_hcd and address 4
> Jan 10 10:55:24 kernel: __ratelimit: 9 callbacks suppressed
> Jan 10 10:55:32 kernel: usb 3-1: reset full speed USB device using
> ohci_hcd and address 4
> Jan 10 10:55:56 kernel: usb 3-1: reset full speed USB device using
> ohci_hcd and address 4
> Jan 10 10:56:44 kernel: ubc: ubc1
> Jan 10 10:56:44 kernel: usb 3-1: reset full speed USB device using
> ohci_hcd and address 4
> Jan 10 10:56:51 kernel: usb 3-1: reset full speed USB device using
> ohci_hcd and address 4
> Jan 10 10:56:52 kernel: __ratelimit: 22 callbacks suppressed
> Jan 10 10:57:00 kernel: usb 3-1: reset full speed USB device using
> ohci_hcd and address 4
>
> lspci:
>
> 00:02.0 USB Controller: nVidia Corporation nForce3 USB 1.1 (rev a5)
> 00:02.1 USB Controller: nVidia Corporation nForce3 USB 1.1 (rev a5)
> 00:02.2 USB Controller: nVidia Corporation nForce3 USB 2.0 (rev a2)
>
>
rhubbell wrote:
> On Sat, 2009-01-10 at 17:55 -0600, Robert Hancock wrote:
>> rhubbell wrote:
>>> (Please CC me in replie,s if it's not too much trouble.)
>>>
>>> I had this issue with previous kernels, but I don't know when the
>>> problem
>>> started. I once was able to read this card.
>>>
>>> Not sure what filesystems are on either card, not sure if it matters.
>>> The cards are not mounted automatically so I am guessing that the
>>> file system doesn't become an issue until mount time.
>>>
>>> The device is a Phison 6-in-1 and has no problems with
>>> other cards.
>>>
>>> When inserted this card causes no problems:
>>>
>>> This is a 128MB card:
>>>
>>> Jan 10 10:47:06 kernel: uba: uba1
>> Looks like your kernel is configured to use the ub "low performance USB
>> storage" driver, you could try the normal USB storage driver instead..
>
> Are you suggesting that the two drivers can't coexist?
>
> Patched to 2.6.29-rc1 and I've rebuilt the kernel without ub and now
> when I try to mount, it is unable to find a readable card. While the
> other card works fine still.
What dmesg output are you getting now?
rhubbell wrote:
> Darn, I meant to respond to the list also.
> Anyway there is no dmesg output for the card.
> The dmesg output looks correct with the 128MB card.
>
> Here's for the 128:
> scsi0 : SCSI emulation for USB Mass Storage devices
> usb-storage: device found at 2
> usb-storage: waiting for device to settle before scanning
> scsi 0:0:0:0: Direct-Access USB Card Reader 1.01 PQ: 0 ANSI: 0 CCS
> sd 0:0:0:0: [sda] 251904 512-byte hardware sectors: (128 MB/123 MiB)
> sd 0:0:0:0: [sda] Write Protect is off
> sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
> sd 0:0:0:0: [sda] Assuming drive cache: write through
> sd 0:0:0:0: [sda] 251904 512-byte hardware sectors: (128 MB/123 MiB)
> sd 0:0:0:0: [sda] Write Protect is off
> sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
> sd 0:0:0:0: [sda] Assuming drive cache: write through
> sda: sda1
> sd 0:0:0:0: [sda] Attached SCSI removable disk
> sd 0:0:0:0: Attached scsi generic sg0 type 0
> usb-storage: device scan complete
That output seems rather normal.. If you're not getting anything like
that with the other card though, I would tend to suspect some kind of
issue with the card, the reader or some kind of incompatibility between
them. Certainly all the USB resets from the other output would tend to
suggest the reader isn't responding properly with that card installed..
On Tue, 2009-01-13 at 21:31 -0600, Robert Hancock wrote:
> rhubbell wrote:
> > Darn, I meant to respond to the list also.
> > Anyway there is no dmesg output for the card.
> > The dmesg output looks correct with the 128MB card.
> >
> > Here's for the 128:
> > scsi0 : SCSI emulation for USB Mass Storage devices
> > usb-storage: device found at 2
> > usb-storage: waiting for device to settle before scanning
> > scsi 0:0:0:0: Direct-Access USB Card Reader 1.01 PQ: 0 ANSI: 0 CCS
> > sd 0:0:0:0: [sda] 251904 512-byte hardware sectors: (128 MB/123 MiB)
> > sd 0:0:0:0: [sda] Write Protect is off
> > sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
> > sd 0:0:0:0: [sda] Assuming drive cache: write through
> > sd 0:0:0:0: [sda] 251904 512-byte hardware sectors: (128 MB/123 MiB)
> > sd 0:0:0:0: [sda] Write Protect is off
> > sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
> > sd 0:0:0:0: [sda] Assuming drive cache: write through
> > sda: sda1
> > sd 0:0:0:0: [sda] Attached SCSI removable disk
> > sd 0:0:0:0: Attached scsi generic sg0 type 0
> > usb-storage: device scan complete
>
> That output seems rather normal.. If you're not getting anything like
> that with the other card though, I would tend to suspect some kind of
> issue with the card, the reader or some kind of incompatibility between
> them. Certainly all the USB resets from the other output would tend to
> suggest the reader isn't responding properly with that card installed..
I found another SD card and I am unable to read that.
I suppose the reader could have a problem, although it's fairly
simple, the led indicator blinks on card insertion.
The card did read in a PS3. Will try another reader.
After just replying to this... I plugged the card reader
into the PS3 and can read both SD cards, no problem.
It does seem to point back to the kernel.
I'll try to figure out how to get more info out of the USB bus.
Enable verbose for starters and see where that goes.
On Tue, 2009-01-13 at 21:31 -0600, Robert Hancock wrote:
> rhubbell wrote:
> > Darn, I meant to respond to the list also.
> > Anyway there is no dmesg output for the card.
> > The dmesg output looks correct with the 128MB card.
> >
> > Here's for the 128:
> > scsi0 : SCSI emulation for USB Mass Storage devices
> > usb-storage: device found at 2
> > usb-storage: waiting for device to settle before scanning
> > scsi 0:0:0:0: Direct-Access USB Card Reader 1.01 PQ: 0 ANSI: 0 CCS
> > sd 0:0:0:0: [sda] 251904 512-byte hardware sectors: (128 MB/123 MiB)
> > sd 0:0:0:0: [sda] Write Protect is off
> > sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
> > sd 0:0:0:0: [sda] Assuming drive cache: write through
> > sd 0:0:0:0: [sda] 251904 512-byte hardware sectors: (128 MB/123 MiB)
> > sd 0:0:0:0: [sda] Write Protect is off
> > sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
> > sd 0:0:0:0: [sda] Assuming drive cache: write through
> > sda: sda1
> > sd 0:0:0:0: [sda] Attached SCSI removable disk
> > sd 0:0:0:0: Attached scsi generic sg0 type 0
> > usb-storage: device scan complete
>
> That output seems rather normal.. If you're not getting anything like
> that with the other card though, I would tend to suspect some kind of
> issue with the card, the reader or some kind of incompatibility between
> them. Certainly all the USB resets from the other output would tend to
> suggest the reader isn't responding properly with that card installed..