Intel Graphics chip question

I've got a MBP with the i7 Processor. 15" model. I also got the upgraded 1680x1050 screen too.
Just tonight, when I turned on my machine it powered up normally, flashed the desktop and then went to a fuzzy/snowy screen. Kinda like snow on an old television set that's not getting a signal but with no movement or flickering. I get the pointer but that's it.
When I restart the machine connected to an external monitor via mini display port, all's fine. When I unplug the external screen it goes back to the same screen issue.
When I restart with external monitor, then turn off the auto graphics switching option in the energy saver system preference panel, all's fine, I can unplug the monitor and use my MBP screen. I can use it with the built in nVidia chip, but not the intel. Any one else have troubles with this?
I just updated the system with the latest software update which had a graphics thing in it, but that did not solve the problem. It seems that my intel graphics chip is dead. Any help or guidance is much appreciated.
Brent

It is a new Macbook Pro 15" i7. I did a complete reinstall and unfortunately my Time Machine Back up does not have before I installed Air Display. Still does it. Even with the new update.
Also reinstalled Air Display just to try and uninstall it - no luck
Also tried PRAM reset it stays on a blue screen after start up (Apple with spinning wheel).
Still works with Nvida but the moment I switch to Dynamic it goes to that screen. I did a reinstall with out my applications from Time Machine...Intel works. Of course I have to rebuild everything.

