linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Piotr Haber" <phaber@broadcom.com>
To: "Vojtech Havel" <xhavel1@fi.muni.cz>
Cc: linux-wireless@vger.kernel.org
Subject: Re: bugreport brcmsmac weak signal
Date: Wed, 2 Jan 2013 08:20:51 +0100	[thread overview]
Message-ID: <50E3DFD3.6010803@broadcom.com> (raw)
In-Reply-To: <1707792.Sg5XObDUQq@ledge>

On 01/02/13 01:09, Vojtech Havel wrote:
> Hi,
> 
> I have problems with my Broadcom BCM4313 wifi card while using brcmsmac module.
> 
> The wifi signal is terribly weak. When the distance between my laptop and AP is 
> more than ~5 m the network is not visible at all. When the laptop is closer, 
> it connects, but it is very slow due to weak signal. I have to sit next to AP 
> when I want link quality more than 60/70.
> 
> If I use Broadcom hybrid driver - wl - it works normally (but has different 
> problems...).
> 
> I tried to use three different wifi networks with this combination and all of 
> them had the same problem.
> 
> -----
> My setting:
> $ uname -r
> 3.8.0-rc1
> 
> I applied the patch from:
> http://marc.info/?l=linux-wireless&m=135635090121154&w=2
> 
> The same with 3.5.7 gentoo kernel.
> -----
> wavemon info: (with brcmsmac, ~5 m between my laptop and the ap)
> 
> ┌─Interface────────────────────────────────────────────────
> │wlan0 (IEEE 802.11bgn, WPA/WPA2),  ESSID: "ihome"         
> ├─Levels───────────────────────────────────────────────────
> │                                                          
> │link quality: 23/70                                       
> │======================                                    
> │                                                          
> │signal level: -87 dBm (2,00 pW)                           
> │========                                                  
> │                                                          
> │                                                          
> ├─Statistics───────────────────────────────────────────────
> │RX: 3 8178(2,41 MiB), invalid: 0 nwid, 0 crypt, 0 frag, 3 misc
> │TX: 4 1789(779,619KiB), mac retries: 31, missed beacons: 0
> ├─Info─────────────────────────────────────────────────────
> │mode: Managed,  access point: (not relevant :-))           
> │freq: 2,437 GHz, channel: 6,  bitrate: 5,5 Mbit/s         
> │power mgt: off,  tx-power: 19 dBm (79,43 mW)             
> │retry: long limit 7,  rts/cts: off,  frag: off            
> │encryption: n/a (requires CAP_NET_ADMIN permissions)      
> ├─Network──────────────────────────────────────────────────
> │wlan0 (UP RUNNING BROADCAST MULTICAST)                    
> │mac: (not relevant :-)), qlen: 1000                        
> │ip: 192.168.1.103/24,  bcast: 255.255.255.255             
> └──────────────────────────────────────────────────────────
Hi Vojtech,
I see you are running v3.8-rc1, that's great since you can provide us
with the content of /sys/kernel/debug/brcmsmac/bcma0:0/hardware so we
know exactly which hardware you have.
Also dmesg contents would be helpful i think

Kind regards
Piotr


  reply	other threads:[~2013-01-02  7:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-02  0:09 bugreport brcmsmac weak signal Vojtech Havel
2013-01-02  7:20 ` Piotr Haber [this message]
2013-01-02  9:09   ` Vojtech Havel
2013-01-02 11:15     ` Piotr Haber
2013-01-02 12:23       ` Vojtech Havel

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=50E3DFD3.6010803@broadcom.com \
    --to=phaber@broadcom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=xhavel1@fi.muni.cz \
    /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).