[Regression] Realtek Card Reader no longer works

[Germán Pabón]

In ubuntu 8.10, my Realtek Card Reader (internal) worked flawlessly. Now, in jaunty, it won't mount no matter what. But it seems that HAL recognize the device, naming it:

Realtek Semiconductor Corp. Mass Storage Device

[Germán Pabón (ninboy)]

uname -a:
Linux laptito 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 x86_64 GNU/Linux

cat /proc/version_signature:
Ubuntu 2.6.28-11.42-generic

lsb_release -rd:
Description: Ubuntu 9.04
Release: 9.04

lsusb | grep 'Realtek'
Bus 001 Device 003: ID 0bda:0158 Realtek Semiconductor Corp. Mass Storage Device

[Peter Kossek (kossek)]

Exactly the same here on 32-bit Ubuntu 9.04.
dmesg shows no messages when inserting SD-Card.

uname -a:
Linux peter-laptop 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686 GNU/Linux

cat /proc/version_signature:
Ubuntu 2.6.28-11.42-generic

lsb_release -rd:
Description: Ubuntu 9.04
Release: 9.04

lsusb | grep Realtek:
Bus 001 Device 002: ID 0bda:0158 Realtek Semiconductor Corp. Mass Stroage Device

[Germán Pabón (ninboy)]

By the way, my lsusb shows "Stroage" instead of "Storage" too, Reported in bug #367082

[Aleksandr (aleksandr-andreev)]

Exactly the same here on 64-bit Ubuntu 9.04.

sudo lsusb -d 0bda:0158 -v

Bus 002 Device 003: ID 0bda:0158 Realtek Semiconductor Corp. Mass Stroage Device
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 2.00
  bDeviceClass 0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 64
  idVendor 0x0bda Realtek Semiconductor Corp.
  idProduct 0x0158 Mass Stroage Device
  bcdDevice 58.87
  iManufacturer 1 Generic
  iProduct 2 USB2.0-CRW
  iSerial 3 20071114173400000
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 32
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 4 CARD READER
    bmAttributes 0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower 500mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 2
      bInterfaceClass 8 Mass Storage
      bInterfaceSubClass 6 SCSI
      bInterfaceProtocol 80 Bulk (Zip)
      iInterface 5 Bulk-In, Bulk-Out, Interface
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x01 EP 1 OUT
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0200 1x 512 bytes
        bInterval 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x82 EP 2 IN
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0200 1x 512 bytes
        bInterval 0
Device Qualifier (for other device speed):
  bLength 10
  bDescriptorType 6
  bcdUSB 2.00
  bDeviceClass 0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 64
  bNumConfigurations 1
Device Status: 0x0000
  (Bus Powered)

[Scott Campbell (scottmartincampbell)]

I had the same problem, but as per http://hardware4linux.info/component/33167/, which suggested that this is handled with the usb-storage module. I loaded the usb-storage module and Jaunty instantly recognized a card and mounted it.

[Germán Pabón (ninboy)]

Same fix that bug #42970

[Germán Pabón (ninboy)]

Sorry, bad comment.
Fix as said by Scott. Load usb-storage module.

In root shell (sudo -s), write and remount

echo "usb-storage" >> /etc/modules; modprobe usb-storage

[Peter Kossek (kossek)]

Thanks for the explaining how to get this to work, Germán and Scott.
Works great now!

[actionparsnip (andrew-woodhead666)]

echo "usb-storage" | sudo tee -a /etc/modules; modprobe usb-storage

Bit easier