linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Piter PUNK <piterpk@terra.com.br>
To: linux-wireless@vger.kernel.org
Subject: RTL8187B transmit problems
Date: Sun, 05 Oct 2008 23:36:39 -0300	[thread overview]
Message-ID: <48E979B7.4040000@terra.com.br> (raw)


Hi,

I have two rtl8187b cards. One built in my notebook and one external
USB wireless dongle from Encore. Both works with the rtl8187 driver
(thanks Herton! thanks Hin-Tak!) but i still have some problems.

I'm using 2.6.27-rc7 kernel and three problems are very common, but
intermittent:

1) I found my network when scan (iwlist wlan0 scan) but i can't
    associate in the found network.

2) I associate in my network but i can't transmit anything.

3) I associate, can transmit but only "small" transmissions. Ping,
    HTTP GET, POP commands... when i try to upload a file, send a
    mail, etc... the connection stuck.

The three problems happens in both rtl8187b cards. I try with two
different access points to make sure the problem isn't AP related and
now i am using an rt73usb without problems.

Without encryption, the problem 2 isn't noticeable. I don't do
a lot of tests without encryption enabled, but i can do if you want.
That's one small example of problem 2:

---
wmaster0  no wireless extensions.

wlan0     IEEE 802.11bg  ESSID:"MyLab"
           Mode:Managed  Frequency:2.437 GHz  Access Point: 
00:1D:0F:FB:B4:52
           Bit Rate=54 Mb/s   Tx-Power=27 dBm
           Retry min limit:7   RTS thr:off   Fragment thr=2352 B
           Encryption key:XXXX-XXXX-XX   Security mode:open
           Power Management:off
           Link Quality=98/100  Signal level:-22 dBm
           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
           Tx excessive retries:0  Invalid misc:0   Missed beacon:0

root@cameron:~# ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
 From 192.168.0.7 icmp_seq=41 Destination Host Unreachable
 From 192.168.0.7 icmp_seq=44 Destination Host Unreachable
 From 192.168.0.7 icmp_seq=47 Destination Host Unreachable
^C
--- 192.168.0.1 ping statistics ---
47 packets transmitted, 0 received, +3 errors, 100% packet loss, time 
46041ms
---

If you have any specific tests or patches to apply I'll be
very happy to try and test them. If you need more information
to "see" the problem, only need to ask what information you
need.

Thanks!

Piter PUNK
-- 
     |        E-Mail: piterpk@terra.com.br        (personal)
    .|.
    /V\
   // \\      UIN:116043354  Homepage:http://piterpunk.info02.com.br
  /(   )\
   ^`~'^
  #105432

             reply	other threads:[~2008-10-06  3:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-06  2:36 Piter PUNK [this message]
2008-10-08 19:57 ` RTL8187B transmit problems Matthew Garrett
2008-10-09 13:10   ` Piter PUNK
  -- strict thread matches above, loose matches on Subject: below --
2008-10-26  7:35 Piter PUNK
2008-10-27  0:31 ` Larry Finger
2008-10-27  1:49   ` Piter PUNK
2008-10-27 17:08     ` Larry Finger
2008-10-28  1:27       ` 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=48E979B7.4040000@terra.com.br \
    --to=piterpk@terra.com.br \
    --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).