How do I set a permanent display resolution?

We will always have a 1080p monitor attached to our jetson nano, but the EDID doesn’t send because it’s attached to VGA via hdmi->vga cable. How do I set the desktop resolution to permanently be 1080p from boot so it never changes?

Currently, when I use NoMachine to remote into the jetson, it shows at 480p, then I change it to 1080p, and when I log out of NoMachine it reverts back to 480p again. How to I permanently lock it at 1080p regardless of if I’m remoted into it or not?

You may try adding this into /etc/X11/xorg.conf:

Section "Screen"
  Identifier "MY-SCREEN"
  DefaultDepth 24
  SubSection "Display"
    Virtual 1920 1080
    Depth 24
  EndSubSection
EndSection

and restart X or reboot.

1 Like

Yeah, that didn’t help. It still reverts to 720x400 on reboot. I don’t know what’s going on with their monitor setup since this is at a remote site.

Is there a way to lock all display outputs to 1080p so that it never changes without sudo?

Not sure I correctly understand:

Do you mean early boot ? The screen section in xorg.conf only applies after X has started.
Or do you mean that after reboot, the Desktop resolution has changed ? In such case you would enable X debug mode with option ModeDebug in /etc/X11/xorg.conf:

Section "Device"
    Identifier  "Tegra0"
    Driver      "nvidia"
# Allow X server to be started even if no display devices are connected.
    Option      "AllowEmptyInitialConfiguration" "true"
    Option      "ModeDebug"
EndSection

then save, reboot, and check file /var/log/Xorg.0.log.

I added the lines you mentioned in your first response to xorg.conf. I’m not able to see the machine booting because it’s remote across the USA for me. I know there’s a monitor attached to it, but I don’t know if it’s straight HDMI or if there’s some conversion cable situation going on there. I do know it’s capable of 1080p, so we’d like it to always display in that resolution no matter what state it’s in. When I connect to it via NoMachine, and it’s in 1080p via the system settings (not xrandr or other command line utilities), and I reboot, when I reconnect to it via NoMachine the resolution is back to 720x400 again.

I’ll add the logging to the system and try again when I get a chance.

May also be a NoMachine configuration issue. See NoMachine - Configuring how you view the remote desktop if it can help.

Here’s the log. Near the end you can see it trying to set the display to 1080p, setting it to “NULL”, then 720x400, then the last line is me manually setting it to 1080p in the settings.

[     5.074] (--) Log file renamed from "/var/log/Xorg.pid-5345.log" to "/var/log/Xorg.0.log"
[     5.075] 
X.Org X Server 1.19.6
Release Date: 2017-12-20
[     5.076] X Protocol Version 11, Revision 0
[     5.076] Build Operating System: Linux 5.4.0-139-generic aarch64 Ubuntu
[     5.076] Current Operating System: Linux tess-bs-004 4.9.299-tegra #1 SMP PREEMPT Tue Nov 22 09:24:39 PST 2022 aarch64
[     5.076] Kernel command line: tegraid=21.1.2.0.0 ddr_die=4096M@2048M section=512M memtype=0 vpr_resize usb_port_owner_info=0 lane_owner_info=0 emc_max_dvfs=0 touch_id=0@63 video=tegrafb no_console_suspend=1 console=ttyS0,115200n8 debug_uartport=lsport,4 earlyprintk=uart8250-32bit,0x70006000 maxcpus=4 usbcore.old_scheme_first=1 lp0_vec=0x1000@0xff780000 core_edp_mv=1125 core_edp_ma=4000 gpt tegra_fbmem=0x800000@0x92cb4000 is_hdmi_initialised=1  earlycon=uart8250,mmio32,0x70006000  root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 sdhci_tegra.en_boot_part_access=1 quiet root=/dev/nvme0n1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 sdhci_tegra.en_boot_part_access=1 
[     5.076] Build Date: 29 March 2023  03:17:58PM
[     5.076] xorg-server 2:1.19.6-1ubuntu4.15 (For technical support please see http://www.ubuntu.com/support) 
[     5.076] Current version of pixman: 0.34.0
[     5.076] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[     5.076] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[     5.076] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Jun 13 14:22:14 2023
[     5.084] (==) Using config file: "/etc/X11/xorg.conf"
[     5.084] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[     5.098] (==) No Layout section.  Using the first Screen section.
[     5.098] (**) |-->Screen "MY-SCREEN" (0)
[     5.098] (**) |   |-->Monitor "<default monitor>"
[     5.099] (==) No device specified for screen "MY-SCREEN".
	Using the first device section listed.
[     5.099] (**) |   |-->Device "Tegra0"
[     5.099] (**) |   |-->GPUDevice "Tegra0"
[     5.099] (==) No monitor specified for screen "MY-SCREEN".
	Using a default monitor configuration.
[     5.099] (==) Automatically adding devices
[     5.099] (==) Automatically enabling devices
[     5.099] (==) Automatically adding GPU devices
[     5.099] (==) Automatically binding GPU devices
[     5.099] (==) Max clients allowed: 256, resource mask: 0x1fffff
[     5.101] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[     5.101] 	Entry deleted from font path.
[     5.101] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[     5.101] 	Entry deleted from font path.
[     5.101] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[     5.101] 	Entry deleted from font path.
[     5.101] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[     5.101] 	Entry deleted from font path.
[     5.101] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[     5.101] 	Entry deleted from font path.
[     5.101] (==) FontPath set to:
	/usr/share/fonts/X11/misc,
	/usr/share/fonts/X11/Type1,
	built-ins
[     5.101] (==) ModulePath set to "/usr/lib/xorg/modules"
[     5.101] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[     5.102] (II) Loader magic: 0x5591458010
[     5.102] (II) Module ABI versions:
[     5.102] 	X.Org ANSI C Emulation: 0.4
[     5.102] 	X.Org Video Driver: 23.0
[     5.102] 	X.Org XInput driver : 24.1
[     5.102] 	X.Org Server Extension : 10.0
[     5.103] (++) using VT number 1

[     5.116] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_31
[     5.118] (II) no primary bus or device found
[     5.118] (WW) "dri" will not be loaded unless you've specified it to be loaded elsewhere.
[     5.118] (II) "glx" will be loaded by default.
[     5.118] (II) LoadModule: "extmod"
[     5.118] (II) Module "extmod" already built-in
[     5.118] (II) LoadModule: "glx"
[     5.125] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[     5.144] (II) Module glx: vendor="X.Org Foundation"
[     5.144] 	compiled for 1.19.6, module version = 1.0.0
[     5.144] 	ABI class: X.Org Server Extension, version 10.0
[     5.144] (II) LoadModule: "nvidia"
[     5.148] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[     5.153] (II) Module nvidia: vendor="NVIDIA Corporation"
[     5.153] 	compiled for 4.0.2, module version = 1.0.0
[     5.154] 	Module class: X.Org Video Driver
[     5.156] (II) NVIDIA dlloader X Driver  32.7.3  Release Build  (integ_stage_rel)  (buildbrain@mobile-u64-5333-d8000)  Tue Nov 22 09:24:22 PST 2022
[     5.156] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[     5.156] (WW) Falling back to old probe method for NVIDIA
[     5.157] (II) Loading sub module "fb"
[     5.157] (II) LoadModule: "fb"
[     5.158] (II) Loading /usr/lib/xorg/modules/libfb.so
[     5.162] (II) Module fb: vendor="X.Org Foundation"
[     5.162] 	compiled for 1.19.6, module version = 1.0.0
[     5.162] 	ABI class: X.Org ANSI C Emulation, version 0.4
[     5.162] (II) Loading sub module "wfb"
[     5.162] (II) LoadModule: "wfb"
[     5.163] (II) Loading /usr/lib/xorg/modules/libwfb.so
[     5.169] (II) Module wfb: vendor="X.Org Foundation"
[     5.169] 	compiled for 1.19.6, module version = 1.0.0
[     5.169] 	ABI class: X.Org ANSI C Emulation, version 0.4
[     5.169] (II) Loading sub module "ramdac"
[     5.169] (II) LoadModule: "ramdac"
[     5.169] (II) Module "ramdac" already built-in
[     5.171] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[     5.171] (EE) Screen 1 deleted because of no matching config section.
[     5.171] (II) UnloadModule: "nvidia"
[     5.172] (II) UnloadSubModule: "wfb"
[     5.172] (II) UnloadSubModule: "fb"
[     5.172] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[     5.172] (==) NVIDIA(0): RGB weight 888
[     5.172] (==) NVIDIA(0): Default visual is TrueColor
[     5.172] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[     5.172] (DB) xf86MergeOutputClassOptions unsupported bus type 0
[     5.172] (**) NVIDIA(0): Option "AllowEmptyInitialConfiguration" "true"
[     5.176] (**) NVIDIA(0): Enabling 2D acceleration
[     5.176] (II) Loading sub module "glxserver_nvidia"
[     5.176] (II) LoadModule: "glxserver_nvidia"
[     5.176] (II) Loading /usr/lib/xorg/modules/extensions/libglxserver_nvidia.so
[     5.214] (II) Module glxserver_nvidia: vendor="NVIDIA Corporation"
[     5.214] 	compiled for 4.0.2, module version = 1.0.0
[     5.214] 	Module class: X.Org Server Extension
[     5.214] (II) NVIDIA GLX Module  32.7.3  Release Build  (integ_stage_rel)  (buildbrain@mobile-u64-5333-d8000)  Tue Nov 22 09:23:35 PST 2022
[     5.230] (--) NVIDIA(0): Valid display device(s) on GPU-0 at SoC
[     5.230] (--) NVIDIA(0):     DFP-0
[     5.230] (--) NVIDIA(0):     DFP-1
[     5.230] (II) NVIDIA(0): NVIDIA GPU NVIDIA Tegra X1 (nvgpu) (GM20B) at SoC (GPU-0)
[     5.230] (--) NVIDIA(0): Memory: 4050904 kBytes
[     5.230] (--) NVIDIA(0): VideoBIOS: 
[     5.230] (--) NVIDIA(GPU-0): XNH (DFP-0): connected
[     5.230] (--) NVIDIA(GPU-0): XNH (DFP-0): External TMDS
[     5.231] (==) NVIDIA(0): 
[     5.231] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[     5.231] (==) NVIDIA(0):     will be used as the requested mode.
[     5.231] (==) NVIDIA(0): 
[     5.231] (II) NVIDIA(0): Validated MetaModes:
[     5.231] (II) NVIDIA(0):     "DFP-0:nvidia-auto-select"
[     5.231] (**) NVIDIA(0): Virtual screen size configured to be 1920 x 1080
[     5.232] (--) NVIDIA(0): DPI set to (18, 5); computed from "UseEdidDpi" X config option
[     5.232] (--) Depth 24 pixmap format is 32 bpp
[     5.233] (II) NVIDIA: Reserving 6144.00 MB of virtual memory for indirect memory
[     5.233] (II) NVIDIA:     access.
[     5.237] (EE) NVIDIA(0): Failed to allocate NVIDIA Error Handler
[     5.237] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[     5.237] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[     5.237] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[     5.237] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[     5.237] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[     5.237] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[     5.237] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[     5.237] (II) NVIDIA(0):     Config Options in the README.
[     5.309] (II) NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select"
[     5.321] (==) NVIDIA(0): Disabling shared memory pixmaps
[     5.321] (==) NVIDIA(0): Backing store enabled
[     5.321] (==) NVIDIA(0): Silken mouse enabled
[     5.335] (==) NVIDIA(0): DPMS enabled
[     5.336] (II) Loading sub module "dri2"
[     5.336] (II) LoadModule: "dri2"
[     5.336] (II) Module "dri2" already built-in
[     5.336] (II) NVIDIA(0): [DRI2] Setup complete
[     5.336] (II) NVIDIA(0): [DRI2]   VDPAU driver: nvidia
[     5.355] (--) RandR disabled
[     5.364] (II) SELinux: Disabled on system
[     5.365] (II) Initializing extension GLX
[     5.365] (II) Indirect GLX disabled.
[     5.499] (II) config/udev: Adding input device tegra-hda HDMI/DP,pcm=3 (/dev/input/event0)
[     5.499] (II) No input driver specified, ignoring this device.
[     5.499] (II) This device may have been added with another device file.
[     5.501] (II) config/udev: Adding input device gpio-keys (/dev/input/event1)
[     5.502] (**) gpio-keys: Applying InputClass "libinput keyboard catchall"
[     5.502] (II) LoadModule: "libinput"
[     5.502] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
[     5.512] (II) Module libinput: vendor="X.Org Foundation"
[     5.512] 	compiled for 1.19.6, module version = 0.27.1
[     5.512] 	Module class: X.Org XInput Driver
[     5.512] 	ABI class: X.Org XInput driver, version 24.1
[     5.512] (II) Using input driver 'libinput' for 'gpio-keys'
[     5.516] (II) systemd-logind: got fd for /dev/input/event1 13:65 fd 34 paused 0
[     5.516] (**) gpio-keys: always reports core events
[     5.516] (**) Option "Device" "/dev/input/event1"
[     5.516] (**) Option "_source" "server/udev"
[     5.517] (II) event1  - gpio-keys: is tagged by udev as: Keyboard
[     5.517] (II) event1  - gpio-keys: device is a keyboard
[     5.517] (II) event1  - gpio-keys: device removed
[     5.518] (**) Option "config_info" "udev:/sys/devices/gpio-keys/input/input1/event1"
[     5.518] (II) XINPUT: Adding extended input device "gpio-keys" (type: KEYBOARD, id 6)
[     5.518] (**) Option "xkb_model" "pc105"
[     5.518] (**) Option "xkb_layout" "us"
[     5.519] (II) event1  - gpio-keys: is tagged by udev as: Keyboard
[     5.519] (II) event1  - gpio-keys: device is a keyboard
[    11.936] (--) NVIDIA(GPU-0): XNH (DFP-0): connected
[    11.937] (--) NVIDIA(GPU-0): XNH (DFP-0): External TMDS
[    12.629] (--) NVIDIA(GPU-0): XNH (DFP-0): connected
[    12.630] (--) NVIDIA(GPU-0): XNH (DFP-0): External TMDS
[    12.821] (II) NVIDIA(0): Setting mode "NULL"
[    12.931] (II) config/udev: Adding input device ELO Touch Solutions  ELO Touch Solutions AccuTouch 2218  (/dev/input/mouse0)
[    12.934] (II) No input driver specified, ignoring this device.
[    12.935] (II) This device may have been added with another device file.
[    12.946] (II) config/udev: Adding input device ELO Touch Solutions  ELO Touch Solutions AccuTouch 2218  (/dev/input/js0)
[    12.946] (II) No input driver specified, ignoring this device.
[    12.947] (II) This device may have been added with another device file.
[    12.949] (II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select @720x400 +0+0 {ViewPortIn=720x400, ViewPortOut=720x400+0+0}"
[    13.146] (II) config/udev: Adding input device ELO Touch Solutions  ELO Touch Solutions AccuTouch 2218  (/dev/input/event2)
[    13.146] (**) ELO Touch Solutions  ELO Touch Solutions AccuTouch 2218 : Applying InputClass "libinput pointer catchall"
[    13.146] (II) Using input driver 'libinput' for 'ELO Touch Solutions  ELO Touch Solutions AccuTouch 2218 '
[    13.205] (II) systemd-logind: got fd for /dev/input/event2 13:66 fd 41 paused 0
[    13.205] (**) ELO Touch Solutions  ELO Touch Solutions AccuTouch 2218 : always reports core events
[    13.205] (**) Option "Device" "/dev/input/event2"
[    13.206] (**) Option "_source" "server/udev"
[    13.209] (II) event2  - ELO Touch Solutions  ELO Touch Solutions AccuTouch 2218 : is tagged by udev as: Mouse
[    13.209] (II) event2  - ELO Touch Solutions  ELO Touch Solutions AccuTouch 2218 : device is a pointer
[    13.209] (II) event2  - ELO Touch Solutions  ELO Touch Solutions AccuTouch 2218 : device removed
[    13.210] (**) Option "config_info" "udev:/sys/devices/70090000.xusb/usb1/1-2/1-2.2/1-2.2.2/1-2.2.2:1.0/0003:04E7:0050.0001/input/input2/event2"
[    13.210] (II) XINPUT: Adding extended input device "ELO Touch Solutions  ELO Touch Solutions AccuTouch 2218 " (type: MOUSE, id 7)
[    13.210] (**) Option "AccelerationScheme" "none"
[    13.212] (**) ELO Touch Solutions  ELO Touch Solutions AccuTouch 2218 : (accel) selected scheme none/0
[    13.212] (**) ELO Touch Solutions  ELO Touch Solutions AccuTouch 2218 : (accel) acceleration factor: 2.000
[    13.213] (**) ELO Touch Solutions  ELO Touch Solutions AccuTouch 2218 : (accel) acceleration threshold: 4
[    13.215] (II) event2  - ELO Touch Solutions  ELO Touch Solutions AccuTouch 2218 : is tagged by udev as: Mouse
[    13.215] (II) event2  - ELO Touch Solutions  ELO Touch Solutions AccuTouch 2218 : device is a pointer
[    14.047] (--) NVIDIA(GPU-0): XNH (DFP-0): connected
[    14.047] (--) NVIDIA(GPU-0): XNH (DFP-0): External TMDS
[    14.264] (--) NVIDIA(GPU-0): XNH (DFP-0): connected
[    14.264] (--) NVIDIA(GPU-0): XNH (DFP-0): External TMDS
[    17.411] (--) NVIDIA(GPU-0): XNH (DFP-0): connected
[    17.412] (--) NVIDIA(GPU-0): XNH (DFP-0): External TMDS
[    17.486] (--) NVIDIA(GPU-0): XNH (DFP-0): connected
[    17.486] (--) NVIDIA(GPU-0): XNH (DFP-0): External TMDS
[    17.641] (--) NVIDIA(GPU-0): XNH (DFP-0): connected
[    17.641] (--) NVIDIA(GPU-0): XNH (DFP-0): External TMDS
[    30.687] (II) NVIDIA(0): Setting mode "HDMI-0: 1920x1080 @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
[    41.046] (II) NVIDIA(0): Setting mode "NULL"
[    41.202] (II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select @720x400 +0+0 {ViewPortIn=720x400, ViewPortOut=720x400+0+0}"
[    47.133] (--) NVIDIA(GPU-0): XNH (DFP-0): connected
[    47.133] (--) NVIDIA(GPU-0): XNH (DFP-0): External TMDS
[    47.155] (--) NVIDIA(GPU-0): XNH (DFP-0): connected
[    47.158] (--) NVIDIA(GPU-0): XNH (DFP-0): External TMDS
[    47.355] (--) NVIDIA(GPU-0): XNH (DFP-0): connected
[    47.355] (--) NVIDIA(GPU-0): XNH (DFP-0): External TMDS
[    56.312] (II) NVIDIA(0): Setting mode "HDMI-0: 1920x1080 @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"

Are you sure this is the log after rebooting with ModeDebug enabled ? I would expect more logs about various modes, but I may be wrong.
Maybe you would try adding a Monitor section for your case.

NoMachine is not the GUI you think it is. What the other person sees at the actual Jetson is normally via the X server. You are not running ssh forwarding, but this might partially explain that NoMachine is its own graphical server separate from what the Jetson shows up as having:

The gist of this:

  • An X server normally interprets graphical events locally, and displays via the local GPU to the local monitor. When you remote connect via ssh with either the “-Y” or “-X” argument, the remote system will instead see the events, and the GPU and software of the remote system will be what interprets those events and creates what you see on the display.
  • A virtual server replaces the X server, but is still X in most cases. NoMachine is a virtual server. You can run both a local server and virtual server simultaneously with independent logins.
  • A virtual server runs directly on the Jetson, but remote connection does not use events. The events are interpreted directly on the Jetson’s GPU and software for this case even if the viewer is on a remote system. Virtual servers forward the result of events, i.e., the actual pixel changes, as seen by the Jetson.
  • Unless you’ve set the virtual server on the Jetson to replace the local X server, the server settings will not show up at the Jetson itself.
  • If someone logs in locally at the Jetson, and reports the result of “echo $DISPLAY”, then it will tell you the designation of the server which is visible to that Jetson user.
  • If someone logs in remotely via NoMachine, and runs the command “echo $DISPLAY”, then if and only if it matches the local $DISPLAY will the two be the same (and perhaps not anyway in some cases).
  • Local systems usually have $DISPLAY as “:0.0”. Remote systems via a virtual server will usually (it is traditional, and is not enforeced) be something like “:10.0”.
  • You can change the resolution and other setup all you want in NoMachine, or in the non-virtual local X server, and the two will not know, nor care, what the other server is set to. If you are setting up the xorg.conf to run a certain resolution, and it is being applied to the local X server, then I would expect the virtual server to not see (nor use) that setting.

X server logs (including virtual) are located as naming convention:
/var/log/Xorg.*.log

What do you see from:
ls -ltr /var/log/Xorg.*.log

Note that the “-ltr” means it will reverse sort based on timestamp of last modification of the file. Are there files with two different names? Those names in the wildcard “*” are the $DISPLAY.

From my jetson logged in via NoMachine:

$ echo $DISPLAY
:0

and results of ls -ltr /var/log/Xorg.*.log:

$ ls -ltr /var/log/Xorg.*.log
-rw-r--r-- 1 root root 18571 Jun 14 10:03 /var/log/Xorg.0.log

What NoMachine is doing, as far as I’ve read, is hooking into the existing running xserver and streaming the composited graphics for the currently logged in user. I’m not familiar with what’s going on under the hood on a lot of this stuff so I could be wrong.

We have other jetsons in the field that are either running headless or on a monitor that don’t have this problem. It just our latest one in the field that’s having this issue.

NoMachine does indeed hook in to the server, but from what I know (and I could be wrong, I don’t use NoMachine) this requires a modified server on the Jetson itself. However, the timestamp on that file is apparently from right about now (are you or the Jetson are in an Eastern Standard Time zone?). So this is likely the correct server and log if you combine it with the $DISPLAY.

However, it is still possible that your client on the remote PC is able to run at a higher or lower resolution. The earlier log does show the NVIDIA module loading, so it seems the server is running correctly.

Does NoMachine have any documentation on setting resolution? What I find most interesting is that your xorg.conf has the “ModeDebug” which @Honey_Patouceul asked for, but the log does not show the mode pool. It is as if the server log is not from the xorg.conf with the ModeDebug in it. @Honey_Patouceul gave a URL for NoMachine configuration, which I have not read, but I am wondering if there is anything there about the location of xorg.conf, such that it might be ignoring the config file and really using some other config file in another location.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.

Continuing the discussion at How to set permanent display resolution [SOLVED] - Jetson & Embedded Systems / Jetson Nano - NVIDIA Developer Forums

1 Like