# Radxa zero 3W with OV5647 not “working”
**URL:** https://dietpi.com/forum/t/radxa-zero-3w-with-ov5647-not-working/25412
**Category:** General Discussion
**Created:** [14 August 2026 15:17 UTC](https://dietpi.com/forum/t/radxa-zero-3w-with-ov5647-not-working/25412 "2026-08-14T15:17:18Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@james\_76](https://dietpi.com/forum/u/james_76)
#### Post date: [14 August 2026 15:17 UTC](https://dietpi.com/forum/t/radxa-zero-3w-with-ov5647-not-working/25412/1 "2026-08-14T15:17:18Z")
Hello,
I would like to record with OV5647 but it’s not detected.
```auto
cat /boot/dietpiEnv.txt
rootdev=UUID=179ca8f5-7f82-4c6c-8e68-7bc38b5bb0ee
rootfstype=ext4
# The init system logs to the console defined last.
consoleargs=console=ttyS2,1500000 console=tty1
extraargs=fsck.repair=yes net.ifnames=0
overlay_path=rockchip
# Multiple prefixes are supported separated by space
overlay_prefix=rockchip-rk3566 rockchip-rk3568 radxa-zero3 rk3568
overlays=npu-enable
user_overlays=radxa-zero3-rpi-camera-v1.3
dietpi@DietPi:~$ sudo dmesg | grep -Ei 'OF:|overlay|device tree|ov5647|csi|dphy'
[0.000000] OF: reserved mem: 0x000000000010f000..0x000000000010f0ff (0 KiB) nomap non-reusable shmem@10f000
[0.138116] SCSI subsystem initialized
[0.337972] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 245)
uname -r
6.18.37-current-rockchip64
```
What is the problem please?
Thank you.
---
### Author:  [@MichaIng](https://dietpi.com/forum/u/MichaIng)
#### Post date: [14 August 2026 17:06 UTC](https://dietpi.com/forum/t/radxa-zero-3w-with-ov5647-not-working/25412/2 "2026-08-14T17:06:46Z")
That `radxa-zero3-rpi-camera-v1.3` overlay does not exist in mainline Linux. You likely copied it from vendor kernel: [linux-rockchip/arch/arm64/boot/dts/rockchip/overlay/radxa-zero3-rpi-camera-v1.3.dts at 5280f9b4336199c4025c8eed894d2b4e2268dcc6 · armbian/linux-rockchip · GitHub](https://github.com/armbian/linux-rockchip/blob/5280f9b4336199c4025c8eed894d2b4e2268dcc6/arch/arm64/boot/dts/rockchip/overlay/radxa-zero3-rpi-camera-v1.3.dts)
But it contains a lot of vendor-specific symbols, like `&rkisp`, which are named differently or do not exist at all in mainline Linux. So this cannot be applied onto mainline Linux without adjusting the node references, and in case add missing ones.
Just loading the driver manually does not help, right?
```sh
modprobe ov5647
```
---
### Author:  [@james\_76](https://dietpi.com/forum/u/james_76)
#### Post date: [14 August 2026 18:10 UTC](https://dietpi.com/forum/t/radxa-zero-3w-with-ov5647-not-working/25412/3 "2026-08-14T18:10:26Z")
> [@MichaIng](#):
>
> `modprobe ov5647`
```auto
dietpi@DietPi:~$ lsmod | grep ov5647
ov5647 24576 0
v4l2_fwnode 24576 1 ov5647
v4l2_async 20480 2 v4l2_fwnode,ov5647
videodev 253952 8 rockchip_vdec,v4l2_async,v4l2_fwnode,ov5647,videobuf2_v4l2,hantro_vpu,rockchip_rga,v4l2_mem2mem
mc 53248 8 rockchip_vdec,v4l2_async,videodev,ov5647,videobuf2_v4l2,hantro_vpu,videobuf2_common,v4l2_mem2mem
dietpi@DietPi:~$ sudo dmesg | grep -Ei 'ov5647|v4l2|csi|rkcif|rkisp'
[0.138116] SCSI subsystem initialized
[0.337972] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 245)
dietpi@DietPi:~$ ls -l /dev/video* 2>/dev/null
crw-rw---- 1 root video 81, 0 Aug 14 08:33 /dev/video0
crw-rw---- 1 root video 81, 1 Aug 14 08:33 /dev/video1
crw-rw---- 1 root video 81, 2 Aug 14 08:33 /dev/video2
crw-rw---- 1 root video 81, 3 Aug 14 08:33 /dev/video3
dietpi@DietPi:~$
```
I try to load driver but it doesn’t resolve.
---
### Author:  [@MichaIng](https://dietpi.com/forum/u/MichaIng)
#### Post date: [14 August 2026 18:57 UTC](https://dietpi.com/forum/t/radxa-zero-3w-with-ov5647-not-working/25412/4 "2026-08-14T18:57:43Z")
As expected. So you need an overlay that works with mainline Linux.
If you really need to use that camera on the Radxa ZERO 3W now, downgrade to vendor kernel. But I see we do not add it to its APT component anymore. Hence download it manually
```sh
cd /tmp
wget https://dietpi.com/downloads/binaries/linux-image-vendor-rk35xx.deb
sudo apt install ./linux-image-vendor-rk35xx.deb
```
It should work, but there is a small chance that it fails to boot due to some bootloader incompatibility or so. Hence be prepared to access the SD card from another system, to change back the symlink in `/boot` to mainline kernel.
---
### Author:  [@james\_76](https://dietpi.com/forum/u/james_76)
#### Post date: [15 August 2026 07:08 UTC](https://dietpi.com/forum/t/radxa-zero-3w-with-ov5647-not-working/25412/5 "2026-08-15T07:08:53Z")
> [@MichaIng](#):
>
> ```auto
> cd /tmp
> wget https://dietpi.com/downloads/binaries/linux-image-vendor-rk35xx.deb
> sudo apt install ./linux-image-vendor-rk35xx.deb
>
> ```
I execute theses command and reboot, the boot of radxa display black screen so doesn’t boot.
---
### Author:  [@MichaIng](https://dietpi.com/forum/u/MichaIng)
#### Post date: [15 August 2026 11:14 UTC](https://dietpi.com/forum/t/radxa-zero-3w-with-ov5647-not-working/25412/6 "2026-08-15T11:14:04Z")
Ah I just see why: The device tree has a different name in the vendor kernel. So you need to access the SD card, and add
```auto
fdtfile=rockchip/rk3566-radxa-zero3.dtb
```
to `/boot/dietpiEnv.txt`.