Broadcom BCM4360 woes, fear it will not work - pls confirm

Questions about Wi-Fi and other network devices, file sharing, firewalls, connection sharing etc
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
titianmom
Level 3
Level 3
Posts: 156
Joined: Thu Jan 07, 2010 12:32 am

Broadcom BCM4360 woes, fear it will not work - pls confirm

Post by titianmom »

Hi,

I picked up a used desktop with good bones, but it came with a Broadcom card (BC4360) (okay, so some bones not so good...).

Since BCM4360 isn't listed under STA or B43 legacy, am I doomed? I tried to use the Driver Manager to install using the STA that it detected, got all excited when the card went live, but it works for about 4-5 mins and then the Upload/Download stalls to next to nothing in speed and then it dies.

(Fortunately I have a cheap USB wireless or I wouldn't be typing in the Forum as we speak...)

under /lib/firmware, I've got everything installed: b43, b43legacy and I'm guessing something for wl since I used the Driver Manager.

I'm running Mint 17 Xfce.

Code: Select all

mom@family-desktop ~ $ lspci -vvnn |grep 14e4
02:00.0 Network controller [0280]: Broadcom Corporation BCM4360 802.11ac Wireless Network Adapter [14e4:43a0] (rev 02)

mom@family-desktop ~ $ lsmod
Module                  Size  Used by
b43                   387371  0 
bcma                   52096  1 b43
ssb                    62379  1 b43
arc4                   12608  2 
rt2800usb              27034  0 
rt2x00usb              20742  1 rt2800usb
rt2800lib              89076  1 rt2800usb
rt2x00lib              55307  3 rt2x00usb,rt2800lib,rt2800usb
mac80211              626489  4 b43,rt2x00lib,rt2x00usb,rt2800lib
crc_ccitt              12707  1 rt2800lib
rfcomm                 69160  8 
bnep                   19624  2 
binfmt_misc            17468  1 
snd_hda_codec_hdmi     46207  4 
btusb                  32412  0 
bluetooth             395423  22 bnep,btusb,rfcomm
dm_multipath           22873  0 
scsi_dh                14882  1 dm_multipath
joydev                 17381  0 
snd_hda_codec_realtek    61438  1 
kvm_amd                59987  0 
kvm                   451511  1 kvm_amd
serio_raw              13462  0 
k10temp                13126  0 
edac_core              62291  0 
snd_hda_intel          52355  5 
edac_mce_amd           22617  0 
snd_hda_codec         192906  3 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_intel
snd_hwdep              13602  1 snd_hda_codec
snd_seq_midi           13324  0 
snd_seq_midi_event     14899  1 snd_seq_midi
snd_pcm               102099  3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel
snd_page_alloc         18710  2 snd_pcm,snd_hda_intel
snd_rawmidi            30144  1 snd_seq_midi
lib80211_crypt_tkip    17619  0 
sp5100_tco             13979  0 
i2c_piix4              22155  0 
wl                   4207846  0 
snd_seq                61560  2 snd_seq_midi_event,snd_seq_midi
lib80211               14381  2 wl,lib80211_crypt_tkip
snd_seq_device         14497  3 snd_seq,snd_rawmidi,snd_seq_midi
snd_timer              29482  2 snd_pcm,snd_seq
cfg80211              484040  4 wl,b43,mac80211,rt2x00lib
snd                    69238  21 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_rawmidi,snd_hda_codec,snd_hda_intel,snd_seq_device,snd_seq_midi
soundcore              12680  1 snd
mac_hid                13205  0 
parport_pc             32701  0 
ppdev                  17671  0 
lp                     17759  0 
parport                42348  3 lp,ppdev,parport_pc
dm_mirror              22135  0 
dm_region_hash         20862  1 dm_mirror
dm_log                 18411  2 dm_region_hash,dm_mirror
hid_generic            12548  0 
usbhid                 52616  0 
hid                   106148  2 hid_generic,usbhid
pata_acpi              13038  0 
nouveau              1097199  3 
mxm_wmi                13021  1 nouveau
wmi                    19177  2 mxm_wmi,nouveau
video                  19476  1 nouveau
i2c_algo_bit           13413  1 nouveau
ttm                    85115  1 nouveau
r8169                  67581  0 
mii                    13934  1 r8169
pata_jmicron           12758  0 
drm_kms_helper         52758  1 nouveau
drm                   302817  5 ttm,drm_kms_helper,nouveau
ahci                   25819  3 
libahci                32168  1 ahci
pata_atiixp            13271  0 
mom@family-desktop ~ $ 

Would using ndiswrapper work? Don't know much about it other than the descript; never used it before and I believe it isn't supported any more? But worth a shot?

Would it do any good to compile the beast myself? I'm guessing not....

Would it do any good to try the card under Mint Debian, instead of Qiana?

Thanks in advance, Kim
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
titianmom
Level 3
Level 3
Posts: 156
Joined: Thu Jan 07, 2010 12:32 am

Re: Broadcom BCM4360 woes, fear it will not work - pls confi

Post by titianmom »

On second thought, I might need to re-compile. Found this on the Broadcom linux driver page: http://www.broadcom.com/support/802.11/linux_sta.php

64-bit driver 6.30.223.248 07/08/2014 Download Zip File <---later number than Mint's under Driver Manager.

Mint's Driver Manager says:

bcmwl-kernel-source
Version 6.30.223.141+bdcom-0ubuntu2 <----notice version number?
Broadcom 802.11 Linux STA wireless driver source


So, should I just re-compile and re-install the one on Broadcom's website? Guess I should try.

Now the current driver I have running, from the Driver Manager under Mint 17 is working, but really flaky and keep dropping out on me....

Kim
PatH57

Re: Broadcom BCM4360 woes, fear it will not work - pls confi

Post by PatH57 »

Hi,

just make sure to remove the b43 first and blacklist it. (it's the buggy one you are using right now)
or you could use the one in the channel first, see if it works?
titianmom
Level 3
Level 3
Posts: 156
Joined: Thu Jan 07, 2010 12:32 am

Re: Broadcom BCM4360 woes, fear it will not work - pls confi

Post by titianmom »

Oddly enough, b43 wasn't listed in the "lsmod", but wl was. As far as blacklisting: b43 had its own, personal blacklist file; obviously the great minds don't want us using it.

I went to: http://www.broadcom.com/support/802.11/linux_sta.php and downloaded, compiled and installed their latest and greatest wl.ko.

Rebooted, logged in....took a few seconds to connect, but I'm up. We'll see how long this one lasts. The one in Mint's Driver Manager supports up to 3.8 but we're all running
3.13.0.whatever.

The newest package off of Broadcom's page (above) supports up to 3.11.x. Also, BCM4360 *was* listed down at the end (4360 Dualband 0x14e4 0x43a0), so lets keep our toezies crossed that this newest attempt at a driver works for Mint 17.

I will watch it, if it crashes I'll report. If not---wooopiiieeee! I'll close this thread out in a day or two; don't want to get ahead of myself tonight and close it. Too gun-shy.

'think I'll watch a movie off hulu. If that doesn't kill it, nothing will. Wouldn't dare start a torrent right now... :lol:

Kim
titianmom
Level 3
Level 3
Posts: 156
Joined: Thu Jan 07, 2010 12:32 am

Re: Broadcom BCM4360 woes, fear it will not work - pls confi

Post by titianmom »

Bad news. Dropping out, weird (tainted) Kernel messages, etc. See excerpts of Syslog:

Code: Select all

mom@family-desktop ~ $ more newestjunk
Jul 31 20:42:43 family-desktop wpa_supplicant[858]: wlan1: Trying to associate with 00:1a:70:7a:51:29 (SSID='
twooldfolks' freq=2437 MHz)
Jul 31 20:42:43 family-desktop NetworkManager[837]: <info> (wlan1): supplicant interface state: scanning -> a
ssociating
Jul 31 20:42:53 family-desktop wpa_supplicant[858]: wlan1: Authentication with 00:1a:70:7a:51:29 timed out.
Jul 31 20:42:53 family-desktop wpa_supplicant[858]: wlan1: CTRL-EVENT-DISCONNECTED bssid=00:1a:70:7a:51:29 re
ason=3 locally_generated=1
Jul 31 20:42:53 family-desktop NetworkManager[837]: <warn> Connection disconnected (reason -3)
Jul 31 20:42:53 family-desktop NetworkManager[837]: <info> (wlan1): supplicant interface state: associating -
> disconnected
Jul 31 20:42:53 family-desktop wpa_supplicant[858]: wlan1: CTRL-EVENT-SCAN-STARTED 
Jul 31 20:42:53 family-desktop NetworkManager[837]: <info> (wlan1): supplicant interface state: disconnected 
-> scanning
Jul 31 20:42:55 family-desktop wpa_supplicant[858]: wlan1: Trying to associate with 00:1a:70:7a:51:29 (SSID='
twooldfolks' freq=2437 MHz)
Jul 31 20:42:55 family-desktop NetworkManager[837]: <info> (wlan1): supplicant interface state: scanning -> a
ssociating
Jul 31 20:42:56 family-desktop wpa_supplicant[858]: wlan1: Associated with 00:1a:70:7a:51:29
Jul 31 20:42:56 family-desktop wpa_supplicant[858]: wlan1: CTRL-EVENT-CONNECTED - Connection to 00:1a:70:7a:5
1:29 completed [id=0 id_str=]
Jul 31 20:42:56 family-desktop NetworkManager[837]: <info> (wlan1): supplicant interface state: associating -
> completed
Jul 31 20:42:56 family-desktop NetworkManager[837]: <info> Activation (wlan1/wireless) Stage 2 of 5 (Device C
onfigure) successful.  Connected to wireless network 'twooldfolks'.
Jul 31 20:42:56 family-desktop NetworkManager[837]: <info> Activation (wlan1) Stage 3 of 5 (IP Configure Star
t) scheduled.
Jul 31 20:42:56 family-desktop NetworkManager[837]: <info> Activation (wlan1) Stage 3 of 5 (IP Configure Star
t) started...
Jul 31 20:42:56 family-desktop NetworkManager[837]: <info> (wlan1): device state change: config -> ip-config 
(reason 'none') [50 70 0]
Jul 31 20:42:56 family-desktop NetworkManager[837]: <info> Activation (wlan1) Beginning DHCPv4 transaction (t
imeout in 45 seconds)
Jul 31 20:42:56 family-desktop NetworkManager[837]: <info> dhclient started with pid 2327
Jul 31 20:42:56 family-desktop NetworkManager[837]: <info> Activation (wlan1) Beginning IP6 addrconf.
Jul 31 20:42:56 family-desktop avahi-daemon[803]: Withdrawing address record for fe80::62a4:4cff:fe82:a270 on
 wlan1.
Jul 31 20:42:56 family-desktop avahi-daemon[803]: Leaving mDNS multicast group on interface wlan1.IPv6 with a
ddress fe80::62a4:4cff:fe82:a270.
Jul 31 20:42:56 family-desktop avahi-daemon[803]: Interface wlan1.IPv6 no longer relevant for mDNS.
Jul 31 20:42:56 family-desktop NetworkManager[837]: <info> Activation (wlan1) Stage 3 of 5 (IP Configure Star
t) complete.


Jul 31 20:48:12 family-desktop dhclient: Internet Systems Consortium DHCP Client 4.2.4
Jul 31 20:48:12 family-desktop dhclient: Copyright 2004-2012 Internet Systems Consortium.
Jul 31 20:48:12 family-desktop dhclient: All rights reserved.
Jul 31 20:48:12 family-desktop dhclient: For info, please visit https://www.isc.org/software/dhcp/
Jul 31 20:48:12 family-desktop dhclient: 
Jul 31 20:48:12 family-desktop NetworkManager[837]: <info> (wlan1): DHCPv4 state changed nbi -> preinit
Jul 31 20:48:12 family-desktop dhclient: Listening on LPF/wlan1/60:a4:4c:82:a2:70
Jul 31 20:48:12 family-desktop dhclient: Sending on   LPF/wlan1/60:a4:4c:82:a2:70
Jul 31 20:48:12 family-desktop dhclient: Sending on   Socket/fallback
Jul 31 20:48:12 family-desktop dhclient: DHCPREQUEST of 192.168.1.102 on wlan1 to 255.255.255.255 port 67 (xi
d=0x7e1f4804)
Jul 31 20:48:12 family-desktop dhclient: DHCPACK of 192.168.1.102 from 192.168.1.1
Jul 31 20:48:12 family-desktop dhclient: bound to 192.168.1.102 -- renewal in 37496 seconds.
Jul 31 20:48:12 family-desktop NetworkManager[837]: <info> (wlan1): DHCPv4 state changed preinit -> reboot
Jul 31 20:48:12 family-desktop NetworkManager[837]: <info>   address 192.168.1.102
Jul 31 20:48:12 family-desktop NetworkManager[837]: <info>   prefix 24 (255.255.255.0)
Jul 31 20:48:12 family-desktop NetworkManager[837]: <info>   gateway 192.168.1.1
Jul 31 20:48:12 family-desktop NetworkManager[837]: <info>   hostname 'family-desktop'
Jul 31 20:48:12 family-desktop NetworkManager[837]: <info>   nameserver '75.75.75.75'
Jul 31 20:48:12 family-desktop NetworkManager[837]: <info>   nameserver '75.75.76.76'
Jul 31 20:48:12 family-desktop NetworkManager[837]: <info>   domain name 'hsd1.wv.comcast.net.'
Jul 31 20:48:12 family-desktop NetworkManager[837]: <info> Activation (wlan1) Stage 5 of 5 (IPv4 Configure Co
mmit) scheduled...
Jul 31 20:48:12 family-desktop NetworkManager[837]: <info> Activation (wlan1) Stage 5 of 5 (IPv4 Commit) star
ted...
Jul 31 20:48:12 family-desktop avahi-daemon[803]: Joining mDNS multicast group on interface wlan1.IPv4 with a
ddress 192.168.1.102.
Jul 31 20:48:12 family-desktop avahi-daemon[803]: New relevant interface wlan1.IPv4 for mDNS.
Jul 31 20:48:12 family-desktop avahi-daemon[803]: Registering new address record for 192.168.1.102 on wlan1.I
Pv4.
Jul 31 20:48:13 family-desktop NetworkManager[837]: <info> (wlan1): device state change: ip-config -> seconda
ries (reason 'none') [70 90 0]
Jul 31 20:48:13 family-desktop NetworkManager[837]: <info> Activation (wlan1) Stage 5 of 5 (IPv4 Commit) comp
lete.
Jul 31 20:48:13 family-desktop NetworkManager[837]: <info> (wlan1): device state change: secondaries -> activ
ated (reason 'none') [90 100 0]
Jul 31 20:48:13 family-desktop NetworkManager[837]: <info> NetworkManager state is now CONNECTED_GLOBAL
Jul 31 20:48:13 family-desktop NetworkManager[837]: <info> Policy set 'twooldfolks' (wlan1) as default for IP
v4 routing and DNS.
Jul 31 20:48:13 family-desktop NetworkManager[837]: <info> Writing DNS information to /sbin/resolvconf
Jul 31 20:48:13 family-desktop dnsmasq[2330]: setting upstream servers from DBus
Jul 31 20:48:13 family-desktop dnsmasq[2330]: using nameserver 75.75.76.76#53
Jul 31 20:48:13 family-desktop dnsmasq[2330]: using nameserver 75.75.75.75#53
Jul 31 20:48:13 family-desktop NetworkManager[837]: <info> Activation (wlan1) successful, device activated.
Jul 31 20:48:13 family-desktop dbus[735]: [system] Activating service name='org.freedesktop.nm_dispatcher' (u
sing servicehelper)
Jul 31 20:48:13 family-desktop dbus[735]: [system] Successfully activated service 'org.freedesktop.nm_dispatc
her'
Jul 31 20:48:14 family-desktop avahi-daemon[803]: Joining mDNS multicast group on interface wlan1.IPv6 with a
ddress fe80::62a4:4cff:fe82:a270.
Jul 31 20:48:14 family-desktop avahi-daemon[803]: New relevant interface wlan1.IPv6 for mDNS.
Jul 31 20:48:14 family-desktop avahi-daemon[803]: Registering new address record for fe80::62a4:4cff:fe82:a27
0 on wlan1.*.
Jul 31 20:48:20 family-desktop ntpdate[2625]: adjust time server 91.189.89.199 offset -0.098464 sec
Jul 31 20:48:29 family-desktop wpa_supplicant[858]: wlan1: CTRL-EVENT-SCAN-STARTED 
Jul 31 20:48:32 family-desktop NetworkManager[837]: <info> (wlan1): IP6 addrconf timed out or failed.
Jul 31 20:48:32 family-desktop NetworkManager[837]: <info> Activation (wlan1) Stage 4 of 5 (IPv6 Configure Ti
meout) scheduled...
Jul 31 20:48:32 family-desktop NetworkManager[837]: <info> Activation (wlan1) Stage 4 of 5 (IPv6 Configure Ti
meout) started...
Jul 31 20:48:32 family-desktop NetworkManager[837]: <info> Activation (wlan1) Stage 4 of 5 (IPv6 Configure Ti
meout) complete.
mom@family-desktop ~ $ 

mom@family-desktop ~ $ tail -20 /var/log/syslog
Jul 31 20:52:34 family-desktop kernel: [  656.415837]  [<ffffffff8108b240>] ? kthread_create_on_node+0x1d0/0x
1d0
Jul 31 20:52:34 family-desktop kernel: [  656.415845]  [<ffffffff8172637c>] ret_from_fork+0x7c/0xb0
Jul 31 20:52:34 family-desktop kernel: [  656.415853]  [<ffffffff8108b240>] ? kthread_create_on_node+0x1d0/0x
1d0
Jul 31 20:52:34 family-desktop kernel: [  656.415858] ---[ end trace 4dd55edd3527d401 ]---
Jul 31 20:52:34 family-desktop NetworkManager[837]: <info> (wlan1): supplicant interface state: associated ->
 disconnected
Jul 31 20:52:34 family-desktop wpa_supplicant[858]: wlan1: CTRL-EVENT-SCAN-STARTED 
Jul 31 20:52:34 family-desktop NetworkManager[837]: <info> (wlan1): supplicant interface state: disconnected 
-> scanning
Jul 31 20:52:42 family-desktop wpa_supplicant[858]: wlan1: CTRL-EVENT-SCAN-STARTED 
Jul 31 20:52:44 family-desktop wpa_supplicant[858]: wlan1: CTRL-EVENT-SSID-REENABLED id=0 ssid="twooldfolks"
Jul 31 20:52:51 family-desktop NetworkManager[837]: <warn> Activation (wlan1/wireless): association took too 
long.
Jul 31 20:52:51 family-desktop NetworkManager[837]: <info> (wlan1): device state change: config -> failed (re
ason 'no-secrets') [50 120 7]
Jul 31 20:52:51 family-desktop NetworkManager[837]: <info> NetworkManager state is now DISCONNECTED
Jul 31 20:52:51 family-desktop NetworkManager[837]: <info> Marking connection 'twooldfolks' invalid.
Jul 31 20:52:51 family-desktop NetworkManager[837]: <warn> Activation (wlan1) failed for connection 'twooldfo
lks'
Jul 31 20:52:51 family-desktop NetworkManager[837]: <warn> Couldn't disconnect supplicant interface: This int
erface is not connected.
Jul 31 20:52:51 family-desktop NetworkManager[837]: <info> (wlan1): device state change: failed -> disconnect
ed (reason 'none') [120 30 0]
Jul 31 20:52:51 family-desktop NetworkManager[837]: <info> (wlan1): deactivating device (reason 'none') [0]
Jul 31 20:52:51 family-desktop wpa_supplicant[858]: wlan1: CTRL-EVENT-SCAN-STARTED 
Jul 31 20:52:51 family-desktop NetworkManager[837]: <warn> Couldn't disconnect supplicant interface: This int
erface is not connected.
Jul 31 20:52:53 family-desktop NetworkManager[837]: <info> (wlan1): supplicant interface state: scanning -> i
nactive
mom@family-desktop ~ $ 


Jul 31 20:52:34 family-desktop wpa_supplicant[858]: wlan1: CTRL-EVENT-SCAN-STARTED 
Jul 31 20:52:34 family-desktop NetworkManager[837]: <info> (wlan1): supplicant interface state: disconnected 
-> scanning
Jul 31 20:52:42 family-desktop wpa_supplicant[858]: wlan1: CTRL-EVENT-SCAN-STARTED 
Jul 31 20:52:44 family-desktop wpa_supplicant[858]: wlan1: CTRL-EVENT-SSID-REENABLED id=0 ssid="twooldfolks"
Jul 31 20:52:51 family-desktop NetworkManager[837]: <warn> Activation (wlan1/wireless): association took too 
long.
Jul 31 20:52:51 family-desktop NetworkManager[837]: <info> (wlan1): device state change: config -> failed (re
ason 'no-secrets') [50 120 7]
Jul 31 20:52:51 family-desktop NetworkManager[837]: <info> NetworkManager state is now DISCONNECTED
Jul 31 20:52:51 family-desktop NetworkManager[837]: <info> Marking connection 'twooldfolks' invalid.
Jul 31 20:52:51 family-desktop NetworkManager[837]: <warn> Activation (wlan1) failed for connection 'twooldfo
lks'
Jul 31 20:52:51 family-desktop NetworkManager[837]: <warn> Couldn't disconnect supplicant interface: This int
erface is not connected.
Jul 31 20:52:51 family-desktop NetworkManager[837]: <info> (wlan1): device state change: failed -> disconnect
ed (reason 'none') [120 30 0]
Jul 31 20:52:51 family-desktop NetworkManager[837]: <info> (wlan1): deactivating device (reason 'none') [0]
Jul 31 20:52:51 family-desktop wpa_supplicant[858]: wlan1: CTRL-EVENT-SCAN-STARTED 
Jul 31 20:52:51 family-desktop NetworkManager[837]: <warn> Couldn't disconnect supplicant interface: This int
erface is not connected.
Jul 31 20:52:53 family-desktop NetworkManager[837]: <info> (wlan1): supplicant interface state: scanning -> i
nactive
Jul 31 20:59:38 family-desktop wpa_supplicant[858]: message repeated 9 times: [ wlan1: CTRL-EVENT-SCAN-STARTE
D ]
Jul 31 20:59:40 family-desktop wpa_supplicant[858]: nl80211: Was expecting local disconnect but got another d
isconnect event first
Jul 31 20:59:40 family-desktop kernel: [ 1082.685834] cfg80211: Calling CRDA to update world regulatory domai
n
Jul 31 20:59:40 family-desktop NetworkManager[837]: <info> (wlan1): supplicant interface state: inactive -> d
isconnected
Jul 31 20:59:40 family-desktop kernel: [ 1082.693617] cfg80211: World regulatory domain updated:
Jul 31 20:59:40 family-desktop kernel: [ 1082.693625] cfg80211:   (start_freq - end_freq @ bandwidth), (max_a
ntenna_gain, max_eirp)
Jul 31 20:59:40 family-desktop kernel: [ 1082.693670] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (3
00 mBi, 2000 mBm)
Jul 31 20:59:40 family-desktop kernel: [ 1082.693676] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (3
00 mBi, 2000 mBm)
Jul 31 20:59:40 family-desktop kernel: [ 1082.693701] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (3
00 mBi, 2000 mBm)
Jul 31 20:59:40 family-desktop kernel: [ 1082.693711] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (3
00 mBi, 2000 mBm)
Jul 31 20:59:40 family-desktop kernel: [ 1082.693716] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (3
00 mBi, 2000 mBm)
Jul 31 20:59:40 family-desktop NetworkManager[837]: <info> (wlan1): supplicant interface state: disconnected 
-> inactive
Jul 31 20:59:45 family-desktop kernel: [ 1087.455939] ------------[ cut here ]------------
Jul 31 20:59:45 family-desktop kernel: [ 1087.456003] WARNING: CPU: 3 PID: 501 at /build/buildd/linux-3.13.0/
net/wireless/sme.c:797 cfg80211_roamed+0x89/0x90 [cfg80211]()
Jul 31 20:59:45 family-desktop kernel: [ 1087.456008] Modules linked in: rfcomm bnep binfmt_misc snd_hda_code
c_hdmi btusb bluetooth joydev kvm_amd kvm lib80211_crypt_tkip snd_hda_codec_realtek dm_multipath scsi_dh wl(P
OF) serio_raw snd_seq_midi snd_seq_midi_event snd_hda_intel lib80211 k10temp snd_hda_codec edac_core edac_mce
_amd snd_hwdep snd_rawmidi snd_pcm snd_page_alloc snd_seq sp5100_tco i2c_piix4 snd_seq_device snd_timer cfg80
211 snd soundcore mac_hid parport_pc ppdev lp parport dm_mirror dm_region_hash dm_log hid_generic usbhid hid 
pata_acpi nouveau r8169 mxm_wmi mii wmi video i2c_algo_bit ttm pata_jmicron drm_kms_helper pata_atiixp drm ah
ci libahci
Jul 31 20:59:45 family-desktop kernel: [ 1087.456110] CPU: 3 PID: 501 Comm: wl_event_handle Tainted: PF      
 W  O 3.13.0-24-generic #46-Ubuntu
Jul 31 20:59:45 family-desktop kernel: [ 1087.456116] Hardware name: MSI MS-7599/870S-G54 (MS-7599), BIOS V17
.20 11/27/2012
Jul 31 20:59:45 family-desktop kernel: [ 1087.456121]  0000000000000009 ffff880035797d88 ffffffff81715a64 000
0000000000000
Jul 31 20:59:45 family-desktop kernel: [ 1087.456132]  ffff880035797dc0 ffffffff810676bd ffff880223fb5000 fff
f88021fa16d80
Jul 31 20:59:45 family-desktop kernel: [ 1087.456141]  0000000000000044 ffff8800c907da40 0000000000000001 fff
f880035797dd0
Jul 31 20:59:45 family-desktop kernel: [ 1087.456150] Call Trace:
Jul 31 20:59:45 family-desktop kernel: [ 1087.456164]  [<ffffffff81715a64>] dump_stack+0x45/0x56
Jul 31 20:59:45 family-desktop kernel: [ 1087.456173]  [<ffffffff810676bd>] warn_slowpath_common+0x7d/0xa0
Jul 31 20:59:45 family-desktop kernel: [ 1087.456181]  [<ffffffff8106779a>] warn_slowpath_null+0x1a/0x20
Jul 31 20:59:45 family-desktop kernel: [ 1087.456215]  [<ffffffffa028f509>] cfg80211_roamed+0x89/0x90 [cfg802
11]
Jul 31 20:59:45 family-desktop kernel: [ 1087.456295]  [<ffffffffa051f528>] wl_bss_connect_done.isra.21+0x98/
0x1a0 [wl]
Jul 31 20:59:45 family-desktop kernel: [ 1087.456365]  [<ffffffffa051f82c>] wl_notify_connect_status+0x1fc/0x
410 [wl]
Jul 31 20:59:45 family-desktop kernel: [ 1087.456446]  [<ffffffffa051e135>] wl_event_handler+0x55/0x220 [wl]
Jul 31 20:59:45 family-desktop kernel: [ 1087.456526]  [<ffffffffa051e0e0>] ? wl_get_assoc_ies+0x240/0x240 [w
l]
Jul 31 20:59:45 family-desktop kernel: [ 1087.456534]  [<ffffffff8108b312>] kthread+0xd2/0xf0
Jul 31 20:59:45 family-desktop kernel: [ 1087.456542]  [<ffffffff8108b240>] ? kthread_create_on_node+0x1d0/0x
1d0
Jul 31 20:59:45 family-desktop kernel: [ 1087.456551]  [<ffffffff8172637c>] ret_from_fork+0x7c/0xb0
Jul 31 20:59:45 family-desktop kernel: [ 1087.456558]  [<ffffffff8108b240>] ? kthread_create_on_node+0x1d0/0x
1d0
Jul 31 20:59:45 family-desktop kernel: [ 1087.456564] ---[ end trace 4dd55edd3527d402 ]---
Jul 31 21:00:41 family-desktop wpa_supplicant[858]: wlan1: CTRL-EVENT-SCAN-STARTED 
Kim
PatH57

Re: Broadcom BCM4360 woes, fear it will not work - pls confi

Post by PatH57 »

Hi Kim,

I will try this week end to compile it for my 4312 with 3.15.6 and see how that goes.
In the meantime keep us posted.

See ya
titianmom
Level 3
Level 3
Posts: 156
Joined: Thu Jan 07, 2010 12:32 am

Re: Broadcom BCM4360 woes, fear it will not work - pls confi

Post by titianmom »

Funny that you want to jump to a later kernel when I'm seriously thinking of dropping back to 3.11.6 (LMDE) and compiling or installing Broadcom's latest for up to 3.11.x. I saw that LMDE has the source *and* the compiled version in their synaptic packages. (I have LMDE loaded on my laptop)

Anyway, have to tell you that its running great this morning!!! Still in Mint 17 with 3.13.x; I logged in--no lag time, no dropping, etc. Looked at the syslog and no errors at all.

Items of interest in dmesg:

cfg80211: Calling CRDA to update world regulatory domain

NOTE: That was what ran last night right before the card cleared up and ran smoothly. I have only an obvious wag idea of what "world regulatory domain" is, because I found this later on:

cfg80211: World regulatory domain updated:
[ 11.984556] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gai
n, max_eirp)
[ 11.984558] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 20
00 mBm)
[ 11.984559] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 20
00 mBm)
[ 11.984561] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 20
00 mBm)
[ 11.984562] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 20
00 mBm)
[ 11.984563] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 20
00 mBm)

