Raspberry Pi 4 bcm2711 / Raspberry Pi 3 bcm2837 (aarch64)
slarm64This forum is for the discussion of slarm64.
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.
I've been running Slarm64-15.0 here and letting -current go it's way. It's software rendering, and a Pi doesn't have the cpu for that. I run Zoom occasionally. The Linux-x86_64 version works under box64. That needs all the cpu, all the 4G of ram + 2G of swap. And I use the oldest Zoom version I can get away (5.10.7) because they're throwing extra features into Zoom like snuff at a wake.
These RK3588 based boards with 8 core cpus and a Mali GPU seem a better bet. I just can't justify it to myself. There's also a little server from solid-run.com based on an NXP 16 core Arm chip. It has a pcie slot, so will take an AMD/Radeon card running on kernel graphics. That's about €$750.
As for the video on the Pi: in this part of the world I can torrent stuff. I usually select 720p movies when I can get them. Laws don't protect companies over people anyhow. Torrent sites get closed down, or made inaccessible but the authorities here are not bothered about individual users. They have enough to be doing with major criminals. I have the VPN anyhow. The closing/banning is done by enforcing EU court orders. There's no court precedent on torrenting in Ireland AFAIK.
EDIT: In /opt/vc/bin (not in the $PATH) there's vcgencmd. I added it and the man pages to the respective paths and Debian was definitely using some GPU bit that Slarm64 is not. There's also an include dir in /opt/vc that looks like headers for some video driver. You can measure gpu clock frequencies for the various blocks. The people doing Asahi Linux are writing a driver based on the leaked mac headers but I don't think anybody will bother for the Pi. It's too puny.
Last edited by business_kid; 06-08-2023 at 05:35 AM.
I have this Pi 4 update featuring the 6.4.8 kernel, & glibc-2.37, and mirrored the current to disk yesterday.
Do you think I can run a major upgradepkg for an update and keep all my carefully crafted config files, or has too much changed in current since Slackware64-15.0 for that to be a feasible option?
Nobody is going to be held legally liable for guessing wrong, you'll just get a dishonourable mention in my bad tempered grumbles as I sort myself out .
Do you think I can run a major upgradepkg for an update and keep all my carefully crafted config files, or has too much changed in current since Slackware64-15.0 for that to be a feasible option?
should work fine, but you may need to install libraries
should work fine, but you may need to install libraries
I'll grep the ChangeLog for 'Added' & 'Removed' and my github stuff may all go south. But your repo is no use to me as is. I'll let you know how it all falls apart.
Just noticed kernel is 6.1.27, your image is 6.4.8. have you a package for that?
I'll grep the ChangeLog for 'Added' & 'Removed' and my github stuff may all go south. But your repo is no use to me as is. I'll let you know how it all falls apart.
Just noticed kernel is 6.1.27, your image is 6.4.8. have you a package for that?
Is it online? I only can find 6.1.27 on slackware.uk, and 6.1.45 on slarm64.org
I grepped the ChangeLog, which goes back to the year dot. When I trimmed it back to Slackware-15.0, there were 103 packages Added & 77 Removed. When you take python modules & the ever metamorphosing kde out of the picture, not much has happened!
Last edited by business_kid; 08-18-2023 at 06:29 AM.
OK, duly noted but your latest RPi image has kernel-6.4.8, and I was looking for that, as it may have been profiled for the rpi.
I'll probably extract the kernel & modules from the image as I'm having issues with the latest image on sdcard. There's always hassle here, as I can't run u-boot because of my tv/monitor, so I have to cobble things up, and I inevitably forget what I did last time. I also get negative vibes from my nearest & dearest if the RPi acts up and impinges on her recreation.
EDIT: The upgrade seems fairly good. I did a mass upgrade for the xfce distro version. I then cut the end of the ChangeLog at slackware-15.0 released. I did a grep for Removed, and did that. The grep for Added was different. I did an installpkg --no-overwrite 'l/python*.txz' ignored new stuff in d/, kde/, extra/, & testing/. Then I installed the rest.
There will be a few old packages compiled against new libs, which will fail for the lack of the old libs. I can find them with 'ls -lht' in /var/log/packages if any of them annoy me, and simply upgrade them.
Last edited by business_kid; 08-18-2023 at 01:36 PM.
Everything went well, although my dire predictions are usually accurate, a reboot restarted. I also found I had updated the 5 15.x kernel to 6.2.0. I know there's 6.4.8 there, but rule #1 of maintenance beckoned
Code:
If it works, don't fix it!
I'll grab the 6.4.8 kernel for the next time. It does well on 6.2.0.
Last edited by business_kid; 08-19-2023 at 03:52 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
.
