Page 1 of 1

My Luckfox Pico Ultra W 720 RGB screen won't light up after being unresponsive for an extended period.

Posted: 2026-05-26 1:17
by HuangMingming

System: Ubuntu
Screen: RGB 720x720
Hardware: Luckfox Pico Ultra W
Problem: After flashing the official Ubuntu system, the screen failed to power on after a week of use; rebooting and powering off did not resolve the issue. After flashing the official BuildRoot firmware, the screen initially displayed white and gray bars, which returned to normal after a while. Compiling the latest GitHub image myself rendered the screen unusable.

Request: How to ensure long-term usability of the Ubuntu system?


Re: My Luckfox Pico Ultra W 720 RGB screen won't light up after being unresponsive for an extended period.

Posted: 2026-05-26 2:52
by Crocodile

Firstly, due to licensing issues, we have ceased maintenance and support for the Ubuntu system, making it impossible for us to further investigate many of the problems.
The issue where the system fails to boot after running for a period of time can typically be resolved by re-flashing the system. This is generally unrelated to kernel configuration, as most kernel configuration errors would trigger a failure on the very first boot. I suspect that a particular service or application may be enabled, causing the Ubuntu system's storage usage to continuously increase over time — for example, due to constantly generated log files. After running for an extended period, the storage space may become full, leading to the boot failure. I recommend using the journalctl tool to investigate this issue.


Re: My Luckfox Pico Ultra W 720 RGB screen won't light up after being unresponsive for an extended period.

Posted: 2026-05-27 13:42
by HuangMingming
Crocodile wrote: 2026-05-26 2:52

Firstly, due to licensing issues, we have ceased maintenance and support for the Ubuntu system, making it impossible for us to further investigate many of the problems.
The issue where the system fails to boot after running for a period of time can typically be resolved by re-flashing the system. This is generally unrelated to kernel configuration, as most kernel configuration errors would trigger a failure on the very first boot. I suspect that a particular service or application may be enabled, causing the Ubuntu system's storage usage to continuously increase over time — for example, due to constantly generated log files. After running for an extended period, the storage space may become full, leading to the boot failure. I recommend using the journalctl tool to investigate this issue.

The latest compiled buildroot SDK fails to light up the screen and reports errors when using the test program
cmd:
git clone https://github.com/LuckfoxTECH/luckfox-pico.git

cd {SDK_PATH}/tools/linux/toolchain/arm-rockchip830-linux-uclibcgnueabihf/
source env_install_toolchain.sh

./build.sh lunch

select:RV1106_Luckfox_Pico_Ultra_W

./build.sh

build log:
/home/luckfox-pico/output/image/userdata.img: 11/4096 files (0.0% non-contiguous), 9239/14498 blocks
tune2fs -m 5 /home/luckfox-pico/output/image/userdata.img
tune2fs 1.43.9 (8-Feb-2018)
Setting reserved blocks percentage to 5% (724 blocks)
resize2fs -M /home/luckfox-pico/output/image/userdata.img
resize2fs 1.43.9 (8-Feb-2018)
Resizing the filesystem on /home/luckfox-pico/output/image/userdata.img to 9765 (1k) blocks.
The filesystem on /home/luckfox-pico/output/image/userdata.img is now 9765 (1k) blocks long.

[build.sh:info] Running build_mkimg succeeded.
[build.sh:info] Running build_tftp_sd_update succeeded.
[mk-update_pack.sh:info] image input dir: /home/luckfox-pico/output/image
[mk-update_pack.sh:info] partition file name: env.img
[mk-update_pack.sh:info] start to package update.img...
[mk-update_pack.sh:info] partitions:
env env.img
idblock idblock.img
uboot uboot.img
boot boot.img
oem oem.img
userdata userdata.img
rootfs rootfs.img
package-file package-file
bootloader download.bin