-------------------

So with all of these freq adjustments, maybe that was the card's problem?? I do know that cfg80211 was a required module when I compiled the firmware for the card.

Later on in dmesg:

wl: module license 'MIXED/Proprietary' taints kernel.
[ 11.729362] Disabling lock debugging due to kernel taint
[ 11.731952] wl: module verification failed: signature and/or required key mi
ssing - tainting kernel
[ 11.748605] INFO @wl_cfg80211_attach : Registered CFG80211 phy

"wl", of course, is the new firmware/module for our Broadcom wireless.

Since this is a proprietary card, I'm (wagging) guessing that this has to do with a build looking for a normal key/registration for a proprietary load/purchased card...and maybe why CFG80211 has to be there?

Its that "taints kernel" thing that bugs me. :) I got the following errors while compiling last night:

WARNING: modpost: missing MODULE_LICENSE() in /home/mom/Downloads/hybrid_wl/wl.o
see include/linux/module.h for more information
WARNING: modpost: Found 1 section mismatch(es).
To see full details build your kernel with:
'make CONFIG_DEBUG_SECTION_MISMATCH=y'
CC /home/mom/Downloads/hybrid_wl/wl.mod.o
LD [M] /home/mom/Downloads/hybrid_wl/wl.ko

I didn't sweat it since it compiled okay, and again, looks like its looking for the normal licensing junk and not finding it...which is expected.


