LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - ARM
User Name
Password
Slackware - ARM This forum is for the discussion of Slackware ARM.

Notices


Reply
  Search this Thread
Old 03-16-2021, 01:19 PM   #1
drmozes
Slackware Contributor
 
Registered: Apr 2008
Location: Surrey, England
Distribution: Slackware
Posts: 1,036

Rep: Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850
Slackware ARM -current world rebuild is out!


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.
 
Old 03-16-2021, 01:24 PM   #2
Exaga
SARPi Maintainer
 
Registered: Nov 2012
Distribution: Slackware [ARM]
Posts: 639

Rep: Reputation: 375Reputation: 375Reputation: 375Reputation: 375
Quote:
Originally Posted by drmozes View Post
Hello

Slackware ARM -current updates are now out. It's a world rebuild and upgrade.
THANKS!!!!!!!!!!!!

AWESOME <3
 
Old 03-16-2021, 09:12 PM   #3
mralk3
Senior Member
 
Registered: May 2015
Distribution: Slackware, OpenBSD
Posts: 1,548

Rep: Reputation: 869Reputation: 869Reputation: 869Reputation: 869Reputation: 869Reputation: 869Reputation: 869
Thanks for the hard work!
 
1 members found this post helpful.
Old 03-16-2021, 11:41 PM   #4
alekow
Member
 
Registered: Sep 2009
Distribution: Slackware
Posts: 213

Rep: Reputation: 59
Quote:
Originally Posted by drmozes View Post
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.

(...)
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

Last edited by alekow; 03-17-2021 at 04:28 AM.
 
Old 03-17-2021, 12:36 PM   #5
Exaga
SARPi Maintainer
 
Registered: Nov 2012
Distribution: Slackware [ARM]
Posts: 639

Rep: Reputation: 375Reputation: 375Reputation: 375Reputation: 375
Quote:
Originally Posted by alekow View Post
I noticed two bugs so far ...
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.
After a full re-install of Slackware ARM current, the first time I configured slackpkg and 'nano -w /etc/slackpkg/mirrors' I get this...

Code:
#----------------------------------------------------------------
# Slackware ARM current: 32bit armv7, hardware floating point ABI.
#----------------------------------------------------------------
#http://slackware.uk/slackwarearm/slackwarearm-current/
#http://ftp.halifax.rwth-aachen.de/slackwarearm/slackwarearm-current/
#http://ftp.slackware.pl/pub/slackwarearm/slackwarearm-current/
#https://mirror.slackbuilds.org/slackwarearm/slackwarearm-current/
#https://slackware.absolutehosting.net/pub/slackwarearm/slackwarearm-current/
#
# Use this as the default if you don't know which to pick:
#http://ftp.arm.slackware.com/slackwarearm/slackwarearm-current/
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?
 
Old 03-17-2021, 01:05 PM   #6
alekow
Member
 
Registered: Sep 2009
Distribution: Slackware
Posts: 213

Rep: Reputation: 59
Seems my upgrade method causes more problems than anticipated ;-) All done as described in my post. But when I do
Code:
slackpkg reinstall slackpkg
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!
 
Old 03-17-2021, 01:46 PM   #7
drmozes
Slackware Contributor
 
Registered: Apr 2008
Location: Surrey, England
Distribution: Slackware
Posts: 1,036

Original Poster
Rep: Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850
Quote:
Originally Posted by alekow View Post
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.
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.

Quote:

Not 100% sure it hasn't caused any other issues, but I haven't found anything else yet.
Some packages won't be set up properly because they run post-installation scripts.

Quote:
I noticed two bugs so far - one is the breeze package being removed - probably by accident, as this is not documented in changelog.
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.

Quote:
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.
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!

Last edited by drmozes; 03-17-2021 at 02:11 PM. Reason: fixed quoting
 
1 members found this post helpful.
Old 03-17-2021, 02:33 PM   #8
alekow
Member
 
Registered: Sep 2009
Distribution: Slackware
Posts: 213

Rep: Reputation: 59
Quote:
Originally Posted by drmozes View Post
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!
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.
Old 03-17-2021, 07:29 PM   #9
glorsplitz
Member
 
Registered: Dec 2002
Distribution: slackware!
Posts: 878

Rep: Reputation: 199Reputation: 199
Yes, thank you for all your hard work!
 
2 members found this post helpful.
Old 03-18-2021, 05:05 AM   #10
drmozes
Slackware Contributor
 
Registered: Apr 2008
Location: Surrey, England
Distribution: Slackware
Posts: 1,036

Original Poster
Rep: Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850
Quote:
Originally Posted by alekow View Post

If you can add the package back and if maintaining it is not too much work for you I would really appreciate it!
It's no trouble for me. It'll be in the next batch.
 
2 members found this post helpful.
Old 03-18-2021, 07:12 AM   #11
alekow
Member
 
Registered: Sep 2009
Distribution: Slackware
Posts: 213

Rep: Reputation: 59
Quote:
Originally Posted by drmozes View Post
It's no trouble for me. It'll be in the next batch.
Great stuff! Thanks! :-)
 
Old 03-18-2021, 11:35 AM   #12
TheTKS
Member
 
Registered: Sep 2017
Location: The deep south... of Canada
Distribution: Slackware, Xubuntu, OpenBSD, elementary, Raspberry Pi OS, Puppy, TinyCore
Posts: 247

Rep: Reputation: 150Reputation: 150
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.

Code:
Error -- Kate
Unable to create io-slave. klauncher said: Error loading '/usr/lib/qt5/plugins/kf5/kio/file.so'."
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.
Old 03-18-2021, 01:56 PM   #13
Exaga
SARPi Maintainer
 
Registered: Nov 2012
Distribution: Slackware [ARM]
Posts: 639

Rep: Reputation: 375Reputation: 375Reputation: 375Reputation: 375
Quote:
Originally Posted by TheTKS View Post
Thank you, drmozes! The SlackwareARM update went smoothly on my RPi4 after last updating Feb 21.

Thanks to you also, exaga. Smooth updating to the 17Mar21 sarpi4 packages after last updating to the 17Feb21 packages.
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.
 
Old 03-18-2021, 06:00 PM   #14
TheTKS
Member
 
Registered: Sep 2017
Location: The deep south... of Canada
Distribution: Slackware, Xubuntu, OpenBSD, elementary, Raspberry Pi OS, Puppy, TinyCore
Posts: 247

Rep: Reputation: 150Reputation: 150
Quote:
Originally Posted by Exaga View Post
The new Slackware ARM current is performing most impressively for me. No niggles or concerns yet.
Same here

Quote:
Originally Posted by Exaga View Post
[SARPi] 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.
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.
Old 03-19-2021, 02:33 AM   #15
nobodino
Member
 
Registered: Jul 2010
Location: in France
Distribution: slackware, slackware from scratch, LFS, slackware [arm], linux Mint,Manjaro...
Posts: 831

Rep: Reputation: 431Reputation: 431Reputation: 431Reputation: 431Reputation: 431
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"?
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] KODI Krypton - 17.x MediaPlayer - Optimized for Raspberry Pi1/Pi2/Pi3 on Slackware ARM 14.2 SF & Slackware ARM - current HF abga Slackware - ARM 40 08-28-2018 08:50 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - ARM

All times are GMT -5. The time now is 03:27 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration