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, very odd! The packages themselves seem to be pretty up-to-date, its just the support files required by slackpkg that aren't being picked up! I've let Darren know!
What is the difference between your kernels and stock slarm64 ones? I did boot my Pi with the stock kernel successfully, although I'm not sure if everything works. In particular, the colourful boot screen is missing.
I was feeling disloyal running Raspberry Pi OS (=Debian Buster). I avoided the initial spade work of setting up the Slackware distro, but excused myself on the basis of being an invalid, and RazPi setup was handy, I have to admit.
Now RazPi OS (formerly raspbian) have dropped Debian 10 (Buster) and dropped all updates. They have released bullseye or debian 11, and apparently there's no end of problems, see post #4 particularly.
Downloading the 64bit Slackware version as I speak. The one thing I'd mention is that Alien Bob's [x86_64] chromium-ungoogled Version 94.0.4606.81 (Official Build, ungoogled-chromium) (64-bit) pukes on the link; If I do a 'file/save as,' I get the error
Code:
support.9oo91e.qjz9zk is blocked
This page has been blocked by Chromium
ERR_BLOCKED_BY_CLIENT
I got it by copying the link to a word processor, and pasting it into a terminal preceded by the magic word "wget" .
Last edited by business_kid; 11-30-2021 at 02:38 PM.
Installed that RazPi 4 20211128-xfce image, and it's not booting.
Apparently it does the initial stuff fine, remounts mounting on /mnt read only, boots, moves the / partition from /mnt to /, but doesn't mount it read write, so the thing runs init, but every write to / fails. That inevitably ends sadly, a reset in this case. Then we loop again, … and again…
I tried it on a real usb disk (/=sda2), and an sdcard (/=mmcblk0p2) - both the same.
Raspberry Pi OS save bootup bother by not having uEnv.txt. The cmdline.txt & /etc/fstab both have "root=PARTUUID=<number>. When you install an image, it's the partuuid of the disk the image was made on, I suppose. You could save bother for end users that way. I personally don't like partuuids, but I detest farting about.
The cmdline.txt & /etc/fstab both have "root=PARTUUID=<number>. When you install an image, it's the partuuid of the disk the image was made on, I suppose. You could save bother for end users that way. I personally don't like partuuids, but I detest farting about.
Use "PARTUUID" in the '/boot/cmdline.txt' file and "UUID" in the '/etc/fstab' file on the RPi devices. Works perfectly for Slackware ARM, not sure about anything else.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
.
