R32.3.1 tx2-4g nvdisplay message

getting this message what does it mean, where is it documented?

[769824.567677] tegradc 15200000.nvdisplay: Horizontal downscale ratio 6x greater than 4x


From the print, it seems like it hits limitation of hardware display block. Do you use nvoverlaysink plugin? Or which sink plugin do you use?

yes I am using nvoverlaysink on my MIPI DSI display. 480x800


This error means you probably feed a large input size to a small display. Since your panel is only 480x800, our display controller needs to do the scaling by itself. Such function has it limitation. And your downscale case seems over that limitation and cause error.

Such limitation is documented iniside TRM. You can avoid this by using nvvidconv.

it was working, and after an sudo apt upgrade it changed to not working, how do I know what will change if I do apt upgrade?

Are there release notes to tell the customers what to expect?


If you do the sudo apt-get upgrade, then depends on the version in your source list file, your system is probably moving to rel-32.4.4 or rel-32.5 now.

cat /etc/nv_tegra_release

R32 (release), REVISION: 3.1, GCID: 18186506, BOARD: t186ref, EABI: aarch64, DATE: Tue Dec 10 07:03:07 UTC 2019


uname -a
Linux BaseSystem_0_5 4.9.140-tegra #182 SMP PREEMPT Mon Apr 5 08:36:55 CDT 2021 aarch64 aarch64 aarch64 GNU/Linux

So some parts of my system are at a different level of release?

What file do I look at?


What is the version before you upgrade to r32.3.1? Are you able to upgrade to r32.4.4 or r32.5.1?

I have been on r32.3.1 because of my camera driver, I CAN NOT change to r32.5.1 or r32.4.4 because my camera driver is not supported on those releases.


I am not sure if this is really caused by apt upgrade
Such limitation is added very long time ago in the driver code. At least the error code from kernel is added even in rel-32.2.

You can try to flash back to your rel-32.3.1 default software and see if this issue is still. Then, run apt-get again and share us what apt upgrade gives you on terminal. And also test if this error happens.

And you should also share us what kind of pipeline you are using for gstreamer. You have been asking questions in this forum for over a year, please really try to learn how to file a topic clearly instead of complaining no one can help you.

I also told this issue is due to you put a larger size buffer to a small display. Thus, just use nvvidconv in your pipeline to avoid such issue. For example, just think about you feed a 4k size buffer to a 480x800 monitor, some components should come out to do the scaling. In your error case, the display driver jumps out and say this scaling is out of its capability. Thus, just use a nvvidconv to replace display driver to do this work.

Just a suggestion: Also try adding ‘pixel-aspect-ratio=1/1’ into output caps when rescaling, at least in last caps between nvvidconv and nvoverlaysink.