Cumulative repo for Slacware ARM

saxa · 11-22-2023, 07:26 PM

Hi , I would be interested to know if maybe somebody has a cumulative repo of the slackware ARM current packages. Particularly from 14.2 to 15.0.

I know there is a slackware cumulative repo on slackware.co.uk , but it is
only for x86_64 and i486.

business_kid · 11-23-2023, 09:46 AM

AFAIK such a thing is not kept by any "Rolling release" distro. What is your specific requirement for it?

The only thing I have ever felt the need for is the previous properly working version, in the event that some update introduces issues (e.g. vlc earlier this year). By backing up the most recent working OS to disk, you have that. It would be silly not to if you're using sdcards.

saxa · 11-23-2023, 12:12 PM

Ok at slackware.co.uk there is a cumulative repo, so you can go downgrading some package that you upgraded and the it had troubles for some reason. I have my BananaPi PRO where I use it for my asterisk server and mistakely
run slackpkg upgrade from 14.2+ current version to final 15.0 then for some reason i realized that it wont work, but too late, and some aaa and few other packages have been upgraded already. Now the trouble is that going back
is a pain as I dont have anymore the packages which were installed at the time, and the -current from that time moved forward and is now 15.0 . So doing an upgrade remotely without being there is a bit too critical for me.
The BPi still works ok, but some base stuff like cp, tar, sed are no longer working complaining that libacl does not find the correct glibc. So I saw I have 2 libacl versions installed and a link pointing to it.

Anyway long story short, I would like to correct my system and or revert it back or upgrade it. But without a working base tools installpkg, removepkg are not fully working.

drmozes · 11-25-2023, 05:00 AM

Quote:

Originally Posted by saxa

The BPi still works ok, but some base stuff like cp, tar, sed are no longer working complaining that libacl does not find the correct glibc. So I saw I have 2 libacl versions installed and a link pointing to it.

14.2+ was the armv7-a port that ultimately became Slackware ARM 15.0.
From what you've said, it seems that you just need to upgrade to the 15.0 package set and any patches.

On another Slackware box, or within the 15.0 installer:

Code:

mkdir /mnt/bpistorage
mount /dev/whatever /mnt/bpistorage
ROOT=/mnt/bpistorage upgradepkg /path/to/slackwarearm-15.0/slackware/<series>/package*z

Upgrade the 'a' series first.
If there was a repo, you could revert like this:

Code:

cd /var/log/removed_packages
ls -ltr

and upgradepkg back to the previous versions of the most recently touched packages.

saxa · 11-28-2023, 06:12 AM

Hi drmozes, many thanks for this tip, but I think this wont work from remote. I am far away from my pi right now and will try to do that once i get close to the board. I think this would be a too risky task for doing it
over network from another side of the world.

gus3 · 11-28-2023, 02:15 PM

What if...

You try it, two days before you leave (Chile? Singapore?); if it goes wrong, you'll be back soon enough to find out why and fix it.

Don't worry; I wasn't that brave, either.

saxa · 11-29-2023, 05:56 AM

No sure, i could even try it earlier

but I am just scared that doing it over network for some reason it loose the connection and then even worst the tmux or screen got screwed up and then i am done

.

saxa · 07-05-2024, 07:01 AM

Ok, I have finally managed to upgrade a and ap series, but unfortunately I upgraded also the kernel images, so now it seems it does no longer boot.

I have copied my original sd card to and .img file, so I can still go back and restart.
I have also dd that original img file to a new bigger 32GB sd card. Then resized it and
it worked and booted up after inserting it into the bananapi.

Now after that I did as drmozes pointed out, mounted the sd card on my x86_64 slackware 15 install
and did the

Code:

