You are not logged in.

#1 2022-01-05 07:44:03

VelocityDv
Member
Registered: 2022-01-04
Posts: 12

[SOLVED] wireless connection with bcm4331

I have installed broadcom-wl package and b43-firmware.
I have followed the tutorial on arch wiki

https://wiki.archlinux.org/title/broadcom_wireless
and have set wl on nano /etc/modules-load.d/wl.conf.

I have also followed wpa_supplicant to configure network with wpa_passphrase
https://wiki.archlinux.org/title/Wpa_supplicant

But unfortunately cannot get wireless network. however ethernet works fine.

Last edited by VelocityDv (2022-01-10 22:33:48)

Offline

#2 2022-01-05 15:04:59

Head_on_a_Stick
Member
From: London
Registered: 2014-02-20
Posts: 7,769
Website

Re: [SOLVED] wireless connection with bcm4331

Please post the exact wpa_supplicant command you tried along with any output in full.

Did you attempt to assign IP addresses for the wireless interface? If so then also post the relevant command(s) and any output.

Also share the output of

lspci -knn | grep -A3 'Net'

Offline

#3 2022-01-05 20:24:35

VelocityDv
Member
Registered: 2022-01-04
Posts: 12

Re: [SOLVED] wireless connection with bcm4331

03:00.0 Ethernet controller [0200]: Broadcom Inc. and subsidiaries NetXtreme BCM57766 Gigabit Ethernet PCIe [14e4:1686] (rev 01)
        Subsystem: Broadcom Inc. and subsidiaries NetXtreme BCM57766 Gigabit Ethernet PCIe [14e4:1686]
        Kernel driver in use: tg3
        Kernel modules: tg3
03:00.1 SD Host controller [0805]: Broadcom Inc. and subsidiaries BCM57765/57785 SDXC/MMC Card Reader [14e4:16bc] (rev 01)
--
04:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4331 802.11a/b/g/n [14e4:4331] (rev 02)
        Subsystem: Apple Inc. AirPort Extreme [106b:00f4]
        Kernel driver in use: wl
        Kernel modules: bcma, wl

Offline

#4 2022-01-05 20:28:59

VelocityDv
Member
Registered: 2022-01-04
Posts: 12

Re: [SOLVED] wireless connection with bcm4331

wpa_passphrase ssid passphrase

in /etc/wpa_supplicant/wpa_supplicant.conf
ctrl_interface=/run/wpa_supplicant
ctrl_interface_group=wheel
update_config=1

network={
        ssid="myssid"
        psk=mypsk
}

systemctl enable dhcpcd.service
systemctl start dhcpcd.service
systemctl enable wpa_supplicant@wlp4s0.service
systemctl start wpa_suppplicant@wlp4s0.service

Offline

#5 2022-01-05 21:10:19

Head_on_a_Stick
Member
From: London
Registered: 2014-02-20
Posts: 7,769
Website

Re: [SOLVED] wireless connection with bcm4331

If you're using wpa_supplicant@wlp4s0.service then the configuration file should be at /etc/wpa_supplicant/wpa_supplicant-wlp4s0.conf:

# /usr/lib/systemd/system/wpa_supplicant@.service
ExecStart=/usr/bin/wpa_supplicant -c/etc/wpa_supplicant/wpa_supplicant-%I.conf -i%I

The journal should confirm this as the source of the problem:

journalctl -u wpa_supplicant@wlp4s0 -u dhcpcd

And note that the service can be started at the same time as it is enabled by passing the --now flag to systemctl(1).

Offline

#6 2022-01-05 21:34:09

VelocityDv
Member
Registered: 2022-01-04
Posts: 12

Re: [SOLVED] wireless connection with bcm4331

