2025-09-06 11:06:16 <omni> hi, is anyone here using qt6-qtwebengine on edge or 3.22-stable on this architecture?
2025-09-06 11:07:25 <omni> https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/89733/commits
2025-09-06 11:07:27 <omni> https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/85390/commits
2025-09-09 04:23:11 <min1123[m]> Question, I'm attempting to run an Alpine Linux on Loongson64 (USB flash drive on Banana Pi-2K0300, at the u-boot prompt over serial over USB-C), I've tried the standard images from 3.22.1, 3.21.4, and 3.21.1. They all appear to have a corrupt partition, and they I cannot mount them or fsck them while on loopback. Is anybody testing/using these?
2025-09-09 06:34:09 <DWwanghao> Hi min1123[m]: I usually boot via UEFI after writing the image to a USB drive using the dd command. All versions including 3.21, 3.22, and Edge work without any issues
2025-09-09 06:36:20 <DWwanghao> Alpine's images are built based on rootfs. Currently, loongarch only supports UEFI boot and does not support U-boot
2025-09-09 07:02:02 <xen0n> The LoongArch boot protocol is supposed to unify around the UEFI system table and PE image, but vendors have been really slow at implementing it
2025-09-09 07:03:14 <xen0n> so it may be the case that the vendor u-boot is still expecting the legacy boot protocol which is ELF kernel images and different FDT format
2025-09-09 11:40:07 <min1123[m]> Sure, but on all the images, I’m seeing the EFI, and the PE there, but the other partitions don’t appear to have a filesystem. What is that rootfs supposed to look like on the bot media?
2025-09-09 11:40:18 <min1123[m]> s/bot/boot/