Question

5

12.10 Quantal display issues using nvidiaXineramaInfoOverride

rated 0 times [ 5] [ 0] / answers: 1 / hits: 2788 / 2 Years ago, fri, march 4, 2022, 1:27:44

After updating to 12.10 today, my xorg.conf doesn't seem to be respected by Quantal. Not sure if this is a 'bug' or whether it's just an adjustment I have to make due to changes in the OS.

When logging in, it seems Ubuntu is now recognizing only one 3840x1080 screen named "Matrox" and maximizing windows spans them across both screens. In 12.04, this configuration file successfully allowed me to override the data provided by my TripleHead2Go and maximize windows to a single monitor.

Any ideas or where to start on trying to debug this?

After a bit of searching, I tried to make changes according to the update here: http://www.phoronix.com/scan.php?page=news_item&px=MTEyMDk

Here's where the config file sits currently:

Section "ServerLayout"

  Identifier     "Layout0"

  Screen      0  "Screen0" 0 0

  InputDevice    "Keyboard0" "CoreKeyboard"

  InputDevice    "Mouse0" "CorePointer"

  Option         "Xinerama" "0"

EndSection



Section "Files"

EndSection



Section "InputDevice"

  Identifier     "Mouse0"

  Driver         "mouse"

  Option         "Protocol" "auto"

  Option         "Device" "/dev/psaux"

  Option         "Emulate3Buttons" "no"

  Option         "ZAxisMapping" "4 5"

EndSection



Section "InputDevice"      

  Identifier     "Keyboard0"

  Driver         "kbd"

EndSection



Section "Monitor"

    # HorizSync source: edid, VertRefresh source: edid

    Identifier     "Monitor0"

    VendorName     "Unknown"

    ModelName      "Matrox"

    HorizSync       31.5 - 80.0

    VertRefresh     59.9 - 75.0

    Option         "DPMS"

EndSection



Section "Device"

    Identifier     "Device0"

    Driver         "nvidia"

    VendorName     "NVIDIA Corporation"

    BoardName      "GeForce GTX 260M"

EndSection



Section "Screen"

    Identifier     "Screen0"

    Device         "Device0"

    Monitor        "Monitor0"

    DefaultDepth    24

    Option         "nvidiaXineramaInfo" "true"

    Option         "nvidiaXineramaInfoOrder" "CRT-0"

    #Option         "metamodes" "CRT: nvidia-auto-select +0+0"

    Option         "nvidiaXineramaInfoOverride" "1920x1080 +0+0, 1920x1080 +1920+0"

    Option         "Stereo" "0"

    SubSection     "Display"

        Depth       24

    EndSubSection

EndSection

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

hreadsoplet

Add To Favorites

Follow

Total Points: 220

Total Questions: 108

Total Answers: 105

Location: Serbia

Member since Fri, Jun 3, 2022

2 Years ago

hreadsoplet questions

1 grep fails to find text in docx file

Fri, Nov 11, 22, 14:00, 2 Years ago

1 How to rename files in ubuntu, recursively, using grep and rename not find?

Sat, Oct 9, 21, 17:57, 3 Years ago

1 Ubuntu 20.04 freezs with Lenovo Thinkpad t14

Wed, May 25, 22, 18:11, 2 Years ago

1 acpi event 69 made my system unusable

Thu, Jan 20, 22, 09:26, 2 Years ago

1 Server Install error 404 not found during ubuntu installation

Mon, Jan 24, 22, 20:23, 2 Years ago

View All

answered 2 Years ago horicgly · Accepted Answer

In recent versions of NVIDIA Linux graphics driver - including the version of nvidia-current in quantal 12.10, 304.51 - the support for RandR 1.2+ has been introduced, improving the integration between the graphics card and the window manager (GNOME, KDE, etc.) with the handling of display resolution, rotation, etc. from window manager tools in addition to nvidia-settings. However it seems that TwinViewXineramaInfoOverride xorg.conf config option (which now has been renamed to nvidiaXineramaInfoOverride) is not working properly.

To follow NVIDIA progress on this subject see:

http://www.nvnews.net/vbulletin/showthread.php?p=2578805

http://www.nvnews.net/vbulletin/showthread.php?t=184814

A possible solution is to use Fake Xinerama http://home.kde.org/~seli/fakexinerama/ that has been proven to work also with Xorg 7.7 (the version of Xorg on quantal 12.10). To follow the procedure described in the linked document you need:

Before the procedure, sudo apt-get install libxinerama-dev

After the procedure, reboot the system

You can use the following content for ~/.fakexinerama:

2

0 0 1920 1080

1920 0 1920 1080

To enable fakexinerama only when the Matrox DualHead2Go is present, you can also add this code to /etc/init/lightdm.conf, before exec lightdm:

if lsusb | grep -q 18ea:0003; then

        echo "Matrox DualHead2Go Detected"

        cp /usr/lib/x86_64-linux-gnu/libXinerama.so.1.0.0-fake /usr/lib/x86_64-linux-gnu/libXinerama.so.1.0.0

else

        echo "Matrox DualHead2Go NOT Detected"

        cp /usr/lib/x86_64-linux-gnu/libXinerama.so.1.0.0-orig /usr/lib/x86_64-linux-gnu/libXinerama.so.1.0.0

fi

Use the following rules to make this code working:

In any case, use /usr/lib/i386-linux-gnu instead of /usr/lib/x86_64-linux-gnu if not on 64 bits

Make a backup copy of the original /usr/lib/x86_64-linux-gnu/libXinerama.so.1.0.0 to /usr/lib/x86_64-linux-gnu/libXinerama.so.1.0.0-orig

Copy the modified version, resulting from fakexinerama build to /usr/lib/x86_64-linux-gnu/libXinerama.so.1.0.0-fake

Replace 18ea:0003 with your device product id, if different (use lsusb to find the right value).

Reboot the system each time you need to switch from Matrox DualHead2Go mode to original mode.

NOTE: once working you should be able to maximize windows to each single screen, but any action that use the RandR information instead of Xinerama won't take care of the fake Xinerama information (e.g. wallpaper, Adobe Flash full screen - including YouTube, etc.).