Thank you so much for your continued feedback—without you, we might never have caught this critical issue!
Hey everyone,
following up on the fix from @chenchongbiao — wanted to share a proper how-to using the official Armbian build system for everybody who cannot wait for a new kernel update from Armbian
How to apply
The fix is already in the radxa/kernel:linux-6.18.2 branch HEAD. A fresh Armbian kernel build picks it up automatically — no patching needed.
Step 1 — Build the kernel debs
git clone --depth=1 https://github.com/armbian/build
cd build
./compile.sh kernel \
BOARD=radxa-dragon-q6a \
BRANCH=current \
RELEASE=trixie \
KERNEL_CONFIGURE=no
Step 2 — Transfer all three debs to the board
scp output/debs/linux-image-current-qcs6490_*.deb \
output/debs/linux-dtb-current-qcs6490_*.deb \
output/debs/linux-headers-current-qcs6490_*.deb \
user@your-board:/tmp/
Step 3 — Install on the board
cd /tmp
sudo dpkg -i linux-image-current-qcs6490_*.deb \
linux-dtb-current-qcs6490_*.deb \
linux-headers-current-qcs6490_*.deb
GRUB is updated automatically. The old kernel is preserved as fallback.
Step 4 — Reboot and verify
sudo reboot
After reboot:
# Fix confirmed — zero UFS errors
sudo dmesg | grep -iE "OCS invalid|pa_err|dl_err|timed-out" | wc -l
# → 0
# Device initializes cleanly
sudo dmesg | grep -i "THGJFGT"
# → KIOXIA THGJFGT1E45BAILB detected, no errors
Thanks to @chenchongbiao for the fix and @pamvdam for the initial testing. ![]()
I can try to submit a patch to Armbian, or another developer can do it.
From his message it seems to be already fixed in Armbian. They just need to publish a new image?
This is also my understanding of the kernel build process
An apt upgrade reverted my system back to the stock 6.18.2-4-qcom kernel, removing the UFS fix.
For now I use sudo apt-mark hold linux-image-6.18.2-4-qcom to prevent replacement.
Do you know when the fix will be integrated into the official kernel, in order to survive normal system upgrades?
linux-image 6.18 has not released a new version. We will update to linux-image 7.0.
The exact timeline has not been confirmed yet — we still need to do some testing.
You can hold the package to prevent it from being upgraded: https://askubuntu.com/a/18656
EDIT: nevermind saw you already figured it out.
I see the maintainer @meco is already here ![]()
Can you answer when there will be a new release of the Radxa Dragon Q6A Armbian Image, with this fix?
Thank you for tagging me. The fix will be in the next Armbian 26.05 release which is going to be up in the next couple days. In the mean time the steps you posted above are a way to solve the issue.
In the future it is best to open an armbian issue and tagging the maintainers as that will be the fastest way for one of us to see it.