<![CDATA[PINE64 - General Discussion on ROCKPRO64]]> https://forum.pine64.org/ Tue, 12 May 2026 06:38:01 +0000 MyBB <![CDATA[installed devuan 5/6 - missing out on resolution]]> https://forum.pine64.org/showthread.php?tid=20196 Fri, 20 Feb 2026 17:36:42 +0000 kapqa]]> https://forum.pine64.org/showthread.php?tid=20196
hjae installed Devuan 5/6 on a newly acquired RockPro64 -
very pleased overall with the system

https://devuan.bio.lmu.de/devuan/dists/d...rd-images/
https://devuan.bio.lmu.de/devuan/dists/e...ard-images

however iam missing out on resolutions,
since xrandr is reporting only resolutions on 16:9 format, however my monitor are mostly in 16:10;

do i need additional driver or firmware?

devuan is a derivative of debian, so devuan 5 iscorresponding to debian 12
devuan 6 to debian 13 trixie roughly.



thank you very much.]]>
hjae installed Devuan 5/6 on a newly acquired RockPro64 -
very pleased overall with the system

https://devuan.bio.lmu.de/devuan/dists/d...rd-images/
https://devuan.bio.lmu.de/devuan/dists/e...ard-images

however iam missing out on resolutions,
since xrandr is reporting only resolutions on 16:9 format, however my monitor are mostly in 16:10;

do i need additional driver or firmware?

devuan is a derivative of debian, so devuan 5 iscorresponding to debian 12
devuan 6 to debian 13 trixie roughly.



thank you very much.]]> <![CDATA[(real) Mainline U-boot finally works on SPI, boots SATA, throw away your SD cards NOW]]> https://forum.pine64.org/showthread.php?tid=19868 Sat, 21 Jun 2025 12:21:32 +0000 aleksei]]> https://forum.pine64.org/showthread.php?tid=19868

Build ATF:


Code:
git clone --depth=1 -b v2.13.0 https://github.com/ARM-software/arm-trusted-firmware.git
make -j $(nproc) CC=gcc PLAT=rk3399 bl31
Build U-boot:


Code:
git clone --depth=1 -b v2025.04 https://source.denx.de/u-boot/u-boot.git
export BL31=/path/to/built/bl31.elf
make mrproper && make rockpro64-rk3399_defconfig
make menuconfig
Here are the changed variables in .config, but don't just copy them to your .config - search for them in menuconfig and change there, the menu will take care of dependencies.




Code:
CONFIG_BOOTDELAY=20
CONFIG_BOOTCOMMAND="bootflow scan -lbm"
CONFIG_CMD_ERASEENV=y
CONFIG_CMD_NVEDIT_LOAD=y
CONFIG_NO_NET=y
CONFIG_BAUDRATE=115200
CONFIG_USE_PREBOOT=y
CONFIG_PREBOOT="usb start"
CONFIG_PREBOOT_DEFINED=y

make -j $(nproc)
Writing to SD card first to test it (from doc/README.rockchip in U-boot source, "Option 3: Package the image with TPL"):







Code:
dd if=idbloader.img of=/dev/sdX seek=64
dd if=u-boot.itb of=/dev/sdX seek=16384
sync


Flashing to SPI is much simpler nowadays, see doc/board/rockchip/rockchip.rst in U-boot source. Create a partition with FAT filesystem on the same SD card, place u-boot-rockchip-spi.bin on it, reboot, get to U-boot cmdline and:



Code:
sf probe
load mmc 1:1 $kernel_addr_r u-boot-rockchip-spi.bin
sf update $fileaddr 0 $filesize
If sf probe returns an error or booting from SPI fails, short pins 23 and 25 on GPIO to temporarily disable SPI. After booting disconnect them again and erase SPI to at least get SD boot working.




U-boot environment section on SPI might be empty, broken or contain wrong variables. To get default environment for installed version of U-boot, remove situational partitions variable and save the environment to SPI, run in U-boot cmdline:




Code:
env default -a
env delete partitions
env save


Then create EFI partition on SATA disk and proceed like with a regular UEFI machine. U-boot from SPI will also scan SATA partitions for extlinux/extlinux.conf, boot.scr and other U-boot-specific boot configs.



* On Arch, pacman -U these 3 pkgs from Manjaro (choose a mirror close to you) to build ATF:




https://mirror.truenetwork.ru/manjaro/ar...kg.tar.zst


https://mirror.truenetwork.ru/manjaro/ar...kg.tar.zst



https://mirror.truenetwork.ru/manjaro/ar...kg.tar.zst



PS Screw this forum software inserting copious newlines on every press of preview button.]]>

Build ATF:


Code:
git clone --depth=1 -b v2.13.0 https://github.com/ARM-software/arm-trusted-firmware.git
make -j $(nproc) CC=gcc PLAT=rk3399 bl31
Build U-boot:


Code:
git clone --depth=1 -b v2025.04 https://source.denx.de/u-boot/u-boot.git
export BL31=/path/to/built/bl31.elf
make mrproper && make rockpro64-rk3399_defconfig
make menuconfig
Here are the changed variables in .config, but don't just copy them to your .config - search for them in menuconfig and change there, the menu will take care of dependencies.




Code:
CONFIG_BOOTDELAY=20
CONFIG_BOOTCOMMAND="bootflow scan -lbm"
CONFIG_CMD_ERASEENV=y
CONFIG_CMD_NVEDIT_LOAD=y
CONFIG_NO_NET=y
CONFIG_BAUDRATE=115200
CONFIG_USE_PREBOOT=y
CONFIG_PREBOOT="usb start"
CONFIG_PREBOOT_DEFINED=y

make -j $(nproc)
Writing to SD card first to test it (from doc/README.rockchip in U-boot source, "Option 3: Package the image with TPL"):







