[SOLVED]Updates *might* have broken my twinview

llawwehttam · 2011-12-08 14:00:59

Hiah folks.

I ran updates late last night and shutdown. On booting up this morning my second monitor (to my right) has a black band on the left hand side of it, covering half the monitor. It seems that the X screen fills the first monitor and continues from the centre of the second monitor off the screen to the right:

So For instance:

Monitor 1 (working) | Monitor 2 (problem) |
XXXXXXXXXXXXXXX |------------XXXXXXXXXXXXXXXXXXXX

The Physical monitor boundaries are marked with | while the position of the X screen is marked with X.

I've never seen anything like this before and its making my second monitor unusable. Any ideas?

Xorg.conf:

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
    Option         "Xinerama" "0"
EndSection

Section "Files"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "InputClass"
    Identifier             "Keyboard Defaults"
    MatchIsKeyboard	   "yes"
    Option "XkbLayout"     "gb"
EndSection

Section "Monitor"
    # HorizSync source: edid, VertRefresh source: edid
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "BRI M1710X CLAA170EA07"
    HorizSync       31.5 - 80.0
    VertRefresh     56.0 - 75.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GT 220"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "TwinView" "1"
    Option         "TwinViewXineramaInfoOrder" "DFP-0"
    Option         "metamodes" "CRT: nvidia-auto-select +1920+0, DFP: nvidia-auto-select +0+0"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

EDIT: I have almost the same setup on my laptop and it has the same problem. However its fine using my 22" 1920x1080p monitor as a secondary display. I haven't had a chance to test vga vs hdmi properly but it seems that 1280x1024 monitors have problems when connected via vga as the secondary screen using nvidia twinview.

Its definitely not the monitor as the same problem happens with my spare 19" 1280x1024 screen and its not the cable as it works fine with my 22" monitor.

I'm really stumped and can only put it down to software.

Any ideas?

EDIT: More info:

llawwehttam@Steelhorn> nvidia-settings -v

nvidia-settings:  version 290.10 
(buildmeister@swio-display-x86-rhel47-07.nvidia.com)  Wed Nov 16 18:46:42 PST
2011
  The NVIDIA X Server Settings tool.

  This program is used to configure the NVIDIA Linux graphics driver.
  For more detail, please see the nvidia-settings(1) man page.

  Copyright (C) 2004 - 2010 NVIDIA Corporation.

llawwehttam@Steelhorn> uname -r
3.1.4-1-ARCH

EDIT: Here are all the updates done since my last successful boot:

boost-libs (1.47.0-3 -> 1.48.0-2)
boost (1.47.0-3 -> 1.48.0-2)
ekiga (3.3.2-1 -> 3.3.2-2)
ethtool (1:3.0-1 -> 1:3.1-1)
git (1.7.7.4-1 -> 1.7.8-1)
hugin (2011.2.0-1 -> 2011.2.0-2)
jack (0.121.3-1 -> 0.121.3-4)
libpst (0.6.53-1 -> 0.6.53-2)
lxappearance (0.5.1-2 -> 0.5.1-3)
makedev (3.23-2 -> 3.23_1-1)
nspluginwrapper (1.4.4-1 -> 1.4.4-2)
virtualbox (4.1.6-3 -> 4.1.6-4)
audiofile (0.2.7-1 -> 0.3.2-1)
libgusb (0.1.3-1)
polkit (0.102-1 -> 0.103-1)
shared-color-profiles (0.1.5-1)
colord (0.1.15-1 -> 0.1.15-3)
djvulibre (3.5.24-1 -> 3.5.24-2)
libgnome-desktop-sharp (2.26.0-7 -> 2.26.0-8)
gtkhtml-sharp (2.26.0-7 -> 2.26.0-8)
gtksourceview2-sharp (2.26.0-7 -> 2.26.0-8)
rsvg2-sharp (2.26.0-7 -> 2.26.0-8)
vte-sharp (2.26.0-7 -> 2.26.0-8)
wnck-sharp (2.26.0-7 -> 2.26.0-8)
gnome-desktop-sharp (2.26.0-7 -> 2.26.0-8)
gstreamer0.10-bad (0.10.22-2 -> 0.10.22-3)
mjpegtools (1.9.0-4 -> 2.0.0-1)
libdvdread (4.1.3-2 -> 4.2.0-1)
libdvdnav (4.1.3-3 -> 4.2.0-1)
gstreamer0.10-bad-plugins (0.10.22-2 -> 0.10.22-3)
hplip (3.11.10-1 -> 3.11.10-2)
jhead (2.90-1 -> 2.93-1)
lib32-glib2 (2.30.1-1 -> 2.30.2-1)
mercurial (2.0-1 -> 2.0.1-1)
module-init-tools (3.16-2 -> 3.16-3)
mkinitcpio (0.8.0-2 -> 0.8.0-3)
pm-quirks (0.20100619-1 -> 0.20100619-2)
postgresql-libs (9.1.1-2 -> 9.1.2-1)
python-rsvg (2.32.0-8 -> 2.32.0-9)
python-wnck (2.32.0-8 -> 2.32.0-9)
redland (1:1.0.14-1 -> 1:1.0.15-1)
redland-storage-virtuoso (1:1.0.14-1 -> 1:1.0.15-1)
shadow (4.1.4.3-2 -> 4.1.4.3-5)
xcb-util (0.3.6-2 -> 0.3.8-1)
startup-notification (0.12-1 -> 0.12-2)
transcode (1.1.6-1 -> 1.1.7-1)
tumbler (0.1.22-4 -> 0.1.23-1)
upower (0.9.14-1 -> 0.9.15-1)
xcb-util-keysyms (0.3.8-1)
vlc (1.1.12-4 -> 1.1.12-5)
doom3 (1.3.1.1304-8 -> 1.3.1.1304-9)
libgnomeprint (2.18.8-3 -> 2.18.8-5)
libgnomeprintui (2.18.6-1 -> 2.18.6-3)
keyutils (1.5.2-2 -> 1.5.5-1)
zsh (4.3.12-3 -> 4.3.14-1)

EDIT: [SOLVED]

However I did play a lot with xorg.conf and with some other config files and did several reboots and some hardware playing so I have no idea exactly what fixed it.

If I work out what the problem.... and thus the solution, was then I'll post it.

Last edited by llawwehttam (2011-12-08 15:51:23)

lothar_m · 2011-12-08 16:14:13

i've got a similar problem. could you please post your current xorg.conf here?

llawwehttam · 2011-12-08 18:38:35

lothar_m wrote:

i've got a similar problem. could you please post your current xorg.conf here?

Here you go. I think its pretty much the same to my first post. Not sure what I changed to fix the problem:

# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings:  version 290.10  (buildmeister@swio-display-x86-rhel47-07.nvidia.com)  Wed Nov 16 18:46:42 PST 2011

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
    Option         "Xinerama" "0"
EndSection

Section "Files"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "InputClass"
    Identifier             "Keyboard Defaults"
    MatchIsKeyboard	   "yes"
    Option "XkbLayout"     "gb"
EndSection

Section "Monitor"
    # HorizSync source: edid, VertRefresh source: edid
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "BRI M1710X CLAA170EA07"
    HorizSync       31.5 - 80.0
    VertRefresh     56.0 - 75.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GT 220"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "TwinView" "1"
    Option         "TwinViewXineramaInfoOrder" "DFP-0"
    Option         "metamodes" "CRT: nvidia-auto-select +1920+0, DFP: nvidia-auto-select +0+0"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Just as a last resort turn off and unplug your monitor, reset it to factory settings, reconnect it to your machine then reboot and press the auto-configure button. Might help.

Arch Linux

#1 2011-12-08 14:00:59