Similar Messages

  • New Intel graphics, OpenGL and CS6

    Currently I'm using an iMac in my home studio but I need to buy a notebook this summer for work, and I'll be using Adobe CS programs so I'll likely have to upgrade to CS6. I'd like to buy a 2.4 GHz 13" MacBook Pro to save a little money (since I have a killer iMac), but I notice the MacBooks now have Intel integrated graphics instead of nVidia. How is OpenGL 2.0 implemented on the Intel graphics chip? Does it work o.k.? I have a chance to buy a late-model 15" MacBook Pro with the discreet graphics card for not much more money, but I don't think I can afford a new MacBook Pro with discreet ATI graphics.
    I am looking for advice: Do photoshop and illustrator work well on the Intel graphics chip?

    Hi tmazzullo,
    I can answer your question with "It depends". I am having issues with non NVidia Graphics Cards while working in Mountain Lion with Illustrator CS6 and applying shadows / effects to text and objects. Everytime I am trying to do this, illustrator crashes.
    If I use a Mac with NVidia it works without any problems. But Intel or Radeon cards force illustrator to crash. I tested this very often on all versions of Mountain Lion so far released an on several Macs. Same result every time.
    Everything else I use in Photoshop or Illustrator works like charm. No problems at all. The Intel HD 4000 is faster than the NVidia 9600M GT in my old MacBook Pro.
    I am designing almost every day in Photoshop and every two days in Illustrator. I have not tested the 3D functions much, so I cannot give you any advice for this.
    If you are sure you are not applying effects to your objects in Illustrator, go for the small portables.
    Hope this helped.
    Edit:
    I have opened a discussion concerning this issue. So maybe there will be an update one day.
    https://discussions.apple.com/message/21739999

  • Can i change out my intel 4 chip set for a better video card on my HP G71 448cl laptop

    I want to play a new video game and this card wont support it.  What are my options.

    Hi,
    Sorry to say but as your Intel Graphics Chip is integrated into the Motherboard it is not an upgradeable component.
    Regards,
    DP-K
    ****Click the White thumb to say thanks****
    ****Please mark Accept As Solution if it solves your problem****
    ****I don't work for HP****
    Microsoft MVP - Windows Experience

  • Is Flash CS4 not compatible with Intel Graphics (laptop)? Really?

    Hi!
    I'm graphic and animation designer. My company buys CS4 suite
    including Photoshop & Flash. And I'm buying a laptop and now
    choosing between one having Intel Graphics and another with ATI
    Radeon. Intel has some features I need, but after googling, finding
    and reading this topic:
    http://www.adobeforums.com/webx?14@@.59b6c473/0
    till the end, I see it does not fully support Photoshop
    CS4!!! I also need Flash CS4 working, so does it support Flash?
    So can you still recommend me buying intel integrated-laptop
    or should I take an ATI Radeon powered one? I need Flash working
    without annoying compatibilites problems. I don't want to buy an
    Intel one, if it is not Photoshop- and Flash- compatible....
    Thank you!

    Anne,
    > after googling, finding and reading this topic:
    >
    http://www.adobeforums.com/webx?14@@.59b6c473/0
    > till the end, I see it [an Intel chip] does not fully
    support
    > Photoshop CS4!!! I also need Flash CS4 working, so does
    > it support Flash?
    It's important you understand what "fully support" means in
    this
    context. According to Eric Palmer's Dec 4 reply (12:11pm),
    Photoshop CS4
    does, in fact, run reliably on systems with Intel graphics.
    Eric purports
    to be an Intel employee, but obviously there's no proof of
    that.
    Regardless, his assertion jibes with with I hear from
    colleagues with Intel
    graphics chips.
    It's not as if Photoshop suddenly fails if you happen to
    choose, say,
    red from the color swatches. It's not as if Photoshop fails
    to export GIFs
    on Intel machines. The only thing you're missing -- and this
    is true for me
    too, even though I don't have Intel equipment -- is
    functionality that
    relies on OpenGL. One of these features, for example, lets
    you rotate the
    canvas while you work on a file. I don't mean rotate the
    image itself ... I
    mean rotate the actual work space without resampling the
    image, just as if
    you were rotating the piece of paper on which you were
    drawing. Granted,
    that sounds like a neat feature (I'd like to experiment with
    it, myself!),
    but it's not a deal-breaker.
    As far as I've seen, the Flash CS4 authoring tool doesn't
    rely on any
    OpenGL-accelerated features.
    David Stiller
    Adobe Community Expert
    Dev blog,
    http://www.quip.net/blog/
    "Luck is the residue of good design."

  • Graphic failure with Intel Graphics

    Hi!
    I got my new MBP 15" i7 two weeks ago and installed all updates that were available.
    I have noticed that if I watch movies in fullscreen mode with the Intel gfxCard and a Growl message appears or if I move my mouse cursor to the hidden dock some graphic failures show up:
    http://img.skitch.com/20100904-by9mfjq6uantsn752ftjc9sg1b.jpg
    This also happens in screensaver if any popup (growl...) appears.
    Thanks a lot!
    StonerL

    Are you forcing the computer to stay on the intel graphics chip with a program (like gfxCardStatus)?
    I have the same computer, but for anything other than simple internet browsing my computer automatically switches to the dedicated nVidia card. As soon as I put up a full screen video or even an app like MS Word it switches cards.

  • 13" macbook pro intel chip question

    I'm considering purchasing the 13" macbook pro. Should I be concened that this model does not have the new intel i chip?

    The short answer is no you should not be concerned, however without knowing how you will be using the computer it may or may not be the best configuration for you. If your needs are primarily Internet based (email, web browsing etc..) and basic functions like MS Office (or equivalent) then you will be quite happy with the current 13" models. However if you are a serious gamer or do other processor intensive applications like 3D renderings, CAD/CAM etc then while the 13" models will do these there are better MBP alternatives.
    The previous poster's assessment of heat and other manufacturer's quality issues are his opinions. Apple does not disclose why it uses the components it does in a specific model therefore his assumption of heat being the reason the 13" models use the Core 2 Duo CPU is a guess. Like any guess he may or may not be correct however at the end of the day it's a guess none the less. Oh and while we're on the subject speculation of Apple's decisions are against the Terms of Use of this forum. As to the longevity of HP computers I seriously doubt he has done an engineering study on these products therefore I give him little credibility on the accuracy of his statement.
    If you really want to find the best product for you go to an Apple Store and use the various models and ask questions. Then you can tell for yourself wether a 13" MBP is the right machine for you or not.
    Regards,
    Roger

  • T520 with Optimus - Can't install Intel Graphics Driver in XP

    Hello,
    I have T520 with Optimus FHD screen.
    I have XP installed in my Ultrabay HDD.
    I understand that XP doesn't support Optimus and that I must go to BIOS and choose either Discrete or Integrated.
    OPTION 1 (Discrete Only)  Which someone what works:
    - So, when I have Discrete enabled in BIOS - and installed Nvidia Drivers in XP - everything works fine, expcept on 90% initial boot ups after going from Win 7 to XP (F12 Options) -  I assume the NVIDIA driver doesn't get initially recognised and the XP boots up in non native resolution.
    - It's only after I restart again and use (F12 again) to pick Ultrabay with XP, the Nvidia gets properly loaded. But this time, there is a prolong delay (60 to 90 seconds) of black screen after the WIndows XP Welcome screen before the desktop appears.
    OPTION 2 (Intgrated Display Only) - Of couse, this after uninstalling NVIDIA Graphic Driver in XP
    - In BIOS, Integrated Graphic in choosen.
    - XP boots up in basic resolution.
    - I download (From Lenovo T520 Driver Page) - Intel Integrated Driver for Win XP 32.
    - When I try to install it, it says "The computer doesn't meet the minimum requirements for installing the software"
    - BTW, I do have all the WIndows Updates including NET 3.0 and higher
    - So then, I try to forcibly installed through Device Manager and Having DISK  - but I get Error message.
    - But somehow, it works after.
    One guess I have and that confuses me is the Otimus Graphic Card - where maybe it can only work with either Optimus Drivers in Windows 7 or Nvidia Drivers in Windows XP. And that the Integrated Intel HD Graphic Drivers in for XP on Lenovo website are only meant for T520 with Intel Graphics ??!!
    Or can optimus be used with intergrated intel drivers only in the XP?
    If anyone can shed a small light, I would be grateful.
    Thanks You
    Solved!
    Go to Solution.

    Glad to know everything is working for you.
    You shouldn't need the discrete to watch flash videos, the Intel integrated should be able to handle that on its own.
    The nVidia card shouldn't be running at all when the machine is in integrated . In fact it doesn't even run in Optimus except when it is actively being used. nVidia proved this when it was first demoing the technology. nVidia removed the nVidia chip from the motherboard of an active system that was running in Optimus using only the integrated graphics, and the computer kept running without issue and the power consumption was the same with and without the chip on the board.
    If you really wanted FireFox to always run with the nVidia card (again, I don't know why you would want this) you can change the settings in the nVidia control panel to force FireFox to run with discrete.
    When asking for help, post your question in the forum. Remember to include your system type, model number and OS. Do not post your serial number.
    Did someone help you today? Press the star on the left to thank them with a Kudo!
    If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help others with the same question in the future.
    My TPs: Twist 2HU: i5-3317U Win 8 Pro, 4GB RAM 250GB Samsung 840 | T420 4177CTO: i5-2520M, HD+, Win 7 Pro x64, 8GB RAM, Optimus, 160GB Intel 320 SSD, Intel 6300 WiFi, BT 3.0 | T400 2764CTO: P8700, WXGA, Win 7 Ult x64, AMD 3470, 8GB RAM, 64GB Samsung SSD, BT, Intel 5300 WiFi | A20m 14.1" PIII 500 (retired). Monitors: 2x Dell U2211h IPS 100% sRGB calibrated w/ Spyder3.

  • When switching the graphics chip, screen faintly blinks once.

    Hi,
    First, this question isn't related with the flickering in some MacBooks Pro models or configurations. It is more sutile situation.
    I read something about this in another post, but I have not been able to find it again until now.
    When I change the graphics mode between the integrated Intel HD chip and discrete nVidia chip, the screen blinks slightly as a small and subtle wink (increase brightness). Yesterday I visited the Genius Bar and I looked into other computers and this did not happen. The technician could see well, but did not give me any answers and I'm not willing to give the computer without any prior guidance.
    Among the solutions that I read was that of reinstalling Mac OS X. I did, but the situation continues.
    Is most noticeable when going from Intel to nVidia chip.
    Does this happen to someone?
    Greetings.
    PS: It is in a MacBook Pro Mid. 2010 model.

    In fact, is both a curiosity and something that I want to resolve if possible.
    What was in the video was simply the change between graphics mode using gfxCardStatus, a simulation of what happens automatically when the system performs the change.
    I had not seen the last line of BSteely, I am sorry. In reality I understand that it is not serious problem, but I draws attention to the note that does not happen in other systems. Thus, I would like to know if it is, for example, in a series of chips with this type of difference.
    This is my second MacBook Pro (I had one of 13" until recently and opted to change it). I have seen lately some items of hardware with defects (in fact, the current is the third computer that I have received after two previous problems with hard drives), and I would like to know if it works as expected. That is...
    Greetings.

  • T400 Graphics Card question

    My parents got me a new laptop (T400) for Christmas it has the Intel graphics card in it but I have theATI Mobility Radeon HD3470 Graphics card. Can I just swap them out or not? I would really like to use this card as I feel it is better just looking for some help on what to do.  If I can swap it out it would be great I do know how to change it out or should I have Lenovo do it for me since they got all the onsite warranty and stuff. Any advice would be greatly appreciated.
    Cheers
    Nomad

    Hi NomadA32,
    Welcome to the forum!
    It is not possible to swap out or replace graphics card on T400, the graphics chip is part of the motherboard. There would in fact be only few handful of notebooks in market that have user upgradable graphics modules.
    Hope it helps.
    Maliha (I don't work for lenovo)
    ThinkPads:- T400[Win 7], T60[Win 7], IBM 240[Win XP]
    IdeaPad: U350
    Apple:- Macbook Air [Snow Leopard]
    Did someone help you today? Compliment them with a Kudos!
    Was your question answered today? Mark it as an Accepted Solution! 
      Lenovo Deutsche Community     Lenovo Comunidad en Español 
    Visit my YouTube Channel

  • How can I disable intel graphics? G570

    Hi!
    I have a question like in the topic. I have a Lenovo G570 laptop with Intel HD integrated Graphics and AMD HD 6300M dedicated Graphics. I'm running on Win7.
    I know that a similar topic was before and that the Intel graphic should switch to amd when necessary but I think it's not working right. The problem is with Skyrim. When I run the game's setup it automatically detects the configuration I possess and chooses the graphic options in the game. As You can imagine they are the lowest possible as it ONLY detects my intel graphic. The AMD adapter is not there (the list which appears to choose from does contain the intel only).
    So, is there ANY way to just turn off the intel adapter and work on amd all the time? It would help a lot. I tried that in device manager but when I disable the intel graphics the screen resolution drops rapidly and aero theme from windows is being disabled. It sucks. As if I was forced to use the intel.
    Can anyone help? I would sure appreciate that a lot.
    Thanks!

    Hi Lenssd9,
    If you could tell us what machine type you're using and the operating system we might be able to pinpoint a means of assisting you without too much reconfiguring.
    Be AWESOME Everyday!
    Donate KUDOS and Click "Accepted Solution"
    Did someone help you today?
    Press the star on the left to thank them with a Kudo!
    If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"
    This will help the rest of the Community with similar issues identify the verified solution and benefit from it.

  • I can't install Intel graphics driver for HP Pavilion G6 2240SH under Windows 8.1

    HI!
    I installed Windows 8.1 Update 1 x64 to my HP Pavilion G6 2240SH laptop. I started install the drivers and I got an error message in the Intel High-Definition setup: "This computer does not meet the minimum requirements for installing the software."
    Intel HD driver version: 10.18.10.3277
    Can anybody help me to solve this problem?
    Thanks,
    Spatrik
    This question was solved.
    View Solution.

    Hello Spatrik, 
    I have read your post on how your notebook computer is displaying an error message that your updated driver does not meet your system requirements, and I would be happy to assist you!
    The first step I recommend is to remove the Intel graphics driver, as well as removing the chipset drivers from Programs and Features. These chipset drivers will be named Intel Chipset Installation Utility and Driver, and Intel Management Engine Interface (MEI) Driver. Once the drivers are removed, please restart your computer.
    When the computer powers back on, please download and install the following drivers:
    Intel Chipset Installation Utility and Driver
    Intel Management Engine Interface (MEI) Driver
    Intel High-Definition (HD) Graphics Driver 
    Once these drivers are re-installed, please follow this document on Using HP Support Assistant (Windows 8). This should help in updating your computer's Intel drivers.   
    Please re-post with the results of your troubleshooting, and I look forward to your reply!
    Regards  
    MechPilot
    I work on behalf of HP
    Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
    Click the “Kudos, Thumbs Up" on the right to say “Thanks” for helping!

  • KDE4 compositing no longer works with Intel graphics card

    I recently upgraded to the new intel graphics card drivers and when I started KDE4, I got a black screen. I disabled compositing through the kwinrc file, but I want it back! Here's my xorg.conf
    Section "ServerLayout"
            Identifier     "Xorg Configured"
            Screen      0  "Screen0" 0 0
            InputDevice    "Keyboard0" "CoreKeyboard"
    EndSection
    Section "ServerFlags"
            Option "AllowMouseOpenFail"  "true"
            Option "AIGLX" "true"
    EndSection
    Section "Module"
            Load  "ddc"  # ddc probing of monitor
            Load  "dbe"
            Load  "dri"
            Load  "extmod"
            Load  "glx"
            Load  "bitmap" # bitmap-fonts
            Load  "freetype"
            Load  "record"
    #       Load  "synaptics"
    EndSection
    Section "InputDevice"
            Identifier  "Keyboard0"
            Driver      "keyboard"
            Option      "CoreKeyboard"
            Option "XkbRules" "xorg"
            Option "XkbModel" "pc105"
            Option "XkbLayout" "gb"
    EndSection
    # Auto-generated by Archie mkxcfg
    Section "Monitor"
            Identifier "Monitor0"
            Option "DPMS" "true"
    EndSection
    # Auto-generated by Archie mkxcfg
    Section "Device"
            Identifier  "Card0"
            Driver      "intel"
    #       Driver      "vesa"
            VendorName  "All"
            BoardName   "All"
            Option      "XAANoOffscreenPixmaps" "true"
            Option      "DRI" "true"
    EndSection
    Section "Screen"
            Identifier "Screen0"
            Device     "Card0"
            Monitor    "Monitor0"
            DefaultColorDepth 24
            SubSection "Display"
                    Depth     24
                    Modes "1280x800" "1024x768" "800x600" "640x480"
            EndSubSection
    EndSection
    Section "DRI"
            Mode 0666
    EndSection
    Section "Extensions"
            Option "Composite" "Enable"
    EndSection
    and my Xorg.0.log
    This is a pre-release version of the X server from The X.Org Foundation.
    It is not supported in any way.
    Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
    Select the "xorg" product for bugs you find in this release.
    Before reporting bugs in pre-release versions please check the
    latest version in the X.Org Foundation git repository.
    See http://wiki.x.org/wiki/GitPage for git access instructions.
    X.Org X Server 1.4.0.90
    Release Date: 5 September 2007
    X Protocol Version 11, Revision 0
    Build Operating System: Linux 2.6.24-ARCH x86_64
    Current Operating System: Linux michael-laptop 2.6.24-ARCH #1 SMP PREEMPT Sun Feb 10 15:44:59 CET 2008 x86_64
    Build Date: 26 January 2008 09:52:13AM
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    Module Loader present
    Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    (==) Log file: "/var/log/Xorg.0.log", Time: Tue Feb 12 11:23:12 2008
    (==) Using config file: "/etc/X11/xorg.conf"
    (==) ServerLayout "Xorg Configured"
    (**) |-->Screen "Screen0" (0)
    (**) | |-->Monitor "Monitor0"
    (**) | |-->Device "Card0"
    (**) |-->Input Device "Keyboard0"
    (**) Option "AllowMouseOpenFail" "true"
    (**) Option "AIGLX" "true"
    (==) Automatically adding devices
    (==) Automatically enabling devices
    (==) No FontPath specified. Using compiled-in default.
    (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi".
    Entry deleted from font path.
    (Run 'mkfontdir' on "/usr/share/fonts/100dpi").
    (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi".
    Entry deleted from font path.
    (Run 'mkfontdir' on "/usr/share/fonts/75dpi").
    (==) FontPath set to:
    /usr/share/fonts/misc,
    /usr/share/fonts/TTF,
    /usr/share/fonts/Type1
    (==) RgbPath set to "/usr/share/X11/rgb"
    (==) ModulePath set to "/usr/lib/xorg/modules"
    (**) Extension "Composite" is enabled
    (==) |-->Input Device "<default pointer>"
    (==) The core pointer device wasn't specified explicitly in the layout.
    Using the default mouse configuration.
    (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    (II) No APM support in BIOS or kernel
    (II) Loader magic: 0x7b0560
    (II) Module ABI versions:
    X.Org ANSI C Emulation: 0.3
    X.Org Video Driver: 2.0
    X.Org XInput driver : 2.0
    X.Org Server Extension : 0.3
    X.Org Font Renderer : 0.5
    (II) Loader running on linux
    (II) LoadModule: "pcidata"
    (II) Loading /usr/lib/xorg/modules//libpcidata.so
    (II) Module pcidata: vendor="X.Org Foundation"
    compiled for 1.4.0.90, module version = 1.0.0
    ABI class: X.Org Video Driver, version 2.0
    (++) using VT number 7
    (II) PCI: PCI scan (all values are in hex)
    (II) PCI: 00:00:0: chip 8086,2a00 card 14c0,0026 rev 0c class 06,00,00 hdr 00
    (II) PCI: 00:02:0: chip 8086,2a02 card 14c0,0026 rev 0c class 03,00,00 hdr 80
    (II) PCI: 00:02:1: chip 8086,2a03 card 14c0,0026 rev 0c class 03,80,00 hdr 80
    (II) PCI: 00:1a:0: chip 8086,2834 card 14c0,0026 rev 03 class 0c,03,00 hdr 80
    (II) PCI: 00:1a:1: chip 8086,2835 card 14c0,0026 rev 03 class 0c,03,00 hdr 00
    (II) PCI: 00:1a:7: chip 8086,283a card 14c0,0026 rev 03 class 0c,03,20 hdr 00
    (II) PCI: 00:1b:0: chip 8086,284b card 14c0,0026 rev 03 class 04,03,00 hdr 00
    (II) PCI: 00:1c:0: chip 8086,283f card 0000,0000 rev 03 class 06,04,00 hdr 81
    (II) PCI: 00:1c:1: chip 8086,2841 card 0000,0000 rev 03 class 06,04,00 hdr 81
    (II) PCI: 00:1c:2: chip 8086,2843 card 0000,0000 rev 03 class 06,04,00 hdr 81
    (II) PCI: 00:1c:3: chip 8086,2845 card 0000,0000 rev 03 class 06,04,00 hdr 81
    (II) PCI: 00:1c:4: chip 8086,2847 card 0000,0000 rev 03 class 06,04,00 hdr 81
    (II) PCI: 00:1c:5: chip 8086,2849 card 0000,0000 rev 03 class 06,04,00 hdr 81
    (II) PCI: 00:1d:0: chip 8086,2830 card 14c0,0026 rev 03 class 0c,03,00 hdr 80
    (II) PCI: 00:1d:1: chip 8086,2831 card 14c0,0026 rev 03 class 0c,03,00 hdr 00
    (II) PCI: 00:1d:2: chip 8086,2832 card 14c0,0026 rev 03 class 0c,03,00 hdr 00
    (II) PCI: 00:1d:7: chip 8086,2836 card 14c0,0026 rev 03 class 0c,03,20 hdr 00
    (II) PCI: 00:1e:0: chip 8086,2448 card 0000,0000 rev f3 class 06,04,01 hdr 01
    (II) PCI: 00:1f:0: chip 8086,2815 card 0000,0000 rev 03 class 06,01,00 hdr 80
    (II) PCI: 00:1f:1: chip 8086,2850 card 14c0,0026 rev 03 class 01,01,8a hdr 00
    (II) PCI: 00:1f:2: chip 8086,2829 card 14c0,0026 rev 03 class 01,06,01 hdr 00
    (II) PCI: 00:1f:3: chip 8086,283e card 14c0,0026 rev 03 class 0c,05,00 hdr 00
    (II) PCI: 04:00:0: chip 14e4,1713 card 14c0,0026 rev 02 class 02,00,00 hdr 00
    (II) PCI: 0c:00:0: chip 8086,4229 card 8086,1101 rev 61 class 02,80,00 hdr 00
    (II) PCI: 0e:06:0: chip 1180,0832 card 14c0,0026 rev 05 class 0c,00,10 hdr 80
    (II) PCI: 0e:06:1: chip 1180,0822 card 14c0,0026 rev 22 class 08,05,00 hdr 80
    (II) PCI: 0e:06:2: chip 1180,0592 card 14c0,0026 rev 12 class 08,80,00 hdr 80
    (II) PCI: End of PCI scan
    (II) Intel Bridge workaround enabled
    (II) Host-to-PCI bridge:
    (II) Bus 0: bridge is at (0:0:0), (0,0,14), BCTRL: 0x0008 (VGA_EN is set)
    (II) Bus 0 I/O range:
    [0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[b]
    (II) Bus 0 non-prefetchable memory range:
    [0] -1 0 0x00000000 - 0xffffffff (0x100000000) MX[b]
    (II) Bus 0 prefetchable memory range:
    [0] -1 0 0x00000000 - 0xffffffff (0x100000000) MX[b]
    (II) PCI-to-PCI bridge:
    (II) Bus 2: bridge is at (0:28:0), (0,2,2), BCTRL: 0x0004 (VGA_EN is cleared)
    (II) Bus 2 I/O range:
    [0] -1 0 0x00002000 - 0x000020ff (0x100) IX[b]
    [1] -1 0 0x00002400 - 0x000024ff (0x100) IX[b]
    [2] -1 0 0x00002800 - 0x000028ff (0x100) IX[b]
    [3] -1 0 0x00002c00 - 0x00002cff (0x100) IX[b]
    (II) Bus 2 non-prefetchable memory range:
    [0] -1 0 0xc0000000 - 0xc3ffffff (0x4000000) MX[b]
    (II) Bus 2 prefetchable memory range:
    [0] -1 0 0xcc000000 - 0xcdffffff (0x2000000) MX[b]
    (II) PCI-to-PCI bridge:
    (II) Bus 4: bridge is at (0:28:1), (0,4,4), BCTRL: 0x0004 (VGA_EN is cleared)
    (II) Bus 4 I/O range:
    [0] -1 0 0x00003000 - 0x000030ff (0x100) IX[b]
    [1] -1 0 0x00003400 - 0x000034ff (0x100) IX[b]
    [2] -1 0 0x00003800 - 0x000038ff (0x100) IX[b]
    [3] -1 0 0x00003c00 - 0x00003cff (0x100) IX[b]
    (II) Bus 4 non-prefetchable memory range:
    [0] -1 0 0xf0000000 - 0xf3ffffff (0x4000000) MX[b]
    (II) Bus 4 prefetchable memory range:
    [0] -1 0 0xfa000000 - 0xfbffffff (0x2000000) MX[b]
    (II) PCI-to-PCI bridge:
    (II) Bus 6: bridge is at (0:28:2), (0,6,6), BCTRL: 0x0004 (VGA_EN is cleared)
    (II) Bus 6 I/O range:
    [0] -1 0 0x00004000 - 0x000040ff (0x100) IX[b]
    [1] -1 0 0x00004400 - 0x000044ff (0x100) IX[b]
    [2] -1 0 0x00004800 - 0x000048ff (0x100) IX[b]
    [3] -1 0 0x00004c00 - 0x00004cff (0x100) IX[b]
    (II) Bus 6 non-prefetchable memory range:
    [0] -1 0 0xf4000000 - 0xf7ffffff (0x4000000) MX[b]
    (II) Bus 6 prefetchable memory range:
    [0] -1 0 0xfc000000 - 0xfdffffff (0x2000000) MX[b]
    (II) PCI-to-PCI bridge:
    (II) Bus 8: bridge is at (0:28:3), (0,8,8), BCTRL: 0x0004 (VGA_EN is cleared)
    (II) Bus 8 I/O range:
    [0] -1 0 0x00005000 - 0x000050ff (0x100) IX[b]
    [1] -1 0 0x00005400 - 0x000054ff (0x100) IX[b]
    [2] -1 0 0x00005800 - 0x000058ff (0x100) IX[b]
    [3] -1 0 0x00005c00 - 0x00005cff (0x100) IX[b]
    (II) Bus 8 non-prefetchable memory range:
    [0] -1 0 0xb8000000 - 0xbbffffff (0x4000000) MX[b]
    (II) Bus 8 prefetchable memory range:
    [0] -1 0 0xc8000000 - 0xc9ffffff (0x2000000) MX[b]
    (II) PCI-to-PCI bridge:
    (II) Bus 10: bridge is at (0:28:4), (0,10,10), BCTRL: 0x0004 (VGA_EN is cleared)
    (II) PCI-to-PCI bridge:
    (II) Bus 12: bridge is at (0:28:5), (0,12,12), BCTRL: 0x0004 (VGA_EN is cleared)
    (II) Bus 12 non-prefetchable memory range:
    [0] -1 0 0xf8200000 - 0xf82fffff (0x100000) MX[b]
    (II) Subtractive PCI-to-PCI bridge:
    (II) Bus 14: bridge is at (0:30:0), (0,14,14), BCTRL: 0x0004 (VGA_EN is cleared)
    (II) Bus 14 non-prefetchable memory range:
    [0] -1 0 0xf8300000 - 0xf83fffff (0x100000) MX[b]
    (II) PCI-to-ISA bridge:
    (II) Bus -1: bridge is at (0:31:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set)
    (--) PCI:*(0:2:0) Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller rev 12, Mem @ 0xf8000000/20, 0xd0000000/28, I/O @ 0x1800/3
    (--) PCI: (0:2:1) Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller rev 12, Mem @ 0xf8100000/20
    (II) Addressable bus resource ranges are
    [0] -1 0 0x00000000 - 0xffffffff (0x100000000) MX[b]
    [1] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[b]
    (II) OS-reported resource ranges:
    [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
    [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [5] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
    (II) Active PCI resource ranges:
    [0] -1 0 0xf8300c00 - 0xf8300cff (0x100) MX[b]
    [1] -1 0 0xf8300800 - 0xf83008ff (0x100) MX[b]
    [2] -1 0 0xf8300000 - 0xf83007ff (0x800) MX[b]
    [3] -1 0 0xf8200000 - 0xf8201fff (0x2000) MX[b]
    [4] -1 0 0xf0000000 - 0xf000ffff (0x10000) MX[b]
    [5] -1 0 0x50000000 - 0x500000ff (0x100) MX[b]
    [6] -1 0 0xf8604000 - 0xf86047ff (0x800) MX[b]
    [7] -1 0 0xf8604c00 - 0xf8604fff (0x400) MX[b]
    [8] -1 0 0xf8400000 - 0xf8403fff (0x4000) MX[b]
    [9] -1 0 0xf8604800 - 0xf8604bff (0x400) MX[b]
    [10] -1 0 0xf8100000 - 0xf81fffff (0x100000) MX[b](B)
    [11] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[b](B)
    [12] -1 0 0xf8000000 - 0xf80fffff (0x100000) MX[b](B)
    [13] -1 0 0x00001c20 - 0x00001c3f (0x20) IX[b]
    [14] -1 0 0x000018e0 - 0x000018ff (0x20) IX[b]
    [15] -1 0 0x000018d0 - 0x000018d3 (0x4) IX[b]
    [16] -1 0 0x000018d8 - 0x000018df (0x8) IX[b]
    [17] -1 0 0x000018d4 - 0x000018d7 (0x4) IX[b]
    [18] -1 0 0x00001c00 - 0x00001c07 (0x8) IX[b]
    [19] -1 0 0x00001810 - 0x0000181f (0x10) IX[b]
    [20] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
    [21] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
    [22] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
    [23] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
    [24] -1 0 0x000018a0 - 0x000018bf (0x20) IX[b]
    [25] -1 0 0x00001880 - 0x0000189f (0x20) IX[b]
    [26] -1 0 0x00001860 - 0x0000187f (0x20) IX[b]
    [27] -1 0 0x00001840 - 0x0000185f (0x20) IX[b]
    [28] -1 0 0x00001820 - 0x0000183f (0x20) IX[b]
    [29] -1 0 0x00001800 - 0x00001807 (0x8) IX[b](B)
    (II) Active PCI resource ranges after removing overlaps:
    [0] -1 0 0xf8300c00 - 0xf8300cff (0x100) MX[b]
    [1] -1 0 0xf8300800 - 0xf83008ff (0x100) MX[b]
    [2] -1 0 0xf8300000 - 0xf83007ff (0x800) MX[b]
    [3] -1 0 0xf8200000 - 0xf8201fff (0x2000) MX[b]
    [4] -1 0 0xf0000000 - 0xf000ffff (0x10000) MX[b]
    [5] -1 0 0x50000000 - 0x500000ff (0x100) MX[b]
    [6] -1 0 0xf8604000 - 0xf86047ff (0x800) MX[b]
    [7] -1 0 0xf8604c00 - 0xf8604fff (0x400) MX[b]
    [8] -1 0 0xf8400000 - 0xf8403fff (0x4000) MX[b]
    [9] -1 0 0xf8604800 - 0xf8604bff (0x400) MX[b]
    [10] -1 0 0xf8100000 - 0xf81fffff (0x100000) MX[b](B)
    [11] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[b](B)
    [12] -1 0 0xf8000000 - 0xf80fffff (0x100000) MX[b](B)
    [13] -1 0 0x00001c20 - 0x00001c3f (0x20) IX[b]
    [14] -1 0 0x000018e0 - 0x000018ff (0x20) IX[b]
    [15] -1 0 0x000018d0 - 0x000018d3 (0x4) IX[b]
    [16] -1 0 0x000018d8 - 0x000018df (0x8) IX[b]
    [17] -1 0 0x000018d4 - 0x000018d7 (0x4) IX[b]
    [18] -1 0 0x00001c00 - 0x00001c07 (0x8) IX[b]
    [19] -1 0 0x00001810 - 0x0000181f (0x10) IX[b]
    [20] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
    [21] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
    [22] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
    [23] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
    [24] -1 0 0x000018a0 - 0x000018bf (0x20) IX[b]
    [25] -1 0 0x00001880 - 0x0000189f (0x20) IX[b]
    [26] -1 0 0x00001860 - 0x0000187f (0x20) IX[b]
    [27] -1 0 0x00001840 - 0x0000185f (0x20) IX[b]
    [28] -1 0 0x00001820 - 0x0000183f (0x20) IX[b]
    [29] -1 0 0x00001800 - 0x00001807 (0x8) IX[b](B)
    (II) OS-reported resource ranges after removing overlaps with PCI:
    [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
    [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [5] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
    (II) All system resource ranges:
    [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
    [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] -1 0 0xf8300c00 - 0xf8300cff (0x100) MX[b]
    [5] -1 0 0xf8300800 - 0xf83008ff (0x100) MX[b]
    [6] -1 0 0xf8300000 - 0xf83007ff (0x800) MX[b]
    [7] -1 0 0xf8200000 - 0xf8201fff (0x2000) MX[b]
    [8] -1 0 0xf0000000 - 0xf000ffff (0x10000) MX[b]
    [9] -1 0 0x50000000 - 0x500000ff (0x100) MX[b]
    [10] -1 0 0xf8604000 - 0xf86047ff (0x800) MX[b]
    [11] -1 0 0xf8604c00 - 0xf8604fff (0x400) MX[b]
    [12] -1 0 0xf8400000 - 0xf8403fff (0x4000) MX[b]
    [13] -1 0 0xf8604800 - 0xf8604bff (0x400) MX[b]
    [14] -1 0 0xf8100000 - 0xf81fffff (0x100000) MX[b](B)
    [15] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[b](B)
    [16] -1 0 0xf8000000 - 0xf80fffff (0x100000) MX[b](B)
    [17] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [18] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
    [19] -1 0 0x00001c20 - 0x00001c3f (0x20) IX[b]
    [20] -1 0 0x000018e0 - 0x000018ff (0x20) IX[b]
    [21] -1 0 0x000018d0 - 0x000018d3 (0x4) IX[b]
    [22] -1 0 0x000018d8 - 0x000018df (0x8) IX[b]
    [23] -1 0 0x000018d4 - 0x000018d7 (0x4) IX[b]
    [24] -1 0 0x00001c00 - 0x00001c07 (0x8) IX[b]
    [25] -1 0 0x00001810 - 0x0000181f (0x10) IX[b]
    [26] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
    [27] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
    [28] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
    [29] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
    [30] -1 0 0x000018a0 - 0x000018bf (0x20) IX[b]
    [31] -1 0 0x00001880 - 0x0000189f (0x20) IX[b]
    [32] -1 0 0x00001860 - 0x0000187f (0x20) IX[b]
    [33] -1 0 0x00001840 - 0x0000185f (0x20) IX[b]
    [34] -1 0 0x00001820 - 0x0000183f (0x20) IX[b]
    [35] -1 0 0x00001800 - 0x00001807 (0x8) IX[b](B)
    (II) "extmod" will be loaded. This was enabled by default and also specifiedin the config file.
    (II) "dbe" will be loaded. This was enabled by default and also specified inthe config file.
    (II) "glx" will be loaded. This was enabled by default and also specified inthe config file.
    (II) "freetype" will be loaded. This was enabled by default and also specified in the config file.
    (II) "record" will be loaded. This was enabled by default and also specifiedin the config file.
    (II) "dri" will be loaded. This was enabled by default and also specified inthe config file.
    (II) LoadModule: "ddc"(II) Module "ddc" already built-in
    (II) LoadModule: "dbe"
    (II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
    (II) Module dbe: vendor="X.Org Foundation"
    compiled for 1.4.0.90, module version = 1.0.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 0.3
    (II) Loading extension DOUBLE-BUFFER
    (II) LoadModule: "dri"
    (II) Loading /usr/lib/xorg/modules/extensions//libdri.so
    (II) Module dri: vendor="X.Org Foundation"
    compiled for 1.4.0.90, module version = 1.0.0
    ABI class: X.Org Server Extension, version 0.3
    (II) Loading extension XFree86-DRI
    (II) LoadModule: "extmod"
    (II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
    (II) Module extmod: vendor="X.Org Foundation"
    compiled for 1.4.0.90, module version = 1.0.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 0.3
    (II) Loading extension SHAPE
    (II) Loading extension MIT-SUNDRY-NONSTANDARD
    (II) Loading extension BIG-REQUESTS
    (II) Loading extension SYNC
    (II) Loading extension MIT-SCREEN-SAVER
    (II) Loading extension XC-MISC
    (II) Loading extension XFree86-VidModeExtension
    (II) Loading extension XFree86-Misc
    (II) Loading extension XFree86-DGA
    (II) Loading extension DPMS
    (II) Loading extension TOG-CUP
    (II) Loading extension Extended-Visual-Information
    (II) Loading extension XVideo
    (II) Loading extension XVideo-MotionCompensation
    (II) Loading extension X-Resource
    (II) LoadModule: "glx"
    (II) Loading /usr/lib/xorg/modules/extensions//libglx.so
    (II) Module glx: vendor="X.Org Foundation"
    compiled for 1.4.0.90, module version = 1.0.0
    ABI class: X.Org Server Extension, version 0.3
    (**) AIGLX enabled
    (II) Loading extension GLX
    (II) LoadModule: "freetype"
    (II) Loading /usr/lib/xorg/modules/fonts//libfreetype.so
    (II) Module freetype: vendor="X.Org Foundation & the After X-TT Project"
    compiled for 1.4.0.90, module version = 2.1.0
    Module class: X.Org Font Renderer
    ABI class: X.Org Font Renderer, version 0.5
    (II) Loading font FreeType
    (II) LoadModule: "record"
    (II) Loading /usr/lib/xorg/modules/extensions//librecord.so
    (II) Module record: vendor="X.Org Foundation"
    compiled for 1.4.0.90, module version = 1.13.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 0.3
    (II) Loading extension RECORD
    (II) LoadModule: "intel"
    (II) Loading /usr/lib/xorg/modules/drivers//intel_drv.so
    (II) Module intel: vendor="X.Org Foundation"
    compiled for 1.4.0.90, module version = 2.2.0
    Module class: X.Org Video Driver
    ABI class: X.Org Video Driver, version 2.0
    (II) LoadModule: "kbd"
    (II) Loading /usr/lib/xorg/modules/input//kbd_drv.so
    (II) Module kbd: vendor="X.Org Foundation"
    compiled for 1.4.0, module version = 1.2.2
    Module class: X.Org XInput Driver
    ABI class: X.Org XInput driver, version 2.0
    (II) LoadModule: "mouse"
    (II) Loading /usr/lib/xorg/modules/input//mouse_drv.so
    (II) Module mouse: vendor="X.Org Foundation"
    compiled for 1.4.0, module version = 1.2.3
    Module class: X.Org XInput Driver
    ABI class: X.Org XInput driver, version 2.0
    (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
    i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G,
    E7221 (i915), 915GM, 945G, 945GM, 945GME, 965G, 965G, 965Q, 946GZ,
    965GM, 965GME/GLE, G33, Q35, Q33
    (II) Primary Device is: PCI 00:02:0
    (--) Assigning device section with no busID to primary device
    (WW) intel: No matching Device section for instance (BusID PCI:0:2:1) found
    (--) Chipset 965GM found
    (II) resource ranges after xf86ClaimFixedResources() call:
    [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
    [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] -1 0 0xf8300c00 - 0xf8300cff (0x100) MX[b]
    [5] -1 0 0xf8300800 - 0xf83008ff (0x100) MX[b]
    [6] -1 0 0xf8300000 - 0xf83007ff (0x800) MX[b]
    [7] -1 0 0xf8200000 - 0xf8201fff (0x2000) MX[b]
    [8] -1 0 0xf0000000 - 0xf000ffff (0x10000) MX[b]
    [9] -1 0 0x50000000 - 0x500000ff (0x100) MX[b]
    [10] -1 0 0xf8604000 - 0xf86047ff (0x800) MX[b]
    [11] -1 0 0xf8604c00 - 0xf8604fff (0x400) MX[b]
    [12] -1 0 0xf8400000 - 0xf8403fff (0x4000) MX[b]
    [13] -1 0 0xf8604800 - 0xf8604bff (0x400) MX[b]
    [14] -1 0 0xf8100000 - 0xf81fffff (0x100000) MX[b](B)
    [15] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[b](B)
    [16] -1 0 0xf8000000 - 0xf80fffff (0x100000) MX[b](B)
    [17] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [18] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
    [19] -1 0 0x00001c20 - 0x00001c3f (0x20) IX[b]
    [20] -1 0 0x000018e0 - 0x000018ff (0x20) IX[b]
    [21] -1 0 0x000018d0 - 0x000018d3 (0x4) IX[b]
    [22] -1 0 0x000018d8 - 0x000018df (0x8) IX[b]
    [23] -1 0 0x000018d4 - 0x000018d7 (0x4) IX[b]
    [24] -1 0 0x00001c00 - 0x00001c07 (0x8) IX[b]
    [25] -1 0 0x00001810 - 0x0000181f (0x10) IX[b]
    [26] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
    [27] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
    [28] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
    [29] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
    [30] -1 0 0x000018a0 - 0x000018bf (0x20) IX[b]
    [31] -1 0 0x00001880 - 0x0000189f (0x20) IX[b]
    [32] -1 0 0x00001860 - 0x0000187f (0x20) IX[b]
    [33] -1 0 0x00001840 - 0x0000185f (0x20) IX[b]
    [34] -1 0 0x00001820 - 0x0000183f (0x20) IX[b]
    [35] -1 0 0x00001800 - 0x00001807 (0x8) IX[b](B)
    (II) resource ranges after probing:
    [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
    [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] -1 0 0xf8300c00 - 0xf8300cff (0x100) MX[b]
    [5] -1 0 0xf8300800 - 0xf83008ff (0x100) MX[b]
    [6] -1 0 0xf8300000 - 0xf83007ff (0x800) MX[b]
    [7] -1 0 0xf8200000 - 0xf8201fff (0x2000) MX[b]
    [8] -1 0 0xf0000000 - 0xf000ffff (0x10000) MX[b]
    [9] -1 0 0x50000000 - 0x500000ff (0x100) MX[b]
    [10] -1 0 0xf8604000 - 0xf86047ff (0x800) MX[b]
    [11] -1 0 0xf8604c00 - 0xf8604fff (0x400) MX[b]
    [12] -1 0 0xf8400000 - 0xf8403fff (0x4000) MX[b]
    [13] -1 0 0xf8604800 - 0xf8604bff (0x400) MX[b]
    [14] -1 0 0xf8100000 - 0xf81fffff (0x100000) MX[b](B)
    [15] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[b](B)
    [16] -1 0 0xf8000000 - 0xf80fffff (0x100000) MX[b](B)
    [17] 0 0 0x000a0000 - 0x000affff (0x10000) MS[b]
    [18] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[b]
    [19] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[b]
    [20] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [21] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
    [22] -1 0 0x00001c20 - 0x00001c3f (0x20) IX[b]
    [23] -1 0 0x000018e0 - 0x000018ff (0x20) IX[b]
    [24] -1 0 0x000018d0 - 0x000018d3 (0x4) IX[b]
    [25] -1 0 0x000018d8 - 0x000018df (0x8) IX[b]
    [26] -1 0 0x000018d4 - 0x000018d7 (0x4) IX[b]
    [27] -1 0 0x00001c00 - 0x00001c07 (0x8) IX[b]
    [28] -1 0 0x00001810 - 0x0000181f (0x10) IX[b]
    [29] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
    [30] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
    [31] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
    [32] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
    [33] -1 0 0x000018a0 - 0x000018bf (0x20) IX[b]
    [34] -1 0 0x00001880 - 0x0000189f (0x20) IX[b]
    [35] -1 0 0x00001860 - 0x0000187f (0x20) IX[b]
    [36] -1 0 0x00001840 - 0x0000185f (0x20) IX[b]
    [37] -1 0 0x00001820 - 0x0000183f (0x20) IX[b]
    [38] -1 0 0x00001800 - 0x00001807 (0x8) IX[b](B)
    [39] 0 0 0x000003b0 - 0x000003bb (0xc) IS[b]
    [40] 0 0 0x000003c0 - 0x000003df (0x20) IS[b]
    (II) Setting vga for screen 0.
    (II) Loading sub module "int10"
    (II) LoadModule: "int10"
    (II) Loading /usr/lib/xorg/modules//libint10.so
    (II) Module int10: vendor="X.Org Foundation"
    compiled for 1.4.0.90, module version = 1.0.0
    ABI class: X.Org Video Driver, version 2.0
    (II) Loading sub module "vbe"
    (II) LoadModule: "vbe"
    (II) Loading /usr/lib/xorg/modules//libvbe.so
    (II) Module vbe: vendor="X.Org Foundation"
    compiled for 1.4.0.90, module version = 1.1.0
    ABI class: X.Org Video Driver, version 2.0
    (II) Loading sub module "vgahw"
    (II) LoadModule: "vgahw"
    (II) Loading /usr/lib/xorg/modules//libvgahw.so
    (II) Module vgahw: vendor="X.Org Foundation"
    compiled for 1.4.0.90, module version = 0.1.0
    ABI class: X.Org Video Driver, version 2.0
    (**) intel(0): Depth 24, (--) framebuffer bpp 32
    (==) intel(0): RGB weight 888
    (==) intel(0): Default visual is TrueColor
    (**) intel(0): Option "DRI" "true"
    (II) intel(0): Integrated Graphics Chipset: Intel(R) 965GM
    (--) intel(0): Chipset: "965GM"
    (--) intel(0): Linear framebuffer at 0xD0000000
    (--) intel(0): IO registers at addr 0xF8000000
    (II) intel(0): 2 display pipes available.
    (==) intel(0): Using EXA for acceleration
    (II) Loading sub module "ddc"
    (II) LoadModule: "ddc"(II) Module "ddc" already built-in
    (II) Loading sub module "i2c"
    (II) LoadModule: "i2c"(II) Module "i2c" already built-in
    (II) intel(0): Output VGA using monitor section Monitor0
    (II) intel(0): I2C bus "CRTDDC_A" initialized.
    (II) intel(0): Output LVDS has no monitor section
    (II) intel(0): I2C bus "LVDSDDC_C" initialized.
    (II) intel(0): I2C device "LVDSDDC_C:ddc2" registered at address 0xA0.
    (II) intel(0): EDID vendor "CPT", prod id 5141
    (II) Loading sub module "int10"
    (II) LoadModule: "int10"
    (II) Reloading /usr/lib/xorg/modules//libint10.so
    (II) intel(0): initializing int10
    (WW) intel(0): Bad V_BIOS checksum
    (II) intel(0): Primary V_BIOS segment is: 0xc000
    (II) intel(0): VESA BIOS detected
    (II) intel(0): VESA VBE Version 3.0
    (II) intel(0): VESA VBE Total Mem: 7616 kB
    (II) intel(0): VESA VBE OEM: Intel(r)Crestline Graphics Chip Accelerated VGABIOS
    (II) intel(0): VESA VBE OEM Software Rev: 1.0
    (II) intel(0): VESA VBE OEM Vendor: Intel Corporation
    (II) intel(0): VESA VBE OEM Product: Intel(r)Crestline Graphics Controller
    (II) intel(0): VESA VBE OEM Product Rev: Hardware Version 0.0
    (II) intel(0): found backlight control method /sys/class/backlight/acpi_video1
    (II) intel(0): I2C bus "SDVOCTRL_E for SDVOB" initialized.
    (II) intel(0): I2C device "SDVOCTRL_E for SDVOB:SDVO Controller B" registered at address 0x70.
    (II) intel(0): No SDVO device found on SDVOB
    (II) intel(0): I2C device "SDVOCTRL_E for SDVOB:SDVO Controller B" removed.
    (II) intel(0): I2C bus "SDVOCTRL_E for SDVOB" removed.
    (II) intel(0): I2C bus "SDVOCTRL_E for SDVOC" initialized.
    (II) intel(0): I2C device "SDVOCTRL_E for SDVOC:SDVO Controller C" registered at address 0x72.
    (II) intel(0): No SDVO device found on SDVOC
    (II) intel(0): I2C device "SDVOCTRL_E for SDVOC:SDVO Controller C" removed.
    (II) intel(0): I2C bus "SDVOCTRL_E for SDVOC" removed.
    (II) intel(0): Output TV has no monitor section
    (II) intel(0): EDID vendor "CPT", prod id 5141
    (II) intel(0): Output VGA disconnected
    (II) intel(0): Output LVDS connected
    (II) intel(0): Output TV disconnected
    (II) intel(0): Output LVDS using initial mode 1280x800
    (II) intel(0): Monitoring connected displays enabled
    (II) intel(0): detected 512 kB GTT.
    (II) intel(0): detected 7676 kB stolen memory.
    (==) intel(0): video overlay key set to 0x101fe
    (==) intel(0): Will not try to enable page flipping
    (==) intel(0): Triple buffering disabled
    (==) intel(0): Using gamma correction (1.0, 1.0, 1.0)
    (==) intel(0): DPI set to (96, 96)
    (II) Loading sub module "fb"
    (II) LoadModule: "fb"
    (II) Loading /usr/lib/xorg/modules//libfb.so
    (II) Module fb: vendor="X.Org Foundation"
    compiled for 1.4.0.90, module version = 1.0.0
    ABI class: X.Org ANSI C Emulation, version 0.3
    (II) Loading sub module "exa"
    (II) LoadModule: "exa"
    (II) Loading /usr/lib/xorg/modules//libexa.so
    (II) Module exa: vendor="X.Org Foundation"
    compiled for 1.4.0.90, module version = 2.2.0
    ABI class: X.Org Video Driver, version 2.0
    (II) Loading sub module "ramdac"
    (II) LoadModule: "ramdac"(II) Module "ramdac" already built-in
    (II) intel(0): Comparing regs from server start up to After PreInit
    (WW) intel(0): Register 0x61200 (PP_STATUS) changed from 0xd0000009 to 0xd000000a
    (WW) intel(0): PP_STATUS before: on, ready, sequencing on
    (WW) intel(0): PP_STATUS after: on, ready, sequencing on
    (II) Loading sub module "dri"
    (II) LoadModule: "dri"
    (II) Reloading /usr/lib/xorg/modules/extensions//libdri.so
    (==) Depth 24 pixmap format is 32 bpp
    (II) do I need RAC? No, I don't.
    (II) resource ranges after preInit:
    [0] 0 0 0xd0000000 - 0xdfffffff (0x10000000) MS[b]
    [1] 0 0 0xf8000000 - 0xf80fffff (0x100000) MS[b]
    [2] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
    [3] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [4] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [5] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [6] -1 0 0xf8300c00 - 0xf8300cff (0x100) MX[b]
    [7] -1 0 0xf8300800 - 0xf83008ff (0x100) MX[b]
    [8] -1 0 0xf8300000 - 0xf83007ff (0x800) MX[b]
    [9] -1 0 0xf8200000 - 0xf8201fff (0x2000) MX[b]
    [10] -1 0 0xf0000000 - 0xf000ffff (0x10000) MX[b]
    [11] -1 0 0x50000000 - 0x500000ff (0x100) MX[b]
    [12] -1 0 0xf8604000 - 0xf86047ff (0x800) MX[b]
    [13] -1 0 0xf8604c00 - 0xf8604fff (0x400) MX[b]
    [14] -1 0 0xf8400000 - 0xf8403fff (0x4000) MX[b]
    [15] -1 0 0xf8604800 - 0xf8604bff (0x400) MX[b]
    [16] -1 0 0xf8100000 - 0xf81fffff (0x100000) MX[b](B)
    [17] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[b](B)
    [18] -1 0 0xf8000000 - 0xf80fffff (0x100000) MX[b](B)
    [19] 0 0 0x000a0000 - 0x000affff (0x10000) MS[b](OprD)
    [20] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[b](OprD)
    [21] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[b](OprD)
    [22] 0 0 0x00001800 - 0x00001807 (0x8) IS[b]
    [23] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [24] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
    [25] -1 0 0x00001c20 - 0x00001c3f (0x20) IX[b]
    [26] -1 0 0x000018e0 - 0x000018ff (0x20) IX[b]
    [27] -1 0 0x000018d0 - 0x000018d3 (0x4) IX[b]
    [28] -1 0 0x000018d8 - 0x000018df (0x8) IX[b]
    [29] -1 0 0x000018d4 - 0x000018d7 (0x4) IX[b]
    [30] -1 0 0x00001c00 - 0x00001c07 (0x8) IX[b]
    [31] -1 0 0x00001810 - 0x0000181f (0x10) IX[b]
    [32] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
    [33] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
    [34] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
    [35] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
    [36] -1 0 0x000018a0 - 0x000018bf (0x20) IX[b]
    [37] -1 0 0x00001880 - 0x0000189f (0x20) IX[b]
    [38] -1 0 0x00001860 - 0x0000187f (0x20) IX[b]
    [39] -1 0 0x00001840 - 0x0000185f (0x20) IX[b]
    [40] -1 0 0x00001820 - 0x0000183f (0x20) IX[b]
    [41] -1 0 0x00001800 - 0x00001807 (0x8) IX[b](B)
    [42] 0 0 0x000003b0 - 0x000003bb (0xc) IS[b](OprU)
    [43] 0 0 0x000003c0 - 0x000003df (0x20) IS[b](OprU)
    (II) intel(0): Kernel reported 238592 total, 1 used
    (II) intel(0): I830CheckAvailableMemory: 954364 kB available
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is 7, (OK)
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is 7, (OK)
    drmOpenByBusid: Searching for BusID pci:0000:00:02.0
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is 7, (OK)
    drmOpenByBusid: drmOpenMinor returns 7
    drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
    (II) [drm] DRM interface version 1.3
    (II) [drm] DRM open master succeeded.
    (II) intel(0): [drm] Using the DRM lock SAREA also for drawables.
    (II) intel(0): [drm] framebuffer mapped by ddx driver
    (II) intel(0): [drm] added 1 reserved context for kernel
    (II) intel(0): X context handle = 0x1
    (II) intel(0): [drm] installed DRM signal handler
    (==) intel(0): VideoRam: 262144 KB
    (**) intel(0): Framebuffer compression disabled
    (**) intel(0): Tiling enabled
    (II) intel(0): Attempting memory allocation with tiled buffers.
    (II) intel(0): Success.
    (II) intel(0): [drm] Registers = 0xf8000000
    (II) intel(0): [drm] ring buffer = 0xd0000000
    (II) intel(0): [drm] mapped front buffer at 0xd0100000, handle = 0xd0100000
    (II) intel(0): [drm] mapped back buffer at 0xd1a00000, handle = 0xd1a00000
    (II) intel(0): [drm] mapped depth buffer at 0xd2040000, handle = 0xd2040000
    (II) intel(0): [drm] mapped classic textures at 0xd2680000, handle = 0xd2680000
    (II) intel(0): [drm] Initialized kernel agp heap manager, 33554432
    (II) intel(0): [dri] visual configs initialized
    (II) intel(0): Page Flipping disabled
    (==) intel(0): Write-combining range (0xd0000000,0x10000000)
    (II) intel(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
    (II) EXA(0): Offscreen pixmap area of 19660800 bytes
    (II) EXA(0): Driver registered support for the following operations:
    (II) Solid
    (II) Copy
    (II) Composite (RENDER acceleration)
    (==) intel(0): Backing store disabled
    (==) intel(0): Silken mouse enabled
    (II) intel(0): Initializing HW Cursor
    (II) intel(0): [DRI] installation complete
    (II) intel(0): [drm] dma control initialized, using IRQ 16
    (II) intel(0): xf86BindGARTMemory: bind key 0 at 0x0077f000 (pgoffset 1919)
    (II) intel(0): xf86BindGARTMemory: bind key 1 at 0x01a00000 (pgoffset 6656)
    (II) intel(0): xf86BindGARTMemory: bind key 2 at 0x02040000 (pgoffset 8256)
    (II) intel(0): xf86BindGARTMemory: bind key 3 at 0x02680000 (pgoffset 9856)
    (II) intel(0): Fixed memory allocation layout:
    (II) intel(0): 0x00000000-0x0001ffff: ring buffer (128 kB)
    (II) intel(0): 0x00020000-0x00029fff: HW cursors (40 kB)
    (II) intel(0): 0x0002a000-0x00031fff: logical 3D context (32 kB)
    (II) intel(0): 0x00032000-0x00041fff: exa G965 state buffer (64 kB)
    (II) intel(0): 0x00100000-0x0073ffff: front buffer (6400 kB) X tiled
    (II) intel(0): 0x00740000-0x019fffff: exa offscreen (19200 kB)
    (II) intel(0): 0x0077f000: end of stolen memory
    (II) intel(0): 0x01a00000-0x0203ffff: back buffer (6400 kB) X tiled
    (II) intel(0): 0x02040000-0x0267ffff: depth buffer (6400 kB) Y tiled
    (II) intel(0): 0x02680000-0x0467ffff: classic textures (32768 kB)
    (II) intel(0): 0x10000000: end of aperture
    (WW) intel(0): ESR is 0x00000001
    (WW) intel(0): Existing errors found in hardware state.
    (II) intel(0): Output configuration:
    (II) intel(0): Pipe A is off
    (II) intel(0): Display plane A is now disabled and connected to pipe A.
    (II) intel(0): Pipe B is on
    (II) intel(0): Display plane B is now enabled and connected to pipe B.
    (II) intel(0): Output VGA is connected to pipe none
    (II) intel(0): Output LVDS is connected to pipe B
    (II) intel(0): Output TV is connected to pipe none
    (**) Option "dpms" "true"
    (**) intel(0): DPMS enabled
    (II) intel(0): Set up textured video
    (II) intel(0): direct rendering: Enabled
    (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    (WW) intel(0): Option "XAANoOffscreenPixmaps" is not used
    (--) RandR disabled
    (II) Initializing built-in extension MIT-SHM
    (II) Initializing built-in extension XInputExtension
    (II) Initializing built-in extension XTEST
    (II) Initializing built-in extension XKEYBOARD
    (II) Initializing built-in extension XC-APPGROUP
    (II) Initializing built-in extension XAccessControlExtension
    (II) Initializing built-in extension SECURITY
    (II) Initializing built-in extension XINERAMA
    (II) Initializing built-in extension XFIXES
    (II) Initializing built-in extension XFree86-Bigfont
    (II) Initializing built-in extension RENDER
    (II) Initializing built-in extension RANDR
    (II) Initializing built-in extension COMPOSITE
    (II) Initializing built-in extension DAMAGE
    (II) Initializing built-in extension XEVIE
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is 8, (OK)
    drmOpenByBusid: Searching for BusID pci:0000:00:02.0
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is 8, (OK)
    drmOpenByBusid: drmOpenMinor returns 8
    drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
    (WW) AIGLX: 3D driver claims to not support visual 0x23
    (WW) AIGLX: 3D driver claims to not support visual 0x24
    (WW) AIGLX: 3D driver claims to not support visual 0x25
    (WW) AIGLX: 3D driver claims to not support visual 0x26
    (WW) AIGLX: 3D driver claims to not support visual 0x27
    (WW) AIGLX: 3D driver claims to not support visual 0x28
    (WW) AIGLX: 3D driver claims to not support visual 0x29
    (WW) AIGLX: 3D driver claims to not support visual 0x2a
    (WW) AIGLX: 3D driver claims to not support visual 0x2b
    (WW) AIGLX: 3D driver claims to not support visual 0x2c
    (WW) AIGLX: 3D driver claims to not support visual 0x2d
    (WW) AIGLX: 3D driver claims to not support visual 0x2e
    (WW) AIGLX: 3D driver claims to not support visual 0x2f
    (WW) AIGLX: 3D driver claims to not support visual 0x30
    (WW) AIGLX: 3D driver claims to not support visual 0x31
    (WW) AIGLX: 3D driver claims to not support visual 0x32
    (II) AIGLX: Loaded and initialized /usr/lib/xorg/modules/dri/i965_dri.so
    (II) GLX: Initialized DRI GL provider for screen 0
    (II) intel(0): Setting screen physical size to 331 x 207
    (**) Option "CoreKeyboard"
    (**) Keyboard0: always reports core events
    (**) Option "Protocol" "standard"
    (**) Keyboard0: Protocol: standard
    (**) Option "AutoRepeat" "500 30"
    (**) Option "XkbRules" "xorg"
    (**) Keyboard0: XkbRules: "xorg"
    (**) Option "XkbModel" "pc105"
    (**) Keyboard0: XkbModel: "pc105"
    (**) Option "XkbLayout" "gb"
    (**) Keyboard0: XkbLayout: "gb"
    (**) Option "CustomKeycodes" "off"
    (**) Keyboard0: CustomKeycodes disabled
    (WW) <default pointer>: No Device specified, looking for one...
    (II) <default pointer>: Setting Device option to "/dev/input/mice"
    (--) <default pointer>: Device: "/dev/input/mice"
    (==) <default pointer>: Protocol: "Auto"
    (**) Option "CorePointer"
    (**) <default pointer>: always reports core events
    (==) <default pointer>: Emulate3Buttons, Emulate3Timeout: 50
    (**) <default pointer>: ZAxisMapping: buttons 4 and 5
    (**) <default pointer>: Buttons: 9
    (**) <default pointer>: Sensitivity: 1
    (II) evaluating device (<default pointer>)
    (II) XINPUT: Adding extended input device "<default pointer>" (type: MOUSE)
    (II) evaluating device (Keyboard0)
    (II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
    (--) <default pointer>: PnP-detected protocol: "ExplorerPS/2"
    (II) <default pointer>: ps2EnableDataReporting: succeeded
    (II) intel(0): EDID vendor "CPT", prod id 5141
    (II) intel(0): Printing DDC gathered Modelines:
    (II) intel(0): Modeline "1280x800"x0.0 68.90 1280 1304 1336 1408 800 801804 813 -hsync -vsync (48.9 kHz)
    (II) intel(0): EDID vendor "CPT", prod id 5141
    (II) 3rd Button detected: disabling emulate3Button
    (II) AIGLX: Suspending AIGLX clients for VT switch
    (II) intel(0): xf86UnbindGARTMemory: unbind key 0
    (II) intel(0): xf86UnbindGARTMemory: unbind key 1
    (II) intel(0): xf86UnbindGARTMemory: unbind key 2
    (II) intel(0): xf86UnbindGARTMemory: unbind key 3
    (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    (II) No APM support in BIOS or kernel
    (II) AIGLX: Resuming AIGLX clients after VT switch
    (II) intel(0): xf86BindGARTMemory: bind key 0 at 0x0077f000 (pgoffset 1919)
    (II) intel(0): xf86BindGARTMemory: bind key 1 at 0x01a00000 (pgoffset 6656)
    (II) intel(0): xf86BindGARTMemory: bind key 2 at 0x02040000 (pgoffset 8256)
    (II) intel(0): xf86BindGARTMemory: bind key 3 at 0x02680000 (pgoffset 9856)
    (II) intel(0): Fixed memory allocation layout:
    (II) intel(0): 0x00000000-0x0001ffff: ring buffer (128 kB)
    (II) intel(0): 0x00020000-0x00029fff: HW cursors (40 kB)
    (II) intel(0): 0x0002a000-0x00031fff: logical 3D context (32 kB)
    (II) intel(0): 0x00032000-0x00041fff: exa G965 state buffer (64 kB)
    (II) intel(0): 0x00100000-0x0073ffff: front buffer (6400 kB) X tiled
    (II) intel(0): 0x00740000-0x019fffff: exa offscreen (19200 kB)
    (II) intel(0): 0x0077f000: end of stolen memory
    (II) intel(0): 0x01a00000-0x0203ffff: back buffer (6400 kB) X tiled
    (II) intel(0): 0x02040000-0x0267ffff: depth buffer (6400 kB) Y tiled
    (II) intel(0): 0x02680000-0x0467ffff: classic textures (32768 kB)
    (II) intel(0): 0x10000000: end of aperture
    (II) intel(0): Output configuration:
    (II) intel(0): Pipe A is off
    (II) intel(0): Display plane A is now disabled and connected to pipe A.
    (II) intel(0): Pipe B is on
    (II) intel(0): Display plane B is now enabled and connected to pipe B.
    (II) intel(0): Output VGA is connected to pipe none
    (II) intel(0): Output LVDS is connected to pipe B
    (II) intel(0): Output TV is connected to pipe none
    (II) intel(0): [drm] mapped front buffer at 0xd0100000, handle = 0x2fff9000
    (II) intel(0): [drm] dma control initialized, using IRQ 16
    (II) <default pointer>: ps2EnableDataReporting: succeeded
    (II) 3rd Button detected: disabling emulate3Button
    Last edited by miggols99 (2008-02-12 14:50:38)

    Maybe it is this bug: http://bugs.kde.org/show_bug.cgi?id=154969
    The decisive effect is 'Improved window management' - if this effect is enabled kwin works normally.
    Last edited by May-C (2008-02-13 01:16:48)

  • Intel graphics 30 bpp support?

    Hi, I am looking into a new monitor and have been searching the web for a while on specs for the Intel Graphics 6000 (on my NUC i5). However I can't find any information on the bit per pixel it supports. The manual for my NUC only says the displayport supports 30 bpp and the hdmi port only support 24 bpp, nothing directly concerning the graphics card. Is it only a driver issue or am I missing something here?
    Christian

    And what is the relevance? Do you actually have a monitor that could benefit from the extended 30bit color range? I'm afraid you are asking the wrong question. That said, it is doubtful that the limited power of any intel graphics could support 30bpc and at the same time keep all required accelerated features in PS running...
    Mylenium

  • [SOLVED] virtual tty covering only part of screen; 2nd graphics chip?

    Hi there!
    I'm running Arch (KDE 4.6.1) on an intel Essential D510mo mobo. Now I'm seeing some graphics issues, which seem interrelated to me:
    1. on the tty the output extends only over part of the screen: the right (estimated) quarter and the bottom (estimated) quarter stay black
    2. plasma device notifications pop up roughly at the same spot where my tty ends. The rest of KDE 'looks normally', extending to the physical borders of my screen
    3. KDE's splash screen (set to Standard, 'Air and Horos Splash Screen') shows two wallpapers: one covering the whole screen, underneath a smaller copy of itself in the same reduced size as seen in 1 and 2
    4. sometimes (mainly when the screen gets driven by my other PC on its DVI-D input) kdm comes up in a lower *resolution*. This lower resolution *might* correspond to the same size as seen in 1 to 3, but it's hard to tell
    Some details regarding my setup:
    - The board is connected to a 1680x1050 TFT via its VGA input.
    - I *think* I'm running KMS (at least switching between TTY's and X works instantly).
    - krandrtray talks of my mobo having two connectors: one is called LVDS1, allowing a resolution of up to 1280x800, the other is called VGA1 allowing a resolution of up to 1680x1050. The ratio of these resolutions roughly corresponds to the two screen sizes I've spoken about in 1-3 above. When clicking krandrtray's 'identify screens', both 'LVDS1' and 'VGA1' are shown on my one physical TFT, slightly shifted (I assume they both are shown in the 'center' of their respective screens). So my mobo seem to think it can drive two screen simultaneously. I don't think so, but I may be wrong.
    - Some time ago, when kdm almost always came up in the wrong resolution, I created a /etc/X11/xorg.conf.d/15-edid.conf to try to force the graphics driver to run at 1680x1050:
    Section "Screen"
    Identifier "Default Screen"
    Device "Intel Corporation "
    Monitor "Generic Monitor"
    DefaultDepth 24
    SubSection "Display"
    Depth 24
    Modes "1680x1050"
    EndSubSection
    EndSection
    I know I'm being terribly vague, sorry for that. If there's any further information you need, I'll be glad to provide it, but at the moment I don't know what to look for. Still, I'd be grateful for any help offered. I'm pretty sure the solution is embarassingly simple.
    Kind regards,
    Rufus
    P.S.: Here go the relevant parts of Xorg.0.log. To my untrained eye, Xorg seems to see two graphics chips:
    [ 8064.638] (II) LoadModule: "glx"
    [ 8064.639] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 8064.680] (II) Module glx: vendor="X.Org Foundation"
    [ 8064.681] compiled for 1.9.4.901, module version = 1.0.0
    [ 8064.681] ABI class: X.Org Server Extension, version 4.0
    [ 8064.681] (==) AIGLX enabled
    [ 8064.681] (II) Loading extension GLX
    [ 8064.681] (II) LoadModule: "record"
    [ 8064.681] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
    [ 8064.682] (II) Module record: vendor="X.Org Foundation"
    [ 8064.682] compiled for 1.9.4.901, module version = 1.13.0
    [ 8064.682] Module class: X.Org Server Extension
    [ 8064.682] ABI class: X.Org Server Extension, version 4.0
    [ 8064.682] (II) Loading extension RECORD
    [ 8064.682] (II) LoadModule: "dri"
    [ 8064.682] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
    [ 8064.683] (II) Module dri: vendor="X.Org Foundation"
    [ 8064.683] compiled for 1.9.4.901, module version = 1.0.0
    [ 8064.683] ABI class: X.Org Server Extension, version 4.0
    [ 8064.683] (II) Loading extension XFree86-DRI
    [ 8064.683] (II) LoadModule: "dri2"
    [ 8064.683] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
    [ 8064.684] (II) Module dri2: vendor="X.Org Foundation"
    [ 8064.684] compiled for 1.9.4.901, module version = 1.2.0
    [ 8064.685] ABI class: X.Org Server Extension, version 4.0
    [ 8064.685] (II) Loading extension DRI2
    [ 8064.685] (==) Matched intel as autoconfigured driver 0
    [ 8064.685] (==) Matched vesa as autoconfigured driver 1
    [ 8064.685] (==) Matched fbdev as autoconfigured driver 2
    [ 8064.685] (==) Assigned the driver to the xf86ConfigLayout
    [ 8064.685] (II) LoadModule: "intel"
    [ 8064.686] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
    [ 8064.688] (II) Module intel: vendor="X.Org Foundation"
    [ 8064.688] compiled for 1.9.4, module version = 2.14.0
    [ 8064.688] Module class: X.Org Video Driver
    [ 8064.688] ABI class: X.Org Video Driver, version 8.0
    [ 8064.688] (II) LoadModule: "vesa"
    [ 8064.690] (WW) Warning, couldn't open module vesa
    [ 8064.690] (II) UnloadModule: "vesa"
    [ 8064.690] (EE) Failed to load module "vesa" (module does not exist, 0)
    [ 8064.690] (II) LoadModule: "fbdev"
    [ 8064.691] (WW) Warning, couldn't open module fbdev
    [ 8064.691] (II) UnloadModule: "fbdev"
    [ 8064.691] (EE) Failed to load module "fbdev" (module does not exist, 0)
    [ 8064.691] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
    i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G,
    E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
    965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
    4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale,
    Sandybridge, Sandybridge, Sandybridge, Sandybridge, Sandybridge,
    Sandybridge, Sandybridge
    [ 8064.693] (++) using VT number 7
    [ 8064.729] drmOpenDevice: node name is /dev/dri/card0
    [ 8064.729] drmOpenDevice: open result is 8, (OK)
    [ 8064.729] drmOpenByBusid: Searching for BusID pci:0000:00:02.0
    [ 8064.729] drmOpenDevice: node name is /dev/dri/card0
    [ 8064.729] drmOpenDevice: open result is 8, (OK)
    [ 8064.729] drmOpenByBusid: drmOpenMinor returns 8
    [ 8064.730] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
    [ 8064.730] (**) intel(0): Depth 24, (--) framebuffer bpp 32
    [ 8064.730] (==) intel(0): RGB weight 888
    [ 8064.730] (==) intel(0): Default visual is TrueColor
    [ 8064.730] (II) intel(0): Integrated Graphics Chipset: Intel(R) Pineview G
    [ 8064.730] (--) intel(0): Chipset: "Pineview G"
    [ 8064.730] (**) intel(0): Tiling enabled
    [ 8064.730] (**) intel(0): SwapBuffers wait enabled
    [ 8064.730] (==) intel(0): video overlay key set to 0x101fe
    [ 8064.731] (II) intel(0): Output LVDS1 has no monitor section
    [ 8064.811] (II) intel(0): Output VGA1 has no monitor section
    [ 8064.811] (II) intel(0): EDID for output LVDS1
    [ 8064.812] (II) intel(0): Not using default mode "320x240" (doublescan mode not supported)
    [ 8064.812] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported)
    [ 8064.812] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported)
    [ 8064.812] (II) intel(0): Not using default mode "512x384" (doublescan mode not supported)
    [ 8064.812] (II) intel(0): Not using default mode "640x480" (doublescan mode not supported)
    [ 8064.812] (II) intel(0): Not using default mode "640x512" (doublescan mode not supported)
    [ 8064.812] (II) intel(0): Not using default mode "800x600" (doublescan mode not supported)
    [ 8064.812] (II) intel(0): Not using default mode "896x672" (doublescan mode not supported)
    [ 8064.812] (II) intel(0): Not using default mode "928x696" (doublescan mode not supported)
    [ 8064.812] (II) intel(0): Not using default mode "960x720" (doublescan mode not supported)
    [ 8064.812] (II) intel(0): Not using default mode "700x525" (doublescan mode not supported)
    [ 8064.812] (II) intel(0): Not using default mode "1024x768" (doublescan mode not supported)
    [ 8064.812] (II) intel(0): Printing probed modes for output LVDS1
    [ 8064.812] (II) intel(0): Modeline "1280x800"x58.1 68.90 1280 1292 1340 1440 800 804 807 823 -hsync -vsync (47.8 kHz)
    [ 8064.812] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
    [ 8064.813] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
    [ 8064.813] (II) intel(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz)
    [ 8064.813] (II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
    [ 8064.874] (II) intel(0): EDID for output VGA1
    [ 8064.874] (II) intel(0): Manufacturer: MAX Model: 7d5 Serial#: 1
    [ 8064.874] (II) intel(0): Year: 2006 Week: 39
    [ 8064.874] (II) intel(0): EDID Version: 1.3
    [ 8064.874] (II) intel(0): Analog Display Input, Input Voltage Level: 0.700/0.300 V
    [ 8064.874] (II) intel(0): Sync: Separate Composite SyncOnGreen
    [ 8064.874] (II) intel(0): Max Image Size [cm]: horiz.: 43 vert.: 27
    [ 8064.874] (II) intel(0): Gamma: 2.20
    [ 8064.874] (II) intel(0): DPMS capabilities: Off; RGB/Color Display
    [ 8064.874] (II) intel(0): Default color space is primary color space
    [ 8064.875] (II) intel(0): First detailed timing is preferred mode
    [ 8064.875] (II) intel(0): redX: 0.640 redY: 0.340 greenX: 0.295 greenY: 0.610
    [ 8064.875] (II) intel(0): blueX: 0.145 blueY: 0.070 whiteX: 0.313 whiteY: 0.329
    [ 8064.875] (II) intel(0): Supported established timings:
    [ 8064.875] (II) intel(0): 720x400@70Hz
    [ 8064.875] (II) intel(0): 640x480@60Hz
    [ 8064.875] (II) intel(0): 640x480@67Hz
    [ 8064.875] (II) intel(0): 640x480@72Hz
    [ 8064.875] (II) intel(0): 640x480@75Hz
    [ 8064.875] (II) intel(0): 800x600@56Hz
    [ 8064.875] (II) intel(0): 800x600@60Hz
    [ 8064.875] (II) intel(0): 800x600@72Hz
    [ 8064.875] (II) intel(0): 800x600@75Hz
    [ 8064.875] (II) intel(0): 832x624@75Hz
    [ 8064.875] (II) intel(0): 1024x768@60Hz
    [ 8064.875] (II) intel(0): 1024x768@70Hz
    [ 8064.875] (II) intel(0): 1024x768@75Hz
    [ 8064.875] (II) intel(0): 1280x1024@75Hz
    [ 8064.876] (II) intel(0): Manufacturer's mask: 0
    [ 8064.876] (II) intel(0): Supported standard timings:
    [ 8064.876] (II) intel(0): #0: hsize: 640 vsize 400 refresh: 70 vid: 2609
    [ 8064.876] (II) intel(0): #1: hsize: 1024 vsize 768 refresh: 72 vid: 19553
    [ 8064.876] (II) intel(0): #2: hsize: 1152 vsize 864 refresh: 75 vid: 20337
    [ 8064.876] (II) intel(0): #3: hsize: 1280 vsize 960 refresh: 60 vid: 16513
    [ 8064.876] (II) intel(0): #4: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
    [ 8064.876] (II) intel(0): #5: hsize: 1440 vsize 900 refresh: 75 vid: 3989
    [ 8064.876] (II) intel(0): Supported detailed timing:
    [ 8064.876] (II) intel(0): clock: 146.2 MHz Image Size: 433 x 270 mm
    [ 8064.876] (II) intel(0): h_active: 1680 h_sync: 1784 h_sync_end 1960 h_blank_end 2240 h_border: 0
    [ 8064.876] (II) intel(0): v_active: 1050 v_sync: 1053 v_sync_end 1059 v_blanking: 1089 v_border: 0
    [ 8064.876] (II) intel(0): Ranges: V min: 56 V max: 75 Hz, H min: 31 H max: 83 kHz, PixClock max 155 MHz
    [ 8064.876] (II) intel(0): Monitor name: B102035W
    [ 8064.876] (II) intel(0): EDID (in hex):
    [ 8064.876] (II) intel(0): 00ffffffffffff003438d50701000000
    [ 8064.877] (II) intel(0): 271001030e2b1b782ec905a3574b9c25
    [ 8064.877] (II) intel(0): 125054bfef00310a614c714f81408180
    [ 8064.877] (II) intel(0): 950f0101010121399030621a274068b0
    [ 8064.877] (II) intel(0): 3600b10e1100001e0000000000000000
    [ 8064.877] (II) intel(0): 00000000000000000000000000fd0038
    [ 8064.877] (II) intel(0): 4b1f530f000a202020202020000000fc
    [ 8064.877] (II) intel(0): 0042313032303335570a2020202000f0
    [ 8064.877] (II) intel(0): Printing probed modes for output VGA1
    [ 8064.877] (II) intel(0): Modeline "1680x1050"x60.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 +hsync +vsync (65.3 kHz)
    [ 8064.877] (II) intel(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz)
    [ 8064.877] (II) intel(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
    [ 8064.877] (II) intel(0): Modeline "1440x900"x75.0 136.75 1440 1536 1688 1936 900 903 909 942 -hsync +vsync (70.6 kHz)
    [ 8064.877] (II) intel(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz)
    [ 8064.877] (II) intel(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz)
    [ 8064.878] (II) intel(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz)
    [ 8064.878] (II) intel(0): Modeline "1024x768"x72.0 78.44 1024 1080 1192 1360 768 769 772 801 -hsync +vsync (57.7 kHz)
    [ 8064.878] (II) intel(0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz)
    [ 8064.878] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
    [ 8064.878] (II) intel(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz)
    [ 8064.878] (II) intel(0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz)
    [ 8064.878] (II) intel(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz)
    [ 8064.878] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
    [ 8064.878] (II) intel(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz)
    [ 8064.878] (II) intel(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 491 520 -hsync -vsync (37.9 kHz)
    [ 8064.878] (II) intel(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz)
    [ 8064.878] (II) intel(0): Modeline "640x480"x66.7 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz)
    [ 8064.878] (II) intel(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
    [ 8064.879] (II) intel(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz)
    [ 8064.879] (II) intel(0): Output LVDS1 connected
    [ 8064.879] (II) intel(0): Output VGA1 connected
    [ 8064.879] (II) intel(0): Using user preference for initial modes
    [ 8064.879] (II) intel(0): Output LVDS1 using initial mode 1280x800
    [ 8064.879] (II) intel(0): Output VGA1 using initial mode 1680x1050
    [ 8064.879] (II) intel(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
    [ 8064.879] (II) intel(0): Kernel page flipping support detected, enabling
    [ 8064.879] (==) intel(0): DPI set to (96, 96)
    [ 8064.879] (II) Loading sub module "fb"
    [ 8064.879] (II) LoadModule: "fb"
    [ 8064.880] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 8064.882] (II) Module fb: vendor="X.Org Foundation"
    [ 8064.882] compiled for 1.9.4.901, module version = 1.0.0
    [ 8064.882] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 8064.882] (II) Loading sub module "dri2"
    [ 8064.882] (II) LoadModule: "dri2"
    [ 8064.882] (II) Reloading /usr/lib/xorg/modules/extensions/libdri2.so
    [ 8064.882] (==) Depth 24 pixmap format is 32 bpp
    [ 8064.883] (II) intel(0): [DRI2] Setup complete
    [ 8064.883] (II) intel(0): [DRI2] DRI driver: i915
    [ 8064.883] (II) intel(0): Allocated new frame buffer 1728x1050 stride 8192, tiled
    [ 8064.883] (II) UXA(0): Driver registered support for the following operations:
    [ 8064.883] (II) solid
    [ 8064.883] (II) copy
    [ 8064.883] (II) composite (RENDER acceleration)
    [ 8064.883] (II) put_image
    [ 8064.883] (II) get_image
    [ 8064.883] (==) intel(0): Backing store disabled
    [ 8064.884] (==) intel(0): Silken mouse enabled
    [ 8064.884] (II) intel(0): Initializing HW Cursor
    [ 8065.019] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    [ 8065.020] (==) intel(0): DPMS enabled
    [ 8065.020] (==) intel(0): Intel XvMC decoder disabled
    [ 8065.020] (II) intel(0): Set up textured video
    [ 8065.020] (II) intel(0): Set up overlay video
    [ 8065.020] (II) intel(0): direct rendering: DRI2 Enabled
    [ 8065.020] (==) intel(0): hotplug detection: "enabled"
    [ 8065.020] (--) RandR disabled
    Last edited by RufusD (2011-03-24 08:36:40)

    OK, it turned out rather easy, I'll write it down here for the record:
    simply add
    video=LVDS-1:d
    to the line
    GRUB_CMDLINE_LINUX_DEFAULT=
    in /etc/default/burg and run the command specified at the top of this file (IIRC, it's "burg-mkconfig -o /boot/burg/burg.cfg"; cf. http://code.google.com/p/burg/wiki/Manu … #Configure)
    This definitely solves issue 1 and 3. Issue 2 *seems* to be solved, issue 4 will need further testing (since it was erratic to begin with)
    Last edited by RufusD (2011-03-24 08:37:37)

  • Will new Intel  "Conroe" chip in Mac towers support more than 4 gig of RAM?

    Hi all,
    long time no speak
    Question:
    Will the new Intel "Conroe" chip in the upcoming Mac towers support more than 4 gig of RAM?
    I score Orchestral and since the new VSL library is completely 24bit i need to at least be able to adress 8 gig of RAM (16 gig would be better
    To APPLE: Guys please be aware that us Pro Users were always eager to adress those 8 gig of RAM in our G5s, but were dissapointed in the fact that Logic FCP etc, were never turned into 64 bit apps.....so adressing 4 gig was it for us........
    I guess another way to ask the same question would be whether "Conroe" is 64 bit, as that is what is required to adress more than 4 gig of RAM.....
    thanx,
    SvK

    Will the new Intel "Conroe" chip in the upcoming Mac
    towers support more than 4 gig of RAM?
    From what I've read Conroe will be 64-bit. A google search of "64-bit conroe" will give you a few sources and more info.
    To APPLE: Guys please be aware that us Pro Users were
    always eager to adress those 8 gig of RAM in our G5s,
    but were dissapointed in the fact that Logic FCP etc,
    were never turned into 64 bit apps.....so adressing 4
    gig was it for us........
    It doesn't need to be a 64-bit application. It just needs to have 64-bit memory addressing. Here is a good article if you're interested.
    http://developer.apple.com/business/macmarket/mathematica.html
    I don't have any experince with VSL, but I did have a quick experience with Kontakt 2 (I sold it). The Kontakt 2 forum has a post from the moderator that explains some issues around Kontakt's memory issues.
    http://www.nativeinstruments.de/forum_us/showthread.php?t=31572
    "furthermore, even Kontakt 2 and related products will not get 64 bit support any time soon since this would require a complete rewrite of the engine - this is the last thing we want at this point! products based on Kontakt 2 are Akoustik Piano and Bandstand."
    The complete rewrite of the audio engine might be the general issue with utilizing more than 4Gb of memory. But, I am not sure...I think there is another issue with how the OS handles memory usage.

Maybe you are looking for