Hello

Slackware ARM -current updates are now out. It's a world rebuild and upgrade.
Given some of the reports for x86 about the amount of time taken to upgrade, you may find it faster to reinstall from scratch.

There are some more KDE packages coming soon too.

One issue I noticed is that the emacsspeak package hasn't built properly. I have investigated and can't figure it out yet. I managed to get some components of it to build, but I suspect the issue is outside of the emacsspeak package.
If anyone figures it out, let me know!

Any other issues, please reply to this thread.

THANKS!!!!!!!!!!!!

AWESOME <3

Thanks for the hard work!

1 members found this post helpful.

Hi Stuart,

Thanks for the updates. I managed to install everything using slackpkg by moving the sd card from my chromebook to a PC, mounting it under /mnt/tmp, specyfying custom ROOT variable and bind-mounting the /mnt/tmp/etc/slackpkg directory to /etc/slackpkg. This made things a lot quicker.

I understand this is a non-standard update procedure and it did cause a problem causing essential links from glibc package not being created under /lib, but I was able to fix that by reinstalling glibc using another working arm installation on the target chromebook.
Not 100% sure it hasn't caused any other issues, but I haven't found anything else yet.

I noticed two bugs so far - one is the breeze package being removed - probably by accident, as this is not documented in changelog. That causes background not being displayed in sddm and I can imagine may cause problems with walpapers, cursors and such not being present.
The other is the slackpkg mirrors.new file that contains x86 mirrors rather than arm specific ones. Of course one can simply remove the *.new file and use the old version and that is what I did.

There is another question I wanted to ask which is not related to the last update, but I noticed the vboot-utils package was removed back in December. What is the reason? Is there a replacement? I was able to find the old one on the internet but this will become unavailable once all the mirrors are updated ;-) and needed some library link creation.

Regards,
Alex

After a full re-install of Slackware ARM current, the first time I configured slackpkg and 'nano -w /etc/slackpkg/mirrors' I get this...

Which is expected. What exactly did you do to receive the x86 mirrors file? Did you do a full upgrade by installing the entire pkg-tree?

Seems my upgrade method causes more problems than anticipated ;-) All done as described in my post. But when I do indeed the replacement file is correct.

I better restore my system from backup and do a proper upgrade before reporting more issues...
Sorry guys for false alarm!

Exactly - that's one of the issues you'll encounter. I'm running Slackware-AArch64 that was installed using that method (without slackpkg) on an x86, and ran ldconfig on an ARM box to create the cache.

Some packages won't be set up properly because they run post-installation scripts.

The breeze-grub package is missing by design, but not the base package. There's a newer version in the queue so i'll see that one gets built.

Because the package was purely for my own experimentation with my old Chromebook. I got it working but it was too much of a hardware faff to document as anything close to being user-friendly and 'supportable'. I'm not going to make the Chromebook supported by Slackware ARM, so I removed the package as it was surplus to requirements. Were you using it?
Given you mention Chromebook, I guess you were. I can add it back if you need it!

1 members found this post helpful.

I recently repurposed the system I installed on Raspberry Pi 3B+ by moving it to "veyron-minnie"(Asus C100PA) chromebook. I am using the package to create kernel partitions.
It all seems a bit over-complicated but it works. I am much happier with Slackware ARM performance on the Chromebook than on Pi and it does get actual use, whereas the Raspberry Pi install was just left aside unneeded.

If you can add the package back and if maintaining it is not too much work for you I would really appreciate it!

1 members found this post helpful.

Yes, thank you for all your hard work!

2 members found this post helpful.

It's no trouble for me. It'll be in the next batch.

2 members found this post helpful.

Great stuff! Thanks! :-)

Thank you, drmozes! The SlackwareARM update went smoothly on my RPi4 after last updating Feb 21.

I noticed only one oddity, qt5 related (no idea if this is of any consequence but notifying anyway): the first time I launched kate after updating SlackwareARM but before updating sarpi4 packages and SlackwareARM kernel-firmware, I got this error. The second and subsequent times launching kate went normally, and some time after that I verified that the file is there.

Thanks to you also, exaga. Smooth updating to the 17Mar21 sarpi4 packages after last updating to the 17Feb21 packages.

TKS

1 members found this post helpful.

The new Slackware ARM current is performing most impressively for me. No niggles or concerns yet. Doubt there will be any TBH.

You're welcome with regards to the SARPi shizzle. I put some work into making sure things were in alignment, especially with the [wireless] drivers and modules after the angst and woes of recent weeks past.

Same here

I noticed. I checked that wifi works without the extra steps needed in recent weeks, and that it switches seamlessly from ethernet to wifi and back when I pull the ethernet cable and then plug it back in.

TKS

1 members found this post helpful.

I made the update on a Pi Desktop with a small m-SATA disk, and it went smoothly.

a question: is there a manner to make multiboot on that kind of "beast"?