Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
How to get Broadcom Corporation BCM43228 working stable?
View unanswered posts
View posts from last 24 hours

Goto page 1, 2, 3, 4  Next  
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
GenHeDi
Tux's lil' helper
Tux's lil' helper


Joined: 02 Jan 2016
Posts: 122

PostPosted: Sat Jan 16, 2016 8:28 pm    Post subject: How to get Broadcom Corporation BCM43228 working stable? Reply with quote

Hello,

I run Gentoo on a Hp Probook 640 G1 equipped with a Broadcom Corporation BCM43228 wireless device. Most of the time it is possible to get good traffic through the wireless interface.
But once and a while it losses connection without a specific reason. Sometimes it is even not possible to establish a proper connection at all. I searched on google a lot without finding a solution. But I learned also that the Broadcom BCM43xxx are causing a lot of linux users a headache.

My kernel (4.1.12 version) is using the b43 module.

Who wants to take the challenge with me, to find a solution in order to make the Broadcom BCM43228 working stable within Gentoo Linux.
_________________
Nulla tenaci invia est via
Back to top
View user's profile Send private message
khayyam
Watchman
Watchman


Joined: 07 Jun 2012
Posts: 6228
Location: Room 101

PostPosted: Sat Jan 16, 2016 9:23 pm    Post subject: Reply with quote

GenHeDi ...

Not enough information to point at a probable cause ... but from the fact that its intermittent I'd probably attribute the issue to the fact that wireless is radio (with all that implies).

Anyhow, please provide details of your setup ... and the output of the following (where 'wlan0' is whatever your interface happens to be named):

Code:
# iw dev wlan0 station dump
# iw dev wlan0 get power_save
# iw reg get
# awk '/(WEXT|(MAC|CFG|NL)80211)/' /usr/src/linux/.config
# modinfo b43

It might also be worth enabling debugging in wpa_supplicant, and log it.

/etc/conf.d/net:
wpa_supplicant_wlan0="-Dnl80211 -dd -f /var/log/wpa_supplicant.log"

