Slackware - ARMThis forum is for the discussion of Slackware ARM.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
OK. I now see why this issue has arisen - because you have chosen to follow a set of instructions that are intended as an example. The link to the example README is there so that users know what they're looking for just to satisfy curiosity. The instructions, on the page you refer to, does say "See the included SARPi.README for information" and not "follow this link because these are the relevant README instructions". The file itself is titled "### Slackware ARM 14.2 on a Raspberry Pi 1 ###" and says "# Example README to install Slackware ARM 14.2 on a Raspberry Pi (1)" clearly at the top so people know it's just for show. I thought I'd made it clear but apparently not clear enough for all people. You are using a Raspberry Pi 4 not a Raspberry Pi (1) so why would anyone follow instructions not based on the device they are using? However, I can see why some confusion has arisen and that link will be vanishing anon, as a result of your understanding and evaluations. Thank you very much for your input.
For future reference; installing Slackware ARM on a Raspberry Pi successfully is virtually assured by following instructions properly. The SARPi Project does not offer support on how to read instructions properly.
I would suggest for you to ignore the README and become overly familiar with the SARPi Slackware ARM Installation Guide which is a; step-by-step, end-to-end, hand-holding type walk-through aimed at Slackware ARM newbies and facilitated by pretty pictures and screenshots. As I stated previously, the README is for those who are already familiar with the installation of Slackware ARM and it is a very brief 'How-to' for the RPi devices.
as a hardware guy, one of my pet peeves is seeing a signal on page 1 of a schematic, with a pointer to page 4 of the schematic, and upon going to page 4 finding the signal name has been changed to something else... that kind of makes it difficult to figure out what wire goes where... but thanks for the heads up... i'll follow this and let you know how it works out...
as a hardware guy, one of my pet peeves is seeing a signal on page 1 of a schematic, with a pointer to page 4 of the schematic, and upon going to page 4 finding the signal name has been changed to something else... that kind of makes it difficult to figure out what wire goes where... but thanks for the heads up... i'll follow this and let you know how it works out...
Apologies for the confusion. I often forget what it's like to be a Slackware newbie and, for that, in this case I am culpable. To a certain degree I am guilty of expecting Slackware ARM users to know [at least] something about the system they are installing and/or using. Instructions should be clear and concise to all those reading them in any given siutuation. Or else, what good are they?
In order to curb any further ambiguity, the 'file description' section of all SARPi download pages have been revised accordingly. I hope these changes will reflect with greater clarity and meet with your approval. Or, at least, serve to appease one of your pet peeves.
ok.... finally got sarpi4 installer working... it seems it takes a while longer on the rainbow screen before booting begins than i'm used to... about 30 or 40 seconds longer than i'm used to... i'll bet i was waiting the usual 10-20 seconds i was used to on the pi3 and going "it's not working"...
from here on it looks like a standard slackware install using FTP, correct?
ok.... finally got sarpi4 installer working... it seems it takes a while longer on the rainbow screen before booting begins than i'm used to... about 30 or 40 seconds longer than i'm used to... i'll bet i was waiting the usual 10-20 seconds i was used to on the pi3 and going "it's not working"...
from here on it looks like a standard slackware install using FTP, correct?
I have noticed that on first booting the SARPi installer, the RPi seems to hang for quite a few seconds longer than expected. Maybe 10-15 seconds but I have never counted. I'm comparing this time to how it boots after Slackware ARM has been installed, which is invariably quicker. It's mostly the same with all RPi versions, I find. I'm not sure why the RPi hangs in this fashion as the boot-firmware [etc.] is the same. Perhaps the bootloader's expecting, or looking for, "Raspbian" and having a bit of trouble finding it, before giving up and loading the kernel.
I haven't tested with installing Slackware ARM via FTP/HTTP server for a month or so. I just make sure the network is operating as expected for the installer - should any user wish to use a remote server as their source media.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.