Terminatin LV code module using Termination Monitor

Hi,
To terminate the LV code module I'm using three VIs: TestStand - Initialize Termination Monitor (put before while loop), TestStand - Get Termination Monitor Status (put within while loop) and TestStand - Close Termination Monitor (put after while loop).
All these three VIs are within one parent VI on the same 'layer'. The solution works.
However, the solution doesn't work if I put the first out of these tree VIs 'one level higher' i the hiearchy on the same layer as the 'parent' VI from description above.
Are they MUST be on the same layer?
Why?

Nope, they don't need to be on the same layer. The cluster that the Init VI returns is just a handful of ActiveX references, which are valid wherever. It would help if you were more clear as to what "doesn't work" means - do you get any errors, or the VI simply ignores the termination? Make sure everything (especially that cluster) is wired through properly.

Similar Messages

  • Compare two sequences loaded in a C# code module.

    Hi,
    Is it possible to compare two sequences loaded in a C# code module using functionality from the TestStand API?
    Best regards

    Hello,
    Here you can find a related post:
    http://forums.ni.com/ni/board/message?board.id=330&message.id=26058&requireLogin=False
    Let me know if you have further questions or if this doesn't help you.
    Kind Regards,
    Thierry C - Applications Engineering Specialist Northern European Region - National Instruments
    CLD, CTA
    If someone helped you, let them know. Mark as solved and/or give a kudo.

  • Teststand Manager Controls in Code Modules

      I am trying to understand how UI controls work in code modules called by TestStand steps.  I can pass a reference to an Application Manager (perhaps the application manager?) to my code module using RunState.engine.GetInternalOption(InternalOption_ApplicationManager).  Does the sequence editor have an application manager?  Or the engine?  Is this the same as the Application Manager control I put on the front panel of the code module?  What about SequenceViewManagers and ExecutionViewManagers?  Can I create those in my code modules to display sequences or executions?  Or can I somehow get those from the sequence editor/engine, or from the Application Manager?
    I know that I just asked a lot of questions, but I guess what I am looking for is some general guidelines for using the manager controls in code modules.  This all came about by an attempt to display an Execution View Manager control in my code module.  Feel free to ignore the following description of my various attempts to get this to work.  This exercise helped me understand the managers a little bit more, but I'm still a little confused.
    Suppose I want to create a custom step type for debugging to display the variables for the current sequence context on the front panel of a code module VI.  (LabVIEW 8.6, TestStand 4.1.)  In my code module, I call ExecutionViewMgr.ConnectVariables to connect to a VariableView control.  Where do I get my ExecutionView Mangager from?  I tried two methods:
    1) create an ExecutionViewManager control; set the manager's current execution using ExecutionViewMgr.Execution (pass RunState.Execution from TestStand to the code module).
    It seems like this should work, but when I run my sequence from the sequence editor, the ExecutionViewMgr.Execution property node returns error -17500.
    When I run from a LabVIEW Operator Interface (using the LabVIEW environment, not the exe), I don't get an error.  But I must connect a list control using ExecutionViewMgr.ConnectExecutionList, and select the execution from the list when the code module is running.  Then I can see the variables when I select the execution in the list.  However, the execution display on the OI goes blank.  I can see either the variables on my code module or the execution on my OI, but not both simultaneously.  It appears that an execution cannot be attached to more than one manager at once (I guess that's reasonable).
    2) pass the result of RunState.engine.GetInternalOption(InternalOption_ApplicationManager) to the code module; set the manager's current execution using ApplicationMgr.GetExecutionViewMgr() (pass RunState.Execution from TestStand to the code module, then as a parameter to GetExecutionViewMgr() ).
    In this case, I would expect that there is no ExecutionView Manager associated with the execution when running from the sequence editor.  But the ApplicationMgr.GetExecutionViewMgr() function returns a non-Null reference.  ExecutionViewMgr.ConnectVariables() causes an error dialog to be displayed (from the function itself, not from TestStand), although it doesn't actually output an error (and the VariableView control remains blank).  The error is "Unable to connect Variables View control."  (See attachment.)
    When I run from my LabVIEW OI, it works perfectly--I see the variables on my code module's UI, and the execution appears on the OI simultaneously.  I guess this makes sense since the TestStand engine is returning the Execution manager that was already created by the OI.
    Attachments:
    Error Dialog.PNG ‏20 KB

    TestStand only allows a single ApplicationMgr per process, creating a second one will error. So the engine will always return the one in either the UI or the Sequence Editor. Events should be seen by both handlers. You have to be careful to ensure that your extra handler does not mess up the UI's handler if yours is called first, like preacknowledging a message. As far as setting up a handler in a code module, you should be able to. However, we have not fully tested this capability, so we cannot say that we fully support this because you might run into issues. In addition, using LabVIEW might present additional issues that might not be seen in other development environments like CVI and Visual Studio. Performing some functionality that can process messages in a COM callback can cause potential hang conditions, to the less you do in a callback the better when using LabVIEW. Keep in mind that you have to ensure that you unregister your handler if the code module returns to the calling execution and you no longer want the handler to be called.
    Attempting to use a new TestStand UI control in a different thread than the UI thread is not recommended because we have done almost no testing on this use case because it is not done in typical UIs.
    Now, for customers that want to create a nice GUI that includes serial number prompting, but still want to be able to work with the Sequence Editor, I suggest that you implement a behavior that works with a supporting GUI, but support an alternative when a non-supporing GUI is present.
    For example, you could do the following:
    1. The process model can send a custom UI message synchronously to the GUI to ask for a serial number. The custom message would contain a reference to a property that contains (a) a boolean to indicate that the UI will "respond" to the message, (b) a string for specifying the serial number, and (c) a notification object from the TestStand Synchronization Server.
    2. When receiving the UI message, a supporting UI will set the boolean to True, duplicate the reference passed locally, and acknowledge the UI message.
    3. When the UI message returns, the exectution will determine if the UI supports the message. If yes, the exectution will (a) wait on the notifcation (b) When the user enters a serial number, the GUI will set the string property and then pulse the notification, and release the reference to the properties passed via the UI message. (c) The execution will return from the notification wait, read the serial number, and continue execution.
    If no, the execution will need to use the default process model prompting or custom prompting that you devise when using the Sequence Editor.
    The process model could use a UI message to determine if the GUI is supportive of this mechanism once instead of with each serial number prompt, but you get the idea.
    Scott Richardson
    National Instruments

  • Use the same code module for several steps in the sequence

    Hello All,
      I have been trying to set up a sequence that uses the same code module for all of the steps in the sequence, but am having trouble referring back to it when I need to send it commands.  I have gotten as far as calling the VI in a new thread so that it can be run asynchronously.  I can run the simple sequence and it will indeed open the VI, and move on to the next step.  When I close the VI manually from the front panel, the sequence in TestStand completes, as expected.  So it appears that I have that much working. 
      My question is how to call the separate thread from the main sequence or other sub sequences when I need to edit the parameters.  If I insert an Action step, I am required to select a VI file, but from what I can tell, it opens a different instance of the file, and does not provide an interface with the other instance running asycronously.  My next guess was to use a Statement step, but I was not able to figure out how to configure the lookup string to call the VI parameters.  Beyond that, I'm not sure how to proceed.  Please advise.   
      My intention is to start the code module VI (asynchronously), run several different subsequences within the main sequence that call that same VI and edit it's parameters, close everything and report on the results.  If I am misunderstanding how TestStand is supposed to work, please let me know. 
    Thanks,
    GSinMN    
    Solved!
    Go to Solution.

    What I do is use a Queue to send data to the asynchronous VI.  So it can run and do whatever, but also recieve the commands from the queue.  I use an Action Engine that holds the queue reference and sends the commands.  So you really just have to call the Action Engine from your sequences.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines

  • I am trying to debug HTBasic code modules while using Test Stand, how do I refresh the subs that have been loaded in memory?

    I am writing an application for Test Stand, we are using modules previously written in HTBasic. Whenever I make a change to the code and try to re-run the program, it just runs the old version of the code. The only way to refresh the code is to close Test Stand down and restart it. Is there a way to flush the memory of modules?

    Hi,
    I haven't used HTBasic with TestStand 2.0.x, but I'm assuming that you have the steps in the sequence set to unload when sequence file is closed (look under the step properties -> run options tab).
    If you're still prototypeing, use the File->Unload all modules option. Have a look at page 4-3 in the user manual - it refers to .DLLs, but I'm assuming the HTBasic falls into the same methodology.
    Altering the run options from it's default will affect the memory useage and speed of execution of the test sequence. Have a look at page 5-22 (page 158 in the .pdf) in the TestStand user manual - basically, if a code module is loaded into memory already, when the step gets to execute, the loading overhead is already done. If it stays in memory after this, then it's avail
    able for next time (quicker second run 'cos it doesn't need to load again. However, the balanceing factor is the sequence is useing more memory at a time, by haveing the module ready.
    My usual setting is to use Load dynamically, and Unload after sequence executes. I use this is only during development however, as this is not the most speed friendly, but a compromise so that if I don't call a step I don't load it, but if I do use a step, I'm sure it's free again when I need to modify the .dll modules I create. If you have a look on page 5-7 (143) of the user manual you can set the sequence file to effectively over-ride each step's load and unload settings - useful if you want to revert back again later. If you use this, you'll see that the top two run options for the step are greyed out, but if you set it back with the sequence file options, they do revert back to their original settings.
    Hope that helps (and works!!)
    S.
    // it takes almost no time to rate an answer

  • [Solved] How to set Code::Blocks to use Terminator!

    Hello All,
    I've recently just gotten into using an IDE to develop teh 1337 codez.
    Ignoring my silliness, I noticed that I can customize C::B to use whichever terminal emulator I like but I'm having trouble with using terminator.
    I've tried the following in the Settings :
    /usr/bin/terminator -t $TITLE -e
    terminator -t $TITLE -e
    terminator $TITLE
    And none of these have worked. Anyone have any suggestions? And yes, terminator is in my /usr/bin directory as evidenced by the output of "which terminator", which is /usr/bin/terminator
    Edit: Nevermind, I did it! Yay! Wanna know what worked? It was this (for once a man page was useful to me) : terminator -T $TITLE -x
    Last edited by MutantJohn (2013-08-23 23:30:39)

    There isn't a "code base" for java stored procedures ... that's an applet's issue.
    for more details about java stored procedures
    review teh java dev. guide and java stored proc guide located at :
    OTN FORUM ENTRY --> Oracle 8.1.7 Java Online Documentation
    http://technet.oracle.com:89/ubb/Forum18/HTML/001567.html
    null

  • 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

  • LabView code module to perform simple pass/fail *IDN? query?

    LabView 7.1, TestStand 3.1, NI PCIGPIB board controlling a communications service monitor and a power supply. I'm having problems with my application sync correctly between the service monitor and GPIB board. I suspect the driver. Does anyone have a simple LabView code module to perform a *IDN? with a partial (in case they change firmware versions)string comparison that I can use in a TestStand seq. At this point if failure I could pop-up and tell operator to abort test and reboot instrument. (only way I've found to clear the buffer). Note: At times this app works fine and is inconsistant in failure times/rates.
    Sorry so wordy and thanks in advance.
    Using LabVIEW 2010SP1 and TestStand 4.5

    Thanks for the reply Craig.
    I've found I can perform a *IDN? using the Instrument I/O Assistant.vi. Ive placed this on a new block diagram and am changing it as I need. I've found in this particular case the *IDN? yields 3 tokens one of which I can use to perform a string comparison on. This will give me a boolean which I can wire to the pane for use by TestStand.
    Using LabVIEW 2010SP1 and TestStand 4.5

  • Is it possible to launch the SequenceAnalyzer from a C# code module in a Custom TestStand Editor

    The Sequence Analyzer is not available in the Custom TestStand Editor Mode GUI.
    Is it possible to add the Sequence Analyzer to a menu in the custom TestStand Editor?
    Is it possible to launch the sequence analyzer from a C# code module, this method is then called from a sequence call back.
    Best regards
    Patrick

    From the TS Help:
    TestStand Sequence Analyzer Application
    Select Start»All Programs»National Instruments»TestStand»Tools»TestStand Analyzer or run <TestStand>\Bin\AnalyzerApp.exe to launch the stand-alone TestStand Sequence Analyzer application. Use this application to analyze projects outside of the TestStand Sequence Editor.
    The sequence analyzer application window contains the following tabs:
    Files—The files and directories to analyze.
    Rules—The rules to use for analysis. Use this tab to enable, disable, and configure rules for analysis in the current project.
    Options—Contains the project options that control the analysis and determine whether the sequence editor automatically saves the current analyzer project.
    Messages—Contains the list of messages for the most recent analysis of the current project, sequence file, or workspace file. The sequence analyzer overwrites the content of the Messages tab each time you start an analysis session.
    Analysis Summary—Contains a summary of the most recent analysis of the project.
    Command-Line Usage
    You can use the following command-line syntax to open an analyzer project:
    AnalyzerApp.exe "C:\My Documents\MyProject.tsaproj"
    CTA, CLA, MTFBWY

  • How do I set up my MacBookPro so that it uses a monitor?

    I recently bought a monitor for my laptop, and I want to set up it as a docking station so I can put my laptop away under my desk. But I am confused on what settings to change.

    This can be done.
    Either using:
    'Clamshell mode': in which the screen stays on, and closing the lid does not effect the external display. (I am not going to explain this mode, as it can result in overheating)
    Temporarily disabling the Internal Screen.
    This is done using terminal and it works. I was nervous trying it, but thankfully nothing went wrong.
    ENSURE THE EXTERNAL MONITOR IS SELECTED AS PRIMARY DISPLAY!
    Open Terminal
    To temporarily disable the internal screen in OS X Lion ONLY!
    sudo nvram boot-args="iog=0x0"
    You’ll need to reboot for changes to take effect, and the internal display will then be completely disabled regardless of whether the Mac is open or closed.
    To undo this, you can go back to the Terminal (Using only the external monitor) and enter:
    sudo nvram -d boot-args
    Then reboot again.
    Or To undo this, rather than typing the Command into Terminal:
    Just zap PRAM by holding down Command+Option+P+R during reboot, which clears out the boot-args as well. If you were to disconnect the MacBook Pro from an external video source, zapping the PRAM would be how you’d want to reenable the internal display.
    Everything worked fine on my Macbok Pro 13" Early 2011.
    Make sure you print of the instructions to have the Commands at your hand

  • Using different monitors?

    Hello! I have an old G3 B/W that I was using an old dinosaur of a monitor with. I am running 8.6 on it because I mainly use it for my Agfa Arcus II scanner. I also have a PowerBook G3 Pismo and PowerBook G5. I have a 17" Studio display that I use with the G4 using the apple adapter. I thought I would use it with the G3 B/W and bought a DVI gender changer and a VGA gender changer but it still won't work with the G3 B/W. So, I am wondering if it would be possible to use the monitor on either of my PowerBooks with the G3 B/W? Or, any other ideas would be greatly appreciated!

    Here is the story on the Display card for the Blue & White G3, from the developer note for the Blue & White G3:
    Monitor Adapter
    An monitor adapter (included with the computer) allows the user to connect a standard Apple monitor cable to the computer. The adapter enables the computer to recognize a wide range of monitor types. The Apple part number for the adapter is 590-1120.
    Monitor Sense Codes
    To identify the type of monitor connected, the computer first determines whether the adapter is connected. It does this by checking pin 11; on the new adapter, this pin is connected to the VSYNC signal.
    If the adapter is not found, the computer next checks to determine whether a DDC-type monitor is connected. DDC is the interface that provides monitor ID signals for VGA and SVGA monitors.
    If the computer does not detect a DDC-capable monitor, it uses the Apple monitor sense codes on the signals MONID(0–2) in Table 3-4. Table 3-5 shows the sense codes and the extended sense codes for each of the monitors the card can support.
    Note The Apple Studio Display 17"/viewable 16" is listed in Table 3-5 with sense code value $06-23, but it is identified using DDC on most Macintosh computers.
    Executive Summary:
    If you hook up a VGA-connector display DIRECTLY to the Blue & White G3, it should provide its capabilities via Digital Data Channel (DDC), or the Mac will assume it is an old Mac Display, whose code will be "NO Display attached", and produce No picture.
    Older Mac (two-row) displays should use adapter 590-1120 and no other.

  • Installing FCP using terminal

    friends: i want to try and install final cut pro HD 4.5 on my macbook air 11 inch running 10.7.2 (if possible). this same program is running great on my other macbook air 11 inch using a slightly earlier OS X (Lion?). 10.7.2 as you know does not support 10.7.2, but i have heard that sometimes it is just the installer that needs the powerpc so i am trying to install it via terminal. the problem is, i do not know how to configure my string properly. when i drop the .app into the terminal window i get this location:
    /Users/mycomputername/Desktop/Final\ Cut\ Pro\ HD.app
    and i was using variations of this:
    sudo installer -package /Users/mycomputername/Desktop/Final\ Cut\ Pro\ HD.app -target /
    try not to laugh, i am not a coder, just trying to get my computer to run this program that i love. the new FCP is too expensive and i don't even like it. if you can assist me in creating the proper string i would be grateful. i know that someone was able to install final cut studio using this method.
    thanks so much for your help!

    I do not use Final Cut Pro, but I play one on Television!
    Here is a quote from Wikipedia:
    In April 2004, version 4.5 of Final Cut Pro was introduced and branded by Apple as "Final Cut Pro HD" due to its native support for Panasonic's tape-based DVCPRO HDformat for compressed 720p and 1080i HD over FireWire. (The software had been capable of uncompressed HD editing since version 3.0, but at the time had required expensive video cards and high speed storage.)
    Any program written in 2004 would have been a PowerPC application.  After Apple migrated all of its future Macs to the Intel platform in 2006, it included in OS X Tiger (and later Leopard, and optionally in Snow Leopard) emulation software that would allow most PowerPC apps to continue to run in Intel.  This sofware was based upon technology that Apple licensed from a 3rd party and which Apple called Rosetta.
    Apple's license to include Rosetta in newer versions of OS X expired with Lion and now Mt. Lion.
    Hence no matter how well you use Terminal, or even Pacifist to install FCP 4.5, it just will NEVER run under Lion on your Mac.
    If your MacBook Air 11" is old enough (2010, MacBookAir3,1) to boot and run Snow Leopard, you can either partition your hard drive or add an external hard drive and install Snow Leopard into it.  You can then "dual-boot" into Snow Leopard when you want to run FCP 4.5 or into Lion when you need iCloud or otherwise.
    Alternatively you can install Snow Leopard Server into Parallels 8 on any 11" MacBook Air and have FCP 4.5 running concurrently with Lion, such as here where the PowerPC app Appleworks is running on a Lion Mac:
                                  [click on image to enlarge]
    Apple is now selling Snow Leopard Server for $19.99 + sales tax & shipping costs at 1.800.MYAPPLE (1.800.692.7753) - Apple Part Number: MC588Z/A (telephone orders only).
    Parallels offers a 14 day free trial download from its website.  It sells retail for $79 but can be found for a discount on the internet.
    NOTE: You are confusing your version with Final Cut Express 3.5 and Final Cut Studio 2, both of which will run in Lion, but whose installers have problems in Lion and Mt. Lion due to a "bug" in the installer program.  For those versions, as pointed out in Jeremy Johnstone's blog, using Terminal (or alternatively, using Pacifist) to install will achieve success in using those versions in Lion.

  • How to debug a function module using in the generic datasource?

    Hi all,
    We have created a generic data source using function modulle and have been extracting the data for a single customer it contains single records but it has pulled out more than 10,000 records. how to debug the function module used in the data source.
    since we schedule for extraction in bi and back ground job gets triggered in ecc for extraction,
    i know in se37 we can select the function module name and then debug but still need to check while the bacground job is trigered through bi.
    Thanks

    Yes you can debug the Function Module.
    Open the function module in SE37 and put a break point in the code where you want to check from, then come to RSA3 and give the datasource name and check the Debug check box on this screen, once you click on the start button it will take you the place where you have placed the break point in the FM, by pressing F5 you can see the flow of the FM.
    Let me know whether this solves your issue.

  • How to use  Progress Monitors?

    how to use Progress Monitors?
    in the name of god
    hi friends
    i have a problem. I am writing a program that read data from a file record by record and store to a database. my problem is here that i want add a progress monitor that when the program is doing its work it appear. I use ProgressMonitorInputStream class but it can not work well. It appear and read file record by record and store in table of database but its progress don’t move and do nothing. I know that I have a tiny problem in use this class. Please guide me.
    i put my codes below.
    best regards
    *////this is an event that invoke my classes*
    private void readbtnActionPerformed(java.awt.event.ActionEvent evt) {                                       
            JFileChooser fileChooser = new JFileChooser();
            fileChooser.setCurrentDirectory(fileName);
            //filtering file extension
            FileNameExtensionFilter filter = new FileNameExtensionFilter("Text file", "txt");
            fileChooser.setFileFilter(filter);
            //fileChooser.setFileSelectionMode(JFileChooser.FILES_AND_DIRECTORIES);
            int result = fileChooser.showOpenDialog(this);
            if (result == JFileChooser.APPROVE_OPTION) {   //if choose ok button
                fileName = fileChooser.getSelectedFile();
                ReadTextFile readFile = new ReadTextFile(fileName);
                readFile.openFile();
                readFile.readRecord();
                *//readFile.closeFile();       //if  this line enable this message appeare "Scanner closed" .why?*      
                readFile.closeFile();
            } else //if choose cancel button
                result = 0;     //do nothing
    */////this is readFile class and invoke data access class and insert data in my database*
    public class ReadTextFile {
        private Scanner input;
        private File fileName;
        private int i = 1;
        DataAccess dal = new DataAccess();                     //new a defined my class
        AcountRecord record = new AcountRecord();
        public ReadTextFile(File n) {       //Constructor
            fileName = new File(String.valueOf(n));
            this.openFile();
        private void setRecord(String val) {
            try {
                record.setId(Integer.parseInt(val.substring(1, 5)));
                record.setTime(Integer.parseInt(val.substring(8, 12)));
                record.setDate(Integer.parseInt(val.substring(15, 21)));
                record.setMode(val.substring(24, 26));
            } catch (Exception e) {
                JOptionPane.showMessageDialog(null, "ÇäÊÎÇÈ ÔãÇ äÇÏÑÓÊ ÇÓÊ.","Set Record Method",JOptionPane.ERROR_MESSAGE);
        public void openFile() {
            try {
                input = new Scanner(fileName);
            } catch (FileNotFoundException e) {
                JOptionPane.showMessageDialog(null, "ÇäÊÎÇÈ ÔãÇ äÇÏÑÓÊ ÇÓÊ.","Open File Method",JOptionPane.ERROR_MESSAGE);
        public void readRecord() {
            new Thread() {
                private Component _Main;
                @Override
                public void run() {
                    try {
                        input = new Scanner(fileName);
                        InputStream in = new FileInputStream(fileName);
                        ProgressMonitorInputStream pm =
                                new ProgressMonitorInputStream(_Main, "reading the file", in);
                        ProgressMonitor pmo = pm.getProgressMonitor( );
                        pmo.setMaximum( (int) fileName.length());
                        while (/*input.hasNext() &&*/ pm.read() != -1) {
                            setRecord(input.next());
                            dal.Connect();
                            String sql = "INSERT INTO fileinfo(pkey,id,date,time,mode)VALUES(%s,%s,%s,%s,'%s')";
                            sql = String.format(sql, i++, record.getId(), record.getDate(), record.getTime(), record.getMode());
                            dal.doCommand(sql);
                    } catch (Exception e) {
                        JOptionPane.showMessageDialog(null, e.getMessage() ," Read Record method.",JOptionPane.ERROR_MESSAGE);
                    dal.Disconnect();      
            }.start();
        public void closeFile() {
            input.close();
    }Edited by: firethumbs on Mar 26, 2009 12:43 PM

    IN THE NAME OF GOD
    hi firends
    i forget say one thing. if remove while loop content this program will work good. i suppose that the while condition and read file records not similar. because while condition check bytes but in while body read records. is that true?
    how can solve this problem?
    best regurds

  • WOrkflow related table and zfunction modules used in a particular workflow

    hi gurus,
                  we need to develop a tool to findout the custom WF, custom BOR and workflow related Zfunction modules used in a particular workflows in the client system.
    Eg-
          I have a custom workflow i need to find the list of all zfunction modules , z includes used in that Workflow.
    please suggest us  the table names which stores ZFunction module or z includes used in particular workflow
    Regards,
    Hari

    The only way to do this is to read through the source code of all the objects accessed within workflow and look for the relevant ABAP statements that access Z tables or function modules.
    [This wiki|https://www.sdn.sap.com/irj/scn/wiki?path=/display/snippets/utilitytosearchABAPsourcecodeandTextelementsfora+string] should get you started on that part.
    As far as the objects are concerned, this is another story altogether. Something as simple as using an SAP standard object attribute in work item text could actually be a delegated subtypes with a redefined virtual attribute.
    So you need to scan everything: all tasks in a workflow and methods, as well as all container elements of each step. You will also need to navigate the object hierarchy to deal with delegation and subtypes. Then you need to consider propagation, what about Zfunction modules called by Zfunction modules in workflow? What if the method submits a report - you would need to scan that report and everything else that it calls and so on.
    This could be a fiendish challenge but sounds like a fun project. Good luck!

Maybe you are looking for

  • Need to print multiple sections in a group

    We have print customer invoices. Along with each invoice, we have to send 1.     A Cover Letter that is always one page 2.     Terms and conditions. This could be between 1 to 3 pages Our requirement is to have separate page numbering for each of the

  • Word report

    Hi All, Currently working on a program where I use the Office Report Generation (Word) With LV 8.5 I used a VI of my own to set a table in autofit. This can not be done with the VI in the toolkit (I think  ) With LV 8.6 the report reference is change

  • Settings not retained after a few days of non-use

    If I don't use the iPod for a few days, when I turn it on I see the menu for selecting my language. Then I also have to reset my contrast and main menu options, etc. Essentially, my settings are not being retained. I can understand the appearance of

  • Problem in modifying the existing record in table control

    Hi Experts, I have one table control.I have entered one record and save it.When I am modifying the same record a duplicate record is created.I need if I modify the same record that record should only modify.How to delete the duplicate record.

  • Partial Solution:Web Service Data Controls don't refresh properly.

    I am runing JDeveloper Studio Edition 10.1.3.2.0.4066 I have developed several Web Service Data Controls and pages to use them to display output. The pages seem to have a problem refreshing output when the value of the input parameter is changed, but