PINE64
slarm64 (unofficial slackware) Rock64 RK3328 (aarch64) - Printable Version

+- PINE64 (https://forum.pine64.org)
+-- Forum: ROCK64 (https://forum.pine64.org/forumdisplay.php?fid=85)
+--- Forum: Linux on Rock64 (https://forum.pine64.org/forumdisplay.php?fid=88)
+--- Thread: slarm64 (unofficial slackware) Rock64 RK3328 (aarch64) (/showthread.php?tid=5868)

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14


RE: slarm64 (unofficial slackware) Rock64 RK3328 (aarch64) - mara - 12-28-2020

update:
kernel 5.10.3
update all packages Mon Dec 28 08:32:11 UTC 2020

slarm64-current-aarch64-base-rock64-5.10.3-build-20201228.img.zst
slarm64-current-aarch64-base-rock64-5.10.3-build-20201228.img.zst.sha256
slarm64-current-aarch64-xfce-rock64-5.10.3-build-20201228.img.zst
slarm64-current-aarch64-xfce-rock64-5.10.3-build-20201228.img.zst.sha256


RE: slarm64 (unofficial slackware) Rock64 RK3328 (aarch64) - mara - 01-26-2021

kernel 5.10.10
slarm64-current-aarch64-base-rock64-5.10.10-build-20210126.img.zst
slarm64-current-aarch64-base-rock64-5.10.10-build-20210126.img.zst.sha256
slarm64-current-aarch64-enlightenment-rock64-5.10.10-build-20210126.img.zst
slarm64-current-aarch64-enlightenment-rock64-5.10.10-build-20210126.img.zst.sha256


RE: slarm64 (unofficial slackware) Rock64 RK3328 (aarch64) - Enig123 - 01-28-2021

I am still using 4.4.246 kernel. However, 'slackpkg upgrade-all' is not working as before, it now returned with message of GPG key mismatch.

It's not working even after 'slackpkg upgrade gpg' command executed.


RE: slarm64 (unofficial slackware) Rock64 RK3328 (aarch64) - mara - 01-29-2021

(01-28-2021, 06:20 PM)Enig123 Wrote: I am still using 4.4.246 kernel. However, 'slackpkg upgrade-all' is not working as before, it now returned with message of GPG key mismatch.

It's not working even after 'slackpkg upgrade gpg' command executed.
Due to a big update, not all packages have been redistributed, today they will be fixed, thanks for the information.


RE: slarm64 (unofficial slackware) Rock64 RK3328 (aarch64) - mara - 01-30-2021

kernel 5.10.10
slarm64-current-aarch64-base-rock64-5.10.10-build-20210126.img.zst
slarm64-current-aarch64-base-rock64-5.10.10-build-20210126.img.zst.sha256
slarm64-current-aarch64-enlightenment-rock64-5.10.10-build-20210126.img.zst
slarm64-current-aarch64-enlightenment-rock64-5.10.10-build-20210126.img.zst.sha256

slarm64-current-aarch64-base-rock64-4.4.254-build-20210130.img.zst
slarm64-current-aarch64-base-rock64-4.4.254-build-20210130.img.zst.sha256
slarm64-current-aarch64-xfce-rock64-4.4.254-build-20210130.img.zst
slarm64-current-aarch64-xfce-rock64-4.4.254-build-20210130.img.zst.sha256


RE: slarm64 (unofficial slackware) Rock64 RK3328 (aarch64) - Enig123 - 02-02-2021

Unfortunately the upgrade-all from previous version still fails.

And, what should do I do to upgrade to the new 4.4.254 kernel?


RE: slarm64 (unofficial slackware) Rock64 RK3328 (aarch64) - mara - 02-03-2021

(02-02-2021, 04:21 PM)Enig123 Wrote: Unfortunately the upgrade-all from previous version still fails.

And, what should do I do to upgrade to the new 4.4.254 kernel?
upgrade-all try changing the mirror, it appears first on slarm64.org
to update the kernel, you need to download the packages and upgrade via upgradepkg.


RE: slarm64 (unofficial slackware) Rock64 RK3328 (aarch64) - Enig123 - 02-27-2021

Hi mara,

I have tried the latest 5.10.10 image, which causes endless reboot on my Rock64 v2.

The 4.4.254 kernel is okay, but after 'slackpkg update & slackpkg upgrade-all', there's errors during the upgrading process, it stuck with the following error messages:
Quote:+==============================================================================
| Upgrading sed-4.8-aarch64-2 package using ./sed-4.8-aarch64-3.txz
+==============================================================================
Pre-installing package sed-4.8-aarch64-3...
sed: /lib64/libc.so.6: version `GLIBC_2.33' not found (required by sed)
sed: /lib64/libc.so.6: version `GLIBC_2.33' not found (required by sed)
Removing package: packages
sed: /lib64/libc.so.6: version `GLIBC_2.33' not found (required by sed)
Any idea how to resolve it?

Edit1:
The second issue has been resolved by myself, after several failed attempts. To make it work, you'll have to download and install the latest
http://dl.slarm64.org/slackware/slarm64-current/slarm64/a/aaa_glibc-solibs-2.33-aarch64-1.txz
http://dl.slarm64.org/slackware/slarm64-current/slarm64/a/aaa_libraries-15.0-aarch64-3.txz
before 'slackpkg update & slackpkg upgrade-all'.

Edit2:
After upgrade-all, the issue of invalid pgp key is still there, whenever I intend to use slackpkg to install a package, it will always warn me about the pgp key:
Quote:You need the GPG key of slarm64 AArch64 <security@slarm64.org>.
To download and install that key, run:

# slackpkg update gpg

You can disable GPG checking too, but it is not a good idea.
To disable GPG, edit slackpkg.conf and change the value of the CHECKGPG
variable to off - you can see an example in the original slackpkg.conf.new
file distributed with slackpkg.

Edit3:
I just did another try, force using slackpkg to install every packages, it seems the issue described in Edit2 gone.


RE: slarm64 (unofficial slackware) Rock64 RK3328 (aarch64) - Enig123 - 02-28-2021

In summary, the correct way to upgrade from the latest image of 4.4.254 kernel is as follow:

1. 'slackpkg update'
2. 'slackpkg upgrade slackpkg' - upgrade slackpkg itself
3. 'slackpkg install aaa_glibc-solibs' - install missing package
4. 'slackpkg install aaa_libraries' - install missing package
5. 'slackpkg upgrade-all'

That's it.


RE: slarm64 (unofficial slackware) Rock64 RK3328 (aarch64) - mara - 02-28-2021

(02-28-2021, 12:00 AM)Enig123 Wrote: In summary, the correct way to upgrade from the latest image of 4.4.254 kernel is as follow:

1. 'slackpkg update'
2. 'slackpkg upgrade slackpkg' - upgrade slackpkg itself
3. 'slackpkg install aaa_glibc-solibs' - install missing package
4. 'slackpkg install aaa_libraries' - install missing package
5. 'slackpkg upgrade-all'

That's it.
yes, this is a bulk rebuild for glibc-2.33.

such an update is correct for any image (the kernel has nothing to do with it)