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.
Yes. It is working well. I put two 500G WD-Black SATA spinners in a RAID 1 configuration. The fan from Pine64 is more than adequate to keep temps down.
Quote:
Originally Posted by drmozes
Ok, I've merged those modules in. I've also made os-initrd-mgr handle /etc/mdadm.conf.
Thanks for the goodies. I hadn't tried to install Slackware with RAID yet.
For those interested: It took a while to translate the existing README_RAID.txt to be used with os-initrd-mgr + syslinux. It boots still... but I am being dropped to an ash shell where I have to restart the RAID array. After that I mount /mnt on the right disk, activated swap, and typed "exit".
Is anyone else getting excited by the news on arm.slackware.com regarding the latest developments on Slackware AArch64 and Stuart's call for testers on the Pinebook Pro & RockPro64?
It's moving ever closer to being completed, I can feel it.
Seems like this is slarm64 information and downloads, not the official Slackware AArch64 OS which MoZes is developing. So, it's not the same.
The information on this page you've referenced is a little confusing/misleading because it's titled "Slackware AArch64" but the filenames and download URLs are related to slarm64.
Seems like this is slarm64 information and downloads, not the official Slackware AArch64 OS which MoZes is developing. So, it's not the same.
The information on this page you've referenced is a little confusing/misleading because it's titled "Slackware AArch64" but the filenames and download URLs are related to slarm64.
ahh yeah, good point, its the unofficial, I forgot about that. I made an account on their wiki so I could see the page edits, it was added by pineadmin. I went ahead and changed AArch64 to Slarm64 and added notes about the differences.
ahh yeah, good point, its the unofficial, I forgot about that. I made an account on their wiki so I could see the page edits, it was added by pineadmin. I went ahead and changed AArch64 to Slarm64 and added notes about the differences.
Nicely done. Especially with mentioning the official Slackware AArch64 port that's currently in development, with a link back to LQ.
Like to add that I'm not trying to make any point. I'm just very aware that "Slackware" is Patrick's trademarked brand name and I'm fastidious about how I use it. What Stuart creates is bona fide Slackware and I try to be very careful in not giving the wrong information or impression with the SARPi software I build for the Raspberry Pi, which uses and is entirely based around his Slackware ARM installer. I still cannot call my work "Slackware" because, even though it amounts to the same end results and respects the Slackware brand, I do not have official permission to use the "Slackware" name to promote my own work. Nor would I attempt to do so, or expect that it would be acceptable if I did.
Slackware [ARM] comes with a reputation of the highest renown and acclaim. Patrick and the Slackware Team work very hard to maintain that level of excellence. These qualities and standards must be fully respected, and perpetuated indefinitely.
Last edited by Exaga; 11-15-2021 at 03:24 AM.
Reason: tpoy
I just wanted to make sure someone on here wasn't maintaining that RockPro page already and then figured this would be the best place to get info. I have a case almost done for my RockPro64 so hopefully I'll be right on time.
I just wanted to make sure someone on here wasn't maintaining that RockPro page already and then figured this would be the best place to get info. I have a case almost done for my RockPro64 so hopefully I'll be right on time.
It would be a very good idea to link arm.slackware.com on that page too. Seeing as the official Slackware AArch64 operating system supports the RockPro64 device. The more coverage the Slackware ARM/AArch64 project receives, the more interest it might generate, and the better it will be.
ok, added it. It could probably use some clean up and reformatting.
Sorting out that wiki page has been on my todo list for several months. I will move Slarm64 to its own section - it cannot be advertised under 'Slackware' and never should have been.
Quote:
If your interested, I'm making a low profile case, still working on it.
I wish I had your hand for making that type of stuff - all of my stuff looks more like the BTTF Delorean with wires everywhere like a mad scientist made it.
Unfortunately my Pinebook Pro broke yesterday - the LCD panel went bad and now it won't power on, so I cannot complete the installation docs, and even if they'll send me a new one, it took months for this one to arrive :-(
However, the installer and OS worked prior to that so perhaps I can work with someone else to finish the docs off.
Every time I think it's finished, I find some new tweak to add into the installer. I added the new 'Power off' feature at the end of the installer to handle the Pinebook Pro's occasional failure to boot after a reboot, and a new feature yesterday to offer to set the console= Kernel cmdline operator to combine all OS and Kernel output if you're running the installer from the Linux Virtual Consoles.
The core RockPro64 support is stable but needs sound and wifi support re-testing with Linux 5.15, so I will finish that in December.
I'm also not sure how to handle the fan within the OS (the installer will enable the fan but it's a simple script that's unsuitable for inclusion into the OS).
I had a look at some of the fan tools but didn't find anything that'd work out of the box with the RockPro64; but that's not a blocker to release.
Sorting out that wiki page has been on my todo list for several months. I will move Slarm64 to its own section - it cannot be advertised under 'Slackware' and never should have been.
Quote:
Originally Posted by drmozes
Unfortunately my Pinebook Pro broke yesterday - the LCD panel went bad and now it won't power on, so I cannot complete the installation docs, and even if they'll send me a new one, it took months for this one to arrive :-(
However, the installer and OS worked prior to that so perhaps I can work with someone else to finish the docs off.
Oh geez! You sure have had some awful luck with hardware lately.
Hope you manage to source a replacement quickly. Let me know if you need any bits and pieces.
Quote:
Originally Posted by drmozes
Every time I think it's finished, I find some new tweak to add into the installer. I added the new 'Power off' feature at the end of the installer to handle the Pinebook Pro's occasional failure to boot after a reboot, and a new feature yesterday to offer to set the console= Kernel cmdline operator to combine all OS and Kernel output if you're running the installer from the Linux Virtual Consoles.
Failure to 'reboot' with that command is also an issue using the SARPi installer on the Raspberry Pis. I've sometimes resorted to 'echo b > /proc/sysrq-trigger' to get the job done. You know I don't modify any of your work so hopefully this new feature might cure it. Hopefully.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.