[Solved]Dual-Head Setup broken after last Kernelupgrade

Hello,
Yesterday I upgraded my from 4.0.2 to 4.0.3 and was kind of surprised when my second display didn't want to show a picture anymore. When booting everything looks good when sudenly one display gets black. It doesn't matter which Desktop I start, even when switching VT only one display is active, so it's not a Xorg-bug.
Nothing shows up in journalctl oder dmesg and as far as the system is concerned everything works as expected. Everything worked as soon as I downgraded the Kernel to 4.0.2.
Enabling testing and installing 4.0.4 didn't work either.
So my question is, does anyone else experience this behaviour?
thanks in advance
- Radeon HD 77xx with open source drivers
- two displays DVI (primary) and HDMI (secondary)
Edit:
I Just checked the kernel from today in testing (4.0.4-2) and saw something really interesting during boot.
[drm:drm_edid_block_valid [drm]] *ERROR* EDID checksum is invalid, remainder is 105
May 22 16:24:55 Arbiter kernel: Raw EDID:
May 22 16:24:55 Arbiter kernel: 00 ff ff ff ff ff ff 00 41 2f 00 00 01 01 01 01
May 22 16:24:55 Arbiter kernel: 00 16 01 03 80 a0 5a 78 0a ee 91 a3 54 4c 99 26
May 22 16:24:55 Arbiter kernel: 0f 50 54 a1 08 00 31 40 45 40 61 40 71 40 81 80
May 22 16:24:55 Arbiter kernel: 01 01 01 01 01 01 02 3a 80 18 71 38 2d 40 58 2c
May 22 16:24:55 Arbiter kernel: 45 00 a0 5a 00 00 00 1e 01 1d 80 18 71 1c 16 20
May 22 16:24:55 Arbiter kernel: 58 2c 25 00 20 00 00 01 03 78 78 78 78 78 78 78
May 22 16:24:55 Arbiter kernel: 78 78 78 78 78 78 78 78 78 78 78 78 78 78 78 78
May 22 16:24:55 Arbiter kernel: ae ae ae ae ae ae ae ae ae ae ae ae ae ae ae ae
May 22 16:24:55 Arbiter kernel: Raw EDID:
May 22 16:24:55 Arbiter kernel: ae ae ae 23 23 23 23 23 23 23 23 23 23 23 23 23
May 22 16:24:55 Arbiter kernel: 23 23 23 23 23 23 23 23 23 23 00 00 00 00 00 00
May 22 16:24:55 Arbiter kernel: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
May 22 16:24:55 Arbiter kernel: 00 00 01 01 01 01 01 01 01 01 01 01 01 01 01 01
May 22 16:24:55 Arbiter kernel: 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01
May 22 16:24:55 Arbiter kernel: 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01
May 22 16:24:55 Arbiter kernel: 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01
May 22 16:24:55 Arbiter kernel: 01 01 01 01 01 01 01 01 01 1d 1d 1d 1d 1d 1d 1d
May 22 16:24:55 Arbiter kernel: Raw EDID:
May 22 16:24:55 Arbiter kernel: 1d 1d 1d 1d 1d 1d 1d 1d 1d 1d 1d 1d 1c 1c 1c 1c
May 22 16:24:55 Arbiter kernel: 1c 1c 1c 1c 1c 1c 1c 1c 1c 1c 1c 1c 1c 1c 1c 1c
May 22 16:24:55 Arbiter kernel: 1c 1c 1c 2c 2c 2c 2c 2c 2c 2c 2c 2c 2c 2c 2c 2c
May 22 16:24:55 Arbiter kernel: 2c 2c 2c 2c 2c 2c 2c 2c 2c 2c 2c 18 18 18 18 18
May 22 16:24:55 Arbiter kernel: 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18
May 22 16:24:55 Arbiter kernel: 18 18 9e 9e 9e 9e 9e 9e 9e 9e 9e 9e 9e 9e 9e 9e
May 22 16:24:55 Arbiter kernel: 9e 9e 9e 9e 9e 9e 9e 9e 9e 9e 8a 8a 8a 8a 8a 8a
May 22 16:24:55 Arbiter kernel: 8a 8a 8a 8a 8a 8a 8a 8a 8a 8a 8a 8a 8a 8a 8a 8a
May 22 16:24:55 Arbiter kernel: Raw EDID:
May 22 16:24:55 Arbiter kernel: 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10
May 22 16:24:55 Arbiter kernel: 10 10 10 10 00 00 00 00 00 00 00 00 00 00 00 00
May 22 16:24:55 Arbiter kernel: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
May 22 16:24:55 Arbiter kernel: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
May 22 16:24:55 Arbiter kernel: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
May 22 16:24:55 Arbiter kernel: 00 00 00 00 00 00 00 00 00 00 31 31 31 31 31 31
May 22 16:24:55 Arbiter kernel: 31 31 31 31 31 31 31 31 31 31 31 31 31 31 31 31
May 22 16:24:55 Arbiter kernel: 31 31 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f
May 22 16:24:55 Arbiter kernel: radeon 0000:02:00.0: HDMI-A-1: EDID block 0 invalid.
May 22 16:24:55 Arbiter kernel: [drm:radeon_dvi_detect [radeon]] *ERROR* HDMI-A-1: probed a monitor but no|invalid EDID
I have no clue what to make of it. As soon as I downgrade the kernel again, everything is normal.
Last edited by raygenbogen (2015-06-09 14:34:18)

I think I kinda 'solved' the problem by enabling early KMS in mkinitcpio.conf and switched my first Display to the second DVI-Port. It works now, but I don't know if this could be labeled as 'solved' since it's a pretty specific solution and propably doesn't apply to anyone else.
Edit. The most recent Kernel 4.0.5 in Testing solved the problem for me.
Last edited by raygenbogen (2015-06-09 14:34:01)

