LinuxQuestions.org - wlan0 raspberry pi4 AArrch64

- Slackware - ARM (https://www.linuxquestions.org/questions/slackware-arm-108/)

- - wlan0 raspberry pi4 AArrch64 (https://www.linuxquestions.org/questions/slackware-arm-108/wlan0-raspberry-pi4-aarrch64-4175716399/)

wlan0 raspberry pi4 AArrch64

Usually I use rc.inet1 and wpa_supplicant for network connection. I have used it successfully on both my raspberry pi4 using the sarpi installer and on Slackware15 on my X84_64.

Unfortunately on AArch64 I can't seem to get to the wlan0 interface on boot up. I can bring up the network after login when I...

Code:

./rc.inet1 wlan0_start

...but never when booting up. I don't have an ethernet cable but I set up rc.inet1.conf as if I did have one, eth0 seems to be available when dhcpd starts during boot because it says that its '..waiting for carrier'

I stopped inet1 and setup NetworkManager, the problem still persists. Network Manager will only connect when I run XFCE4 and never during boot, even when it reports that its starting it up.

I've only had this problem with AARch64 and I have no idea why its not recoginising wlan0 until after boot.

A couple of things.

wlan0 is the onboard wifi. I had signal difficulties with it as any nearby lump of metal can act as a Faraday shield to the aerial, inhibiting reception/transmission. I made that worse with a (metal) Flirc case. The download speed varied with what angle/orientation the box was at.
I also had initial issues and found the Debian (RPi OS) firmware was patched and solved it. Then I went back to the kernel one and it worked too :eek: I never got to the bottom of that.
I found many folks had switched to usb wifi. I did too, and never looked back. I don't load the firmware now, just usb wifi.

The firmware takes a second to load. I will be looking into why that is the case.

For now a good work around is to enable network manager (netconfig) and edit:

Code:

/etc/NetworkManager/conf.d/00-dhcp-client.conf

Then disable dhcpcd and have network manager use dhclient to gain an IP address.

Code:

[main]

# Choose a DHCP client below. Upstream recommends internal, but results may vary.

#

# dhcpcd is the DHCP client usually used by Slackware:

#dhcp=dhcpcd

#

# dhclient is the ISC reference DHCP client, part of the dhcp package:

dhcp=dhclient

#

# This is a simple DHCP client that is built into NetworkManager:

#dhcp=internal

Reboot and you should be able to get an IP address on wlan0. Let me know how it goes!

EDIT: I did reproduce this issue. With the above changes it is fixed, sort of. :) WiFi takes a minute to load and grab an IP address.

EDIT2:

Code:

[  22.042881] Bluetooth: hci0: BCM4345C0 'brcm/BCM4345C0.hcd' Patch

[  22.101950] EXT4-fs (sda2): re-mounted. Quota mode: none.

[  22.599289] EXT4-fs (mmcblk1p2): mounted filesystem with ordered data mode. Quota mode: none.

[  22.836738] Bluetooth: hci0: BCM43455 37.4MHz Raspberry Pi 3+

[  22.836758] Bluetooth: hci0: BCM4345C0 (003.001.025) build 0342

[  23.435419] NET: Registered PF_INET6 protocol family

[  23.435964] Segment Routing with IPv6

[  23.435977] In-situ OAM (IOAM) with IPv6

[  26.282788] bcmgenet fd580000.ethernet: configuring instance for external RGMII (RX delay)

[  26.342986] bcmgenet fd580000.ethernet eth0: Link is Down

[  83.062800] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6

[  83.066350] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Nov  1 2021 00:37:25 version 7.45.241 (1a2f2fa CY) FWID 01-703fd60

[  90.085848] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

Takes about 90 seconds from first boot.