I'm going to leave it running all day today and keep track. If no hiccups, I'm going to act like a typical old-lady and ignore the tainted kernel issue (Kernel?? Like in "corn"??) and assume its a key registration thing with Broadcom? Unless you've got better ideas...then I'll mark as [SOLVED] ... sorta.

Kim
PatH57

Re: Broadcom BCM4360 woes, fear it will not work - pls confi

Post by PatH57 »

Hi Kim

did the install on 3.15 and had the same message so I consider it as a warning and not an error.
Works great so far but I'm switching back to b43 for AP support.
the regulatory update is to check if any new channels would have been added or changed in the 2.4GHz or the 5GHz range nothing to worry about they haven't changed much over the last couple of years.
titianmom
Level 3
Level 3
Posts: 156
Joined: Thu Jan 07, 2010 12:32 am

Re: Broadcom BCM4360 woes, fear it will not work - pls confi

Post by titianmom »

Thanks for the info! We'll see as the day goes on. I'm getting some lag, now. Sigh... ??
PatH57

Re: Broadcom BCM4360 woes, fear it will not work - pls confi

Post by PatH57 »

check

Code: Select all

dmesg |grep wl 
from time to time to see what's going on.
Have a nice week end
titianmom
Level 3
Level 3
Posts: 156
Joined: Thu Jan 07, 2010 12:32 am

