From: Larry Finger <Larry.Finger@lwfinger.net>
To: Piter PUNK <piterpk@terra.com.br>
Cc: linux-wireless@vger.kernel.org
Subject: Re: RTL8187B transmit problems
Date: Mon, 27 Oct 2008 10:08:43 -0700 [thread overview]
Message-ID: <4905F59B.9030107@lwfinger.net> (raw)
In-Reply-To: <49051E0E.2030909@terra.com.br>
Piter PUNK wrote:
> Larry Finger wrote:
>> What are the details of your device? Please post the output of 'dmesg
>> | grep -i
>> rtl'.
>
> This is the built-in rtl8187b adapter:
>
> usb 1-1: new high speed USB device using ehci_hcd and address 7
> usb 1-1: configuration #1 chosen from 1 choice
> usb 1-1: New USB device found, idVendor=0bda, idProduct=8189
> usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> usb 1-1: Product: RTL8187B_WLAN_Adapter
> usb 1-1: Manufacturer: Manufacturer_Realtek
> usb 1-1: SerialNumber: 00e04c000001
> rtl8187: 8187B chip detected. Support is EXPERIMENTAL, and could damage
> your
> hardware, use at your own risk
> phy3: Selected rate control algorithm 'pid'
> phy3: hwaddr 00:16:44:aa:df:bf, RTL8187BvE V0 + rtl8225z2
>
> This is my external rtl8187b USB dongle:
>
> usb 1-3: new high speed USB device using ehci_hcd and address 8
> usb 1-3: configuration #1 chosen from 1 choice
> rtl8187: 8187B chip detected. Support is EXPERIMENTAL, and could damage
> your
> hardware, use at your own risk
> phy4: Selected rate control algorithm 'pid'
> phy4: hwaddr 00:18:e7:42:2c:23, RTL8187BvE V0 + rtl8225z2
> usb 1-3: New USB device found, idVendor=0bda, idProduct=8189
> usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> usb 1-3: Product: RTL8187B_WLAN_Adapter
> usb 1-3: Manufacturer: Manufacturer_Realtek
> usb 1-3: SerialNumber: 00e04c000001
>
> Both have the same "not-working" results. Using any of my other
> adapters the transmission works fine. (ok, it didn't work with
> USB Marvell dongle... but it isn't even detected)
My device is a little different that yours:
rtl8187: 8187B chip detected. Support is EXPERIMENTAL, and could damage your
hardware, use at your own risk
rtl8187: inconsistency between id with OEM info!
phy1: Selected rate control algorithm 'pid'
phy1: hwaddr 00:11:6b:3e:c4:0a, RTL8187BvB(early) V0 + rtl8225z2
I'll review the code to look at the differences in paths for your device and
mine. Just in case there is a data dependency, please send me (privately) your
2048 byte file.
Thanks,
Larry
next prev parent reply other threads:[~2008-10-27 17:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-26 7:35 RTL8187B transmit problems Piter PUNK
2008-10-27 0:31 ` Larry Finger
2008-10-27 1:49 ` Piter PUNK
2008-10-27 17:08 ` Larry Finger [this message]
2008-10-28 1:27 ` Piter PUNK
-- strict thread matches above, loose matches on Subject: below --
2008-10-06 2:36 Piter PUNK
2008-10-08 19:57 ` Matthew Garrett
2008-10-09 13:10 ` Piter PUNK
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=4905F59B.9030107@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=piterpk@terra.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.