Geforce GTX 980 TI

Aspire Acer G3 605 PredatorGPU: GeForce GTX 980CPU: intel(R) Core(TM) i5-4590 CPU @ 3.30GHzMemory: 12.00 GB RAM (11.92 GB Usable)Current Resolution: 1920 x 1080, 30HzDriver Version: 353.30Operating System: Microsoft Windows 8.1 Pro I am pretty sure its a 500+ PSU thats in there the needed PSU for a Geforce GTX 980 TI would be a 600+ or 650+ however after doing some reading,  statement was made where by this was said..... so i went out and bought a 650 psu and the 980 Ti. turns out this Acer pc uses some stupid 12 pin connector that no other pc uses.I would assume that connector is for the PSU as opposed to the GPU, either way do we have a PSU that will fit straight in so i could use a GTX 980 GPU ?

Hello Durand1981,  So the bottomline here comes down to this: Gateway(now owned by Acer) used proprietary 12v connectors for their motherboards. This connector is unique to their products and create a very difficult environment for those who choose to upgrade their PSUs.  However, despite the difficulty of circumventing the proprietary wiring, there is a solution to this. It comes in the form of a DYI rewiring to attach an adaptor to make a 24-pin AT connector compatible with the 12v rail. You can follow the instructions here if you wish to explore this option.   I personally would recommend getting a new motherboard to compliment your new GPU to ensure there are no compatibility issues -- though this may void your OEM Windows OS license. It's the easiest, albeit most expensive solution, but it also provides an additional layer ensuring that your system is prepared for future upgrades and enchancements that this proprietary mobo+PSU combo almost prohibits. 

