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 see the new images dated 20230910, but I'm not in the least tempted because as of 20230909(yesterday) current is broken. VLC won't play some mkvs or any mp4s. I have reverted to my backup of last May, and everything's fine. The same VLC, Libx264 & libx265 play those problem Videos fine. MPV & ffplay both played problem videos fine, and Slackwareaarch64 had the same issue, but sorted itself out in the last few days.
I don't have the packages from last May. I will henceforth hold a package snapshot of working current packages. I do have the current ones. So if you guys can give me a short list of suspects I can upgrade them one at a time & finger the offending package.
I posted the previous message on 20230910, but then noticed you had added some updates on the 20230910.
So I updated to the new image eventually and added vlc, x264, & x265. I could only get root on the sdcard as I couldn't set a user password, either in your script or with commands. But cvlc is playing the offending mp4s and mkvs so it is incumbent on me to grovel, apologise, and do whatever polite people do in such circumstances. VLC won't start but it's bellyaching about the outdated cache in another homedir. I'll try it as a luser as soon as I can get in as a luser.
I did have my usual song & dance with the screen size. I started out editing your config.txt, but that didn't sort it. What did sort the screen size was copying over my existing config.txt from the old install and editing that for the new kernel. So it seems the order in that config.txt is important here anyway. It's all on an sdcard still, and everything works fine where I am (on the August image).
What firmware version are you running on your RazPi(s)??
I don't want to update - no thank you. Didn't they make a pass at uefi?
I have firmware (2019?) where you can boot off usb, you can overclock the gpu (not that I'm bothered), and you don't have uefi, or any attempt at it. The RazPi is quite messy enough to boot without adding firmware to stop you booting! Is there anything I'm missing?
I'm mirroring current with ftp from slackware.uk ATM and I'll run a mass upgradepkg on that sdcard and test it before moving over. mmcblk0p2 is now a 31G ext4 partition. I logged into a tty as root, which triggered your 'adduser' script. But although I can apparently set the user password as root, I can't log in to XFCE as a user. Is my user disabled or expired or something? I tried as well from an X terminal as root, but no joy.
Last edited by business_kid; 09-16-2023 at 12:05 PM.
Excellent! The last kernel update (6.5.2) broke my TV-hat because of the "fixes" the kernel developers applied to stop NVidia doing naughty things. They did get fixed in later releases, so hopefully I can get my slarm64 setup running again!
Well, that got them to install, but that's the end of the good news, I'm afraid. It now won't boot at all - indeed, its showing exactly the same symptoms as the Slackwareaarch64 Pi-fork kernels. On booting, the monitor comes out of standby, but there are no boot messages - the screen remains blank - and the keyboard is totally unresponsive. The only way out is to remove the power! I've tried both direct booting the image and u-boot.
Even Exaga over at Sarpi is reporting oddities with the 6.6+ kernels, though those do boot. Not sure what is going on. I thought these newer kernels were supposed to have better support for arm, but at present - at least on the Pies - that doesn't appear to be the case.
No criticism, you understand, just reporting what has happened, and perhaps warning others to beware!
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!
I think this is something more fundamental. Its interesting that Slackwareaarch64 is having an identical issue (won't boot with the 6.6 Pi-fork kernel) and that Exaga (Sarpi) has been having an issue with 6.6 too.
Exaga hasn't told me exactly what his issue is, my system still boots and runs, though it doesn't seem 100% stable and he has been issuing updated kernels almost every other day.
If push comes to shove, I can boot Sarpi, then chroot into slarm64 and revert the update. However I'm inclined to give the developers some time to find the problem and fix it first.
I'm not complaining, BTW, but if the developers aren't made aware, they aren't going to fix it!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
VLC won't start but it's bellyaching about the outdated cache in another homedir. I'll try it as a luser as soon as I can get in as a luser.
