I upgraded to the latest kernel packages March 11th release. Now I am unable to connect to the Wi-Fi router without using an Ethernet cable. When trying to access addresses outside the local network I get "ping: google.com: Temporary failure in name resolution". Attempts to connect to the Wi-Fi it won't take the password. Not sure if it's a problem with the packages or on my end somewhere. It was fine before the upgrade.

Please state clearly:
1. Whether you have LAN access over Wi-Fi? Try pinging the router, and other hosts.
2. Whether you use NetworkManager (or what else?) to connect to Wi-Fi.
3. Whether you can `ping 1.1.1.1` address.
4. Whether you rely on DHCP or use static configuration.
5. Whether connecting a different Wi-Fi network solves the problem.
6. Whether you use a firewall, like nft.
7. Whether you use WireGuard/OpenVPN.

Also, post the output of:
1. `ifconfig`
2. `cat /etc/resolv.conf`

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.200 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fe80::3ebb:d6b6:54b0:ee94 prefixlen 64 scopeid 0x20<link>
ether b8:27:eb:54:ab:87 txqueuelen 1000 (Ethernet)
RX packets 60626 bytes 10550376 (10.0 MiB)
RX errors 0 dropped 296 overruns 0 frame 0
TX packets 87006 bytes 19187321 (18.2 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 326 bytes 31068 (30.3 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 326 bytes 31068 (30.3 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlan0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 12:99:c2:5c:91:39 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

# Generated by NetworkManager
search .myftp.org
nameserver 9.9.9.9
nameserver 149.112.112.112

wlan0 has no inet? ip address, how did you set one before?

I have network manager auto connect to wlan0 with static ip. But after the upgrade I no longer can connect to any network. Even a guest network without password. Only way to get headless access was to plug it directly in with eth0.

Your wlan0 interface does not have an IP address, no wonder you do not have internet access. Now tell what it is exactly that you do to obtain it.

I usually activate my connection with nmtui and have it auto reconnect. After reboot it will auto connect. Now I can't connect to any Wi-Fi routers. I have it connected with eth0.

I'm no network expert, just some experience doing my stuffs.

I don't know how you auto reconnect wlan0 with static ip without indicating ip addr.

Are you getting prompt for ip addr, ssid, passphrase?

1 members found this post helpful.

I select auto connect in nmtui. Everything is entered correctly. It shows like it's trying to connect but eventually times out and asks for the password. I put in the correct password and yet it still won't connect. Won't even connect to an open ssid. This is what's weird about it. Nothing works except for eth0 but even that's not completely working properly. This is why I'm at a lost for ideas.

Power cycle the router, log in as admin, what wired/wireless devices does it see?

never used nmtui, for years I've configured wpa_supplicant.conf, run a script at boot that runs wpa_supplicant daemon, brings up id addr, add default gw

1 members found this post helpful.

Your reply is useless by itself. Post the logs!

If you're only using the RPi3 for headless (remote) access, you might want to install Slackware proper (the RPi4 install guide can be followed exactly - the installer image is the same for both).
I rarely update the firmware for the RPi because my experience is that it's not well tested upstream.
I don't know if anybody has tested installing SA64 on the RPi3 recently, but you can try it if you have a spare SD card and SSD/HD.
If it works for you now it should continue to work since the Kernel will remain at 6.1 until the release of Slackware 15.1.

1 members found this post helpful.

The logical next step would be to revert the software to a time when it did work, and do not upgrade. As the Slackware saying goes, "If it isn't broken don't fix it."

I have always maintained, since time immemorial, that the Raspberry Pi onboard wireless adapter is more trouble than it's worth and users should look to install a cheap-and-cheerful USB wirless adapter instead. There are far less problems and issues by doing so for Slackware/driver/module/sanity reasons.

To quote the Aussies, "Bloody oath!"

---

@etalia
As far as SARPi usage and development goes, and you can take this from the horses mouth, it should no longer be the go-to option while MoZes supports the Raspberry Pi. Users should install and run the official Slackware ARM/AArch64 software because that is maintained and supported much better than I have the inclination or appetite to manage these days. Yes (in case you were wondering) new batches of SARPi are built from time to time as and when my motivation and the opportunity presents itself, but long gone are the days when I dedicated almost all of my free time to supporting a hardware platform of which the creators weren't interested in endorsing Slackware running on it! SARPi is there if/when people want to test or play around or <insert reason here> purposes. I don't really support or get involved with things as much as I once did because I'm not getting any younger, I have health issues which are degenerative, and there's much more to life than solving other people's Linux problems or teaching people how to read instructions properly. Let someone else do it - i.e. Stuart and Brent.

I still love Slackware. I use it every day. My avidity and passion for what Pat creates will never fade away or die before I do.

3 members found this post helpful.

Exaga, Cheers to you and thanks again!

1 members found this post helpful.

Just installed the latest SARPi stuff with the 6.1.24 kernel and wifi is working again, all good... @Exaga ... thanks man, appreciate the time and effort you have put in to make these damn things functional, cheers!

2 members found this post helpful.