Mouse & Keyboard freeze

Please help... my G4 and my mouse & keyboard are not communicating. I have 2 other Macs in the house & the mouse & keyboard work just fine on those computers. I also have a wireless Mighty Mouse that doesn't work with my desktop Mac either...works fine on my laptop.
I can turn the G4 on & off, but cannot use it. I am stumped.
Thank you.

First, try lugging your keyboard into your other USB port. Try a USB device in that port. Is the port good?
Are you using a wireless mouse & kb? New battery?
Try starting up in Safe Mode
[Mac OS X: Starting up in Safe Mode|http://docs.info.apple.com/article.html?artnum=107393]
[What is Safe Boot, Safe Mode? (Mac OS X)|http://docs.info.apple.com/article.html?artnum=107392]
[Safe Boot takes longer than normal startup|http://docs.info.apple.com/article.html?artnum=107394]
Safe boot mode runs a directory check command similar to that used by Disk Utility's repair. In Tiger it ignores some stored information (cache) that is normally read that speeds up the boot process, and it moves some other caches to the trash. It also uses only System fonts and disables all Startup Items and any Login Items.
If that doesn't help then boot from you installer disc to run Disk Utility to repair your drive and permissions.
[Resolve startup issues and perform disk maintenance with Disk Utility and fsck|http://docs.info.apple.com/article.html?artnum=106214]
[Using Disk Utility in Mac OS X 10.4.3 or later|http://docs.info.apple.com/article.html?artnum=302672]
[Disk Utility's Repair Disk Permissions|http://docs.info.apple.com/article.html?artnum=25751]
From BDaqua (couldn't have said it better):
"Try Disk Utility
1. Insert the Mac OS X Install disc that came with your computer (Edit: Do not use this disc if it is not the same general version as what you have currently on your computer, e.g. use a Tiger disc for a Tiger drive, not a Panther disc), then restart the computer while holding the C key.
2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu. (In Mac OS X 10.4 or later, you must select your language first.)
Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.
3. Click the First Aid tab.
4. Click the disclosure triangle to the left of the hard drive icon to display the names of your hard disk volumes and partitions.
5. Select your Mac OS X volume.
6. Click Repair. Disk Utility checks and repairs the disk.
Then Safe Boot, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, reboot when it completes."

Similar Messages

  • Macbook Pro Retina Mouse/Keyboard freeze

    Hi there,
    I have a 2013 macbook pro retina that's less than a month old. I have experienced a number of trackpad/mousepad freeze issues while using the computer. They occurred in close succession while using 10.93. I update to 10.94 and had not experienced the problem again since then(a week or more) but today it crashed. this is a big problem as i am a dj and use this laptop to play live gigs. I was hoping that you could help me isolate the problem. What happens is I will be working away and suddenly the mouse will freeze and the computer will become unresponsive, the keyboard doesn't work except for the power button.... also, the desktop background disappears upon forced restart.... any ideas? what may be causing this? Thanks in advance, Richard

    If your machine is less than a month old, you should use your warranty and call AppleCare (you have 90 days of phone support) or take your machine back to the Apple Store (make an appointment with the Genius Bar first) and let them deal with the issue.
    If yours is the 13" model, there is a thread on here (somewhere) about trackpad and keyboard failures when also using Bluetooth, I think (don't quote me on that - I don't have the affected machines so I don't follow the thread too closely).
    But I do believe that Apple is aware of the issue and had 'fixed' it in either a patch preceding 10.9.4 or in 10.9.4 itself.
    Give them a call...
    Clinton

  • Mouse+Keyboard Freeze and LOUD fan noise...

    Hi,
    Seems to be a few similar threads, so here we go...
    Just got my iMac G5 20" 1GB Ram (OS 10.4.3) 2 days ago. All went well and suddenly, mouse + keyboard froze. About 10sec later, the fans kick iun, VERY loud. Never stopped for 2 hours.
    If I reboot, shutdown and restart, do all the kind of troubleshooting you can read, it always starts again int he grey screen with the Apple and the fans at max revs, VERY nousy.
    Eventually it goes away. But about 1 hour later, same story.
    I ran the Apple Hardware test and all tests came PASS but there was originally a memory error POST/0/2048 notice. But the 1GB memory test passed...
    Had a chat with the Apple Agent support, said this code shows a hardware component failure.
    Have to bring back 10KG of EXPENSIVE Apple HW to the store tomorrow.
    Great way to spend Xmas indeed
    Any comments or suggestions?
    Thanks,
    JP

    Hey,
    When does this happen exactly? On Toshiba screen or Windows startup screen?
    Are you running factory settings or another OS?
    I think its hard to say why this happens. It could be software or hardware malfunction
    Fact is you can test the RAM modules using Memtest86 or another diagnostic tool. You can ask Google to find it, its freeware. Just download an iso image and create a bootable CD/DVD. If you boot from this disk you can start the test.

  • USB Mouse & Keyboard freezes with USB KVM after a while

    Looks like connecting and disconnecting USB keyboard & mouse using USB hub causes some processes to freeze - the mouse and keyboard stop responding and you cannot log out or restart the OS X. Anybody else has the same issue?

    I found what the issue was - it was not Apple or KVM, but logitech software that I installed to handle my trackball. Uninstalling the software fixed this issue. So the conclusion is - USB KVM works great with MacBook, but Logitech software is junk.

  • Mouse & keyboard freeze at startup

    Hallo, sorry for my poor English, I hope made myself clear.
    I've a problem with my mouse and keyboard (Logitech S 530 Mac cordless). They used to work very well, but from one day to the next, they work in login screen, where I can move the mouse pointer and write down my login password, but they freeze when the computer loads the start screen. Nothing happens forcing a boot. I can use them only if I unplug the power and then I plug it in again. I've set up the restart after an electric fall, so it powers up and all work fine. Could you help me? Thanks a lot

    Your English is quite good by the way!
    I's starting to sound like Hard Drive failure or at least severe HD corruption, see if it even shows up here...
    "Try Disk Utility
    1. Insert the Mac OS X Install disc, then restart the computer while holding the C key.
    2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu. (In Mac OS X 10.4 or later, you must select your language first.)
    *Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.*
    3. Click the First Aid tab.
    4. Select your Mac OS X volume.
    5. Click Repair. Disk Utility checks and repairs the disk."
    http://docs.info.apple.com/article.html?artnum=106214

  • Mouse/keyboard freezes?

    Two questions. 1- does anyone else experience their mouse freezing? I was watching a movie and when I finished I closed the dvd player and the mouse was froze, and the keyboard wouldn't eject the cd? I then had to use ea shortcut. 2- is there a shortcut way to reboot the computer?

    Do you have the Intel model? It is in one of your posts, but not the other? If it is, try posting over in this forum.
    If not, try updating to 10.4.6 using the Combo updater instead of the delta update through software update.
    Obviously backup all your data first, preferably by cloning the internal drive to a FireWire drive using SuperDuper. Then download but don't apply update yet. Repair permissions, unplug all USB and FW devices - except keyboard and mouse - apply update, restart, and repair permissions again.

  • Mouse/keyboard freezing machine around same time every day

    Using a silver tower G5 here and around the same time every day for the past week I've had to power down the machine. The mouse and keyboard just freeze. About a week ago we did put this on a KVM to switch between this and a G4 connected to a SCSI scanner. The KVM has only PS/2 ports so we're using the Belkin Y PS/2 to USB adapters. The problem seemed to have started a day or so after starting to use the KVM but I'm not sure if this is related to the freezing problem. Here's what's in the Console around the time of the freeze:
    Mac OS X Version 10.4.8 (Build 8L127)
    2007-03-06 12:18:21 -0500
    2007-03-06 12:18:22.606 SystemUIServer[76] lang is:en
    Mar 6 12:18:26 metros-power-mac-g5 ntpdate[105]: no servers can be used, exiting
    Mar 6 12:18:26 metros-power-mac-g5 VersionCueCS2Daemon[167]: warning: VersionCueCS2Daemon not started by mach_init process (parent pid: 1)
    Mar 6 12:18:26 metros-power-mac-g5 VersionCueCS2Daemon[167]: Unknown plist format in 'com.apple.sharing.firewall' - 'firewall'
    2007-03-06 12:19:04.634 Finder[77] CFLog (0): CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
    Adobe LM Service: Started
    AdobeLM Service
    Power Mac G5 (2.1)   Mac OS X (10.4.8)   2.5 GB RAM

    Rob Kudyba-
    Too many adapters. For troubleshooting purposes can you go with a mouse and keyboard connected as directly as possible?
    Do you know what Adobe LM is? That seems to be buggering things up a little.
    If you still have the errors after trying it with as few adapters as possible, try repairing your startup disk.
    Luck-
    -DaddyPaycheck

  • Thinkpad Yoga Mouse / Keyboard freezing

    Hello,
    On my new TPY 20CD001UK the keyboard and trackpad seem to freeze very often. All dirvers are updated. The digitizer and touchpad continue working when the trackpad and keyboard become unresponsive.
    Occasionally the keyboard will lag and dump all entered text after it unfreezes.
    Is there any fix for this?

    Okay... so lets focus back on the question. Why are we having lockups?  I'm on a model with the SSD. It happened again, shortly after I posted my comments. It happened after coming out of sleep. Since there is no HDD indicator, one has absolutely no idea if there is HDD/SSD activity consuming CPU. So, you wait, and hope eventually the system will begin responding.

  • Mouse freezes Keyboard freezes USB Headset freezes USB freezes :)

    Since arch install the new 3.7.9 kernel my usb devices freezes random (mouse, keyboard and so on)
    [ 5.119718] microcode: failed to load file amd-ucode/microcode_amd.bin
    [ 5.119946] microcode: CPU1: patch_level=0x01000095
    [ 5.119957] microcode: CPU2: patch_level=0x01000095
    [ 5.119965] microcode: CPU3: patch_level=0x01000095
    [ 5.120024] microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
    [ 2874.323594] INFO: task khubd:72 blocked for more than 120 seconds.
    [ 2874.323601] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    [ 2874.323605] khubd D ffff88012753bef0 0 72 2 0x00000000
    [ 2874.323613] ffff880127999ad8 0000000000000046 ffff88012814d960 ffff880127999fd8
    [ 2874.323620] ffff880127999fd8 ffff880127999fd8 ffff880129acf1c0 ffff88012814d960
    [ 2874.323625] ffffffff81a40e60 0000000000000001 ffff880127999a18 ffffffff810586fc
    [ 2874.323630] Call Trace:
    [ 2874.323642] [<ffffffff810586fc>] ? print_time.part.3+0x6c/0x90
    [ 2874.323662] [<ffffffffa0035840>] ? ohci_urb_dequeue+0x80/0xd0 [ohci_hcd]
    [ 2874.323677] [<ffffffffa00116c4>] ? unlink1+0x34/0x160 [usbcore]
    [ 2874.323688] [<ffffffff814baba9>] schedule+0x29/0x70
    [ 2874.323700] [<ffffffffa0014445>] usb_kill_urb+0x75/0xb0 [usbcore]
    [ 2874.323705] [<ffffffff8107bea0>] ? abort_exclusive_wait+0xb0/0xb0
    [ 2874.323718] [<ffffffffa0012fe5>] usb_hcd_flush_endpoint+0xb5/0x180 [usbcore]
    [ 2874.323730] [<ffffffffa0015d5e>] usb_disable_endpoint+0x5e/0x90 [usbcore]
    [ 2874.323741] [<ffffffffa0015dd6>] usb_disable_interface+0x46/0x60 [usbcore]
    [ 2874.323753] [<ffffffffa00186cd>] usb_unbind_interface+0x18d/0x1a0 [usbcore]
    [ 2874.323762] [<ffffffff8134419c>] __device_release_driver+0x7c/0xe0
    [ 2874.323767] [<ffffffff8134422c>] device_release_driver+0x2c/0x40
    [ 2874.323773] [<ffffffff81343b6e>] bus_remove_device+0xee/0x160
    [ 2874.323778] [<ffffffff813413da>] device_del+0x12a/0x1b0
    [ 2874.323788] [<ffffffffa0015ea0>] usb_disable_device+0xb0/0x270 [usbcore]
    [ 2874.323798] [<ffffffffa000c98d>] usb_disconnect+0xad/0x160 [usbcore]
    [ 2874.323809] [<ffffffffa000eec3>] hub_thread+0x433/0x1720 [usbcore]
    [ 2874.323814] [<ffffffff814ba595>] ? __schedule+0x435/0x920
    [ 2874.323819] [<ffffffff8107bea0>] ? abort_exclusive_wait+0xb0/0xb0
    [ 2874.323829] [<ffffffffa000ea90>] ? usb_remote_wakeup+0x70/0x70 [usbcore]
    [ 2874.323835] [<ffffffff8107b1b0>] kthread+0xc0/0xd0
    [ 2874.323841] [<ffffffff81010000>] ? perf_trace_xen_mmu_set_pte_at+0xb0/0x100
    [ 2874.323846] [<ffffffff8107b0f0>] ? kthread_freezable_should_stop+0x70/0x70
    [ 2874.323852] [<ffffffff814c35ac>] ret_from_fork+0x7c/0xb0
    [ 2874.323858] [<ffffffff8107b0f0>] ? kthread_freezable_should_stop+0x70/0x70
    [ 4046.558474] 2:2:1: usb_set_interface failed (-62)
    [ 4046.561463] 2:1:2: usb_set_interface failed (-62)
    [ 4046.564456] 2:2:1: usb_set_interface failed (-62)
    [ 4063.625732] 2:1:2: usb_set_interface failed (-62)
    [ 4063.629716] 2:2:1: usb_set_interface failed (-62)
    [ 4063.632709] 2:1:2: usb_set_interface failed (-62)
    [ 4063.635703] 2:2:1: usb_set_interface failed (-62)
    [ 4073.403671] 2:1:2: usb_set_interface failed (-62)
    [ 4073.406659] 2:2:1: usb_set_interface failed (-62)
    [ 4073.409655] 2:1:2: usb_set_interface failed (-62)
    [ 4073.412649] 2:2:1: usb_set_interface failed (-62)
    [ 4134.273608] 2:1:2: usb_set_interface failed (-62)
    [ 4134.276602] 2:2:1: usb_set_interface failed (-62)
    [ 4134.279596] 2:1:2: usb_set_interface failed (-62)
    [ 4134.282590] 2:2:1: usb_set_interface failed (-62)
    [ 4135.969965] 2:1:2: usb_set_interface failed (-62)
    [ 4135.973953] 2:2:1: usb_set_interface failed (-62)
    Connect ps/2 mouse / keyboard worked. Reconnect any usb device didn't work.
    Manufacturer: ASRock
    Product Name: K10N78M Pro
    Linux 3.7.9-1-ARCH #1 SMP PREEMPT Mon Feb 18 02:13:30 EET 2013 x86_64 GNU/Linux
    AMD Phenom(tm) 9950 Quad-Core Processor
    i hope someone can help

    I have the same problem - extremely annoying, particularly if I have several other applications / documents open with unsaved changes!
    I thought I had found a fix by force-quitting the Finder (another App must be open) and then plugging in the headset, then clicking the Finder icon on the dock to re-launch it - that worked a few times, but not all the time.
    This would be a *really good topic* for someone to resolve.
    Mark

  • Mouse, Keyboard and Track pad Freezes

    After upgrade to Lion everytime my iMac goes to 'Sleep', the mouse, keyboard and track pad freezes and cannot wake the computer up. After waking the computer with the power button on the back, these devices still will not response or work. I know there is a option in the Bluetooth system pref. to check 'Allow Bluetooth devices to wake this computer". Make no difference to me when this is checked. Anybody have the same problem as me?

    I'm facing a very similar problem .
    My MBP keyboard freezes eventually during the day - sometimes for a minute, sometimes for much more than that. Mouse continues to work just fine.

  • Mouse, keyboard and clock freezing

    Hello
    My mouse, keyboard and clock are randomly freezing and I have to power off.  Restart and it is fine for awhile.  Went to the Genius Bar and couldn't recreate it of course.  Created a new user account but it happens there also.  So annoying.  Have read on the boards and google that other people have had the same issue but can't find a solution.  Help?  Running Snow Leopard

    Quote
    Corsair said that setting the Failsafe Defaults and setting XMP to enabled should work.
    As I said before, XMP Settings (DDR3-1600/CL8) are overclocking settings, not default settings.  Corsair does not (actually cannot) reallly guarantee that these settings are stable.  To point that out, I quoted the standard note that Corsair has put into the datasheet for your modules.
    The native settings (industry standard settings) for your modules are DDR3-1333 @9-9-9-24 @1.5 +/- 0.075V.  I already provided you with a link to the datasheet which lists these parameters. That is why I suggested to use these.  Have you tried these settings yet?
    Quote
    It seems like the BIOS settings for their RAM is a trade secret and heavily guarded
    Not really.  They are in the datasheet.
    If the DDR3-1333 settings do not change anything, reduce the memory clock speed to DDR3-1066.  That is the maximum clock speed the memory controller of your processor natively supports (according to Intel Specifications).
    Please keep Spread Spectrum disabled at all times.
    Quote
    Does anyone know what settings in the BIOS I have to set so the RAM runs at 1.5v?
    The JEDEC Standard SPD Settings for your memory modules are in the Corsair Datasheet. I have already pointed them out twice.
    Quote
    Also I've noticed that the IOH temperature has been running around 60 - 70 degrees C.
    The maximum allowable temperature for the IOH is around 100°C (according to Intel Specs).  As long as the temperature stays below that value, there should be no functional issues.  To double check:  Point an extra fan to the IOH heatsink to provide additional cooling and see if that changes anything.
    One more thing:
    What is your current BIOS Version?

  • Mouse keeps FREEZING........KEYBOARD NOT WORKING!!!!

    Hey, hoping someone could help. The last couple days, I will walk away from the laptop and come back only to see the trackpad is frozen and I am unable to type. I know that the laptop is NOT frozen because any audio/video will still be playing.
    Any ideas why this is happening???

    I have a similar issue, and it appears to be tied to static electricity. When I feel a small charge of electricity through the touchpad after it has sat a while, it froze. An external mouse/keyboard can be attached and work well. Of course, that isn't convenient on a laptop.
    I have since "grounded" myself before I touch the keyboard/pad and have eliminated the issue over 90%. This isn't convenient, but it works.
    I identified this issue in this thread:
    http://discussions.apple.com/thread.jspa?threadID=1889075&start=0&tstart=0

  • [SOLVED] Laptop keyboard freezes randomly.

    I have Arch dual booted with Windows 8.1 on an Asus K53SM laptop.
    Laptop specs are:
    * Intel i5 2nd Gen @ 2.5 GHz
    * 8GB RAM
    * 750 GB Hard disk
    * nvidia GT630M 2GB
    Right after installing Arch, I installed GNOME as the DE and everything was working fine. Recently, I uninstalled GNOME and installed KDE. I'm experiencing random keyboard freezes. I've tested it with a USB keyboard, so it is not a hardware issue I guess.
    * The [<Super> + S] combination to display all workspaces works fine.
    * So does the <Alt> + F2, to write commands, but the keys don't work (so can't type anything there).
    These freezes are totally random, and the keyboard works fine after 1-2 minutes. Here is the output for Xorg.0.log ->
    [ 21.228]
    X.Org X Server 1.16.4
    Release Date: 2014-12-20
    [ 21.228] X Protocol Version 11, Revision 0
    [ 21.228] Build Operating System: Linux 3.17.6-1-ARCH x86_64
    [ 21.228] Current Operating System: Linux ape 3.18.6-1-ARCH #1 SMP PREEMPT Sat Feb 7 08:44:05 CET 2015 x86_64
    [ 21.228] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=92ae3f1c-0f63-4de9-9323-487d50c0bd60 rw quiet splash usbcore.old_scheme_first=1
    [ 21.228] Build Date: 11 February 2015 08:10:00AM
    [ 21.228]
    [ 21.228] Current version of pixman: 0.32.6
    [ 21.228] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 21.228] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 21.228] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Feb 15 20:18:09 2015
    [ 21.333] (==) Using config file: "/etc/X11/xorg.conf"
    [ 21.333] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
    [ 21.440] (==) ServerLayout "X.org Configured"
    [ 21.440] (**) |-->Screen "Screen0" (0)
    [ 21.440] (**) | |-->Monitor "Monitor0"
    [ 21.456] (**) | |-->Device "Card0"
    [ 21.456] (**) |-->Screen "Screen1" (1)
    [ 21.456] (**) | |-->Monitor "Monitor1"
    [ 21.456] (**) | |-->Device "Card1"
    [ 21.456] (**) |-->Input Device "Mouse0"
    [ 21.456] (**) |-->Input Device "Keyboard0"
    [ 21.456] (==) Automatically adding devices
    [ 21.456] (==) Automatically enabling devices
    [ 21.456] (==) Automatically adding GPU devices
    [ 21.679] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/OTF/".
    [ 21.679] Entry deleted from font path.
    [ 21.679] (Run 'mkfontdir' on "/usr/share/fonts/OTF/").
    [ 21.718] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 21.718] Entry deleted from font path.
    [ 21.718] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 21.728] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 21.728] Entry deleted from font path.
    [ 21.728] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 21.728] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/OTF/".
    [ 21.728] Entry deleted from font path.
    [ 21.728] (Run 'mkfontdir' on "/usr/share/fonts/OTF/").
    [ 21.728] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 21.728] Entry deleted from font path.
    [ 21.728] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 21.728] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 21.728] Entry deleted from font path.
    [ 21.728] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 21.728] (**) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/Type1/,
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/Type1/
    [ 21.728] (**) ModulePath set to "/usr/lib/xorg/modules"
    [ 21.728] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
    [ 21.728] (WW) Disabling Mouse0
    [ 21.728] (WW) Disabling Keyboard0
    [ 21.739] (II) Loader magic: 0x819d80
    [ 21.739] (II) Module ABI versions:
    [ 21.739] X.Org ANSI C Emulation: 0.4
    [ 21.739] X.Org Video Driver: 18.0
    [ 21.739] X.Org XInput driver : 21.0
    [ 21.739] X.Org Server Extension : 8.0
    [ 21.742] (EE) systemd-logind: failed to get session: PID 301 does not belong to any known session
    [ 21.743] (II) xfree86: Adding drm device (/dev/dri/card0)
    [ 21.745] (--) PCI:*(0:0:2:0) 8086:0126:1043:212e rev 9, Mem @ 0xdc400000/4194304, 0xb0000000/268435456, I/O @ 0x0000e000/64
    [ 21.746] (--) PCI: (0:1:0:0) 10de:0de9:1043:212e rev 161, Mem @ 0xdb000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 0x0000d000/128, BIOS @ 0x????????/524288
    [ 21.746] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    [ 21.763] (II) "glx" will be loaded. This was enabled by default and also specified in the config file.
    [ 21.763] (II) LoadModule: "glx"
    [ 21.856] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 22.220] (II) Module glx: vendor="X.Org Foundation"
    [ 22.220] compiled for 1.16.4, module version = 1.0.0
    [ 22.220] ABI class: X.Org Server Extension, version 8.0
    [ 22.220] (==) AIGLX enabled
    [ 22.220] (II) LoadModule: "intel"
    [ 22.220] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
    [ 22.286] (II) Module intel: vendor="X.Org Foundation"
    [ 22.286] compiled for 1.16.3, module version = 2.99.917
    [ 22.286] Module class: X.Org Video Driver
    [ 22.286] ABI class: X.Org Video Driver, version 18.0
    [ 22.286] (II) LoadModule: "nvidia"
    [ 22.286] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
    [ 22.367] (II) Module nvidia: vendor="NVIDIA Corporation"
    [ 22.367] compiled for 4.0.2, module version = 1.0.0
    [ 22.367] Module class: X.Org Video Driver
    [ 22.374] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
    i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
    915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
    Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
    GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
    [ 22.375] (II) intel: Driver for Intel(R) HD Graphics: 2000-6000
    [ 22.375] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100
    [ 22.375] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200, 6200, P6300
    [ 22.375] (II) NVIDIA dlloader X Driver 346.35 Sat Jan 10 20:32:18 PST 2015
    [ 22.375] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
    [ 22.386] (++) using VT number 7
    [ 22.429] (II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0 20140905
    [ 22.483] (II) Loading sub module "fb"
    [ 22.483] (II) LoadModule: "fb"
    [ 22.483] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 22.502] (II) Module fb: vendor="X.Org Foundation"
    [ 22.502] compiled for 1.16.4, module version = 1.0.0
    [ 22.502] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 22.502] (II) Loading sub module "wfb"
    [ 22.502] (II) LoadModule: "wfb"
    [ 22.502] (II) Loading /usr/lib/xorg/modules/libwfb.so
    [ 22.510] (II) Module wfb: vendor="X.Org Foundation"
    [ 22.511] compiled for 1.16.4, module version = 1.0.0
    [ 22.511] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 22.511] (II) Loading sub module "ramdac"
    [ 22.511] (II) LoadModule: "ramdac"
    [ 22.511] (II) Module "ramdac" already built-in
    [ 22.704] (--) intel(0): Integrated Graphics Chipset: Intel(R) HD Graphics 3000
    [ 22.704] (--) intel(0): CPU: x86-64, sse2, sse3, ssse3, sse4.1, sse4.2, avx
    [ 22.704] (==) intel(0): Depth 24, (--) framebuffer bpp 32
    [ 22.704] (==) intel(0): RGB weight 888
    [ 22.704] (==) intel(0): Default visual is TrueColor
    [ 22.705] (II) intel(0): Output LVDS1 using monitor section Monitor0
    [ 22.705] (--) intel(0): Found backlight control interface acpi_video0 (type 'firmware') for output LVDS1
    [ 22.705] (II) intel(0): Enabled output LVDS1
    [ 22.705] (II) intel(0): Output VGA1 has no monitor section
    [ 22.705] (II) intel(0): Enabled output VGA1
    [ 22.705] (II) intel(0): Output HDMI1 has no monitor section
    [ 22.705] (II) intel(0): Enabled output HDMI1
    [ 22.705] (II) intel(0): Output DP1 has no monitor section
    [ 22.705] (II) intel(0): Enabled output DP1
    [ 22.705] (--) intel(0): Using a maximum size of 256x256 for hardware cursors
    [ 22.706] (II) intel(0): Output VIRTUAL1 has no monitor section
    [ 22.706] (II) intel(0): Enabled output VIRTUAL1
    [ 22.706] (--) intel(0): Output LVDS1 using initial mode 1366x768 on pipe 0
    [ 22.706] (==) intel(0): TearFree disabled
    [ 22.706] (==) intel(0): DPI set to (96, 96)
    [ 22.706] (II) Loading sub module "dri2"
    [ 22.706] (II) LoadModule: "dri2"
    [ 22.706] (II) Module "dri2" already built-in
    [ 22.706] (II) Loading sub module "present"
    [ 22.706] (II) LoadModule: "present"
    [ 22.706] (II) Module "present" already built-in
    [ 22.706] (==) NVIDIA(1): Depth 24, (==) framebuffer bpp 32
    [ 22.706] (==) NVIDIA(1): RGB weight 888
    [ 22.706] (==) NVIDIA(1): Default visual is TrueColor
    [ 22.706] (==) NVIDIA(1): Using gamma correction (1.0, 1.0, 1.0)
    [ 22.740] (**) NVIDIA(1): Enabling 2D acceleration
    [ 22.740] (EE) NVIDIA(1): Failed to initialize the GLX module; please check in your X
    [ 22.740] (EE) NVIDIA(1): log file that the GLX module has been loaded in your X
    [ 22.740] (EE) NVIDIA(1): server, and that the module is the NVIDIA GLX module. If
    [ 22.740] (EE) NVIDIA(1): you continue to encounter problems, Please try
    [ 22.740] (EE) NVIDIA(1): reinstalling the NVIDIA driver.
    [ 24.454] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 24.455] (II) NVIDIA(GPU-0): Found DRM driver nvidia-drm (20130102)
    [ 24.456] (II) NVIDIA(1): NVIDIA GPU GeForce GT 630M (GF108) at PCI:1:0:0 (GPU-0)
    [ 24.456] (--) NVIDIA(1): Memory: 2097152 kBytes
    [ 24.456] (--) NVIDIA(1): VideoBIOS: 70.08.92.00.fa
    [ 24.456] (II) NVIDIA(1): Detected PCI Express Link width: 16X
    [ 24.461] (--) NVIDIA(1): Valid display device(s) on GeForce GT 630M at PCI:1:0:0
    [ 24.461] (--) NVIDIA(1): CRT-0 (boot, connected)
    [ 24.461] (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
    [ 24.461] (**) NVIDIA(1): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 24.461] (**) NVIDIA(1): device CRT-0 (Using EDID frequencies has been enabled on
    [ 24.461] (**) NVIDIA(1): all display devices.)
    [ 24.463] (==) NVIDIA(1):
    [ 24.463] (==) NVIDIA(1): No modes were requested; the default mode "nvidia-auto-select"
    [ 24.463] (==) NVIDIA(1): will be used as the requested mode.
    [ 24.463] (==) NVIDIA(1):
    [ 24.463] (II) NVIDIA(1): Validated MetaModes:
    [ 24.463] (II) NVIDIA(1): "CRT-0:nvidia-auto-select"
    [ 24.463] (II) NVIDIA(1): Virtual screen size determined to be 1024 x 768
    [ 24.473] (WW) NVIDIA(1): CRT-0 does not have an EDID, or its EDID does not contain a
    [ 24.473] (WW) NVIDIA(1): maximum image size; cannot compute DPI from CRT-0's EDID.
    [ 24.473] (==) NVIDIA(1): DPI set to (75, 75); computed from built-in default
    [ 24.473] (--) Depth 24 pixmap format is 32 bpp
    [ 24.515] (II) intel(0): SNA initialized with Sandybridge (gen6, gt2) backend
    [ 24.515] (==) intel(0): Backing store enabled
    [ 24.515] (==) intel(0): Silken mouse enabled
    [ 24.516] (II) intel(0): HW Cursor enabled
    [ 24.516] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    [ 24.524] (==) intel(0): DPMS enabled
    [ 24.525] (==) intel(0): display hotplug detection enabled
    [ 24.525] (II) intel(0): [DRI2] Setup complete
    [ 24.525] (II) intel(0): [DRI2] DRI driver: i965
    [ 24.525] (II) intel(0): [DRI2] VDPAU driver: i965
    [ 24.525] (II) intel(0): direct rendering: DRI2 enabled
    [ 24.525] (II) intel(0): hardware support for Present enabled
    [ 24.525] (--) RandR disabled
    [ 24.525] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory
    [ 24.525] (II) NVIDIA: access.
    [ 24.529] (II) NVIDIA(1): ACPI: failed to connect to the ACPI event daemon; the daemon
    [ 24.529] (II) NVIDIA(1): may not be running or the "AcpidSocketPath" X
    [ 24.529] (II) NVIDIA(1): configuration option may not be set correctly. When the
    [ 24.530] (II) NVIDIA(1): ACPI event daemon is available, the NVIDIA X driver will
    [ 24.530] (II) NVIDIA(1): try to use it to receive ACPI event notifications. For
    [ 24.530] (II) NVIDIA(1): details, please see the "ConnectToAcpid" and
    [ 24.530] (II) NVIDIA(1): "AcpidSocketPath" X configuration options in Appendix B: X
    [ 24.530] (II) NVIDIA(1): Config Options in the README.
    [ 24.536] (II) NVIDIA(1): Setting mode "CRT-0:nvidia-auto-select"
    [ 24.649] (==) NVIDIA(1): Disabling shared memory pixmaps
    [ 24.649] (==) NVIDIA(1): Backing store enabled
    [ 24.649] (==) NVIDIA(1): Silken mouse enabled
    [ 24.649] (==) NVIDIA(1): DPMS enabled
    [ 24.663] (II) Loading sub module "dri2"
    [ 24.663] (II) LoadModule: "dri2"
    [ 24.663] (II) Module "dri2" already built-in
    [ 24.663] (II) NVIDIA(1): [DRI2] Setup complete
    [ 24.663] (II) NVIDIA(1): [DRI2] VDPAU driver: nvidia
    [ 24.663] (--) RandR disabled
    [ 24.872] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
    [ 24.872] (II) AIGLX: enabled GLX_ARB_create_context
    [ 24.872] (II) AIGLX: enabled GLX_ARB_create_context_profile
    [ 24.872] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
    [ 24.872] (II) AIGLX: enabled GLX_INTEL_swap_event
    [ 24.872] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
    [ 24.872] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
    [ 24.872] (II) AIGLX: enabled GLX_ARB_fbconfig_float
    [ 24.872] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
    [ 24.872] (II) AIGLX: enabled GLX_ARB_create_context_robustness
    [ 24.872] (II) AIGLX: Loaded and initialized i965
    [ 24.872] (II) GLX: Initialized DRI2 GL provider for screen 0
    [ 24.873] (II) AIGLX: Screen 1 is not DRI2 capable
    [ 24.873] (EE) AIGLX: reverting to software rendering
    [ 25.619] (II) AIGLX: Loaded and initialized swrast
    [ 25.619] (II) GLX: Initialized DRISWRAST GL provider for screen 1
    [ 25.634] (II) intel(0): switch to mode [email protected] on LVDS1 using pipe 0, position (0, 0), rotation normal, reflection none
    [ 25.640] (II) intel(0): Setting screen physical size to 361 x 203
    [ 25.988] (II) config/udev: Adding input device Power Button (/dev/input/event3)
    [ 25.988] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 25.988] (II) LoadModule: "evdev"
    [ 25.988] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 26.030] (II) Module evdev: vendor="X.Org Foundation"
    [ 26.030] compiled for 1.16.2, module version = 2.9.1
    [ 26.030] Module class: X.Org XInput Driver
    [ 26.030] ABI class: X.Org XInput driver, version 21.0
    [ 26.030] (II) Using input driver 'evdev' for 'Power Button'
    [ 26.030] (**) Power Button: always reports core events
    [ 26.031] (**) evdev: Power Button: Device: "/dev/input/event3"
    [ 26.031] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 26.031] (--) evdev: Power Button: Found keys
    [ 26.031] (II) evdev: Power Button: Configuring as keyboard
    [ 26.031] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input7/event3"
    [ 26.031] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    [ 26.031] (**) Option "xkb_rules" "evdev"
    [ 26.031] (**) Option "xkb_model" "pc104"
    [ 26.031] (**) Option "xkb_layout" "us"
    [ 26.086] (II) config/udev: Adding input device Video Bus (/dev/input/event6)
    [ 26.086] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
    [ 26.086] (II) Using input driver 'evdev' for 'Video Bus'
    [ 26.086] (**) Video Bus: always reports core events
    [ 26.086] (**) evdev: Video Bus: Device: "/dev/input/event6"
    [ 26.086] (--) evdev: Video Bus: Vendor 0 Product 0x6
    [ 26.086] (--) evdev: Video Bus: Found keys
    [ 26.086] (II) evdev: Video Bus: Configuring as keyboard
    [ 26.086] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input14/event6"
    [ 26.086] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
    [ 26.086] (**) Option "xkb_rules" "evdev"
    [ 26.086] (**) Option "xkb_model" "pc104"
    [ 26.086] (**) Option "xkb_layout" "us"
    [ 26.087] (II) config/udev: Adding input device Video Bus (/dev/input/event5)
    [ 26.087] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
    [ 26.087] (II) Using input driver 'evdev' for 'Video Bus'
    [ 26.087] (**) Video Bus: always reports core events
    [ 26.087] (**) evdev: Video Bus: Device: "/dev/input/event5"
    [ 26.087] (--) evdev: Video Bus: Vendor 0 Product 0x6
    [ 26.087] (--) evdev: Video Bus: Found keys
    [ 26.087] (II) evdev: Video Bus: Configuring as keyboard
    [ 26.087] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:4c/LNXVIDEO:00/input/input13/event5"
    [ 26.087] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 8)
    [ 26.087] (**) Option "xkb_rules" "evdev"
    [ 26.088] (**) Option "xkb_model" "pc104"
    [ 26.088] (**) Option "xkb_layout" "us"
    [ 26.088] (II) config/udev: Adding input device Lid Switch (/dev/input/event1)
    [ 26.088] (II) No input driver specified, ignoring this device.
    [ 26.088] (II) This device may have been added with another device file.
    [ 26.089] (II) config/udev: Adding input device Sleep Button (/dev/input/event2)
    [ 26.089] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
    [ 26.089] (II) Using input driver 'evdev' for 'Sleep Button'
    [ 26.089] (**) Sleep Button: always reports core events
    [ 26.089] (**) evdev: Sleep Button: Device: "/dev/input/event2"
    [ 26.089] (--) evdev: Sleep Button: Vendor 0 Product 0x3
    [ 26.089] (--) evdev: Sleep Button: Found keys
    [ 26.089] (II) evdev: Sleep Button: Configuring as keyboard
    [ 26.089] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input6/event2"
    [ 26.089] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 9)
    [ 26.089] (**) Option "xkb_rules" "evdev"
    [ 26.089] (**) Option "xkb_model" "pc104"
    [ 26.089] (**) Option "xkb_layout" "us"
    [ 26.090] (II) config/udev: Adding drm device (/dev/dri/card1)
    [ 26.090] (II) xfree86: Adding drm device (/dev/dri/card1)
    [ 26.090] (EE) /dev/dri/card1: failed to set DRM interface version 1.4: Permission denied
    [ 26.091] (II) config/udev: Adding input device USB 2.0 UVC VGA WebCam (/dev/input/event12)
    [ 26.091] (**) USB 2.0 UVC VGA WebCam: Applying InputClass "evdev keyboard catchall"
    [ 26.091] (II) Using input driver 'evdev' for 'USB 2.0 UVC VGA WebCam'
    [ 26.091] (**) USB 2.0 UVC VGA WebCam: always reports core events
    [ 26.091] (**) evdev: USB 2.0 UVC VGA WebCam: Device: "/dev/input/event12"
    [ 26.091] (--) evdev: USB 2.0 UVC VGA WebCam: Vendor 0x13d3 Product 0x5710
    [ 26.091] (--) evdev: USB 2.0 UVC VGA WebCam: Found keys
    [ 26.091] (II) evdev: USB 2.0 UVC VGA WebCam: Configuring as keyboard
    [ 26.091] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/input/input19/event12"
    [ 26.091] (II) XINPUT: Adding extended input device "USB 2.0 UVC VGA WebCam" (type: KEYBOARD, id 10)
    [ 26.091] (**) Option "xkb_rules" "evdev"
    [ 26.091] (**) Option "xkb_model" "pc104"
    [ 26.091] (**) Option "xkb_layout" "us"
    [ 26.092] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event9)
    [ 26.092] (II) No input driver specified, ignoring this device.
    [ 26.092] (II) This device may have been added with another device file.
    [ 26.093] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event10)
    [ 26.093] (II) No input driver specified, ignoring this device.
    [ 26.093] (II) This device may have been added with another device file.
    [ 26.093] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=3 (/dev/input/event11)
    [ 26.093] (II) No input driver specified, ignoring this device.
    [ 26.093] (II) This device may have been added with another device file.
    [ 26.094] (II) config/udev: Adding input device Logitech USB Optical Mouse (/dev/input/event13)
    [ 26.094] (**) Logitech USB Optical Mouse: Applying InputClass "evdev pointer catchall"
    [ 26.094] (II) Using input driver 'evdev' for 'Logitech USB Optical Mouse'
    [ 26.094] (**) Logitech USB Optical Mouse: always reports core events
    [ 26.094] (**) evdev: Logitech USB Optical Mouse: Device: "/dev/input/event13"
    [ 26.094] (--) evdev: Logitech USB Optical Mouse: Vendor 0x46d Product 0xc05a
    [ 26.094] (--) evdev: Logitech USB Optical Mouse: Found 3 mouse buttons
    [ 26.094] (--) evdev: Logitech USB Optical Mouse: Found scroll wheel(s)
    [ 26.094] (--) evdev: Logitech USB Optical Mouse: Found relative axes
    [ 26.094] (--) evdev: Logitech USB Optical Mouse: Found x and y relative axes
    [ 26.094] (II) evdev: Logitech USB Optical Mouse: Configuring as mouse
    [ 26.094] (II) evdev: Logitech USB Optical Mouse: Adding scrollwheel support
    [ 26.094] (**) evdev: Logitech USB Optical Mouse: YAxisMapping: buttons 4 and 5
    [ 26.094] (**) evdev: Logitech USB Optical Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 26.094] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1/4-1.1:1.0/0003:046D:C05A.0001/input/input20/event13"
    [ 26.094] (II) XINPUT: Adding extended input device "Logitech USB Optical Mouse" (type: MOUSE, id 11)
    [ 26.095] (II) evdev: Logitech USB Optical Mouse: initialized for relative axes.
    [ 26.095] (**) Logitech USB Optical Mouse: (accel) keeping acceleration scheme 1
    [ 26.095] (**) Logitech USB Optical Mouse: (accel) acceleration profile 0
    [ 26.095] (**) Logitech USB Optical Mouse: (accel) acceleration factor: 2.000
    [ 26.095] (**) Logitech USB Optical Mouse: (accel) acceleration threshold: 4
    [ 26.096] (II) config/udev: Adding input device Logitech USB Optical Mouse (/dev/input/mouse1)
    [ 26.096] (II) No input driver specified, ignoring this device.
    [ 26.096] (II) This device may have been added with another device file.
    [ 26.096] (II) config/udev: Adding input device Asus WMI hotkeys (/dev/input/event8)
    [ 26.096] (**) Asus WMI hotkeys: Applying InputClass "evdev keyboard catchall"
    [ 26.096] (II) Using input driver 'evdev' for 'Asus WMI hotkeys'
    [ 26.096] (**) Asus WMI hotkeys: always reports core events
    [ 26.096] (**) evdev: Asus WMI hotkeys: Device: "/dev/input/event8"
    [ 26.096] (--) evdev: Asus WMI hotkeys: Vendor 0 Product 0
    [ 26.096] (--) evdev: Asus WMI hotkeys: Found keys
    [ 26.096] (II) evdev: Asus WMI hotkeys: Configuring as keyboard
    [ 26.096] (**) Option "config_info" "udev:/sys/devices/platform/asus-nb-wmi/input/input15/event8"
    [ 26.096] (II) XINPUT: Adding extended input device "Asus WMI hotkeys" (type: KEYBOARD, id 12)
    [ 26.096] (**) Option "xkb_rules" "evdev"
    [ 26.096] (**) Option "xkb_model" "pc104"
    [ 26.096] (**) Option "xkb_layout" "us"
    [ 26.097] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
    [ 26.097] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
    [ 26.097] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
    [ 26.097] (**) AT Translated Set 2 keyboard: always reports core events
    [ 26.097] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
    [ 26.098] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
    [ 26.098] (--) evdev: AT Translated Set 2 keyboard: Found keys
    [ 26.098] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
    [ 26.098] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
    [ 26.098] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 13)
    [ 26.098] (**) Option "xkb_rules" "evdev"
    [ 26.098] (**) Option "xkb_model" "pc104"
    [ 26.098] (**) Option "xkb_layout" "us"
    [ 26.099] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event7)
    [ 26.099] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
    [ 26.099] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
    [ 26.099] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default clickpad buttons"
    [ 26.099] (II) LoadModule: "synaptics"
    [ 26.099] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
    [ 26.109] (II) Module synaptics: vendor="X.Org Foundation"
    [ 26.109] compiled for 1.16.0, module version = 1.8.1
    [ 26.109] Module class: X.Org XInput Driver
    [ 26.109] ABI class: X.Org XInput driver, version 21.0
    [ 26.109] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
    [ 26.109] (**) SynPS/2 Synaptics TouchPad: always reports core events
    [ 26.109] (**) Option "Device" "/dev/input/event7"
    [ 26.210] (II) synaptics: SynPS/2 Synaptics TouchPad: ignoring touch events for semi-multitouch device
    [ 26.210] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5762 (res 52)
    [ 26.210] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4902 (res 83)
    [ 26.210] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
    [ 26.210] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
    [ 26.210] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left right double triple
    [ 26.210] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
    [ 26.210] (**) Option "TapButton1" "1"
    [ 26.210] (**) Option "TapButton2" "2"
    [ 26.210] (**) Option "TapButton3" "3"
    [ 26.210] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    [ 26.210] (**) SynPS/2 Synaptics TouchPad: always reports core events
    [ 26.263] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio4/input/input12/event7"
    [ 26.263] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 14)
    [ 26.263] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
    [ 26.263] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MaxSpeed is now 1.75
    [ 26.263] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) AccelFactor is now 0.036
    [ 26.264] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
    [ 26.264] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
    [ 26.264] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
    [ 26.264] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
    [ 26.264] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    [ 26.264] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0)
    [ 26.265] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates"
    [ 26.265] (II) config/udev: Adding input device PC Speaker (/dev/input/event4)
    [ 26.265] (II) No input driver specified, ignoring this device.
    [ 26.265] (II) This device may have been added with another device file.
    [ 26.282] removing GPU device /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card1 /dev/dri/card1
    [ 26.282] (II) config/udev: Adding drm device (/dev/dri/card1)
    [ 26.282] (II) xfree86: Adding drm device (/dev/dri/card1)
    [ 26.282] (EE) /dev/dri/card1: failed to set DRM interface version 1.4: Permission denied
    [ 81.255] (II) intel(0): EDID vendor "AUO", prod id 9964
    [ 81.255] (II) intel(0): Printing DDC gathered Modelines:
    [ 81.255] (II) intel(0): Modeline "1366x768"x0.0 71.80 1366 1414 1446 1526 768 771 777 784 -hsync -vsync (47.1 kHz eP)
    [ 81.277] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 81.293] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 81.644] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 81.660] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 81.678] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 84.668] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 84.685] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 86.539] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 2962.717] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 2962.734] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 2966.160] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 2966.176] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 3045.352] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 3045.370] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 3066.487] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 3066.504] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 4507.909] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 4507.925] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 4568.870] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 4568.887] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 4749.685] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 4749.702] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 4841.172] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 4841.189] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 5067.684] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 5067.701] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 5098.091] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 5098.108] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 5231.697] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 5231.715] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 7726.903] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 7726.920] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 7989.858] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 7989.875] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 8118.003] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 8118.020] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 8525.573] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 8525.590] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 8645.496] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 8645.513] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 8787.791] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 8787.808] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 10010.206] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 10010.223] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 10511.439] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 10511.456] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 10576.580] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 10576.597] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 10758.287] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 10758.304] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 12833.372] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 12833.389] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 14722.424] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 14722.441] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 15499.091] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 15499.108] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 16138.293] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 16138.309] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 16563.842] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 16563.858] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 17097.871] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 17097.888] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 17958.793] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 17958.810] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 18046.490] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 18046.506] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 18286.639] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 18286.655] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 18857.140] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 18857.157] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 19683.981] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 19683.997] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 19746.465] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 19746.483] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 19801.499] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 19801.516] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 24516.593] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 24516.610] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 24714.424] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 24714.440] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 24733.954] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 24733.970] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 24794.748] (II) AIGLX: Suspending AIGLX clients for VT switch
    [ 24795.935] (II) AIGLX: Resuming AIGLX clients after VT switch
    [ 24795.935] (II) intel(0): switch to mode [email protected] on LVDS1 using pipe 0, position (0, 0), rotation normal, reflection none
    [ 24795.971] (II) NVIDIA(1): Setting mode "CRT-0:nvidia-auto-select"
    [ 24796.039] (II) NVIDIA(1): ACPI: failed to connect to the ACPI event daemon; the daemon
    [ 24796.039] (II) NVIDIA(1): may not be running or the "AcpidSocketPath" X
    [ 24796.039] (II) NVIDIA(1): configuration option may not be set correctly. When the
    [ 24796.039] (II) NVIDIA(1): ACPI event daemon is available, the NVIDIA X driver will
    [ 24796.039] (II) NVIDIA(1): try to use it to receive ACPI event notifications. For
    [ 24796.039] (II) NVIDIA(1): details, please see the "ConnectToAcpid" and
    [ 24796.039] (II) NVIDIA(1): "AcpidSocketPath" X configuration options in Appendix B: X
    [ 24796.040] (II) NVIDIA(1): Config Options in the README.
    [ 24796.057] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 24796.061] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    [ 25764.817] (II) AIGLX: Suspending AIGLX clients for VT switch
    [ 25766.007] (II) AIGLX: Resuming AIGLX clients after VT switch
    [ 25766.007] (II) intel(0): switch to mode [email protected] on LVDS1 using pipe 0, position (0, 0), rotation normal, reflection none
    [ 25766.036] (II) NVIDIA(1): Setting mode "CRT-0:nvidia-auto-select"
    [ 25766.104] (II) NVIDIA(1): ACPI: failed to connect to the ACPI event daemon; the daemon
    [ 25766.104] (II) NVIDIA(1): may not be running or the "AcpidSocketPath" X
    [ 25766.104] (II) NVIDIA(1): configuration option may not be set correctly. When the
    [ 25766.104] (II) NVIDIA(1): ACPI event daemon is available, the NVIDIA X driver will
    [ 25766.104] (II) NVIDIA(1): try to use it to receive ACPI event notifications. For
    [ 25766.104] (II) NVIDIA(1): details, please see the "ConnectToAcpid" and
    [ 25766.104] (II) NVIDIA(1): "AcpidSocketPath" X configuration options in Appendix B: X
    [ 25766.104] (II) NVIDIA(1): Config Options in the README.
    [ 25766.122] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 25766.129] (EE) evdev: Logitech USB Optical Mouse: Unable to open evdev device "/dev/input/event13".
    [ 25766.129] [dix] couldn't enable device 11
    [ 25766.129] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    [ 25766.132] (II) config/udev: removing device Logitech USB Optical Mouse
    [ 25766.132] (II) evdev: Logitech USB Optical Mouse: Close
    [ 25766.132] (II) UnloadModule: "evdev"
    [ 27662.047] (II) AIGLX: Suspending AIGLX clients for VT switch
    [ 27663.314] (II) AIGLX: Resuming AIGLX clients after VT switch
    [ 27663.314] (II) intel(0): switch to mode [email protected] on LVDS1 using pipe 0, position (0, 0), rotation normal, reflection none
    [ 27663.345] (II) NVIDIA(1): Setting mode "CRT-0:nvidia-auto-select"
    [ 27663.413] (II) NVIDIA(1): ACPI: failed to connect to the ACPI event daemon; the daemon
    [ 27663.413] (II) NVIDIA(1): may not be running or the "AcpidSocketPath" X
    [ 27663.413] (II) NVIDIA(1): configuration option may not be set correctly. When the
    [ 27663.413] (II) NVIDIA(1): ACPI event daemon is available, the NVIDIA X driver will
    [ 27663.413] (II) NVIDIA(1): try to use it to receive ACPI event notifications. For
    [ 27663.413] (II) NVIDIA(1): details, please see the "ConnectToAcpid" and
    [ 27663.413] (II) NVIDIA(1): "AcpidSocketPath" X configuration options in Appendix B: X
    [ 27663.413] (II) NVIDIA(1): Config Options in the README.
    [ 27663.431] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 27663.439] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    [ 27694.770] (II) config/udev: Adding input device Logitech USB Optical Mouse (/dev/input/event13)
    [ 27694.770] (**) Logitech USB Optical Mouse: Applying InputClass "evdev pointer catchall"
    [ 27694.770] (II) Using input driver 'evdev' for 'Logitech USB Optical Mouse'
    [ 27694.770] (**) Logitech USB Optical Mouse: always reports core events
    [ 27694.770] (**) evdev: Logitech USB Optical Mouse: Device: "/dev/input/event13"
    [ 27694.770] (--) evdev: Logitech USB Optical Mouse: Vendor 0x46d Product 0xc05a
    [ 27694.770] (--) evdev: Logitech USB Optical Mouse: Found 3 mouse buttons
    [ 27694.770] (--) evdev: Logitech USB Optical Mouse: Found scroll wheel(s)
    [ 27694.770] (--) evdev: Logitech USB Optical Mouse: Found relative axes
    [ 27694.770] (--) evdev: Logitech USB Optical Mouse: Found x and y relative axes
    [ 27694.770] (II) evdev: Logitech USB Optical Mouse: Configuring as mouse
    [ 27694.770] (II) evdev: Logitech USB Optical Mouse: Adding scrollwheel support
    [ 27694.770] (**) evdev: Logitech USB Optical Mouse: YAxisMapping: buttons 4 and 5
    [ 27694.770] (**) evdev: Logitech USB Optical Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 27694.770] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1/4-1.1:1.0/0003:046D:C05A.0002/input/input39/event13"
    [ 27694.770] (II) XINPUT: Adding extended input device "Logitech USB Optical Mouse" (type: MOUSE, id 11)
    [ 27694.771] (II) evdev: Logitech USB Optical Mouse: initialized for relative axes.
    [ 27694.771] (**) Logitech USB Optical Mouse: (accel) keeping acceleration scheme 1
    [ 27694.771] (**) Logitech USB Optical Mouse: (accel) acceleration profile 0
    [ 27694.771] (**) Logitech USB Optical Mouse: (accel) acceleration factor: 2.000
    [ 27694.771] (**) Logitech USB Optical Mouse: (accel) acceleration threshold: 4
    [ 27694.771] (II) config/udev: Adding input device Logitech USB Optical Mouse (/dev/input/mouse1)
    [ 27694.771] (II) No input driver specified, ignoring this device.
    [ 27694.771] (II) This device may have been added with another device file.
    [ 28826.102] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 28826.119] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 28869.273] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 28869.290] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 29665.856] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 29665.873] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 29759.751] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 29759.768] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 30246.231] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 30246.248] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 31539.152] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 31539.168] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 33130.297] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 33130.314] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 35115.805] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 35115.822] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 36739.995] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 36740.011] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 37099.972] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 37099.988] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 37115.693] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 37115.709] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 37292.799] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 37292.816] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 37896.583] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 37896.600] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 40947.452] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 40947.469] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 40999.729] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 40999.746] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 41027.146] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 41027.163] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 41198.146] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 41198.162] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 41405.365] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 41405.382] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 43125.113] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 43125.128] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 43212.374] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 43212.391] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 44006.946] (II) AIGLX: Suspending AIGLX clients for VT switch
    [ 44008.163] (II) AIGLX: Resuming AIGLX clients after VT switch
    [ 44008.163] (II) intel(0): switch to mode [email protected] on LVDS1 using pipe 0, position (0, 0), rotation normal, reflection none
    [ 44008.193] (II) NVIDIA(1): Setting mode "CRT-0:nvidia-auto-select"
    [ 44008.262] (II) NVIDIA(1): ACPI: failed to connect to the ACPI event daemon; the daemon
    [ 44008.262] (II) NVIDIA(1): may not be running or the "AcpidSocketPath" X
    [ 44008.262] (II) NVIDIA(1): configuration option may not be set correctly. When the
    [ 44008.262] (II) NVIDIA(1): ACPI event daemon is available, the NVIDIA X driver will
    [ 44008.262] (II) NVIDIA(1): try to use it to receive ACPI event notifications. For
    [ 44008.262] (II) NVIDIA(1): details, please see the "ConnectToAcpid" and
    [ 44008.262] (II) NVIDIA(1): "AcpidSocketPath" X configuration options in Appendix B: X
    [ 44008.262] (II) NVIDIA(1): Config Options in the README.
    [ 44008.280] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 44008.287] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    Please help me to resolve this.
    Last edited by vortex_ape (2015-02-22 14:39:47)

    I haven't been experiencing the issue for some hours.
    The issue occurred more frequently when I was compiling something. When I tried to reproduce the issue, it didn't occur.
    The interesting thing to note is that I updated the system twice in the past 2 days. I checked the pacman log and saw that xorg-server-common, xorg-server, xorg-server-devel were among the upgraded packages. I guess they were causing the problem.
    I'll need to test for a couple of days though before I consider the issue to be resolved. I'll update if the issue persists.

  • Mouse pointer freezes sometimes

    Whenever I unplug my iPod (shuffle) from the keyboard (of course after having the volume unmounted), some seconds later the mouse pointer freezes and the computer is totally unresponsive for some seconds. Then everything is normal again, i.e. the mouse pointer can be moved again.
    The "system.log" tells something about communication problems with the USB and bus reset or similar.
    Is this meant with "hot pluggable"? Should not the iPod be independent from the keyboard or mouse?

    As far as I remember:
    - It does not happen when directly connected to the computer
    - It has never happened with the G3, only with the G5
    And, yes, the iPod's firmware is the latest one.
    And: Connecting the iPod to the keyboard is just more convenient, even if it's slower. As the MacOS does multitasking, I do not mind if a data transfer runs with two megabytes per second or with one, because I can do something else in the meantime.

  • Need Urgent Help in PM8M-V H problem - keyboard freeze

    Hi everyone,
    I'm a newbie in this forum and I really need urgent help with my motherboard.
    My PC specification:
    Intel Pentium 4 2.4GHz
    MSI PM8M-V H W7104VMS v3.4 022206 14:32:17
    1GB(512MB x 2) Kingston PC3200 400MHz
    Seagate SATA II 320GB ST3320620SV (set with jumper to support SATA I)
    Power Color ATI Radeon 9550 256MB
    Lite-On DVDRW SHM-165P6S
    USB mouse, PS/2 Keyboard
    I really appreciate if anyone can help to guide me in solving my problem. My keyboard tends to freeze at the part where it says "Press any key to boot from CD". This limits me to do anything until I'm totally loaded into Windows.  Thus, disable me to perform any formating and fresh installation of OS. However, the keyboards works fine at the begining of the POST and in BIOS. Is there any settings in BIOS that i should perform?.....
    However, I realise in order to get through the foresaid message without the the keyboard freeze up is by keep on trying to boot up and shut down until it works (but only work once, then hv to try again), but this is not a solution as if what if I wanted to have 2 OS?... I cant use the keyboard to choose either of the OS installed. I have tried to change the RAM, change keyboard, use the build in VGA, or even remove the motherboard from the ATX casing - result: still have the same problem. What should I do??.. I have look around the forum for answers but there isnt any (I hope I didnt miss any). Is there any problem with my motherboard, or its BIOS, or any of the harware compatibility or etc..... what actually can I do?   
    I do not dare to perform any BIOS update Unnecessary (it seems that many have problems with BIOS problem in this forum) and moreover i think my BIOS is the most up-to-date. I cant find any new version in the net. Anyway I will check this topic frequently as possible to hope for any solution. What is the best solutions?
    Thanks.

    But the thing that makes me wonder is, my BIOS version is the latest but why this type of problem occurs??
    What version of BIOS should I use?? Any recommendation ??
    Thanks.

