Automatic Phase Switching on 890gxm-g65

MSI 890gxm-g65
AMD phenom II X6 1055T 2.8ghz
2x 2gb Kingston ddr3 1333mhz (total 4gb)
FSP Epsilon 600w 80plus quad 12+v rail
Palit Sonic OC GTX460 1gb gddr5 256bit
Cooler Master Elite 335
500 caviar blue wd 16mb cache 7200rpm
2tb caviar green wd 64mb cache 7200rpm
Win 7 Home Premium 64bit
Bios rev 1.6
there are 4 aps leds above the CPU. They are always lit no matter what. And bios defaults to disabling the APS feature. And per mobo manual, ther are only two phases, 1 led lit for power saving and 4 lit for full load.
Bios defaults are disabled for the APS, enabled for cool and quiet.
Will i see any difference if i enable it? Should i enable it? Or just leave it disabled.

HI,
maybe you are having this problem because the feature is not working in BIOS. After updating the BIOS on my 790fx-gd70 I also noticed that APS didn't work any longer. I contacted support but haven't heard from them yet.
You can however turn Phase Switching on after boot-up using "Green Power Center" in Windows.

Similar Messages

  • 890GXM-G65 will it boot?

    just had a question for the people that own the 890GXM-G65 will it boot into bios with an unsupported cpu 1055t for bios flashing?
    already ordered everything and dont want to have to spend money on another cpu even if it would only cost $40
    MSI 890GXM-G65
    AMD Phenom II X6 1055T
    Mushkin Enhanced Blackline 4gb 2x2 ddr3 1600
    nzxt vulcan
    corsair hx 650

    Quote from: saint12 on 12-February-11, 16:33:23
    got everything up and running mine came with bios ver 1.6 used m-flash to flash to ver 1.8 had no problems only thing i don't like is the lan wont run at 1gbps to my netgear wnce2001 even if i select 1gb full it wont even switch from 100mb.
    This is a different issue ,you should open another thread.
    Anyway you can t get 1000M if the switch in the router can t do 1000.
    Is the router gigabit on the LAN ports?The router will limit you.

  • 890GXM-G65 No onboard (realtek) analog sound

    About a month ago I saved up enough of my precious dollars to upgrade my slow, single core computer into something a bit more passable for this day and age.  The new computer is much better, but it is lacking something very important to me: sound.
    I can't hear any audio.  Windows, in all flavors, thinks the device is functional, while the Realtek control panel app swears up and down that I have not plugged anything into the back ports.  I've talked to my dealer, friends, one online forum, and finally found my way here, a forum dedicated to MSI boards that I somehow didn't come across earlier or I would've come here straight away.
    Well, without further ado, here are the specs:
    890GXM-G65 MS-8642 BIOS 1.B0
    AMD Athlon 2 X3 3.2Ghz
    Crucial 2x2GB CT25664BA1339A
    Antek25 650W +12V~38A, +5V~24A, +3.3V~24A
    XP Pro SP3 x86 / Server 2003 R2 x64 / *cough* 7 x86
    I have other hardware of course, but since I've been testing I've stripped it down to the bare essentials.
    I also found a very similar thread (https://forum-en.msi.com/index.php?topic=151266.0).  It was resolved by putting in a different sound card, but that's not an option for me.
    As I've said, I've tried to figure this out with the help of others for some time now.
    Things I've tried:
    * Tried multiple OSes, including to my chagrin Windows 7.  I was going to try Delphi but the installer didn't like my setup, and well, this IS a gaming rig so it's not worth figuring out why.
    * Tried multiple drivers, both new, old, MSI, Realtek, and on 7 the default drivers, across all of the OSes above.
    * Tried jumping the front panel connector.  Supposedly you don't have to anymore, but just in case I shorted 5-6 and 9-10 to no effect.
    * Tried every combination of settings I could think of in the realtek manager, especially the one related to ignoring the front panel jack detection.
    * Tried removing, reluctantly, the board from the case.
    * Tried fresh install of 7 on the stripped down and removed board.
    * Tried RMAing the board after everyone concluded that the board was bad.  This was very painful.  I was without any reasonable computing power for a week.  To my great shock, this did not help and I am right back where I was last month.
    Things I can't try:
    * Testing the front panel audio (I don't have any such connector; JAUD1 is open)
    * Testing the digital out (again, no such equipment)
    Things that people always ask just in case (if there's a stupidly easy thing I've missed though go ahead and ask it--I sometimes miss stupidly easy things):
    * Is the on-board sound enabled in the BIOS?  Yes it is.
    * Do the speakers work?  Yep.  Worked since the 90s, works in laptop today.
    * On 7 did you switch it from digital out to analog out?  Yes, sort've.  The analog out options couldn't be selected normally, but I could select the headphones option if I disabled the front panel jack detection.  Not having a front panel, I was not surprised to find that this didn't work (though the green volume bar was moving).  A 'disable rear jack detection' setting would be very nice.
    I am stumped, as is everyone else I've asked--we all thought the old board must have been defective but getting a new, equally incapable board seems to put that theory to rest.  I'm well past the point where I'd normally write it off and use a spare sound card, but this board only has one PCI slot, and it is occupied.  The only available slot is the second PCI-E 16 slot, and I don't think they make sound cards for that.  And even if they did I really don't have the money to buy anything new; I've already sunk more than I budgeted for on this.
    Any ideas?

    Enable Digital IO.. is not under properties.. Control Panel/Sound/Double Click (to open) on your choice of 'playback devices'.. in this case 'the default out choice..Speakers and then under the 'Custom' Tab.. it is the Only check box or option under the 'Custom' Tab. Odds are it is unchecked but worth looking. I unhooked my Speakers and it was still there. Also without my speakers attached is the  Configure Icon box.. but it is unavailable to open, unless the output choice (the Default out choice) is clicked on and highlighted. Then you can enter Configure.
    We are both using Windows 7.. The question of your posted pictures is seen in the pictures. Lower picture shows 2ea Default.. Green Circle active as default. Your upper picture doesn't show Speakers as a selection, it shows a Headset. So my question was leading to a possible conflict of Default outputs. No I'm not drunk, but I am electronic capable.. poss that's a reason my explanation is seeming drunk..lol
    My point is.. when setting your DEFAULT output choice... If you have your speakers 1/8" plugged into the Boards 'Green" jack. Have it that way only... no other speakers or headsets attached. Make the Speaker out choice under Control Panel/ Sound and under the Playback tab.. the only Default choice. Undo any second Default selection. That is the Output choice showing a Green Circle with a check mark inside it. That is what you are assigning as the audio out you are using. Just to see if there is a conflict. Again the posted lower picture that you show under the Sound box has 2 defaults.
    You also have the Realtek HD Audio Manager shown. Possibly that is a conflict.. Is one set different than the other? You have 2 separate audio control programs. One is the Windows OS Sound control choice, and the other is your Realtek HD Audio Mamager. If you un-install the Realtek HD Audio Manager program, you still have the Windows 7 OS Sound controls. Both is just an option. You do want to always have your Windows Sound programs installed.. it controls a lot to include your Theme Sounds and more... Your Realtek HD Audio Manager is optional. If both are not set for defaults out, such as the exact same output selections... they will conflict.
    You can always reinstall the Realtek Audio program. Since you have no sound and don't know if it is a board electrical problem.. as in a broken circuit. Use just one.. Windows one!! Then if you have sound from the Green jack input on the board... it will tell you that the board is infact OK. Then it all boils down to which program to use.
    Fixing a problem is a task of the process of elimination. Make it simple to see if it will work.
    Try again removing the Realtek HD Audio, optional program. Plug your speaker into the proper output. Make sure that under Sound and the playback tab.. speakers are default. That green circle. Highlight the Speaker choice. Click on Configure. and follow to configure. Double click on the Speaker selection. Go through all the tabs and make proper choices. Also on your desktop, on the bottom right open settings from the Speaker Icon next to the Time and Date. Volume is on and up, and the mixer setting also are up for volume. Now you are setup for speakers without out a secondary conflict of two programs and 2 defaults. If you have no sound after that... at least you know you finally have all the proper settings, and no conflicts.
    Keep it simple and basic until you figure out your no sound woes. Still not working? Then it's time do figure out if you problem is software based or hardware based. Man, I hope you are following this.. I really am trying to help. I know problems can be so frustrating. I build and fix a lot of problems for Friends. No master but I do understand diagnostic processes.
    I hope the next Post from you is that your possible conflicts are gone, and you have sound. If it is a conflict? Sure seems possible.

  • MSI 890GXM-G65 Thuban Issues

    Hi,
    Sorry if I post this in the wrong section.
    I've been using v1.0 original bios for MSI 890GXM-G65 board without any problems.
    Recently I tried updating to v1.2 to enable support for X6 1055T as stated in the link below.
    My cpu code is HDT55TFBK6DGR which is the 125W version and requires v1.2 bios.
    http://www.msi.com/index.php?func=prodcpu2&prod_no=2012&maincat_no=1#menu
    I am unable to turn off Cool'n'Quiet feature for the Thuban core.
    Enabling or disabling the setting in BIOS has no effect at all.
    Multipliers keep dropping to x4 from the stock x14.
    I also could not find any setting in BIOS to switch off Turbo Core.
    I posted the issues in detail here:
    http://forums.hardwarezone.com.sg/showpost.php?p=45130922&postcount=66
    I found out that the MSI 790FX-GD70 also do not have such a feature to disable Turbo Core.
    In comparison, the Biostar TA890GXE has that setting in its BIOS so this is not a specific issue for 890G-based boards.
    Lastly, I could not get CPU-Z (or any other programs for that matter) to display accurate readings of the cpu vcore (set in BIOS).
    Will MSI be releasing a new BIOS soon to fix these issues ?
    Thanks.

    Quote from: Golden Arm on 18-April-10, 06:25:26
    Ah, that explains it. How's that Thuban CPU running at stock levels compared to other Quad-cores (if you have had any)?
    Actually that hardwarezone link in my first post goes to my mini review of the X6 1055T.
    http://forums.hardwarezone.com.sg/showthread.php?t=2731901
    Unfortunately I only have synthetic benchmarks to compare the results with.
    This is my very FIRST phenom chip from AMD.
    The only quad I ever tried was the Intel Q6600 (used for 1-mth) before sticking to 2-core processors ever since. LOL!
    Quote from: greyno3 on 18-April-10, 03:50:14
    I don't see a bios update yet for the 790FX-GD70. This mb I am running is my brothers...haha. I am waiting for the 890FX-GD70.
    One of our local overclocker "ridney" is using the X6 1055T on MSI 790FX-GD70 with the latest 1.11b1 bios.
    He has the same cpu batch as me but he is on water. I'm not willing to go >1.52V on air for this hexacore chip (not yet anyway).
    He had posted all his OC'ing @ http://www.xtremesystems.org/forums/showthread.php?t=249606
    The screenshot posted (towards bottom of page) @ https://forum-en.msi.com/index.php?topic=136443.0 was his!!   
    The reason I posted my inquiry here is because I thought there would be newer (beta) bios for the 890GXM-G65 which MAY allow me to disable turbo core.

  • MSI 890GXM-G65 Black Screen

    Hey guys, new member, but Ive been a longtime reader.
    I have the MSI 890GXM-G65 motherboard with the following other components:
    AMD X4 820 CPU
    8GB (4x2GB DDR3 1333) ram
    1TB Western Digital
    Antec High Current 400W PSU
    DVDRW
    I have a black screen on the PC when it boots. The monitor doesn't turn on at all. I removed all peripherals except CPU, motherboard, ram and power supply.
    Here's what I have tried:
    1. Replaced RAM with other known working ram
    2. Tried one stick in each of the 4 slots individually.
    3. Tried a different power supply.
    4. Installed a PCI express video card.
    5. Switched CPUS to an AMD B73 CPU
    6. Tried VGA, DVI and HDMI on the motherboard output.
    None of these things have worked. The CPU fan spins at what appears to be full speed, all four blue LEDs are on, and there is no video.
    Do you have any suggestions as to what I can do?

    It isn't a new build. It was working before with these exact specs for about a year. This is my HTPC, so I don't use it  too often, last used a week ago. I turned it on today and got nothing. So I've been replacing every part I can.
    Forgot to mention  that I also cleared the CMOS, which did nothing.

  • 890GXM-G65 New Build

    Hello
    I am building a new machine but having blue screen crashes during OS installation. The machine spec is as follows:
    Motherboard: MSI 890GXM-G65, with latest 1B BIOS. BOIS is set to default settings.
    Memory: 2 x 4GB Corsair 1333 DDR3 Non-ECC (9-9-9-24) 1.50V, dual channel.
    Power Supply: Arctic 700W.
    Processor: AMD Phenom II X4 955 Black Edition Socket AM3 3.2 GHz.
    HDD: Seagate 500GB 3.5" Barracuda SATA-III 6Gb/s
    Optical Drive: LG BH10LS30 10x BD-RE with DVD±RW & LightScribe SATA Blu-Ray
    First I tried loading my old Windows XP OS but this was was crashing at random points in the installation process. Sometimes I would get all the way through but it would crash during updating from the Windows Update website. I gave this up and decided to bit the bullet and put Windows 7 on it. This began blue screening almost immediately, but my most successful attempt has got to 66% in the expanding files phase of the install (several times it has stopped here). I had a 550W PSU installed at this time, so I decided to put the PSU shown above in, but this has made no difference. The blue screen message is almost always "IRQL_NOT_LESS_OR_EQUAL", which does not tell me to much. It might be indicating a CPU or Motheboard issue, but I cannot decide which.
    I now have a pretty big investment in hardware and software, and not a lot to show for it. I would be most grateful for any pointers that anyone has to offer on how to proceed further with determining where the problem lies. Thanks very much for reading this.

    The Corsair is for sure far more powerful then both others.
    As you have to look at the 12V rail, it output 34A BUT that is continues power.
    Those other PSU's will not do that, not even close.
    You can simply not buy a powersupply that outputs 500W continues for a lower price then the Corsair.
    But the entire game isn't about watts, it's about 12V amperes that can be delivered continues, the Corsair does that.
    Those "brands" you name for sure won't deliver anything near and probably explode when you try.
    Please do some reading at http://www.jonnyguru.com/ you will quickly find out that watts are not the game to be played, the amps that the 12V regulators can handle are.
    BTW, he has some reviews about el-cheapo PSU's that blow to pieces big time not even reaching anything near the Wattage on the label.
    Please don't fall for the Watt trap as it's abused by many cheap crap PSU's, even if they do look fancy.
    Just read this test about the CX-430 and you know enough: http://www.jonnyguru.com/modules.php?name=NDReviews&op=Story&reid=214

  • 890GXM-G65 RAID 5 Issues (SB850)

    Hi all
    Hopefully you guys can help me, I am hours and hours into this by now.  My 890GXM-G65 does not want to cooperate with me to make a 3x4TB RAID 5 array using Seagate ST4000DM000 HDDs.  I can get it to build the array and it will show up in windows/RAIDXpert, I am able to do a quick format and it shows up in explorer.  So far so good.  Start to transfer data and within ~1 min RAIDXpert tells me the array went critical or it will BSOD with AHCIx64.sys as the error and DRIVER_IRQL_NOT_LESS_OR_EQUAL. If I reboot the drive on port 3 is now shown as a single disk but it is there again and I can re-create the array.  RAIDXpert will show port 3 as disconnected if it does not BSOD and will re-appear after a reboot, but as a single disk just like when it does BSOD.
    Interestingly if I delete the Logical Drive and reboot, the single disk will come up as a failed array, as if it somehow got split off into its own Logical Drive, but it will not show as an LD when the main 2 disk part still exists.
    I have tried switching the drive around to isolate if it is a particular drive, but no matter what drive is connected it is always port 3 that is lost. 
    I have tried different cables, no luck.
    I have tried replacing the motherboard, no luck (yes I actually have a spare board, lol).
    I have even tried replacing the CPU as this one is somewhat old and abused, no luck.
    I have re-installed windows, no luck.
    I have tried a different PSU, no luck
    I have tried different RAM, no luck
    When I switch the controller to AHCI mode in the BIOS I am able to do a full format on each individual drive just fine so I believe the drives to be fine
    In RAID mode trying to use as individual drives, when I begin to transfer data to the drive on port 3 the drive simply disappears until a reboot.
    At this point I am completely confused, does the SB850 not support 4TB drives?  Before the reinstall I tried with 3x 500GB drives and it would still crash the system, but it would not kick a drive out of the array as consistently.  I have not had a BSOD since the windows reinstall however, only the RAIDXpert telling me the array failed.
    Does anyone have any advice or ideas at all?  I am completely baffled at this point to where I am looking at replacing the whole system or getting a RAID card, only issue is I only have the PCI slot free to put a card into.
    Here is the entire spec list
    Proc: AMD Phenom II x6 1090T
    Mobo: MSI 890GXM-G65
    RAM: 16GB Corsair Vengeance 1866
    GPU: Visiontek LP HD 7750
    PSU: Seasonic 300W Gold TFX
    SSD: 128GB Samsung 830
    HDD: 3x 4TB Seagate ST4000DM000
    Optical: Silverstone Slim BD-R
    Add-Ins: ASUS PCE-AC66 Wireless
    Silverstone EC-04 USB 3.0 Card
    Rosewill RC-120 SATA 150 card
    Case: In-Win BL040.300TB3LF Low Profile mATX
    Yes there is a ton of stuff packed into a very small space.

    Looks like I'm the only one with this issue 
    I did some experimenting, basically trying different SSD make/model but otherwise keeping setup identical. Instead of Kingston V300 I attached Samsung 840 Pro 120GB to this system hoping that it could be SSD-controller specific problem. Unfortunately nothing has changed - I still have grave issues with waking up from S3 sleep. Now I'm inclined to believe that this is the problem with RAID controller on motherboard  rather than Kingston drive issue. Too bad, I like this motherboard but looks like I have to start thinking about replacing it with something else. Guess I would be looking at some other vendor/chipset then.

  • [Solved]Control of automatic GPU switching in Linux 3.13

    I'm using the Linux Kernel 3.13 of the testing repository, I have a laptop with Hybrid Graphics ATI/Intel:
    00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
    01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Whistler [Radeon HD 6730M/6770M/7690M XT] (rev ff)
    I use the vgaswitcheroo method to shutdown the discrete GPU, it generally show this:
    0:IGD:+:Pwr:0000:00:02.0
    1:DIS: :Off:0000:01:00.0
    But with the New Kernel Feature Automatic GPU Switching I can't shutdown the Discrete GPU of my Hybrid Graphics System, I got this output:
    0:IGD:+:Pwr:0000:00:02.0
    1:DIS: :DynPwr:0000:01:00.0
    I have searched for the power_dpm_state in /sys/class/drm for change to "battery" mode but it file doesn't exist (With the Kernel 3.12 I can set up DPM to "battery" mode)
    I don't want to use the Discrete GPU on Linux to save energy and with the DynPwr I got about 60 ͦ C
    How Can I set up my Hybrid Graphics Cards for reduce the temperature?
    Thanks!
    Last edited by josejacomeb (2014-02-23 00:32:33)

    denspirit wrote:
    Any line with something like 
    ACPI Error: Method parse/execution failed [\_TZ_.TZ01._TMP]
    clearly seems to be DSDT bug - a bug in your notebook's low-level firmware. It's nearly insolvable.
    You may  try to update BIOS, or decompose@recompile DSDT by yourself.
    I have not succeeded in the latter task, though in my case it just can't remember brightness between reboots and lockups GPU if I dare to switch it.
    By the way, have you seen the Lenovo S540 wiki page on ArchWiki? It suggests to disable modesetting in intel videocard ( kernel parameter intel.modeset=0 means exactly that).
    And I can't say anything about stack trace (!) in your dmesg. Maybe it's related to above intel modesetting.
    Yes:
    Mar 30 20:12:28 lenovo1 kernel: ACPI Exception: AE_BAD_PARAMETER, Returned by Handler for [EmbeddedControl] (20131
    Mar 30 20:12:28 lenovo1 kernel: ACPI Error: Method parse/execution failed [\_TZ_.TZ01._TMP] (Node ffff88022387ac80
    Mar 30 20:12:28 lenovo1 kernel: ACPI Exception: AE_BAD_PARAMETER, Returned by Handler for [EmbeddedControl] (20131
    Mar 30 20:12:28 lenovo1 kernel: ACPI Error: Method parse/execution failed [\_TZ_.TZ01._TMP] (Node ffff88022387ac80
    Mar 30 20:12:28 lenovo1 kernel: mei_me 0000:00:16.0: irq 61 for MSI/MSI-X
    Bios is latest available!
    I'll have a look at disabling Intel nomodeset and test later or tomorrow and report back. (This is a dual boot uefi machine booting via rEFInd)
    Edit: booting the 3.13.7 kernel with intel,modeset=0 gives the same blank screen on graphical boot but the kernel loads fine - access vis ssh to downgrade the kernel to 3.13.6 and boot with the same parameter works fine though. So there remains a problem with the graphical boot for kernel .13.7
    For the working 3.13.6 kernel the Xorg log is:
    $ cat /var/log/Xorg.0.log
    [ 11.880]
    X.Org X Server 1.15.0
    Release Date: 2013-12-27
    [ 11.880] X Protocol Version 11, Revision 0
    [ 11.880] Build Operating System: Linux 3.12.5-1-ARCH x86_64
    [ 11.880] Current Operating System: Linux lenovo1 3.13.6-1-ARCH #1 SMP PREEMPT Fri Mar 7 22:47:48 CET 2014 x86_64
    [ 11.880] Kernel command line: \boot\vmlinuz-linux root=PARTUUID=a01aa42a-8ece-4584-a632-bea1f042c80a ro rootfstype=ext4 systemd.unit=graphical.target initrd=boot\initramfs-linux.img
    [ 11.880] Build Date: 09 January 2014 08:47:24AM
    [ 11.880]
    [ 11.880] Current version of pixman: 0.32.4
    [ 11.880] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 11.880] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 11.880] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Mar 30 21:37:13 2014
    [ 11.882] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 11.882] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
    [ 11.884] (==) No Layout section. Using the first Screen section.
    [ 11.884] (==) No screen section available. Using defaults.
    [ 11.884] (**) |-->Screen "Default Screen Section" (0)
    [ 11.884] (**) | |-->Monitor "<default monitor>"
    [ 11.885] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    [ 11.885] (==) Automatically adding devices
    [ 11.885] (==) Automatically enabling devices
    [ 11.885] (==) Automatically adding GPU devices
    [ 11.892] (==) 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/
    [ 11.892] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 11.892] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 11.892] (II) Loader magic: 0x804c80
    [ 11.892] (II) Module ABI versions:
    [ 11.892] X.Org ANSI C Emulation: 0.4
    [ 11.892] X.Org Video Driver: 15.0
    [ 11.892] X.Org XInput driver : 20.0
    [ 11.892] X.Org Server Extension : 8.0
    [ 11.892] (II) xfree86: Adding drm device (/dev/dri/card1)
    [ 11.892] (II) xfree86: Adding drm device (/dev/dri/card0)
    [ 11.893] (--) PCI:*(0:0:2:0) 8086:0a16:17aa:2216 rev 9, Mem @ 0xf0000000/4194304, 0xe0000000/268435456, I/O @ 0x00005000/64
    [ 11.893] (--) PCI: (0:6:0:0) 1002:6660:17aa:2216 rev 0, Mem @ 0xd0000000/268435456, 0xf0400000/262144, I/O @ 0x00003000/256, BIOS @ 0x????????/131072
    [ 11.893] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    [ 11.893] Initializing built-in extension Generic Event Extension
    [ 11.893] Initializing built-in extension SHAPE
    [ 11.893] Initializing built-in extension MIT-SHM
    [ 11.893] Initializing built-in extension XInputExtension
    [ 11.893] Initializing built-in extension XTEST
    [ 11.893] Initializing built-in extension BIG-REQUESTS
    [ 11.893] Initializing built-in extension SYNC
    [ 11.893] Initializing built-in extension XKEYBOARD
    [ 11.893] Initializing built-in extension XC-MISC
    [ 11.893] Initializing built-in extension SECURITY
    [ 11.893] Initializing built-in extension XINERAMA
    [ 11.893] Initializing built-in extension XFIXES
    [ 11.894] Initializing built-in extension RENDER
    [ 11.894] Initializing built-in extension RANDR
    [ 11.894] Initializing built-in extension COMPOSITE
    [ 11.894] Initializing built-in extension DAMAGE
    [ 11.894] Initializing built-in extension MIT-SCREEN-SAVER
    [ 11.894] Initializing built-in extension DOUBLE-BUFFER
    [ 11.894] Initializing built-in extension RECORD
    [ 11.894] Initializing built-in extension DPMS
    [ 11.894] Initializing built-in extension Present
    [ 11.894] Initializing built-in extension DRI3
    [ 11.894] Initializing built-in extension X-Resource
    [ 11.894] Initializing built-in extension XVideo
    [ 11.894] Initializing built-in extension XVideo-MotionCompensation
    [ 11.894] Initializing built-in extension XFree86-VidModeExtension
    [ 11.894] Initializing built-in extension XFree86-DGA
    [ 11.894] Initializing built-in extension XFree86-DRI
    [ 11.894] Initializing built-in extension DRI2
    [ 11.894] (II) "glx" will be loaded by default.
    [ 11.894] (II) LoadModule: "dri2"
    [ 11.894] (II) Module "dri2" already built-in
    [ 11.894] (II) LoadModule: "glamoregl"
    [ 11.896] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
    [ 11.907] (II) Module glamoregl: vendor="X.Org Foundation"
    [ 11.907] compiled for 1.15.0, module version = 0.6.0
    [ 11.907] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 11.907] (II) LoadModule: "glx"
    [ 11.907] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 11.909] (II) Module glx: vendor="X.Org Foundation"
    [ 11.909] compiled for 1.15.0, module version = 1.0.0
    [ 11.909] ABI class: X.Org Server Extension, version 8.0
    [ 11.909] (==) AIGLX enabled
    [ 11.909] Loading extension GLX
    [ 11.909] (==) Matched intel as autoconfigured driver 0
    [ 11.909] (==) Matched intel as autoconfigured driver 1
    [ 11.909] (==) Matched modesetting as autoconfigured driver 2
    [ 11.909] (==) Matched fbdev as autoconfigured driver 3
    [ 11.909] (==) Matched vesa as autoconfigured driver 4
    [ 11.909] (==) Assigned the driver to the xf86ConfigLayout
    [ 11.909] (II) LoadModule: "intel"
    [ 11.909] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
    [ 11.911] (II) Module intel: vendor="X.Org Foundation"
    [ 11.911] compiled for 1.15.0, module version = 2.99.911
    [ 11.911] Module class: X.Org Video Driver
    [ 11.911] ABI class: X.Org Video Driver, version 15.0
    [ 11.911] (II) LoadModule: "modesetting"
    [ 11.911] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
    [ 11.912] (II) Module modesetting: vendor="X.Org Foundation"
    [ 11.912] compiled for 1.15.0, module version = 0.8.1
    [ 11.912] Module class: X.Org Video Driver
    [ 11.912] ABI class: X.Org Video Driver, version 15.0
    [ 11.912] (II) LoadModule: "fbdev"
    [ 11.912] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
    [ 11.912] (II) Module fbdev: vendor="X.Org Foundation"
    [ 11.912] compiled for 1.15.0, module version = 0.4.4
    [ 11.912] Module class: X.Org Video Driver
    [ 11.912] ABI class: X.Org Video Driver, version 15.0
    [ 11.912] (II) LoadModule: "vesa"
    [ 11.912] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
    [ 11.913] (II) Module vesa: vendor="X.Org Foundation"
    [ 11.913] compiled for 1.15.0, module version = 2.3.2
    [ 11.913] Module class: X.Org Video Driver
    [ 11.913] ABI class: X.Org Video Driver, version 15.0
    [ 11.913] (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
    [ 11.913] (II) intel: Driver for Intel(R) HD Graphics: 2000-5000
    [ 11.913] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100
    [ 11.913] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200
    [ 11.913] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
    [ 11.913] (II) FBDEV: driver for framebuffer: fbdev
    [ 11.913] (II) VESA: driver for VESA chipsets: vesa
    [ 11.913] (++) using VT number 7
    [ 11.919] (WW) Falling back to old probe method for modesetting
    [ 11.919] (EE) open /dev/dri/card0: Invalid argument
    [ 11.919] (WW) Falling back to old probe method for fbdev
    [ 11.919] (II) Loading sub module "fbdevhw"
    [ 11.919] (II) LoadModule: "fbdevhw"
    [ 11.919] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
    [ 11.920] (II) Module fbdevhw: vendor="X.Org Foundation"
    [ 11.920] compiled for 1.15.0, module version = 0.0.2
    [ 11.920] ABI class: X.Org Video Driver, version 15.0
    [ 11.920] (WW) Falling back to old probe method for vesa
    [ 11.920] (--) intel(0): Integrated Graphics Chipset: Intel(R) HD Graphics 4400
    [ 11.920] (--) intel(0): CPU: x86-64, sse2, sse3, ssse3, sse4.1, sse4.2, avx, avx2
    [ 11.920] (II) intel(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
    [ 11.920] (==) intel(0): Depth 24, (--) framebuffer bpp 32
    [ 11.920] (==) intel(0): RGB weight 888
    [ 11.920] (==) intel(0): Default visual is TrueColor
    [ 11.920] (**) intel(0): Framebuffer tiled
    [ 11.920] (**) intel(0): Pixmaps tiled
    [ 11.920] (**) intel(0): "Tear free" disabled
    [ 11.920] (**) intel(0): Forcing per-crtc-pixmaps? no
    [ 11.920] (II) intel(0): Output eDP1 has no monitor section
    [ 11.920] (--) intel(0): Found backlight control interface acpi_video0 (type 'firmware') for output eDP1
    [ 11.920] (II) intel(0): Output DP1 has no monitor section
    [ 11.920] (II) intel(0): Output HDMI1 has no monitor section
    [ 11.920] (II) intel(0): Output HDMI2 has no monitor section
    [ 11.920] (II) intel(0): Output VIRTUAL1 has no monitor section
    [ 11.921] (--) intel(0): Output eDP1 using initial mode 1920x1080 on pipe 0
    [ 11.921] (==) intel(0): DPI set to (96, 96)
    [ 11.921] (II) Loading sub module "dri2"
    [ 11.921] (II) LoadModule: "dri2"
    [ 11.921] (II) Module "dri2" already built-in
    [ 11.921] (II) UnloadModule: "modesetting"
    [ 11.921] (II) Unloading modesetting
    [ 11.921] (II) UnloadModule: "fbdev"
    [ 11.921] (II) Unloading fbdev
    [ 11.921] (II) UnloadSubModule: "fbdevhw"
    [ 11.921] (II) Unloading fbdevhw
    [ 11.921] (II) UnloadModule: "vesa"
    [ 11.921] (II) Unloading vesa
    [ 11.921] (==) Depth 24 pixmap format is 32 bpp
    [ 11.923] (II) intel(0): SNA initialized with Haswell (gen7.5, gt2) backend
    [ 11.923] (==) intel(0): Backing store enabled
    [ 11.923] (==) intel(0): Silken mouse enabled
    [ 11.923] (II) intel(0): HW Cursor enabled
    [ 11.923] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    [ 11.924] (==) intel(0): DPMS enabled
    [ 11.924] (II) intel(0): [DRI2] Setup complete
    [ 11.924] (II) intel(0): [DRI2] DRI driver: i965
    [ 11.924] (II) intel(0): [DRI2] VDPAU driver: i965
    [ 11.924] (II) intel(0): direct rendering: DRI2 Enabled
    [ 11.924] (==) intel(0): hotplug detection: "enabled"
    [ 11.924] (--) RandR disabled
    [ 11.943] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
    [ 11.943] (II) AIGLX: enabled GLX_ARB_create_context
    [ 11.943] (II) AIGLX: enabled GLX_ARB_create_context_profile
    [ 11.943] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
    [ 11.943] (II) AIGLX: enabled GLX_INTEL_swap_event
    [ 11.943] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
    [ 11.943] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
    [ 11.943] (II) AIGLX: enabled GLX_ARB_fbconfig_float
    [ 11.943] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
    [ 11.943] (II) AIGLX: Loaded and initialized i965
    [ 11.943] (II) GLX: Initialized DRI2 GL provider for screen 0
    [ 11.951] (II) intel(0): switch to mode [email protected] on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none
    [ 11.970] (II) intel(0): Setting screen physical size to 508 x 285
    [ 12.048] (II) config/udev: Adding input device Power Button (/dev/input/event2)
    [ 12.048] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 12.048] (II) LoadModule: "evdev"
    [ 12.048] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 12.049] (II) Module evdev: vendor="X.Org Foundation"
    [ 12.049] compiled for 1.15.0, module version = 2.8.2
    [ 12.049] Module class: X.Org XInput Driver
    [ 12.049] ABI class: X.Org XInput driver, version 20.0
    [ 12.049] (II) Using input driver 'evdev' for 'Power Button'
    [ 12.049] (**) Power Button: always reports core events
    [ 12.049] (**) evdev: Power Button: Device: "/dev/input/event2"
    [ 12.049] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 12.049] (--) evdev: Power Button: Found keys
    [ 12.049] (II) evdev: Power Button: Configuring as keyboard
    [ 12.049] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event2"
    [ 12.049] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    [ 12.049] (**) Option "xkb_rules" "evdev"
    [ 12.049] (**) Option "xkb_model" "pc104"
    [ 12.049] (**) Option "xkb_layout" "gb"
    [ 12.063] (II) config/udev: Adding input device Video Bus (/dev/input/event4)
    [ 12.063] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
    [ 12.063] (II) Using input driver 'evdev' for 'Video Bus'
    [ 12.063] (**) Video Bus: always reports core events
    [ 12.063] (**) evdev: Video Bus: Device: "/dev/input/event4"
    [ 12.063] (--) evdev: Video Bus: Vendor 0 Product 0x6
    [ 12.063] (--) evdev: Video Bus: Found keys
    [ 12.063] (II) evdev: Video Bus: Configuring as keyboard
    [ 12.063] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:01/input/input4/event4"
    [ 12.063] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
    [ 12.063] (**) Option "xkb_rules" "evdev"
    [ 12.063] (**) Option "xkb_model" "pc104"
    [ 12.063] (**) Option "xkb_layout" "gb"
    [ 12.063] (II) config/udev: Adding input device Video Bus (/dev/input/event3)
    [ 12.063] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
    [ 12.063] (II) Using input driver 'evdev' for 'Video Bus'
    [ 12.063] (**) Video Bus: always reports core events
    [ 12.063] (**) evdev: Video Bus: Device: "/dev/input/event3"
    [ 12.063] (--) evdev: Video Bus: Vendor 0 Product 0x6
    [ 12.063] (--) evdev: Video Bus: Found keys
    [ 12.063] (II) evdev: Video Bus: Configuring as keyboard
    [ 12.063] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:2f/LNXVIDEO:00/input/input3/event3"
    [ 12.063] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 8)
    [ 12.063] (**) Option "xkb_rules" "evdev"
    [ 12.063] (**) Option "xkb_model" "pc104"
    [ 12.063] (**) Option "xkb_layout" "gb"
    [ 12.064] (II) config/udev: Adding input device Power Button (/dev/input/event0)
    [ 12.064] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 12.064] (II) Using input driver 'evdev' for 'Power Button'
    [ 12.064] (**) Power Button: always reports core events
    [ 12.064] (**) evdev: Power Button: Device: "/dev/input/event0"
    [ 12.064] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 12.064] (--) evdev: Power Button: Found keys
    [ 12.064] (II) evdev: Power Button: Configuring as keyboard
    [ 12.064] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0/event0"
    [ 12.064] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 9)
    [ 12.064] (**) Option "xkb_rules" "evdev"
    [ 12.064] (**) Option "xkb_model" "pc104"
    [ 12.064] (**) Option "xkb_layout" "gb"
    [ 12.064] (II) config/udev: Adding input device Lid Switch (/dev/input/event1)
    [ 12.064] (II) No input driver specified, ignoring this device.
    [ 12.064] (II) This device may have been added with another device file.
    [ 12.064] (II) config/udev: Adding drm device (/dev/dri/card1)
    [ 12.064] (II) config/udev: Adding input device HDA Intel HDMI HDMI/DP,pcm=8 (/dev/input/event6)
    [ 12.064] (II) No input driver specified, ignoring this device.
    [ 12.064] (II) This device may have been added with another device file.
    [ 12.064] (II) config/udev: Adding input device HDA Intel HDMI HDMI/DP,pcm=3 (/dev/input/event8)
    [ 12.064] (II) No input driver specified, ignoring this device.
    [ 12.064] (II) This device may have been added with another device file.
    [ 12.065] (II) config/udev: Adding input device HDA Intel HDMI HDMI/DP,pcm=7 (/dev/input/event7)
    [ 12.065] (II) No input driver specified, ignoring this device.
    [ 12.065] (II) This device may have been added with another device file.
    [ 12.065] (II) config/udev: Adding input device Integrated Camera (/dev/input/event9)
    [ 12.065] (**) Integrated Camera: Applying InputClass "evdev keyboard catchall"
    [ 12.065] (II) Using input driver 'evdev' for 'Integrated Camera'
    [ 12.065] (**) Integrated Camera: always reports core events
    [ 12.065] (**) evdev: Integrated Camera: Device: "/dev/input/event9"
    [ 12.065] (--) evdev: Integrated Camera: Vendor 0x5986 Product 0x29d
    [ 12.065] (--) evdev: Integrated Camera: Found keys
    [ 12.065] (II) evdev: Integrated Camera: Configuring as keyboard
    [ 12.065] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6:1.0/input/input12/event9"
    [ 12.065] (II) XINPUT: Adding extended input device "Integrated Camera" (type: KEYBOARD, id 10)
    [ 12.065] (**) Option "xkb_rules" "evdev"
    [ 12.065] (**) Option "xkb_model" "pc104"
    [ 12.065] (**) Option "xkb_layout" "gb"
    [ 12.065] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event13)
    [ 12.065] (II) No input driver specified, ignoring this device.
    [ 12.065] (II) This device may have been added with another device file.
    [ 12.065] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event12)
    [ 12.065] (II) No input driver specified, ignoring this device.
    [ 12.065] (II) This device may have been added with another device file.
    [ 12.065] (II) config/udev: Adding drm device (/dev/dri/card0)
    [ 12.065] (II) xfree86: Adding drm device (/dev/dri/card0)
    [ 12.065] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event5)
    [ 12.065] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
    [ 12.065] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
    [ 12.065] (**) AT Translated Set 2 keyboard: always reports core events
    [ 12.065] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event5"
    [ 12.065] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
    [ 12.065] (--) evdev: AT Translated Set 2 keyboard: Found keys
    [ 12.065] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
    [ 12.065] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input5/event5"
    [ 12.065] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 11)
    [ 12.065] (**) Option "xkb_rules" "evdev"
    [ 12.065] (**) Option "xkb_model" "pc104"
    [ 12.065] (**) Option "xkb_layout" "gb"
    [ 12.066] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event14)
    [ 12.066] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
    [ 12.066] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
    [ 12.066] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default clickpad buttons"
    [ 12.066] (II) LoadModule: "synaptics"
    [ 12.066] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
    [ 12.066] (II) Module synaptics: vendor="X.Org Foundation"
    [ 12.066] compiled for 1.15.0, module version = 1.7.4
    [ 12.066] Module class: X.Org XInput Driver
    [ 12.066] ABI class: X.Org XInput driver, version 20.0
    [ 12.066] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
    [ 12.066] (**) SynPS/2 Synaptics TouchPad: always reports core events
    [ 12.066] (**) Option "Device" "/dev/input/event14"
    [ 12.160] (II) synaptics: SynPS/2 Synaptics TouchPad: found clickpad property
    [ 12.160] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5112 (res 42)
    [ 12.160] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 3834 (res 42)
    [ 12.160] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
    [ 12.160] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
    [ 12.160] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left double triple
    [ 12.160] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
    [ 12.160] (**) Option "TapButton1" "1"
    [ 12.160] (**) Option "TapButton2" "2"
    [ 12.160] (**) Option "TapButton3" "3"
    [ 12.160] (**) Option "SoftButtonAreas" "50% 0 82% 0 0 0 0 0"
    [ 12.160] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    [ 12.160] (**) SynPS/2 Synaptics TouchPad: always reports core events
    [ 12.222] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input11/event14"
    [ 12.222] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 12)
    [ 12.223] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
    [ 12.223] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MaxSpeed is now 1.75
    [ 12.223] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) AccelFactor is now 0.046
    [ 12.223] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
    [ 12.223] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
    [ 12.223] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
    [ 12.223] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
    [ 12.223] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    [ 12.223] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0)
    [ 12.223] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates"
    [ 12.223] (II) config/udev: Adding input device PC Speaker (/dev/input/event10)
    [ 12.223] (II) No input driver specified, ignoring this device.
    [ 12.223] (II) This device may have been added with another device file.
    [ 12.224] (II) config/udev: Adding input device ThinkPad Extra Buttons (/dev/input/event11)
    [ 12.224] (**) ThinkPad Extra Buttons: Applying InputClass "evdev keyboard catchall"
    [ 12.224] (II) Using input driver 'evdev' for 'ThinkPad Extra Buttons'
    [ 12.224] (**) ThinkPad Extra Buttons: always reports core events
    [ 12.224] (**) evdev: ThinkPad Extra Buttons: Device: "/dev/input/event11"
    [ 12.224] (--) evdev: ThinkPad Extra Buttons: Vendor 0x17aa Product 0x5054
    [ 12.224] (--) evdev: ThinkPad Extra Buttons: Found keys
    [ 12.224] (II) evdev: ThinkPad Extra Buttons: Configuring as keyboard
    [ 12.224] (**) Option "config_info" "udev:/sys/devices/platform/thinkpad_acpi/input/input7/event11"
    [ 12.224] (II) XINPUT: Adding extended input device "ThinkPad Extra Buttons" (type: KEYBOARD, id 13)
    [ 12.224] (**) Option "xkb_rules" "evdev"
    [ 12.224] (**) Option "xkb_model" "pc104"
    [ 12.224] (**) Option "xkb_layout" "gb"
    [ 18.631] (II) config/udev: Adding input device TPPS/2 IBM TrackPoint (/dev/input/mouse1)
    [ 18.631] (II) No input driver specified, ignoring this device.
    [ 18.631] (II) This device may have been added with another device file.
    [ 18.632] (II) config/udev: Adding input device TPPS/2 IBM TrackPoint (/dev/input/event15)
    [ 18.632] (**) TPPS/2 IBM TrackPoint: Applying InputClass "evdev pointer catchall"
    [ 18.632] (II) Using input driver 'evdev' for 'TPPS/2 IBM TrackPoint'
    [ 18.632] (**) TPPS/2 IBM TrackPoint: always reports core events
    [ 18.632] (**) evdev: TPPS/2 IBM TrackPoint: Device: "/dev/input/event15"
    [ 18.632] (--) evdev: TPPS/2 IBM TrackPoint: Vendor 0x2 Product 0xa
    [ 18.632] (--) evdev: TPPS/2 IBM TrackPoint: Found 3 mouse buttons
    [ 18.632] (--) evdev: TPPS/2 IBM TrackPoint: Found relative axes
    [ 18.632] (--) evdev: TPPS/2 IBM TrackPoint: Found x and y relative axes
    [ 18.632] (II) evdev: TPPS/2 IBM TrackPoint: Configuring as mouse
    [ 18.632] (**) evdev: TPPS/2 IBM TrackPoint: YAxisMapping: buttons 4 and 5
    [ 18.632] (**) evdev: TPPS/2 IBM TrackPoint: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 18.632] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/serio2/input/input16/event15"
    [ 18.632] (II) XINPUT: Adding extended input device "TPPS/2 IBM TrackPoint" (type: MOUSE, id 14)
    [ 18.632] (II) evdev: TPPS/2 IBM TrackPoint: initialized for relative axes.
    [ 18.632] (**) TPPS/2 IBM TrackPoint: (accel) keeping acceleration scheme 1
    [ 18.632] (**) TPPS/2 IBM TrackPoint: (accel) acceleration profile 0
    [ 18.632] (**) TPPS/2 IBM TrackPoint: (accel) acceleration factor: 2.000
    [ 18.632] (**) TPPS/2 IBM TrackPoint: (accel) acceleration threshold: 4
    [ 21.459] (II) intel(0): EDID vendor "AUO", prod id 13549
    [ 21.459] (II) intel(0): Printing DDC gathered Modelines:
    [ 21.459] (II) intel(0): Modeline "1920x1080"x0.0 140.00 1920 1968 2068 2100 1080 1083 1084 1110 -hsync -vsync (66.7 kHz eP)
    Last edited by mcloaked (2014-03-30 20:50:21)

  • Pls help MSI 890GXM-G65

    tomorrow i buy    MSI 890GXM-G65 and AMD Phenom II X4 840 AM3 3.2GHz 2MB Cache 45nm HDX840WFGMBOX 
    no any information MSI 890GXM-G65 cpu support for phenom II X4 840 HDX840WFGMBOX  msi offical site  i waiting answer
    thanks
    S.

    I have one in my 890FXA-GD70 board and it works fine (not on CPU support list for my board too, I notice), don't see why it shouldn't work in your 890GXM-G65 board also.

  • 890GXM-G65 front panel - AC' 97 or HD audio?

    Hello, folks. I bought an 890GXM-G65 and I am having a doubt regarding the installation. The audio connector from the front panel splits in two. One connector reads “AC’ 97” and the other “HD Audio”. My motherboard manual says nothing about which one should I use to plug into the JAUD1.
    I have been researching and looks like AC’ 97 is from AMD boards and HD audio is from Intel boards. Is that correct? Should then I use the connector AC’ 97?
    I appreciate any help!
    Cheers,

    Quote from: Stu on 07-November-10, 22:34:34
    Ujee,
    Please keep discussion of your problem in your own thread, don't hijack others.
    Oh my bad. Never thought it was called a "hijack". I'm sorry for this.

  • 890GXM-G65 Dimm Instructions Incorrect?

    Whoa! Is the User Manual wrong or somethin'?
    Re: Page En-8
    For Dual Channel Operation:
    * When I populate the recommended DIMM1 & DIMM2 Slots with 2Gb sticks, the system will not even POST.
    * Populate just one stick in DIMM1 = normal POST & normal Boot into Windows 7.
    * Populate one stick in DIMM1 & one stick in DIMM3 = again, normal POST & Boot.
    Who's wrong here?
    MSI 890GXM-G65 (MS-7642)
    BIOS ver. A7642AMS.160.2010-04-30
    Phenom II X6 1055
    2x2GB DDR3-1600MHz 7-8-7-20 Corsair
    Diamond Radeon 5750 1Gb
    HDD: WD 160Gb SATA 7200rpm
    Plextor SATA DVD RW
    PSU: Apevia X-QPack2 500W
    Windows 7 Ultimate

    Quote from: roycordaro on 25-May-10, 02:37:38
    Whoa! Is the User Manual wrong or somethin'?
    Re: Page En-8
    For Dual Channel Operation:
    * When I populate the recommended DIMM1 & DIMM2 Slots with 2Gb sticks, the system will not even POST.
    * Populate either stick in DIMM1 = normal POST & normal Boot into Windows 7.
    * Populate one stick in DIMM1 & one stick in DIMM3 = again, normal POST & Boot.
    Who's wrong here?
    MSI 890GXM-G65 (MS-7642)
    BIOS ver. A7642AMS.160.2010-04-30
    Phenom II X6 1055
    2x2GB DDR3-1600MHz 7-8-7-20 Corsair
    Diamond Radeon 5750 1Gb
    HDD: WD 160Gb SATA 7200rpm
    Plextor SATA DVD RW
    PSU: Apevia X-QPack2 500W
    Windows 7 Ultimate

  • 890GXM-G65

    Good day everyone.
    I'm looking for a place to buy a single 890GXM-G65 from that ships to the Netherlands. I have looked around but can't find anything.
    Hans

    If you are still looking for one, cybertronpc is the only place I could find one retail, although pricey.  It works great though, and 3 year warranty if retail.  No warranty if bought used or on ebay or something like that.  I had ordered at 3 other places only for them to get canceled, despite them saying they were in stock.  I just bought it a little over a month ago and they only had about 10 left then.  Could be out. 
    http://www.cybertronpc.com/Itemdesc~ic~MBD-MSI-890GXMA~Group~BUSINESS~Cat~COMPONENTS.htm
    Not sure if MSI will support the board though, only AM3+ compatable board that didnt get a bios update for Vishera, although Vishera CPUs work.  My FX-6300 wont run any faster than 1600 RAM in dual channel.  It only supports up to 1866 in single channel and doesnt like any overclock of the FSB or RAM.   I have tight timings at 1600 though, CL7. 
    Perhaps a bios update would make it more overclocking friendly, as even though it allows 2400mhz NB frequnecy, windows wont show 2400mhz, 2000mhz no matter what I change in the bios.  Maybe something else that needs the bios update for.

  • 890GXM-G65 alarm

    Can someone tell me what the high-pitched alarm noise is the 890GXM-G65?
    It's coming on in a new game I'm trying to play, but doesn't seem to be temperature related (core temp hasn't exceed 41 degrees, according to AMD OverDrive & SpeedFan) and motherboard temperature seems quite low too.  What is the alarm for? 

    Quote from: Tenoq on 17-October-10, 18:42:42
    Appears to be the motherboard.  Do they have an audible alarm?  The alarm is just a constant high-pitched whine and has only started happening under severe load.  I did hear it briefly once before running LinX... but not since. 
    It's definitely not VGA.  VGA temp is very low thanks to an aftermarket cooler. 
    Quote
    It's definitely not VGA.  VGA temp is very low thanks to an aftermarket cooler. 
    Temp doesn't matter, as said before: either test with another VGA or with another PSU.
    This noise typically comes from standard choke:
    This kind of conventional choke has one major disadvantage: high-frequency-noise. When the GPU needs a lot of electricity, the coil and metal stick will be under full loading so that the generated magnetic force will cause mutual interference resulting in vibration. The vibration speed is extremely high and therefore causes high-frequency noise. The noise level depends on the loading and can vary from for humans inaudible 10 dB to unbearable 30 dB.
    In contrast, a solid state choke’s esign is entirely different. It still has a coil inside but is one solid, massive body where the coil is buried in iron, similar toa building where concrete encloses the steel beams. No matter how high the current, solid state chokes won’t vibrate and therefore won’t emit annoying noise. In comparison with traditional chokes, SSC is much more stable and have a higher anti-surge capacity

  • 890GXM-G65 AM3+/black socket

    Hi all. Just wanted to know if the 890GXM-G65 will be getting a black socket/AM3+ revision in the near future...since it is certified AM3+ but the one on the site still has a white/AM3 socket (BD/FX chips won't fit). Thanks.

    Ask MSI: >>How to contact MSI.<<
    As we are not MSI we don't know.

  • 890GXM-G65 MoBo info, links don't work

    Hi,
        I have an 890GXM-G65 MoBo and I know about the cpu compatibility chart on the main site.
    I found the moderator post on the forum (How to check CPU support ), but neither the AM3(+) link nor the
    Vishera link works.
         Does anyone still have the info from the microsites? It would be much appreciated 
                                                       Thank you
                                                           J

    Simply check the product site for cpu support (like instructed in "How to check CPU support"): http://www.msi.com/support/mb/890GXMG65.html#support-cpu

Maybe you are looking for

  • StorE steel 640GB - data error (cyclic redundancy check) message

    Hi I have had the StorE drive for a few months, so lots of data on it. Today windows detects it as a local drive and when I attempt to access it I get a message telling me the disk needs to be formatted, when I select no, I get a message saying *data

  • How do I determine which version of windows os is installed on the computer that my application is running on.

    I need to determine which version of windows os in on the computer running my application to make some minor adjustments to a subvi.  Is there a programmatic way to determine this using Labview.

  • JMS Sender adapter configuration

    Hi, I have a problem in configuring my JMS sender adapter. My source structure is in the form of a FIXED lenght file. Its structure is as follows: Rec ID                       Required                 Loop repeat  SHC                               R 

  • Which compression type should I use?

    Hello~ I'm saving Keynote presentations to QuickTime for viewing on the web. Under the Compression Type menu there are 14 different choices to choose from, Animation to PNG. Apple is big to push the H.264 codec, but I'm getting mixed results with it

  • WRT160N error during install

    I just purchased WRT160N and during the install of LELA there is an error. " Linksys Updater failed to start- verify you have sufficient privileges to start system services" pops up during install.  Then it asks to retry and it hasn't worked or close