Will NVIDIA GeForce GTX 560 fit into HP ProBook6470b
Hi,
I want to install NVIDIA GeForce GTX 560 card into my HP laptop ( ProBook 6470b). Will it require any other hardware also?
On which port I can insert/install it.
Thanks in advance.
Br
Manvash
This question was solved.
View Solution.
Hi Erico, Thanks a lot!
Similar Messages
-
Nvidia Quadro 600, GeForce GTX 560 Ti or cheaper for Photoshop CS5 and Lightroom 3?
Hello,
I am a professional photographer and I am setting up a new PC (i7, Windows 7 64bit). But I have some troubles to choose the graphic card.
I use Lightroom and Photoshop CS5 3, no video editing.
Between the Open GL, Open CL, CUDA accelerations etc ... professional graphic cards models and consumer ones I am lost!
The Nvidia GeForce GTX 560 Ti seems more powerful and more versatile but I tell myself that if Nvidia has professional range there must be a reason.
So in Photoshop CS5 and Lightroom 3 what would be the best: GeForce GTX 560 Ti or Nvidia Quadro 600?
http://www.geforce.com/Hardware/GPUs/geforce-gtx-560ti/specifications
http://www.nvidia.com/object/product-quadro-600-us.html
Any reason to get a Quadro 2000?
http://www.nvidia.com/object/product-quadro-2000-us.html
Or the graphic card doesn’t matter much and I should take an entry-level GeForce to enjoy the HDMI and the silence? Which one then?
Does the Quadro 600 manages 10bits display 10bits? And the Geforce?
Any change announced with Photoshop CS6 and Ligthroom4?
The only 3D application I use is Google Earth in 3D mode, does it make any difference?
Thank you for your help.You say "no video editing"... If that's going to be the case, and you won't use the Mercury engine in the Adobe Premiere Pro package, which needs the nVidia Cuda subsystem, then I recommend you consider the ATI brand over nVidia.
Why?
Because while neither brand's developers (ATI or nVidia) always release perfect drivers, I find ATI display drivers to be of consistently higher quality than that of nVidia releases. What this means to you is generally fewer crashes or quirks. ATI has also traditionally supported older cards into the future better than nVidia - this might matter to you in a few years.
People ask me what video card I would recommend, and right now that would be a VisionTek ATI Radeon HD 6670 1 GB GDDR5 card. I like this particular card because:
I've had 100% success with VisionTek cards in a number of different systems, not only initially but they have all run as long as I have used them, without ever breaking down.
The 6670 model uses very little power (under 70 watts) and as such doesn't stress your computer's power supply, need a separate power connection, nor make a lot of fan noise.
It's not the fastest card made for 3D gaming, but it's inexpensive and excellent for Photoshop. No matter what you choose, you should get a card that scores over 500 on the Passmark GPU benchmark, ideally over 1000: http://www.videocardbenchmark.net/
The ATI Catalyst display driver implementations for the 4670/5670/6670 line of cards have been good and solid.
1 GB of on-card memory seems to be a good size, even for editing a lot of images, and GDDR5 memory provides faster access than DDR3.
You should know that besides using Photoshop heavily, I also develop OpenGL-based software as well, so I have some additional insight into driver implementations.
-Noel -
Why does the GeForce GTX 560 Ti NOT support OpenCL?
From the Nvidia web site it says that the GeForce GTX 560 Ti supports: DirectX 11 > 3D Vision > PhysX > CUDA > SLI >
301.24 drivers have been used and have downgraded to 296.10 to see if that would help, but it didn't.
When I check the performance tab under Advanced it shows that the OpenCL option is grayed out. When I check the Sys info log it also shows that OpenCL is Not availible (included below).
Why is this and when will it be fixed? Now that CS6 is shipping it should be working.
Adobe Photoshop Version: 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00) x64
Operating System: Windows 7 64-bit
Version: 6.1 Service Pack 1
System architecture: Intel CPU Family:6, Model:10, Stepping:7 with MMX, SSE Integer, SSE FP, SSE2, SSE3, SSE4.1, SSE4.2, HyperThreading
Physical processor count: 4
Logical processor count: 8
Processor speed: 3411 MHz
Built-in memory: 16351 MB
Free memory: 12614 MB
Memory available to Photoshop: 14726 MB
Memory used by Photoshop: 95 %
Image tile size: 128K
Image cache levels: 4
OpenGL Drawing: Enabled.
OpenGL Drawing Mode: Advanced
OpenGL Allow Normal Mode: True.
OpenGL Allow Advanced Mode: True.
OpenGL Allow Old GPUs: Not Detected.
Video Card Vendor: NVIDIA Corporation
Video Card Renderer: GeForce GTX 560 Ti/PCIe/SSE2
Display: 2
Display Bounds:= top: -1080, left: 0, bottom: 0, right: 1920
Display: 1
Display Bounds:= top: 0, left: 0, bottom: 1080, right: 1920
Video Card Number: 1
Video Card: NVIDIA GeForce GTX 560 Ti
OpenCL Unavailable
Driver Version: 8.17.12.9610
Driver Date: 20120229000000.000000-000
Video Card Driver: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Video Mode: 1920 x 1080 x 4294967296 colors
Video Card Caption: NVIDIA GeForce GTX 560 Ti
Video Card Memory: 1024 MB
Video Rect Texture Size: 16384Bandalier1 wrote:
Problem solved. NVidia just released their first 300 series drivers and the Open CL option is working now…
Good for you! I was just about to start typing a reply to the OP clarifying that support for OpenGL depends on the driver for the card, when I read your last post.. -
I am looking at buying a new iMac but not sure if I need the Nvidia Geforce GTX 680 MX 2GB or put the money into Memory I will not be gaming
New to the iMac and appleWelcome to the Apple Support Communities
If you aren't going to use your Mac for anything special (Final Cut, Aperture, Photoshop, games...), you don't need that graphic card and you will save money.
Also, as it looks like you are going to buy the 27-inch iMac, I recommend you to buy the Mac with 8 GB of memory, and then, buy the memory that your iMac needs in OWC or Crucial (the iMac supports 32 GB of RAM) > http://eshop.macsales.com/shop/memory/iMac/2012_27/DDR3L
Doing this, you will save a lot of money. Also, it won't void the warranty of the Mac. If you need help installing the RAM, see > http://support.apple.com/kb/ht5540 -
Will Premiere Pro CC work OK with Nvidia GeForce GTX 765M?
Will Premiere Pro CC work OK with Nvidia GeForce GTX 765M?
This laptop I am on right vnow has a n nVidai GTX 765M and it works beautifully on Premiere CS6, CC and CC 2014. You do have to add it to the Adobe file "cuda_supported_cards.txt file or simp[ly delete it. I hope you know that you have to be plugged in to the AC line to successfully what to edit with a laptop. Also you can improve the GPU performance if you reset the memory clock on the GPU to 1500 MHz from the default 1000 MHz. It is because nVidia.slows down the clock to conserve battery. If you register on the site you can see my results on our Premiere Pro BenchMark (PPBM) site.
-
Imac 2012 NVIDIA GeForce GTX 680MX will it work with adobe Mercury playback Engine?
imac 2012, 28" 16 gigs ram
NVIDIA GeForce GTX 680MX 2 gigs ram, will it work with adobe Mercury playback Engine for accelerated rendering in Premiere Pro & After EffectsOne would certainly think so, since earlier, lesser GTX cards were supported...
http://www.adobe.com/products/premiere/tech-specs.html
Supported NVIDIA graphics cards for GPU acceleration
GeForce GTX 285 (Windows and Mac OS)
GeForce GTX 470 (Windows)
GeForce GTX 570 (Windows)
GeForce GTX 580 (Windows) -
Will the Asus Nvidia GeForce GTX 650 work for prem pro?
Will the Asus Nvidia GeForce GTX 650 work in prem pro. The one in adobe's recommended list does not have an 'X' in the card description?
[Moved to Hardware forum.]
-
Will card nVidia geforce GTx 760 work with premiere pro?
Will card nVidia geforce GTx 760 work with premiere pro?
Yes, the GTX 760 will work nicely with Premiere on the PC. What version? With CS6, you may need to delete the "cuda_supported_cards.txt" file from the Adobe folder.
Thanks
Jeff Pulera
Safe Harbor Computers -
NVIDIA GeForce GTX 680MX 2 gigs ram, will it work with Mercury playback Engine for accelerate
NVIDIA GeForce GTX 680MX 2 gigs ram, will it work with adobe Mercury playback Engine for accelerated rendering for Premeire Pro cs6?
I am a PC guy but, I have 6 work stations with CS6 but the wife wants a Mac so I am getting her an imac with the NVIDIA GeForce GTX 680MX 2 gigs ram. Do you think this video card in the mac will still be able to utilize the Adobe CS6 MPE?
It's not formally supported by Adobe for GPU acceleration; however judging from the fact that the lesser GTX-650M is (with 6.02 update), and the end-user ability to enable support for unsupported cards in Adobe apps, it should work. -
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
SectionHi:
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.
JordanI'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. -
Photoshop CS6 doesn't recognize my NVIDIA GeForce GTX 675M GPU?
I just bought a brand new Alienware M17x R4 with Windows 8 Pro x64 and Photoshop CS6 won't recognize my NVIDIA GeForce GTX 675M GPU?
I've already updated Windows 8, Photoshop and the Nvidia graphics driver.
Any ideas? I spent so much on a nice graphics card but now it seems PS CS6 can't even use it. It's using the Intel HD4000 instead:
I also tried this: http://forums.adobe.com/message/4545768#4545768
And deleted the settings but that didn't help.
According to this, my graphics card should work, it's a NVIDIA GeForce GTX 675M, which is a 600 series GPU: http://helpx.adobe.com/photoshop/kb/photoshop-cs6-gpu-faq.html#tested_cards
Tested video cards for Photoshop CS6
Adobe tested the following video cards before the release of Photoshop CS6. This document lists the video card by series. The minimum amount of RAM supported on video cards for Photoshop CS6 is 256 MB. Photoshop 13.1 cannot display 3D features if you have less than 512 MB VRAM on your video card.
Important: This document is updated as newly released cards are tested. However, Adobe cannot test all cards in a timely manner. If a video card is not listed here, but was released after May 2012, you can assume that the card will work with Photoshop CS6.
Adobe tested laptop and desktop versions of the following cards. Be sure to download the latest driver for your specific model. (Laptop and desktop versions have slightly different names.)
nVidia GeForce 8000, 9000, 100, 200, 300, 400, 500, 600 series
I've run out of ideas. Any suggestions?Okay, I figured it out...duh.
My bad...or rather, Nvidia's bad!
In their app profiler, they set Photoshop to use the "default" settings, which defaults to the integrated graphics. By changing the profile to make it use the discreet graphics, it worked!
This also fixed my issue of the background flashing / flickering.
I know that's a known bug with Windows 8 + AMD (http://helpx.adobe.com/photoshop/kb/image-background-transparent-or-flickers.html)
However, Adobe should look into this same bug occuring with the Intel HD4000 integrated GPU, because this happened with my laptop.
Maybe that bug doesn't occur on systems that only have an integrated GPU, but on systems with Optimus, it's definitely a reproducible issue.
When I switch back to integrated, the issue pops up again.
It's nice that Nvidia provides an option for us to either use the integrated or discreet graphics, however, Adobe needs to follow through and make sure that Photoshop doesn't wig out when we're using the integrated GPU. Sometimes, your customers need to do work on battery power, so the integrated flickering /flashing /transparent background bug definitely needs to be fixed.
Personally, I can get 6hrs out of this laptop running the integrated GPU, but when I use the discreet, that cuts it down to only 2hrs. -
Can't get GeForce GTX 560 Ti card CUDA to work with new Premiere Pro CC 2014 version
In the past I've been able to get CUDA on my GeForce GTX 560 Ti card to work with Mercury Playback engine by adding "GeForce GTX 560 Ti" to the cuda_supported_cards.txt file. But with the new CC 2014 version of Premiere, that file isn't in the Premiere Pro directory anymore. Is there a way to get my GTX 560 Ti to be listed as a CUDA-supported card with CC 2014?
Okay, I figured it out. I installed the latest graphics driver and then opened the NVIDIA control panel. In there I selected "Manage 3D settings" and went to the "program settings" tab. I selected Adobe Premiere (adobe premiere pro.exe) from the list and under the "CUDA - GPUs" feature, I changed it to "Use these GPUs" and selected my GTX 560 Ti (which was the only one listed).
After doing that, I opened Premiere Pro CC 2014 and selected "Project Settings - General" and was then able to choose "Mercury Playback Engine GPU Acceleration" under Renderer (which had previously been unavailable).
Hopefully this will help someone else if they encounter the same problem. -
[BUG] Photoshop CC crashed immediately after selecting NVIDIA GeForce GTX 680M GPU
I just started using Photoshop CC trial and I immediately ran into problem with my video card.
First Photoshop doesn't recognized my GPU which is Nvidia GTX 680M. I'm using a new Alienware R4 with Win8 pro, I then searched the forum and followed this thread
Photoshop CS6 doesn't recognize my NVIDIA GeForce GTX 675M GPU?http://forums.adobe.com/thread/1157982
After following the instruction now Photoshop CC is supposely using my NVIDIA GPU, but it immediately crashed after launching, for both 32 bits and 64 bits. My NVIDIA driver version is 320.49 600 series, the latested one I just updated. If I deselect the NVIDIA option in the control panel I no longer suffer the crash problem but as you know there is a reported problem with Intel HD4000 integrated GPU where screen flickering keeps happening if you use a toolbox. To avoid the problem the only thing I can do is to deselect the use GPU option in CC option (changing the mode advanced setting doesn't help). By deselcting the GPU option get rid of the problem but there is another problem with zooming: it cannot zoom in real time anymore, instead it's having a toolbox where you choose a reagion and it will jump to that region, and I can only zoom in by doing this, not zooming out.
So basically I had a problem with NVIDIA which crashes CC immediately and a problem with Intel HD4000 integrated GPU with flickering screen and another problem with no GPU selected where I cannot zoom in real time. Whatever I do always give me some sets of problem that I can't solve.
BTW I haven't try CS6 yet, I may proceed to download a trial copy and I thought CC and CS6 are using the same core. Nevertheless, those problem should definately be looked into.
Any helps? Thanks in advance.If you check that user's Profile, you'll discover it is not actually nVidia per se
Profile
Username: Sora
Age: 7 ¾
Favourite activity: Playing computer games
Spots: In abundance
Ambition: To have a clue
For what it’s worth, I have most of the CC apps installed on an MSI GT70 ONE with GTX680M — driver 9.18.13.614 dated 8/28/2012 and using Windows 8, and while I have not used them all on that laptop, the ones I have appear to be working faultlessly. -
HP Pavilion p6510f Desktop intermittent failures - Antec 25 430 WATT Power & NVIDIA GEFORCE GTX 650
After installing a new power supply and video card (Antec 25 430 WATT Power & NVIDIA GEFORCE GTX 650), my system became unstable. It worked fine for the first 3-4 hours then had a BSOD (blue screen of death) with kernel_data_inpage_error 0000007A and later a critical process failure 000000F4. I've done all of the tests listed on this page as well as removed and replaced the cmos battery:
http://www.faultwire.com/solutions-fatal_error/KERNEL-DATA-INPAGE-ERROR-0x0000007A-*1137.html
All of the tests passed and no problems were found and yet the system still fails after 3-4 hours of use.
So, I removed everything from my system and restored it to it's original settings. It seems to be back to normal now (but, we'll see for how long).
This experience has demoralized me. This is due to the fact that I've heard of others having difficulties trying to upgrade their systems. Seems like there is about a 50% success rate unless you know what works from past experience. I feel that the only way to get a system that has good graphics now is a well tested gaming box (PS3, XBOX, or Wii). Is there any recommended or possibly well tested setups for this type of system that could give me the quality of a GEFORCE GTX 650 without causing blue screens or cause instability for my computer?
Since this computer comes with ATI and AMD parts, I presume maybe getting an ATI or AMD graphics card would work? Regardless of the graphics card, the 250W power that comes with this system would most likely need to be replaced. Are there are any power supplys that you recommend or possibly tested?
I realize there are a few questions in this post, but I have one more. Are there any motherboard analysis tools to enusre nothing has gone wrong with the mother board? When the blue screens were occurring it seemed to make strange noises from the hard drive as it it were thrashing and after rebooting it would sometimes fail to recognize the existance of the hard drive as well. Since all of the hard drive tests were successful (I also ran SeaTools), this leads me to believe that the power is inssuficient, but I'm now fearful that if I upgrade the power it will only cause more problems.
A paying customer,
Zintage
This question was solved.
View Solution.So, using the standard setup still makes strange noises at various intervals, but not as frequently. I have a bad feeling that it has caused disk drive problems based on the fact that:
1) Strange noises are now occuring during particular load times (although rarely)
2) Computer crashes (although, it no longer crashes now that I'm back in it's regular setup)
3) Occassionall it has really slow access times
These symptoms fall into the category of a failing drive based on the following site:
http://www.lifehack.org/articles/technology/how-to-tell-when-your-hard-drive-is-going-to-fail.html
I'm going to return the power supply and game card and look to investing in a new hard drive in case this one finally decides to go to valhalla.
Maybe you are looking for
-
The field "GLTPC" is unknown, but there is a field with the similar name*
Hi all When i am running the report painter reports in SAP i am getting this error . Syntax error in program SAPFGRWG in include FGRWGE60 in line 19 Last changed by SAP Author SA
-
BAPI to process mutiple incoming payments
Hi Experts, Is there any BAPI to post mutiple incoming payemnts. As of now i get file from the bank for the customer payments debited from there card , I am using BAPI 'BAPI_ACC_DOCUMENT_POST' to process the data sent to us from the bank. With this B
-
Next / previous image swap WITH larger image popup
Very simply what I need to do is almost identical to what you see here: http://www.java-scripts.net/javascripts/Slide-Show-Script.phtml (scroll down to the animal pictures) When you click "next" and "previous" the images swap through a series called
-
Hi All, i have a requirement where i need to put a check on the date eneterd in the database table to be greater than present in the table . for this i have created Zxxxxx event routine and written logic inside. that routine type as 1 that is
-
Hi, Mayby anybody here knows where do the portal iviews xml files are saved in the server? Thanks. Promise to award points... Ruthie.