-- Boot 95c2e021f1f64f4d856c54d501d56409 --
Jan 05 19:31:51 ArchLinux dhcpcd[368]: dhcpcd-9.4.1 starting
Jan 05 19:31:51 ArchLinux dhcpcd[3-- Boot 95c2e021f1f64f4d856c54d501d56409 --
Jan 05 19:31:51 ArchLinux dhcpcd[368]: dhcpcd-9.4.1 starting
Jan 05 19:31:51 ArchLinux dhcpcd[371]: dev: loaded udev
Jan 05 19:31:51 ArchLinux dhcpcd[371]: DUID 00:04:a8:02:10:01:f4:d7:95:51:ae:c3:32:79:56:30:21:cb
Jan 05 19:31:51 ArchLinux systemd[1]: Starting dhcpcd on all interfaces...
Jan 05 19:31:51 ArchLinux systemd[1]: Started dhcpcd on all interfaces.
Jan 05 19:31:52 ArchLinux dhcpcd[371]: enp3s0f0: waiting for carrier
Jan 05 19:31:52 ArchLinux dhcpcd[371]: enp3s0f0: waiting for carrier
Jan 05 19:31:52 ArchLinux dhcpcd[371]: enp3s0f0: waiting for carrier
Jan 05 19:31:52 ArchLinux systemd[1]: Started WPA supplicant daemon (interface-specific version).
Jan 05 19:31:52 ArchLinux wpa_supplicant[431]: Successfully initialized wpa_supplicant
Jan 05 19:31:52 ArchLinux dhcpcd[371]: wlp4s0: waiting for carrier
Jan 05 19:31:52 ArchLinux dhcpcd[371]: wlp4s0: waiting for carrier
Jan 05 19:31:52 ArchLinux dhcpcd[371]: wlp4s0: carrier acquired
Jan 05 19:31:52 ArchLinux dhcpcd[371]: wlp4s0: IAID de:98:23:b2
Jan 05 19:31:52 ArchLinux dhcpcd[371]: wlp4s0: adding address fe80::4a1:6264:d81d:162d
Jan 05 19:31:52 ArchLinux dhcpcd[371]: wlp4s0: old hardware address: ca:d3:de:98:23:b2
Jan 05 19:31:52 ArchLinux dhcpcd[371]: wlp4s0: new hardware address: 8c:2d:aa:33:e0:df
Jan 05 19:31:52 ArchLinux dhcpcd[371]: wlp4s0: carrier lost
Jan 05 19:31:52 ArchLinux dhcpcd[371]: wlp4s0: deleting address fe80::4a1:6264:d81d:162d
Jan 05 19:31:52 ArchLinux dhcpcd[371]: wlp4s0: carrier acquired
Jan 05 19:31:52 ArchLinux dhcpcd[371]: wlp4s0: IAID aa:33:e0:df
Jan 05 19:31:52 ArchLinux dhcpcd[371]: wlp4s0: adding address fe80::fab4:a330:e22d:d47
Jan 05 19:31:52 ArchLinux dhcpcd[371]: wlp4s0: carrier lost - roaming
Jan 05 19:31:52 ArchLinux dhcpcd[371]: wlp4s0: carrier lost - roaming
Jan 05 19:31:52 ArchLinux dhcpcd[371]: wlp4s0: carrier lost - roaming
Jan 05 19:31:52 ArchLinux dhcpcd[371]: wlp4s0: carrier lost - roaming
Jan 05 19:31:53 ArchLinux dhcpcd[371]: wlp4s0: soliciting an IPv6 router
Jan 05 19:31:53 ArchLinux dhcpcd[371]: wlp4s0: carrier acquired
Jan 05 19:31:53 ArchLinux dhcpcd[371]: wlp4s0: IAID aa:33:e0:df
Jan 05 19:31:53 ArchLinux dhcpcd[371]: wlp4s0: soliciting an IPv6 router
Jan 05 19:31:54 ArchLinux dhcpcd[371]: wlp4s0: soliciting a DHCP lease
Jan 05 19:31:55 ArchLinux wpa_supplicant[431]: wlp4s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UN>
Jan 05 19:31:55 ArchLinux wpa_supplicant[431]: wlp4s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UN>
Jan 05 19:32:03 ArchLinux dhcpcd[371]: wlp4s0: carrier lost - roaming
Jan 05 19:32:03 ArchLinux dhcpcd[371]: wlp4s0: carrier lost - roaming
Jan 05 19:32:03 ArchLinux dhcpcd[371]: wlp4s0: carrier acquired71]: dev: loaded udev
Jan 05 19:31:51 ArchLinux dhcpcd[371]: DUID 00:04:a8:02:10:01:f4:d7:95:51:ae:c3:32:79:56:30:21:cb
Jan 05 19:31:51 ArchLinux systemd[1]: Starting dhcpcd on all interfaces...
Jan 05 19:31:51 ArchLinux systemd[1]: Started dhcpcd on all interfaces.
Jan 05 19:31:52 ArchLinux dhcpcd[371]: enp3s0f0: waiting for carrier
Jan 05 19:31:52 ArchLinux dhcpcd[371]: enp3s0f0: waiting for carrier
Jan 05 19:31:52 ArchLinux dhcpcd[371]: enp3s0f0: waiting for carrier
Jan 05 19:31:52 ArchLinux systemd[1]: Started WPA supplicant daemon (interface-specific version).
Jan 05 19:31:52 ArchLinux wpa_supplicant[431]: Successfully initialized wpa_supplicant
Jan 05 19:31:52 ArchLinux dhcpcd[371]: wlp4s0: waiting for carrier
Jan 05 19:31:52 ArchLinux dhcpcd[371]: wlp4s0: waiting for carrier
Jan 05 19:31:52 ArchLinux dhcpcd[371]: wlp4s0: carrier acquired
Jan 05 19:31:52 ArchLinux dhcpcd[371]: wlp4s0: IAID de:98:23:b2
Jan 05 19:31:52 ArchLinux dhcpcd[371]: wlp4s0: adding address fe80::4a1:6264:d81d:162d
Jan 05 19:31:52 ArchLinux dhcpcd[371]: wlp4s0: old hardware address: ca:d3:de:98:23:b2
Jan 05 19:31:52 ArchLinux dhcpcd[371]: wlp4s0: new hardware address: 8c:2d:aa:33:e0:df
Jan 05 19:31:52 ArchLinux dhcpcd[371]: wlp4s0: carrier lost
Jan 05 19:31:52 ArchLinux dhcpcd[371]: wlp4s0: deleting address fe80::4a1:6264:d81d:162d
Jan 05 19:31:52 ArchLinux dhcpcd[371]: wlp4s0: carrier acquired
Jan 05 19:31:52 ArchLinux dhcpcd[371]: wlp4s0: IAID aa:33:e0:df
Jan 05 19:31:52 ArchLinux dhcpcd[371]: wlp4s0: adding address fe80::fab4:a330:e22d:d47
Jan 05 19:31:52 ArchLinux dhcpcd[371]: wlp4s0: carrier lost - roaming
Jan 05 19:31:52 ArchLinux dhcpcd[371]: wlp4s0: carrier lost - roaming
Jan 05 19:31:52 ArchLinux dhcpcd[371]: wlp4s0: carrier lost - roaming
Jan 05 19:31:52 ArchLinux dhcpcd[371]: wlp4s0: carrier lost - roaming
Jan 05 19:31:53 ArchLinux dhcpcd[371]: wlp4s0: soliciting an IPv6 router
Jan 05 19:31:53 ArchLinux dhcpcd[371]: wlp4s0: carrier acquired
Jan 05 19:31:53 ArchLinux dhcpcd[371]: wlp4s0: IAID aa:33:e0:df
Jan 05 19:31:53 ArchLinux dhcpcd[371]: wlp4s0: soliciting an IPv6 router
Jan 05 19:31:54 ArchLinux dhcpcd[371]: wlp4s0: soliciting a DHCP lease
Jan 05 19:31:55 ArchLinux wpa_supplicant[431]: wlp4s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UN>
Jan 05 19:31:55 ArchLinux wpa_supplicant[431]: wlp4s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UN>
Jan 05 19:32:03 ArchLinux dhcpcd[371]: wlp4s0: carrier lost - roaming
Jan 05 19:32:03 ArchLinux dhcpcd[371]: wlp4s0: carrier lost - roaming
Jan 05 19:32:03 ArchLinux dhcpcd[371]: wlp4s0: carrier acquired time.