Code:
dd if=idbloader.img of=/dev/sdX seek=64
dd if=u-boot.itb of=/dev/sdX seek=16384
sync


Flashing to SPI is much simpler nowadays, see doc/board/rockchip/rockchip.rst in U-boot source. Create a partition with FAT filesystem on the same SD card, place u-boot-rockchip-spi.bin on it, reboot, get to U-boot cmdline and:



Code:
sf probe
load mmc 1:1 $kernel_addr_r u-boot-rockchip-spi.bin
sf update $fileaddr 0 $filesize
If sf probe returns an error or booting from SPI fails, short pins 23 and 25 on GPIO to temporarily disable SPI. After booting disconnect them again and erase SPI to at least get SD boot working.




U-boot environment section on SPI might be empty, broken or contain wrong variables. To get default environment for installed version of U-boot, remove situational partitions variable and save the environment to SPI, run in U-boot cmdline:




Code:
env default -a
env delete partitions
env save


Then create EFI partition on SATA disk and proceed like with a regular UEFI machine. U-boot from SPI will also scan SATA partitions for extlinux/extlinux.conf, boot.scr and other U-boot-specific boot configs.



* On Arch, pacman -U these 3 pkgs from Manjaro (choose a mirror close to you) to build ATF:




https://mirror.truenetwork.ru/manjaro/ar...kg.tar.zst


https://mirror.truenetwork.ru/manjaro/ar...kg.tar.zst



https://mirror.truenetwork.ru/manjaro/ar...kg.tar.zst



PS Screw this forum software inserting copious newlines on every press of preview button.]]> <![CDATA[where to get debian 12 image for rockpro64?]]> https://forum.pine64.org/showthread.php?tid=19836 Sun, 18 May 2025 16:35:44 +0000 heocb]]> https://forum.pine64.org/showthread.php?tid=19836 <![CDATA[Need help with spi incircuit programming]]> https://forum.pine64.org/showthread.php?tid=19776 Thu, 03 Apr 2025 18:40:50 +0000 wofei]]> https://forum.pine64.org/showthread.php?tid=19776 I have a rockpro64 V2.1 board with no reaction. Neither serial output, nor any blinking leds after power on. Now i want to flash the u-boot to to the spi chip for trying to boot from usb. Unfortunatley, the sd- and the emmc ports are not available, fixed with glue. (the rockpro is build in a test equipment for cars, bought 4 years ago from my cousin for about 4000 euros, these days was the first try, but this thing is dead, warranty is over and repair from the reseller is not possible)
Is there a way to flash the spi in circuit with the available *-img files? I can read and write the spi chip with my raspberry, but i can´t find a rom file, only img files..
thanks, wofei]]> I have a rockpro64 V2.1 board with no reaction. Neither serial output, nor any blinking leds after power on. Now i want to flash the u-boot to to the spi chip for trying to boot from usb. Unfortunatley, the sd- and the emmc ports are not available, fixed with glue. (the rockpro is build in a test equipment for cars, bought 4 years ago from my cousin for about 4000 euros, these days was the first try, but this thing is dead, warranty is over and repair from the reseller is not possible)
Is there a way to flash the spi in circuit with the available *-img files? I can read and write the spi chip with my raspberry, but i can´t find a rom file, only img files..
thanks, wofei]]> <![CDATA[Use android on RockPro64 without a LCD screen ?]]> https://forum.pine64.org/showthread.php?tid=19764 Sat, 29 Mar 2025 05:15:11 +0000 john_nash]]> https://forum.pine64.org/showthread.php?tid=19764 https://wiki.pine64.org/wiki/ROCKPro64_S...es#Android
But I don't have a LCD screen. Anyway I can use it without one ? I wish to control it from my PC, through scrcpy program. But this program need Android to enable usb debugging. Which again need LCD to enable manually.]]> https://wiki.pine64.org/wiki/ROCKPro64_S...es#Android
But I don't have a LCD screen. Anyway I can use it without one ? I wish to control it from my PC, through scrcpy program. But this program need Android to enable usb debugging. Which again need LCD to enable manually.]]> <![CDATA[Rock Pro 64 Won't power on]]> https://forum.pine64.org/showthread.php?tid=19730 Tue, 11 Mar 2025 21:49:12 +0000 matthewmkr]]> https://forum.pine64.org/showthread.php?tid=19730 https://github.com/ayufan-rock64/linux-b...ash-spi.md , but it won't power on, so I doubt it's doing anything.

Tried following this advice as well and still nada https://www.reddit.com/r/PINE64official/...mc_or_usd/


Video of symptoms: https://youtube.com/shorts/jDHW6B4bH5g?feature=share]]> https://github.com/ayufan-rock64/linux-b...ash-spi.md , but it won't power on, so I doubt it's doing anything.

Tried following this advice as well and still nada https://www.reddit.com/r/PINE64official/...mc_or_usd/


Video of symptoms: https://youtube.com/shorts/jDHW6B4bH5g?feature=share]]> <![CDATA[How to use ROCKPro64 PCI-e X4 to M.2/NGFF NVMe SSD Interface Card]]> https://forum.pine64.org/showthread.php?tid=19527 Sat, 23 Nov 2024 14:15:46 +0000 jykeith123]]> https://forum.pine64.org/showthread.php?tid=19527 I connected a PCI NVMe adapter to the RockPro64, but nothing is added to 
Code:
/dev/sd*
 or 
Code:
/dev/nvme*
. The products I tested are as follows:


PM9A1 500GB
FireCuda530 2TB

What could be the problem?

os : Armbian_24.5.1_Rockpro64_noble_current_6.6.31]]> I connected a PCI NVMe adapter to the RockPro64, but nothing is added to 
Code:
/dev/sd*
 or 
Code:
/dev/nvme*
. The products I tested are as follows:


PM9A1 500GB
FireCuda530 2TB

What could be the problem?

os : Armbian_24.5.1_Rockpro64_noble_current_6.6.31]]> <![CDATA[No HDMI Video - Anything To Check?]]> https://forum.pine64.org/showthread.php?tid=19433 Wed, 25 Sep 2024 10:58:51 +0000 angrymallard]]> https://forum.pine64.org/showthread.php?tid=19433
I've tried a few other images as well, LibreELEC (originally I planned for this to be a media center so this was the first one I tried), a few different Armbian images including the XFCE Debian 12 version, the Cinnamon Debian 12 version, the Ubuntu Gnome version, and DietPi. I can't verify that any of these work, although I am pretty certain that these have SSH access disabled by default and without video there's no way for me to enable that to check on these distributions. I also used the "flash_spi" image here https://github.com/sigmaris/u-boot/wiki/...oot-to-SPI to make sure that was working properly.

I also tried to add the kernel module from this guide https://wiki.pine64.org/wiki/ROCKPro64#N..._on_Debian but it seems like my problem is happening before the kernel loads since there's no video output at all when it boots in the first place.

Since I can boot and SSH into the minimal Armbian install, is there anything I should check before I send this unit back? I don't currently have a serial cable but hope that since I can SSH into a terminal I won't need one for looking around at anything.]]>
I've tried a few other images as well, LibreELEC (originally I planned for this to be a media center so this was the first one I tried), a few different Armbian images including the XFCE Debian 12 version, the Cinnamon Debian 12 version, the Ubuntu Gnome version, and DietPi. I can't verify that any of these work, although I am pretty certain that these have SSH access disabled by default and without video there's no way for me to enable that to check on these distributions. I also used the "flash_spi" image here https://github.com/sigmaris/u-boot/wiki/...oot-to-SPI to make sure that was working properly.

I also tried to add the kernel module from this guide https://wiki.pine64.org/wiki/ROCKPro64#N..._on_Debian but it seems like my problem is happening before the kernel loads since there's no video output at all when it boots in the first place.

Since I can boot and SSH into the minimal Armbian install, is there anything I should check before I send this unit back? I don't currently have a serial cable but hope that since I can SSH into a terminal I won't need one for looking around at anything.]]> <![CDATA[power button not working]]> https://forum.pine64.org/showthread.php?tid=19212 Wed, 08 May 2024 05:26:55 +0000 Vista8720]]> https://forum.pine64.org/showthread.php?tid=19212 thanks]]> thanks]]> <![CDATA[Installing Wifi drive for the RockPro64]]> https://forum.pine64.org/showthread.php?tid=19051 Sun, 11 Feb 2024 05:32:20 +0000 John45595]]> https://forum.pine64.org/showthread.php?tid=19051
At present I have tried formatting a USB stick to FAT32 and adding the files from here to a folder named "firmware" on the USB stick however the installer can not identify these files and keeps throwing an error stating the following files are missing:

brim/brcmfmac43455-sdio.bin
brim/brcmfmac43455-sdio.pine64,rockpro64-v2.1.bin

I can't install the OS without getting the wifi working so I am not entirely sure how to go about rectifying this problem. Does anyone have any suggestions? Should I be using a different OS? Is it a requirement to have a wired internet connection when you first install Debian?

If there are no other options I can go somewhere with a wired connection and install the OS and try and get the wifi firmware installed once the OS is already installed however I would like to avoid that if possible.]]>
At present I have tried formatting a USB stick to FAT32 and adding the files from here to a folder named "firmware" on the USB stick however the installer can not identify these files and keeps throwing an error stating the following files are missing:

brim/brcmfmac43455-sdio.bin
brim/brcmfmac43455-sdio.pine64,rockpro64-v2.1.bin

I can't install the OS without getting the wifi working so I am not entirely sure how to go about rectifying this problem. Does anyone have any suggestions? Should I be using a different OS? Is it a requirement to have a wired internet connection when you first install Debian?

If there are no other options I can go somewhere with a wired connection and install the OS and try and get the wifi firmware installed once the OS is already installed however I would like to avoid that if possible.]]> <![CDATA[Another Fan Question]]> https://forum.pine64.org/showthread.php?tid=19034 Fri, 02 Feb 2024 14:32:43 +0000 backwoodstech2]]> https://forum.pine64.org/showthread.php?tid=19034
Plugging it in I get nothing...no fan movement at all. I'm using a recent version of Armbian if that matters.

I believe I see this device under /sys/class/hwmon/hwmon4/ since is see pwm1 as well as pwm1_enable. 

Code:
cat /sys/class/hwmon/hwmon4/pwm1_enable

returns 1 


Code:
/sys/class/hwmon/hwmon4$ cat /sys/class/hwmon/hwmon4/pwm1

returns 0

Code:
echo 255 | sudo tee /sys/class/hwmon/hwmon4/pwm1

still no fan response

Code:
cat /sys/class/hwmon/hwmon4/pwm1
to verify my adjustment but this still returns 0. Fan is motionless.

At this point i'm ready to give up and connect to the boards 12v out but I have questions there.

The original cable it comes with splits to 2 different SATA connection leads, leading me to believe this is not a conventional connection? This is for the CON15 DC out header.

the Noctua includes a big 4pin adapter but I'm not confident in what to order. I also didn't see anything relevant in the Pine store for accessories. 

FYI I'm currently not running any SATA drives as I recently opted for NVMe (mostly due to availability).

any help please!!??]]>
Plugging it in I get nothing...no fan movement at all. I'm using a recent version of Armbian if that matters.

I believe I see this device under /sys/class/hwmon/hwmon4/ since is see pwm1 as well as pwm1_enable. 

Code:
cat /sys/class/hwmon/hwmon4/pwm1_enable

returns 1 