Also, if the issue occurs, besides a 'station dump', the output of 'iw event -f' would be useful (you'll have to leave it running for a while, and/or redirect the output to a file).

best ... khay
Back to top
View user's profile Send private message
GenHeDi
Tux's lil' helper
Tux's lil' helper


Joined: 02 Jan 2016
Posts: 122

PostPosted: Sun Jan 17, 2016 7:13 pm    Post subject: Reply with quote

Hello khayyam,

Thanks for taking the challange.
Code:

iw dev wlp2s0b1 station dump
Station 64:70:02:df:4a:76 (on wlp2s0b1)
        inactive time:  25050 ms
        rx bytes:       4157405
        rx packets:     15013
        tx bytes:       287712
        tx packets:     2142
        tx retries:     5004
        tx failed:      37
        signal:         -65 dBm
        signal avg:     -63 dBm
        tx bitrate:     54.0 MBit/s
        rx bitrate:     11.0 MBit/s
        expected throughput:    1.70Mbps
        authorized:     yes
        authenticated:  yes
        preamble:       long
        WMM/WME:        yes
        MFP:            no
        TDLS peer:      no

Code:

iw dev wlp2s0b1 get power_save
Power save: off

Code:

iw reg get
country 00: DFS-UNSET
        (2402 - 2472 @ 40), (N/A, 20), (N/A)
        (2457 - 2482 @ 40), (N/A, 20), (N/A), PASSIVE-SCAN
        (2474 - 2494 @ 20), (N/A, 20), (N/A), NO-OFDM, PASSIVE-SCAN
        (5170 - 5250 @ 80), (N/A, 20), (N/A), PASSIVE-SCAN
        (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, PASSIVE-SCAN
        (5490 - 5730 @ 160), (N/A, 20), (0 ms), DFS, PASSIVE-SCAN
        (5735 - 5835 @ 80), (N/A, 20), (N/A), PASSIVE-SCAN
        (57240 - 63720 @ 2160), (N/A, 0), (N/A)

Code:

awk '/(WEXT|(MAC|CFG|NL)80211)/' /usr/src/linux/.config
CONFIG_WEXT_CORE=y
CONFIG_WEXT_PROC=y
CONFIG_WEXT_SPY=y
CONFIG_WEXT_PRIV=y
CONFIG_CFG80211=m
# CONFIG_NL80211_TESTMODE is not set
# CONFIG_CFG80211_DEVELOPER_WARNINGS is not set
# CONFIG_CFG80211_REG_DEBUG is not set
CONFIG_CFG80211_DEFAULT_PS=y
# CONFIG_CFG80211_INTERNAL_REGDB is not set
CONFIG_CFG80211_WEXT=y
CONFIG_CFG80211_WEXT_EXPORT=y
CONFIG_MAC80211=m
CONFIG_MAC80211_HAS_RC=y
CONFIG_MAC80211_RC_MINSTREL=y
CONFIG_MAC80211_RC_MINSTREL_HT=y
# CONFIG_MAC80211_RC_MINSTREL_VHT is not set
CONFIG_MAC80211_RC_DEFAULT_MINSTREL=y
CONFIG_MAC80211_RC_DEFAULT="minstrel_ht"
# CONFIG_MAC80211_MESH is not set
CONFIG_MAC80211_LEDS=y
# CONFIG_MAC80211_MESSAGE_TRACING is not set
# CONFIG_MAC80211_DEBUG_MENU is not set
# CONFIG_MAC80211_HWSIM is not set

Code:

modinfo b43
filename:       /lib/modules/4.1.12-gentoo20151220_2030/kernel/drivers/net/wireless/b43/b43.ko
firmware:       b43/ucode9.fw
firmware:       b43/ucode5.fw
firmware:       b43/ucode16_mimo.fw
firmware:       b43/ucode15.fw
firmware:       b43/ucode14.fw
firmware:       b43/ucode13.fw
firmware:       b43/ucode11.fw
license:        GPL
author:         Rafał Miłecki
author:         Gábor Stefanik
author:         Michael Buesch
author:         Stefano Brivio
author:         Martin Langer
description:    Broadcom B43 wireless driver
alias:          ssb:v4243id0812rev10*
alias:          ssb:v4243id0812rev0F*
alias:          ssb:v4243id0812rev0D*
alias:          ssb:v4243id0812rev0C*
alias:          ssb:v4243id0812rev0B*
alias:          ssb:v4243id0812rev0A*
alias:          ssb:v4243id0812rev09*
alias:          ssb:v4243id0812rev07*
alias:          ssb:v4243id0812rev06*
alias:          ssb:v4243id0812rev05*
alias:          bcma:m04BFid0812rev2Acl*
alias:          bcma:m04BFid0812rev28cl*
alias:          bcma:m04BFid0812rev1Ecl*
alias:          bcma:m04BFid0812rev1Dcl*
alias:          bcma:m04BFid0812rev1Ccl*
alias:          bcma:m04BFid0812rev18cl*
alias:          bcma:m04BFid0812rev17cl*
alias:          bcma:m04BFid0812rev11cl*
alias:          pcmcia:m02D0c0476f*fn*pfn*pa*pb*pc*pd*
alias:          pcmcia:m02D0c0448f*fn*pfn*pa*pb*pc*pd*
depends:        ssb,bcma,pcmcia,mac80211,led-class,cfg80211
intree:         Y
vermagic:       4.1.12-gentoo20151220_2030 SMP mod_unload modversions
parm:           bad_frames_preempt:enable(1) / disable(0) Bad Frames Preemption (int)
parm:           fwpostfix:Postfix for the .fw files to load. (string)
parm:           hwpctl:Enable hardware-side power control (default off) (int)
parm:           nohwcrypt:Disable hardware encryption. (int)
parm:           hwtkip:Enable hardware tkip. (int)
parm:           qos:Enable QOS support (default on) (int)
parm:           btcoex:Enable Bluetooth coexistence (default on) (int)
parm:           verbose:Log message verbosity: 0=error, 1=warn, 2=info(default), 3=debug (int)
parm:           pio:Use PIO accesses by default: 0=DMA, 1=PIO (int)
parm:           allhwsupport:Enable support for all hardware (even it if overlaps with the brcmsmac driver) (int)

Code:

lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller (rev 06)
00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06)
00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 04)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-V (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d4)
00:1c.6 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #7 (rev d4)
00:1c.7 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #8 (rev d4)
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM87 Express LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 04)
02:00.0 Network controller: Broadcom Corporation BCM43228 802.11a/b/g/n
03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI Express Card Reader (rev 01)


The other stuff I will provide when useful
_________________
Nulla tenaci invia est via
Back to top
View user's profile Send private message
GenHeDi
Tux's lil' helper
Tux's lil' helper


