You are not logged in.
I have "Network controller: Broadcom Limited BCM43142 802.11b/g/n (rev 01)" as my wifi adapter ad I am using "wl" driver for it. The problem started showing up like 2,3 months back. I just restarted the PC whenever that happened. But now it is getting worse. The wifi stops after 10, 20 minutes or so now. Here are some of the things that I have checked so far
1. No dmesg log when the wifi stops, no change at all.
2. "ip link" shows the wifi interface (That is "wlp8s0") in the list.
3. If try to connect with wpa_supplicant it shows "wlp8s0: CTRL-EVENT-SCAN-FAILED ret=-1 retry=1"
4. Even checked if the wifi is soft blocked or not (with rfkill) and its not.
5. Tried to reload the wl module with "rmmod wl" and then reload the module with "modprobe wl". After doing "modprobe wl", although lspci showed me "Kernel modules: wl" but no module was in use. Before doing "rmmod wl" the module wl was in use.
I don't know what else to try, can anyone please suggest me something?
Offline
Are you using broadcom-wl-dkms from community or broadcom-wl from AUR ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Are you using broadcom-wl-dkms from community or broadcom-wl from AUR ?
How can I check that? (Sorry but I am still noob at this thing)
Here is the output of :
"dkms status "
broadcom-wl, 6.30.223.271, 4.10.10-1-ARCH, x86_64: installed
"cat /usr/src/broadcom-wl-6.30.223.271/dkms.conf "
PACKAGE_NAME="broadcom-wl"
PACKAGE_VERSION="6.30.223.271"
BUILT_MODULE_NAME[0]="wl"
DEST_MODULE_LOCATION[0]="/kernel/drivers/net/wireless"
PATCH[0]="001-null-pointer-fix.patch"
PATCH[1]="002-rdtscl.patch"
PATCH[2]="003-linux47.patch"
PATCH[3]="004-linux48.patch"
PATCH[4]="005-debian-fix-kernel-warnings.patch"
AUTOINSTALL="yes"
Offline
looks very much like the one from from community, but let's verify.
post output of pacman -Si broadcom-wl-dkms .
what is output of lspci -vnn -d 14e4: ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
looks very much like the one from from community, but let's verify.
post output of pacman -Si broadcom-wl-dkms .
what is output of lspci -vnn -d 14e4: ?
pacman -Si broadcom-wl-dkms
Repository : community
Name : broadcom-wl-dkms
Version : 6.30.223.271-11
Description : Broadcom 802.11 Linux STA wireless driver
Architecture : x86_64
URL : https://www.broadcom.com/support/download-search/?pf=Wireless+LAN+Infrastructure
Licenses : custom
Groups : None
Provides : None
Depends On : dkms
Optional Deps : None
Conflicts With : broadcom-wl
Replaces : None
Download Size : 1504.60 KiB
Installed Size : 7798.00 KiB
Packager : Alexander Rødseth <rodseth@gmail.com>
Build Date : Wed 05 Apr 2017 02:30:02 AM IST
Validated By : MD5 Sum SHA-256 Sum Signaturelspci -vnn -d 14e4:
08:00.0 Network controller [0280]: Broadcom Limited BCM43142 802.11b/g/n [14e4:4365] (rev 01)
Subsystem: Dell Wireless 1704 802.11n + BT 4.0 [1028:0016]
Flags: bus master, fast devsel, latency 0, IRQ 17
Memory at c1500000 (64-bit, non-prefetchable) [size=32K]
Capabilities: <access denied>
Kernel driver in use: wl
Kernel modules: bcma, wlOffline
Incase you wondered, that lspci command came from [1].
The pci-id for your broadcom card is 14e4:4365 , and on your system the kernel knows 2 modules that have support for that card :
bcma and wl .
I checked [2] for 14e4:4365 and found your chipset is a BCM4366 PCIe device that is supported by the brcmfmac driver.
In my experience The bcma kernel module appears to be the lower-level module used by both brcmfmac and brcmsmac driver.
remove broadcom-wl-dkms and reboot.
run the same lspci command again and it should now list :
kernel driver in use : bcma
kernel modules: bcma
Test if the in kernel driver works better then the broadcom-wl one.
[1]https://wiki.archlinux.org/index.php/Broadcom_wireless
[2]https://wireless.wiki.kernel.org/en/use … rted_chips
Last edited by Lone_Wolf (2017-04-20 15:12:16)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Incase you wondered, that lspci command came from [1].
The pci-id for your broadcom card is 14e4:4365 , and on your system the kernel knows 2 modules that have support for that card :
bcma and wl .
I checked [2] for 14e4:4365 and found your chipset is a BCM4366 PCIe device that is supported by the brcmfmac driver.
In my experience The bcma kernel module appears to be the lower-level module used by both brcmfmac and brcmsmac driver.remove broadcom-wl-dkms and reboot.
run the same lspci command again and it should now list :
kernel driver in use : bcma
kernel modules: bcmaTest if the in kernel driver works better then the broadcom-wl one.
[1]https://wiki.archlinux.org/index.php/Broadcom_wireless
[2]https://wireless.wiki.kernel.org/en/use … rted_chips
The internal kernel driver didn't work because when I installed arch the same module "bcma" was in use and wifi was not working. I looked around on this forum and get to know that wl driver will work fine. It did work for some time, like for a month or two, without any issues. But as I keep on updating frequently, I THINK that there is some kind of "NOT SO GOOD UNDERSTANDING" between the kernel and the module now.
Tell me if I am wrong. Thanks for helping.
EDIT : Also thanks for telling me the way you approached the problem, was really helpfull.
Last edited by hemantcompiler (2017-04-20 15:36:05)
Offline
Support for your chipset was added to the bcma / brcmfmac kernel modules about a year ago, chances are good it will improve fast.
The broadcom-wl driver otoh is barely maintained and it's successor is the bcma module tree.
Best advise I can give is to check often (especially after a kernel or linux-firmware update)
whether bcma works better then broadcom-wl and swtich as soon as possible.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Support for your chipset was added to the bcma / brcmfmac kernel modules about a year ago, chances are good it will improve fast.
The broadcom-wl driver otoh is barely maintained and it's successor is the bcma module tree.Best advise I can give is to check often (especially after a kernel or linux-firmware update)
whether bcma works better then broadcom-wl and swtich as soon as possible.
Okay, Thank you!
Offline