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.
The NVidia fixes have actually been fixed for some time - since about 6.5.6 or thereabouts IIRC. Up until this latest update, the previous newest kernel for slarm64 was 6.5.2, which worked except that it broke TV reception due to the NVidia fix!
Well I, for one still seem to have that 6.5.2 source. I know sndwvs just keeps current online. Couldn't you get patches from kernel.org to bring 6.5.2 up to or past 6.5.6 where the Nvidia fixes were fixed without crossing into 6.6.x?
Last edited by business_kid; 01-30-2024 at 01:43 PM.
The 6.7.8 kernel version puked. X never came up, and reboot with a 3 fingered salute was unreliable. But the 6.7.9 version works on sdcard. It seems to be slackware-like. It should have a one-line <something>-version file with the release name & number as install scripts often check that. But it has alsa, not pulse, and no systemd. I could live with. I was surprised to see runlevel 2. Are you switching over to irradium, or doing both? I can appreciate that you're a free agent.
slackware for the aarch64 architecture already exists, so it is no longer necessary to further support the full slarm64 distribution, but I also need the riscv64 architecture, so the choice fell on the same lightweight source base distribution crux, on which I built irradium for both architectures aarch64, riscv64, and added a binary package manager with simple management and subscription packages.
Well, your install images were certainly handier than all the palaver with installing Slackware Arm. You also took a more pragmatic approach to porting to the SBC, and are issuing 2 binary images in 2 days indicates you're a developer who is on the ball.
I have your 6.5.2 slackware image for the moment. When/if that goes past it's 'best before' date, I'll have to choose between suffering the Slackware Arm devs or learning crux/irradium/whatever.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