Joined: 02 Jan 2016
Posts: 122

PostPosted: Sun Jan 17, 2016 7:49 pm    Post subject: Reply with quote

By the way, following questions:

My /etc/conf.d/net
Code:

cat /etc/conf.d/net
config_enp0s25="dhcp"
config_wlp2s0b1="dhcp"
modules="wpa_supplicant"


And from the wpa_supplicant wiki:
Quote:

Enable Logging

By default, wpa_supplicant performs very little debugging without the debug flag enabled.
root #USE="debug" emerge --ask wpa_supplicant
FILE /etc/conf.d/netfor usage with the Setup for Gentoo net.* scripts
Code:

modules_wlan0="wpa_supplicant"
wpa_supplicant_wlan0="-Dnl80211 -d -f /var/log/wpa_supplicant.log"
config_wlan0="dhcp"


Code:

emerge -pv wpa_supplicant

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R    ] net-wireless/wpa_supplicant-2.4-r3::gentoo  USE="dbus hs2-0 qt4 readline ssl -ap -eap-sim -fasteap -gnutls -p2p (-ps3) (-selinux) -smartcard -tdls -uncommon-eap-types -wimax -wps" 0 KiB

Total: 1 package (1 reinstall), Size of downloads: 0 KiB

- Is it necessary to replace the _wlan0 part with my _wlp2s0b1?
- Is it necessary to extend the modules line to modules_wlp2s0b1?
- Do I need to emerge the wpa_supplicant with "debug" use-flag?
_________________
Nulla tenaci invia est via
Back to top
View user's profile Send private message
khayyam
Watchman
Watchman


Joined: 07 Jun 2012
Posts: 6228
Location: Room 101

PostPosted: Sun Jan 17, 2016 8:23 pm    Post subject: Reply with quote

GenHeDi wrote:
- Is it necessary to replace the _wlan0 part with my _wlp2s0b1?

GenHeDi ... yes.

GenHeDi wrote:
- Is it necessary to extend the modules line to modules_wlp2s0b1?

Yes, without it this would be also be set for enp0s25. So, to be more explicit:

/etc/conf.d/net:
modules_wlp2s0b1="wpa_supplicant dhcpcd"
modules_enp0s25="dhcpcd"

GenHeDi wrote:
- Do I need to emerge the wpa_supplicant with "debug" use-flag?

No, in fact there is no 'debug' useflag on wpa_supplicant any longer, I had requested (via a bug report) that DEBUG_FILE be set by default, it doesn't add much in terms of code but it means that users with issues don't have to enable the useflag and re-build simply to use '-dd -f'.

The output above seems ok ... but generally the advice with b42 is to disable hwcrypt (at least it was ... not sure what the current status is ITR).

Code:
# echo "options b42 nohwcrypt" > /etc/modprobe.d/b42.conf

If you post with output as and when the issue occurs then I might get a better idea of what's happening.

best ... khay
Back to top
View user's profile Send private message
GenHeDi
Tux's lil' helper
Tux's lil' helper


Joined: 02 Jan 2016
Posts: 122

PostPosted: Mon Jan 18, 2016 7:09 pm    Post subject: Reply with quote

Is it possible that you mean b43 instead of b42?
_________________
Nulla tenaci invia est via
Back to top
View user's profile Send private message
khayyam
Watchman
Watchman


Joined: 07 Jun 2012
Posts: 6228
Location: Room 101

PostPosted: Mon Jan 18, 2016 11:25 pm    Post subject: Reply with quote

GenHeDi wrote:
Is it possible that you mean b43 instead of b42?

GenHeDi ... yes, I did ... I've always said those two keys are too close together ;)

best ... khay
Back to top
View user's profile Send private message
GenHeDi
Tux's lil' helper
Tux's lil' helper


Joined: 02 Jan 2016
Posts: 122

PostPosted: Tue Jan 19, 2016 8:11 pm    Post subject: Reply with quote

Code:
echo "options b43 nohwcrypt" > /etc/modprobe.d/b43.conf


Results in a non working wireless adapter (after a restart of my computer).
After a look in dmesg I found following line:
Code:

[   15.932047] b43: `' invalid for parameter `nohwcrypt'


Is it possible that you mean:
Code:
echo "options b43 nohwcrypt=1" > /etc/modprobe.d/b43.conf


Regards
_________________
Nulla tenaci invia est via
Back to top
View user's profile Send private message
khayyam
Watchman
Watchman


