Hello all !
I was trying to follow sarpi instruction for a pi4 new installation and have noticed that they seems to be somehow not in line with ( for example ) the rsync repository.
Can you point me to the right site to install a arch64 slackware on a rpi4 ?

Thanks in advance.

Pierluigi

AFAIK, the Sarpi instructions are for 32 bit systems.

64 bit instructions are here.

-->https://docs.slackware.com/slackware...4_bcm2711_rpi4

Hope this helps.

Yes it looks like the site needs some updating... For SARpi and slackwareaarch64, the download example in the SARpi Project installation instructions should be changed from "ftp.slackware.uk::slackwarearm/slackwarearm-current" to "ftp.slackware.uk::slackwarearm/slackwareaarch64-current".

3 members found this post helpful.

Yes, thanks Cliff, I was aware of this site.
Only I'm a bit more familiar with Sarpi and I think it was a bit easier for me ( and my bad english understanding ) to follow sarpi instruction.
Not a problem, though. If is a Slackware ( and it is ) I will follow whatever instruction I find

Pierluigi

I still have 2016 sarpi rpi3 install running and updated. Also have slackwareaarch64 rpi4 running.

slackwareaarch64 is as close to slackware proper, unless you need to tweak kernel stuffs.

As far as I know it's still the only way to install -current onto my pi zero 2w. I just installed it using https://slackware.uk/sarpi/rpi3/current-armv8/img/ and instructions worked (just replace armv7 with armv8 when replacing kernel)

1 members found this post helpful.

Be aware that there are tools such as the os-initrd-mgr and the hardware model specific kernel module loader scripts that were added to the aarch64 port that may not be compatible. I would ask Exaga if they are or are not.

At the very least I think the sarpi kernel packages and Slackware aarch64 kernel packages need to be blacklisted in slackpkg.

Hopefully Exaga will chime in to confirm.

Additionally, the raspberry pi 3 and 4 have support in Slackware Aarch64. The raspberry pi 4 will install according to the installation directions written by Stuart Winter. Sarpi isn't required to run Slackware on the 64 bit Raspberry pis.

I tested the Pi 3B last week and it requires the use of the mini root to install the system. Some manual steps to use the pkgtool utility in a chroot shell are required once booted to run some installation steps.

2 members found this post helpful.

Just to confirm that after the new rsync instruction from netcrawl ( thanks again, mate ! ) I've managed to install a rpi4 with sarpi instruction, following the manual, and adapting names when needed ( eg. replace armv7 with armv8 on removal of packages ).

Thanks to all !


Pierluigi

2 members found this post helpful.

For future reference, here is the Slackware installation documentation I described earlier.

3 members found this post helpful.

I guess you're right, the SARPi installation guide does need updating, if only for clarity and accuracy reasons. I'm really not sure if users rely on it for Slackware AArch64 installation but then it's a moot point because there's the official software and documentation that should be consulted for that purpose. I just assumed users would instinctively refer to the official documentation rather than rely on some old (and somewhat irrelevant) 3rd party shizzle.

1 members found this post helpful.

No worries, I happened to notice a while back that the download examples as shown didn't quite work, and that there was an easy work-around. I've pretty much moved on to the normal slackware aarch64 installation, but I keep the SARPI stuff around because it's what I started with on an Rpi. Cheers!

1 members found this post helpful.

I've made a few alterations to the SARPi Get Slack information. It's not enough, and I know the entire installation guide needs a makeover to bring it up to scratch. It's been on my mind since before Slackware AArch64 was initially released, I just never got around to addressing it. The entire SARPi website is hand coded and will require quite some time and effort to revamp.

Right now I'm inclined to put a website overhaul on the backburner until the RPi5 arrives. Which could be November/December, or even early next year (according to estimated delivery times). At which point it'll make more sense to "kill two birds with one stone" so to speak, by moving things along. So please bear with me in the meantime.

I fully agree with you and think it's prudent, and also essential, that users 'move on' and refer to the official Slackware ARM/AArch64 software and documentation for installation on the Raspberry Pi devices, and all other supported platforms. Whatever Stuart decides is best, is exactly that.

2 members found this post helpful.

rip saRPI?

1 members found this post helpful.

Why not contribute directly to Slackware ARM, add the Raspberry Pi 5 hardware model support (once you have the board), and help document the installation process?

I cannot speak for Stuart but I think it would be a big help to the Aarch64 port. I have the time, am willing to do the work, but I do not have the finances to purchase a Raspberry Pi 5. At least not for several months. Fixed income and all that.

1 members found this post helpful.