Laptop intel 4000 gpu and nvidia 675m offer same performance?

in photoshop...particularly when rendering 3d extrusions they both do the same time rendering a layer.  obviously i can force photoshop to use either gpu.  the 675m is a heck of a lot more powerful than the integrated intel gpu. 
any special trick to make it render faster using the nvidia as opposed to the intel?

The concept of a dual GPU laptop is that the embedded Intel GPU will come into play, when you are on the battery, doing very low-level and general computing, and it will save battery life.
In a perfect world, when using higher-intensity programs, such as Ps, the nVidia, or AMD/ATI GPU will automatically come into play, giving you greater performance. That is not always the case, but is what is intended.
With a program, such as Ps, you will not be using both GPU's for any process - it's one, or the other.
Good luck,
Hunt

Similar Messages

  • Intel and nVidia at the same time, with OpenGL

    Hi all,
    I'd like to set up a multi-seat Xorg config, with the onboard Intel video powering three monitors connected to that card, and an nVidia card powering two monitors connected to it.
    This seems straightforward enough to configure in the Xorg config which I have done, but when the time comes to install the "nvidia" package, it conflicts with the Intel driver.  Specifically I can't have mesa-libgl (Intel) and nvidia-libgl installed at the same time.
    I guess this is fair enough as they both want to become the default GL driver, but in my case the actual GL driver will depend on which seat is being used - sitting at the Intel monitors the GL driver should be Intel, and sitting at the nVidia monitors it should be the nvidia GL driver.
    Is there a way to install both drivers at the same time, and specify which libGL to use by e.g. changing the library search path?
    I have looked at Bumblebee but it seems aimed at duplicating displays across to the other video card, whereas I want the displays to appear on directly attached hardware.

    Short answer: No.
    Long answer: Arch wiki NVIDIA (replace nouveau with the intel driver package).
    They do not work at the same time, however.

  • Intel Control Panel and Nvidia

    Hi,  I will order a new screen for my lenovo y50-70 tomorrow! right now i added about 40 saturation in the intel hd control panel to make the TN screen look a bit better (BY FAR NOT GOOD).the TN panel is terrible. but i was wondering if the changes that i make in the intel hd control panel will affect my games which run on the nvidia card?   Yoran Kremer

    And the system you have is..... 
    >>Posting Guide<<
    But simply said: if you have dedicated graphics card (Nvidia/AMD) then integrated GPU will not be available to be used.

  • [SOLVED] Boot Resolution with Intel Haswell GPU and KMS

    Dear All,
         This thread is a follow up of this one: https://bbs.archlinux.org/viewtopic.php?id=189562. I created a new thread as I think the focus of the problem has shifted and the old title might be misleading and lead to helpful people ignoring the thread. I hope this is ok. Please correct me if I did not behave correctly.
    I think most of the "flashes" I see come from X switching from native resolution (3200x1800) which is used when starting, to 1920x1080, which I set in the configuration file.
    So my question is: how can I have the 1920x1080 resolution at boot (i.e. during early boot, using the KMS and including the i915 driver in mkinitcipo?):
    I tried:
    1) Creating the configuration file in xorg.conf.d and including it into the mkinicpio
    2) Setting the GRUB_GFX_MODE
    3) Using the EDID method (with built-in resolution 1920x1080) as described here: https://wiki.archlinux.org/index.php/ke … s_and_EDID
    4) Using uvesafb as described in the WIKI: https://wiki.archlinux.org/index.php/uvesafb
    Nothing worked. X starts during boot always with the same native resolution, the switches to 1920x1080 when GDM starts. Can you please suggest a method to set the boot resolution? It is for sure technically possible as Ubuntu does it when installed on the same hardware.. I think I just haven't found a way...
    Valerio
    Last edited by valmar (2014-11-10 15:15:07)

    Ok, answering my own question, it would appear that adding video=1920x1080 does the trick. However, I still see a lot of flashing (I think that people call it flickering)

  • GPU acceleration fix for Dell Intel and Nvidia chipsets with external monitor?

    I have a Dell XPS laptop with both integrated Intel chips and Nvidia chips and I can only get the GPU acceleration to work when I don't have any external monitors plugged in.
    Is there some way I can get Illustrator to enable the Nvidia GPU and stop being confused by multiple chipsets on external monitors? I really like the live zoom.

    same problem here,
    'm getting a little frustrated trying to get my laptop working with my LG DLP 3D ready projector to display in 3D. The projector itself will work in 3D as long as the resolution is 1024x768@120hz and the laptop's NVidia GTX 770M should have no issues driving the projector with this resolution.
    Where it seems like the problems occur is Intel HD 4600 graphics driver gets in the way every time i try to run anything 3D, the software Im using to run any 3D type files do not recognize the projector as a 3D capable device because all the laptop is using is the Intel HD 4600 graphics.
    If I could somehow turn off the Intel graphics and just force the laptop to just use the NVidia card I think all my issues will go away. I just am not having success in doing this.
    I have tried to go into the NVidia control panel and under 3D settings pick the software program that runs my 3D files and tell it to use the NVidia card...but it never works.
    I think everything is sent through the Intel graphics card regardless if the laptop is using the NVidia card (just guessing here)?
    I also tried to simply uninstall the drivers but that did not work,
    I also tried to disable the Intel graphics but it then went into some type of generic display driver mode and still would not work.
    I also went into the BIOS to look for any settings that would allow me to disable the Intel graphics card ..no luck, could not find any settings for this.
    Can someone help me with this? how can I disable the Intel graphics and force the laptop to just use the NVidia card all the time?
    Thanks!!

  • Laptop for Photoshop - GPU (Nvidia vs AMD) + Display (IPS vs TN) questions - please help

    Hi, I am helping someone with getting a new laptop for PhotoShop work, and am very confused about a couple of things.
    Hoping that the pros on this forum can help.
    1. Dedicated Graphics card - needed or not?
        If needed, AMD Radeon/FirePro (difficult to find on laptops) or Nvidia GeForce GTX 6xxM/7xxM or Quadro?
    2. Suggestions on laptops with an IPS panel and wide color gamut.
    Re. 1 - this is very confusing. From what I researched, the new Photoshop versions (CS6 and above) do use the GPU very effectively, and are using OpenCL rather than CUDA. Yet there are people on some forums that say that a GPU is not needed unless editing video.
    My friend is not editing video - he is using Photoshop to create Digital Art. He does use all of the Photoshop features in his work. No 3D work, no video editing. The end result is Printed artwork - sometimes large prints 3 ft x 4 ft printed with geeclee on canvas/high quality paper.
    Is a GPU needed, and if so is it better to get the AMD cards (Radeon most likely) that seem to completely outperform the GeForce cards in OpenCL at least?
    Most of the laptops available seem to have the GTX 6xxM or 7xxM cards, and I read on one forum that the OpenCL functions are disabled on these cards. Read on another forum that it can be re-enabled with a hack. Thorougly confused. Please help.
    Re. 2 - This too is confusing. Seems like an IPS panel has the best color rendition, but then they do not cover the entire color spectrum - or at least not as widely as the TN panels. If this will be the only monitor for work, is an IPS panel the best way to go or is it better to get a TN with wide gamut? Are there laptops with both - an IPS panel and a wide color gamut - without breaking the bank?
    Currently the Sager/Clevo machines, and some MSI models, and ASUS models seem to be the best candidates. Had to rule out Dell Precision 6700/4700 and HP Elitebook 8770W/8570W due to price, but considering refurbished ones.
    I am working with a $1200 budget with maybe some stretchability. Any advice/suggestions will be much appreciated.

    At the potential risk of your pretending to kick me off what you misguidedly perceive as your thread—which by the way you would have no right to do, since you do not own a thread just because you started it—I'll have a couple of comments on your original thoughts.
    There's no reason to be "confused" here.
    1.— Utilization of the GPU is indeed always beneficial to using recent versions of Photoshop, regardless of whether you work with video or not.  Whether you "need it or not" is a different discussion.
    2.— Of course it's absolutely necessary to be able to work with a monitor that has a narrower gamut than your working space or even your output target profile.  In my case, for example, as I'm 99.9% concerned with high quality prints, I work exclusively in ProPhoto RGB.  I'd be in a pickle if I were to restrict my work to just what I can see on any monitor regardless of how wide its gamut were.
    One just has to learn how to work in Photoshop.  That's what  Gamut Warning and Soft Proofing are there, for example.  Printers are capable of printing some colors that are not visible on any monitor.
    3.—  If both the video card and/or its driver fail to support Open GL and Shader Model, no "hack" on Earth can make up for it.
    4.— If someone came to me for advice on a laptop on which to run Photoshop  well, my main and perhaps only goal would be to dissuade that person from wasting his or her money.
    I know there might be flak from some laptop users for that immediately preceding paragraph, but hopefully not as much as you're likely to get—and deservedly so—from Mac Pro users for your astonishingly uninformed comments on those machines. 
    One thing is having a laptop as a second machine on which to show your Photoshop work to clients and prospective clients when forced to, and another one is trying to use a laptop as one's main, working Photoshop machine.
    Going to a laptop publication (which I gather the obscure, niche-market "NBR" you cite is) for information on whether to use one or not is like seeking theological religious advice about world religions from the Pope in the Vatican or the Ayatollah in Tehran. 
    5.— In the past I had run Photoshop on a variety of different nVidia GeForce cards with up to 512 MB of VRAM, but with Photoshop CS6's more advanced utilization of the GPU I have moved to a mutant, factory-overclocked, flashed ATI Radeon HD 5770 with 1 GB of VRAM driving side-by-side dual 22" monitors in my current desktop Mac Pro 2.66 GHz under OS X Lion 10.7.5 and I couldn't possibly be happier.
    I do run my second copy of Photoshop on my Mac Book (not "Pro") laptop with its stock Intel GMA 950 video circuitry and its paltry  64 MB of shared system memory, and it works just fine for the aforementioned purposes of showing  Photoshop work to others.  I wouldn't want to do any editing in Photoshop on that machine other than for minor touch-ups in an emergency, however.
    Lastly, I feel compelled to add that, in my opinion, basic human decency would dictate that you offer Trevor some sort of apology for your presumptuousness in asking him to leave this thread.  If I hadn't already begun typing this post before you posted your #6, I might have just ignored your thread.  Considering the overall anti-laptop tenor of this post, you may well wish I had. 

  • Running Intel HD Graphics for UI and Nvidia GT640m for CUDA

    Hello,
    I wanted to configure my laptop with arch64 in such a way that I can run all the UI stuff on the Intel integrated video card and still being able to debug my CUDA application without having my desktop freezing. But there's conflict between libgl and nvidia-utils.
    When libgl is installed then GNOME shows up in good quality, but CUDA doesn't work. On the other side, when nvdiai-utils is installed GNOME goes to fallback mode and the CUDA stuff runs.
    In the first case, the nvidia cuda driver aren't loaded. In the second case, Cuda works, but i don't know on which device the desktop stuff is executed. How do I find out? How to run both side by side?
    The devices:
    Intel HD Graphics 4000 (i7 3610QM) for X
    Nvidia GT 640m only for CUDA.
    Thank you for your time.

    Since I have only mathematical computations to do, I solved it like that:
    The proposed solution with AUR package, contains old dev-drivers for x64. The same for the nvidia website. Only the nvidia and nvidia-utils package from extra are up to date.
    So I downloaded the nvidia packages (nvidia and nvidia-utils) and installed them, then i installed cuda-sdk and cuda-toolkit from community. After that I unzipped nvidia and nvidia-utils to some folder, removed the files conflicting with Intel's OpenGL and forced the removal of nvidia and nvidia-utils. Then I copied the unpack files to their intended place and reinstalled Intel's OpenGL package.
    It works for purely local numerical computations. Note that OpenGL can not be execute on this machine, but development is possible.

  • HP Envy 15 Graphics Problem with Windows 8.1 (Intel and NVidia Graphics). Help!

    I bought an HP ENVY TouchSmart 15-j013ea about 6 months ago and I have had a major problem with the graphics that I cannot seem to solve. I think it started when I updated to Windows 8.1, even though I am not 100% certain.
    I have noticed the following three problems, and I think they are related:
    Some windows (such as Chrome, Skype, or even Device Manager or other windows) are very blurry compared to others.
    The firefox menu window has some deformed black arrows instead of the normal ones.
    When playing a game (specifically, Star Wars the Force Unleashed 2), after a while I get an error that the computer has ran out of memory. However, according to task manager, only about 50% is in use, not to mention that I have 8 GB of RAM + 2 GB graphics memory. At the same time, the computer gets rather loud (like a fan working overtime) and hot.
    The laptop has both Intel and NVidia graphics, and both are enabled in Device Manager. To be honest, I have no idea which is used when, or how to check that (let me know if there is a way)
    I have tried the following without success:
    Uninstalling the Intel graphics driver from device manager and installing a version I downloaded from the HP website for my laptop and OS. After that, Windows would NOT BOOT, and I had to do a system restore.
    Uninstalling the Intel graphics from Programs and Features, and installing 2 different versions from the Intel website. Nothing changed.
    Updating Nvidia driver through GeForce Experience. Nothing changed.
    Updating Intel drivers from Windows Update. Nothing changed.
    Quite frankly I am not sure what the problem could be, since the graphics versions are supposed to be compatible with WIndows 8.1. I also don't get why some windows are blurry and others are not. I am thinking the computer uses only the Intel graphics and not the Nvidia (at least in the blurry windows), but even if that was the case (and it shouldn't be), I don't think I should be having this problem.
    At this point, I really need help. My graphics details are:
    Intel HD Graphics 4600: Driver version: 10.18.10.3412
    NVidia GeForce GT 740M: Driver version: 335.23
    NVidia GeForce Experience version: 1.8.2
    I am attaching screenshots that show driver details and the problems.
    Thank you.
    Blurry Chrome:
    Firefox menu problem:
    Device Manager and driver windows are also blurry, both graphics are shown

    I had a similar problem with a Dell laptop.  I found the problem was the laptop wanted to switch between the Intel and NYIDIA video cards.  It would switch to the Intel when high graphics was not required then to the NIVIDIA when high graphics was required.  The laptop does this to save power when high graphics is not required but it caused problems with some applications, specifically high graphics games.
    For me the solution was to disable the Intel graphics processor.  You can do this by right clicking on your Wallpaper, select the NIVIDIA Control Panel, then select Set Physx Configuration.  You will see a dropdown box labeled Select Physx Processor.  It is set to Auto by default.  This allows the switching I described. Select this dropdown box and select your NIVIDIA processor.  This will prevent the laptop from switching and force it to use your NVIDIA processor exclusively.
    Hope this helps.
    Sacto Fred
    Owner and CEO
    H&O PC Soultions

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

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

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

  • Intel 4000 graphics failure both windows and linux on thinkpad edge s430

    After 5-30 minutes the screen breaks up in flickering (or just black) and system freezes. I need to turn off computer. After restart the error occurs again quickly.
    This occurs regardless if I boot to windows or into a linux bootable dvd.
    But
    Remote desktop connection to the computer and it works fine for days .
    ->
    Thus I believe it is the intel 4000 graphics that has some hardware failure which is not invoked upon remote desktop.
    I wonder if this is a known issue?
    I wonder if only a replacement of the intel 4000 graphics will fix this (this probably means replacing the main board entirely?)
    Or
    If it is in any way likely that it is _only_ because maybe thermal paste between cooler and cpu/graphics is slipping?
    Lenovo Thinkpad Edge S430
    Intel I7 + Intel HD 4000
    No additional graphics

    Have you tried setting up the connection manually?
    e.g.
    /etc/init.d/networkmanager stop
    #Unlock wireless devices
    rfkill unblock all
    #enable interface
    ifconfig wlan0 up
    #check network visibility
    iwlist wlan0 scanning
    #configure wifi
    iwconfig wlan0 essid <ESSID>
    iwconfig tx auto
    and then set up wpa_supplicant in case you use WPA2!
    #Get ip address
    dhclient wlan0
    One thing I regularly miss when getting a new wifi device is to add it to the MAC filter list of my router, so check if the MAC address is added there...
    W520|4282-W16|2720QM|16GB|Q1000M|FHD|500GB|UMTS|BIOS 1.26|Gentoo Linux/2.6.39-r3|Win7-64-Prof|

  • My macMini has only a 1.5 GHz Intel Solo Core and is now unable to do things like Turbo Tax. I use it mainly for email, web browsing, bill paying, banking. Should my next purchase be a notebook, laptop, mini or iPad?

    My macMini has only a 1.5 GHz Intel Solo Core and is now unable to do things like Turbo Tax. I use it mainly for email, web browsing, bill paying, banking. Should my next purchase be a notebook, laptop, mini or iPad?

    Desktop: Mac Mini dual-core i5 (or quad i7 if you can afford it, it might seem overpowered but it will last you longer. Upgrade to 16GB RAM if you want to future proof that side of the machine. Don't buy from Apple, install it yourself).
    Laptop: MacBook Pro 13' if you don't need portability, or MacBook Air 11' if you do (as RRFS has said).
    A notebook and a laptop are the same thing.

  • FAQ: What features use the GPU and how do I troubleshoot GPU issues?

    Photoshop CS6 GPU FAQ
    Introduction
    This document provides a quick reference guide to video card usage in Photoshop.  Some features require a compatible video card to work; if the video card or its driver is defective or unsupported, those features will not work at all.  Other features use the video card for acceleration and if the card or driver is defective those features will run more slowly.
    Mercury Graphics Engine
    The Mercury Graphics Engine (MGE) represents features that use video card, or GPU, acceleration. In Photoshop CS6, this new engine delivers near-instant results when editing with key tools such as Liquify, Warp, Lighting Effects and the Oil Paint filter. The new MGE delivers unprecedented responsiveness for a fluid feel as you work.
    MGE is new to Photoshop CS6, and uses both the OpenGL and OpenCL frameworks. It does not use the proprietary CUDA framework from nVidia.
    In order to use MGE, you must have a supported video card and updated driver. If you do not have a supported card, performance will be degraded. In most cases the acceleration is lost and the feature runs in the normal CPU mode. However, there are some features that will not work without a supported video card.
    GPU features added in Photoshop CS6
    Adaptive Wide Angle Filter (compatible video card required)
    Liquify (accelerated by compatible video card with 512MB VRAM, GPU mode unavailable on Windows XP)
    Oil Paint (compatible video card required)
    Warp and Puppet Warp (accelerated by compatible video card, GPU mode unavailable on Windows XP)
    Field Blur, Iris Blur, and Tilt/Shift (accelerated by compatible video
    card supporting OpenCL, GPU mode unavailable on Windows XP)
    Lighting Effects Gallery (compatible video card required with 512MB
    VRAM, unavailable on Windows XP)
    New 3D enhancements (3D features in Photoshop require a compatible video card with 512MB VRAM, unavailable on Windows XP):
    Draggable Shadows
    Ground plane reflections
    Roughness
    On-canvas UI controls
    Ground plane
    Liqht widgets on edge of canvas
    IBL (image based light) controller
    * Note that all 3D features are unavailable on Windows XP in Photoshop CS6
    GPU features added in previous versions of Photoshop
    Scrubby Zoom. See Zoom continuously
    Heads Up Display (HUD) color picker. See Choose a color while painting
    Color sampling ring. Choose colors with the Eyedropper tool
    Brush dynamic resize and hardness control. See Resize or change hardness of cursors by dragging
    Bristle Brush tip previews. Bristle tip shape options
    Rule of thirds crop grid overlay. Crop images
    Zoom enhancements. Smooth display at all zoom levels and temporary zoom. See Zoom continuouslyTemporarily zoom an image
    Animated transitions for one-stop zoom.
    Flick-panning.
    Rotate the canvas. Use the Rotate View tool
    View nonsquare pixel images. Adjust pixel aspect ratio
    Pixel grid. Hide the pixel grid
    Adobe Color Engine (ACE).
    Draw Brush tip cursors. Resize or change hardness of cursors by dragging
    Adobe Bridge GPU features
    Preview panel
    Full-screen preview
    Review mode
    See Preview and compare images in Adobe Bridge CS6 Help for information on all of these features.
    GPU/OpenGL preferences in Photoshop CS6
    The advantages of using a compatible video card (GPU) with Photoshop are that you can experience better performance and more features.   Problems can occur if you have an older video card with limited VRAM or if you use other programs at the same time as Photoshop that use the GPU.
    Choose Edit > Preferences (Windows) or Photoshop > Preferences (Mac OS).
    In the Performance panel, make sure Use Graphics Processor is selected in GPU Settings.
    Click Advanced Settings and specify the following options:
    Mode > Basic
    Mode > Normal
    Mode > Advanced Provides the benefits of Normal mode as well as newer OpenGL advances that can result in improved performance.
    Use Graphics Processor to Accelerate Computation
    Use OpenCL Uses the GPU to accelerate the new blur filters (Field Blur, Iris Blur, and Tilt-Shift) – OpenCL will only be available on newer GPUs that support OpenCL v1.1 or higher
    Anti-Alias Guides And Paths Allows the GPU hardware to smooth the edges of drawn guides and paths.
    30 Bit Display (Windows only) Allows Photoshop to display 30 bit data directly to screen on video cards that support it
    Quick GPU Troubleshooting Steps
    You can experience problems such as artifacts, errors, and crashes if there are incompatibilities between Photoshop and the display components that access the GPU.
    If you experience crashes, incorrectly rendered windows or objects, redraw issues, or performance issues while running Photoshop, first determine whether OpenGL is causing the problem.
    Turn off OpenGL.
    Choose Edit > Preferences (Windows) or Photoshop > Preferences (Mac OS).
    In the Performance panel, uncheck Use Graphics Processor. Click OK.
    Restart Photoshop, and perform the same function.
    If the problem recurs while OpenGL Drawing is disabled, OpenGL is not the cause. For additional troubleshooting, see Troubleshoot system errors and freezes | Adobe software on Windows (cpsid_82252) or Troubleshoot system errors and freezes | Adobe software on Mac OS 10.x (cpsid_82414).
    If the problem resolves, proceed with the rest of the troubleshooting steps to fix OpenGL.
    Make sure that you're using the latest update of Photoshop.Updates fix bugs and issues.
    Update the display driver.Updated display drivers can fix many issues, such as crashing, incorrectly rendered objects, and performance problems. Determine what video card you have and go directly to the manufacturer's website (nVidia or ATI/AMD) and download the latest driver. (Note: Simply doing a Windows Update is does not guarantee you are using the latest driver. You must go directly to the nVideo or ATI/AMD websites to get the absolute latest driver.) After you update your driver, turn on Use Graphics Processor in Photoshop preferences.
    Reset preferences.
    Resetting preferences returns OpenGL settings to their default status. Reset Photoshop preferences by pressing and holding Shift+Ctrl+Alt (Windows) or Shift+Option+Command (Mac OS) immediately after you start Photoshop.
    Click Yes when asked if you want to delete the Adobe Photoshop Settings File.
    Retry the function that caused the problem.
    Change the OpenGL mode to Basic.
    Setting the OpenGL mode to Basic uses the least amount of GPU memory and the most basic GPU feature set.
    Close all documents.
    Choose Edit > Preferences (Windows) or Photoshop > Preferences (Mac OS)
    In the Performance panel, click the GPU Settings Advanced Settings button.
    Choose Mode > Basic
    Restart Photoshop.
    If this solution resolves the problem, switch to Normal mode. See if the issue recurs. If the issue recurs, return to Basic mode.
    Note:  If you’re changing GPU preferences to troubleshoot a problem, re-launch Photoshop after each change.
    If you are using more than one video adapter, remove the additional cards.
    Multiple video adapters can cause problems with GPU accelerated or enabled features in Photoshop. It's best to connect two (or more) monitors into one video adapter. If you have to use more than one video adapter, make sure that they are the same make and model. Otherwise, crashes and other problems can occur in Photoshop.
    Note: Using two video adapters does not enhance Photoshop's performance.
    Check your Cache Levels setting.
    If you've set your Cache Levels to 1 in Photoshop preferences, you can experience performance issues with GPU features. Reset Cache Levels to the default setting, which is 4.
    Choose Edit > Preferences > Performance (Windows) or Photoshop > Preferences (Mac OS)
    In the Performance panel, choose Cache Levels > 4.
    The GPU Sniffer
    To help guard against Photoshop crashes related to bad GPU hardware or drivers, Photoshop employs a small program called the GPU Sniffer. Every time Photoshop is launched, Photoshop launches the sniffer. The sniffer runs rudimentary tests of the GPU and reports the results to Photoshop. If the sniffer crashes or reports a failure status to Photoshop, Photoshop will not use the GPU. The Use Graphics Hardware checkbox in the Performance panel of the Preferences will be unchecked and disabled.
    The first time the sniffer fails, Photoshop will display a dialog indicating that it has detected a problem with the GPU. On subsequent launches the dialog will not appear unless the Photoshop preferences are reset.
    If the user corrects the problem, either by replacing the video card or by updating the driver, then the sniffer will pass on the next launch and the Use Graphics Hardware checkbox will be enabled and returned to its previous state (enabled or disabled).
    Tested video cards for Photoshop CS6
    Adobe tested the following video cards before the release of Photoshop CS6. This document lists the video card by series. While the minimum amount of VRAM supported on video cards for Photoshop CS6 is 256MB, some features require 512MB of VRAM to be enabled.
    Note: Adobe tested laptop and desktop versions of the following cards. Be sure to download the latest driver for your specific model. (Laptop and desktop versions have slightly different names.)
    nVidia GeForce 8000, 9000, 100, 200, 300, 400, 500 series 
    nVidia Quadro 400, 600, 2000, 4000 (Mac & Win), CX, 5000, 6000
    AMD/ATI Radeon 2000, 3000, 4000, 5000, 6000, 7000 series
    AMD/ATI FirePro 3800, 4800, 5800, 7800, 8800, 9800, 3900, 4900, 5900, 7900
    Intel Intel HD Graphics, Intel HD Graphics P3000, Intel HD Graphics P4000
    Note: ATI X1000 series and nVidia 7000 series cards are no longer being tested and are not officially supported in CS6 – some basic GL functionality may be available for both these cards.
    Note: 3Dand some Open GL features are disabled on Windows XP, as stated on : http://labs.adobe.com/technologies/photoshopcs6/

    I've had several timeout since the pings were started. Got a some response times > 1ms (nothing greater than 7 or 8ms), but no timeouts.

  • Can't load nvidia module after kernel and nvidia update

    After latest kernel (3.6.36.2) and nvidia (260.19.29) upgrade xorg doesn't work. I investigated a little, and that's what I found:
    # modprobe nvidia
    FATAL: Error inserting nvidia (/lib/modules/2.6.36-ARCH/kernel/drivers/video/nvidia.ko): No such device
    I blacklisted nouveau module:
    # cat /etc/rc.conf | grep nouveau
    MODULES=(b43 vboxdrv !nouveau)
    but it didn't help.
    Video card:
    # lspci | grep VGA
    01:00.0 VGA compatible controller: nVidia Corporation G84 [GeForce 8600M GT] (rev a1)

    Initializing cgroup subsys cpuset
    Initializing cgroup subsys cpu
    Linux version 2.6.36-ARCH (tobias@T-POWA-LX) (gcc version 4.5.1 20101125 (prerelease) (GCC) ) #1 SMP PREEMPT Fri Dec 10 20:01:53 UTC 2010
    BIOS-provided physical RAM map:
    BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
    BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
    BIOS-e820: 00000000000dc000 - 0000000000100000 (reserved)
    BIOS-e820: 0000000000100000 - 000000005fed0000 (usable)
    BIOS-e820: 000000005fed0000 - 000000005fee3000 (ACPI NVS)
    BIOS-e820: 000000005fee3000 - 0000000060000000 (reserved)
    BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
    BIOS-e820: 00000000fed00000 - 00000000fed00400 (reserved)
    BIOS-e820: 00000000fed14000 - 00000000fed1a000 (reserved)
    BIOS-e820: 00000000fed1c000 - 00000000fed90000 (reserved)
    BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
    BIOS-e820: 00000000ff000000 - 0000000100000000 (reserved)
    Notice: NX (Execute Disable) protection missing in CPU or disabled in BIOS!
    DMI present.
    e820 update range: 0000000000000000 - 0000000000001000 (usable) ==> (reserved)
    e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
    last_pfn = 0x5fed0 max_arch_pfn = 0x100000
    MTRR default type: uncachable
    MTRR fixed ranges enabled:
    00000-9FFFF write-back
    A0000-BFFFF uncachable
    C0000-FFFFF write-protect
    MTRR variable ranges enabled:
    0 base 000000000 mask FC0000000 write-back
    1 base 040000000 mask FE0000000 write-back
    2 base 05FF00000 mask FFFF00000 uncachable
    3 disabled
    4 disabled
    5 disabled
    6 disabled
    7 disabled
    x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
    e820 update range: 0000000000002000 - 0000000000010000 (usable) ==> (reserved)
    Scanning 1 areas for low memory corruption
    modified physical RAM map:
    modified: 0000000000000000 - 0000000000001000 (reserved)
    modified: 0000000000001000 - 0000000000002000 (usable)
    modified: 0000000000002000 - 0000000000010000 (reserved)
    modified: 0000000000010000 - 000000000009f800 (usable)
    modified: 000000000009f800 - 00000000000a0000 (reserved)
    modified: 00000000000dc000 - 0000000000100000 (reserved)
    modified: 0000000000100000 - 000000005fed0000 (usable)
    modified: 000000005fed0000 - 000000005fee3000 (ACPI NVS)
    modified: 000000005fee3000 - 0000000060000000 (reserved)
    modified: 00000000fec00000 - 00000000fec10000 (reserved)
    modified: 00000000fed00000 - 00000000fed00400 (reserved)
    modified: 00000000fed14000 - 00000000fed1a000 (reserved)
    modified: 00000000fed1c000 - 00000000fed90000 (reserved)
    modified: 00000000fee00000 - 00000000fee01000 (reserved)
    modified: 00000000ff000000 - 0000000100000000 (reserved)
    initial memory mapped : 0 - 01800000
    found SMP MP-table at [c00f7bc0] f7bc0
    init_memory_mapping: 0000000000000000-00000000377fe000
    0000000000 - 0000400000 page 4k
    0000400000 - 0037400000 page 2M
    0037400000 - 00377fe000 page 4k
    kernel direct mapping tables up to 377fe000 @ 15000-1a000
    RAMDISK: 37e47000 - 37ff0000
    Allocated new RAMDISK: 00100000 - 002a8feb
    Move RAMDISK from 0000000037e47000 - 0000000037feffea to 00100000 - 002a8fea
    ACPI: RSDP 000f7b40 00024 (v02 Compal)
    ACPI: XSDT 5fed8834 0008C (v01 Compal CRESTLNE 06040000 LTP 00000000)
    ACPI: FACP 5fedfbd2 000F4 (v03 INTEL CRESTLNE 06040000 ALAN 00000001)
    ACPI: DSDT 5fed9b9f 05FBF (v02 Compal CRESTLNE 06040000 INTL 20061109)
    ACPI: FACS 5fee2fc0 00040
    ACPI: APIC 5fedfcc6 00068 (v01 INTEL CRESTLNE 06040000 LOHR 0000005A)
    ACPI: HPET 5fedfd2e 00038 (v01 Compal CRESTLNE 06040000 LOHR 0000005A)
    ACPI: MCFG 5fedfd66 0003C (v01 INTEL CRESTLNE 06040000 LOHR 0000005A)
    ACPI: TCPA 5fedfda2 00032 (v01 Intel CRESTLNE 06040000 LOHR 0000005A)
    ACPI: TMOR 5fedfdd4 00026 (v01 PTLTD 06040000 PTL 00000003)
    ACPI: SLIC 5fedfdfa 00176 (v01 Compal CRESTLNE 06040000 TBD 00000001)
    ACPI: APIC 5fedff70 00068 (v01 PTLTD ? APIC 06040000 LTP 00000000)
    ACPI: BOOT 5fedffd8 00028 (v01 PTLTD $SBFTBL$ 06040000 LTP 00000001)
    ACPI: SSDT 5fed98da 002C5 (v01 SataRe SataAhci 00001000 INTL 20050624)
    ACPI: SSDT 5fed8e4c 0025F (v01 PmRef Cpu0Tst 00003000 INTL 20050624)
    ACPI: SSDT 5fed8da6 000A6 (v01 PmRef Cpu1Tst 00003000 INTL 20050624)
    ACPI: SSDT 5fed88c0 004E6 (v01 PmRef CpuPm 00003000 INTL 20050624)
    ACPI: BIOS bug: multiple APIC/MADT found, using 0
    ACPI: If "acpi_apic_instance=2" works better, notify [email protected]
    ACPI: Local APIC address 0xfee00000
    646MB HIGHMEM available.
    887MB LOWMEM available.
    mapped low ram: 0 - 377fe000
    low ram: 0 - 377fe000
    Zone PFN ranges:
    DMA 0x00000001 -> 0x00001000
    Normal 0x00001000 -> 0x000377fe
    HighMem 0x000377fe -> 0x0005fed0
    Movable zone start PFN for each node
    early_node_map[3] active PFN ranges
    0: 0x00000001 -> 0x00000002
    0: 0x00000010 -> 0x0000009f
    0: 0x00000100 -> 0x0005fed0
    On node 0 totalpages: 392800
    free_area_init_node: node 0, pgdat c142d600, node_mem_map c1598020
    DMA zone: 32 pages used for memmap
    DMA zone: 0 pages reserved
    DMA zone: 3952 pages, LIFO batch:0
    Normal zone: 1744 pages used for memmap
    Normal zone: 221486 pages, LIFO batch:31
    HighMem zone: 1294 pages used for memmap
    HighMem zone: 164292 pages, LIFO batch:31
    Using APIC driver default
    ACPI: PM-Timer IO Port: 0x1008
    ACPI: Local APIC address 0xfee00000
    ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
    ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
    ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
    ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
    ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
    IOAPIC[0]: apic_id 1, version 32, address 0xfec00000, GSI 0-23
    ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
    ACPI: IRQ0 used by override.
    ACPI: IRQ2 used by override.
    ACPI: IRQ9 used by override.
    Using ACPI (MADT) for SMP configuration information
    ACPI: HPET id: 0x8086a201 base: 0xfed00000
    SMP: Allowing 2 CPUs, 0 hotplug CPUs
    nr_irqs_gsi: 40
    early_res array is doubled to 64 at [16000 - 167ff]
    PM: Registered nosave memory: 0000000000002000 - 0000000000010000
    PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
    PM: Registered nosave memory: 00000000000a0000 - 00000000000dc000
    PM: Registered nosave memory: 00000000000dc000 - 0000000000100000
    Allocating PCI resources starting at 60000000 (gap: 60000000:9ec00000)
    Booting paravirtualized kernel on bare hardware
    setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:2 nr_node_ids:1
    PERCPU: Embedded 13 pages/cpu @c2400000 s31488 r0 d21760 u2097152
    pcpu-alloc: s31488 r0 d21760 u2097152 alloc=1*4194304
    pcpu-alloc: [0] 0 1
    Built 1 zonelists in Zone order, mobility grouping on. Total pages: 389730
    Kernel command line: BOOT_IMAGE=/boot/vmlinuz26 root=/dev/sda2 ro
    PID hash table entries: 4096 (order: 2, 16384 bytes)
    Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
    Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
    Enabling fast FPU save and restore... done.
    Enabling unmasked SIMD FPU exception support... done.
    Initializing CPU#0
    allocated 7858220 bytes of page_cgroup
    please try 'cgroup_disable=memory' option if you don't want memory cgroups
    Subtract (52 early reservations)
    #1 [0000001000 - 0000002000] EX TRAMPOLINE
    #2 [0001000000 - 000158fe8c] TEXT DATA BSS
    #3 [0001590000 - 0001596198] BRK
    #4 [00000f7bd0 - 0000100000] BIOS reserved
    #5 [00000f7bc0 - 00000f7bd0] MP-table mpf
    #6 [000009f800 - 000009fd71] BIOS reserved
    #7 [000009ff35 - 00000f7bc0] BIOS reserved
    #8 [000009fd71 - 000009ff35] MP-table mpc
    #9 [0000010000 - 0000011000] TRAMPOLINE
    #10 [0000011000 - 0000015000] ACPI WAKEUP
    #11 [0000015000 - 0000016000] PGTABLE
    #12 [0000100000 - 00002a9000] NEW RAMDISK
    #13 [0001597000 - 0001598000] BOOTMEM
    #14 [0001598000 - 0002198000] BOOTMEM
    #15 [000158fec0 - 000158fec4] BOOTMEM
    #16 [000158ff00 - 000158ffc0] BOOTMEM
    #17 [00015961c0 - 0001596214] BOOTMEM
    #18 [0002198000 - 000219b000] BOOTMEM
    #19 [000158ffc0 - 0001590000] BOOTMEM
    #20 [000219b000 - 000219e000] BOOTMEM
    #21 [0001596240 - 0001596265] BOOTMEM
    #22 [0001596280 - 00015962a7] BOOTMEM
    #23 [00015962c0 - 0001596464] BOOTMEM
    #24 [0001596480 - 00015964c0] BOOTMEM
    #25 [00015964c0 - 0001596500] BOOTMEM
    #26 [0001596500 - 0001596540] BOOTMEM
    #27 [0001596540 - 0001596580] BOOTMEM
    #28 [0001596580 - 00015965c0] BOOTMEM
    #29 [00015965c0 - 0001596600] BOOTMEM
    #30 [0001596600 - 0001596640] BOOTMEM
    #31 [0001596640 - 0001596680] BOOTMEM
    #32 [0001596680 - 00015966c0] BOOTMEM
    #33 [00015966c0 - 0001596700] BOOTMEM
    #34 [0001596700 - 0001596740] BOOTMEM
    #35 [0001596740 - 0001596780] BOOTMEM
    #36 [0001596780 - 0001596790] BOOTMEM
    #37 [00015967c0 - 00015967d0] BOOTMEM
    #38 [0001596800 - 000159682d] BOOTMEM
    #39 [0001596840 - 000159686d] BOOTMEM
    #40 [0002400000 - 000240d000] BOOTMEM
    #41 [0002600000 - 000260d000] BOOTMEM
    #42 [0001596880 - 0001596884] BOOTMEM
    #43 [00015968c0 - 00015968c4] BOOTMEM
    #44 [0001596900 - 0001596908] BOOTMEM
    #45 [0001596940 - 0001596948] BOOTMEM
    #46 [0001596980 - 0001596a28] BOOTMEM
    #47 [0001596a40 - 0001596aa8] BOOTMEM
    #48 [000219e000 - 00021a2000] BOOTMEM
    #49 [00021a2000 - 0002222000] BOOTMEM
    #50 [0002222000 - 0002262000] BOOTMEM
    #51 [000260d000 - 0002d8b82c] BOOTMEM
    Initializing HighMem for node 0 (000377fe:0005fed0)
    Memory: 1542868k/1571648k available (3104k kernel code, 28332k reserved, 1205k data, 428k init, 662344k highmem)
    virtual kernel memory layout:
    fixmap : 0xfff16000 - 0xfffff000 ( 932 kB)
    pkmap : 0xff800000 - 0xffc00000 (4096 kB)
    vmalloc : 0xf7ffe000 - 0xff7fe000 ( 120 MB)
    lowmem : 0xc0000000 - 0xf77fe000 ( 887 MB)
    .init : 0xc1436000 - 0xc14a1000 ( 428 kB)
    .data : 0xc1308056 - 0xc1435820 (1205 kB)
    .text : 0xc1000000 - 0xc1308056 (3104 kB)
    Checking if this processor honours the WP bit even in supervisor mode...Ok.
    SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
    Hierarchical RCU implementation.
    RCU-based detection of stalled CPUs is disabled.
    Verbose stalled-CPUs detection is disabled.
    NR_IRQS:512
    Extended CMOS year: 2000
    Console: colour VGA+ 80x25
    console [tty0] enabled
    hpet clockevent registered
    Fast TSC calibration using PIT
    Detected 1795.546 MHz processor.
    Calibrating delay loop (skipped), value calculated using timer frequency.. 3592.72 BogoMIPS (lpj=5985153)
    pid_max: default: 32768 minimum: 301
    Security Framework initialized
    TOMOYO Linux initialized
    AppArmor: AppArmor disabled by boot time parameter
    Mount-cache hash table entries: 512
    Initializing cgroup subsys ns
    Initializing cgroup subsys cpuacct
    Initializing cgroup subsys memory
    Initializing cgroup subsys devices
    Initializing cgroup subsys freezer
    Initializing cgroup subsys net_cls
    Initializing cgroup subsys blkio
    CPU: Physical Processor ID: 0
    CPU: Processor Core ID: 0
    mce: CPU supports 6 MCE banks
    CPU0: Thermal monitoring handled by SMI
    using mwait in idle threads.
    Performance Events: PEBS fmt0+, Core2 events, Intel PMU driver.
    PEBS disabled due to CPU errata.
    ... version: 2
    ... bit width: 40
    ... generic registers: 2
    ... value mask: 000000ffffffffff
    ... max period: 000000007fffffff
    ... fixed-purpose events: 3
    ... event mask: 0000000700000003
    ACPI: Core revision 20100702
    Enabling APIC mode: Flat. Using 1 I/O APICs
    ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
    CPU0: Intel(R) Core(TM)2 Duo CPU T7100 @ 1.80GHz stepping 0d
    NMI watchdog enabled, takes one hw-pmu counter.
    Booting Node 0, Processors #1 Ok.
    Initializing CPU#1
    CPU1: Thermal monitoring handled by SMI
    NMI watchdog enabled, takes one hw-pmu counter.
    Brought up 2 CPUs
    Total of 2 processors activated (7184.34 BogoMIPS).
    devtmpfs: initialized
    NET: Registered protocol family 16
    ACPI: bus type pci registered
    PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
    PCI: not using MMCONFIG
    PCI: PCI BIOS revision 2.10 entry at 0xfdde1, last bus=14
    PCI: Using configuration type 1 for base access
    bio: create slab <bio-0> at 0
    ACPI: EC: Look up EC in DSDT
    ACPI: BIOS _OSI(Linux) query ignored
    ACPI: SSDT 5fed95da 00238 (v01 PmRef Cpu0Ist 00003000 INTL 20050624)
    ACPI: Dynamic OEM Table Load:
    ACPI: SSDT (null) 00238 (v01 PmRef Cpu0Ist 00003000 INTL 20050624)
    ACPI: SSDT 5fed90ab 004AA (v01 PmRef Cpu0Cst 00003001 INTL 20050624)
    ACPI: Dynamic OEM Table Load:
    ACPI: SSDT (null) 004AA (v01 PmRef Cpu0Cst 00003001 INTL 20050624)
    ACPI: SSDT 5fed9812 000C8 (v01 PmRef Cpu1Ist 00003000 INTL 20050624)
    ACPI: Dynamic OEM Table Load:
    ACPI: SSDT (null) 000C8 (v01 PmRef Cpu1Ist 00003000 INTL 20050624)
    ACPI: SSDT 5fed9555 00085 (v01 PmRef Cpu1Cst 00003000 INTL 20050624)
    ACPI: Dynamic OEM Table Load:
    ACPI: SSDT (null) 00085 (v01 PmRef Cpu1Cst 00003000 INTL 20050624)
    ACPI: Interpreter enabled
    ACPI: (supports S0 S3 S4 S5)
    ACPI: Using IOAPIC for interrupt routing
    PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
    PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in ACPI motherboard resources
    PCI: Using MMCONFIG for extended config space
    ACPI: EC: GPE = 0x1c, I/O: command/status = 0x66, data = 0x62
    ACPI: No dock devices found.
    PCI: Ignoring host bridge windows from ACPI; if necessary, use "pci=use_crs" and report a bug
    ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
    pci_root PNP0A08:00: host bridge window [io 0x0000-0x0cf7] (ignored)
    pci_root PNP0A08:00: host bridge window [io 0x0d00-0xffff] (ignored)
    pci_root PNP0A08:00: host bridge window [mem 0x000a0000-0x000bffff] (ignored)
    pci_root PNP0A08:00: host bridge window [mem 0x000d0000-0x000d3fff] (ignored)
    pci_root PNP0A08:00: host bridge window [mem 0x000d4000-0x000d7fff] (ignored)
    pci_root PNP0A08:00: host bridge window [mem 0x000d8000-0x000dbfff] (ignored)
    pci_root PNP0A08:00: host bridge window [mem 0x60000000-0xdfffffff] (ignored)
    pci_root PNP0A08:00: host bridge window [mem 0xf0000000-0xfebfffff] (ignored)
    pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
    pci 0000:00:01.0: PME# disabled
    pci 0000:00:1a.0: reg 20: [io 0x1800-0x181f]
    pci 0000:00:1a.1: reg 20: [io 0x1820-0x183f]
    pci 0000:00:1a.7: reg 10: [mem 0xf8404800-0xf8404bff]
    pci 0000:00:1a.7: PME# supported from D0 D3hot D3cold
    pci 0000:00:1a.7: PME# disabled
    pci 0000:00:1b.0: reg 10: [mem 0xf8400000-0xf8403fff 64bit]
    pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
    pci 0000:00:1b.0: PME# disabled
    pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
    pci 0000:00:1c.0: PME# disabled
    pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
    pci 0000:00:1c.1: PME# disabled
    pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold
    pci 0000:00:1c.2: PME# disabled
    pci 0000:00:1c.3: PME# supported from D0 D3hot D3cold
    pci 0000:00:1c.3: PME# disabled
    pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
    pci 0000:00:1c.4: PME# disabled
    pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold
    pci 0000:00:1c.5: PME# disabled
    pci 0000:00:1d.0: reg 20: [io 0x1840-0x185f]
    pci 0000:00:1d.1: reg 20: [io 0x1860-0x187f]
    pci 0000:00:1d.2: reg 20: [io 0x1880-0x189f]
    pci 0000:00:1d.7: reg 10: [mem 0xf8404c00-0xf8404fff]
    pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
    pci 0000:00:1d.7: PME# disabled
    pci 0000:00:1f.0: quirk: [io 0x1000-0x107f] claimed by ICH6 ACPI/GPIO/TCO
    pci 0000:00:1f.0: quirk: [io 0x1180-0x11bf] claimed by ICH6 GPIO
    pci 0000:00:1f.0: ICH7 LPC Generic IO decode 1 PIO at 0680 (mask 007f)
    pci 0000:00:1f.0: ICH7 LPC Generic IO decode 3 PIO at 0068 (mask 0007)
    pci 0000:00:1f.0: ICH7 LPC Generic IO decode 4 PIO at 1640 (mask 007f)
    pci 0000:00:1f.1: reg 10: [io 0x0000-0x0007]
    pci 0000:00:1f.1: reg 14: [io 0x0000-0x0003]
    pci 0000:00:1f.1: reg 18: [io 0x0000-0x0007]
    pci 0000:00:1f.1: reg 1c: [io 0x0000-0x0003]
    pci 0000:00:1f.1: reg 20: [io 0x18a0-0x18af]
    pci 0000:00:1f.2: reg 10: [io 0x18d8-0x18df]
    pci 0000:00:1f.2: reg 14: [io 0x18cc-0x18cf]
    pci 0000:00:1f.2: reg 18: [io 0x18d0-0x18d7]
    pci 0000:00:1f.2: reg 1c: [io 0x18c8-0x18cb]
    pci 0000:00:1f.2: reg 20: [io 0x18e0-0x18ff]
    pci 0000:00:1f.2: reg 24: [mem 0xf8404000-0xf84047ff]
    pci 0000:00:1f.2: PME# supported from D3hot
    pci 0000:00:1f.2: PME# disabled
    pci 0000:00:1f.3: reg 10: [mem 0x00000000-0x000000ff]
    pci 0000:00:1f.3: reg 20: [io 0x1c00-0x1c1f]
    pci 0000:01:00.0: reg 10: [mem 0xc6000000-0xc6ffffff]
    pci 0000:01:00.0: reg 14: [mem 0xd0000000-0xdfffffff 64bit pref]
    pci 0000:01:00.0: reg 1c: [mem 0xc4000000-0xc5ffffff 64bit]
    pci 0000:01:00.0: reg 24: [io 0x2000-0x207f]
    pci 0000:01:00.0: reg 30: [mem 0x00000000-0x0001ffff pref]
    pci 0000:00:01.0: PCI bridge to [bus 01-01]
    pci 0000:00:01.0: bridge window [io 0x2000-0x2fff]
    pci 0000:00:01.0: bridge window [mem 0xc4000000-0xc6ffffff]
    pci 0000:00:01.0: bridge window [mem 0xd0000000-0xdfffffff 64bit pref]
    pci 0000:00:1c.0: PCI bridge to [bus 02-02]
    pci 0000:00:1c.0: bridge window [io 0x3000-0x3fff]
    pci 0000:00:1c.0: bridge window [mem 0xbc000000-0xbfffffff]
    pci 0000:00:1c.0: bridge window [mem 0xcc000000-0xcdffffff 64bit pref]
    pci 0000:04:00.0: reg 10: [mem 0xf0000000-0xf000ffff 64bit]
    pci 0000:04:00.0: PME# supported from D3hot D3cold
    pci 0000:04:00.0: PME# disabled
    pci 0000:00:1c.1: PCI bridge to [bus 04-04]
    pci 0000:00:1c.1: bridge window [io 0x4000-0x4fff]
    pci 0000:00:1c.1: bridge window [mem 0xf0000000-0xf3ffffff]
    pci 0000:00:1c.1: bridge window [mem 0xfa000000-0xfbffffff 64bit pref]
    pci 0000:00:1c.2: PCI bridge to [bus 06-06]
    pci 0000:00:1c.2: bridge window [io 0x5000-0x5fff]
    pci 0000:00:1c.2: bridge window [mem 0xf4000000-0xf7ffffff]
    pci 0000:00:1c.2: bridge window [mem 0xfc000000-0xfdffffff 64bit pref]
    pci 0000:00:1c.3: PCI bridge to [bus 08-08]
    pci 0000:00:1c.3: bridge window [io 0x6000-0x6fff]
    pci 0000:00:1c.3: bridge window [mem 0xb4000000-0xb7ffffff]
    pci 0000:00:1c.3: bridge window [mem 0xc8000000-0xc9ffffff 64bit pref]
    pci 0000:00:1c.4: PCI bridge to [bus 0a-0a]
    pci 0000:00:1c.4: bridge window [io 0xf000-0x0000] (disabled)
    pci 0000:00:1c.4: bridge window [mem 0xfff00000-0x000fffff] (disabled)
    pci 0000:00:1c.4: bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
    pci 0000:0c:00.0: reg 10: [mem 0xf8000000-0xf8003fff]
    pci 0000:0c:00.0: supports D1 D2
    pci 0000:0c:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force'
    pci 0000:00:1c.5: PCI bridge to [bus 0c-0c]
    pci 0000:00:1c.5: bridge window [io 0xf000-0x0000] (disabled)
    pci 0000:00:1c.5: bridge window [mem 0xf8000000-0xf80fffff]
    pci 0000:00:1c.5: bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
    pci 0000:0e:06.0: proprietary Ricoh MMC controller disabled (via firewire function)
    pci 0000:0e:06.0: MMC cards are now supported by standard SDHCI controller
    pci 0000:0e:06.0: reg 10: [mem 0xf8100000-0xf81007ff]
    pci 0000:0e:06.0: supports D1 D2
    pci 0000:0e:06.0: PME# supported from D0 D1 D2 D3hot D3cold
    pci 0000:0e:06.0: PME# disabled
    pci 0000:0e:06.1: reg 10: [mem 0xf8100800-0xf81008ff]
    pci 0000:0e:06.1: supports D1 D2
    pci 0000:0e:06.1: PME# supported from D0 D1 D2 D3hot D3cold
    pci 0000:0e:06.1: PME# disabled
    pci 0000:0e:06.2: reg 10: [mem 0xf8101000-0xf81010ff]
    pci 0000:0e:06.2: supports D1 D2
    pci 0000:0e:06.2: PME# supported from D0 D1 D2 D3hot D3cold
    pci 0000:0e:06.2: PME# disabled
    pci 0000:00:1e.0: PCI bridge to [bus 0e-0e] (subtractive decode)
    pci 0000:00:1e.0: bridge window [io 0xf000-0x0000] (disabled)
    pci 0000:00:1e.0: bridge window [mem 0xf8100000-0xf81fffff]
    pci 0000:00:1e.0: bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
    pci 0000:00:1e.0: bridge window [io 0x0000-0xffff] (subtractive decode)
    pci 0000:00:1e.0: bridge window [mem 0x00000000-0xffffffff] (subtractive decode)
    pci_bus 0000:00: on NUMA node 0
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEGP._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP01._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP02._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP03._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP04._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP05._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP06._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCIB._PRT]
    ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 *5 6 7 10 12 14 15)
    ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 5 6 7 11 12 14 15) *10
    ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 *7 10 12 14 15)
    ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 7 11 12 14 15) *10
    ACPI: PCI Interrupt Link [LNKE] (IRQs 1 3 4 5 6 7 10 12 14 15) *11
    ACPI: PCI Interrupt Link [LNKF] (IRQs 1 3 4 5 6 7 *11 12 14 15)
    ACPI: PCI Interrupt Link [LNKG] (IRQs 1 3 4 5 6 7 10 12 14 15) *11
    ACPI: PCI Interrupt Link [LNKH] (IRQs 1 3 4 5 6 7 11 12 14 15) *10
    HEST: Table is not found!
    vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
    vgaarb: loaded
    PCI: Using ACPI for IRQ routing
    PCI: pci_cache_line_size set to 64 bytes
    reserve RAM buffer: 0000000000002000 - 000000000000ffff
    reserve RAM buffer: 000000000009f800 - 000000000009ffff
    reserve RAM buffer: 000000005fed0000 - 000000005fffffff
    NetLabel: Initializing
    NetLabel: domain hash size = 128
    NetLabel: protocols = UNLABELED CIPSOv4
    NetLabel: unlabeled traffic allowed by default
    HPET: 3 timers in total, 0 timers will be used for per-cpu timer
    hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
    hpet0: 3 comparators, 64-bit 14.318180 MHz counter
    Switching to clocksource tsc
    pnp: PnP ACPI init
    ACPI: bus type pnp registered
    pnp: PnP ACPI: found 10 devices
    ACPI: ACPI bus type pnp unregistered
    system 00:01: [mem 0xfed1c000-0xfed1ffff] has been reserved
    system 00:01: [mem 0xfed14000-0xfed17fff] has been reserved
    system 00:01: [mem 0xfed18000-0xfed18fff] has been reserved
    system 00:01: [mem 0xfed19000-0xfed19fff] has been reserved
    system 00:01: [mem 0xe0000000-0xefffffff] has been reserved
    system 00:01: [mem 0xfed20000-0xfed3ffff] has been reserved
    system 00:01: [mem 0xfed40000-0xfed44fff] has been reserved
    system 00:01: [mem 0xfed45000-0xfed8ffff] has been reserved
    system 00:04: [mem 0xfed00000-0xfed003ff] has been reserved
    system 00:06: [io 0x0680-0x069f] has been reserved
    system 00:06: [io 0x0800-0x080f] has been reserved
    system 00:06: [io 0x1000-0x107f] has been reserved
    system 00:06: [io 0x1180-0x11bf] has been reserved
    system 00:06: [io 0x1640-0x164f] has been reserved
    system 00:06: [io 0xfe00] has been reserved
    system 00:06: [io 0xff00-0xff7f] has been reserved
    pci 0000:00:1c.4: BAR 14: assigned [mem 0x60000000-0x601fffff]
    pci 0000:00:1c.4: BAR 15: assigned [mem 0x60200000-0x603fffff 64bit pref]
    pci 0000:00:1c.5: BAR 15: assigned [mem 0x60400000-0x605fffff 64bit pref]
    pci 0000:00:1c.4: BAR 13: assigned [io 0x7000-0x7fff]
    pci 0000:00:1c.5: BAR 13: assigned [io 0x8000-0x8fff]
    pci 0000:00:1f.3: BAR 0: assigned [mem 0x60600000-0x606000ff]
    pci 0000:00:1f.3: BAR 0: set to [mem 0x60600000-0x606000ff] (PCI address [0x60600000-0x606000ff]
    pci 0000:01:00.0: BAR 6: can't assign mem pref (size 0x20000)
    pci 0000:00:01.0: PCI bridge to [bus 01-01]
    pci 0000:00:01.0: bridge window [io 0x2000-0x2fff]
    pci 0000:00:01.0: bridge window [mem 0xc4000000-0xc6ffffff]
    pci 0000:00:01.0: bridge window [mem 0xd0000000-0xdfffffff 64bit pref]
    pci 0000:00:1c.0: PCI bridge to [bus 02-02]
    pci 0000:00:1c.0: bridge window [io 0x3000-0x3fff]
    pci 0000:00:1c.0: bridge window [mem 0xbc000000-0xbfffffff]
    pci 0000:00:1c.0: bridge window [mem 0xcc000000-0xcdffffff 64bit pref]
    pci 0000:00:1c.1: PCI bridge to [bus 04-04]
    pci 0000:00:1c.1: bridge window [io 0x4000-0x4fff]
    pci 0000:00:1c.1: bridge window [mem 0xf0000000-0xf3ffffff]
    pci 0000:00:1c.1: bridge window [mem 0xfa000000-0xfbffffff 64bit pref]
    pci 0000:00:1c.2: PCI bridge to [bus 06-06]
    pci 0000:00:1c.2: bridge window [io 0x5000-0x5fff]
    pci 0000:00:1c.2: bridge window [mem 0xf4000000-0xf7ffffff]
    pci 0000:00:1c.2: bridge window [mem 0xfc000000-0xfdffffff 64bit pref]
    pci 0000:00:1c.3: PCI bridge to [bus 08-08]
    pci 0000:00:1c.3: bridge window [io 0x6000-0x6fff]
    pci 0000:00:1c.3: bridge window [mem 0xb4000000-0xb7ffffff]
    pci 0000:00:1c.3: bridge window [mem 0xc8000000-0xc9ffffff 64bit pref]
    pci 0000:00:1c.4: PCI bridge to [bus 0a-0a]
    pci 0000:00:1c.4: bridge window [io 0x7000-0x7fff]
    pci 0000:00:1c.4: bridge window [mem 0x60000000-0x601fffff]
    pci 0000:00:1c.4: bridge window [mem 0x60200000-0x603fffff 64bit pref]
    pci 0000:00:1c.5: PCI bridge to [bus 0c-0c]
    pci 0000:00:1c.5: bridge window [io 0x8000-0x8fff]
    pci 0000:00:1c.5: bridge window [mem 0xf8000000-0xf80fffff]
    pci 0000:00:1c.5: bridge window [mem 0x60400000-0x605fffff 64bit pref]
    pci 0000:00:1e.0: PCI bridge to [bus 0e-0e]
    pci 0000:00:1e.0: bridge window [io disabled]
    pci 0000:00:1e.0: bridge window [mem 0xf8100000-0xf81fffff]
    pci 0000:00:1e.0: bridge window [mem pref disabled]
    pci 0000:00:01.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    pci 0000:00:01.0: setting latency timer to 64
    pci 0000:00:1c.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
    pci 0000:00:1c.0: setting latency timer to 64
    pci 0000:00:1c.1: PCI INT B -> GSI 16 (level, low) -> IRQ 16
    pci 0000:00:1c.1: setting latency timer to 64
    pci 0000:00:1c.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
    pci 0000:00:1c.2: setting latency timer to 64
    pci 0000:00:1c.3: PCI INT D -> GSI 19 (level, low) -> IRQ 19
    pci 0000:00:1c.3: setting latency timer to 64
    pci 0000:00:1c.4: PCI INT A -> GSI 17 (level, low) -> IRQ 17
    pci 0000:00:1c.4: setting latency timer to 64
    pci 0000:00:1c.5: PCI INT B -> GSI 16 (level, low) -> IRQ 16
    pci 0000:00:1c.5: setting latency timer to 64
    pci 0000:00:1e.0: setting latency timer to 64
    pci_bus 0000:00: resource 0 [io 0x0000-0xffff]
    pci_bus 0000:00: resource 1 [mem 0x00000000-0xffffffff]
    pci_bus 0000:01: resource 0 [io 0x2000-0x2fff]
    pci_bus 0000:01: resource 1 [mem 0xc4000000-0xc6ffffff]
    pci_bus 0000:01: resource 2 [mem 0xd0000000-0xdfffffff 64bit pref]
    pci_bus 0000:02: resource 0 [io 0x3000-0x3fff]
    pci_bus 0000:02: resource 1 [mem 0xbc000000-0xbfffffff]
    pci_bus 0000:02: resource 2 [mem 0xcc000000-0xcdffffff 64bit pref]
    pci_bus 0000:04: resource 0 [io 0x4000-0x4fff]
    pci_bus 0000:04: resource 1 [mem 0xf0000000-0xf3ffffff]
    pci_bus 0000:04: resource 2 [mem 0xfa000000-0xfbffffff 64bit pref]
    pci_bus 0000:06: resource 0 [io 0x5000-0x5fff]
    pci_bus 0000:06: resource 1 [mem 0xf4000000-0xf7ffffff]
    pci_bus 0000:06: resource 2 [mem 0xfc000000-0xfdffffff 64bit pref]
    pci_bus 0000:08: resource 0 [io 0x6000-0x6fff]
    pci_bus 0000:08: resource 1 [mem 0xb4000000-0xb7ffffff]
    pci_bus 0000:08: resource 2 [mem 0xc8000000-0xc9ffffff 64bit pref]
    pci_bus 0000:0a: resource 0 [io 0x7000-0x7fff]
    pci_bus 0000:0a: resource 1 [mem 0x60000000-0x601fffff]
    pci_bus 0000:0a: resource 2 [mem 0x60200000-0x603fffff 64bit pref]
    pci_bus 0000:0c: resource 0 [io 0x8000-0x8fff]
    pci_bus 0000:0c: resource 1 [mem 0xf8000000-0xf80fffff]
    pci_bus 0000:0c: resource 2 [mem 0x60400000-0x605fffff 64bit pref]
    pci_bus 0000:0e: resource 1 [mem 0xf8100000-0xf81fffff]
    pci_bus 0000:0e: resource 4 [io 0x0000-0xffff]
    pci_bus 0000:0e: resource 5 [mem 0x00000000-0xffffffff]
    NET: Registered protocol family 2
    IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
    TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
    TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
    TCP: Hash tables configured (established 131072 bind 65536)
    TCP reno registered
    UDP hash table entries: 512 (order: 2, 16384 bytes)
    UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
    NET: Registered protocol family 1
    PCI: CLS 64 bytes, default 64
    Unpacking initramfs...
    Freeing initrd memory: 1700k freed
    Simple Boot Flag at 0x38 set to 0x1
    apm: BIOS not found.
    Scanning for low memory corruption every 60 seconds
    audit: initializing netlink socket (disabled)
    type=2000 audit(1294159792.419:1): initialized
    highmem bounce pool size: 64 pages
    HugeTLB registered 4 MB page size, pre-allocated 0 pages
    VFS: Disk quotas dquot_6.5.2
    Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
    msgmni has been set to 1723
    Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
    io scheduler noop registered
    io scheduler deadline registered
    io scheduler cfq registered (default)
    intel_idle: MWAIT substates: 0x22220
    intel_idle: does not run on family 6 model 15
    ERST: Table is not found!
    isapnp: Scanning for PnP cards...
    isapnp: No Plug & Play device found
    Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
    serio: i8042 KBD port at 0x60,0x64 irq 1
    serio: i8042 AUX port at 0x60,0x64 irq 12
    mice: PS/2 mouse device common for all mice
    rtc_cmos 00:07: RTC can wake from S4
    rtc_cmos 00:07: rtc core: registered rtc_cmos as rtc0
    rtc0: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
    cpuidle: using governor ladder
    cpuidle: using governor menu
    TCP cubic registered
    NET: Registered protocol family 17
    Registering the dns_resolver key type
    Using IPI No-Shortcut mode
    PM: Resume from disk failed.
    registered taskstats version 1
    rtc_cmos 00:07: setting system clock to 2011-01-04 16:49:53 UTC (1294159793)
    Initalizing network drop monitor service
    Freeing unused kernel memory: 428k freed
    udev[38]: starting version 165
    input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
    SCSI subsystem initialized
    libata version 3.00 loaded.
    ahci 0000:00:1f.2: version 3.0
    ahci 0000:00:1f.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19
    ahci 0000:00:1f.2: irq 40 for MSI/MSI-X
    ahci 0000:00:1f.2: AHCI 0001.0100 32 slots 3 ports 3 Gbps 0x7 impl SATA mode
    ahci 0000:00:1f.2: flags: 64bit ncq sntf pm led clo pio slum part ccc
    ahci 0000:00:1f.2: setting latency timer to 64
    scsi0 : ahci
    scsi1 : ahci
    scsi2 : ahci
    ata1: SATA max UDMA/133 abar m2048@0xf8404000 port 0xf8404100 irq 40
    ata2: SATA max UDMA/133 abar m2048@0xf8404000 port 0xf8404180 irq 40
    ata3: SATA max UDMA/133 abar m2048@0xf8404000 port 0xf8404200 irq 40
    ata_piix 0000:00:1f.1: version 2.13
    ata_piix 0000:00:1f.1: PCI INT A -> GSI 19 (level, low) -> IRQ 19
    ata_piix 0000:00:1f.1: setting latency timer to 64
    scsi3 : ata_piix
    scsi4 : ata_piix
    ata4: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0x18a0 irq 14
    ata5: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0x18a8 irq 15
    ata4.00: ATAPI: Slimtype DVDRW SSM-8515S, GS09, max UDMA/33
    ata4.00: configured for UDMA/33
    ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    ata2: SATA link down (SStatus 0 SControl 300)
    ata3: SATA link down (SStatus 0 SControl 300)
    ata1.00: unexpected _GTF length (8)
    ata1.00: ATA-8: ST9320423AS, 0002SDM1, max UDMA/133
    ata1.00: 625142448 sectors, multi 16: LBA48 NCQ (depth 31/32)
    ata1.00: unexpected _GTF length (8)
    ata1.00: configured for UDMA/133
    scsi 0:0:0:0: Direct-Access ATA ST9320423AS 0002 PQ: 0 ANSI: 5
    scsi 3:0:0:0: CD-ROM Slimtype DVDRW SSM-8515S GS09 PQ: 0 ANSI: 5
    sd 0:0:0:0: [sda] 625142448 512-byte logical blocks: (320 GB/298 GiB)
    sd 0:0:0:0: [sda] Write Protect is off
    sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
    sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 >
    sd 0:0:0:0: [sda] Attached SCSI disk
    sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
    cdrom: Uniform CD-ROM driver Revision: 3.20
    sr 3:0:0:0: Attached scsi CD-ROM sr0
    EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
    Not activating Mandatory Access Control now since /sbin/tomoyo-init doesn't exist.
    udev[839]: starting version 165
    input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1
    ACPI: Lid Switch [LID0]
    input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2
    ACPI: Power Button [PWRB]
    input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
    ACPI: Power Button [PWRF]
    ACPI: acpi_idle registered with cpuidle
    Monitor-Mwait will be used to enter C-1 state
    Monitor-Mwait will be used to enter C-2 state
    Monitor-Mwait will be used to enter C-3 state
    Marking TSC unstable due to TSC halts in idle
    input: PC Speaker as /devices/platform/pcspkr/input/input4
    Switching to clocksource hpet
    compal-laptop: Identified laptop model 'FL90/IFL90'
    cfg80211: Calling CRDA to update world regulatory domain
    compal-laptop: Driver 0.2.7 successfully loaded
    i801_smbus 0000:00:1f.3: PCI INT C -> GSI 19 (level, low) -> IRQ 19
    Linux agpgart interface v0.103
    pci_hotplug: PCI Hot Plug PCI Core version: 0.5
    iTCO_vendor_support: vendor-support=0
    sdhci: Secure Digital Host Controller Interface driver
    sdhci: Copyright(c) Pierre Ossman
    shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
    sdhci-pci 0000:0e:06.1: SDHCI controller found [1180:0822] (rev 22)
    sdhci-pci 0000:0e:06.1: PCI INT B -> GSI 23 (level, low) -> IRQ 23
    sdhci-pci 0000:0e:06.1: Will use DMA mode even though HW doesn't fully claim to support it.
    Registered led device: mmc0::
    mmc0: SDHCI controller on PCI [0000:0e:06.1] using DMA
    sd 0:0:0:0: Attached scsi generic sg0 type 0
    sr 3:0:0:0: Attached scsi generic sg1 type 5
    ACPI: Battery Slot [BAT1] (battery present)
    ACPI: WMI: Mapper loaded
    ACPI: AC Adapter [ACAD] (on-line)
    usbcore: registered new interface driver usbfs
    usbcore: registered new interface driver hub
    usbcore: registered new device driver usb
    acpi device:03: registered as cooling_device2
    input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:01/LNXVIDEO:00/input/input5
    ACPI: Video Device [VGA] (multi-head: yes rom: no post: no)
    b43-pci-bridge 0000:0c:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
    b43-pci-bridge 0000:0c:00.0: setting latency timer to 64
    ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x11, vendor 0x4243)
    ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x0A, vendor 0x4243)
    ssb: Core 2 found: USB 1.1 Host (cc 0x817, rev 0x03, vendor 0x4243)
    ssb: Core 3 found: PCI-E (cc 0x820, rev 0x01, vendor 0x4243)
    ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    ehci_hcd 0000:00:1a.7: PCI INT C -> GSI 18 (level, low) -> IRQ 18
    ehci_hcd 0000:00:1a.7: setting latency timer to 64
    ehci_hcd 0000:00:1a.7: EHCI Host Controller
    ehci_hcd 0000:00:1a.7: new USB bus registered, assigned bus number 1
    ehci_hcd 0000:00:1a.7: debug port 1
    ehci_hcd 0000:00:1a.7: cache line size of 64 is not supported
    ehci_hcd 0000:00:1a.7: irq 18, io mem 0xf8404800
    ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 4 ports detected
    ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 23 (level, low) -> IRQ 23
    ehci_hcd 0000:00:1d.7: setting latency timer to 64
    ehci_hcd 0000:00:1d.7: EHCI Host Controller
    ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 2
    ehci_hcd 0000:00:1d.7: debug port 1
    ehci_hcd 0000:00:1d.7: cache line size of 64 is not supported
    ehci_hcd 0000:00:1d.7: irq 23, io mem 0xf8404c00
    ssb: Sonics Silicon Backplane found on PCI device 0000:0c:00.0
    ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
    hub 2-0:1.0: USB hub found
    hub 2-0:1.0: 6 ports detected
    firewire_ohci 0000:0e:06.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
    iTCO_wdt: Intel TCO WatchDog Timer Driver v1.06
    iTCO_wdt: Found a ICH8M TCO device (Version=2, TCOBASE=0x1060)
    iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
    psmouse serio1: ID: 10 00 64
    firewire_ohci: Added fw-ohci device 0000:0e:06.0, OHCI v1.10, 4 IR + 4 IT contexts, quirks 0x1
    uhci_hcd: USB Universal Host Controller Interface driver
    uhci_hcd 0000:00:1a.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    uhci_hcd 0000:00:1a.0: setting latency timer to 64
    uhci_hcd 0000:00:1a.0: UHCI Host Controller
    uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 3
    uhci_hcd 0000:00:1a.0: irq 16, io base 0x00001800
    hub 3-0:1.0: USB hub found
    hub 3-0:1.0: 2 ports detected
    uhci_hcd 0000:00:1a.1: PCI INT B -> GSI 21 (level, low) -> IRQ 21
    uhci_hcd 0000:00:1a.1: setting latency timer to 64
    uhci_hcd 0000:00:1a.1: UHCI Host Controller
    uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 4
    uhci_hcd 0000:00:1a.1: irq 21, io base 0x00001820
    hub 4-0:1.0: USB hub found
    hub 4-0:1.0: 2 ports detected
    uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
    uhci_hcd 0000:00:1d.0: setting latency timer to 64
    uhci_hcd 0000:00:1d.0: UHCI Host Controller
    uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 5
    uhci_hcd 0000:00:1d.0: irq 23, io base 0x00001840
    hub 5-0:1.0: USB hub found
    hub 5-0:1.0: 2 ports detected
    uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
    uhci_hcd 0000:00:1d.1: setting latency timer to 64
    uhci_hcd 0000:00:1d.1: UHCI Host Controller
    uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 6
    uhci_hcd 0000:00:1d.1: irq 19, io base 0x00001860
    hub 6-0:1.0: USB hub found
    hub 6-0:1.0: 2 ports detected
    uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
    uhci_hcd 0000:00:1d.2: setting latency timer to 64
    uhci_hcd 0000:00:1d.2: UHCI Host Controller
    uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 7
    uhci_hcd 0000:00:1d.2: irq 18, io base 0x00001880
    hub 7-0:1.0: USB hub found
    hub 7-0:1.0: 2 ports detected
    tg3.c:v3.113 (August 2, 2010)
    tg3 0000:04:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
    tg3 0000:04:00.0: setting latency timer to 64
    tg3 0000:04:00.0: vpd r/w failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update.
    usb 1-2: new high speed USB device using ehci_hcd and address 2
    tg3 0000:04:00.0: vpd r/w failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update.
    elantech: assuming hardware version 1, firmware version 2.0.4
    tg3 0000:04:00.0: vpd r/w failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update.
    tg3 0000:04:00.0: eth0: Tigon3 [partno(none) rev b002] (PCI Express) MAC address 00:1b:38:55:15:a4
    tg3 0000:04:00.0: eth0: attached PHY is 5787 (10/100/1000Base-T Ethernet) (WireSpeed[1])
    tg3 0000:04:00.0: eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1]
    tg3 0000:04:00.0: eth0: dma_rwctrl[76180000] dma_mask[64-bit]
    elantech: Synaptics capabilities query result 0x10, 0x02, 0x64.
    HDA Intel 0000:00:1b.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
    HDA Intel 0000:00:1b.0: irq 41 for MSI/MSI-X
    HDA Intel 0000:00:1b.0: setting latency timer to 64
    input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input6
    firewire_core: created device fw0: GUID 00023f79b240229a, S400
    b43-phy0: Broadcom 4311 WLAN found (core revision 10)
    nvidia: module license 'NVIDIA' taints kernel.
    Disabling lock debugging due to kernel taint
    phy0: Selected rate control algorithm 'minstrel_ht'
    Registered led device: b43-phy0::tx
    Registered led device: b43-phy0::rx
    Registered led device: b43-phy0::radio
    Broadcom 43xx driver loaded [ Features: PMLS, Firmware-ID: FW13 ]
    input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input7
    Linux video capture interface: v2.00
    uvcvideo: Found UVC 1.00 device USB 2.0 Camera (04f2:b018)
    input: USB 2.0 Camera as /devices/pci0000:00/0000:00:1a.7/usb1/1-2/1-2:1.0/input/input8
    usbcore: registered new interface driver uvcvideo
    USB Video Class driver (v0.1.0)
    nvidia 0000:01:00.0: power state changed by ACPI to D0
    nvidia 0000:01:00.0: power state changed by ACPI to D0
    nvidia 0000:01:00.0: enabling device (0000 -> 0003)
    nvidia 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    nvidia 0000:01:00.0: setting latency timer to 64
    vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
    NVRM: The NVIDIA GPU 0000:01:00.0 (PCI ID: 10de:0407) installed
    NVRM: in this system is not supported by the 260.19.29 NVIDIA Linux
    NVRM: graphics driver release. Please see 'Appendix A -
    NVRM: Supported NVIDIA GPU Products' in this release's README,
    NVRM: available on the Linux graphics driver download page at
    NVRM: www.nvidia.com.
    nvidia: probe of 0000:01:00.0 failed with error -1
    NVRM: The NVIDIA probe routine failed for 1 device(s).
    NVRM: None of the NVIDIA graphics adapters were initialized!
    EXT4-fs (sda2): re-mounted. Opts: (null)
    EXT4-fs (sda2): re-mounted. Opts: (null)
    EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
    fuse init (API version 7.15)
    Adding 3156768k swap on /dev/sda3. Priority:-1 extents:1 across:3156768k
    nvidia 0000:01:00.0: setting latency timer to 64
    vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=none,decodes=none:owns=io+mem
    NVRM: The NVIDIA GPU 0000:01:00.0 (PCI ID: 10de:0407) installed
    NVRM: in this system is not supported by the 260.19.29 NVIDIA Linux
    NVRM: graphics driver release. Please see 'Appendix A -
    NVRM: Supported NVIDIA GPU Products' in this release's README,
    NVRM: available on the Linux graphics driver download page at
    NVRM: www.nvidia.com.
    nvidia: probe of 0000:01:00.0 failed with error -1
    NVRM: The NVIDIA probe routine failed for 1 device(s).
    NVRM: None of the NVIDIA graphics adapters were initialized!
    last lines looks interesting, but I also checked mentioned Appendix A of README, and I found 8600M GT (PCI ID 0x0407) between supported chips.

  • Intel Graphics - Lags and glitches since linux 3.6?

    Hi there,
    since the upgrade which included the linux-3.6 package (among others, unfourtunately I have no idea which packages were upgraded exactly, only downgrading the kernel was no fix), I experience graphical glitches when I use my laptop. There's a Ivy Bridge graphics chip in it and I use the intel driver together with SNA. When I boot up the computer it says
    drm:__gen6_gt_force_wake_mt_get] *ERROR* Force wake wait timed out
    and I can find this in my journal from time to time
    Oct 20 21:14:35 marco-thinkpad kernel: [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
    Oct 20 21:14:35 marco-thinkpad kernel: [drm] capturing error event; look for more information in /debug/dri/0/i915_error_state
    Oct 20 21:14:41 marco-thinkpad kernel: [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
    Oct 20 21:14:47 marco-thinkpad kernel: [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
    Oct 20 21:14:53 marco-thinkpad kernel: [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
    Oct 20 21:14:59 marco-thinkpad kernel: [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
    Oct 20 21:15:05 marco-thinkpad kernel: [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
    Oct 20 21:15:11 marco-thinkpad kernel: [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
    Oct 20 21:15:17 marco-thinkpad kernel: [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
    The i915_error_state file is very big, so I had to xz and upload it: http://www30.zippyshare.com/v/33532322/file.html
    Additionally, everything just feels slow somehow, for example KDE's Expose effect gives me approximately 5-6fps while it was perfectly smooth before.
    Here is an example of how the graphical glitches look like: http://www.abload.de/img/intelbug1yostj.png
    I hope there's someone here who can help me Thank you very much in advance!

    kicka wrote:
    xf86-video-intel                   to               2.20.9-1
    xf86-input-evdev                 to               2.7.2.1
    xorg-server                         to              1.12.4.1
    xorg-server-common           to              1.12.4.1
    I downgraded using the aur package https://aur.archlinux.org/packages.php?ID=31937, and put in /etc/pacman.conf
    IgnorePkg = xorg-server xorg-server-common xf86-video-intel xf86-input-evdev
    I experienced the same behaviour - GPU hung. However, I have only encountered it playing Team Fortress 2 using wine and bumblebee. Strange, because the game runs on nvidia card. I had to kill hl2.exe, and restart the game.
    Today, I did exactly what you said, and so far, after 2 hours of gameplay just one crash, but most propably unrelated to the intel GPU. Has anyone opened of found a bug report related to that problem? Downgrading is only a short-term solution.
    About performance regressions, I haven't experienced any using the system normally (but cairo-compmgr isn't heavy for a gpu). On the other hand, Team Fortress 2 has bigger fps drops than before, but that might be my subjective feeling.

  • GT60 0NC, no GPU and fan at 100% all the time

    Hello.
    Recently after many tries to solve nvlddmkm.sys problems I've got final crash. After which my OS could not see my GPU and fan was spinning at full speed. It was after underclocking shader clock from 1240MHz to 1200MHz and opening a game. The screen froze and at the bottom of the it, there was black belt through the screen with RGB colours dots in random locations. Now after full reinstall of the OS from win7 64bit to win8.1 64bit, this all still persist.
    Any ideas would be good, as I could not see nor find any solution to this.
    My current config is:
    -MSI laptop GT60 0NC
    -NVIDIA GPU GeForce GTX 670M
    -Intel Core i7-3630QM
    -Windows 8.1 Pro N 64bit

    So to settle the fan down I would have to disable dGPU. Not just unplug it but disable it. And to do this I would probably need unlocked BIOS. Correct me if I am wrong, if not I would appreciate any leads how to do this.
    And if my dGPU is broken I can at least try the oven. And question about further actions, can i access mini PCI-e in MSI GT60 0NC in any way? To try connecting external GPU via EXP GDC Beast Laptop External Independent Video Card Dock. I do have GTX 460 from my old PC so I am just wondering.

Maybe you are looking for