Joined: 07 Jun 2012
Posts: 6228
Location: Room 101

PostPosted: Tue Jan 19, 2016 10:56 pm    Post subject: Reply with quote

GenHeDi wrote:
Is it possible that you mean:

Code:
echo "options b43 nohwcrypt=1" > /etc/modprobe.d/b43.conf

GenHiDi ... yes ... the above 'modinfo b43' states the parameter is an integer '(int)'

Code:
parm:  nohwcrypt:Disable hardware encryption. (int)

In my case, ath5k, its boolean '(bool)'.

modinfo ath5k | egrep '^parm.*nohwcrypt':
parm:  nohwcrypt:Disable hardware encryption. (bool)

I do wish if different drivers used the same parameter they would be consistent in how it was enabled.

best ... khay
Back to top
View user's profile Send private message
GenHeDi
Tux's lil' helper
Tux's lil' helper


Joined: 02 Jan 2016
Posts: 122

PostPosted: Wed Jan 20, 2016 7:54 pm    Post subject: Reply with quote

Oke, I have put everything in place according to your description. First result of the wpa log file is shown below (last bunch of lines).
The connection is not dropping connection yet, but is not fast at this moment. The forum site was build slow (the emoticons were first only text hyper links and than one by one becoming pictures)
Code:
   
wlp2s0b1: WPA: Key negotiation completed with 64:70:02:df:4a:76 [PTK=CCMP GTK=CCMP]
CTRL_IFACE monitor sent successfully to /tmp/wpa_ctrl_2856-1\x00
wlp2s0b1: Cancelling authentication timeout
wlp2s0b1: State: GROUP_HANDSHAKE -> COMPLETED
wlp2s0b1: Radio work 'sme-connect'@0x6e8920 done in 0.851203 seconds
wlp2s0b1: CTRL-EVENT-CONNECTED - Connection to 64:70:02:df:4a:76 completed [id=0 id_str=]
CTRL_IFACE monitor sent successfully to /tmp/wpa_ctrl_2856-1\x00
nl80211: Set wlp2s0b1 operstate 0->1 (UP)
netlink: Operstate: ifindex=3 linkmode=-1 (no change), operstate=6 (IF_OPER_UP)
EAPOL: External notification - portValid=1
EAPOL: External notification - EAP success=1
EAPOL: SUPP_PAE entering state AUTHENTICATING
EAPOL: SUPP_BE entering state SUCCESS
EAP: EAP entering state DISABLED
EAPOL: SUPP_PAE entering state AUTHENTICATED
EAPOL: Supplicant port status: Authorized
nl80211: Set supplicant port authorized for 64:70:02:df:4a:76
EAPOL: SUPP_BE entering state IDLE
EAPOL authentication completed - result=SUCCESS
nl80211: Set rekey offload
nl80211: Driver does not support rekey offload
RTM_NEWLINK: ifi_index=3 ifname=wlp2s0b1 operstate=6 linkmode=1 ifi_family=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
RTM_NEWLINK: ifi_index=3 ifname=wlp2s0b1 operstate=6 linkmode=1 ifi_family=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
EAPOL: startWhen --> 0
EAPOL: disable timer tick
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
wlp2s0b1: BSS: Remove id 3 BSSID 94:a7:b7:4a:43:75 SSID 'H369A4A4375' due to wpa_bss_flush_by_age
CTRL_IFACE monitor sent successfully to /tmp/wpa_ctrl_2856-1\x00
wlp2s0b1: BSS: Remove id 4 BSSID 70:9f:2d:89:67:45 SSID 'H368N896745' due to wpa_bss_flush_by_age
CTRL_IFACE monitor sent successfully to /tmp/wpa_ctrl_2856-1\x00
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
wlp2s0b1: BSS: Remove id 0 BSSID 70:9f:2d:9c:44:aa SSID 'H369A9C44AA' due to wpa_bss_flush_by_age
CTRL_IFACE monitor sent successfully to /tmp/wpa_ctrl_2856-1\x00
wlp2s0b1: BSS: Remove id 1 BSSID 72:9f:2d:9c:44:ab SSID 'KPN Fon' due to wpa_bss_flush_by_age
CTRL_IFACE monitor sent successfully to /tmp/wpa_ctrl_2856-1\x00
wlp2s0b1: BSS: Remove id 2 BSSID fa:8f:ca:90:a1:66 SSID '' due to wpa_bss_flush_by_age
CTRL_IFACE monitor sent successfully to /tmp/wpa_ctrl_2856-1\x00
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1

