Mabox linux and multi screen with nvidia

Technical Issues Hardware and Drivers
1

the first thing you do if you are running the free source , is to install the nividia drivers
in mabox controlcenter under hardware you see what you are running free or nvidia
however its very easy to change and setup multi screens , remember you are running manjaro .

sudo nvidia-settings

this wil openen the nvida settings in root , you can now save your settings in the good map and for mabox that is /ect/x11/mhwd.d/nvidia.conf

the right name is always nvidia.conf and make sure it is in the map mhwd.d for manjaro

> if you setup for example 4 screens in xserver display configuration there you see how many screens there are , if you have a card that can run multiscreens , set them how you want them from 1 to 2 to 3 to 4 in the right order , frist apply and than save to x configuration file in the map given above and you are running k’now perfetc 4 screens after reboot.

1 Like
2

I’ve had much difficulty with two screens. Screen tearing is bad until “Force Composition Pipeline” is enabled. This must be done at each logon (settings are not saved / loaded automatically.)

Whenever sudo nvidia-settings is run, it always gives at least one error: (nvidia-settings:5752): GLib-GObject-CRITICAL **: 19:44:04.631: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

Looking in /etc/X11/mhwd.d/nvidia.conf this file has not been modified since the driver was installed. Neither has /etc/X11/xorg.conf.d/20-nvidia.conf. The nvidia-settings config is saved to /etc/X11/xorg.conf however.

I think it is reading /etc/X11/xorg.conf because in the X11 logs, I see:

[    11.768] (--) NVIDIA(GPU-0): 
[    11.924] (WW) NVIDIA(0): No valid modes for
[    11.924] (WW) NVIDIA(0):     "HDMI-0:nvidia-auto-select+1920+0{ForceCompositionPipeline=On},DP-1:nvidia-auto-select+0+0{ForceCompositionPipeline=On}";
[    11.924] (WW) NVIDIA(0):     removing.
[    11.924] (WW) NVIDIA(0): 
[    11.924] (WW) NVIDIA(0): Unable to validate any modes; falling back to the default mode
[    11.924] (WW) NVIDIA(0):     "nvidia-auto-select".
[    11.924] (WW) NVIDIA(0): 
[    11.924] (II) NVIDIA(0): Validated MetaModes:
[    11.924] (II) NVIDIA(0):     "DFP-4:nvidia-auto-select,DFP-1:nvidia-auto-select"
[    11.924] (II) NVIDIA(0): Virtual screen size determined to be 3840 x 1080
[    12.017] (--) NVIDIA(0): DPI set to (92, 91); computed from "UseEdidDpi" X config
[    12.017] (--) NVIDIA(0):     option
[    12.017] (II) NVIDIA: Reserving 24576.00 MB of virtual memory for indirect memory
[    12.017] (II) NVIDIA:     access.
[    12.027] (II) NVIDIA(0): Setting mode "DFP-4:nvidia-auto-select,DFP-1:nvidia-auto-select"

Any ideas?

3

Hi @rdtsc ,

Not from experience but cheeting with Anonchatgpt. No account/login. No save history. (with limitations).

Maybe there are other mabox users with experience to give an answer.

Question : nvidia setting, Force Composition Pipeline. not enabled when reboot system.

ANSWER : There could be a few reasons why the “Force Composition Pipeline” setting in NVIDIA is not enabled after rebooting the system. Here are a few potential solutions:

  1. Check driver version: Make sure you have the latest NVIDIA drivers installed on your system. Visit the NVIDIA website and download the latest drivers for your specific GPU model.

  2. Confirm compatible GPU: Ensure that your GPU supports the “Force Composition Pipeline” feature. Older or lower-end GPUs may not have this capability.

  3. Edit xorg configuration file: Open the xorg configuration file using a text editor (usually located in /etc/X11/xorg.conf or /etc/X11/xorg.conf.d/) and add the following lines:
    Section "Screen" Option "metamodes" "your_resolution +0+0 {ForceCompositionPipeline=On}" EndSection
    Save the file and restart your system. This should enable the composition pipeline upon reboot.

  4. Create a startup script: Create a startup script that runs the following command:
    nvidia-settings --assign CurrentMetaMode="your_resolution +0+0 { ForceCompositionPipeline = On }"
    Make sure the script is set to run automatically on system startup.

  5. Use a third-party tool: There are third-party tools available that can help enable the composition pipeline automatically on system startup, such as “GreenWithEnvy” or “NVIDIA Profile Inspector.”

Good luck …

:bird:

4

Oh! In this line, notice it tries using HDMI-0 and DP-1:

[    11.924] (WW) NVIDIA(0):     "HDMI-0:nvidia-auto-select+1920+0{ForceCompositionPipeline=On},DP-1:nvidia-auto-select+0+0{ForceCompositionPipeline=On}";

But in this line, it ends up using DFP-4 and DFP-1:

[    11.924] (II) NVIDIA(0): Validated MetaModes:
[    11.924] (II) NVIDIA(0):     "DFP-4:nvidia-auto-select,DFP-1:nvidia-auto-select"

This stems from the original video card; it had one Display Port and one HDMI port. But this video card was replaced. The logs are showing the issue - it is trying to load an old config from the previous video card.

So I searched through the entire disk for HDMI-0 (not recommended, but I wanted to see everywhere this was mentioned):

sudo grep -id recurse --exclude-dir=/proc,/sys "HDMI-0" /*

The important files were these:

/etc/X11/xorg.conf.d/20-nvidia.conf: Option "metamodes" "HDMI-0: nvidia-auto-select +1920+0 {ForceCompositionPipeline=On}, DP-1: nvidia-auto-select +0+0 {ForceCompositionPipeline=On}"
/home/me/.config/autostart/lxrandr-autostart.desktop:Exec=sh -c 'xrandr --output DP-1 --mode 1920x1080 --rate 60.00 --output HDMI-0 --mode 1920x1080 --rate 60.00 --right-of DP-1'

Armed with this info, made a backup of those files and edited them, changing HDMI-0 to DFP-4 or DP-4, and updating the name of the video card. After rebooting, the correct profile is now applied. :grinning:

1 Like