Hello!
A question. I have a bollixed (A fancy word for broken as designed) 16GB card of the other OS for the Raspberry Pi, a Pi3B (it is the Pi3A design). Can I unzip the SARPI zip file of the FAT32 boot partition onto the contents onto that matching space?

I've read the documents enclosed with the SARPI zip file and it seems to think that I'd need to make a matching space onto the target card before starting things up.

I did also have one on networking, but, ah, I'll save that for a new thread.

If I understand you correctly, you have a faulty SD card and are asking if the contents of sarpi*-installer-boot*.zip can be copied to the /boot directory.

The answer is, "Yes", with the proviso that their release version matches. So you shouldn't mix and swap an earlier release version with a later release version and vice versa.

When SD cards have failed on me in the past I have been able to clone them to a new SD card and repair the system successfully. I've usually done this using 'dd' on another Linux system.

For example:

2 members found this post helpful.

Hello!
A good surmise and a good suggestion. But actually what's broken is the release of the other bird's OS, not the card itself. Much of the OS works, what does not, is VNC, the card will boot properly. Since the whole business is properly setup in the format used by the Pi, I'd like to install your excellent creation from its Zip file onto that, and thence do the next steps from there.

The sarpi*-installer-boot*.zip archives are designed for end users to DIY their way to installing Slackware Linux on the Raspberry Pi devices or for creating a rescue boot disk, etc. They have many implications and purposes and are available for everyone to make use of.

1 members found this post helpful.

Hi

Could you consider initiating the transition of SARPi for Slackware AArch64 into a designated space? One of the primary objectives of Slackware ARM is to establish a platform where individuals can actively contribute to updating and enhancing hardware model support, including direct integration for the RPi within Slackware.

SARPi has veered in a direction that conflicts with Slackware AArch64, potentially causing confusion regarding who's using what. It would be beneficial to delineate these spaces to maintain clarity, moving forwards.
This applies to AArch64 only - SARPi for ARM32 is the best and recommended solution for 32bit Slackware ARM on the RPis.

Additionally, kindly clarify on the website that SARPi is a derivative or fork of Slackware ARM. Currently, the presentation may be misconstrued as the official stance, especially given the lack of mention that the RPi4 is directly supported. Addressing statements about the absence of alterations of Slackware ARM is crucial, particularly concerning the Broadcom firmware within the Slackware kernel-firmware package, which is overwritten by one of the SARPi packages.


Thanks.

1 members found this post helpful.

Hello!
Works for me!
Yes I'll support it.

1 members found this post helpful.

Hello,

With the greatest of respect, I have not considered it. If I would, then and my answer would be the same as it always has been.

One of the objectives of the SARPi Project with the Raspberry Pi 5 is to give you and Brent a few incentives and a basis from which to start supporting this device yourselves. If that should happen, then you'll be supporting the Raspberry Pi 5 officially, which would be fantastic news and great for the Slackware community. You guys do a really great job and are in the best position to do it, and it's very much appreciated indeed.

SARPi has not veered, or wavered at all, in any direction. Not now and not ever. I'm certain you're aware that I've been building and testing SARPi64 installers (a.k.a 32-bit initrd-armv7 with 64-bit kernel and modules) since 2016-2017, and the only thing that was missing back then was a Slackware ARM 64-bit OS to complete the venture. So, in that respect, it's what you're now doing that has encroached on what the SARPi64 Project does and was created for; which is in total support for Slackware AArch64 on the Raspberry Pi devices. SARPi64 Project existed years before you realised there was much profit/benefit in building the Slackware AArch64 OS, I hasten to add. If we can take anything away from this, let it be clear (and let's be honest in agreeing) that SARPi has not veered anywhere, at any time, for any reason. I can only guess why you would propagate such a statement when you know it to be biased, unjustified, unfounded, and untrue.

I consider this as is a cheap shot below the belt. It just shows how little respect there is for anyone else's community efforts other than one's own interests.

"The SARPi Project is a community effort by Penthux.NET and is not officially endorsed by Slackware Linux Inc. or Raspberry Pi Ltd." - featured on multiple pages throughout the SARPi Project website. Including the Home page - https://sarpi.penthux.net/index.php?p=home

"The SARPi Project does not modify any Slackware ARM packages or source-tree files, or Raspberry Pi closed-source boot-firmware or wireless firmware files, within the SARPi installers and packages it distributes." - https://sarpi.penthux.net/index.php?p=sarpi

SARPi is, at best/worst, viewed as a bastardisation of the old official Slackware ARM/AArch64 installer but for all intents and purposes it is just that. The information is all there and has been there for years, changing very little throughout. It never was a problem, and has never been questioned by you (or any other Slackware developers) until now. I believe that everyone who views or uses SARPi software knows exactly what it is and that it's not 'official' by Slackware standards. However, it does use the old Slackware ARM/AArch64 installer (i.e. from before the time when you decided to swap the virtual consoles around in the installer, circa December 2021) and none of the original Slackware setup scripts or installer files have ever been changed, or modified, or removed, or otherwise. Only a SARPi installer README file and the appurtenant kernel modules have been added. Nothing else. I've kept everything intact and as it was intended to be. But you already know this. We've discussed this countless times in years gone by, and I think it was also discussed on the Slack Chat podcast series 1 at some point. Not 100% certain as it was quite some time ago, and you did 99.999% of the talking throughout every episode anyway. LOL

Please tell me exactly what information you would like to see featured on the SARPi Project website and I will do my very best to accommodate you, as always.

