Is the UK mirror out of date as getting a gpg sig error
Didn’t like https either cert not valid so tried uk http
Radxa Zero Slarm64 (aarch64 unofficial slackware)
slackpkg update gpg && slackpkg update
@stuartiannaylor I found the driver for AP6236 which gets wifi module loaded by kernel. I haven’t been able to successfully connect and am in the middle of working out whether it is my router or some OS configuration on my pi.
Maybe worth trying the patch @mara mentioned here, or try Slarm64 if you would have support for the wifi module. fw_bcm43436b0.bin seems to be the driver to use.
I think this one is for the 2gb+ with AP6256 I have bit 512mb & 2gb but only tested the 2gb.
On that wifi connects and works great.
fixes for first login
slarm64-current-aarch64-server-radxa_zero-5.13.11-build-20210818.img.zst
slarm64-current-aarch64-server-radxa_zero-5.13.11-build-20210818.img.zst.sha256
slarm64-current-aarch64-xfce-radxa_zero-5.13.11-build-20210818.img.zst
slarm64-current-aarch64-xfce-radxa_zero-5.13.11-build-20210818.img.zst.sha256
slarm64-current-aarch64-enlightenment-radxa_zero-5.13.11-build-20210818.img.zst
slarm64-current-aarch64-enlightenment-radxa_zero-5.13.11-build-20210818.img.zst.sha256
2 Likes
kernel 5.14.5
slarm64-current-aarch64-server-radxa_zero-5.14.5-build-20210917.img.zst
slarm64-current-aarch64-server-radxa_zero-5.14.5-build-20210917.img.zst.sha256
slarm64-current-aarch64-xfce-radxa_zero-5.14.5-build-20210917.img.zst
slarm64-current-aarch64-xfce-radxa_zero-5.14.5-build-20210917.img.zst.sha256
slarm64-current-aarch64-enlightenment-radxa_zero-5.14.5-build-20210917.img.zst
slarm64-current-aarch64-enlightenment-radxa_zero-5.14.5-build-20210917.img.zst.sha256
1 Like
kernel 5.15.2
slarm64-current-aarch64-server-radxa_zero-5.15.2-build-20211116.img.zst
slarm64-current-aarch64-server-radxa_zero-5.15.2-build-20211116.img.zst.sha256
slarm64-current-aarch64-xfce-radxa_zero-5.15.2-build-20211116.img.zst
slarm64-current-aarch64-xfce-radxa_zero-5.15.2-build-20211116.img.zst.sha256
1 Like
update kernel 5.16.2
slarm64-current-aarch64-server-radxa_zero-5.16.2-build-20220122.img.zst
slarm64-current-aarch64-server-radxa_zero-5.16.2-build-20220122.img.zst.sha256
slarm64-current-aarch64-xfce-radxa_zero-5.16.2-build-20220122.img.zst
slarm64-current-aarch64-xfce-radxa_zero-5.16.2-build-20220122.img.zst.sha256
1 Like
Hi there, I’m having trouble booting this. Copied the latest 5.16.2 XFCE image to SD, and for me it always hangs after “Starting kernel” and just sits there forever. Any idea on what to try?
Hi, try enabling more verbosity=8 output in /boot/uEnv.txt
I’ve tried that, but it behaves exactly the same, which is super strange. This is all I get on my screen.
Also, to mention, my SKU is 4GB RAM, 64GB eMMC (flashed with radxa-zero-erase-emmc.bin)
everything is correctly recorded and the booting is in progress, then it seems to hang or wait for the root partition, you can try changing the root partition to mmcblk1p1.
does the blue led start flashing?
my board: 4GB RAM, WIFI5/BT5, 16GB eMMC, external antenna connector
Thanks, fixed the bug.
update kernel 5.16.14
Installation README.TXT
slarm64-current-aarch64-server-radxa_zero-5.16.14-build-20220312.img.zst
slarm64-current-aarch64-server-radxa_zero-5.16.14-build-20220312.img.zst.sha256
slarm64-current-aarch64-xfce-radxa_zero-5.16.14-build-20220312.img.zst
slarm64-current-aarch64-xfce-radxa_zero-5.16.14-build-20220312.img.zst.sha256
Hi, sorry, only got to testing it today. Doesn’t matter if I do mmcblk0p1 or mmcblk1p1, it behaves the same. No blue LED. I’ve also tried flashing the server image you posted today (XFCE link seems to not be uploaded yet) and that one instead bootloops like this:
yes, there is no blue led, is this a new image with a 5.16.14 kernel?
Yes, this was newly imaged slarm64-current-aarch64-server-radxa_zero-5.16.14-build-20220312.img.zst
Sstrange, I specifically tested and everything loaded for me.
The difference is probably that the bootloader from 20220122 is already installed in the eMMC.
Try writing the bootloader boot-20220312.tar.xz
Tested the new bootloader in eMMC, still broken. Although now at least it’s not bootlooping again, it went back to the previous behavior of being stuck on “Starting kernel…”
Then only the output through debug (uart) will help to understand, it seems there is some difference between your board and mine.
Okay, caught the boot output on UART, the whole thing is here: https://pastebin.com/BGtLGEkL
However I think the relevant section is this:
[ 2.999872] mmc0: new ultra high speed SDR50 SDIO card at address 0001
[ 3.014550] udevd[1189]: starting eudev-3.2.11
[ 3.017714] mmc2: new HS200 MMC card at address 0001
[ 3.020107] mmcblk2: mmc2:0001 SLD64G 57.6 GiB
[ 3.030252] mmc1: card 5048 removed
[ 3.032259] udevd[1191]: inotify_add_watch(5, /dev/mmcblk1, 10) failed: No such file or directory
[ 3.038169] udevd[1208]: inotify_add_watch(5, /dev/mmcblk1p1, 10) failed: No such file or directory
[ 3.052389] mmcblk2boot0: mmc2:0001 SLD64G 4.00 MiB
[ 3.054654] mmcblk2boot1: mmc2:0001 SLD64G 4.00 MiB
[ 3.058597] mmcblk2rpmb: mmc2:0001 SLD64G 4.00 MiB, chardev (242:0)
It seems like one of the storages gets remapped to mmc2, and mmc1 gets dropped? But I have no idea why.