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.
[EDIT] forgot to mention the kernel in the installer image and kernel packages uses a 16k PAGESIZE for additional performance. I've been testing and running it over the last few days and it's stunning, like a young Burt Reynolds!
Last edited by Exaga; 12-25-2023 at 02:26 PM.
Reason: ho ho ho!
Did Santa get Exaga rpi5 to resolve the issue going on here? I didn't see you say "that doesn't happen with my rpi5 install".
Merry Christmas gloryspitz!
Approx. 4-5 days ago I received an email from ThePiHut informing me that "your order has been dispatched" and the Raspberry Pi 5 arrived the very next morning, which was a total surprise with Christmas post and everything. I believed that it wouldn't be arriving until well after the New Year, from the ETA I was previously given. All credit to them for doing a fantastic job!
You didn't see me say "that doesn't happen with my rpi5 install" on that thread because it didn't, is why.
I wanted to get the SARPi5 batch built and tested thoroughly before getting involved with any other concerns. I built several kernels and was in the throes of testing them when I saw that post, so was a little busy with my own shizzle tbh. Plus I knew that SARPi5 batch from October 2023 was due to be replaced when testing was complete.
Last edited by Exaga; 12-25-2023 at 08:35 AM.
Reason: typo, induced by Jack Daniels
Merry Christmas Exaga & all! For Christmas i received in my mailbox (not a rpi5 but) a rpi2b Will test Slackware ARM 15.0 on it.
Speaking about your last batch Exaga, so the installer is working now on rpi5? Will make a test tomorrow. Great work and thank you!
Merry Christmas Exaga & all! For Christmas i received in my mailbox (not a rpi5 but) a rpi2b Will test Slackware ARM 15.0 on it.
Speaking about your last batch Exaga, so the installer is working now on rpi5? Will make a test tomorrow. Great work and thank you!
Merry Christmas dodoLQ hope you're having a lovely day!
The last installer did work but I had to take a lot of entries out of the config.txt file for some reason. It wasn't finding or loading the initrd with standard settings and that was weird. Not sure what was causing it, but I used a bare minimum config to boot with and that worked. After that, I installed Slackware AArch64 and ran a SARPi5 build. It all went pretty much OK. Testing and playing around with the OS was the best it's ever been IMHO. Really great fun!
The latest SARPi5 installer and pkgs work as expected. Hope it helps people until the RPi5 can be officially supported <hint hint>
Merry Christmas to everyone! @Exaga, thanks for the update, just the sort of thing I've been wanting to hear... Cheers!
Merry Christmas netcrawl.
No worries and you is welcome. Blame those who subscribed to The MagPi Magazine which pushed me back in the queue for an earlier delivery of the RPi5
Expect Slackware AArch64 to run at least 3x as quick on the RPi5 as it did on the RPi4. I was so amazed by its speed that I checked 3-4 times to make sure something hadn't gone wrong with the system, or that my grasp of the real-time continuum hadn't been compromised. HAHAHA!
Honestly, it's goddam awesome. This is one reason why I love Slackware so much. It never ceases to amaze me. <3
Honestly, it's goddam awesome. This is one reason why I love Slackware so much. It never ceases to amaze me. <3
Strong recommendation! lol I guess I should check my local retailer about availability... Last time I checked the boards weren't expected to be shipped until mid-Jan., and the custom cases and coolers etc., sometime towards the end of Feb..
Strong recommendation! lol I guess I should check my local retailer about availability... Last time I checked the boards weren't expected to be shipped until mid-Jan., and the custom cases and coolers etc., sometime towards the end of Feb..
Agreed. Availability can be problematic, as it always seems to be with this family of ARM devices. I've considered myself to be quite fortunate with the RPi4 and RPi5, not to have waited +6 months as I did for the first Raspberry Pi to be delivered after ordering it.
With regards to suitable cases and coolers, I've done a whole load of investigation and research. Unfortunately, and I know this should come as no surprise but, the reality of the RPi5's thermodynamics is not entirely in-line with the official advertising/marketing pitch, or most user reviews/blogs/videos and personal opinions, that I've viewed on the Internet. Rather than go into detail here, I've done a RPi5 review on the SARPi website that you may find helpful, which includes my forthright opinion(s) on the official Raspberry Pi 5 case and Active Cooler, and actively managed fan control firmware.
When all is said and done, the Raspberry Pi 5 is more than adequate and suitable for running Slackware, and that's mainly what I'm interested in. It may not be as blisteringly fast or capable as the Rock 5 model B (or comparable in price to a refurbished Intel i7 Mini PC - LOL WTF?!?!) or an Orange Pi 5 Plus (that's at least twice the price of the RPi5) but it's certainly much better supported on the software side of things.
For me personally, in terms of price vs features vs performance, the Raspberry Pi 5 is one of the more attractive and affordable alternatives available. I just want to run Slackware and I don't need power that's relative to a coronal mass ejection in order to do that. Although it would certainly be nice, if I could justify the expenditure involved.
Last edited by Exaga; 12-26-2023 at 03:21 AM.
Reason: Crunchy peanut butter on toast is the breakfast of Kings!
Wowie Installed successfully via NFS (exported assets) Slackwareaarch64-current via Exaga's sarpi project! It was fast and that rpi5 is a blast!! After installation, booting takes only 2 or 3s /o\ But i installed the system on a nvme ssd drive via an usb3-2-nvme adapter. I ordered a pimoroni nvme base for better perfs i think via the PCIe socket!
Now what i want to do is to use an external rtc module on the pi5, but that don't work..
Now what i want to do is to use an external rtc module on the pi5, but that don't work..
Code:
dtparam=i2c_arm=on
dtoverlay=i2c-rtc,ds3231
don't have effect. Maybe Exaga has a tip?!
You don't need to install a RTC because the RPi5 has one built-in. It's a DS1307 based RTC going by the documentation and modules loaded. Incidentally, I do not have either of the config.txt parameters enabled that you've listed above and yet the on-board RTC and hwclock command seems to work fine.
Code:
root@iana:~# hwclock -v
hwclock from util-linux 2.39.3
System Time: 1703617277.662116
Trying to open: /dev/rtc0
Using the rtc interface to the clock.
Last drift adjustment done at 1703616497 seconds after 1969
Last calibration done at 1703616497 seconds after 1969
Hardware clock is on local time
Assuming hardware clock is kept in local time.
Waiting for clock tick...
ioctl(3, RTC_UIE_ON, 0): Invalid argument
Waiting in loop for time from /dev/rtc0 to change
...got clock tick
Time read from Hardware Clock: 2023/12/26 19:01:18
Hw clock time : 2023/12/26 19:01:18 = 1703617278 seconds since 1969
Time since last adjustment is 781 seconds
Calculated Hardware Clock drift is 0.000000 seconds
2023-12-26 19:01:17.648730+00:00
to try and track the modules through the kernel's symbol table, but good luck with that because it got me nowhere. If you do find anything out please let me know.
shows nothing so... I really do not know yet how the RTC is configured and works with the system. I dug around for 20-30 minutes trying to work it out but it seems the RPi Foundation are keeping their propietary intellectual property under wraps for now.
However, the onboard RTC works as expected so I'm just using that.
Wowie Installed successfully via NFS (exported assets) Slackwareaarch64-current via Exaga's sarpi project! It was fast and that rpi5 is a blast!! After installation, booting takes only 2 or 3s /o\ But i installed the system on a nvme ssd drive via an usb3-2-nvme adapter. I ordered a pimoroni nvme base for better perfs i think via the PCIe socket!
Glad you found that Slackware AArch64 on the Raspberry 5 is super amazing. I'm so happy I'm not alone anymore in realising and experiencing this! THANK YOU <3
Be on the look out for any software that crashes or gives any errors. You are using a 16k pagesize with that SARPi5 kernel. I've tried finding issues but so far Slackware seems to love everything I do with it under this configuration. Truly wonderful and a testament to the Slackware Team for doing such a fine job with it. Thanks very much guys.
MERRY CHRISTMAS!
Last edited by Exaga; 12-26-2023 at 01:39 PM.
Reason: pagesize not pagefile DOH!
Wowie Installed successfully via NFS (exported assets) Slackwareaarch64-current via Exaga's sarpi project! It was fast and that rpi5 is a blast!! After installation, booting takes only 2 or 3s /o\ But i installed the system on a nvme ssd drive via an usb3-2-nvme adapter. I ordered a pimoroni nvme base for better perfs i think via the PCIe socket!
Now what i want to do is to use an external rtc module on the pi5, but that don't work..
Code:
dtparam=i2c_arm=on
dtoverlay=i2c-rtc,ds3231
don't have effect. Maybe Exaga has a tip?!
In your /boot/config.txt file add this:
Code:
dtparam=rtc=off
That will turn off the internal RTC and avoid any conflict between /dev/rtc | /dev/rtc0 | /dev/rtc1 | etc.
Install and configure your own external RTC module as normal after that.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Merry Christmas
