Hardware Monitor Setup Freeze (K7T266Pro2) [SOLVED]

1.Product Type: K7T 266 Pro2 (6380 v2)
2.BIOS version: AMI V3.70
3.External VGA Type: ATI Radeon VE 7000 AGP 128Mo
4.CPU Type: Athlon XP 1600+
5.Memory Type: 2*256 Mo DDR PC2100 PQI
6.Power Supply Type: Heden PSXA870 380W with -5V output
7.Operating System: Win XP Pro Sp2
8.Problem Description:
When accessing to hardware monitor setup page in BIOS, I get a freeze that I can olny escape by Ctrl Alt Suppr.
I have made an update of Bios to V3.70 because a new module of memory I have bought make problems. This update do not change anything, so I remove this new module and don't use anymore.
But by updating, my CPU clock down to 1050 Mhz instead of 1333Mhz, due to FSB set to 100Mhz.
And impossible to access the page to set the parameter at 133Mhz due to a freeze.
How to solve the problem and get back the right configuration I had before ?
I have read that the problem may come from the power supplies that don't have -5V. I don't know what produce my PS, but how to prevent BIOS to check this -5V ?
EDIT : I have check my PS and it produce -5V.
Many thanks for your hlep.
Regards.
OLIVIER THIEBAUT

Merry Chrismas everydody.
Back with happy news :
- I have flash with v3.7 : flash OK
- Still getting the problem : hardware monitor page setup freeze, and unable to set FSB to 133Mhz and get the right CPU clock.
So, my solution :
- Looking for editing the AMI Bios file.
- I have load v3.70 Bios file in editor, and only change one parameter : I have set not active the -5V check in hardware monitor module.
- Save my new bios file (called it v3.71)
- Then, flash with that edited bios file
- And manage to access the Hardware Monitor Setup page to set the FSB at 133Mhe. No more freeze.
I don't know how to call this type of solution, but it works well.
For moderators, you can modify the subject by adding [solved] if you want.
Many thanks for everybody.