Code:
/sys/class/hwmon/hwmon4$ cat /sys/class/hwmon/hwmon4/pwm1

returns 0

Code:
echo 255 | sudo tee /sys/class/hwmon/hwmon4/pwm1

still no fan response

Code:
cat /sys/class/hwmon/hwmon4/pwm1
to verify my adjustment but this still returns 0. Fan is motionless.

At this point i'm ready to give up and connect to the boards 12v out but I have questions there.

The original cable it comes with splits to 2 different SATA connection leads, leading me to believe this is not a conventional connection? This is for the CON15 DC out header.

the Noctua includes a big 4pin adapter but I'm not confident in what to order. I also didn't see anything relevant in the Pine store for accessories. 

FYI I'm currently not running any SATA drives as I recently opted for NVMe (mostly due to availability).

any help please!!??]]> <![CDATA[Overclock of RAM, CPU and GPU]]> https://forum.pine64.org/showthread.php?tid=18959 Wed, 20 Dec 2023 15:54:32 +0000 Maxpako]]> https://forum.pine64.org/showthread.php?tid=18959
For those who wants to take out the most performance out of the rk3399 on your RockPro64, I have here a u-boot and a DTS where on Manjaro works perfectly.

This includes a 1.6GHz on the little cores, a 2.2GHz on the big cores, and 1GHz on the GPU, as well as setting the RAM to 933MHz LPDDR4.

Please find it on the Pine64 > rock64 discord channel:
https://discord.com/channels/46323792798...1534507058

Here are the gains:
[Image: image.png?ex=659315e6&is=6580a0e6&hm=8c1...height=165]
GPU and CPU stressed out in a roshambo case, no more than 70ºC.

Unfortunately, on Batocera which I'm most interested, there's no audio using this u-boot.
Any help will be appreciated to fix this on Batocera.

Please note that it's not my work, I just followed these threads and info available:
=> https://forum.pine64.org/showthread.php?tid=13506
https://wiki.pine64.org/wiki/ROCKPro64_H...g_the_RAM)
So, credits to them.]]>
For those who wants to take out the most performance out of the rk3399 on your RockPro64, I have here a u-boot and a DTS where on Manjaro works perfectly.

This includes a 1.6GHz on the little cores, a 2.2GHz on the big cores, and 1GHz on the GPU, as well as setting the RAM to 933MHz LPDDR4.

Please find it on the Pine64 > rock64 discord channel:
https://discord.com/channels/46323792798...1534507058

Here are the gains:
[Image: image.png?ex=659315e6&is=6580a0e6&hm=8c1...height=165]
GPU and CPU stressed out in a roshambo case, no more than 70ºC.

Unfortunately, on Batocera which I'm most interested, there's no audio using this u-boot.
Any help will be appreciated to fix this on Batocera.

Please note that it's not my work, I just followed these threads and info available:
=> https://forum.pine64.org/showthread.php?tid=13506
https://wiki.pine64.org/wiki/ROCKPro64_H...g_the_RAM)
So, credits to them.]]> <![CDATA[SPI]]> https://forum.pine64.org/showthread.php?tid=18923 Sun, 03 Dec 2023 14:23:30 +0000 hazz]]> https://forum.pine64.org/showthread.php?tid=18923 I'm able to boot the netbsd emmc only shorting the pin 20-21.How can i reset as a default spi?
I do not want to connect via the serial console but just run the NETBSD 10RC1 and connect via ssh
Any tips would be very appreciated]]> I'm able to boot the netbsd emmc only shorting the pin 20-21.How can i reset as a default spi?
I do not want to connect via the serial console but just run the NETBSD 10RC1 and connect via ssh
Any tips would be very appreciated]]> <![CDATA[Max Resolution Supported by RP64?]]> https://forum.pine64.org/showthread.php?tid=18798 Mon, 16 Oct 2023 17:13:57 +0000 hoarfrosty]]> https://forum.pine64.org/showthread.php?tid=18798
However my RockPro64 with Linux is only able to reach 1920x1080 @ 120 Hz. Ive tried multiple distros (Manjaro, Arch, Ubuntu, Debian, and Armbian Twister). I'm back on Manjaro now, as that runs the smoothest (YMMV). It correctly identifies the model of the display, but doesn't offer higher resolutions and I'm stuck with black bars on the sides of my screen.

In the RockPro64 specs it says the following:
Dual VOP: one supports resolutions up to 4096x2160 and AFBC; the other supports resolutions up to 2560x1600

So, I wonder if there is a way to use the larger VOP and reach the 3440x1440 resolution? Or am I just trying to push this little board beyond its limits?

I've gone through several unsuccessful attempts at adding the resolution using xrandr (addmode, output, etc.).

Here is some more info, and a EDID file I found on GitHub, but haven't been able to use.

Code:
$ cvt 3440 1400 100
# 3440x1400 99.96 Hz (CVT) hsync: 148.44 kHz; pclk: 707.75 MHz
Modeline "3440x1400_100.00"  707.75  3440 3728 4104 4768  1400 1403 1413 1485 -hsync +vsync
Code:
$ xrandr -q
Screen 0: minimum 16 x 16, current 1920 x 1080, maximum 32767 x 32767
HDMI-A-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 810mm x 350mm
   1920x1080     59.96*+
   1440x1080     59.99 
   1400x1050     59.98 
   1280x1024     59.89 
   1280x960      59.94 
   1152x864      59.96 
   1024x768      59.92 
   800x600       59.86 
   640x480       59.38 
   320x240       59.52 
   1680x1050     59.95 
   1440x900      59.89 
   1280x800      59.81 
   1152x720      59.97 
   960x600       59.63 
   928x580       59.88 
   800x500       59.50 
   768x480       59.90 
   720x480       59.71 
   640x400       59.95 
   320x200       58.96 
   1600x900      59.95 
   1368x768      59.88 
   1280x720      59.86 
   1024x576      59.90 
   864x486       59.92 
   720x400       59.55 
   640x350       59.77