I have made it clear in the README file included within the sarpi*hacks package that the overwriting (i.e. updating) of the Broadcom wireless firmware/driver software takes place by installing these packages. (See: https://slackware.uk/sarpi/extra/sarpi-hacks.README and the README file in the relevant pkgs themselves) I also understand this file is linked on each relevant SARPi download page.

The SARPi installer tutorial guide is years old and it has always been my intention to bring it fully up to date. However, it's not a priority on the To-do list. If you have any suggestions on how to expediate this process, or wish to contribute yourself towards making it happen, any input and/or submissions will be most welcome and gratefully received.

The SARPi Project has been supporting the Raspberry Pi 4 since July 2019. There was no official Slackware ARM support at that time, or for another couple of years after that.

One of the freedoms that Slackware offers is for users to do what they like with it. Unless I have missed something fundamental recently then that has not changed, at least from my understanding. If that is not still the case then please enlighten me further. With the SARPi Project I am doing exactly that, and I am not trying to gain anything by doing it. I do not seek recognition or attention. I do not ask for financial donations or endorsements of any kind. There aren't even any "like and subscribe" type requests from me and there never will be. I simply do what I do because I (mostly) like doing it.

Thank you very much for your time.

1 members found this post helpful.

YAY! A new recruit!

I've taken a close look at SARPi, and I've identified a few areas that might benefit from some attention:

1. The OS InitRD management appears to be missing, and this is a crucial element for effective system management and troubleshooting.
   
2. The Installer process seems a bit cumbersome. In contrast, Slackware AArch64 provides a more streamlined experience with a single bootable SD card image, allowing for an entirely offline installation without the need for post-install fixes.
   
3. The Installer appears to be an older, modified version that lacks some of the recent fixes and improvements available in newer releases.
   
4. There seems to be a limitation in the Kernel upgrade process, preventing its completion through slackpkg.

It's important to note these observations in a constructive light, with the aim of potentially enhancing the overall user experience and system functionality. Addressing these points could contribute to a smoother and more efficient use of SARPi.


Should you reconsider and decide to contribute your support to the broader Slackware project, please feel free to reach out. I am confident that the community would greatly appreciate your involvement, particularly considering the significant updates introduced in Linux 6.6.

Your potential contributions could undoubtedly enhance the overall development and success of the Slackware community. Thank you for your consideration, and we look forward to any future collaboration you may be open to.

In reference to the website content, I recommend reviewing the post related to Wi-Fi on the RPi Zero. It might be beneficial to clarify that SARPi utilizes the RPi Kernel fork, encompassing support for newer Raspberry Pi hardware models that may not be included in the standard Slackware distribution. This distinction can help users understand the unique advantages and hardware compatibility that SARPi offers compared to the mainline Slackware release.

Best regards.
Stuart.

Duly noted. SARPi has always been a community effort and has always been portrayed, promoted, and hopefully recognised by all as such. That's with any flaws and shortcomings that come with not being officially endorsed or maintained.

If users want to play around with SARPi software then that's up to them, and why it exists. I can only point out that SARPi as a community project has been nothing but totally supportive and complimentary towards all things Slackware.

I would suggest that you to buy a Raspberry Pi 5 and start supporting it yourself, as the most logical and prudent solution in my opinion.

It goes without saying, I know for sure that my contributions over the years towards Slackware Linux on the Raspberry Pi devices have been very useful and welcome to countless numbers of users, even a few from the Slackware team itself. We're all Slackers doing what we love to do and unless it's working against the greater good or goals of Pat, his contributors, and/or the Slackware community in general, then I'd say that all users are free to follow their dreams and ambitions. I'm very well aware of what's right and/or wrong in that respect.

"The SARPi Project does not support the Raspberry Pi Zero [W] or the Raspberry Pi Zero 2 W" - https://sarpi.penthux.net/index.php?p=rpiviews

* Raspberry Pi
* Broadcom firmwares
- https://slackware.uk/sarpi/extra/COPYRIGHT.TXT

- https://slackware.uk/sarpi/extra/sarpi-hacks.README
It seems any reservations you may have about the SARPi Project are not based on facts or that certain information is missing or misrepresented, but arise from a personal agenda. I'm really not sure why you chose to bring these things into the public eye now. If you're just trying to recruit people to your cause then just say so, and there's really no need to question or challenge the interests, or work, or activities, of others while doing so.

1 members found this post helpful.

Our efforts are dedicated to contributing to the public domain, with a specific focus on optimising the presentation of Slackware on the ARM platform. The primary goal is to create a seamless and efficient experience. Our broader intention is to incorporate any enhancements made into the Slackware x86 platform.

Over the past few years, a substantial investment of thousands of hours has been made in this pursuit. Unfortunately, SARPi's current presentation does not adequately showcase these contributions, as detailed in my earlier response.

As you well know, people frequently overlook details, and SARPi is often mistakenly regarded as the official Slackware. Concerns arise when considering reports about Kernels not undergoing thorough testing before deployment. This issue raises alarms for me as the Kernel is a critical OS component and must be tested. It's imperative to address this, especially when SARPi identifies itself as "Slackware AArch64 on the Raspberry Pi", without making reference to the official presentation and documentation. Aligning with and acknowledging the official support is crucial for maintaining credibility and ensuring a reliable user experience.

Enhancing SARPi's user experience can be achieved with a few straightforward adjustments. One suggestion is to construct the RPi Kernel directly from the build script within the Slackware ARM source tree. Additionally, there is potential to eventually replicate the All in One Installer.

Please consider these recommendations with an open mind. It's important to note that SARPi is a commendable project, and I sincerely appreciate the considerable efforts you've invested. Your contributions are valued, and I hope to see the project continue to thrive.

Cheers
s.

Very sorry doctorwho8 for hijacking your thread. Not my intention.

Hello!
Oh it's okay. I enjoyed the discussions. And now that we've got more work for ourselves, all the better.

1 members found this post helpful.