I installed rock-s0_debian_bookworm_cli_b6.img to the emmc of my pi s0 and tried to do a system upgrade using rsetup.
About https: //radxa-repo.github.io/bookworm, It claims :
The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 67A474DD40402951 NO_PUBKEY 5D93177D0752732A
Something seems broken in radxa repos.
Can you help ?
Hi,
Could you try to follow the Usage in this link to import the key:
# Install signing keyring
keyring="$(mktemp)"
version="$(curl -L https://github.com/radxa-pkg/radxa-archive-keyring/releases/latest/download/VERSION)"
curl -L --output "$keyring" "https://github.com/radxa-pkg/radxa-archive-keyring/releases/latest/download/radxa-archive-keyring_${version}_all.deb"
sudo dpkg -i "$keyring"
rm -f "$keyring"
Then see if you still get the error?
I tested this. rsetup fails to upgrade system. If I reboot, I see it now boots 6.1.68-3-stable instead of 68-1. But then, this goes to kernel panic :
** Booting bootflow ‘[email protected]_3’ with extlinux
U-Boot menu
1: Debian GNU/Linux 12 (bookworm) 6.1.68-3-stable
2: Debian GNU/Linux 12 (bookworm) 6.1.68-3-stable (rescue target)
3: Debian GNU/Linux 12 (bookworm) 6.1.68-1-stable
4: Debian GNU/Linux 12 (bookworm) 6.1.68-1-stable (rescue target)
Enter choice: 1: Debian GNU/Linux 12 (bookworm) 6.1.68-3-stable
Retrieving file: /boot/vmlinuz-6.1.68-3-stable
append: root=UUID=8c261e5d-465a-4a91-b99c-35e28e6e8556 console=ttyS0,1500000n8 quiet splash loglevel=4 rw earlycon consoleblank=0 console=tty1 coherent_pool=2M irqchip.gicv3_pseudo_nmi=0 cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 kasan=off
Retrieving file: /usr/lib/linux-image-6.1.68-3-stable/rockchip/rk3308-rock-s0.dtb
Moving Image from 0x2080000 to 0x2200000, end=4890000
Booting using the fdt blob at 0x1d00000
Working FDT set to 1d00000
ERROR: reserving fdt memory region failed (addr=0 size=0 flags=0)
Loading Device Tree to 000000001df0b000, end 000000001df1bb2f … OK
Working FDT set to 1df0b000
Starting kernel …
[ 0.000000] OF: fdt: Reserved memory: failed to reserve memory for node ‘drm-logo@00000000’: base 0x0000000000000000, size 0 MiB
[ 0.000000] OF: fdt: Reserved memory: failed to reserve memory for node ‘drm-logo@00000000’: base 0x0000000000000000, size 0 MiB
[ 0.633964] dw-apb-uart ff0e0000.serial: Failed to create device link (0x180) with vcc-1v8
[ 0.637863] /dev/root: Can’t open blockdev
[ 0.638365] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ 0.639109] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 6.1.68-3-stable #ba6f5fb46
[ 0.639781] Hardware name: Radxa ROCK S0 (DT)
[ 0.640180] Call trace:
[ 0.640410] dump_backtrace.part.0+0xe0/0xf0
[ 0.640823] show_stack+0x18/0x30
[ 0.641137] dump_stack_lvl+0x68/0x84
[ 0.641482] dump_stack+0x18/0x34
[ 0.641798] panic+0x174/0x334
[ 0.642089] mount_block_root+0x17c/0x22c
[ 0.642471] mount_root+0x204/0x240
[ 0.642797] prepare_namespace+0x130/0x170
[ 0.643180] kernel_init_freeable+0x2b0/0x2dc
[ 0.643586] kernel_init+0x24/0x12c
[ 0.643917] ret_from_fork+0x10/0x20
[ 0.644259] SMP: stopping secondary CPUs
[ 0.644672] Kernel Offset: disabled
[ 0.644991] CPU features: 0x00000,00000080,0000421b
[ 0.645437] Memory Limit: none
[ 0.645727] —[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]—
Do you get kernel panic if you choose booting the 6.1.68-1-stable one?
No. Only when trying update with rsetup