Similar Messages

  • [Solved] Catalyst graphical glitches with dual head setup

    Hello all, having a weird issue with my dual monitor setup where graphical glitches make my primary monitor completely unusable. The Tear Free feature of the proprietary catalyst driver is what seems to be causing it:
    Tear Free enabled:
    Tear Free disabled:
    I can safely enable it with one monitor disabled also. The issue is that without Tear Free enabled, I'm experiencing some serious screen tearing when watching videos and playing games.
    My video card is the XFX HD 7970 Double D and I'm using the latest version of catalyst (14.4), installed from Vi0L0's repo. The monitors are the same model with the same specs (1920x1200 @60Hz). I definitely used to be able to use Tear Free with my dual head setup at most a month ago, so some update at some point must have broken it. I temporarily switched back to the open source driver before I had found Tear Free to be the culprit and the performance is still hardly comparable.
    Any ideas? Thanks in advance.
    Last edited by bheinks (2014-05-15 02:38:45)

    Rexilion wrote:Maybe try looking at /var/log/pacman.log and see if you can downgrade packages (start with the kernel). See if that works around the problem.
    Downgrading catalyst to 14.3 seems to have done the job. Thanks for the suggestion, marking as solved.
    Inxsible wrote:bheinks, you have been on the forums long enough to be aware of the forum rules. Make use of an image hosting site.
    Sorry, I don't post often and wasn't aware of the rules on images. I'll keep that in mind next time.

  • [solved] Dual head / Xinerama / xrandr setup with Intel 945 & dwm

    Recently came into possession of a 17" LCD and would like to use it in tandem with the internal LCD of my netbook. Clone works with xrandr, as does extended mode to an extent.  The problem is that in extended mode (or spanning, or whatever you want to call it) the smaller screen has dead space which isn't respected by dwm (or any other WM I've tried).  So I'd like to setup dual X sessions (aka Zaphod mode?), each running their own instance of dwm--I don't need to move windows from screen to screen so that's not a concern.
    Has anyone had luck accomplishing this with the current intel driver?  The closest I've gotten so far is a black screen/blinking cursor which drops back to a login prompt after a few seconds.   I see a ton of related topics on Google about this and most of them are unresolved.  If I can get something put together I'll document it in the dwm and/or intel wikis.
    Specs:
    * Acer Aspire One AOD150 with Intel GMA945 @ 1024x600
    * LCD @ 1280x1024
    Last edited by thayer (2009-08-30 05:03:14)

    It's a work in progress, but for those who are interested I was able to get a dual-head setup (using xrandr and the Xinerama extensions) with the current Intel driver (not legacy) using the following:
    /etc/X11/xorg.conf:
    # file: /etc/X11/xorg.conf
    # author: Thayer Williams - http://cinderwick.ca
    # vim:enc=utf-8:nu:ai:si:et:ts=4:sw=4:ft=sh:
    Section "ServerLayout"
    Identifier "AA1Xorg"
    Screen 0 "AA1Screen" 0 0
    InputDevice "AA1Keyboard" "CoreKeyboard"
    InputDevice "LogitechMX518" "CorePointer"
    InputDevice "SynapticsTouchpad" "AlwaysCore"
    Option "BlankTime" "0"
    Option "StandbyTime" "0"
    Option "SuspendTime" "0" # disable all other forms of power save
    Option "OffTime" "10" # turn off DPMS-capable monitor after x mins
    EndSection
    Section "ServerFlags"
    Option "DontZap" "false" # ctrl+alt+backspace to restart x (see input too)
    Option "AIGLX" "false"
    Option "AutoAddDevices" "false" # false to disabl hal hotplugging
    Option "AllowMouseOpenFail" "true" # load Xorg even if mouse input not found
    EndSection
    Section "Files"
    ModulePath "/usr/lib/xorg/modules"
    FontPath "/usr/share/fonts/misc"
    FontPath "/usr/share/fonts/75dpi"
    FontPath "/usr/share/fonts/100dpi"
    FontPath "/usr/share/fonts/Type1"
    FontPath "/usr/share/fonts/TTF"
    FontPath "/usr/share/fonts/artwiz-fonts"
    FontPath "/usr/share/fonts/local"
    EndSection
    Section "Module"
    Load "synaptics"
    EndSection
    Section "InputDevice"
    Identifier "AA1Keyboard"
    Driver "kbd"
    Option "CoreKeyboard"
    Option "XkbModel" "pc105"
    Option "XkbLayout" "us"
    Option "XkbOptions" "terminate:ctrl_alt_bksp" # yes, we really want ctrl+alt+backspace to restart X
    EndSection
    Section "InputDevice"
    Identifier "LogitechMX518"
    Driver "mouse"
    Option "Device" "/dev/input/mice"
    Option "Protocol" "ExplorerPS/2" # options: ExplorerPS/2, IMPS/2, auto, USB (Exp. req'd for side-buttons)
    Option "ZAxisMapping" "4 5"
    Option "Buttons" "5"
    Option "ButtonMapping" "1 2 3 8 9"
    Option "Emulate3Buttons" "no"
    EndSection
    Section "InputDevice"
    Identifier "SynapticsTouchpad"
    Driver "synaptics"
    #Option "Device" "/dev/input/mice"
    Option "Device" "/dev/psaux"
    Option "Protocol" "auto-dev"
    Option "ZAxisMapping" "4 5 6 7"
    Option "SHMConfig" "true" # configurable at runtime? security risk if on
    Option "LeftEdge" "1700" # x coord left
    Option "RightEdge" "5300" # x coord right
    Option "TopEdge" "1700" # y coord top
    Option "BottomEdge" "4200" # y coord bottom
    Option "FingerLow" "25" # pressure below this level triggers release
    Option "FingerHigh" "30" # pressure above this level triggers touch
    Option "TapButton1" "1" # mouse button reported on a non-corner one-finger tap
    Option "TapButton2" "2" # mouse button reported on a non-corner two-finger tap
    Option "FastTaps" "true" # make single-taps faster, and double-taps slower
    Option "MaxTapTime" "180" # max time in ms for detecting tap
    Option "MaxTapMove" "220"
    Option "VertEdgeScroll" "true" # enable vertical scroll zone
    Option "HorizEdgeScroll" "true" # enable horizontal scroll zone
    Option "CornerCoasting" "true" # enable continuous scroll with finger in corner
    Option "CoastingSpeed" "0.30" # corner coasting speed
    Option "VertScrollDelta" "100" # edge-to-edge scroll distance of the vertical scroll
    Option "HorizScrollDelta" "100" # edge-to-edge scroll distance of the horizontal scroll
    Option "MinSpeed" "0.09" # speed factor for low pointer movement
    Option "MaxSpeed" "0.18" # maximum speed factor for fast pointer movement
    Option "AccelFactor" "0.0015" # acceleration factor for normal pointer movements
    Option "VertTwoFingerScroll" "true" # vertical scroll anywhere with two fingers
    Option "HorizTwoFingerScroll" "true" # horizontal scroll anywhere with two fingers
    EndSection
    Section "Monitor"
    Identifier "AA1Monitor"
    VendorName "Acer"
    Option "DPMS" "true"
    HorizSync 28-96
    VertRefresh 50-75
    EndSection
    Section "Device"
    Identifier "Intel945"
    Driver "intel"
    BusID "PCI:0:2:0"
    Option "Tiling" "false" # controls whether buffers are allocated in tiled mode
    EndSection
    Section "Screen"
    Identifier "AA1Screen"
    Device "Intel945"
    Monitor "AA1Monitor"
    SubSection "Display"
    Depth 24
    Modes "1280x1024" "1280x600" "1024x768" "1024x600" "800x600" "640x480"
    Virtual 2048 2048
    EndSubSection
    EndSection
    Until I have a chance to write a fancier script I've added the following to ~/.xinitrc:
    xrandr --output LVDS1 --mode 1024x600
    xrandr --output VGA1 --below LVDS1 --mode 1280x1024
    The first command ensures the netbook screen takes the proper resolution and the second enables the external LCD.  If I startx when the LCD is disconnected then the netbook screen is the only screen enabled (no dead space).
    Caveats
    1. With mplayer in fullscreen it appears as 1024x600 even when opened on the 1280x1024 screen.
    2. The external LCD cannot be placed left or right of the netbook screen because it would exceed the 2048 virtual resolution which segfaults X with the latest intel driver.  Virtual cannot be set higher than 2048 in either direction without segfaulting X; though I imagine this will be addressed in future versions of the intel driver.
    Many thanks to mzapotoczny!
    Last edited by thayer (2009-08-30 04:41:40)

  • Frozen system when booting with dual-head setup (updates)

    Hi guys,
    I made a fresh install a couple of weeks ago and I configured my system for a dual-head setup following the wiki. I activated KMS and added radeon to the kernel parameters.
    My xorg.conf looks like this:
    Section "Monitor"
    Identifier "DVI-0"
    Option "PreferredMode" "1920x1080"
    Option "Position" "0 0"
    EndSection
    Section "Monitor"
    Identifier "HDMI-0"
    Option "PreferredMode" "1920x1080"
    Option "Position" "1920 0"
    EndSection
    I was having random freezes for a couple of days, but I didn't pay too much attention to it. I hard rebooted my computer when it froze and it could boot normally that second time.
    But after yesterday, last update to the open source drivers xf86-video-ati (1:7.5.0-2) and lib32-mesa-libgl (10.5.2-1), my system doesn't boot unless I disconnect one of the screens. When only one screen it's connected everything is fine. If I plug the second screen, it pops up the KDE service to configurate the second screen but as soon I press 'apply the chages' my system freezes and I had to hard reboot.
    I've tried all possible combinations usingt different outputs from the screens, getting the same results. Two of them connected --> freezes after grub loading. One connected --> boot Ok, but as soon as I plug the second one and I apply changes, freezes.
    I found one configuration that doesn't freeze my system. When I plug the second screen, as I said, KDE service automatically pops up. Before I was changing the positions of the screen, one beside the other one, and my system freezes when I apply the changes. If I just left the default configuration (one screen in top of the other), it doesn't freeze my system. After that, I can rearrange the screens, as I need them, and it doesn't freeze.
    Here it is my grub.cfg
    # DO NOT EDIT THIS FILE
    # It is automatically generated by grub-mkconfig using templates
    # from /etc/grub.d and settings from /etc/default/grub
    ### BEGIN /etc/grub.d/00_header ###
    insmod part_gpt
    insmod part_msdos
    if [ -s $prefix/grubenv ]; then
    load_env
    fi
    if [ "${next_entry}" ] ; then
    set default="${next_entry}"
    set next_entry=
    save_env next_entry
    set boot_once=true
    else
    set default="0"
    fi
    if [ x"${feature_menuentry_id}" = xy ]; then
    menuentry_id_option="--id"
    else
    menuentry_id_option=""
    fi
    export menuentry_id_option
    if [ "${prev_saved_entry}" ]; then
    set saved_entry="${prev_saved_entry}"
    save_env saved_entry
    set prev_saved_entry=
    save_env prev_saved_entry
    set boot_once=true
    fi
    function savedefault {
    if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
    fi
    function load_video {
    if [ x$feature_all_video_module = xy ]; then
    insmod all_video
    else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
    fi
    if [ x$feature_default_font_path = xy ] ; then
    font=unicode
    else
    insmod part_msdos
    insmod ext2
    set root='hd0,msdos2'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 e36984ca-21d8-4191-ba2f-a09bf8ce6f88
    else
    search --no-floppy --fs-uuid --set=root e36984ca-21d8-4191-ba2f-a09bf8ce6f88
    fi
    font="/usr/share/grub/unicode.pf2"
    fi
    if loadfont $font ; then
    set gfxmode=auto
    load_video
    insmod gfxterm
    set locale_dir=$prefix/locale
    set lang=en_US
    insmod gettext
    fi
    terminal_input console
    terminal_output gfxterm
    if [ x$feature_timeout_style = xy ] ; then
    set timeout_style=menu
    set timeout=5
    # Fallback normal timeout code in case the timeout_style feature is
    # unavailable.
    else
    set timeout=5
    fi
    ### END /etc/grub.d/00_header ###
    ### BEGIN /etc/grub.d/10_linux ###
    menuentry 'Arch Linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-e36984ca-21d8-4191-ba2f-a09bf8ce6f88' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='hd0,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 128c8e95-9496-49d1-9a9e-bc886662258d
    else
    search --no-floppy --fs-uuid --set=root 128c8e95-9496-49d1-9a9e-bc886662258d
    fi
    echo 'Loading Linux linux ...'
    linux /vmlinuz-linux root=UUID=e36984ca-21d8-4191-ba2f-a09bf8ce6f88 rw quiet
    echo 'Loading initial ramdisk ...'
    initrd /initramfs-linux.img
    submenu 'Advanced options for Arch Linux' $menuentry_id_option 'gnulinux-advanced-e36984ca-21d8-4191-ba2f-a09bf8ce6f88' {
    menuentry 'Arch Linux, with Linux linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-advanced-e36984ca-21d8-4191-ba2f-a09bf8ce6f88' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='hd0,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 128c8e95-9496-49d1-9a9e-bc886662258d
    else
    search --no-floppy --fs-uuid --set=root 128c8e95-9496-49d1-9a9e-bc886662258d
    fi
    echo 'Loading Linux linux ...'
    linux /vmlinuz-linux root=UUID=e36984ca-21d8-4191-ba2f-a09bf8ce6f88 rw quiet
    echo 'Loading initial ramdisk ...'
    initrd /initramfs-linux.img
    menuentry 'Arch Linux, with Linux linux (fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-fallback-e36984ca-21d8-4191-ba2f-a09bf8ce6f88' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='hd0,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 128c8e95-9496-49d1-9a9e-bc886662258d
    else
    search --no-floppy --fs-uuid --set=root 128c8e95-9496-49d1-9a9e-bc886662258d
    fi
    echo 'Loading Linux linux ...'
    linux /vmlinuz-linux root=UUID=e36984ca-21d8-4191-ba2f-a09bf8ce6f88 rw quiet
    echo 'Loading initial ramdisk ...'
    initrd /initramfs-linux-fallback.img
    ### END /etc/grub.d/10_linux ###
    ### BEGIN /etc/grub.d/20_linux_xen ###
    ### END /etc/grub.d/20_linux_xen ###
    ### BEGIN /etc/grub.d/30_os-prober ###
    ### END /etc/grub.d/30_os-prober ###
    ### BEGIN /etc/grub.d/40_custom ###
    # This file provides an easy way to add custom menu entries. Simply type the
    # menu entries you want to add after this comment. Be careful not to change
    # the 'exec tail' line above.
    ### END /etc/grub.d/40_custom ###
    ### BEGIN /etc/grub.d/41_custom ###
    if [ -f ${config_directory}/custom.cfg ]; then
    source ${config_directory}/custom.cfg
    elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
    source $prefix/custom.cfg;
    fi
    ### END /etc/grub.d/41_custom ###
    ### BEGIN /etc/grub.d/60_memtest86+ ###
    ### END /etc/grub.d/60_memtest86+ ###
    And my fstab
    # /etc/fstab: static file system information
    # <file system> <dir> <type> <options> <dump> <pass>
    # /dev/sda2 resto del disco
    UUID=e36984ca-21d8-4191-ba2f-a09bf8ce6f88 / ext4 defaults,noatime,discard 0 1
    # /dev/sda1 100MB
    UUID=128c8e95-9496-49d1-9a9e-bc886662258d /boot ext4 defaults,noatime,discard 0 2
    # /dev/sdc2 10GB
    UUID=3959515c-30e4-4749-bc30-5babba3311e8 /var ext4 defaults 0 2
    # /dev/sdc3 resto del disco
    UUID=8ccc2ed9-35e5-4a4f-81f1-98cc8bfc4ed1 /home ext4 defaults,noatime 0 2
    # /dev/sdc1
    UUID=35e39da9-c942-434d-bbfc-deb5e40ee8be none swap defaults 0 0
    #montaje de temp en ram
    tmpfs /tmp tmpfs nodev,nosuid,size=3G 0 0
    # External HDD
    UUID=0ae5eb6a-8c4c-480c-8efe-609ae83f2bdc /media/External\040HDD ext4 defaults 0 0
    # Seagate Expansion Drive
    UUID=16668D4B668D2C95 /media/Seagate\040Expansion\040Driventfs-3g defaults,nofail 0 0
    What else should I check?
    Thanks in advance.
    Edit: added info
    Edit2: more tests.
    Last edited by doblerone (2015-03-31 08:12:38)

    Rexilion wrote:Maybe try looking at /var/log/pacman.log and see if you can downgrade packages (start with the kernel). See if that works around the problem.
    Downgrading catalyst to 14.3 seems to have done the job. Thanks for the suggestion, marking as solved.
    Inxsible wrote:bheinks, you have been on the forums long enough to be aware of the forum rules. Make use of an image hosting site.
    Sorry, I don't post often and wasn't aware of the rules on images. I'll keep that in mind next time.

  • Nouveau graphical tearing, dual-head setup

    I currently experience tearing while using the Nouveau drivers for my NVidia card. I experienced the same (or a similar) tearing issue while using the proprietary drivers, which, along with the inherent incompatibility with most of the linux graphics stack, led me to switch to Nouveau.
    I'm using the 3D support from nouveau-dri along with xf86-video-nouveau and the most recent Gnome 3 build in the official repositories.
    I have a dual-head setup with one 1024x768 IBM monitor to the left of a 1920x1080 Dell monitor. Both report 60Hz vertical refresh rate in their configuration menus.
    So far, my attempts to solve this problem have consisted of the following steps:
    1. Use a minimal xorg.conf and configure everything using the integrated Gnome display settings utility. The minimal xorg.conf was as follows:
    Section "Device"
    Identifier "nvidia"
    Driver "nouveau"
    Option "GLXVBlank" "true"
    EndSection
    2. Enable/disable the GLXVBlank flag in xorg.conf.
    I do not experience the same issue when booted to Windows 7, using the most recent official NVidia drivers.
    I would greatly appreciate any help anyone could offer on this issue, it is quite frustrating to boot into Windows to watch videos without horizontal breaks in every frame. Thanks!
    Output from xrandr --current is as follows:
    [ifx@melancholy ~]$ xrandr --current
    Screen 0: minimum 320 x 200, current 2944 x 1080, maximum 8192 x 8192
    DVI-I-1 connected 1920x1080+1024+0 (normal left inverted right x axis y axis) 477mm x 268mm
    1920x1080 60.0*+
    1280x1024 75.0 60.0
    1152x864 75.0
    1024x768 75.1 60.0
    800x600 75.0 60.3
    640x480 75.0 60.0
    720x400 70.1
    DVI-I-2 connected 1024x768+0+312 (normal left inverted right x axis y axis) 304mm x 228mm
    1024x768 60.0*+ 75.1 70.1
    832x624 74.6
    800x600 72.2 75.0 60.3 56.2
    640x480 72.8 75.0 60.0 59.9
    720x400 70.1
    My current xorg.conf is as follows:
    Section "Monitor"
    Identifier "Monitor0"
    Option "PreferredMode" "1920x1080_60.00"
    EndSection
    Section "Monitor"
    Identifier "Monitor1"
    Option "PreferredMode" "1024x768_60.00"
    Option "LeftOf" "Monitor0"
    EndSection
    Section "Device"
    Identifier "nvidia"
    Driver "nouveau"
    Option "Monitor-DVI-I-1" "Monitor0"
    Option "Monitor-DVI-I-2" "Monitor1"
    Option "GLXVBlank" "true"
    EndSection
    Section "Screen"
    Identifier "Screen0"
    DefaultDepth 24
    SubSection "Display"
    Depth 24
    Virtual 2944 1080
    EndSubSection
    Device "nvidia"
    EndSection
    Section "ServerLayout"
    Identifier "Layout0"
    Screen "Screen0"
    EndSection
    Other information can be provided on request.

    Hello. I have the same problem. Not just on Arch. I've had this problem with many distros, graphics cards, and drivers across the board. Installing the proprietary nvidia driver fixes the video tearing (vsync) issue for me. However; A) it's Linux, I don't want to use proprietary anything (otherwise I'd be on a Mac); and B) the proprietary driver will not flip my display to portrait anyway.
    I basically have the same setup as Meyermagic. One GeForce 8600 GT, Two monitors (identical acers) 1680x1050 (oriented in portrait so 1050x1680 if you like), using open source Nouveau driver, created a minimal xorg file in /etc/X11/xorg.conf.d/20-nouveau.conf
    Section "Module"
    Load "glx"
    EndSection
    Section "Device"
    Identifier "Nvidia card"
    Driver "nouveau"
    Option "GLXVBlank" "true"
    EndSection
    Both monitors have a refresh rate of 60Hz. I still get really bad tearing as I drag windows across the screens.
    Again, I've had this issue with almost every Linux box I've built (the only time this is not even remotely an issue is on my Thinkpad T400 using the Intel graphics). I'm guessing I'm doing something wrong or I've just had bad luck because it is nearly impossible to find any support for this on any forum anywhere. Anything I do find is either a thread like this where someone asked the question and simply never got a response. Or it is some out-of-date forum that give you 10 ways to modify the xorg.conf none of which make any sense or don't work. Not to mention that xorg.conf is now depreciated anyways.
    Seriously, even if there is a wiki that concisely explains in excruciating detail how to actually modify the xorg conf files then I could figure it out for myself but I can't find that anywhere which makes me feel really stupid because I know it has to be out there. If there isn't an xorg wiki or xorg.com site or something that explains how to use the thing then I'm not sure I want to live on this planet anymore.
    If anyone can help in any way please do.

  • [SOLVED] Dual-Screen Setup with ATI Catalyst

    I'm having a beast of a time trying to set up X to work on my two screens.
    Screen 1 is a 23" screen connected with a DVI cable.  My preferred resolution for this one is 1920x1080.  Screen 2 is a 17" screen (4:3) connected with a VGA cable.  My preferred resolution for this one is 1280x960.
    I tried using "aticonfig --initial=dual-head".  This does not produce a working xorg.conf file.  Specifically, my smaller monitor simply complains about not being able to display the given video mode.  Running xrandr (from the main screen) shows only that output as being "connected" - the rest of them (including the CRT outputs which seem to correspond to the VGA port) as "disconnected".
    I've spent about 5 hours searching for an answer to this, and the only ones I seem to be able to find are nvidia-specific.
    I have an ATI Radeon HD 4850 or 4870 - I honestly forget which, although the drivers should be the same.  I'm using the catalyst driver from the AUR, because I'd like to have 3D acceleration.
    I've read through the entire xorg.conf man page, and tried a few things from there (including writing my own xorg.conf from scratch).  Unfortunately, this seems incredibly useless, as the man page doesn't list any of the options that I seem to need (for example, I've read about and tried the "PairModes" option under "Device").
    I can probably eventually figure this out, but it would be nice to have a few pointers.  For example:
    Should I have one or two "Device" sections in xorg.conf?  Should I have one or two "Screen" sections in xorg.conf?  Where can I find a full list of possible "Option" keys, at least for the Device section?  Should I be using Xinerama (I've tried with and without, to no avail).
    EDIT:  I solved this by using the aticonfig tool some more, and not by messing around with xorg.conf.  Specifically, the command:
    aticonfig --initial=dual-head --xinerama=on --resolution=0,1920x1080 --resolution=1,1280x960 --screen-layout=right
    I'll leave this here in the hopes that it can help someone else.
    Last edited by Tempest (2011-08-06 02:28:41)

    If you aren't playing games, it may be worth it to check out xf86-video-ati. Then you can configure your displays the standard way with xrandr.

  • Bootsplash on a dual-head setup without KMS?

    Hello!
    I have been wanting to get a bootsplash working on my system, to get a feeling of a more polished system, but sadly I'm running the catalyst drivers for decent 3D game framerate, and it doesn't support KMS. It seemed like that would have been okay, and that for example plymouth could work through a framebuffer, but sadly I have dual-head with two different resolutions(1920x1200 and 1020x1280), and I couldn't get Uvesafb/v86d to work with that. I really want to get a bootsplash and I am willing to sacrafise some time to get it working. The main goal is just to get it working, but ideally I'd like it without any resolution changing or black flicker, as it's described here.  So Plymouth is my first-pick, as it looks "best".
    So far I have tried Splashy, FBsplash and Plymouth, with different degrees of success:
    FBsplash:
        Miscsplashutils(dependency) didn't build because freetype had been built without static linking(I don't know anything about this). I got it working with something I found in the comments though.
        But then FBsplash wouldn't build. And I gave it up.
    Splashy:
        Installation worked(splashy-full) after I modified the PKGBUILD with some automake patches so it should work with automake 1.14. But when I booted it the screen was just flickering black
    Plymouth:
        I got it installing, can't remeber if I needed some patches. And it worked, although only with a text-bootsplash. I also installed a framebuffer(Uvesafb/v86d) but that didn't work properly.
        The Plymouth loading anymation(spinfinity) continued into gdm.
    I am willing to retry everything and clearify what doesn't work, and why.
    Thanks to anyone who can help!
    Last edited by totokaka (2013-08-21 16:21:23)

    So I've been trying to get some development on this, and used most of the day to get uvesafb working.
    It is working quite good, but I don't get the native resolution of the screen(1920x1200), I only get 1600x1200.
    And my secound monitor is disabled, I suspect it's because the computer sends a resolution to big to both the screens, but it's really a a feature for me, as the terminal would be sideways on the secound monitor anyways.
    During my testing I also came to a new idea: Have the framebuffer, X and GDM originally only start the main monitor, and then leave it up to gnome to enable it. that way I would only get the flicker between GDM and gnome-shell, which I will get anyway, because it seems like everything ignores X's rotation of the screens, or at least doesnt support sideways. However I didn't find a way to get this working, any ideas?
    EDIT; My card is an HD6790, and as far as I can understand the GPU's bios is sending supported modes to uvesafb?
    Last edited by totokaka (2013-08-22 19:22:52)

  • Dual head setup (mach64 - ATI Rage Mobility)

    hello everyone!
    I want to use a new extra monitor I got recently, with my laptop, I use aweosme.
    I have installed:
    xf86-video-mach64 (recompiled with dri support)
    mach64-dri (from community)
    mach64drm (from AUR)
    https://wiki.archlinux.org/index.php/Mach64
    Still I can't get OpenGL to work:
    ismaelvc@toybox ~ $ glxinfo | egrep "direct rendering|OpenGL renderer"
    direct rendering: Yes
    OpenGL renderer string: Gallium 0.4 on softpipe
    I don't really know if it got something to do with this but I post it anyway in case it is.
    xrandr doesnt detect the other monitor:
    ismaelvc@toybox ~ $ xrandr -q
    xrandr: Failed to get size of gamma for output default
    Screen 0: minimum 320 x 175, current 1024 x 768, maximum 1024 x 768
    default connected 1024x768+0+0 0mm x 0mm
    1024x768 87.0* 85.0 75.0 70.0 60.0 81.0
    832x624 75.0
    800x600 85.0 75.0 72.0 60.0 56.0
    640x480 85.0 75.0 73.0 60.0
    720x400 85.0
    640x400 85.0
    640x350 85.0
    512x384 87.0 85.0 75.0 70.0 60.0
    416x312 75.0
    400x300 85.0 75.0 72.0 60.0 56.0
    320x240 85.0 75.0 73.0 60.0
    360x200 85.0
    320x200 85.0
    320x175 85.0
    Still it displays exactly the same that gets displayed at my laptop.
    I used to had problems with the drivers, I needed both mach64 and radeon for it to detect the screen properly, until I created a "20-mach64.conf" with this:
    Section "Device"
    Identifier "Card0"
    Driver "mach64"
    Card "ATI Rage Mobility - Mach64"
    Option "DMAMode" "async"
    Option "ForcePCIMode" "false"
    Option "AgpMode" "2"
    Option "AgpSize" "32"
    Option "BufferSize" "2"
    Option "LocalTextures" "true"
    Option "EnablePageFlip" "true"
    EndSection
    Section "Module"
    #<Your modules>
    Load "glx"
    Load "dri"
    EndSection
    Section "DRI"
    Group "video" #change to any desired group to restrict access
    Mode 0660
    EndSection
    I have a doubt regarding the commented line that came as example in the mach64 wiki that reads <your modules>, I don't know what goes in there.
    Also I red this for some mach64 related xorg info:
    http://www.x.org/archive/X11R6.8.0/doc/ati5.html
    http://forums.fedoraforum.org/showthread.php?t=201482
    The last one is for a cursor problem I have, but it wont get fixed, neither, anyway the default xcursor looks good in awesome, I switched to cli apps form many tasks, and use uzbl now! all this plus arch is now so minimmal I love it lol!
    I red in a post (not in this one) mach64 chips supported dual head, but I can't find it again, I will post it when I find it.
    Thanks in advance!
    EDIT: ok here it is, where it say its supported: I don't understand all the configs.
    http://cgit.freedesktop.org/xorg/driver … ff432c36bf
    Last edited by ismaelvc (2012-06-29 03:52:09)

    Sorry to necrobump but I was seeing you get a lot of incorrect information on LinuxQuestions.
    The mach64 driver does NOT support dualhead. Some chips are capable of it but this feature has yet to be added to the driver. It is also not compatible with xrandr. The man page you linked to mentioning dualhead support is for xf86-video-ati. It is only accessible from the git history of xf86-video-mach64 because those drivers used to live in the same source tree.
    I can try to help with DRI if that's still not working for you.

  • [SOLVED] Dual head acting weird

    Hello,
    Today I started sorting out about dual head. I configured xorg.conf as said on the wiki.
    The strange thing is, my second display acts as my primary display and my first display acts as second display.
    Also display the second display my console, when I start X, the display still act as first display .
    Here's my Xorg.conf (http://pastebin.com/F7X5fs2e)
    Thank you!
    Last edited by Kansl (2010-08-25 23:34:43)

    Kansl wrote:
    Hello,
    Today I started sorting out about dual head. I configured xorg.conf as said on the wiki.
    The strange thing is, my second display acts as my primary display and my first display acts as second display.
    Also display the second display my console, when I start X, the display still act as first display .
    Here's my Xorg.conf (http://pastebin.com/F7X5fs2e)
    Thank you!
    We need hardware info, also what drivers you're running, what desktop environment (if any), and if you're wanting compositing or not.
    Differences in hardware cause massive differences in how you configure Xorg.

  • KDE 4.1 with irregular dual head setup -- recommendations, suggestions

    Hello,
    I'm running KDE on a laptop with a 1440X900 screen and a 1280X1024 external monitor. 
    I couldn't get the KRandR to split the desktop onto two monitors, but plain xrandr worked fine -- the desktop is split, the external monitor is on the left, and resolutions are as they should be. 
    However, I'm having some problems/quirks with KDE 4.1 --
    1.  When both monitors are on, KDM's login window is on the left monitor, not the primary one (the one on the laptop).
    2.  When filing mail in Thunderbird, the contextual menus will trail off the bottom of the screen below the task bar, rather than reposition themselves to remain visible
    3.  The plasmoid swirly thing is in the upper right corner of the left monitor, but not the monitor on the right.
    Thanks,
    Chris

    I think I kinda 'solved' the problem by enabling early KMS in mkinitcpio.conf and switched my first Display to the second DVI-Port. It works now, but I don't know if this could be labeled as 'solved' since it's a pretty specific solution and propably doesn't apply to anyone else.
    Edit. The most recent Kernel 4.0.5 in Testing solved the problem for me.
    Last edited by raygenbogen (2015-06-09 14:34:01)

  • T510 ThinkVanta​ge button and updates software broken after last update 12/1/2010

    After last updates I ran on Dec 1, 2010, the ThinkVantage button does nothing.  Running the updates and drivers from the control panel flashes the GUI splash screen then closes.
    Lenovo really screwed this one up!  Now you can't even get the updates to work to fix other issues.
    In the event logs I show PC-Doctor errors
    The description for Event ID 1 from source PC-Doctor cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
    If the event originated on another computer, the display information had to be saved with the event.
    The following information was included with the event:
    (1972) Asapi: (13:00:09:5300)(1972) DEFECT.LOCALIZATION - Error -- Missing String: scriptlets : button1 locale: PCDLocale: language = en, customer = lenovo, variant = ltt
    Log Name:      Application
    Source:        ThinkVantage Registry Monitor Service
    Date:          12/1/2010 12:29:40 PM
    Event ID:      0
    Task Category: None
    Level:         Information
    Keywords:      Classic
    User:          N/A
    Computer:      jmw-77
    Description:
    The description for Event ID 0 from source ThinkVantage Registry Monitor Service cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
    If the event originated on another computer, the display information had to be saved with the event.
    The following information was included with the event:
    Service started
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/ev​ent">
      <System>
        <Provider Name="ThinkVantage Registry Monitor Service" />
        <EventID Qualifiers="0">0</EventID>
        <Level>4</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2010-12-01T17:29:40.000000000Z" />
        <EventRecordID>42737</EventRecordID>
        <Channel>Application</Channel>
        <Computer>jmw-77</Computer>
        <Security />
      </System>
      <EventData>
        <Data>Service started</Data>
      </EventData>
    </Event>

    Hi and welcome to the forum!
    Try uninstalling the PC-Doctor / Lenovo ThinkVantage Toolbox and System Update from Add/Remove programs, do a mandatory restart, thereafter download and run CCleaner, scan for registry issues with it and fix them. Subsequently, manually install both Toolbox and System Update.
    Keep us posted with the results.
    Maliha (I don't work for lenovo)
    ThinkPads:- T400[Win 7], T60[Win 7], IBM 240[Win XP]
    IdeaPad: U350
    Apple:- Macbook Air [Snow Leopard]
    Did someone help you today? Compliment them with a Kudos!
    Was your question answered today? Mark it as an Accepted Solution! 
      Lenovo Deutsche Community     Lenovo Comunidad en Español 
    Visit my YouTube Channel

  • Wiki icons broken after last upgrade?

    Has anyone noticed that the wiki icons after the last update 10.7.2 are broken?
    I just did a remote upgrade and noticed the links are now broken on the wiki pages..  I'll troubleshoot it from an apache perspective later tonight, but I was just curious as to if anyone else has run into this anomaly..

    So after getting home from a business trip yesterday, I decided to look into this..   I found that screen sharing was also not working.
    I rebooted the server and screen sharing started working again, as well as the icons are now also being displayed properly in the wiki's.  I wanted to get screen sharing working first as the server is in the basement, and I'd rather sit at my desk to troubleshoot   (Simply restarting screen sharing did not fix that problem)
    If it happens again, I'll troubleshoot before rebooting.

  • Grub/boot using wrong monitor (dual-head setup)?

    I have a dual monitor set up, using two dvi slots on my radeon HD card.
    When I start up my system, regardless of the order of the cables, it first shows my bios slash screen on both monitors, then it goes to Grub2 and I see "Loading Grub.." on both monitors.  After that, it always defaults to displaying on my "secondary" monitor, which I do not use very often.  Meanwhile my primary monitor goes black until my system reaches the SLIM login.
    Is there any way to define which monitor is to be used in Grub2 and during booting?
    I'm thinking it the default display may be configured in the /etc/grub.d/00_header file but I have no idea how to edit that.
    As I said, I tried switching the cables and also checked the bios and didn't see any settings regarding this.
    Last edited by CheesyBeef (2011-06-15 17:10:23)

    The primary display is the one that holds the tiny white stripe representing the MenuBar in this presentation in system Preferences > Displays:
    Drag the white stripe to the display you would like to be Primary.

  • [SOLVED] Touchpad Synaptics not works after last update of xf86-input

    after this packages
    xf86-input-synaptics 1.8.0-2 <<< works
    xf86-input-synaptics 1.8.0-3 << not works
    https://projects.archlinux.org/svntogit … 54796cff46
    dmesg|grep input
    [ 0.866883] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
    [ 1.842679] input: HID 04f3:0103 as /devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.0/0003:04F3:0103.0001/input/input2
    [ 1.842756] hid-generic 0003:04F3:0103.0001: input,hidraw0: USB HID v1.10 Keyboard [HID 04f3:0103] on usb-0000:00:14.0-1/input0
    [ 1.843934] input: HID 04f3:0103 as /devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.1/0003:04F3:0103.0002/input/input3
    [ 1.844001] hid-generic 0003:04F3:0103.0002: input,hidraw1: USB HID v1.10 Device [HID 04f3:0103] on usb-0000:00:14.0-1/input1
    [ 2.169742] input: A4TECH USB Device as /devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.0/0003:09DA:9066.0003/input/input4
    [ 2.169933] hid-generic 0003:09DA:9066.0003: input,hiddev0,hidraw2: USB HID v1.11 Keyboard [A4TECH USB Device] on usb-0000:00:14.0-2/input0
    [ 2.171262] input: A4TECH USB Device as /devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.1/0003:09DA:9066.0004/input/input5
    [ 2.171357] hid-generic 0003:09DA:9066.0004: input,hidraw3: USB HID v1.11 Mouse [A4TECH USB Device] on usb-0000:00:14.0-2/input1
    [ 10.099521] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input6
    [ 10.099624] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input7
    [ 10.099692] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input8
    [ 10.398671] input: PC Speaker as /devices/platform/pcspkr/input/input9
    [ 11.840489] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input10
    [ 12.211308] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:3a/LNXVIDEO:00/input/input11
    [ 12.212530] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input12
    [ 13.254950] sound hdaudioC0D0: inputs:
    [ 13.580490] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/sound/card0/hdaudioC0D0/input13
    [ 13.580985] input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input14
    [ 13.581106] input: HDA Intel PCH Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input15
    [ 13.581224] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input16
    [ 17.274881] input: WebCam SC-13HDL11939N as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/input/input17
    journalctl -b |grep input
    ago 21 09:02:37 drog-laptop kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
    ago 21 09:02:37 drog-laptop kernel: input: HID 04f3:0103 as /devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.0/0003:04F3:0103.0001/input/input2
    ago 21 09:02:37 drog-laptop kernel: hid-generic 0003:04F3:0103.0001: input,hidraw0: USB HID v1.10 Keyboard [HID 04f3:0103] on usb-0000:00:14.0-1/input0
    ago 21 09:02:37 drog-laptop kernel: input: HID 04f3:0103 as /devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.1/0003:04F3:0103.0002/input/input3
    ago 21 09:02:37 drog-laptop kernel: hid-generic 0003:04F3:0103.0002: input,hidraw1: USB HID v1.10 Device [HID 04f3:0103] on usb-0000:00:14.0-1/input1
    ago 21 09:02:37 drog-laptop kernel: input: A4TECH USB Device as /devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.0/0003:09DA:9066.0003/input/input4
    ago 21 09:02:37 drog-laptop kernel: hid-generic 0003:09DA:9066.0003: input,hiddev0,hidraw2: USB HID v1.11 Keyboard [A4TECH USB Device] on usb-0000:00:14.0-2/input0
    ago 21 09:02:37 drog-laptop kernel: input: A4TECH USB Device as /devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.1/0003:09DA:9066.0004/input/input5
    ago 21 09:02:37 drog-laptop kernel: hid-generic 0003:09DA:9066.0004: input,hidraw3: USB HID v1.11 Mouse [A4TECH USB Device] on usb-0000:00:14.0-2/input1
    ago 21 09:02:40 drog-laptop kernel: input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input6
    ago 21 09:02:40 drog-laptop kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input7
    ago 21 09:02:40 drog-laptop kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input8
    ago 21 09:02:41 drog-laptop kernel: input: PC Speaker as /devices/platform/pcspkr/input/input9
    ago 21 09:02:42 drog-laptop kernel: input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input10
    ago 21 09:02:42 drog-laptop kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:3a/LNXVIDEO:00/input/input11
    ago 21 09:02:42 drog-laptop kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input12
    ago 21 09:02:43 drog-laptop kernel: sound hdaudioC0D0: inputs:
    ago 21 09:02:44 drog-laptop kernel: input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/sound/card0/hdaudioC0D0/input13
    ago 21 09:02:44 drog-laptop kernel: input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input14
    ago 21 09:02:44 drog-laptop kernel: input: HDA Intel PCH Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input15
    ago 21 09:02:44 drog-laptop kernel: input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input16
    ago 21 09:02:47 drog-laptop kernel: input: WebCam SC-13HDL11939N as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/input/input17
    ago 21 09:02:52 drog-laptop acpid[589]: starting up with netlink and the input layer
    ago 21 09:02:53 drog-laptop systemd-logind[585]: Watching system buttons on /dev/input/event7 (Power Button)
    ago 21 09:02:53 drog-laptop systemd-logind[585]: Watching system buttons on /dev/input/event11 (Video Bus)
    ago 21 09:02:53 drog-laptop systemd-logind[585]: Watching system buttons on /dev/input/event10 (Video Bus)
    ago 21 09:02:53 drog-laptop systemd-logind[585]: Watching system buttons on /dev/input/event6 (Power Button)
    ago 21 09:02:53 drog-laptop systemd-logind[585]: Watching system buttons on /dev/input/event5 (Lid Switch)
    cat /usr/share/X11/xorg.conf.d/50-synaptics.conf
    # Example xorg.conf.d snippet that assigns the touchpad driver
    # to all touchpads. See xorg.conf.d(5) for more information on
    # InputClass.
    # DO NOT EDIT THIS FILE, your distribution will likely overwrite
    # it when updating. Copy (and rename) this file into
    # /etc/X11/xorg.conf.d first.
    # Additional options may be added in the form of
    # Option "OptionName" "value"
    Section "InputClass"
    Identifier "touchpad catchall"
    Driver "synaptics"
    MatchIsTouchpad "on"
    Option "TapButton1" "1"
    Option "TapButton2" "2"
    Option "TapButton3" "3"
    # This option is recommend on all Linux systems using evdev, but cannot be
    # enabled by default. See the following link for details:
    # http://who-t.blogspot.com/2010/11/how-to-ignore-configuration-errors.html
    MatchDevicePath "/dev/input/event*"
    EndSection
    Section "InputClass"
    Identifier "touchpad ignore duplicates"
    MatchIsTouchpad "on"
    MatchOS "Linux"
    MatchDevicePath "/dev/input/mouse*"
    Option "Ignore" "on"
    EndSection
    # This option enables the bottom right corner to be a right button on clickpads
    # and the right and middle top areas to be right / middle buttons on clickpads
    # with a top button area.
    # This option is only interpreted by clickpads.
    Section "InputClass"
    Identifier "Default clickpad buttons"
    MatchDriver "synaptics"
    Option "SoftButtonAreas" "50% 0 82% 0 0 0 0 0"
    Option "SecondarySoftButtonAreas" "58% 0 0 8% 42% 58% 0 8%"
    EndSection
    # This option disables software buttons on Apple touchpads.
    # This option is only interpreted by clickpads.
    Section "InputClass"
    Identifier "Disable clickpad buttons on Apple touchpads"
    MatchProduct "Apple|bcm5974"
    MatchDriver "synaptics"
    Option "SoftButtonAreas" "0 0 0 0 0 0 0 0"
    EndSection
    xinput
    ⎡ Virtual core pointer id=2 [master pointer (3)]
    ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
    ⎜ ↳ HID 04f3:0103 id=11 [slave pointer (2)]
    ⎜ ↳ A4TECH USB Device id=12 [slave pointer (2)]
    ⎜ ↳ A4TECH USB Device id=13 [slave pointer (2)]
    ⎜ ↳ SynPS/2 Synaptics TouchPad id=16 [slave pointer (2)]
    ⎣ Virtual core keyboard id=3 [master keyboard (2)]
    ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
    ↳ Power Button id=6 [slave keyboard (3)]
    ↳ Video Bus id=7 [slave keyboard (3)]
    ↳ Video Bus id=8 [slave keyboard (3)]
    ↳ Power Button id=9 [slave keyboard (3)]
    ↳ HID 04f3:0103 id=10 [slave keyboard (3)]
    ↳ WebCam SC-13HDL11939N id=14 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=15 [slave keyboard (3)]
    synclient
    Couldn't find synaptics properties. No synaptics driver loaded?
    lsmod
    Module Size Used by
    bbswitch 12878 0
    nls_iso8859_1 12461 1
    nls_cp437 16553 1
    vfat 21231 1
    fat 61984 1 vfat
    fuse 87446 5
    uvcvideo 78952 0
    videobuf2_vmalloc 12816 1 uvcvideo
    ath3k 12685 0
    videobuf2_memops 12519 1 videobuf2_vmalloc
    videobuf2_core 47787 1 uvcvideo
    ecb 12737 1
    v4l2_common 12995 1 videobuf2_core
    btusb 25625 0
    bluetooth 394557 3 ath3k,btusb
    videodev 126443 3 uvcvideo,v4l2_common,videobuf2_core
    media 18365 2 uvcvideo,videodev
    6lowpan_iphc 16588 1 bluetooth
    snd_hda_codec_hdmi 45117 1
    snd_hda_codec_realtek 67127 1
    snd_hda_codec_generic 63126 1 snd_hda_codec_realtek
    nvram 13034 0
    joydev 17063 0
    mousedev 17272 0
    ipt_REJECT 12465 1
    xt_comment 12427 2
    arc4 12536 2
    xt_LOG 17156 5
    ath9k 94538 0
    ath9k_common 21746 1 ath9k
    ath9k_hw 403753 2 ath9k_common,ath9k
    ath 26067 3 ath9k_common,ath9k,ath9k_hw
    mac80211 514630 1 ath9k
    r8169 68119 0
    mii 12675 1 r8169
    cfg80211 454161 4 ath,ath9k_common,ath9k,mac80211
    snd_hda_intel 26327 4
    snd_hda_controller 26727 1 snd_hda_intel
    snd_hda_codec 108552 5 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel,snd_hda_controller
    i915 864723 4
    drm_kms_helper 49262 1 i915
    snd_hwdep 17244 1 snd_hda_codec
    snd_pcm 88487 4 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_controller
    iTCO_wdt 12831 0
    iTCO_vendor_support 12649 1 iTCO_wdt
    coretemp 12820 0
    hwmon 12930 1 coretemp
    led_class 12859 1 ath9k
    intel_rapl 17356 0
    rfkill 18867 3 cfg80211,bluetooth
    x86_pkg_temp_thermal 12951 0
    psmouse 102792 0
    drm 258005 6 i915,drm_kms_helper
    intel_powerclamp 17122 0
    kvm_intel 143217 0
    snd_timer 26614 1 snd_pcm
    shpchp 35210 0
    lpc_ich 20768 0
    mei_me 17941 0
    intel_gtt 17848 1 i915
    kvm 413027 1 kvm_intel
    crct10dif_pclmul 13394 0
    crc32_pclmul 12915 0
    crc32c_intel 21809 0
    ghash_clmulni_intel 12978 0
    cryptd 18553 1 ghash_clmulni_intel
    microcode 22061 0
    evdev 21544 29
    pcspkr 12595 0
    mac_hid 12633 0
    i2c_algo_bit 12744 1 i915
    i2c_i801 16965 0
    mei 75033 1 mei_me
    serio_raw 12849 0
    i2c_core 50152 7 drm,i915,i2c_i801,drm_kms_helper,i2c_algo_bit,v4l2_common,videodev
    tpm_tis 17134 0
    thermal 17559 0
    fan 12681 0
    battery 13356 0
    snd 69340 16 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel
    soundcore 13031 2 snd,snd_hda_codec
    tpm 31467 1 tpm_tis
    video 17995 1 i915
    button 12909 1 i915
    processor 27777 0
    xt_limit 12601 7
    wmi 17339 0
    ac 12715 0
    xt_tcpudp 12527 11
    xt_addrtype 12557 4
    nf_conntrack_ipv4 17706 7
    nf_defrag_ipv4 12483 1 nf_conntrack_ipv4
    xt_conntrack 12681 7
    ip6_tables 26025 0
    nf_conntrack_netbios_ns 12445 0
    nf_conntrack_broadcast 12365 1 nf_conntrack_netbios_ns
    nf_nat_ftp 12460 0
    nf_nat 22338 1 nf_nat_ftp
    nf_conntrack_ftp 16783 1 nf_nat_ftp
    nf_conntrack 87324 7 nf_nat_ftp,nf_conntrack_netbios_ns,nf_nat,xt_conntrack,nf_conntrack_broadcast,nf_conntrack_ftp,nf_conntrack_ipv4
    iptable_filter 12536 1
    ip_tables 26011 1 iptable_filter
    x_tables 27104 10 xt_comment,ip_tables,xt_tcpudp,xt_limit,xt_conntrack,xt_LOG,iptable_filter,ipt_REJECT,ip6_tables,xt_addrtype
    ext4 497695 2
    crc16 12343 2 ext4,bluetooth
    mbcache 17171 1 ext4
    jbd2 86460 1 ext4
    hid_generic 12393 0
    usbhid 44507 0
    hid 102220 2 hid_generic,usbhid
    sd_mod 44356 5
    sr_mod 21903 0
    cdrom 47479 1 sr_mod
    crc_t10dif 12431 1 sd_mod
    crct10dif_common 12356 2 crct10dif_pclmul,crc_t10dif
    atkbd 22254 0
    libps2 12739 2 atkbd,psmouse
    ahci 29195 4
    libahci 27158 1 ahci
    libata 181553 2 ahci,libahci
    ehci_pci 12512 0
    scsi_mod 142915 3 libata,sd_mod,sr_mod
    xhci_hcd 152990 0
    ehci_hcd 69939 1 ehci_pci
    usbcore 199328 7 ath3k,btusb,uvcvideo,ehci_hcd,ehci_pci,usbhid,xhci_hcd
    usb_common 12440 1 usbcore
    i8042 18002 1 libps2
    serio 18282 6 serio_raw,atkbd,i8042,psmouse
    EDIT:
    cat /var/log/Xorg.0.log| grep Synap
    [ 301.566] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event9)
    [ 301.566] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
    [ 301.566] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
    [ 301.566] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default clickpad buttons"
    [ 301.566] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
    [ 301.566] (II) Using input driver 'evdev' for 'SynPS/2 Synaptics TouchPad'
    [ 301.566] (**) SynPS/2 Synaptics TouchPad: always reports core events
    [ 301.566] (**) evdev: SynPS/2 Synaptics TouchPad: Device: "/dev/input/event9"
    [ 301.566] (--) evdev: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
    [ 301.566] (--) evdev: SynPS/2 Synaptics TouchPad: Found 3 mouse buttons
    [ 301.566] (--) evdev: SynPS/2 Synaptics TouchPad: Found absolute axes
    [ 301.566] (--) evdev: SynPS/2 Synaptics TouchPad: Found absolute multitouch axes
    [ 301.566] (--) evdev: SynPS/2 Synaptics TouchPad: Found x and y absolute axes
    [ 301.566] (--) evdev: SynPS/2 Synaptics TouchPad: Found absolute touchpad.
    [ 301.566] (II) evdev: SynPS/2 Synaptics TouchPad: Configuring as touchpad
    [ 301.566] (**) evdev: SynPS/2 Synaptics TouchPad: YAxisMapping: buttons 4 and 5
    [ 301.567] (**) evdev: SynPS/2 Synaptics TouchPad: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 301.567] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 16)
    [ 301.567] (II) evdev: SynPS/2 Synaptics TouchPad: initialized for absolute axes.
    [ 301.567] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
    [ 301.567] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 0
    [ 301.567] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
    [ 301.567] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
    [ 301.567] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse1)
    [ 301.567] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates"
    (EE) [dix] SynPS/2 Synaptics TouchPad: unable to find touch point 1
    EDIT2:
    SOLVED!
    just remove /etc/X11/xorg.conf.d/10-evdev.conf
    Last edited by drog (2014-08-21 13:29:49)

    lordheavy wrote:
    X reads first configuration in /usr/share/X11/xorg.conf.d then /etc/X11/xorg.conf.d
    When you copy 10-evdev.conf file into /etc/X11 you completly override previous system configuration. It's the reason copying synaptics configuration file into /etc/X11 fixes the issue
    Defining default system configuration in /etc/X11 with previous xorg was a mistake, now it's fixed.
    Wiki should be fixed. It's not a packaging bug, but a configuration bug.
    @lordheavy
    I agree with you that the new xf86-input-synaptics package is using the right configuration scheme, however it is breaking the functionality on every installed system. It was a packaging bug, which is now fixed, but it has to be handled manually by most users of previous versions. That's why I won't re-open the bug report FS#41589. Instead, I am asking here: shouldn't this change be notified to the users just like it has been done for most breaking changes on archlinux frontpage news?
    By the way, thanks for your great work.

  • [Solved]Dual Monitor Setup

    So, I inherited a new monitor from my friend just a couple days ago and had a go at setting it up. Here's my current setup, to illustrate:
    -- MOD EDIT -- Please follow image posting rules
    The one on the right is mirroring the left at the moment, which happened via default when I booted up. I have the monitor to the left plugged via a dvi cable, and the one to the right that is rotated (for the purpose of better viewing webpages) with plain old vga. Both are running off my only graphics card, a Radeon X300:
    $ lspci | grep VGA
    01:00.0 VGA compatible controller: ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)]
    Here is the compatible resolutions and refresh rates and such for each:
    $ xrandr
    Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 4096 x 4096
    VGA-0 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 376mm x 301mm
    1280x1024 60.0*+ 75.0
    1152x864 75.0
    1024x768 75.1 60.0
    800x600 75.0 60.3
    640x480 75.0 60.0
    720x400 70.1
    DVI-0 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 450mm x 280mm
    1680x1050 60.0 +
    1280x1024 75.0 60.0*
    1440x900 75.0 59.9
    1152x864 75.0 70.0 60.0
    1024x768 75.1 70.1 60.0
    832x624 74.6
    800x600 72.2 75.0 60.3 56.2
    640x480 72.8 75.0 66.7 60.0
    720x400 70.1
    S-video disconnected (normal left inverted right x axis y axis)
    So, this information aside, I went and tried to add my second screen and make everything happy, I used the dual screen section in the X.Org Wiki page, which I believe was for the nVidia users, but I couldn't find any direction otherwise, so I figured with a few changes it could work with my radeon just fine. I am on xorg-server 1.9.4.901-1 with openbox as my window manager, no complete DE.
    This is my current /etc/X11/xorg.conf.d/10-monitor.conf written for two monitors, which at the moment does not work, saying no screens found when I run startx:
    Section "ServerLayout"
    Identifier "DualScreen"
    Screen 0 "Screen0"
    Scren 1 "Screen1" RightOf "Screen0" #Screen1 is to the right of Screen0
    Option "Xinerama" "1" #To move windows between screens, set to 1
    EndScetion
    Section "Monitor"
    Identifier "Monitor0"
    Option "Enable" "true"
    EndSection
    Section "Monitor"
    Identifier "Monitor0"
    Option "Enable" "true"
    EndSection
    Section "Device"
    Identifier "Device0"
    Driver "radeon"
    Screen 0
    EndSection
    Section "Device"
    Identifier "Device1"
    Driver "radeon"
    Screen 1
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Device0"
    Monitor "Monitor0"
    DefaultDepth 24
    Option "TwinView" "0" #Set to 1 to make both monitors act as one big screen, with no distinction between the two
    SubSection "Display"
    Depth 24
    Modes "1680x1050_60.00"
    EndSubSection
    EndSection
    Section "Screen"
    Identifier "Screen1"
    Device "Device1"
    Monitor" "Monitor1"
    DefaultDepth 24
    Option "TwinView" "0"
    SubSection "Display"
    Depth 24
    Modes 1280x1024_75.00
    EndSubSection
    EndSection
    And here is the same file, in a working configuration:
    Section "Monitor"
    Identifier "Monitor0"
    EndSection
    Section "Device"
    Identifier "Device0"
    Driver "radeon" #Driver used for this monitor
    EndSection
    Section "Screen"
    Identifier "Screen0" #Collapse Monitor and Device section to Screen section
    Device "Device0"
    Monitor "Monitor0"
    DefaultDepth 24 #Choose the Depth (16 || 24) (24 for true colour)
    Subsection "Display"
    Depth 24
    Modes "1680x1050_75.00" #Choose the resolution
    EndSubSection
    EndSection
    This leaves me with 3 questions I cannot seem to figure out:
    1) What did I do wrong with the non-working xorg config file, giving the error "no screens found"?
    2) Another extra twist of difficulty comes from the rotated monitor on the right.  How should I adopt for that, with resolutions and such?
    3) Xinerama/Twinview  - I am confused which one of these I should choose, what they offer over the other, or should I just not bother at all?
    I would like, in a "perfectly good configuration", windows to be able to move from each monitor to the other, the monitors to be two distinct monitors (ie. they don't mirror each other), a maximized window to only fill up just the one monitor (and not both), and finally, fullscreen programs (like games and such) only fullscreen to the monitor they are on. Is such a configuration possible with all of these parameters?
    -Scott
    Last edited by Inxsible (2011-06-05 18:33:38)

    BurntSushi wrote:
    Your desired configuration is quite common, and indeed, is the default setup provided by Openbox---once the monitors are properly configured, of course :-)
    Anywho, modifying xorg.conf files for something like this is a thing of the past, man. (Incidentally, you have made the lethal mistake of assuming an nvidia config will work with an ATI card. For example, "TwinView" is only available when you are using the nvidia proprietary driver.)
    Judging by your use of "radeon" as your video driver, it looks like you're using xf86-video-ati. Therefore, congratulations, xrandr will rescue you :-) (This should also be the case if you you're using the Catalyst driver.)
    thinkwiki should be enough to get your feet wet. Note: This guide is a bit dated, but 90% of it is still relevant and useful. For example, it claims that you need to modify your xorg.conf to add a Virtual screen size---this is only true if kernel modesetting is disabled. If it's enabled (and it should be if you're using xf86-video-ati), then you're good to go. If you're using Catalyst, you will have had to disable KMS. So you'd either have to add a Virtual screen to use xrandr, or configure your monitor setup with amdcccle.
    Finally, you asked about rotation. I don't think this is anything that `man xrandr` can't answer, and you should be okay as far as support goes---rotation was added in RandR 1.2, which any civilized video driver should support. (Except nvidia blob.)
    Anywho, feel free to come back with more questions if you have any!
    (For terminology sake, this means you will be using neither Xinerama nor TwinView to configure your multi-monitors. You will be using RandR if you use xrandr. Interestingly, your screen setup will still be reported to Openbox via the Xinerama extension. You may be interested in a utility like `lxrandr` if the command line frightens you.)
    Xrandr does the job elegantly, thanks! It's a simple matter of putting the commands I needed in openbox's autostart.sh. Thanks for pointing me in the right direction.
    #xrandr --output DVI-0 1680x1050 --output VGA-0 1280x1024 --right-of DVI-0
    # xrandr --output VGA-0 --rotate left
    Scott

Maybe you are looking for