[Solved] GS70 GTX 870M Graphical Issue

I bought an MSI GS70 Stealth Pro, and the first game I tried was League of Legends. To my dismay it is the only game giving me this graphical glitch. I have tried Titanfall, Battlefield 4, Elder Scrolls: Online, as well as FurMark and Unengine and none of them have given me any problems. I am running the latest beta drivers (337.50) as the only previous drivers give me the same result.
Here is a video of the issue:
https://www.youtube.com/watch?v=4RFdFws4ie4
Any help would be greatly appreciated!

Quote from: Svet;105766
what files you see when you type:
dir [ENTER]
I will try again and see, so I type on the A:\>"dir" and press enter? ok
EDIT:
Nevermind, I got it I think, I wrote "B:" and show up the vbios.bat so I just wrote it and worked!
- - - Updated - - -
Quote from: Svet;105766
what files you see when you type:
dir [ENTER]
I will try again and see, so I type on the A:\>"dir" and press enter? ok
EDIT:
Nevermind, I got it I think, I wrote "B:" and show up the vbios.bat so I just wrote it and worked!

Similar Messages

  • MSi GE70 Apache Pro w/ nVidia GeForce GTX 860M Graphics Issues

    Hi there,
    I recently purchased an MSi gaming notebook with nVidia GTX 860M graphics. However, just recently I've been having game-breaking issues with textures rendering, artifacts and particles as well as the drivers crashing now and again(desktop flashing and flickering).
    I've only had this laptop for just over two months and am quite disappointed with issues coming up already.
    To get to the specifics; I have recently been playing through the Mass Effect trilogy and, just the other day, started up a file in Skyrim. The following screenshots show my biggest issues aside from the obviously serious driver crashing issues. I believe the issues started maybe a month into owning this laptop and since it has been getting progressively worse. I feel as though I have been all over the internet trying to find a fix to this, I've tried everything suggested, everything that I could think of, and I am just about ready to have it sent back. I was hoping someone may have some other options before I do send it in.
    https://www.dropbox.com/s/d8koa8f8i1z9j3d/Photo%202014-09-30%2C%201%2040%2044%20AM.jpg?dl=0
    On the title screen for Mass Effect 3 I get these consistent blue and red glowing orbs, they also occur on several other maps within gameplay.
    https://www.dropbox.com/s/a9c47w320u5xylb/Photo%202014-09-30%2C%201%2043%2016%20AM.jpg?dl=0
    Once I get in-game, this occurs everywhere. Textures "expanding" off of characters into random points.
    https://www.dropbox.com/s/v37un4vespalosx/Photo%202014-09-30%2C%201%2045%2036%20AM.jpg?dl=0
    This happens occassionally on characters; ridiculously shadowed faces to the point where they are barely recognisable.
    https://www.dropbox.com/s/8cebgs4t10ghnh0/Photo%202014-09-30%2C%201%2046%2020%20AM.jpg?dl=0
    On almost all wall textures there are white glowing particles like the ones behind the character here. In extreme cases, the wall becomes a texture of textures. All of the textures in the game are miniaturized into a wall of textures on certain objects.
    I've also had signs and the game's menus and interface stretched and skewed all over the place. If I continue to play it with the above issues, the game eventually hangs and I have to alt+tab out and back in, or close it using the task manager. All of these issues also occur in Skyrim and any game using the same, or similar, engines. The only game I have been able to play almost seamlessly without any issues is Ragnarok Online 2, an online MMORPG.
    I have tried the following:
    nVidia's GeForce Control Panel: any and all combination of options.
    Re-installing video drivers.
    Re-installing DirectX and PhysX.
    Formatting and a fresh install of Windows and all games and drivers.
    Any other troubleshooting other forums have provided.
    Removing the pagefile for virtual memory limits.
    Using Intel HD graphics to test for other issues.
    PC/nVidia power settings.
    The one time I thought it may be fixed, all it took was me plugging in my laptop to cause the issues all over again. I've tried downloading MSi Afterburner to check GPU temperatures and I rarely even go over 65~70. I'm absolutely out of ideas. It was suggested to me by a family member that it may be a hardware issue, hence the consideration for sending it in.
    I'm running Windows 7 64-bit
    nVidia GeForce GTX 860M
    Intel Core i7-4710HQ CPU @ 2.50GHz
    12GB of RAM
    Any ideas/help would be greatly appreciated. I would really rather not have to send it back. I've also posted this over at the nVidia forums because I'm -hoping- it's a software issue.
    Thanks in advance!

    Quote
    It was suggested to me by a family member that it may be a hardware issue, hence the consideration for sending it in.
    Quote
    To me it sounds like a hardware issue (especially if you have rolled back to factory default and reinstalled from scratch)
    It wouldn't be a hardware issue since you can play other games without problem.
    Easiest way to tell if it's a hardware issue or not is to run the benchmark tool for example 3DMark 11 and see if the problem also happens during the benchmark.
    For the rendering problem you were talking, please provide not only the problem picture but also the picture without problem to let us make the comparison.
    I'm sorry to say, but some of the picture I'm not really getting what the problem you're talking about.
    For the shadow face, here are few user provided fix which might be helpful.
    http://forums.steampowered.com/forums/showthread.php?t=2282965
    http://forum.bioware.com/topic/55984-shadows-way-too-darkblack-intendedscreenshot-solved/
    Quote
    Re-installing DirectX and PhysX.
    NVIDIA moderator says some of the games is required to play some older Physx games, but not sure if it works.
    If you would like to have a try.
    https://forums.geforce.com/default/topic/524066/geforce-drivers/official-nvidia-r310-61-beta-display-driver-feedback-thread-released-11-20-12-/post/3714758/#3714758
    I'd suggest to post the issue on EA, steam or obioware and see if there are people looking into it.

  • MSI GS70 GTX 765 graphics card issue

     I've been using the laptop for close to 8 months and had no problems with it until I felt the need to plug it to an external monitor via a mini dp to DVi cable. It worked perfectly for a few days. I watched a few seasons of house of cards on it and one day, all of a sudden the external monitor is blank and from here on it doesnt work when connected to an external monitor. i tried the hdmi port instead, i tried the other mini DP port. I also tried a lot of different things like updating the nvidia grpahics, updating the intel graphics, I uninstalled and reinstalled all the drivers, finally after doing all of this and getting no results, i restored the laptop to its factory settings, thinking that this must be a problem that windows 8.1 caused. Even after getting it back to windows 8, its still the same. in the device manager, under display adapter, right next to the nvidia geforce gtx 765m, there's a hazard sign. So that means it detects the graphics card, but unfortunately it doesn't seem to be working. I tried installing a varied bunch of nvidia drivers too, if that means anything . Can anyone point me in the right direction?
    I've posted results I got from GPU-Z. The clock rates of the GPU seem to be at zero. I'm glad that it is getting detected, but there's still the hazard sign in the device manager. What gives? :/

    1. Make sure the mini-DP to DVI cable is not damaged first. Borrow another laptop or machine to try the cable to make sure it's okay.
    2. Remove all NVIDIA drivers and install the NVIDIA driver from here: http://www.msi.com/support/nb/GS70-STEALTH.html#down-driver
       Select your OS to download. Remember to check "Perform a clean installation" while running NVIDIA driver installer.
    3. Press Fn+F2 to manually switch on the video output (MSI shortcut key function).
    4. Press Windows+P to manually switch on the video output (Windows function).
    5. If none of the above worked, update your BIOS & EC & remove all power sources of the laptop & poke the reset hole on the right side. Then power on again.
    6. Try step 3 & 4 again.
    4. If still none of the above worked, I'm afraid you may need to send it to local authorized service point to find & fix the problem.

  • [SOLVED] ATI (open source) Graphics Issue due to Upgrade

    Shadowrun Returns finally loaded (after ages) but performance was abysmal whereas I was playing it with the same settings flawlessly yesterday. L4D2 was "laggy" while clicking in the interface and on the opening video, and then I got sound with a black screen and had to kill the process.
    I believe it is related to a recent update in one of the following packages (at least I did not have this problem yesterday, and I updated first thing this morning):
    [2014-05-06 08:32] [PACMAN] starting full system upgrade
    [2014-05-06 08:32] [PACMAN] upgraded mesa (10.1.1-2 -> 10.1.2-1)
    [2014-05-06 08:32] [PACMAN] upgraded mesa-libgl (10.1.1-2 -> 10.1.2-1)
    [2014-05-06 08:32] [PACMAN] upgraded ati-dri (10.1.1-2 -> 10.1.2-1)
    [2014-05-06 08:32] [PACMAN] upgraded x265 (0.9-1 -> 1.0-1)
    [2014-05-06 08:32] [PACMAN] upgraded ffmpeg (1:2.2.1-1 -> 1:2.2.2-1)
    [2014-05-06 08:32] [PACMAN] upgraded lib32-mesa (10.1.1-1 -> 10.1.2-1)
    [2014-05-06 08:32] [PACMAN] upgraded lib32-mesa-libgl (10.1.1-1 -> 10.1.2-1)
    [2014-05-06 08:32] [PACMAN] upgraded lib32-ati-dri (10.1.1-1 -> 10.1.2-1)
    There doesn't seem to be much useful output when starting Steam from the command line here's the beginning output:
    Running Steam on arch rolling 64-bit
    STEAM_RUNTIME is enabled automatically
    Installing breakpad exception handler for appid(steam)/version(1398287272_client)
    libGL error: dlopen /usr/lib32/xorg/modules/dri/r600_dri.so failed (/home/username/.local/share/Steam/ubuntu12_32/steam-runtime/i386/usr/lib/i386-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /usr/lib32/xorg/modules/dri/r600_dri.so))
    libGL error: unable to load driver: r600_dri.so
    libGL error: driver pointer missing
    libGL error: failed to load driver: r600
    Installing breakpad exception handler for appid(steam)/version(1398287272_client)
    (steam:1501): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita",
    (steam:1501): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita",
    /usr/share/themes/Adwaita/gtk-2.0/gtkrc:1137: error: unexpected identifier `direction', expected character `}'
    Fontconfig error: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 70: non-double matrix element
    Fontconfig error: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 70: non-double matrix element
    Fontconfig warning: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 78: saw unknown, expected number
    My card shouldn't be using the r600 driver (mine is a Radeon HD 5770) and it's quite possible those errors have always been there.
    Any help would be greatly appreciated.
    Last edited by cyrxi (2014-05-06 15:03:55)

    I have similar problem. I have removed steam-runtime libstdc++ libraries (I could not start game with them), but performance is very low. I use open source ati drivers (lib32-ati-dri also installed) and have Radeon 7770. Some time ago I could play Super Meat Boy with good performance, but now even intro is like 5 FPS which is obviously now what I expected. I am rather casual player so I can't say when (after which update as I presume) performance were redused. System is up-to-date.
    I noticed that if I use AccelMethod "EXA" hardware acceleration do not work, with "GLAMOR" I have artefacts (e.g. with title bar and context menu) in KDE, but it run at normal SMB at normal speed. According to Arch Wiki there is a bug in X11 related to GLAMOR.
    Last edited by fenuks (2014-05-10 21:27:11)

  • Nvidia GTX 870M issue on GS70-2PE

    Hi,
    My laptop came back from repairs but now gpu is messing up :( like on my other motherboard my GTX 870M would run just fine no problems but now after repair due to BIOS death on my other motherboard my new motherboard GPU is having trouble with DX11 :/
    When i started bioshock infinite it showed up with flickering textures like lines here and there so i assigned everything to ultra and then it threw error message saying DX11 device removed or Crashed. then i pressed OK and second box came saying Bioshock Infinite has stopped responding and needs to be shutdown :/ so i removed graphics drivers did clean install tried game again and straight away after intro game goes black i hear music for like 20 seconds then this box appears again saying Bioshock Infinite has stopped responding and needs to be shutdown -.- so i tried to install DX11 but got message saying it's already installed so now i'm out of ideas :/ does anyone have fix for this issue?
    /Thanks

    Quote from: JakeSully;113828
    i have 332.38 so when i upgrade i select advanced on 344.11 and then you will find feature list and then a box under big box saying Clean Install if you select that it will then uninstall old drivers and then install new ones and yes issue occures on all drivers no mather which i pick :/
    There are people who share that by using this check box, the drivers are not uninstalled completely and cause some issues, so all drivers have to be uninstalled manually from the Control Panel> Unisntall a program.
    I'm sorry to hear that, a friend of mine owns the GS70 Stealth, she likes it a lot and it runs really well.
    Maybe it's the driver's issue, but we can't test on that now.
    Hope your next notebook will work out fine.

  • [HOWTO] fix throttling/temperature problems of GTX 870m (and probably others)

    Hey,
    The problem:
    Other than repasting and undervolting using a VBIOS mod, you can't do much to prevent the guaranteed 93°C hit on the GS70 with the GTX 870m,
    which results in serious throttling after a short while of full load on the GPU to prevent hardware-damage and thus, while playing, massive FPS drops. Also the mentioned "fixes" only delay the inevitable.
    That's what I thought to be correct - turns out, it isn't.
    This may work for any laptop/card combination with temperature/throttling issues, not only the GS70-2PE + GTX 870m!
    I've found a way to circumvent the 93°C problem on the GS70 with a GTX 870m (may apply to other laptops/cards aswell):
    The NVIDIA driver (and only the driver, not any hardmodded VBIOS) is able to set some stuff about the temperature target, you can't change with a hard mod - I've talked to svet about that.
    Let's have a look some screenshots I took:
    Screenshot #1 - default behaviour:
    On the first screenshot you see the default behaviour of a brand new GS70-2PE with a GTX 870m - not repasted. It was taken right after I took the second screenshot, so there's still some amount of data left on the charts from before.
    Have a look at the "GPU Core Clock" in GPU-Z. You'll notice big spikes (which go down to about 480 MHz) on the right hand side of the graph. That's the throttling the card automatically does when it's hit its 93°C temperature for about a minute. That are lag-spikes when playing something demanding.
    You also notice on the "PerfCap Reason" row - when it was throttling in the "GPU Core Clock" row no soft performance cap was induced so this was done by the card (or the EC?) internally (that's the empty space on the right hand side of the chart).
    Now let's look at the second screenshot.
    Screenshot #2 - fixing things:
    Notice the difference on the right hand side of both screenshots' "GPU Core Clock" charts. See the spike-downs gone in the second screenshot?
    You can also see, that compared to the first chart, the driver has reduced the voltage to reach the Temperature Target while the clock rate was reduced.
    Here I've slightly lowered the base clock of the GPU by -40 MHz, aswell as reduced the Voltage Offset by -18.8 mV. (Both settings may not even be necessary, please report your results)
    This is the important part:
    Additionally I've set the Temperature Target as priorized over the Power Target, and set the Temperature Target to 90°C.
    As you can see when the GPU hits 91°C, after a couple of seconds it will clock down, but controlled by the driver (you can see that in the "PerfCap Reason" chart). It's not as bad as the drop to 450 MHz, it's just a 100 MHz drop, to about 810 MHz in my case. It stays there until it reaches a temperature of about 86°C, stays there a bit, clocks up again, and so on. (The clock values you see don't reflect the 810 MHz, the screenshot was taken while the PerfCap was not in effect)
    Results
    What have we gained?
    No massive last-resort throttling by the card itself, but a small clock drop induced by the NVIDIA driver to meet our desired temperature target. A huge all-around performance improvement when the card gets hot and less FPS drops when playing for a long time or a GPU hungry game.
    What have we lost?
    Some few seconds of boost clock as the card clocks down a bit earlier. Also in my case I've lost 40 MHz of base clock (that may not even be necessary).
    Combine that with a decent repasting and I'd call my GS70-2PE with a GTX 870m "stable" and reasonably fast on full GPU load.
    By pressing the "Create Clocks Shortcut" button in NVIDIA Inspector those settings will be set on boot.
    Please tell me what you think. Any improvements and experiences welcome.
    panni

    Quote from: bahadir.onc on 24-September-14, 18:37:57
    Hey everyone!
    I downloaded nvidia inspector to apply this fix,but shocked to see in default behaviour my Voltage Offset was -68.8. Should I change that? There is a big difference with the value the fix provides and my default value..
    Also,I consider repasting with IC Diamond. Should I?
    Hey,
    the offset shouldn't matter - inspector showed some weird behaviour when modifying and/or initially setting it. Try to apply my fix and don't do anything to the offset as a first try to be safe. It shouldn't matter nevertheless, as we're talking about a very small millivolts value, nothing big.
    Regarding repasting with IC Diamond: I've had great success in "repasting" using Liquid MetalPad - you might want to consider this.

  • Graphics issue in Heroes of Newerth

    Hi,
    I just installed hon but due to a graphical issue I can't play it:
    Anyone already had this problem and was able to solve it?
    Graphics card is a Geforce GTX 460 (275.09.07)
    \edit: Answered by myself - the bug is known:
    http://forums.heroesofnewerth.com/showt … st13921576
    Last edited by Barghest (2011-07-17 14:22:06)

    Hi,
    I just installed hon but due to a graphical issue I can't play it:
    Anyone already had this problem and was able to solve it?
    Graphics card is a Geforce GTX 460 (275.09.07)
    \edit: Answered by myself - the bug is known:
    http://forums.heroesofnewerth.com/showt … st13921576
    Last edited by Barghest (2011-07-17 14:22:06)

  • GDM and Gnome graphical issues with Nvidia card

    Hi !
    I want to install archlinux with cinnamon as desktop environment on the computer of a friend, but I have some issue with it, and especially with (I think) the graphic card, it's a Nvidia GeForce FX 5200LE.
    I tried installing nvidia-173xx from the aur first. I installed gdm, but it's extremly slow, as a result that I can't log in (nevertheless the mouse is fluid..)  the cpu is not so much used yet, and it's the same thing in the cinnamon session or the gnome session (I tried installing lightdm to log in which works fine). Moreover, in the session I've got some strange graphical things, such as some missing white pixels, or a blue window when I launch nautilus, ... (here are some screenshots : http://i49.tinypic.com/2efhm6s.png and a with a window : http://i46.tinypic.com/116m05k.png)
    I tried to install the nouveau driver instead, and now gdm don't freeze, I can log in, but there is always these strange graphical issues.
    Is the graphic card too old for gnome ? Or did I forget something ?
    Thank you in advance for your help !! And sorry for my english ..
    Here are some log with the nouveau driver :
    - Xorg.log :
    [ 9.026]
    X.Org X Server 1.12.4
    Release Date: 2012-08-27
    [ 9.026] X Protocol Version 11, Revision 0
    [ 9.026] Build Operating System: Linux 3.4.8-1-ARCH i686
    [ 9.026] Current Operating System: Linux famille-workstation 3.5.3-1-ARCH #1 SMP PREEMPT Sun Aug 26 08:15:06 UTC 2012 i686
    [ 9.026] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=83840f06-da6c-4558-a8ef-8ed779442ff3 ro quiet pci=nomsi
    [ 9.026] Build Date: 27 August 2012 08:08:29AM
    [ 9.026]
    [ 9.026] Current version of pixman: 0.26.2
    [ 9.026] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 9.026] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 9.027] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Sep 5 13:26:01 2012
    [ 9.053] (==) Using config file: "/etc/X11/xorg.conf"
    [ 9.053] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 9.072] (==) No Layout section. Using the first Screen section.
    [ 9.072] (==) No screen section available. Using defaults.
    [ 9.072] (**) |-->Screen "Default Screen Section" (0)
    [ 9.072] (**) | |-->Monitor "<default monitor>"
    [ 9.074] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    [ 9.074] (**) Option "AIGLX" "off"
    [ 9.074] (==) Automatically adding devices
    [ 9.074] (==) Automatically enabling devices
    [ 9.127] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/OTF/".
    [ 9.127] Entry deleted from font path.
    [ 9.128] (Run 'mkfontdir' on "/usr/share/fonts/OTF/").
    [ 9.128] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/Type1/".
    [ 9.128] Entry deleted from font path.
    [ 9.128] (Run 'mkfontdir' on "/usr/share/fonts/Type1/").
    [ 9.128] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/100dpi/,
    /usr/share/fonts/75dpi/
    [ 9.128] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 9.128] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 9.128] (II) Loader magic: 0x82225a0
    [ 9.128] (II) Module ABI versions:
    [ 9.128] X.Org ANSI C Emulation: 0.4
    [ 9.128] X.Org Video Driver: 12.1
    [ 9.128] X.Org XInput driver : 16.0
    [ 9.128] X.Org Server Extension : 6.0
    [ 9.129] (--) PCI:*(0:1:0:0) 10de:0323:107d:1334 rev 161, Mem @ 0xe0000000/16777216, 0xd8000000/134217728, BIOS @ 0x????????/131072
    [ 9.129] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    [ 9.129] (II) LoadModule: "extmod"
    [ 9.145] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
    [ 9.156] (II) Module extmod: vendor="X.Org Foundation"
    [ 9.156] compiled for 1.12.4, module version = 1.0.0
    [ 9.156] Module class: X.Org Server Extension
    [ 9.156] ABI class: X.Org Server Extension, version 6.0
    [ 9.156] (II) Loading extension MIT-SCREEN-SAVER
    [ 9.156] (II) Loading extension XFree86-VidModeExtension
    [ 9.156] (II) Loading extension XFree86-DGA
    [ 9.156] (II) Loading extension DPMS
    [ 9.156] (II) Loading extension XVideo
    [ 9.156] (II) Loading extension XVideo-MotionCompensation
    [ 9.156] (II) Loading extension X-Resource
    [ 9.156] (II) LoadModule: "dbe"
    [ 9.157] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
    [ 9.157] (II) Module dbe: vendor="X.Org Foundation"
    [ 9.157] compiled for 1.12.4, module version = 1.0.0
    [ 9.157] Module class: X.Org Server Extension
    [ 9.157] ABI class: X.Org Server Extension, version 6.0
    [ 9.157] (II) Loading extension DOUBLE-BUFFER
    [ 9.157] (II) LoadModule: "glx"
    [ 9.157] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 9.164] (II) Module glx: vendor="X.Org Foundation"
    [ 9.164] compiled for 1.12.4, module version = 1.0.0
    [ 9.164] ABI class: X.Org Server Extension, version 6.0
    [ 9.164] (**) AIGLX disabled
    [ 9.165] (II) Loading extension GLX
    [ 9.165] (II) LoadModule: "record"
    [ 9.165] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
    [ 9.166] (II) Module record: vendor="X.Org Foundation"
    [ 9.166] compiled for 1.12.4, module version = 1.13.0
    [ 9.166] Module class: X.Org Server Extension
    [ 9.166] ABI class: X.Org Server Extension, version 6.0
    [ 9.166] (II) Loading extension RECORD
    [ 9.166] (II) LoadModule: "dri"
    [ 9.166] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
    [ 9.172] (II) Module dri: vendor="X.Org Foundation"
    [ 9.172] compiled for 1.12.4, module version = 1.0.0
    [ 9.172] ABI class: X.Org Server Extension, version 6.0
    [ 9.172] (II) Loading extension XFree86-DRI
    [ 9.172] (II) LoadModule: "dri2"
    [ 9.172] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
    [ 9.173] (II) Module dri2: vendor="X.Org Foundation"
    [ 9.173] compiled for 1.12.4, module version = 1.2.0
    [ 9.173] ABI class: X.Org Server Extension, version 6.0
    [ 9.173] (II) Loading extension DRI2
    [ 9.173] (==) Matched nouveau as autoconfigured driver 0
    [ 9.173] (==) Matched nvidia as autoconfigured driver 1
    [ 9.173] (==) Matched nv as autoconfigured driver 2
    [ 9.173] (==) Matched vesa as autoconfigured driver 3
    [ 9.173] (==) Matched fbdev as autoconfigured driver 4
    [ 9.173] (==) Assigned the driver to the xf86ConfigLayout
    [ 9.173] (II) LoadModule: "nouveau"
    [ 9.180] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
    [ 9.191] (II) Module nouveau: vendor="X.Org Foundation"
    [ 9.191] compiled for 1.12.2, module version = 1.0.1
    [ 9.191] Module class: X.Org Video Driver
    [ 9.191] ABI class: X.Org Video Driver, version 12.0
    [ 9.191] (II) LoadModule: "nvidia"
    [ 9.191] (WW) Warning, couldn't open module nvidia
    [ 9.191] (II) UnloadModule: "nvidia"
    [ 9.191] (II) Unloading nvidia
    [ 9.192] (EE) Failed to load module "nvidia" (module does not exist, 0)
    [ 9.192] (II) LoadModule: "nv"
    [ 9.192] (WW) Warning, couldn't open module nv
    [ 9.192] (II) UnloadModule: "nv"
    [ 9.192] (II) Unloading nv
    [ 9.192] (EE) Failed to load module "nv" (module does not exist, 0)
    [ 9.192] (II) LoadModule: "vesa"
    [ 9.192] (WW) Warning, couldn't open module vesa
    [ 9.192] (II) UnloadModule: "vesa"
    [ 9.192] (II) Unloading vesa
    [ 9.192] (EE) Failed to load module "vesa" (module does not exist, 0)
    [ 9.192] (II) LoadModule: "fbdev"
    [ 9.193] (WW) Warning, couldn't open module fbdev
    [ 9.193] (II) UnloadModule: "fbdev"
    [ 9.193] (II) Unloading fbdev
    [ 9.193] (EE) Failed to load module "fbdev" (module does not exist, 0)
    [ 9.193] (II) NOUVEAU driver
    [ 9.193] (II) NOUVEAU driver for NVIDIA chipset families :
    [ 9.193] RIVA TNT (NV04)
    [ 9.193] RIVA TNT2 (NV05)
    [ 9.193] GeForce 256 (NV10)
    [ 9.193] GeForce 2 (NV11, NV15)
    [ 9.193] GeForce 4MX (NV17, NV18)
    [ 9.193] GeForce 3 (NV20)
    [ 9.193] GeForce 4Ti (NV25, NV28)
    [ 9.193] GeForce FX (NV3x)
    [ 9.193] GeForce 6 (NV4x)
    [ 9.193] GeForce 7 (G7x)
    [ 9.193] GeForce 8 (G8x)
    [ 9.193] GeForce GTX 200 (NVA0)
    [ 9.193] GeForce GTX 400 (NVC0)
    [ 9.193] (++) using VT number 7
    [ 9.196] drmOpenDevice: node name is /dev/dri/card0
    [ 9.196] drmOpenDevice: open result is 7, (OK)
    [ 9.196] drmOpenByBusid: Searching for BusID pci:0000:01:00.0
    [ 9.196] drmOpenDevice: node name is /dev/dri/card0
    [ 9.196] drmOpenDevice: open result is 7, (OK)
    [ 9.196] drmOpenByBusid: drmOpenMinor returns 7
    [ 9.196] drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
    [ 9.196] (II) [drm] nouveau interface version: 1.0.0
    [ 9.196] (II) Loading sub module "dri"
    [ 9.196] (II) LoadModule: "dri"
    [ 9.197] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
    [ 9.197] (II) Module dri: vendor="X.Org Foundation"
    [ 9.197] compiled for 1.12.4, module version = 1.0.0
    [ 9.197] ABI class: X.Org Server Extension, version 6.0
    [ 9.197] (II) NOUVEAU(0): Loaded DRI module
    [ 9.197] drmOpenDevice: node name is /dev/dri/card0
    [ 9.197] drmOpenDevice: open result is 8, (OK)
    [ 9.197] drmOpenDevice: node name is /dev/dri/card0
    [ 9.197] drmOpenDevice: open result is 8, (OK)
    [ 9.197] drmOpenByBusid: Searching for BusID pci:0000:01:00.0
    [ 9.197] drmOpenDevice: node name is /dev/dri/card0
    [ 9.197] drmOpenDevice: open result is 8, (OK)
    [ 9.197] drmOpenByBusid: drmOpenMinor returns 8
    [ 9.197] drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
    [ 9.197] (II) [drm] DRM interface version 1.4
    [ 9.197] (II) [drm] DRM open master succeeded.
    [ 9.197] (--) NOUVEAU(0): Chipset: "NVIDIA NV34"
    [ 9.197] (II) NOUVEAU(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
    [ 9.197] (==) NOUVEAU(0): Depth 24, (--) framebuffer bpp 32
    [ 9.197] (==) NOUVEAU(0): RGB weight 888
    [ 9.197] (==) NOUVEAU(0): Default visual is TrueColor
    [ 9.197] (==) NOUVEAU(0): Using HW cursor
    [ 9.197] (==) NOUVEAU(0): GLX sync to VBlank disabled.
    [ 9.197] (==) NOUVEAU(0): Page flipping enabled
    [ 9.197] (==) NOUVEAU(0): Swap limit set to 2 [Max allowed 2]
    [ 9.227] (II) NOUVEAU(0): Output VGA-1 has no monitor section
    [ 9.280] (II) NOUVEAU(0): Output TV-1 has no monitor section
    [ 9.309] (II) NOUVEAU(0): EDID for output VGA-1
    [ 9.309] (II) NOUVEAU(0): Manufacturer: SAM Model: 1b Serial#: 1195913527
    [ 9.309] (II) NOUVEAU(0): Year: 2003 Week: 16
    [ 9.309] (II) NOUVEAU(0): EDID Version: 1.3
    [ 9.309] (II) NOUVEAU(0): Analog Display Input, Input Voltage Level: 0.700/0.300 V
    [ 9.309] (II) NOUVEAU(0): Sync: Separate Composite SyncOnGreenSerration on. V.Sync Pulse req. if CompSync or SyncOnGreen
    [ 9.309] (II) NOUVEAU(0): Max Image Size [cm]: horiz.: 34 vert.: 27
    [ 9.309] (II) NOUVEAU(0): Gamma: 2.40
    [ 9.309] (II) NOUVEAU(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
    [ 9.309] (II) NOUVEAU(0): First detailed timing is preferred mode
    [ 9.309] (II) NOUVEAU(0): redX: 0.634 redY: 0.354 greenX: 0.304 greenY: 0.581
    [ 9.309] (II) NOUVEAU(0): blueX: 0.143 blueY: 0.102 whiteX: 0.318 whiteY: 0.339
    [ 9.309] (II) NOUVEAU(0): Supported established timings:
    [ 9.309] (II) NOUVEAU(0): 720x400@70Hz
    [ 9.309] (II) NOUVEAU(0): 640x480@60Hz
    [ 9.309] (II) NOUVEAU(0): 640x480@67Hz
    [ 9.309] (II) NOUVEAU(0): 640x480@72Hz
    [ 9.310] (II) NOUVEAU(0): 640x480@75Hz
    [ 9.310] (II) NOUVEAU(0): 800x600@56Hz
    [ 9.310] (II) NOUVEAU(0): 800x600@60Hz
    [ 9.310] (II) NOUVEAU(0): 800x600@72Hz
    [ 9.310] (II) NOUVEAU(0): 800x600@75Hz
    [ 9.310] (II) NOUVEAU(0): 832x624@75Hz
    [ 9.310] (II) NOUVEAU(0): 1024x768@60Hz
    [ 9.310] (II) NOUVEAU(0): 1024x768@70Hz
    [ 9.310] (II) NOUVEAU(0): 1024x768@75Hz
    [ 9.310] (II) NOUVEAU(0): 1280x1024@75Hz
    [ 9.310] (II) NOUVEAU(0): 1152x864@75Hz
    [ 9.310] (II) NOUVEAU(0): Manufacturer's mask: 0
    [ 9.310] (II) NOUVEAU(0): Supported standard timings:
    [ 9.310] (II) NOUVEAU(0): #0: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
    [ 9.310] (II) NOUVEAU(0): #1: hsize: 1024 vsize 768 refresh: 60 vid: 16481
    [ 9.310] (II) NOUVEAU(0): #2: hsize: 800 vsize 600 refresh: 60 vid: 16453
    [ 9.310] (II) NOUVEAU(0): #3: hsize: 640 vsize 480 refresh: 60 vid: 16433
    [ 9.310] (II) NOUVEAU(0): Supported detailed timing:
    [ 9.310] (II) NOUVEAU(0): clock: 108.0 MHz Image Size: 338 x 270 mm
    [ 9.310] (II) NOUVEAU(0): h_active: 1280 h_sync: 1328 h_sync_end 1440 h_blank_end 1688 h_border: 0
    [ 9.310] (II) NOUVEAU(0): v_active: 1024 v_sync: 1025 v_sync_end 1028 v_blanking: 1066 v_border: 0
    [ 9.310] (II) NOUVEAU(0): Ranges: V min: 56 V max: 76 Hz, H min: 30 H max: 81 kHz, PixClock max 145 MHz
    [ 9.310] (II) NOUVEAU(0): Monitor name: SyncMaster
    [ 9.310] (II) NOUVEAU(0): Serial No: HJGW403719
    [ 9.310] (II) NOUVEAU(0): EDID (in hex):
    [ 9.310] (II) NOUVEAU(0): 00ffffffffffff004c2d1b0037314847
    [ 9.310] (II) NOUVEAU(0): 100d01030f221b8cea6f8ba25a4d9424
    [ 9.310] (II) NOUVEAU(0): 1a5156bfef8081806140454031400101
    [ 9.310] (II) NOUVEAU(0): 010101010101302a009851002a403070
    [ 9.310] (II) NOUVEAU(0): 1300520e1100001e000000fd00384c1e
    [ 9.310] (II) NOUVEAU(0): 510e000a202020202020000000fc0053
    [ 9.310] (II) NOUVEAU(0): 796e634d61737465720a2020000000ff
    [ 9.310] (II) NOUVEAU(0): 00484a47573430333731390a20200057
    [ 9.310] (II) NOUVEAU(0): EDID vendor "SAM", prod id 27
    [ 9.310] (II) NOUVEAU(0): Using EDID range info for horizontal sync
    [ 9.310] (II) NOUVEAU(0): Using EDID range info for vertical refresh
    [ 9.310] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 9.310] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
    [ 9.310] (II) NOUVEAU(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 9.310] (II) NOUVEAU(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 9.310] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 9.310] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e)
    [ 9.310] (II) NOUVEAU(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
    [ 9.310] (II) NOUVEAU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 9.311] (II) NOUVEAU(0): Printing probed modes for output VGA-1
    [ 9.311] (II) NOUVEAU(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
    [ 9.311] (II) NOUVEAU(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "1280x800"x74.9 106.50 1280 1360 1488 1696 800 803 809 838 -hsync +vsync (62.8 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "1280x800"x59.8 83.50 1280 1352 1480 1680 800 803 809 831 +hsync -vsync (49.7 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "1280x768"x74.9 102.25 1280 1360 1488 1696 768 771 778 805 +hsync -vsync (60.3 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "1280x768"x59.9 79.50 1280 1344 1472 1664 768 771 778 798 -hsync +vsync (47.8 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "1024x576"x60.0 46.97 1024 1064 1168 1312 576 577 580 597 -hsync +vsync (35.8 kHz)
    [ 9.311] (II) NOUVEAU(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "848x480"x60.0 33.75 848 864 976 1088 480 486 494 517 +hsync +vsync (31.0 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 491 520 -hsync -vsync (37.9 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "640x480"x66.7 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 489 492 525 -hsync -vsync (31.5 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 9.363] (II) NOUVEAU(0): EDID for output TV-1
    [ 9.363] (II) NOUVEAU(0): Output VGA-1 connected
    [ 9.363] (II) NOUVEAU(0): Output TV-1 disconnected
    [ 9.363] (II) NOUVEAU(0): Using exact sizes for initial modes
    [ 9.363] (II) NOUVEAU(0): Output VGA-1 using initial mode 1280x1024
    [ 9.363] (II) NOUVEAU(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
    [ 9.363] (--) NOUVEAU(0): Virtual size is 1280x1024 (pitch 0)
    [ 9.363] (**) NOUVEAU(0): Driver mode "1280x1024": 108.0 MHz (scaled from 0.0 MHz), 64.0 kHz, 60.0 Hz
    [ 9.363] (II) NOUVEAU(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
    [ 9.363] (**) NOUVEAU(0): Driver mode "1280x1024": 135.0 MHz (scaled from 0.0 MHz), 80.0 kHz, 75.0 Hz
    [ 9.363] (II) NOUVEAU(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 9.363] (**) NOUVEAU(0): Driver mode "1280x960": 108.0 MHz (scaled from 0.0 MHz), 60.0 kHz, 60.0 Hz
    [ 9.363] (II) NOUVEAU(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 9.363] (**) NOUVEAU(0): Driver mode "1280x800": 106.5 MHz (scaled from 0.0 MHz), 62.8 kHz, 74.9 Hz
    [ 9.363] (II) NOUVEAU(0): Modeline "1280x800"x74.9 106.50 1280 1360 1488 1696 800 803 809 838 -hsync +vsync (62.8 kHz e)
    [ 9.363] (**) NOUVEAU(0): Driver mode "1280x800": 83.5 MHz (scaled from 0.0 MHz), 49.7 kHz, 59.8 Hz
    [ 9.363] (II) NOUVEAU(0): Modeline "1280x800"x59.8 83.50 1280 1352 1480 1680 800 803 809 831 +hsync -vsync (49.7 kHz e)
    [ 9.363] (**) NOUVEAU(0): Driver mode "1152x864": 108.0 MHz (scaled from 0.0 MHz), 67.5 kHz, 75.0 Hz
    [ 9.363] (II) NOUVEAU(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 9.363] (**) NOUVEAU(0): Driver mode "1280x768": 102.2 MHz (scaled from 0.0 MHz), 60.3 kHz, 74.9 Hz
    [ 9.363] (II) NOUVEAU(0): Modeline "1280x768"x74.9 102.25 1280 1360 1488 1696 768 771 778 805 +hsync -vsync (60.3 kHz e)
    [ 9.363] (**) NOUVEAU(0): Driver mode "1280x768": 79.5 MHz (scaled from 0.0 MHz), 47.8 kHz, 59.9 Hz
    [ 9.363] (II) NOUVEAU(0): Modeline "1280x768"x59.9 79.50 1280 1344 1472 1664 768 771 778 798 -hsync +vsync (47.8 kHz e)
    [ 9.363] (**) NOUVEAU(0): Driver mode "1024x768": 78.8 MHz (scaled from 0.0 MHz), 60.1 kHz, 75.1 Hz
    [ 9.363] (II) NOUVEAU(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
    [ 9.363] (**) NOUVEAU(0): Driver mode "1024x768": 75.0 MHz (scaled from 0.0 MHz), 56.5 kHz, 70.1 Hz
    [ 9.363] (II) NOUVEAU(0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
    [ 9.363] (**) NOUVEAU(0): Driver mode "1024x768": 65.0 MHz (scaled from 0.0 MHz), 48.4 kHz, 60.0 Hz
    [ 9.364] (II) NOUVEAU(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 9.364] (**) NOUVEAU(0): Mode "1024x576": 47.0 MHz (scaled from 0.0 MHz), 35.8 kHz, 60.0 Hz
    [ 9.364] (II) NOUVEAU(0): Modeline "1024x576"x60.0 46.97 1024 1064 1168 1312 576 577 580 597 -hsync +vsync (35.8 kHz)
    [ 9.364] (**) NOUVEAU(0): Driver mode "832x624": 57.3 MHz (scaled from 0.0 MHz), 49.7 kHz, 74.6 Hz
    [ 9.364] (II) NOUVEAU(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
    [ 9.364] (**) NOUVEAU(0): Driver mode "800x600": 50.0 MHz (scaled from 0.0 MHz), 48.1 kHz, 72.2 Hz
    [ 9.364] (II) NOUVEAU(0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
    [ 9.364] (**) NOUVEAU(0): Driver mode "800x600": 49.5 MHz (scaled from 0.0 MHz), 46.9 kHz, 75.0 Hz
    [ 9.364] (II) NOUVEAU(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 9.364] (**) NOUVEAU(0): Driver mode "800x600": 40.0 MHz (scaled from 0.0 MHz), 37.9 kHz, 60.3 Hz
    [ 9.364] (II) NOUVEAU(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 9.364] (**) NOUVEAU(0): Driver mode "800x600": 36.0 MHz (scaled from 0.0 MHz), 35.2 kHz, 56.2 Hz
    [ 9.364] (II) NOUVEAU(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 9.364] (**) NOUVEAU(0): Driver mode "848x480": 33.8 MHz (scaled from 0.0 MHz), 31.0 kHz, 60.0 Hz
    [ 9.364] (II) NOUVEAU(0): Modeline "848x480"x60.0 33.75 848 864 976 1088 480 486 494 517 +hsync +vsync (31.0 kHz e)
    [ 9.364] (**) NOUVEAU(0): Driver mode "640x480": 31.5 MHz (scaled from 0.0 MHz), 37.9 kHz, 72.8 Hz
    [ 9.364] (II) NOUVEAU(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 491 520 -hsync -vsync (37.9 kHz e)
    [ 9.364] (**) NOUVEAU(0): Driver mode "640x480": 31.5 MHz (scaled from 0.0 MHz), 37.5 kHz, 75.0 Hz
    [ 9.364] (II) NOUVEAU(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 9.364] (**) NOUVEAU(0): Driver mode "640x480": 30.2 MHz (scaled from 0.0 MHz), 35.0 kHz, 66.7 Hz
    [ 9.364] (II) NOUVEAU(0): Modeline "640x480"x66.7 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
    [ 9.364] (**) NOUVEAU(0): Driver mode "640x480": 25.2 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
    [ 9.364] (II) NOUVEAU(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 9.364] (**) NOUVEAU(0): Driver mode "640x480": 25.2 MHz (scaled from 0.0 MHz), 31.5 kHz, 59.9 Hz
    [ 9.364] (II) NOUVEAU(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 489 492 525 -hsync -vsync (31.5 kHz e)
    [ 9.364] (**) NOUVEAU(0): Driver mode "720x400": 28.3 MHz (scaled from 0.0 MHz), 31.5 kHz, 70.1 Hz
    [ 9.364] (II) NOUVEAU(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 9.364] (**) NOUVEAU(0): Display dimensions: (340, 270) mm
    [ 9.364] (**) NOUVEAU(0): DPI set to (95, 96)
    [ 9.364] (II) Loading sub module "fb"
    [ 9.364] (II) LoadModule: "fb"
    [ 9.364] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 9.375] (II) Module fb: vendor="X.Org Foundation"
    [ 9.375] compiled for 1.12.4, module version = 1.0.0
    [ 9.375] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 9.375] (II) Loading sub module "exa"
    [ 9.375] (II) LoadModule: "exa"
    [ 9.376] (II) Loading /usr/lib/xorg/modules/libexa.so
    [ 9.380] (II) Module exa: vendor="X.Org Foundation"
    [ 9.380] compiled for 1.12.4, module version = 2.5.0
    [ 9.380] ABI class: X.Org Video Driver, version 12.1
    [ 9.380] (II) Loading sub module "shadowfb"
    [ 9.380] (II) LoadModule: "shadowfb"
    [ 9.380] (II) Loading /usr/lib/xorg/modules/libshadowfb.so
    [ 9.382] (II) Module shadowfb: vendor="X.Org Foundation"
    [ 9.382] compiled for 1.12.4, module version = 1.0.0
    [ 9.382] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 9.382] (--) Depth 24 pixmap format is 32 bpp
    [ 9.382] (II) NOUVEAU(0): Opened GPU channel 1
    [ 9.384] (II) NOUVEAU(0): [DRI2] Setup complete
    [ 9.384] (II) NOUVEAU(0): [DRI2] DRI driver: nouveau
    [ 9.384] (II) NOUVEAU(0): [DRI2] VDPAU driver: nouveau
    [ 9.399] (II) EXA(0): Driver allocated offscreen pixmaps
    [ 9.399] (II) EXA(0): Driver registered support for the following operations:
    [ 9.399] (II) Solid
    [ 9.399] (II) Copy
    [ 9.399] (II) Composite (RENDER acceleration)
    [ 9.399] (II) UploadToScreen
    [ 9.399] (II) DownloadFromScreen
    [ 9.399] (==) NOUVEAU(0): Backing store disabled
    [ 9.399] (==) NOUVEAU(0): Silken mouse enabled
    [ 9.399] (II) NOUVEAU(0): [XvMC] Associated with NV30 texture adapter.
    [ 9.399] (II) NOUVEAU(0): [XvMC] Extension initialized.
    [ 9.399] (==) NOUVEAU(0): DPMS enabled
    [ 9.399] (II) NOUVEAU(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    [ 9.399] (--) RandR disabled
    [ 9.399] (II) Initializing built-in extension Generic Event Extension
    [ 9.399] (II) Initializing built-in extension SHAPE
    [ 9.399] (II) Initializing built-in extension MIT-SHM
    [ 9.400] (II) Initializing built-in extension XInputExtension
    [ 9.400] (II) Initializing built-in extension XTEST
    [ 9.400] (II) Initializing built-in extension BIG-REQUESTS
    [ 9.400] (II) Initializing built-in extension SYNC
    [ 9.400] (II) Initializing built-in extension XKEYBOARD
    [ 9.400] (II) Initializing built-in extension XC-MISC
    [ 9.400] (II) Initializing built-in extension SECURITY
    [ 9.400] (II) Initializing built-in extension XINERAMA
    [ 9.400] (II) Initializing built-in extension XFIXES
    [ 9.400] (II) Initializing built-in extension RENDER
    [ 9.400] (II) Initializing built-in extension RANDR
    [ 9.400] (II) Initializing built-in extension COMPOSITE
    [ 9.400] (II) Initializing built-in extension DAMAGE
    [ 9.800] (II) AIGLX: Loaded and initialized swrast
    [ 9.800] (II) GLX: Initialized DRISWRAST GL provider for screen 0
    [ 9.807] (II) NOUVEAU(0): NVEnterVT is called.
    [ 9.807] (II) NOUVEAU(0): Setting screen physical size to 338 x 270
    [ 9.807] resize called 1280 1024
    [ 10.066] (II) config/udev: Adding input device Power Button (/dev/input/event2)
    [ 10.066] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 10.066] (II) LoadModule: "evdev"
    [ 10.066] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 10.075] (II) Module evdev: vendor="X.Org Foundation"
    [ 10.075] compiled for 1.12.3.901, module version = 2.7.3
    [ 10.075] Module class: X.Org XInput Driver
    [ 10.075] ABI class: X.Org XInput driver, version 16.0
    [ 10.075] (II) Using input driver 'evdev' for 'Power Button'
    [ 10.076] (**) Power Button: always reports core events
    [ 10.076] (**) evdev: Power Button: Device: "/dev/input/event2"
    [ 10.076] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 10.076] (--) evdev: Power Button: Found keys
    [ 10.076] (II) evdev: Power Button: Configuring as keyboard
    [ 10.076] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event2"
    [ 10.076] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    [ 10.076] (**) Option "xkb_rules" "evdev"
    [ 10.076] (**) Option "xkb_model" "evdev"
    [ 10.076] (**) Option "xkb_layout" "us"
    [ 10.117] (II) config/udev: Adding input device Power Button (/dev/input/event1)
    [ 10.117] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 10.117] (II) Using input driver 'evdev' for 'Power Button'
    [ 10.117] (**) Power Button: always reports core events
    [ 10.117] (**) evdev: Power Button: Device: "/dev/input/event1"
    [ 10.118] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 10.118] (--) evdev: Power Button: Found keys
    [ 10.118] (II) evdev: Power Button: Configuring as keyboard
    [ 10.118] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input1/event1"
    [ 10.118] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
    [ 10.118] (**) Option "xkb_rules" "evdev"
    [ 10.118] (**) Option "xkb_model" "evdev"
    [ 10.118] (**) Option "xkb_layout" "us"
    [ 10.118] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
    [ 10.118] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
    [ 10.118] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
    [ 10.119] (**) AT Translated Set 2 keyboard: always reports core events
    [ 10.119] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
    [ 10.119] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
    [ 10.119] (--) evdev: AT Translated Set 2 keyboard: Found keys
    [ 10.119] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
    [ 10.119] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
    [ 10.119] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 8)
    [ 10.119] (**) Option "xkb_rules" "evdev"
    [ 10.119] (**) Option "xkb_model" "evdev"
    [ 10.119] (**) Option "xkb_layout" "us"
    [ 10.120] (II) config/udev: Adding input device ImPS/2 Logitech Wheel Mouse (/dev/input/event4)
    [ 10.120] (**) ImPS/2 Logitech Wheel Mouse: Applying InputClass "evdev pointer catchall"
    [ 10.120] (II) Using input driver 'evdev' for 'ImPS/2 Logitech Wheel Mouse'
    [ 10.120] (**) ImPS/2 Logitech Wheel Mouse: always reports core events
    [ 10.120] (**) evdev: ImPS/2 Logitech Wheel Mouse: Device: "/dev/input/event4"
    [ 10.120] (--) evdev: ImPS/2 Logitech Wheel Mouse: Vendor 0x2 Product 0x5
    [ 10.120] (--) evdev: ImPS/2 Logitech Wheel Mouse: Found 3 mouse buttons
    [ 10.120] (--) evdev: ImPS/2 Logitech Wheel Mouse: Found scroll wheel(s)
    [ 10.120] (--) evdev: ImPS/2 Logitech Wheel Mouse: Found relative axes
    [ 10.120] (--) evdev: ImPS/2 Logitech Wheel Mouse: Found x and y relative axes
    [ 10.120] (II) evdev: ImPS/2 Logitech Wheel Mouse: Configuring as mouse
    [ 10.120] (II) evdev: ImPS/2 Logitech Wheel Mouse: Adding scrollwheel support
    [ 10.120] (**) evdev: ImPS/2 Logitech Wheel Mouse: YAxisMapping: buttons 4 and 5
    [ 10.120] (**) evdev: ImPS/2 Logitech Wheel Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 10.120] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input4/event4"
    [ 10.120] (II) XINPUT: Adding extended input device "ImPS/2 Logitech Wheel Mouse" (type: MOUSE, id 9)
    [ 10.120] (II) evdev: ImPS/2 Logitech Wheel Mouse: initialized for relative axes.
    [ 10.120] (**) ImPS/2 Logitech Wheel Mouse: (accel) keeping acceleration scheme 1
    [ 10.120] (**) ImPS/2 Logitech Wheel Mouse: (accel) acceleration profile 0
    [ 10.120] (**) ImPS/2 Logitech Wheel Mouse: (accel) acceleration factor: 2.000
    [ 10.120] (**) ImPS/2 Logitech Wheel Mouse: (accel) acceleration threshold: 4
    [ 10.121] (II) config/udev: Adding input device ImPS/2 Logitech Wheel Mouse (/dev/input/mouse0)
    [ 10.121] (II) No input driver specified, ignoring this device.
    [ 10.121] (II) This device may have been added with another device file.
    [ 10.121] (II) config/udev: Adding input device PC Speaker (/dev/input/event3)
    [ 10.121] (II) No input driver specified, ignoring this device.
    [ 10.121] (II) This device may have been added with another device file.
    [ 10.174] (II) NOUVEAU(0): EDID vendor "SAM", prod id 27
    [ 10.174] (II) NOUVEAU(0): Using hsync ranges from config file
    [ 10.174] (II) NOUVEAU(0): Using vrefresh ranges from config file
    [ 10.174] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 10.174] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
    [ 10.174] (II) NOUVEAU(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 10.174] (II) NOUVEAU(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 10.174] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 10.174] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e)
    [ 10.174] (II) NOUVEAU(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
    [ 10.174] (II) NOUVEAU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 10.174] (II) NOUVEAU(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 10.174] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 10.174] (II) NOUVEAU(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
    [ 10.174] (II) NOUVEAU(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
    [ 10.174] (II) NOUVEAU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 10.174] (II) NOUVEAU(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
    [ 10.174] (II) NOUVEAU(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 10.174] (II) NOUVEAU(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
    [ 10.174] (II) NOUVEAU(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 14.960] (II) NOUVEAU(0): EDID vendor "SAM", prod id 27
    [ 14.960] (II) NOUVEAU(0): Using hsync ranges from config file
    [ 14.960] (II) NOUVEAU(0): Using vrefresh ranges from config file
    [ 14.960] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 14.960] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
    [ 14.961] (II) NOUVEAU(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 14.961] (II) NOUVEAU(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 14.961] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 14.961] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e)
    [ 14.961] (II) NOUVEAU(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
    [ 14.961] (II) NOUVEAU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 14.961] (II) NOUVEAU(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 14.961] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 14.961] (II) NOUVEAU(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
    [ 14.961] (II) NOUVEAU(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
    [ 14.961] (II) NOUVEAU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 14.961] (II) NOUVEAU(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
    [ 14.961] (II) NOUVEAU(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 14.961] (II) NOUVEAU(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
    [ 14.961] (II) NOUVEAU(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 84.256] (II) NOUVEAU(0): NVLeaveVT is called.
    [ 111.559] (II) NOUVEAU(0): NVEnterVT is called.
    [ 111.601] (II) NOUVEAU(0): EDID vendor "SAM", prod id 27
    [ 111.601] (II) NOUVEAU(0): Using hsync ranges from config file
    [ 111.601] (II) NOUVEAU(0): Using vrefresh ranges from config file
    [ 111.601] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 111.601] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
    [ 111.601] (II) NOUVEAU(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 111.601] (II) NOUVEAU(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 111.601] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 111.601] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e)
    [ 111.601] (II) NOUVEAU(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
    [ 111.601] (II) NOUVEAU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 111.602] (II) NOUVEAU(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 111.602] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 111.602] (II) NOUVEAU(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
    [ 111.602] (II) NOUVEAU(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
    [ 111.602] (II) NOUVEAU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 111.602] (II) NOUVEAU(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
    [ 111.602] (II) NOUVEAU(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 111.602] (II) NOUVEAU(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
    [ 111.602] (II) NOUVEAU(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 119.891] (II) NOUVEAU(0): EDID vendor "SAM", prod id 27
    [ 119.891] (II) NOUVEAU(0): Using hsync ranges from config file
    [ 119.891] (II) NOUVEAU(0): Using vrefresh ranges from config file
    [ 119.891] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 119.891] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
    [ 119.891] (II) NOUVEAU(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 119.891] (II) NOUVEAU(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 119.891] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 119.891] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e)
    [ 119.891] (II) NOUVEAU(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
    [ 119.891] (II) NOUVEAU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 119.891] (II) NOUVEAU(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 119.891] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 119.891] (II) NOUVEAU(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
    [ 119.891] (II) NOUVEAU(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
    [ 119.891] (II) NOUVEAU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 119.891] (II) NOUVEAU(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
    [ 119.891] (II) NOUVEAU(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 119.892] (II) NOUVEAU(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
    [ 119.892] (II) NOUVEAU(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 121.162] (II) NOUVEAU(0): EDID vendor "SAM", prod id 27
    [ 121.162] (II) NOUVEAU(0): Using hsync ranges from config file
    [ 121.162] (II) NOUVEAU(0): Using vrefresh ranges from config file
    [ 121.162] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 121.162] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
    [ 121.162] (II) NOUVEAU(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 121.162] (II) NOUVEAU(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 121.162] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 121.162] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e)
    [ 121.162] (II) NOUVEAU(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
    [ 121.162] (II) NOUVEAU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 121.162] (II) NOUVEAU(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 121.162] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 121.162] (II) NOUVEAU(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
    [ 121.162] (II) NOUVEAU(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
    [ 121.162] (II) NOUVEAU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 121.162] (II) NOUVEAU(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
    [ 121.162] (II) NOUVEAU(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 121.163] (II) NOUVEAU(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
    [ 121.163] (II) NOUVEAU(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 122.743] (II) NOUVEAU(0): EDID vendor "SAM", prod id 27
    [ 122.743] (II) NOUVEAU(0): Using hsync ranges from config file
    [ 122.743] (II) NOUVEAU(0): Using vrefresh ranges from config file
    [ 122.743] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 122.743] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
    [ 122.743] (II) NOUVEAU(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 122.743] (II) NOUVEAU(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 122.743] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 122.743] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e)
    [ 122.743] (II) NOUVEAU(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
    [ 122.743] (II) NOUVEAU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 122.743] (II) NOUVEAU(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 122.743] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 122.743] (II) NOUVEAU(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
    [ 122.743] (II) NOUVEAU(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
    [ 122.743] (II) NOUVEAU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 122.743] (II) NOUVEAU(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
    [ 122.743] (II) NOUVEAU(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 122.744] (II) NOUVEAU(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
    [ 122.744] (II) NOUVEAU(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 138.896] (II) NOUVEAU(0): NVLeaveVT is called.
    [ 167.669] (II) NOUVEAU(0): NVEnterVT is called.
    [ 167.720] (II) NOUVEAU(0): EDID vendor "SAM", prod id 27
    [ 167.720] (II) NOUVEAU(0): Using hsync ranges from config file
    [ 167.720] (II) NOUVEAU(0): Using vrefresh ranges from config file
    [ 167.720] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 167.720] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
    [ 167.720] (II) NOUVEAU(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 167.720] (II) NOUVEAU(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 167.720] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 167.720] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e)
    [ 167.720] (II) NOUVEAU(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
    [ 167.720] (II) NOUVEAU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 167.720] (II) NOUVEAU(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 167.720] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 167.720] (II) NOUVEAU(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
    [ 167.720] (II) NOUVEAU(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
    [ 167.720] (II) NOUVEAU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 167.720] (II) NOUVEAU(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
    [ 167.720] (II) NOUVEAU(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 167.720] (II) NOUVEAU(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
    [ 167.720] (II) NOUVEAU(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 186.390] (II) NOUVEAU(0): NVLeaveVT is called.
    - .xsession-errors in gnome session :
    GNOME_KEYRING_CONTROL=/home/olivier/.cache/keyring-D3uSoF
    GNOME_KEYRING_CONTROL=/home/olivier/.cache/keyring-D3uSoF
    GPG_AGENT_INFO=/home/olivier/.cache/keyring-D3uSoF/gpg:0:1
    GNOME_KEYRING_CONTROL=/home/olivier/.cache/keyring-D3uSoF
    GPG_AGENT_INFO=/home/olivier/.cache/keyring-D3uSoF/gpg:0:1
    SSH_AUTH_SOCK=/home/olivier/.cache/keyring-D3uSoF/ssh
    nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 30
    nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 30
    nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 55
    nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 56
    nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 59
    nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 58
    nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 30
    nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 30
    nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 30
    nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 55
    nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 56
    nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 59
    nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 58
    nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 30
    Failed to play sound: File or data not found
    ** Message: applet now removed from the notification area
    ** Message: applet now embedded in the notification area
    Avertissement du gestionnaire de fenêtres : CurrentTime used to choose focus window; focus window may not be correct.
    Avertissement du gestionnaire de fenêtres : Got a request to focus the no_focus_window with a timestamp of 0. This shouldn't happen!
    nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 30
    (gnome-shell:700): folks-WARNING **: Failed to find primary PersonaStore with type ID 'eds' and ID 'system'.
    Individuals will not be linked properly and creating new links between Personas will not work.
    The configured primary PersonaStore's backend may not be installed. If you are unsure, check with your distribution.
    (gnome-shell:700): GLib-GIO-WARNING **: Dropping signal ActiveSessionChanged of type (s) since the type from the expected interface is (o)
    (gnome-settings-daemon:657): color-plugin-WARNING **: Done switch to new account, reload devices
    (gnome-shell:700): GLib-GIO-WARNING **: Dropping signal ActiveSessionChanged of type (s) since the type from the expected interface is (o)
    (gnome-shell:700): GLib-GIO-WARNING **: Dropping signal ActiveSessionChanged of type (s) since the type from the expected interface is (o)
    Last edited by Jejel59 (2012-09-06 11:34:53)

    I'm no expert on reading the xsession errors, but I had all sorts of problems running gnome3 with my machine of the same vintage.   Cinamon is based on gnome3.  I switched to Mate which is a re-packaging of the old gnome2 along with Compiz for the window manager and all works well.
    I strongly suspect that they are using the newer OpenGL 4 API.  The Nvidia FX5200 is stuck at OpenGL 2.1.

  • Graphic Issues with Leopard - iMac 24" White GeForce 7300 GT

    Upon installing Leopard, I've noticed several graphics issues and general lag and delayed response with the interface. I'm running a 24" iMac 2.16ghz White early 2007, 3gb of RAM, with the GeForce 7300GT card. I have Time Machine disabled, and Spotlight has fully indexed.
    When installing Leopard, I did an "Erase and Install" and have manually installed my Applications after the Leopard install. I'm using only a few applications that are all "Leopard ready" and have a relatively clean system at this point. I have also cleaned the PRAM, per the recommendations in some of the threads ive read, which didn't seem to correct the issue in this case.
    It seems that any time I run any type of video or graphical application, such as Photo Booth, World of Warcraft, iChat, etc, I get a large amount of lag and slow response with the interface. Windows respond very slowly, and the applications freeze for 15-20 seconds. Even when not engaging any applications, opening folders in the finder as well as the dock appear to stall and respond very slowly.
    Aside from these issues, Leopard has performed very well and I have had no other issues. Quicklook and coverflow all seem to respond very quickly and smoothly. My guess is that it may be driver related as it seems to be centered around items that are engaging the video card, though it is strange how some graphical effects seem to work smoothly while others are rather choppy. I have been watching the Activity Monitor and there don't appear to be any processes that are sucking up CPU, and nothing obvious that may be reducing performance.
    I'm just curious if anyone else has noticed anything similar to this on similar hardware, or possibly may know what the culprit could be. My best guess, again, is that it could be the drivers or firmware with this specific hardware that I'm using.
    Thanks for your time

    I've had the same graphics issues with my white iMac 24 (serial no starts W8638), but with the GeForce 7600 card. AppleCare got me to do all the usual stuff (reset PRAM, clean Leopard install etc) but problems continued. The usual pattern is that after a while horizontal lines appear (usually in Safari) and things deteriorate form then on until there is so much pixellation that I have to turn off and back on.
    Yesterday I ran for several hours using SMCFanControl to set the fans to max and had no problems, so my suspicion is that the additional graphics requirements of Leopard are over-heating the graphics card or logic board.
    The Apple engineer took the machine away today and said they'll probably replace the logic board and graphics card (I think they can't change one without the other in the iMac?).
    Will be a few days but I'll report back on what repairs they make and whether they solve the problem. My fear is that any changes they make will have no effect if its a design problem and the card is just not up to the job without over-heating. Though it could be the card just needs a good clean
    Has anyone else tried increasing fan speed?

  • Safari Graphics Issues 10.6.5 help !!!

    Hello!
    I bought a Macbook Pro 15 one month ago and im very satisfied but i realized that Safari 5.0 has some graphics issues displaying web pages. (not only top sites)
    There have been an update (Comboupdate 10.6.2) for those graphics issues but since 10.6.5 has been released there haven`t been any updates to solve my problem.
    I have to restore my Safari Browser delete the cache and the problem is gone.
    Do you think if there will be an update for this problem or am I the only one with this problem.
    Every update has been updated correctly and i tested also with another user calling the apple care support.
    Everything else is going well.
    Thank you
    sindikat
    Message was edited by: sindikat

    Overman2000 wrote:
    I'm actually having problems with Safari as well on my new MacBook Pro (bought August '10). Recently, I've been getting screens with multiple blocks of images on various web pages. When I switch to another program, or the Finder, the blocks remain. The only way to clear up the display is to quit Safari. Any suggestions?
    I've seen the same issue on one of my machines. Only in facebook, and only when playing a java based game, only if using fast user switch to move between users, and typically, only if the machine has gone to sleep at some point in the process.
    refreshing/reloading the page will correct it, with the caveat the game will go back to the initial 'play' screen.
    That said, the 10.6.6 update appears to have corrected the problem.

  • Aperture 3, Snow Leopard, iMac ATI Radeon X1600 and graphics issues

    I have been searching the web to see if 10.6.4 has finally solved the graphics issues with the white iMac 2.16 intel with the ATI Radeon X1600 graphics processors and seen some mixed reviews. What is the consensus here, has 10.6.4 finally solved the graphics issues when editing photos in Aperture 3 (not to mention problems with iPhoto and iChat also). I had to downgrade to Leopard before so I don't want to upgrade to SL again and go back down the downgrade path. Thanks in advance for the feedback

    I can say that 10.6.4 has worked out the kinks for my white 24" iMac with 7300GT card. From what others have posted here, it appears the x1600 issues have been resolved as well. I was running 10.6.2 prior to this update and advising everyone else of same. Of course, 10.6.2 and SL was not perfect, with some issues cropping up here and there. IMHO the 10.6.4 release is equivalent to the 10.5.3 release by comparison. In fact, I upgraded my Mac mini after my good experiences with 10.6.4 on my iMac. Not sure if this helps or not.

  • Re: Graphic Issues with Leopard - iMac 24" White GeForce 7300 GT

    I noticed the same issue. It's especially noticeable in Photo Booth. The video and sound don't sync up.

    I've had the same graphics issues with my white iMac 24 (serial no starts W8638), but with the GeForce 7600 card. AppleCare got me to do all the usual stuff (reset PRAM, clean Leopard install etc) but problems continued. The usual pattern is that after a while horizontal lines appear (usually in Safari) and things deteriorate form then on until there is so much pixellation that I have to turn off and back on.
    Yesterday I ran for several hours using SMCFanControl to set the fans to max and had no problems, so my suspicion is that the additional graphics requirements of Leopard are over-heating the graphics card or logic board.
    The Apple engineer took the machine away today and said they'll probably replace the logic board and graphics card (I think they can't change one without the other in the iMac?).
    Will be a few days but I'll report back on what repairs they make and whether they solve the problem. My fear is that any changes they make will have no effect if its a design problem and the card is just not up to the job without over-heating. Though it could be the card just needs a good clean
    Has anyone else tried increasing fan speed?

  • [GUIDE] Update AMD Mobility Radeon drivers to fix graphics issues

    I made this small guide because some topics on this forum are about this problem and there is no official step-by-step solution from HP. So, how to fix your laptop's graphics issues by updating drivers for AMD Mobility Radeon HD GPU to latest version from AMD?
    1. Install latest BIOS for your laptop from HP.http://h30434.www3.hp.com/t5/Notebook-Display-and-Video/Official-HP-statement-on-Switchable-Graphics-and-Open-GL/td-p/766285
    2. In BIOS set Switchable Graphics Mode to 'Fixed mode'.http://imageshack.us/photo/my-images/268/79500144.jpg/
    3. Install latest graphics driver for your laptop from HP.http://www8.hp.com/us/en/support-drivers.html
    4. In Catalyst Control Center make sure that active GPU is 'High-performance GPU'.http://imageshack.us/photo/my-images/853/cccv.png/
    5. Download latest version of Mobility Radeon drivers for your operating system from AMD.For now, I recommend version 12.6:- for Windows 7 64-bit:http://www2.ati.com/DRIVERS/mobile/12-6_mobility_vista_win7_64_dd_ccc.exe- for Windows 7 32-bit:http://www2.ati.com/DRIVERS/mobile/12-6_mobility_vista_win7_32_dd_ccc.exe
    6. Install AMD driver on top of HP driver. This installation will update AMD components to latest version.
    7. Enjoy graphics performance as if it was properly supported by HP.
    Solution for HP:
    Release new driver each time AMD makes a new release within 1 week maximum. Hard? But this guy does nearly the same. Alone and for free. http://leshcatlabs.net/ OR simply ask AMD to provide direct links to new drivers like in an example above (see point 5) and sticky these links with a step-by-step instruction on this forum.
    Problem solved. With kudos from Russia. Alexander.
    P.S. Does this guide work?
    http://h30434.www3.hp.com/t5/Notebook-Display-and-Video/Video-Card-Drivers-AMD-Radeon-HD-6770M/m-p/1405781#M43216
    http://h30434.www3.hp.com/t5/Notebook-Display-and-Video/7690M-GPU-HP-HORRIBLE-DRIVER-SUPPORT/m-p/1403429#M43109

    hey there, i ve recently bought the g6-1304sv notebook first things i did when i got it was all the updates, both the windows 7 updates and the HP assistant updates(that basically gave me the new bios and i guess new drivers for graphics) when i got into the bios and actually switched it to fixed mode the notebook gave me a bluescreen (i could only get into the pc in safe mode through which i uninstalled drivers for both the onboard and the amd card in order to actually get back in the pc normal way) the strange thing after that  was that it didnt give me the catalyst center on the right click and when i downloaded and installed the latest it would say that catalyst could not start because it couldnt find the card (or sth like that) updated drivers for amd etc but still nothing. what i did then is creat backup cds and restore pc to factory settings. (does that remove bios update? dont think so)From that point onwards everything works fine and im now using the amd card no problemwhat worries me is the hp assistant messages saying that i need to update urgently. will that mess everything up again?i hope this helps others and i hope you have an answer for me thx in advance and for the guide!!!

  • GT72 refreshed with GTX 900M graphics

    Today sees the launch of one of the biggest leaps in mobile graphics we’ve seen in a long time. We’re talking of course about the NVIDIA GTX 900M series, which consists of the GTX 970M and the 980M. These come in distinctly different flavors, but they’re both extremely high-performing, while using less power than the previous generation.
    If you want the best, the GTX 980M is your choice. A GT72 with the GTX 980M scores over 11000 points at stock frequencies in 3DMark 11 (with NVIDIA 344.00 drivers), whereas the GTX 970M outperforms the previous generation’s high-end offering GTX 880M in the same benchmark by scoring about 9200 points.
    Unlike other gaming notebooks on the market, the GT72 is actually upgradable – you can swap your existing GTX 870M/880M graphics card for the 970M/980M, thanks to a unique MXM graphics design. Depending on your territory, you can purchase this yourself (if you’re experienced enough to do the job yourself) or have the job performed for you at an MSI authorized service center. For more details on this, see http://event.msi.com/gt72mxm

    Well, here it is..... the MSI GT72-2QE Dominator Pro-208US! Essentially, this notebook is equally equipped as the previously reviewed, GT72 2PE-007US, with one major exception..... the awesome NVidia GTX-980M. As such, I will be using my thoughts of the previous 880M model..... amending these where appropriate. As to unboxing photos, essentially everything is the same, so please review the photos HERE.
    So, here it is.....
    It's Bold, it's Bad, it's Fast, it's Powerful, and honestly, there is not much, not to like about this notebook. Also at present, this notebook is fully MXM upgradable, and for a single GPU solution, it really doesn't get much better than this.
    This model uses the same Chi Mei CMN1735 screen, which has good brightness, color, and contrast. Previously, I criticized this screen for lack of viewing angles, but interestingly enough, this is not the case with this notebook. The Steelseries keyboard is indeed flex-free, keys are very positive and responsive, and the back-lighting is brighter..... which I attribute to the keyboard's re-design. Looks and feels great!
    As to performance, the benchmarks below attest to the GT72's awesomeness, so what about noise, and the redesigned dual-fan cooling solution?
    Simply put, it is quieter than the GT70, has a better fan profile, and temps are well managed. Given the hardware, of course you will hear the fans spin up when the system is stressed, but this is not at all disturbing..... and when doing common task, the fans are only noticed if you get close and cozy with the system. Ambient room temperature were again 78F, and the system's idle temps were CPU@36C, and GPU@33C. Without the use of Cooler Booster ('stock' fan profile only), during benchmarks the highest CPU temp reached was 73C, and the GPU only reached a high of 70C. Throughout, the palm rest remains cool to the touch, it's polymer is smooth as glass, and it's surface is seamless across the touchpad. Only a mild warmth rises from the keyboard.
    That said, how does the new GTX-980M (Maxwell GM204) stack up in the benchmarks, as compared to the previous GTX-880M (Kepler GK104)?
    Significantly improved in both performance and efficiency, the GTX-980M excels over the GTX-880M as follows:
    1.) Vantage score improves by 3651, while GPU temp reduced by 10 degrees-C (18F), and the CPU by 5 degrees-C (9F).
    2.) 3DMark11 score improves by 2292, while GPU temp reduced by 10 degrees-C (18F), and the CPU by 9 degrees-C (16F).
    3.) 3DMark Sky Diver score improves by 4228, while GPU temp reduced by 16 degrees-C (29F), and the CPU by 8 degrees-C (14F).
    It should be noted that the factory release 344.00 driver was used for these benchmarks, and the 980M is yet to be recognised in FutureMarks validation process. Performance scores should improve with future NVidia driver release packages. Also, this 2nd-GEN Maxwell was manufactured still using the 28nm process, and efficiency will further improve with future Maxwell's, as this process is reduced.
    So what about SuperRAID 3, is it fast? Oh YEAH! Performance exceeds SuperRAID 2, as expected, and system boots to desktop in as little as 6 to 7 seconds. HD Tune Pro reports an average read time for the Toshiba M.2 SSD's, as 1530MB/s..... while the previous SuperRAID 2 Sandisk X100 mSATA SSD's averaged 1411MB/s. On the other hand, SuperRAID 3 really shines in the Crystal Disk Mark scores. To best evaluate the 'Real-World' performance of SuperRAID 3, I again used the PCMark 8 Storage Test. For those unfamiliar with this benchmark, the performance score of 5016 is very respectible. The duration of this benchmark is generally 1 to 3 hours, and the GT72 sped through in just 1 hour and 16 minutes. All in all, I applaud MSI's use of the new M.2 SSD's, but I think performance will most improve with future 9-Series Intel chipsets.
    At this point I conducted an audit of the systems storage capability, and all audits (including Intel's IRST) reports a total of 6 SATA ports, distributed as follows:
    Port 0 = M.2 SSD, SATA III @ 6Gbs
    Port 1 = M.2 SSD, SATA III @ 6Gbs
    Port 2 = ODD, SATA II @ 3Gbs
    Port 3 = HDD, SATA II @ 3Gbs  (NOTE: MSI has installed a SATA III, 6Gbs HDD on this port)
    Port 4 = M.2 SSD, SATA III @ 6Gbs
    Port 5 = M.2 SSD, SATA III @ 6Gbs
    This will undoubtedly come as somewhat a disappointment, to those desiring faster alternative storage devices to ports #2 & #3.
    it is when gaming, that you understand the mastery of it's intuitive design. The re-designed flex-free keyboard, the large smooth & heat-free palm rest, the spatial Dynaudio speakers, and vivid display, all lend to an immersive gaming experience. So much so, I found myself playing my test game far longer than originally intended, and playing on this notebook is simply FUN!
    To run the GT72 through it's paces, I again chose the recently released AMD optimized title, Sniper Elite III, by Rebellion. With game settings max'ed to 'Ultra', the GTX-980M smoothly sliced through the frames like a hot knife to butter, with frame-rates from 45 to 94FPS, averaging at 65FPS. Game play was extremely smooth and fluid, and never a hic-cup or artifact. Also, just as benchmark scores should improve in time, I anticipate frame rates will improve, as more mature future drivers are released.
    To best represent the 'Out-of-the-Box' experience, I played with the stock fan profile, and Cooler Booster was never used. Like with my benchmark testing, the fan noise was not disturbing, and game audio though the Dynaudio speakers easily comes to the forefront. Fan noise was never a distraction. Temps of the GPU peaked to 75C, and the CPU peaked at 61C. Again, with hardware like this, and without the use of Cooler Booster, these temps are outstanding.... and the new dual fan design is a success!
    In conclusion, the look and feel is very stylish, build quality is nice, and the smooth finish is actually somewhat fingerprint resistant. Overall, with these great looks, it's fully loaded system specs, and stellar performance scores, the MSI GT72 Dominator Pro (with 980M) not only entitles bragging rights..... it DEMANDS them!
    Enjoy!
    The following screenshots are the benchmark results using NVidia's new 344.24 driver release. Rather than performance, the focus of this release was implementing new Maxwell features, and game optimization..... ergo, these scores were actually slightly lower. Again, the ambient temp was 78F. Future drivers should improve performance levels.
    Information on NVidia's new GTX-980M:
    To take the 980M through it's paces, I allowed the Unigine benchmarks to loop 5 times, prior to actually running these benchmarks. This stressed the card to 100% for a considerable period, yet max temp never exceeded 75C.
    PCMark 8 Storage Test, and Creative benchmark scores are EXCELLENT!
    Enjoy!

  • Graphical issues with JFileChooser

    I have reduced the problem as much as I could:
    package javaapplication4;
    import java.applet.Applet;
    import javax.swing.*;
    public class NewJApplet extends JApplet {
        public void init() {}
        public void start() {
            javax.swing.JFileChooser FC = new javax.swing.JFileChooser();       
            if (FC.showOpenDialog(this) == javax.swing.JFileChooser.APPROVE_OPTION) {}       
    }If I start this as an Applet the FileChooser sometimes has [graphical issues|http://arokh.dnsalias.org/Images/FileChooser.png]. (ErrorLog)
    If started as a normal app (through main method) it works perfectly fine.
    Can anybody also reproduce/solve this?
    I'm using FireFox3 B5 (IE7 also shows this problem) & WinXP SP2
    Sun Java 6 Update 6

    I also have a 27 in iMac Core i7 3.4 with the 2GB Graphics Card.
    I called apple care and informed them + I recorded a video of it happening with ScreenFlow and sent it to apple. Please call apple care and inform them so they escalate this issue.
    When I called them they sent me a file to Capture the Data of my computer to see what happened and what caused it.
    By the way this computer should be able to connect with 6 screens simultaneously.
    Please if you are experiencing this issue write here to inform apple about and call apple care or see the genius bar.
    Thanks

Maybe you are looking for

  • Ipad mini stuck in recovery mode after ios 8.1 update

    i have a first generation ipad mini which usually works fine.  last night the ios update appeared in my settings and i tried to install it. i didnt have enough space so deleted some apps and then installed. the ipad switched on at the end but said th

  • Error in simple CQL

    I am trying to implement very simple CEP program.Cep is consist of the following component. 1.Jms adapter named MarketEventInputadapter,which is reading map message data from a simple queue. 2.one input channel named MarketEventInputchannel. 3.one pr

  • Need help with greenscreen tutorial

    Hello forum members.  I have recently started using photoshop for the first time and have been racking my brain out on this issue. I took shots on a green screen and want to extract the subject and place onto another picture. I decided to look at a t

  • 10.6.4 incompatibilities, Word, Daylite, Mail

    My machine updated yesterday. Today Word froze the machine and needed a power cycle (pull the plug) Daylite 9.10 mail integration no longer works

  • Get  window component id

    hi.. i am trying to fetch the windows components id from java..(as Testing tool do that) so is it possible to fetch the native windows components id in java?? Thanks & Regards fun_with_me