Masking issues with Motion 5

Hi guys,
I had this general masking technique that I used with Motion 4 where I'd use any group of shapes, paintstrokes and so on, to mask some other object by dragging my group of "mask objects" into the image mask source well.
This technique no longer works as expected with Motion 5.
As an example, consider this project where I want to gradually reveal a circle.
Below are screen shots from both Motion 4 and Motion 5 of the same project, at frame 10:
As you can see, Motion 4 gradually unveils the masked shape (a circle), but Motion 5 doesn't.
I could get around this particular case by adding a write on behaviour to the circle shape. BUt this does not work as a general masking technique in M5, which is a bit sad.
Anyone care to shed some light?
BR;
::e

Hi Chand+Mark
Chandosx wrote:
You could get away with it by setting the blending mode to stencil alpha, but that won't work in every situation.  The other thing you could do, is place the layer that's the source of the mask at the very bottom of everything, so it's not shown, and leave the layer turned on.  Then all should work sorta the same.  Quirky.
I'm not really familiar with what stencil alpha does, so I can't comment on that.
But the bottom layer option won't be any good if you want partially transparent output.
It *will* show unless you have some layer covering it up, which would be purely coincidential
UNLESS you use one very very special color for the mask source shape, and send the whole shebang through the keyer to get your alpha channel proper
Chandosx wrote:
And one other way I just tested, that works for sure, is using keyframes on the source shape's "First Point Offset"(or last ).
Hey, a self-made "write-on" for the mask source shape?
Well, it works in M4 - I'll confirm with M5 tomorrow.
Thanks for all your efforts to figure this out!
I still certainly consider this a bug and would expect this to be fixed.
How can I go ahead and report this a bug to Apple, are they monitoring this forum?
Cheers!
::e