Re: Broadcom BCM4360 woes, fear it will not work - pls confi

Post by titianmom »

Just got back from going out, when I left the connection had completely dropped out. By the time I came back it had reconnected.

Did the dmesg wl, got bunches of the following:

[13136.214918] ERROR @wl_cfg80211_get_station : Wrong Mac address
[13142.218175] ERROR @wl_cfg80211_get_station : Wrong Mac address


?? That's a new one in the logs...

Kim
PatH57

Re: Broadcom BCM4360 woes, fear it will not work - pls confi

Post by PatH57 »

bugger thought this one was gone.....
titianmom
Level 3
Level 3
Posts: 156
Joined: Thu Jan 07, 2010 12:32 am

Re: Broadcom BCM4360 woes, fear it will not work - pls confi

Post by titianmom »

Yep, I'm going to keep an eye on it. I also plan to log into the Windows side--for all I know, its flaky under Windows and its the card (but I don't think so...)

If its fine under Windows and it keep acting weird in Linux, I'm prob going to drop back to LMDE and see what happens with that. Or get another card or usb wireless for it, because I'd be out of ideas at that point.

Kim
titianmom
Level 3
Level 3
Posts: 156
Joined: Thu Jan 07, 2010 12:32 am

Re: Broadcom BCM4360 woes, fear it will not work - pls confi

