From: Larry Finger <Larry.Finger@lwfinger.net>
To: Michael Wu <flamingice@sourmilk.net>,
wireless <linux-wireless@vger.kernel.org>
Subject: Problems with RTL8187 USB device
Date: Tue, 26 Feb 2008 16:13:37 -0700 [thread overview]
Message-ID: <47C49D21.1030905@lwfinger.net> (raw)
After the BCM4311 that is built-in on my laptop failed, I bought a USB wi-fi device to use until I
get my laptop fixed. Based on suggestions from the wireless mailing list, I bought one with an
RTL8187 chip. Naturally, I am having problems getting it working.
First of all, the device works with Windows - thus it is OK.
The device is manufactured by "Level 1". The FCC ID is NDD9573160714 and it has the identifying code
of WNC-0301USB07091001070-V5.
The output of 'lsusb -v' for this device when run as root is
Bus 001 Device 002: ID 0bda:8187 Realtek Semiconductor Corp.
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 0x8187
bcdDevice 2.00
iManufacturer 1 Manufacturer_Realtek
iProduct 2 RTL8187B_WLAN_Adapter
iSerial 3 00e04c000001
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 81
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 4 Wireless Network Card
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 9
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 2 RTL8187B_WLAN_Adapter
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 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 0x04 EP 4 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 0x05 EP 5 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 0x06 EP 6 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 0x07 EP 7 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 0x89 EP 9 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 0x0a EP 10 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 0x0b EP 11 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 0x0c EP 12 OUT
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)
Using kernel 2.6.25-rc3 from Linus's tree, the following appear in dmesg output:
usb 1-6: new high speed USB device using ehci_hcd and address 2
usb 1-6: configuration #1 chosen from 1 choice
phy0: Selected rate control algorithm 'pid'
phy0: hwaddr 00:11:6b:3e:c2:79, rtl8187 V0 + rtl8225
usbcore: registered new interface driver rtl8187
udev: renamed network interface wlan0 to eth2
phy0: RF Calibration Failed! 0 in rtl8225_rf_init
The wireless device appears in the iwconfig and ifconfig lists, but no scan data are received.
When I try to use the device with a kernel from the 'everything' branch of Linville's tree, the
machine crashes with a blinking caps lock key indicating a kernel panic. I have not succeeded in
capturing a netconsole dump for this situation.
What additional information besides the netconsole dump would be useful in sorting out these problems?
Thanks,
Larry
next reply other threads:[~2008-02-26 23:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-26 23:13 Larry Finger [this message]
2008-02-27 1:07 ` Problems with RTL8187 USB device John W. Linville
2008-02-27 5:27 ` Larry Finger
2008-03-01 19:21 ` Larry Finger
2008-03-25 20:31 ` Daniel Gimpelevich
2008-04-01 15:41 ` Daniel Gimpelevich
2008-04-01 17:51 ` John W. Linville
2008-04-01 18:07 ` Daniel Gimpelevich
2008-04-01 18:24 ` [PATCH] rtl8187b work in progress John W. Linville
2008-04-02 0:09 ` Herton Ronaldo Krzesinski
2008-04-02 2:40 ` Herton Ronaldo Krzesinski
2008-04-04 3:33 ` Pavel Roskin
2008-04-04 14:07 ` Herton Ronaldo Krzesinski
2008-04-04 15:17 ` Pavel Roskin
2008-04-07 12:01 ` Herton Ronaldo Krzesinski
2008-04-04 3:21 ` Pavel Roskin
2008-04-01 21:26 ` Problems with RTL8187 USB device Pavel Roskin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47C49D21.1030905@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=flamingice@sourmilk.net \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).