Considering iMac 24" with nVidia 8800GTS

Hi All,
I'm currently running a PC with the specs below and have been considering a move to a Mac after having played with OSX and being very impressed. It seems to be what an OS should be - a thin veneer over the hardware.
The only thing concerning me is the iMac's game playing ability. Has anyone switched from PC to Mac with similiar specs? What would the difference in performance be? Would the iMac be able to run most current games?
I'm guessing the weak point would be the iMac's video card - a 8800GTS vs the 8800GTX that I have in my PC. Motherboard and processor wise, the Mac is much better. Presumably the two will kind of balance each other out?
Regards
RobP

Thanks Lenn,
I think I will hold off for a while, but my intention will be to make the switch at some point. I've been very impressed with Apple's iPod Touch and their OSX system.
Maybe, at some point in the future apple will consider better graphics cards. The rest of the specification is right up there. With such a card, Apple would have a chance of capturing some of the PC games market.
Regards
RobP

Similar Messages

CS4 on XP with NVIDIA 8800GT - terrible performance

I'm running CS4 on XP (Boot Camp on MAC) with an NVIDIA 8800GT 512mb. Performance is awful - constantly freezing during playback. The problem persists on After Effects as well. Meanwhile, the entire CS3 suite runs like a champ.
I found Adobe's registry keys that correct an issue with this graphics card and Photoshop CS4 - but it was no help to Premiere or After Effects.
I'm assuming this is a problem at the driver level but thought it was worth posting to see if anyone had found a solution.
CS4 works rather well on my PC(only) workstation with an NVIDIA 8800GTS 320mb.
Any ideas? I really think it's a graphics card issue, but let me know if you think I'm off track. Thanks.
Mac Pro
Dual Xenon Quad 3.2
2Gigs Ram
NVIDIA 8800GT 512
CS3 Installed w/ all updates
CS4 Installed w/ all updates

Model
ugnx-01
proe-04
catia-02
3dsmax-04
maya-02
sw-01
Adobe Test Render
Core2Duo T7300 Geforce 8600 Gt
5.07
12.81
14.13
18.68
27.08
8.96
4:18
Core2 Extreme 9300 Quadro 3700M
17.19
33.66
63.62
56.49
52.72
84.03
1:46
8 X 3.2ghz Xeon W5580 Quadro CX
17.48
48.65
52.95
81.31
91.99
99.04
1:06
4 X 3.2ghz Core i7 965 Quadro CX
27.26
87.53
96.38
108.56
210.73
253.31
0:52
Thanks for the tool, this will come in handy. I will be sure to post the Core i7 965. Unfortunatly I no longer have the dual Xeon Core i7 computer as it was just for a review. Here's some SpecViewPerf10 benchmarks(2 threads) along with adobe primiere pro render times. Keep in mind the test render was not using the quadro render accelerator presets to make it more of a CPU benchmark. As you can clearly see, the single Core i7 computer greatly outperforms the Xeon computer. The xeon computer also had more ram, faster hard drives, expensive intel motherboard, all the most expensive things you could possibly put in a PC. The Core i7 computer was made with cheaper components. I tried multiple SpecViewPerf10 benchmarks with 1-8 threads and nomatter what the Core i7 965 would beat it. Took out one of the Xeon W5580 cores, same benchmarks. Disabled hyperthreading on the W5580, same benchmarks. The Xeon W5580 is still fast, it's just if you are paying $2k per processor you would expect that a single $1k processor would not be better.
Also if you goto http://ppbm4.com/Benchmark.html. You can see your Core i7 920 beat out the Dual Xeon W5580 and W5590.
I was not entirely sure whether you meant the XEON or the Quadro CX in your benchmark tests. Unfortunatly your test tool will not show the power of the Quadro CX. I am sure you are aware, to utilize the Quadro CX you have to use special presets from a plugin. If I used these in the test it wouldn't be a good comparsion tool. I will however give the test a shot and send my results. I see your computer is top currently
In respect to the person previously. It is completly possible for a person who doesn't edit much to use Premiere Pro CS4 on Windows XP and not have a problem. It is also possible for a person to use Windows 95 and not have it crash. Does that make it a stable program still? Consider yourself one of the lucky ones. In a work environment where Premiere Pro is used on a daily basis it is considered unacceptable to have to redo a project once a week due to a bug. Windows 7 has less conflicts with Premiere Pro and therefore you should not use Windows XP. I had to put Windows 7 on all the video editors computers because they refused to use CS4 on Windows XP as it crashed too much.

Mac Pro 2007 with Nvidia 8800GT screen redraw problems on Mac OS 10.5.2

I seem to be having a slight screen redraw problem. Such as when grabbing the browser window and moving up and down it seems the redraw can't keep up,also seems problematic when watching flash or other video online. It does it in the finder too for windows listings or in icon view there is a fluttering or flashing back and forth, kind of like a white super split second flash when dragging the window box smaller or larger not as bad as when making smaller. Hard to describe but my original Ge-force that I pulled was not having these characteristics. I figure that the drivers need tweaking. In windows I am not getting these results. I have newer boot camp installed as well as the leopard graphics update done so I am trying to see if others are having a slight problem or maybe it is me.
Also I make certain it is not heat related as I monitor that and it does not matter at what temp it is.

