something's burning !!
The driver itself is nothing to worry about since any kernel upgrade will automatically break it.
But the blacklist, yes you'll have to manually 'undo' the custom blacklistings to be able to try the native brcmsmac or the default proprietary wl driver. If they don't work, or work poorly, they are not yet fixed and you can safely repeat... what do you guys call it... uh..
Unfortunately, I don't know of a better way to test this.
Spilled the Beans
First of all, thanks so much for your help. I'm a noob to linux, but really like Linux Mint and installed Mint 14 on my HP Folio 13 - 1020US. I have since reinstalled Mint 15 & Ubuntu 13.04 and the wireless has been the bain of my existence for 3 days. 6+ hours of searching etc. and this has been the most helpful thread so far.
Having said that, I successfully followed your #31 "VSF" post and for the first time, I connected to my WiFi. However, it is painfully slow (read: unusable) and sometimes just disconnects. You mentioned some people had better performance with another driver (brcm ?) Is there any advice or somewhere you can point me to on how to install that driver AFTER having done your steps. Appreciate it.
Here's some basics to start with:
lspci -nn | grep 0280Code:description: Wireless interface product: BCM4313 802.11b/g/n Wireless LAN Controller vendor: Broadcom Corporation physical id: 0 bus info: pci@0000:02:00.0 logical name: eth1 version: 01 serial: c0:18:85:07:b7:fd width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=wl0 driverversion=5.100.82.112 latency=0 multicast=yes wireless=IEEE 802.11 resources: irq:18 memory:c2600000-c2603fff
lsmodCode:Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller [14e4:4727] (rev 01)
Code:Module Size Used by lib80211_crypt_tkip 17379 0 wl 2573614 0 lib80211 14352 2 wl,lib80211_crypt_tkip nls_iso8859_1 12713 1 michael_mic 12612 0 arc4 12615 0 parport_pc 28152 0 ppdev 17073 0 rfcomm 42641 0 bnep 18036 2 bluetooth 228619 10 bnep,rfcomm binfmt_misc 17500 1 coretemp 13355 0 kvm 443165 0 ghash_clmulni_intel 13259 0 aesni_intel 55399 0 aes_x86_64 17255 1 aesni_intel xts 12885 1 aesni_intel lrw 13257 1 aesni_intel gf128mul 14951 2 lrw,xts ablk_helper 13597 1 aesni_intel cryptd 20373 3 ghash_clmulni_intel,aesni_intel,ablk_helper joydev 17377 0 hid_generic 12540 0 hp_wmi 18048 0 sparse_keymap 13890 1 hp_wmi snd_hda_codec_hdmi 36913 1 snd_hda_codec_idt 70256 1 dm_multipath 22843 0 snd_hda_intel 39619 3 scsi_dh 14843 1 dm_multipath snd_hda_codec 136453 3 snd_hda_codec_hdmi,snd_hda_codec_idt,snd_hda_intel snd_hwdep 13602 1 snd_hda_codec snd_pcm 97451 3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel microcode 22881 0 snd_page_alloc 18710 2 snd_pcm,snd_hda_intel uvcvideo 80847 0 snd_seq_midi 13324 0 videobuf2_vmalloc 13056 1 uvcvideo snd_seq_midi_event 14899 1 snd_seq_midi usbhid 47074 0 videobuf2_memops 13202 1 videobuf2_vmalloc videobuf2_core 40513 1 uvcvideo snd_rawmidi 30180 1 snd_seq_midi hid 101002 2 hid_generic,usbhid videodev 129260 2 uvcvideo,videobuf2_core psmouse 95870 0 snd_seq 61554 2 snd_seq_midi_event,snd_seq_midi rtsx_pci_ms 13011 0 serio_raw 13215 0 snd_seq_device 14497 3 snd_seq,snd_rawmidi,snd_seq_midi memstick 16554 1 rtsx_pci_ms snd_timer 29425 2 snd_pcm,snd_seq lpc_ich 17061 0 snd 68876 16 snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_idt,snd_pcm,snd_seq,snd_rawmidi,snd_hda_codec,snd_hda_intel,snd_seq_device soundcore 12680 1 snd mei 41158 0 lp 17759 0 mac_hid 13205 0 parport 46345 3 lp,ppdev,parport_pc btrfs 785967 0 zlib_deflate 26885 1 btrfs libcrc32c 12615 1 btrfs dm_raid45 76725 0 xor 17116 1 dm_raid45 dm_mirror 21946 0 dm_region_hash 20820 1 dm_mirror dm_log 18529 3 dm_region_hash,dm_mirror,dm_raid45 usb_storage 57204 1 rtsx_pci_sdmmc 17475 0 i915 600351 3 rtsx_pci 33355 2 rtsx_pci_ms,rtsx_pci_sdmmc i2c_algo_bit 13413 1 i915 drm_kms_helper 49394 1 i915 r8169 67446 0 drm 286313 4 i915,drm_kms_helper ahci 25731 2 libahci 31364 1 ahci wmi 19070 1 hp_wmi video 19390 1 i915
something's burning !!
Welcome to the forums kajkob
While I search the brcmsmac fix and take a close look myself, let's do a sanity check in the meanwhile. Please follow the "Wireless Script" link in my signature, follow the instructions there, and post back the result of the script here (the wireless-info.txt file or its contents or its pastebin link).
And please confirm - have you tried any other fixes as well in the parallel or in the past? (on the same installation). If yes, please provide the link to the solution you followed (if you remember, otherwise not necessary).
I hope we can make it at least 'usable'.
EDIT:
For reference : http://ubuntuforums.org/showthread.p...9#post12652119
http://ubuntuforums.org/showthread.p...2#post12663032 (apparently not applicable to 4727)
Last edited by varunendra; June 8th, 2013 at 08:21 AM. Reason: added reference
Spilled the Beans
Thanks for the quick response, unfortunately I was gone for the weekend. While trying to retrace my steps, I realized I may have made a huge tiny mistake.. at some point I followed the directions in post #2 at
http://ubuntuforums.org/showthread.php?t=2148444
using the firmware linked in #4 on that page (Broadcom_Firmware_070513.tar.gz herunterladen) basically flashing the firmware of the card. Now, the wireless won't connect at all again as even just hitting the wireless button to turn it on does nothing..and I can't even turn it on in Windows any longer! Am I correct that flashing the firmware of the wireless card hardware would affect it in any OS and most importantly, how would I reverse this? At this point I think I may have caused more of a problem than just the drivers... please help!
FYI - I flashed the machine's BIOS to an updated version (and back for good measure) which did not help. Can't turn on the wireless card in any OS..
Last edited by kajkob; June 10th, 2013 at 05:58 AM. Reason: Spelling
something's burning !!
Hi,
Before answering your questions, I'd ask you to please not panic! It can be something simple, not necessarily something as severe as you think.
I can't say why you are unable to turn it on even in windows, but I can say with 100% confidence that the firmware you downloaded has nothing to do with it.Originally Posted by kajkob
Like I mentioned within the brackets in the Edit part of my previous post, I don't think it is even applicable to your card, although I have seen praseodym suggesting the same firmware package in a few threads (and he is a lot more experienced than me). Besides, the firmware files like this are dynamically loaded by the driver in the computer's memory, not the card itself (I may be wrong on this, but I'm sure it is loaded in a 'volatile' area). It is not the static firmware of the card. So even if you somehow manage to load an incorrect firmware for a card, it can't affect it permanently.
Firstly, I don't think you can even flash a wireless card actually. Like I mentioned above, the firmware loaded by the driver is the dynamic part that is required for certain functions. It gets reset on a reboot (or is supposed to). In some cases however, the static firmware CAN get stuck resulting in weird behaviour. In that case, the usual recommendation is to just disconnect it from all power sources for a few minutes (20 seconds to 10 minutes, depending upon various factors). It is easier to do in a desktop, but in a laptop, it may be a bit difficult.Am I correct that flashing the firmware of the wireless card hardware would affect it in any OS and most importantly, how would I reverse this? At this point I think I may have caused more of a problem than just the drivers... please help!
Now before trying anything else, I'd once again ask you to just run the "Wireless script" I mentioned in my previous post, and post back its results here. We may get significant hints in it about the problem.
PS:
Although I wouldn't recommend it yet, if you are absolutely sure that the firmware of the card is stuck, you may try this -
If you reverted the version of the BIOS, upgrade it again. Then reset it to default settings (although it should automatically be done during upgrade, but just in case). The option to reset to default is usually listed as "Load Defaults" or "Load Optimized Defaults" etc. in the "Exit" menu of the BIOS. Try whatever you have in yours.
If this doesn't make it work in either OS, then try disconnecting the wireless card. Most often, the wireless card is placed in a user-accessible area at the bottom of the laptop chasis. See if you can access it after removing the cover panels at the bottom. If you can, just disconnect the two plug-type wires connected to it, remove the screw(s) and pull it out. Leave it for about 10 minutes then re-seat in its place like before. As far as I know, this is all you can do with it (apart from entirely replacing it with another one).
Last edited by varunendra; June 10th, 2013 at 08:54 AM.
Spilled the Beans
That's great news, thanks for the explanation.It is not the static firmware of the card. So even if you somehow manage to load an incorrect firmware for a card, it can't affect it permanently.
Did this last night actually and it indeed 'reset' everything allowing me to turn the WiFi card on with the hardware switch again, both in Windows and LinuxIf you reverted the version of the BIOS, upgrade it again. Then reset it to default settings..
I can't remember everything, but I reinstalled Linux after some of the attempts so they were wiped. Did not try the b43 drivers as they state no support for 14e4:4727. I did of course try the suggested Broadcom drivers first which failed. Did the firmware flash as mentioned on this current install and then tried your solution.And please confirm - have you tried any other fixes as well in the parallel or in the past?
Sorry I didn't reailze I could run that without the wireless card being on at all, so I panicked a bit as you said. Also, to clarify, the card does turn on now again in Linux as mentioned but was only able to load one page very slowly and then disconnected. Here are the results:Now before trying anything else, I'd once again ask you to just run the "Wireless script" I mentioned in my previous post, and post back its results here. We may get significant hints in it about the problem.
Code:*************** info trace *************** ***** uname -a ***** Linux karl-FolioMint 3.8.0-23-generic #34-Ubuntu SMP Wed May 29 20:22:58 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux ***** lsb_release ***** Distributor ID: LinuxMint Description: Linux Mint 15 Olivia Release: 15 Codename: olivia ***** lspci ***** 01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller [10ec:8168] (rev 06) Subsystem: Hewlett-Packard Company Device [103c:17f8] Kernel driver in use: r8169 02:00.0 Network controller [0280]: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller [14e4:4727] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:1795] Kernel driver in use: wl ***** lsusb ***** Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1bcf:2c07 Sunplus Innovation Technology Inc. Bus 001 Device 004: ID 0a5c:21e3 Broadcom Corp. Bus 002 Device 003: ID 046d:c521 Logitech, Inc. Cordless Mouse Receiver ***** iwconfig ***** eth1 IEEE 802.11 Access Point: Not-Associated Link Quality:5 Signal level:239 Noise level:164 Rx invalid nwid:0 invalid crypt:0 invalid misc:0 ***** rfkill ***** 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 2: hp-wifi: Wireless LAN Soft blocked: no Hard blocked: no 3: hp-bluetooth: Bluetooth Soft blocked: no Hard blocked: no ***** lsmod ***** wl 2573614 0 lib80211 14352 2 wl,lib80211_crypt_tkip ***** nm-tool ***** NetworkManager Tool State: connected (global) - Device: eth1 [Asus] --------------------------------------------------------- Type: 802.11 WiFi Driver: wl State: connected Default: yes HW Address: <MAC address removed> Capabilities: Speed: 54 Mb/s Wireless Properties WEP Encryption: yes WPA Encryption: yes WPA2 Encryption: yes Wireless Access Points (* = current AP) *Asus: Infra, <MAC address removed>, Freq 2447 MHz, Rate 0 Mb/s, Strength 100 WPA WPA2 IPv4 Settings: Address: 192.168.1.104 Prefix: 24 (255.255.255.0) Gateway: 192.168.1.1 DNS: 65.32.5.111 DNS: 65.32.5.112 - Device: eth0 ----------------------------------------------------------------- Type: Wired Driver: r8169 State: unavailable Default: no HW Address: <MAC address removed> Capabilities: Carrier Detect: yes Wired Properties Carrier: off ***** NetworkManager.state ***** [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ***** NetworkManager.conf ***** [main] plugins=ifupdown,keyfile dns=dnsmasq [ifupdown] managed=false ***** interfaces ***** # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback ***** iwlist ***** eth1 Scan completed : Cell 01 - Address: <MAC address removed> ESSID:"Asus" Mode:Managed Frequency:2.447 GHz (Channel 8) Quality:5/5 Signal level:-6 dBm Noise level:-92 dBm IE: IEEE 802.11i/WPA2 Version 1 Group Cipher : TKIP Pairwise Ciphers (2) : CCMP TKIP Authentication Suites (1) : PSK IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (2) : CCMP TKIP Authentication Suites (1) : PSK Encryption key:on Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s 24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s 12 Mb/s; 48 Mb/s ***** resolv.conf ***** nameserver 127.0.1.1 search cfl.rr.com nameserver 208.67.222.222 nameserver 208.67.220.220 ***** blacklist ***** [/etc/modprobe.d/blacklist-ath_pci.conf] blacklist ath_pci [/etc/modprobe.d/blacklist.conf] blacklist evbug blacklist usbmouse blacklist usbkbd blacklist eepro100 blacklist de4x5 blacklist eth1394 blacklist snd_intel8x0m blacklist snd_aw2 blacklist i2c_i801 blacklist prism54 blacklist bcma blacklist brcmsmac blacklist 43 blacklist garmin_gps blacklist asus_acpi blacklist snd_pcsp blacklist pcspkr blacklist amd76x_edac ***** dmesg ***** [ 4.327544] wl: module license 'unspecified' taints kernel. [ 4.509158] eth1: Broadcom BCM4727 802.11 Hybrid Wireless Controller 5.100.82.112 ****************** done ******************
Last edited by kajkob; June 10th, 2013 at 05:31 PM. Reason: Spelling
something's burning !!
Aha!! At least we got back to where we began
Possible culprit no.1 -
Please change the encryption settings in your router to pure WPA2-PSK (AES) only. No WPA/WPA2 mixed mode, no TKIP. This is something I'd ask you to do regardless of the driver in use.
Then, for your wireless connection in Network Manager, make sure "Method" under IPv6 is set to "Ignore" and the same under IPv4 is set to "Automatic (DHCP) address only". This will allow you to define your own DNS for the connection. Then in the "DNS servers" field, enter the addresses of Google's open DNS servers - type exactly (without the double-quotes) : "8.8.8.8, 8.8.4.4"
Click "Save" > close.
Then restart both your router and laptop, and try to connect. If it is still slow, post back the results of -
Code:ifconfig iwconfig sudo iwlist eth1 scan nm-tool
Spilled the Beans
Wow, I went way down this rabbit hole... Went on a bit of tangent when messing with the WiFi and decided to upgrade to a new router this week (Asus RT-N66U) which is set up and working fine. Now, after extensive messing with many things at once (SSD TRIM support, etc) which I now think was a mistake, I had to start completely over and reinstalled. Now new issues arrise.. this time when I try to compile the the driver, I get the following error message:
Code:karl@karlFolioMint ~/Desktop/hybrid-portsrc_x86_64-v5_100_82_112 $ make KBUILD_NOPEDANTIC=1 make -C /lib/modules/`uname -r`/build M=`pwd` make[1]: Entering directory `/usr/src/linux-headers-3.9.6-030906-generic' Wireless Extension is the only possible API for this kernel version Using Wireless Extension API LD /home/karl/Desktop/hybrid-portsrc_x86_64-v5_100_82_112/built-in.o CC [M] /home/karl/Desktop/hybrid-portsrc_x86_64-v5_100_82_112/src/shared/linux_osl.o CC [M] /home/karl/Desktop/hybrid-portsrc_x86_64-v5_100_82_112/src/wl/sys/wl_linux.o CC [M] /home/karl/Desktop/hybrid-portsrc_x86_64-v5_100_82_112/src/wl/sys/wl_iw.o CC [M] /home/karl/Desktop/hybrid-portsrc_x86_64-v5_100_82_112/src/wl/sys/wl_cfg80211.o LD [M] /home/karl/Desktop/hybrid-portsrc_x86_64-v5_100_82_112/wl.o Building modules, stage 2. Wireless Extension is the only possible API for this kernel version Using Wireless Extension API MODPOST 1 modules WARNING: modpost: missing MODULE_LICENSE() in /home/karl/Desktop/hybrid-portsrc_x86_64-v5_100_82_112/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/karl/Desktop/hybrid-portsrc_x86_64-v5_100_82_112/wl.mod.o LD [M] /home/karl/Desktop/hybrid-portsrc_x86_64-v5_100_82_112/wl.ko make[1]: Leaving directory `/usr/src/linux-headers-3.9.6-030906-generic'The wl.ko file is in the directory, but when I go onto the next steps this is what I get:If successful, you should see "wl.ko" file in the extracted directory. If it is there, ONLY THEN proceed as follows (in the same terminal, same directory) -
I think I should note that since I started over, the system setup may be different etc. so here is some other basic info that may come into play.Code:$ modprobe -rfv wl FATAL: Module wl not found.
#cat /etc/lsb-release; uname -a
# lspci -nnk | grep -iA2 netCode:DISTRIB_ID=LinuxMint DISTRIB_RELEASE=15 DISTRIB_CODENAME=olivia DISTRIB_DESCRIPTION="Linux Mint 15 Olivia" Linux karlFolioMint 3.9.6-030906-generic #201306131535 SMP Thu Jun 13 19:35:54 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
# iwconfigCode:01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller [10ec:8168] (rev 06) Subsystem: Hewlett-Packard Company Device [103c:17f8] Kernel driver in use: r8169 02:00.0 Network controller [0280]: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller [14e4:4727] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:1795] 03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5209 PCI Express Card Reader [10ec:5209] (rev 01)
Current blacklisted in /etc/modprobe.d/blacklist.conf:Code:eth0 no wireless extensions. lo no wireless extensions.blacklist brmcsmac
blacklist bcma
blacklist ssb
blacklist b43
blacklist b43legacy
blacklist ndiswrapper
So I can't quite make it as far this time, any suggestions on the make failure? Thanks
Last edited by kajkob; June 15th, 2013 at 12:27 AM.
something's burning !!
The warning messeges you got are normal and there is nothing serious about them. We don't need to worry about warnings unless they translate into Errors. Only in that case do we need to take a close look at the warning messages to find out the reason for the error.
Like I mentioned in the original post that you were following, IF -
..then we are good to go ahead.
That command is meant to unload the wrong version of the wl driver if it is loaded. In your case it wasn't, hence the error. So no worries there (I should have made it clear in that post, sorry).Code:$ modprobe -rfv wl FATAL: Module wl not found.
For your info, the "-r" option in modprobe commands stands for "remove". Without it, the command does the opposite - that is, loads a driver. (-f is for "force", -v for "verbose").
Also, why have you blacklisted ndiswrapper? Did you install it? It is absolutely not needed, although blacklisting won't have any effect (no need to blacklist something that doesn't even exist in the system), its presence make me suspicious that you might have tried too many random things -
In the same manner, you also don't need to blacklist b43, b43legacy or ssb. They won't get loaded for your particular card unless you force them to.Current blacklisted in /etc/modprobe.d/blacklist.conf:blacklist brmcsmac
blacklist bcma
blacklist ssb
blacklist b43
blacklist b43legacy
blacklist ndiswrapper
Like I mentioned above, warnings are normal and it wasn't a failure. The presence of wl.ko was a proof of success. Afterwards, the modprobe command tried to remove a driver which wasn't loaded, hence the error. So everything so far seems normal to me, and so you can proceed with the rest of the steps.any suggestions on the make failure?
But if you have tried ndiswrapper, it may cause troubles if we still have its remnants. For now, just complete the steps for the compiled wl.ko driver and post back if we have any problems after that.
Thanks.
Spilled the Beans
Like I said, total noob! Thanks for explaining. Sounds like I should have just kept going with the instructions... I will do that when I return tomorrow.That command is meant to unload the wrong version of the wl driver if it is loaded. In your case it wasn't, hence the error. So no worries there (I should have made it clear in that post, sorry).
For your info, the "-r" option in modprobe commands stands for "remove". Without it, the command does the opposite - that is, loads a driver. (-f is for "force", -v for "verbose").
No, I did not explicitly install ndiswrapper or any of the other blacklisted drivers..but after all those forum posts, from my (mis?)understanding some drivers are part of the kernel itself, so I just blacklisted everything I knew I didn't want to use. I see that it's not necessary now. I'll report back..
Posting Permissions
Adv Reply
Bookmarks