Skip to contentSkip to conversation

UDEV : ASUS Laptop G73S MultiCard Reader

DISCUSSION Postmaster 2 participants 4 messages Jul 16, 2011 – Jul 17, 2011

lore
Share & tools
lore

Postmaster

author
#0 lore raw

my laptop comes with an internal Realtek card reader ( vendor=0x0bda, product=0x0139 )

It is not recognized by udevd.

The bInterface class is 255, which I think is wrong ( should be 8 for mass storage device, i think )

Right now the kern does not assign this device to usb-storage. The realtek driver is nice, but the product id of 0x0138 does not match this productid 0f 0x0139.

How are the udev hooks supposed to work to rename the bInterface class from vendor specific to mass storage/realtek driver?

============LSUSB -v =================

Bus 001 Device 004: ID 0bda:0139 Realtek Semiconductor Corp. USB 2.0 multicard reader
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00

   bDeviceClass          255 Vendor Specific Class
   bDeviceSubClass       255 Vendor Specific Subclass
   bDeviceProtocol       255 Vendor Specific Protocol
   bMaxPacketSize0        64
   idVendor           0x0bda Realtek Semiconductor Corp.
   idProduct          0x0139 USB 2.0 multicard reader
   bcdDevice           39.60
   iManufacturer           1 Generic
   iProduct                2 USB2.0-CRW
   iSerial                 3 20100201396000000
   bNumConfigurations      1

Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 39
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 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 6
bInterfaceProtocol 80
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
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0003 1x 3 bytes
bInterval 10
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)

[root@Asus gat]#

#1 lore raw
Quoted 7 lines · Postmaster

my laptop comes with an internal Realtek card reader ( vendor=0x0bda, product=0x0139 )

It is not recognized by udevd.

The bInterface class is 255, which I think is wrong ( should be 8 for mass storage device, i think )

If so, that's the device problem, nothing you can do from the kernel, or from udev, to change that. See the USB spec for details.

Quoted 3 lines

Right now the kern does not assign this device to usb-storage. The realtek driver is nice, but the product id of 0x0138 does not match this productid 0f 0x0139.

That is because this is a different device, and it says it is a vendor-specific protocol, which will not work with the usb-storage driver, sorry.

greg k-h

author
#2 lore raw
In reply to Postmaster
Quoted 4 lines

That is because this is a different device, and it says it is a vendor-specific protocol, which will not work with the usb-storage driver, sorry.

I Disagree with most of what u suggest.

Who knows what vendor specific means. And you really wont know until you try. Which is why there are tables to handle Unusual Devices.

At this time there is a realtek driver in the latest kern code. I would like to load up this driver when usb-core detects this device.

Right now, I have not found the udev rule for loading up usb-storage.

So where are the udev system specs

BTW: is there a way to disable, and enable the device? Since this usb device is internal, if I have too many "printk" or DBG messages at boot-up time, it tends to overflow the rsyslogd daemon.

btw#2 where is this forum? All one sees in the written docs is to email questions, rather than post questions to a forum.

#3 lore raw
In reply to Postmaster
Quoted 6 lines · Postmaster
Quoted 4 lines

That is because this is a different device, and it says it is a vendor-specific protocol, which will not work with the usb-storage driver, sorry.

I Disagree with most of what u suggest.

I'm sorry to hear that.

Quoted 2 lines

Who knows what vendor specific means. And you really wont know until you try. Which is why there are tables to handle Unusual Devices.

If a vendor says it is not a mass-storage device, why do you think they are lying? And the term, "vendor specific" has a very specific definition, see the USB specification if you are curious as to what it is.

Quoted 4 lines

At this time there is a realtek driver in the latest kern code. I would like to load up this driver when usb-core detects this device.

Right now, I have not found the udev rule for loading up usb-storage.

There is no such rule, the usb device id causes it to happen through modprobe of the module alias of the device.

Quoted 1 line

So where are the udev system specs

This is not something that udev does at all, sorry.

Quoted 6 lines

BTW: is there a way to disable, and enable the device? Since this usb device is internal, if I have too many "printk" or DBG messages at boot-up time, it tends to overflow the rsyslogd daemon.

btw#2 where is this forum? All one sees in the written docs is to email questions, rather than post questions to a forum.

Yes, this is done through email, not a web forum.

greg k-h