Offline

#7 2022-01-05 21:39:29

VelocityDv
Member
Registered: 2022-01-04
Posts: 12

Re: [SOLVED] wireless connection with bcm4331

Head_on_a_Stick wrote:

If you're using wpa_supplicant@wlp4s0.service then the configuration file should be at /etc/wpa_supplicant/wpa_supplicant-wlp4s0.conf:

# /usr/lib/systemd/system/wpa_supplicant@.service
ExecStart=/usr/bin/wpa_supplicant -c/etc/wpa_supplicant/wpa_supplicant-%I.conf -i%I

The journal should confirm this as the source of the problem:

journalctl -u wpa_supplicant@wlp4s0 -u dhcpcd

And note that the service can be started at the same time as it is enabled by passing the --now flag to systemctl(1).


for

# /usr/lib/systemd/system/wpa_supplicant@.service
ExecStart=/usr/bin/wpa_supplicant -c/etc/wpa_supplicant/wpa_supplicant-%I.conf -i%I

there is currently no file as such. would I need to create a new one and add the following? thanks

Offline

#8 2022-01-05 21:57:24

Head_on_a_Stick
Member
From: London
Registered: 2014-02-20
Posts: 7,769
Website

Re: [SOLVED] wireless connection with bcm4331

To repeat: you need a file at /etc/wpa_supplicant/wpa_supplicant-wlp4s0.conf for wpa_supplicant@wlp4s0 to work properly.

