hello all, gee it's quiet around here, maybe mozes needs quiet to get 6.9.x off and running

last week or so, rpi3 sarpi installed slackware, networking has come to a crawl

I don't know if any sarpi updates, boot-firmware/hacks, affects anything like wireless or is that just slackware proper that does

I have another slackware arm install on laptop other side of room and networking is way better, this is a slackware proper install, I have not done anything router changes

THANKS

SARPi always sucks. Nothing new there. What's so different about last week or so?

Specifics please.

some time ago, I got rpi3, installed slackware by way of sarpi, been applying slackware updates and sarpi updates since, expecting something to fail/crash/stop working but it's still going

specifically, it's all up to date and I've not done anything but updates

THANKS

hmmm, saw this thread

if I'm applying sarpi updates and slackware updates, am I causing trouble?

1 members found this post helpful.

Not at all. Slackware is ultimately reliable. I always ensure SARPi works to install it successfully and keep up to date with any drivers and firmware for the RPi models.

You're free to basically do whatever you like with the software you install and run. Who is the better judge of how to use it but you? Only if/when you rely on others in order for things to work there may be issues. Slackware is very accommodating and easy to work with. Usually the only problems are with what the Raspberry Pi dev's implement and release, but that's not very often these days.

From your initial post I assumed there was a significant problem somewhere along the line and was interested to know more details in order to determine if it needed to be addressed.

1 members found this post helpful.

Thank you Exaga. As I said. I've regularly applied sarpi and slackware updates and just recently, wifi has come to a crawl.

ssh 15 to 20 seconds to respond, 15 to 20 seconds for password

cli speed test script
rpi3 sarpi install
PBP Slackware AArch64

1 members found this post helpful.

If you're using the onboard RPi WNIC it's a bag of shite. Always was. Always will be. I've said this for years and years.

Find yourself the cheapest, nastiest, most unstable, nightmare inducing, USB wireless dongle and it will still be infinitely more reliable that the Cypress crap that's featured on the Raspberry Pis while running under Slackware. This is my experience and I'd testify to that and sign it with my own sweat and tears. I probably already have quite a few times, in fact.

Get yourself a USB wireless dongle. Forget the onboard RPi WNIC shizzle and do your sanity and equilibirum a favor.

1 members found this post helpful.

Reliability of Rpi's wifi I can't speak about, because I seldom use it. But I always ensure that it functions after a new installation. I'm running a Rpi4 with Slackware aarch64 and a self-built kernel from the Raspberry Pi Kernel fork, and an Rpi5 with Sarpi installed Slackware aarch64.

So after reading the OP I was curious about their wifi functionality. I ran the speedtest posted on both, as well as speedtest.net via firefox, several times.

The Rpi5 downloads were between 110-118 Mbit/s, uploads averaged 33.98 Mbit/s, depending on server. The Rpi4 downloads were between 50-70 Mbit/s, uploads 21-33 Mbit/s, depending on server. Max upload on my internet connection is 34 Mbit/s.

So I'm not dissatisfied with the wifi on the Rpi4 and 5, but as stated I don't use wifi a great deal so I have no idea how they might function long term. Just my observations...

2 members found this post helpful.

I appreciate and thank you for the comments.

I'm sorry if I wasn't clear, I just wanted to know if there was something that changed recently that has made wifi dead slow, slackware updates or sarpi updates, like something kernel, firmware, whatever.

This rpi3 has been running slackware installed by way of sarpi a few years same way and this first time this has happened.

Yes I can dongle but doesn't answer why whatever happened.

2 members found this post helpful.

Can't say anything about an Rpi3, but I regularly update my pi's and there has been no change in wifi that I have noticed... Cheers!

2 members found this post helpful.

Problems just need explaining with some clarity so that everyone is reading the same page. It saves time, if nothing else.

If this is the first time you have experienced unexplained wireless weirdness of Twilight Zone proportions on the Raspberry Pi devices then you've been lucky.

A lesson I learned early on in my ARM adventures was that whatever works is best. Doesn't matter what that is as long as it works. RPi wireless may be quite good now but I won't rely on it due to past experiences. If someone comes along with solid affirmation that it's stable and reliable I may change my mind.

Thanks for testing.

2 members found this post helpful.

That's more or less been my approach to making Rpi's work, and I don't use them for anything "mission critical", but they are useful, once you get them running the way you want. Cheers!

1 members found this post helpful.

how is sarpi slackware installed rpi3 onboard wifi disabled to use usb wifi dongle instead? thanks

1 members found this post helpful.

rmmod brcmfmac - to remove the onboard RPi wireless NIC drivers

modprobe <your_new_module> - to load the drivers for your USB wireless dongle.

Example:
What you need to achieve is covered on the following page: https://sarpi.penthux.net/index.php?p=wireless-nic - all the information is there but you may have to scroll around a bit depending on your order of doing things.

[EDIT] it's not anything to do with 'sarpi slackware' it's just Slackware.

1 members found this post helpful.

how so? the 'following page' you mentioned says

there is no "/boot/config.txt" with "just" slackware, right?

1 members found this post helpful.

According to https://docs.slackware.com/slackware..._tree_overlays, yes there is a /boot/config.txt file.

But we're dealing with Slackware ARM that's been installed with the SARPi installer on a Raspberry Pi 3 here. Right? In which case, yes there most certainly is a /boot/config.txt file.

SARPi doesn't offer or create an alternate version of Slackware ARM/AArch64. It installs the official software. The difference is in the way that the system boots. Stuart observes and maintains open-source standards by using the U-boot universal boot loader in the official Slackware software. Whereas SARPi doesn't by using the closed-source Raspberry Pi boot loader to achieve the same thing.

1 members found this post helpful.