Custom Resolution with fbset: FBIOPUT_VSCREENINFO: Invalid argument

Hi Toradex Community,

I am currently developing a Yocto image to run a Qt6 app using the following configs/version:

  • Yocto 4.0.11 (Kirkstone)
  • Uboot 2022.07
  • Kernel version 6.1.37
  • Yocto manifest: Boot2Qt 6.2.10 for Toradex (v6.2.10-lts.xml)
  • Board: Apalis iMX6
  • External screen resolution 1366x768
  • Connection type: HDMI

On my previous version, I was working with Yocto 3.1 (Dunfell), and to set the screen’s resolution, I would create a file /etv/fb.modes containing the following:

mode “1360x768 60.00Hz 32bit (GTF)”
# PCLK: 84.72 MHz, H: 47.70 kHz, V: 60.00 Hz
geometry 1360 768 1360 768 32
timings 11804 208 64 23 1 144 3
hsync low
vsync high

Calling the command

fbset “1360x768 60.00Hz 32bit (GTF)”

would then work like a charm, immediately setting the screen’s resolution to it.

However, upon upgrading the kernel, even though I am using the same hardware, screen and connections, calling this custom display resolution now outputs

fbset: FBIOPUT_VSCREENINFO: Invalid argument

I’ve taken a look at Display Output, Resolution and Timings (Linux) | Toradex Developer Center, but changing vidargs to anything doesn’t seem to have any effect.

Would anyone be able to help me figure out what’s missing, or if this newer version has a new way to set custom resolutions?

Thanks in advance,

To add to the above, I’ve also looked into the following Boot2Qt link: Customizing Runtime Environment | Boot to Qt 6.2.10, where it mentions to set the Display Resolution via the fbpanel command on U-Boot, but that command does not seem to exist (even though fbpanel’s requirement is to have U-Boot v2015.07)

Greetings @anthonyabboud,

It’s a bit strange you have to set the timing and resolution values for an HDMI screen. I would assume the EDID would provide such information already.

Anyways I’m not familiar with such an error message. On quick search I found this thread for raspberry pi: ioctl FBIOPUT_VSCREENINFO: Invalid argument - Raspberry Pi Forums

Perhaps your kernel command line here is incorrect or messed up?

Best Regards,