Code:
Monitor Asset Manager Report, generated 29.4.2023
Copyright (c) 1995-2019, EnTech Taiwan.
---------------------------

Monitor #1 [Real-time 0x0100]
  Model name............... Dell AW3423DW
  Manufacturer............. Dell
  Plug and Play ID......... DELA1E4
  Serial number............
  Manufacture date......... 2022, ISO week 42
  Filter driver............ None
  -------------------------
  EDID revision............ 1.4
  Input signal type........ Digital (DisplayPort)
  Color bit depth.......... 10 bits per primary color
  Color encoding formats... RGB 4:4:4, YCrCb 4:4:4, YCrCb 4:2:2
  Screen size.............. 810 x 350 mm (34.7 in)
  Power management......... Active off/sleep
  Extension blocs.......... 2
  -------------------------
  DDC/CI................... Supported
  MCCS revison............. 2.2
  Display technology....... TFT
  Controller............... Unknown
  Firmware revision........ 2.166
  Firmware flags........... 0x0010FFFF
  Active power on time..... 1117 hours
  Power consumption........ Not supported
  Current frequency........ 182.83kHz, 120.00Hz

Color characteristics
  Default color space...... Non-sRGB
  Display gamma............ 2.20
  Red chromaticity......... Rx 0.690 - Ry 0.304
  Green chromaticity....... Gx 0.241 - Gy 0.715
  Blue chromaticity........ Bx 0.146 - By 0.057
  White point (default).... Wx 0.313 - Wy 0.329
  Additional descriptors... None

Timing characteristics
  Horizontal scan range.... 255-255kHz
  Vertical scan range...... 1-175Hz
  Video bandwidth.......... 990MHz
  CVT standard............. Not supported
  GTF standard............. Supported
  Additional descriptors... None
  Preferred timing......... Yes
  Native/preferred timing.. 3440x1440p at 60Hz
    Modeline............... "3440x1440" 319.750 3440 3488 3520 3600 1440 1473 1478 1481 +hsync -vsync

Standard timings supported
     640 x  480p at  60Hz - IBM VGA
     800 x  600p at  60Hz - VESA
    1024 x  768p at  60Hz - VESA

EIA/CEA/CTA-861 Information
  Revision number.......... 3
  IT underscan............. Supported
  Basic audio.............. Supported
  YCbCr 4:4:4.............. Supported
  YCbCr 4:2:2.............. Supported
  Native formats........... 1
  Detailed timing #1....... 3440x1440p at 100Hz
    Modeline............... "3440x1440" 543.500 3440 3488 3520 3600 1440 1502 1507 1510 +hsync -vsync

CE audio data (formats supported)
  LPCM    2-channel, 16-bit              at 32/44/48 kHz

CE speaker allocation data
  Channel configuration.... 2.0
  Front left/right......... Yes
  Front LFE................ No
  Front center............. No
  Rear left/right.......... No
  Rear center.............. No
  Front left/right center.. No
  Rear left/right center... No
  Rear LFE................. No

CE vendor specific data (VSDB)
  IEEE registration number. 0x00044B
  CEC physical address..... 0.1.0.1
  Maximum TMDS clock....... 165MHz

CE colorimetry data
  xvYCC601 support......... No
  xvYCC709 support......... No
  sYCC601 support.......... No
  AdobeYCC601 support...... No
  AdobeRGB support......... No
  BT2020CYCC support....... No
  BT2020YCC support........ Yes
  BT2020RGB support........ Yes
  Metadata profile flags... 0x00

CE video capability data
  CE scan behavior......... Always underscanned
  IT scan behavior......... Always underscanned
  PT scan behavior......... Always underscanned
  RGB quantization range... Selectable (via AVI YQ)
  YCC quantization range... Not supported

HDR static metadata
  SDR luminance............ Yes
  HDR luminance............ No
  SMPTE ST2084............. Yes
  Hybrid log............... No
  Data payload............. 0605018D4B00

Report information
  Date generated........... 29.4.2023
  Software revision........ 2.91.0.1043
  Data source.............. Real-time 0x0100
  Operating system......... 10.0.19045.2

Raw data
  00,FF,FF,FF,FF,FF,FF,00,10,AC,E4,A1,53,41,36,30,2A,20,01,04,B5,51,23,78,3B,FC,A1,B0,4D,3D,B7,25,
  0E,50,54,21,08,00,01,01,01,01,01,01,01,01,01,01,01,01,01,01,01,01,E7,7C,70,A0,D0,A0,29,50,30,20,
  15,08,29,62,31,00,00,1A,00,00,00,FF,00,23,47,37,51,59,4D,78,67,77,41,42,31,43,00,00,00,FD,00,01,
  AF,FF,FF,63,01,0A,20,20,20,20,20,20,00,00,00,FC,00,44,65,6C,6C,20,41,57,33,34,32,33,44,57,02,08,
  02,03,20,F1,23,09,07,01,83,01,00,00,65,4B,04,00,01,01,E3,05,C0,00,E2,00,6A,E6,06,05,01,8D,4B,00,
  4E,D4,70,A0,D0,A0,46,50,30,20,E5,0C,29,62,31,00,00,1A,00,00,00,00,00,00,00,00,00,00,00,00,00,00,
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,6F

---------------------------