Here's another similar experience -- and my solution.
I bought a Quad-core 2.8GHz (8GB RAM) Mac Pro in May and got the "better" Nvidia 8800GT. I thought I was happy, but there were redraw issues after sleeping and a display "roughness" I found annoying. Upgrading to OSX 10.5.4 didn't help.
I found it to be mostly absent on startup, but sleeping the Mac would bring it on. I.e., after sleep, the relatiionship between the 8800GT would be different than before. when I logged out and in again, the problem woud vanish. No what I expect from a "superior" graphics card. I ascribed it to funky drivers from Apple.
The store I bought the Mac from offered to swap for my suggestion of an ATI HD 3870, so I went for it about a week ago.
This card is far smoother than the 8800GT and just as fast in rendering benchmerks for graphics. (I'm not a gamer.) I am a happy camper! There is no stuttering, oddball redraw, or jerkiness as there had been with the 8800. It's perfect! Never mind that it may be 5% slower for gamers, it feels faster for my use.
BUT NOTE: As I now see from reading several forums, I wasn't alone is getting a screaming-Mimi at first! The first 3870 ran at nearly full fan speed at power-up. The speed changed a little with resolution changes on my big Mitsubishi CRT monitor, and actually stopped when I switched to 1080x1920 @ 72Hz! Then the fan would start and quit, start and quit randomly -- convincing me it was defective.
I returned this RED-shrouded unit and the store replaced it, this time with (randomly) a BLUE-shrouded unit. (Slightly lower serial.)
Bottom Line: This replacement 3870 is quiet as a mouse! Fan runs near-silently at startup and after hours of regular use in a 75ºF room. I get the distinct feeling that a bunch of cards with wonky fan controllers were built, and some of us got 'em.
Bad News: The ATI HD 3870 does NOT support multiple refresh rates under Windows XP-SP2 booting the Mac Pro, with or without Boot Camp drivers installed. No version of the ATI drivers fixes this, and ATI does not officially support Boot Camp yet. You can choose a resolution okay, but you're stuck at 60Hz refresh -- a pain for those of us who hate 60Hz flicker. (I like 100Hz refresh.)

IMAC 24Inch with NVidia 256 MB graphics card CRASHED NO SCREEN STARTUP HELP

HI there, wondering if anyone has had their nvidia GT graphics card crash then the screen go black?
I got home tonight, my ali imac 24inch, looks like its off, I turn it on, everything boots up but no
screen. Ive shared the screen through my macbook and look at the system info and it says under graphics displays "No information found" What does this mean? Has my graphics card destroyed itself?
It better not have! HELP!!!

Actually you may find that you have more success with an AMD\ATI Radeon video card.
I have experienced that with some motherboards, specifically Pegatron motherboards.
The problem is that you are delving into the DIY gaming PC realm and trying to do it with a prebuilt desktop PC.
Upgrading a prebuilt PC does not always result in a success story. Don't even consider trying to install cutting edge gaming memory modules. That will be a definite disappointment for you.
You may get lucky with an AMD Radeon HD video card.
But...You might just run into the same frustrating scenario you are facing today. I wish I had better news to give you.
****Please click on Accept As Solution if a suggestion solves your problem. It helps others facing the same problem to find a solution easily****
2015 Microsoft MVP - Windows Experience Consumer

Mac Pro (2008) with Nvidia 8800GT - Adding a second (ATI 5870) possible?

Hello there,
I have a 3,1 mac Pro with the bto Nvidia 8800 GT in it, but buying the Apple/ATI 5770/5870 as 'upgrade' is somewhat expensive (where do these prices come from??), I was wondering whether I could 'just' buy a normal 5870 (for less than the half of the apple one) and add it to the system to be used under Windows only (and hook it up with a second cable to my monitor) - so I keep the 8800 for EFI boot/mac os x, but would use the 5870 under windows.
Now what I was wondering is, do they fit in the 2008 mac pro case? And do I need any particular power cable for the extra card?!
Cheers and Thanks,
-J

Hello there,
I have a 3,1 mac Pro with the bto Nvidia 8800 GT in it, but buying the Apple/ATI 5770/5870 as 'upgrade' is somewhat expensive (where do these prices come from??), I was wondering whether I could 'just' buy a normal 5870 (for less than the half of the apple one) and add it to the system to be used under Windows only (and hook it up with a second cable to my monitor) - so I keep the 8800 for EFI boot/mac os x, but would use the 5870 under windows.
Now what I was wondering is, do they fit in the 2008 mac pro case? And do I need any particular power cable for the extra card?!
Cheers and Thanks,
-J

IMac 24" with NVidia 7600GT - Crappy image quality

Hi,
I just installed Windows 7 after updating my graphics firmware as described here: http://support.apple.com/kb/HT3967. The less I can say is that the quality of the image displayed is far from being decent, weird patterns are appearing, some parts of the image are flickering... in a word, a nightmare.
I made some pictures... Take a look at http://picasaweb.google.com/adam.eljabri/Windows7OnIMac24#
The first one is a screenshot I made on the same machine using the Windows 7 Snipping Tool, everything looks normal.
I installed Bootcamp 3.0, upgraded to 3.1 and even installed the updated drivers I could get for my card through Windows Update... each time with the same results.
Played with resolution (currently running at 1920x1200) and color depth (currently 32bit) but it didn't help.
Anybody else experiencing the same behaviour ?

That's interesting... Seems that putting my iMac to sleep and then waking it up solves the problem!
Not an ideal solution but at least it is a workaround.

IMac 24 with Nvidia 7600...bad video card choice?

Hi folks. I've had my iMac 24 incher for a few days now and I went to try one of my favorite game demos, Unreal Tournament 2004 and the performance I got from the video was a lot less than what I thought it would be. I have the game for my Windows machine which is a 3Ghz P4, 2GB RAM, GeForce 6600GT and the performance on that seems way better than my iMac. Why? I thought the video card it in was suppose to be pretty good (GeForce 7600GT 256mb). I changed the settings in UT to the native res of the mac but it didnt' help. Anything I can do about this? Thanks.

He said that he was running the demo. I don't
think
this has been updated to universal binary.
It has been updated. Do a search on versiontracker.
Do you mean this?
http://www.versiontracker.com/dyn/moreinfo/macosx/22450
Versiontracker screwed up again. This is a patch that updates the retail release of UT 2004 for Mac to version 3369.2. It isn't the demo. The demo weighs in at nearly 600 MB. If you have a link to a download of an actual UB demo of UT 2004, please feel free to share.
20" iMac CD (early '06) Mac OS X (10.4.7)

Clean install with nVidia 8800GT issue

I know that you either need a legacy graphics card or a 10.5.2+ installation DVD/CD to be able to do a clean install. There is a number of workarounds also and I used one of them. I restarted my MacPro in TARGET DISK MODE and connected it via FireWire 400 to my 15" MacBook Pro. I then successfully installed and updated OSX onto one of my MacPro internal drives. So now I have a clean 10.5.4 on my MacPro. But there is one issue/problem. My System Profiler now thinks that I have a MacBook Pro. How can I change that and if this is a problem or not.
TIA!

Little confused over here. Yes it was a clean install. I did not use a CD that came with neither the MacPro (because it would not run on MacBook Pro) nor the one for the MacBook Pro (because it is a Tiger CD). I used a 10.5 Retail DVD. After I installed it, I ran all the updates including hte 10.5.4 update. Only after that I could boot my MacPro using that hard drive. And now, it shows "Alexander's 15" MacBook Pro" in the system profiler. It does seem to show all the components correctly. 16GB RAM on a MacBook Pro? Haha, I wish.

Does imac come with nvidia graphics cards

title says it all

According to the apple specs for the 2012 21.5" and 27" iMacs they contain, the following depding on choices shown there:
AMD Radeon HD 6750M
AMD Radeon HD 6770M
AMD Radeon HD 6770M
AMD Radeon HD 6970M

IPhone not connecting through Bluetooth on iMac 21.5 inch with Nvidia 750 M

On my iMac 21.5 with Nvidia 750 M, both of my iPhones (iPhone 5s and iPhone 6) won't connect through bluetooth. I've tried disconnecting my wireless keyboard and mouse. The same connection error would pop-up. *By the way, you can talk in programmer's terms to me.*

An iPhone will not pair via Bluetooth to a computer (Mac or Windows) except for personal hotspot and then only if your cellular plan supports it. https://discussions.apple.com/docs/DOC-7722
If you are attempting to use Handoff/Continuity, that does involve Bluetooth but the devices are NOT paired; Bluetooth just needs to be on and the devices in range of each other. The following may help with Handoff/Continuity issues: http://support.apple.com/kb/TS5458

Got my 1st Mac! I have an iMac with Nvidia GT640M. What great native OSX FPS or MMO games will run well on it, if any?

Got my 1st Mac! I have an iMac with Nvidia GT640M. What great native OSX FPS or MMO games will run well on it, if any?
I'm an Android developer and got my iMac primarily for coding at home as well as general home computing (after being issued a macbook air at work and falling in love with OSX). I was a huge Windows gamer in the past but not in years. I switched from Windows to Linux a few years ago (when I transitioned my career from Windows development to Android). So gaming wasn't a big consideration in fact I didn't want anything too great for gaming so that I don't get sucked into gaming 24x7. However if I can enjoy a game or two on my iMac that would be cool.
I want a native Mac game and I want it to run well (not just barely on the lowest settings) or I would not bother. Will anything run great on my iMac or at least very good?

It's the same Deus Ex franchise.
If you want multyplayer games, again see App store where you will find Call of duty, Call of Duty 2, Call of Duty Black ops, and Modern Combat.
You can also search online for Mac compatible games.

NVIDIA 8800gt for Mac Pro (mid 2007 models) not compatible with TIGER !

Just tried to install Tiger on a hard drive while i was successfully able to use the NVIDIA 8800gt in Leopard on another hard drive and the computer would either stall or just have the gray screen come up. Brought it to Tekserve and they said Apple doesn't have firmware for this yet and it won't run on Tiger.. runs flawlessly on Leopard.. anyone have updates on this?

I purchased the 8800 card intending to run it with Tiger. I was assured both by the sales person I spoke with, and the engineer they checked with that it would work under Tiger. I even asked if it came with a driver CD and they said no, but it wasn't needed, it would "just work".
Of course, when I got it and put it in my Mac Pro running 10.4.11, it didn't boot. Then I realized there was a sticker on the box that said it required "10.5.2". I checked the product web page and it did not mention Leopard as a requirement. However, as of Monday April 28th, this was added to the web page. I have a screenshot from two days before which doesn't list it.
Anyway, I've returned the card and will be credited, but I am very disappointed. I can only conclude there was every intention to support tiger (probably with a Tiger Graphics Update 1.0 or some such) but this wasn't ready in time and they hastilty had to slap on the "10.5.2 required" sticker to the boxes.
Hopefully this update will come out at some point, and then I can repurchase the card. (I do not wish to upgrade to Leopard until the finder is fixed.) It would also be nice is there was a 10.4.12 release that supports the new Mac Pro's (hint: you'll get more sales if you do!)
If all else fails maybe ATI will have a new card out in the near future, and hopefully will support Tiger. I think they do a better job on drivers than nvidia anyway.

