-
Notifications
You must be signed in to change notification settings - Fork 221
Description
Body
Hardware / Software
- Board: Radxa Dragon Q6A
- SoC: QCS6490 / QCM6490
- OS: Ubuntu (official Radxa image)
- Running kernel: 6.15.7+
- Kernel build info: Linux 6.15.7+ (built by nascs@mrs-taylor)
Context
I am working on enabling a camera sensor (Sony IMX586) on the CAM1 connector of the Radxa Dragon Q6A.
The Device Tree configuration is already in place and correctly loaded at boot.
The sensor is detected on the correct CCI bus and the camera pipeline is active.
However, I am currently blocked at the kernel module build stage.
Problem
The running kernel (6.15.7+) appears to be a Radxa-custom kernel, but the corresponding kernel build artifacts are not publicly available.
Because of this, it is not possible to build or load external kernel modules, due to:
- Missing Module.symvers
- Mismatch in kernel.release / vermagic
- Unresolved symbols during modpost
The available public repositories and Ubuntu packages only provide headers for kernel 6.8.x, which are not compatible with the running 6.15.7+ kernel.
What is needed
To proceed, I need one of the following options:
1 - The full kernel source tree used to build kernel 6.15.7+ for the Dragon Q6A
- Including the exact .config used
OR
2 - A matching kernel headers / build artifacts package for kernel 6.15.7+, containing at least:
- Module.symvers
- include/ (generated headers)
- scripts/ (modpost, etc.)
- Correct kernel.release (6.15.7+)
OR
3 - If available, a prebuilt camera BSP or IMX586 driver compatible with the Radxa Q6A / QCS6490 platform.
Why this is required
Without the matching kernel build artifacts, it is technically impossible to:
- Build out-of-tree kernel modules
- Load sensor drivers (vermagic mismatch / unresolved symbols)
This blocks camera sensor bring-up on the platform.
Summary
- Kernel 6.15.7+ is running correctly on the board
- Kernel headers/build artifacts for this version are missing
- External driver development is blocked without them
Any guidance or access to the correct kernel sources or headers would be greatly appreciated.
Thank you for your support.