Post by titianmom »

Still looking into it, but found that BCM4360 pci.id chart entry says I can only use wl, which is what I'm using. (And explains why there's a blacklsit for b43.)
I was wondering about that since you said you were going back to b43. But you have a different card than I do.

I was in Windows and it dropped out, and the troubleshooting tool said it was the router, so I reset it after shutting down and now Im back in to Linux and there are no errors, again....for how long?

Toward the end of my up time in Linux it was spewing some interesting kernel stuff in dmesg. Was getting some weird no MAC found errors and associating 00:00:00:00, etc failing, but I found out that that could be IPv6 related. THis used to be a gaming machine, after all, and explains his choice of card. (?)
PatH57

Re: Broadcom BCM4360 woes, fear it will not work - pls confi

Post by PatH57 »

probably went for whatever card was there :lol:
Under windows all card manufacturers have to provide whql drivers so it will work even with the cheapest thing (well it will connect)
ipv6 is still implemented so drivers and routers may need to be updated, check if yours doesn't have a newer firmware?

Try it for a couple of days and see what happens.
I use the b43 driver because it does enable mixed mode and AP (access point) mode and also I can push the range from 20dB to 30dB witch is nice if I'm a bit to far from the router (careful it is not legal in some countries to do this). Whereas the broadcom driver doesn't support this (have to check with the new one but at a glance I'd say no)
http://www.google.fr/url?sa=t&rct=j&q=& ... 7243,d.d2k
titianmom
Level 3
Level 3
Posts: 156
Joined: Thu Jan 07, 2010 12:32 am

Re: Broadcom BCM4360 woes, fear it will not work - pls confi

Post by titianmom »

Found out can't upgrade any firmware on the router (LInksys WTGwhatever it is; old) and it doesn't provide IPv6, and hubby the network guy says you don't need IPv6 nec to do voice (skype). SHould have asked him in the first place. That's where all the IPv6 Wrong MAC addr errors are coming from., so that mystery is solved.

I'm educating myself as I go...

I've been looking a bit into avahi daemon, apparently its needed for a bunch of gnome packages. Can you educate me
on this?

Again, excuse my ignorance. If I can eliminate a daemon I don't need which is causing the error msgs, that would be nice.
I'm guessing I can't and its a mute point, but thought I'd ask.

Otherwise, we're connected so far today...it burps now and then, but reconnects. ...so far....

I'm thinking seriously of just reloading it with LMDE Cinnamon and running Windows under Virtual Box so I don't have to deal with viruses.
I won't use it for much anyways, maybe a tax form or whatever. If I do get a virus I can just trash that VM and re-install it. Sounds
like a good idea to me, anyways.

I'll have to look into which Broadcom driver version is best for me under LMDE....


Kim
PatH57

Re: Broadcom BCM4360 woes, fear it will not work - pls confi

Post by PatH57 »

Hi Kim,

the avahi daemon is a network discovery daemon.It's also part of gnome and cinnamon.
http://en.wikipedia.org/wiki/Avahi_%28software%29

Better live it alone.

LMDE uses the same kernel structure as mint or ubuntu, so driver will be the same.
titianmom
Level 3
Level 3
Posts: 156
Joined: Thu Jan 07, 2010 12:32 am

Re: Broadcom BCM4360 woes, fear it will not work - pls confi

Post by titianmom »

PatH57 wrote:Hi Kim,

the avahi daemon is a network discovery daemon.It's also part of gnome and cinnamon.
http://en.wikipedia.org/wiki/Avahi_%28software%29

Better live it alone.
Assumed as much. THanks...

LMDE uses the same kernel structure as mint or ubuntu, so driver will be the same.
Okay. Was wondering more about kernel version, tho. And anyway, was looking for a way to use Windows 7 inside Linux vs doing the dual boot. I know someone who does that in Apple to avoid the virus issue. His kids use the machine for MS games and get viruses now and then and he just kills off the old VM for Windows and reinstalls it.
PatH57

Re: Broadcom BCM4360 woes, fear it will not work - pls confi

Post by PatH57 »

virtualbox is what I use (just get it from package manager)
Locked

Return to “Networking”