_________________
Nulla tenaci invia est via
Back to top
View user's profile Send private message
khayyam
Watchman
Watchman


Joined: 07 Jun 2012
Posts: 6228
Location: Room 101

PostPosted: Wed Jan 20, 2016 8:51 pm    Post subject: Reply with quote

GenHeDi ...

ok, I need to see the output of 'iw dev wlp2s0b1 station dump' and 'iw event -f' during this same period (the latter may take some time to generate output). Also, is there anything in dmesg ... specifically related to b43, or (MAC|CFG|NL)80211.

best ... khay
Back to top
View user's profile Send private message
GenHeDi
Tux's lil' helper
Tux's lil' helper


Joined: 02 Jan 2016
Posts: 122

PostPosted: Wed Jan 20, 2016 9:37 pm    Post subject: Reply with quote

khayyam

Oke, last lines containing:
Code:

nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1
nl80211: Drv Event 64 (NL80211_CMD_NOTIFY_CQM) received for wlp2s0b1

Code:

iw dev wlp2s0b1 station dump
Station 64:70:02:df:4a:76 (on wlp2s0b1)
        inactive time:  6600 ms
        rx bytes:       35973087
        rx packets:     38529
        tx bytes:       2606487
        tx packets:     21959
        tx retries:     53752
        tx failed:      8094
        signal:         -33 dBm
        signal avg:     -41 dBm
        tx bitrate:     18.0 MBit/s
        rx bitrate:     5.5 MBit/s
        expected throughput:    0.383Mbps
        authorized:     yes
        authenticated:  yes
        preamble:       long
        WMM/WME:        yes
        MFP:            no
        TDLS peer:      no

Code:

