There's a reason why website content exists and should be read thoroughly...

The list is complete as far as supported RPi devices by the SARPi Project goes. The SARPi installer for the Raspberry Pi (1) works perfectly for the Zero - something which may have been overlooked by the pedantic because "zero" doesn't appear in any of the file name(s).

The SARPi Project isn't like a radio show where you call/write in and ask for your mom's favourite song to be played on her birthday. The SARPi Project very much supports and promotes users doing their own thing and being ultimately successful towards that end. One of the real strengths of Slackware [ARM] is; it's the best educational tool for Linux that ever existed, or will exist, and makes anything possible by design and investing the appropriate amount of time, effort, and self-edification into it. Slackware offers all users the same capability and it should be grabbed by both horns and harnessed and tamed. If/when that's not possible, maybe Google can help... https://github.com/gpiozero/gpiozero

1 members found this post helpful.

Is that an invitation to try a proper arm install for once in my life ?
I'm actually thinking of making an x86_64 miniroot

1 members found this post helpful.

HAHAHA. Go for it!

Louigi... the truth is, I thought about you while I was building this batch for Slackware ARM 14.2 on the RPi4, hoping it might be useful for you, and any others who have a need/desire to run the soft float port. Plus the "N/A" - kernel and release date version - on the SARPi downloads webpage has been annoying me for some time. So, I really had to do something about it to save my future sanity.

Incidentally, I had to "Frankenstein" a few things, initially, in order to make build it properly - e.g. I didn't have a RPi4 kernel/modules which supported soft float ABI and had to basically compile it in stages. But we won't be going into the finer details in case MoZes finds out what I did to his software's integrity. LOL!

Wow that's an honor for me
I might not try the full install but I'll check out that the kernel, modules and hacks are fine on my RPi4.

As I've said may times before: it is perfectly fine to run the RPi4 current kernel with the softfloat 14.2 userland: although the kernel is perfectly capable of receiving userland requests to perform hardfloat operations, have the hardfloat unit perform it and give back the result to the useland; the softfloat userland will never ask that.
To my understanding it is the libc that will ither perform softfloat operation all in userland or ask kernel to perform hardfloat so the 14.2 userland will never ask the kernel to perform hardfloat operations regardless if it could or not and the kernel is not providing the softfloat calculation to softfloat libc.
The other way round is not possible: you cannot use a hardfloat userland with a kernel that is not configured to perform hardfloat operations ... it might be even more complicated then that as to my understanding there are 2 possibilities for performing hardfloat operations

• softfp - this supports a hardware FPU, but the ABI is soft compatible.
• hard - the ABI uses float or VFP registers.

We are going way off topic and in a ground I'm not even properly prepared on.
To put it short I've been using the SARPi4 hardfloat kernel to run 14.2 userland ever since I got my first RPi4 and I never got into trouble directly because of this.
Anytime I could not get it to work was probably because I did something else wrong.

It's nice that we now have the matching kernel (which I guess will be just a tiny bit smaller with respect to the same release hardfloat capable one) ... and I will test it just to double check that everything is fine.

Don't worry about MoZes ... he's probably still in the basement listening to the music you gave him or maybe catching up with the last updates on current.

1 members found this post helpful.

I use https://git.kernel.org/pub/scm/linux.../ktest?id=HEAD for testing, checking, verifying, etc. The few potential issues that came to my attention this time around were...

... which may be relevant to some users.

Otherwise; wired networking is stable, connecting USB devices are detected and seem to work fine, rsync/ftp/wget/curl remote files are all working great, ssh no problem(s), and building from source is 100% successful.

I haven't tested the desktop, etc. So, any issues in that respect you'll have to keep me apprised of. NB: unless it's a show-stopper I won't be interested in putting any time/effort into troubleshooting this SARPi batch for 14.2 on the RPi4.

I don't care about going off-topic when it's relevant and interesting.

[EDIT] found this recently which I may test out to see if it's useful... http://autotest.github.io/

I was just joking, aparently my humor is too odd to be understood

I just cooked a miniroot with the sarpi 4 softfloat goodies ... basic functionality is ok.
From home I will do more extensive wifi testing ... I'm away currently (but I can scan nearby AP from the onboard wifi).
I will try one of the testing utils on the newest revision RPi4 I have ... will update you if I find anything worth noting.

1 members found this post helpful.

Oh... you were joking! I do apologise for misunderstanding your humour. Could you explain the joke please?

Thanks Louigi.

I've got the Slackware 14.2 OS saved on a sd card for the time being. If there's any serious flaws found with the SARPi kernel/modules or networking I can easily build a fresh batch in 30-40 minutes.

