Intel HD Graphics and 16GB RAM upgrade?
Does anyone know if there is any way of increasing the amount of RAM allocated to a Intel HD Graphics 3000 graphics card? I recently installed 16GB RAM and I have 512MB of graphics memory. I am not sure what it was before as I hadn't checked but I was wondering if there was an app or a terminal command that you could use to increase the memory to 1GB or more maybe?
I have Windows 7 installed over bootcamp if you could do something in there that my effect Mac OS X. Also in Windows, there is a settings option in the taskbar that I can change the options of the graphics card (ie: Resolutions, Energy Efficiency, etc...) and I don't know but would that change the settings in Mac OS X too?
I have looked around on the internet and a few other people are having this problem. Thanks!
NO. Once you have installed 8 GB RAM or more, you have maximized the Intel 3000 Graphics VRAM.
Ciao.
Similar Messages
-
What operating system can I upgrade my 2006 MacBook Pro 17" inch to if it has a 2.16Gh Intel dual core and 2G ram?
A Core Solo or Core Duo Mac can go to Mac OS X 10.6.8. A Core 2 Duo or better can go to Mac OS X 10.7.2.
(63169) -
Everytime I go to export a photo, I get an error.
"Export Results: Not enough memory (1)
Using Windows 7 32-bit. Intel i5 4690K CPU 16GB RAM 120 SSD and 1 TB harddrive.Even though you have 16gb of ram installed, 32 bit Windows can only use 4gb of it so 12gb is wasted. This is the reason you are getting not enough memory errors and is a known problem with Lightroom an 32 bit Windows during export. You need to change to 64 bit Windows.
-
Issues with sleep/wake feature after 16GB RAM upgrade in my MacBook Pro. Any thoughts?
Just installed a 16GB RAM upgrade in my MacBook Pro and now it doesn't wake up on it's own when I open the lid. I have to press the power button. It works fine with a smaller RAM upgrade.
I've tried putting in just one of the 8GB modules and the sleep/wake feature works as normal so there isn't a problem with the RAM modules that I've bought (Crucial.com). I've also put in a combination of Apple's original RAM and the new ones to make 10GB (8GB + 2GB), and the sleep/wake feature works on that too. Put both 8GB modules back in and the MacBook doesn't wake up when I open the lid, I have to press the power button to wake it up. The MacBook itself works fine, super fast and the memory is recognised on 'About This Mac', the sleep/wake issue is the only problem I'm having with the 16GB RAM.
Any thoughts on this? Has anybody else had this sleep/wake issue like this when upgrading RAM?I upgraded my early 2011 MBP to 16 gigs with Crucial. My machine would not sleep properly, because when I tried to wake it, it would wake from its hibernate image file. This is the issue I've seen here in this list.
I tried all the suggestions I saw on these groups. Nothing helped. I contacted Crucial, who suggested that if their RAM was defective, they'd replace it per their warranty process. I needed some proof it was their RAM causing the problem.
I put the original 8 gigs RAM back in the machine (2 4 gig sticks), and it behaved normally. I then put one stick of Crucial RAM in, all by itself. The machine behaved normally. I put the other stick of Crucial RAM back in, and took the first one out. The machine would not properly sleep and wake from sleep. This proved that one stick was causing the problem, and the other was not.
Defective RAM!
I then requested and received an RMA from Crucial to send the defective RAM back. They paid shipping. I got new sticks of RAM about a week later. These new sticks of RAM work properly. No sleep issues.
I'm surprised and disappointed to say that this is not the first time I've received defective RAM from Crucial. I've purchased from them for years, and had GREAT service and received high quality products. The past couple years my experience has been different.
I'm still pretty steamed about this, as I spent a great deal of time trying to diagnose the problem and fix it. I don't really have that kind of time to waste. My expectation was that their RAM was high quality, and unlikely to be at fault.
Perhaps this is just a bad batch of RAM. I get that. I can forgive them once. But this has happened twice in the past three years. I'll look elsewhere for my next memory purchase.
Keep in mind that their customer ratings are generally very high. My experience is probably isolated. -
Just purchased a new mac mini 3GHz Intel Core i7, with 16GB ram version 10.10.1. With it i purchased a new wireless keyboard. All of a sudden I was not able to use the #1 key. I thought I had a defected newly purchased keyboard. I pulled out my older wireless keyboard, and the same thing happened. It must not be the keyboard if it happened to two different keyboards. I have a habit of restarting my computer, when things don't work, I find it helps, and sure enough, everything works. Today, it happened again. Does anyone know what is causing this to happen?
Try resetting the SMC and PRAM
Intel-based Macs: Resetting the System Management Controller (SMC)
About NVRAM and PRAM
Try reinstalling Yosemite with out losing stuff. See:
OS X Yosemite: Reinstall OS X -
ThinkStation E30, built-in Intel HD Graphics and 2560x1440 display
I'm setting up a ThinkStation E30 w/ Intel HD Graphics and connecting it to an EIZO CG276 display.
The EIZO display supports 2560x1440 but I'm only able to get 1920x1200 from the built-in graphics (Win7 64bit).
Since the display only shipped with a DVI cable and a DisplayPort-to-mini-DisplayPort cable, I was provided a DisplayPort to DVI adapter by our IT dept.
Is the DP-to-DVI adpater limiting my resolution?
Is the built-in Intel HD Graphics capable of delivering 2560x1440?
If the built-in graphics isn't up to the job, my next question will be compatible graphics cards that deliver...
* 30bit color (10bits/channel).
* 2560x1440
* At least 2 x DisplayPort ports.
Thanks,
TerryThe MacBook Air is also power a much lower-resloution panel for its own display, so more of the GPU power can go towards an external display. The 15" Retina MacBook Pro is powering four times as many pixels as an Air.
-
MacBook Pro 13' Early 2011: Still Slow After 16GB RAM Upgrade
Hi,
I have a MacBook Pro 13' Early 2011 running Yosemite. After the RAM upgrade to 16GB, the speed of the computer is still not satisfactory, having some lag times in launching softwares and startup. Please suggest me what to do. Below is the report. Thank you!
Problem description:
The computer is still running slow even after the RAM upgrade to 16GB.
EtreCheck version: 2.0.11 (98)
Report generated November 18, 2014 at 5:40:20 AM EST
Hardware Information: ℹ️
MacBook Pro (13-inch, Early 2011) (Verified)
MacBook Pro - model: MacBookPro8,1
1 2.3 GHz Intel Core i5 CPU: 2-core
16 GB RAM Upgradeable
BANK 0/DIMM0
8 GB DDR3 1600 MHz ok
BANK 1/DIMM0
8 GB DDR3 1600 MHz ok
Bluetooth: Old - Handoff/Airdrop2 not supported
Wireless: en1: 802.11 a/b/g/n
Video Information: ℹ️
Intel HD Graphics 3000 - VRAM: 512 MB
Color LCD 1280 x 800
System Software: ℹ️
OS X 10.10.1 (14B25) - Uptime: 0:7:52
Disk Information: ℹ️
ST9320325ASG disk0 : (320.07 GB)
S.M.A.R.T. Status: Verified
EFI (disk0s1) <not mounted> : 210 MB
Recovery HD (disk0s3) <not mounted> [Recovery]: 650 MB
Macintosh HD (disk1) / [Startup]: 318.84 GB (156.62 GB free)
Encrypted AES-XTS Unlocked
Core Storage: disk0s2 319.21 GB Online
MATSHITADVD-R UJ-8A8
USB Information: ℹ️
Apple Computer, Inc. IR Receiver
Apple Inc. FaceTime HD Camera (Built-in)
Apple Inc. Apple Internal Keyboard / Trackpad
Apple Inc. BRCM2070 Hub
Apple Inc. Bluetooth USB Host Controller
Thunderbolt Information: ℹ️
Apple Inc. thunderbolt_bus
Gatekeeper: ℹ️
Mac App Store and identified developers
Kernel Extensions: ℹ️
/System/Library/Extensions
[loaded] com.Cycling74.driver.Soundflower (1.5.2) Support
[not loaded] com.marvell.kext.USBGenericPrinterClass (1.0.0) Support
[loaded] com.rim.driver.BlackBerryUSBDriverInt (0.0.74) Support
[not loaded] com.rim.driver.BlackBerryUSBDriverVSP (0.0.74) Support
[not loaded] com.wacom.kext.pentablet (5.3.0 - SDK 10.8) Support
Launch Agents: ℹ️
[loaded] com.google.keystone.agent.plist Support
[loaded] com.oracle.java.Java-Updater.plist Support
[running] com.rim.BBAlbumArtCacher.plist Support
[running] com.rim.BBLaunchAgent.plist Support
[running] com.wacom.pentablet.plist Support
Launch Daemons: ℹ️
[loaded] com.adobe.fpsaud.plist Support
[loaded] com.google.keystone.daemon.plist Support
[loaded] com.macpaw.CleanMyMac2.Agent.plist Support
[loaded] com.microsoft.office.licensing.helper.plist Support
[loaded] com.oracle.java.Helper-Tool.plist Support
[loaded] com.oracle.java.JavaUpdateHelper.plist Support
[running] com.rim.BBDaemon.plist Support
User Launch Agents: ℹ️
[loaded] com.adobe.ARM.[...].plist Support
[loaded] com.macpaw.CleanMyMac2Helper.diskSpaceWatcher.plist Support
[loaded] com.macpaw.CleanMyMac2Helper.scheduledScan.plist Support
[loaded] com.macpaw.CleanMyMac2Helper.trashWatcher.plist Support
[not loaded] com.valvesoftware.steamclean.plist Support
User Login Items: ℹ️
Dropbox Application (/Applications/Dropbox.app)
Internet Plug-ins: ℹ️
JavaAppletPlugin: Version: Java 7 Update 71 Check version
o1dbrowserplugin: Version: 5.38.6.0 - SDK 10.8 Support
WacomNetscape: Version: 2.1.0-1 - SDK 10.8 Support
Default Browser: Version: 600 - SDK 10.10
Flip4Mac WMV Plugin: Version: 2.4.0.11 Support
WacomTabletPlugin: Version: WacomTabletPlugin 2.1.0.2 Support
AdobePDFViewerNPAPI: Version: 11.0.09 - SDK 10.6 Support
FlashPlayer-10.6: Version: 15.0.0.223 - SDK 10.6 Support
Silverlight: Version: 5.1.10411.0 - SDK 10.6 Support
Flash Player: Version: 15.0.0.223 - SDK 10.6 Support
QuickTime Plugin: Version: 7.7.3
googletalkbrowserplugin: Version: 5.38.6.0 - SDK 10.8 Support
SharePointBrowserPlugin: Version: 14.4.6 - SDK 10.6 Support
AdobePDFViewer: Version: 11.0.09 - SDK 10.6 Support
DirectorShockwave: Version: 11.6.5r635 Support
User Internet Plug-ins: ℹ️
CitrixOnlineWebDeploymentPlugin: Version: 1.0.105 Support
WebEx64: Version: 1.0 - SDK 10.6 Support
3rd Party Preference Panes: ℹ️
Flash Player Support
Flip4Mac WMV Support
Java Support
Time Machine: ℹ️
Mobile backups: OFF
Auto backup: NO - Auto backup turned off
Volumes being backed up:
Macintosh HD: Disk size: 318.84 GB Disk used: 162.22 GB
Destinations:
LACIE SHARE [Local]
Total size: 350.07 GB
Total number of backups: 5
Oldest backup: 2012-07-17 01:12:57 +0000
Last backup: 2014-03-19 07:05:24 +0000
Size of backup disk: Too small
Backup size 350.07 GB < (Disk used 162.22 GB X 3)
Top Processes by CPU: ℹ️
9% mds
6% WindowServer
1% BBLaunchAgent
0% AppleSpell
0% fontd
Top Processes by Memory: ℹ️
103 MB mds_stores
86 MB Dropbox
86 MB ocspd
69 MB com.apple.WebKit.WebContent
52 MB Safari
Virtual Memory Information: ℹ️
13.07 GB Free RAM
1.71 GB Active RAM
740 MB Inactive RAM
1.66 GB Wired RAM
1.31 GB Page-ins
0 B Page-outsFirst go to the RIM web site and look to see if they have an uninstaller for the device you had. Some times a reinstall of the application and then running the uninstaller is required for complete removal.
If no uninstaller is available, then you will have to use Spotlight to find all items with 'Blackberry' and 'Rim' in the titles. I would also download EasyFind and use that to locate such files. Often it will locate items that Spotlight misses.
Ciao. -
15" Macbook Pro mid-2010, 16GB RAM upgrade possible?
Hi all,
I've been looking around all the support forums and questions asked etc..
But I can't find a definitive answer about support for the 15" mid-2010 MBP being able to use 16GB (and be stable).
I'm aware that it's perfectly fine on the 13" model, however I have the 15" i7.
From what I've been reading it's because of the motherboard/Graphics chip/EFI BIOS incompatibiity with anything more than 8GB. (Which is silly really, as the same Intel core i7 can have up too at least 32GB of RAM on any none-Mac system.)
Have Apple not pushed out an EFI BIOS update that could allow the use of 16GB RAM?
If this has been clearly answered elsewhere (and I haven't found it), feel free to point me in the right direction.
Thanks, Jon.Unfortunately, 8GB is the limit. I have the same machine. Why it works on the 13" and not the 15" is ridiculous, but that's how it is.
-
Is the current top line Mac Mini with an SSD and 16GB RAM up to PS CS6 and LR5?
I currently have a 2007 MacPro 2007 2.66GH Xeon dual core ( 4 cores ) with 9GB RAM.
I had been thinking of the new MacPro but it will probably be hellishly expensive. I was thinking of getting a top of the line Mac Mini with 16GB RAM and an SSD and using USB 3.0 and Thunderbolt to run most of my programs and data storage externally. I use LR5 and PS CS6.
I was just wondering if the latest Mac Mini was up to the taks with 2-4 GB files and multiple layers? How well do this little guys hold up? I know that the power supply is now internal. Do they run cool enough.... even with an SSD?
Any Mini users out there care to chime in?Well, the big drawback on the Minis is Intel integrated Graphics.
iMacs & Minis run far too hot in my Opinion, Apple likely tested them in a 68° F. air conditioned room.
I myself would be looking into an older iMac, or Widows PC!
iMac "Core i5" 2.5 21.5-Inch (Mid-2011)... Geekbench: 7241/7970
iMac "Core i5" 2.7 27-Inch (Mid-2011)... Geekbench: 7844/8565
iMac "Core i5" 2.7 21.5-Inch (Mid-2011)... Geekbench: 7890/8647
iMac "Core i7" 2.8 21.5-Inch (Mid-2011)... Geekbench: 10248/10690
Mac Pro "Quad Core" 2.66 (2009/Nehalem)... Geekbench: 8269/9237
iMac "Core i5" 2.9 27-Inch (Late 2012)... Geekbench: 9225/10271
Mac Pro "Eight Core" 2.8 (2008)... Geekbench: 9162/10564
Mac Pro "Quad Core" 3.2 (2010/Nehalem).. Geekbench: 9850/10440
MacBook Pro "Core i7" 2.5 27" Late 2011... Geekbench: 10706/11699
Mac mini "Core i7" 2.6 (Late 2012)... Geekbench: 11367/12807
iMac "Core i7" 3.4 27-Inch (Mid-2011)... Geekbench: 11648/12651
Mac Pro "Eight Core" 2.26 (2009/Nehalem)... Geekbench: 11864/13363
Mac Pro "Eight Core" 2.66 (2009/Nehalem)... Geekbench: 14317/16093
Mac Pro "Eight Core" 2.93 (2009/Nehalem)... Geekbench: 15572/17619
Mac Pro "Twelve Core" 2.66 (2010/Westmere)... Geekbench: 20294/22605
iMac "Core i5" 2.7 21.5-Inch (Late 2012)... Geekbench: 8068/9145
Mac mini "Core i7" 2.3 (Late 2012)... Geekbench: 10626/11825
iMac "Core i7" 3.1 21.5-Inch (Late 2012)... Geekbench: 12490/14143
iMac "Core i7" 3.4 27-Inch (Mid-2011)... Geekbench: 11648/12651... Geekbench: 12857/13772 -
Does anyone else have display issues with Intel X3100 graphics and OS X Lion?
I took the screenshot below to demonstrate one issue I have had with graphics since upgrading to OS X Lion. I use a Late 2007 MacBook with 2.0GHz Core 2 Duo and the Intel X3100 graphics chipset. I have 4GB RAM. Had to reboot to get this to correct itself. The problem is the menubar (obvious) and the desktop image is missing, replaced by the grey.
I have an external monitor connected (second image) and everything displays properly there.
Some other issues I've noticed are using Mission Control sometimes yields unpredictable results, graphically speaking, and the fullscreen apps don't always allow me to see the menubar. These all seem graphically related. Is this a hardware or software problem? Any solutions?Here is another display issue with my machine...perhaps software rather than hardware? The icon for the rtf file "Matt Passages" is missing entirely. There is a faint rectangle present instead. The same file has an icon in the first image posted above. No change to the file since then. And two other RTFs have the icon! Odd things with Lion.
-
Apple replaced the logic board, wiped the computer, did a fresh instal of the OS, and also a fresh instal of all the programs during the beginning of 2015. The GeekBench scores are the highest of any of the similar computers (at least on the day of my testing). But here's what's happening. The Macbook Pro Retina has a GeForce GT 650m with Cuda Technology and it can't handle editing in Premiere Pro with Cuda Acceleration turned on. Open CL, a second form of graphic acceleration on the Macbook Pro, appears to be functioning properly.
At the Apple Store on 1-10-2015, I was told that since the logic board and the graphic cards have been replaced that there is nothing they can do and they recommend contacting Corporate. This comes after they told me to buy a new logic board and that that would solve the problem. This comes after Apple did not listen, for over a month, about the possibility that they didn't properly build a professional notebook computer.
The computer displays a black program monitor screen, at random times, when the user edits footage with Cuda Acceleration enabled. It used to lead to an entire system crash and/or a Premiere Pro crash before the operating system was completely re-installed. My solution, since I bought the computer, was to edit in Open CL... However, I've come to learn that there is a major difference in performance between Open CL and Cuda Acceleration.
For the Macbook Pro Retina, Adobe Media Encoder render times are about 20% faster with Cuda Acceleration than Open CL. The 2013 Macbook Pro Retina appears to be able to handle Cuda Acceleration in Media Encoder, but I have had a number of issues leading to program crashes on every project before the new logic board and operating system were installed. For over a year and a half, I actually never used Cuda Acceleration. Having sent every crash report and user data to Apple over that time, I truly expected an update of some sorts and it never came.
FYI: The latest Macbook Pro Retina uses the GeForce GT 750m... This is essentially the same graphic card that performs about 10 - 20% faster due to a new "boost mode." More importantly, it actually has the exact same number of Cuda cores. Having the same number of Cuda Cores means that the Cuda Acceleration is essentially the same when exporting or viewing video. To prove a point to Apple that their 2013 Macbook Pro Retina isn't functioning properly, I bought the latest computer with the 2.5 i7, 16gb Ram, 512gb SSD and I can honestly say that the 2014 model works perfectly fine with Cuda Acceleration turned on while editing in Premiere. I can also say that a proper render test proved the 2013 and 2014 model to be the exact same.
I'm new to this whole pay $2700 for a computer that your manufacturer didn't / can't test properly, so I will be contacting Apple and speaking with Senior Advisors, their Customer Support division, and will soon speak with their Corporate branch. I'm confident that the Early 2013 Macbook Pro Retina with a 2.7 i7 16gb Ram and a 512 SSD is nearly the same at rendering video and editing video, provided the Cuda Acceleration works, as their latest 2014 Macbook Pro Retina with the 2.5 i7 processor 16gb Ram, and a 512 SSD. It's truly a great computer and a great build, minus their current inability to properly test / diagnose their computer.
Knowing that the latest graphic card in the Macbook Pro lineup is essentially the same model, I feel that Apple is not directly looking into the viability and life span of their current Macbook Pro Retina product line. They can't test for performance issues relating to their graphic cards, so why consider buying from them when the end user is actually in a position to experience up to a 20% decrease in certain professional programs.
For future reference, I'd strongly urge other individuals to avoid purchasing Apple products if they offer Cuda Technology. In my opinion, Apple is an Open CL organization, at best, who is not responsibly manufacturing / producing computers that fit their organization's strengths. For a fact, they can't test their Cuda Technology and won't even attempt to address Cuda Acceleration errors for Apple owners (01-11-2015). I say this having walked out of the Apple Store on 1-10-2015 with virtually no support other than to contact Corporate.Looks like a RAM issue.
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x02FE, 0x000000000000000000000000000000000000
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x02FE, 0x000000000000000000000000000000000000 -
13" MacBook Pro with Retina 256gb SSD and 16gb ram?
So I have decided to go with a 13" MacBook Pro with Retina.
I am now deciding on how to customize it...
My uses are:
Primary -> Writing. I am an aspiring writer/ future published author, and this unit will serve as a primary storage unit for on-the-go writing. The SSD will help in this capacity, tremendously, as well as battery life, as inspiration to write can happen anywhere. I found he typability to be easier on the MacBook Pro as well, rather than the Air.
Secondary -> Music, videos, gaming.
Basically, I am aware that the crispness of the rPro is apparent. I am not worried so much by the music, or videos, or even browsing part, as I'm sure its quite speedy.
What I am thinking is the might of the 4gb ram, 128gb SSD storage.
Would it be more worthwhile, since I plan to use this for 5+ years, to go for the little bit extra and get the 8gb ram, 256gb SSD storage unit, for only $200 extra. This seems a minor fee considering the length at which I plan to use and keep this.
That being said, I still play some older games and whatnot, with the possibility of playing World of Warcraft in the future... That being said, and knowing that Macs are not gaming powerhouses (unless you wish to go 15"+), would it be worthwhile to splurge another $200 for the 16GB ram? What major differences would doubling the 8 to 16 do for me and the performance of this MacBook?
Thanks in advance!
NickSince it is not possible to upgrade the RAM after purchase (it is soldered to the logicboard), I would definitely opt for 8GB. The same goes for the SSD- I would opt for double the storage. Though it is possible to upgrade your drive in the future, it comes at the cost of installing it yourself and potentially voiding any Apple warranty.
It would not be worthwhile to spend another 200$ on 16gb of RAM, IMO for your purposes. The lack of a discrete GPU and a duel core processor is what will limit gaming performance. 8GB of RAM is enough, in itself.
Rather than spending an additional $400 dollars, either spend the extra $200 for the 8gb 256GB model, or consider the 15'' entry level model for $700 extra dollars-which would be plently powerful enough for your purposes. -
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 -
How to change Virtual Memory in Windows 7 with SSD and 16GB RAM
I have SSD Samsung 850Pro with OS Windows 7 and have installed physical RAM 16GB.
In Adobe Help/Optimize performance/Photoshop written :
" To change Virtual Memory in Windows 7 and Vista, quit all applications and then do the following:
Choose Start > Control Panel, and double-click System.
Choose Advanced System Settings in the Tasks list.
Select the Advanced tab and click Settings in the Performance section.
Select the Advanced tab and click Change.
Deselect Automatically Manage Paging File Size For All Drives.
Click each hard disk letter to show the available space on that drive. Select a hard drive that has three times the amount of your computer’s installed RAM and doesn’t contain a scratch disk.
Select Custom Size, and type the amount of your physical RAM plus 300 MB in the Initial Size box. Type three times the amount of your computer’s installed RAM into the Maximum Size box.
Click Set, and then click OK. Continue to click OK to exit all dialog boxes.
Restart the computer: If you have applications open, select Restart Later, close your applications, then restart Windows. Otherwise, click Restart Now. "
Select Custom Size, and type the amount of your physical RAM plus 300 MB in the Initial Size box. Type three times the amount of your computer’s installed RAM into the Maximum Size box.
I have 16GB RAM
in the Initial Size box : 16384+300=16684MB
in the Maximum Size box:16684x3=50052MB
but in the description of SSD written :
" In order to address any potential lack of memory capacity, the Windows operating system automatically generates a block of virtual memory (pagefile.sys) on the C: drive. For example, a Windows® 7 64-bit system with 4 GB of physical memory would generate 4 GB of virtual memory at boot time.
In the past, before PC Memory (DRAM Modules) were available in high volume, PCs needed to utilize some HDD space to address any memory shortcomings. Today, with PCs featuring 4 GB of memory or more, it is possible to reduce or even eliminate the use of virtual memory. Additionally, using expanded physical memory, rather than creating virtual memory on the SSD, has performance and reliability advantages for the entire system. Some applications may require the use of virtual memory. In this case, please consider your specific application requirements before disabling this feature!!! ”..."SET virtual memory in the Initial Size Box :200MB and in the Maximum Size box: 2048MB"
what is the right choice ???
Please HelpWindows set to default virtual memory : 16348 MB =16GB !
But SSD program Samsung Magician wants virtual memory between in the Initial Size Box :200MB and in the Maximum Size box: 2048MB or 4096MB. If more than 8GB suggests that SSD will work slowly.
Perhaps the description in Adobe execution Help / Optimize / Photoshop is not correct or ? -
T410, Intel HD Graphics and Windows Server 2008
Hi All
When I run my video drivers with the standard VGA it works fine but I can't use my analog VGA port to a projector or external monitor without changing the BOS settings. If I install the Windows 7/Vista video drivers for the Intel HD Graphics, it appears to install ok, then, when I reboot, it starts to flash (it appears to be going through various modes) and then eventually comes up with a BSOD. I have tried the latest version and a previous version of the same driver.
Any ideas?
Thanks
AWindows 7 drivers should work, but the applications asociated with the drivers (a.k.a "panel control") won't work.
Officialy, Windows Server 2008 isn't supported by Lenovo. You can try to enter to Intel's site and checke there if they had published a working driver for your operative system.
Best regards.
IPnaSh
First Spanish Community Guru - Colaborador ad honorem
Maybe you are looking for
-
Best way to load videos to iMovie?
I have recently bought Canon EOS 5D mark iii and I am using Apperture for managing my photos. I have started taking videos as well now. I can load the videos from Apperture into iMovie for editing. But could I load them directly from my camera? Apper
-
Ways to retrieve Validation transform information for documentation
Hi All, We have a requirement which needs to document validation rule in all validation transform of data flow in a project. Does anyone know if there is a way which we can retrieve validation rules from DI repository? E.g. a SQL statement. I searche
-
Airtunes/airport express not working with MacBook
I have a new Macbook and an older Powerbook. The Powerbook is working nicely with my airport express and airtunes. I copied all settings to the new Macbook and configured it the same way, I also did the firmware update. ITunes found the airport expre
-
Having a problem in iBooks. When I highlight a section I would like to copy the highlighted parts sometimes to post in my notes. Can't seem to get it to work. Any ideas?
-
Hi, I am using the singleton design pattern in some places to insure unicity and access to some "global" data. However, I am now designing a few servlets where I would need this pattern but applied to a Session. My goal is to insure unicity of some s