time iw event -f
wlp2s0b1: del station 64:70:02:df:4a:76
wlp2s0b1 (phy #0): deauth 64:70:02:df:4a:76 -> 30:10:b3:0e:6b:20 reason 2: Previous authentication no longer valid [frame: c0 08 40 01 30 10 b3 0e 6b 20 64 70 02 df 4a 76 64 70 02 df 4a 76 90 12 02 00]
wlp2s0b1 (phy #0): disconnected (by AP) reason: 2: Previous authentication no longer valid
phy #0: regulatory domain change: set to world roaming by the wireless core upon initialization request
wlp2s0b1 (phy #0): scan started
wlp2s0b1 (phy #0): scan finished: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 5180 5200 5220 5240 5745 5765 5785 5805 5825, "Network-647002df4a76" ""
wlp2s0b1: new station 64:70:02:df:4a:76
wlp2s0b1: del station 64:70:02:df:4a:76
wlp2s0b1 (phy #0): auth: timed out
wlp2s0b1 (phy #0): scan started
wlp2s0b1 (phy #0): scan finished: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 5180 5200 5220 5240 5745 5765 5785 5805 5825, "Network-647002df4a76" ""
wlp2s0b1: new station 64:70:02:df:4a:76
wlp2s0b1: del station 64:70:02:df:4a:76
wlp2s0b1 (phy #0): auth: timed out
wlp2s0b1 (phy #0): scan started
wlp2s0b1 (phy #0): scan finished: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 5180 5200 5220 5240 5745 5765 5785 5805 5825, "Network-647002df4a76" ""
wlp2s0b1: new station 64:70:02:df:4a:76
wlp2s0b1 (phy #0): auth 64:70:02:df:4a:76 -> 30:10:b3:0e:6b:20 status: 0: Successful [frame: b0 00 40 01 30 10 b3 0e 6b 20 64 70 02 df 4a 76 64 70 02 df 4a 76 00 00 00 00 02 00 00 00]
wlp2s0b1 (phy #0): assoc 64:70:02:df:4a:76 -> 30:10:b3:0e:6b:20 status: 0: Successful [frame: 10 00 40 01 30 10 b3 0e 6b 20 64 70 02 df 4a 76 64 70 02 df 4a 76 10 00 31 04 00 00 04 c0 01 08 82 84 8b 0c 12 96 18 24 32 04 30 48 60 6c dd 18 00 50 f2 02 01 01 86 00 03 a4 00 00 27 a4 00 00 42 43 5e 00 62 32 2f 00 dd 09 00 03 7f 01 01 00 00 ff 7f dd 0a 00 03 7f 04 01 00 06 00 40 00]
wlp2s0b1 (phy #0): connected to 64:70:02:df:4a:76
wlp2s0b1 (phy #0): CQM event: unknown event
wlp2s0b1 (phy #0): CQM event: unknown event
wlp2s0b1 (phy #0): CQM event: unknown event
wlp2s0b1 (phy #0): CQM event: unknown event
wlp2s0b1 (phy #0): CQM event: unknown event
wlp2s0b1 (phy #0): CQM event: unknown event
^C                                                                                                                                                                                             
                                                                                                                                                                                               
real    6m36.800s                                                                                                                                                                               
user    0m0.000s                                                                                                                                                                               
sys     0m0.000s

Code:

dmesg | grep b43
[   13.854218] b43-phy0: Broadcom 43228 WLAN found (core revision 30)
[   13.854641] b43-phy0: Found PHY: Analog 9, Type 4 (N), Revision 16
[   13.854650] b43-phy0: Found Radio: Manuf 0x17F, ID 0x2057, Revision 9, Version 1
[   14.365340] b43 bcma0:1 wlp2s0b1: renamed from wlan0
[   19.642002] b43-phy0: Loading firmware version 784.2 (2012-08-15 21:35:19)

Code:

dmesg | grep 80211
[   13.525312] cfg80211: Calling CRDA to update world regulatory domain
[   13.900483] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[   14.702651] cfg80211: World regulatory domain updated:
[   14.702652] cfg80211:  DFS Master region: unset
[   14.702653] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[   14.702655] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[   14.702657] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[   14.702658] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
[   14.702659] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[   14.702661] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[   14.702662] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
[   14.702663] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
[   14.702664] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
[ 1823.123992] cfg80211: Calling CRDA to update world regulatory domain
[ 1823.125892] cfg80211: World regulatory domain updated:
[ 1823.125894] cfg80211:  DFS Master region: unset
[ 1823.125895] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[ 1823.125897] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[ 1823.125898] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[ 1823.125899] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
[ 1823.125901] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[ 1823.125902] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[ 1823.125904] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
[ 1823.125905] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
[ 1823.125906] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)


Luckely during this data collection session I lost connection. I played on youtube a long song and suddenly the music stopped. I hope this output give you some information.
I gained a new connection by ifconfig wlp2s0b1 down/up.
_________________
Nulla tenaci invia est via
Back to top
View user's profile Send private message
khayyam
Watchman
Watchman


Joined: 07 Jun 2012
Posts: 6228
Location: Room 101

PostPosted: Thu Jan 21, 2016 12:06 am    Post subject: Reply with quote

GenHeDi ... here's what (little) I can tell you ...

GenHeDi wrote:
Code:
wlp2s0b1 (phy #0): CQM event: unknown event

CQM is "connection quality monitor", such an "unknown event" probably means a buggy driver, if it were protocol related it would probably know, and report, the cause.

The dump shows some level of failed TX (transmissions), which we can attribute either to the driver (bug), or radio interference. When you get transmission failures the bitrate drops, higher bitrates translate to tighter packed frames (and so more chance of collision/failure) so stepping down is normal/expected ... though, as you noticed, it effects throughput.

So, we know something is wrong, and given the 'unknown event' I'd suspect it's either hardware, or the driver (rather than general radio interference).

GenHeDi wrote:
I gained a new connection by ifconfig wlp2s0b1 down/up.

If you're runing wpa_supplicant from /etc/init.d/net.wlp2s0b1 you shouldn't need to, wpa_cli should be running and will call /etc/wpa_supplicant/wpa_cli.sh when DISCONNECT is registered. Does it not automatically reconnect (if not this is another hint at a driver bug).

best ... khay
Back to top
View user's profile Send private message
NForce
Tux's lil' helper
Tux's lil' helper


Joined: 07 Nov 2009
Posts: 79
Location: Kaunas, Lithuania

PostPosted: Thu Jan 21, 2016 3:17 pm    Post subject: Reply with quote

Have you tried cutting proprietary broadcom firmware with b43-fwcutter? That helped me on fedora once, not long time ago. I had exactly the same problem (connection dropped after a while)
Back to top
View user's profile Send private message
GenHeDi
Tux's lil' helper
Tux's lil' helper


Joined: 02 Jan 2016
Posts: 122

PostPosted: Thu Jan 21, 2016 7:35 pm    Post subject: Reply with quote

@khayyam
Yes, I'm running wpa_supplicant from /etc/init.d/net.wlp2s0b1 and it is definitely not always reconnecting automatically. I checked /etc/wpa_supplicant/wpa_cli.sh and it is available.
The only way to reconnect in current situation is to execute ifconfig wlp2s0b1 down/up. Although sometimes the connection get suddenly slow and the browser is waiting on traffic from the visited site. I think that during those moments it is reconnecting automatically, but definitely not always.

@NForce
Nope, at this moment I'm using the standard b43 driver delivered with the Gentoo installation. Cutting proprietary firmware is new stuff for me, is it possible to explain some steps to follow?

Regards to all
_________________
Nulla tenaci invia est via
Back to top
View user's profile Send private message
yaclo
n00b
n00b


Joined: 11 Sep 2015
Posts: 20

PostPosted: Thu Jan 21, 2016 7:50 pm    Post subject: Reply with quote

you may try another driver for broadcom wifi cards

Code:
emerge broadcom-wl
Back to top
View user's profile Send private message
khayyam
Watchman
Watchman


Joined: 07 Jun 2012
Posts: 6228
Location: Room 101

PostPosted: Thu Jan 21, 2016 7:56 pm    Post subject: Reply with quote

GenHeDi wrote:
Yes, I'm running wpa_supplicant from /etc/init.d/net.wlp2s0b1 and it is definitely not always reconnecting automatically. I checked /etc/wpa_supplicant/wpa_cli.sh and it is available. The only way to reconnect in current situation is to execute ifconfig wlp2s0b1 down/up. Although sometimes the connection get suddenly slow and the browser is waiting on traffic from the visited site. I think that during those moments it is reconnecting automatically, but definitely not always.

GenHeDi ... if you get 'disconnected (by AP) reason:' then it should automatically attempt to reconnect, you'll see this in 'iw event -f' (as in the above) ... are you saying that this occurs but no connection is established? I'm not really sure I understand why you think its not doing this (even if irratically). Please try adding the following to the global definitions in wpa_supplicant.conf

/etc/wpa_supplicant/wpa_supplicant.conf:
eapol_version=2
fast_reauth=1

BTW, rather than 'ifconfig iface up/down' you can do 'wpa_cli reconnect'.

best ... khay
Back to top
View user's profile Send private message
Logicien
Veteran
Veteran


Joined: 16 Sep 2005
Posts: 1368
Location: Montréal

PostPosted: Thu Jan 21, 2016 10:17 pm    Post subject: Reply with quote

According with the b43 page, b43 only support the BCM43228 device with the PCI-ID 14e4:4359 , unless the chip ID do not correspond to it's PCI-ID.

So, the output of the command
Code:
lspci -d 1404: -nn

will help to be sure if b43 support this Broadcom device.
_________________
Paul
Back to top
View user's profile Send private message
Logicien
Veteran
Veteran


Joined: 16 Sep 2005
Posts: 1368
Location: Montréal

PostPosted: Thu Jan 21, 2016 10:46 pm    Post subject: Reply with quote

GenHeDi wrote:
time iw event -f
wlp2s0b1: del station 64:70:02:df:4a:76
wlp2s0b1 (phy #0): deauth 64:70:02:df:4a:76 -> 30:10:b3:0e:6b:20 reason 2: Previous authentication no longer valid [frame: c0 08 40 01 30 10 b3 0e 6b 20 64 70 02 df 4a 76 64 70 02 df 4a 76 90 12 02 00]
wlp2s0b1 (phy #0): disconnected (by AP) reason: 2: Previous authentication no longer valid


The deauthentication reason is 2. According with the page Linux WiFi: Deauthenticated Reason Codes, the client is authentificated but not authorised. The problem can come from the AP router configuration and/or the client permissions.

I have seen Wireless connects, then disconnect as Solved problem for reason 2 deauthentication by changing the AP configuration to only accept Wpa authentification encryption.
_________________
Paul


Last edited by Logicien on Thu Jan 21, 2016 10:56 pm; edited 4 times in total
Back to top
View user's profile Send private message
khayyam
Watchman
Watchman


Joined: 07 Jun 2012
Posts: 6228
Location: Room 101

PostPosted: Thu Jan 21, 2016 10:47 pm    Post subject: Reply with quote

Logicien wrote:
According with the b43 page, b43 only support the BCM43228 device with the PCI-ID 14e4:4359

Logicien ... good point, at least its worth checking this is in fact a suitable driver. Also, as it provides 'wl' as an "alternative" I would probably suggest GenHeDi give that a try.

yaclo wrote:
you may try another driver for broadcom wifi cards

Code:
emerge broadcom-wl

I don't see such a package, that is the package name used in Arch Linux but I think the gentoo package is net-wireless/broadcom-sta.

best ... khay
Back to top
View user's profile Send private message
GenHeDi
Tux's lil' helper
Tux's lil' helper


Joined: 02 Jan 2016
Posts: 122

PostPosted: Fri Jan 22, 2016 5:17 pm    Post subject: Reply with quote

Logicien: thanks for joining and supporting.
Code:

lspci | grep Broadcom
02:00.0 Network controller: Broadcom Corporation BCM43228 802.11a/b/g/n

Code:

lspci -n | grep 14e4
02:00.0 0280: 14e4:4359

_________________
Nulla tenaci invia est via
Back to top
View user's profile Send private message
GenHeDi
Tux's lil' helper
Tux's lil' helper


Joined: 02 Jan 2016
Posts: 122

PostPosted: Fri Jan 22, 2016 5:34 pm    Post subject: Reply with quote

I had a look in my router (a TP-Link TL-WR1043ND) and I have following options:

WPA/WPA2 - personal (recommended) >> is selected (also possible to select WPA/WPA2 - enterprice)

- version > automatic (recommended) >> is selected
> WPA-PSK
> WPA2-PSK

- encryption > automatic (recommended)
> TKIP
> AES >>>> is selected
_________________
Nulla tenaci invia est via
Back to top
View user's profile Send private message
GenHeDi
Tux's lil' helper
Tux's lil' helper


Joined: 02 Jan 2016
Posts: 122

PostPosted: Fri Jan 22, 2016 5:47 pm    Post subject: Reply with quote

@khayyam
Quote:
if you get 'disconnected (by AP) reason:' then it should automatically attempt to reconnect, you'll see this in 'iw event -f' (as in the above) ... are you saying that this occurs but no connection is established? I'm not really sure I understand why you think its not doing this (even if irratically)


It is an assumption, not based on data. I was just looking at the screen of the browser and not looking into log-files. I apologize for the fact that I might have put you on the wrong track.

Fact is that my connection was frozen while collecting the data above.
_________________
Nulla tenaci invia est via
Back to top
View user's profile Send private message
yaclo
n00b
n00b


Joined: 11 Sep 2015
Posts: 20

PostPosted: Fri Jan 22, 2016 7:13 pm    Post subject: Reply with quote

khayyam wrote:
Logicien wrote:
According with the b43 page, b43 only support the BCM43228 device with the PCI-ID 14e4:4359

Logicien ... good point, at least its worth checking this is in fact a suitable driver. Also, as it provides 'wl' as an "alternative" I would probably suggest GenHeDi give that a try.

yaclo wrote:
you may try another driver for broadcom wifi cards

Code:
emerge broadcom-wl

I don't see such a package, that is the package name used in Arch Linux but I think the gentoo package is net-wireless/broadcom-sta.

best ... khay


you're right
thanks
Back to top
View user's profile Send private message
khayyam
Watchman
Watchman


Joined: 07 Jun 2012
Posts: 6228
Location: Room 101

PostPosted: Sat Jan 23, 2016 3:07 am    Post subject: Reply with quote

Logicien wrote:
The deauthentication reason is 2. According with the page Linux WiFi: Deauthenticated Reason Codes, the client is authentificated but not authorised. The problem can come from the AP router configuration and/or the client permissions.

Logicien ... it can happen if there is a breakdown in transmission (lost beacon) between the AP and the STA.

Logicien wrote:
I have seen Wireless connects, then disconnect as Solved problem for reason 2 deauthentication by changing the AP configuration to only accept Wpa authentification encryption.

I don't think this is the case, the above suggests the issue is not on the protocol level. These things are always very difficult to debug because radio is inherently prone to environmental pollution. So, it *could* in fact be anything (ie, the Faraday effect, location, weather, solar flares, heavy traffic in the same spectrum from adjacent AP's ... you name it), but I would suspect the hardware/driver based on the above (and assuming GenHeDi doesn't have similar issues with other clients/OSes/machines).

best ... khay
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Goto page 1, 2, 3, 4  Next
Page 1 of 4

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum