Ooops! Looks like I touched a nerve! Sorry, that wasn't intended!

Yes, I know that Sarpi64 is "just" an installer for the official packages. However, there is a big difference in both the kernels and the boot procedure. As far as the Pies go, this makes the difference between a system that works, and one that doesn't. This is not a criticism of Stuart's work. He has regularly acknowledged that he doesn't have much in the way of Pi hardware, and that the other - similar - Arm systems are his priority. This is even stated in the documentation: However, it is a very popular piece of hardware, and Slackwareaarch64 can be made to run on it, as you yourself have shown.

My efforts are to try and work out *why* the basic Slackwareaarch64 install is failing, and use my (limited) knowledge to suggest fixes. I am aware that this may require waiting for the release of the 6.1/2 kernels before we get full support, but in the meantime, there are workarounds - thought they may not be as straightforward as simply using Sarpi or Slarm64.

Hope this smoothes any ruffled feathers!

--
Pete

Not so much ruffled my feathers but torrefied them, not before plucking one from SARPi's plumage to stick in your hat as an ornamental hackle.

Prologue: -
The whole concept and intention behind SARPi64 was to encourage and/or assist in making an official Slackware AArch64 OS a reality. Not to further or facilitate any other unofficial Slackware community projects which are/were generating income from their efforts.

Act 1: The Issue -
I do not want SARPi being used to publicly support or promote anything other than officially released software for which it was created. However much I made that clear at the time it didn't seem to have any bearing on you going ahead with your intentions (which I do not have a problem with - what you do for yourself is your own business) and making it very public with a handheld walkthrough of 'how-to do it' (which I have nothing but problems with - because it encourages others to "contravene SARPi's setup infrastructure to install another product which does not follow the Slackware philosophy", as Alien Bob so eloquently worded it).

Act 2: The Aftermath -
As a result, I closed shop on the SARPi64 Project publicly and shut down the website, removing all information and downloads. I denied the Slackware [ARM] community access to a pioneering and unique endeavor which may, or may not, have been conducive towards achieving its goals. Which caused me much angst and perturbation, and that's understating it because I was consumately livid at the time! However, eventually Stuart decided to create Slackware AArch64 so SARPi64's purpose became superfluous. Which was great because it killed a lot of demons and made a long time dream come true. End of that history and saga.

Act 3: Present Day -
So, when I see people comparing Slackware and SARPi it's usually without explanation or extrapolation and it doesn't instill me with happy thoughts. Someone reading such musings, without understanding the reasons why or what's involved, WILL get the wrong impression and form opinions based on other people's impartiality and ambition. Slackware AArch64 is official software, endorsed by Pat Volkerding, and is the real deal - "Slackware proper" as MoZes might say. SARPi is not any of those things, far from it. SARPi works because it uses the Raspberry Pi boot-firmware that's designed to work exclusively for their ARM device(s), which is closed-source and so far detached from the 'Slackware Way' it might as well be on the surface of Pluto!

Epilogue: -
SARPi64 is no longer relevant now that Slackware AArch64 is available. Bug Stuart about any concerns you may have about it. Please don't use my work as a lever or fulcrum to blame or shame other people's work when it doesn't suit your requirements and/or doesn't expidite desired results.

Go and talk to the RPi people and ask them nicely if they'll work to upstream their changes into the mainline Kernel more readily.
It'd be in their favour!

Linux 6.1.2 is stable on my RPi4 so I just need to build 6.1.3 and reinstall everything and push it out.
You never know, it just might work out of the box and you can dance on the table, and sing to the stars; or watch one of Bill Maher's Club Random podcasts like me!

I might edit the Install doc and tone the message down to a caution.

4 members found this post helpful.

My $.02, or whatever it's worth... I've had the 6.1.2 kernel running on a pi4 for a day or two as well, no problems...

2 members found this post helpful.

I agree! Sadly, I'm not sure how to contact the people who matter...

I'm looking forward to this. I see in another thread you mention a revised installer (if I'm reading it correctly) which I'm also looking forward too.

Yes, I think that would be a good idea. I already had a Pi (Xmas present from my son, a year or two back) and have never really got on with the various 'Buntu distributions, which is what Raspberry seem keen to push. I understand why they do that, as it is pretty idiot proof, but where's the fun in that?

I do like to have control over my systems, and whilst I have tried other distros down the years, I've always kept Slackware as my main OS and never found a good reason to switch to anything else.

Again, apologies if I've upset anyone with my comments. That certainly wasn't my intention. I was trying to highlight the issues I've run into, the workarounds I've tried, and why. My ultimate wish is to see Slackware running on my Arm hardware as smoothly as it does on x86(_64). Its nearly there, and hopefully the upcoming revisions will bring it nearer to that goal.

--
Pete

I found the same with kernel 6.1.2 - no problems whatsoever. It seems pretty solid for my requirements.

2 members found this post helpful.