Hi all.
Sorry if I'm not posting this properly, my first time here.
I have what might be a bug to report:
My Realtek 8187 USB wifi card is not being handled by rtl8187 module.
I am using Ubuntu 8.10, and module from Jan 29th that is (presumably)
supplied by Ubuntu package linux-backports-modules-
intrepid is not handling the card, as well as the one I built myself
from (git?) sources, dated Feb 15th.
I can properly load the module rtl8187 (both already mentioned
versions), but when I insert the USB card, nothing happens. See logs
at the bottom.
To properly load two versions I had to correspondingly rename
mac80211.ko and cfg80211.ko, since there were errors reported (unknown
symbols, unable to load, etc). Since I can properly load the modules,
dependencies are not the problem. Unless there is some other *.ko that
I need to rename?
The card is AirLive WL1600USB, PCI/USB ID 1b75:8187,
url: http://www.airlive.com/product/product_3.jsp?pdid=PD1223473034861
I somehow have the feeling that the PCI/USB ID of this card is
unrecognized by the module (if the module even recognizes hardware
only by it's ID), since this is rather obscure ID (google only returns
2 results for that ID). I'm no expert, I might be wrong.
I'd like to get it working with native drivers if possible. Didn't try
ndiswrapper yet, and I'd rather if that were not my only option.
If any more info is needed, please, feel free to ask.
$ tail /var/log/syslog
Feb 16 05:55:36 CH4 kernel: [ 1389.137978] usbcore: deregistering
interface driver rtl8187
Feb 16 05:55:41 CH4 kernel: [ 1394.294357] usbcore: registered new
interface driver rtl8187
Feb 16 05:55:45 CH4 kernel: [ 1397.480159] usb 4-3: new high speed USB
device using ehci_hcd and address 4
Feb 16 05:55:45 CH4 kernel: [ 1397.678395] usb 4-3: configuration #1
chosen from 1 choice
$ lsusb
Bus 004 Device 004: ID 1b75:8187
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
$ uname -a
Linux CH4 2.6.27-11-generic #1 SMP Thu Jan 29 19:24:39 UTC 2009 i686 GNU/Linux
modinfo for the self-built Feb 15th version:
$ modinfo rtl8187
filename:
/lib/modules/2.6.27-11-generic/updates/drivers/net/wireless/rtl818x/rtl8187.ko
license: GPL
description: RTL8187/RTL8187B USB wireless driver
author: Larry Finger <[email protected]>
author: Hin-Tak Leung <[email protected]>
author: Herton Ronaldo Krzesinski <[email protected]>
author: Andrea Merello <[email protected]>
author: Michael Wu <[email protected]>
srcversion: 545837A60AA95978807201A
alias: usb:v13D1pABE6d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0DF6p0028d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0DF6p000Dd*dc*dsc*dp*ic*isc*ip*
alias: usb:v03F0pCA02d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0846p4260d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0846p6A00d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0846p6100d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0BDAp8198d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0BDAp8197d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0BDAp8189d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0BDAp8187d*dc*dsc*dp*ic*isc*ip*
alias: usb:v050Dp705Ed*dc*dsc*dp*ic*isc*ip*
alias: usb:v0B05p171Dd*dc*dsc*dp*ic*isc*ip*
depends: mac80211,eeprom_93cx6,cfg80211,usbcore
vermagic: 2.6.27-11-generic SMP mod_unload modversions 586
$ dmesg
[ 3536.706004] usbcore: deregistering interface driver rtl8187
[ 3540.582591] usbcore: registered new interface driver rtl8187
[ 3545.160202] usb 4-4: new high speed USB device using ehci_hcd and address 5
[ 3545.326673] usb 4-4: configuration #1 chosen from 1 choice
[ 3556.715311] usb 4-4: USB disconnect, address 5
[ 3558.944148] usb 4-3: new high speed USB device using ehci_hcd and address 6
[ 3559.110562] usb 4-3: configuration #1 chosen from 1 choice
Thanks for the hard work and your help.
Viktor
--
Don't let people drive you crazy when you know it's in walking distance.
Hin-Tak Leung wrote:
> Hiya,
>
> A quick search on google shows Airlive hosting a linux driver here:
>
> http://www.airlive.com/support/support_3a.jsp?pdid=PD1223473034861
>
> I had a quick look and indeed it looks like the realtek vendor driver
> (or a variant of) for 8187L.
> Note that this is for reference, since we all know the vendor driver
> has some issues with the latest wireless stack, etc.
Once I get confirmation from the OP that his device works, I have a patch with a
total of 6 new ID's for rtl8187. Four of them came from the .inf file
accompaning the Windows version of the RTL8187L driver.
Larry
On Mon, Feb 16, 2009 at 06:33:10AM +0100, Viktor Ilija=C5=A1i=C4=87 wro=
te:
> The card is AirLive WL1600USB, PCI/USB ID 1b75:8187,
> url: http://www.airlive.com/product/product_3.jsp?pdid=3DPD1223473034=
861
>=20
> I somehow have the feeling that the PCI/USB ID of this card is
> unrecognized by the module (if the module even recognizes hardware
> only by it's ID), since this is rather obscure ID (google only return=
s
> 2 results for that ID). I'm no expert, I might be wrong.
You might try applying the patch below and rebuilding your kernel.
Does that get the driver to recognize the device?
John
---
diff --git a/drivers/net/wireless/rtl818x/rtl8187_dev.c b/drivers/net/w=
ireless/rtl818x/rtl8187_dev.c
index 82bd47e..5da2bd7 100644
--- a/drivers/net/wireless/rtl818x/rtl8187_dev.c
+++ b/drivers/net/wireless/rtl818x/rtl8187_dev.c
@@ -59,6 +59,8 @@ static struct usb_device_id rtl8187_table[] __devinit=
data =3D {
{USB_DEVICE(0x0df6, 0x0028), .driver_info =3D DEVICE_RTL8187B},
/* Abocom */
{USB_DEVICE(0x13d1, 0xabe6), .driver_info =3D DEVICE_RTL8187},
+ /* AirLive */
+ {USB_DEVICE(0x1b75, 0x8187), .driver_info =3D DEVICE_RTL8187},
{}
};
=20
--=20
John W. Linville Someday the world will need a hero, and you
[email protected] might be all we have. Be ready.
Xose Vazquez Perez wrote:
> John W. Linville wrote:
>
>> You might try applying the patch below and rebuilding your kernel.
>
> easier, try:
>
> # modprobe rtl8187
> # echo "0x1b75 0x8187" > /sys/bus/usb/drivers/rtl8187/new_id
When you do that, does it work?
Larry
Hi all.
Yesterday evening I tried John's patch (I manually added those two
lines to the source), and the driver properly loads and it seem to
work.
However.... it would seem that my card died some time in the last few
days. It works for about 10-15 seconds after i plug it in, and then
"dies". I'd say that when it gets warm, it's out of the game.
In Linux after i plug it in, it works just enough time to:
1. detect networks in ubuntu network manager (and return a nice scan
result with iwlist wlan3 scan)
2. starts to connect to my network (and reaches random points in connecting)
3. stops responding altogether, cannot connect, no more results with
iwlist scan, etc.
I noticed this exact behavior in windows too, yesterday morning,
before I tried these patches, so linux driver is DEFINITELY not to
blame.
In windows it very shortly detects available networks, starts to
connect and very soon stops responding and finding networks.
I'll return it to shop to be replaced, and I'll report back when I get
one that works properly.
Also, Larry, I took lsusb -v output during those first few moments
while the card operates properly, hope it helps:
$ sudo lsusb -v
Bus 004 Device 004: ID 1b75:8187
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x1b75
idProduct 0x8187
bcdDevice 1.00
iManufacturer 1 Manufacturer_Realtek_RTL8187_
iProduct 2 AirLive WL1600USB
iSerial 3 004F78000572
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 39
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 3
bInterfaceClass 0 (Defined at Interface level)
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 5 Bulk-IN,Bulk-OUT,Bulk-OUT
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 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 0x02 EP 2 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 0x03 EP 3 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)
Hin-Tak, I did see the AirLive linux reference driver, but didn't even
want to try that, unless my only option left was ndiswrapper. I know
those manufacturer's "drivers" usually cause more frustration than
use.
Thanks all for your time and help.
Viktor
--
Don't let people drive you crazy when you know it's in walking distance.
On Tue, Feb 17, 2009 at 01:12, Larry Finger <[email protected]> wrote:
>
> Hin-Tak Leung wrote:
> > Hiya,
> >
> > A quick search on google shows Airlive hosting a linux driver here:
> >
> > http://www.airlive.com/support/support_3a.jsp?pdid=PD1223473034861
> >
> > I had a quick look and indeed it looks like the realtek vendor driver
> > (or a variant of) for 8187L.
> > Note that this is for reference, since we all know the vendor driver
> > has some issues with the latest wireless stack, etc.
>
> Once I get confirmation from the OP that his device works, I have a patch with a
> total of 6 new ID's for rtl8187. Four of them came from the .inf file
> accompaning the Windows version of the RTL8187L driver.
>
> Larry
Hiya,
A quick search on google shows Airlive hosting a linux driver here:
http://www.airlive.com/support/support_3a.jsp?pdid=PD1223473034861
I had a quick look and indeed it looks like the realtek vendor driver
(or a variant of) for 8187L.
Note that this is for reference, since we all know the vendor driver
has some issues with the latest wireless stack, etc.
John W. Linville wrote:
> You might try applying the patch below and rebuilding your kernel.
easier, try:
# modprobe rtl8187
# echo "0x1b75 0x8187" > /sys/bus/usb/drivers/rtl8187/new_id
regards,
--
Polycommander, Erkowit, Urquiola, Andros Patria, Cason, Aegean Sea, Prestige, ...
Viktor Ilija=C5=A1i=C4=87 wrote:
> Hi all.
>=20
> Yesterday evening I tried John's patch (I manually added those two
> lines to the source), and the driver properly loads and it seem to
> work.
>=20
> However.... it would seem that my card died some time in the last few
> days. It works for about 10-15 seconds after i plug it in, and then
> "dies". I'd say that when it gets warm, it's out of the game.
>=20
> In Linux after i plug it in, it works just enough time to:
> 1. detect networks in ubuntu network manager (and return a nice scan
> result with iwlist wlan3 scan)
> 2. starts to connect to my network (and reaches random points in conn=
ecting)
> 3. stops responding altogether, cannot connect, no more results with
> iwlist scan, etc.
>=20
> I noticed this exact behavior in windows too, yesterday morning,
> before I tried these patches, so linux driver is DEFINITELY not to
> blame.
>=20
> In windows it very shortly detects available networks, starts to
> connect and very soon stops responding and finding networks.
>=20
> I'll return it to shop to be replaced, and I'll report back when I ge=
t
> one that works properly.
>=20
> Also, Larry, I took lsusb -v output during those first few moments
> while the card operates properly, hope it helps:
That output confirms that it is an 8187, not an 8187b.
I also had a Realtek device fail, but after replacement, all has been w=
ell.
Thanks for testing.
Larry
Viktor Ilija=C5=A1i=C4=87 wrote:
>=20
> If any more info is needed, please, feel free to ask.
>=20
> $ tail /var/log/syslog
> Feb 16 05:55:36 CH4 kernel: [ 1389.137978] usbcore: deregistering
> interface driver rtl8187
> Feb 16 05:55:41 CH4 kernel: [ 1394.294357] usbcore: registered new
> interface driver rtl8187
> Feb 16 05:55:45 CH4 kernel: [ 1397.480159] usb 4-3: new high speed US=
B
> device using ehci_hcd and address 4
> Feb 16 05:55:45 CH4 kernel: [ 1397.678395] usb 4-3: configuration #1
> chosen from 1 choice
>=20
> $ lsusb
> Bus 004 Device 004: ID 1b75:8187
> Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
The driver for USB devices is selected from the ID's, just as it is wit=
h PCI
devices.
Please send the details for your device as output from the 'lsusb -v' c=
ommand. I
don't need the data for any other USB stuff, just the 8187. Once I have=
that
info, I will send you a test patch for your sources.
Larry
Viktor Ilija=C5=A1i=C4=87 wrote:
> Hi, all.
>=20
> I received a new card, after the old one died, and I'm happy to repor=
t
> that the card works properly under Linux with my patched version of
> the driver (the patch was only to add the USB ID). I see that the
> patch was already submitted to the kernel while my card was being
> replaced.
>=20
> Thanks all for your work and help.
You are welcome. Thanks for reporting the new ID. That patch has been a=
pplied to
2.6.29-rcX and will appear in the next releases of 2.6.{27,28}.Y.
Larry
Hi, all.
I received a new card, after the old one died, and I'm happy to report
that the card works properly under Linux with my patched version of
the driver (the patch was only to add the USB ID). I see that the
patch was already submitted to the kernel while my card was being
replaced.
Thanks all for your work and help.
Viktor
--
Don't let people drive you crazy when you know it's in walking distance.