Release: Slackware 15.0 release candidate 2, ARM 32bit
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.
Nice work Dr Mozes! Have a question to Exaga: in the latest changelog of SA-current, does your recent packages(installer, kernel-5.15.5, etc) need a rebuild or remains ok for installing SARPi? Hope you'll understand
Nice work Dr Mozes! Have a question to Exaga: in the latest changelog of SA-current, does your recent packages(installer, kernel-5.15.5, etc) need a rebuild or remains ok for installing SARPi? Hope you'll understand
I was thinking the same thing. So, yesterday I tested with 'slackpkg upgrade-all' on a Raspberry Pi 4 running Slackware ARM 15 release candidate 1 and installed all the new Slackware ARM 15 release candidate 2 packages via that method. It took some time (approx. an hour) but the entire upgrade process was very smooth (zero errors) and the system runs great as a result. No reinstall required. Right now I am upgrading the SARPi build machines with the new software packages.
However, that being said and to ensure everything is up-to-date and accurate, I will be rebuilding the SARPi installers and packages so that they are fully in-line with Stuart's latest Slackware ARM -current OS release. Either later today or tomorrow I'll upload the new batch - still running kernel 5.15.5 version.
I've upgraded both SlackwareARM and the Sarpi kernel packages on my RPi4.
Thanks for those upgrades, drmozes and exaga!
Most things I use are working as expected, but I've seen odd behaviour around browsers that I don't understand and wonder if anybody else is seeing them. I'm running Xfce.
What I had installed before yesterday:
- SlackwareARM from the previous update (from Nov 9)
- Sarpi kernel packages for 5.15.1
Behaviour:
- Firefox worked normally
- If I opened Konqueror and tried to navigate to a website, Firefox would launch and the website open there while Konqueror would stay open on a blank page
- Falkon would display a long line of text in the address bar and wouldn't open any websites, starting with the following (I can post the complete text if you want):
After upgrading today to the latest SlackwareARM 15.0 rc2 packages and Sarpi kernel packages for 5.15.5:
- Falkon behaves as before
- Konqueror looks like it's behaving as before, but doesn't call Firefox to open... I'm guessing that's related to the next point
- Firefox doesn't launch from the webbrowser icon on the bottom panel or the Application menu FF icon. If I try from the command line, I get this:
Code:
bash-5.1# firefox
XPCOMGlueLoad error for file /usr/lib/firefox/libxul.so:
libvpx.so.6: cannot open shared object file: No such file or directory
Couldn't load XPCOM.
and /usr/lib/firefox/ contains
Code:
bash-5.1$ ls -l
total 129464
-rw-r--r-- 1 root root 536 Mar 15 2021 application.ini
drwxr-xr-x 4 root root 4096 Mar 16 2021 browser
drwxr-xr-x 3 root root 4096 Mar 16 2021 defaults
-rw-r--r-- 1 root root 72 Mar 16 2021 dependentlibs.list
lrwxrwxrwx 1 root root 11 Mar 18 2021 firefox -> firefox-bin
-rwxr-xr-x 1 root root 551768 Mar 16 2021 firefox-bin
drwxr-xr-x 2 root root 4096 Mar 16 2021 fonts
drwxr-xr-x 3 root root 4096 Mar 16 2021 gmp-clearkey
drwxr-xr-x 2 root root 4096 Mar 16 2021 gtk2
-rwxr-xr-x 1 root root 30552 Mar 16 2021 liblgpllibs.so
-rwxr-xr-x 1 root root 211772 Mar 16 2021 libmozavcodec.so
-rwxr-xr-x 1 root root 178292 Mar 16 2021 libmozavutil.so
-rwxr-xr-x 1 root root 5684 Mar 16 2021 libmozgtk.so
-rwxr-xr-x 1 root root 891924 Mar 16 2021 libmozsqlite3.so
-rwxr-xr-x 1 root root 9824 Mar 16 2021 libmozwayland.so
-rwxr-xr-x 1 root root 108247708 Mar 16 2021 libxul.so
-rw-r--r-- 1 root root 21282603 Mar 16 2021 omni.ja
-rwxr-xr-x 1 root root 560024 Mar 16 2021 pingsender
-rw-r--r-- 1 root root 164 Mar 16 2021 platform.ini
-rwxr-xr-x 1 root root 547640 Mar 16 2021 plugin-container
-rw-r--r-- 1 root root 0 Mar 16 2021 removed-files
Is anyone else seeing this? Any clues on how to fix it?
Originally posted in Lynx browser in SlackwareARM on my RPi4.
Edited in ungoogled-Chromium (thanks, AlienBob!) on my x86_64 desktop.
Thanks,
TKS
EDIT: Or is it finally the end for FF on SlackwareARM 32 bit, as foreseen in the changelog of May 10
Code:
xap/mozilla-firefox-78.8.0esr-arm-2.txz: Removed.
The latest version of Firefox does not build on 32bit ARM.
...
pasture/mozilla-firefox-78.8.0esr-arm-2.txz: Added.
This is the last working build of the v78 ESR release and (presently) still
runs.
If so, all the more reason to be excited about the upcoming Slackware AArch64, as per the same changelog
Code:
For those of you who were using Slackware ARM as a desktop, the good news is that
the latest Firefox is available on Slackware AArch64, so you can switch to that if your
machine is 64bit capable (and supported) once Slackware AArch64 is publicly available.
Tested Current days ago, no Firefox and SeaMonkey. Then tested Konqueror, it was a no go!
From the change log:
Mon May 10 08:08:08 UTC 2021
xap/mozilla-firefox-78.8.0esr-arm-2.txz: Removed.
The latest version of Firefox does not build on 32bit ARM.
All of the other distributions stopped supporting Firefox on ARM years ago,
and I've spent countless hours through the years, cajoling Mozilla suite into
a good mood; and now it's time to part ways.
For those of you who were using Slackware ARM as a desktop, the good news is
that the latest Firefox is available on Slackware AArch64, so you can switch
to that if your machine is 64bit capable (and supported) once Slackware
AArch64 is publicly available
Wed Nov 18 08:08:08 UTC 2020
xap/seamonkey-2.53.3-arm-1.txz: Removed.
I've spent enough time on this package and haven't been able to get it building.
As we already have a browser, there's no justification to spend more time here.
If anybody fixes it, send me a diff to the Slackware/x86 SlackBuild and I'll
add it back!
Good News! Slarm64 has both and they work very good!!
I was using 5.15.5 kernel & etc., ran "slackpkg upgrade-all" and Slackware rc2 is running just fine. Firefox choked loading libvpx.so.6 so I symlinked it to libvpx.so.7 and Firefox boots/runs normally. Not a recommended hack, but it works for a test run.
Other than that, all's well on my Pi4.
Last edited by netcrawl; 11-30-2021 at 03:25 PM.
Reason: verbiage...
I was using 5.15.5 kernel & etc., ran "slackpkg upgrade-all" and Slackware rc2 is running just fine. Firefox choked loading libvpx.so.6 so I symlinked it to libvpx.so.7 and Firefox boots/runs normally. Not a recommended hack, but it works for a test run.
Other than that, all's well on my Pi4.
netcrawl, thank you! Symlinking libvpx.so.6 to libvps.so.7 worked to get FF opening for me again.
It may be a non-recommended hack, maybe even reckless, but I'll use it for non-critical browsing.
I've upgraded both SlackwareARM and the Sarpi kernel packages on my RPi4.
Slackware ARM 15.0 rc2 seems to be working perfectly for me on all RPis but I do not use the desktop, just CLI. So far I can't fault it.
I rebuilt all the SARPi shizzle and uploaded it. The installer images include Stuart's latest initrd-armv7.img as I used that to build the initrd.gz which includes his Slackware ARM OS installer. They work perfectly to get Slackware ARM 15.0 rc2 installed but users still need to 'reboot -f' once setup is complete on the RPis. I really need to find time to look into the power modules as Stuart advises.
At the moment I'm really enjoying using it and each day is another step closer to release.
Tested Current days ago, no Firefox and SeaMonkey. Then tested Konqueror, it was a no go!
Browsers on 32bit ARM aren't in good shape and given how slow 32bit machines are running desktops, I don't see the point in using 32bit ARM for anything other than headless machines - particularly with Slackware AArch64 coming soon.
The Mozilla suite works fine on Slackware AArch64 because they're maintained for 64bit architecture.
Are you saying that the Firefox in pasture no longer works either? I'll remove it if that's the case.
Propping it up with some hacks isn't considered 'working' for me.
Are you saying that the Firefox in pasture no longer works either? I'll remove it if that's the case.
Propping it up with some hacks isn't considered 'working' for me.
drmozes, I can confirm that FF 78.8.0esr in pasture no longer works for me as is, and in any case is out of date (and you mentioned in the changelog that newer versions won’t build.) I can force it to run only with a hack, so I agree that I can’t call it working. Undead, maybe?
Falkon and Konqueror also don’t work as installed, but I haven’t done anything to dig into why or how to fix them, and not sure I have the knowledge to do so outside of internet searching.
Lynx, on the other hand, works fine.
Quote:
Originally Posted by drmozes
given how slow 32bit machines are running desktops, I don't see the point in using 32bit ARM for anything other than headless machines - particularly with Slackware AArch64 coming soon.
The Raspberry Pi 4 4GB is surprisingly (to me) peppy on SlackwareARM with a midweight DE like Xfce with a few applications running - a couple of files in kate, a couple of terminal windows, a couple of instances of Thunar, Arduino IDE with serial window open and an Arduino Uno or ESP32 board connected, and Firefox with a few tabs open for basic browsing doesn’t seem to tax it. In FF, videos can bog down and pages with lots of video or even high res graphics can be slow to load.
I haven’t tried to run harder than that, so no idea what load would make it practically unusable.
It’s no match for Slackware64 on my reasonably powered x86_64 desktop box, of course.
Once Slackware 15.0 AArch64 arrives, though, SlackwareARM -current will be gone as soon as I can get AArch64 installed.
drmozes, I can confirm that FF 78.8.0esr in pasture no longer works for me as is, and in any case is out of date (and you mentioned in the changelog that newer versions won’t build.) I can force it to run only with a hack, so I agree that I can’t call it working. Undead, maybe?
Thanks, it's gone.
Quote:
Falkon and Konqueror also don’t work as installed, but I haven’t done anything to dig into why or how to fix them, and not sure I have the knowledge to do so outside of internet searching.
There's just been an upgrade to KDE so I'll have a look soon.
Quote:
Once Slackware 15.0 AArch64 arrives, though, SlackwareARM -current will be gone as soon as I can get AArch64 installed.
It has occurred to me that 15.0 might be the last release of 32bit ARM, but the hardware is reliable so I'll see what I do there.
The Raspberry Pi 4 4GB is surprisingly (to me) peppy on SlackwareARM
Not that Slackware ARM was ever sluggish IMHO, but for at least the last 2 years on the Raspberry Pi 4 the speed/responsiveness/vibrance of the -current operating system has become progressively more outstanding. That will surely translate to the 64-bit architecture.
Quote:
Originally Posted by TheTKS
Once Slackware 15.0 AArch64 arrives, though, SlackwareARM -current will be gone as soon as I can get AArch64 installed.
I'll run Slackware AArch64 as a main system for sure. I'll keep the Slackware ARM 15.0 build systems going for sarpi reasons for as long as Stuart wants to keep maintaining the OS.
Quote:
Originally Posted by drmozes
It has occurred to me that 15.0 might be the last release of 32bit ARM, but the hardware is reliable so I'll see what I do there.
I'd wager, when the time comes for you to make that decision there'll be no manufacturers producing 32-bit-only ARM devices without 64-bit capabilities. Technology is moving forward at a rapid pace.
Please do not shelve support for Pi 1, have five running SlackwareArm32 14.2. Got them working on equipment. Best ever!
The last time I built a sarpi installer for the Raspberry Pi (1) was on 14 March 2021 using kernel 5.10.22 version. Then I powered the device down and did not intend to use it again for building any binaries. Or any other purpose for that matter.
Out of curiosity I powered the RPi (1) back up yesterday evening and started a batch build using kernel 5.15.5 - to determine how long it would take. So far, it's been running for approx. 9 hours and hasn't built the kernel yet - which is the first item in the list. Compare that to the RPi2, 3, and 4 - all these devices would have built a full batch of files in that time, with hours to spare.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