TOOL_PATH=/home/luckfox-pico/tools/linux/Linux_Pack_Firmware
Android Firmware Package Tool v2.2
------ PACKAGE ------
Add file: /home/luckfox-pico/output/image/env.img
env,Add file: /home/luckfox-pico/output/image/env.img done,offset=0x800,size=0x8000,userspace=0x10,flash_address=0x00000000
Add file: /home/luckfox-pico/output/image/idblock.img
idblock,Add file: /home/luckfox-pico/output/image/idblock.img done,offset=0x8800,size=0x2e000,userspace=0x5c,flash_address=0x00000040
Add file: /home/luckfox-pico/output/image/uboot.img
uboot,Add file: /home/luckfox-pico/output/image/uboot.img done,offset=0x36800,size=0x40000,userspace=0x80,flash_address=0x00000440
Add file: /home/luckfox-pico/output/image/boot.img
boot,Add file: /home/luckfox-pico/output/image/boot.img done,offset=0x76800,size=0x3af200,userspace=0x75f,flash_address=0x00000640
Add file: /home/luckfox-pico/output/image/oem.img
oem,Add file: /home/luckfox-pico/output/image/oem.img done,offset=0x426000,size=0x25ec000,userspace=0x4bd8,flash_address=0x00010640
Add file: /home/luckfox-pico/output/image/userdata.img
userdata,Add file: /home/luckfox-pico/output/image/userdata.img done,offset=0x2a12000,size=0x989400,userspace=0x1313,flash_address=0x00110640
Add file: /home/luckfox-pico/output/image/rootfs.img
rootfs,Add file: /home/luckfox-pico/output/image/rootfs.img done,offset=0x339b800,size=0x193df000,userspace=0x327be,flash_address=0x00190640
Add file: /home/luckfox-pico/output/image/package-file
package-file,Add file: /home/luckfox-pico/output/image/package-file done,offset=0x1c77a800,size=0xa5,userspace=0x1
Add file: /home/luckfox-pico/output/image/download.bin
bootloader,Add file: /home/luckfox-pico/output/image/download.bin done,offset=0x1c77b000,size=0x419c0,userspace=0x84
Add CRC...
Make firmware OK!
------ OK ------
********rkImageMaker ver 2.2********
Generating new image, please wait...
Writing head info...
Writing boot file...
Writing firmware...
Generating MD5 data...
MD5 data generated successfully!
New image generated successfully!
[mk-update_pack.sh:info] Making -RK1106 update.img OK.
[build.sh:info] Running build_updateimg succeeded.
[build.sh:info] Running build_firmware succeeded.
[build.sh:info] Running build_all succeeded.
'uboot.debug.tar.bz2' -> '/home/luckfox-pico/IMAGE/IPC_EMMC_BUILDROOT_RV1106_LUCKFOX_PICO_ULTRA_20260527.1017_RELEASE_TEST/DEBUG_FILES/uboot/uboot.debug.tar.bz2'
make[1]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule.
make[1]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule.
make[1]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule.
make[1]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule.
make[1]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule.
make[1]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule.
make[1]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule.
save to /home/luckfox-pico/IMAGE/IPC_EMMC_BUILDROOT_RV1106_LUCKFOX_PICO_ULTRA_20260527.1017_RELEASE_TEST
[build.sh:info] Running build_save succeeded.
[build.sh:info] Running build_allsave succeeded.

After burning the latest image, the screen still cannot be lit up and an error message appears when executing the test program.

adb shell "modetest -M rockchip -s 70@66:720x720"
setting mode 720x720-48.87Hz on connectors 70, crtc 66
failed to set gamma: Invalid argument


Re: My Luckfox Pico Ultra W 720 RGB screen won't light up after being unresponsive for an extended period.

Posted: 2026-05-28 1:13
by Crocodile

By default, all mirror images have the boot logo display enabled. If even the logo does not appear, running modetest will have no effect. Please check whether the screen has backlight in a low-brightness environment, and use evtest to verify if the touch functionality is working properly.


Re: My Luckfox Pico Ultra W 720 RGB screen won't light up after being unresponsive for an extended period.

Posted: 2026-06-18 14:44
by brosce

If even the boot logo doesn’t show, this points more to display initialization or hardware than the firmware build itself. Check the backlight, cable connection, and whether touch still works with evtest that should narrow it down fast.Broken Display