Wired connection seems fine ... I used that to take over there the wpa config and my netconnect scrpt.
Wifi is working fine ... I did a slackpkg update, upgrade-all through wifi without any problems (well after upgrade wget was broken for a missing dep but I fixed that).
I installed bluez and bluez-firmware but can't get any device to show up.
I looked in the sarpi4 hacks and I could not find the bluez firmware there so maybe that's why ... would you consider adding that into the sarpi4 hacks ?
I will now see if I can get one of the tests you suggested to work on the miniroot.

Oh geez... not this Bluetooth shizzle again. Thanks for reminding me. Have you forgotten what we did to fix this?

I honestly haven't looked at it since last time... https://www.linuxquestions.org/quest...ml#post6219476 ... but I did notice that the files in '/usr/lib/firmware/brcm' were pretty much the same ones as found in '/lib/firmware/brcm'. So, I did a little jiggery-pokery and some re-working of the SARPi build processes - but only revising the '/boot/config.txt' file on Slackware ARM current. I haven't done anything with the 14.2 /boot packages.

[EDIT] The new BCM wireless and Bluetooth card drivers (43455 and 43456) are already included in the sarpi-hacks pkg - for 14.2 and current. I did this with Slackware 15.0 in mind because I do not want to be going through this issue again for a while. Haha!

Anyway... add these two lines into the '/boot/config.txt' file...

Reboot the device. When you login you should get a device showing up...

This seems to be working for me. Plus, I haven't installed any new packages since installing Slackware ARM 14.2 on the RPi4. So there's only the official packages which MoZes includes, and nothing else, on this system.

Those two lines in '/boot/config.txt' are what's missing and they do need to be in there. I'll add them into 'config.txt.new' and do a re-build of this 14.2 batch and then upload it. That is, unless you get back to me before then and say it's still not working.

[EDIT #2] - I just checked and those two lines are in the '/boot/config.txt.new' file. Hmmm. Can you have a look and see if it's the same with your files please Louigi? My '/boot/config.txt.new' Bluetooth section looks like this...

1 members found this post helpful.

Wow I thought I would need some bluez firmware stuff again .... I can confirm that by just putting
in /boot/config.txt BT s working (sarpi4 goodies for Pi4 14.2 + 14.2 miniroot + bluez*).

I did not remember the details but I was convinced I would need some firmware for it t work ... I guess not.
Sorry I've not found the time to setup the test tool and chase down the dependencies required to get it to run
I was out of enthusiasm after manually chasing the links dependencies ... I was too lazy to to put this into the miniroot and half way down doing it manually I regretted it ...
I wonder did any of that get into slackpkg ?
Maybe I should clean it up a bit and put it on slackware docs ... after all it is very slackware specific.

Thanks very much for your input again Louigi. It's all updated now and a new SARPi batch has been built for Slackware ARM 14.2 on the RPi4 with the 'config.txt' amendments included, and uploaded: https://sarpi.fatdog.eu/index.php?p=rpi4get142

You'll probably have bluez-firmware installed if you did a full installation of Slackware ARM 14.2, as have I, and that's why the Bluetooth is initialising as expected. Just as I already have bluez-5.40 installed, but there is an update available... not that I'll ever use it, personally!

Good to know it works for the RPi3/4 without any further tinkering. Gotta love Slackware [ARM] <3

BTW: noticed ttyAMA0 gets regstered but then something happens and init complains that the serial console is re-spawning too fast. I looked and in fact /dev/ttyAMA0 is not there.
Not sure if its
enable_uart=0
reponsible for that (taking the first serial for BT ... I will try if enable_uart=1 makes it any better) or if it is some other issue.

From post #1:

Amen to that. In retrospect, it's under powered. It's funny to think how far we have come since the 1970s. Then we still had one Z80 @4Mhz with CP/M 'mini computer' running terminals in all departments of a small business on 64KB of ram, or if they were lucky, a few 64KB pages. The computer was to be considered offline on Thursday mornings, because the wages program was being run. But accounts, stock control, etc were all done on the Z80 via 1200 baud dumb terminals connected to serial ports.

Now we consider the RazPi 1(A) with 32bit cpu @ hundreds of Mhz +256MB ram as totally under powered.

That's life and evolution ... 1991 the Linux kernel was less then 1Mb ... now look at it's size even without all the modules in /lib/modules
1992 a 33Mhz 486DX with 8Mb of ram and 120Mb HDU was concidered quite luxury what shall we concider as luxury now ? 8 core i7, 64Gb Ram and 2Tb HDU
I normally make the efi boot partition no smaller then 128Mb ... I used to have dual boot with both windows and full linux install in 120Mb

@Exaga ... nope enable_uart=1 made no difference ... mayne because I installed the srapi 4 goodies in chroot it made a mess of /dev ...
Created the device manually but still no go