ROOT=/mnt/tmp upgradepkg /home/slackwarearm/slackwarearm-15.0/slackware/a/*.t?z

then I did it again

Code:

ROOT=/mnt/tmp upgradepkg --install-new /home/slackwarearm/slackwarearm-15.0/slackware/a/*.t?z

And after that upgraded also the ap series.

But now seems it does no longer boot.

Probably it does not boot due to a new kernel it is now on the sdcard. Any ideas on how to update the uboot to
point to a new kernel ?

drmozes · 07-05-2024, 10:28 AM

Quote:

Originally Posted by saxa

Now after that I did as drmozes pointed out, mounted the sd card on my x86_64 slackware 15 install

This was a suggestion to rescue a broken install. There are a number of packages that detect the Hardware Model during the package installation process, which won't work on x86.
You need to upgrade packages natively.

Quote:

Originally Posted by saxa

And after that upgraded also the ap series.

But now seems it does no longer boot.

Probably it does not boot due to a new kernel it is now on the sdcard. Any ideas on how to update the uboot to
point to a new kernel ?

U-boot's config should not need changing because the config (assuming you followed the instructions and didn't change it) uses a statically named Kernel and initrd. The Kernel package creates symlinks from the versioned Kernel and initrd to the static names.

You'll need to look at the serial console to debug it; or just revert to the previous state from your backup and upgrade natively (which is what I'd do).

saxa · 07-06-2024, 05:05 AM

Hi @drmozes, ok I got , I will try to connect the cable on the debug pins to see whats on.

saxa · 07-06-2024, 06:16 AM

Tis is what I get on the console:

Code:

Model: LeMaker Banana Pro
I2C:   ready
DRAM:  1 GiB
MMC:   SUNXI SD/MMC: 0
Setting up a 720x576i composite-pal console (overscan 32x20)
In:    serial
Out:   vga
Err:   vga
SCSI:  SATA link 0 timeout.
AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
flags: ncq stag pm led clo only pmp pio slum part ccc apst
Net:   eth0: ethernet@01c50000
starting USB...
USB0:   USB EHCI 1.00
USB1:   USB OHCI 1.0
USB2:   USB EHCI 1.00
USB3:   USB OHCI 1.0
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 2 for devices... 1 USB Device(s) found
Hit any key to stop autoboot:  0
mmc - MMC sub system

Usage:
mmc info - display info of the current MMC device
mmc read addr blk# cnt
mmc write addr blk# cnt
mmc erase blk# cnt
mmc rescan
mmc part - lists available partition on current mmc device
mmc dev [dev] [part] - show or set current mmc device [partition]
mmc list - lists available devices
mmc hwpartition [args...] - does hardware partitioning
  arguments (sizes in 512-byte blocks):
    [user [enh start cnt] [wrrel {on|off}]] - sets user data area attributes
    [gp1|gp2|gp3|gp4 cnt [enh] [wrrel {on|off}]] - general purpose partition
    [check|set|complete] - mode, complete set partitioning completed
  WARNING: Partitioning is a write-once setting once it is set to complete.
  Power cycling is required to initialize partitions after set to complete.
mmc setdsr <value> - set DSR register value

mmc - MMC sub system

Usage:
mmc info - display info of the current MMC device
mmc read addr blk# cnt
mmc write addr blk# cnt
mmc erase blk# cnt
mmc rescan
mmc part - lists available partition on current mmc device
mmc dev [dev] [part] - show or set current mmc device [partition]
mmc list - lists available devices
mmc hwpartition [args...] - does hardware partitioning
  arguments (sizes in 512-byte blocks):
    [user [enh start cnt] [wrrel {on|off}]] - sets user data area attributes
    [gp1|gp2|gp3|gp4 cnt [enh] [wrrel {on|off}]] - general purpose partition
    [check|set|complete] - mode, complete set partitioning completed
  WARNING: Partitioning is a write-once setting once it is set to complete.
  Power cycling is required to initialize partitions after set to complete.
mmc setdsr <value> - set DSR register value

25506 bytes read in 1980 ms (11.7 KiB/s)
5901224 bytes read in 742 ms (7.6 MiB/s)

And it stays there.

saxa · 07-06-2024, 06:16 AM

Then seems it load the kernel and errors:

Code:

[    5.188675] usbcore: registered new interface driver ums-freecom
[    5.221032] usbcore: registered new interface driver ums-isd200
[    5.253759] usbcore: registered new interface driver ums-sddr09
[    5.285529] usbcore: registered new interface driver ums-sddr55
[    5.317969] usbcore: registered new interface driver ums-alauda
[    5.349714] usbcore: registered new interface driver ums-jumpshot
[    5.380936] usbcore: registered new interface driver ums-onetouch
[    5.428976] usbcore: registered new interface driver uas
[    5.632801] sdhci: Secure Digital Host Controller Interface driver
[    5.642134] sdhci: Copyright(c) Pierre Ossman
[    5.670796] sdhci-pltfm: SDHCI platform and OF driver helper
[    5.912501] device-mapper: ioctl: 4.45.0-ioctl (2021-03-22) initialised: dm-devel@redhat.com
[    6.537372] raid6: skip pq benchmark and using algorithm neonx8
[    6.546453] raid6: using neon recovery algorithm
[    6.566097] xor: measuring software checksum speed
[    6.582564]    arm4regs        :  1172 MB/sec
[    6.603829]    8regs           :   712 MB/sec
[    6.623321]    32regs          :   810 MB/sec
[    6.644662]    neon            :   697 MB/sec
[    6.651781] xor: using function: arm4regs (1172 MB/sec)
[    6.989693] Btrfs loaded, crc32c=crc32c-generic, zoned=no, fsverity=yes
[    7.132396] JFS: nTxBlock = 7989, nTxLock = 63917
[    7.558472] SGI XFS with ACLs, security attributes, realtime, quota, no debug enabled
[    7.635375] FS-Cache: Loaded
[    7.807994] RPC: Registered named UNIX socket transport module.
[    7.816878] RPC: Registered udp transport module.
[    7.824389] RPC: Registered tcp transport module.
[    7.831854] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    8.032387] FS-Cache: Netfs 'nfs' registered for caching
mdadm: No arrays found in config file or automatically
[   11.246220] urandom_read: 3 callbacks suppressed
[   11.246252] random: vgchange: uninitialized urandom read (4 bytes read)
mount: mounting /dev/mmcblk0p1 on /mnt failed: No such file or directory
ERROR:  No /sbin/init found on rootdev (or not mounted).  Trouble ahead.
        You can try to fix it. Type 'exit' when things are done.

/bin/sh: can't access tty; job control turned off
/ # [   32.241189] vcc3v0: disabling
[   32.247333] vcc3v3: disabling
[   32.253365] vcc5v0: disabling
[   32.259395] gmac-3v3: disabling

saxa · 07-06-2024, 06:19 AM

then I can type exit and I get this:

Code:

[   32.259395] gmac-3v3: disabling
exit
mount: mounting /proc on /mnt/proc failed: No such file or directory
mount: mounting /sys on /mnt/sys failed: No such file or directory
mount: mounting /run on /mnt/run failed: No such file or directory
mount: mounting /dev on /mnt/dev failed: No such file or directory
/boot/initrd-armv7.gz:  exiting
BusyBox v1.32.1 (2022-01-27 13:20:27 GMT)[  251.908708] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
[  251.926245] CPU: 0 PID: 1 Comm: switch_root Not tainted 5.15.21-armv7 #1
[  251.936467] Hardware name: Allwinner sun7i (A20) Family
[  251.945189] [<c030df00>] (unwind_backtrace) from [<c03095e4>] (show_stack+0x10/0x14)
[  251.960004] [<c03095e4>] (show_stack) from [<c0a236d8>] (dump_stack_lvl+0x40/0x4c)
[  251.974728] [<c0a236d8>] (dump_stack_lvl) from [<c0a1d104>] (panic+0xb8/0x2bc)
[  251.985657] [<c0a1d104>] (panic) from [<c033ecac>] (do_exit+0x1d0/0x518)
[  251.996081] [<c033ecac>] (do_exit) from [<c033fc74>] (do_group_exit+0x58/0xb8)
[  252.007080] [<c033fc74>] (do_group_exit) from [<c033fce4>] (__wake_up_parent+0x0/0x14)
[  252.022598] CPU1: stopping
[  252.029168] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.15.21-armv7 #1
[  252.039722] Hardware name: Allwinner sun7i (A20) Family
[  252.048971] [<c030df00>] (unwind_backtrace) from [<c03095e4>] (show_stack+0x10/0x14)
[  252.064759] [<c03095e4>] (show_stack) from [<c0a236d8>] (dump_stack_lvl+0x40/0x4c)
[  252.080436] [<c0a236d8>] (dump_stack_lvl) from [<c030bf28>] (do_handle_IPI+0x128/0x2b4)
[  252.096809] [<c030bf28>] (do_handle_IPI) from [<c030c0c8>] (ipi_handler+0x14/0x20)
[  252.113102] [<c030c0c8>] (ipi_handler) from [<c038d4a8>] (handle_percpu_devid_irq+0x6c/0x11c)
[  252.130710] [<c038d4a8>] (handle_percpu_devid_irq) from [<c0387d2c>] (handle_irq_desc+0x24/0x34)
[  252.148766] [<c0387d2c>] (handle_irq_desc) from [<c03884d4>] (handle_domain_irq+0x38/0x50)
[  252.166556] [<c03884d4>] (handle_domain_irq) from [<c0666710>] (gic_handle_irq+0x80/0x98)
[  252.184825] [<c0666710>] (gic_handle_irq) from [<c0300b48>] (__irq_svc+0x48/0x5c)
[  252.202520] Exception stack(0xc18b1f58 to 0xc18b1fa0)
[  252.212680] 1f40:                                                       00007ad4 00000000
[  252.230867] 1f60: 00000001 c0316da0 c18b0000 00000000 c18b0000 c100bda4 4020406a 410fc074
[  252.248947] 1f80: 00000000 00000000 00000000 c18b1fa8 c0306674 c0306664 600b0013 ffffffff
[  252.267014] [<c0300b48>] (__irq_svc) from [<c0306664>] (arch_cpu_idle+0x1c/0x38)
[  252.284396] [<c0306664>] (arch_cpu_idle) from [<c0a32a30>] (default_idle_call+0x38/0x54)
[  252.302595] [<c0a32a30>] (default_idle_call) from [<c0365a64>] (cpuidle_idle_call+0x60/0x180)
[  252.321499] [<c0365a64>] (cpuidle_idle_call) from [<c0365c38>] (do_idle+0xb4/0xc0)
[  252.339552] [<c0365c38>] (do_idle) from [<c0365ef4>] (cpu_startup_entry+0x18/0x1c)
[  252.357622] [<c0365ef4>] (cpu_startup_entry) from [<40301504>] (0x40301504)
[  252.369923] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100 ]---
 multi-call binary.

Usage: switch_root [-c CONSOLE_DEV] NEW_ROOT NEW_INIT [ARGS]

Free initramfs and switch to another root fs:
chroot to NEW_ROOT, delete all in /, move NEW_ROOT to /,
execute NEW_INIT. PID must be 1. NEW_ROOT must be a mountpoint.

        -c DEV  Reopen stdio to DEV after switch

saxa · 07-07-2024, 02:48 AM

If I understand it correctly it does no longer find the / partition for some reason. So maybe this was caused from the gparted partition expansion I did. Could it be ? After I expanded the root partition from 14GB to 30GB it seems that the fdisk showed the partition type dos in stead linux. But it booted correctly when I tried it. This happened before I attempted the upgradepkg commands. So I tought it was all ok.

saxa · 07-07-2024, 02:50 AM

Will try to redo the whole process, but this time will upgrade only the minimum package set, and then boot and upgrade everything natively in the bananapi instead of x86_64 machine.