Maybe you are looking for

  • Sub Contracting Purchase Order

    Hi All What is table name and field name to see the alternative BOM status for Sub Contracting Purchase Orders? Example: I have a Material :Shaft, which has two alternative BOM's. When i placed the Sub Contracting order to the Vendor. System will exp

  • Object not found in lookup of SetDynamicConfiguration.

    Hi, We are doing File to Proxy Scenario, in the File adapter we used the SetDynamicConfiguration as the module with module Type as Local enterprise Bean and Paramaters as DynamicFeedeNS and _Simulate. during testing the  File adapter  shows log as "A

  • ITunes store does not match that of the gift card...

    I got a gift card from Germany and live in Switzerland. Apple support recommends to give it away to somebody living in Germany or so... Not very helpfull ! In internet there are some blogs how to install an account in a foreign country, but you have

  • Essbase not retaining formulas on retrieval in Excel

    Good Evening! Has anyone seen an instance where essbase won't retain formulas on retrieval in Excel? We are using Essbase v6.5.4 apparently rebooting the computer fixes the problem, but that is irritating. Is there a patch or a setting somewhere? Tha

  • Is it dangerous to repair permissions ?

    i mean is there the smallest risk i lose some compatibility or access or data or whatever you want in all my system ?? (im working professionaly with my mac with Pro Tools installed and if some pro tools sessions do not open or miss some files its a