[SOLVED] Wireless Network Adapter identified; No connection

PJxSlain · 2020-12-27 21:03:01

Fresh installation of Arch, Wireless Network Adapter identified and works (works perfectly fine in previously installed Win10 enviro). Not connecting or appearing as a valid device so turned to the wiki:

Checked to see if the driver for the card has been loaded:

lspci -k
03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4352 802.11ac Wireless Network Adapter (rev 03)
Subsystem: AzureWave Device 2123
Kernel driver in use: bcma-pci-bridge
Kernel modules: bcma
04:00.0 Ethernet controller: Qualcomm Atheros QCA8171 Gigabit Ethernet (rev 10)
Subsystem: ASUSTek Computer Inc. Device 200f
Kernel driver in use: alx
Kernel modules: alx

ip link
1: lo:
2: enp4s0:

No wireless interface options are appearing and what I have found continues on with setting the "interface up". Since no interface option is appearing, how would I go about moving onto the next steps of getting the Network controller to communicate with the rest of the system?

Last edited by PJxSlain (2020-12-27 23:15:46)

seth · 2020-12-27 21:07:51

https://wiki.archlinux.org/index.php/Br … roadcom-wl

If not, please post a complete system journal ("sudo journalctl -b")
Edit: and also the output of "rfkill"

Also

works perfectly fine in previously installed Win10 enviro

You might have to check the 3rd link in my signature if you've still a windows installation around.

Last edited by seth (2020-12-27 21:08:11)

PJxSlain · 2020-12-27 21:31:13

So starting with the link you posted:

rmmod b43
rmmod: ERROR: Module b43 is not currently loaded

rmmod ssb
rmmod: ERROR: Module ssb is not currently loaded

modprobe wl
modprobe: FATAL: Module wl not found in directory /lib/modules/5.9.14-arch1-1

Next comes your request:

sudo journalctl -b
-- Journal begins at Sat 2020-12-26 23:46:13 UTC, ends at Sun 2020-12-27 21:21:59 UTC. --
Dec 27 21:20:47 SlainROG kernel: microcode: microcode updated early to revision 0x28, date = 2019-11-12
Dec 27 21:20:47 SlainROG kernel: Linux version 5.9.14-arch1-1 (linux@archlinux) (gcc (GCC) 10.2.0, GNU ld (GNU Binutils) 2.35.1) #1 SMP PREEMPT Sat, 12 Dec 2020 14:37:12 +0000
Dec 27 21:20:47 SlainROG kernel: Command line: root=PARTUUID=203789d3-3622-446e-9e7e-4ecae8421f94 rw add_efi_memmap initrd=boot\intel-ucode.img initrd=boot\initramfs-linux.img
Dec 27 21:20:47 SlainROG kernel: KERNEL supported cpus:
Dec 27 21:20:47 SlainROG kernel: Intel GenuineIntel
Dec 27 21:20:47 SlainROG kernel: AMD AuthenticAMD
Dec 27 21:20:47 SlainROG kernel: Hygon HygonGenuine
Dec 27 21:20:47 SlainROG kernel: Centaur CentaurHauls
Dec 27 21:20:47 SlainROG kernel: zhaoxin Shanghai
Dec 27 21:20:47 SlainROG kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Dec 27 21:20:47 SlainROG kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Dec 27 21:20:47 SlainROG kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Dec 27 21:20:47 SlainROG kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
Dec 27 21:20:47 SlainROG kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
Dec 27 21:20:47 SlainROG kernel: BIOS-provided physical RAM map:
Dec 27 21:20:47 SlainROG kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
Dec 27 21:20:47 SlainROG kernel: BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
Dec 27 21:20:47 SlainROG kernel: BIOS-e820: [mem 0x0000000000059000-0x000000000009efff] usable
Dec 27 21:20:47 SlainROG kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] reserved
Dec 27 21:20:47 SlainROG kernel: BIOS-e820: [mem 0x0000000000100000-0x000000006972ffff] usable
Dec 27 21:20:47 SlainROG kernel: BIOS-e820: [mem 0x0000000069730000-0x0000000069736fff] ACPI NVS
Dec 27 21:20:47 SlainROG kernel: BIOS-e820: [mem 0x0000000069737000-0x0000000069fa5fff] usable
Dec 27 21:20:47 SlainROG kernel: BIOS-e820: [mem 0x0000000069fa6000-0x000000006a233fff] reserved
Dec 27 21:20:47 SlainROG kernel: BIOS-e820: [mem 0x000000006a234000-0x0000000079885fff] usable
Dec 27 21:20:47 SlainROG kernel: BIOS-e820: [mem 0x0000000079886000-0x0000000079a9cfff] reserved
Dec 27 21:20:47 SlainROG kernel: BIOS-e820: [mem 0x0000000079a9d000-0x0000000079e02fff] usable
Dec 27 21:20:47 SlainROG kernel: BIOS-e820: [mem 0x0000000079e03000-0x000000007ab06fff] ACPI NVS
Dec 27 21:20:47 SlainROG kernel: BIOS-e820: [mem 0x000000007ab07000-0x000000007affefff] reserved
Dec 27 21:20:47 SlainROG kernel: BIOS-e820: [mem 0x000000007afff000-0x000000007affffff] usable
Dec 27 21:20:47 SlainROG kernel: BIOS-e820: [mem 0x000000007bc00000-0x000000007fdfffff] reserved
Dec 27 21:20:47 SlainROG kernel: BIOS-e820: [mem 0x00000000f0000000-0x00000000f7ffffff] reserved
Dec 27 21:20:47 SlainROG kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Dec 27 21:20:47 SlainROG kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
Dec 27 21:20:47 SlainROG kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Dec 27 21:20:47 SlainROG kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Dec 27 21:20:47 SlainROG kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Dec 27 21:20:47 SlainROG kernel: BIOS-e820: [mem 0x0000000100000000-0x000000047f1fffff] usable
Dec 27 21:20:47 SlainROG kernel: NX (Execute Disable) protection: active
Dec 27 21:20:47 SlainROG kernel: e820: update [mem 0x67a14018-0x67a2d657] usable ==> usable
Dec 27 21:20:47 SlainROG kernel: e820: update [mem 0x67a14018-0x67a2d657] usable ==> usable
Dec 27 21:20:47 SlainROG kernel: e820: update [mem 0x67a3b018-0x67a4b057] usable ==> usable
Dec 27 21:20:47 SlainROG kernel: e820: update [mem 0x67a3b018-0x67a4b057] usable ==> usable
Dec 27 21:20:47 SlainROG kernel: e820: update [mem 0x67a07018-0x67a13057] usable ==> usable
Dec 27 21:20:47 SlainROG kernel: e820: update [mem 0x67a07018-0x67a13057] usable ==> usable
Dec 27 21:20:47 SlainROG kernel: extended physical RAM map:
Dec 27 21:20:47 SlainROG kernel: reserve setup_data: [mem 0x0000000000000000-0x0000000000057fff] usable
Dec 27 21:20:47 SlainROG kernel: reserve setup_data: [mem 0x0000000000058000-0x0000000000058fff] reserved
Dec 27 21:20:47 SlainROG kernel: reserve setup_data: [mem 0x0000000000059000-0x000000000009efff] usable
Dec 27 21:20:47 SlainROG kernel: reserve setup_data: [mem 0x000000000009f000-0x000000000009ffff] reserved
Dec 27 21:20:47 SlainROG kernel: reserve setup_data: [mem 0x0000000000100000-0x0000000067a07017] usable
Dec 27 21:20:47 SlainROG kernel: reserve setup_data: [mem 0x0000000067a07018-0x0000000067a13057] usable
Dec 27 21:20:47 SlainROG kernel: reserve setup_data: [mem 0x0000000067a13058-0x0000000067a14017] usable
Dec 27 21:20:47 SlainROG kernel: reserve setup_data: [mem 0x0000000067a14018-0x0000000067a2d657] usable
Dec 27 21:20:47 SlainROG kernel: reserve setup_data: [mem 0x0000000067a2d658-0x0000000067a3b017] usable
Dec 27 21:20:47 SlainROG kernel: reserve setup_data: [mem 0x0000000067a3b018-0x0000000067a4b057] usable
Dec 27 21:20:47 SlainROG kernel: reserve setup_data: [mem 0x0000000067a4b058-0x000000006972ffff] usable

rfkill
ID TYPE DEVICE SOFT HARD
0 bluetooth hci0 unblocked unblocked

loqs · 2020-12-27 21:35:19

Boot the Arch installation media which contains the Broadcom wl module, does that list the wireless interface?

Last edited by loqs (2020-12-27 21:36:12)

PJxSlain · 2020-12-27 21:39:49

Using the installation media, the outputs are the same as the installation and there are no indications of the wireless interface.

seth · 2020-12-27 21:44:03

Please remove the partial journal in comment #3 and use

sudo journalctl -b |  curl -F 'f:1=<-' ix.io

to upload the journal.

Also the installtion iso cannot have caused the same outputs as

modprobe: FATAL: Module wl not found in directory /lib/modules/5.9.14-arch1-1

happens because you didn't install the module but it's present in the installation iso.

PJxSlain · 2020-12-27 22:00:07

sudo journalctl -b | curl -F 'f:1=<-' ix.io
http://ix.io/2K2r

So what i meant was that the interface outputs in 'lspci -k & ip link' are the same. The the Network adapter is showing in 'lspci' but no wireless interface in 'ip link'.

seth · 2020-12-27 22:08:54

This is why it doesn't work on the installed system:

Dec 27 21:55:31 SlainROG kernel: b43-phy0: Broadcom 4352 WLAN found (core revision 42)
Dec 27 21:55:31 SlainROG kernel: b43-phy0 ERROR: FOUND UNSUPPORTED PHY (Analog 12, Type 11 (AC), Revision 1)
Dec 27 21:55:31 SlainROG kernel: b43: probe of bcma0:1 failed with error -95

