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.
I wasn't paying attention to all that came with my rpi4 kit, that power switch thingy is cool.
The reason for the in-line power switch is mainly down to prior experience from constantly powering on/off the Raspberry Pi devices (i.e. repeatedly unpluging and re-connecting the power jack to the 5v sockets an untold number of times on a frequent basis).
With the micro-USB power socket, on all previous models to the Raspberry Pi 4, I found that over years of frequent use, if I had not been gentle and careful enough when connecting and disconnecting the PSU plug, the power socket became stretched and the plug was not a snug fit once it was seated. Not that this caused any real problems with power but I wanted to eliminate the risk of any such faults happenning. The USB-C connector on the Raspberry Pi 4 seems to be a little more robust and may stand the test of time, but I didn't want to encourage any similar issues arising with it.
These in-line power switches are perfect for the job and can stay connected permanently. I use them for both the micro-USB and USB-C sockets on the Raspberry Pi devices nowadays. The Raspberry Pi 4 on the far left of the image ("kron") doesn't feature an in-line power switch because that's the Slackware ARM current Apache server/NTP server system running from a SSD which stays active 24/7.
Last edited by Exaga; 06-02-2021 at 03:13 AM.
Reason: yes
With the micro-USB power socket, on all previous models to the Raspberry Pi 4, I found that over years of frequent use, if I had not been gentle and careful enough when connecting and disconnecting the PSU plug, the power socket became stretched and the plug was not a snug fit once it was seated. Not that this caused any real problems with power
I had the same problem and ended up taping the power cable onto the case to keep it securely seated.
You can also get these type of power strips with individual controls for each socket, which is what I now use.
I had the same problem and ended up taping the power cable onto the case to keep it securely seated.
You can also get these type of power strips with individual controls for each socket, which is what I now use.
I have... (Hmmm, I think we have discussed this in detail in the past...) a power extension like the one in your pic but it has 4x 4Amp USB sockets built-in which I power the SARPi build machines from. Additionally, there's 6x 3-pin 13Amp power sockets with individual on/off switching for PSUs and other power cables, etc.
I have an installation of Slackware Aarch64-current running on the Raspberry Pi 4.
I used the mainline kernel, dtbs, modules and firmware that come with Slackware. No need to (re)compile a kernel anymore. I did use the raspberry pi firmware for /boot from GitHub.
Next steps will be to fill in the blanks in the platform script within the initrd. Then adjust the installer to accommodate minor changes.
I've been running slarm64-current on the pinebook pro with LUKS+LVM.
To do that, I started with sndwvs' microsd as a base, from which I built custom kernel and then installed on internal eMMC.
The only reason I built a custom kernel and deviated from our community's build was due to the following note on custom kernels in slackware's README_CRYPT.TXT file:
Quote:
A note on custom kernels
------------------------
If you want to compile your own custom kernel to work with LUKS encrypted
partitions, you need to enable at least the following two options in your
kernel configuration:
Multiple devices driver support (RAID and LVM) --->
<*> Device mapper support
<*> Crypt target support
This is equivalent to the following options in your .config file:
CONFIG_BLK_DEV_DM=y
CONFIG_DM_CRYPT=y
Do not compile these as module! They are required in your kernel.
The kernel shipped with the pinebook pro image shared at the pine64 forum, had those two kernel options configured as modules. Those were the only changes to the kernel configuration I made.
The LUKS works, but the key has to be entered in the dark (the display hasn't lit up yet, even though it's at the prompt). Just another level of stealth
I mention it here in case those revisions want to be included.
--cheers
Last edited by slac-in-the-box; 06-18-2021 at 05:48 PM.
Reason: added the -current
Any update on this ?
The slackwareaarch64-current/ folder vanished from arm.slackware.com !
I wouldn't be too concerned at this point. MoZes is not known for releasing anything that's less than perfect as possible, if not 100% perfect in all aspects. Just hang on in there and keep your eyes peeled.
Quote:
Originally Posted by pchristy
Its vanished from Slackware.uk too!
Slackware.uk mirrors arm.slackware.com so if it's missing from the main repository then it's not at all surprising.
I'm not unduly worried! The "missing" folders didn't seem to have anything like a full system, so I assumed the were just "holding" pending being filled.
The fact they have disappeared may actually be good news! Maybe he's filling them up on his local server prior to releasing? Either way, I'm sure he'll be along in a while with an update for those of us chomping at the bit!
In the meantime, Slarm64 is doing sterling service!
Thanks Brent. I've added libahci ahci sdhci sdhci_pltfm roles to the main loader script for all Hardware Models.
'drm' is already loaded so you don't need that one.
For the others, you could move them into the rpi4 loader script and I'll include them within the next build.
I will be able to test it this weekend. I have a NAS case and miscellaneous coming in the mail. Yes, I am just now getting a proper case for the RockPro64.
I will be able to test it this weekend. I have a NAS case and miscellaneous coming in the mail. Yes, I am just now getting a proper case for the RockPro64.
Ok, I've merged those modules in. I've also made os-initrd-mgr handle /etc/mdadm.conf.
You bought the big black case? I like those ones.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