Hardware data
  BUS_SLOT = PCI00000.PCI00004.PCI00008.PCI0000C.PCI00010.PCI00014.PCI00018.PCI0001C
  00000000 = 14801022.00000000.06000000.00800000.00000000.00000000.00000000.00000000
  00000008 = 14821022.00000000.06000000.00800000.00000000.00000000.00000000.00000000
  00000009 = 14831022.00100406.06040000.00810010.00000000.00000000.00010100.000001F1
  0000000A = 14831022.00100407.06040000.00810010.00000000.00000000.00080200.2000F1F1
  00000010 = 14821022.00000000.06000000.00800000.00000000.00000000.00000000.00000000
  00000018 = 14821022.00000000.06000000.00800000.00000000.00000000.00000000.00000000
  00000019 = 14831022.00100406.06040000.00810010.00000000.00000000.00090900.000001F1
  0000001A = 14831022.00100407.06040000.00810010.00000000.00000000.000A0A00.2000E1E1
  00000020 = 14821022.00000000.06000000.00800000.00000000.00000000.00000000.00000000
  00000028 = 14821022.00000000.06000000.00800000.00000000.00000000.00000000.00000000
  00000038 = 14821022.00000000.06000000.00800000.00000000.00000000.00000000.00000000
  00000039 = 14841022.00100404.06040000.00810010.00000000.00000000.000B0B00.000001F1
  00000040 = 14821022.00000000.06000000.00800000.00000000.00000000.00000000.00000000
  00000041 = 14841022.00100406.06040000.00810010.00000000.00000000.000C0C00.000001F1
  000000A0 = 790B1022.02200403.0C050061.00800000.00000000.00000000.00000000.00000000
  000000A3 = 790E1022.0220000F.06010051.00800000.00000000.00000000.00000000.00000000
  000000C0 = 14401022.00000000.06000000.00800000.00000000.00000000.00000000.00000000
  000000C1 = 14411022.00000000.06000000.00800000.00000000.00000000.00000000.00000000
  000000C2 = 14421022.00000000.06000000.00800000.00000000.00000000.00000000.00000000
  000000C3 = 14431022.00000000.06000000.00800000.00000000.00000000.00000000.00000000
  000000C4 = 14441022.00000000.06000000.00800000.00000000.00000000.00000000.00000000
  000000C5 = 14451022.00000000.06000000.00800000.00000000.00000000.00000000.00000000
  000000C6 = 14461022.00000000.06000000.00800000.00000000.00000000.00000000.00000000
  000000C7 = 14471022.00000000.06000000.00800000.00000000.00000000.00000000.00000000
  00000100 = 50161987.00100406.01080201.00000010.FCF00004.00000000.00000000.00000000
  00000200 = 57AD1022.00100407.06040000.00010010.00000000.00000000.00080302.0000F1F1
  00000328 = 57A31022.00100407.06040000.00810010.00000000.00000000.00040403.0000F1F1
  00000330 = 57A31022.00100406.06040000.00810010.00000000.00000000.00050503.000001F1
  00000340 = 57A41022.00100406.06040000.00810010.00000000.00000000.00060603.000001F1
  00000348 = 57A41022.00100406.06040000.00810010.00000000.00000000.00070703.000001F1
  00000350 = 57A41022.00100406.06040000.00810010.00000000.00000000.00080803.000001F1
  00000400 = 15398086.00100406.02000003.00000010.FCB00000.00000000.00000001.FCB20000
  00000500 = 00121102.00100006.04030001.00000010.FCAFC004.00000000.FCAF8004.00000000
  00000600 = 14851022.00100404.13000000.00800010.00000000.00000000.00000000.00000000
  00000601 = 149C1022.00100406.0C033000.00800010.FC700004.00000000.00000000.00000000
  00000603 = 149C1022.00100406.0C033000.00800010.FC600004.00000000.00000000.00000000
  00000700 = 79011022.00100406.01060151.00000010.00000000.00000000.00000000.00000000
  00000800 = 79011022.00100406.01060151.00000010.00000000.00000000.00000000.00000000
  00000900 = 43A014E4.00100006.02800003.00000010.FC4F8004.00000000.FC200004.00000000
  00000A00 = 220810DE.00100407.030000A1.00800010.FB000000.0000000C.00000078.0000000C
  00000A01 = 1AEF10DE.00100006.040300A1.00800010.FC0FC000.00000000.00000000.00000000
  00000B00 = 148A1022.00100404.13000000.00000010.00000000.00000000.00000000.00000000
  00000C00 = 14851022.00100404.13000000.00800010.00000000.00000000.00000000.00000000
  00000C01 = 14861022.00100400.10800000.00800010.00000000.00000000.FCE00000.00000000
  00000C03 = 149C1022.00100406.0C033000.00800010.FCC00004.00000000.00000000.00000000
  00000C04 = 14871022.00100006.04030000.00800010.FCDF0000.00000000.00000000.00000000
  --------
]]>
However my RockPro64 with Linux is only able to reach 1920x1080 @ 120 Hz. Ive tried multiple distros (Manjaro, Arch, Ubuntu, Debian, and Armbian Twister). I'm back on Manjaro now, as that runs the smoothest (YMMV). It correctly identifies the model of the display, but doesn't offer higher resolutions and I'm stuck with black bars on the sides of my screen.

In the RockPro64 specs it says the following:
Dual VOP: one supports resolutions up to 4096x2160 and AFBC; the other supports resolutions up to 2560x1600

So, I wonder if there is a way to use the larger VOP and reach the 3440x1440 resolution? Or am I just trying to push this little board beyond its limits?

I've gone through several unsuccessful attempts at adding the resolution using xrandr (addmode, output, etc.).

Here is some more info, and a EDID file I found on GitHub, but haven't been able to use.