I have a MacPro 3,1 with 2 Nvidia 8800GT Kernel Panic

Ever since I installed Lion it is Kernel Panic Central! It seems to be Graphic IO related I submitted the crash....
This box was completely indestructuble till OS X Lion, It ran great for about a week after the upgrade, but now it's crashing like crazy is anyone else having this issue on a similar box?
I'm dreading a re-intall from scratch but.....running out of choices.
usually I get some graphihc artifacts then the Kernel Panic presents itself

Try with first just one 8800, then the other, removing one, and see if the panics go away.
Every new OS has done something similar. people said the same back in 2009 with their 8800GTs failing thnking the new OS and drivers, or added stress (and heat).
Toasting an 8800GT in the oven has been known to bring it back to life, apparently weak solder joints?

Accelerating Compressor with NVIDIA GTX 285 or GT 120?

Is there any way to accelerate Compressor using OpenCL with NVIDIA GTX 285 or GT 120? Plans to do this?

RedTruck wrote:
the standard? really…?
Yes. Every consumer camcorder that we sell at my camera shop records to AVCHD. Every Blu Ray player sold at WalMart, Best Buy, Target, etc. etc. etc. etc. uses AVCHD. It's the standard. Period.
Apple needs to get with the times! Sorry, but it's the truth. I'm not denigrating Apple, but they are living in a false reality if they think that AVCHD/Blu Ray is not the standard now, or that it's just going to go away because they refuse to acknowledge it or incorporate it into their products.
The assumption for many years has been that if you had a video camera, you should buy a Mac and it will be able to edit your videos right out of the box and burn them to a disc for playback on your computer. But it's simply not the case anymore.
I have customers come to my store and purchase AVCHD camcorders, and I got really tired of having to explain to people who came back with patches of hair missing where they pulled it out, that, "Sorry the Mac does not support the current HD standard."
"Huh? What?"
"That's right, it does not support AVCHD playback nor does it support Blu Ray."
"Really? Why?"
"I don't know."
"OK, well, what am I supposed to do? I just want to copy HD files to my Mac from off my camcorder and watch them."
"Sorry, not possible. Well, you could try VLC... but it will be choppy and horrific, unless you can somehow decipher its arcane preferences and get it to play those files back smooth, but I've been doing this for 20 years and I have no clue how to make VLC work for smooth AVCHD playback on a newer model iMac."
"OK.. well, how do I get them burned to disc?"
"Well, you could import them into iMovie, which requires transcoding the video into a much, much larger format, that takes a lot of time --"
"-- but wait, I bought a flash memory camcorder because I wanted to avoid the long camera to computer transfer times that plagued my life with a tape-based camcorder. But you're telling me now I have to wait hours and hours to capture my 120gb hard drive full of AVCHD video to my Mac in HD?"
"Yes, that's correct. Oh, and if you want to burn it to AVCHD/Blu Ray, you'll have to buy Toast and an external Blu Ray burner. That'll run you about.. $400. Oh, and when you do this, it will have to re-encode the video back into AVCHD, which will take *at least as long* as when you captured it in iMovie in the first place. And that 120GB of video is going to require... a LOT more than 120GB to store on your computer."
"$400?! I thought Mac came with the latest technology and supported the latest standards! More than 120GB? What the heck, why?"
"I'm sorry, but Apple transcodes it out of its native format, into some intermediary codec that eats up exponentially more space."
"Why the heck do they do that?"
"I don't know. Adobe Premiere Elements is the only consumer editing package that supports AVCHD natively, yet it only runs on PC. You could buy Premiere Pro CS4 but .. don't ask the price of that. Look, I don't know what to tell you. Buy Windows, install it, buy Premiere Elements, install that, and then buy Roxio Creator 2010 Pro, to burn your Blu Rays, and buy an external Blu Ray burner."
"Or just buy a PC that ships with Blu Ray?"
"**** no. Just wait.. until some undetermined future time.. when Apple finally decides to get with the times... <<sigh>>"
Anyway look. Currently Mac doesn't support the latest standards. I frequently have customers come to my camera shop, which is in the same mall as an Apple store, and I've had this conversation over, and over, and over again.
Anyone who disagrees that AVCHD is the standard needs to consider the fact that they are totally wrong.
Message was edited by: DaddieMac

[SOLVED] EDID read invalid with nvidia-313.18

