Skip to content
DOCUMENTATION
Experimental

Dragon Q6A-class boards

The qcs6490 image targets the Arrow Dragon Q6A and similar QCS6490 boards. It is the one UFLinux device image that needs a kernel from another distribution, and the reason it is labelled experimental is specific and worth understanding before you flash one.

Board id qcs6490
Boards Arrow Dragon Q6A and similar QCS6490 boards
Architecture aarch64
Kernel Nura linux-postmarketos-qcom-sc7280
Boot Board UEFI + systemd-boot
Root filesystem f2fs, label UFLINUX_ROOT
Status Experimental

Some QCS6490 boards have no firmware-provided device tree, and Alpine’s linux-lts is neither configured nor patched for the platform’s display — so HDMI stays black. That was observed on real hardware: the board’s firmware reached systemd-boot and the entry loaded, but nothing appeared on the screen.

The image therefore runs the mainline kernel from Nura, the postmarketOS distribution. It ships the Qualcomm drivers built in, the board device trees under /boot/dtbs, and a linux.efi zboot image that systemd-boot loads directly.

Nura’s dtbloader EFI driver is also carried in EFI/systemd/drivers. It installs a board device tree before systemd-boot runs, which covers boards whose firmware provides none.

Nura is used only as an extra aarch64 package source pinned to a specific branch, and only for that kernel and driver. The index itself is not pinned — postmarketOS rebuilds a release branch’s index regularly — so the branch is the pin. Bootloaders and every other driver come from Alpine, and no Nura device-* package is ever installed.

Both packages are fetched and unpacked rather than installed. Nura ships its own mkinitfs replacement that conflicts with Alpine’s, and apk solves against everything in /etc/apk/repositories — with both visible, apk refuses to select any package set that pulls in a kernel. So the files are unpacked at their package paths and become ordinary rootfs content, with no Nura entry in the installed database.

Two consequences you should know about:

  • Because the kernel is unpacked, no update-kernel hook runs. The image profile assembles the boot files by hand and generates the initramfs with Alpine’s mkinitfs against the unpacked /lib/modules tree — postmarketOS is a merged-usr distribution and unpacks its modules under /usr/lib/modules, so the profile links /lib/modules there.
  • Unpacked packages get no triggers and cannot be upgraded with apk. To move the kernel forward, flash a newer image.
  • The initramfs must be gzip-compressed. The inspected Nura 7.0.8-r0 kernel enables CONFIG_RD_GZIP but disables CONFIG_RD_ZSTD, so the ISO’s Zstandard setting would stop the kernel from unpacking the early userspace. qcs6490 therefore sets initramfs_compression: gzip in config/devices.json; other boards default to Zstandard.
  • Firmware for built-in drivers is listed explicitly. The QUP I2C driver (i2c-qcom-geni) is built into the kernel, probes while the initramfs is still running, and asks for qcom/qcm6490/qupv3fw.elf before the root filesystem mounts — without it the I2C bus feeding the HDMI bridge never appears. Boards list such files in initramfs_files, and the profile passes them to mkinitfs as custom_files.
  • Display modules are loaded from /etc/modules. The whole HDMI chain is loadable modules — the Dragon Q6A’s bridge is described in the device tree as radxa,ra620, which the generic simple-bridge driver claims — so the board lists them in initramfs_modules and the profile writes them into the initramfs.

Same procedure as every other device image — see Device images. Log in as user / user over HDMI on tty1 or the ttyMSM0 serial console.

Derived from docs/device-images.md inUFlinux-project/uflinux3(b4f4817). Report documentation problems inUFlinux-project/docs.