Code:
$ cvt 3440 1400 100
# 3440x1400 99.96 Hz (CVT) hsync: 148.44 kHz; pclk: 707.75 MHz
Modeline "3440x1400_100.00"  707.75  3440 3728 4104 4768  1400 1403 1413 1485 -hsync +vsync
Code:
$ xrandr -q
Screen 0: minimum 16 x 16, current 1920 x 1080, maximum 32767 x 32767
HDMI-A-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 810mm x 350mm
   1920x1080     59.96*+
   1440x1080     59.99 
   1400x1050     59.98 
   1280x1024     59.89 
   1280x960      59.94 
   1152x864      59.96 
   1024x768      59.92 
   800x600       59.86 
   640x480       59.38 
   320x240       59.52 
   1680x1050     59.95 
   1440x900      59.89 
   1280x800      59.81 
   1152x720      59.97 
   960x600       59.63 
   928x580       59.88 
   800x500       59.50 
   768x480       59.90 
   720x480       59.71 
   640x400       59.95 
   320x200       58.96 
   1600x900      59.95 
   1368x768      59.88 
   1280x720      59.86 
   1024x576      59.90 
   864x486       59.92 
   720x400       59.55 
   640x350       59.77

Code:
Monitor Asset Manager Report, generated 29.4.2023
Copyright (c) 1995-2019, EnTech Taiwan.
---------------------------

Monitor #1 [Real-time 0x0100]
  Model name............... Dell AW3423DW
  Manufacturer............. Dell
  Plug and Play ID......... DELA1E4
  Serial number............
  Manufacture date......... 2022, ISO week 42
  Filter driver............ None
  -------------------------
  EDID revision............ 1.4
  Input signal type........ Digital (DisplayPort)
  Color bit depth.......... 10 bits per primary color
  Color encoding formats... RGB 4:4:4, YCrCb 4:4:4, YCrCb 4:2:2
  Screen size.............. 810 x 350 mm (34.7 in)
  Power management......... Active off/sleep
  Extension blocs.......... 2
  -------------------------
  DDC/CI................... Supported
  MCCS revison............. 2.2
  Display technology....... TFT
  Controller............... Unknown
  Firmware revision........ 2.166
  Firmware flags........... 0x0010FFFF
  Active power on time..... 1117 hours
  Power consumption........ Not supported
  Current frequency........ 182.83kHz, 120.00Hz

Color characteristics
  Default color space...... Non-sRGB
  Display gamma............ 2.20
  Red chromaticity......... Rx 0.690 - Ry 0.304
  Green chromaticity....... Gx 0.241 - Gy 0.715
  Blue chromaticity........ Bx 0.146 - By 0.057
  White point (default).... Wx 0.313 - Wy 0.329
  Additional descriptors... None

Timing characteristics
  Horizontal scan range.... 255-255kHz
  Vertical scan range...... 1-175Hz
  Video bandwidth.......... 990MHz
  CVT standard............. Not supported
  GTF standard............. Supported
  Additional descriptors... None
  Preferred timing......... Yes
  Native/preferred timing.. 3440x1440p at 60Hz
    Modeline............... "3440x1440" 319.750 3440 3488 3520 3600 1440 1473 1478 1481 +hsync -vsync

Standard timings supported
     640 x  480p at  60Hz - IBM VGA
     800 x  600p at  60Hz - VESA
    1024 x  768p at  60Hz - VESA

EIA/CEA/CTA-861 Information
  Revision number.......... 3
  IT underscan............. Supported
  Basic audio.............. Supported
  YCbCr 4:4:4.............. Supported
  YCbCr 4:2:2.............. Supported
  Native formats........... 1
  Detailed timing #1....... 3440x1440p at 100Hz
    Modeline............... "3440x1440" 543.500 3440 3488 3520 3600 1440 1502 1507 1510 +hsync -vsync

CE audio data (formats supported)
  LPCM    2-channel, 16-bit              at 32/44/48 kHz

CE speaker allocation data
  Channel configuration.... 2.0
  Front left/right......... Yes
  Front LFE................ No
  Front center............. No
  Rear left/right.......... No
  Rear center.............. No
  Front left/right center.. No
  Rear left/right center... No
  Rear LFE................. No

CE vendor specific data (VSDB)
  IEEE registration number. 0x00044B
  CEC physical address..... 0.1.0.1
  Maximum TMDS clock....... 165MHz

CE colorimetry data
  xvYCC601 support......... No
  xvYCC709 support......... No
  sYCC601 support.......... No
  AdobeYCC601 support...... No
  AdobeRGB support......... No
  BT2020CYCC support....... No
  BT2020YCC support........ Yes
  BT2020RGB support........ Yes
  Metadata profile flags... 0x00

CE video capability data
  CE scan behavior......... Always underscanned
  IT scan behavior......... Always underscanned
  PT scan behavior......... Always underscanned
  RGB quantization range... Selectable (via AVI YQ)
  YCC quantization range... Not supported

HDR static metadata
  SDR luminance............ Yes
  HDR luminance............ No
  SMPTE ST2084............. Yes
  Hybrid log............... No
  Data payload............. 0605018D4B00

Report information
  Date generated........... 29.4.2023
  Software revision........ 2.91.0.1043
  Data source.............. Real-time 0x0100
  Operating system......... 10.0.19045.2

Raw data
  00,FF,FF,FF,FF,FF,FF,00,10,AC,E4,A1,53,41,36,30,2A,20,01,04,B5,51,23,78,3B,FC,A1,B0,4D,3D,B7,25,
  0E,50,54,21,08,00,01,01,01,01,01,01,01,01,01,01,01,01,01,01,01,01,E7,7C,70,A0,D0,A0,29,50,30,20,
  15,08,29,62,31,00,00,1A,00,00,00,FF,00,23,47,37,51,59,4D,78,67,77,41,42,31,43,00,00,00,FD,00,01,
  AF,FF,FF,63,01,0A,20,20,20,20,20,20,00,00,00,FC,00,44,65,6C,6C,20,41,57,33,34,32,33,44,57,02,08,
  02,03,20,F1,23,09,07,01,83,01,00,00,65,4B,04,00,01,01,E3,05,C0,00,E2,00,6A,E6,06,05,01,8D,4B,00,
  4E,D4,70,A0,D0,A0,46,50,30,20,E5,0C,29,62,31,00,00,1A,00,00,00,00,00,00,00,00,00,00,00,00,00,00,
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,6F

