linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rogerio Luz Coelho <rogluz.news@gmail.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: RTL 8187b - naughty behaviour
Date: Sat, 3 Apr 2010 13:49:49 -0300	[thread overview]
Message-ID: <i2x917a57cb1004030949qabd49dfeqa1f7cb66f4ef0f4e@mail.gmail.com> (raw)
In-Reply-To: <4BB7660A.3030900@lwfinger.net>

2010/4/3 Larry Finger <Larry.Finger@lwfinger.net>:
> On 04/03/2010 08:56 AM, Rogerio Luz Coelho wrote:
>> Hello, sorry for posting this in a DEV list, but I tried elsewhere and
>> people are generally kind, but unhelpfull. I am NOT a kernel
>> programer, so I will impose on the list´s good will somewhat ;)
>>
>> I have a Laptop witch uses the Realtek rtl8187b chip in a USB internal
>> conection.
>>
>> The chip WORKS in kernel Debian 2.6.32-3 , but is has an odd behavior:
>>
>> It works, connects and gives me ADSL speed as long as I am no more
>> than 3 meters from the router. Beyond that I get a "wrong password"
>> message in NetworkManager or Wicd (tried them both with similar
>> results)
>
> Your device may behaves very differently from mine. At 15 m from my AP,
> my rtl8187B device gets the following performance:
>
> finger@larrylap:~> tcpperf -c desktop
> Duration: 10 573usec
> Bytes sent: 4574208 (4467 kB 4 MB 0 GB)
> Bandwidth: 3659157 b/s (3659.16 kb/s 3.66 Mb/s)
> Close duration: 0s 62usec
>
> finger@larrylap:~> iwconfig wlan3
> wlan3     IEEE 802.11bg  ESSID:"lwfdjf_rad"
>          Mode:Managed  Frequency:2.412 GHz  Access Point: 00:14:BF:85:49:FA
>          Bit Rate=11 Mb/s   Tx-Power=20 dBm
>          Retry  long limit:7   RTS thr:off   Fragment thr:off
>          Power Management:off
>          Link Quality=69/70  Signal level=-41 dBm
>          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>          Tx excessive retries:0  Invalid misc:0   Missed beacon:0
>
> My device is a Level One WNC-0301USB and shows the following in dmesg:
>
> finger@larrylap:~> dmesg | grep rtl
> [129918.822942] rtl8187: inconsistency between id with OEM info!
> [129918.827838] phy1: hwaddr 00:11:6b:3e:c4:0a, RTL8187BvB(early) V0 +
> rtl8225z2, rfkill mask 2
> [129918.860071] rtl8187: Customer ID is 0x00
> [129918.860230] Registered led device: rtl8187-phy1::radio
> [129918.860333] Registered led device: rtl8187-phy1::tx
> [129918.860448] Registered led device: rtl8187-phy1::rx
> [129918.862425] rtl8187: wireless switch is on
> [129918.863143] usbcore: registered new interface driver rtl8187
>
> At my usual distance of 2 m from the AP, the transmit rate is about 13
> Mb/s and the reported signal level is -23 dBm, about what you report.
> Our chips are different, but that has not previously been a problem.
>
> Have you used this device with kernels older than 2.6.32? Fortunately,
> it does not need external firmware, thus it works with any Live CD. I
> have routinely tested all fairly recent kernels and have never seen this
> problem.
>
> Larry
>

I have a MS-Win7 instalation on this Laptop and it works 100% even at
longer distances than you report,even with walls in between.

Will do the tcpperf test as soon as I get home. There are other with
the same problem with my exact chip here in Brasil , that is because
one of our leading Laptop vendors uses this config.

Does it matter that the USB port used in this setting is a connected
to a USB HUB and then to the mother board?

More details and tests will come your way in a day or two ... will
reinstall Mandriva 2010 and do some tests with older kernels.

Thaks for the quick reply :)

Rogerio

  reply	other threads:[~2010-04-03 16:49 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-03 13:56 RTL 8187b - naughty behaviour Rogerio Luz Coelho
2010-04-03 16:00 ` Larry Finger
2010-04-03 16:49   ` Rogerio Luz Coelho [this message]
2010-04-03 16:58     ` Larry Finger
2010-04-03 17:00       ` Rogerio Luz Coelho
2010-04-03 17:04         ` Rogerio Luz Coelho
2010-04-03 17:33           ` Larry Finger
2010-04-03 17:52             ` Rogerio Luz Coelho
2010-04-10 12:07         ` Rogerio Luz Coelho
2010-04-10 18:50           ` Gábor Stefanik
2010-04-10 19:40             ` Rogerio Luz Coelho
2010-04-11 13:35               ` Gábor Stefanik
2010-04-22 20:45                 ` Rogerio Luz Coelho
2010-04-23 20:16                   ` Gábor Stefanik
2010-04-24 10:47                     ` Rogerio Luz Coelho
2010-04-24 13:59                       ` Larry Finger
2010-06-03 15:40                 ` Rogerio Luz Coelho
2010-08-08 22:22                   ` Rogerio Luz Coelho
2010-08-09  1:43                     ` Larry Finger
2010-08-11  0:03                       ` Rogerio Luz Coelho
2010-08-11  0:23                         ` Thadeu Lima de Souza Cascardo
2010-08-11  2:51                           ` Larry Finger
2010-04-04  0:20       ` Hin-Tak Leung
2010-04-05  0:53         ` Rogerio Luz Coelho
2010-04-05  1:50           ` Gábor Stefanik
2010-04-05  3:12             ` Rogerio Luz Coelho
2010-04-05  3:43               ` Gábor Stefanik
2010-04-03 20:03   ` Gus Wirth
2010-04-03 21:40     ` Larry Finger
2010-05-06 17:36   ` seno
2010-05-06 18:20     ` Larry Finger
2010-05-14 20:12       ` seno
2010-05-14 20:20       ` seno

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=i2x917a57cb1004030949qabd49dfeqa1f7cb66f4ef0f4e@mail.gmail.com \
    --to=rogluz.news@gmail.com \
    --cc=Larry.Finger@lwfinger.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).