Hello All,
after several months of trouble-free operation, my main system started having issues with detecting my second monitor properly. I am quite sure that this has something to do with the latest nvidia driver (313.18) but since I don't use this machine daily, I can't say exactly.
First, what's the problem? I have an nVidia GTX 460 card with two 26" TFTs @1920x1200 attached. No special configuration file has been necessary for some time now (everything detected automatically as needed). Now the main display (the left of two screens) is working as usual while the right one is limited to an 800x600 resolution. I've already tried several approaches to manually configure this one as intended but so far without success. nvidia-settings won't allow me to set any resolution other than Auto and is also weirdly showing the second display as DFP-3 whereas I think it used to be DFP-1 (following DFP-0 which is still active). A hardware issue can be eliminated as everything is smooth using an Ubuntu bootable CD which uses nouveau by default.
Here's the Xorg.0.log with a clean configuration (i. e. no /etc/X11/xorg.conf.d/10-monitor.conf)
[ 2.266]
X.Org X Server 1.13.2
Release Date: 2013-01-24
[ 2.266] X Protocol Version 11, Revision 0
[ 2.266] Build Operating System: Linux 3.7.4-1-ARCH x86_64
[ 2.266] Current Operating System: Linux einstein 3.7.6-1-ARCH #1 SMP PREEMPT Mon Feb 4 09:15:13 CET 2013 x86_64
[ 2.266] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=edf8551b-5b2d-4942-af17-b2ebb09a6cb6 ro quiet init=/usr/lib/systemd/systemd
[ 2.266] Build Date: 25 January 2013 09:33:50AM
[ 2.266]
[ 2.266] Current version of pixman: 0.28.2
[ 2.266] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 2.266] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 2.266] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Feb 9 11:29:34 2013
[ 2.268] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 2.269] (==) No Layout section. Using the first Screen section.
[ 2.269] (==) No screen section available. Using defaults.
[ 2.269] (**) |-->Screen "Default Screen Section" (0)
[ 2.269] (**) | |-->Monitor "<default monitor>"
[ 2.269] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 2.269] (==) Automatically adding devices
[ 2.269] (==) Automatically enabling devices
[ 2.269] (==) Automatically adding GPU devices
[ 2.270] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 2.270] Entry deleted from font path.
[ 2.271] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 2.271] Entry deleted from font path.
[ 2.271] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 2.271] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 2.271] Entry deleted from font path.
[ 2.271] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 2.271] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/Type1/
[ 2.271] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 2.271] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 2.271] (II) Loader magic: 0x7fcc40
[ 2.271] (II) Module ABI versions:
[ 2.271] X.Org ANSI C Emulation: 0.4
[ 2.271] X.Org Video Driver: 13.1
[ 2.271] X.Org XInput driver : 18.0
[ 2.271] X.Org Server Extension : 7.0
[ 2.272] (--) PCI:*(0:1:0:0) 10de:0e22:19da:2166 rev 161, Mem @ 0xf4000000/33554432, 0xe0000000/134217728, 0xe8000000/67108864, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[ 2.272] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 2.272] Initializing built-in extension Generic Event Extension
[ 2.272] Initializing built-in extension SHAPE
[ 2.272] Initializing built-in extension MIT-SHM
[ 2.272] Initializing built-in extension XInputExtension
[ 2.272] Initializing built-in extension XTEST
[ 2.272] Initializing built-in extension BIG-REQUESTS
[ 2.272] Initializing built-in extension SYNC
[ 2.272] Initializing built-in extension XKEYBOARD
[ 2.272] Initializing built-in extension XC-MISC
[ 2.272] Initializing built-in extension SECURITY
[ 2.272] Initializing built-in extension XINERAMA
[ 2.272] Initializing built-in extension XFIXES
[ 2.272] Initializing built-in extension RENDER
[ 2.272] Initializing built-in extension RANDR
[ 2.272] Initializing built-in extension COMPOSITE
[ 2.272] Initializing built-in extension DAMAGE
[ 2.272] Initializing built-in extension MIT-SCREEN-SAVER
[ 2.272] Initializing built-in extension DOUBLE-BUFFER
[ 2.272] Initializing built-in extension RECORD
[ 2.272] Initializing built-in extension DPMS
[ 2.272] Initializing built-in extension X-Resource
[ 2.272] Initializing built-in extension XVideo
[ 2.272] Initializing built-in extension XVideo-MotionCompensation
[ 2.272] Initializing built-in extension XFree86-VidModeExtension
[ 2.272] Initializing built-in extension XFree86-DGA
[ 2.272] Initializing built-in extension XFree86-DRI
[ 2.272] Initializing built-in extension DRI2
[ 2.272] (II) LoadModule: "glx"
[ 2.273] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 2.346] (II) Module glx: vendor="NVIDIA Corporation"
[ 2.346] compiled for 4.0.2, module version = 1.0.0
[ 2.346] Module class: X.Org Server Extension
[ 2.346] (II) NVIDIA GLX Module 313.18 Wed Jan 9 15:34:35 PST 2013
[ 2.346] Loading extension GLX
[ 2.346] (==) Matched nouveau as autoconfigured driver 0
[ 2.346] (==) Matched nvidia as autoconfigured driver 1
[ 2.346] (==) Matched nv as autoconfigured driver 2
[ 2.346] (==) Matched vesa as autoconfigured driver 3
[ 2.346] (==) Matched modesetting as autoconfigured driver 4
[ 2.346] (==) Matched fbdev as autoconfigured driver 5
[ 2.346] (==) Assigned the driver to the xf86ConfigLayout
[ 2.346] (II) LoadModule: "nouveau"
[ 2.347] (WW) Warning, couldn't open module nouveau
[ 2.347] (II) UnloadModule: "nouveau"
[ 2.347] (II) Unloading nouveau
[ 2.347] (EE) Failed to load module "nouveau" (module does not exist, 0)
[ 2.347] (II) LoadModule: "nvidia"
[ 2.347] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 2.355] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 2.355] compiled for 4.0.2, module version = 1.0.0
[ 2.355] Module class: X.Org Video Driver
[ 2.356] (II) LoadModule: "nv"
[ 2.356] (WW) Warning, couldn't open module nv
[ 2.356] (II) UnloadModule: "nv"
[ 2.356] (II) Unloading nv
[ 2.356] (EE) Failed to load module "nv" (module does not exist, 0)
[ 2.356] (II) LoadModule: "vesa"
[ 2.356] (WW) Warning, couldn't open module vesa
[ 2.356] (II) UnloadModule: "vesa"
[ 2.356] (II) Unloading vesa
[ 2.356] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 2.356] (II) LoadModule: "modesetting"
[ 2.357] (WW) Warning, couldn't open module modesetting
[ 2.357] (II) UnloadModule: "modesetting"
[ 2.357] (II) Unloading modesetting
[ 2.357] (EE) Failed to load module "modesetting" (module does not exist, 0)
[ 2.357] (II) LoadModule: "fbdev"
[ 2.357] (WW) Warning, couldn't open module fbdev
[ 2.357] (II) UnloadModule: "fbdev"
[ 2.357] (II) Unloading fbdev
[ 2.357] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 2.357] (II) NVIDIA dlloader X Driver 313.18 Wed Jan 9 15:15:26 PST 2013
[ 2.357] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 2.357] (++) using VT number 1
[ 2.358] (II) Loading sub module "wfb"
[ 2.358] (II) LoadModule: "wfb"
[ 2.358] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 2.359] (II) Module wfb: vendor="X.Org Foundation"
[ 2.359] compiled for 1.13.2, module version = 1.0.0
[ 2.359] ABI class: X.Org ANSI C Emulation, version 0.4
[ 2.359] (II) Loading sub module "ramdac"
[ 2.359] (II) LoadModule: "ramdac"
[ 2.359] (II) Module "ramdac" already built-in
[ 2.360] (II) NVIDIA(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 2.360] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[ 2.360] (==) NVIDIA(0): RGB weight 888
[ 2.360] (==) NVIDIA(0): Default visual is TrueColor
[ 2.360] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 2.360] (**) NVIDIA(0): Enabling 2D acceleration
[ 3.170] (II) NVIDIA(GPU-0): Display (Idek Iiyama PLE2607WS (DFP-0)) does not support
[ 3.170] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
[ 3.229] (WW) NVIDIA(GPU-0): The EDID read for display device DFP-3 is invalid:
[ 3.229] (WW) NVIDIA(GPU-0): unrecognized EDID Header.
[ 3.229] (--) NVIDIA(GPU-0):
[ 3.229] (--) NVIDIA(GPU-0): Raw EDID bytes:
[ 3.229] (--) NVIDIA(GPU-0):
[ 3.229] (--) NVIDIA(GPU-0): ff ff ff ff ff ff ff ff 26 cd 08 56 c0 c4 00 00
[ 3.229] (--) NVIDIA(GPU-0): 1d 13 01 03 81 37 22 78 2a 7b 65 a5 55 48 99 26
[ 3.229] (--) NVIDIA(GPU-0): 12 50 54 bd ef 80 71 4f 81 80 81 8f 95 00 95 0f
[ 3.229] (--) NVIDIA(GPU-0): a9 40 b3 00 01 01 28 3c 80 a0 70 b0 23 40 30 20
[ 3.229] (--) NVIDIA(GPU-0): 36 00 26 58 21 00 00 1a 1a 36 80 a0 70 38 1f 40
[ 3.229] (--) NVIDIA(GPU-0): 50 20 85 04 26 58 21 00 00 1a 00 00 00 fd 00 37
[ 3.229] (--) NVIDIA(GPU-0): 4c 1d 51 11 00 0a 20 20 20 20 20 20 00 00 00 fc
[ 3.229] (--) NVIDIA(GPU-0): 00 50 4c 45 32 36 30 37 57 53 0a 20 20 20 00 1e
[ 3.229] (--) NVIDIA(GPU-0):
[ 3.229] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 3.229] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 3.229] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 3.229] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 3.229] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 3.229] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 3.229] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 3.229] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 3.229] (--) NVIDIA(GPU-0):
[ 3.229] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 3.229] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 3.229] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 3.229] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 3.229] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 3.229] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 3.229] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 3.229] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 3.229] (--) NVIDIA(GPU-0):
[ 3.230] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 460 (GF104) at PCI:1:0:0 (GPU-0)
[ 3.230] (--) NVIDIA(0): Memory: 1048576 kBytes
[ 3.230] (--) NVIDIA(0): VideoBIOS: 70.04.13.00.a3
[ 3.230] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[ 3.232] (--) NVIDIA(0): Valid display device(s) on GeForce GTX 460 at PCI:1:0:0
[ 3.232] (--) NVIDIA(0): CRT-0
[ 3.232] (--) NVIDIA(0): CRT-1
[ 3.232] (--) NVIDIA(0): Idek Iiyama PLE2607WS (DFP-0) (connected)
[ 3.232] (--) NVIDIA(0): DFP-1
[ 3.232] (--) NVIDIA(0): DFP-2
[ 3.232] (--) NVIDIA(0): DFP-3 (connected)
[ 3.232] (--) NVIDIA(0): DFP-4
[ 3.232] (--) NVIDIA(0): CRT-0: 400.0 MHz maximum pixel clock
[ 3.232] (--) NVIDIA(0): CRT-1: 400.0 MHz maximum pixel clock
[ 3.232] (--) NVIDIA(0): Idek Iiyama PLE2607WS (DFP-0): 330.0 MHz maximum pixel clock
[ 3.232] (--) NVIDIA(0): Idek Iiyama PLE2607WS (DFP-0): Internal Dual Link TMDS
[ 3.232] (--) NVIDIA(0): DFP-1: 165.0 MHz maximum pixel clock
[ 3.232] (--) NVIDIA(0): DFP-1: Internal Single Link TMDS
[ 3.232] (--) NVIDIA(0): DFP-2: 165.0 MHz maximum pixel clock
[ 3.232] (--) NVIDIA(0): DFP-2: Internal Single Link TMDS
[ 3.232] (--) NVIDIA(0): DFP-3: 330.0 MHz maximum pixel clock
[ 3.232] (--) NVIDIA(0): DFP-3: Internal Dual Link TMDS
[ 3.232] (--) NVIDIA(0): DFP-4: 480.0 MHz maximum pixel clock
[ 3.232] (--) NVIDIA(0): DFP-4: Internal DisplayPort
[ 3.232] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 3.232] (**) NVIDIA(0): device Idek Iiyama PLE2607WS (DFP-0) (Using EDID
[ 3.232] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
[ 3.233] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 3.233] (**) NVIDIA(0): device DFP-3 (Using EDID frequencies has been enabled on
[ 3.233] (**) NVIDIA(0): all display devices.)
[ 3.233] (==) NVIDIA(0):
[ 3.233] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[ 3.233] (==) NVIDIA(0): will be used as the requested mode.
[ 3.233] (==) NVIDIA(0):
[ 3.233] (II) NVIDIA(0): Validated MetaModes:
[ 3.233] (II) NVIDIA(0): "DFP-0:nvidia-auto-select,DFP-3:nvidia-auto-select"
[ 3.233] (II) NVIDIA(0): Virtual screen size determined to be 2720 x 1200
[ 3.261] (--) NVIDIA(0): DPI set to (88, 89); computed from "UseEdidDpi" X config
[ 3.261] (--) NVIDIA(0): option
[ 3.261] (--) Depth 24 pixmap format is 32 bpp
[ 3.261] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory
[ 3.261] (II) NVIDIA: access.
[ 3.265] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 3.265] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 3.265] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 3.265] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 3.265] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 3.265] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 3.265] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[ 3.265] (II) NVIDIA(0): Config Options in the README.
[ 3.267] (II) NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select,DFP-3:nvidia-auto-select"
[ 3.357] Loading extension NV-GLX
[ 3.452] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 3.452] (==) NVIDIA(0): Backing store disabled
[ 3.452] (==) NVIDIA(0): Silken mouse enabled
[ 3.453] (==) NVIDIA(0): DPMS enabled
[ 3.453] Loading extension NV-CONTROL
[ 3.453] Loading extension XINERAMA
[ 3.453] (II) Loading sub module "dri2"
[ 3.453] (II) LoadModule: "dri2"
[ 3.453] (II) Module "dri2" already built-in
[ 3.453] (II) NVIDIA(0): [DRI2] Setup complete
[ 3.453] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
[ 3.453] (--) RandR disabled
[ 3.456] (II) Initializing extension GLX
[ 3.502] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[ 3.503] (**) Power Button: Applying InputClass "system-keyboard"
[ 3.503] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 3.503] (II) LoadModule: "evdev"
[ 3.503] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 3.505] (II) Module evdev: vendor="X.Org Foundation"
[ 3.505] compiled for 1.13.0, module version = 2.7.3
[ 3.505] Module class: X.Org XInput Driver
[ 3.505] ABI class: X.Org XInput driver, version 18.0
[ 3.505] (II) Using input driver 'evdev' for 'Power Button'
[ 3.505] (**) Power Button: always reports core events
[ 3.505] (**) evdev: Power Button: Device: "/dev/input/event1"
[ 3.505] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 3.505] (--) evdev: Power Button: Found keys
[ 3.505] (II) evdev: Power Button: Configuring as keyboard
[ 3.505] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1/event1"
[ 3.505] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 3.505] (**) Option "xkb_rules" "evdev"
[ 3.505] (**) Option "xkb_model" "pc105"
[ 3.505] (**) Option "xkb_layout" "de"
[ 3.505] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 3.529] (II) config/udev: Adding input device Power Button (/dev/input/event0)
[ 3.529] (**) Power Button: Applying InputClass "system-keyboard"
[ 3.529] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 3.529] (II) Using input driver 'evdev' for 'Power Button'
[ 3.529] (**) Power Button: always reports core events
[ 3.529] (**) evdev: Power Button: Device: "/dev/input/event0"
[ 3.529] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 3.529] (--) evdev: Power Button: Found keys
[ 3.529] (II) evdev: Power Button: Configuring as keyboard
[ 3.529] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0/event0"
[ 3.529] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[ 3.529] (**) Option "xkb_rules" "evdev"
[ 3.529] (**) Option "xkb_model" "pc105"
[ 3.529] (**) Option "xkb_layout" "de"
[ 3.529] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 3.530] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event11)
[ 3.530] (II) No input driver specified, ignoring this device.
[ 3.530] (II) This device may have been added with another device file.
[ 3.530] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event12)
[ 3.530] (II) No input driver specified, ignoring this device.
[ 3.530] (II) This device may have been added with another device file.
[ 3.531] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event13)
[ 3.531] (II) No input driver specified, ignoring this device.
[ 3.531] (II) This device may have been added with another device file.
[ 3.531] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event14)
[ 3.531] (II) No input driver specified, ignoring this device.
[ 3.531] (II) This device may have been added with another device file.
[ 3.531] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event3)
[ 3.531] (II) No input driver specified, ignoring this device.
[ 3.531] (II) This device may have been added with another device file.
[ 3.531] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event4)
[ 3.531] (II) No input driver specified, ignoring this device.
[ 3.531] (II) This device may have been added with another device file.
[ 3.532] (II) config/udev: Adding input device HDA Intel PCH Line Out (/dev/input/event5)
[ 3.532] (II) No input driver specified, ignoring this device.
[ 3.532] (II) This device may have been added with another device file.
[ 3.532] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event7)
[ 3.532] (**) Logitech USB Receiver: Applying InputClass "evdev pointer catchall"
[ 3.532] (II) Using input driver 'evdev' for 'Logitech USB Receiver'
[ 3.532] (**) Logitech USB Receiver: always reports core events
[ 3.532] (**) evdev: Logitech USB Receiver: Device: "/dev/input/event7"
[ 3.532] (--) evdev: Logitech USB Receiver: Vendor 0x46d Product 0xc51a
[ 3.532] (--) evdev: Logitech USB Receiver: Found 20 mouse buttons
[ 3.532] (--) evdev: Logitech USB Receiver: Found scroll wheel(s)
[ 3.532] (--) evdev: Logitech USB Receiver: Found relative axes
[ 3.532] (--) evdev: Logitech USB Receiver: Found x and y relative axes
[ 3.532] (II) evdev: Logitech USB Receiver: Configuring as mouse
[ 3.532] (II) evdev: Logitech USB Receiver: Adding scrollwheel support
[ 3.532] (**) evdev: Logitech USB Receiver: YAxisMapping: buttons 4 and 5
[ 3.532] (**) evdev: Logitech USB Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 3.532] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.7/2-1.7:1.0/input/input7/event7"
[ 3.532] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: MOUSE, id 8)
[ 3.532] (II) evdev: Logitech USB Receiver: initialized for relative axes.
[ 3.533] (**) Logitech USB Receiver: (accel) keeping acceleration scheme 1
[ 3.533] (**) Logitech USB Receiver: (accel) acceleration profile 0
[ 3.533] (**) Logitech USB Receiver: (accel) acceleration factor: 2.000
[ 3.533] (**) Logitech USB Receiver: (accel) acceleration threshold: 4
[ 3.533] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/mouse0)
[ 3.533] (II) No input driver specified, ignoring this device.
[ 3.533] (II) This device may have been added with another device file.
[ 3.533] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event8)
[ 3.533] (**) Logitech USB Receiver: Applying InputClass "system-keyboard"
[ 3.533] (**) Logitech USB Receiver: Applying InputClass "evdev keyboard catchall"
[ 3.533] (II) Using input driver 'evdev' for 'Logitech USB Receiver'
[ 3.533] (**) Logitech USB Receiver: always reports core events
[ 3.533] (**) evdev: Logitech USB Receiver: Device: "/dev/input/event8"
[ 3.534] (--) evdev: Logitech USB Receiver: Vendor 0x46d Product 0xc51a
[ 3.534] (--) evdev: Logitech USB Receiver: Found 1 mouse buttons
[ 3.534] (--) evdev: Logitech USB Receiver: Found scroll wheel(s)
[ 3.534] (--) evdev: Logitech USB Receiver: Found relative axes
[ 3.534] (II) evdev: Logitech USB Receiver: Forcing relative x/y axes to exist.
[ 3.534] (--) evdev: Logitech USB Receiver: Found absolute axes
[ 3.534] (II) evdev: Logitech USB Receiver: Forcing absolute x/y axes to exist.
[ 3.534] (--) evdev: Logitech USB Receiver: Found keys
[ 3.534] (II) evdev: Logitech USB Receiver: Configuring as mouse
[ 3.534] (II) evdev: Logitech USB Receiver: Configuring as keyboard
[ 3.534] (II) evdev: Logitech USB Receiver: Adding scrollwheel support
[ 3.534] (**) evdev: Logitech USB Receiver: YAxisMapping: buttons 4 and 5
[ 3.534] (**) evdev: Logitech USB Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 3.534] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.7/2-1.7:1.1/input/input8/event8"
[ 3.534] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD, id 9)
[ 3.534] (**) Option "xkb_rules" "evdev"
[ 3.534] (**) Option "xkb_model" "pc105"
[ 3.534] (**) Option "xkb_layout" "de"
[ 3.534] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 3.534] (II) evdev: Logitech USB Receiver: initialized for relative axes.
[ 3.534] (WW) evdev: Logitech USB Receiver: ignoring absolute axes.
[ 3.534] (**) Logitech USB Receiver: (accel) keeping acceleration scheme 1
[ 3.534] (**) Logitech USB Receiver: (accel) acceleration profile 0
[ 3.534] (**) Logitech USB Receiver: (accel) acceleration factor: 2.000
[ 3.534] (**) Logitech USB Receiver: (accel) acceleration threshold: 4
[ 3.535] (II) config/udev: Adding input device Microsoft Microsoft® Digital Media Pro Keyboard (/dev/input/event9)
[ 3.535] (**) Microsoft Microsoft® Digital Media Pro Keyboard: Applying InputClass "system-keyboard"
[ 3.535] (**) Microsoft Microsoft® Digital Media Pro Keyboard: Applying InputClass "evdev keyboard catchall"
[ 3.535] (II) Using input driver 'evdev' for 'Microsoft Microsoft® Digital Media Pro Keyboard'
[ 3.535] (**) Microsoft Microsoft® Digital Media Pro Keyboard: always reports core events
[ 3.535] (**) evdev: Microsoft Microsoft® Digital Media Pro Keyboard: Device: "/dev/input/event9"
[ 3.535] (--) evdev: Microsoft Microsoft® Digital Media Pro Keyboard: Vendor 0x45e Product 0xb0
[ 3.535] (--) evdev: Microsoft Microsoft® Digital Media Pro Keyboard: Found keys
[ 3.535] (II) evdev: Microsoft Microsoft® Digital Media Pro Keyboard: Configuring as keyboard
[ 3.535] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0/input/input9/event9"
[ 3.535] (II) XINPUT: Adding extended input device "Microsoft Microsoft® Digital Media Pro Keyboard" (type: KEYBOARD, id 10)
[ 3.535] (**) Option "xkb_rules" "evdev"
[ 3.535] (**) Option "xkb_model" "pc105"
[ 3.535] (**) Option "xkb_layout" "de"
[ 3.535] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 3.536] (II) config/udev: Adding input device Microsoft Microsoft® Digital Media Pro Keyboard (/dev/input/event10)
[ 3.536] (**) Microsoft Microsoft® Digital Media Pro Keyboard: Applying InputClass "system-keyboard"
[ 3.536] (**) Microsoft Microsoft® Digital Media Pro Keyboard: Applying InputClass "evdev keyboard catchall"
[ 3.536] (II) Using input driver 'evdev' for 'Microsoft Microsoft® Digital Media Pro Keyboard'
[ 3.536] (**) Microsoft Microsoft® Digital Media Pro Keyboard: always reports core events
[ 3.536] (**) evdev: Microsoft Microsoft® Digital Media Pro Keyboard: Device: "/dev/input/event10"
[ 3.536] (--) evdev: Microsoft Microsoft® Digital Media Pro Keyboard: Vendor 0x45e Product 0xb0
[ 3.536] (--) evdev: Microsoft Microsoft® Digital Media Pro Keyboard: Found 1 mouse buttons
[ 3.536] (--) evdev: Microsoft Microsoft® Digital Media Pro Keyboard: Found scroll wheel(s)
[ 3.536] (--) evdev: Microsoft Microsoft® Digital Media Pro Keyboard: Found relative axes
[ 3.536] (--) evdev: Microsoft Microsoft® Digital Media Pro Keyboard: Found absolute axes
[ 3.536] (--) evdev: Microsoft Microsoft® Digital Media Pro Keyboard: Found absolute multitouch axes
[ 3.536] (--) evdev: Microsoft Microsoft® Digital Media Pro Keyboard: Found x and y absolute axes
[ 3.536] (--) evdev: Microsoft Microsoft® Digital Media Pro Keyboard: Found keys
[ 3.536] (II) evdev: Microsoft Microsoft® Digital Media Pro Keyboard: Forcing relative x/y axes to exist.
[ 3.536] (II) evdev: Microsoft Microsoft® Digital Media Pro Keyboard: Configuring as mouse
[ 3.536] (II) evdev: Microsoft Microsoft® Digital Media Pro Keyboard: Configuring as keyboard
[ 3.536] (II) evdev: Microsoft Microsoft® Digital Media Pro Keyboard: Adding scrollwheel support
[ 3.536] (**) evdev: Microsoft Microsoft® Digital Media Pro Keyboard: YAxisMapping: buttons 4 and 5
[ 3.536] (**) evdev: Microsoft Microsoft® Digital Media Pro Keyboard: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 3.536] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.1/input/input10/event10"
[ 3.536] (II) XINPUT: Adding extended input device "Microsoft Microsoft® Digital Media Pro Keyboard" (type: KEYBOARD, id 11)
[ 3.536] (**) Option "xkb_rules" "evdev"
[ 3.536] (**) Option "xkb_model" "pc105"
[ 3.536] (**) Option "xkb_layout" "de"
[ 3.536] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 3.536] (II) evdev: Microsoft Microsoft® Digital Media Pro Keyboard: initialized for relative axes.
[ 3.536] (WW) evdev: Microsoft Microsoft® Digital Media Pro Keyboard: ignoring absolute axes.
[ 3.536] (**) Microsoft Microsoft® Digital Media Pro Keyboard: (accel) keeping acceleration scheme 1
[ 3.536] (**) Microsoft Microsoft® Digital Media Pro Keyboard: (accel) acceleration profile 0
[ 3.536] (**) Microsoft Microsoft® Digital Media Pro Keyboard: (accel) acceleration factor: 2.000
[ 3.536] (**) Microsoft Microsoft® Digital Media Pro Keyboard: (accel) acceleration threshold: 4
[ 3.537] (II) config/udev: Adding input device Microsoft Microsoft® Digital Media Pro Keyboard (/dev/input/js0)
[ 3.537] (**) Microsoft Microsoft® Digital Media Pro Keyboard: Applying InputClass "system-keyboard"
[ 3.537] (II) No input driver specified, ignoring this device.
[ 3.537] (II) This device may have been added with another device file.
[ 3.537] (II) config/udev: Adding input device Eee PC WMI hotkeys (/dev/input/event6)
[ 3.537] (**) Eee PC WMI hotkeys: Applying InputClass "system-keyboard"
[ 3.537] (**) Eee PC WMI hotkeys: Applying InputClass "evdev keyboard catchall"
[ 3.537] (II) Using input driver 'evdev' for 'Eee PC WMI hotkeys'
[ 3.537] (**) Eee PC WMI hotkeys: always reports core events
[ 3.537] (**) evdev: Eee PC WMI hotkeys: Device: "/dev/input/event6"
[ 3.537] (--) evdev: Eee PC WMI hotkeys: Vendor 0 Product 0
[ 3.537] (--) evdev: Eee PC WMI hotkeys: Found keys
[ 3.537] (II) evdev: Eee PC WMI hotkeys: Configuring as keyboard
[ 3.537] (**) Option "config_info" "udev:/sys/devices/platform/eeepc-wmi/input/input6/event6"
[ 3.537] (II) XINPUT: Adding extended input device "Eee PC WMI hotkeys" (type: KEYBOARD, id 12)
[ 3.537] (**) Option "xkb_rules" "evdev"
[ 3.537] (**) Option "xkb_model" "pc105"
[ 3.537] (**) Option "xkb_layout" "de"
[ 3.537] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 3.538] (II) config/udev: Adding input device PC Speaker (/dev/input/event2)
[ 3.538] (II) No input driver specified, ignoring this device.
[ 3.538] (II) This device may have been added with another device file.
[ 3.542] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event4)
[ 3.542] (II) No input driver specified, ignoring this device.
[ 3.542] (II) This device may have been added with another device file.
[ 3.542] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event14)
[ 3.542] (II) No input driver specified, ignoring this device.
[ 3.542] (II) This device may have been added with another device file.
[ 3.543] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event3)
[ 3.543] (II) No input driver specified, ignoring this device.
[ 3.543] (II) This device may have been added with another device file.
[ 3.543] (II) config/udev: Adding input device HDA Intel PCH Line Out (/dev/input/event5)
[ 3.543] (II) No input driver specified, ignoring this device.
[ 3.543] (II) This device may have been added with another device file.
[ 3.543] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event13)
[ 3.543] (II) No input driver specified, ignoring this device.
[ 3.543] (II) This device may have been added with another device file.
[ 3.543] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event12)
[ 3.543] (II) No input driver specified, ignoring this device.
[ 3.543] (II) This device may have been added with another device file.
[ 3.543] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event11)
[ 3.543] (II) No input driver specified, ignoring this device.
[ 3.543] (II) This device may have been added with another device file.
[ 3.620] (II) NVIDIA(GPU-0): Display (Idek Iiyama PLE2607WS (DFP-0)) does not support
[ 3.620] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
[ 3.620] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 3.620] (**) NVIDIA(0): device Idek Iiyama PLE2607WS (DFP-0) (Using EDID
[ 3.620] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
[ 3.679] (WW) NVIDIA(GPU-0): The EDID read for display device DFP-3 is invalid:
[ 3.679] (WW) NVIDIA(GPU-0): unrecognized EDID Header.
[ 3.679] (--) NVIDIA(GPU-0):
[ 3.679] (--) NVIDIA(GPU-0): Raw EDID bytes:
[ 3.679] (--) NVIDIA(GPU-0):
[ 3.679] (--) NVIDIA(GPU-0): ff ff ff ff ff ff ff ff 26 cd 08 56 c0 c4 00 00
[ 3.679] (--) NVIDIA(GPU-0): 1d 13 01 03 81 37 22 78 2a 7b 65 a5 55 48 99 26
[ 3.679] (--) NVIDIA(GPU-0): 12 50 54 bd ef 80 71 4f 81 80 81 8f 95 00 95 0f
[ 3.679] (--) NVIDIA(GPU-0): a9 40 b3 00 01 01 28 3c 80 a0 70 b0 23 40 30 20
[ 3.679] (--) NVIDIA(GPU-0): 36 00 26 58 21 00 00 1a 1a 36 80 a0 70 38 1f 40
[ 3.679] (--) NVIDIA(GPU-0): 50 20 85 04 26 58 21 00 00 1a 00 00 00 fd 00 37
[ 3.679] (--) NVIDIA(GPU-0): 4c 1d 51 11 00 0a 20 20 20 20 20 20 00 00 00 fc
[ 3.679] (--) NVIDIA(GPU-0): 00 50 4c 45 32 36 30 37 57 53 0a 20 20 20 00 1e
[ 3.680] (--) NVIDIA(GPU-0):
[ 3.680] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 3.680] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 3.680] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 3.680] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 3.680] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 3.680] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 3.680] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 3.680] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 3.680] (--) NVIDIA(GPU-0):
[ 3.680] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 3.680] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 3.680] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 3.680] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 3.680] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 3.680] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 3.680] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 3.680] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 3.680] (--) NVIDIA(GPU-0):
[ 3.680] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 3.680] (**) NVIDIA(0): device DFP-3 (Using EDID frequencies has been enabled on
[ 3.680] (**) NVIDIA(0): all display devices.)
[ 4.259] (II) NVIDIA(GPU-0): Display (Idek Iiyama PLE2607WS (DFP-0)) does not support
[ 4.259] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
[ 4.259] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 4.259] (**) NVIDIA(0): device Idek Iiyama PLE2607WS (DFP-0) (Using EDID
[ 4.259] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
[ 4.319] (WW) NVIDIA(GPU-0): The EDID read for display device DFP-3 is invalid:
[ 4.319] (WW) NVIDIA(GPU-0): unrecognized EDID Header.
[ 4.319] (--) NVIDIA(GPU-0):
[ 4.319] (--) NVIDIA(GPU-0): Raw EDID bytes:
[ 4.319] (--) NVIDIA(GPU-0):
[ 4.319] (--) NVIDIA(GPU-0): ff ff ff ff ff ff ff ff 26 cd 08 56 c0 c4 00 00
[ 4.319] (--) NVIDIA(GPU-0): 1d 13 01 03 81 37 22 78 2a 7b 65 a5 55 48 99 26
[ 4.319] (--) NVIDIA(GPU-0): 12 50 54 bd ef 80 71 4f 81 80 81 8f 95 00 95 0f
[ 4.319] (--) NVIDIA(GPU-0): a9 40 b3 00 01 01 28 3c 80 a0 70 b0 23 40 30 20
[ 4.319] (--) NVIDIA(GPU-0): 36 00 26 58 21 00 00 1a 1a 36 80 a0 70 38 1f 40
[ 4.319] (--) NVIDIA(GPU-0): 50 20 85 04 26 58 21 00 00 1a 00 00 00 fd 00 37
[ 4.319] (--) NVIDIA(GPU-0): 4c 1d 51 11 00 0a 20 20 20 20 20 20 00 00 00 fc
[ 4.319] (--) NVIDIA(GPU-0): 00 50 4c 45 32 36 30 37 57 53 0a 20 20 20 00 1e
[ 4.319] (--) NVIDIA(GPU-0):
[ 4.319] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 4.319] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 4.319] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 4.319] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 4.319] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 4.319] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 4.319] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 4.319] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 4.319] (--) NVIDIA(GPU-0):
[ 4.319] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 4.319] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 4.319] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 4.319] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 4.319] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 4.319] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 4.319] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 4.319] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 4.319] (--) NVIDIA(GPU-0):
[ 4.319] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 4.319] (**) NVIDIA(0): device DFP-3 (Using EDID frequencies has been enabled on
[ 4.319] (**) NVIDIA(0): all display devices.)
[ 16.599] (II) NVIDIA(GPU-0): Display (Idek Iiyama PLE2607WS (DFP-0)) does not support
[ 16.599] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
[ 16.599] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 16.599] (**) NVIDIA(0): device Idek Iiyama PLE2607WS (DFP-0) (Using EDID
[ 16.599] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
[ 16.659] (WW) NVIDIA(GPU-0): The EDID read for display device DFP-3 is invalid:
[ 16.659] (WW) NVIDIA(GPU-0): unrecognized EDID Header.
[ 16.659] (--) NVIDIA(GPU-0):
[ 16.659] (--) NVIDIA(GPU-0): Raw EDID bytes:
[ 16.659] (--) NVIDIA(GPU-0):
[ 16.659] (--) NVIDIA(GPU-0): ff ff ff ff ff ff ff ff 26 cd 08 56 c0 c4 00 00
[ 16.659] (--) NVIDIA(GPU-0): 1d 13 01 03 81 37 22 78 2a 7b 65 a5 55 48 99 26
[ 16.659] (--) NVIDIA(GPU-0): 12 50 54 bd ef 80 71 4f 81 80 81 8f 95 00 95 0f
[ 16.659] (--) NVIDIA(GPU-0): a9 40 b3 00 01 01 28 3c 80 a0 70 b0 23 40 30 20
[ 16.659] (--) NVIDIA(GPU-0): 36 00 26 58 21 00 00 1a 1a 36 80 a0 70 38 1f 40
[ 16.659] (--) NVIDIA(GPU-0): 50 20 85 04 26 58 21 00 00 1a 00 00 00 fd 00 37
[ 16.659] (--) NVIDIA(GPU-0): 4c 1d 51 11 00 0a 20 20 20 20 20 20 00 00 00 fc
[ 16.659] (--) NVIDIA(GPU-0): 00 50 4c 45 32 36 30 37 57 53 0a 20 20 20 00 1e
[ 16.659] (--) NVIDIA(GPU-0):
[ 16.659] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 16.659] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 16.659] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 16.659] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 16.659] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 16.659] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 16.659] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 16.659] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 16.659] (--) NVIDIA(GPU-0):
[ 16.659] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 16.659] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 16.659] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 16.659] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 16.659] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 16.659] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 16.659] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 16.659] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 16.659] (--) NVIDIA(GPU-0):
[ 16.659] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 16.659] (**) NVIDIA(0): device DFP-3 (Using EDID frequencies has been enabled on
[ 16.659] (**) NVIDIA(0): all display devices.)
[ 17.393] (II) NVIDIA(GPU-0): Display (Idek Iiyama PLE2607WS (DFP-0)) does not support
[ 17.393] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
[ 17.393] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 17.393] (**) NVIDIA(0): device Idek Iiyama PLE2607WS (DFP-0) (Using EDID
[ 17.393] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
[ 17.453] (WW) NVIDIA(GPU-0): The EDID read for display device DFP-3 is invalid:
[ 17.453] (WW) NVIDIA(GPU-0): unrecognized EDID Header.
[ 17.453] (--) NVIDIA(GPU-0):
[ 17.453] (--) NVIDIA(GPU-0): Raw EDID bytes:
[ 17.453] (--) NVIDIA(GPU-0):
[ 17.453] (--) NVIDIA(GPU-0): ff ff ff ff ff ff ff ff 26 cd 08 56 c0 c4 00 00
[ 17.453] (--) NVIDIA(GPU-0): 1d 13 01 03 81 37 22 78 2a 7b 65 a5 55 48 99 26
[ 17.453] (--) NVIDIA(GPU-0): 12 50 54 bd ef 80 71 4f 81 80 81 8f 95 00 95 0f
[ 17.453] (--) NVIDIA(GPU-0): a9 40 b3 00 01 01 28 3c 80 a0 70 b0 23 40 30 20
[ 17.453] (--) NVIDIA(GPU-0): 36 00 26 58 21 00 00 1a 1a 36 80 a0 70 38 1f 40
[ 17.453] (--) NVIDIA(GPU-0): 50 20 85 04 26 58 21 00 00 1a 00 00 00 fd 00 37
[ 17.453] (--) NVIDIA(GPU-0): 4c 1d 51 11 00 0a 20 20 20 20 20 20 00 00 00 fc
[ 17.453] (--) NVIDIA(GPU-0): 00 50 4c 45 32 36 30 37 57 53 0a 20 20 20 00 1e
[ 17.453] (--) NVIDIA(GPU-0):
[ 17.453] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 17.453] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 17.453] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 17.453] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 17.453] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 17.453] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 17.453] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 17.453] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 17.453] (--) NVIDIA(GPU-0):
[ 17.453] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 17.453] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 17.453] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 17.453] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 17.453] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 17.453] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 17.453] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 17.453] (--) NVIDIA(GPU-0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 17.453] (--) NVIDIA(GPU-0):
[ 17.453] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 17.453] (**) NVIDIA(0): device DFP-3 (Using EDID frequencies has been enabled on
[ 17.453] (**) NVIDIA(0): all display devices.)
As you can see, the EDID information cannot be obtained from the second display. Since I haven't found any indication of this being a bug in the latest nVidia driver, I wanted to ask whether you have come across any hints or explanations.
For the time being, I can live with it but I'm actually considering moving to nouveau instead now.
Thanks for your time. Cheers
Smoerrebroed
Last edited by Smoerrebroed (2013-05-04 11:34:32)

Alright, though it still bothers me that for some reason the nvidia driver no longer correctly reads and processes EDID information on all connectors, supplying DFP-0's EDID to DFP-3 via the "CustomEDID" option fixed all woes. 1920x1200 is now again detected as default, TwinView is enabled and so on ... even without a sophisticated 10-monitor.conf:
Section "Device"
Identifier "GeForce GTX 460"
Driver "nvidia"
Option "CustomEDID" "DFP-3:/etc/X11/xorg.conf.d/edid.bin"
EndSection
Everything else remains at default and works. Perhaps this post will also help others in dealing with nvidia issues.
One thing this has taught me though is: As much inclined as I am towards open source software, the nouveau driver is really still a long way off the performance of the proprietary nvidia module. If you want/need to work seriously in 3D, there's no alternative.
Cheers
Smoerrebroed
Last edited by Smoerrebroed (2013-05-31 19:36:45)

Considering iMac 24" with nVidia 8800GTS

Similar Messages

Maybe you are looking for