---------------------------

Hardware data
  BUS_SLOT = PCI00000.PCI00004.PCI00008.PCI0000C.PCI00010.PCI00014.PCI00018.PCI0001C
  00000000 = 14801022.00000000.06000000.00800000.00000000.00000000.00000000.00000000
  00000008 = 14821022.00000000.06000000.00800000.00000000.00000000.00000000.00000000
  00000009 = 14831022.00100406.06040000.00810010.00000000.00000000.00010100.000001F1
  0000000A = 14831022.00100407.06040000.00810010.00000000.00000000.00080200.2000F1F1
  00000010 = 14821022.00000000.06000000.00800000.00000000.00000000.00000000.00000000
  00000018 = 14821022.00000000.06000000.00800000.00000000.00000000.00000000.00000000
  00000019 = 14831022.00100406.06040000.00810010.00000000.00000000.00090900.000001F1
  0000001A = 14831022.00100407.06040000.00810010.00000000.00000000.000A0A00.2000E1E1
  00000020 = 14821022.00000000.06000000.00800000.00000000.00000000.00000000.00000000
  00000028 = 14821022.00000000.06000000.00800000.00000000.00000000.00000000.00000000
  00000038 = 14821022.00000000.06000000.00800000.00000000.00000000.00000000.00000000
  00000039 = 14841022.00100404.06040000.00810010.00000000.00000000.000B0B00.000001F1
  00000040 = 14821022.00000000.06000000.00800000.00000000.00000000.00000000.00000000
  00000041 = 14841022.00100406.06040000.00810010.00000000.00000000.000C0C00.000001F1
  000000A0 = 790B1022.02200403.0C050061.00800000.00000000.00000000.00000000.00000000
  000000A3 = 790E1022.0220000F.06010051.00800000.00000000.00000000.00000000.00000000
  000000C0 = 14401022.00000000.06000000.00800000.00000000.00000000.00000000.00000000
  000000C1 = 14411022.00000000.06000000.00800000.00000000.00000000.00000000.00000000
  000000C2 = 14421022.00000000.06000000.00800000.00000000.00000000.00000000.00000000
  000000C3 = 14431022.00000000.06000000.00800000.00000000.00000000.00000000.00000000
  000000C4 = 14441022.00000000.06000000.00800000.00000000.00000000.00000000.00000000
  000000C5 = 14451022.00000000.06000000.00800000.00000000.00000000.00000000.00000000
  000000C6 = 14461022.00000000.06000000.00800000.00000000.00000000.00000000.00000000
  000000C7 = 14471022.00000000.06000000.00800000.00000000.00000000.00000000.00000000
  00000100 = 50161987.00100406.01080201.00000010.FCF00004.00000000.00000000.00000000
  00000200 = 57AD1022.00100407.06040000.00010010.00000000.00000000.00080302.0000F1F1
  00000328 = 57A31022.00100407.06040000.00810010.00000000.00000000.00040403.0000F1F1
  00000330 = 57A31022.00100406.06040000.00810010.00000000.00000000.00050503.000001F1
  00000340 = 57A41022.00100406.06040000.00810010.00000000.00000000.00060603.000001F1
  00000348 = 57A41022.00100406.06040000.00810010.00000000.00000000.00070703.000001F1
  00000350 = 57A41022.00100406.06040000.00810010.00000000.00000000.00080803.000001F1
  00000400 = 15398086.00100406.02000003.00000010.FCB00000.00000000.00000001.FCB20000
  00000500 = 00121102.00100006.04030001.00000010.FCAFC004.00000000.FCAF8004.00000000
  00000600 = 14851022.00100404.13000000.00800010.00000000.00000000.00000000.00000000
  00000601 = 149C1022.00100406.0C033000.00800010.FC700004.00000000.00000000.00000000
  00000603 = 149C1022.00100406.0C033000.00800010.FC600004.00000000.00000000.00000000
  00000700 = 79011022.00100406.01060151.00000010.00000000.00000000.00000000.00000000
  00000800 = 79011022.00100406.01060151.00000010.00000000.00000000.00000000.00000000
  00000900 = 43A014E4.00100006.02800003.00000010.FC4F8004.00000000.FC200004.00000000
  00000A00 = 220810DE.00100407.030000A1.00800010.FB000000.0000000C.00000078.0000000C
  00000A01 = 1AEF10DE.00100006.040300A1.00800010.FC0FC000.00000000.00000000.00000000
  00000B00 = 148A1022.00100404.13000000.00000010.00000000.00000000.00000000.00000000
  00000C00 = 14851022.00100404.13000000.00800010.00000000.00000000.00000000.00000000
  00000C01 = 14861022.00100400.10800000.00800010.00000000.00000000.FCE00000.00000000
  00000C03 = 149C1022.00100406.0C033000.00800010.FCC00004.00000000.00000000.00000000
  00000C04 = 14871022.00100006.04030000.00800010.FCDF0000.00000000.00000000.00000000
  --------
]]> <![CDATA[You don't sell case and fan for "ROCKPro64 4GB Single Board Computer"?]]> https://forum.pine64.org/showthread.php?tid=18705 Sat, 16 Sep 2023 14:44:11 +0000 Clea]]> https://forum.pine64.org/showthread.php?tid=18705
You don't sell case and fan for "ROCKPro64 4GB Single Board Computer"?

Where to buy?

I wish to use it with LibreELEC]]>
You don't sell case and fan for "ROCKPro64 4GB Single Board Computer"?

Where to buy?

I wish to use it with LibreELEC]]>