Does "lspci -k" on the install iso say the device is using the "wl" module?

PJxSlain · 2020-12-27 22:29:20

So "lspci -k" on the installation iso produces:

03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4352 802.11ac Wireless Network Adapter (rev 03)
Subsystem: AzureWave Device 2123
Kernel driver in use: bcma-pci-bridge
Kernel modules: bcma, wl

seth · 2020-12-27 22:31:31

"no"
unload the bcma drivers and load wl, see what happens.

PJxSlain · 2020-12-27 22:41:37

modprobe -r bcma
modprobe: FATAL: Module bcma is in use.

also tried rmmod bcma
rmmod: ERROR: Module bcma is in use by: b43

modprobe wl
modprobe: FATAL: Module wl not found in directory /lib/modules/5.9.14-arch1-1

seth · 2020-12-27 22:45:43

modprobe -r b43
modprobe -r bcma

modprobe: FATAL: Module wl not found in directory /lib/modules/5.9.14-arch1-1

Is that the install iso or yor installed system? For the latter: you still need to intall the module.

PJxSlain · 2020-12-27 22:52:54

So those outputs are from my installed system. I have installed the broadcom-wl driver, unloaded the bcma driver and loaded wl driver. Updated queries:

lspci -k
3:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4352 802.11ac Wireless Network Adapter (rev 03)
Subsystem: AzureWave Device 2123
Kernel driver in use: bcma-pci-bridge
Kernel modules: bcma, wl
04:00.0 Ethernet controller: Qualcomm Atheros QCA8171 Gigabit Ethernet (rev 10)
Subsystem: ASUSTeK Computer Inc. Device 200f
Kernel driver in use: alx
Kernel modules: alx

ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
link/ether 78:24:af:02:ab:c3 brd ff:ff:ff:ff:ff:ff

Still appearing to not be identifying a wireless interface, just the ethernet.

seth · 2020-12-27 22:56:13

Kernel driver in use: bcma-pci-bridge

?

Please post the actual IO for

unloaded the bcma driver and loaded wl driver

PJxSlain · 2020-12-27 23:01:54

modprobe -r bcma

modprobe wl

There were no outputs for these.

seth · 2020-12-27 23:06:50

lsmod | grep bcma

You should probably also track "dmesg -w" while juggling the modules.

In case you start to wonder: there's a reason why broadcom has its own wiki page ;-)

PJxSlain · 2020-12-27 23:14:08

So after running these commands again and after posting my response i had the idea to try "ip link" again

ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp4s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
link/ether 78:24:af:02:ab:c3 brd ff:ff:ff:ff:ff:ff
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DORMANT group default qlen 1000
link/ether 54:27:1e:c5:24:05 brd ff:ff:ff:ff:ff:ff

After wifi configurations I'm happy to report that wireless interface is working as intended now. Checked again after reboot and everything seems to have stuck for the swap and everything is working as intended.

Odd to me that the IO for "lspci -k" was the same in the installation ISO as it is in the installation but now in the installation the wireless interface is registered now. Looks like I'll have some "light reading" on the wiki to find out why broadcom is such a bugger. Thanks for the assistance!

Arch Linux

#1 2020-12-27 21:03:01

[SOLVED] Wireless Network Adapter identified; No connection

#2 2020-12-27 21:07:51

Re: [SOLVED] Wireless Network Adapter identified; No connection

#3 2020-12-27 21:31:13

Re: [SOLVED] Wireless Network Adapter identified; No connection

#4 2020-12-27 21:35:19

Re: [SOLVED] Wireless Network Adapter identified; No connection

#5 2020-12-27 21:39:49

Re: [SOLVED] Wireless Network Adapter identified; No connection

#6 2020-12-27 21:44:03

Re: [SOLVED] Wireless Network Adapter identified; No connection

#7 2020-12-27 22:00:07

Re: [SOLVED] Wireless Network Adapter identified; No connection

#8 2020-12-27 22:08:54

Re: [SOLVED] Wireless Network Adapter identified; No connection

#9 2020-12-27 22:29:20

Re: [SOLVED] Wireless Network Adapter identified; No connection

#10 2020-12-27 22:31:31

Re: [SOLVED] Wireless Network Adapter identified; No connection

#11 2020-12-27 22:41:37

Re: [SOLVED] Wireless Network Adapter identified; No connection

#12 2020-12-27 22:45:43

Re: [SOLVED] Wireless Network Adapter identified; No connection

#13 2020-12-27 22:52:54

Re: [SOLVED] Wireless Network Adapter identified; No connection

#14 2020-12-27 22:56:13

Re: [SOLVED] Wireless Network Adapter identified; No connection

#15 2020-12-27 23:01:54

Re: [SOLVED] Wireless Network Adapter identified; No connection

#16 2020-12-27 23:06:50

Re: [SOLVED] Wireless Network Adapter identified; No connection

#17 2020-12-27 23:14:08

Re: [SOLVED] Wireless Network Adapter identified; No connection

Board footer