Bizarre plug-in behaviour

Hi all
I recently installed Logic etc. on a nice shiny new Mac. Booting up Logic for the first time (and many times subsequently) the Audio Unit Manager (AUM) tells me about various incompatible plug-ins (a few freebies from magazines, no great loss, but unfortunately my Pluggo stuff as well). Anyway, I deleted them all from User/Library/Audio/Plugins/Components....but THEY'RE STILL SHOWING IN AUM??! More strangely, there's a plug-in there (an acoustic guitar strumming emulator) THAT I NEVER INSTALLED on the new Mac?? It doesn't exist anywhere on my system (at least not according to Spotlight)...but trips the AUM? What is going on?! Have I inadvertently copied some reference (preference?) file over from my old Mac.
Also, the AUM seems to offer the option of disabling the incompatible plug-ins, which I do...but it makes no difference, they still reappear and trip the alarm.
...for the last bit of weirdness, when I go to open certain applications, I get the usual "Open with..." option if I right-click...but it shows applications WHICH AREN'T ON MY DISK...and I never installed on the new Mac.
Please, can someone help my exorcise the ghost in my machine?
N

Relax. Breathe calmly.
For the AU part, check out /Library in addition to user/Library.
Christian

Similar Messages

  • Stationery (templates) behaviour question

    As a Licensed Old Crank, I've done what I can to get rid of Starting Points, and never have gone into Templates. Recently I created a blank, landscape oriented 11x17 document in Draw and saved it where I wanted, as Stationery (.cws) for on-going use ignoring the Templates default.
    When I open the document w/ a double click, a window in my format pops open called "Untitled" just as expected. But unexpectedly, my Stationery document makes a copy of itself called "<name> copy.cws", or copy1, 2 etc. if there's already such a document. Each one behaves as Stationery, but none 'is' the item I'm working with, just waiting for a new name, or to swap its .cws for a .cwk on saving. Of course using a tedious Open… dialogue in AW (and having to select the document type AWTemplates, which are apparently not AW Documents) works perfectly.
    It's only for my amusement that I ask; is there an accepted theory about the purpose intended by such bizarre non-standard behaviour? Has it ever been reported elswhere in the Applverse? Or does it join List View in Tiger's Finder that unaccountably has no Cut in its Edit menu in the Hall of Apple Oddities?
    Message was edited by: Ed Hanna
    Message was edited by: Ed Hanna

    AppleWorks template files are intended to be opened from Starting Points (they contain information that AW uses to organize your template files). It doesn't hurt anything, but is just a matter of self-preservation. AppleWorks has indexed those template files so you can find them easily from within AppleWorks. If your Mac has multiple user accounts, it keeps each user's templates separate from the others, while allowing all users access to the common templates. When you try to open them from the Finder, AW immediately makes a copy of it to make it harder for you to make an inadvertent change to the original indexed version.
    If you want to be able to double-click a template, you can use my solution to delete the original template after a "copy" was created, then remove "(space)copy" from the name of the copy created. I found that this copy (now named as the original template) will not create copies.

  • Only two hard drives - optimal file locations?

    Hi,
    Can anyone tell what would be the optimal file location configuration (regarding perfomance) when there are only two physical hard drives available? One is abviously running the OS (Windows XP), but how to locate raw images, ACR cache and catalog-files for optimal performance (and are there any other file locations to consider from LR point of view)? The search did not provide answer to this question, and with google everything pretty much boils down to having (at least) three physical hard drives or RAID-array, which are not an option for me.
    The workstation can have only two internal drives but allows dedicated controllers for both of them, and I would prefer not to have external drive (only USB2 and FW400 connectors available). Memory is already maxed for the current mother board, and disk activity seems to be next place to optimize. The current performance is "ok", but it would not hurt to squeeze a bit more.
    Running Windows XP and LR 2.3.
    Thanks in advance.

    Thank you for your advice. It has been quite a pain to find out credible setup hints for simple two drive setup.
    This slightly differs from original topic, but...
    Have there been more inprovements within 2.4 code than have been mentioned in release notes (e.g. http://thelightroomlab.com/2009/06/lightroom-24-and-adobe-camera-raw-54-available/)? I have currently no need for additional camera support, and the bugs mentiones as "fixed" have not been a problem for me. I have had some cases with inconsistent plug-in behaviour (and few crashes) with export plug-ins, but I have judged those as problems either with SDK or plug-in itself.

  • After upgrade to IOS 5 I can no longer charge iPhone 4 in car.

    I upgraded my iPhone 4 to IOS 5 last night and now when I try to use my car charger it doesnt work.   Everything was working fine prior to upgrade and I have tried to reboot iPhone with no behavior changes.  It will charge using the USB charger connected to my iMac.

    I dont beleive its an iOS 5 Issue - i think its hardware...
    Simply because i have been running iOS 5 beta's since june and there were no issues with my iPhone 4.
    When i installed the GM on my iphone 4 (which is the same build as the public release) there were no issues with charging in my vehicle.
    Now, charging my iPhone 4S in my car is practically impossible.
    when i plug mine in, it will display the "Plugged" symbol on the battery display but not actually charge. the battery will still decrease.
    then it will randomly "disconnect" and not register that it is plugged in. then appear to be plugged in, then not, then plugged in, then not.
    This will repeat over and over again without actually charging and the charger being in the socket throughout.
    however yesterday i left it plugged in and my battery was 9% and after the strange plugged-in behaviour i noticed it was charging normally after about 20 mins in the car.
    But when i did the same journey time today, the battery wouldnt register at all.... charging has only been successful ONCE since 14th October on the iPhone 4s
    No idea whats up with it...
    anybody else?

  • Has anyone had problems with iCloud being blocked by corporate web security?

    Has anyone else encountered problems with iCloud being blocked by the web-security on company computers?   I never had any problems with me.com, but now it appears I will be unable to check my mail via any computer at work. 
    Since iCloud is a portal for high-volume image and file sharing, I can understand why the site would be blocked, but it's very frustrating that this possibility would not have been anticipated, and an alternate web-mail site been set up.  Otherwise many me.com subscribers may be left unable to use the iCloud web-mail portal via computers at work or at internet cafes that may block access to potentially risky websites.
    Has anyone figured out a back door to this problem? 

    I dont beleive its an iOS 5 Issue - i think its hardware...
    Simply because i have been running iOS 5 beta's since june and there were no issues with my iPhone 4.
    When i installed the GM on my iphone 4 (which is the same build as the public release) there were no issues with charging in my vehicle.
    Now, charging my iPhone 4S in my car is practically impossible.
    when i plug mine in, it will display the "Plugged" symbol on the battery display but not actually charge. the battery will still decrease.
    then it will randomly "disconnect" and not register that it is plugged in. then appear to be plugged in, then not, then plugged in, then not.
    This will repeat over and over again without actually charging and the charger being in the socket throughout.
    however yesterday i left it plugged in and my battery was 9% and after the strange plugged-in behaviour i noticed it was charging normally after about 20 mins in the car.
    But when i did the same journey time today, the battery wouldnt register at all.... charging has only been successful ONCE since 14th October on the iPhone 4s
    No idea whats up with it...
    anybody else?

  • IWeb random save issues

    This last week has been very traumatic...
    I am a hardened fan of iWeb and it has served me well. However, just lately I have noticed some rather bizarre and irritating behaviour.
    After closing the programme and reopening, I notice work missing despite saving.
    Even while working, I can work on a page, move to another for a wile only to return to find my recent changes are no longer there. Yes I save as I go and no I do not accidentally revert to saved.
    In frustration I deleted my prefence file and this worked for a few days but now I am scared to close the program.
    Has anyone else had this problem?
    What would you suggest in my position where I have published the site but have hours of work that I could lose if I close the app and open again.
    I use TimeMachine but I am guessing as it is not saving correctly, this will not help me?
    All the best,
    Mark

    You would need to close iWeb, delete the cache and then relaunch to see if that will have any effect.  Also reboot your Mac.
    You won't be albe to keep iWeb open indefinitely and then when it does get closed for some reason you've lost more work than you will have lost now.  Are you running Lion?  If so then this may be of some help:
    In Lion the Library folder is now invisible. To make it permanently visible enter the following in the Terminal application window: chflags nohidden ~/Library and hit the Enter button - 10.7: Un-hide the User Library folder.
    To open your domain file in Lion or to switch between multiple domain files Cyclosaurus has provided us with the following script that you can make into an Applescript application with Script Editor. Open Script Editor, copy and paste the script below into Script Editor's window and save as an application.
    do shell script "/usr/bin/defaults write com.apple.iWeb iWebDefaultsDocumentPath -boolean no"delay 1
    tell application "iWeb" to activate
    You can download an already compiled version with this link: iWeb Switch Domain.
    Just launch the application, find and select the domain file you want to open and it will open with iWeb. It modifies the iWeb preference file each time it's launched so one can switch between domain files.
    WARNING: iWeb Switch Domain will overwrite an existing Domain.sites2 file if you select to create a new domain in the same folder.  So rename your domain files once they've been created to something other than the default name.
    The application also works with earlier systems. 

  • ScreenUpdating=False fails to prevent screen updating, and causes bizarre behaviour

    I have recently installed Office 2013 (MSO Standard 2013) on my (Win 7 Professional) computer.  During a brief transitional period, Office 2003 will remain on my computer.
    I had been looking forward to running the many Excel VBA applications on Excel 2013, but am not only disappointed, but alarmed.  We are significantly dependent on over 50 business applications running in Excel VBA (many of which are complex,
    and many of which I have developed), but we now find that seemingly one difference alone (though we may yet discover more) is rendering many of them virtually unusable.  That difference is the behaviour of the Application.ScreenUpdating method.
    In Excel 2003, the ScreenUpdating method behaved intuitively, predictably and reliably.  It basically does what it says - all screen updating, except for the status bar, is frozen.  To allow users to peek at any updates, one would simply
    set ScreenUpdating=True and at the appropriate point freeze updating with ScreenUpdating=False.  Now, in Excel 2013, we are instead finding behaviour which has to be described as bizarre, counterintuitive and destructive.  Essentially, what is happening
    is that whenever another worksheet is activated, ScreenUpdating=False does not prevent screen updating - and for good measure, there are a number of other unpleasant side-effects.  I have spent many long hours searching through hundreds of forum posts
    and testing workarounds - all without success.  I have seen many posts complaining about ScreenUpdating in Excel 2013, but not a single implementable solution.  Yes, I've seen the advice about replacing Select or Activate methods with objects, but
    this workaround would not only be extremely costly and impractical in our case (it would require reworking tens of thousands of lines of code and would probably take many person months of unjustifiable work), it almost certainly wouldn't work.  (You'll
    have to take my word on that.)  And all because ScreenUpdating=False doesn't really prevent screen updating any more!  I cannot accept that ScreenUpdating is working properly in Excel 2013, nor that its functionality is in any way acceptable.
    The problems are best illustrated with a simple example.  I created this example to verify that the flickering was unrelated to the complexity of the business applications I referred to above.  In this example, there is a "master"
    workbook named "ScreenUpdatingTest.xls".  This contains a single button on its only worksheet, and this button executes macro "TestScreenUpdating".  This macro turns screen updating off, then sequentially opens workbook AAA.xls,
    workbook BBB.xls and workbook CCC.xls with a 3 second interval between each workbook being opened.  After 3 more seconds, it activates workbook ScreenUpdatingTest.xls and then turns screen updating on.  Along the way, it reports these actions in
    the status bar.  One would expect that this would result in AAA, BBB and CCC being opened in the background, with the user seeing no changes on the screen apart from the status bar and the workbooks appearing in the task bar.  This is precisely what
    happens in Excel 2003.
    By contrast, Excel 2013 seems to do absolutely nothing for about 12 seconds (even the task bar and the status bar remains unchanged), then, AAA, BBB and CCC can be seen to open (in maximized windows) in rapid succession.  The only message I see in the
    status bar is the last one, "Switched back to ScreenUpdatingTest.xls."  Even more bizarrely, that there is a call to Msgbox "Hi" just before the Application.ScreenUpdating=True at the end of the subroutine - and this should be unrelated
    to which workbook the focus end up with, right?  Wrong!  If Msgbox "Hi" is commented out, the focus ends up with CCC.xls - in other words, Workbooks(ThisWorkbook.Name).Activate seems to be ignored.  But if Msgbox "Hi" is
    uncommented, the focus ends up with ScreenUpdatingTest.xls!  This is crazy, isn't it?
    Sub TestScreenUpdating()
    Application.ScreenUpdating = False
    Application.Wait Now() + TimeValue("00:00:03")
    Workbooks.Open ThisWorkbook.Path & "\AAA.xls"
    Windows("AAA.xls").Activate
    Application.StatusBar = "AAA.xls has been opened."
    'Excel 2003:
    ' I see workbook ScreenUpdatingTest.xls on the screen with no flickering.
    ' AAA.xls is open in the task bar.
    ' The message that AAA.xls has been opened appears in the status bar.
    'Excel 2013:
    ' I see workbook ScreenUpdatingTest.xls on the screen with no flickering.
    ' AAA.xls is >>>NOT<<< open in the task bar
    ' >>>NO<<< message that AAA.xls has been opened appears in the status bar.
    Application.Wait Now() + TimeValue("00:00:03")
    Workbooks.Open ThisWorkbook.Path & "\BBB.xls"
    Windows("BBB.xls").Activate
    Application.StatusBar = "BBB.xls has been opened."
    'Excel 2003:
    ' I see workbook ScreenUpdatingTest.xls on the screen with no flickering.
    ' AAA.xls and BBB.xls are open in the task bar.
    ' The message that BBB.xls has been opened appears in the status bar.
    'Excel 2013:
    ' I see workbook ScreenUpdatingTest.xls on the screen with no flickering.
    ' AAA.xls and BBB.xls are >>>NOT<<< open in the task bar.
    ' >>>NO<<< message that BBB.xls has been opened appears in the status bar.
    Application.Wait Now() + TimeValue("00:00:03")
    Workbooks.Open ThisWorkbook.Path & "\CCC.xls"
    Windows("CCC.xls").Activate
    Application.StatusBar = "CCC.xls has been opened."
    'Excel 2003:
    ' I see workbook ScreenUpdatingTest.xls on the screen with no flickering.
    ' AAA.xls, BBB.xls and CCC.xls are open in the task bar.
    ' The message that CCC.xls has been opened appears in the status bar.
    'Excel 2013:
    ' I see workbook ScreenUpdatingTest.xls on the screen with no flickering.
    ' AAA.xls, BBB.xls and CCC.xls are >>>NOT<<< open in the task bar.
    ' >>>NO<<< message that CCC.xls has been opened appears in the status bar.
    Application.Wait Now() + TimeValue("00:00:03")
    Workbooks(ThisWorkbook.Name).Activate
    Application.StatusBar = "Switched back to ScreenUpdatingTest.xls."
    MsgBox "Hi"
    Application.ScreenUpdating = True
    'Excel 2003:
    ' I see workbook ScreenUpdatingTest.xls on the screen with no flickering.
    ' AAA.xls, BBB.xls and CCC.xls are open in the task bar.
    ' The message that we have switched back to ScreenUpdatingTest.xls appears in the status bar.
    'Excel 2013:
    ' Workbooks AAA.xls, BBB.xls and CCC.xls appear in rapid succession.
    ' When execution ends:
    ' If Msgbox "Hi" is commented out, the focus is with CCC.xls.
    ' If Msgbox "Hi" is uncommented, the focus is with ScreenUpdatingTest.xls.
    ' AAA.xls, BBB.xls and CCC.xls are >>>NOT<<< open in the task bar.
    ' The message that we have switched back to ScreenUpdatingTest.xls appears in the status bar.
    End Sub
    Surely it is reasonable to expect that such functionality should remain consistent from one version to the next!  Our applications in Excel 2003 had a professional, elegant user interface, and they behaved predictably, intuitively and robustly. 
    With Excel 2013, this is utterly trashed, with flickering, unpredictable behaviour (who knows what will get the focus?) and inefficiency (things are so much slower when the screen updates).  With Office 2003 going out of support, vast numbers of people
    in my company will be moving to Excel 2013 as Excel 2003 is decommissioned.  I imagine the same will be happening in many other companies.  We now find ourselves on the cusp of being dealt us a devastating blow due to ONE DYSFUNCTIONAL METHOD, and
    we are desperate for a solution.  A solution would either have to restore the former Excel 2003 functionality of ScreenUpdating, or it would have to introduce a new method which really does turn screen updating on or off without exception.
    Please, HELP!
    -Peter

    Thanks for the input, Jim.
    I don't think the Single Document Interface is contributing to the problem.  Since installing Office 2013, Excel 2003 has also inherited a Single Document Interface - yet while it behaves like a charm, Excel 2013 behaves ineptly.
    Whatever the reasons for the problem, the fact is that this functionality is now broken - one might even say catastrophically broken - and some sort of resolution is essential.  It would be madness to allow something like this to have such a severe
    impact on business operations.
    My call for help is still out there, as loud as ever!  BTW, I can send my example files, zipped, to anyone who might like to look at them.
    Peter
    Sydney, Australia

  • Different behaviour of a plug in in CS6 and CS5.5

    I've noticed a difference in a plugin behaviour in CS6 and CS5.5.
    In a SequenceSetup function the following call generates a PF_Cmd_ARBITRARY_CALLBACK in CS6 with the PF_Arbitrary_FLAT_SIZE_FUNC state of extra parameter. The same PF_Cmd_ARBITRARY_CALLBACK appears later in a plugin work and doesn't work properly in CS6. Though in CS5.5 there is no problem with this function, it doesn't generate any weird events.
    suites.ParamUtilsSuite1()->PF_GetCurrentState(in_data->effect_ref, &seqData->curSessionParamState); (code for CS5.5)
    suites.ParamUtilsSuite3()->PF_GetCurrentState(in_data->effect_ref,PF_P aramIndex_CHECK_ALL, NULL, NULL, &seqData->curSessionParamState); (updated code for CS6, in respect that the signature of PF_GetCurrentState has changed)
    I work in Windows 7, x64. CS6 is 11.0.0.378 version, CS5.5 is 10.5.0.253 version. The only change between these two version of the plug in is the PF_GetCurrentState signature. So I suppose that the problem is inside a new SDK. But I have no guess where it may be.. Do you have any idea what might have changed in CS6 to provide such an error?

    Hi Niakris,
    Thanks very much for closing the loop and reporting back what worked for you.  As to why there is a difference between CS5.5 and CS6, one of the engineers here explains:
    "I assume the behavior change is due to me making code in certain libraries thread-safe, and explicitly disallowing the execution of certain callbacks on anything other than the main thread. If it worked before CS6, it worked by accident, and was very unsafe to do."
    Glad to have you testing compatibility with CS6!
    Cheers,
    Zac

  • Most Bizarre JTabbedPane behaviour. Help Required!!!

    Folks
    I am getting a Bizarre behaviour regarding JTabbedPane.
    Here it is:
    I am using the addTab() method in my Main class:
    tabbedPane.addTab("One",
    null,
    new SCSCF(),
    "Testing One");
    Nothing is displayed on my Window!!!!!
    But when I say:
    tabbedPane.addTab("One",
    null,
    new SCSCF().show(),
    "Testing One");
    the concerned class details is displayed.
    public class SCSCF {
    public SCSCF(){
    new ScscfGui("Test");
    public Component show(){
    return new ScscfGui("Test");
    Can some please explain this as this is Urgent!!!
    I would like to use the first Option of calling the class directly!!!!!
    ie addTab(...
    new SCSCF(),
    Please can some one help!! Has any one understood my question!!!!

    Now what component is ur SCSCF() class?? Is it a JPanel or what?? Posting some code should help, perhaps...

  • Bizarre keyboard behaviour after 4.2 upgrade

    Since upgrading to KDE 4.2 (from 4.1) as part of a system upgrade, my system has been practically unusable due to the bizarre keyboard behaviour within KDE.
    Right from the KDM login screen, most of the keys do not work as normal.  For most letters, the key has to be pressed twice in order to generate the letter.  However, I cannot type anything with a "u" because it is interpreted as a shortcut to undo everything I have just entered!  Letter "f" has to be typed 4 times.  If I type "h" once it appears; if I type it again it disappears.  Letter "l" produces a vertical division in the window.  I could go on....
    Since my password ends in "u" I even had to change the password in order to login to KDE because the "u" would delete the characters I'd already entered!  But once logged in the problem is just the same.
    I have tried setting a different keyboard layout within KDE but this made no difference.
    I have tried uninstalling and reinstalling KDE.
    The problem seems to be KDE related, because outside KDE, in a system console, the keyboard works absolutely normally.  And it doesn't seem to be related to the individual KDE user, since as I said, the problem is present as soon as the KDM login screen appears.
    Has anyone got any ideas please?

    Thanks for the suggestions.  Although they did not prove to be the answer, I have now overcome the problem.  I suspect it was a one-off caused by corrupted data, probably in the xorg installation rather than KDE.  I removed xorg then reinstalled it - some of the pkg files were corrupt and had to be replaced.  Then I had trouble starting the X server at all, and had to reinstall several library packages.  The system is running more normally now, though I think there are still some data corruptions in there and time will tell whether the installation is salvageable.

  • Bizarre behaviour in 9.0.2: Colour Draining

    Hi, not a major emergency but worrying behaviour nonetheless:
    I was playing through a project, with two displays set up. Mixer on my main MBP screen, arrange on the other screen. As the song was playing, the colours on the mixer window began to drain gradually until it was almost (but not quite) black and white. The other window on the peripheral screen was unaffected, as was the desktop on the main screen. Only the mixer window was doing this. When I stopped playback it seemed to reset the colour, but the same thing would happen whenever I pressed play again: gradual draining, as if someone was slowly turning down the colour knob. But ONLY on the mixer window itself.
    Until I looked at the other screen, I thought I was losing my mind/going blind! I restarted Logic and it seemed to stop doing it, but it's alarming to say the least.
    I'm just curious if anyone else has experienced this in 9.0.2 or any other versions.

    Yes, I've seen a few graphic glitches, usually on 8.0.2 projects opened in 9. I haven't seen color draining to grayscale, but I've seen fading of colors, particularly when the projects are struggling to run in .v. 9 (all too often).
    I've also seen the patchy effect like Guitarisation's example, together with mixer faders broken up and displaying twice, one above the other, in the channel strip. I've no idea what causes it, and the only work around I've found is to switch screensets so the windows redraw which often fixes it.

  • Bizarre X behaviour after boot

    Hello,
    I've recently done a fresh install on a new desktop, encrypted root with btrfs. I've installed minimal packages: base base-devel, xorg-server, xorg-xinit, xf86-video-nouveau, xf86-input-evdev, awesome, firefox and urxvt. Everything boots up fine, no errors.
    When I startx (as a user and with a skel .xinitrc), the window manager loads and everything appears to be ok. However, launching firefox the UI becomes semi-unresponsive (I can't click any buttons, enter a URL etc.), but if I restart X everything works fine. I've also tried with openbox (nstead of awesome) and the same problem occurs - I can open a menu, launch firefox and shortly after the UI becomes semi-unresponsive, including the Openbox UI. I am just using firefox as an example, even loading just a urxvt will cause similar behaviour.
    systemctl status shows no failed services
    journalctl shows no errors
    My initial thoughts were something with dbus was not configured correctly. But I've exhausted the dbus and systemd wikis and everything appears to be correct.
    Xorg.0.log (on boot, semi-unresponsive)
    [ 14.755]
    X.Org X Server 1.15.0
    Release Date: 2013-12-27
    [ 14.755] X Protocol Version 11, Revision 0
    [ 14.755] Build Operating System: Linux 3.12.5-1-ARCH x86_64
    [ 14.755] Current Operating System: Linux wasteland 3.12.9-2-ARCH #1 SMP PREEMPT Fri Jan 31 10:22:54 CET 2014 x86_64
    [ 14.755] Kernel command line: vmlinuz-linux initrd=initramfs-linux.img root=/dev/mapper/root cryptdevice=/dev/sda2:root:allow-discards ro
    [ 14.755] Build Date: 09 January 2014 08:47:24AM
    [ 14.755]
    [ 14.755] Current version of pixman: 0.32.4
    [ 14.755] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 14.755] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 14.755] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Feb 17 14:30:38 2014
    [ 14.756] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 14.756] (==) No Layout section. Using the first Screen section.
    [ 14.756] (==) No screen section available. Using defaults.
    [ 14.756] (**) |-->Screen "Default Screen Section" (0)
    [ 14.756] (**) | |-->Monitor "<default monitor>"
    [ 14.756] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    [ 14.756] (==) Automatically adding devices
    [ 14.756] (==) Automatically enabling devices
    [ 14.756] (==) Automatically adding GPU devices
    [ 14.757] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [ 14.757] Entry deleted from font path.
    [ 14.758] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/Type1/,
    /usr/share/fonts/100dpi/,
    /usr/share/fonts/75dpi/
    [ 14.758] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 14.758] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 14.758] (II) Loader magic: 0x804c80
    [ 14.758] (II) Module ABI versions:
    [ 14.758] X.Org ANSI C Emulation: 0.4
    [ 14.758] X.Org Video Driver: 15.0
    [ 14.758] X.Org XInput driver : 20.0
    [ 14.758] X.Org Server Extension : 8.0
    [ 14.758] (II) xfree86: Adding drm device (/dev/dri/card0)
    [ 14.758] (II) xfree86: Adding drm device (/dev/dri/card1)
    [ 14.759] (--) PCI:*(0:1:0:0) 10de:0e22:1458:34fc rev 161, Mem @ 0xf4000000/33554432, 0xe8000000/134217728, 0xf0000000/67108864, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
    [ 14.759] (--) PCI: (0:2:0:0) 10de:0e22:1458:34fc rev 161, Mem @ 0xe4000000/33554432, 0xd8000000/134217728, 0xe0000000/67108864, I/O @ 0x0000d000/128, BIOS @ 0x????????/524288
    [ 14.759] (II) Open ACPI successful (/var/run/acpid.socket)
    [ 14.759] Initializing built-in extension Generic Event Extension
    [ 14.759] Initializing built-in extension SHAPE
    [ 14.759] Initializing built-in extension MIT-SHM
    [ 14.759] Initializing built-in extension XInputExtension
    [ 14.759] Initializing built-in extension XTEST
    [ 14.759] Initializing built-in extension BIG-REQUESTS
    [ 14.759] Initializing built-in extension SYNC
    [ 14.759] Initializing built-in extension XKEYBOARD
    [ 14.759] Initializing built-in extension XC-MISC
    [ 14.759] Initializing built-in extension SECURITY
    [ 14.759] Initializing built-in extension XINERAMA
    [ 14.759] Initializing built-in extension XFIXES
    [ 14.759] Initializing built-in extension RENDER
    [ 14.759] Initializing built-in extension RANDR
    [ 14.759] Initializing built-in extension COMPOSITE
    [ 14.759] Initializing built-in extension DAMAGE
    [ 14.759] Initializing built-in extension MIT-SCREEN-SAVER
    [ 14.759] Initializing built-in extension DOUBLE-BUFFER
    [ 14.759] Initializing built-in extension RECORD
    [ 14.759] Initializing built-in extension DPMS
    [ 14.759] Initializing built-in extension Present
    [ 14.759] Initializing built-in extension DRI3
    [ 14.759] Initializing built-in extension X-Resource
    [ 14.759] Initializing built-in extension XVideo
    [ 14.759] Initializing built-in extension XVideo-MotionCompensation
    [ 14.759] Initializing built-in extension XFree86-VidModeExtension
    [ 14.759] Initializing built-in extension XFree86-DGA
    [ 14.759] Initializing built-in extension XFree86-DRI
    [ 14.759] Initializing built-in extension DRI2
    [ 14.759] (II) LoadModule: "glx"
    [ 14.760] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 14.766] (II) Module glx: vendor="X.Org Foundation"
    [ 14.766] compiled for 1.15.0, module version = 1.0.0
    [ 14.766] ABI class: X.Org Server Extension, version 8.0
    [ 14.766] (==) AIGLX enabled
    [ 14.766] Loading extension GLX
    [ 14.766] (==) Matched nouveau as autoconfigured driver 0
    [ 14.766] (==) Matched nvidia as autoconfigured driver 1
    [ 14.766] (==) Matched nv as autoconfigured driver 2
    [ 14.766] (==) Matched nouveau as autoconfigured driver 3
    [ 14.766] (==) Matched nvidia as autoconfigured driver 4
    [ 14.766] (==) Matched nv as autoconfigured driver 5
    [ 14.766] (==) Matched nouveau as autoconfigured driver 6
    [ 14.766] (==) Matched nvidia as autoconfigured driver 7
    [ 14.766] (==) Matched nv as autoconfigured driver 8
    [ 14.766] (==) Matched modesetting as autoconfigured driver 9
    [ 14.766] (==) Matched fbdev as autoconfigured driver 10
    [ 14.766] (==) Matched vesa as autoconfigured driver 11
    [ 14.766] (==) Assigned the driver to the xf86ConfigLayout
    [ 14.766] (II) LoadModule: "nouveau"
    [ 14.766] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
    [ 14.767] (II) Module nouveau: vendor="X.Org Foundation"
    [ 14.767] compiled for 1.15.0, module version = 1.0.10
    [ 14.767] Module class: X.Org Video Driver
    [ 14.767] ABI class: X.Org Video Driver, version 15.0
    [ 14.767] (II) LoadModule: "nvidia"
    [ 14.768] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
    [ 14.777] (II) Module nvidia: vendor="NVIDIA Corporation"
    [ 14.777] compiled for 4.0.2, module version = 1.0.0
    [ 14.777] Module class: X.Org Video Driver
    [ 14.777] (II) LoadModule: "nv"
    [ 14.784] (WW) Warning, couldn't open module nv
    [ 14.784] (II) UnloadModule: "nv"
    [ 14.784] (II) Unloading nv
    [ 14.784] (EE) Failed to load module "nv" (module does not exist, 0)
    [ 14.784] (II) LoadModule: "modesetting"
    [ 14.784] (WW) Warning, couldn't open module modesetting
    [ 14.784] (II) UnloadModule: "modesetting"
    [ 14.784] (II) Unloading modesetting
    [ 14.784] (EE) Failed to load module "modesetting" (module does not exist, 0)
    [ 14.784] (II) LoadModule: "fbdev"
    [ 14.784] (WW) Warning, couldn't open module fbdev
    [ 14.784] (II) UnloadModule: "fbdev"
    [ 14.784] (II) Unloading fbdev
    [ 14.784] (EE) Failed to load module "fbdev" (module does not exist, 0)
    [ 14.784] (II) LoadModule: "vesa"
    [ 14.784] (WW) Warning, couldn't open module vesa
    [ 14.784] (II) UnloadModule: "vesa"
    [ 14.784] (II) Unloading vesa
    [ 14.784] (EE) Failed to load module "vesa" (module does not exist, 0)
    [ 14.784] (II) NOUVEAU driver
    [ 14.784] (II) NOUVEAU driver for NVIDIA chipset families :
    [ 14.784] RIVA TNT (NV04)
    [ 14.784] RIVA TNT2 (NV05)
    [ 14.784] GeForce 256 (NV10)
    [ 14.784] GeForce 2 (NV11, NV15)
    [ 14.784] GeForce 4MX (NV17, NV18)
    [ 14.784] GeForce 3 (NV20)
    [ 14.784] GeForce 4Ti (NV25, NV28)
    [ 14.784] GeForce FX (NV3x)
    [ 14.784] GeForce 6 (NV4x)
    [ 14.784] GeForce 7 (G7x)
    [ 14.784] GeForce 8 (G8x)
    [ 14.784] GeForce GTX 200 (NVA0)
    [ 14.784] GeForce GTX 400 (NVC0)
    [ 14.784] (II) NVIDIA dlloader X Driver 331.38 Wed Jan 8 18:51:00 PST 2014
    [ 14.784] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
    [ 14.784] (++) using VT number 1
    [ 14.784] (II) [drm] nouveau interface version: 1.1.1
    [ 14.785] (II) [drm] nouveau interface version: 1.1.1
    [ 14.785] (II) Loading sub module "dri2"
    [ 14.785] (II) LoadModule: "dri2"
    [ 14.785] (II) Module "dri2" already built-in
    [ 14.785] (--) NOUVEAU(0): Chipset: "NVIDIA NVC4"
    [ 14.785] (II) NOUVEAU(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
    [ 14.785] (==) NOUVEAU(0): Depth 24, (--) framebuffer bpp 32
    [ 14.785] (==) NOUVEAU(0): RGB weight 888
    [ 14.785] (==) NOUVEAU(0): Default visual is TrueColor
    [ 14.785] (==) NOUVEAU(0): Using HW cursor
    [ 14.785] (==) NOUVEAU(0): GLX sync to VBlank disabled.
    [ 14.785] (==) NOUVEAU(0): Page flipping enabled
    [ 14.785] (==) NOUVEAU(0): Swap limit set to 2 [Max allowed 2]
    [ 14.819] (II) NOUVEAU(0): Output DVI-I-1 has no monitor section
    [ 14.842] (II) NOUVEAU(0): Output DVI-I-2 has no monitor section
    [ 14.844] (II) NOUVEAU(0): Output HDMI-1 has no monitor section
    [ 14.874] (II) NOUVEAU(0): EDID for output DVI-I-1
    [ 14.874] (II) NOUVEAU(0): Manufacturer: GSM Model: 5678 Serial#: 95359
    [ 14.874] (II) NOUVEAU(0): Year: 2010 Week: 6
    [ 14.874] (II) NOUVEAU(0): EDID Version: 1.3
    [ 14.874] (II) NOUVEAU(0): Digital Display Input
    [ 14.874] (II) NOUVEAU(0): Max Image Size [cm]: horiz.: 49 vert.: 32
    [ 14.874] (II) NOUVEAU(0): Gamma: 2.20
    [ 14.874] (II) NOUVEAU(0): DPMS capabilities: StandBy Suspend Off
    [ 14.874] (II) NOUVEAU(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
    [ 14.874] (II) NOUVEAU(0): First detailed timing is preferred mode
    [ 14.874] (II) NOUVEAU(0): redX: 0.635 redY: 0.342 greenX: 0.292 greenY: 0.611
    [ 14.874] (II) NOUVEAU(0): blueX: 0.147 blueY: 0.070 whiteX: 0.313 whiteY: 0.329
    [ 14.874] (II) NOUVEAU(0): Supported established timings:
    [ 14.874] (II) NOUVEAU(0): 720x400@70Hz
    [ 14.874] (II) NOUVEAU(0): 640x480@60Hz
    [ 14.874] (II) NOUVEAU(0): 640x480@75Hz
    [ 14.874] (II) NOUVEAU(0): 800x600@56Hz
    [ 14.874] (II) NOUVEAU(0): 800x600@60Hz
    [ 14.874] (II) NOUVEAU(0): 800x600@75Hz
    [ 14.874] (II) NOUVEAU(0): 832x624@75Hz
    [ 14.874] (II) NOUVEAU(0): 1024x768@60Hz
    [ 14.874] (II) NOUVEAU(0): 1024x768@75Hz
    [ 14.874] (II) NOUVEAU(0): 1280x1024@75Hz
    [ 14.874] (II) NOUVEAU(0): 1152x864@75Hz
    [ 14.874] (II) NOUVEAU(0): Manufacturer's mask: 0
    [ 14.874] (II) NOUVEAU(0): Supported standard timings:
    [ 14.874] (II) NOUVEAU(0): #0: hsize: 1440 vsize 900 refresh: 60 vid: 149
    [ 14.874] (II) NOUVEAU(0): #1: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
    [ 14.874] (II) NOUVEAU(0): #2: hsize: 1280 vsize 960 refresh: 60 vid: 16513
    [ 14.874] (II) NOUVEAU(0): #3: hsize: 1152 vsize 864 refresh: 75 vid: 20337
    [ 14.874] (II) NOUVEAU(0): Supported detailed timing:
    [ 14.874] (II) NOUVEAU(0): clock: 119.0 MHz Image Size: 474 x 296 mm
    [ 14.874] (II) NOUVEAU(0): h_active: 1680 h_sync: 1728 h_sync_end 1760 h_blank_end 1840 h_border: 0
    [ 14.874] (II) NOUVEAU(0): v_active: 1050 v_sync: 1053 v_sync_end 1059 v_blanking: 1080 v_border: 0
    [ 14.874] (II) NOUVEAU(0): Supported detailed timing:
    [ 14.874] (II) NOUVEAU(0): clock: 146.2 MHz Image Size: 474 x 296 mm
    [ 14.874] (II) NOUVEAU(0): h_active: 1680 h_sync: 1784 h_sync_end 1960 h_blank_end 2240 h_border: 0
    [ 14.874] (II) NOUVEAU(0): v_active: 1050 v_sync: 1053 v_sync_end 1059 v_blanking: 1089 v_border: 0
    [ 14.874] (II) NOUVEAU(0): Ranges: V min: 56 V max: 75 Hz, H min: 30 H max: 83 kHz, PixClock max 155 MHz
    [ 14.874] (II) NOUVEAU(0): Monitor name: W2242
    [ 14.874] (II) NOUVEAU(0): EDID (in hex):
    [ 14.874] (II) NOUVEAU(0): 00ffffffffffff001e6d78567f740100
    [ 14.874] (II) NOUVEAU(0): 06140103ea312078eaaec5a2574a9c25
    [ 14.874] (II) NOUVEAU(0): 125054a76b80950081808140714f0101
    [ 14.874] (II) NOUVEAU(0): 0101010101017c2e90a0601a1e403020
    [ 14.874] (II) NOUVEAU(0): 3600da281100001a21399030621a2740
    [ 14.874] (II) NOUVEAU(0): 68b03600da281100001c000000fd0038
    [ 14.874] (II) NOUVEAU(0): 4b1e530f000a202020202020000000fc
    [ 14.874] (II) NOUVEAU(0): 0057323234320a202020202020200070
    [ 14.874] (II) NOUVEAU(0): Printing probed modes for output DVI-I-1
    [ 14.874] (II) NOUVEAU(0): Modeline "1680x1050"x59.9 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz eP)
    [ 14.874] (II) NOUVEAU(0): Modeline "1680x1050"x60.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz e)
    [ 14.874] (II) NOUVEAU(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 14.874] (II) NOUVEAU(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [ 14.874] (II) NOUVEAU(0): Modeline "1440x900"x59.9 88.75 1440 1488 1520 1600 900 903 909 926 +hsync -vsync (55.5 kHz e)
    [ 14.874] (II) NOUVEAU(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 14.874] (II) NOUVEAU(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 14.874] (II) NOUVEAU(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
    [ 14.874] (II) NOUVEAU(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 14.874] (II) NOUVEAU(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
    [ 14.874] (II) NOUVEAU(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 14.874] (II) NOUVEAU(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 14.874] (II) NOUVEAU(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 14.874] (II) NOUVEAU(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 14.874] (II) NOUVEAU(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 14.874] (II) NOUVEAU(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 14.897] (II) NOUVEAU(0): EDID for output DVI-I-2
    [ 14.899] (II) NOUVEAU(0): EDID for output HDMI-1
    [ 14.899] (II) NOUVEAU(0): Output DVI-I-1 connected
    [ 14.899] (II) NOUVEAU(0): Output DVI-I-2 disconnected
    [ 14.899] (II) NOUVEAU(0): Output HDMI-1 disconnected
    [ 14.899] (II) NOUVEAU(0): Using exact sizes for initial modes
    [ 14.899] (II) NOUVEAU(0): Output DVI-I-1 using initial mode 1680x1050
    [ 14.899] (II) NOUVEAU(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
    [ 14.899] (--) NOUVEAU(0): Virtual size is 1680x1050 (pitch 0)
    [ 14.899] (**) NOUVEAU(0): Driver mode "1680x1050": 119.0 MHz (scaled from 0.0 MHz), 64.7 kHz, 59.9 Hz
    [ 14.899] (II) NOUVEAU(0): Modeline "1680x1050"x59.9 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz eP)
    [ 14.899] (**) NOUVEAU(0): Driver mode "1680x1050": 146.2 MHz (scaled from 0.0 MHz), 65.3 kHz, 60.0 Hz
    [ 14.899] (II) NOUVEAU(0): Modeline "1680x1050"x60.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz e)
    [ 14.899] (**) NOUVEAU(0): Driver mode "1280x1024": 135.0 MHz (scaled from 0.0 MHz), 80.0 kHz, 75.0 Hz
    [ 14.899] (II) NOUVEAU(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 14.899] (**) NOUVEAU(0): Driver mode "1280x1024": 108.0 MHz (scaled from 0.0 MHz), 64.0 kHz, 60.0 Hz
    [ 14.899] (II) NOUVEAU(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [ 14.899] (**) NOUVEAU(0): Driver mode "1440x900": 88.8 MHz (scaled from 0.0 MHz), 55.5 kHz, 59.9 Hz
    [ 14.899] (II) NOUVEAU(0): Modeline "1440x900"x59.9 88.75 1440 1488 1520 1600 900 903 909 926 +hsync -vsync (55.5 kHz e)
    [ 14.899] (**) NOUVEAU(0): Driver mode "1280x960": 108.0 MHz (scaled from 0.0 MHz), 60.0 kHz, 60.0 Hz
    [ 14.899] (II) NOUVEAU(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 14.899] (**) NOUVEAU(0): Driver mode "1152x864": 108.0 MHz (scaled from 0.0 MHz), 67.5 kHz, 75.0 Hz
    [ 14.899] (II) NOUVEAU(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 14.899] (**) NOUVEAU(0): Driver mode "1024x768": 78.8 MHz (scaled from 0.0 MHz), 60.1 kHz, 75.1 Hz
    [ 14.899] (II) NOUVEAU(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
    [ 14.899] (**) NOUVEAU(0): Driver mode "1024x768": 65.0 MHz (scaled from 0.0 MHz), 48.4 kHz, 60.0 Hz
    [ 14.899] (II) NOUVEAU(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 14.899] (**) NOUVEAU(0): Driver mode "832x624": 57.3 MHz (scaled from 0.0 MHz), 49.7 kHz, 74.6 Hz
    [ 14.899] (II) NOUVEAU(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
    [ 14.899] (**) NOUVEAU(0): Driver mode "800x600": 49.5 MHz (scaled from 0.0 MHz), 46.9 kHz, 75.0 Hz
    [ 14.899] (II) NOUVEAU(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 14.899] (**) NOUVEAU(0): Driver mode "800x600": 40.0 MHz (scaled from 0.0 MHz), 37.9 kHz, 60.3 Hz
    [ 14.899] (II) NOUVEAU(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 14.899] (**) NOUVEAU(0): Driver mode "800x600": 36.0 MHz (scaled from 0.0 MHz), 35.2 kHz, 56.2 Hz
    [ 14.899] (II) NOUVEAU(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 14.899] (**) NOUVEAU(0): Driver mode "640x480": 31.5 MHz (scaled from 0.0 MHz), 37.5 kHz, 75.0 Hz
    [ 14.899] (II) NOUVEAU(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 14.899] (**) NOUVEAU(0): Driver mode "640x480": 25.2 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
    [ 14.899] (II) NOUVEAU(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 14.899] (**) NOUVEAU(0): Driver mode "720x400": 28.3 MHz (scaled from 0.0 MHz), 31.5 kHz, 70.1 Hz
    [ 14.899] (II) NOUVEAU(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 14.899] (==) NOUVEAU(0): DPI set to (96, 96)
    [ 14.899] (II) Loading sub module "fb"
    [ 14.899] (II) LoadModule: "fb"
    [ 14.899] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 14.901] (II) Module fb: vendor="X.Org Foundation"
    [ 14.901] compiled for 1.15.0, module version = 1.0.0
    [ 14.901] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 14.901] (II) Loading sub module "exa"
    [ 14.901] (II) LoadModule: "exa"
    [ 14.901] (II) Loading /usr/lib/xorg/modules/libexa.so
    [ 14.901] (II) Module exa: vendor="X.Org Foundation"
    [ 14.901] compiled for 1.15.0, module version = 2.6.0
    [ 14.901] ABI class: X.Org Video Driver, version 15.0
    [ 14.901] (II) Loading sub module "shadowfb"
    [ 14.901] (II) LoadModule: "shadowfb"
    [ 14.901] (II) Loading /usr/lib/xorg/modules/libshadowfb.so
    [ 14.902] (II) Module shadowfb: vendor="X.Org Foundation"
    [ 14.902] compiled for 1.15.0, module version = 1.0.0
    [ 14.902] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 14.902] (II) Loading sub module "dri2"
    [ 14.902] (II) LoadModule: "dri2"
    [ 14.902] (II) Module "dri2" already built-in
    [ 14.902] (--) NOUVEAU(G0): Chipset: "NVIDIA NVC4"
    [ 14.902] (==) NOUVEAU(G0): Depth 24, (--) framebuffer bpp 32
    [ 14.902] (==) NOUVEAU(G0): RGB weight 888
    [ 14.902] (==) NOUVEAU(G0): Default visual is TrueColor
    [ 14.902] (==) NOUVEAU(G0): Using HW cursor
    [ 14.902] (==) NOUVEAU(G0): GLX sync to VBlank disabled.
    [ 14.902] (==) NOUVEAU(G0): Page flipping enabled
    [ 14.902] (==) NOUVEAU(G0): Swap limit set to 2 [Max allowed 2]
    [ 14.929] (II) NOUVEAU(G0): Output DVI-I-1-3 has no monitor section
    [ 14.952] (II) NOUVEAU(G0): Output DVI-I-1-4 has no monitor section
    [ 14.954] (II) NOUVEAU(G0): Output HDMI-1-2 has no monitor section
    [ 14.977] (II) NOUVEAU(G0): EDID for output DVI-I-1-3
    [ 15.000] (II) NOUVEAU(G0): EDID for output DVI-I-1-4
    [ 15.002] (II) NOUVEAU(G0): EDID for output HDMI-1-2
    [ 15.002] (II) NOUVEAU(G0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
    [ 15.002] (--) NOUVEAU(G0): Virtual size is 1024x768 (pitch 0)
    [ 15.002] (**) NOUVEAU(G0): Mode "1680x1050": 146.2 MHz (scaled from 0.0 MHz), 65.3 kHz, 60.0 Hz
    [ 15.002] (II) NOUVEAU(G0): Modeline "1680x1050"x60.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz)
    [ 15.002] (==) NOUVEAU(G0): DPI set to (96, 96)
    [ 15.002] (II) Loading sub module "fb"
    [ 15.002] (II) LoadModule: "fb"
    [ 15.002] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 15.002] (II) Module fb: vendor="X.Org Foundation"
    [ 15.002] compiled for 1.15.0, module version = 1.0.0
    [ 15.002] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 15.002] (II) Loading sub module "exa"
    [ 15.002] (II) LoadModule: "exa"
    [ 15.002] (II) Loading /usr/lib/xorg/modules/libexa.so
    [ 15.002] (II) Module exa: vendor="X.Org Foundation"
    [ 15.002] compiled for 1.15.0, module version = 2.6.0
    [ 15.002] ABI class: X.Org Video Driver, version 15.0
    [ 15.002] (II) Loading sub module "shadowfb"
    [ 15.002] (II) LoadModule: "shadowfb"
    [ 15.003] (II) Loading /usr/lib/xorg/modules/libshadowfb.so
    [ 15.003] (II) Module shadowfb: vendor="X.Org Foundation"
    [ 15.003] compiled for 1.15.0, module version = 1.0.0
    [ 15.003] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 15.003] (II) UnloadModule: "nvidia"
    [ 15.003] (II) Unloading nvidia
    [ 15.003] (--) Depth 24 pixmap format is 32 bpp
    [ 15.004] (II) NOUVEAU(G0): Opened GPU channel 0
    [ 15.010] (II) NOUVEAU(G0): [DRI2] Setup complete
    [ 15.010] (II) NOUVEAU(G0): [DRI2] DRI driver: nouveau
    [ 15.010] (II) NOUVEAU(G0): [DRI2] VDPAU driver: nouveau
    [ 15.010] (II) EXA(256): Driver allocated offscreen pixmaps
    [ 15.010] (II) EXA(256): Driver registered support for the following operations:
    [ 15.010] (II) Solid
    [ 15.010] (II) Copy
    [ 15.010] (II) Composite (RENDER acceleration)
    [ 15.010] (II) UploadToScreen
    [ 15.010] (II) DownloadFromScreen
    [ 15.010] (==) NOUVEAU(G0): Backing store enabled
    [ 15.010] (==) NOUVEAU(G0): Silken mouse enabled
    [ 15.010] (II) NOUVEAU(G0): [XvMC] Associated with Nouveau GeForce 8/9 Textured Video.
    [ 15.010] (II) NOUVEAU(G0): [XvMC] Extension initialized.
    [ 15.010] (==) NOUVEAU(G0): DPMS enabled
    [ 15.010] (II) NOUVEAU(G0): RandR 1.2 enabled, ignore the following RandR disabled message.
    [ 15.012] (II) NOUVEAU(0): Opened GPU channel 0
    [ 15.018] (II) NOUVEAU(0): [DRI2] Setup complete
    [ 15.018] (II) NOUVEAU(0): [DRI2] DRI driver: nouveau
    [ 15.018] (II) NOUVEAU(0): [DRI2] VDPAU driver: nouveau
    [ 15.018] (II) EXA(0): Driver allocated offscreen pixmaps
    [ 15.018] (II) EXA(0): Driver registered support for the following operations:
    [ 15.018] (II) Solid
    [ 15.018] (II) Copy
    [ 15.018] (II) Composite (RENDER acceleration)
    [ 15.018] (II) UploadToScreen
    [ 15.018] (II) DownloadFromScreen
    [ 15.018] (==) NOUVEAU(0): Backing store enabled
    [ 15.018] (==) NOUVEAU(0): Silken mouse enabled
    [ 15.018] (II) NOUVEAU(0): [XvMC] Associated with Nouveau GeForce 8/9 Textured Video.
    [ 15.018] (II) NOUVEAU(0): [XvMC] Extension initialized.
    [ 15.018] (==) NOUVEAU(0): DPMS enabled
    [ 15.018] (II) NOUVEAU(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    [ 15.018] (--) RandR disabled
    [ 15.092] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
    [ 15.092] (II) AIGLX: enabled GLX_ARB_create_context
    [ 15.092] (II) AIGLX: enabled GLX_ARB_create_context_profile
    [ 15.092] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
    [ 15.092] (II) AIGLX: enabled GLX_INTEL_swap_event
    [ 15.092] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
    [ 15.092] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
    [ 15.092] (II) AIGLX: enabled GLX_ARB_fbconfig_float
    [ 15.092] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
    [ 15.092] (II) AIGLX: Loaded and initialized nouveau
    [ 15.092] (II) GLX: Initialized DRI2 GL provider for screen 0
    [ 15.097] (II) NOUVEAU(G0): NVEnterVT is called.
    [ 15.100] (II) NOUVEAU(0): NVEnterVT is called.
    [ 15.126] (II) NOUVEAU(0): Setting screen physical size to 444 x 277
    [ 15.126] resize called 1680 1050
    [ 15.151] (II) config/udev: Adding input device Power Button (/dev/input/event5)
    [ 15.151] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 15.151] (II) LoadModule: "evdev"
    [ 15.151] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 15.152] (II) Module evdev: vendor="X.Org Foundation"
    [ 15.152] compiled for 1.15.0, module version = 2.8.2
    [ 15.152] Module class: X.Org XInput Driver
    [ 15.152] ABI class: X.Org XInput driver, version 20.0
    [ 15.152] (II) Using input driver 'evdev' for 'Power Button'
    [ 15.152] (**) Power Button: always reports core events
    [ 15.152] (**) evdev: Power Button: Device: "/dev/input/event5"
    [ 15.152] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 15.152] (--) evdev: Power Button: Found keys
    [ 15.152] (II) evdev: Power Button: Configuring as keyboard
    [ 15.152] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input7/event5"
    [ 15.152] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    [ 15.152] (**) Option "xkb_rules" "evdev"
    [ 15.152] (**) Option "xkb_model" "pc104"
    [ 15.152] (**) Option "xkb_layout" "us"
    [ 15.161] (II) config/udev: Adding input device Power Button (/dev/input/event4)
    [ 15.161] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 15.161] (II) Using input driver 'evdev' for 'Power Button'
    [ 15.161] (**) Power Button: always reports core events
    [ 15.161] (**) evdev: Power Button: Device: "/dev/input/event4"
    [ 15.161] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 15.161] (--) evdev: Power Button: Found keys
    [ 15.161] (II) evdev: Power Button: Configuring as keyboard
    [ 15.161] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input6/event4"
    [ 15.161] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
    [ 15.161] (**) Option "xkb_rules" "evdev"
    [ 15.161] (**) Option "xkb_model" "pc104"
    [ 15.161] (**) Option "xkb_layout" "us"
    [ 15.161] (II) config/udev: Adding drm device (/dev/dri/card0)
    [ 15.161] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event20)
    [ 15.161] (II) No input driver specified, ignoring this device.
    [ 15.161] (II) This device may have been added with another device file.
    [ 15.161] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event19)
    [ 15.161] (II) No input driver specified, ignoring this device.
    [ 15.161] (II) This device may have been added with another device file.
    [ 15.161] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event18)
    [ 15.161] (II) No input driver specified, ignoring this device.
    [ 15.161] (II) This device may have been added with another device file.
    [ 15.162] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event17)
    [ 15.162] (II) No input driver specified, ignoring this device.
    [ 15.162] (II) This device may have been added with another device file.
    [ 15.162] (II) config/udev: Adding drm device (/dev/dri/card1)
    [ 15.162] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event24)
    [ 15.162] (II) No input driver specified, ignoring this device.
    [ 15.162] (II) This device may have been added with another device file.
    [ 15.162] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event23)
    [ 15.162] (II) No input driver specified, ignoring this device.
    [ 15.162] (II) This device may have been added with another device file.
    [ 15.162] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event22)
    [ 15.162] (II) No input driver specified, ignoring this device.
    [ 15.162] (II) This device may have been added with another device file.
    [ 15.162] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event21)
    [ 15.162] (II) No input driver specified, ignoring this device.
    [ 15.162] (II) This device may have been added with another device file.
    [ 15.162] (II) config/udev: Adding input device Gaming Keyboard (/dev/input/event1)
    [ 15.162] (**) Gaming Keyboard: Applying InputClass "evdev keyboard catchall"
    [ 15.162] (II) Using input driver 'evdev' for 'Gaming Keyboard'
    [ 15.162] (**) Gaming Keyboard: always reports core events
    [ 15.162] (**) evdev: Gaming Keyboard: Device: "/dev/input/event1"
    [ 15.162] (--) evdev: Gaming Keyboard: Vendor 0x46d Product 0xc221
    [ 15.162] (--) evdev: Gaming Keyboard: Found keys
    [ 15.162] (II) evdev: Gaming Keyboard: Configuring as keyboard
    [ 15.162] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-13/1-13.1/1-13.1:1.0/input/input3/event1"
    [ 15.162] (II) XINPUT: Adding extended input device "Gaming Keyboard" (type: KEYBOARD, id 8)
    [ 15.162] (**) Option "xkb_rules" "evdev"
    [ 15.162] (**) Option "xkb_model" "pc104"
    [ 15.162] (**) Option "xkb_layout" "us"
    [ 15.162] (II) config/udev: Adding input device Gaming Keyboard (/dev/input/event2)
    [ 15.162] (**) Gaming Keyboard: Applying InputClass "evdev keyboard catchall"
    [ 15.162] (II) Using input driver 'evdev' for 'Gaming Keyboard'
    [ 15.162] (**) Gaming Keyboard: always reports core events
    [ 15.162] (**) evdev: Gaming Keyboard: Device: "/dev/input/event2"
    [ 15.162] (--) evdev: Gaming Keyboard: Vendor 0x46d Product 0xc221
    [ 15.162] (--) evdev: Gaming Keyboard: Found keys
    [ 15.162] (II) evdev: Gaming Keyboard: Configuring as keyboard
    [ 15.162] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-13/1-13.1/1-13.1:1.1/input/input4/event2"
    [ 15.162] (II) XINPUT: Adding extended input device "Gaming Keyboard" (type: KEYBOARD, id 9)
    [ 15.162] (**) Option "xkb_rules" "evdev"
    [ 15.162] (**) Option "xkb_model" "pc104"
    [ 15.162] (**) Option "xkb_layout" "us"
    [ 15.163] (II) config/udev: Adding input device G11 Keyboard (/dev/input/event3)
    [ 15.163] (**) G11 Keyboard: Applying InputClass "evdev keyboard catchall"
    [ 15.163] (II) Using input driver 'evdev' for 'G11 Keyboard'
    [ 15.163] (**) G11 Keyboard: always reports core events
    [ 15.163] (**) evdev: G11 Keyboard: Device: "/dev/input/event3"
    [ 15.163] (--) evdev: G11 Keyboard: Vendor 0x46d Product 0xc225
    [ 15.163] (--) evdev: G11 Keyboard: Found keys
    [ 15.163] (II) evdev: G11 Keyboard: Configuring as keyboard
    [ 15.163] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-13/1-13.4/1-13.4:1.0/input/input5/event3"
    [ 15.163] (II) XINPUT: Adding extended input device "G11 Keyboard" (type: KEYBOARD, id 10)
    [ 15.163] (**) Option "xkb_rules" "evdev"
    [ 15.163] (**) Option "xkb_model" "pc104"
    [ 15.163] (**) Option "xkb_layout" "us"
    [ 15.163] (II) config/udev: Adding input device Saitek Cyborg R.A.T.7 Albino (/dev/input/event0)
    [ 15.163] (**) Saitek Cyborg R.A.T.7 Albino: Applying InputClass "evdev pointer catchall"
    [ 15.163] (II) Using input driver 'evdev' for 'Saitek Cyborg R.A.T.7 Albino'
    [ 15.163] (**) Saitek Cyborg R.A.T.7 Albino: always reports core events
    [ 15.163] (**) evdev: Saitek Cyborg R.A.T.7 Albino: Device: "/dev/input/event0"
    [ 15.163] (--) evdev: Saitek Cyborg R.A.T.7 Albino: Vendor 0x6a3 Product 0xcce
    [ 15.163] (--) evdev: Saitek Cyborg R.A.T.7 Albino: Found 17 mouse buttons
    [ 15.163] (--) evdev: Saitek Cyborg R.A.T.7 Albino: Found scroll wheel(s)
    [ 15.163] (--) evdev: Saitek Cyborg R.A.T.7 Albino: Found relative axes
    [ 15.163] (--) evdev: Saitek Cyborg R.A.T.7 Albino: Found x and y relative axes
    [ 15.163] (II) evdev: Saitek Cyborg R.A.T.7 Albino: Configuring as mouse
    [ 15.163] (II) evdev: Saitek Cyborg R.A.T.7 Albino: Adding scrollwheel support
    [ 15.163] (**) evdev: Saitek Cyborg R.A.T.7 Albino: YAxisMapping: buttons 4 and 5
    [ 15.163] (**) evdev: Saitek Cyborg R.A.T.7 Albino: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 15.163] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-14/1-14:1.0/input/input2/event0"
    [ 15.163] (II) XINPUT: Adding extended input device "Saitek Cyborg R.A.T.7 Albino" (type: MOUSE, id 11)
    [ 15.163] (II) evdev: Saitek Cyborg R.A.T.7 Albino: initialized for relative axes.
    [ 15.163] (**) Saitek Cyborg R.A.T.7 Albino: (accel) keeping acceleration scheme 1
    [ 15.163] (**) Saitek Cyborg R.A.T.7 Albino: (accel) acceleration profile 0
    [ 15.163] (**) Saitek Cyborg R.A.T.7 Albino: (accel) acceleration factor: 2.000
    [ 15.163] (**) Saitek Cyborg R.A.T.7 Albino: (accel) acceleration threshold: 4
    [ 15.163] (II) config/udev: Adding input device Saitek Cyborg R.A.T.7 Albino (/dev/input/mouse0)
    [ 15.163] (II) No input driver specified, ignoring this device.
    [ 15.163] (II) This device may have been added with another device file.
    [ 15.163] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event8)
    [ 15.163] (II) No input driver specified, ignoring this device.
    [ 15.163] (II) This device may have been added with another device file.
    [ 15.163] (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event16)
    [ 15.163] (II) No input driver specified, ignoring this device.
    [ 15.163] (II) This device may have been added with another device file.
    [ 15.163] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event15)
    [ 15.163] (II) No input driver specified, ignoring this device.
    [ 15.163] (II) This device may have been added with another device file.
    [ 15.164] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event14)
    [ 15.164] (II) No input driver specified, ignoring this device.
    [ 15.164] (II) This device may have been added with another device file.
    [ 15.164] (II) config/udev: Adding input device HDA Intel PCH Line Out Front (/dev/input/event13)
    [ 15.164] (II) No input driver specified, ignoring this device.
    [ 15.164] (II) This device may have been added with another device file.
    [ 15.164] (II) config/udev: Adding input device HDA Intel PCH Line Out Surround (/dev/input/event12)
    [ 15.164] (II) No input driver specified, ignoring this device.
    [ 15.164] (II) This device may have been added with another device file.
    [ 15.164] (II) config/udev: Adding input device HDA Intel PCH Line Out CLFE (/dev/input/event11)
    [ 15.164] (II) No input driver specified, ignoring this device.
    [ 15.164] (II) This device may have been added with another device file.
    [ 15.164] (II) config/udev: Adding input device HDA Intel PCH Line Out Side (/dev/input/event10)
    [ 15.164] (II) No input driver specified, ignoring this device.
    [ 15.164] (II) This device may have been added with another device file.
    [ 15.164] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event9)
    [ 15.164] (II) No input driver specified, ignoring this device.
    [ 15.164] (II) This device may have been added with another device file.
    [ 15.164] (II) config/udev: Adding input device Eee PC WMI hotkeys (/dev/input/event7)
    [ 15.164] (**) Eee PC WMI hotkeys: Applying InputClass "evdev keyboard catchall"
    [ 15.164] (II) Using input driver 'evdev' for 'Eee PC WMI hotkeys'
    [ 15.164] (**) Eee PC WMI hotkeys: always reports core events
    [ 15.164] (**) evdev: Eee PC WMI hotkeys: Device: "/dev/input/event7"
    [ 15.164] (--) evdev: Eee PC WMI hotkeys: Vendor 0 Product 0
    [ 15.164] (--) evdev: Eee PC WMI hotkeys: Found keys
    [ 15.164] (II) evdev: Eee PC WMI hotkeys: Configuring as keyboard
    [ 15.164] (**) Option "config_info" "udev:/sys/devices/platform/eeepc-wmi/input/input10/event7"
    [ 15.164] (II) XINPUT: Adding extended input device "Eee PC WMI hotkeys" (type: KEYBOARD, id 12)
    [ 15.164] (**) Option "xkb_rules" "evdev"
    [ 15.164] (**) Option "xkb_model" "pc104"
    [ 15.164] (**) Option "xkb_layout" "us"
    [ 15.164] (II) config/udev: Adding input device PC Speaker (/dev/input/event6)
    [ 15.164] (II) No input driver specified, ignoring this device.
    [ 15.164] (II) This device may have been added with another device file.
    [ 15.227] (II) NOUVEAU(0): EDID vendor "GSM", prod id 22136
    [ 15.227] (II) NOUVEAU(0): Using EDID range info for horizontal sync
    [ 15.227] (II) NOUVEAU(0): Using EDID range info for vertical refresh
    [ 15.227] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 15.227] (II) NOUVEAU(0): Modeline "1680x1050"x0.0 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz eP)
    [ 15.227] (II) NOUVEAU(0): Modeline "1680x1050"x0.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz e)
    [ 15.227] (II) NOUVEAU(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 15.227] (II) NOUVEAU(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 15.227] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 15.227] (II) NOUVEAU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 15.227] (II) NOUVEAU(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 15.227] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 15.227] (II) NOUVEAU(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
    [ 15.227] (II) NOUVEAU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 15.227] (II) NOUVEAU(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
    [ 15.227] (II) NOUVEAU(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 15.227] (II) NOUVEAU(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 15.227] (II) NOUVEAU(0): Modeline "1440x900"x0.0 88.75 1440 1488 1520 1600 900 903 909 926 +hsync -vsync (55.5 kHz e)
    [ 15.227] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [ 15.227] (II) NOUVEAU(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 69.523] (II) evdev: Eee PC WMI hotkeys: Close
    [ 69.523] (II) UnloadModule: "evdev"
    [ 69.523] (II) evdev: Saitek Cyborg R.A.T.7 Albino: Close
    [ 69.523] (II) UnloadModule: "evdev"
    [ 69.523] (II) evdev: G11 Keyboard: Close
    [ 69.523] (II) UnloadModule: "evdev"
    [ 69.523] (II) evdev: Gaming Keyboard: Close
    [ 69.523] (II) UnloadModule: "evdev"
    [ 69.523] (II) evdev: Gaming Keyboard: Close
    [ 69.523] (II) UnloadModule: "evdev"
    [ 69.523] (II) evdev: Power Button: Close
    [ 69.523] (II) UnloadModule: "evdev"
    [ 69.523] (II) evdev: Power Button: Close
    [ 69.523] (II) UnloadModule: "evdev"
    [ 69.523] (II) NOUVEAU(G0): NVLeaveVT is called.
    [ 69.523] Error dropping master: -22(Invalid argument)
    [ 69.523] (II) NOUVEAU(G0): Closed GPU channel 0
    [ 69.525] (II) NOUVEAU(0): NVLeaveVT is called.
    [ 69.526] (II) NOUVEAU(0): Closed GPU channel 0
    [ 69.558] (EE) Server terminated successfully (0). Closing log file.
    Xorg.0.log (after restarting X, everything works fine!)
    X.Org X Server 1.15.0
    Release Date: 2013-12-27
    [ 80.293] X Protocol Version 11, Revision 0
    [ 80.295] Build Operating System: Linux 3.12.5-1-ARCH x86_64
    [ 80.296] Current Operating System: Linux wasteland 3.12.9-2-ARCH #1 SMP PREEMPT Fri Jan 31 10:22:54 CET 2014 x86_64
    [ 80.296] Kernel command line: vmlinuz-linux initrd=initramfs-linux.img root=/dev/mapper/root cryptdevice=/dev/sda2:root:allow-discards ro
    [ 80.299] Build Date: 09 January 2014 08:47:24AM
    [ 80.301]
    [ 80.303] Current version of pixman: 0.32.4
    [ 80.306] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 80.306] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 80.314] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Feb 17 14:31:44 2014
    [ 80.315] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 80.315] (==) No Layout section. Using the first Screen section.
    [ 80.315] (==) No screen section available. Using defaults.
    [ 80.315] (**) |-->Screen "Default Screen Section" (0)
    [ 80.315] (**) | |-->Monitor "<default monitor>"
    [ 80.315] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    [ 80.315] (==) Automatically adding devices
    [ 80.315] (==) Automatically enabling devices
    [ 80.315] (==) Automatically adding GPU devices
    [ 80.315] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [ 80.315] Entry deleted from font path.
    [ 80.315] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/Type1/,
    /usr/share/fonts/100dpi/,
    /usr/share/fonts/75dpi/
    [ 80.315] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 80.315] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 80.315] (II) Loader magic: 0x804c80
    [ 80.315] (II) Module ABI versions:
    [ 80.315] X.Org ANSI C Emulation: 0.4
    [ 80.315] X.Org Video Driver: 15.0
    [ 80.315] X.Org XInput driver : 20.0
    [ 80.315] X.Org Server Extension : 8.0
    [ 80.316] (II) xfree86: Adding drm device (/dev/dri/card0)
    [ 80.316] (II) xfree86: Adding drm device (/dev/dri/card1)
    [ 80.316] (--) PCI:*(0:1:0:0) 10de:0e22:1458:34fc rev 161, Mem @ 0xf4000000/33554432, 0xe8000000/134217728, 0xf0000000/67108864, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
    [ 80.316] (--) PCI: (0:2:0:0) 10de:0e22:1458:34fc rev 161, Mem @ 0xe4000000/33554432, 0xd8000000/134217728, 0xe0000000/67108864, I/O @ 0x0000d000/128, BIOS @ 0x????????/524288
    [ 80.316] (II) Open ACPI successful (/var/run/acpid.socket)
    [ 80.317] Initializing built-in extension Generic Event Extension
    [ 80.319] Initializing built-in extension SHAPE
    [ 80.320] Initializing built-in extension MIT-SHM
    [ 80.322] Initializing built-in extension XInputExtension
    [ 80.324] Initializing built-in extension XTEST
    [ 80.325] Initializing built-in extension BIG-REQUESTS
    [ 80.327] Initializing built-in extension SYNC
    [ 80.328] Initializing built-in extension XKEYBOARD
    [ 80.330] Initializing built-in extension XC-MISC
    [ 80.331] Initializing built-in extension SECURITY
    [ 80.332] Initializing built-in extension XINERAMA
    [ 80.334] Initializing built-in extension XFIXES
    [ 80.335] Initializing built-in extension RENDER
    [ 80.337] Initializing built-in extension RANDR
    [ 80.338] Initializing built-in extension COMPOSITE
    [ 80.340] Initializing built-in extension DAMAGE
    [ 80.341] Initializing built-in extension MIT-SCREEN-SAVER
    [ 80.342] Initializing built-in extension DOUBLE-BUFFER
    [ 80.344] Initializing built-in extension RECORD
    [ 80.345] Initializing built-in extension DPMS
    [ 80.347] Initializing built-in extension Present
    [ 80.348] Initializing built-in extension DRI3
    [ 80.349] Initializing built-in extension X-Resource
    [ 80.351] Initializing built-in extension XVideo
    [ 80.352] Initializing built-in extension XVideo-MotionCompensation
    [ 80.354] Initializing built-in extension XFree86-VidModeExtension
    [ 80.355] Initializing built-in extension XFree86-DGA
    [ 80.357] Initializing built-in extension XFree86-DRI
    [ 80.358] Initializing built-in extension DRI2
    [ 80.358] (II) LoadModule: "glx"
    [ 80.358] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 80.359] (II) Module glx: vendor="X.Org Foundation"
    [ 80.359] compiled for 1.15.0, module version = 1.0.0
    [ 80.359] ABI class: X.Org Server Extension, version 8.0
    [ 80.359] (==) AIGLX enabled
    [ 80.359] Loading extension GLX
    [ 80.360] (==) Matched nouveau as autoconfigured driver 0
    [ 80.360] (==) Matched nvidia as autoconfigured driver 1
    [ 80.360] (==) Matched nv as autoconfigured driver 2
    [ 80.360] (==) Matched nouveau as autoconfigured driver 3
    [ 80.360] (==) Matched nvidia as autoconfigured driver 4
    [ 80.360] (==) Matched nv as autoconfigured driver 5
    [ 80.360] (==) Matched modesetting as autoconfigured driver 6
    [ 80.360] (==) Matched fbdev as autoconfigured driver 7
    [ 80.360] (==) Matched vesa as autoconfigured driver 8
    [ 80.360] (==) Assigned the driver to the xf86ConfigLayout
    [ 80.360] (II) LoadModule: "nouveau"
    [ 80.360] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
    [ 80.360] (II) Module nouveau: vendor="X.Org Foundation"
    [ 80.360] compiled for 1.15.0, module version = 1.0.10
    [ 80.360] Module class: X.Org Video Driver
    [ 80.360] ABI class: X.Org Video Driver, version 15.0
    [ 80.360] (II) LoadModule: "nvidia"
    [ 80.360] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
    [ 80.360] (II) Module nvidia: vendor="NVIDIA Corporation"
    [ 80.360] compiled for 4.0.2, module version = 1.0.0
    [ 80.360] Module class: X.Org Video Driver
    [ 80.360] (II) LoadModule: "nv"
    [ 80.360] (WW) Warning, couldn't open module nv
    [ 80.360] (II) UnloadModule: "nv"
    [ 80.360] (II) Unloading nv
    [ 80.360] (EE) Failed to load module "nv" (module does not exist, 0)
    [ 80.360] (II) LoadModule: "modesetting"
    [ 80.360] (WW) Warning, couldn't open module modesetting
    [ 80.360] (II) UnloadModule: "modesetting"
    [ 80.360] (II) Unloading modesetting
    [ 80.360] (EE) Failed to load module "modesetting" (module does not exist, 0)
    [ 80.360] (II) LoadModule: "fbdev"
    [ 80.360] (WW) Warning, couldn't open module fbdev
    [ 80.360] (II) UnloadModule: "fbdev"
    [ 80.360] (II) Unloading fbdev
    [ 80.360] (EE) Failed to load module "fbdev" (module does not exist, 0)
    [ 80.360] (II) LoadModule: "vesa"
    [ 80.360] (WW) Warning, couldn't open module vesa
    [ 80.360] (II) UnloadModule: "vesa"
    [ 80.360] (II) Unloading vesa
    [ 80.360] (EE) Failed to load module "vesa" (module does not exist, 0)
    [ 80.360] (II) NOUVEAU driver
    [ 80.360] (II) NOUVEAU driver for NVIDIA chipset families :
    [ 80.360] RIVA TNT (NV04)
    [ 80.360] RIVA TNT2 (NV05)
    [ 80.360] GeForce 256 (NV10)
    [ 80.360] GeForce 2 (NV11, NV15)
    [ 80.360] GeForce 4MX (NV17, NV18)
    [ 80.360] GeForce 3 (NV20)
    [ 80.360] GeForce 4Ti (NV25, NV28)
    [ 80.360] GeForce FX (NV3x)
    [ 80.360] GeForce 6 (NV4x)
    [ 80.360] GeForce 7 (G7x)
    [ 80.360] GeForce 8 (G8x)
    [ 80.360] GeForce GTX 200 (NVA0)
    [ 80.360] GeForce GTX 400 (NVC0)
    [ 80.360] (II) NVIDIA dlloader X Driver 331.38 Wed Jan 8 18:51:00 PST 2014
    [ 80.360] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
    [ 80.360] (++) using VT number 1
    [ 80.361] (II) [drm] nouveau interface version: 1.1.1
    [ 80.361] (II) Loading sub module "dri2"
    [ 80.361] (II) LoadModule: "dri2"
    [ 80.361] (II) Module "dri2" already built-in
    [ 80.361] (--) NOUVEAU(0): Chipset: "NVIDIA NVC4"
    [ 80.361] (II) NOUVEAU(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
    [ 80.361] (==) NOUVEAU(0): Depth 24, (--) framebuffer bpp 32
    [ 80.361] (==) NOUVEAU(0): RGB weight 888
    [ 80.361] (==) NOUVEAU(0): Default visual is TrueColor
    [ 80.361] (==) NOUVEAU(0): Using HW cursor
    [ 80.361] (==) NOUVEAU(0): GLX sync to VBlank disabled.
    [ 80.361] (==) NOUVEAU(0): Page flipping enabled
    [ 80.361] (==) NOUVEAU(0): Swap limit set to 2 [Max allowed 2]
    [ 80.394] (II) NOUVEAU(0): Output DVI-I-1 has no monitor section
    [ 80.417] (II) NOUVEAU(0): Output DVI-I-2 has no monitor section
    [ 80.420] (II) NOUVEAU(0): Output HDMI-1 has no monitor section
    [ 80.449] (II) NOUVEAU(0): EDID for output DVI-I-1
    [ 80.449] (II) NOUVEAU(0): Manufacturer: GSM Model: 5678 Serial#: 95359
    [ 80.449] (II) NOUVEAU(0): Year: 2010 Week: 6
    [ 80.449] (II) NOUVEAU(0): EDID Version: 1.3
    [ 80.449] (II) NOUVEAU(0): Digital Display Input
    [ 80.449] (II) NOUVEAU(0): Max Image Size [cm]: horiz.: 49 vert.: 32
    [ 80.449] (II) NOUVEAU(0): Gamma: 2.20
    [ 80.449] (II) NOUVEAU(0): DPMS capabilities: StandBy Suspend Off
    [ 80.449] (II) NOUVEAU(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
    [ 80.449] (II) NOUVEAU(0): First detailed timing is preferred mode
    [ 80.449] (II) NOUVEAU(0): redX: 0.635 redY: 0.342 greenX: 0.292 greenY: 0.611
    [ 80.449] (II) NOUVEAU(0): blueX: 0.147 blueY: 0.070 whiteX: 0.313 whiteY: 0.329
    [ 80.449] (II) NOUVEAU(0): Supported established timings:
    [ 80.449] (II) NOUVEAU(0): 720x400@70Hz
    [ 80.449] (II) NOUVEAU(0): 640x480@60Hz
    [ 80.449] (II) NOUVEAU(0): 640x480@75Hz
    [ 80.449] (II) NOUVEAU(0): 800x600@56Hz
    [ 80.449] (II) NOUVEAU(0): 800x600@60Hz
    [ 80.449] (II) NOUVEAU(0): 800x600@75Hz
    [ 80.449] (II) NOUVEAU(0): 832x624@75Hz
    [ 80.449] (II) NOUVEAU(0): 1024x768@60Hz
    [ 80.449] (II) NOUVEAU(0): 1024x768@75Hz
    [ 80.449] (II) NOUVEAU(0): 1280x1024@75Hz
    [ 80.450] (II) NOUVEAU(0): 1152x864@75Hz
    [ 80.450] (II) NOUVEAU(0): Manufacturer's mask: 0
    [ 80.450] (II) NOUVEAU(0): Supported standard timings:
    [ 80.450] (II) NOUVEAU(0): #0: hsize: 1440 vsize 900 refresh: 60 vid: 149
    [ 80.450] (II) NOUVEAU(0): #1: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
    [ 80.450] (II) NOUVEAU(0): #2: hsize: 1280 vsize 960 refresh: 60 vid: 16513
    [ 80.450] (II) NOUVEAU(0): #3: hsize: 1152 vsize 864 refresh: 75 vid: 20337
    [ 80.450] (II) NOUVEAU(0): Supported detailed timing:
    [ 80.450] (II) NOUVEAU(0): clock: 119.0 MHz Image Size: 474 x 296 mm
    [ 80.450] (II) NOUVEAU(0): h_active: 1680 h_sync: 1728 h_sync_end 1760 h_blank_end 1840 h_border: 0
    [ 80.450] (II) NOUVEAU(0): v_active: 1050 v_sync: 1053 v_sync_end 1059 v_blanking: 1080 v_border: 0
    [ 80.450] (II) NOUVEAU(0): Supported detailed timing:
    [ 80.450] (II) NOUVEAU(0): clock: 146.2 MHz Image Size: 474 x 296 mm
    [ 80.450] (II) NOUVEAU(0): h_active: 1680 h_sync: 1784 h_sync_end 1960 h_blank_end 2240 h_border: 0
    [ 80.450] (II) NOUVEAU(0): v_active: 1050 v_sync: 1053 v_sync_end 1059 v_blanking: 1089 v_border: 0
    [ 80.450] (II) NOUVEAU(0): Ranges: V min: 56 V max: 75 Hz, H min: 30 H max: 83 kHz, PixClock max 155 MHz
    [ 80.450] (II) NOUVEAU(0): Monitor name: W2242
    [ 80.450] (II) NOUVEAU(0): EDID (in hex):
    [ 80.450] (II) NOUVEAU(0): 00ffffffffffff001e6d78567f740100
    [ 80.450] (II) NOUVEAU(0): 06140103ea312078eaaec5a2574a9c25
    [ 80.450] (II) NOUVEAU(0): 125054a76b80950081808140714f0101
    [ 80.450] (II) NOUVEAU(0): 0101010101017c2e90a0601a1e403020
    [ 80.450] (II) NOUVEAU(0): 3600da281100001a21399030621a2740
    [ 80.450] (II) NOUVEAU(0): 68b03600da281100001c000000fd0038
    [ 80.450] (II) NOUVEAU(0): 4b1e530f000a202020202020000000fc
    [ 80.450] (II) NOUVEAU(0): 0057323234320a202020202020200070
    [ 80.450] (II) NOUVEAU(0): Printing probed modes for output DVI-I-1
    [ 80.450] (II) NOUVEAU(0): Modeline "1680x1050"x59.9 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz eP)
    [ 80.450] (II) NOUVEAU(0): Modeline "1680x1050"x60.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz e)
    [ 80.450] (II) NOUVEAU(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 80.450] (II) NOUVEAU(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [ 80.450] (II) NOUVEAU(0): Modeline "1440x900"x59.9 88.75 1440 1488 1520 1600 900 903 909 926 +hsync -vsync (55.5 kHz e)
    [ 80.450] (II) NOUVEAU(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 80.450] (II) NOUVEAU(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 80.450] (II) NOUVEAU(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
    [ 80.450] (II) NOUVEAU(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 80.450] (II) NOUVEAU(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
    [ 80.450] (II) NOUVEAU(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 80.450] (II) NOUVEAU(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 80.450] (II) NOUVEAU(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 80.450] (II) NOUVEAU(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 80.450] (II) NOUVEAU(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 80.450] (II) NOUVEAU(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 80.473] (II) NOUVEAU(0): EDID for output DVI-I-2
    [ 80.475] (II) NOUVEAU(0): EDID for output HDMI-1
    [ 80.475] (II) NOUVEAU(0): Output DVI-I-1 connected
    [ 80.475] (II) NOUVEAU(0): Output DVI-I-2 disconnected
    [ 80.475] (II) NOUVEAU(0): Output HDMI-1 disconnected
    [ 80.475] (II) NOUVEAU(0): Using exact sizes for initial modes
    [ 80.475] (II) NOUVEAU(0): Output DVI-I-1 using initial mode 1680x1050
    [ 80.475] (II) NOUVEAU(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
    [ 80.475] (--) NOUVEAU(0): Virtual size is 1680x1050 (pitch 0)
    [ 80.475] (**) NOUVEAU(0): Driver mode "1680x1050": 119.0 MHz (scaled from 0.0 MHz), 64.7 kHz, 59.9 Hz
    [ 80.475] (II) NOUVEAU(0): Modeline "1680x1050"x59.9 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz eP)
    [ 80.475] (**) NOUVEAU(0): Driver mode "1680x1050": 146.2 MHz (scaled from 0.0 MHz), 65.3 kHz, 60.0 Hz
    [ 80.475] (II) NOUVEAU(0): Modeline "1680x1050"x60.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz e)
    [ 80.475] (**) NOUVEAU(0): Driver mode "1280x1024": 135.0 MHz (scaled from 0.0 MHz), 80.0 kHz, 75.0 Hz
    [ 80.475] (II) NOUVEAU(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 80.475] (**) NOUVEAU(0): Driver mode "1280x1024": 108.0 MHz (scaled from 0.0 MHz), 64.0 kHz, 60.0 Hz
    [ 80.475] (II) NOUVEAU(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [ 80.475] (**) NOUVEAU(0): Driver mode "1440x900": 88.8 MHz (scaled from 0.0 MHz), 55.5 kHz, 59.9 Hz
    [ 80.475] (II) NOUVEAU(0): Modeline "1440x900"x59.9 88.75 1440 1488 1520 1600 900 903 909 926 +hsync -vsync (55.5 kHz e)
    [ 80.475] (**) NOUVEAU(0): Driver mode "1280x960": 108.0 MHz (scaled from 0.0 MHz), 60.0 kHz, 60.0 Hz
    [ 80.475] (II) NOUVEAU(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 80.475] (**) NOUVEAU(0): Driver mode "1152x864": 108.0 MHz (scaled from 0.0 MHz), 67.5 kHz, 75.0 Hz
    [ 80.475] (II) NOUVEAU(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 80.475] (**) NOUVEAU(0): Driver mode "1024x768": 78.8 MHz (scaled from 0.0 MHz), 60.1 kHz, 75.1 Hz
    [ 80.475] (II) NOUVEAU(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
    [ 80.475] (**) NOUVEAU(0): Driver mode "1024x768": 65.0 MHz (scaled from 0.0 MHz), 48.4 kHz, 60.0 Hz
    [ 80.475] (II) NOUVEAU(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 80.475] (**) NOUVEAU(0): Driver mode "832x624": 57.3 MHz (scaled from 0.0 MHz), 49.7 kHz, 74.6 Hz
    [ 80.475] (II) NOUVEAU(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
    [ 80.475] (**) NOUVEAU(0): Driver mode "800x600": 49.5 MHz (scaled from 0.0 MHz), 46.9 kHz, 75.0 Hz
    [ 80.475] (II) NOUVEAU(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 80.475] (**) NOUVEAU(0): Driver mode "800x600": 40.0 MHz (scaled from 0.0 MHz), 37.9 kHz, 60.3 Hz
    [ 80.475] (II) NOUVEAU(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 80.475] (**) NOUVEAU(0): Driver mode "800x600": 36.0 MHz (scaled from 0.0 MHz), 35.2 kHz, 56.2 Hz
    [ 80.475] (II) NOUVEAU(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 80.475] (**) NOUVEAU(0): Driver mode "640x480": 31.5 MHz (scaled from 0.0 MHz), 37.5 kHz, 75.0 Hz
    [ 80.475] (II) NOUVEAU(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 80.475] (**) NOUVEAU(0): Driver mode "640x480": 25.2 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
    [ 80.475] (II) NOUVEAU(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 80.475] (**) NOUVEAU(0): Driver mode "720x400": 28.3 MHz (scaled from 0.0 MHz), 31.5 kHz, 70.1 Hz
    [ 80.475] (II) NOUVEAU(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 80.475] (==) NOUVEAU(0): DPI set to (96, 96)
    [ 80.475] (II) Loading sub module "fb"
    [ 80.475] (II) LoadModule: "fb"
    [ 80.475] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 80.475] (II) Module fb: vendor="X.Org Foundation"
    [ 80.475] compiled for 1.15.0, module version = 1.0.0
    [ 80.475] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 80.475] (II) Loading sub module "exa"
    [ 80.475] (II) LoadModule: "exa"
    [ 80.475] (II) Loading /usr/lib/xorg/modules/libexa.so
    [ 80.475] (II) Module exa: vendor="X.Org Foundation"
    [ 80.475] compiled for 1.15.0, module version = 2.6.0
    [ 80.475] ABI class: X.Org Video Driver, version 15.0
    [ 80.475] (II) Loading sub module "shadowfb"
    [ 80.475] (II) LoadModule: "shadowfb"
    [ 80.475] (II) Loading /usr/lib/xorg/modules/libshadowfb.so
    [ 80.475] (II) Module shadowfb: vendor="X.Org Foundation"
    [ 80.475] compiled for 1.15.0, module version = 1.0.0
    [ 80.475] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 80.475] (II) UnloadModule: "nvidia"
    [ 80.475] (II) Unloading nvidia
    [ 80.475] (--) Depth 24 pixmap format is 32 bpp
    [ 80.477] (II) NOUVEAU(0): Opened GPU channel 0
    [ 80.483] (II) NOUVEAU(0): [DRI2] Setup complete
    [ 80.483] (II) NOUVEAU(0): [DRI2] DRI driver: nouveau
    [ 80.483] (II) NOUVEAU(0): [DRI2] VDPAU driver: nouveau
    [ 80.483] (II) EXA(0): Driver allocated offscreen pixmaps
    [ 80.483] (II) EXA(0): Driver registered support for the following operations:
    [ 80.483] (II) Solid
    [ 80.483] (II) Copy
    [ 80.483] (II) Composite (RENDER acceleration)
    [ 80.483] (II) UploadToScreen
    [ 80.483] (II) DownloadFromScreen
    [ 80.483] (==) NOUVEAU(0): Backing store enabled
    [ 80.483] (==) NOUVEAU(0): Silken mouse enabled
    [ 80.483] (II) NOUVEAU(0): [XvMC] Associated with Nouveau GeForce 8/9 Textured Video.
    [ 80.483] (II) NOUVEAU(0): [XvMC] Extension initialized.
    [ 80.483] (==) NOUVEAU(0): DPMS enabled
    [ 80.483] (II) NOUVEAU(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    [ 80.483] (--) RandR disabled
    [ 80.500] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
    [ 80.500] (II) AIGLX: enabled GLX_ARB_create_context
    [ 80.500] (II) AIGLX: enabled GLX_ARB_create_context_profile
    [ 80.500] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
    [ 80.500] (II) AIGLX: enabled GLX_INTEL_swap_event
    [ 80.500] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
    [ 80.500] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
    [ 80.500] (II) AIGLX: enabled GLX_ARB_fbconfig_float
    [ 80.500] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
    [ 80.500] (II) AIGLX: Loaded and initialized nouveau
    [ 80.500] (II) GLX: Initialized DRI2 GL provider for screen 0
    [ 80.504] (II) NOUVEAU(0): NVEnterVT is called.
    [ 80.522] (II) NOUVEAU(0): Setting screen physical size to 444 x 277
    [ 80.522] resize called 1680 1050
    [ 80.536] (II) config/udev: Adding input device Power Button (/dev/input/event5)
    [ 80.536] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 80.536] (II) LoadModule: "evdev"
    [ 80.536] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 80.536] (II) Module evdev: vendor="X.Org Foundation"
    [ 80.536] compiled for 1.15.0, module version = 2.8.2
    [ 80.536] Module class: X.Org XInput Driver
    [ 80.536] ABI class: X.Org XInput driver, version 20.0
    [ 80.536] (II) Using input driver 'evdev' for 'Power Button'
    [ 80.536] (**) Power Button: always reports core events
    [ 80.536] (**) evdev: Power Button: Device: "/dev/input/event5"
    [ 80.536] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 80.536] (--) evdev: Power Button: Found keys
    [ 80.536] (II) evdev: Power Button: Configuring as keyboard
    [ 80.536] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input7/event5"
    [ 80.536] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    [ 80.536] (**) Option "xkb_rules" "evdev"
    [ 80.536] (**) Option "xkb_model" "pc104"
    [ 80.536] (**) Option "xkb_layout" "us"
    [ 80.545] (II) config/udev: Adding input device Power Button (/dev/input/event4)
    [ 80.545] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 80.545] (II) Using input driver 'evdev' for 'Power Button'
    [ 80.545] (**) Power Button: always reports core events
    [ 80.545] (**) evdev: Power Button: Device: "/dev/input/event4"
    [ 80.545] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 80.545] (--) evdev: Power Button: Found keys
    [ 80.545] (II) evdev: Power Button: Configuring as keyboard
    [ 80.545] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input6/event4"
    [ 80.545] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
    [ 80.545] (**) Option "xkb_rules" "evdev"
    [ 80.545] (**) Option "xkb_model" "pc104"
    [ 80.545] (**) Option "xkb_layout" "us"
    [ 80.545] (II) config/udev: Adding drm device (/dev/dri/card0)
    [ 80.545] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event20)
    [ 80.545] (II) No input driver specified, ignoring this device.
    [ 80.545] (II) This device may have been added with another device file.
    [ 80.545] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event19)
    [ 80.545] (II) No input driver specified, ignoring this device.
    [ 80.545] (II) This device may have been added with another device file.
    [ 80.545] (II) config/udev: Adding input device HDA NVidia HD

    Please reproduce the issue and post the output of dmesg:
    dmesg > dmesg.txt
    if the system hangs hard, then try to clean reboot and do:
    journalctl -b -1 -k > dmesg.txt
    as root.

  • Fan behaviour of EliteBook 8560p when plugged in and when on battery

    Hi,
    I am wondering why the fan (permanent activity disabled in BIOS) of my EliteBook 8560p is more active when it runs on AC power as it is active when it is on battery power  (especially when the notebook is in the docking station, the notebook lid is closed and I use an external monitor)? I would assume that the power consumption would be less...
    Is there any way to change the fan behaviour in that sense?
    Well, it is fine, that I can deactivate permanent activity of the fan via BIOS, but when it is possible that it is not needed on battery power why not the same for AC power - especially when the power consumption is less...?
    Schlumpf

    Hi Huffer, thank you for the quick response.
    O.k., the fan consumes quite a lot of power. On the other hand, why using it when it is not really needed (as shown when on battery)?
    However, I found under "Power Options > Advanced Settings > Processor power management" some interesting settings.
    Well, there also should be settings about "Core Parking", "Allow Throttle States" etc... but it seems that they are hidden. On one website I found tweaks for listing such settings in the BIOS...
    http://www.ryanstevens.co.uk/2011/03/18/tutorial-s​peed-windows-pc/
    It relates to http://msdn.microsoft.com/en-us/windows/hardware/g​g566941.aspx
    "Copy its GUID from the document – ‘Allow throttle states’ is ‘ 3b04d4fd-1cc7-4f23-ab1c-d1337819c4bb ‘, for instance – and build a command along the lines of powercfg -attributes SUB_ PROCESSOR 3b04d4fd-1cc7-4f23-ab1c-d1337819c4bb-ATTRIB_HIDE ."
    I think that the cpu throttling is enabled only while on battery, isn't it?
    Or is it possible to control this "Enhanced Intel SpeedStep® Technology" via the "Minimum/maximum processor state" settings?

  • Strange behaviour of JBuilder Plug-In with Inner class

    Hi, I'm using the Kodo 2.5.2 Plug-In with JBuilder 8. I have an inner
    persistent class. It seems that it is necessary to have a zero length file
    named EnclosingClass$InnerClass.java for the build process to work, since
    if I delete this file and run the application it throws an exception
    saying that the Inner class has not an specified field which it really
    has. I don't know if this is a bug of the Kodo implementation or of the
    JBuilder Plug-In.
    Thanks for any help.
    Jaime.

    This is one of the limitations of the JBuilder plugin. Hopefully it
    will be resolved in the next iteration of our plugins for 3.x.
    Jaime De La Jara F. wrote:
    Hi, I'm using the Kodo 2.5.2 Plug-In with JBuilder 8. I have an inner
    persistent class. It seems that it is necessary to have a zero length file
    named EnclosingClass$InnerClass.java for the build process to work, since
    if I delete this file and run the application it throws an exception
    saying that the Inner class has not an specified field which it really
    has. I don't know if this is a bug of the Kodo implementation or of the
    JBuilder Plug-In.
    Thanks for any help.
    Jaime.
    Steve Kim
    [email protected]
    SolarMetric Inc.
    http://www.solarmetric.com

  • File Plug-in strange behaviour

    Hi all,
    I'm trying to publish a stream using my own File Plugin but I
    don't understand how the FMS wants to use it.
    When I publish a stream using NetStream.publish("streamname",
    "record") the FMS:
    1.- opens the file to read
    2.- query all the attributes of the file (using the handle).
    I return size '0' (the file is empty).
    3.- tries to read 294912 bytes.
    4.- the file is empty, so I tell the FMS that I've read 0
    bytes.
    5.- closes the file
    6.- queries all the attributes of the file (using the name).
    7.- open the file to read & write
    8.- queries again the file.
    9.- tries to read 294912 bytes, but the file is empty.
    10.- closes the file.
    The client gets 'NetStream.Record.NoAccess'.
    I don't know what the FMS is expecting from the File Plugin.
    I'm trying to follow the documentation and the examples, but it
    doesn't work.
    Any clues?
    Thanks,
    Jorge

    The file plug-in works fine in publishing case. Just use
    provided FMS sample and you will be able to record publishing file
    using external plug-in. Do not modify read by returning 0 since FMS
    expects flv file header 13 bytes. Actually in publishing case you
    do not needed to modify anything since in that case FMS passing
    data to you in write request and you could post that data anywhere
    you want.

Maybe you are looking for