Similar Messages

  • Performance issues with Motion (position, scale, rotate) and GTX 590

    I'm experiencing performance issues with my Premiere Pro CC when I scale, position or rotate a clip in the program monitor.
    I have no performance issues with playback! It's only, when i move something with the mouse or by changing the x,y-values of Position in the Motion-Dialog in video effects.
    Premiere then lags terribly and updates the program monitor only about once per second - this makes it very difficult and cumbersome to work and position things.
    On a second Premiere installation on my laptop, performance is fine and fluid - allthough it doesn't have GPU support and is a much slower computer.
    I'm pretty sure this has somehow to do with my graphic card, which is a Nvidia GTX 590.
    I was told by the support, that it is actually a dual graphic card, which is not supported/liked by Premiere.
    The thing is, until the latest Premiere update, I did not have performance issues at all with this card.
    I also read on the forum that others with the GTX 590 did not experience any problems with it
    So where does this come from?
    There is no change in performance whether or not I activate Mercury Playback Engine GPU acceleration.
    I also tried deactivating one of the 2 gpus, but there also was no change.
    Does anyone else know this problem and has anyone a solution?
    I'm running Premiere CC on a Win 7 64bit engine, Nvidia GTX 590, latest driver (of today),

    I am suffering from the same phenomenon since I updated just before christmas, I think.
    I am hardly able to do scaling, rotating and translating in the program monitor itslef - whil motion has been highlighted in teh effect controls.
    In the effect controls I can scale, rotate etc however.
    Also I have noticed there is a yellow box with handles in teh program monitor. I remember it was white before.
    I cannot figure out what to change in my preferences. What has happened?
    best,
    Hans Wessels
    Premiere CC
    Mac Pro OSX 10.7.5
    16 GB 1066 MHz DD3
    2 X NVIDIA GeForce GT 120 512 MB

  • Issues with Motion in Using Compressor for a PAL DVD

    I am new to DVD Studio Pro and Compressor and am trying to create a DVD of a 50 minute PAL project that I made using FCP. I have found a couple tutorials on how to export my project using compressor to be compatible with DSP via pre sets (DVD: Best Quality 4:3) and actually manipulating the controls myself. I have found in using both techniques that during any scene with motion, the edges of the moving actor become blurred and grainy. The tutorials that I checked out I assume (since they were from the US) were for NTSC projects, is there any other considerations that I should make in compressing a PAL project, which might contribute to this graininess? Any ideas?
    Any help would be much appreciated. I have included my settings from Compressor below.
    Thanks.
    Name: MPEG-2 6.2Mbps 2-pass 4:3
    Description: Fits up to 90 minutes of video with Dolby Digital audio at 192 Kbps or 60 minutes with AIFF audio on a DVD-5
    File Extension: m2v
    Estimated file size: 273.48 MB
    Type: MPEG-2 video elementary stream
    Video Encoder
    Format: M2V
    Width: 720
    Height: 576
    Pixel aspect ratio: PAL CCIR 601
    Crop: None
    Frame rate: 25
    Frame Controls: Off
    Aspect ratio: 4:3
    Field dominance: Bottom first
    Average data rate: 6.2 (Mbps)
    2 Pass VBR enabled
    Maximum data rate: 7.7 (Mbps)
    High quality
    Best motion estimation
    Closed GOP Size: 12, Structure: IBBP
    DVD Studio Pro meta-data enabled

    The general concepts are the same in terms of maintaining quality throughout the work process in terms of Codecs, exports etc.
    As to the motion areas, compression markers in FCP can help in problem areas. What you should do is grab some of the problems sections and drop markers in there and encode them. Some of the frame controls can help, depending on source footage. What was the original material and cpautred/edited? Sometimes things in there can also give quality hits.
    Lastly some things (like real black outfits on light backgrounds) can cause some edging issues which can take some work to clean up as much as possible...

  • Rendering/playback issues with Motion

    Greetings!
    I am relatively new on these forums, and I just posted this same question/situation under "Mac Pro" as I am not sure if this is a software or hardware issue.
    I'm working on a video project, and trying to apply Digital Juice's R2G Motion templates to my title sequence. The problem is the rendering of the template in Motion is awful. It strains to play, it's painfully slow, and it's impossible to really get an idea of what is going on. Even if telling Motion to take the rendering from "Full" to "Half", rebooting my Mac, clearing PRAM, and having Motion be the only running application, it makes no difference. Playback is practically at a stand still.
    The confusion comes when I tried to run the same template in Motion at my work computer. Playback, while still slow, is manageable. It will at least play back the template at half speed "smoothly" enough that I have a good idea what is happening. And in this test, I was running FCP, Word, TweetDeck, and Juicer at the same time. With all that, Motion on my work computer played the template back at a better pace than my home computer.
    Here's the breakdown on the computer's hardware:
    WORK COMPUTER:
    2.66 GHz Quad-Core (4 core)
    8GB RAM
    ATI Radeon HD 4870
    HOME COMPUTER:
    2 3.2 GHz Quad-Core (8 core)
    8GB RAM
    ATI Radeon HD 2600 (2 cards)
    Both are running Mac Snow Leopard 10.6.7 and Motion 4. And the template is playing better on my Work Computer. Hence, my confusion.
    If anyone can give me a good direction to follow, a workaround, or some sort of solution (the only thing I've found suggested is a new video card), I would be eternally grateful. (And no, doing the job on my work won't fly. LOL)
    Thanks, everyone. I look forward to the replies.
    Tee Morris
    Struggling with Motion, at present

    Welcome to the family.
    Your 4870 card is superior to the 2600.
    I have no idea what Digital Juice is up to these days but their stock video packages come with h-u-g-e media files that must be rendered using their Juicer app.
    Templates often include base media that is ultra-high rez to accommodate any format and the components must be rendered out to your format BEFORE you start working.
    bogiesan

  • Issue with Motion Menu looping in CS6

    Greetings all!  I have been troubled with a recurring issue in a project I've been working on for a while where my Main Menu (the only one I have with a moving background) will not loop correctly.  I am not an Encore veteran so there may be something simple that I'm doing wrong and just haven't caught yet... or perhaps this is some weird bug, I'm not sure.  Here is what I've set up and the problem I'm having:
    My Main Menu has 4 buttons: one goes to a primary video and the others are 3 submenus... all submenus work fine and can link back to the Main Menu without issue and when the Main Menu first loads, it also works fine with the video in the background playing normally.  The primary video linked from the Main Menu also returns to the Main Menu as its End Action.  My problem arises when the Main Menu is allowed to reach the end of its video and loops back to the beginning again before navigating away to another part of the disc.  When it loops, the background video plays all the way through a second time like you would expect, however the menu is no longer interactive and no buttons can be pressed (the highlight also disappears on the second loop).  Following the conclusion of the second loop, the Main Menu doesn't loop a third time but rather jumps randomly to about chapter 2 or 3 of the primary video!  I have definitely not set it to do this.  I was not sure what to do about the End Action of the Main Menu itself, as the "Motion" tab of the Menu's properties has a drop-down for looping the motion part... thus so far I have the End Action set to "Main Menu: Default".  The motion background video is 45 seconds long and I have tried messing with the loop settings under the Motion tab, but it hasn't seemed to make much of a difference, it still breaks.  Just for clarification, this is an error which I didn't notice right away because it appears to loop through the menu a second time normally, but the error occurs after the first play of the motion menu.  Also, it happens both in preview and when I burn it to a disc.
    If anyone else has experienced an issue like this or happens to know what I did wrong, please let me know so I can finally get this DVD project over with!  I would be most grateful!  Thank you!

    Project corruption most frequently occurs because one or more changes are made and Encore gets "confused." But we rarely know why some such changes behave correctly and others do not.
    If you must change an asset use a different name, never ever simply overwrite.
    This just may be the issue then... Using Adobe's fancy "Dynamic Link" thingy I did edit a few assets after importing them into Encore.  Sadly, I think Encore is definitely confused by this as now every time I open my project it prompts me to re-import one of the assets because it detected "changes" when in fact I have not changed it more than once and it is just trying to re-import the same thing over and over.  I really wish I'd known to take these measure beforehand as I'm not sure how long it'll take now to rebuild the project completely, but I suppose I have no other choice if I want a working menu...  wish me luck!
    I'd like to note, however, that the asset that it always prompts me for is NOT related in any way to the Main Menu that is causing problems.  It's an asset linked to from a different submenu.  Also, I had planned everything out first, but as you might expect, little hiccups appear along the way and things need to be tweaked to have them work the way you want.  Or maybe you think to add something later that you hadn't thought of before, it actually happens pretty often.
    Still, it seems like Adobe is trying to promote the easy manipulation of assets within projects with the Dynamic Link feature.  I really hate how these softwares do not even work the way they should... and yet Adobe charges people insane amounts of money for them.
    Is there any good DVD authoring software that isn't so temperamental?  I apologize if this isn't the appropriate place to ask... just curious for the sake of my own sanity.

  • Some very weird issue with Motion tween

    Hello, guys! I confronted some kind of weird problem. I uploaded it in fla, https://www.dropbox.com/s/u9bkjiokk51m1o3/landscape_START.fla. Soo, about the problem, flowers in layers 8,9,10 act wrong, when im trying to apply motion tween, they move from their current position right to the hell another one, and i can't understand why. Can somebody explain me what the matter? Because the  rest of objects in another layers make it right, when i use motion tween. Oh, and btw, when you make zoom like 50% and less, u can see the workplace consist of gray square in dark gray square, again, wtf? When i make sizes in properties panel larger, it just goes crazy.

    Emm, i meant that you should make motion tween by yourself to see that problem with flowers on layers 8,9,10. You just selecting any frame you want, then applying motion tween on flower on layer 8,9 or 10 and then puff, its like screwed up. Well, i tried to copy and replace this flower movie clips, but its always the same. For example, the rest of objects, when you apply motion tween on em, dont changing their location...

  • Anyone else haveing issues where Motion 5 performs worse than Motion 4?

    I'm having an issue where even simple particle emitters playback slowly.  I can create the same simple effect in 4 and it plays back in real time.
    I even saved a test file in 4 (which ran real time), and when I open it in 5 it plays back slower.  What gives?

    I´m having a strange issues with Motion 5 performance:
    In my iMac 2010 (i3 @ 3,06 ghz, Radeon 4670 256 mb and 8 gb) Motion 5 is about 20-25% faster than Motion 4.
    For example, when rendering the PulseHD Open Motion 4 takes 2:30 mins and Motion 5 takes 2:00 mins.
    The strange results come from my Macbook Pro 2010 (i5 @ 2,4 ghz, Geforce GT 330m and 8 gb also):
    With the same template this computer takes 3:20 mins in Motion 4 and about 6:30 mins in Motion 5!!!! So near the double.
    Even more strange: if I make a ram preview in Motion 5 with this same template and settings that I used in the final render it only takes 2:51 mins and Motion 4 is slower, because it takes 3:25 mins!!!!!!
    I forgot to say that in all the cases the render quality was set to normal and motion blur was turned on with 8 samples.
    So, it´s clear that Motion 5 needs an update as does FCP X, because in my computers it crashes a lot.

  • What happened to Final Cut's integration with Motion??  Renders are hosed..

    So is it just me? I have a HUGE project (1.5 hour bio/documentary) that is crashing Final Cut every time it tries to render or export. I was getting an error that said the crash could have been possible to a "ProGraphics plug-in." I can't locate any plug-in anywhere on any drive that's associated with "ProGraphics" at all. From what I gather it's something to do with Motion integration, causing problems with renders. Basically, I've used many Motion effects within my Final Cut sequences. They're nested everywhere, and were rendering just fine a few days ago (although I was still having issues with exporting). So basically I either need to wait for a fix, or go back and re-cut without the Motion graphics. Uggh. Disgusted and in need of a patch (or a drink).
    My versions of all software are current, as is my operating system. I've done all updates and patches (I'm a versiontracker geek so I keep up with this stuff). I've deleted preferences, dumped all render files (that's when I figured out the rendering issues with Motion), rebuilt permissions, created a clean User Account, etc. I've done hardware tests on the drives and RAM. I'm out of options.
    Can anyone from Apple confirm that there are indeed issues with this, just to reassure me that I'm not going insane?
    Thanks.
    Scott Dickens
    Richmond, VA

    Try searching the forums for that ProGraphics term., might find something that helps.
    Chances are you lost or damaged a system-level hook in one of your recent efforts to stay up to date. Most of us would not update QT or the pro apps until big projects are out the door or securely backed up. We often print to tape or export a completely flattened movie before running major upgrades to the Mac OS.
    However, I just popped open an old FCP project that has some Motion work in it from about 8 months ago. Everything hooked right up and some tests rendered okay.
    Huge projects with delicately nested elements need careful workflow decisions. I try to pre-render or use proxies where ever possible. Hard lessons learned over a decode of After Effects work. Hope you get better advice but searching for the ProGraphics error term will get you results faster.
    bogiesan

  • Drawing artifacts with motion under a gradient mask

    Hello,
    I am having an issue with using a motion under a gradient mask and was hoping someone might have a solution. I have a  transparent png bubble in movie clips that are being randomly sized and  animation started using code. The design has a reflection and I am  using a gradient mask for the effect. The issue is when the bubbles  animate they are causing drawing artifacts. Please see the attached  screen shot or you can see the swf here - http://archetypeworks.com/test/tm/. Below is the code I am using to set the mask. Any help or  suggestions are appreciated.
    Code:
    bottomMask.cacheAsBitmap = true;
    beaker_bottom.cacheAsBitmap = true;
    beaker_bottom.mask = bottomMask;
    Thank you,
    Ococ

    Thank you for the suggestion, but that did not work. I also tried breaking apart the png, using the magic wand to select and delete the transparent areas. Still getting the same issue.

  • Hi, i am having an issue with a basic motion scroll effect.  I already watched and read every tutorial out there regarding this topic and even tried the adobe chat support, but the guy on the other end of the line disconnected me-, probably he didn't unde

    Hi, i am having an issue with a basic motion scroll effect.
    I already watched and read every tutorial out there regarding this topic and even tried the adobe chat support, but the guy on the other end of the line disconnected me…, probably he didn't understand what i wanted from him because english is not my native language, so a will try to be very, very clear about this one..
    please note, that i am new to muse, this is my first project ever.
    my idea is as following:
    when the customer comes to our companies site, he just sees our logo on a white Background. the logo consists of, say, four elements. when the customer scrolls down, the logo starts to disassamble: first the first part of the logo flies out the left side of the site, then the second part of the logo vanishes down, then the third part of the logo flies to the right, then the fourth part of the logo flies to the top and out of the customers view. given what i have seen, it is possible to do that….
    so…..
    now i have the four parts of my logo imported as png files into muse and assembled them in design view to build our companies logo. I select every one of the four parts and go into the scroll effects tab left beside the layers tab. first i enter the same values for every one of the four parts: initial motion: 0x and 0x again for the left and right motion; key position ( t-handle) : 0px; final motion: 0x and 0x again for the left and right value.
    now i hit "preview".: the logo is "pinned" at the correct position, i can scroll but the logo stays where it is. so far so good….
    now i select all the four elements again and go to the scroll effecs tab. at "final motion", i click the down arrows and enter 1x. I hit Preview…
    when i am scrolling down the WHOLE logo goes down…. so far so good.
    NOW i want the first part of the logo to go down, THEN the second part to go left, THEN the third part to go up, THEN the fourth part to go right.
    so i select ONLY the first part, go to the scroll motion tab, at "final motion" i click the left arrows, then i enter 1x.( the up-down value, i set to 0 again).. i hit Preview…
    the first part of the logo goes left as soon as i start scrolling, the other three parts still go down at the same time…
    NOW i want the second part of the logo to start moving, when the first part has left the scene, not at the same time as the first part.
    SO I SELECT THE SECOND PART AND DRAG ITS T-HANDLE (KEY POSITION) DOWN TO, LETS SAY, 200PX. SO IT STARTS MOVING ONLY AFTER THE CUSTOMER HAS REACHED THAT POINT, RIGHT?
    BUT WHEN I PREVIEW THAT ****, THE LOGO IS NOT TOGETHER ANYMORE, THE SECOND PART IS FLOATING ANYWHERE ELSE BUT WHERE IT SHOULD BE…..WTFF????
    short: when i move the t handle, the initial position of the object changes. thats what i said to the adobe employee, but he said, that thats the expected behavior….
    but if thats so, how can i have my four parts correctly together, so they form my logo, but with different t handles, so that they all start to move at different times??
    Pleeease help me, i am dying of frustration here…..:( that behavior cant be right, right?
    Thanks so much to everyone who actually reads this post and tries to help…….
    All the best,
    Niki Lapan

    Thank you so much for helping,
    But i really wonder how you did that. did you always switch between design view and preview view, then change the key position for 2px then switch back, to align the four letters? because i imagine that can get really frustrating, if you have a logo consisting of 58 parts instead of 4!:)
    Anyway thank you very much for your time and effort!!!!

  • Issue with Clipping Mask when scrubbing timeline

    Has anyone encountered an issue with editing a clipping mask or repositioning it on the timeline only to see that nothing moves on the timeline when scrubbing the playhead?
    This has occurred multiple times on different Edge Animate projects.
    So far this has happened on SVGs, pngs, basic shapes, etc.
    I posted a video in my adobe cc folder to view as a reference.
    I'm using OS X 10.10.3 and Edge Animate 2014.1.1

    I right click on the clip in Timeline, choose Effects Mask > Apply
    The rectangular mask appears on the screen, I drag one corner in to make it smaller - what the exact dimensions are I know not. The logo I need covered happens to be almost at the exact center of the screen.
    I choose the EDIT Tab > Brightness/Contrast > Set the levels so the mask is perfectly white (thus, covering up the logo) > Apply > Done
    The preview works. When I output as AVI, MOV, MPG, MP4, etc., the mask that I placed over the logo has now moved either above where I originally placed it or above and to the left.
    I have no idea how to answer the second part of your question.

  • Weird issue with Bridge CC and vector masked TIFF files

    For some reason in Bridge CC my vector masked transparent backgrounds in my tiff files are showing.  I didnt have this issue with CS6.  only way to fix it is for me to flatten my image and resave it as a tiff without the mask.  Any option i need to click on?

    We don't even know what platform (Mac or Win) or version of the OS you are running.
    Also:  Are you aware that the latest version of Photoshop is not "CC" but CC2014v14.2.2 ?
    BOILERPLATE TEXT:
    Note that this is boilerplate text.
    If you give complete and detailed information about your setup and the issue at hand,
    such as your platform (Mac or Win),
    exact versions of your OS, of Photoshop (not just "CS6", but something like CS6v.13.0.6) and of Bridge,
    your settings in Photoshop > Preference > Performance
    the type of file you were working on,
    machine specs, such as total installed RAM, scratch file HDs, total available HD space, video card specs, including total VRAM installed,
    what troubleshooting steps you have taken so far,
    what error message(s) you receive,
    if having issues opening raw files also the exact camera make and model that generated them,
    if you're having printing issues, indicate the exact make and model of your printer, paper size, image dimensions in pixels (so many pixels wide by so many pixels high). if going through a RIP, specify that too.
    A screen shot of your settings or of the image could be very helpful too,
    etc.,
    someone may be able to help you (not necessarily this poster, who is not a Windows user).
    Please read this FAQ for advice on how to ask your questions correctly for quicker and better answers:
    http://forums.adobe.com/thread/419981?tstart=0
    Thanks!

  • Motion having issues with layered PSD files.  Adds more to images

    Motion is distorting my layered PSD files in a way that I can't seem to figure out how to fix. Here are two examples of what I'm talking about:
    http://www.coyopa.com/motion_problem.jpg
    http://www.coyopa.com/motion_problem2.jpg
    There are two PSD images. The person is one layer and the background is the other. As you can see with the background layer turned on, the image is stretched or smeared. When the background layer is turned off, elements from the distorted background are appearing, such as the extended black shoulder or the line coming out of the head.
    The images I started with with were high res scans saved as grayscale TIFs. I converted them to PSD and switched the color space to RGB. I did my work in Photoshop and imported them into Motion which is when the problems began.
    I suspect the problem may be my graphics card which is a NVIDIA GeForce 7300 GT. I am running Motion 3.0.2 and Leopard 10.5.8. My Motion project settings are XDCAM EX 1080p30.

    I'm having a similar problem, but changing the resolution to the exact max of 2896x2896 doesn't work for me...and neither does any smaller resolution for some reason.
    Today, my layered PSD file is at least not experiencing the crazy tile-effect you included in your posted images, but it is now:
    1) always converting the top layer of the PSD file to a flattened image of the whole file.
    2) ignoring/mutating my alpha channel information, as areas that should be transparent and smoothly masked off are now opaque and/or blocky.
    My images are large, but I need to keep them large for dollying in real closely when i fly a camera through the scene. This is not a problem in After Effects, but I also need to do a lot of these 2.5D animations and several need particle/replicator effects... and I just work much much faster in Motion than AE. I don't remember having this problem with Motion 3 at all, but I can't say I've done a scientific comparison (nor do I want to uninstall M4 for M3).
    My system info can be found here:
    [IMG]http://i36.tinypic.com/2n744di.jpg[/IMG]
    [IMG]http://i33.tinypic.com/28cks42.jpg[/IMG]
    Original PSD file info:
    [IMG]http://i37.tinypic.com/amdr9v.jpg[/IMG]
    [IMG]http://i36.tinypic.com/99kv1g.jpg[/IMG]
    [IMG]http://i33.tinypic.com/3355w8x.jpg[/IMG]
    [IMG]http://i37.tinypic.com/1zb6y3m.jpg[/IMG]
    [IMG]http://i35.tinypic.com/9i5rhz.jpg[/IMG]
    Motion 4 info:
    [IMG]http://i38.tinypic.com/es40v4.jpg[/IMG]
    [IMG]http://i37.tinypic.com/2crva83.jpg[/IMG]
    [IMG]http://i35.tinypic.com/2e3popz.jpg[/IMG]
    [IMG]http://i37.tinypic.com/jrv8tz.jpg[/IMG]
    [IMG]http://i37.tinypic.com/28rh6hs.jpg[/IMG]
    Any help is appreciated!
    Thank you!

  • HT1551 Just got apple tv - I am having issues with the video similar to the jittery picture that I got with blu-rays before turning off "Auto motion plus".  Now the netflix streams have that same jittery aspect.  Ideas?

    I am having jittery video with shows I stream from netflix.  (I just set up my apple tv).  The problem is similar to what happened when I got my blu-ray player and was solved when I turned off the "Auto motion detect" setting on my television.  Ideas?

    72jen wrote:
    Just tried changing the hertz - i got an error message that my tv may not support 50 Hz.
    5o/60Hz settings may or may not help - the TV motion processing is often the main cause of glitches.
    If you still see them with motion processing off, then it's either the video encoding, poor stream quality (Netflix) or an AppleTV issue.
    There really aren't mny options to play with.
    On the internet using a browser you may be able to log in to Netflix and specify video quality.
    AC

  • Issues with using 3 monitors on 2 external gpu

    Hi,
    I have some issues with configuring Xorg to use 3 monitors. I have 2 external graphic cards (same model, no SLI). Monitors connected to the first gpu are recognized ok but I can't configure my 3rd monitor conencted to the second gpu via HDMI nor DVI.
    1st is recognized as DVI-I-1, 2nd is DP-1 in first card, 3rd monitor is in second card (bus 22:00.0) as DP-1-2 (also tried connecting as DVI-I-2). I can see them in Xorg log but I can't configure my 3rd monitor via kscreen nor xrandr. :-/
    lspci |grep VGA:
    03:00.0 VGA compatible controller: NVIDIA Corporation GF108GL [Quadro 600] (rev a1)
    22:00.0 VGA compatible controller: NVIDIA Corporation GF108GL [Quadro 600] (rev a1)
    xrandr:
    Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 8192 x 8192
    DVI-I-1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 527mm x 297mm
    1920x1080 60.0*+
    1600x900 60.0
    1280x1024 75.0 60.0
    1152x864 75.0
    1024x768 75.1 60.0
    800x600 75.0 60.3
    640x480 75.0 60.0
    720x400 70.1
    DP-1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 527mm x 297mm
    1920x1080 60.0*+
    1600x900 60.0
    1280x1024 75.0 60.0
    1152x864 75.0
    1024x768 75.1 60.0
    800x600 75.0 60.3
    640x480 75.0 60.0
    720x400 70.1
    Xorg config (autoconfig enable only 2 monitors, I generated config and tried to edit it with no luck, I noticed there is PCI:34:0:0 generated by Xorg so I also tried to change it to 22:0:0, I also tried to add that option "Monitor-<output>" but same result):
    Section "ServerLayout"
    Identifier "X.org Configured"
    #Screen 0 "Screen0" 0 0
    #Screen 1 "Screen1" RightOf "Screen0"
    InputDevice "Mouse0" "CorePointer"
    InputDevice "Keyboard0" "CoreKeyboard"
    EndSection
    Section "Files"
    ModulePath "/usr/lib/xorg/modules"
    FontPath "/usr/share/fonts/misc/"
    FontPath "/usr/share/fonts/TTF/"
    FontPath "/usr/share/fonts/OTF/"
    FontPath "/usr/share/fonts/Type1/"
    FontPath "/usr/share/fonts/100dpi/"
    FontPath "/usr/share/fonts/75dpi/"
    EndSection
    Section "Module"
    Load "glx"
    EndSection
    Section "InputDevice"
    Identifier "Keyboard0"
    Driver "kbd"
    EndSection
    Section "InputDevice"
    Identifier "Mouse0"
    Driver "mouse"
    Option "Protocol" "auto"
    Option "Device" "/dev/input/mice"
    Option "ZAxisMapping" "4 5 6 7"
    EndSection
    Section "Monitor"
    Identifier "Monitor0"
    VendorName "DELL"
    Option "Monitor-DVI-I-1" "DVI-I-1"
    EndSection
    Section "Monitor"
    Identifier "Monitor1"
    VendorName "DELL"
    Option "Monitor-DP-1" "DP-1"
    EndSection
    Section "Monitor"
    Identifier "Monitor2"
    VendorName "DELL"
    Option "Monitor-DP-1-2" "DP-1-2"
    EndSection
    Section "Device"
    Identifier "Card0"
    Driver "nouveau"
    BusID "PCI:3:0:0"
    Option "Monitor-DVI-I-1"
    Option "Monitor-DP-1"
    EndSection
    Section "Device"
    Identifier "Card1"
    Driver "nouveau"
    BusID "PCI:34:0:0"
    Option "Monitor-DP-1-2"
    EndSection
    Xorg log (I can see that monitor at time 1767.316):
    [ 1766.959]
    X.Org X Server 1.14.5
    Release Date: 2013-12-12
    [ 1766.960] X Protocol Version 11, Revision 0
    [ 1766.960] Build Operating System: Linux 3.12.5-1-ARCH x86_64
    [ 1766.960] Current Operating System: Linux CZ09DT1XM5002 3.12.5-1-ARCH #1 SMP PREEMPT Thu Dec 12 12:57:31 CET 2013 x86_64
    [ 1766.960] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=e2c593e5-b0f4-4c74-84fd-5a88db345ca4 rw quiet
    [ 1766.961] Build Date: 13 December 2013 03:11:42PM
    [ 1766.962]
    [ 1766.962] Current version of pixman: 0.32.4
    [ 1766.963] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 1766.963] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 1766.965] (==) Log file: "/var/log/Xorg.1.log", Time: Thu Jan 2 12:43:56 2014
    [ 1766.965] (++) Using config file: "/etc/X11/xorg.conf.d/20-multimonitor.conf"
    [ 1766.966] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 1766.966] (==) ServerLayout "X.org Configured"
    [ 1766.966] (==) No screen section available. Using defaults.
    [ 1766.966] (**) |-->Screen "Default Screen Section" (0)
    [ 1766.966] (**) | |-->Monitor "<default monitor>"
    [ 1766.966] (==) No device specified for screen "Default Screen Section".
    Using the first device section listed.
    [ 1766.966] (**) | |-->Device "Card0"
    [ 1766.966] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    [ 1766.966] (**) |-->Input Device "Mouse0"
    [ 1766.966] (**) |-->Input Device "Keyboard0"
    [ 1766.966] (==) Automatically adding devices
    [ 1766.966] (==) Automatically enabling devices
    [ 1766.966] (==) Automatically adding GPU devices
    [ 1766.966] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [ 1766.966] Entry deleted from font path.
    [ 1766.966] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
    [ 1766.966] Entry deleted from font path.
    [ 1766.966] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 1766.966] Entry deleted from font path.
    [ 1766.966] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 1766.967] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 1766.967] Entry deleted from font path.
    [ 1766.967] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 1766.967] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [ 1766.967] Entry deleted from font path.
    [ 1766.967] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
    [ 1766.967] Entry deleted from font path.
    [ 1766.967] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 1766.967] Entry deleted from font path.
    [ 1766.967] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 1766.967] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 1766.967] Entry deleted from font path.
    [ 1766.967] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 1766.967] (**) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/
    [ 1766.967] (**) ModulePath set to "/usr/lib/xorg/modules"
    [ 1766.967] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
    [ 1766.967] (WW) Disabling Mouse0
    [ 1766.967] (WW) Disabling Keyboard0
    [ 1766.967] (II) Loader magic: 0x7fec20
    [ 1766.967] (II) Module ABI versions:
    [ 1766.967] X.Org ANSI C Emulation: 0.4
    [ 1766.967] X.Org Video Driver: 14.1
    [ 1766.967] X.Org XInput driver : 19.1
    [ 1766.967] X.Org Server Extension : 7.0
    [ 1766.967] (II) xfree86: Adding drm device (/dev/dri/card0)
    [ 1766.967] (II) xfree86: Adding drm device (/dev/dri/card1)
    [ 1767.169] (--) PCI:*(0:3:0:0) 10de:0df8:10de:0835 rev 161, Mem @ 0xc6000000/16777216, 0xc8000000/134217728, 0xd0000000/33554432, I/O @ 0x00007000/128, BIOS @ 0x????????/524288
    [ 1767.169] (--) PCI: (0:34:0:0) 10de:0df8:10de:0835 rev 161, Mem @ 0xfa000000/16777216, 0xf0000000/134217728, 0xf8000000/33554432, I/O @ 0x0000f000/128, BIOS @ 0x????????/524288
    [ 1767.169] Initializing built-in extension Generic Event Extension
    [ 1767.170] Initializing built-in extension SHAPE
    [ 1767.170] Initializing built-in extension MIT-SHM
    [ 1767.170] Initializing built-in extension XInputExtension
    [ 1767.171] Initializing built-in extension XTEST
    [ 1767.171] Initializing built-in extension BIG-REQUESTS
    [ 1767.172] Initializing built-in extension SYNC
    [ 1767.172] Initializing built-in extension XKEYBOARD
    [ 1767.172] Initializing built-in extension XC-MISC
    [ 1767.173] Initializing built-in extension SECURITY
    [ 1767.173] Initializing built-in extension XINERAMA
    [ 1767.174] Initializing built-in extension XFIXES
    [ 1767.174] Initializing built-in extension RENDER
    [ 1767.174] Initializing built-in extension RANDR
    [ 1767.175] Initializing built-in extension COMPOSITE
    [ 1767.175] Initializing built-in extension DAMAGE
    [ 1767.175] Initializing built-in extension MIT-SCREEN-SAVER
    [ 1767.176] Initializing built-in extension DOUBLE-BUFFER
    [ 1767.176] Initializing built-in extension RECORD
    [ 1767.176] Initializing built-in extension DPMS
    [ 1767.177] Initializing built-in extension X-Resource
    [ 1767.177] Initializing built-in extension XVideo
    [ 1767.177] Initializing built-in extension XVideo-MotionCompensation
    [ 1767.178] Initializing built-in extension XFree86-VidModeExtension
    [ 1767.178] Initializing built-in extension XFree86-DGA
    [ 1767.178] Initializing built-in extension XFree86-DRI
    [ 1767.179] Initializing built-in extension DRI2
    [ 1767.179] (II) "glx" will be loaded. This was enabled by default and also specified in the config file.
    [ 1767.179] (II) LoadModule: "glx"
    [ 1767.179] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 1767.179] (II) Module glx: vendor="X.Org Foundation"
    [ 1767.179] compiled for 1.14.5, module version = 1.0.0
    [ 1767.179] ABI class: X.Org Server Extension, version 7.0
    [ 1767.179] (==) AIGLX enabled
    [ 1767.180] Loading extension GLX
    [ 1767.180] (II) LoadModule: "nouveau"
    [ 1767.180] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
    [ 1767.180] (II) Module nouveau: vendor="X.Org Foundation"
    [ 1767.180] compiled for 1.14.4, module version = 1.0.10
    [ 1767.180] Module class: X.Org Video Driver
    [ 1767.180] ABI class: X.Org Video Driver, version 14.1
    [ 1767.180] (II) NOUVEAU driver
    [ 1767.180] (II) NOUVEAU driver for NVIDIA chipset families :
    [ 1767.180] RIVA TNT (NV04)
    [ 1767.180] RIVA TNT2 (NV05)
    [ 1767.180] GeForce 256 (NV10)
    [ 1767.180] GeForce 2 (NV11, NV15)
    [ 1767.180] GeForce 4MX (NV17, NV18)
    [ 1767.180] GeForce 3 (NV20)
    [ 1767.180] GeForce 4Ti (NV25, NV28)
    [ 1767.180] GeForce FX (NV3x)
    [ 1767.180] GeForce 6 (NV4x)
    [ 1767.180] GeForce 7 (G7x)
    [ 1767.180] GeForce 8 (G8x)
    [ 1767.180] GeForce GTX 200 (NVA0)
    [ 1767.180] GeForce GTX 400 (NVC0)
    [ 1767.180] (--) using VT number 3
    [ 1767.182] (II) [drm] nouveau interface version: 1.1.1
    [ 1767.183] (II) [drm] nouveau interface version: 1.1.1
    [ 1767.183] (II) Loading sub module "dri2"
    [ 1767.183] (II) LoadModule: "dri2"
    [ 1767.183] (II) Module "dri2" already built-in
    [ 1767.183] (--) NOUVEAU(0): Chipset: "NVIDIA NVC1"
    [ 1767.183] (II) NOUVEAU(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
    [ 1767.183] (==) NOUVEAU(0): Depth 24, (--) framebuffer bpp 32
    [ 1767.183] (==) NOUVEAU(0): RGB weight 888
    [ 1767.183] (==) NOUVEAU(0): Default visual is TrueColor
    [ 1767.183] (==) NOUVEAU(0): Using HW cursor
    [ 1767.183] (==) NOUVEAU(0): GLX sync to VBlank disabled.
    [ 1767.183] (==) NOUVEAU(0): Page flipping enabled
    [ 1767.183] (==) NOUVEAU(0): Swap limit set to 2 [Max allowed 2]
    [ 1767.222] (II) NOUVEAU(0): Output DVI-I-1 has no monitor section
    [ 1767.230] (II) NOUVEAU(0): Output DP-1 has no monitor section
    [ 1767.265] (II) NOUVEAU(0): EDID for output DVI-I-1
    [ 1767.265] (II) NOUVEAU(0): Manufacturer: DEL Model: a09b Serial#: 827608652
    [ 1767.265] (II) NOUVEAU(0): Year: 2013 Week: 41
    [ 1767.265] (II) NOUVEAU(0): EDID Version: 1.3
    [ 1767.265] (II) NOUVEAU(0): Digital Display Input
    [ 1767.265] (II) NOUVEAU(0): Max Image Size [cm]: horiz.: 53 vert.: 30
    [ 1767.265] (II) NOUVEAU(0): Gamma: 2.20
    [ 1767.265] (II) NOUVEAU(0): DPMS capabilities: StandBy Suspend Off
    [ 1767.265] (II) NOUVEAU(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
    [ 1767.265] (II) NOUVEAU(0): First detailed timing is preferred mode
    [ 1767.265] (II) NOUVEAU(0): redX: 0.650 redY: 0.338 greenX: 0.320 greenY: 0.613
    [ 1767.265] (II) NOUVEAU(0): blueX: 0.154 blueY: 0.061 whiteX: 0.313 whiteY: 0.329
    [ 1767.265] (II) NOUVEAU(0): Supported established timings:
    [ 1767.265] (II) NOUVEAU(0): 720x400@70Hz
    [ 1767.265] (II) NOUVEAU(0): 640x480@60Hz
    [ 1767.265] (II) NOUVEAU(0): 640x480@75Hz
    [ 1767.265] (II) NOUVEAU(0): 800x600@60Hz
    [ 1767.265] (II) NOUVEAU(0): 800x600@75Hz
    [ 1767.265] (II) NOUVEAU(0): 1024x768@60Hz
    [ 1767.265] (II) NOUVEAU(0): 1024x768@75Hz
    [ 1767.265] (II) NOUVEAU(0): 1280x1024@75Hz
    [ 1767.265] (II) NOUVEAU(0): Manufacturer's mask: 0
    [ 1767.265] (II) NOUVEAU(0): Supported standard timings:
    [ 1767.265] (II) NOUVEAU(0): #0: hsize: 1152 vsize 864 refresh: 75 vid: 20337
    [ 1767.265] (II) NOUVEAU(0): #1: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
    [ 1767.265] (II) NOUVEAU(0): #2: hsize: 1600 vsize 900 refresh: 60 vid: 49321
    [ 1767.265] (II) NOUVEAU(0): #3: hsize: 1920 vsize 1080 refresh: 60 vid: 49361
    [ 1767.265] (II) NOUVEAU(0): Supported detailed timing:
    [ 1767.265] (II) NOUVEAU(0): clock: 148.5 MHz Image Size: 527 x 297 mm
    [ 1767.265] (II) NOUVEAU(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
    [ 1767.265] (II) NOUVEAU(0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0
    [ 1767.265] (II) NOUVEAU(0): Serial No: 36WJX3A91TNL
    [ 1767.265] (II) NOUVEAU(0): Monitor name: DELL P2414H
    [ 1767.265] (II) NOUVEAU(0): Ranges: V min: 56 V max: 76 Hz, H min: 30 H max: 83 kHz, PixClock max 175 MHz
    [ 1767.265] (II) NOUVEAU(0): EDID (in hex):
    [ 1767.265] (II) NOUVEAU(0): 00ffffffffffff0010ac9ba04c4e5431
    [ 1767.265] (II) NOUVEAU(0): 2917010380351e78eaa0a5a656529d27
    [ 1767.265] (II) NOUVEAU(0): 0f5054a54b00714f8180a9c0d1c00101
    [ 1767.265] (II) NOUVEAU(0): 010101010101023a801871382d40582c
    [ 1767.265] (II) NOUVEAU(0): 45000f292100001e000000ff00333657
    [ 1767.265] (II) NOUVEAU(0): 4a5833413931544e4c0a000000fc0044
    [ 1767.265] (II) NOUVEAU(0): 454c4c205032343134480a20000000fd
    [ 1767.265] (II) NOUVEAU(0): 00384c1e5311000a20202020202000c2
    [ 1767.265] (II) NOUVEAU(0): Printing probed modes for output DVI-I-1
    [ 1767.265] (II) NOUVEAU(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP)
    [ 1767.265] (II) NOUVEAU(0): Modeline "1600x900"x60.0 118.96 1600 1696 1864 2128 900 901 904 932 -hsync +vsync (55.9 kHz)
    [ 1767.265] (II) NOUVEAU(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 1767.265] (II) NOUVEAU(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [ 1767.265] (II) NOUVEAU(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 1767.265] (II) NOUVEAU(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
    [ 1767.265] (II) NOUVEAU(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 1767.265] (II) NOUVEAU(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 1767.265] (II) NOUVEAU(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 1767.265] (II) NOUVEAU(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 1767.265] (II) NOUVEAU(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 1767.265] (II) NOUVEAU(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 1767.273] (II) NOUVEAU(0): EDID for output DP-1
    [ 1767.273] (II) NOUVEAU(0): Manufacturer: DEL Model: a09a Serial#: 844123724
    [ 1767.273] (II) NOUVEAU(0): Year: 2013 Week: 41
    [ 1767.273] (II) NOUVEAU(0): EDID Version: 1.4
    [ 1767.273] (II) NOUVEAU(0): Digital Display Input
    [ 1767.273] (II) NOUVEAU(0): 8 bits per channel
    [ 1767.273] (II) NOUVEAU(0): Digital interface is DisplayPort
    [ 1767.273] (II) NOUVEAU(0): Max Image Size [cm]: horiz.: 53 vert.: 30
    [ 1767.273] (II) NOUVEAU(0): Gamma: 2.20
    [ 1767.273] (II) NOUVEAU(0): DPMS capabilities: Off
    [ 1767.273] (II) NOUVEAU(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4 YCrCb 4:2:2
    [ 1767.273] (II) NOUVEAU(0): First detailed timing is preferred mode
    [ 1767.273] (II) NOUVEAU(0): Preferred mode is native pixel format and refresh rate
    [ 1767.273] (II) NOUVEAU(0): redX: 0.650 redY: 0.338 greenX: 0.320 greenY: 0.613
    [ 1767.273] (II) NOUVEAU(0): blueX: 0.154 blueY: 0.061 whiteX: 0.313 whiteY: 0.329
    [ 1767.273] (II) NOUVEAU(0): Supported established timings:
    [ 1767.273] (II) NOUVEAU(0): 720x400@70Hz
    [ 1767.273] (II) NOUVEAU(0): 640x480@60Hz
    [ 1767.273] (II) NOUVEAU(0): 640x480@75Hz
    [ 1767.273] (II) NOUVEAU(0): 800x600@60Hz
    [ 1767.273] (II) NOUVEAU(0): 800x600@75Hz
    [ 1767.273] (II) NOUVEAU(0): 1024x768@60Hz
    [ 1767.273] (II) NOUVEAU(0): 1024x768@75Hz
    [ 1767.273] (II) NOUVEAU(0): 1280x1024@75Hz
    [ 1767.273] (II) NOUVEAU(0): Manufacturer's mask: 0
    [ 1767.273] (II) NOUVEAU(0): Supported standard timings:
    [ 1767.273] (II) NOUVEAU(0): #0: hsize: 1152 vsize 864 refresh: 75 vid: 20337
    [ 1767.273] (II) NOUVEAU(0): #1: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
    [ 1767.273] (II) NOUVEAU(0): #2: hsize: 1600 vsize 900 refresh: 60 vid: 49321
    [ 1767.273] (II) NOUVEAU(0): #3: hsize: 1920 vsize 1080 refresh: 60 vid: 49361
    [ 1767.273] (II) NOUVEAU(0): Supported detailed timing:
    [ 1767.273] (II) NOUVEAU(0): clock: 148.5 MHz Image Size: 527 x 297 mm
    [ 1767.273] (II) NOUVEAU(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
    [ 1767.273] (II) NOUVEAU(0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0
    [ 1767.273] (II) NOUVEAU(0): Serial No: 36WJX3A92PNL
    [ 1767.273] (II) NOUVEAU(0): Monitor name: DELL P2414H
    [ 1767.273] (II) NOUVEAU(0): Ranges: V min: 56 V max: 76 Hz, H min: 30 H max: 83 kHz, PixClock max 175 MHz
    [ 1767.273] (II) NOUVEAU(0): EDID (in hex):
    [ 1767.273] (II) NOUVEAU(0): 00ffffffffffff0010ac9aa04c4e5032
    [ 1767.273] (II) NOUVEAU(0): 29170104a5351e783aa0a5a656529d27
    [ 1767.273] (II) NOUVEAU(0): 0f5054a54b00714f8180a9c0d1c00101
    [ 1767.273] (II) NOUVEAU(0): 010101010101023a801871382d40582c
    [ 1767.273] (II) NOUVEAU(0): 45000f292100001e000000ff00333657
    [ 1767.273] (II) NOUVEAU(0): 4a5833413932504e4c0a000000fc0044
    [ 1767.273] (II) NOUVEAU(0): 454c4c205032343134480a20000000fd
    [ 1767.273] (II) NOUVEAU(0): 00384c1e5311000a2020202020200053
    [ 1767.273] (II) NOUVEAU(0): Printing probed modes for output DP-1
    [ 1767.273] (II) NOUVEAU(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP)
    [ 1767.273] (II) NOUVEAU(0): Modeline "1600x900"x60.0 118.96 1600 1696 1864 2128 900 901 904 932 -hsync +vsync (55.9 kHz)
    [ 1767.273] (II) NOUVEAU(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 1767.273] (II) NOUVEAU(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [ 1767.273] (II) NOUVEAU(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 1767.273] (II) NOUVEAU(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
    [ 1767.273] (II) NOUVEAU(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 1767.273] (II) NOUVEAU(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 1767.273] (II) NOUVEAU(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 1767.273] (II) NOUVEAU(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 1767.273] (II) NOUVEAU(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 1767.273] (II) NOUVEAU(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 1767.273] (II) NOUVEAU(0): Output DVI-I-1 connected
    [ 1767.273] (II) NOUVEAU(0): Output DP-1 connected
    [ 1767.273] (II) NOUVEAU(0): Using exact sizes for initial modes
    [ 1767.273] (II) NOUVEAU(0): Output DVI-I-1 using initial mode 1920x1080
    [ 1767.273] (II) NOUVEAU(0): Output DP-1 using initial mode 1920x1080
    [ 1767.273] (II) NOUVEAU(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
    [ 1767.274] (--) NOUVEAU(0): Virtual size is 1920x1080 (pitch 0)
    [ 1767.274] (**) NOUVEAU(0): Driver mode "1920x1080": 148.5 MHz (scaled from 0.0 MHz), 67.5 kHz, 60.0 Hz
    [ 1767.274] (II) NOUVEAU(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP)
    [ 1767.274] (**) NOUVEAU(0): Mode "1600x900": 119.0 MHz (scaled from 0.0 MHz), 55.9 kHz, 60.0 Hz
    [ 1767.274] (II) NOUVEAU(0): Modeline "1600x900"x60.0 118.96 1600 1696 1864 2128 900 901 904 932 -hsync +vsync (55.9 kHz)
    [ 1767.274] (**) NOUVEAU(0): Driver mode "1280x1024": 135.0 MHz (scaled from 0.0 MHz), 80.0 kHz, 75.0 Hz
    [ 1767.274] (II) NOUVEAU(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 1767.274] (**) NOUVEAU(0): Driver mode "1280x1024": 108.0 MHz (scaled from 0.0 MHz), 64.0 kHz, 60.0 Hz
    [ 1767.274] (II) NOUVEAU(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [ 1767.274] (**) NOUVEAU(0): Driver mode "1152x864": 108.0 MHz (scaled from 0.0 MHz), 67.5 kHz, 75.0 Hz
    [ 1767.274] (II) NOUVEAU(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 1767.274] (**) NOUVEAU(0): Driver mode "1024x768": 78.8 MHz (scaled from 0.0 MHz), 60.1 kHz, 75.1 Hz
    [ 1767.274] (II) NOUVEAU(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
    [ 1767.274] (**) NOUVEAU(0): Driver mode "1024x768": 65.0 MHz (scaled from 0.0 MHz), 48.4 kHz, 60.0 Hz
    [ 1767.274] (II) NOUVEAU(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 1767.274] (**) NOUVEAU(0): Driver mode "800x600": 49.5 MHz (scaled from 0.0 MHz), 46.9 kHz, 75.0 Hz
    [ 1767.274] (II) NOUVEAU(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 1767.274] (**) NOUVEAU(0): Driver mode "800x600": 40.0 MHz (scaled from 0.0 MHz), 37.9 kHz, 60.3 Hz
    [ 1767.274] (II) NOUVEAU(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 1767.274] (**) NOUVEAU(0): Driver mode "640x480": 31.5 MHz (scaled from 0.0 MHz), 37.5 kHz, 75.0 Hz
    [ 1767.274] (II) NOUVEAU(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 1767.274] (**) NOUVEAU(0): Driver mode "640x480": 25.2 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
    [ 1767.274] (II) NOUVEAU(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 1767.274] (**) NOUVEAU(0): Driver mode "720x400": 28.3 MHz (scaled from 0.0 MHz), 31.5 kHz, 70.1 Hz
    [ 1767.274] (II) NOUVEAU(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 1767.274] (==) NOUVEAU(0): DPI set to (96, 96)
    [ 1767.274] (II) Loading sub module "fb"
    [ 1767.274] (II) LoadModule: "fb"
    [ 1767.274] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 1767.274] (II) Module fb: vendor="X.Org Foundation"
    [ 1767.274] compiled for 1.14.5, module version = 1.0.0
    [ 1767.274] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 1767.274] (II) Loading sub module "exa"
    [ 1767.274] (II) LoadModule: "exa"
    [ 1767.274] (II) Loading /usr/lib/xorg/modules/libexa.so
    [ 1767.274] (II) Module exa: vendor="X.Org Foundation"
    [ 1767.274] compiled for 1.14.5, module version = 2.6.0
    [ 1767.274] ABI class: X.Org Video Driver, version 14.1
    [ 1767.274] (II) Loading sub module "shadowfb"
    [ 1767.274] (II) LoadModule: "shadowfb"
    [ 1767.274] (II) Loading /usr/lib/xorg/modules/libshadowfb.so
    [ 1767.274] (II) Module shadowfb: vendor="X.Org Foundation"
    [ 1767.274] compiled for 1.14.5, module version = 1.0.0
    [ 1767.274] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 1767.274] (II) Loading sub module "dri2"
    [ 1767.274] (II) LoadModule: "dri2"
    [ 1767.274] (II) Module "dri2" already built-in
    [ 1767.274] (--) NOUVEAU(G0): Chipset: "NVIDIA NVC1"
    [ 1767.275] (==) NOUVEAU(G0): Depth 24, (--) framebuffer bpp 32
    [ 1767.275] (==) NOUVEAU(G0): RGB weight 888
    [ 1767.275] (==) NOUVEAU(G0): Default visual is TrueColor
    [ 1767.275] (==) NOUVEAU(G0): Using HW cursor
    [ 1767.275] (==) NOUVEAU(G0): GLX sync to VBlank disabled.
    [ 1767.275] (==) NOUVEAU(G0): Page flipping enabled
    [ 1767.275] (==) NOUVEAU(G0): Swap limit set to 2 [Max allowed 2]
    [ 1767.308] (II) NOUVEAU(G0): Output DVI-I-1-2 has no monitor section
    [ 1767.316] (II) NOUVEAU(G0): Output DP-1-2 has no monitor section
    [ 1767.339] (II) NOUVEAU(G0): EDID for output DVI-I-1-2
    [ 1767.347] (II) NOUVEAU(G0): EDID for output DP-1-2
    [ 1767.347] (II) NOUVEAU(G0): Manufacturer: DEL Model: a09a Serial#: 844124236
    [ 1767.347] (II) NOUVEAU(G0): Year: 2013 Week: 41
    [ 1767.347] (II) NOUVEAU(G0): EDID Version: 1.4
    [ 1767.347] (II) NOUVEAU(G0): Digital Display Input
    [ 1767.347] (II) NOUVEAU(G0): 8 bits per channel
    [ 1767.347] (II) NOUVEAU(G0): Digital interface is DisplayPort
    [ 1767.347] (II) NOUVEAU(G0): Max Image Size [cm]: horiz.: 53 vert.: 30
    [ 1767.347] (II) NOUVEAU(G0): Gamma: 2.20
    [ 1767.347] (II) NOUVEAU(G0): DPMS capabilities: Off
    [ 1767.347] (II) NOUVEAU(G0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4 YCrCb 4:2:2
    [ 1767.347] (II) NOUVEAU(G0): First detailed timing is preferred mode
    [ 1767.347] (II) NOUVEAU(G0): Preferred mode is native pixel format and refresh rate
    [ 1767.347] (II) NOUVEAU(G0): redX: 0.650 redY: 0.338 greenX: 0.320 greenY: 0.613
    [ 1767.347] (II) NOUVEAU(G0): blueX: 0.154 blueY: 0.061 whiteX: 0.313 whiteY: 0.329
    [ 1767.347] (II) NOUVEAU(G0): Supported established timings:
    [ 1767.347] (II) NOUVEAU(G0): 720x400@70Hz
    [ 1767.347] (II) NOUVEAU(G0): 640x480@60Hz
    [ 1767.347] (II) NOUVEAU(G0): 640x480@75Hz
    [ 1767.347] (II) NOUVEAU(G0): 800x600@60Hz
    [ 1767.347] (II) NOUVEAU(G0): 800x600@75Hz
    [ 1767.347] (II) NOUVEAU(G0): 1024x768@60Hz
    [ 1767.347] (II) NOUVEAU(G0): 1024x768@75Hz
    [ 1767.347] (II) NOUVEAU(G0): 1280x1024@75Hz
    [ 1767.348] (II) NOUVEAU(G0): Manufacturer's mask: 0
    [ 1767.348] (II) NOUVEAU(G0): Supported standard timings:
    [ 1767.348] (II) NOUVEAU(G0): #0: hsize: 1152 vsize 864 refresh: 75 vid: 20337
    [ 1767.348] (II) NOUVEAU(G0): #1: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
    [ 1767.348] (II) NOUVEAU(G0): #2: hsize: 1600 vsize 900 refresh: 60 vid: 49321
    [ 1767.348] (II) NOUVEAU(G0): #3: hsize: 1920 vsize 1080 refresh: 60 vid: 49361
    [ 1767.348] (II) NOUVEAU(G0): Supported detailed timing:
    [ 1767.348] (II) NOUVEAU(G0): clock: 148.5 MHz Image Size: 527 x 297 mm
    [ 1767.348] (II) NOUVEAU(G0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
    [ 1767.348] (II) NOUVEAU(G0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0
    [ 1767.348] (II) NOUVEAU(G0): Serial No: 36WJX3A92PPL
    [ 1767.348] (II) NOUVEAU(G0): Monitor name: DELL P2414H
    [ 1767.348] (II) NOUVEAU(G0): Ranges: V min: 56 V max: 76 Hz, H min: 30 H max: 83 kHz, PixClock max 175 MHz
    [ 1767.348] (II) NOUVEAU(G0): EDID (in hex):
    [ 1767.348] (II) NOUVEAU(G0): 00ffffffffffff0010ac9aa04c505032
    [ 1767.348] (II) NOUVEAU(G0): 29170104a5351e783aa0a5a656529d27
    [ 1767.348] (II) NOUVEAU(G0): 0f5054a54b00714f8180a9c0d1c00101
    [ 1767.348] (II) NOUVEAU(G0): 010101010101023a801871382d40582c
    [ 1767.348] (II) NOUVEAU(G0): 45000f292100001e000000ff00333657
    [ 1767.348] (II) NOUVEAU(G0): 4a583341393250504c0a000000fc0044
    [ 1767.348] (II) NOUVEAU(G0): 454c4c205032343134480a20000000fd
    [ 1767.348] (II) NOUVEAU(G0): 00384c1e5311000a202020202020004f
    [ 1767.348] (II) NOUVEAU(G0): Printing probed modes for output DP-1-2
    [ 1767.348] (II) NOUVEAU(G0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP)
    [ 1767.348] (II) NOUVEAU(G0): Modeline "1600x900"x60.0 118.96 1600 1696 1864 2128 900 901 904 932 -hsync +vsync (55.9 kHz)
    [ 1767.348] (II) NOUVEAU(G0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 1767.348] (II) NOUVEAU(G0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [ 1767.348] (II) NOUVEAU(G0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 1767.348] (II) NOUVEAU(G0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
    [ 1767.348] (II) NOUVEAU(G0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 1767.348] (II) NOUVEAU(G0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 1767.348] (II) NOUVEAU(G0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 1767.348] (II) NOUVEAU(G0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 1767.348] (II) NOUVEAU(G0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 1767.348] (II) NOUVEAU(G0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 1767.348] (II) NOUVEAU(G0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
    [ 1767.348] (--) NOUVEAU(G0): Virtual size is 1024x768 (pitch 0)
    [ 1767.348] (**) NOUVEAU(G0): Mode "1920x1080": 173.0 MHz (scaled from 0.0 MHz), 67.2 kHz, 60.0 Hz
    [ 1767.348] (II) NOUVEAU(G0): Modeline "1920x1080"x60.0 173.00 1920 2048 2248 2576 1080 1083 1088 1120 -hsync +vsync (67.2 kHz)
    [ 1767.348] (==) NOUVEAU(G0): DPI set to (96, 96)
    [ 1767.348] (II) Loading sub module "fb"
    [ 1767.348] (II) LoadModule: "fb"
    [ 1767.348] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 1767.348] (II) Module fb: vendor="X.Org Foundation"
    [ 1767.348] compiled for 1.14.5, module version = 1.0.0
    [ 1767.348] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 1767.348] (II) Loading sub module "exa"
    [ 1767.348] (II) LoadModule: "exa"
    [ 1767.348] (II) Loading /usr/lib/xorg/modules/libexa.so
    [ 1767.348] (II) Module exa: vendor="X.Org Foundation"
    [ 1767.348] compiled for 1.14.5, module version = 2.6.0
    [ 1767.348] ABI class: X.Org Video Driver, version 14.1
    [ 1767.348] (II) Loading sub module "shadowfb"
    [ 1767.348] (II) LoadModule: "shadowfb"
    [ 1767.348] (II) Loading /usr/lib/xorg/modules/libshadowfb.so
    [ 1767.348] (II) Module shadowfb: vendor="X.Org Foundation"
    [ 1767.348] compiled for 1.14.5, module version = 1.0.0
    [ 1767.348] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 1767.348] (--) Depth 24 pixmap format is 32 bpp
    [ 1767.351] (II) NOUVEAU(G0): Opened GPU channel 0
    [ 1767.359] (II) NOUVEAU(G0): [DRI2] Setup complete
    [ 1767.359] (II) NOUVEAU(G0): [DRI2] DRI driver: nouveau
    [ 1767.359] (II) NOUVEAU(G0): [DRI2] VDPAU driver: nouveau
    [ 1767.360] (II) EXA(256): Driver allocated offscreen pixmaps
    [ 1767.360] (II) EXA(256): Driver registered support for the following operations:
    [ 1767.360] (II) Solid
    [ 1767.360] (II) Copy
    [ 1767.360] (II) Composite (RENDER acceleration)
    [ 1767.360] (II) UploadToScreen
    [ 1767.360] (II) DownloadFromScreen
    [ 1767.360] (==) NOUVEAU(G0): Backing store disabled
    [ 1767.360] (==) NOUVEAU(G0): Silken mouse enabled
    [ 1767.360] (II) NOUVEAU(G0): [XvMC] Associated with Nouveau GeForce 8/9 Textured Video.
    [ 1767.360] (II) NOUVEAU(G0): [XvMC] Extension initialized.
    [ 1767.360] (==) NOUVEAU(G0): DPMS enabled
    [ 1767.360] (II) NOUVEAU(G0): RandR 1.2 enabled, ignore the following RandR disabled message.
    [ 1767.360] (WW) NOUVEAU(G0): Option "Monitor-DVI-I-1" is not used
    [ 1767.360] (WW) NOUVEAU(G0): Option "Monitor-DP-1" is not used
    [ 1767.362] (II) NOUVEAU(0): Opened GPU channel 0
    [ 1767.366] (II) NOUVEAU(0): [DRI2] Setup complete
    [ 1767.366] (II) NOUVEAU(0): [DRI2] DRI driver: nouveau
    [ 1767.366] (II) NOUVEAU(0): [DRI2] VDPAU driver: nouveau
    [ 1767.366] (II) EXA(0): Driver allocated offscreen pixmaps
    [ 1767.366] (II) EXA(0): Driver registered support for the following operations:
    [ 1767.366] (II) Solid
    [ 1767.366] (II) Copy
    [ 1767.366] (II) Composite (RENDER acceleration)
    [ 1767.366] (II) UploadToScreen
    [ 1767.366] (II) DownloadFromScreen
    [ 1767.366] (==) NOUVEAU(0): Backing store disabled
    [ 1767.366] (==) NOUVEAU(0): Silken mouse enabled
    [ 1767.366] (II) NOUVEAU(0): [XvMC] Associated with Nouveau GeForce 8/9 Textured Video.
    [ 1767.366] (II) NOUVEAU(0): [XvMC] Extension initialized.
    [ 1767.366] (==) NOUVEAU(0): DPMS enabled
    [ 1767.366] (II) NOUVEAU(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    [ 1767.366] (--) RandR disabled
    [ 1767.388] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
    [ 1767.388] (II) AIGLX: enabled GLX_INTEL_swap_event
    [ 1767.388] (II) AIGLX: enabled GLX_ARB_create_context
    [ 1767.388] (II) AIGLX: enabled GLX_ARB_create_context_profile
    [ 1767.388] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
    [ 1767.388] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
    [ 1767.388] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
    [ 1767.389] (II) AIGLX: Loaded and initialized nouveau
    [ 1767.389] (II) GLX: Initialized DRI2 GL provider for screen 0
    [ 1767.390] (II) NOUVEAU(G0): NVEnterVT is called.
    [ 1767.393] (II) NOUVEAU(0): NVEnterVT is called.
    [ 1767.444] (II) NOUVEAU(0): Setting screen physical size to 508 x 285
    [ 1767.444] resize called 1920 1080
    [ 1767.479] (II) config/udev: Adding input device Power Button (/dev/input/event2)
    [ 1767.479] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 1767.479] (II) LoadModule: "evdev"
    [ 1767.479] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 1767.479] (II) Module evdev: vendor="X.Org Foundation"
    [ 1767.479] compiled for 1.14.3, module version = 2.8.2
    [ 1767.479] Module class: X.Org XInput Driver
    [ 1767.479] ABI class: X.Org XInput driver, version 19.1
    [ 1767.479] (II) Using input driver 'evdev' for 'Power Button'
    [ 1767.479] (**) Power Button: always reports core events
    [ 1767.479] (**) evdev: Power Button: Device: "/dev/input/event2"
    [ 1767.479] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 1767.479] (--) evdev: Power Button: Found keys
    [ 1767.479] (II) evdev: Power Button: Configuring as keyboard
    [ 1767.479] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/event2"
    [ 1767.479] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    [ 1767.479] (**) Option "xkb_rules" "evdev"
    [ 1767.479] (**) Option "xkb_model" "pc104"
    [ 1767.479] (**) Option "xkb_layout" "us"
    [ 1767.499] (II) config/udev: Adding input device Power Button (/dev/input/event1)
    [ 1767.499] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 1767.499] (II) Using input driver 'evdev' for 'Power Button'
    [ 1767.500] (**) Power Button: always reports core events
    [ 1767.500] (**) evdev: Power Button: Device: "/dev/input/event1"
    [ 1767.500] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 1767.500] (--) evdev: Power Button: Found keys
    [ 1767.500] (II) evdev: Power Button: Configuring as keyboard
    [ 1767.500] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input2/event1"
    [ 1767.500] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
    [ 1767.500] (**) Option "xkb_rules" "evdev"
    [ 1767.500] (**) Option "xkb_model" "pc104"
    [ 1767.500] (**) Option "xkb_layout" "us"
    [ 1767.500] (II) config/udev: Adding drm device (/dev/dri/card0)
    [ 1767.500] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event14)
    [ 1767.500] (II) No input driver specified, ignoring this device.
    [ 1767.500] (II) This device may have been added with another device file.
    [ 1767.500] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event13)
    [ 1767.500] (II) No input driver specified, ignoring this device.
    [ 1767.500] (II) This device may have been added with another device file.
    [ 1767.500] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event12)
    [ 1767.501] (II) No input driver specified, ignoring this device.
    [ 1767.501] (II) This device may have been added with another device file.
    [ 1767.501] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event11)
    [ 1767.501] (II) No input driver specified, ignoring this device.
    [ 1767.501] (II) This device may have been added with another device file.
    [ 1767.501] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event6)
    [ 1767.501] (II) No input driver specified, ignoring this device.
    [ 1767.501] (II) This device may have been added with another device file.
    [ 1767.501] (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event9)
    [ 1767.501] (II) No input driver specified, ignoring this device.
    [ 1767.501] (II) This device may have been added with another device file.
    [ 1767.501] (II) config/udev: Adding input device HDA Intel PCH Line Out (/dev/input/event8)
    [ 1767.501] (II) No input driver specified, ignoring this device.
    [ 1767.501] (II) This device may have been added with another device file.
    [ 1767.501] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event7)
    [ 1767.501] (II) No input driver specified, ignoring this device.
    [ 1767.501] (II) This device may have been added with another device file.
    [ 1767.502] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event10)
    [ 1767.502] (II) No input driver specified, ignoring this device.
    [ 1767.502] (II) This device may have been added with another device file.
    [ 1767.502] (II) config/udev: Adding input device DELL Dell USB Entry Keyboard (/dev/input/event4)
    [ 1767.502] (**) DELL Dell USB Entry Keyboard: Applying InputClass "evdev keyboard catchall"
    [ 1767.502] (II) Using input driver 'evdev' for 'DELL Dell USB Entry Keyboard'
    [ 1767.502] (**) DELL Dell USB Entry Keyboard: always reports core events
    [ 1767.502] (**) evdev: DELL Dell USB Entry Keyboard: Device: "/dev/input/event4"
    [ 1767.502] (--) evdev: DELL Dell USB Entry Keyboard: Vendor 0x413c Product 0x2107
    [ 1767.502] (--) evdev: DELL Dell USB Entry Keyboard: Found keys
    [ 1767.502] (II) evdev: DELL Dell USB Entry Keyboard: Configuring as keyboard
    [ 1767.502] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.5/4-1.5:1.0/input/input5/event4"
    [ 1767.502] (II) XINPUT: Adding extended input device "DELL Dell USB Entry Keyboard" (type: KEYBOARD, id 8)
    [ 1767.502] (**) Option "xkb_rules" "evdev"
    [ 1767.502] (**) Option "xkb_model" "pc104"
    [ 1767.502] (**) Option "xkb_layout" "us"
    [ 1767.502] (II) config/udev: Adding input device Logitech USB Optical Mouse (/dev/input/event5)
    [ 1767.502] (**) Logitech USB Optical Mouse: Applying InputClass "evdev pointer catchall"
    [ 1767.502] (II) Using input driver 'evdev' for 'Logitech USB Optical Mouse'
    [ 1767.502] (**) Logitech USB Optical Mouse: always reports core events
    [ 1767.502] (**) evdev: Logitech USB Optical Mouse: Device: "/dev/input/event5"
    [ 1767.502] (--) evdev: Logitech USB Optical Mouse: Vendor 0x46d Product 0xc077
    [ 1767.502] (--) evdev: Logitech USB Optical Mouse: Found 12 mouse buttons
    [ 1767.502] (--) evdev: Logitech USB Optical Mouse: Found scroll wheel(s)
    [ 1767.502] (--) evdev: Logitech USB Optical Mouse: Found relative axes
    [ 1767.502] (--) evdev: Logitech USB Optical Mouse: Found x and y relative axes
    [ 1767.502] (II) evdev: Logitech USB Optical Mouse: Configuring as mouse
    [ 1767.502] (II) evdev: Logitech USB Optical Mouse: Adding scrollwheel support
    [ 1767.503] (**) evdev: Logitech USB Optical Mouse: YAxisMapping: buttons 4 and 5
    [ 1767.503] (**) evdev: Logitech USB Optical Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 1767.503] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.6/4-1.6:1.0/input/input6/event5"
    [ 1767.503] (II) XINPUT: Adding extended input device "Logitech USB Optical Mouse" (type: MOUSE, id 9)
    [ 1767.503] (II) evdev: Logitech USB Optical Mouse: initialized for relative axes.
    [ 1767.503] (**) Logitech USB Optical Mouse: (accel) keeping acceleration scheme 1
    [ 1767.503] (**) Logitech USB Optical Mouse: (accel) acceleration profile 0
    [ 1767.503] (**) Logitech USB Optical Mouse: (accel) acceleration factor: 2.000
    [ 1767.503] (**) Logitech USB Optical Mouse: (accel) acceleration threshold: 4
    [ 1767.503] (II) config/udev: Adding input device Logitech USB Optical Mouse (/dev/input/mouse0)
    [ 1767.503] (II) No input driver specified, ignoring this device.
    [ 1767.503] (II) This device may have been added with another device file.
    [ 1767.503] (II) config/udev: Adding drm device (/dev/dri/card1)
    [ 1767.503] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event18)
    [ 1767.503] (II) No input driver specified, ignoring this device.
    [ 1767.503] (II) This device may have been added with another device file.
    [ 1767.504] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event17)
    [ 1767.504] (II) No input driver specified, ignoring this device.
    [ 1767.504] (II) This device may have been added with another device file.
    [ 1767.504] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event16)
    [ 1767.504] (II) No input driver specified, ignoring this device.
    [ 1767.504] (II) This device may have been added with another device file.
    [ 1767.504] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event15)
    [ 1767.504] (II) No input driver specified, ignoring this device.
    [ 1767.504] (II) This device may have been added with another device file.
    [ 1767.504] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
    [ 1767.504] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
    [ 1767.504] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
    [ 1767.504] (**) AT Translated Set 2 keyboard: always reports core events
    [ 1767.504] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
    [ 1767.504] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
    [ 1767.504] (--) evdev: AT Translated Set 2 keyboard: Found keys
    [ 1767.504] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
    [ 1767.504] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
    [ 1767.504] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 10)
    [ 1767.504] (**) Option "xkb_rules" "evdev"
    [ 1767.504] (**) Option "xkb_model" "pc104"
    [ 1767.504] (**) Option "xkb_layout" "us"
    [ 1767.505] (II) config/udev: Adding input device PS/2 Generic Mouse (/dev/input/event19)
    [ 1767.505] (**) PS/2 Generic Mouse: Applying InputClass "evdev pointer catchall"
    [ 1767.505] (II) Using input driver 'evdev' for 'PS/2 Generic Mouse'
    [ 1767.505] (**) PS/2 Generic Mouse: always reports core events
    [ 1767.505] (**) evdev: PS/2 Generic Mouse: Device: "/dev/input/event19"
    [ 1767.505] (--) evdev: PS/2 Generic Mouse: Vendor 0x2 Product 0x1
    [ 1767.505] (--) evdev: PS/2 Generic Mouse: Found 3 mouse buttons
    [ 1767.505] (--) evdev: PS/2 Generic Mouse: Found relative axes
    [ 1767.505] (--) evdev: PS/2 Generic Mouse: Found x and y relative axes
    [ 1767.505] (II) evdev: PS/2 Generic Mouse: Configuring as mouse
    [ 1767.505] (**) evdev: PS/2 Generic Mouse: YAxisMapping: buttons 4 and 5
    [ 1767.505] (**) evdev: PS/2 Generic Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 1767.505] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input7/event19"
    [ 1767.505] (II) XINPUT: Adding extended input device "PS/2 Generic Mouse" (type: MOUSE, id 11)
    [ 1767.505] (II) evdev: PS/2 Generic Mouse: initialized for relative axes.
    [ 1767.505] (**) PS/2 Generic Mouse: (accel) keeping acceleration scheme 1
    [ 1767.505] (**) PS/2 Generic Mouse: (accel) acceleration profile 0
    [ 1767.505] (**) PS/2 Generic Mouse: (accel) acceleration factor: 2.000
    [ 1767.505] (**) PS/2 Generic Mouse: (accel) acceleration threshold: 4
    [ 1767.505] (II) config/udev: Adding input device PS/2 Generic Mouse (/dev/input/mouse1)
    [ 1767.505] (II) No input driver specified, ignoring this device.
    [ 1767.505] (II) This device may have been added with another device file.
    [ 1767.505] (II) config/udev: Adding input device PC Speaker (/dev/input/event3)
    [ 1767.505] (II) No input driver specified, ignoring this device.
    [ 1767.505] (II) This device may have been added with another device file.
    [ 1774.230] (II) AIGLX: Suspending AIGLX clients for VT switch
    [ 1774.230] (II) NOUVEAU(0): NVLeaveVT is called.
    [ 1774.230] (II) NOUVEAU(G0): NVLeaveVT is called.
    [ 1779.499] (II) evdev: PS/2 Generic Mouse: Close
    [ 1779.499] (II) UnloadModule: "evdev"
    [ 1779.499] (II) evdev: AT Translated Set 2 keyboard: Close
    [ 1779.499] (II) UnloadModule: "evdev"
    [ 1779.499] (II) evdev: Logitech USB Optical Mouse: Close
    [ 1779.499] (II) UnloadModule: "evdev"
    [ 1779.499] (II) evdev: DELL Dell USB Entry Keyboard: Close
    [ 1779.499] (II) UnloadModule: "evdev"
    [ 1779.499] (II) evdev: Power Button: Close
    [ 1779.499] (II) UnloadModule: "evdev"
    [ 1779.499] (II) evdev: Power Button: Close
    [ 1779.499] (II) UnloadModule: "evdev"
    [ 1779.499] (II) NOUVEAU(G0): NVLeaveVT is called.
    [ 1780.500] Error dropping master: -22(Invalid argument)
    [ 1780.501] (II) NOUVEAU(G0): Closed GPU channel 0
    [ 1780.503] (II) NOUVEAU(0): Closed GPU channel 0
    [ 1780.503] (EE) Server terminated successfully (0). Closing log file.
    Thanks for any help!

    I have  a similar issue except with two ATI cards and four monitors.
    I have a working xorg.conf that uses Xinerama and all 4 work but have been trying to get xrandr to work since xinerama is deprecated supposedly.
    I would like to switch to xrandr but there is some kind of magic voodoo I have with my current xorg.conf that doesn't even work on an exact same machine and cards that I tried to setup for a co-worker.
    lspci:
    01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV610 [Radeon HD 2400 PRO/XT]
    04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV610 [Radeon HD 2400 PRO/XT]
    My xorg.conf:
    Section "Device"
    Identifier "ATI0"
    Driver "radeon"
    BusID "PCI:1:0:0"
    Option "ZaphodHeads" "DVI-0"
    Screen 0
    EndSection
    Section "Device"
    Identifier "ATI1"
    Driver "radeon"
    BusID "PCI:1:0:0"
    Option "ZaphodHeads" "DVI-1"
    Screen 1
    EndSection
    Section "Device"
    Identifier "ATI2"
    Driver "radeon"
    BusID "PCI:4:0:0"
    Option "ZaphodHeads" "DVI-2"
    Screen 0
    EndSection
    Section "Device"
    Identifier "ATI3"
    Driver "radeon"
    BusID "PCI:4:0:0"
    Option "ZaphodHeads" "DVI-3"
    Screen 1
    EndSection
    Section "Monitor"
    Identifier "DVI-0"
    Option "Primary" "On"
    Option "DPMS" "true"
    Option "PreferredMode" "1920x1080"
    Option "TargetRefresh" "60"
    EndSection
    Section "Monitor"
    Identifier "DVI-1"
    Option "DPMS" "true"
    Option "PreferredMode" "1920x1080"
    Option "TargetRefresh" "60"
    EndSection
    Section "Monitor"
    Identifier "DVI-2"
    Option "DPMS" "true"
    Option "PreferredMode" "1920x1080"
    Option "TargetRefresh" "60"
    EndSection
    Section "Monitor"
    Identifier "DVI-3"
    Option "DPMS" "true"
    Option "PreferredMode" "1920x1080"
    Option "TargetRefresh" "60"
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "ATI0"
    Monitor "DVI-0"
    DefaultDepth 24
    SubSection "Display"
    Depth 24
    Modes "1920x1080"
    EndSubSection
    EndSection
    Section "Screen"
    Identifier "Screen1"
    Device "ATI1"
    Monitor "DVI-1"
    DefaultDepth 24
    SubSection "Display"
    Depth 24
    Modes "1920x1080"
    EndSubSection
    EndSection
    Section "Screen"
    Identifier "Screen2"
    Device "ATI2"
    Monitor "DVI-2"
    DefaultDepth 24
    SubSection "Display"
    Depth 24
    Modes "1920x1080"
    EndSubSection
    EndSection
    Section "Screen"
    Identifier "Screen3"
    Device "ATI3"
    Monitor "DVI-3"
    DefaultDepth 24
    Subsection "Display"
    Depth 24
    Modes "1920x1080"
    EndSubSection
    EndSection
    Section "InputDevice"
    Identifier "Mouse0"
    Driver "mouse"
    Option "Protocol" "auto"
    Option "Emulate3Buttons" "no"
    Option "ZAxisMapping" "4 5"
    EndSection
    Section "InputDevice"
    Identifier "Keyboard0"
    Driver "kbd"
    EndSection
    Section "ServerLayout"
    Identifier "Default Layout"
    Screen "Screen0" 0 0
    Screen "Screen1" RightOf "Screen0"
    Screen "Screen2" Above "Screen1"
    Screen "Screen3" Above "Screen0"
    InputDevice "Keyboard0" "CoreKeyboard"
    InputDevice "Mouse0" "CorePointer"
    Option "Xinerama" "1"
    EndSection
    My Xorg.0.log shows all the DVI connections when I don't use a xorg.conf file but only two are "connected"
    I see DVI-0 and DVI-1 connected and in "xrandr -q" but in Xorg.0.log I see DVI-1-2 and DVI-1-3.
    xrandr --listproviders show the two cards as well.
    Tried "xrandr --setprovideroutputsource 1 0" and they show up in KDE but as clones and then X crashes eventually.
    "xrandr --setprovideroutputsource 0 1" just plain crashes X

Maybe you are looking for

  • Error code -36 - when backing up Iphoto library to external

    While backing up my iphoto library to my external hard drive - I got this message - "Finder cannot complete the operation because some data in iphoto library.2 could not be read or written. (Error code -36) What to do?

  • Report painter- business area and Cost center

    Hi All, we have a requirement to create the Report painter report where in the Revenue will be By business area and cost of the particular cost center by Cost element. i.e revenue by Business area against cost by department. It it possible to use rep

  • Wifi BB curve 8520 :(

    Hi everyone .. well, I have seen all the posts here but, i didn't found an answer for my problem simply said, I turn the wifi on, and when I start scaning he just cant' detect any wifi network .. knowing that there is a wifi network at home from my l

  • Where's the tool??

    Finally I found a tutorial I understood, Adobe Photoshop Black & White Where the heck do I access that feature in Photoshop?

  • Database Tablespaces with different block sizes...

    Hi , What are the pros and cons of setting different block sizes to tablespaces, and where may be this useful??? Thanks, Simon