Similar Messages

  • After Effects rendern über GPU mit GeForce GTX 980

    Hallo
    Mein Problem ist: Ich kann im After Effects nicht über meine neue Grafikkarte (GTX 980) über GPU rendern.
    Was muss ich tun damit ich über GPU rendern kann? Kann mir jemand Helfen?
    Facts:
    Programmversion: Adobe After Effects CC 2014.1.1 (Version 13.1.1.3.) Auf dem neusten Stand
    Grafikkarte: GeForce GTX 980
    Treiber: Nivida-Treiber auf dem neusten Stand (Cuda wird unterstützt)
    System: Windows 8.1, 64 Bit, , Prozessor i7-4770K, 3.5 Ghz, RAM 32GB,
    Dies habe ich bereits ausprobiert:
    CUDA-Hack: In die Datei "raytracer_supported_cards.txt" meine Grafikkarte reingeschrieben (ohne Schreibfehler ) -> funktioniert leider nicht
    Weiss jemand eine Lösung? oder kann mir Weiterhelfen?
    Besten Dank bereits im Vorraus für Feedbacks
    Dani

    pupsi123 schrieb:
    Was muss ich tun damit ich über GPU rendern kann?
    Eine GPU verwenden, die von After Effects unterstützt wird. Eventuell nicht den neuesten Treiber nehmen. Warum werden Treiber so oft aktualisiert? Weil auch mit jeder Version neue Bugs entstehen.

  • NVIDIA GEFORCE GTX 980 supported by Adobe CC?

    Hey Adobe,
    Quick question: I'm upgrading my PC and need to know;
    Is the NVIDIA GEFORCE GTX 980 Graphics card (GPU) supported by Adobe CC?
    Specifically premier Pro / After effects / Photoshop and Audition.
    It's not on your list of supported cards page...
    Thanks!

    The GTX 980 works well with:
    "Specifically premier Pro / After effects / Photoshop and Audition"
    The only GPU acceleration worth talking about is Premiere Pro, and yes it does that fine.

  • MSI Gtx 980 core voltage LOCKED !

    I just put my msi gtx 980 4g into my pc, was gonna take some benchmark testing and overclock, but i found out that in the msi afterburner, the core voltage is locked. now this is weird i think, im really new to overclocking, but iknow with all the money i spendt on the 980 that option should be UNLOCKED !
    Any help to get ? Thank you.
    My PC specs:
    MSI Geforce gtx 980 4G
    ASROCK h87M pro4 Motherboard
    16 gig ram
    i5 4670k processor
    600watt powersupply
    256 gig ssd
    1tb harddisk
    some fans, some led lights, and uh yea thats it.

    Quote from: shahabi-89 on 17-December-14, 00:14:30
    @Nichrome Off-topic
    But can you please help me with the new bios for gtx 970.
    I did as Svet asked and created a new topic with bios attached and S/N. But he is offline now and hopefully you can help me.
    Continue with your own topic then.
    Quote from: shahabi-89 on 17-December-14, 00:14:30
    @partynachim, sorry for loaning your thread..
    Instead of hijacking 

  • GeForce GTX 970 & 980: Availability of free copies of Witcher 3 & Batman Arkham Knight?

    Does Best Buy have plans to support NVIDIA's promotion of free codes for Witcher 3 & Batman Arkham Knight?
    Details regarding Nvidia's promotion is available (removed per forum guidelines)
    I have my eye on purchasing a PNY GeForce GTX970 from Best Buy & hope I can obtain both of these games when buying...

    Hello Joe_Fongul,
    Thank you for posting on the forums and your interest in purchasing the GeForce GTX 970 & 980!  
    At this current time, we are offering the Witcher 3: Wild Hunt with the purchase of the GeForce GTX 960.  Please continue to check the links above for further details and future promotions.  
    Thank you again for reaching out and we really do value your business.  
    Blake|Social Media Specialist | Best Buy® Corporate
     Private Message

  • MSI GeForce Gtx 970 Coil Whine noise threw headset/stereo

    Hi, I recently got an MSI GeForce Gtx 970 and for some odd reason, when I boot up a game it starts making some sort of Coil Whine noise which is not coming from my computer, it's coming from my headset or stereo. The noise kind of sounds like an electric tooth brush. And I have read many reviews on this graphics card and people are saying that they are hearing a Coil Whine noise coming from the graphics card, but me it's my headset. It may be an interference. Anyone have any ideas?

    Quote from: stephenapthorp on 11-January-15, 23:58:19
    Hey man,
    I am not sure about this completely but I know my buddy has a gtx 980 and he gets coil whine. It also affects his headphones when they are plugged in. He told me the sound is much better when he got a set of USB head phones. G430 ones I think.
    Regards
    Steve
    Thanks for the tip!

  • GeForce 970/980 - Maxwell Cuda Support

    Hi. I recently bought myself a GeForce 970 GFX card for my PC. I did see however that this card uses a Maxwell Cuda, which is not yet supported by Adobe Premiere (sure you can use the workaround and use it as an unsupported Cuda card, but according to all the forums I have read, this does not make full use of the cards processing capabilities)  - and I wanted to know if Adobe is looking into this, and by when do they expect to have support for Maxwell CUDA and subsequently the GeForce 970/980 cards?
    GTX 970 and Premiere Pro

    Hi!
    I just bought my EVGA GeForce GTX 970 SC and installed it into my PC (specs below). I did everything i could possibly do, like editing the cuda support file, selecting MEP(Cuda) in preferences, updating my drivers and even installing the CUDA Toolkit that nVidia provides. I can't find any way to make my GPU work! Exporting a 5min video with warp stabilizer took me 17min ! Can someone explain me how they got their GPUs working? (BTW, using Premiere Pro CC 2014.1 and 347.09 driver)
    PC Specs
    Motherboard: Asus Maximus VI Formula
    CPU: Intel Core i7 4770k Cuad-Core (4.2 GHz OC)
    RAM: Corsair Vengeance Pro 16gb 1600 MHz
    SSD: Samsung 840 EVO 250 Gb
    HDD: Western Digital Green 1Tb
    Video Card: EVGA GeForce GTX 970 SC
    Power Supply: Carsair RM1000 1000w 80plus GOLD

  • GTX 980 Ti dead?

    I purchased an MSI GTX 980 Ti a week ago. It has been working perfectly until today. Upon turning on my PC windows 7 froze on boot and artifacts filled the screen. It shut down and said installation eeded repair. Repair could not be completed, so I reinstalled Windows 7. Everything works fine until I load the driver for the GTX 980 Ti (Nvidia 353.06) and the same problems occurs, with the system freezing on restart. Is the card dead? I am at a loss.

    Sorry, was using my mobile. Specs:
    Intel i7 4790k
    Gigabyte Z97-UD3H
    OCZ Technology 600watt PSU
    16GB Corsair Vengeance DDR3 RAM (edited - my fault)
    Windows 7 64 Bit
    The drivers were removed with a full reinstall of Windows. The system then powers up fine, using Microsoft standard VGA driver. However, changing the screen resolution to highest results in artifacts on the screen again.
    There is currently only 1 driver for this card which is what I am using. MSI directs you to use Geforce Experience to update.
    I don't have another PC to use I'm afraid, so I'm forced to try and run with logic. The system ran fine using the same Nvidia Driver for the past week, but now I get this.

  • MSI GeForce GTX 970 with MSI Z68A-GD55 (G3) motherboard

    Hi!
    I have seen a similar issue here that was resolved with the help of this forum. (https://forum-en.msi.com/index.php?topic=251322.0). I still want to ask my questons however, since I have a slightly different situation.
    I recently bought a new Graphics card, a MSI GTX 970, to replace my older EVGA GTX 570. After installing it, the time it takes to startup the computer is quite a bit longer. The very begninning of the startup process is the part that takes longer, I see a black screen and "B2" in the lower right hand corner, with the older GPU this was seen for a few seconds but now it stays that way for about a minute. After that I see some random colors in stead of the MSI logo and then the regular "Starting Windows" image appears, from there the startup is as fast as before.
    When the computer has started it seems to work perfectly, and the new graphics card is great, everything on "ultra" in games etc.
    I guess the way to resolve this issue is to update BIOS. I am a bit afraid of this however, of the risk of destroying something.
    What would be your suggestions? Is it better to update bios or to leave it as it is, since the computer works? Are the any risks with keeping this bios version, that seems to have some issue with the graphics card?
    Any help would be greately appreciated!
    /Johan
    Board: MSI Z68A-GD55 (G3)
    Bios: Version 23.7
    VGA: MSI GeForce GTX 970 Gaming 4GB
    PSU:  Corsair TX 750W Modular
    MEM: G.Skill Ripjaws X Performance 2x4GB
    CPU:  Intel Core i5-2500K Sandy Bridge 3.3GHz – not overclocked
    System Harddrive:  SSD 120GB Corsair SATA 2.5", Force 3 Series
    Extra Harddrive: 1TB Samsung SP SATA-2* 7200RPM Spinpoint F3
    OS: Windows®7 Home 64-bit
    Cooling: Standard fans from the case (Fractal Design Define R3) and for the CPU plus one Scythe Slip Stream 140mm (1200rpm)

    Ok, thanks for the advice.
    I have started looking at the instructions and have downloaded the installer and the bios file. It seems Norton Internet Security has some problem with the installer.  When I start the installer it reaches the point when it shows the current bios version, after that it is interupted by Norton. The reason that Norton gives is that it has found something called "Suspicious.Cloud.9.B" in the file b4.bks. How should I react to this?

  • MSI GeForce GTX 560Ti "Twin Frozr II" crash at 50 degrees Celsius

    I get artifacts (pink squares all over screen) in heaven benchmark, fluid benchmark and gta 4,  a few seconds  later I get a black screen and then an error message there windows tell me the driver has crash but praise msi it was successfully recovered. All this then the card is nearing 50 degrees Celsius.
    I have:
    MSI GeForce GTX 560Ti "Twin Frozr II", (BIOS: 70.24.0a.00.00)
    Gigabyte GA-890GPA-UD3H, Socket-AM3
    AMD Phenom II X4 965 Black Edition
    Corsair Powersupply 650W Black,ATX/EPS
    Corsair XMS3 DDR3 1600MHz 4GB CL9
    Windows 7 64bit (with sp1)
    DC OUTPUT    +3.3V +5V  +12V -12V  +5Vsb
    MAX LOAD    24A    30A  52A   0.8A   3A
    I tested driver on msi site and the latest nvidia driver, even tested some beta driver. All give the same result as stated above. I also tested to set the clocks at reference speed but no go. Also tested voltage at 1025.

    Got a new card today, same card but new.
    No problems now, seem the new card has newer bios and lower  core voltage. Maybe that is a way to fix it, just upgrade bios.

  • Mercury CUDA not enabling when using NVIDIA GeForce GTX 285 on Apple Mac Pro after Mavericks install

    Been using the same setup since CS5 with the Mercury CUDA running perfectly. After recent upgrade of OS X to 10.9 Mercury CUDA is no longer available and only lets me run with the OpenGL or software options. Im using a NVIDIA GeForce GTX 285 for apple computers. Here are the results for the GPUSniffer program in the latest Premiere Pro 7.1.0 files. The LAST line make me chucle because it the first on the list of supported card in the "cuda_supported_cards.txt" file. Anybody else seen this?
    --- OpenGL Info ---
    Vendor: NVIDIA Corporation
    Renderer: NVIDIA GeForce GTX 285 OpenGL Engine
    OpenGL Version: 2.1 NVIDIA-8.18.27 310.40.05f01
    GLSL Version: 1.20
    Monitors: 1
    Monitor 0 properties -
       Size: (0, 0, 1920, 1080)
       Max texture size: 8192
       Supports non-power of two: 1
       Shaders 444: 1
       Shaders 422: 1
       Shaders 420: 1
    --- GPU Computation Info ---
    Found 1 devices supporting GPU computation.
    OpenCL Device 0 -
       Name: GeForce GTX 285
       Vendor: NVIDIA (Apple platform)
       Capability: 1.2
       Driver: 1
       Total Video Memory: 1024MB
       * Not enabled by default because it did not match the named list of cards.

    found a link from a couple of days ago on a creative cow forum post one of the poster saying they are from adobe stating this
    Re: Mercury Playback Engine MacPro
    by Peter Garaway on Nov 12, 2013 at 9:49:16 am
    Hi Wendell,
    Sorry for the inconvenience. NVIDIA is currently working on drivers that support CUDA on Mavericks 10.9 with some of the older NVIDIA cards such as the GTX 285 and the Quadro 4800.
    For others interested, the Quadro 4000, K5000 and GTX 680 ect... work with CUDA in 10.9.
    Best,
    Peter Garaway
    Adobe
    Premiere Pro
    I have latest CUDA drivers, so i guess i am just waiting till a proper update that have the fixes to support my card.

  • MSi GE70 Apache Pro w/ nVidia GeForce GTX 860M Graphics Issues

    Hi there,
    I recently purchased an MSi gaming notebook with nVidia GTX 860M graphics. However, just recently I've been having game-breaking issues with textures rendering, artifacts and particles as well as the drivers crashing now and again(desktop flashing and flickering).
    I've only had this laptop for just over two months and am quite disappointed with issues coming up already.
    To get to the specifics; I have recently been playing through the Mass Effect trilogy and, just the other day, started up a file in Skyrim. The following screenshots show my biggest issues aside from the obviously serious driver crashing issues. I believe the issues started maybe a month into owning this laptop and since it has been getting progressively worse. I feel as though I have been all over the internet trying to find a fix to this, I've tried everything suggested, everything that I could think of, and I am just about ready to have it sent back. I was hoping someone may have some other options before I do send it in.
    https://www.dropbox.com/s/d8koa8f8i1z9j3d/Photo%202014-09-30%2C%201%2040%2044%20AM.jpg?dl=0
    On the title screen for Mass Effect 3 I get these consistent blue and red glowing orbs, they also occur on several other maps within gameplay.
    https://www.dropbox.com/s/a9c47w320u5xylb/Photo%202014-09-30%2C%201%2043%2016%20AM.jpg?dl=0
    Once I get in-game, this occurs everywhere. Textures "expanding" off of characters into random points.
    https://www.dropbox.com/s/v37un4vespalosx/Photo%202014-09-30%2C%201%2045%2036%20AM.jpg?dl=0
    This happens occassionally on characters; ridiculously shadowed faces to the point where they are barely recognisable.
    https://www.dropbox.com/s/8cebgs4t10ghnh0/Photo%202014-09-30%2C%201%2046%2020%20AM.jpg?dl=0
    On almost all wall textures there are white glowing particles like the ones behind the character here. In extreme cases, the wall becomes a texture of textures. All of the textures in the game are miniaturized into a wall of textures on certain objects.
    I've also had signs and the game's menus and interface stretched and skewed all over the place. If I continue to play it with the above issues, the game eventually hangs and I have to alt+tab out and back in, or close it using the task manager. All of these issues also occur in Skyrim and any game using the same, or similar, engines. The only game I have been able to play almost seamlessly without any issues is Ragnarok Online 2, an online MMORPG.
    I have tried the following:
    nVidia's GeForce Control Panel: any and all combination of options.
    Re-installing video drivers.
    Re-installing DirectX and PhysX.
    Formatting and a fresh install of Windows and all games and drivers.
    Any other troubleshooting other forums have provided.
    Removing the pagefile for virtual memory limits.
    Using Intel HD graphics to test for other issues.
    PC/nVidia power settings.
    The one time I thought it may be fixed, all it took was me plugging in my laptop to cause the issues all over again. I've tried downloading MSi Afterburner to check GPU temperatures and I rarely even go over 65~70. I'm absolutely out of ideas. It was suggested to me by a family member that it may be a hardware issue, hence the consideration for sending it in.
    I'm running Windows 7 64-bit
    nVidia GeForce GTX 860M
    Intel Core i7-4710HQ CPU @ 2.50GHz
    12GB of RAM
    Any ideas/help would be greatly appreciated. I would really rather not have to send it back. I've also posted this over at the nVidia forums because I'm -hoping- it's a software issue.
    Thanks in advance!

    Quote
    It was suggested to me by a family member that it may be a hardware issue, hence the consideration for sending it in.
    Quote
    To me it sounds like a hardware issue (especially if you have rolled back to factory default and reinstalled from scratch)
    It wouldn't be a hardware issue since you can play other games without problem.
    Easiest way to tell if it's a hardware issue or not is to run the benchmark tool for example 3DMark 11 and see if the problem also happens during the benchmark.
    For the rendering problem you were talking, please provide not only the problem picture but also the picture without problem to let us make the comparison.
    I'm sorry to say, but some of the picture I'm not really getting what the problem you're talking about.
    For the shadow face, here are few user provided fix which might be helpful.
    http://forums.steampowered.com/forums/showthread.php?t=2282965
    http://forum.bioware.com/topic/55984-shadows-way-too-darkblack-intendedscreenshot-solved/
    Quote
    Re-installing DirectX and PhysX.
    NVIDIA moderator says some of the games is required to play some older Physx games, but not sure if it works.
    If you would like to have a try.
    https://forums.geforce.com/default/topic/524066/geforce-drivers/official-nvidia-r310-61-beta-display-driver-feedback-thread-released-11-20-12-/post/3714758/#3714758
    I'd suggest to post the issue on EA, steam or obioware and see if there are people looking into it.

  • Problem with 3 monitors Intel HD Graphics and GeForce GTX 560

    I would like to attach 3 monitors to my box -- 1 to integrated Intel card and 2 to discreet Nvidia. I've tried different configs but I failed to make monitors connected to different cards to work at the same time. I have system with stock kernel, latest updates and the following configuration:
    $ lspci | egrep "VGA|Disp"
    00:02.0 Display controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
    01:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 Ti] (rev a1)
    $ pacman -Qi xorg-server xf86-video-intel nvidia awesome-git linux | egrep "Name|Version"
    Name : xorg-server
    Version : 1.17.1-3
    Name : xf86-video-intel
    Version : 2.99.917-3
    Name : nvidia
    Version : 346.47-3
    Name : awesome-git
    Version : 3.5.2.397.gdde5b1b-1
    Name : linux
    Version : 3.18.6-1
    $ lsmod | egrep 'i915|nvidia'
    nvidia 8335766 46
    i915 946695 2
    button 12953 1 i915
    i2c_algo_bit 12744 1 i915
    video 18043 2 i915,asus_wmi
    drm_kms_helper 80985 1 i915
    drm 263481 7 i915,drm_kms_helper,nvidia
    i2c_core 50152 6
    drm,i915,i2c_i801,drm_kms_helper,i2c_algo_bit,nvidia
    intel_gtt 17848 2 i915,intel_agp
    I've tried different xorg configs. Here is the best one. All 3 monitors are active with it (I could drag cursor over them) but only 2 (which connected to nvidia card) display DE.
    Section "DRI"
    Mode 0666
    EndSection
    Section "Monitor"
    Identifier "SAM"
    ModelName "Samsung SMS27A850"
    HorizSync 30.0 - 90.0
    VertRefresh 56.0 - 75.0
    Option "DPMS"
    DisplaySize 597 336 # In millimeters
    EndSection
    Section "Monitor"
    Identifier "VS"
    ModelName "ViewSonic VG1930wm"
    Option "DPMS"
    Option "RightOf" "SAM"
    Option "Rotate" "left"
    EndSection
    Section "Monitor"
    Identifier "BNQ"
    ModelName "BenQ FP737s"
    Option "DPMS"
    Option "LeftOf" "SAM"
    Option "Rotate" "left"
    EndSection
    Section "Device"
    Identifier "nvidia"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce GTX 560 Ti"
    BusID "01:00:0"
    Option "Monitor-DVI-I-1" "SAM"
    Option "Monitor-DVI-I-2" "VS"
    EndSection
    Section "Device"
    Identifier "intel"
    Driver "intel"
    Option "AccelMethod" "none"
    VendorName "Intel"
    BoardName "Intel Integrated Graphic Controller"
    BusID "00:02:0"
    Option "Monitor-VGA-0" "BNQ"
    EndSection
    Section "Screen"
    Identifier "SAM-Screen"
    Device "nvidia"
    Monitor "SAM"
    EndSection
    Section "Screen"
    Identifier "VS-Screen"
    Device "nvidia"
    Monitor "VS"
    EndSection
    Section "Screen"
    Identifier "BNQ-Screen"
    Device "intel"
    Monitor "BNQ"
    EndSection
    Section "ServerLayout"
    Identifier "Layout0"
    Screen 0 "SAM-Screen"
    Screen 1 "VS-Screen" RightOf "SAM-Screen"
    Screen 2 "BNQ-Screen" LeftOf "SAM-Screen"
    Option "Xinerama" "0"
    EndSection
    Also, xrandr shows last monitor (VGA-0, it plugged into Intel card) as disconnected
    $ xrandr
    Screen 0: minimum 8 x 8, current 3460 x 1440, maximum 16384 x 16384
    DVI-I-0 disconnected primary (normal left inverted right x axis y axis)
    VGA-0 disconnected (normal left inverted right x axis y axis)
    DVI-I-1 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 518mm x 324mm
    2560x1440 59.95*+
    1920x1200 59.88
    1920x1080 60.00 50.00
    1680x1050 59.95
    1600x1200 60.00
    1440x900 59.89
    1280x1024 75.02 60.02
    1280x960 60.00
    1280x800 59.81
    1280x720 60.00 50.00
    1152x864 75.00
    1024x768 75.03 70.07 60.00
    800x600 75.00 72.19 60.32 56.25
    720x576 50.00
    720x480 59.94
    640x480 75.00 72.81 59.94
    HDMI-0 disconnected (normal left inverted right x axis y axis)
    DVI-I-2 connected 900x1440+2560+0 left (normal left inverted right x axis y axis) 410mm x 256mm
    1440x900 59.89*+ 74.98
    1280x1024 75.02 60.02
    1280x960 60.00
    1152x864 75.00
    1024x768 75.03 70.07 60.00
    800x600 75.00 72.19 60.32 56.25
    640x480 75.00 72.81 59.94
    640x400 70.10
    But it's still posible to start application on last monitor with 'env DISPLAY:=0.1 urxvt'
    Here is full Xorg log file and highlights:
    [ 4789.920] (EE) intel(1): Cannot position output VGA1 relative to unknown output SAM
    [ 4792.053] (EE) intel(G0): [drm] failed to set drm interface version: Permission denied [13].
    [ 4792.053] (II) intel(G0): [drm] Contents of '/sys/kernel/debug/dri/0/clients':
    [ 4792.053] (II) intel(G0): [drm] command pid dev master a uid magic
    [ 4792.053] (II) intel(G0): [drm] Xorg 10086 0 y y 0 0
    [ 4792.053] (II) intel(G0): [drm] Xorg 10086 0 n y 0 0
    [ 4792.053] (EE) intel(G0): Failed to claim DRM device.
    [ 4792.053] (II) UnloadModule: "intel"
    [ 4789.342]
    X.Org X Server 1.17.1
    Release Date: 2015-02-10
    [ 4789.342] X Protocol Version 11, Revision 0
    [ 4789.342] Build Operating System: Linux 3.18.6-1-ARCH x86_64
    [ 4789.342] Current Operating System: Linux earth 3.18.6-1-ARCH #1 SMP PREEMPT Sat Feb 7 08:44:05 CET 2015 x86_64
    [ 4789.342] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=dc49b07c-e67c-4b6f-91f7-7c1adc050e21 rw quiet ipv6.disable=1 init=/usr/lib/systemd/systemd security=tomoyo TOMOYO_trigger=/usr/lib/systemd/systemd
    [ 4789.342] Build Date: 22 February 2015 12:50:32PM
    [ 4789.342]
    [ 4789.342] Current version of pixman: 0.32.6
    [ 4789.342] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 4789.342] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 4789.342] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Mar 1 14:43:55 2015
    [ 4789.342] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 4789.342] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
    [ 4789.342] (==) ServerLayout "Layout0"
    [ 4789.342] (**) |-->Screen "SAM-Screen" (0)
    [ 4789.342] (**) | |-->Monitor "SAM"
    [ 4789.343] (**) | |-->Device "nvidia"
    [ 4789.343] (**) |-->Screen "VS-Screen" (1)
    [ 4789.343] (**) | |-->Monitor "VS"
    [ 4789.343] (**) | |-->Device "nvidia"
    [ 4789.343] (**) |-->Screen "BNQ-Screen" (2)
    [ 4789.343] (**) | |-->Monitor "BNQ"
    [ 4789.343] (**) | |-->Device "intel"
    [ 4789.343] (**) Option "Xinerama" "0"
    [ 4789.343] (==) Automatically adding devices
    [ 4789.343] (==) Automatically enabling devices
    [ 4789.343] (==) Automatically adding GPU devices
    [ 4789.343] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/OTF/,
    /usr/share/fonts/Type1/,
    /usr/share/fonts/100dpi/,
    /usr/share/fonts/75dpi/
    [ 4789.343] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 4789.343] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 4789.343] (II) Loader magic: 0x815d80
    [ 4789.343] (II) Module ABI versions:
    [ 4789.343] X.Org ANSI C Emulation: 0.4
    [ 4789.343] X.Org Video Driver: 19.0
    [ 4789.343] X.Org XInput driver : 21.0
    [ 4789.343] X.Org Server Extension : 9.0
    [ 4789.344] (EE) systemd-logind: failed to get session: PID 10086 does not belong to any known session
    [ 4789.345] (II) xfree86: Adding drm device (/dev/dri/card1)
    [ 4789.345] (II) xfree86: Adding drm device (/dev/dri/card0)
    [ 4789.347] (--) PCI: (0:0:2:0) 8086:0102:1043:84ca rev 9, Mem @ 0xf6400000/4194304, 0xd0000000/268435456, I/O @ 0x0000f000/64
    [ 4789.347] (--) PCI:*(0:1:0:0) 10de:1200:10b0:0401 rev 161, Mem @ 0xf4000000/33554432, 0xe0000000/134217728, 0xe8000000/67108864, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
    [ 4789.347] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    [ 4789.347] (II) LoadModule: "glx"
    [ 4789.347] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 4789.359] (II) Module glx: vendor="NVIDIA Corporation"
    [ 4789.359] compiled for 4.0.2, module version = 1.0.0
    [ 4789.359] Module class: X.Org Server Extension
    [ 4789.359] (II) NVIDIA GLX Module 346.47 Thu Feb 19 18:09:07 PST 2015
    [ 4789.359] (II) LoadModule: "nvidia"
    [ 4789.359] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
    [ 4789.360] (II) Module nvidia: vendor="NVIDIA Corporation"
    [ 4789.360] compiled for 4.0.2, module version = 1.0.0
    [ 4789.360] Module class: X.Org Video Driver
    [ 4789.360] (II) LoadModule: "intel"
    [ 4789.360] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
    [ 4789.360] (II) Module intel: vendor="X.Org Foundation"
    [ 4789.360] compiled for 1.17.1, module version = 2.99.917
    [ 4789.360] Module class: X.Org Video Driver
    [ 4789.360] ABI class: X.Org Video Driver, version 19.0
    [ 4789.360] (II) NVIDIA dlloader X Driver 346.47 Thu Feb 19 17:47:18 PST 2015
    [ 4789.360] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
    [ 4789.360] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
    i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
    915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
    Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
    GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
    [ 4789.360] (II) intel: Driver for Intel(R) HD Graphics: 2000-6000
    [ 4789.360] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100
    [ 4789.360] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200, 6200, P6300
    [ 4789.360] (++) using VT number 7
    [ 4789.471] (II) Loading sub module "fb"
    [ 4789.471] (II) LoadModule: "fb"
    [ 4789.471] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 4789.471] (II) Module fb: vendor="X.Org Foundation"
    [ 4789.471] compiled for 1.17.1, module version = 1.0.0
    [ 4789.471] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 4789.472] (II) Loading sub module "wfb"
    [ 4789.472] (II) LoadModule: "wfb"
    [ 4789.472] (II) Loading /usr/lib/xorg/modules/libwfb.so
    [ 4789.472] (II) Module wfb: vendor="X.Org Foundation"
    [ 4789.472] compiled for 1.17.1, module version = 1.0.0
    [ 4789.472] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 4789.472] (II) Loading sub module "ramdac"
    [ 4789.472] (II) LoadModule: "ramdac"
    [ 4789.472] (II) Module "ramdac" already built-in
    [ 4789.473] (II) intel(1): Using Kernel Mode Setting driver: i915, version 1.6.0 20140905
    [ 4789.474] (II) intel(G0): Using Kernel Mode Setting driver: i915, version 1.6.0 20140905
    [ 4789.474] (II) NVIDIA(0): Creating default Display subsection in Screen section
    "SAM-Screen" for depth/fbbpp 24/32
    [ 4789.474] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
    [ 4789.474] (==) NVIDIA(0): RGB weight 888
    [ 4789.474] (==) NVIDIA(0): Default visual is TrueColor
    [ 4789.474] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
    [ 4789.474] (**) NVIDIA(0): Enabling 2D acceleration
    [ 4789.841] (II) NVIDIA(GPU-0): Found DRM driver nvidia-drm (20150116)
    [ 4789.842] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 560 Ti (GF114) at PCI:1:0:0 (GPU-0)
    [ 4789.842] (--) NVIDIA(0): Memory: 1048576 kBytes
    [ 4789.842] (--) NVIDIA(0): VideoBIOS: 70.24.21.00.00
    [ 4789.842] (II) NVIDIA(0): Detected PCI Express Link width: 16X
    [ 4789.875] (--) NVIDIA(0): Valid display device(s) on GeForce GTX 560 Ti at PCI:1:0:0
    [ 4789.875] (--) NVIDIA(0): CRT-0
    [ 4789.875] (--) NVIDIA(0): CRT-1
    [ 4789.875] (--) NVIDIA(0): Samsung SMS27A850 (DFP-0) (boot, connected)
    [ 4789.875] (--) NVIDIA(0): DFP-1
    [ 4789.875] (--) NVIDIA(0): ViewSonic VG1930wm (DFP-2) (connected)
    [ 4789.875] (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
    [ 4789.875] (--) NVIDIA(GPU-0): CRT-1: 400.0 MHz maximum pixel clock
    [ 4789.875] (--) NVIDIA(0): Samsung SMS27A850 (DFP-0): Internal TMDS
    [ 4789.875] (--) NVIDIA(GPU-0): Samsung SMS27A850 (DFP-0): 330.0 MHz maximum pixel clock
    [ 4789.875] (--) NVIDIA(0): DFP-1: Internal TMDS
    [ 4789.875] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
    [ 4789.875] (--) NVIDIA(0): ViewSonic VG1930wm (DFP-2): Internal TMDS
    [ 4789.875] (--) NVIDIA(GPU-0): ViewSonic VG1930wm (DFP-2): 330.0 MHz maximum pixel clock
    [ 4789.875] (**) NVIDIA(0): Option "Rotate" "left"
    [ 4789.875] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 4789.875] (**) NVIDIA(0): device Samsung SMS27A850 (DFP-0) (Using EDID frequencies
    [ 4789.875] (**) NVIDIA(0): has been enabled on all display devices.)
    [ 4789.875] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
    [ 4789.875] (WW) NVIDIA(GPU-0): mode "1920x1080" is specified in the EDID; however, the
    [ 4789.875] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
    [ 4789.875] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
    [ 4789.875] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1920x1080".
    [ 4789.876] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
    [ 4789.876] (WW) NVIDIA(GPU-0): mode "1280x720" is specified in the EDID; however, the
    [ 4789.876] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
    [ 4789.876] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
    [ 4789.876] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1280x720".
    [ 4789.876] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
    [ 4789.876] (WW) NVIDIA(GPU-0): mode "720x576" is specified in the EDID; however, the
    [ 4789.876] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
    [ 4789.876] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
    [ 4789.876] (WW) NVIDIA(GPU-0): VertRefresh check for mode "720x576".
    [ 4789.877] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 4789.877] (**) NVIDIA(0): device ViewSonic VG1930wm (DFP-2) (Using EDID frequencies
    [ 4789.877] (**) NVIDIA(0): has been enabled on all display devices.)
    [ 4789.878] (==) NVIDIA(0):
    [ 4789.878] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
    [ 4789.878] (==) NVIDIA(0): will be used as the requested mode.
    [ 4789.878] (==) NVIDIA(0):
    [ 4789.878] (II) NVIDIA(0): Validated MetaModes:
    [ 4789.878] (II) NVIDIA(0):
    [ 4789.878] (II) NVIDIA(0): "DFP-0:nvidia-auto-select,DFP-2:nvidia-auto-select{Rotation=90}"
    [ 4789.878] (II) NVIDIA(0): Virtual screen size determined to be 3460 x 1440
    [ 4789.905] (--) NVIDIA(0): DPI set to (125, 114); computed from "UseEdidDpi" X config
    [ 4789.905] (--) NVIDIA(0): option
    [ 4789.906] (--) intel(1): Integrated Graphics Chipset: Intel(R) HD Graphics 2000
    [ 4789.906] (--) intel(1): CPU: x86-64, sse2, sse3, ssse3, sse4.1, sse4.2, avx
    [ 4789.906] (II) intel(1): Creating default Display subsection in Screen section
    "BNQ-Screen" for depth/fbbpp 24/32
    [ 4789.906] (==) intel(1): Depth 24, (--) framebuffer bpp 32
    [ 4789.906] (==) intel(1): RGB weight 888
    [ 4789.906] (==) intel(1): Default visual is TrueColor
    [ 4789.906] (**) intel(1): Option "AccelMethod" "none"
    [ 4789.906] (II) intel(1): Output VGA1 using monitor section BNQ
    [ 4789.906] (**) intel(1): Option "LeftOf" "SAM"
    [ 4789.906] (**) intel(1): Option "Rotate" "left"
    [ 4789.906] (II) intel(1): Enabled output VGA1
    [ 4789.906] (II) intel(1): Output HDMI1 has no monitor section
    [ 4789.906] (II) intel(1): Enabled output HDMI1
    [ 4789.906] (II) intel(1): Output DP1 has no monitor section
    [ 4789.906] (II) intel(1): Enabled output DP1
    [ 4789.906] (II) intel(1): Output HDMI2 has no monitor section
    [ 4789.906] (II) intel(1): Enabled output HDMI2
    [ 4789.906] (II) intel(1): Output HDMI3 has no monitor section
    [ 4789.906] (II) intel(1): Enabled output HDMI3
    [ 4789.906] (II) intel(1): Output DP2 has no monitor section
    [ 4789.906] (II) intel(1): Enabled output DP2
    [ 4789.906] (II) intel(1): Output DP3 has no monitor section
    [ 4789.906] (II) intel(1): Enabled output DP3
    [ 4789.906] (--) intel(1): Using a maximum size of 256x256 for hardware cursors
    [ 4789.906] (II) intel(1): Output VIRTUAL1 has no monitor section
    [ 4789.906] (II) intel(1): Enabled output VIRTUAL1
    [ 4789.906] (II) intel(1): EDID for output DP1
    [ 4789.906] (II) intel(1): EDID for output DP2
    [ 4789.906] (II) intel(1): EDID for output DP3
    [ 4789.906] (II) intel(1): EDID for output HDMI1
    [ 4789.906] (II) intel(1): EDID for output HDMI2
    [ 4789.907] (II) intel(1): EDID for output HDMI3
    [ 4789.920] (II) intel(1): EDID for output VGA1
    [ 4789.920] (II) intel(1): Manufacturer: BNQ Model: 7659 Serial#: 28
    [ 4789.920] (II) intel(1): Year: 2003 Week: 39
    [ 4789.920] (II) intel(1): EDID Version: 1.3
    [ 4789.920] (II) intel(1): Analog Display Input, Input Voltage Level: 0.700/0.700 V
    [ 4789.920] (II) intel(1): Sync: Separate Composite
    [ 4789.920] (II) intel(1): Max Image Size [cm]: horiz.: 34 vert.: 27
    [ 4789.920] (II) intel(1): Gamma: 2.20
    [ 4789.920] (II) intel(1): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
    [ 4789.920] (II) intel(1): First detailed timing is preferred mode
    [ 4789.920] (II) intel(1): redX: 0.640 redY: 0.340 greenX: 0.290 greenY: 0.611
    [ 4789.920] (II) intel(1): blueX: 0.140 blueY: 0.069 whiteX: 0.310 whiteY: 0.330
    [ 4789.920] (II) intel(1): Supported established timings:
    [ 4789.920] (II) intel(1): 720x400@70Hz
    [ 4789.920] (II) intel(1): 640x480@60Hz
    [ 4789.920] (II) intel(1): 640x480@67Hz
    [ 4789.920] (II) intel(1): 640x480@72Hz
    [ 4789.920] (II) intel(1): 640x480@75Hz
    [ 4789.920] (II) intel(1): 800x600@56Hz
    [ 4789.920] (II) intel(1): 800x600@60Hz
    [ 4789.920] (II) intel(1): 800x600@72Hz
    [ 4789.920] (II) intel(1): 800x600@75Hz
    [ 4789.920] (II) intel(1): 832x624@75Hz
    [ 4789.920] (II) intel(1): 1024x768@60Hz
    [ 4789.920] (II) intel(1): 1024x768@70Hz
    [ 4789.920] (II) intel(1): 1024x768@75Hz
    [ 4789.920] (II) intel(1): 1280x1024@75Hz
    [ 4789.920] (II) intel(1): 1152x864@75Hz
    [ 4789.920] (II) intel(1): Manufacturer's mask: 0
    [ 4789.920] (II) intel(1): Supported standard timings:
    [ 4789.920] (II) intel(1): #0: hsize: 1152 vsize 864 refresh: 75 vid: 20337
    [ 4789.920] (II) intel(1): #1: hsize: 1280 vsize 1024 refresh: 76 vid: 36993
    [ 4789.920] (II) intel(1): #2: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
    [ 4789.920] (II) intel(1): #3: hsize: 1280 vsize 1024 refresh: 72 vid: 35969
    [ 4789.920] (II) intel(1): Supported detailed timing:
    [ 4789.920] (II) intel(1): clock: 108.0 MHz Image Size: 338 x 270 mm
    [ 4789.920] (II) intel(1): h_active: 1280 h_sync: 1328 h_sync_end 1440 h_blank_end 1688 h_border: 0
    [ 4789.920] (II) intel(1): v_active: 1024 v_sync: 1025 v_sync_end 1028 v_blanking: 1066 v_border: 0
    [ 4789.920] (II) intel(1): Supported detailed timing:
    [ 4789.920] (II) intel(1): clock: 25.2 MHz Image Size: 304 x 228 mm
    [ 4789.920] (II) intel(1): h_active: 640 h_sync: 656 h_sync_end 752 h_blank_end 800 h_border: 0
    [ 4789.920] (II) intel(1): v_active: 350 v_sync: 387 v_sync_end 389 v_blanking: 449 v_border: 0
    [ 4789.920] (II) intel(1): Ranges: V min: 56 V max: 75 Hz, H min: 31 H max: 81 kHz, PixClock max 145 MHz
    [ 4789.920] (II) intel(1): Monitor name: BenQ FP737s
    [ 4789.920] (II) intel(1): EDID (in hex):
    [ 4789.920] (II) intel(1): 00ffffffffffff0009d159761c000000
    [ 4789.920] (II) intel(1): 270d01036c221b78eac6f6a3574a9c23
    [ 4789.920] (II) intel(1): 114f54bfef80714f81908180818c0101
    [ 4789.920] (II) intel(1): 010101010101302a009851002a403070
    [ 4789.920] (II) intel(1): 1300520e1100001ed50980a0205e6310
    [ 4789.920] (II) intel(1): 1060520830e41000001a000000fd0038
    [ 4789.920] (II) intel(1): 4b1f510e000a202020202020000000fc
    [ 4789.920] (II) intel(1): 0042656e51204650373337730a200072
    [ 4789.920] (II) intel(1): Printing probed modes for output VGA1
    [ 4789.920] (II) intel(1): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
    [ 4789.920] (II) intel(1): Modeline "1280x1024"x76.0 141.81 1280 1376 1512 1744 1024 1025 1028 1070 -hsync +vsync (81.3 kHz)
    [ 4789.920] (II) intel(1): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 4789.920] (II) intel(1): Modeline "1280x1024"x72.0 132.84 1280 1368 1504 1728 1024 1025 1028 1067 -hsync +vsync (76.9 kHz)
    [ 4789.920] (II) intel(1): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 4789.920] (II) intel(1): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
    [ 4789.920] (II) intel(1): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
    [ 4789.920] (II) intel(1): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 4789.920] (II) intel(1): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
    [ 4789.920] (II) intel(1): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
    [ 4789.920] (II) intel(1): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 4789.920] (II) intel(1): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 4789.920] (II) intel(1): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 4789.920] (II) intel(1): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 4789.920] (II) intel(1): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 491 520 -hsync -vsync (37.9 kHz e)
    [ 4789.920] (II) intel(1): Modeline "640x480"x66.7 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
    [ 4789.920] (II) intel(1): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 4789.920] (II) intel(1): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 4789.920] (II) intel(1): Modeline "640x350"x70.1 25.17 640 656 752 800 350 387 389 449 +hsync -vsync (31.5 kHz e)
    [ 4789.920] (II) intel(1): EDID for output VIRTUAL1
    [ 4789.920] (II) intel(1): Output DP1 disconnected
    [ 4789.920] (II) intel(1): Output DP2 disconnected
    [ 4789.920] (II) intel(1): Output DP3 disconnected
    [ 4789.920] (II) intel(1): Output HDMI1 disconnected
    [ 4789.920] (II) intel(1): Output HDMI2 disconnected
    [ 4789.920] (II) intel(1): Output HDMI3 disconnected
    [ 4789.920] (II) intel(1): Output VGA1 connected
    [ 4789.920] (II) intel(1): Output VIRTUAL1 disconnected
    [ 4789.920] (II) intel(1): Using user preference for initial modes
    [ 4789.920] (II) intel(1): Output VGA1 using initial mode 1280x1024
    [ 4789.920] (EE) intel(1): Cannot position output VGA1 relative to unknown output SAM
    [ 4789.920] (II) intel(1): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
    [ 4789.920] (==) intel(1): TearFree disabled
    [ 4789.920] (==) intel(1): DPI set to (96, 96)
    [ 4789.920] (II) Loading sub module "dri2"
    [ 4789.920] (II) LoadModule: "dri2"
    [ 4789.920] (II) Module "dri2" already built-in
    [ 4789.920] (II) Loading sub module "present"
    [ 4789.920] (II) LoadModule: "present"
    [ 4789.920] (II) Module "present" already built-in
    [ 4792.053] (EE) intel(G0): [drm] failed to set drm interface version: Permission denied [13].
    [ 4792.053] (II) intel(G0): [drm] Contents of '/sys/kernel/debug/dri/0/clients':
    [ 4792.053] (II) intel(G0): [drm] command pid dev master a uid magic
    [ 4792.053] (II) intel(G0): [drm] Xorg 10086 0 y y 0 0
    [ 4792.053] (II) intel(G0): [drm] Xorg 10086 0 n y 0 0
    [ 4792.053] (EE) intel(G0): Failed to claim DRM device.
    [ 4792.053] (II) UnloadModule: "intel"
    [ 4792.053] (--) Depth 24 pixmap format is 32 bpp
    [ 4792.053] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory
    [ 4792.053] (II) NVIDIA: access.
    [ 4792.057] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
    [ 4792.057] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
    [ 4792.057] (II) NVIDIA(0): configuration option may not be set correctly. When the
    [ 4792.057] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
    [ 4792.057] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
    [ 4792.057] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
    [ 4792.057] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
    [ 4792.057] (II) NVIDIA(0): Config Options in the README.
    [ 4792.091] (II) NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select,DFP-2:nvidia-auto-select{Rotation=90}"
    [ 4792.264] (==) NVIDIA(0): Disabling shared memory pixmaps
    [ 4792.264] (==) NVIDIA(0): Backing store enabled
    [ 4792.264] (==) NVIDIA(0): Silken mouse enabled
    [ 4792.264] (**) NVIDIA(0): DPMS enabled
    [ 4792.264] (II) Loading sub module "dri2"
    [ 4792.264] (II) LoadModule: "dri2"
    [ 4792.264] (II) Module "dri2" already built-in
    [ 4792.264] (II) NVIDIA(0): [DRI2] Setup complete
    [ 4792.264] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
    [ 4792.264] (--) RandR disabled
    [ 4792.264] (II) intel(1): SNA initialized with disabled backend
    [ 4792.264] (==) intel(1): Backing store enabled
    [ 4792.264] (==) intel(1): Silken mouse enabled
    [ 4792.264] (II) intel(1): HW Cursor enabled
    [ 4792.264] (II) intel(1): RandR 1.2 enabled, ignore the following RandR disabled message.
    [ 4792.264] (**) intel(1): DPMS enabled
    [ 4792.264] (==) intel(1): display hotplug detection enabled
    [ 4792.264] (II) intel(1): Textured video not supported on this hardware
    [ 4792.264] (WW) intel(1): loading DRI2 whilst the GPU is wedged.
    [ 4792.264] (II) intel(1): [DRI2] Setup complete
    [ 4792.264] (II) intel(1): [DRI2] DRI driver: i965
    [ 4792.264] (II) intel(1): [DRI2] VDPAU driver: i965
    [ 4792.264] (II) intel(1): direct rendering: DRI2 enabled
    [ 4792.265] (II) intel(1): hardware support for Present enabled
    [ 4792.265] (WW) intel(1): Option "Monitor-VGA-0" is not used
    [ 4792.265] (WW) intel(1): Option "LeftOf" is not used
    [ 4792.265] (WW) intel(1): Option "Rotate" is not used
    [ 4792.265] (--) RandR disabled
    [ 4792.268] (II) Initializing extension GLX
    [ 4792.268] (II) Indirect GLX disabled.(II) intel(1): switch to mode [email protected] on VGA1 using pipe 0, position (0, 0), rotation left, reflection none
    [ 4792.332] (II) intel(1): Setting screen physical size to 270 x 338
    [ 4792.386] (II) config/udev: Adding input device Power Button (/dev/input/event2)
    [ 4792.386] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 4792.386] (**) Power Button: Applying InputClass "libinput keyboard catchall"
    [ 4792.386] (**) Power Button: Applying InputClass "system-keyboard"
    [ 4792.386] (II) LoadModule: "libinput"
    [ 4792.386] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
    [ 4792.387] (II) Module libinput: vendor="X.Org Foundation"
    [ 4792.387] compiled for 1.17.1, module version = 0.7.0
    [ 4792.387] Module class: X.Org XInput Driver
    [ 4792.387] ABI class: X.Org XInput driver, version 21.0
    [ 4792.387] (II) Using input driver 'libinput' for 'Power Button'
    [ 4792.387] (**) Power Button: always reports core events
    [ 4792.387] (**) Option "Device" "/dev/input/event2"
    [ 4792.387] (II) input device 'Power Button', /dev/input/event2 is tagged by udev as: Keyboard
    [ 4792.387] (II) input device 'Power Button', /dev/input/event2 is a keyboard
    [ 4792.399] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event2"
    [ 4792.399] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    [ 4792.399] (**) Option "xkb_model" "pc104"
    [ 4792.399] (**) Option "xkb_layout" "us,ru"
    [ 4792.399] (**) Option "xkb_options" "caps:swapescape,grp:toggle"
    [ 4792.432] (II) input device 'Power Button', /dev/input/event2 is tagged by udev as: Keyboard
    [ 4792.432] (II) input device 'Power Button', /dev/input/event2 is a keyboard
    [ 4792.432] (II) config/udev: Adding input device Power Button (/dev/input/event1)
    [ 4792.432] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 4792.432] (**) Power Button: Applying InputClass "libinput keyboard catchall"
    [ 4792.432] (**) Power Button: Applying InputClass "system-keyboard"
    [ 4792.432] (II) Using input driver 'libinput' for 'Power Button'
    [ 4792.432] (**) Power Button: always reports core events
    [ 4792.432] (**) Option "Device" "/dev/input/event1"
    [ 4792.433] (II) input device 'Power Button', /dev/input/event1 is tagged by udev as: Keyboard
    [ 4792.433] (II) input device 'Power Button', /dev/input/event1 is a keyboard
    [ 4792.489] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1/event1"
    [ 4792.489] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
    [ 4792.489] (**) Option "xkb_model" "pc104"
    [ 4792.489] (**) Option "xkb_layout" "us,ru"
    [ 4792.489] (**) Option "xkb_options" "caps:swapescape,grp:toggle"
    [ 4792.490] (II) input device 'Power Button', /dev/input/event1 is tagged by udev as: Keyboard
    [ 4792.490] (II) input device 'Power Button', /dev/input/event1 is a keyboard
    [ 4792.490] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event0)
    [ 4792.490] (II) No input driver specified, ignoring this device.
    [ 4792.490] (II) This device may have been added with another device file.
    [ 4792.490] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event17)
    [ 4792.490] (II) No input driver specified, ignoring this device.
    [ 4792.490] (II) This device may have been added with another device file.
    [ 4792.490] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event18)
    [ 4792.490] (II) No input driver specified, ignoring this device.
    [ 4792.490] (II) This device may have been added with another device file.
    [ 4792.491] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event19)
    [ 4792.491] (II) No input driver specified, ignoring this device.
    [ 4792.491] (II) This device may have been added with another device file.
    [ 4792.491] (II) config/udev: Adding input device Microsoft Microsoft® 2.4GHz Transceiver v8.0 (/dev/input/event3)
    [ 4792.491] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "evdev keyboard catchall"
    [ 4792.491] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "libinput keyboard catchall"
    [ 4792.491] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "system-keyboard"
    [ 4792.491] (II) Using input driver 'libinput' for 'Microsoft Microsoft® 2.4GHz Transceiver v8.0'
    [ 4792.491] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: always reports core events
    [ 4792.491] (**) Option "Device" "/dev/input/event3"
    [ 4792.491] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event3 is tagged by udev as: Keyboard
    [ 4792.491] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event3 is a keyboard
    [ 4792.554] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/0003:045E:07B2.0004/input/input24/event3"
    [ 4792.554] (II) XINPUT: Adding extended input device "Microsoft Microsoft® 2.4GHz Transceiver v8.0" (type: KEYBOARD, id 8)
    [ 4792.554] (**) Option "xkb_model" "pc104"
    [ 4792.554] (**) Option "xkb_layout" "us,ru"
    [ 4792.554] (**) Option "xkb_options" "caps:swapescape,grp:toggle"
    [ 4792.554] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event3 is tagged by udev as: Keyboard
    [ 4792.554] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event3 is a keyboard
    [ 4792.555] (II) config/udev: Adding input device Microsoft Microsoft® 2.4GHz Transceiver v8.0 (/dev/input/event4)
    [ 4792.555] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "evdev pointer catchall"
    [ 4792.555] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "libinput pointer catchall"
    [ 4792.555] (II) Using input driver 'libinput' for 'Microsoft Microsoft® 2.4GHz Transceiver v8.0'
    [ 4792.555] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: always reports core events
    [ 4792.555] (**) Option "Device" "/dev/input/event4"
    [ 4792.555] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event4 is tagged by udev as: Mouse
    [ 4792.555] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event4 is a pointer caps
    [ 4792.609] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.1/0003:045E:07B2.0005/input/input25/event4"
    [ 4792.610] (II) XINPUT: Adding extended input device "Microsoft Microsoft® 2.4GHz Transceiver v8.0" (type: MOUSE, id 9)
    [ 4792.610] (**) Option "AccelerationScheme" "none"
    [ 4792.610] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: (accel) selected scheme none/0
    [ 4792.610] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: (accel) acceleration factor: 2.000
    [ 4792.610] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: (accel) acceleration threshold: 4
    [ 4792.610] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event4 is tagged by udev as: Mouse
    [ 4792.610] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event4 is a pointer caps
    [ 4792.610] (II) config/udev: Adding input device Microsoft Microsoft® 2.4GHz Transceiver v8.0 (/dev/input/mouse0)
    [ 4792.610] (II) No input driver specified, ignoring this device.
    [ 4792.610] (II) This device may have been added with another device file.
    [ 4792.611] (II) config/udev: Adding input device Microsoft Microsoft® 2.4GHz Transceiver v8.0 (/dev/input/event5)
    [ 4792.611] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "evdev keyboard catchall"
    [ 4792.611] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "joystick catchall"
    [ 4792.611] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "libinput keyboard catchall"
    [ 4792.611] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "system-keyboard"
    [ 4792.611] (II) Using input driver 'libinput' for 'Microsoft Microsoft® 2.4GHz Transceiver v8.0'
    [ 4792.611] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: always reports core events
    [ 4792.611] (**) Option "Device" "/dev/input/event5"
    [ 4792.611] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event5 is tagged by udev as: Keyboard Joystick
    [ 4792.611] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event5 is a keyboard
    [ 4792.676] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.2/0003:045E:07B2.0006/input/input26/event5"
    [ 4792.676] (II) XINPUT: Adding extended input device "Microsoft Microsoft® 2.4GHz Transceiver v8.0" (type: KEYBOARD, id 10)
    [ 4792.676] (**) Option "xkb_model" "pc104"
    [ 4792.676] (**) Option "xkb_layout" "us,ru"
    [ 4792.676] (**) Option "xkb_options" "caps:swapescape,grp:toggle"
    [ 4792.676] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event5 is tagged by udev as: Keyboard Joystick
    [ 4792.676] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event5 is a keyboard
    [ 4792.677] (II) config/udev: Adding input device Microsoft Microsoft® 2.4GHz Transceiver v8.0 (/dev/input/js0)
    [ 4792.677] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "system-keyboard"
    [ 4792.677] (II) No input driver specified, ignoring this device.
    [ 4792.677] (II) This device may have been added with another device file.
    [ 4792.677] (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event7)
    [ 4792.677] (II) No input driver specified, ignoring this device.
    [ 4792.677] (II) This device may have been added with another device file.
    [ 4792.677] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event8)
    [ 4792.677] (II) No input driver specified, ignoring this device.
    [ 4792.677] (II) This device may have been added with another device file.
    [ 4792.677] (II) config/udev: Adding input device HDA Intel PCH Line Out Front (/dev/input/event9)
    [ 4792.677] (II) No input driver specified, ignoring this device.
    [ 4792.677] (II) This device may have been added with another device file.
    [ 4792.678] (II) config/udev: Adding input device HDA Intel PCH Line Out Surround (/dev/input/event10)
    [ 4792.678] (II) No input driver specified, ignoring this device.
    [ 4792.678] (II) This device may have been added with another device file.
    [ 4792.678] (II) config/udev: Adding input device HDA Intel PCH Line Out CLFE (/dev/input/event11)
    [ 4792.678] (II) No input driver specified, ignoring this device.
    [ 4792.678] (II) This device may have been added with another device file.
    [ 4792.678] (II) config/udev: Adding input device HDA Intel PCH Line Out Side (/dev/input/event12)
    [ 4792.678] (II) No input driver specified, ignoring this device.
    [ 4792.678] (II) This device may have been added with another device file.
    [ 4792.678] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event13)
    [ 4792.678] (II) No input driver specified, ignoring this device.
    [ 4792.678] (II) This device may have been added with another device file.
    [ 4792.678] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=7 (/dev/input/event14)
    [ 4792.678] (II) No input driver specified, ignoring this device.
    [ 4792.678] (II) This device may have been added with another device file.
    [ 4792.679] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=8 (/dev/input/event15)
    [ 4792.679] (II) No input driver specified, ignoring this device.
    [ 4792.679] (II) This device may have been added with another device file.
    [ 4792.679] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event6)
    [ 4792.679] (II) No input driver specified, ignoring this device.
    [ 4792.679] (II) This device may have been added with another device file.
    [ 4792.679] (II) config/udev: Adding input device Eee PC WMI hotkeys (/dev/input/event16)
    [ 4792.679] (**) Eee PC WMI hotkeys: Applying InputClass "evdev keyboard catchall"
    [ 4792.679] (**) Eee PC WMI hotkeys: Applying InputClass "libinput keyboard catchall"
    [ 4792.679] (**) Eee PC WMI hotkeys: Applying InputClass "system-keyboard"
    [ 4792.679] (II) Using input driver 'libinput' for 'Eee PC WMI hotkeys'
    [ 4792.679] (**) Eee PC WMI hotkeys: always reports core events
    [ 4792.679] (**) Option "Device" "/dev/input/event16"
    [ 4792.679] (II) input device 'Eee PC WMI hotkeys', /dev/input/event16 is tagged by udev as: Keyboard
    [ 4792.679] (II) input device 'Eee PC WMI hotkeys', /dev/input/event16 is a keyboard
    [ 4792.712] (**) Option "config_info" "udev:/sys/devices/platform/eeepc-wmi/input/input19/event16"
    [ 4792.712] (II) XINPUT: Adding extended input device "Eee PC WMI hotkeys" (type: KEYBOARD, id 11)
    [ 4792.712] (**) Option "xkb_model" "pc104"
    [ 4792.713] (**) Option "xkb_layout" "us,ru"
    [ 4792.713] (**) Option "xkb_options" "caps:swapescape,grp:toggle"
    [ 4792.713] (II) input device 'Eee PC WMI hotkeys', /dev/input/event16 is tagged by udev as: Keyboard
    [ 4792.713] (II) input device 'Eee PC WMI hotkeys', /dev/input/event16 is a keyboard
    [ 4793.050] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 4793.050] (**) NVIDIA(0): device ViewSonic VG1930wm (DFP-2) (Using EDID frequencies
    [ 4793.050] (**) NVIDIA(0): has been enabled on all display devices.)
    [ 4793.081] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 4793.081] (**) NVIDIA(0): device Samsung SMS27A850 (DFP-0) (Using EDID frequencies
    [ 4793.081] (**) NVIDIA(0): has been enabled on all display devices.)
    [ 4793.081] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
    [ 4793.081] (WW) NVIDIA(GPU-0): mode "1920x1080" is specified in the EDID; however, the
    [ 4793.081] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
    [ 4793.081] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
    [ 4793.081] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1920x1080".
    [ 4793.081] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
    [ 4793.081] (WW) NVIDIA(GPU-0): mode "1280x720" is specified in the EDID; however, the
    [ 4793.081] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
    [ 4793.081] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
    [ 4793.081] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1280x720".
    [ 4793.081] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
    [ 4793.081] (WW) NVIDIA(GPU-0): mode "720x576" is specified in the EDID; however, the
    [ 4793.081] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
    [ 4793.081] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
    [ 4793.081] (WW) NVIDIA(GPU-0): VertRefresh check for mode "720x576".
    [ 4793.129] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 4793.129] (**) NVIDIA(0): device ViewSonic VG1930wm (DFP-2) (Using EDID frequencies
    [ 4793.129] (**) NVIDIA(0): has been enabled on all display devices.)
    [ 4793.160] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 4793.160] (**) NVIDIA(0): device Samsung SMS27A850 (DFP-0) (Using EDID frequencies
    [ 4793.160] (**) NVIDIA(0): has been enabled on all display devices.)
    [ 4793.160] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
    [ 4793.160] (WW) NVIDIA(GPU-0): mode "1920x1080" is specified in the EDID; however, the
    [ 4793.160] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
    [ 4793.160] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
    [ 4793.160] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1920x1080".
    [ 4793.160] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
    [ 4793.160] (WW) NVIDIA(GPU-0): mode "1280x720" is specified in the EDID; however, the
    [ 4793.160] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
    [ 4793.160] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
    [ 4793.160] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1280x720".
    [ 4793.160] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
    [ 4793.160] (WW) NVIDIA(GPU-0): mode "720x576" is specified in the EDID; however, the
    [ 4793.160] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
    [ 4793.160] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
    [ 4793.160] (WW) NVIDIA(GPU-0): VertRefresh check for mode "720x576".
    [ 4793.229] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 4793.229] (**) NVIDIA(0): device ViewSonic VG1930wm (DFP-2) (Using EDID frequencies
    [ 4793.229] (**) NVIDIA(0): has been enabled on all display devices.)
    [ 4793.259] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 4793.259] (**) NVIDIA(0): device Samsung SMS27A850 (DFP-0) (Using EDID frequencies
    [ 4793.259] (**) NVIDIA(0): has been enabled on all display devices.)
    [ 4793.259] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
    [ 4793.259] (WW) NVIDIA(GPU-0): mode "1920x1080" is specified in the EDID; however, the
    [ 4793.259] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
    [ 4793.259] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
    [ 4793.259] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1920x1080".
    [ 4793.259] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
    [ 4793.259] (WW) NVIDIA(GPU-0): mode "1280x720" is specified in the EDID; however, the
    [ 4793.259] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
    [ 4793.259] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
    [ 4793.259] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1280x720".
    [ 4793.259] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
    [ 4793.259] (WW) NVIDIA(GPU-0): mode "720x576" is specified in the EDID; however, the
    [ 4793.259] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
    [ 4793.259] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
    [ 4793.259] (WW) NVIDIA(GPU-0): VertRefresh check for mode "720x576".
    [ 4849.763] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 4849.763] (**) NVIDIA(0): device ViewSonic VG1930wm (DFP-2) (Using EDID frequencies
    [ 4849.763] (**) NVIDIA(0): has been enabled on all display devices.)
    [ 4849.794] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 4849.794] (**) NVIDIA(0): device Samsung SMS27A850 (DFP-0) (Using EDID frequencies
    [ 4849.794] (**) NVIDIA(0): has been enabled on all display devices.)
    [ 4849.794] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
    [ 4849.794] (WW) NVIDIA(GPU-0): mode "1920x1080" is specified in the EDID; however, the
    [ 4849.794] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
    [ 4849.794] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
    [ 4849.794] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1920x1080".
    [ 4849.795] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
    [ 4849.795] (WW) NVIDIA(GPU-0): mode "1280x720" is specified in the EDID; however, the
    [ 4849.795] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
    [ 4849.795] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
    [ 4849.795] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1280x720".
    [ 4849.795] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
    [ 4849.795] (WW) NVIDIA(GPU-0): mode "720x576" is specified in the EDID; however, the
    [ 4849.795] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
    [ 4849.795] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
    [ 4849.795] (WW) NVIDIA(GPU-0): VertRefresh check for mode "720x576".
    I also tried other configs, but neither of them made me happy:
    Section "DRI"
    Mode 0666
    EndSection
    Section "Monitor"
    Identifier "SAM"
    ModelName "Samsung SMS27A850"
    HorizSync 30.0 - 90.0
    VertRefresh 56.0 - 75.0
    Option "DPMS"
    DisplaySize 597 336 # In millimeters
    EndSection
    Section "Monitor"
    Identifier "VS"
    ModelName "ViewSonic VG1930wm"
    Option "DPMS"
    Option "RightOf" "SAM"
    Option "Rotate" "left"
    EndSection
    Section "Monitor"
    Identifier "BNQ"
    ModelName "BenQ FP737s"
    Option "DPMS"
    Option "LeftOf" "SAM"
    Option "Rotate" "left"
    EndSection
    Section "Device"
    Identifier "nvidia-sam"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce GTX 560 Ti"
    BusID "01:00:0"
    Option "Monitor-DVI-I-1" "SAM"
    Screen 0
    EndSection
    Section "Device"
    Identifier "nvidia-vs"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce GTX 560 Ti"
    BusID "01:00:0"
    Option "Monitor-DVI-I-2" "VS"
    Screen 1
    EndSection
    Section "Device"
    Identifier "intel"
    Driver "modesetting"
    Option "AccelMethod" "none"
    VendorName "Intel"
    BoardName "Intel Integrated Graphic Controller"
    BusID "00:02:0"
    Option "Monitor-VGA-0" "BNQ"
    Screen 2
    EndSection
    Section "Screen"
    Identifier "SAM-Screen"
    Device "nvidia-sam"
    Monitor "SAM"
    #DefaultDepth 24
    # Option "Stereo" "0"
    # Option "SLI" "Off"
    # Option "MultiGPU" "Off"
    # Option "BaseMosaic" "off"
    #Option "AllowEmptyInitialConfiguration"
    # SubSection "Display"
    # Depth 24
    # EndSubSection
    EndSection
    Section "Screen"
    Identifier "VS-Screen"
    Device "nvidia-vs"
    Monitor "VS"
    #DefaultDepth 24
    # Option "Stereo" "0"
    # Option "SLI" "Off"
    # Option "MultiGPU" "Off"
    # Option "BaseMosaic" "off"
    #Option "AllowEmptyInitialConfiguration"
    # SubSection "Display"
    # Depth 24
    # EndSubSection
    EndSection
    Section "Screen"
    Identifier "BNQ-Screen"
    Device "intel"
    Monitor "BNQ"
    EndSection
    Section "ServerLayout"
    Identifier "Layout0"
    Screen 0 "SAM-Screen"
    Screen 1 "VS-Screen" RightOf "SAM-Screen"
    Screen 2 "BNQ-Screen" LeftOf "SAM-Screen"
    Option "Xinerama" "0"
    EndSection
    [ 4488.527]
    X.Org X Server 1.17.1
    Release Date: 2015-02-10
    [ 4488.527] X Protocol Version 11, Revision 0
    [ 4488.527] Build Operating System: Linux 3.18.6-1-ARCH x86_64
    [ 4488.527] Current Operating System: Linux earth 3.18.6-1-ARCH #1 SMP PREEMPT Sat Feb 7 08:44:05 CET 2015 x86_64
    [ 4488.527] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=dc49b07c-e67c-4b6f-91f7-7c1adc050e21 rw quiet ipv6.disable=1 init=/usr/lib/systemd/systemd security=tomoyo TOMOYO_trigger=/usr/lib/systemd/systemd
    [ 4488.527] Build Date: 22 February 2015 12:50:32PM
    [ 4488.527]
    [ 4488.527] Current version of pixman: 0.32.6
    [ 4488.527] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 4488.527] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 4488.527] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Mar 1 14:38:54 2015
    [ 4488.527] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 4488.527] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
    [ 4488.528] (==) ServerLayout "Layout0"
    [ 4488.528] (**) |-->Screen "SAM-Screen" (0)
    [ 4488.528] (**) | |-->Monitor "SAM"
    [ 4488.528] (**) | |-->Device "nvidia-sam"
    [ 4488.528] (**) |-->Screen "VS-Screen" (1)
    [ 4488.528] (**) | |-->Monitor "VS"
    [ 4488.528] (**) | |-->Device "nvidia-vs"
    [ 4488.528] (**) |-->Screen "BNQ-Screen" (2)
    [ 4488.528] (**) | |-->Monitor "BNQ"
    [ 4488.528] (**) | |-->Device "intel"
    [ 4488.528] (**) Option "Xinerama" "0"
    [ 4488.528] (==) Automatically adding devices
    [ 4488.528] (==) Automatically enabling devices
    [ 4488.528] (==) Automatically adding GPU devices
    [ 4488.528] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/OTF/,
    /usr/share/fonts/Type1/,
    /usr/share/fonts/100dpi/,
    /usr/share/fonts/75dpi/
    [ 4488.528] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 4488.528] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 4488.528] (II) Loader magic: 0x815d80
    [ 4488.528] (II) Module ABI versions:
    [ 4488.528] X.Org ANSI C Emulation: 0.4
    [ 4488.528] X.Org Video Driver: 19.0
    [ 4488.528] X.Org XInput driver : 21.0
    [ 4488.528] X.Org Server Extension : 9.0
    [ 4488.529] (EE) systemd-logind: failed to get session: PID 32224 does not belong to any known session
    [ 4488.530] (II) xfree86: Adding drm device (/dev/dri/card1)
    [ 4488.530] (II) xfree86: Adding drm device (/dev/dri/card0)
    [ 4488.531] (--) PCI: (0:0:2:0) 8086:0102:1043:84ca rev 9, Mem @ 0xf6400000/4194304, 0xd0000000/268435456, I/O @ 0x0000f000/64
    [ 4488.531] (--) PCI:*(0:1:0:0) 10de:1200:10b0:0401 rev 161, Mem @ 0xf4000000/33554432, 0xe0000000/134217728, 0xe8000000/67108864, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
    [ 4488.531] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    [ 4488.531] (II) LoadModule: "glx"
    [ 4488.531] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 4488.542] (II) Module glx: vendor="NVIDIA Corporation"
    [ 4488.542] compiled for 4.0.2, module version = 1.0.0
    [ 4488.542] Module class: X.Org Server Extension
    [ 4488.542] (II) NVIDIA GLX Module 346.47 Thu Feb 19 18:09:07 PST 2015
    [ 4488.542] (II) LoadModule: "nvidia"
    [ 4488.542] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
    [ 4488.543] (II) Module nvidia: vendor="NVIDIA Corporation"
    [ 4488.543] compiled for 4.0.2, module version = 1.0.0
    [ 4488.543] Module class: X.Org Video Driver
    [ 4488.543] (II) LoadModule: "modesetting"
    [ 4488.543] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
    [ 4488.543] (II) Module modesetting: vendor="X.Org Foundation"
    [ 4488.543] compiled for 1.17.1, module version = 1.17.1
    [ 4488.543] Module class: X.Org Video Driver
    [ 4488.543] ABI class: X.Org Video Driver, version 19.0
    [ 4488.543] (II) NVIDIA dlloader X Driver 346.47 Thu Feb 19 17:47:18 PST 2015
    [ 4488.543] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
    [ 4488.543] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
    [ 4488.543] (++) using VT number 7
    [ 4488.645] (II) Loading sub module "fb"
    [ 4488.645] (II) LoadModule: "fb"
    [ 4488.645] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 4488.645] (II) Module fb: vendor="X.Org Foundation"
    [ 4488.646] compiled for 1.17.1, module version = 1.0.0
    [ 4488.646] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 4488.646] (II) Loading sub module "wfb"
    [ 4488.646] (II) LoadModule: "wfb"
    [ 4488.646] (II) Loading /usr/lib/xorg/modules/libwfb.so
    [ 4488.646] (II) Module wfb: vendor="X.Org Foundation"
    [ 4488.646] compiled for 1.17.1, module version = 1.0.0
    [ 4488.646] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 4488.646] (II) Loading sub module "ramdac"
    [ 4488.646] (II) LoadModule: "ramdac"
    [ 4488.646] (II) Module "ramdac" already built-in
    [ 4488.647] (II) modeset(2): using drv /dev/dri/card0
    [ 4488.647] (II) modeset(G0): using drv /dev/dri/card0
    [ 4488.647] (EE) Screen 2 deleted because of no matching config section.
    [ 4488.647] (II) UnloadModule: "modesetting"
    [ 4488.647] (II) NVIDIA(0): Creating default Display subsection in Screen section
    "SAM-Screen" for depth/fbbpp 24/32
    [ 4488.647] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
    [ 4488.647] (==) NVIDIA(0): RGB weight 888
    [ 4488.647] (==) NVIDIA(0): Default visual is TrueColor
    [ 4488.647] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
    [ 4488.648] (II) NVIDIA(1): Creating default Display subsection in Screen section
    "VS-Screen" for depth/fbbpp 24/32
    [ 4488.648] (**) NVIDIA(0): Enabling 2D acceleration
    [ 4489.049] (II) NVIDIA(GPU-0): Found DRM driver nvidia-drm (20150116)
    [ 4489.050] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 560 Ti (GF114) at PCI:1:0:0 (GPU-0)
    [ 4489.050] (--) NVIDIA(0): Memory: 1048576 kBytes
    [ 4489.050] (--) NVIDIA(0): VideoBIOS: 70.24.21.00.00
    [ 4489.050] (II) NVIDIA(0): Detected PCI Express Link width: 16X
    [ 4489.082] (--) NVIDIA(0): Valid display device(s) on GeForce GTX 560 Ti at PCI:1:0:0
    [ 4489.082] (--) NVIDIA(0): CRT-0
    [ 4489.082] (--) NVIDIA(0): CRT-1
    [ 4489.082] (--) NVIDIA(0): Samsung SMS27A850 (DFP-0) (boot, connected)
    [ 4489.082] (--) NVIDIA(0): DFP-1
    [ 4489.082] (--) NVIDIA(0): ViewSonic VG1930wm (DFP-2) (connected)
    [ 4489.082] (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
    [ 4489.082] (--) NVIDIA(GPU-0): CRT-1: 400.0 MHz maximum pixel clock
    [ 4489.082] (--) NVIDIA(0): Samsung SMS27A850 (DFP-0): Internal TMDS
    [ 4489.082] (--) NVIDIA(GPU-0): Samsung SMS27A850 (DFP-0): 330.0 MHz maximum pixel clock
    [ 4489.082] (--) NVIDIA(0): DFP-1: Internal TMDS
    [ 4489.082] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
    [ 4489.082] (--) NVIDIA(0): ViewSonic VG1930wm (DFP-2): Internal TMDS
    [ 4489.082] (--) NVIDIA(GPU-0): ViewSonic VG1930wm (DFP-2): 330.0 MHz maximum pixel clock
    [ 4489.083] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 4489.083] (**) NVIDIA(0): device Samsung SMS27A850 (DFP-0) (Using EDID frequencies
    [ 4489.083] (**) NVIDIA(0): has been enabled on all display devices.)
    [ 4489.083] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
    [ 4489.083] (WW) NVIDIA(GPU-0): mode "1920x1080" is specified in the EDID; however, the
    [ 4489.083] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
    [ 4489.083] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
    [ 4489.083] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1920x1080".
    [ 4489.083] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
    [ 4489.083] (WW) NVIDIA(GPU-0): mode "1280x720" is specified in the EDID; however, the
    [ 4489.083] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
    [ 4489.083] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
    [ 4489.083] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1280x720".
    [ 4489.083] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
    [ 4489.083] (WW) NVIDIA(GPU-0): mode "720x576" is specified in the EDID; however, the
    [ 4489.083] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
    [ 4489.083] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
    [ 4489.083] (WW) NVIDIA(GPU-0): VertRefresh check for mode "720x576".
    [ 4489.084] (==) NVIDIA(0):
    [ 4489.084] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
    [ 4489.084] (==) NVIDIA(0): will be used as the requested mode.
    [ 4489.084] (==) NVIDIA(0):
    [ 4489.084] (II) NVIDIA(0): Validated MetaModes:
    [ 4489.084] (II) NVIDIA(0): "DFP-0:nvidia-auto-select"
    [ 4489.084] (II) NVIDIA(0): Virtual screen size determined to be 2560 x 1440
    [ 4489.113] (--) NVIDIA(0): DPI set to (125, 114); computed from "UseEdidDpi" X config
    [ 4489.113] (--) NVIDIA(0): option
    [ 4489.114] (==) NVIDIA(1): Depth 24, (==) framebuffer bpp 32
    [ 4489.114] (==) NVIDIA(1): RGB weight 888
    [ 4489.114] (==) NVIDIA(1): Default visual is TrueColor
    [ 4489.114] (==) NVIDIA(1): Using gamma correction (1.0, 1.0, 1.0)
    [ 4489.114] (II) NVIDIA(1): NVIDIA GPU GeForce GTX 560 Ti (GF114) at PCI:1:0:0 (GPU-0)
    [ 4489.114] (--) NVIDIA(1): Memory: 1048576 kBytes
    [ 4489.114] (--) NVIDIA(1): VideoBIOS: 70.24.21.00.00
    [ 4489.114] (II) NVIDIA(1): Detected PCI Express Link width: 16X
    [ 4489.146] (--) NVIDIA(1): Valid display device(s) on GeForce GTX 560 Ti at PCI:1:0:0
    [ 4489.146] (--) NVIDIA(1): CRT-0
    [ 4489.146] (--) NVIDIA(1): CRT-1
    [ 4489.146] (--) NVIDIA(1): Samsung SMS27A850 (DFP-0) (boot, connected)
    [ 4489.146] (--) NVIDIA(1): DFP-1
    [ 4489.146] (--) NVIDIA(1): ViewSonic VG1930wm (DFP-2) (connected)
    [ 4489.146] (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
    [ 4489.146] (--) NVIDIA(GPU-0): CRT-1: 400.0 MHz maximum pixel clock
    [ 4489.146] (--) NVIDIA(1): Samsung SMS27A850 (DFP-0): Internal TMDS
    [ 4489.146] (--) NVIDIA(GPU-0): Samsung SMS27A850 (DFP-0): 330.0 MHz maximum pixel clock
    [ 4489.146] (--) NVIDIA(1): DFP-1: Internal TMDS
    [ 4489.146] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
    [ 4489.146] (--) NVIDIA(1): ViewSonic VG1930wm (DFP-2): Internal TMDS
    [ 4489.146] (--) NVIDIA(GPU-0): ViewSonic VG1930wm (DFP-2): 330.0 MHz maximum pixel clock
    [ 4489.146] (**) NVIDIA(1): Option "Rotate" "left"
    [ 4489.146] (**) NVIDIA(1): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 4489.146] (**) NVIDIA(1): device ViewSonic VG1930wm (DFP-2) (Using EDID frequencies
    [ 4489.146] (**) NVIDIA(1): has been enabled on all display devices.)
    [ 4489.147] (==) NVIDIA(1):
    [ 4489.147] (==) NVIDIA(1): No modes were requested; the default mode "nvidia-auto-select"
    [ 4489.147] (==) NVIDIA(1): will be used as the requested mode.
    [ 4489.147] (==) NVIDIA(1):
    [ 4489.147] (II) NVIDIA(1): Validated MetaModes:
    [ 4489.147] (II) NVIDIA(1): "DFP-2:nvidia-auto-select{Rotation=90}"
    [ 4489.147] (II) NVIDIA(1): Virtual screen size determined to be 900 x 1440
    [ 4489.150] (--) NVIDIA(1): DPI set to (55, 140); computed from "UseEdidDpi" X config
    [ 4489.150] (--) NVIDIA(1): option
    [ 4489.150] (EE)
    [ 4489.150] (EE) Backtrace:
    [ 4489.151] (EE) 0: /usr/lib/xorg-server/Xorg (OsLookupColor+0x119) [0x5949c9]
    [ 4489.151] (EE) 1: /usr/lib/libc.so.6 (__restore_rt+0x0) [0x7f64dd88653f]
    [ 4489.151] (EE) 2: /usr/lib/xorg-server/Xorg (xf86nameCompare+0x19) [0x4a9159]
    [ 4489.151] (EE) 3: /usr/lib/xorg-server/Xorg (xf86findOption+0x2c) [0x4a2c6c]
    [ 4489.151] (EE) 4: /usr/lib/xorg-server/Xorg (xf86SetDepthBpp+0x430) [0x4828d0]
    [ 4489.151] (EE) 5: /usr/lib/xorg/modules/drivers/modesetting_drv.so (_init+0x25e1) [0x7f64d695aab1]
    [ 4489.151] (EE) 6: /usr/lib/xorg-server/Xorg (InitOutput+0xbcc) [0x47b63c]
    [ 4489.151] (EE) 7: /usr/lib/xorg-server/Xorg (remove_fs_handlers+0x22a) [0x43c9da]
    [ 4489.152] (EE) 8: /usr/lib/libc.so.6 (__libc_start_main+0xf0) [0x7f64dd873800]
    [ 4489.152] (EE) 9: /usr/lib/xorg-server/Xorg (_start+0x29) [0x427039]
    [ 4489.152] (EE) 10: ? (?+0x29) [0x29]
    [ 4489.152] (EE)
    [ 4489.152] (EE) Segmentation fault at address 0x231
    [ 4489.152] (EE)
    Fatal server error:
    [ 4489.152] (EE) Caught signal 11 (Segmentation fault). Server aborting
    [ 4489.152] (EE)
    [ 4489.152] (EE)
    Please consult the The X.Org Foundation support
    at http://wiki.x.org
    for help.
    [ 4489.152] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
    [ 4489.152] (EE)
    [ 4489.295] (EE) Server terminated with error (1). Closing log file.
    Section "DRI"
    Mode 0666
    EndSection
    Section "Monitor"
    Identifier "SAM"
    ModelName "Samsung SMS27A850"
    HorizSync 30.0 - 90.0
    VertRefresh 56.0 - 75.0
    Option "DPMS"
    DisplaySize 597 336 # In millimeters
    EndSection
    Section "Monitor"
    Identifier "VS"
    ModelName "ViewSonic VG1930wm"
    Option "DPMS"
    Option "RightOf" "SAM"
    Option "Rotate" "left"
    EndSection
    Section "Monitor"
    Identifier "BNQ"
    ModelName "BenQ FP737s"
    Option "DPMS"
    Option "LeftOf" "SAM"
    Option "Rotate" "left"
    EndSection
    Section "Device"
    Identifier "nvidia-sam"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce GTX 560 Ti"
    BusID "01:00:0"
    Option "Monitor-DVI-I-1" "SAM"
    Screen 0
    EndSection
    Section "Device"
    Identifier "nvidia-vs"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce GTX 560 Ti"
    BusID "01:00:0"
    Option "Monitor-DVI-I-2" "VS"
    Screen 1
    EndSection
    Section "Device"
    Identifier "intel"
    Driver "intel"
    Option "AccelMethod" "none"
    VendorName "Intel"
    BoardName "Intel Integrated Graphic Controller"
    BusID "00:02:0"
    Option "Monitor-VGA-0" "BNQ"
    Screen 2
    EndSection
    Section "Screen"
    Identifier "SAM-Screen"
    Device "nvidia-sam"
    Monitor "SAM"
    #DefaultDepth 24
    # Option "Stereo" "0"
    # Option "SLI" "Off"
    # Option "MultiGPU" "Off"
    # Option "BaseMosaic" "off"
    #Option "AllowEmptyInitialConfiguration"
    # SubSection "Display"
    # Depth 24
    # EndSubSection
    EndSection
    Section "Screen"
    Identifier "VS-Screen"
    Device "nvidia-vs"
    Monitor "VS"
    #DefaultDepth 24
    # Option "Stereo" "0"
    # Option "SLI" "Off"
    # Option "MultiGPU" "Off"
    # Option "BaseMosaic" "off"
    #Option "AllowEmptyInitialConfiguration"
    # SubSection "Display"
    # Depth 24
    # EndSubSection
    EndSection
    Section "Screen"
    Identifier "BNQ-Screen"
    Device "intel"
    Monitor "BNQ"
    EndSection
    Section

    Hi:
    There is a specific order you need to install the graphics drivers for the notebooks with the nvidia/intel graphics.
    1. Install the Intel chipset installation utility and reboot.  If the one on your notebook's support page doesn't work, use this one.
    https://downloadcenter.intel.com/Detail_Desc.aspx?​DwnldID=20775&lang=eng&ProdId=816
    2. Install the Intel HD graphics driver and reboot.  If the one on your notebook's suport page doesn't work, try this one.
    https://downloadcenter.intel.com/Detail_Desc.aspx?​DwnldID=24348
    3. Install the nVidia HD graphics driver and reboot.  If the one on your notebook's support page doesn't work, try this one.
    http://www.nvidia.com/download/driverResults.aspx/​81879/en-us

  • Problem with Matrox Mini, NVIDIA GeForce GTX 570, Premiere 5.5.2 and After Effects CS5.5

    Hello,
    We have a couple video workstation PC's in our office.
    Premiere and After Effects have been crashing lately with increasing frequency - about every two minutes now.
    Here is the setup:
    Hardware
    Matrox Mini - Matrox Utility release 5.5.1
    Nvidia GeForce GTX 570 - Driver release 275.33
    Intel Xeon X5660 2.8 GHz processors
    24 GB Ram
    Software
    Adobe CS5.5, specifically...
    After Effects 10.5.0.253
    Premiere 5.5.2
    Windows 7 64-bit
    We have two 21" LCD monitors in dual display running from the computer, and the Matrox Mini outputs a preview signal to a 15" CRT.
    The crashes occur when I have After Effects and Premiere open at the same time. I am editing in a Matrox 720p29.97 timeline in Premiere. I imported several compositions from AE into Premiere through Dynamic Link and am matching audio with the animations in comps. When I switch back to AE to make an edit in the comp, After Effects generates a crash warning and then gives me the opportunity to save the project under a new name. After saving, it closes down completely. The Matrox WYSIWYG Control Panel in the system tray crashes during AE's crash, disabling the preview to the CRT from Premiere and AE. Since the Premiere sequence is a Matrox preset - in order to have output to the CRT - this freezes the timeline; the video and audio no longer play. When I save and then try to close Premiere, Premiere freezes and will not close without a force quit via the Task Manager.
    In order to deal with this temporarily, I am editing in an AVCHD 720p30 sequence preset in Premiere, which doesn't send a preview feed to the CRT, obviously, since it's not a Matrox preset and the CRT is connected via the Matrox Mini. It's more than a minor inconvenience, since I use the CRT for color accuracy.
    It is frustrating, since we did not have this problem until the recent CS5.5.2 update. We have tried changing drivers for the GTX 570 and changing the Matrox utility software to other versions, but no luck.
    Is there a combination of GTX 570 drivers, Matrox software releases, and AE/Premiere settings that will make this work? I know there are "Known Issue" posts with Nvidia cards on Matrox's website, which include the GTX 570, but, again, this problem started with the Adobe CS5.5.2 update.
    Any help here would be great, and I am willing to provide more information about the system and our crashes if it helps find a solution for the community, as I know this is not an isolated problem after reading Nvidia's, Matrox's, and Adobe's forums. I just can't find a hollistic solution on any of the individual manufacturer's forums.
    Thank You.
    Jordan

    I've been running with Matrox for years, starting with the Axio LE. I do 75% broadcast work and find that the Matrox works very well with my kind of workflow. Monitoring is critical and since we have to deal with 3rd. party solutions, Matrox was my pick dating way back to 2006. Sure I've had frustrations with it, but I've made far more money off Matrox than frustration.
       Here's my nearly crash-free setup:
    Gigabyte GZ-X58A-OC moboard
    Intel 990X (only overclocking to 4.0)
    24Gb of Kingston HyperX Ram
    GTX580 Graphics Card
    Matrox MXO2-LE w/Max
    Crucial 240Gb Sata III drive (the one that has a nearly perfect score on Newegg's site)
    2 x 2Tb WD Blacks Raid 0
    2 x 1Tb WD Blacks Raid 0
    Win 7 Ultimatte (it's a high-end version of Windows that's great for keying!)
    CS5.5 Suite
    Boris Red 5
    Boris Continuum Complete 8
    Trapcode Shine, Form, 3d Stroke, Starglow, and Particular
    Optical Flares by Video CoPilot
       The reason I list all of that software, is that it all seems to get along together, including with Matrox! So, I can't say I highly endorse Matrox because I've never tried Black Magic or running an external monitor off of my video card.
        I use After Effects with all sorts of plug ins and rarely have crashes. If I put in a long day I'll have the usual crashes here and there (mainly with PremierePro), but nothing that has required evan a soft reboot of the computer.
       My frustration with Matrox is mainly the delay that often comes with Adobe coming out with a new release and Matrox taking 2 or 3 months to catch up, though when Adobe went from 5 to 5.5, there was no delay at all.
       I think that a lot of the people who trash Matrox probably haven't used a Matrox product in years. But before you listen to me, I must confess that I was an early adopter (and advocate) of SSDs and even today, many people on this forum think they're still a waste of money!
       I'll close by simply saying that I've not left Matrox after 5+ years, but keep in mind I haven't had the bad experiences that so many others seem to have had, but again, perhaps they had those bad experiences long ago.

  • X99S GAMING 9 AC Not booting - Debug 94 code - Issue with GTX 980 SLI in WoW

    Hello, I bought the X99S GAMING 9 AC motherboard but have ran into some issues.
    The computer won't boot when I put my second MSI GTX 980 Gaming 4 GB card in the last PCEI 3.0 port (PCIE port 5) and I get the debug LED message 94 on the motherboard. I have a SLI setup.
    The first card I have in the second PCIE 3.0 port due to the Noctua U14S CPU fan takes up space for the first slot. So I have been running my grafic cards in PCIE slot 2 and 4 with some issues.
    First the card in slot 2 gets really warm over 86 celsius. And second: SLI runs really poorly in World of Warcraft. I get a lot higher performance with just one card activated. I am not sure if it's cause I am not running my cards in the recommended PCIE 3.0 ports or because WoW has some issues with SLI, but I heard other people have no issues at all with WoW in SLI.
    I got the same issue with 3Dmark firestrike, the cards perform really poor in SLI. I get higher score with SLI turned off..
    Though SLI seems to run pretty well in 3dmark 11 and Diablo 3 Reaper of Souls.
    But the main issue right now, is that the computer won't boot with the grafic cards in PCIE port 2 and 5. The solution to run them next to each other is not good, cause it gets really hot and I get bad performance in WoW and Firestrike.
    Picture of my setup before I switched places with the grafic cards as you can see, it is really tight:
    Any upcoming bios updates (got v1.3) that will solve this issue on the horization? Hopefully this get sorted out really soon..
    My whole computer setup:
    Intel i7 5820K | MSI X99S Gaming 9 AC (bios 1.3) | SLI MSI GTX 980 Gaming 4GB | Samsung 850 Pro 512 GB | WD Red 4TB | G.Skill Ripjaws DDR4 3000MHz 4x4GB | EVGA SuperNOVA P2 1000W | Noctua NH-U14S PnP | Fractal Design Define XL R2 | 5 Noctua NF-A14 PWM 140mm fans | Windows 7 Pro 64 bit

    You must use the recommended PCIE slots as the manual says for your CPU type, PCIE #1 and PCIE #4 if I remember, just open the manual :P for optimal 2Way SLI, also your 5820k will limit to 28 pcie lanes only if you plan to add more vgas...the other problem is your giant CPU air cooler blocking PCIE#1, do a favor to yourself, buy a watercooler for your 5820k and your problems are gone, add some overclock in your system, low noise and better temps.
    Here I use 3x980 in SLI with X99S Gaming 9 AC, going soon to WC the VGAs with EK blocks.....3way is far more temperature critical than 2way spaced one.
    Cheers

Maybe you are looking for

  • How do I save my itunes music/ library to a flash stick?

    I want to put all my itunes music onto a flash stick to play in my car. Do I just pluf flash stick into usb slot on Mac and transver? Sorry not too good at this!!!!

  • E not assigned Error when running Data Manager

    Hi, When I try to import Master Data from BW to BPC, All the ID's are loaded correctly, however I get an error message that :E not assigned when I run the Data Manager even though I have the Language set to "E". Any inputs are appreciated. thanks, Va

  • Separating Java add-in from ABAP Stack server

    I have installed an ABAP Stack and added the JAVA add-in on the same physical server.  Now I would like to have the JAVA add-in run on a physically different server.  ABAP on Server1 and JAVA add-in on server2. What is the process to move the add-in

  • Where can i see EIS log file

    Hi to all, When i am doing the member load through EIS, i got the error like the load terminated with errors. where can i see these error logs in detail. Thanks for your help in advance.

  • Downloadin​g Modules Problem

    Hi Looking at various threads, I realise I've probably gone wrong because I should've restarted before trying to install the software. However, I didn't know that so I'm now stuck in this lousy situation. My software manager has been stuck on 3 of 60