I quoted the ExecStart line in /usr/lib/systemd/system/wpa_supplicant@.service just to demonstrate this, sorry if that was unclear. The ArchWiki page you claimed to have followed also provides this information.

And please use code tags when posting terminal output. For journal content it's best to either direct the output to a file or pass the --no-pager option (--no-p for short) to avoid the clipping which is evident in your post.

Offline

#9 2022-01-05 22:16:13

VelocityDv
Member
Registered: 2022-01-04
Posts: 12

Re: [SOLVED] wireless connection with bcm4331

yes i have this file /etc/wpa_supplicant/wpa_supplicant-wlp4s0.conf

Offline

#10 2022-01-05 22:35:46

VelocityDv
Member
Registered: 2022-01-04
Posts: 12

Re: [SOLVED] wireless connection with bcm4331

Offline

#11 2022-01-06 10:44:14

Head_on_a_Stick
Member
From: London
Registered: 2014-02-20
Posts: 7,769
Website

Re: [SOLVED] wireless connection with bcm4331

Okay, that looks like a Broadcom SNAFU — Linux support for that brand of wireless card is about as bad as it gets. If you have the choice *never* buy anything from that manufacturer if you want to run it with an open-source operating system. IMO the same goes for NVIDIA graphics cards but that's off-topic here.

Support for that brand is so bad the ArchWiki has a whole page devoted to it and there are two suggestions on that page for this particular card. Try them both out and if they don't work post back with full details of exactly what you tried and how you tried to implement it. Also post any relevant error messages & journal content in full. TIA.

Offline

#12 2022-01-06 15:57:00

seth
Member
Registered: 2012-09-03
Posts: 51,940

Re: [SOLVED] wireless connection with bcm4331

Make sure your wpa_supplicant service isn't colliding w/ https://wiki.archlinux.org/title/Dhcpcd … supplicant
Reboot, try to connect the wifi and post the outputs of

rfkill
find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
sudo journalctl -b | curl -F 'f:1=<-' ix.io

Online

#13 2022-01-10 22:35:59

VelocityDv
Member
Registered: 2022-01-04
Posts: 12

Re: [SOLVED] wireless connection with bcm4331

i used nmtui to get it working. idk how but it works now. thanks for all the help.

Offline

Board footer

Powered by FluxBB