R835-P56X: Bios Options - Intel (R) AT and AT Suspend?

I was poking around in the BIOS for my R835-P56X and found a couple options that I haven't seen before:
Intel (R) AT
Intel (R) AT Suspend
I can't find any discussion of these options in the User's Guide (which doesn't cover the BIOS except for what can be changed with the HWSetup utility).
Does anyone know what they do?

The question would be if it translates into real gains in real world applications. You should test some 3D game or something to see if the performance is really great or just the same as usual. glxgears is quite a useless benchmark by itself (though it's good news that you get 3000 fps anyway).

Similar Messages

  • Probook 640 bios - Enable Intel VT-x and disable trusted execution for VMWare

    With the Probook 640, can someone please explain, step by step, how I would make the proper settings in the bios for VMWare virtualization?  I need to enable Intel VT-x and disable trusted execution.Thank you.

    randallto wrote:
    There was another setting in bois I found that required scrolling in the bios screen. Tricky to find with no mouse.
    I am not sure if some day these terminologies can be standardized so someone can follow very specific instructions rather than vague instructions that are further obfuscated with the use of technical acronyms.
    That is the problem, that error message in VM is not explicit enough as to what steps to take to correct the problem. These bois screen authors decide arbitrarily to name settings as it relates to their world personally and there are not standards.
    I still don't know how that  got changed in the first place but that is not an issue with VM ware as to what else is changing the setting.
    Do you have any explicit suggestions as to how the error message can be improved?

  • Portege R835-P56X : are there no Wifi and soundcard drivers for WIn XP ?

    I have just got a Portege R835-P56X . Are there any Wifi and Soundcard drivers for Windows XP for this laptop ?  I want to downgrade to win XP as I have a huge collection of legacy software which have compatibility issues with WIndows 7. I can't find the required drivers on the Toshiba website, all though there are drivers for webcam or touchpad. I don't understand the reason for having a few drivers for XP but not all the required ones. Surely one can't use a laptop without Wifi or  audio.  

    Portege R835-P56X
    Best to upgrade Home Premium to Professional and then install XP Mode. Works really well here.
       Upgrade to another edition of Windows 7 by using Windows Anytime Upgrade
       Install and use Windows XP Mode in Windows 7
    It's not necessary to have hardware vitualization enabled. See KB977206.
    -Jerry

  • R835 P56X lock ups

    From day 1 (purchased a month ago) I'm still having lock ups with this laptop!  After few hours of use the screen goes black (sometimes blue), if I try to revive it the fan kicks in at full speed sounding like a leaf blower!
    I've reinstalled Win7 with the latest drivers, installed a new SSD instead of the HD and this problem keeps re-occuring randomly (daily)!
    I certainly would appreciate any ideas!

    I replaced my HDD with a OCZ Vertex 3 SSD for my R835-P56x.  It boot in seconds and runs nice and fast, but I get lock-ups and BSOD after several hours (as described above).  Not sure if it had the problem with the HDD, because I didnt use the PC very long before upgrading.  I am also running a 800MB Dataram RAM Disk (Version 3.5.130) for browser cache, which I suspect could be the culprit.   My bios is 3.90 (7/31/2012).
    Portege R835-P56x, i5 2410M, 16GB RAM, Vertex 3 SSD 240GB.

  • R835-P56X:i can use SATA III (6.0 Gb/s) Now

    R835-P56X:i can use SATA III (6.0 Gb/s) Now
    1.BIOS Update to 3.0
    2.My OCZ Vertex3 SSD firmware update to 2.11
    3.install Intel RST Driver
    Attachments:
    02.jpg ‏115 KB
    03.jpg ‏118 KB
    01.jpg ‏110 KB
    atto.jpg ‏128 KB

    I emailed Toshiba regarding this issue and this is their reply:
    Hi!
    "On Fri, Oct 28, 2011 at 9:08 AM, Contact Us <[email protected]> wrote:
    Hello Tor
    The SATA 111 will be launched mid 2012 and do not have any clear details as of yet.
    Regards,
    Inside Sales
    Toshiba of Canada Limited"
    I am very happy with my Portege R835, except for the sata-issue....severely limiting my SSD speed, as I as many others bought this computer specifically because I thought it supported Sata 3. It is absolutely horrific of Toshiba to limit the sata speeds without telling their customers about it!! They will definitely lose thousands of customers on this rather stupid move of theirs. Unbelievable!! Why ruin such a good computer. Sell customers a Ferrari not telling them it's speed limited to 80mph. Toshiba; be up front about such vital information to your customers!!!

  • R835 P56X USB 3 problems

    I have my R835 running nice now with Crucial M4 SSD, 8 gigs ram, 6230 wifi and the latest Bios & drivers.  But, whenever I use the usb3 port to transfer files from or to my usb3 supported external drive, it starts out fast but then comes to a screaching halt at quarter or third into the transfer!  The computer doesn't freeze or crash, its just like the port locks up!  Then I'd have to use the other usb2 ports without any problems, but slower!
    Any ideas?  I made sure the usb3 driver is installed!
    Thanks.

    Check out this post from another forum:
    [quote]
    USB 3.0 problem appeared on my Satellite R830 after a month of everyday use. Controller started to power itself off not only on heavy file transfers, but sometimes even with simple USB mouse connected to it. Problem existed on both OSes which I have installed on my SSD: 32-bit WinXP Pro with latest driver from Toshiba's website ver. 2.0.34.1 and 64-bit FC16 Linux with 3.1.2 kernel (i've swapped stock HDD to Intel 320 SSD and said goodbye to Win7).
    After a small research it seems that this is not Toshiba's problem, but a bug in old firmware of Renesas uPD720200 USB 3.0 controllers. It is described here for example. I've installed latest Renesas firmware (4.0.1.5) and latest Windows driver (2.1.28.0) found here, and it helped. I think problem has completely vanished now on all OSes, so solution was in firmware update, not in driver.
    [/quote]
    http://http://forum.notebookreview.com/toshiba/616670-satellite-r830-r835-serious-flaws-besides-phan...
    Good luck
    ========================================================
    QOSMIO - x505 q8102X
    i7-2630QM , GTX 460m , 18.4" screen @ 1680x945p

  • Problem with 3 monitors Intel HD Graphics and GeForce GTX 560

    I would like to attach 3 monitors to my box -- 1 to integrated Intel card and 2 to discreet Nvidia. I've tried different configs but I failed to make monitors connected to different cards to work at the same time. I have system with stock kernel, latest updates and the following configuration:
    $ lspci | egrep "VGA|Disp"
    00:02.0 Display controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
    01:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 Ti] (rev a1)
    $ pacman -Qi xorg-server xf86-video-intel nvidia awesome-git linux | egrep "Name|Version"
    Name : xorg-server
    Version : 1.17.1-3
    Name : xf86-video-intel
    Version : 2.99.917-3
    Name : nvidia
    Version : 346.47-3
    Name : awesome-git
    Version : 3.5.2.397.gdde5b1b-1
    Name : linux
    Version : 3.18.6-1
    $ lsmod | egrep 'i915|nvidia'
    nvidia 8335766 46
    i915 946695 2
    button 12953 1 i915
    i2c_algo_bit 12744 1 i915
    video 18043 2 i915,asus_wmi
    drm_kms_helper 80985 1 i915
    drm 263481 7 i915,drm_kms_helper,nvidia
    i2c_core 50152 6
    drm,i915,i2c_i801,drm_kms_helper,i2c_algo_bit,nvidia
    intel_gtt 17848 2 i915,intel_agp
    I've tried different xorg configs. Here is the best one. All 3 monitors are active with it (I could drag cursor over them) but only 2 (which connected to nvidia card) display DE.
    Section "DRI"
    Mode 0666
    EndSection
    Section "Monitor"
    Identifier "SAM"
    ModelName "Samsung SMS27A850"
    HorizSync 30.0 - 90.0
    VertRefresh 56.0 - 75.0
    Option "DPMS"
    DisplaySize 597 336 # In millimeters
    EndSection
    Section "Monitor"
    Identifier "VS"
    ModelName "ViewSonic VG1930wm"
    Option "DPMS"
    Option "RightOf" "SAM"
    Option "Rotate" "left"
    EndSection
    Section "Monitor"
    Identifier "BNQ"
    ModelName "BenQ FP737s"
    Option "DPMS"
    Option "LeftOf" "SAM"
    Option "Rotate" "left"
    EndSection
    Section "Device"
    Identifier "nvidia"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce GTX 560 Ti"
    BusID "01:00:0"
    Option "Monitor-DVI-I-1" "SAM"
    Option "Monitor-DVI-I-2" "VS"
    EndSection
    Section "Device"
    Identifier "intel"
    Driver "intel"
    Option "AccelMethod" "none"
    VendorName "Intel"
    BoardName "Intel Integrated Graphic Controller"
    BusID "00:02:0"
    Option "Monitor-VGA-0" "BNQ"
    EndSection
    Section "Screen"
    Identifier "SAM-Screen"
    Device "nvidia"
    Monitor "SAM"
    EndSection
    Section "Screen"
    Identifier "VS-Screen"
    Device "nvidia"
    Monitor "VS"
    EndSection
    Section "Screen"
    Identifier "BNQ-Screen"
    Device "intel"
    Monitor "BNQ"
    EndSection
    Section "ServerLayout"
    Identifier "Layout0"
    Screen 0 "SAM-Screen"
    Screen 1 "VS-Screen" RightOf "SAM-Screen"
    Screen 2 "BNQ-Screen" LeftOf "SAM-Screen"
    Option "Xinerama" "0"
    EndSection
    Also, xrandr shows last monitor (VGA-0, it plugged into Intel card) as disconnected
    $ xrandr
    Screen 0: minimum 8 x 8, current 3460 x 1440, maximum 16384 x 16384
    DVI-I-0 disconnected primary (normal left inverted right x axis y axis)
    VGA-0 disconnected (normal left inverted right x axis y axis)
    DVI-I-1 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 518mm x 324mm
    2560x1440 59.95*+
    1920x1200 59.88
    1920x1080 60.00 50.00
    1680x1050 59.95
    1600x1200 60.00
    1440x900 59.89
    1280x1024 75.02 60.02
    1280x960 60.00
    1280x800 59.81
    1280x720 60.00 50.00
    1152x864 75.00
    1024x768 75.03 70.07 60.00
    800x600 75.00 72.19 60.32 56.25
    720x576 50.00
    720x480 59.94
    640x480 75.00 72.81 59.94
    HDMI-0 disconnected (normal left inverted right x axis y axis)
    DVI-I-2 connected 900x1440+2560+0 left (normal left inverted right x axis y axis) 410mm x 256mm
    1440x900 59.89*+ 74.98
    1280x1024 75.02 60.02
    1280x960 60.00
    1152x864 75.00
    1024x768 75.03 70.07 60.00
    800x600 75.00 72.19 60.32 56.25
    640x480 75.00 72.81 59.94
    640x400 70.10
    But it's still posible to start application on last monitor with 'env DISPLAY:=0.1 urxvt'
    Here is full Xorg log file and highlights:
    [ 4789.920] (EE) intel(1): Cannot position output VGA1 relative to unknown output SAM
    [ 4792.053] (EE) intel(G0): [drm] failed to set drm interface version: Permission denied [13].
    [ 4792.053] (II) intel(G0): [drm] Contents of '/sys/kernel/debug/dri/0/clients':
    [ 4792.053] (II) intel(G0): [drm] command pid dev master a uid magic
    [ 4792.053] (II) intel(G0): [drm] Xorg 10086 0 y y 0 0
    [ 4792.053] (II) intel(G0): [drm] Xorg 10086 0 n y 0 0
    [ 4792.053] (EE) intel(G0): Failed to claim DRM device.
    [ 4792.053] (II) UnloadModule: "intel"
    [ 4789.342]
    X.Org X Server 1.17.1
    Release Date: 2015-02-10
    [ 4789.342] X Protocol Version 11, Revision 0
    [ 4789.342] Build Operating System: Linux 3.18.6-1-ARCH x86_64
    [ 4789.342] Current Operating System: Linux earth 3.18.6-1-ARCH #1 SMP PREEMPT Sat Feb 7 08:44:05 CET 2015 x86_64
    [ 4789.342] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=dc49b07c-e67c-4b6f-91f7-7c1adc050e21 rw quiet ipv6.disable=1 init=/usr/lib/systemd/systemd security=tomoyo TOMOYO_trigger=/usr/lib/systemd/systemd
    [ 4789.342] Build Date: 22 February 2015 12:50:32PM
    [ 4789.342]
    [ 4789.342] Current version of pixman: 0.32.6
    [ 4789.342] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 4789.342] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 4789.342] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Mar 1 14:43:55 2015
    [ 4789.342] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 4789.342] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
    [ 4789.342] (==) ServerLayout "Layout0"
    [ 4789.342] (**) |-->Screen "SAM-Screen" (0)
    [ 4789.342] (**) | |-->Monitor "SAM"
    [ 4789.343] (**) | |-->Device "nvidia"
    [ 4789.343] (**) |-->Screen "VS-Screen" (1)
    [ 4789.343] (**) | |-->Monitor "VS"
    [ 4789.343] (**) | |-->Device "nvidia"
    [ 4789.343] (**) |-->Screen "BNQ-Screen" (2)
    [ 4789.343] (**) | |-->Monitor "BNQ"
    [ 4789.343] (**) | |-->Device "intel"
    [ 4789.343] (**) Option "Xinerama" "0"
    [ 4789.343] (==) Automatically adding devices
    [ 4789.343] (==) Automatically enabling devices
    [ 4789.343] (==) Automatically adding GPU devices
    [ 4789.343] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/OTF/,
    /usr/share/fonts/Type1/,
    /usr/share/fonts/100dpi/,
    /usr/share/fonts/75dpi/
    [ 4789.343] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 4789.343] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 4789.343] (II) Loader magic: 0x815d80
    [ 4789.343] (II) Module ABI versions:
    [ 4789.343] X.Org ANSI C Emulation: 0.4
    [ 4789.343] X.Org Video Driver: 19.0
    [ 4789.343] X.Org XInput driver : 21.0
    [ 4789.343] X.Org Server Extension : 9.0
    [ 4789.344] (EE) systemd-logind: failed to get session: PID 10086 does not belong to any known session
    [ 4789.345] (II) xfree86: Adding drm device (/dev/dri/card1)
    [ 4789.345] (II) xfree86: Adding drm device (/dev/dri/card0)
    [ 4789.347] (--) PCI: (0:0:2:0) 8086:0102:1043:84ca rev 9, Mem @ 0xf6400000/4194304, 0xd0000000/268435456, I/O @ 0x0000f000/64
    [ 4789.347] (--) PCI:*(0:1:0:0) 10de:1200:10b0:0401 rev 161, Mem @ 0xf4000000/33554432, 0xe0000000/134217728, 0xe8000000/67108864, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
    [ 4789.347] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    [ 4789.347] (II) LoadModule: "glx"
    [ 4789.347] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 4789.359] (II) Module glx: vendor="NVIDIA Corporation"
    [ 4789.359] compiled for 4.0.2, module version = 1.0.0
    [ 4789.359] Module class: X.Org Server Extension
    [ 4789.359] (II) NVIDIA GLX Module 346.47 Thu Feb 19 18:09:07 PST 2015
    [ 4789.359] (II) LoadModule: "nvidia"
    [ 4789.359] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
    [ 4789.360] (II) Module nvidia: vendor="NVIDIA Corporation"
    [ 4789.360] compiled for 4.0.2, module version = 1.0.0
    [ 4789.360] Module class: X.Org Video Driver
    [ 4789.360] (II) LoadModule: "intel"
    [ 4789.360] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
    [ 4789.360] (II) Module intel: vendor="X.Org Foundation"
    [ 4789.360] compiled for 1.17.1, module version = 2.99.917
    [ 4789.360] Module class: X.Org Video Driver
    [ 4789.360] ABI class: X.Org Video Driver, version 19.0
    [ 4789.360] (II) NVIDIA dlloader X Driver 346.47 Thu Feb 19 17:47:18 PST 2015
    [ 4789.360] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
    [ 4789.360] (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
    [ 4789.360] (II) intel: Driver for Intel(R) HD Graphics: 2000-6000
    [ 4789.360] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100
    [ 4789.360] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200, 6200, P6300
    [ 4789.360] (++) using VT number 7
    [ 4789.471] (II) Loading sub module "fb"
    [ 4789.471] (II) LoadModule: "fb"
    [ 4789.471] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 4789.471] (II) Module fb: vendor="X.Org Foundation"
    [ 4789.471] compiled for 1.17.1, module version = 1.0.0
    [ 4789.471] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 4789.472] (II) Loading sub module "wfb"
    [ 4789.472] (II) LoadModule: "wfb"
    [ 4789.472] (II) Loading /usr/lib/xorg/modules/libwfb.so
    [ 4789.472] (II) Module wfb: vendor="X.Org Foundation"
    [ 4789.472] compiled for 1.17.1, module version = 1.0.0
    [ 4789.472] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 4789.472] (II) Loading sub module "ramdac"
    [ 4789.472] (II) LoadModule: "ramdac"
    [ 4789.472] (II) Module "ramdac" already built-in
    [ 4789.473] (II) intel(1): Using Kernel Mode Setting driver: i915, version 1.6.0 20140905
    [ 4789.474] (II) intel(G0): Using Kernel Mode Setting driver: i915, version 1.6.0 20140905
    [ 4789.474] (II) NVIDIA(0): Creating default Display subsection in Screen section
    "SAM-Screen" for depth/fbbpp 24/32
    [ 4789.474] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
    [ 4789.474] (==) NVIDIA(0): RGB weight 888
    [ 4789.474] (==) NVIDIA(0): Default visual is TrueColor
    [ 4789.474] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
    [ 4789.474] (**) NVIDIA(0): Enabling 2D acceleration
    [ 4789.841] (II) NVIDIA(GPU-0): Found DRM driver nvidia-drm (20150116)
    [ 4789.842] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 560 Ti (GF114) at PCI:1:0:0 (GPU-0)
    [ 4789.842] (--) NVIDIA(0): Memory: 1048576 kBytes
    [ 4789.842] (--) NVIDIA(0): VideoBIOS: 70.24.21.00.00
    [ 4789.842] (II) NVIDIA(0): Detected PCI Express Link width: 16X
    [ 4789.875] (--) NVIDIA(0): Valid display device(s) on GeForce GTX 560 Ti at PCI:1:0:0
    [ 4789.875] (--) NVIDIA(0): CRT-0
    [ 4789.875] (--) NVIDIA(0): CRT-1
    [ 4789.875] (--) NVIDIA(0): Samsung SMS27A850 (DFP-0) (boot, connected)
    [ 4789.875] (--) NVIDIA(0): DFP-1
    [ 4789.875] (--) NVIDIA(0): ViewSonic VG1930wm (DFP-2) (connected)
    [ 4789.875] (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
    [ 4789.875] (--) NVIDIA(GPU-0): CRT-1: 400.0 MHz maximum pixel clock
    [ 4789.875] (--) NVIDIA(0): Samsung SMS27A850 (DFP-0): Internal TMDS
    [ 4789.875] (--) NVIDIA(GPU-0): Samsung SMS27A850 (DFP-0): 330.0 MHz maximum pixel clock
    [ 4789.875] (--) NVIDIA(0): DFP-1: Internal TMDS
    [ 4789.875] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
    [ 4789.875] (--) NVIDIA(0): ViewSonic VG1930wm (DFP-2): Internal TMDS
    [ 4789.875] (--) NVIDIA(GPU-0): ViewSonic VG1930wm (DFP-2): 330.0 MHz maximum pixel clock
    [ 4789.875] (**) NVIDIA(0): Option "Rotate" "left"
    [ 4789.875] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 4789.875] (**) NVIDIA(0): device Samsung SMS27A850 (DFP-0) (Using EDID frequencies
    [ 4789.875] (**) NVIDIA(0): has been enabled on all display devices.)
    [ 4789.875] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
    [ 4789.875] (WW) NVIDIA(GPU-0): mode "1920x1080" is specified in the EDID; however, the
    [ 4789.875] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
    [ 4789.875] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
    [ 4789.875] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1920x1080".
    [ 4789.876] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
    [ 4789.876] (WW) NVIDIA(GPU-0): mode "1280x720" is specified in the EDID; however, the
    [ 4789.876] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
    [ 4789.876] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
    [ 4789.876] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1280x720".
    [ 4789.876] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
    [ 4789.876] (WW) NVIDIA(GPU-0): mode "720x576" is specified in the EDID; however, the
    [ 4789.876] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
    [ 4789.876] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
    [ 4789.876] (WW) NVIDIA(GPU-0): VertRefresh check for mode "720x576".
    [ 4789.877] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 4789.877] (**) NVIDIA(0): device ViewSonic VG1930wm (DFP-2) (Using EDID frequencies
    [ 4789.877] (**) NVIDIA(0): has been enabled on all display devices.)
    [ 4789.878] (==) NVIDIA(0):
    [ 4789.878] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
    [ 4789.878] (==) NVIDIA(0): will be used as the requested mode.
    [ 4789.878] (==) NVIDIA(0):
    [ 4789.878] (II) NVIDIA(0): Validated MetaModes:
    [ 4789.878] (II) NVIDIA(0):
    [ 4789.878] (II) NVIDIA(0): "DFP-0:nvidia-auto-select,DFP-2:nvidia-auto-select{Rotation=90}"
    [ 4789.878] (II) NVIDIA(0): Virtual screen size determined to be 3460 x 1440
    [ 4789.905] (--) NVIDIA(0): DPI set to (125, 114); computed from "UseEdidDpi" X config
    [ 4789.905] (--) NVIDIA(0): option
    [ 4789.906] (--) intel(1): Integrated Graphics Chipset: Intel(R) HD Graphics 2000
    [ 4789.906] (--) intel(1): CPU: x86-64, sse2, sse3, ssse3, sse4.1, sse4.2, avx
    [ 4789.906] (II) intel(1): Creating default Display subsection in Screen section
    "BNQ-Screen" for depth/fbbpp 24/32
    [ 4789.906] (==) intel(1): Depth 24, (--) framebuffer bpp 32
    [ 4789.906] (==) intel(1): RGB weight 888
    [ 4789.906] (==) intel(1): Default visual is TrueColor
    [ 4789.906] (**) intel(1): Option "AccelMethod" "none"
    [ 4789.906] (II) intel(1): Output VGA1 using monitor section BNQ
    [ 4789.906] (**) intel(1): Option "LeftOf" "SAM"
    [ 4789.906] (**) intel(1): Option "Rotate" "left"
    [ 4789.906] (II) intel(1): Enabled output VGA1
    [ 4789.906] (II) intel(1): Output HDMI1 has no monitor section
    [ 4789.906] (II) intel(1): Enabled output HDMI1
    [ 4789.906] (II) intel(1): Output DP1 has no monitor section
    [ 4789.906] (II) intel(1): Enabled output DP1
    [ 4789.906] (II) intel(1): Output HDMI2 has no monitor section
    [ 4789.906] (II) intel(1): Enabled output HDMI2
    [ 4789.906] (II) intel(1): Output HDMI3 has no monitor section
    [ 4789.906] (II) intel(1): Enabled output HDMI3
    [ 4789.906] (II) intel(1): Output DP2 has no monitor section
    [ 4789.906] (II) intel(1): Enabled output DP2
    [ 4789.906] (II) intel(1): Output DP3 has no monitor section
    [ 4789.906] (II) intel(1): Enabled output DP3
    [ 4789.906] (--) intel(1): Using a maximum size of 256x256 for hardware cursors
    [ 4789.906] (II) intel(1): Output VIRTUAL1 has no monitor section
    [ 4789.906] (II) intel(1): Enabled output VIRTUAL1
    [ 4789.906] (II) intel(1): EDID for output DP1
    [ 4789.906] (II) intel(1): EDID for output DP2
    [ 4789.906] (II) intel(1): EDID for output DP3
    [ 4789.906] (II) intel(1): EDID for output HDMI1
    [ 4789.906] (II) intel(1): EDID for output HDMI2
    [ 4789.907] (II) intel(1): EDID for output HDMI3
    [ 4789.920] (II) intel(1): EDID for output VGA1
    [ 4789.920] (II) intel(1): Manufacturer: BNQ Model: 7659 Serial#: 28
    [ 4789.920] (II) intel(1): Year: 2003 Week: 39
    [ 4789.920] (II) intel(1): EDID Version: 1.3
    [ 4789.920] (II) intel(1): Analog Display Input, Input Voltage Level: 0.700/0.700 V
    [ 4789.920] (II) intel(1): Sync: Separate Composite
    [ 4789.920] (II) intel(1): Max Image Size [cm]: horiz.: 34 vert.: 27
    [ 4789.920] (II) intel(1): Gamma: 2.20
    [ 4789.920] (II) intel(1): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
    [ 4789.920] (II) intel(1): First detailed timing is preferred mode
    [ 4789.920] (II) intel(1): redX: 0.640 redY: 0.340 greenX: 0.290 greenY: 0.611
    [ 4789.920] (II) intel(1): blueX: 0.140 blueY: 0.069 whiteX: 0.310 whiteY: 0.330
    [ 4789.920] (II) intel(1): Supported established timings:
    [ 4789.920] (II) intel(1): 720x400@70Hz
    [ 4789.920] (II) intel(1): 640x480@60Hz
    [ 4789.920] (II) intel(1): 640x480@67Hz
    [ 4789.920] (II) intel(1): 640x480@72Hz
    [ 4789.920] (II) intel(1): 640x480@75Hz
    [ 4789.920] (II) intel(1): 800x600@56Hz
    [ 4789.920] (II) intel(1): 800x600@60Hz
    [ 4789.920] (II) intel(1): 800x600@72Hz
    [ 4789.920] (II) intel(1): 800x600@75Hz
    [ 4789.920] (II) intel(1): 832x624@75Hz
    [ 4789.920] (II) intel(1): 1024x768@60Hz
    [ 4789.920] (II) intel(1): 1024x768@70Hz
    [ 4789.920] (II) intel(1): 1024x768@75Hz
    [ 4789.920] (II) intel(1): 1280x1024@75Hz
    [ 4789.920] (II) intel(1): 1152x864@75Hz
    [ 4789.920] (II) intel(1): Manufacturer's mask: 0
    [ 4789.920] (II) intel(1): Supported standard timings:
    [ 4789.920] (II) intel(1): #0: hsize: 1152 vsize 864 refresh: 75 vid: 20337
    [ 4789.920] (II) intel(1): #1: hsize: 1280 vsize 1024 refresh: 76 vid: 36993
    [ 4789.920] (II) intel(1): #2: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
    [ 4789.920] (II) intel(1): #3: hsize: 1280 vsize 1024 refresh: 72 vid: 35969
    [ 4789.920] (II) intel(1): Supported detailed timing:
    [ 4789.920] (II) intel(1): clock: 108.0 MHz Image Size: 338 x 270 mm
    [ 4789.920] (II) intel(1): h_active: 1280 h_sync: 1328 h_sync_end 1440 h_blank_end 1688 h_border: 0
    [ 4789.920] (II) intel(1): v_active: 1024 v_sync: 1025 v_sync_end 1028 v_blanking: 1066 v_border: 0
    [ 4789.920] (II) intel(1): Supported detailed timing:
    [ 4789.920] (II) intel(1): clock: 25.2 MHz Image Size: 304 x 228 mm
    [ 4789.920] (II) intel(1): h_active: 640 h_sync: 656 h_sync_end 752 h_blank_end 800 h_border: 0
    [ 4789.920] (II) intel(1): v_active: 350 v_sync: 387 v_sync_end 389 v_blanking: 449 v_border: 0
    [ 4789.920] (II) intel(1): Ranges: V min: 56 V max: 75 Hz, H min: 31 H max: 81 kHz, PixClock max 145 MHz
    [ 4789.920] (II) intel(1): Monitor name: BenQ FP737s
    [ 4789.920] (II) intel(1): EDID (in hex):
    [ 4789.920] (II) intel(1): 00ffffffffffff0009d159761c000000
    [ 4789.920] (II) intel(1): 270d01036c221b78eac6f6a3574a9c23
    [ 4789.920] (II) intel(1): 114f54bfef80714f81908180818c0101
    [ 4789.920] (II) intel(1): 010101010101302a009851002a403070
    [ 4789.920] (II) intel(1): 1300520e1100001ed50980a0205e6310
    [ 4789.920] (II) intel(1): 1060520830e41000001a000000fd0038
    [ 4789.920] (II) intel(1): 4b1f510e000a202020202020000000fc
    [ 4789.920] (II) intel(1): 0042656e51204650373337730a200072
    [ 4789.920] (II) intel(1): Printing probed modes for output VGA1
    [ 4789.920] (II) intel(1): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
    [ 4789.920] (II) intel(1): Modeline "1280x1024"x76.0 141.81 1280 1376 1512 1744 1024 1025 1028 1070 -hsync +vsync (81.3 kHz)
    [ 4789.920] (II) intel(1): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 4789.920] (II) intel(1): Modeline "1280x1024"x72.0 132.84 1280 1368 1504 1728 1024 1025 1028 1067 -hsync +vsync (76.9 kHz)
    [ 4789.920] (II) intel(1): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 4789.920] (II) intel(1): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
    [ 4789.920] (II) intel(1): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
    [ 4789.920] (II) intel(1): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 4789.920] (II) intel(1): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
    [ 4789.920] (II) intel(1): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
    [ 4789.920] (II) intel(1): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 4789.920] (II) intel(1): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 4789.920] (II) intel(1): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 4789.920] (II) intel(1): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 4789.920] (II) intel(1): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 491 520 -hsync -vsync (37.9 kHz e)
    [ 4789.920] (II) intel(1): Modeline "640x480"x66.7 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
    [ 4789.920] (II) intel(1): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 4789.920] (II) intel(1): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 4789.920] (II) intel(1): Modeline "640x350"x70.1 25.17 640 656 752 800 350 387 389 449 +hsync -vsync (31.5 kHz e)
    [ 4789.920] (II) intel(1): EDID for output VIRTUAL1
    [ 4789.920] (II) intel(1): Output DP1 disconnected
    [ 4789.920] (II) intel(1): Output DP2 disconnected
    [ 4789.920] (II) intel(1): Output DP3 disconnected
    [ 4789.920] (II) intel(1): Output HDMI1 disconnected
    [ 4789.920] (II) intel(1): Output HDMI2 disconnected
    [ 4789.920] (II) intel(1): Output HDMI3 disconnected
    [ 4789.920] (II) intel(1): Output VGA1 connected
    [ 4789.920] (II) intel(1): Output VIRTUAL1 disconnected
    [ 4789.920] (II) intel(1): Using user preference for initial modes
    [ 4789.920] (II) intel(1): Output VGA1 using initial mode 1280x1024
    [ 4789.920] (EE) intel(1): Cannot position output VGA1 relative to unknown output SAM
    [ 4789.920] (II) intel(1): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
    [ 4789.920] (==) intel(1): TearFree disabled
    [ 4789.920] (==) intel(1): DPI set to (96, 96)
    [ 4789.920] (II) Loading sub module "dri2"
    [ 4789.920] (II) LoadModule: "dri2"
    [ 4789.920] (II) Module "dri2" already built-in
    [ 4789.920] (II) Loading sub module "present"
    [ 4789.920] (II) LoadModule: "present"
    [ 4789.920] (II) Module "present" already built-in
    [ 4792.053] (EE) intel(G0): [drm] failed to set drm interface version: Permission denied [13].
    [ 4792.053] (II) intel(G0): [drm] Contents of '/sys/kernel/debug/dri/0/clients':
    [ 4792.053] (II) intel(G0): [drm] command pid dev master a uid magic
    [ 4792.053] (II) intel(G0): [drm] Xorg 10086 0 y y 0 0
    [ 4792.053] (II) intel(G0): [drm] Xorg 10086 0 n y 0 0
    [ 4792.053] (EE) intel(G0): Failed to claim DRM device.
    [ 4792.053] (II) UnloadModule: "intel"
    [ 4792.053] (--) Depth 24 pixmap format is 32 bpp
    [ 4792.053] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory
    [ 4792.053] (II) NVIDIA: access.
    [ 4792.057] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
    [ 4792.057] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
    [ 4792.057] (II) NVIDIA(0): configuration option may not be set correctly. When the
    [ 4792.057] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
    [ 4792.057] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
    [ 4792.057] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
    [ 4792.057] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
    [ 4792.057] (II) NVIDIA(0): Config Options in the README.
    [ 4792.091] (II) NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select,DFP-2:nvidia-auto-select{Rotation=90}"
    [ 4792.264] (==) NVIDIA(0): Disabling shared memory pixmaps
    [ 4792.264] (==) NVIDIA(0): Backing store enabled
    [ 4792.264] (==) NVIDIA(0): Silken mouse enabled
    [ 4792.264] (**) NVIDIA(0): DPMS enabled
    [ 4792.264] (II) Loading sub module "dri2"
    [ 4792.264] (II) LoadModule: "dri2"
    [ 4792.264] (II) Module "dri2" already built-in
    [ 4792.264] (II) NVIDIA(0): [DRI2] Setup complete
    [ 4792.264] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
    [ 4792.264] (--) RandR disabled
    [ 4792.264] (II) intel(1): SNA initialized with disabled backend
    [ 4792.264] (==) intel(1): Backing store enabled
    [ 4792.264] (==) intel(1): Silken mouse enabled
    [ 4792.264] (II) intel(1): HW Cursor enabled
    [ 4792.264] (II) intel(1): RandR 1.2 enabled, ignore the following RandR disabled message.
    [ 4792.264] (**) intel(1): DPMS enabled
    [ 4792.264] (==) intel(1): display hotplug detection enabled
    [ 4792.264] (II) intel(1): Textured video not supported on this hardware
    [ 4792.264] (WW) intel(1): loading DRI2 whilst the GPU is wedged.
    [ 4792.264] (II) intel(1): [DRI2] Setup complete
    [ 4792.264] (II) intel(1): [DRI2] DRI driver: i965
    [ 4792.264] (II) intel(1): [DRI2] VDPAU driver: i965
    [ 4792.264] (II) intel(1): direct rendering: DRI2 enabled
    [ 4792.265] (II) intel(1): hardware support for Present enabled
    [ 4792.265] (WW) intel(1): Option "Monitor-VGA-0" is not used
    [ 4792.265] (WW) intel(1): Option "LeftOf" is not used
    [ 4792.265] (WW) intel(1): Option "Rotate" is not used
    [ 4792.265] (--) RandR disabled
    [ 4792.268] (II) Initializing extension GLX
    [ 4792.268] (II) Indirect GLX disabled.(II) intel(1): switch to mode [email protected] on VGA1 using pipe 0, position (0, 0), rotation left, reflection none
    [ 4792.332] (II) intel(1): Setting screen physical size to 270 x 338
    [ 4792.386] (II) config/udev: Adding input device Power Button (/dev/input/event2)
    [ 4792.386] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 4792.386] (**) Power Button: Applying InputClass "libinput keyboard catchall"
    [ 4792.386] (**) Power Button: Applying InputClass "system-keyboard"
    [ 4792.386] (II) LoadModule: "libinput"
    [ 4792.386] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
    [ 4792.387] (II) Module libinput: vendor="X.Org Foundation"
    [ 4792.387] compiled for 1.17.1, module version = 0.7.0
    [ 4792.387] Module class: X.Org XInput Driver
    [ 4792.387] ABI class: X.Org XInput driver, version 21.0
    [ 4792.387] (II) Using input driver 'libinput' for 'Power Button'
    [ 4792.387] (**) Power Button: always reports core events
    [ 4792.387] (**) Option "Device" "/dev/input/event2"
    [ 4792.387] (II) input device 'Power Button', /dev/input/event2 is tagged by udev as: Keyboard
    [ 4792.387] (II) input device 'Power Button', /dev/input/event2 is a keyboard
    [ 4792.399] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event2"
    [ 4792.399] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    [ 4792.399] (**) Option "xkb_model" "pc104"
    [ 4792.399] (**) Option "xkb_layout" "us,ru"
    [ 4792.399] (**) Option "xkb_options" "caps:swapescape,grp:toggle"
    [ 4792.432] (II) input device 'Power Button', /dev/input/event2 is tagged by udev as: Keyboard
    [ 4792.432] (II) input device 'Power Button', /dev/input/event2 is a keyboard
    [ 4792.432] (II) config/udev: Adding input device Power Button (/dev/input/event1)
    [ 4792.432] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 4792.432] (**) Power Button: Applying InputClass "libinput keyboard catchall"
    [ 4792.432] (**) Power Button: Applying InputClass "system-keyboard"
    [ 4792.432] (II) Using input driver 'libinput' for 'Power Button'
    [ 4792.432] (**) Power Button: always reports core events
    [ 4792.432] (**) Option "Device" "/dev/input/event1"
    [ 4792.433] (II) input device 'Power Button', /dev/input/event1 is tagged by udev as: Keyboard
    [ 4792.433] (II) input device 'Power Button', /dev/input/event1 is a keyboard
    [ 4792.489] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1/event1"
    [ 4792.489] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
    [ 4792.489] (**) Option "xkb_model" "pc104"
    [ 4792.489] (**) Option "xkb_layout" "us,ru"
    [ 4792.489] (**) Option "xkb_options" "caps:swapescape,grp:toggle"
    [ 4792.490] (II) input device 'Power Button', /dev/input/event1 is tagged by udev as: Keyboard
    [ 4792.490] (II) input device 'Power Button', /dev/input/event1 is a keyboard
    [ 4792.490] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event0)
    [ 4792.490] (II) No input driver specified, ignoring this device.
    [ 4792.490] (II) This device may have been added with another device file.
    [ 4792.490] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event17)
    [ 4792.490] (II) No input driver specified, ignoring this device.
    [ 4792.490] (II) This device may have been added with another device file.
    [ 4792.490] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event18)
    [ 4792.490] (II) No input driver specified, ignoring this device.
    [ 4792.490] (II) This device may have been added with another device file.
    [ 4792.491] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event19)
    [ 4792.491] (II) No input driver specified, ignoring this device.
    [ 4792.491] (II) This device may have been added with another device file.
    [ 4792.491] (II) config/udev: Adding input device Microsoft Microsoft® 2.4GHz Transceiver v8.0 (/dev/input/event3)
    [ 4792.491] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "evdev keyboard catchall"
    [ 4792.491] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "libinput keyboard catchall"
    [ 4792.491] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "system-keyboard"
    [ 4792.491] (II) Using input driver 'libinput' for 'Microsoft Microsoft® 2.4GHz Transceiver v8.0'
    [ 4792.491] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: always reports core events
    [ 4792.491] (**) Option "Device" "/dev/input/event3"
    [ 4792.491] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event3 is tagged by udev as: Keyboard
    [ 4792.491] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event3 is a keyboard
    [ 4792.554] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/0003:045E:07B2.0004/input/input24/event3"
    [ 4792.554] (II) XINPUT: Adding extended input device "Microsoft Microsoft® 2.4GHz Transceiver v8.0" (type: KEYBOARD, id 8)
    [ 4792.554] (**) Option "xkb_model" "pc104"
    [ 4792.554] (**) Option "xkb_layout" "us,ru"
    [ 4792.554] (**) Option "xkb_options" "caps:swapescape,grp:toggle"
    [ 4792.554] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event3 is tagged by udev as: Keyboard
    [ 4792.554] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event3 is a keyboard
    [ 4792.555] (II) config/udev: Adding input device Microsoft Microsoft® 2.4GHz Transceiver v8.0 (/dev/input/event4)
    [ 4792.555] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "evdev pointer catchall"
    [ 4792.555] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "libinput pointer catchall"
    [ 4792.555] (II) Using input driver 'libinput' for 'Microsoft Microsoft® 2.4GHz Transceiver v8.0'
    [ 4792.555] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: always reports core events
    [ 4792.555] (**) Option "Device" "/dev/input/event4"
    [ 4792.555] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event4 is tagged by udev as: Mouse
    [ 4792.555] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event4 is a pointer caps
    [ 4792.609] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.1/0003:045E:07B2.0005/input/input25/event4"
    [ 4792.610] (II) XINPUT: Adding extended input device "Microsoft Microsoft® 2.4GHz Transceiver v8.0" (type: MOUSE, id 9)
    [ 4792.610] (**) Option "AccelerationScheme" "none"
    [ 4792.610] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: (accel) selected scheme none/0
    [ 4792.610] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: (accel) acceleration factor: 2.000
    [ 4792.610] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: (accel) acceleration threshold: 4
    [ 4792.610] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event4 is tagged by udev as: Mouse
    [ 4792.610] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event4 is a pointer caps
    [ 4792.610] (II) config/udev: Adding input device Microsoft Microsoft® 2.4GHz Transceiver v8.0 (/dev/input/mouse0)
    [ 4792.610] (II) No input driver specified, ignoring this device.
    [ 4792.610] (II) This device may have been added with another device file.
    [ 4792.611] (II) config/udev: Adding input device Microsoft Microsoft® 2.4GHz Transceiver v8.0 (/dev/input/event5)
    [ 4792.611] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "evdev keyboard catchall"
    [ 4792.611] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "joystick catchall"
    [ 4792.611] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "libinput keyboard catchall"
    [ 4792.611] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "system-keyboard"
    [ 4792.611] (II) Using input driver 'libinput' for 'Microsoft Microsoft® 2.4GHz Transceiver v8.0'
    [ 4792.611] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: always reports core events
    [ 4792.611] (**) Option "Device" "/dev/input/event5"
    [ 4792.611] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event5 is tagged by udev as: Keyboard Joystick
    [ 4792.611] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event5 is a keyboard
    [ 4792.676] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.2/0003:045E:07B2.0006/input/input26/event5"
    [ 4792.676] (II) XINPUT: Adding extended input device "Microsoft Microsoft® 2.4GHz Transceiver v8.0" (type: KEYBOARD, id 10)
    [ 4792.676] (**) Option "xkb_model" "pc104"
    [ 4792.676] (**) Option "xkb_layout" "us,ru"
    [ 4792.676] (**) Option "xkb_options" "caps:swapescape,grp:toggle"
    [ 4792.676] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event5 is tagged by udev as: Keyboard Joystick
    [ 4792.676] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event5 is a keyboard
    [ 4792.677] (II) config/udev: Adding input device Microsoft Microsoft® 2.4GHz Transceiver v8.0 (/dev/input/js0)
    [ 4792.677] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "system-keyboard"
    [ 4792.677] (II) No input driver specified, ignoring this device.
    [ 4792.677] (II) This device may have been added with another device file.
    [ 4792.677] (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event7)
    [ 4792.677] (II) No input driver specified, ignoring this device.
    [ 4792.677] (II) This device may have been added with another device file.
    [ 4792.677] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event8)
    [ 4792.677] (II) No input driver specified, ignoring this device.
    [ 4792.677] (II) This device may have been added with another device file.
    [ 4792.677] (II) config/udev: Adding input device HDA Intel PCH Line Out Front (/dev/input/event9)
    [ 4792.677] (II) No input driver specified, ignoring this device.
    [ 4792.677] (II) This device may have been added with another device file.
    [ 4792.678] (II) config/udev: Adding input device HDA Intel PCH Line Out Surround (/dev/input/event10)
    [ 4792.678] (II) No input driver specified, ignoring this device.
    [ 4792.678] (II) This device may have been added with another device file.
    [ 4792.678] (II) config/udev: Adding input device HDA Intel PCH Line Out CLFE (/dev/input/event11)
    [ 4792.678] (II) No input driver specified, ignoring this device.
    [ 4792.678] (II) This device may have been added with another device file.
    [ 4792.678] (II) config/udev: Adding input device HDA Intel PCH Line Out Side (/dev/input/event12)
    [ 4792.678] (II) No input driver specified, ignoring this device.
    [ 4792.678] (II) This device may have been added with another device file.
    [ 4792.678] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event13)
    [ 4792.678] (II) No input driver specified, ignoring this device.
    [ 4792.678] (II) This device may have been added with another device file.
    [ 4792.678] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=7 (/dev/input/event14)
    [ 4792.678] (II) No input driver specified, ignoring this device.
    [ 4792.678] (II) This device may have been added with another device file.
    [ 4792.679] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=8 (/dev/input/event15)
    [ 4792.679] (II) No input driver specified, ignoring this device.
    [ 4792.679] (II) This device may have been added with another device file.
    [ 4792.679] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event6)
    [ 4792.679] (II) No input driver specified, ignoring this device.
    [ 4792.679] (II) This device may have been added with another device file.
    [ 4792.679] (II) config/udev: Adding input device Eee PC WMI hotkeys (/dev/input/event16)
    [ 4792.679] (**) Eee PC WMI hotkeys: Applying InputClass "evdev keyboard catchall"
    [ 4792.679] (**) Eee PC WMI hotkeys: Applying InputClass "libinput keyboard catchall"
    [ 4792.679] (**) Eee PC WMI hotkeys: Applying InputClass "system-keyboard"
    [ 4792.679] (II) Using input driver 'libinput' for 'Eee PC WMI hotkeys'
    [ 4792.679] (**) Eee PC WMI hotkeys: always reports core events
    [ 4792.679] (**) Option "Device" "/dev/input/event16"
    [ 4792.679] (II) input device 'Eee PC WMI hotkeys', /dev/input/event16 is tagged by udev as: Keyboard
    [ 4792.679] (II) input device 'Eee PC WMI hotkeys', /dev/input/event16 is a keyboard
    [ 4792.712] (**) Option "config_info" "udev:/sys/devices/platform/eeepc-wmi/input/input19/event16"
    [ 4792.712] (II) XINPUT: Adding extended input device "Eee PC WMI hotkeys" (type: KEYBOARD, id 11)
    [ 4792.712] (**) Option "xkb_model" "pc104"
    [ 4792.713] (**) Option "xkb_layout" "us,ru"
    [ 4792.713] (**) Option "xkb_options" "caps:swapescape,grp:toggle"
    [ 4792.713] (II) input device 'Eee PC WMI hotkeys', /dev/input/event16 is tagged by udev as: Keyboard
    [ 4792.713] (II) input device 'Eee PC WMI hotkeys', /dev/input/event16 is a keyboard
    [ 4793.050] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 4793.050] (**) NVIDIA(0): device ViewSonic VG1930wm (DFP-2) (Using EDID frequencies
    [ 4793.050] (**) NVIDIA(0): has been enabled on all display devices.)
    [ 4793.081] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 4793.081] (**) NVIDIA(0): device Samsung SMS27A850 (DFP-0) (Using EDID frequencies
    [ 4793.081] (**) NVIDIA(0): has been enabled on all display devices.)
    [ 4793.081] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
    [ 4793.081] (WW) NVIDIA(GPU-0): mode "1920x1080" is specified in the EDID; however, the
    [ 4793.081] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
    [ 4793.081] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
    [ 4793.081] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1920x1080".
    [ 4793.081] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
    [ 4793.081] (WW) NVIDIA(GPU-0): mode "1280x720" is specified in the EDID; however, the
    [ 4793.081] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
    [ 4793.081] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
    [ 4793.081] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1280x720".
    [ 4793.081] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
    [ 4793.081] (WW) NVIDIA(GPU-0): mode "720x576" is specified in the EDID; however, the
    [ 4793.081] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
    [ 4793.081] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
    [ 4793.081] (WW) NVIDIA(GPU-0): VertRefresh check for mode "720x576".
    [ 4793.129] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 4793.129] (**) NVIDIA(0): device ViewSonic VG1930wm (DFP-2) (Using EDID frequencies
    [ 4793.129] (**) NVIDIA(0): has been enabled on all display devices.)
    [ 4793.160] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 4793.160] (**) NVIDIA(0): device Samsung SMS27A850 (DFP-0) (Using EDID frequencies
    [ 4793.160] (**) NVIDIA(0): has been enabled on all display devices.)
    [ 4793.160] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
    [ 4793.160] (WW) NVIDIA(GPU-0): mode "1920x1080" is specified in the EDID; however, the
    [ 4793.160] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
    [ 4793.160] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
    [ 4793.160] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1920x1080".
    [ 4793.160] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
    [ 4793.160] (WW) NVIDIA(GPU-0): mode "1280x720" is specified in the EDID; however, the
    [ 4793.160] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
    [ 4793.160] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
    [ 4793.160] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1280x720".
    [ 4793.160] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
    [ 4793.160] (WW) NVIDIA(GPU-0): mode "720x576" is specified in the EDID; however, the
    [ 4793.160] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
    [ 4793.160] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
    [ 4793.160] (WW) NVIDIA(GPU-0): VertRefresh check for mode "720x576".
    [ 4793.229] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 4793.229] (**) NVIDIA(0): device ViewSonic VG1930wm (DFP-2) (Using EDID frequencies
    [ 4793.229] (**) NVIDIA(0): has been enabled on all display devices.)
    [ 4793.259] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 4793.259] (**) NVIDIA(0): device Samsung SMS27A850 (DFP-0) (Using EDID frequencies
    [ 4793.259] (**) NVIDIA(0): has been enabled on all display devices.)
    [ 4793.259] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
    [ 4793.259] (WW) NVIDIA(GPU-0): mode "1920x1080" is specified in the EDID; however, the
    [ 4793.259] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
    [ 4793.259] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
    [ 4793.259] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1920x1080".
    [ 4793.259] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
    [ 4793.259] (WW) NVIDIA(GPU-0): mode "1280x720" is specified in the EDID; however, the
    [ 4793.259] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
    [ 4793.259] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
    [ 4793.259] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1280x720".
    [ 4793.259] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
    [ 4793.259] (WW) NVIDIA(GPU-0): mode "720x576" is specified in the EDID; however, the
    [ 4793.259] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
    [ 4793.259] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
    [ 4793.259] (WW) NVIDIA(GPU-0): VertRefresh check for mode "720x576".
    [ 4849.763] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 4849.763] (**) NVIDIA(0): device ViewSonic VG1930wm (DFP-2) (Using EDID frequencies
    [ 4849.763] (**) NVIDIA(0): has been enabled on all display devices.)
    [ 4849.794] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 4849.794] (**) NVIDIA(0): device Samsung SMS27A850 (DFP-0) (Using EDID frequencies
    [ 4849.794] (**) NVIDIA(0): has been enabled on all display devices.)
    [ 4849.794] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
    [ 4849.794] (WW) NVIDIA(GPU-0): mode "1920x1080" is specified in the EDID; however, the
    [ 4849.794] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
    [ 4849.794] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
    [ 4849.794] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1920x1080".
    [ 4849.795] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
    [ 4849.795] (WW) NVIDIA(GPU-0): mode "1280x720" is specified in the EDID; however, the
    [ 4849.795] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
    [ 4849.795] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
    [ 4849.795] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1280x720".
    [ 4849.795] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
    [ 4849.795] (WW) NVIDIA(GPU-0): mode "720x576" is specified in the EDID; however, the
    [ 4849.795] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
    [ 4849.795] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
    [ 4849.795] (WW) NVIDIA(GPU-0): VertRefresh check for mode "720x576".
    I also tried other configs, but neither of them made me happy:
    Section "DRI"
    Mode 0666
    EndSection
    Section "Monitor"
    Identifier "SAM"
    ModelName "Samsung SMS27A850"
    HorizSync 30.0 - 90.0
    VertRefresh 56.0 - 75.0
    Option "DPMS"
    DisplaySize 597 336 # In millimeters
    EndSection
    Section "Monitor"
    Identifier "VS"
    ModelName "ViewSonic VG1930wm"
    Option "DPMS"
    Option "RightOf" "SAM"
    Option "Rotate" "left"
    EndSection
    Section "Monitor"
    Identifier "BNQ"
    ModelName "BenQ FP737s"
    Option "DPMS"
    Option "LeftOf" "SAM"
    Option "Rotate" "left"
    EndSection
    Section "Device"
    Identifier "nvidia-sam"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce GTX 560 Ti"
    BusID "01:00:0"
    Option "Monitor-DVI-I-1" "SAM"
    Screen 0
    EndSection
    Section "Device"
    Identifier "nvidia-vs"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce GTX 560 Ti"
    BusID "01:00:0"
    Option "Monitor-DVI-I-2" "VS"
    Screen 1
    EndSection
    Section "Device"
    Identifier "intel"
    Driver "modesetting"
    Option "AccelMethod" "none"
    VendorName "Intel"
    BoardName "Intel Integrated Graphic Controller"
    BusID "00:02:0"
    Option "Monitor-VGA-0" "BNQ"
    Screen 2
    EndSection
    Section "Screen"
    Identifier "SAM-Screen"
    Device "nvidia-sam"
    Monitor "SAM"
    #DefaultDepth 24
    # Option "Stereo" "0"
    # Option "SLI" "Off"
    # Option "MultiGPU" "Off"
    # Option "BaseMosaic" "off"
    #Option "AllowEmptyInitialConfiguration"
    # SubSection "Display"
    # Depth 24
    # EndSubSection
    EndSection
    Section "Screen"
    Identifier "VS-Screen"
    Device "nvidia-vs"
    Monitor "VS"
    #DefaultDepth 24
    # Option "Stereo" "0"
    # Option "SLI" "Off"
    # Option "MultiGPU" "Off"
    # Option "BaseMosaic" "off"
    #Option "AllowEmptyInitialConfiguration"
    # SubSection "Display"
    # Depth 24
    # EndSubSection
    EndSection
    Section "Screen"
    Identifier "BNQ-Screen"
    Device "intel"
    Monitor "BNQ"
    EndSection
    Section "ServerLayout"
    Identifier "Layout0"
    Screen 0 "SAM-Screen"
    Screen 1 "VS-Screen" RightOf "SAM-Screen"
    Screen 2 "BNQ-Screen" LeftOf "SAM-Screen"
    Option "Xinerama" "0"
    EndSection
    [ 4488.527]
    X.Org X Server 1.17.1
    Release Date: 2015-02-10
    [ 4488.527] X Protocol Version 11, Revision 0
    [ 4488.527] Build Operating System: Linux 3.18.6-1-ARCH x86_64
    [ 4488.527] Current Operating System: Linux earth 3.18.6-1-ARCH #1 SMP PREEMPT Sat Feb 7 08:44:05 CET 2015 x86_64
    [ 4488.527] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=dc49b07c-e67c-4b6f-91f7-7c1adc050e21 rw quiet ipv6.disable=1 init=/usr/lib/systemd/systemd security=tomoyo TOMOYO_trigger=/usr/lib/systemd/systemd
    [ 4488.527] Build Date: 22 February 2015 12:50:32PM
    [ 4488.527]
    [ 4488.527] Current version of pixman: 0.32.6
    [ 4488.527] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 4488.527] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 4488.527] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Mar 1 14:38:54 2015
    [ 4488.527] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 4488.527] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
    [ 4488.528] (==) ServerLayout "Layout0"
    [ 4488.528] (**) |-->Screen "SAM-Screen" (0)
    [ 4488.528] (**) | |-->Monitor "SAM"
    [ 4488.528] (**) | |-->Device "nvidia-sam"
    [ 4488.528] (**) |-->Screen "VS-Screen" (1)
    [ 4488.528] (**) | |-->Monitor "VS"
    [ 4488.528] (**) | |-->Device "nvidia-vs"
    [ 4488.528] (**) |-->Screen "BNQ-Screen" (2)
    [ 4488.528] (**) | |-->Monitor "BNQ"
    [ 4488.528] (**) | |-->Device "intel"
    [ 4488.528] (**) Option "Xinerama" "0"
    [ 4488.528] (==) Automatically adding devices
    [ 4488.528] (==) Automatically enabling devices
    [ 4488.528] (==) Automatically adding GPU devices
    [ 4488.528] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/OTF/,
    /usr/share/fonts/Type1/,
    /usr/share/fonts/100dpi/,
    /usr/share/fonts/75dpi/
    [ 4488.528] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 4488.528] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 4488.528] (II) Loader magic: 0x815d80
    [ 4488.528] (II) Module ABI versions:
    [ 4488.528] X.Org ANSI C Emulation: 0.4
    [ 4488.528] X.Org Video Driver: 19.0
    [ 4488.528] X.Org XInput driver : 21.0
    [ 4488.528] X.Org Server Extension : 9.0
    [ 4488.529] (EE) systemd-logind: failed to get session: PID 32224 does not belong to any known session
    [ 4488.530] (II) xfree86: Adding drm device (/dev/dri/card1)
    [ 4488.530] (II) xfree86: Adding drm device (/dev/dri/card0)
    [ 4488.531] (--) PCI: (0:0:2:0) 8086:0102:1043:84ca rev 9, Mem @ 0xf6400000/4194304, 0xd0000000/268435456, I/O @ 0x0000f000/64
    [ 4488.531] (--) PCI:*(0:1:0:0) 10de:1200:10b0:0401 rev 161, Mem @ 0xf4000000/33554432, 0xe0000000/134217728, 0xe8000000/67108864, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
    [ 4488.531] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    [ 4488.531] (II) LoadModule: "glx"
    [ 4488.531] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 4488.542] (II) Module glx: vendor="NVIDIA Corporation"
    [ 4488.542] compiled for 4.0.2, module version = 1.0.0
    [ 4488.542] Module class: X.Org Server Extension
    [ 4488.542] (II) NVIDIA GLX Module 346.47 Thu Feb 19 18:09:07 PST 2015
    [ 4488.542] (II) LoadModule: "nvidia"
    [ 4488.542] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
    [ 4488.543] (II) Module nvidia: vendor="NVIDIA Corporation"
    [ 4488.543] compiled for 4.0.2, module version = 1.0.0
    [ 4488.543] Module class: X.Org Video Driver
    [ 4488.543] (II) LoadModule: "modesetting"
    [ 4488.543] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
    [ 4488.543] (II) Module modesetting: vendor="X.Org Foundation"
    [ 4488.543] compiled for 1.17.1, module version = 1.17.1
    [ 4488.543] Module class: X.Org Video Driver
    [ 4488.543] ABI class: X.Org Video Driver, version 19.0
    [ 4488.543] (II) NVIDIA dlloader X Driver 346.47 Thu Feb 19 17:47:18 PST 2015
    [ 4488.543] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
    [ 4488.543] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
    [ 4488.543] (++) using VT number 7
    [ 4488.645] (II) Loading sub module "fb"
    [ 4488.645] (II) LoadModule: "fb"
    [ 4488.645] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 4488.645] (II) Module fb: vendor="X.Org Foundation"
    [ 4488.646] compiled for 1.17.1, module version = 1.0.0
    [ 4488.646] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 4488.646] (II) Loading sub module "wfb"
    [ 4488.646] (II) LoadModule: "wfb"
    [ 4488.646] (II) Loading /usr/lib/xorg/modules/libwfb.so
    [ 4488.646] (II) Module wfb: vendor="X.Org Foundation"
    [ 4488.646] compiled for 1.17.1, module version = 1.0.0
    [ 4488.646] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 4488.646] (II) Loading sub module "ramdac"
    [ 4488.646] (II) LoadModule: "ramdac"
    [ 4488.646] (II) Module "ramdac" already built-in
    [ 4488.647] (II) modeset(2): using drv /dev/dri/card0
    [ 4488.647] (II) modeset(G0): using drv /dev/dri/card0
    [ 4488.647] (EE) Screen 2 deleted because of no matching config section.
    [ 4488.647] (II) UnloadModule: "modesetting"
    [ 4488.647] (II) NVIDIA(0): Creating default Display subsection in Screen section
    "SAM-Screen" for depth/fbbpp 24/32
    [ 4488.647] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
    [ 4488.647] (==) NVIDIA(0): RGB weight 888
    [ 4488.647] (==) NVIDIA(0): Default visual is TrueColor
    [ 4488.647] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
    [ 4488.648] (II) NVIDIA(1): Creating default Display subsection in Screen section
    "VS-Screen" for depth/fbbpp 24/32
    [ 4488.648] (**) NVIDIA(0): Enabling 2D acceleration
    [ 4489.049] (II) NVIDIA(GPU-0): Found DRM driver nvidia-drm (20150116)
    [ 4489.050] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 560 Ti (GF114) at PCI:1:0:0 (GPU-0)
    [ 4489.050] (--) NVIDIA(0): Memory: 1048576 kBytes
    [ 4489.050] (--) NVIDIA(0): VideoBIOS: 70.24.21.00.00
    [ 4489.050] (II) NVIDIA(0): Detected PCI Express Link width: 16X
    [ 4489.082] (--) NVIDIA(0): Valid display device(s) on GeForce GTX 560 Ti at PCI:1:0:0
    [ 4489.082] (--) NVIDIA(0): CRT-0
    [ 4489.082] (--) NVIDIA(0): CRT-1
    [ 4489.082] (--) NVIDIA(0): Samsung SMS27A850 (DFP-0) (boot, connected)
    [ 4489.082] (--) NVIDIA(0): DFP-1
    [ 4489.082] (--) NVIDIA(0): ViewSonic VG1930wm (DFP-2) (connected)
    [ 4489.082] (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
    [ 4489.082] (--) NVIDIA(GPU-0): CRT-1: 400.0 MHz maximum pixel clock
    [ 4489.082] (--) NVIDIA(0): Samsung SMS27A850 (DFP-0): Internal TMDS
    [ 4489.082] (--) NVIDIA(GPU-0): Samsung SMS27A850 (DFP-0): 330.0 MHz maximum pixel clock
    [ 4489.082] (--) NVIDIA(0): DFP-1: Internal TMDS
    [ 4489.082] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
    [ 4489.082] (--) NVIDIA(0): ViewSonic VG1930wm (DFP-2): Internal TMDS
    [ 4489.082] (--) NVIDIA(GPU-0): ViewSonic VG1930wm (DFP-2): 330.0 MHz maximum pixel clock
    [ 4489.083] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 4489.083] (**) NVIDIA(0): device Samsung SMS27A850 (DFP-0) (Using EDID frequencies
    [ 4489.083] (**) NVIDIA(0): has been enabled on all display devices.)
    [ 4489.083] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
    [ 4489.083] (WW) NVIDIA(GPU-0): mode "1920x1080" is specified in the EDID; however, the
    [ 4489.083] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
    [ 4489.083] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
    [ 4489.083] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1920x1080".
    [ 4489.083] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
    [ 4489.083] (WW) NVIDIA(GPU-0): mode "1280x720" is specified in the EDID; however, the
    [ 4489.083] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
    [ 4489.083] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
    [ 4489.083] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1280x720".
    [ 4489.083] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
    [ 4489.083] (WW) NVIDIA(GPU-0): mode "720x576" is specified in the EDID; however, the
    [ 4489.083] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
    [ 4489.083] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
    [ 4489.083] (WW) NVIDIA(GPU-0): VertRefresh check for mode "720x576".
    [ 4489.084] (==) NVIDIA(0):
    [ 4489.084] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
    [ 4489.084] (==) NVIDIA(0): will be used as the requested mode.
    [ 4489.084] (==) NVIDIA(0):
    [ 4489.084] (II) NVIDIA(0): Validated MetaModes:
    [ 4489.084] (II) NVIDIA(0): "DFP-0:nvidia-auto-select"
    [ 4489.084] (II) NVIDIA(0): Virtual screen size determined to be 2560 x 1440
    [ 4489.113] (--) NVIDIA(0): DPI set to (125, 114); computed from "UseEdidDpi" X config
    [ 4489.113] (--) NVIDIA(0): option
    [ 4489.114] (==) NVIDIA(1): Depth 24, (==) framebuffer bpp 32
    [ 4489.114] (==) NVIDIA(1): RGB weight 888
    [ 4489.114] (==) NVIDIA(1): Default visual is TrueColor
    [ 4489.114] (==) NVIDIA(1): Using gamma correction (1.0, 1.0, 1.0)
    [ 4489.114] (II) NVIDIA(1): NVIDIA GPU GeForce GTX 560 Ti (GF114) at PCI:1:0:0 (GPU-0)
    [ 4489.114] (--) NVIDIA(1): Memory: 1048576 kBytes
    [ 4489.114] (--) NVIDIA(1): VideoBIOS: 70.24.21.00.00
    [ 4489.114] (II) NVIDIA(1): Detected PCI Express Link width: 16X
    [ 4489.146] (--) NVIDIA(1): Valid display device(s) on GeForce GTX 560 Ti at PCI:1:0:0
    [ 4489.146] (--) NVIDIA(1): CRT-0
    [ 4489.146] (--) NVIDIA(1): CRT-1
    [ 4489.146] (--) NVIDIA(1): Samsung SMS27A850 (DFP-0) (boot, connected)
    [ 4489.146] (--) NVIDIA(1): DFP-1
    [ 4489.146] (--) NVIDIA(1): ViewSonic VG1930wm (DFP-2) (connected)
    [ 4489.146] (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
    [ 4489.146] (--) NVIDIA(GPU-0): CRT-1: 400.0 MHz maximum pixel clock
    [ 4489.146] (--) NVIDIA(1): Samsung SMS27A850 (DFP-0): Internal TMDS
    [ 4489.146] (--) NVIDIA(GPU-0): Samsung SMS27A850 (DFP-0): 330.0 MHz maximum pixel clock
    [ 4489.146] (--) NVIDIA(1): DFP-1: Internal TMDS
    [ 4489.146] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
    [ 4489.146] (--) NVIDIA(1): ViewSonic VG1930wm (DFP-2): Internal TMDS
    [ 4489.146] (--) NVIDIA(GPU-0): ViewSonic VG1930wm (DFP-2): 330.0 MHz maximum pixel clock
    [ 4489.146] (**) NVIDIA(1): Option "Rotate" "left"
    [ 4489.146] (**) NVIDIA(1): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 4489.146] (**) NVIDIA(1): device ViewSonic VG1930wm (DFP-2) (Using EDID frequencies
    [ 4489.146] (**) NVIDIA(1): has been enabled on all display devices.)
    [ 4489.147] (==) NVIDIA(1):
    [ 4489.147] (==) NVIDIA(1): No modes were requested; the default mode "nvidia-auto-select"
    [ 4489.147] (==) NVIDIA(1): will be used as the requested mode.
    [ 4489.147] (==) NVIDIA(1):
    [ 4489.147] (II) NVIDIA(1): Validated MetaModes:
    [ 4489.147] (II) NVIDIA(1): "DFP-2:nvidia-auto-select{Rotation=90}"
    [ 4489.147] (II) NVIDIA(1): Virtual screen size determined to be 900 x 1440
    [ 4489.150] (--) NVIDIA(1): DPI set to (55, 140); computed from "UseEdidDpi" X config
    [ 4489.150] (--) NVIDIA(1): option
    [ 4489.150] (EE)
    [ 4489.150] (EE) Backtrace:
    [ 4489.151] (EE) 0: /usr/lib/xorg-server/Xorg (OsLookupColor+0x119) [0x5949c9]
    [ 4489.151] (EE) 1: /usr/lib/libc.so.6 (__restore_rt+0x0) [0x7f64dd88653f]
    [ 4489.151] (EE) 2: /usr/lib/xorg-server/Xorg (xf86nameCompare+0x19) [0x4a9159]
    [ 4489.151] (EE) 3: /usr/lib/xorg-server/Xorg (xf86findOption+0x2c) [0x4a2c6c]
    [ 4489.151] (EE) 4: /usr/lib/xorg-server/Xorg (xf86SetDepthBpp+0x430) [0x4828d0]
    [ 4489.151] (EE) 5: /usr/lib/xorg/modules/drivers/modesetting_drv.so (_init+0x25e1) [0x7f64d695aab1]
    [ 4489.151] (EE) 6: /usr/lib/xorg-server/Xorg (InitOutput+0xbcc) [0x47b63c]
    [ 4489.151] (EE) 7: /usr/lib/xorg-server/Xorg (remove_fs_handlers+0x22a) [0x43c9da]
    [ 4489.152] (EE) 8: /usr/lib/libc.so.6 (__libc_start_main+0xf0) [0x7f64dd873800]
    [ 4489.152] (EE) 9: /usr/lib/xorg-server/Xorg (_start+0x29) [0x427039]
    [ 4489.152] (EE) 10: ? (?+0x29) [0x29]
    [ 4489.152] (EE)
    [ 4489.152] (EE) Segmentation fault at address 0x231
    [ 4489.152] (EE)
    Fatal server error:
    [ 4489.152] (EE) Caught signal 11 (Segmentation fault). Server aborting
    [ 4489.152] (EE)
    [ 4489.152] (EE)
    Please consult the The X.Org Foundation support
    at http://wiki.x.org
    for help.
    [ 4489.152] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
    [ 4489.152] (EE)
    [ 4489.295] (EE) Server terminated with error (1). Closing log file.
    Section "DRI"
    Mode 0666
    EndSection
    Section "Monitor"
    Identifier "SAM"
    ModelName "Samsung SMS27A850"
    HorizSync 30.0 - 90.0
    VertRefresh 56.0 - 75.0
    Option "DPMS"
    DisplaySize 597 336 # In millimeters
    EndSection
    Section "Monitor"
    Identifier "VS"
    ModelName "ViewSonic VG1930wm"
    Option "DPMS"
    Option "RightOf" "SAM"
    Option "Rotate" "left"
    EndSection
    Section "Monitor"
    Identifier "BNQ"
    ModelName "BenQ FP737s"
    Option "DPMS"
    Option "LeftOf" "SAM"
    Option "Rotate" "left"
    EndSection
    Section "Device"
    Identifier "nvidia-sam"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce GTX 560 Ti"
    BusID "01:00:0"
    Option "Monitor-DVI-I-1" "SAM"
    Screen 0
    EndSection
    Section "Device"
    Identifier "nvidia-vs"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce GTX 560 Ti"
    BusID "01:00:0"
    Option "Monitor-DVI-I-2" "VS"
    Screen 1
    EndSection
    Section "Device"
    Identifier "intel"
    Driver "intel"
    Option "AccelMethod" "none"
    VendorName "Intel"
    BoardName "Intel Integrated Graphic Controller"
    BusID "00:02:0"
    Option "Monitor-VGA-0" "BNQ"
    Screen 2
    EndSection
    Section "Screen"
    Identifier "SAM-Screen"
    Device "nvidia-sam"
    Monitor "SAM"
    #DefaultDepth 24
    # Option "Stereo" "0"
    # Option "SLI" "Off"
    # Option "MultiGPU" "Off"
    # Option "BaseMosaic" "off"
    #Option "AllowEmptyInitialConfiguration"
    # SubSection "Display"
    # Depth 24
    # EndSubSection
    EndSection
    Section "Screen"
    Identifier "VS-Screen"
    Device "nvidia-vs"
    Monitor "VS"
    #DefaultDepth 24
    # Option "Stereo" "0"
    # Option "SLI" "Off"
    # Option "MultiGPU" "Off"
    # Option "BaseMosaic" "off"
    #Option "AllowEmptyInitialConfiguration"
    # SubSection "Display"
    # Depth 24
    # EndSubSection
    EndSection
    Section "Screen"
    Identifier "BNQ-Screen"
    Device "intel"
    Monitor "BNQ"
    EndSection
    Section

    Hi:
    There is a specific order you need to install the graphics drivers for the notebooks with the nvidia/intel graphics.
    1. Install the Intel chipset installation utility and reboot.  If the one on your notebook's support page doesn't work, use this one.
    https://downloadcenter.intel.com/Detail_Desc.aspx?​DwnldID=20775&lang=eng&ProdId=816
    2. Install the Intel HD graphics driver and reboot.  If the one on your notebook's suport page doesn't work, try this one.
    https://downloadcenter.intel.com/Detail_Desc.aspx?​DwnldID=24348
    3. Install the nVidia HD graphics driver and reboot.  If the one on your notebook's support page doesn't work, try this one.
    http://www.nvidia.com/download/driverResults.aspx/​81879/en-us

  • P67A-GD55 Rev B3, When a new bios including Intel Raid Oprtion Rom 10.6.0.1091

    P67A-GD55 Rev B3, When a new bios including Intel Raid Oprtion Rom 10.6.0.1091 ?
    Hello,
    I am the owner of a MSI motherboard P67A-GD55 (Rev B3).
    The operating system Windows 7 Pro 64 bit is installed on a disk in AHCI OCZ Vertex 3120 Go SATA0 mounted on the port (version 3).
     I get many bugs and blue screens.
    This would be resolved with the latest driver Intel Rapid Storage Technology 10.6.0.1022.
     It must been associated with a bios with the Intel RAID Option ROM 10.6.0.1091.
     The latest bios for my motherboard is 1.E (or 1.14) version which includes Intel RAID Option ROM 10.5.0.1034.
     Are there plans to release a new bios with the new ROM?
    If not, is there a way to include the last Intel Option Rom in the bios 1.E?
    Thank you in advance for your reply.
    SM

    Quote
    I get many bugs and blue screens.
    This would be resolved with the latest driver Intel Rapid Storage Technology 10.6.0.1022.
     It must been associated with a bios with the Intel RAID Option ROM 10.6.0.1091.
    What bugs and blue screens?
    If this was a major issue as such, then everyone would be complaining about this.
    >>Posting Guide<<

  • BIOS option to "permanently disable" Computrace

    Hi,
    In the T500 BIOS Setup is the option:
    Security:Computrace: Computrace Module Activation
    with 3 possible values:
    Enabled (default?)
    Disabled
    Permanently Disabled
    I think I understand how Computrace BIOS works: on boot the BIOS checks and makes sure the necessary drivers/services are present in the OS filesystem before the supported OS boots. The Computrace service then runs "hidden" in the OS and periodically phones home.
    What I'd like to know is what happens if I select the BIOS option "Permanently Disabled". Is the Computrace checker/loader deleted from the BIOS? Is it possible to ever turn Computrace back on at a later date, perhaps by flashing the BIOS?
    Thanks,
    Frank
    Results of Your Ideal Business-Class Laptop survey, concluded 2009-07-29.
    Did someone help you?
    Say thanks! with a kudo.
    Even better: Pay it forward, help someone else.
    Solved!
    Go to Solution.

    This field lets you Activate or Disable the BIOS module interface of the optional Computrace(R) Service from Absolute(R) Software. The Computrace agent from Absolute Software is a service solution designed to help track assets and provide recovery services in the event the notebook is lost or stolen. The Computrace agent communicates with the Absolute Software Monitoring Server at programmed intervals to provide the tracking service. By activating the service, you consent to the transmission of information from and to your computer and the Absolute Software Monitoring Server. The Computrace service is purchased as a separate option and the monitoring Server will enable its agent security module through an interface provided by the BIOS. The Computrace tracking agent can only be used in the US, UK, Canada, and Australia. Computrace(R) and Absolute(R) are registered trademarks of Absolute Software Corporation.
    Disable = Permanently block the Computrace module interface.
    Deactivate = Block the Computrace module interface (default).
    Activate = Permit the Computrace module interface.
    The Absolute Anti-Theft solution is presently Deactivated. Note that the Activate or Disable options will permanently Activate or Disable the feature and no further changes will be allowed.
    Also, if people are wondering about the service - for home users you can get info here: http://www.lojackforlaptops.com/learnmore.asp
    For all of the software solutions - the info is here: http://www.absolute.com/
    do you have renter's or home owners insurance? if so, it isn't worth it.
    second, it only works if someone is going to use it on the internet.
    third, you should read the terms for recovery http://www.absolute.com/PDF/EULA.pdf
    which means that even if they recover the lappie, they do not cover the fact that it may be damaged or data lost. you must also always have it automatically loaded to connect regularily...if you are travelling and using dial up that may mean extra phone expenses. once lappie is located, the cops have to get the lappie...if it is outside recovery territory, your loss. it is recovery and not insurance in case of theft. and the nice catcher that if you didn't take precautions to safeguard against the theft, then it doesn't guarantee the recovery nor pay the $1000 if they cannot recover it (para 8.9). another important note, is that $1000 is max, and decreases annually (para 9).
    prices are:
    LoJack for Laptops - 4 year term US$119.99
    LoJack for Laptops - 3 year term US$99.99
    LoJack for Laptops - 2 year term US$79.99
    LoJack for Laptops - 1 year term US$49.99
    if you have insurance, i think it is absurd to buy these things. it is like buying lojack for a car, rather useless.
    ThinkPad T400: Intel® C2D P8400 | ATI® Radeon HD 3470 (ATI Switchable Graphics) | 4GB RAM DDR3 | 250GB 5400RPM | CD-RW | ThinkPad 11b/g | 14.1" WXGA+ LED | 4-Cell Battery | Windows 7
    NOD32 2.7 Anti-Virus | Office 2007 | Professional Pianist (20 years)

  • Portege R835-P56X web cam application stuck on screen

    So hi peeps, Ive had my Portege for almost 3 years, and this problem just started in the last month or so. The application menu that is hidden off screen and slides out when you put your mouse there is stuck on screen, will not go away, and remains on top when other programs are running. Its extremely annoying! There's no error message or anything. Has anyone else encountered this problem? And if so, how do you fix it?
    TIA!!
    Attachments:
    webcamapp.png ‏441 KB
    webcamapp2.png ‏91 KB

    Portege R835-P56X
    Downoads here.
    I would uninstall and reinstall the application.
       Toshiba Web Camera Application
    -Jerry

  • I have a iMac 21,5" Intel mid 2011 and I need to know if is possible I change the original 500Gb HD for a 512Gb SSD? If yes, where I find a tutorial about this? Thanks a lot and best regards all.

    Hi people,
    I'm typing from Brasil, sorry my English.
    I have a iMac 21,5" Intel mid 2011 and I need to know if is possible I change the original 500Gb HD for a 512Gb SSD?
    I intend to keep the original DVD driver and install the SSD in the same HD place.
    If yes, where I find a tutorial about this?
    And I will like to know if the 512GB Solid-State Drive Kit for Mac Pro is compatible with iMac.
    http://store.apple.com/us/product/MC731ZM/A/512gb-solid-state-drive-kit-for-mac- pro?fnode=5f
    What brand and model of SSD do you recommend?
    Thanks a lot for now and best regards all.
    Carlos Sgrillo
    Porto Alegre, RS, Brasil

    Tukaine
    Sep 23, 2012 10:59 PM
    Since the late 2009 iMacs came out, replacing the hard drive has caused the internal Hard Drive Fan to start running at around 6000RPM.
    This is due to Apple replacing the external Hard Drive temperature sensor with a proprietary firmware and using the drives internal sensor.
    Replacement drives do not contain the firmware to deliver temperature data on the temperature sensor cable.
    When the iMac does not receive a good signal from the hard drive it puts the fan at full speed to protect the drive.
    If you replace your drive, your iMac will initially seem fine, but soon the fan will begin to speed up to full speed. Resetting the SMC (System Management Controller) will have a temporary effect, but again the fan will speed up.
    Fixes people have used in the past included:
    Using smcFanControl and the terminal to set a MAX speed for the fan and writing scripts to start this after every sleep/restart.
    Shorting the temperature sensor cable (Not a possibility on 2011 iMacs) this tricks the iMac into thinking the drives temperature is very low, hence slow fan speed.
    Both these fixes are less then perfect and leave the drive in a dangerous situation with no protection from overheating.
    Another option people try is other Fan Control software. These programs will not work for this particular issue as they often only control the base speed, and if they do control the fans actual speed they rely on the temperature reported by the sensor which is now incorrect.
    HDD Fan Control
    HDD Fan Control works to fix this issue by reading the drives internal temperature using the S.M.A.R.T protocol and set the fans actual speed to a value good to protect the drive.
    It runs at startup and continually to always control the fan correctly, prevent the loud fan noise and protect the drive from overheating
    Instead of HDDFan Control, get the free SSDFan Control
    http://exirion.net/ssdfanctrl/

  • HP Pavilion dv7-4083cl (w/ Intel Core i5 and ATI GPU): Which is its normal temperature?

    Hello,
    I have a question about HP Pavilion dv7-4083cl (w/ Intel Core i5 and ATI GPU):
    Which is its normal temperature?
    Environment: 24 °C (Celcius)
    HWMonitor and Real Temp agrees with the numbers find below.
    The two CPU Cores starts at 37 °C and in about an hour are at 53 °C, with CPU usage under 10%.
    The GPU starts at 34 °C and easly goes to 57 °C, with some peaks at 72 °C
    Regarding "Hewlett-Packard 144B": (under low/idle CPU usage)
    TZ01: starts at 40 °C and very fast goes to 55 °C or 65 °C (and more, under CPU load)
    PCH starts at 59 °C and very fast goes to 76 °C (and stays there)
    GMCH: starts at 40 °C and very fast goes to 55 °C or 65 °C
    ATI Mobility Radeon HD 5470 (TMPIN0): Starts at 34 °C and easily goes and stays at 57-58 °C
    Note: I'm also using a cooler (two fans, under its base)
    If I run Real Temp (v. 3.6) "Sensor Test", the cores goes up to 100 °C , and even a bit more.
    Which is the normal / expected behavior / operational range?
    Steady PCH at 76 °C is it normal?
    TZ01, GMCH at 55 - 65 °C is it normal?
    i5 Cores at 55 °C is it normal? (and easily going to 70 °C or more)
    GPU (ATI) at 57 °C is it normal?
    is it normal to climb up to 100-105 °C under a 5 minutes high CPU usage operation?
    Thanks!

    i roll back to bios F.25 which is the older version of bios that support my device but still suffering from same D90 system overheating error.
    i can't contact hp support or send it to offical hp center currently coz i am from Egypt and i live in far town

  • Re: i got this code from my hp wen i enter my bios options i forgot my password ( CNU9490YWX​)

    I ENTERED MY BIOS OPTION BECAUSE I CANT INSTALL WINDOWS ON DISK, IT STATES THAT WINDOWS CANT INSTALL ON THIS DISK SO I WENT ON YOU TUBE AND RESEARCHED SOME VIDEOS WHICH NEEDS ME TO GO IN MY BIOS MENU TO DISABLE SOME STUFF. PLZ HELP
    This question was solved.
    View Solution.

    You're happy and that makes us happy!  
    ****Please click on Accept As Solution if a suggestion solves your problem. It helps others facing the same problem to find a solution easily****
    2015 Microsoft MVP - Windows Experience Consumer

  • Whats the use of these Bios Option

    after Flashing the bios of my x58-pro To 8.50 I saw there is some new option in the bios that you can say there is practically no guidance in the manual on what they do.
    i'm interested specially in 3 of them which i believe have something with power saving ,I wonder if somebody can tell me what they exactly do.
    C State Package limit setting     (which have the option of Auto,C1,C3,.....,C7)
    C1 Auto Demotion                    ( Disable,Enable)
    C3 Auto Demotion                    ( Disable,Enable)
    thanks

    Quote from: Jack t.N. on 23-August-09, 17:12:12
    Actually, there is not that much to explain here.  C-States are IDLE- or HALT States that the processor can enter to save power (when it has nothing to do).  C3, C6 & C7 are more enhanced power-saving HALT States than C1. When the system enters a certain HALT State, CPU Core Frequency and voltage are usually reduced to save power.
    The first option allows you to specify or limit the "deepness" of the HALT State.  If you don't want it to enter the C7 HALT State, choose the next lower state as the limit.  The second and third option are actually rather self-explanatory.
    thanks so if i want the best powersaving in first option i use c7 and then at 2nd and 3rd option i use disable

  • Is there a way to update a Mac OS X v10.4.11 with processor of 2GHz Intel Core 2Duo and memory of 1GB 667 MHz DDR2 SDRAM into v10.9.4?Thanks

    Is there a way to update a Mac OS X v10.4.11 with processor of 2GHz Intel Core 2Duo and memory of 1GB 667 MHz DDR2 SDRAM into v10.9.4?Thanks

    You do realise that you can add Ram, if that is all that is holding you back it's not a problem.
    Tell me the exact model and age of your Mac. (The model identifier can be found by holding the option key down and clicking on the Apple Menu, select System Information (top entry) and then read the model identifier from the righthand panel (2nd entry down)

Maybe you are looking for