Similar Messages

  • [Solved]Dual Monitor Setup

    So, I inherited a new monitor from my friend just a couple days ago and had a go at setting it up. Here's my current setup, to illustrate:
    -- MOD EDIT -- Please follow image posting rules
    The one on the right is mirroring the left at the moment, which happened via default when I booted up. I have the monitor to the left plugged via a dvi cable, and the one to the right that is rotated (for the purpose of better viewing webpages) with plain old vga. Both are running off my only graphics card, a Radeon X300:
    $ lspci | grep VGA
    01:00.0 VGA compatible controller: ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)]
    Here is the compatible resolutions and refresh rates and such for each:
    $ xrandr
    Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 4096 x 4096
    VGA-0 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 376mm x 301mm
    1280x1024 60.0*+ 75.0
    1152x864 75.0
    1024x768 75.1 60.0
    800x600 75.0 60.3
    640x480 75.0 60.0
    720x400 70.1
    DVI-0 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 450mm x 280mm
    1680x1050 60.0 +
    1280x1024 75.0 60.0*
    1440x900 75.0 59.9
    1152x864 75.0 70.0 60.0
    1024x768 75.1 70.1 60.0
    832x624 74.6
    800x600 72.2 75.0 60.3 56.2
    640x480 72.8 75.0 66.7 60.0
    720x400 70.1
    S-video disconnected (normal left inverted right x axis y axis)
    So, this information aside, I went and tried to add my second screen and make everything happy, I used the dual screen section in the X.Org Wiki page, which I believe was for the nVidia users, but I couldn't find any direction otherwise, so I figured with a few changes it could work with my radeon just fine. I am on xorg-server 1.9.4.901-1 with openbox as my window manager, no complete DE.
    This is my current /etc/X11/xorg.conf.d/10-monitor.conf written for two monitors, which at the moment does not work, saying no screens found when I run startx:
    Section "ServerLayout"
    Identifier "DualScreen"
    Screen 0 "Screen0"
    Scren 1 "Screen1" RightOf "Screen0" #Screen1 is to the right of Screen0
    Option "Xinerama" "1" #To move windows between screens, set to 1
    EndScetion
    Section "Monitor"
    Identifier "Monitor0"
    Option "Enable" "true"
    EndSection
    Section "Monitor"
    Identifier "Monitor0"
    Option "Enable" "true"
    EndSection
    Section "Device"
    Identifier "Device0"
    Driver "radeon"
    Screen 0
    EndSection
    Section "Device"
    Identifier "Device1"
    Driver "radeon"
    Screen 1
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Device0"
    Monitor "Monitor0"
    DefaultDepth 24
    Option "TwinView" "0" #Set to 1 to make both monitors act as one big screen, with no distinction between the two
    SubSection "Display"
    Depth 24
    Modes "1680x1050_60.00"
    EndSubSection
    EndSection
    Section "Screen"
    Identifier "Screen1"
    Device "Device1"
    Monitor" "Monitor1"
    DefaultDepth 24
    Option "TwinView" "0"
    SubSection "Display"
    Depth 24
    Modes 1280x1024_75.00
    EndSubSection
    EndSection
    And here is the same file, in a working configuration:
    Section "Monitor"
    Identifier "Monitor0"
    EndSection
    Section "Device"
    Identifier "Device0"
    Driver "radeon" #Driver used for this monitor
    EndSection
    Section "Screen"
    Identifier "Screen0" #Collapse Monitor and Device section to Screen section
    Device "Device0"
    Monitor "Monitor0"
    DefaultDepth 24 #Choose the Depth (16 || 24) (24 for true colour)
    Subsection "Display"
    Depth 24
    Modes "1680x1050_75.00" #Choose the resolution
    EndSubSection
    EndSection
    This leaves me with 3 questions I cannot seem to figure out:
    1) What did I do wrong with the non-working xorg config file, giving the error "no screens found"?
    2) Another extra twist of difficulty comes from the rotated monitor on the right.  How should I adopt for that, with resolutions and such?
    3) Xinerama/Twinview  - I am confused which one of these I should choose, what they offer over the other, or should I just not bother at all?
    I would like, in a "perfectly good configuration", windows to be able to move from each monitor to the other, the monitors to be two distinct monitors (ie. they don't mirror each other), a maximized window to only fill up just the one monitor (and not both), and finally, fullscreen programs (like games and such) only fullscreen to the monitor they are on. Is such a configuration possible with all of these parameters?
    -Scott
    Last edited by Inxsible (2011-06-05 18:33:38)

    BurntSushi wrote:
    Your desired configuration is quite common, and indeed, is the default setup provided by Openbox---once the monitors are properly configured, of course :-)
    Anywho, modifying xorg.conf files for something like this is a thing of the past, man. (Incidentally, you have made the lethal mistake of assuming an nvidia config will work with an ATI card. For example, "TwinView" is only available when you are using the nvidia proprietary driver.)
    Judging by your use of "radeon" as your video driver, it looks like you're using xf86-video-ati. Therefore, congratulations, xrandr will rescue you :-) (This should also be the case if you you're using the Catalyst driver.)
    thinkwiki should be enough to get your feet wet. Note: This guide is a bit dated, but 90% of it is still relevant and useful. For example, it claims that you need to modify your xorg.conf to add a Virtual screen size---this is only true if kernel modesetting is disabled. If it's enabled (and it should be if you're using xf86-video-ati), then you're good to go. If you're using Catalyst, you will have had to disable KMS. So you'd either have to add a Virtual screen to use xrandr, or configure your monitor setup with amdcccle.
    Finally, you asked about rotation. I don't think this is anything that `man xrandr` can't answer, and you should be okay as far as support goes---rotation was added in RandR 1.2, which any civilized video driver should support. (Except nvidia blob.)
    Anywho, feel free to come back with more questions if you have any!
    (For terminology sake, this means you will be using neither Xinerama nor TwinView to configure your multi-monitors. You will be using RandR if you use xrandr. Interestingly, your screen setup will still be reported to Openbox via the Xinerama extension. You may be interested in a utility like `lxrandr` if the command line frightens you.)
    Xrandr does the job elegantly, thanks! It's a simple matter of putting the commands I needed in openbox's autostart.sh. Thanks for pointing me in the right direction.
    #xrandr --output DVI-0 1680x1050 --output VGA-0 1280x1024 --right-of DVI-0
    # xrandr --output VGA-0 --rotate left
    Scott

  • [Solved] gs60 ghost pro triple monitor setup??

    any one try to put a display port hub on the gs60 ghost pro something like the 3d-club MST
    link: http://www.club-3d.com/index.php/products/reader.en/product/mst-hub-1-3.html
    i have a triple monitor setup for my desktop machine and i was wondering if it is possible to just plug my gs60 into a USB hub for sound, keyboard, and mouse. then a MST display port hub just dock and game. from what i read online the GTX 870M will work in this configuration i just want to know if anyone here has tried it?

    Quote from: Yippyyay;104043
    any one try to put a display port hub on the gs60 ghost pro something like the 3d-club MST
    link: http://www.club-3d.com/index.php/products/reader.en/product/mst-hub-1-3.html
    i have a triple monitor setup for my desktop machine and i was wondering if it is possible to just plug my gs60 into a USB hub for sound, keyboard, and mouse. then a MST display port hub just dock and game. from what i read online the GTX 870M will work in this configuration i just want to know if anyone here has tried it?
    Yes, it works.

  • Dual monitor setup MBA 2013

    Hello Everyone,
    This is my first post on the Apple Support Community.
    Nice to meet al of you!
    System information:
    Macbook Air medio 2013
    Model MacBookAir6,2
    Intel Core i7 1,7GHZ
    8GB
    512GB SSD
    I am wondering if it is possible to have a dual monitor setup using the thunderbolt feature daisy-chain.
    The configuration i am looking for is:
    MBA --> Belkin Thunderbolt™ Express Dock (for using gigabit ethernet) --> Dell U2414H --> Dell U2414H
    Specs:
    Belkin Thunderbolt™ Express Dock = http://www.belkin.com/us/p/P-F4U055/
    Dell U2414H = http://accessories.us.dell.com/sna/productdetail.aspx?c=us&cs=04&l=en&sku=860-BB CG
    Do i have a chance this could work?
    I'm looking forward to hearing from you all.
    Thanks!
    Kind regards,
    Njamo187

    Hello,
    I had the same problem with a nVidia GT120 card (2009 Mac Pro standard). OSX wouldn't show the gray screen on the 3090, even when it was connected alone (to the DVI port). Also, the login screen would always revert to the secondary display (connected thru the mini display port to DVI adapter).
    After login, all was well.
    Now I've solved the problem with an nVidia GTX 285 card. The 3090 is connected to the n.1 DVI port and the secondary display (a 1600x1200 Eizo L997) to the n.2 DVI port, and the Mac Pro boots correctly on the 3090 (gray screen and everything, at full 2560x1600 resolution).
    Note that the first time I booted up the Mac after replacing the GT120 with the GTX 285 I had the same problem, and solved it by disconnecting the secondary display and then rebooting with the 3090 alone. Now everything works as it should.
    Dont't know if there is a bug somewhere (EFI, maybe) of if the GT120 and your ATI are simply unable to work at full resolution before OSX desktop loading.

  • Dual monitor setup broken in Leopard

    There are numerous problems running an external Cinema Display from a MacBook Pro using Leopard. I've tried with 2 MacBook Pros (one 15", one 17") and 2 different Cinema Displays (24" and 30"). Not to mention everything was fine under Tiger. Both Leopard installations were "clean installs".
    1. Closing the lid of the MBP doesn’t remove the screen from Leopard (Or Spaces).
    2. When the MBP sleeps with a Display attached it never comes back onto the Display, only the MBP’s LCD.
    3. Periodically the MBP refuses to wake when it’s connected to the display.
    4. I can no longer use the power button on the Display to sleep/shutdown the MBP.
    5. Simply plugging the Display sometimes causes it to wake (while the MBP is closed). In Tiger, I had to have the Power Adapter connected to wake my Sleeping MBP with the lid closed (as stated in the documentation).
    Wonder if all this will be fixed in 10.5.1 (hoping)?

    Firefox doesn't always play well with a multiple monitor setup and hardware acceleration.
    Try to disable hardware acceleration.
    *Tools > Options > Advanced > General > Browsing: "Use hardware acceleration when available"
    *https://support.mozilla.org/kb/how-do-i-upgrade-my-graphics-drivers

  • In dual monitor setup firefox 9.01 menus blink in and out

    Every version of firefox AFTER the 3.6 series has problems in dual monitor setups and I want to be able to keep all tabs I had open when I close firefox so when I open again they are there. In dual monitor if I use monitor 2 for firefox (which is the way I use it) the menu blink rapidly when I click on them and make very hard to navigate. What is it with the video setup in win7 I have to use an older version of winamp due to tearing in the second monitor? Have all you companies not fully learned who to implement dual monitor setups properly or is that not really a concern?

    Firefox doesn't always play well with a multiple monitor setup and hardware acceleration.
    Try to disable hardware acceleration.
    *Tools > Options > Advanced > General > Browsing: "Use hardware acceleration when available"
    *https://support.mozilla.org/kb/how-do-i-upgrade-my-graphics-drivers

  • Dual-monitor setup + screen rotation

    Hello, I want to use my desktop computer with a dual-monitor setup. I have connected both monitors successfully, but problems arise after this point.
    The first problem is that they both just display the same screen and that xrandr only detects one screen called "Screen 0". I can change the screen resolution with it, so at least it sees things correctly, but I don't know how to extend my screen area to a new desktop. Not sure if this is relevant, but they're both monitors of the same model.
    output of xrandr wrote:[user@archbang ~]$ xrandr
    xrandr: Failed to get size of gamma for output default
    Screen 0: minimum 640 x 480, current 1600 x 1200, maximum 1600 x 1200
    default connected 1600x1200+0+0 0mm x 0mm
       1600x1200       0.0*
       1280x1024       0.0 
       1024x768        0.0 
       800x600         0.0 
       640x480         0.0
    The second problem is that I can't rotate my screen (I want this because it has pivot functionality). I'm using the xf86-video-ati driver.
    output of xrandr -o left wrote:[user@archbang ~]$ xrandr -o left
    X Error of failed request:  BadMatch (invalid parameter attributes)
      Major opcode of failed request:  149 (RANDR)
      Minor opcode of failed request:  2 (RRSetScreenConfig)
      Serial number of failed request:  14
      Current serial number in output stream:  14
    I hope I've provided enough information. Thanks in advance.
    Last edited by Ffeiofewpoj (2012-01-28 08:03:04)

    I meant to post this in the Kernel & Hardware section and I've no clue how it ended up here. Sorry for that. Could someone move it?
    Last edited by Ffeiofewpoj (2012-01-27 13:25:01)

  • Win 8.1 not remembering dual monitor setup after reboot

    Hello,
    I am running Windows 8.1 64-bit Enterprise N with the following hardware:
    HP ENVY TouchSmart 4-1245tu Sleekbook with Intel HD 4000 Graphics
    Dell Monitor
    HDMI Out from laptop to VBGA In on monitor (HDMI to VGA Convertor used to connect with second monitor).
    I have setup multiple monitors and it works fine. However once I do a reboot on the laptop the machine, after reboot only laptop screen is detected and second monitor/external monitor not detected ( it is blank with the External monitor having its backlight on (so its not in standby) but nothing is being sent to it.)
    It looks as if Windows 8.1 is not remembering the extend monitor setup after a reboot.
    I am running the latest drivers from Intel for Windows 8.1 64 bit and Intel 4000 graphics:
    Release Version: Production Version
    Driver Version: 15.33.5.64.3316
    Package: 209756
    Intel(R) Graphics Driver: 10.18.10.3316
    Intel(R) Display Audio Driver: 6.16.0.3123
    Operating System(s):  
    Microsoft Windows* 8.1 64-bit
    Release Date: October 04, 2013
    Downloaded from intel site - https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=23405&lang=eng 
    Any ideas?

    I have the same problem with HP8300 Elite CMT
    Dual monitor works fine after reinstalling the video drivers.
    When I restart the PC the second monitor is not found and the drivers have to be reinstalled.
    I have opened a support case
    Case ID <4648891774>
    Waiting for feedback - if the problem is resolved  - I will post an update

  • Monitor setup has changed - KDE Daemon after sleep

    After the monitor goes into powersave mode and is restored I keep gettung the Monitor setup has changed - KDE Daemon  box, anyone know how to get rid of this? everything seams to work but the box is getting annoying.  Logs dont show anything wrong and I have tried lots of things to fix it with no solution.

    Ok still cant work this out. manually set monitor settings etc the box still pops up when waking monotor from sleep. logs still show nothing.  Can anyone help?
    Log below
    [ 11.918]
    This is a pre-release version of the X server from The X.Org Foundation.
    It is not supported in any way.
    Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
    Select the "xorg" product for bugs you find in this release.
    Before reporting bugs in pre-release versions please check the
    latest version in the X.Org Foundation git repository.
    See http://wiki.x.org/wiki/GitPage for git access instructions.
    [ 11.918]
    X.Org X Server 1.13.2.901 (1.13.3 RC 1)
    Release Date: 2013-02-15
    [ 11.918] X Protocol Version 11, Revision 0
    [ 11.918] Build Operating System: Linux 3.7.5-1-ARCH x86_64
    [ 11.918] Current Operating System: Linux ThunderBolt.LoadBalancer.Org 3.7.9-2-ARCH #1 SMP PREEMPT Mon Feb 25 12:04:25 CET 2013 x86_64
    [ 11.918] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=bc60faad-b008-4f1f-8682-88d4c6f235cc ro quiet
    [ 11.918] Build Date: 18 February 2013 03:52:56PM
    [ 11.918]
    [ 11.918] Current version of pixman: 0.28.2
    [ 11.918] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 11.918] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 11.918] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Mar 6 17:45:33 2013
    [ 12.161] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 12.326] (==) ServerLayout "ServerLayout0"
    [ 12.326] (==) No screen section available. Using defaults.
    [ 12.326] (**) |-->Screen "Default Screen Section" (0)
    [ 12.326] (**) | |-->Monitor "<default monitor>"
    [ 12.326] (==) No device specified for screen "Default Screen Section".
    Using the first device section listed.
    [ 12.326] (**) | |-->Device "Intel Graphics"
    [ 12.326] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    [ 12.326] (**) Option "BlankTime" "0"
    [ 12.326] (**) Option "StandbyTime" "0"
    [ 12.326] (**) Option "SuspendTime" "0"
    [ 12.326] (**) Option "OffTime" "0"
    [ 12.326] (==) Automatically adding devices
    [ 12.326] (==) Automatically enabling devices
    [ 12.326] (==) Automatically adding GPU devices
    [ 12.513] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [ 12.513] Entry deleted from font path.
    [ 12.561] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 12.561] Entry deleted from font path.
    [ 12.561] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 12.561] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 12.561] Entry deleted from font path.
    [ 12.561] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 12.561] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/Type1/
    [ 12.561] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 12.561] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 12.562] (II) Loader magic: 0x7fcc20
    [ 12.562] (II) Module ABI versions:
    [ 12.562] X.Org ANSI C Emulation: 0.4
    [ 12.562] X.Org Video Driver: 13.1
    [ 12.562] X.Org XInput driver : 18.0
    [ 12.562] X.Org Server Extension : 7.0
    [ 12.562] (II) config/udev: Adding drm device (/dev/dri/card0)
    [ 12.563] (--) PCI:*(0:0:2:0) 8086:2e22:1025:0251 rev 3, Mem @ 0xfe400000/4194304, 0xd0000000/268435456, I/O @ 0x0000dc00/8
    [ 12.563] (--) PCI: (0:0:2:1) 8086:2e23:1025:0251 rev 3, Mem @ 0xfe900000/1048576
    [ 12.762] Initializing built-in extension Generic Event Extension
    [ 12.763] Initializing built-in extension SHAPE
    [ 12.763] Initializing built-in extension MIT-SHM
    [ 12.763] Initializing built-in extension XInputExtension
    [ 12.763] Initializing built-in extension XTEST
    [ 12.763] Initializing built-in extension BIG-REQUESTS
    [ 12.763] Initializing built-in extension SYNC
    [ 12.763] Initializing built-in extension XKEYBOARD
    [ 12.763] Initializing built-in extension XC-MISC
    [ 12.763] Initializing built-in extension SECURITY
    [ 12.763] Initializing built-in extension XINERAMA
    [ 12.763] Initializing built-in extension XFIXES
    [ 12.763] Initializing built-in extension RENDER
    [ 12.763] Initializing built-in extension RANDR
    [ 12.763] Initializing built-in extension COMPOSITE
    [ 12.763] Initializing built-in extension DAMAGE
    [ 12.763] Initializing built-in extension MIT-SCREEN-SAVER
    [ 12.763] Initializing built-in extension DOUBLE-BUFFER
    [ 12.763] Initializing built-in extension RECORD
    [ 12.763] Initializing built-in extension DPMS
    [ 12.763] Initializing built-in extension X-Resource
    [ 12.763] Initializing built-in extension XVideo
    [ 12.763] Initializing built-in extension XVideo-MotionCompensation
    [ 12.763] Initializing built-in extension XFree86-VidModeExtension
    [ 12.763] Initializing built-in extension XFree86-DGA
    [ 12.763] Initializing built-in extension XFree86-DRI
    [ 12.763] Initializing built-in extension DRI2
    [ 12.763] (II) LoadModule: "glx"
    [ 12.816] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 12.828] (II) Module glx: vendor="X.Org Foundation"
    [ 12.829] compiled for 1.13.2.901, module version = 1.0.0
    [ 12.829] ABI class: X.Org Server Extension, version 7.0
    [ 12.829] (==) AIGLX enabled
    [ 12.829] Loading extension GLX
    [ 12.829] (II) LoadModule: "intel"
    [ 12.853] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
    [ 13.078] (II) Module intel: vendor="X.Org Foundation"
    [ 13.078] compiled for 1.13.2.901, module version = 2.21.3
    [ 13.079] Module class: X.Org Video Driver
    [ 13.079] ABI class: X.Org Video Driver, version 13.1
    [ 13.079] (II) intel: Driver for Intel 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, B43, Clarkdale, Arrandale,
    Sandybridge Desktop (GT1), Sandybridge Desktop (GT2),
    Sandybridge Desktop (GT2+), Sandybridge Mobile (GT1),
    Sandybridge Mobile (GT2), Sandybridge Mobile (GT2+),
    Sandybridge Server, Ivybridge Mobile (GT1), Ivybridge Mobile (GT2),
    Ivybridge Desktop (GT1), Ivybridge Desktop (GT2), Ivybridge Server,
    Ivybridge Server (GT2), Haswell Desktop (GT1), Haswell Desktop (GT2),
    Haswell Desktop (GT2+), Haswell Mobile (GT1), Haswell Mobile (GT2),
    Haswell Mobile (GT2+), Haswell Server (GT1), Haswell Server (GT2),
    Haswell Server (GT2+), Haswell SDV Desktop (GT1),
    Haswell SDV Desktop (GT2), Haswell SDV Desktop (GT2+),
    Haswell SDV Mobile (GT1), Haswell SDV Mobile (GT2),
    Haswell SDV Mobile (GT2+), Haswell SDV Server (GT1),
    Haswell SDV Server (GT2), Haswell SDV Server (GT2+),
    Haswell ULT Desktop (GT1), Haswell ULT Desktop (GT2),
    Haswell ULT Desktop (GT2+), Haswell ULT Mobile (GT1),
    Haswell ULT Mobile (GT2), Haswell ULT Mobile (GT2+),
    Haswell ULT Server (GT1), Haswell ULT Server (GT2),
    Haswell ULT Server (GT2+), Haswell CRW Desktop (GT1),
    Haswell CRW Desktop (GT2), Haswell CRW Desktop (GT2+),
    Haswell CRW Mobile (GT1), Haswell CRW Mobile (GT2),
    Haswell CRW Mobile (GT2+), Haswell CRW Server (GT1),
    Haswell CRW Server (GT2), Haswell CRW Server (GT2+),
    ValleyView PO board
    [ 13.079] (++) using VT number 7
    [ 13.213] (II) intel(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
    [ 13.213] (==) intel(0): Depth 24, (--) framebuffer bpp 32
    [ 13.213] (==) intel(0): RGB weight 888
    [ 13.213] (==) intel(0): Default visual is TrueColor
    [ 13.213] (**) intel(0): Option "AccelMethod" "sna"
    [ 13.213] (--) intel(0): Integrated Graphics Chipset: Intel(R) G45/G43
    [ 13.213] (**) intel(0): Framebuffer tiled
    [ 13.213] (**) intel(0): Pixmaps tiled
    [ 13.213] (**) intel(0): "Tear free" disabled
    [ 13.213] (**) intel(0): Forcing per-crtc-pixmaps? no
    [ 13.253] (II) intel(0): Output VGA1 has no monitor section
    [ 13.362] (II) intel(0): Output HDMI1 using monitor section HDMI1
    [ 13.403] (II) intel(0): Output DP1 has no monitor section
    [ 13.443] (II) intel(0): EDID for output VGA1
    [ 13.552] (II) intel(0): EDID for output HDMI1
    [ 13.552] (II) intel(0): Manufacturer: GSM Model: 56cc Serial#: 258443
    [ 13.552] (II) intel(0): Year: 2011 Week: 4
    [ 13.552] (II) intel(0): EDID Version: 1.3
    [ 13.552] (II) intel(0): Digital Display Input
    [ 13.552] (II) intel(0): Max Image Size [cm]: horiz.: 53 vert.: 30
    [ 13.552] (II) intel(0): Gamma: 2.20
    [ 13.552] (II) intel(0): No DPMS capabilities specified
    [ 13.552] (II) intel(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
    [ 13.552] (II) intel(0): First detailed timing is preferred mode
    [ 13.552] (II) intel(0): redX: 0.635 redY: 0.342 greenX: 0.292 greenY: 0.611
    [ 13.552] (II) intel(0): blueX: 0.147 blueY: 0.070 whiteX: 0.313 whiteY: 0.329
    [ 13.552] (II) intel(0): Supported established timings:
    [ 13.552] (II) intel(0): 640x480@60Hz
    [ 13.552] (II) intel(0): 800x600@60Hz
    [ 13.552] (II) intel(0): 1024x768@60Hz
    [ 13.552] (II) intel(0): Manufacturer's mask: 0
    [ 13.552] (II) intel(0): Supported standard timings:
    [ 13.552] (II) intel(0): #0: hsize: 1680 vsize 1050 refresh: 60 vid: 179
    [ 13.552] (II) intel(0): #1: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
    [ 13.552] (II) intel(0): #2: hsize: 1280 vsize 960 refresh: 60 vid: 16513
    [ 13.552] (II) intel(0): Supported detailed timing:
    [ 13.552] (II) intel(0): clock: 138.5 MHz Image Size: 531 x 299 mm
    [ 13.552] (II) intel(0): h_active: 1920 h_sync: 1968 h_sync_end 2000 h_blank_end 2080 h_border: 0
    [ 13.552] (II) intel(0): v_active: 1080 v_sync: 1083 v_sync_end 1088 v_blanking: 1111 v_border: 0
    [ 13.552] (II) intel(0): Supported detailed timing:
    [ 13.552] (II) intel(0): clock: 148.5 MHz Image Size: 531 x 299 mm
    [ 13.552] (II) intel(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
    [ 13.552] (II) intel(0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0
    [ 13.552] (II) intel(0): Ranges: V min: 56 V max: 61 Hz, H min: 30 H max: 83 kHz, PixClock max 155 MHz
    [ 13.552] (II) intel(0): Monitor name: W2442
    [ 13.552] (II) intel(0): Supported detailed timing:
    [ 13.552] (II) intel(0): clock: 148.5 MHz Image Size: 531 x 299 mm
    [ 13.552] (II) intel(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
    [ 13.552] (II) intel(0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0
    [ 13.552] (II) intel(0): Supported detailed timing:
    [ 13.552] (II) intel(0): clock: 74.2 MHz Image Size: 531 x 299 mm
    [ 13.552] (II) intel(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
    [ 13.552] (II) intel(0): v_active: 540 v_sync: 542 v_sync_end 547 v_blanking: 562 v_border: 0
    [ 13.552] (II) intel(0): Supported detailed timing:
    [ 13.552] (II) intel(0): clock: 74.2 MHz Image Size: 531 x 299 mm
    [ 13.552] (II) intel(0): h_active: 1280 h_sync: 1390 h_sync_end 1430 h_blank_end 1650 h_border: 0
    [ 13.552] (II) intel(0): v_active: 720 v_sync: 725 v_sync_end 730 v_blanking: 750 v_border: 0
    [ 13.552] (II) intel(0): Supported detailed timing:
    [ 13.552] (II) intel(0): clock: 27.0 MHz Image Size: 531 x 299 mm
    [ 13.552] (II) intel(0): h_active: 720 h_sync: 736 h_sync_end 798 h_blank_end 858 h_border: 0
    [ 13.552] (II) intel(0): v_active: 480 v_sync: 489 v_sync_end 495 v_blanking: 525 v_border: 0
    [ 13.552] (II) intel(0): Number of EDID sections to follow: 1
    [ 13.552] (II) intel(0): EDID (in hex):
    [ 13.552] (II) intel(0): 00ffffffffffff001e6dcc568bf10300
    [ 13.552] (II) intel(0): 0415010380351e780aaec5a2574a9c25
    [ 13.552] (II) intel(0): 125054210800b3008180814001010101
    [ 13.552] (II) intel(0): 0101010101011a3680a070381f403020
    [ 13.552] (II) intel(0): 3500132b2100001a023a801871382d40
    [ 13.552] (II) intel(0): 582c4500132b2100001e000000fd0038
    [ 13.552] (II) intel(0): 3d1e530f000a202020202020000000fc
    [ 13.552] (II) intel(0): 0057323434320a202020202020200128
    [ 13.552] (II) intel(0): 020321f14e900403011412051f101300
    [ 13.552] (II) intel(0): 000000230907078301000065030c0010
    [ 13.552] (II) intel(0): 00023a801871382d40582c4500132b21
    [ 13.552] (II) intel(0): 00001e011d8018711c1620582c250013
    [ 13.552] (II) intel(0): 2b2100009e011d007251d01e206e2855
    [ 13.552] (II) intel(0): 00132b2100001e8c0ad08a20e02d1010
    [ 13.552] (II) intel(0): 3e9600132b2100001800000000000000
    [ 13.552] (II) intel(0): 00000000000000000000000000000026
    [ 13.552] (II) intel(0): Printing probed modes for output HDMI1
    [ 13.552] (II) intel(0): Modeline "1920x1080"x59.9 138.50 1920 1968 2000 2080 1080 1083 1088 1111 +hsync -vsync (66.6 kHz eP)
    [ 13.552] (II) intel(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz e)
    [ 13.552] (II) intel(0): Modeline "1920x1080"x50.0 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (56.2 kHz e)
    [ 13.552] (II) intel(0): Modeline "1920x1080i"x60.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e)
    [ 13.552] (II) intel(0): Modeline "1920x1080i"x50.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e)
    [ 13.552] (II) intel(0): Modeline "1680x1050"x59.9 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
    [ 13.552] (II) intel(0): Modeline "1680x945"x60.0 131.48 1680 1784 1960 2240 945 946 949 978 -hsync +vsync (58.7 kHz)
    [ 13.552] (II) intel(0): Modeline "1400x1050"x59.9 101.00 1400 1448 1480 1560 1050 1053 1057 1080 +hsync -vsync (64.7 kHz e)
    [ 13.552] (II) intel(0): Modeline "1600x900"x60.0 118.96 1600 1696 1864 2128 900 901 904 932 -hsync +vsync (55.9 kHz)
    [ 13.552] (II) intel(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [ 13.552] (II) intel(0): Modeline "1440x900"x59.9 88.75 1440 1488 1520 1600 900 903 909 926 +hsync -vsync (55.5 kHz e)
    [ 13.552] (II) intel(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 13.552] (II) intel(0): Modeline "1366x768"x60.0 85.89 1366 1439 1583 1800 768 769 772 795 -hsync +vsync (47.7 kHz)
    [ 13.552] (II) intel(0): Modeline "1360x768"x60.0 85.50 1360 1424 1536 1792 768 771 777 795 +hsync +vsync (47.7 kHz e)
    [ 13.552] (II) intel(0): Modeline "1280x800"x59.9 71.00 1280 1328 1360 1440 800 803 809 823 +hsync -vsync (49.3 kHz e)
    [ 13.552] (II) intel(0): Modeline "1280x768"x60.0 68.25 1280 1328 1360 1440 768 771 778 790 +hsync -vsync (47.4 kHz e)
    [ 13.552] (II) intel(0): Modeline "1280x720"x50.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e)
    [ 13.552] (II) intel(0): Modeline "1280x720"x60.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
    [ 13.552] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 13.552] (II) intel(0): Modeline "1024x576"x60.0 46.97 1024 1064 1168 1312 576 577 580 597 -hsync +vsync (35.8 kHz)
    [ 13.552] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 13.552] (II) intel(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 13.552] (II) intel(0): Modeline "720x576"x50.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e)
    [ 13.552] (II) intel(0): Modeline "848x480"x60.0 33.75 848 864 976 1088 480 486 494 517 +hsync +vsync (31.0 kHz e)
    [ 13.552] (II) intel(0): Modeline "720x480"x59.9 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
    [ 13.552] (II) intel(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 13.552] (II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 13.593] (II) intel(0): EDID for output DP1
    [ 13.593] (II) intel(0): Output VGA1 disconnected
    [ 13.593] (II) intel(0): Output HDMI1 connected
    [ 13.593] (II) intel(0): Output DP1 disconnected
    [ 13.593] (II) intel(0): Using exact sizes for initial modes
    [ 13.593] (II) intel(0): Output HDMI1 using initial mode 1920x1080
    [ 13.593] (II) intel(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
    [ 13.593] (==) intel(0): DPI set to (96, 96)
    [ 13.593] (II) Loading sub module "dri2"
    [ 13.593] (II) LoadModule: "dri2"
    [ 13.593] (II) Module "dri2" already built-in
    [ 13.593] (==) Depth 24 pixmap format is 32 bpp
    [ 13.793] (II) intel(0): SNA initialized with Broadwater/Crestline backend
    [ 13.793] (==) intel(0): Backing store disabled
    [ 13.793] (==) intel(0): Silken mouse enabled
    [ 13.793] (II) intel(0): HW Cursor enabled
    [ 13.793] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    [ 13.794] (==) intel(0): DPMS enabled
    [ 13.794] (II) intel(0): Overlay video not supported on this hardware
    [ 13.794] (II) intel(0): [XvMC] xvmc_vld driver initialized.
    [ 13.794] (II) intel(0): [DRI2] Setup complete
    [ 13.794] (II) intel(0): [DRI2] DRI driver: i965
    [ 13.794] (II) intel(0): direct rendering: DRI2 Enabled
    [ 13.794] (==) intel(0): hotplug detection: "enabled"
    [ 13.794] (--) RandR disabled
    [ 14.124] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
    [ 14.124] (II) AIGLX: enabled GLX_INTEL_swap_event
    [ 14.124] (II) AIGLX: enabled GLX_ARB_create_context
    [ 14.124] (II) AIGLX: enabled GLX_ARB_create_context_profile
    [ 14.124] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
    [ 14.124] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
    [ 14.124] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
    [ 14.124] (II) AIGLX: Loaded and initialized i965
    [ 14.124] (II) GLX: Initialized DRI2 GL provider for screen 0
    [ 14.125] (II) intel(0): switch to mode 1920x1080 on crtc 3 (pipe 0)
    [ 14.210] (II) intel(0): Setting screen physical size to 508 x 285
    [ 14.922] (II) config/udev: Adding input device Power Button (/dev/input/event2)
    [ 14.922] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 14.922] (II) LoadModule: "evdev"
    [ 14.922] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 14.957] (II) Module evdev: vendor="X.Org Foundation"
    [ 14.957] compiled for 1.13.0, module version = 2.7.3
    [ 14.957] Module class: X.Org XInput Driver
    [ 14.957] ABI class: X.Org XInput driver, version 18.0
    [ 14.957] (II) Using input driver 'evdev' for 'Power Button'
    [ 14.957] (**) Power Button: always reports core events
    [ 14.957] (**) evdev: Power Button: Device: "/dev/input/event2"
    [ 14.957] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 14.957] (--) evdev: Power Button: Found keys
    [ 14.957] (II) evdev: Power Button: Configuring as keyboard
    [ 14.957] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event2"
    [ 14.957] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    [ 14.957] (**) Option "xkb_rules" "evdev"
    [ 14.957] (**) Option "xkb_model" "evdev"
    [ 14.957] (**) Option "xkb_layout" "us"
    [ 14.988] (II) config/udev: Adding input device Power Button (/dev/input/event1)
    [ 14.988] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 14.988] (II) Using input driver 'evdev' for 'Power Button'
    [ 14.988] (**) Power Button: always reports core events
    [ 14.988] (**) evdev: Power Button: Device: "/dev/input/event1"
    [ 14.988] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 14.988] (--) evdev: Power Button: Found keys
    [ 14.989] (II) evdev: Power Button: Configuring as keyboard
    [ 14.989] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1/event1"
    [ 14.989] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
    [ 14.989] (**) Option "xkb_rules" "evdev"
    [ 14.989] (**) Option "xkb_model" "evdev"
    [ 14.989] (**) Option "xkb_layout" "us"
    [ 14.989] (II) config/udev: Adding drm device (/dev/dri/card0)
    [ 14.989] (II) config/udev: Adding input device UVC Camera (046d:0825) (/dev/input/event14)
    [ 14.989] (**) UVC Camera (046d:0825): Applying InputClass "evdev keyboard catchall"
    [ 14.989] (II) Using input driver 'evdev' for 'UVC Camera (046d:0825)'
    [ 14.989] (**) UVC Camera (046d:0825): always reports core events
    [ 14.989] (**) evdev: UVC Camera (046d:0825): Device: "/dev/input/event14"
    [ 14.989] (--) evdev: UVC Camera (046d:0825): Vendor 0x46d Product 0x825
    [ 14.989] (--) evdev: UVC Camera (046d:0825): Found keys
    [ 14.989] (II) evdev: UVC Camera (046d:0825): Configuring as keyboard
    [ 14.989] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.7/usb1/1-6/1-6:1.0/input/input14/event14"
    [ 14.989] (II) XINPUT: Adding extended input device "UVC Camera (046d:0825)" (type: KEYBOARD, id 8)
    [ 14.989] (**) Option "xkb_rules" "evdev"
    [ 14.989] (**) Option "xkb_model" "evdev"
    [ 14.989] (**) Option "xkb_layout" "us"
    [ 14.990] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event4)
    [ 14.990] (II) No input driver specified, ignoring this device.
    [ 14.990] (II) This device may have been added with another device file.
    [ 14.990] (II) config/udev: Adding input device HDA Intel Front Headphone (/dev/input/event10)
    [ 14.990] (II) No input driver specified, ignoring this device.
    [ 14.990] (II) This device may have been added with another device file.
    [ 14.991] (II) config/udev: Adding input device HDA Intel Line Out CLFE (/dev/input/event11)
    [ 14.991] (II) No input driver specified, ignoring this device.
    [ 14.991] (II) This device may have been added with another device file.
    [ 14.991] (II) config/udev: Adding input device HDA Intel Line Out Surround (/dev/input/event12)
    [ 14.991] (II) No input driver specified, ignoring this device.
    [ 14.991] (II) This device may have been added with another device file.
    [ 14.991] (II) config/udev: Adding input device HDA Intel Line Out Front (/dev/input/event13)
    [ 14.991] (II) No input driver specified, ignoring this device.
    [ 14.991] (II) This device may have been added with another device file.
    [ 14.991] (II) config/udev: Adding input device HDA Intel HDMI/DP,pcm=3 (/dev/input/event6)
    [ 14.991] (II) No input driver specified, ignoring this device.
    [ 14.991] (II) This device may have been added with another device file.
    [ 14.992] (II) config/udev: Adding input device HDA Intel Line (/dev/input/event7)
    [ 14.992] (II) No input driver specified, ignoring this device.
    [ 14.992] (II) This device may have been added with another device file.
    [ 14.992] (II) config/udev: Adding input device HDA Intel Front Mic (/dev/input/event8)
    [ 14.992] (II) No input driver specified, ignoring this device.
    [ 14.992] (II) This device may have been added with another device file.
    [ 14.992] (II) config/udev: Adding input device HDA Intel Rear Mic (/dev/input/event9)
    [ 14.992] (II) No input driver specified, ignoring this device.
    [ 14.992] (II) This device may have been added with another device file.
    [ 14.993] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
    [ 14.993] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
    [ 14.993] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
    [ 14.993] (**) AT Translated Set 2 keyboard: always reports core events
    [ 14.993] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
    [ 14.993] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
    [ 14.993] (--) evdev: AT Translated Set 2 keyboard: Found keys
    [ 14.993] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
    [ 14.993] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
    [ 14.993] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 9)
    [ 14.993] (**) Option "xkb_rules" "evdev"
    [ 14.993] (**) Option "xkb_model" "evdev"
    [ 14.993] (**) Option "xkb_layout" "us"
    [ 14.993] (II) config/udev: Adding input device ImPS/2 Generic Wheel Mouse (/dev/input/event5)
    [ 14.993] (**) ImPS/2 Generic Wheel Mouse: Applying InputClass "evdev pointer catchall"
    [ 14.993] (II) Using input driver 'evdev' for 'ImPS/2 Generic Wheel Mouse'
    [ 14.993] (**) ImPS/2 Generic Wheel Mouse: always reports core events
    [ 14.993] (**) evdev: ImPS/2 Generic Wheel Mouse: Device: "/dev/input/event5"
    [ 14.993] (--) evdev: ImPS/2 Generic Wheel Mouse: Vendor 0x2 Product 0x5
    [ 14.993] (--) evdev: ImPS/2 Generic Wheel Mouse: Found 3 mouse buttons
    [ 14.993] (--) evdev: ImPS/2 Generic Wheel Mouse: Found scroll wheel(s)
    [ 14.993] (--) evdev: ImPS/2 Generic Wheel Mouse: Found relative axes
    [ 14.993] (--) evdev: ImPS/2 Generic Wheel Mouse: Found x and y relative axes
    [ 14.993] (II) evdev: ImPS/2 Generic Wheel Mouse: Configuring as mouse
    [ 14.993] (II) evdev: ImPS/2 Generic Wheel Mouse: Adding scrollwheel support
    [ 14.994] (**) evdev: ImPS/2 Generic Wheel Mouse: YAxisMapping: buttons 4 and 5
    [ 14.994] (**) evdev: ImPS/2 Generic Wheel Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 14.994] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input5/event5"
    [ 14.994] (II) XINPUT: Adding extended input device "ImPS/2 Generic Wheel Mouse" (type: MOUSE, id 10)
    [ 14.994] (II) evdev: ImPS/2 Generic Wheel Mouse: initialized for relative axes.
    [ 14.994] (**) ImPS/2 Generic Wheel Mouse: (accel) keeping acceleration scheme 1
    [ 14.994] (**) ImPS/2 Generic Wheel Mouse: (accel) acceleration profile 0
    [ 14.994] (**) ImPS/2 Generic Wheel Mouse: (accel) acceleration factor: 2.000
    [ 14.994] (**) ImPS/2 Generic Wheel Mouse: (accel) acceleration threshold: 4
    [ 14.994] (II) config/udev: Adding input device ImPS/2 Generic Wheel Mouse (/dev/input/mouse0)
    [ 14.994] (II) No input driver specified, ignoring this device.
    [ 14.994] (II) This device may have been added with another device file.
    [ 14.994] (II) config/udev: Adding input device PC Speaker (/dev/input/event3)
    [ 14.994] (II) No input driver specified, ignoring this device.
    [ 14.994] (II) This device may have been added with another device file.
    [ 23.841] (II) intel(0): EDID vendor "GSM", prod id 22220
    [ 23.841] (II) intel(0): Using EDID range info for horizontal sync
    [ 23.841] (II) intel(0): Using EDID range info for vertical refresh
    [ 23.841] (II) intel(0): Printing DDC gathered Modelines:
    [ 23.841] (II) intel(0): Modeline "1920x1080"x0.0 138.50 1920 1968 2000 2080 1080 1083 1088 1111 +hsync -vsync (66.6 kHz eP)
    [ 23.841] (II) intel(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz e)
    [ 23.842] (II) intel(0): Modeline "1920x1080i"x0.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e)
    [ 23.842] (II) intel(0): Modeline "1280x720"x0.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
    [ 23.842] (II) intel(0): Modeline "720x480"x0.0 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
    [ 23.842] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 23.842] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 23.842] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 23.842] (II) intel(0): Modeline "1680x1050"x0.0 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
    [ 23.842] (II) intel(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [ 23.842] (II) intel(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 23.842] (II) intel(0): Modeline "720x576"x0.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e)
    [ 23.842] (II) intel(0): Modeline "1440x576i"x0.0 27.00 1440 1464 1590 1728 576 580 586 625 interlace -hsync -vsync (15.6 kHz e)
    [ 23.842] (II) intel(0): Modeline "1280x720"x0.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e)
    [ 23.842] (II) intel(0): Modeline "1440x480i"x0.0 27.00 1440 1478 1602 1716 480 488 494 525 interlace -hsync -vsync (15.7 kHz e)
    [ 23.842] (II) intel(0): Modeline "1920x1080"x0.0 74.25 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync (27.0 kHz e)
    [ 23.842] (II) intel(0): Modeline "1920x1080i"x0.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e)
    [ 23.884] (II) intel(0): switch to mode 1920x1080 on crtc 3 (pipe 0)
    [ 24.108] (II) intel(0): EDID vendor "GSM", prod id 22220
    [ 24.108] (II) intel(0): Using hsync ranges from config file
    [ 24.108] (II) intel(0): Using vrefresh ranges from config file
    [ 24.108] (II) intel(0): Printing DDC gathered Modelines:
    [ 24.108] (II) intel(0): Modeline "1920x1080"x0.0 138.50 1920 1968 2000 2080 1080 1083 1088 1111 +hsync -vsync (66.6 kHz eP)
    [ 24.108] (II) intel(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz e)
    [ 24.108] (II) intel(0): Modeline "1920x1080i"x0.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e)
    [ 24.108] (II) intel(0): Modeline "1280x720"x0.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
    [ 24.108] (II) intel(0): Modeline "720x480"x0.0 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
    [ 24.108] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 24.108] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 24.108] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 24.108] (II) intel(0): Modeline "1680x1050"x0.0 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
    [ 24.108] (II) intel(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [ 24.108] (II) intel(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 24.108] (II) intel(0): Modeline "720x576"x0.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e)
    [ 24.108] (II) intel(0): Modeline "1440x576i"x0.0 27.00 1440 1464 1590 1728 576 580 586 625 interlace -hsync -vsync (15.6 kHz e)
    [ 24.108] (II) intel(0): Modeline "1280x720"x0.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e)
    [ 24.108] (II) intel(0): Modeline "1440x480i"x0.0 27.00 1440 1478 1602 1716 480 488 494 525 interlace -hsync -vsync (15.7 kHz e)
    [ 24.108] (II) intel(0): Modeline "1920x1080"x0.0 74.25 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync (27.0 kHz e)
    [ 24.108] (II) intel(0): Modeline "1920x1080i"x0.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e)
    [ 33.191] (II) intel(0): EDID vendor "GSM", prod id 22220
    [ 33.191] (II) intel(0): Using hsync ranges from config file
    [ 33.191] (II) intel(0): Using vrefresh ranges from config file
    [ 33.191] (II) intel(0): Printing DDC gathered Modelines:
    [ 33.191] (II) intel(0): Modeline "1920x1080"x0.0 138.50 1920 1968 2000 2080 1080 1083 1088 1111 +hsync -vsync (66.6 kHz eP)
    [ 33.191] (II) intel(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz e)
    [ 33.191] (II) intel(0): Modeline "1920x1080i"x0.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e)
    [ 33.191] (II) intel(0): Modeline "1280x720"x0.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
    [ 33.191] (II) intel(0): Modeline "720x480"x0.0 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
    [ 33.191] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 33.191] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 33.191] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 33.191] (II) intel(0): Modeline "1680x1050"x0.0 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
    [ 33.191] (II) intel(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [ 33.192] (II) intel(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 33.192] (II) intel(0): Modeline "720x576"x0.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e)
    [ 33.192] (II) intel(0): Modeline "1440x576i"x0.0 27.00 1440 1464 1590 1728 576 580 586 625 interlace -hsync -vsync (15.6 kHz e)
    [ 33.192] (II) intel(0): Modeline "1280x720"x0.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e)
    [ 33.192] (II) intel(0): Modeline "1440x480i"x0.0 27.00 1440 1478 1602 1716 480 488 494 525 interlace -hsync -vsync (15.7 kHz e)
    [ 33.192] (II) intel(0): Modeline "1920x1080"x0.0 74.25 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync (27.0 kHz e)
    [ 33.192] (II) intel(0): Modeline "1920x1080i"x0.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e)
    [ 40.998] (II) intel(0): EDID vendor "GSM", prod id 22220
    [ 40.998] (II) intel(0): Using hsync ranges from config file
    [ 40.998] (II) intel(0): Using vrefresh ranges from config file
    [ 40.998] (II) intel(0): Printing DDC gathered Modelines:
    [ 40.998] (II) intel(0): Modeline "1920x1080"x0.0 138.50 1920 1968 2000 2080 1080 1083 1088 1111 +hsync -vsync (66.6 kHz eP)
    [ 40.998] (II) intel(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz e)
    [ 40.998] (II) intel(0): Modeline "1920x1080i"x0.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e)
    [ 40.998] (II) intel(0): Modeline "1280x720"x0.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
    [ 40.998] (II) intel(0): Modeline "720x480"x0.0 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
    [ 40.998] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 40.998] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 40.998] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 40.998] (II) intel(0): Modeline "1680x1050"x0.0 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
    [ 40.998] (II) intel(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [ 40.998] (II) intel(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 40.998] (II) intel(0): Modeline "720x576"x0.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e)
    [ 40.998] (II) intel(0): Modeline "1440x576i"x0.0 27.00 1440 1464 1590 1728 576 580 586 625 interlace -hsync -vsync (15.6 kHz e)
    [ 40.998] (II) intel(0): Modeline "1280x720"x0.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e)
    [ 40.998] (II) intel(0): Modeline "1440x480i"x0.0 27.00 1440 1478 1602 1716 480 488 494 525 interlace -hsync -vsync (15.7 kHz e)
    [ 40.998] (II) intel(0): Modeline "1920x1080"x0.0 74.25 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync (27.0 kHz e)
    [ 40.998] (II) intel(0): Modeline "1920x1080i"x0.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e)
    [ 936.094] (II) evdev: ImPS/2 Generic Wheel Mouse: Close
    [ 936.094] (II) UnloadModule: "evdev"
    [ 936.094] (II) evdev: AT Translated Set 2 keyboard: Close
    [ 936.094] (II) UnloadModule: "evdev"
    [ 936.094] (II) evdev: UVC Camera (046d:0825): Close
    [ 936.094] (II) UnloadModule: "evdev"
    [ 936.094] (II) evdev: Power Button: Close
    [ 936.094] (II) UnloadModule: "evdev"
    [ 936.094] (II) evdev: Power Button: Close
    [ 936.094] (II) UnloadModule: "evdev"
    [ 936.194] Server terminated successfully (0). Closing log file.
    kde log
    Note that your system uses syslog. All of kdm's internally generated messages
    (i.e., not from libraries and external programs/scripts it uses) go to the
    daemon.* syslog facility; check your syslog configuration to find out to which
    file(s) it is logged. PAM logs messages related to authentication to authpriv.*.
    Initializing built-in extension Generic Event Extension
    Initializing built-in extension SHAPE
    Initializing built-in extension MIT-SHM
    Initializing built-in extension XInputExtension
    Initializing built-in extension XTEST
    Initializing built-in extension BIG-REQUESTS
    Initializing built-in extension SYNC
    Initializing built-in extension XKEYBOARD
    Initializing built-in extension XC-MISC
    Initializing built-in extension SECURITY
    Initializing built-in extension XINERAMA
    Initializing built-in extension XFIXES
    Initializing built-in extension RENDER
    Initializing built-in extension RANDR
    Initializing built-in extension COMPOSITE
    Initializing built-in extension DAMAGE
    Initializing built-in extension MIT-SCREEN-SAVER
    Initializing built-in extension DOUBLE-BUFFER
    Initializing built-in extension RECORD
    Initializing built-in extension DPMS
    Initializing built-in extension X-Resource
    Initializing built-in extension XVideo
    Initializing built-in extension XVideo-MotionCompensation
    Initializing built-in extension XFree86-VidModeExtension
    Initializing built-in extension XFree86-DGA
    Initializing built-in extension XFree86-DRI
    Initializing built-in extension DRI2
    Loading extension GLX
    klauncher(7126) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(7120)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(7120)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    klauncher(7543) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(7537)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(7537)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    kdmgreet: Fatal IO error: client killed
    Server terminated successfully (0). Closing log file.
    Initializing built-in extension Generic Event Extension
    Initializing built-in extension SHAPE
    Initializing built-in extension MIT-SHM
    Initializing built-in extension XInputExtension
    Initializing built-in extension XTEST
    Initializing built-in extension BIG-REQUESTS
    Initializing built-in extension SYNC
    Initializing built-in extension XKEYBOARD
    Initializing built-in extension XC-MISC
    Initializing built-in extension SECURITY
    Initializing built-in extension XINERAMA
    Initializing built-in extension XFIXES
    Initializing built-in extension RENDER
    Initializing built-in extension RANDR
    Initializing built-in extension COMPOSITE
    Initializing built-in extension DAMAGE
    Initializing built-in extension MIT-SCREEN-SAVER
    Initializing built-in extension DOUBLE-BUFFER
    Initializing built-in extension RECORD
    Initializing built-in extension DPMS
    Initializing built-in extension X-Resource
    Initializing built-in extension XVideo
    Initializing built-in extension XVideo-MotionCompensation
    Initializing built-in extension XFree86-VidModeExtension
    Initializing built-in extension XFree86-DGA
    Initializing built-in extension XFree86-DRI
    Initializing built-in extension DRI2
    Loading extension GLX
    klauncher(326) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(285)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(285)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    Server terminated successfully (0). Closing log file.
    Initializing built-in extension Generic Event Extension
    Initializing built-in extension SHAPE
    Initializing built-in extension MIT-SHM
    Initializing built-in extension XInputExtension
    Initializing built-in extension XTEST
    Initializing built-in extension BIG-REQUESTS
    Initializing built-in extension SYNC
    Initializing built-in extension XKEYBOARD
    Initializing built-in extension XC-MISC
    Initializing built-in extension SECURITY
    Initializing built-in extension XINERAMA
    Initializing built-in extension XFIXES
    Initializing built-in extension RENDER
    Initializing built-in extension RANDR
    Initializing built-in extension COMPOSITE
    Initializing built-in extension DAMAGE
    Initializing built-in extension MIT-SCREEN-SAVER
    Initializing built-in extension DOUBLE-BUFFER
    Initializing built-in extension RECORD
    Initializing built-in extension DPMS
    Initializing built-in extension X-Resource
    Initializing built-in extension XVideo
    Initializing built-in extension XVideo-MotionCompensation
    Initializing built-in extension XFree86-VidModeExtension
    Initializing built-in extension XFree86-DGA
    Initializing built-in extension XFree86-DRI
    Initializing built-in extension DRI2
    Loading extension GLX
    klauncher(341) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(294)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(294)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    Server terminated successfully (0). Closing log file.
    Initializing built-in extension Generic Event Extension
    Initializing built-in extension SHAPE
    Initializing built-in extension MIT-SHM
    Initializing built-in extension XInputExtension
    Initializing built-in extension XTEST
    Initializing built-in extension BIG-REQUESTS
    Initializing built-in extension SYNC
    Initializing built-in extension XKEYBOARD
    Initializing built-in extension XC-MISC
    Initializing built-in extension SECURITY
    Initializing built-in extension XINERAMA
    Initializing built-in extension XFIXES
    Initializing built-in extension RENDER
    Initializing built-in extension RANDR
    Initializing built-in extension COMPOSITE
    Initializing built-in extension DAMAGE
    Initializing built-in extension MIT-SCREEN-SAVER
    Initializing built-in extension DOUBLE-BUFFER
    Initializing built-in extension RECORD
    Initializing built-in extension DPMS
    Initializing built-in extension X-Resource
    Initializing built-in extension XVideo
    Initializing built-in extension XVideo-MotionCompensation
    Initializing built-in extension XFree86-VidModeExtension
    Initializing built-in extension XFree86-DGA
    Initializing built-in extension XFree86-DRI
    Initializing built-in extension DRI2
    Loading extension GLX
    klauncher(273) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(264)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(264)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    Server terminated successfully (0). Closing log file.
    Initializing built-in extension Generic Event Extension
    Initializing built-in extension SHAPE
    Initializing built-in extension MIT-SHM
    Initializing built-in extension XInputExtension
    Initializing built-in extension XTEST
    Initializing built-in extension BIG-REQUESTS
    Initializing built-in extension SYNC
    Initializing built-in extension XKEYBOARD
    Initializing built-in extension XC-MISC
    Initializing built-in extension SECURITY
    Initializing built-in extension XINERAMA
    Initializing built-in extension XFIXES
    Initializing built-in extension RENDER
    Initializing built-in extension RANDR
    Initializing built-in extension COMPOSITE
    Initializing built-in extension DAMAGE
    Initializing built-in extension MIT-SCREEN-SAVER
    Initializing built-in extension DOUBLE-BUFFER
    Initializing built-in extension RECORD
    Initializing built-in extension DPMS
    Initializing built-in extension X-Resource
    Initializing built-in extension XVideo
    Initializing built-in extension XVideo-MotionCompensation
    Initializing built-in extension XFree86-VidModeExtension
    Initializing built-in extension XFree86-DGA
    Initializing built-in extension XFree86-DRI
    Initializing built-in extension DRI2
    Loading extension GLX
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Error: Can't find file "uk" for symbols include
    > Exiting
    > Abandoning symbols file "default"
    Errors from xkbcomp are not fatal to the X server
    klauncher(857) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(847)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(847)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Error: Can't find file "uk" for symbols include
    > Exiting
    > Abandoning symbols file "default"
    Errors from xkbcomp are not fatal to the X server
    Server terminated successfully (0). Closing log file.
    Initializing built-in extension Generic Event Extension
    Initializing built-in extension SHAPE
    Initializing built-in extension MIT-SHM
    Initializing built-in extension XInputExtension
    Initializing built-in extension XTEST
    Initializing built-in extension BIG-REQUESTS
    Initializing built-in extension SYNC
    Initializing built-in extension XKEYBOARD
    Initializing built-in extension XC-MISC
    Initializing built-in extension SECURITY
    Initializing built-in extension XINERAMA
    Initializing built-in extension XFIXES
    Initializing built-in extension RENDER
    Initializing built-in extension RANDR
    Initializing built-in extension COMPOSITE
    Initializing built-in extension DAMAGE
    Initializing built-in extension MIT-SCREEN-SAVER
    Initializing built-in extension DOUBLE-BUFFER
    Initializing built-in extension RECORD
    Initializing built-in extension DPMS
    Initializing built-in extension X-Resource
    Initializing built-in extension XVideo
    Initializing built-in extension XVideo-MotionCompensation
    Initializing built-in extension XFree86-VidModeExtension
    Initializing built-in extension XFree86-DGA
    Initializing built-in extension XFree86-DRI
    Initializing built-in extension DRI2
    Loading extension GLX
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Error: Can't find file "uk" for symbols include
    > Exiting
    > Abandoning symbols file "default"
    Errors from xkbcomp are not fatal to the X server
    klauncher(1223) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(1215)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(1215)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Error: Can't find file "uk" for symbols include
    > Exiting
    > Abandoning symbols file "default"
    Errors from xkbcomp are not fatal to the X server
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    Server terminated successfully (0). Closing log file.
    Initializing built-in extension Generic Event Extension
    Initializing built-in extension SHAPE
    Initializing built-in extension MIT-SHM
    Initializing built-in extension XInputExtension
    Initializing built-in extension XTEST
    Initializing built-in extension BIG-REQUESTS
    Initializing built-in extension SYNC
    Initializing built-in extension XKEYBOARD
    Initializing built-in extension XC-MISC
    Initializing built-in extension SECURITY
    Initializing built-in extension XINERAMA
    Initializing built-in extension XFIXES
    Initializing built-in extension RENDER
    Initializing built-in extension RANDR
    Initializing built-in extension COMPOSITE
    Initializing built-in extension DAMAGE
    Initializing built-in extension MIT-SCREEN-SAVER
    Initializing built-in extension DOUBLE-BUFFER
    Initializing built-in extension RECORD
    Initializing built-in extension DPMS
    Initializing built-in extension X-Resource
    Initializing built-in extension XVideo
    Initializing built-in extension XVideo-MotionCompensation
    Initializing built-in extension XFree86-VidModeExtension
    Initializing built-in extension XFree86-DGA
    Initializing built-in extension XFree86-DRI
    Initializing built-in extension DRI2
    Loading extension GLX
    klauncher(269) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(263)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(263)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    Server terminated successfully (0). Closing log file.
    Initializing built-in extension Generic Event Extension
    Initializing built-in extension SHAPE
    Initializing built-in extension MIT-SHM
    Initializing built-in extension XInputExtension
    Initializing built-in extension XTEST
    Initializing built-in extension BIG-REQUESTS
    Initializing built-in extension SYNC
    Initializing built-in extension XKEYBOARD
    Initializing built-in extension XC-MISC
    Initializing built-in extension SECURITY
    Initializing built-in extension XINERAMA
    Initializing built-in extension XFIXES
    Initializing built-in extension RENDER
    Initializing built-in extension RANDR
    Initializing built-in extension COMPOSITE
    Initializing built-in extension DAMAGE
    Initializing built-in extension MIT-SCREEN-SAVER
    Initializing built-in extension DOUBLE-BUFFER
    Initializing built-in extension RECORD
    Initializing built-in extension DPMS
    Initializing built-in extension X-Resource
    Initializing built-in extension XVideo
    Initializing built-in extension XVideo-MotionCompensation
    Initializing built-in extension XFree86-VidModeExtension
    Initializing built-in extension XFree86-DGA
    Initializing built-in extension XFree86-DRI
    Initializing built-in extension DRI2
    Loading extension GLX
    klauncher(706) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(700)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(700)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    Server terminated successfully (0). Closing log file.
    Initializing built-in extension Generic Event Extension
    Initializing built-in extension SHAPE
    Initializing built-in extension MIT-SHM
    Initializing built-in extension XInputExtension
    Initializing built-in extension XTEST
    Initializing built-in extension BIG-REQUESTS
    Initializing built-in extension SYNC
    Initializing built-in extension XKEYBOARD
    Initializing built-in extension XC-MISC
    Initializing built-in extension SECURITY
    Initializing built-in extension XINERAMA
    Initializing built-in extension XFIXES
    Initializing built-in extension RENDER
    Initializing built-in extension RANDR
    Initializing built-in extension COMPOSITE
    Initializing built-in extension DAMAGE
    Initializing built-in extension MIT-SCREEN-SAVER
    Initializing built-in extension DOUBLE-BUFFER
    Initializing built-in extension RECORD
    Initializing built-in extension DPMS
    Initializing built-in extension X-Resource
    Initializing built-in extension XVideo
    Initializing built-in extension XVideo-MotionCompensation
    Initializing built-in extension XFree86-VidModeExtension
    Initializing built-in extension XFree86-DGA
    Initializing built-in extension XFree86-DRI
    Initializing built-in extension DRI2
    Loading extension GLX
    klauncher(2630) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(2624)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(2624)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    Server terminated successfully (0). Closing log file.
    Initializing built-in extension Generic Event Extension
    Initializing built-in extension SHAPE
    Initializing built-in extension MIT-SHM
    Initializing built-in extension XInputExtension
    Initializing built-in extension XTEST
    Initializing built-in extension BIG-REQUESTS
    Initializing built-in extension SYNC
    Initializing built-in extension XKEYBOARD
    Initializing built-in extension XC-MISC
    Initializing built-in extension SECURITY
    Initializing built-in extension XINERAMA
    Initializing built-in extension XFIXES
    Initializing built-in extension RENDER
    Initializing built-in extension RANDR
    Initializing built-in extension COMPOSITE
    Initializing built-in extension DAMAGE
    Initializing built-in extension MIT-SCREEN-SAVER
    Initializing built-in extension DOUBLE-BUFFER
    Initializing built-in extension RECORD
    Initializing built-in extension DPMS
    Initializing built-in extension X-Resource
    Initializing built-in extension XVideo
    Initializing built-in extension XVideo-MotionCompensation
    Initializing built-in extension XFree86-VidModeExtension
    Initializing built-in extension XFree86-DGA
    Initializing built-in extension XFree86-DRI
    Initializing built-in extension DRI2
    Loading extension GLX
    klauncher(3118) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(3112)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(3112)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    Server terminated successfully (0). Closing log file.
    Initializing built-in extension Generic Event Extension
    Initializing built-in extension SHAPE
    Initializing built-in extension MIT-SHM
    Initializing built-in extension XInputExtension
    Initializing built-in extension XTEST
    Initializing built-in extension BIG-REQUESTS
    Initializing built-in extension SYNC
    Initializing built-in extension XKEYBOARD
    Initializing built-in extension XC-MISC
    Initializing built-in extension SECURITY
    Initializing built-in extension XINERAMA
    Initializing built-in extension XFIXES
    Initializing built-in extension RENDER
    Initializing built-in extension RANDR
    Initializing built-in extension COMPOSITE
    Initializing built-in extension DAMAGE
    Initializing built-in extension MIT-SCREEN-SAVER
    Initializing built-in extension DOUBLE-BUFFER
    Initializing built-in extension RECORD
    Initializing built-in extension DPMS
    Initializing built-in extension X-Resource
    Initializing built-in extension XVideo
    Initializing built-in extension XVideo-MotionCompensation
    Initializing built-in extension XFree86-VidModeExtension
    Initializing built-in extension XFree86-DGA
    Initializing built-in extension XFree86-DRI
    Initializing built-in extension DRI2
    Loading extension GLX
    klauncher(4638) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(4632)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(4632)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    Server terminated successfully (0). Closing log file.
    Initializing built-in extension Generic Event Extension
    Initializing built-in extension SHAPE
    Initializing built-in extension MIT-SHM
    Initializing built-in extension XInputExtension
    Initializing built-in extension XTEST
    Initializing built-in extension BIG-REQUESTS
    Initializing built-in extension SYNC
    Initializing built-in extension XKEYBOARD
    Initializing built-in extension XC-MISC
    Initializing built-in extension SECURITY
    Initializing built-in extension XINERAMA
    Initializing built-in extension XFIXES
    Initializing built-in extension RENDER
    Initializing built-in extension RANDR
    Initializing built-in extension COMPOSITE
    Initializing built-in extension DAMAGE
    Initializing built-in extension MIT-SCREEN-SAVER
    Initializing built-in extension DOUBLE-BUFFER
    Initializing built-in extension RECORD
    Initializing built-in extension DPMS
    Initializing built-in extension X-Resource
    Initializing built-in extension XVideo
    Initializing built-in extension XVideo-MotionCompensation
    Initializing built-in extension XFree86-VidModeExtension
    Initializing built-in extension XFree86-DGA
    Initializing built-in extension XFree86-DRI
    Initializing built-in extension DRI2
    Loading extension GLX
    klauncher(5014) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(5008)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(5008)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    Server terminated successfully (0). Closing log file.
    Initializing built-in extension Generic Event Extension
    Initializing built-in extension SHAPE
    Initializing built-in extension MIT-SHM
    Initializing built-in extension XInputExtension
    Initializing built-in extension XTEST
    Initializing built-in extension BIG-REQUESTS
    Initializing built-in extension SYNC
    Initializing built-in extension XKEYBOARD
    Initializing built-in extension XC-MISC
    Initializing built-in extension SECURITY
    Initializing built-in extension XINERAMA
    Initializing built-in extension XFIXES
    Initializing built-in extension RENDER
    Initializing built-in extension RANDR
    Initializing built-in extension COMPOSITE
    Initializing built-in extension DAMAGE
    Initializing built-in extension MIT-SCREEN-SAVER
    Initializing built-in extension DOUBLE-BUFFER
    Initializing built-in extension RECORD
    Initializing built-in extension DPMS
    Initializing built-in extension X-Resource
    Initializing built-in extension XVideo
    Initializing built-in extension XVideo-MotionCompensation
    Initializing built-in extension XFree86-VidModeExtension
    Initializing built-in extension XFree86-DGA
    Initializing built-in extension XFree86-DRI
    Initializing built-in extensio

  • Does LR handle a dual monitor setup with different aspect ratios (16:9 and 16:10)?

    Does LR 5 handle a dual monitor setup with different aspect ratios (16:9 and 16:10)?
    I'm planing to buy a 27" 16:9 monitor and use it as primary together with a 22" 16:10. Does any have any idea?
    Thanks

    Moreover, the two monitors can have completely different characteristics.  As always, you really need to calibrate/profile any monitor (with a hardware tool - Spyder, Colormunki etc).  That's no more important with two monitors, but you see for sure if you don't, as two dissimilar monitors will then probably look different. 

  • Dynadock VGA - monitor suddenly freezes and disappears

    OK, perhaps a bit cryptic.
    What happens is this: I have a Zepto Znote notebook with a GeForce 8600M graphics card. I want to use that as my only computer, but I'm 100 % dependant on a dual monitor setup in my line of work (media work with a video on one and a script on the other).
    On both Vista 32 and XP I have managed to install everything (and I have tried with both Toshiba drivers and newer Display Link drivers) and the monitor works.
    But after a random period, from a minute and up to around 15 minutes (which is the longest I have managed to work this far) the monitor on the Dynadock just locks up on the current image page, and I can't get the mouse up on that monitor anymore. The actual program running on that monitor (often Foxit PDF reader or Word) has now jumped to the main monitor, behind the active program.
    The secondary Dynadock monitor will be deactivated in display manager, and if I activate it again nothing happens. I have to restart the computer without the Dynadock plugged in and then plug it in.
    It will work for a few minutes again, and we're back to the same problem. I tried to update the LAN drivers and the Display Link drivers and disabling the LAN, but that didn't do anything.
    And this can happen while I'm doing something on the secondary monitor or when the display has a static image.
    What type of image doesn't seem to matter either. Can anybody please help me?

    Hi
    Okaccording to you message the secondary Dynadock monitor deactivates in display manager.
    I think its not a Dynadock issue but possibly its your notebook issue.
    I think the Dynadock loses the connection signal to the notebook and therefore the secondary Dynadock monitor deactivates and the pic freezes.
    It would be interesting to know how it works with another computer.

  • MacPro3,1 triple monitor setup

    Hi there!
    I'm looking to expand my Apple 30" monitor setup with two (very cheap but highly acclaimed) Dell UltraSharp™ U2311H monitors. However, I'm unsure if I do or do not need an additional video card and if so, which one. I have an NVIDIA GeForce 8800 GT with (I think) two DVI-I Dual Link ports. I've read that there are DVI-splitters, but I have been unable to find any conclusive information.
    Does anyone know how I can do this?
    Friendly greetings, D, Amsterdam.

    Hi Grant!
    Thanks for your help earlier ;-)
    I hope you might be able to shed some light on a little problem I have with my triple monitor setup. I bought the following items:
    Two Dell Professional P2411H 61cm (24") LED monitors.
    Two MiniDisplayPort to DVI adapters.
    I've took your advice on the card and also got one ATI RADEON HD 5770 1GB-ZML card.
    The monitors, in combination with the adapters and the card ... it all works, but there's one limitation I believe shouldn't be there.
    The problem is this: either the hardware or software is only allowing me to connect two displays in total. If I connect all three displays, only the Dell monitors are able to connect. If I disconnect one Dell monitor, the Apple 30" display goes live. So, whatever in whatever combination or order I try to connect the displays, only two screens are connecting simultaneously.
    Do you, or does someone else know how to fix this? Would be great to fix this soon and become the pixonaut of my own digitale cockpit!

  • HP Pavilion dv7-2250ed and dual monitor setup

    Good evening,
    Currently I own a HP Pavilion dv7-2250ed notebook using a dual monitor setup (notebook display + extra monitor)
    I wondered if it would be possible to hook 2 monitors to this laptop? (notebook display + extra monitor + extra monitor)
    If this causes the problem, the notebook display isn't requered.
    Also, if not, is there a dockingstation for this brand which supports the above?
    Kind Regards,
    Cor van Noorloos
    Edit: a note to the devs of these forums, using multiple tags is done by comma's, not by spaces. You might wish to rephrase this phrase.

    wgarn wrote:
    I have attempted to connect one monitor via HDMI and the other one via the VGA interface.
    Using Windows 7 OS and "default configurations" (Control Panel\Appearance and Personalization\Display\Screen Resolution) it is possible to use both external monitors as desktop. However the laptop screen will go blank. So at any time it appears to be possible to have an extended desktop with only two screens.
    - Does HP have any drivers/solutions that make it possible to extend the desktop from "Mobile PC" display to two additional desktops?
    - Has anyone tried third party software  (e.g.. UltraMon)?
    - Is there a technical restriction (e.g.. Videocard capability)?
    - How about using a Linux OS (e.g.. Ubuntu)?
    - What external Hardware exists that would enable me to extend my desktop to three or more monitors simultaneously?
    Many thanks in advance.
    It's the graphics card and the number of physical connections available.  You might have 3 connections (notebook display being one) but the graphics card likely does not support more than 2 monitors.  Intel graphics only support 2, however you may be able to find some AMD chips that will support more however that would be a major upgrade.
    ________________________________________________________________________________________________________ I Love Kudos! If you feel my post has helped you please click the White Kudos! Star just below my name
    If you feel my answer has fixed your problem please click 'Mark As Solution' and make it easier for others to find help quickly

  • Hardware monitor error

    have any of you experienced spontaneous system shut downs followed by bios reports of 'hardware monitor error' press delete to enter setup etc.  My system has been brought to its knees by this and the good people at samsung have told me that it is probably the vga or the mainboard - which are the g4ti4200td and the a7v333 respectively.  I am stumped, is this possibly an IRQ issue, or a refresh rate issue or what.  The problem is not isolated to high graphic output operations, indicating, I would thing, a memory problem.  It happens seemingly in spite of me, no matter if I am running any programs or not.
    any info is much appreciated... thanx ?(

    Can I have your specs of your computer you are running on? Thanks...

  • How do I avoid errors on a Multi - monitor setup?

    Hi.
    I want to use Photoshop CS6 on a Multi - monitor setup, using iGPU multi-monitor + GPU system for 4 monitors.
    Preiously, I used Photoshop on a Multi - monitor setup without useing iGPU multi-monitor.
    And, Photoshop worked well.
    However, when I wanted to use 1 more monitor, my GPU supports only 3 monitors.
    Then, I enabled iGPU multi-monitor function. It supports 2 more monitors.
    At first, It worked. But, after I use "Free transform", "Transform"  or something like these tools, Photoshop hang up!
    I couldn't figure out the reason why these errors happened.
    I need ways to avoid these errors.
    Thanks.

    Thanks for viewing this discussion.
    Finally, I brok through this problem.
    I show you how to do, in case of when you face to this problem.
    The way to solve this problem is, simple, "buy a new GPU."
    But, there is 1 important point, you should buy a same bland's GPU.
    In my case, I have SAPPHIRE'S RADEON HD5670, and I bought SAPPHIRE'S RADEON HD 6450.
    I think that Photoshop GPUsniffer was confused about GPU driver.
    Because there were 2 drivers -- Radeon and Intel Graphics -- exist.
    That's why Photoshop hang up.
    For your reference,
    Best regards.

Maybe you are looking for