MCU 5320 Hardware Bug

We have a Cisco 5320 MCU.  Recently after upgrading to version 4.5, we had an issue with the MCU performing an unexpected restart.  This problem began to reoccur.  After opening a TAC case, it was noted that this was related to a hardware bug CSCuc98311.  We received an RMA, and after about 2 weeks the problem started happening again.  Another TAC case was opened, it was referenced as the same issue.  This MCU was behaving the same.  Unexpected restarts.  We downgraded to 4.3, the original software we were on, and the problem still occurred. Below is the error fault reference in the log.  We will be receiving our 3rd MCU today.  I am very skeptical about this issue, and the stability of the MCU.  This has caused major interruptinos with multi-point video meetings.  Has anyone else experienced this problem or seen this before?
(2,3) hv_panic: got processor error: PC 0x3_03a0, ICS/PL 0
(2,3) L1_I_ERROR:            0_0000_0000
(2,3) MEM_ERROR_CBOX_ADDR:   0x0058_272d
(2,3) MEM_ERROR_CBOX_STATUS: 0x0001_0083
(2,3) MEM_ERROR_MBOX_ADDR:   0_0000_0000
(2,3) MEM_ERROR_MBOX_STATUS: 0_0000_0000
(2,3) XDN_DEMUX_ERROR:       0_0000_0000
(2,3) DIAG_TRACE_CTL:        0_0000_0000
(2,3) mshim/0:
This is tracked under a known bug CSCuc98311

If you upgrade your MCU 5320 with the TelePresence Server migration software, this will turn the MCU into a TelePresence Server so all features and functionality will be that of a TelePresence Server and not an MCU.  See the Running TS Software on MCU 5300 Series install guide on how to convert your MCU to a TelePresence Server if you're interested.
Here are two good discussions comparing the MCU and TelePresence Server platforms, one of them specifically about migrating from one to the other.
what-difference-between-mcu-cisco-telepresence-server
why-replace-mse-8510-mcu-44-telepresence-server-31
The cisco_ts_3.1_1.98_for_mcu_5300 software is for migrating an MCU 5300 Series to a TelePresence Server.  While the cisco_ts8700_3.1_1.98 software is specifically for hardware that is already running TP Server software, such as the various TelePresence Servers models listed here, this includes MCUs that were migrated to run TP Server software such as the MCU 5300 Series and MCU MSE 8510.

Similar Messages

  • How to create a video only conference at MCU 5320 .. ?

    How to create a video only conference at MCU 5320 .. ?

    Hi,
    This community is for Cisco Webex Meetings Server and Cisco Unified MeetingPlace products. For questions about Telepresence MCU, I would advise you post this question under Telepresence community to get a TP expert answer it.
    I hope this helps.
    -Dejan

  • How to create a audio only conference at MCU 5320 .. ?

    How to create a audio only conference at MCU 5320 .. ?

    Hi Hermanus,
    Please, post this question to Telepresence support community as this community is for Cisco WebEx Meetings Server and Cisco Unified MeetingPlace products and is not being observed by TP experts. Hence, you will not be able to get an answer to your questions.
    I hope this helps.
    -Dejan

  • Software or hardware bug???HELP!

    i was using my 8GB nano-ipod while running and i continuously switched tracks rythmically every second or so.Suddenly, as if the next button got stuck in place and the ipod kept automatically switching on songs one after the other.It kept doing that until i connected it to the computer and refreshed the song list.So, is this a common bug?and what is it related to?i mean, can it be fixed?!.......thx 4 ur help
      Windows XP Pro  

    This was probably just a little glitch in the iPod, and might or might not happen again.
    Does your iPod do this each time you are going through a list of songs ever since, or not?
    If this ever happens again, you can try resetting your iPod:
    Press and hold the Menu and Select (middle of clickwheel) buttons together for about 5-10 seconds.
    You might need to attempt this several times.
    If this behavior seems to keep recurring in your iPod, and quite a few resetting attempts don't seem to work, you might need to try restoring your iPod.
    For instructions, see this:
    Restoring iPod to factory settings
    -Kylene

  • 5320 firmware bugs

    Hi
    I recently upgraded my 5320 expressmusic from 3.08 -> 4.13
    The upgrade was successful.
    But now I am experiencing a few problems.
    1. Sometimes applications terminates unexpectedly with "System error (-1)"
    2. Phone suddenly restarts when invoked from standby
    3. Light timeout has disapeared, Only choice is scrensaver timeout
    4. Phone hangs sometimes while changing songs in music player .it responds after unplugging the headset.
    anyone else experienced similar issues? any solutions?
    Regards, Abhishek.

    Just answering your question abhisek
    1 and 2, when i'm using 4.13 I don't seem have this problem
    3 have another appz to handle it like battery extender, you can get it for free at ovi.
    4 that's the most bothering 4 me while it's XpressMusic but doesn't express me much while it happen.
    So I upgrade it from my phone, not from PC to FW 05.16 then the music doesn't have problem.

  • IPad Mini Hardware Bug Detected

    I recently exchanged my iPad mini becuase it was doing crazy things. In a certain scenario (unknown what at the time). The iPad would go crazy, apps would close others would open randomly, and when I tried to type, random keys would follow, other apps would open.
    Apple was kind enought to give me a new iPad Mini, without asking.
    Now a week later with few apps loaded it has began doing it again. This time I was more observant of my scenario. The issue happened when using the iPad Mini whilst fully charged, and on I believe a CPU intenisve situation. In this case streaming a video on Air Video, perhaps also impacted by other apps in memory per the usual nature of the iPad.
    A guess would be that in an CPU intense application (or just any perhaps), the device allocates power as needed to the app but if being charged the power goes over a normal amount. I notice the device gets hot during this as well. Once unplugged, within a minute or so, the problem goes away.
    It is a problem as I like to leave my device charging when I can.
    Perhaps if Apple cannot fix the problem they can release an app that shows onthe screen that it is charged 100% so I do not have to watch it so close.
    Any tips
    Regards,
    Loren
    @mr_internet

    Never heard of this issue. I would try a Reset and/or Restore, if it is still doing it make another trip to Apple.

  • Serious bug: call set-up problem in case of several DNS SRV records

    Hello Cisco,
    We have a MCU that consists of two servers in cluster. We have SIP SRV DNS records that point to both servers with equal priority and weight.
    All applications work nice with such setup, except from Free Jabber. Jabber is unable to set up the connection most of the time. One time the connection is successful and 5, maybe even 10 times it is unsuccessful.
    For testing, we removed SIP DNS records pointing to one server. This way Jabber works much better. There are some cases when the call set up fails but in most cases it works.
    Looking the logs of the MCU, we can see three different ways, how call set-up may fail. It is probably unreasonable describe the details in this forum message. Anyway, it seems to be sure that in case there SIP SRV records point to one server then Jabber is able to connect the MCU, in case the records point to two servers equally then Jabber is pricnipally unable to connect the MCU. This bug should be fixed, IMHO.
    Btw, what record does Jabber follow, is it _sips._tcp or _sip._tls?
    Greetings and thank you in advance,
    Marko Laurits

    Hello Cisco,
    We have a MCU that consists of two servers in cluster. We have SIP SRV DNS records that point to both servers with equal priority and weight.
    All applications work nice with such setup, except from Free Jabber. Jabber is unable to set up the connection most of the time. One time the connection is successful and 5, maybe even 10 times it is unsuccessful.
    For testing, we removed SIP DNS records pointing to one server. This way Jabber works much better. There are some cases when the call set up fails but in most cases it works.
    Looking the logs of the MCU, we can see three different ways, how call set-up may fail. It is probably unreasonable describe the details in this forum message. Anyway, it seems to be sure that in case there SIP SRV records point to one server then Jabber is able to connect the MCU, in case the records point to two servers equally then Jabber is pricnipally unable to connect the MCU. This bug should be fixed, IMHO.
    Btw, what record does Jabber follow, is it _sips._tcp or _sip._tls?
    Greetings and thank you in advance,
    Marko Laurits

  • Wrh54g hw bug?

    I'm using a crossover cable to bridge 2 routers and it seems that it doesn't work. Is this a hardware bug? I never had issues with a netgear or dlink router. The router works regularly if I just connect it to my dsl modem and such (having more than one host).
    Message Edited by uslacker99 on 04-27-2008 12:30 AM

    Are the IP addresses of two router's different? Try using straight cable.

  • DTMF via MCU

    Topology:
    Video Endpoints x2 •à SIP •à VCS-C •à SIP Ad-Hoc MCU 5320 •à SIP Audio Conference Bridge CUCM
    Right now I have ad-hoc multiway working great on my video units. If a unit calls into the audio conference bridge first does all the DTMF and joins the conference then adds and merges video endpoints everything is fine. The challenge is if they do it in a different order.
    For example let’s say they merge 3 video endpoints together then add the audio conference, the audio conference which is hosted off of CUCM which VCS-C has a SIP connection to never hears the DTMF tones to join the conference. The audio conference only supports RFC 2833 and the SIP trunk from VCS-C to CUCM is set to only support RFC2833.
    Is it possible to have the MCU 5320 send RF2833 DTMF out, even if it’s to all participants in the conference that wouldn’t matter. My main goal here is I want them to be able to join the audio conference in any order, dialed first, last or anywhere in-between.
    Thanks,
    ~~~
    Rate helpful posts
    Blog - http://tripplehelix.net       

    god this is old man here is the user guide all thats in here is as follows
     http://nds1.nokia.com/phones/files/guides/Nokia_3120_UG_en.pdf
    have a look as it may provide more info than the manual
    Direct callingThe multi-mode browser supports functions that you can access while browsing.
    You can make a voice call, send DTMF tones while a voice call is in progress, and
    save in contacts a name and a phone number from a page. 
    If  i have helped at all a click on the white star below would be nice thanks.
    Now using the Lumia 1520

  • MCU Conference Dial out failing

    Hi Everyone
    We have a MCU 5320 running software 4.5(1.45) with TMS 14.4.1. If we schedule a conference in TMS with  hte MCU and a number of our endpoints the conference is created on the MCU but it never dials the endpoints. There's an error "Particaipants not called: awaiting DSP resource". Endpoints can call in to the meeting fine. Has anyone seen this?
    Thanks
    John

    Potentially yes, you might have to do some SIP profile and stuff but I havent seen a config readily available. This *might* get you started where you use MCU in place of the xlite.
    http://www.netcraftsmen.net/blogs/entry/sip-endpoints-in-cisco-communications-manager-call-manager-express-x-lite.html

  • Video conferencing and SIP URI setup

    I am new to Cisco's video products and am trying to configure them for some simple video conferencing. I currently have the following in our environment:
    CUCM v7.1.5
    VCS X7.2.1
    TMS v14.1.0
    MCU 5320 v4.3(2.17)
    EX90 vTC5.1.2
    I am also new to SIP URI dialing. I have done some base configuration on my VCS, TMS, and MCU, following the installation and configuration guide. What I am struggling with is what I need in order to set up the SIP URI info for the EX90. Does there need to be an AD account configured that has a sip directory value? Or can I just use whatever SIP address I want as long as the domain matches what I put in the VCS for the domain and allow list?
    I followed the following guides:
    TMS
    http://www.cisco.com/en/US/docs/telepresence/infrastructure/tms/install_guide/Cisco_TMS_install_guide_14-1.pdf
    VCS
    http://www.cisco.com/en/US/docs/telepresence/infrastructure/vcs/install_guide/Cisco_VCS_Getting_Started_X7-2.pdf
    http://www.cisco.com/en/US/docs/telepresence/infrastructure/vcs/config_guide/Cisco_VCS_Basic_Configuration_Single_VCS_Control_Deployment_Guide_X7-2.pdf
    MCU
    http://www.cisco.com/en/US/docs/telepresence/infrastructure/mcu/install_guide/Cisco_TelePresence_MCU_5300_Series_Getting_started.pdf
    VCS & CUCM Call routing
    http://www.cisco.com/en/US/docs/telepresence/infrastructure/vcs/config_guide/Cisco_VCS_Cisco_Unified_Communications_Manager_Deployment_Guide_CUCM_6-1_7_8_and_X7-0.pdf
    Any assistance and understanding that can be shared would be greatly appreciated!
    Thanks in advance,
    Mr. A little confused - Arras V. Martin

    Hi Arras.  Good morning.  I'm going to hopefully answer some of your questions you have here.  You also may find that the Telepresense Community on the Support Forums is a great place to post this as well. 
    First, I would recomment to you to update from TMS 14.1 to TMS 14.1.1.  There was a major scheduling bug in this release, and had to be removed and updated with TMS 14.1.1.  I would start by updating TMS to that version. 
    CUCM 7.1.5 is a bit older release.  There are some nuasances with this version that have been fixed in 8.6.2 CUCM.  Also, if running 8.5 CUCM or higher, you can add this to TMS and manage TP endpoints on CUCM via this version.  So if you have CTS endpoints or EX, MX and C-series registered to CUCM, you can manage and schedule those units in TMS. 
    Q -Does there need to be an AD account configured that has a sip directory value?
    A - If you add the device in TMS and have it registered to VCS as SIP, you can configure the SIP URI field to whatever SIP URI you wish to assign to the system.  As long as the domain you specify is part of VCS domain and your allow list pattern or rule is ok, the system should register just fine. 
    If you running SIP only environment, you can always restrict bookings in TMS to allow SIP only if this is what your gearing towards. 
    Hope this helps you out a bit.  Feel free to post any more questions here you may have and will do my best to get those answered for ya.
    VR
    Patrick

  • Pure craziness: W530 will post with a DIMM in slot 1 **or** 3, but not both.

    I've been going nuts here, so I apologize in advance if this email sounds a litted harried.
    I have two identical W530s in front of me. Both of them are i7-3820QM and are intended to support up to 32GB of RAM. So I went and ordered 32GB of RAM from Crucial and it showed up this afternoon. I promptly installed it all in machine A because I was in the middle of doing some work on machine B. Everything was fine with machine A.
    After I finished my work on machine B I decided to move the four DIMMs over there for various reasons; machine B will be there final destination. I stuck them in, making sure to seat them nicely. The machine refused to post. I pulled a couple out. The machine refused to post. I put them back in machine A. Machine A posted. Something fishy was up with machine B.
    To make a long story short, read the title of this message. This is seriously one of the weirdest things I have ever encountered with a piece of hardware. If you have all four DIMMs installed, the machine does not post. If you remove **only** DIMM 1, the machine posts. If you remove **only** DIMM 3, the machine posts. Slots 2 and 4 work just fine; whether they are empty or full or partially full doesn't effect a **bleep** thing. I've also tried this with 4GB DIMMs instead of 8GB DIMMS; same deal.
    Just to be ridiculously clear, here are he configurations that work and those that don't. "x" means that slot is empty.
    x x x x - fails, beeps (obviously)
    x x x 4 - works
    x x 3 x - works
    x x 3 4 - works
    x 2 x x - works
    x 2 x 4 - works
    x 2 3 x - works
    x 2 3 4 - works
    1 x x x - works
    1 x x 4 - works
    1 x 3 x - fails silently
    1 x 3 4 - fails silently
    1 2 x x - works
    1 2 x 4 - works
    1 2 3 x - fails silently
    1 2 3 4 - fails silently
    **bleep** is going on here? The BIOS isn't even giving error beeps in the failure modes. If I'm somehow being a total moron, please let me know; that is so much more satisfying than the idea of a machine that can't use all its RAM slots because of some weird hardware bug.
    Thanks!

    OK, so you've contacted service for repair on this system? I think that you've exhausted all user actions to correct.
    W520, i7-2820QM, BIOS 1.42, 1920x1080 FHD, 32 GB RAM, 2000M NVIDIA GPU, Samsung 850 Pro 1TB SSD, Crucial M550 mSata 512GB, WD 2TB USB 3.0, eSata Plextor PX-LB950UE BluRay
    W520, i7-2760QM, BIOS 1.42 1920x1080 FHD, 32 GB RAM, 1000M NVIDIA GPU, Crucial M500 480GB mSata SSD, Hitachi 500GB HDD, WD 2TB USB 3.0

  • PB G4 17" 1.5hz:: slot1 (reversed) == EMPTY.  WHAT?!!!

    Hiya,
    I've just recently discovered that my Powerbook G4 17" (1.5hz) is no longer happy with its SLOT1 (Reversed) memory slot. Whereas I previously had two (2x) 1gig SODIMMS in there, installed for me on the day I bought it by the Apple guys, I now have only 1gig available.
    Swapping the SODIMMS around reveals that yes, in fact, the reversed slot (SLOT1) no longer works. Both SODIMM chips work just fine in the upper slot, reporting 1gig of RAM, but neither one is detected by the bottom slot. I bought this machine in September 2004 .. so that means I'm screwed, right?
    Anyone know a solution? The problem is I no longer live in the country I bought this Powerbook (Australia) and have to suffer through the European Apple support dilemna .. is there an easier way to fix this? Is it something I can repair myself (I'm a qualified electronics repair guy, can handle a lot of the surface-mount repair stuff myself in my own lab...)
    If anyone has any clues how to fix this without a) paying Apple through the nose to fix their hardware bugs, and b) having to ship my most important work-tool back to Australia, and c) waiting weeks and weeks.. please let me know. I really want my 2Gigs back!

    Welcome to Apple Discussions gurgnox!
    Had you purchased AppleCare, you'd still be under its coverage today. The AppleCare coverage is 3 years from date of computer's purchase. In the future always purchase AppleCare in the first year. Unfortunately the memory slot replacement program only applies to the 15" Powerbook and not the 17". Therefore, your issue would have to be resolved under AppleCare. I would contact AppleCare wherever you are at and at least let them know you have the issue. http://www.apple.com/contact/phone_contacts.html
    Unless more people having the issue report to AppleCare directly that they are having it, the chances of us seeing a repair program that extends beyond:
    http://docs.info.apple.com/article.html?artnum=303173-de
    http://docs.info.apple.com/article.html?artnum=303173
    won't ever get extended to other models.
    You might want to try resetting the PRAM and see if that helps.
    http://docs.info.apple.com/article.html?artnum=2238
    And other posters who are having problems who need resolution, please post a new topic thread here:
    http://discussions.apple.com/forum.jspa?forumID=1027
    First off, you'll get a wider audience who may be able to solve your problem. Secondly, responses to you won't confuse the original poster with solutions that don't apply to them. And thirdly, you'll know for certain whether or not a response applies to you.

  • [Solved] mga crashes xorg

    Hi all.
    I have a Matrox Millennium II and every time i use mga (xf86-video-mga) on the Screen section of xorg.conf, the Xorg crashes. I have tried to use the xorg.conf generated by Xubuntu 7.10 (which runs great on that distro) on Arch, but no success.
    Here's the xorg.conf (generated by Xubuntu):
    # xorg.conf (xorg X Window System server configuration file)
    # This file was generated by dexconf, the Debian X Configuration tool, using
    # values from the debconf database.
    # Edit this file with caution, and see the xorg.conf manual page.
    # (Type "man xorg.conf" at the shell prompt.)
    # This file is automatically updated on xserver-xorg package upgrades *only*
    # if it has not been modified since the last upgrade of the xserver-xorg
    # package.
    # If you have edited this file but would like it to be automatically updated
    # again, run the following command:
    # sudo dpkg-reconfigure -phigh xserver-xorg
    Section "Files"
    EndSection
    Section "InputDevice"
    Identifier "Generic Keyboard"
    Driver "kbd"
    Option "CoreKeyboard"
    Option "XkbRules" "xorg"
    Option "XkbModel" "pc105"
    Option "XkbLayout" "pt"
    EndSection
    Section "InputDevice"
    Identifier "Configured Mouse"
    Driver "mouse"
    Option "CorePointer"
    Option "Device" "/dev/input/mice"
    Option "Protocol" "ImPS/2"
    Option "ZAxisMapping" "4 5"
    Option "Emulate3Buttons" "true"
    EndSection
    Section "InputDevice"
    Driver "wacom"
    Identifier "stylus"
    Option "Device" "/dev/input/wacom"
    Option "Type" "stylus"
    Option "ForceDevice" "ISDV4" # Tablet PC ONLY
    EndSection
    Section "InputDevice"
    Driver "wacom"
    Identifier "eraser"
    Option "Device" "/dev/input/wacom"
    Option "Type" "eraser"
    Option "ForceDevice" "ISDV4" # Tablet PC ONLY
    EndSection
    Section "InputDevice"
    Driver "wacom"
    Identifier "cursor"
    Option "Device" "/dev/input/wacom"
    Option "Type" "cursor"
    Option "ForceDevice" "ISDV4" # Tablet PC ONLY
    EndSection
    Section "Device"
    Identifier "Matrox Graphics, Inc. MGA 2164W [Millennium II]"
    Driver "mga"
    BusID "PCI:1:7:0"
    Option "OldDmaInit" "True"
    EndSection
    Section "Monitor"
    Identifier "Monitor Genérico"
    Option "DPMS"
    EndSection
    Section "Screen"
    Identifier "Default Screen"
    Device "Matrox Graphics, Inc. MGA 2164W [Millennium II]"
    Monitor "Monitor Genérico"
    DefaultDepth 24
    SubSection "Display"
    Modes "1280x1024" "1024x768" "832x624" "800x600" "720x400" "640x480"
    EndSubSection
    EndSection
    Section "ServerLayout"
    Identifier "Default Layout"
    Screen "Default Screen"
    InputDevice "Generic Keyboard"
    InputDevice "Configured Mouse"
    # Uncomment if you have a wacom tablet
    # InputDevice "stylus" "SendCoreEvents"
    # InputDevice "cursor" "SendCoreEvents"
    # InputDevice "eraser" "SendCoreEvents"
    EndSection
    Here's the /var/log/Xorg.0.log (sorry, it's long):
    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 i686
    Current Operating System: Linux localhost 2.6.24-ARCH #1 SMP PREEMPT Sun Feb 10 15:21:33 UTC 2008 i686
    Build Date: 03 February 2008 02:54:48PM
    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: Sat Mar 1 19:50:21 2008
    (==) Using config file: "/etc/X11/xorg.conf"
    (==) ServerLayout "Default Layout"
    (**) |-->Screen "Default Screen" (0)
    (**) | |-->Monitor "Monitor Genérico"
    (**) | |-->Device "Matrox Graphics, Inc. MGA 2164W [Millennium II]"
    (**) |-->Input Device "Generic Keyboard"
    (**) |-->Input Device "Configured Mouse"
    (==) Automatically adding devices
    (==) Automatically enabling devices
    (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").
    (==) FontPath set to:
    /usr/share/fonts/misc,
    /usr/share/fonts/75dpi:unscaled,
    /usr/share/fonts/TTF,
    /usr/share/fonts/Type1
    (==) RgbPath set to "/usr/share/X11/rgb"
    (==) ModulePath set to "/usr/lib/xorg/modules"
    (II) Open ACPI successful (/var/run/acpid.socket)
    (II) Loader magic: 0x81d65c0
    (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 4
    (II) PCI: PCI scan (all values are in hex)
    (II) PCI: 00:00:0: chip 10de,02f4 card 10de,02f4 rev a2 class 05,00,00 hdr 80
    (II) PCI: 00:00:1: chip 10de,02fa card 10de,02fa rev a2 class 05,00,00 hdr 80
    (II) PCI: 00:00:2: chip 10de,02fe card 10de,02fe rev a2 class 05,00,00 hdr 80
    (II) PCI: 00:00:3: chip 10de,02f8 card 10de,02f8 rev a2 class 05,00,00 hdr 80
    (II) PCI: 00:00:4: chip 10de,02f9 card 10de,02f9 rev a2 class 05,00,00 hdr 00
    (II) PCI: 00:00:5: chip 10de,02ff card 10de,02ff rev a2 class 05,00,00 hdr 80
    (II) PCI: 00:00:6: chip 10de,027f card 10de,027f rev a2 class 05,00,00 hdr 80
    (II) PCI: 00:00:7: chip 10de,027e card 10de,027e rev a2 class 05,00,00 hdr 80
    (II) PCI: 00:08:0: chip 10de,0369 card 1043,cb84 rev a1 class 05,00,00 hdr 00
    (II) PCI: 00:09:0: chip 10de,0360 card 1043,cb84 rev a2 class 06,01,00 hdr 80
    (II) PCI: 00:09:1: chip 10de,0368 card 1043,cb84 rev a2 class 0c,05,00 hdr 80
    (II) PCI: 00:09:2: chip 10de,036a card 1043,cb84 rev a2 class 05,00,00 hdr 80
    (II) PCI: 00:0a:0: chip 10de,036c card 1043,cb84 rev a1 class 0c,03,10 hdr 80
    (II) PCI: 00:0a:1: chip 10de,036d card 1043,cb84 rev a2 class 0c,03,20 hdr 80
    (II) PCI: 00:0c:0: chip 10de,036e card 1043,cb84 rev a1 class 01,01,8a hdr 00
    (II) PCI: 00:0d:0: chip 10de,037f card 1043,cb84 rev a2 class 01,01,85 hdr 80
    (II) PCI: 00:0d:1: chip 10de,037f card 1043,cb84 rev a2 class 01,01,85 hdr 80
    (II) PCI: 00:0d:2: chip 10de,037f card 1043,cb84 rev a2 class 01,01,85 hdr 80
    (II) PCI: 00:0e:0: chip 10de,0370 card 0000,0000 rev a2 class 06,04,01 hdr 81
    (II) PCI: 00:0e:1: chip 10de,0371 card 1043,81f6 rev a2 class 04,03,00 hdr 80
    (II) PCI: 00:10:0: chip 10de,0373 card 1043,cb84 rev a2 class 06,80,00 hdr 00
    (II) PCI: 00:11:0: chip 10de,0373 card 1043,cb84 rev a2 class 06,80,00 hdr 00
    (II) PCI: 00:16:0: chip 10de,0375 card 0000,0000 rev a2 class 06,04,00 hdr 01
    (II) PCI: 00:18:0: chip 1022,1100 card 0000,0000 rev 00 class 06,00,00 hdr 80
    (II) PCI: 00:18:1: chip 1022,1101 card 0000,0000 rev 00 class 06,00,00 hdr 80
    (II) PCI: 00:18:2: chip 1022,1102 card 0000,0000 rev 00 class 06,00,00 hdr 80
    (II) PCI: 00:18:3: chip 1022,1103 card 0000,0000 rev 00 class 06,00,00 hdr 80
    (II) PCI: 01:07:0: chip 102b,051b card 102b,0100 rev 00 class 03,00,00 hdr 00
    (II) PCI: 01:0b:0: chip 104c,8023 card 1043,815b rev 00 class 0c,00,10 hdr 00
    (II) PCI: 02:00:0: chip 1095,3132 card 1043,819f rev 01 class 01,80,00 hdr 00
    (II) PCI: End of PCI scan
    (II) PCI-to-ISA bridge:
    (II) Bus -1: bridge is at (0:9:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set)
    (II) Subtractive PCI-to-PCI bridge:
    (II) Bus 1: bridge is at (0:14:0), (0,1,1), BCTRL: 0x0a0c (VGA_EN is set)
    (II) Bus 1 non-prefetchable memory range:
    [0] -1 0 0xfc800000 - 0xfd7fffff (0x1000000) MX[b]
    (II) Bus 1 prefetchable memory range:
    [0] -1 0 0xfb000000 - 0xfbffffff (0x1000000) MX[b]
    (II) PCI-to-PCI bridge:
    (II) Bus 2: bridge is at (0:22:0), (0,2,2), BCTRL: 0x0004 (VGA_EN is cleared)
    (II) Bus 2 I/O range:
    [0] -1 0 0x0000a000 - 0x0000a0ff (0x100) IX[b]
    [1] -1 0 0x0000a400 - 0x0000a4ff (0x100) IX[b]
    [2] -1 0 0x0000a800 - 0x0000a8ff (0x100) IX[b]
    [3] -1 0 0x0000ac00 - 0x0000acff (0x100) IX[b]
    (II) Bus 2 non-prefetchable memory range:
    [0] -1 0 0xfdf00000 - 0xfdffffff (0x100000) MX[b]
    (II) Host-to-PCI bridge:
    (II) Bus 0: bridge is at (0:24:0), (0,0,2), 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 (0x0) MX[b]
    (II) Bus 0 prefetchable memory range:
    [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[b]
    (--) PCI:*(1:7:0) Matrox Graphics, Inc. MGA 2164W [Millennium II] rev 0, Mem @ 0xfb000000/24, 0xfd7f8000/14, 0xfc800000/23, BIOS @ 0xfd7e0000/16
    (II) Addressable bus resource ranges are
    [0] -1 0 0x00000000 - 0xffffffff (0x0) 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 0xfdff8000 - 0xfdffbfff (0x4000) MX[b]
    [1] -1 0 0xfdfff000 - 0xfdfff07f (0x80) MX[b]
    [2] -1 0 0xfd7f4000 - 0xfd7f7fff (0x4000) MX[b]
    [3] -1 0 0xfd7ff000 - 0xfd7ff7ff (0x800) MX[b]
    [4] -1 0 0xfe025000 - 0xfe02500f (0x10) MX[b]
    [5] -1 0 0xfe026000 - 0xfe0260ff (0x100) MX[b]
    [6] -1 0 0xfe027000 - 0xfe027fff (0x1000) MX[b]
    [7] -1 0 0xfe028000 - 0xfe02800f (0x10) MX[b]
    [8] -1 0 0xfe029000 - 0xfe0290ff (0x100) MX[b]
    [9] -1 0 0xfe02a000 - 0xfe02afff (0x1000) MX[b]
    [10] -1 0 0xfe020000 - 0xfe023fff (0x4000) MX[b]
    [11] -1 0 0xfe02b000 - 0xfe02bfff (0x1000) MX[b]
    [12] -1 0 0xfe02c000 - 0xfe02cfff (0x1000) MX[b]
    [13] -1 0 0xfe02d000 - 0xfe02dfff (0x1000) MX[b]
    [14] -1 0 0xfe02e000 - 0xfe02e0ff (0x100) MX[b]
    [15] -1 0 0xfe02f000 - 0xfe02ffff (0x1000) MX[b]
    [16] -1 0 0xfd000000 - 0xfd00ffff (0x10000) MX[b](B)
    [17] -1 0 0xfc800000 - 0xfcffffff (0x800000) MX[b](B)
    [18] -1 0 0xfd7f8000 - 0xfd7fbfff (0x4000) MX[b](B)
    [19] -1 0 0xfb000000 - 0xfbffffff (0x1000000) MX[b](B)
    [20] -1 0 0x0000ac00 - 0x0000ac7f (0x80) IX[b]
    [21] -1 0 0x0000b000 - 0x0000b007 (0x8) IX[b]
    [22] -1 0 0x0000b400 - 0x0000b407 (0x8) IX[b]
    [23] -1 0 0x0000b800 - 0x0000b80f (0x10) IX[b]
    [24] -1 0 0x0000bc00 - 0x0000bc03 (0x4) IX[b]
    [25] -1 0 0x0000c000 - 0x0000c007 (0x8) IX[b]
    [26] -1 0 0x0000c400 - 0x0000c403 (0x4) IX[b]
    [27] -1 0 0x0000c800 - 0x0000c807 (0x8) IX[b]
    [28] -1 0 0x0000cc00 - 0x0000cc0f (0x10) IX[b]
    [29] -1 0 0x00000b60 - 0x00000b63 (0x4) IX[b]
    [30] -1 0 0x00000960 - 0x00000967 (0x8) IX[b]
    [31] -1 0 0x00000be0 - 0x00000be3 (0x4) IX[b]
    [32] -1 0 0x000009e0 - 0x000009e7 (0x8) IX[b]
    [33] -1 0 0x0000e000 - 0x0000e00f (0x10) IX[b]
    [34] -1 0 0x00000b70 - 0x00000b73 (0x4) IX[b]
    [35] -1 0 0x00000970 - 0x00000977 (0x8) IX[b]
    [36] -1 0 0x00000bf0 - 0x00000bf3 (0x4) IX[b]
    [37] -1 0 0x000009f0 - 0x000009f7 (0x8) IX[b]
    [38] -1 0 0x0000f400 - 0x0000f40f (0x10) IX[b]
    [39] -1 0 0x00001c40 - 0x00001c7f (0x40) IX[b]
    [40] -1 0 0x00001c00 - 0x00001c3f (0x40) IX[b]
    (II) Active PCI resource ranges after removing overlaps:
    [0] -1 0 0xfdff8000 - 0xfdffbfff (0x4000) MX[b]
    [1] -1 0 0xfdfff000 - 0xfdfff07f (0x80) MX[b]
    [2] -1 0 0xfd7f4000 - 0xfd7f7fff (0x4000) MX[b]
    [3] -1 0 0xfd7ff000 - 0xfd7ff7ff (0x800) MX[b]
    [4] -1 0 0xfe025000 - 0xfe02500f (0x10) MX[b]
    [5] -1 0 0xfe026000 - 0xfe0260ff (0x100) MX[b]
    [6] -1 0 0xfe027000 - 0xfe027fff (0x1000) MX[b]
    [7] -1 0 0xfe028000 - 0xfe02800f (0x10) MX[b]
    [8] -1 0 0xfe029000 - 0xfe0290ff (0x100) MX[b]
    [9] -1 0 0xfe02a000 - 0xfe02afff (0x1000) MX[b]
    [10] -1 0 0xfe020000 - 0xfe023fff (0x4000) MX[b]
    [11] -1 0 0xfe02b000 - 0xfe02bfff (0x1000) MX[b]
    [12] -1 0 0xfe02c000 - 0xfe02cfff (0x1000) MX[b]
    [13] -1 0 0xfe02d000 - 0xfe02dfff (0x1000) MX[b]
    [14] -1 0 0xfe02e000 - 0xfe02e0ff (0x100) MX[b]
    [15] -1 0 0xfe02f000 - 0xfe02ffff (0x1000) MX[b]
    [16] -1 0 0xfd000000 - 0xfd00ffff (0x10000) MX[b](B)
    [17] -1 0 0xfc800000 - 0xfcffffff (0x800000) MX[b](B)
    [18] -1 0 0xfd7f8000 - 0xfd7fbfff (0x4000) MX[b](B)
    [19] -1 0 0xfb000000 - 0xfbffffff (0x1000000) MX[b](B)
    [20] -1 0 0x0000ac00 - 0x0000ac7f (0x80) IX[b]
    [21] -1 0 0x0000b000 - 0x0000b007 (0x8) IX[b]
    [22] -1 0 0x0000b400 - 0x0000b407 (0x8) IX[b]
    [23] -1 0 0x0000b800 - 0x0000b80f (0x10) IX[b]
    [24] -1 0 0x0000bc00 - 0x0000bc03 (0x4) IX[b]
    [25] -1 0 0x0000c000 - 0x0000c007 (0x8) IX[b]
    [26] -1 0 0x0000c400 - 0x0000c403 (0x4) IX[b]
    [27] -1 0 0x0000c800 - 0x0000c807 (0x8) IX[b]
    [28] -1 0 0x0000cc00 - 0x0000cc0f (0x10) IX[b]
    [29] -1 0 0x00000b60 - 0x00000b63 (0x4) IX[b]
    [30] -1 0 0x00000960 - 0x00000967 (0x8) IX[b]
    [31] -1 0 0x00000be0 - 0x00000be3 (0x4) IX[b]
    [32] -1 0 0x000009e0 - 0x000009e7 (0x8) IX[b]
    [33] -1 0 0x0000e000 - 0x0000e00f (0x10) IX[b]
    [34] -1 0 0x00000b70 - 0x00000b73 (0x4) IX[b]
    [35] -1 0 0x00000970 - 0x00000977 (0x8) IX[b]
    [36] -1 0 0x00000bf0 - 0x00000bf3 (0x4) IX[b]
    [37] -1 0 0x000009f0 - 0x000009f7 (0x8) IX[b]
    [38] -1 0 0x0000f400 - 0x0000f40f (0x10) IX[b]
    [39] -1 0 0x00001c40 - 0x00001c7f (0x40) IX[b]
    [40] -1 0 0x00001c00 - 0x00001c3f (0x40) IX[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 0xfdff8000 - 0xfdffbfff (0x4000) MX[b]
    [5] -1 0 0xfdfff000 - 0xfdfff07f (0x80) MX[b]
    [6] -1 0 0xfd7f4000 - 0xfd7f7fff (0x4000) MX[b]
    [7] -1 0 0xfd7ff000 - 0xfd7ff7ff (0x800) MX[b]
    [8] -1 0 0xfe025000 - 0xfe02500f (0x10) MX[b]
    [9] -1 0 0xfe026000 - 0xfe0260ff (0x100) MX[b]
    [10] -1 0 0xfe027000 - 0xfe027fff (0x1000) MX[b]
    [11] -1 0 0xfe028000 - 0xfe02800f (0x10) MX[b]
    [12] -1 0 0xfe029000 - 0xfe0290ff (0x100) MX[b]
    [13] -1 0 0xfe02a000 - 0xfe02afff (0x1000) MX[b]
    [14] -1 0 0xfe020000 - 0xfe023fff (0x4000) MX[b]
    [15] -1 0 0xfe02b000 - 0xfe02bfff (0x1000) MX[b]
    [16] -1 0 0xfe02c000 - 0xfe02cfff (0x1000) MX[b]
    [17] -1 0 0xfe02d000 - 0xfe02dfff (0x1000) MX[b]
    [18] -1 0 0xfe02e000 - 0xfe02e0ff (0x100) MX[b]
    [19] -1 0 0xfe02f000 - 0xfe02ffff (0x1000) MX[b]
    [20] -1 0 0xfd000000 - 0xfd00ffff (0x10000) MX[b](B)
    [21] -1 0 0xfc800000 - 0xfcffffff (0x800000) MX[b](B)
    [22] -1 0 0xfd7f8000 - 0xfd7fbfff (0x4000) MX[b](B)
    [23] -1 0 0xfb000000 - 0xfbffffff (0x1000000) MX[b](B)
    [24] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [25] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
    [26] -1 0 0x0000ac00 - 0x0000ac7f (0x80) IX[b]
    [27] -1 0 0x0000b000 - 0x0000b007 (0x8) IX[b]
    [28] -1 0 0x0000b400 - 0x0000b407 (0x8) IX[b]
    [29] -1 0 0x0000b800 - 0x0000b80f (0x10) IX[b]
    [30] -1 0 0x0000bc00 - 0x0000bc03 (0x4) IX[b]
    [31] -1 0 0x0000c000 - 0x0000c007 (0x8) IX[b]
    [32] -1 0 0x0000c400 - 0x0000c403 (0x4) IX[b]
    [33] -1 0 0x0000c800 - 0x0000c807 (0x8) IX[b]
    [34] -1 0 0x0000cc00 - 0x0000cc0f (0x10) IX[b]
    [35] -1 0 0x00000b60 - 0x00000b63 (0x4) IX[b]
    [36] -1 0 0x00000960 - 0x00000967 (0x8) IX[b]
    [37] -1 0 0x00000be0 - 0x00000be3 (0x4) IX[b]
    [38] -1 0 0x000009e0 - 0x000009e7 (0x8) IX[b]
    [39] -1 0 0x0000e000 - 0x0000e00f (0x10) IX[b]
    [40] -1 0 0x00000b70 - 0x00000b73 (0x4) IX[b]
    [41] -1 0 0x00000970 - 0x00000977 (0x8) IX[b]
    [42] -1 0 0x00000bf0 - 0x00000bf3 (0x4) IX[b]
    [43] -1 0 0x000009f0 - 0x000009f7 (0x8) IX[b]
    [44] -1 0 0x0000f400 - 0x0000f40f (0x10) IX[b]
    [45] -1 0 0x00001c40 - 0x00001c7f (0x40) IX[b]
    [46] -1 0 0x00001c00 - 0x00001c3f (0x40) IX[b]
    (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: "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: "glx"
    (II) Loading /usr/lib/xorg/modules/extensions//libglx.so
    (II) Module glx: vendor="NVIDIA Corporation"
    compiled for 4.0.2, module version = 1.0.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 0.1
    (II) NVIDIA GLX Module 169.09 Fri Jan 11 15:31:25 PST 2008
    (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: "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: "mga"
    (II) Loading /usr/lib/xorg/modules/drivers//mga_drv.so
    (II) Module mga: vendor="X.Org Foundation"
    compiled for 1.4.0.90, module version = 1.9.100
    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) MGA: driver for Matrox chipsets: mga2064w, mga1064sg, mga2164w,
    mga2164w AGP, mgag100, mgag100 PCI, mgag200, mgag200 PCI,
    mgag200 SE A PCI, mgag200 SE B PCI, mgag400, mgag550
    (II) Primary Device is: PCI 01:07:0
    (--) Chipset mga2164w 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 0xfdff8000 - 0xfdffbfff (0x4000) MX[b]
    [5] -1 0 0xfdfff000 - 0xfdfff07f (0x80) MX[b]
    [6] -1 0 0xfd7f4000 - 0xfd7f7fff (0x4000) MX[b]
    [7] -1 0 0xfd7ff000 - 0xfd7ff7ff (0x800) MX[b]
    [8] -1 0 0xfe025000 - 0xfe02500f (0x10) MX[b]
    [9] -1 0 0xfe026000 - 0xfe0260ff (0x100) MX[b]
    [10] -1 0 0xfe027000 - 0xfe027fff (0x1000) MX[b]
    [11] -1 0 0xfe028000 - 0xfe02800f (0x10) MX[b]
    [12] -1 0 0xfe029000 - 0xfe0290ff (0x100) MX[b]
    [13] -1 0 0xfe02a000 - 0xfe02afff (0x1000) MX[b]
    [14] -1 0 0xfe020000 - 0xfe023fff (0x4000) MX[b]
    [15] -1 0 0xfe02b000 - 0xfe02bfff (0x1000) MX[b]
    [16] -1 0 0xfe02c000 - 0xfe02cfff (0x1000) MX[b]
    [17] -1 0 0xfe02d000 - 0xfe02dfff (0x1000) MX[b]
    [18] -1 0 0xfe02e000 - 0xfe02e0ff (0x100) MX[b]
    [19] -1 0 0xfe02f000 - 0xfe02ffff (0x1000) MX[b]
    [20] -1 0 0xfd000000 - 0xfd00ffff (0x10000) MX[b](B)
    [21] -1 0 0xfc800000 - 0xfcffffff (0x800000) MX[b](B)
    [22] -1 0 0xfd7f8000 - 0xfd7fbfff (0x4000) MX[b](B)
    [23] -1 0 0xfb000000 - 0xfbffffff (0x1000000) MX[b](B)
    [24] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [25] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
    [26] -1 0 0x0000ac00 - 0x0000ac7f (0x80) IX[b]
    [27] -1 0 0x0000b000 - 0x0000b007 (0x8) IX[b]
    [28] -1 0 0x0000b400 - 0x0000b407 (0x8) IX[b]
    [29] -1 0 0x0000b800 - 0x0000b80f (0x10) IX[b]
    [30] -1 0 0x0000bc00 - 0x0000bc03 (0x4) IX[b]
    [31] -1 0 0x0000c000 - 0x0000c007 (0x8) IX[b]
    [32] -1 0 0x0000c400 - 0x0000c403 (0x4) IX[b]
    [33] -1 0 0x0000c800 - 0x0000c807 (0x8) IX[b]
    [34] -1 0 0x0000cc00 - 0x0000cc0f (0x10) IX[b]
    [35] -1 0 0x00000b60 - 0x00000b63 (0x4) IX[b]
    [36] -1 0 0x00000960 - 0x00000967 (0x8) IX[b]
    [37] -1 0 0x00000be0 - 0x00000be3 (0x4) IX[b]
    [38] -1 0 0x000009e0 - 0x000009e7 (0x8) IX[b]
    [39] -1 0 0x0000e000 - 0x0000e00f (0x10) IX[b]
    [40] -1 0 0x00000b70 - 0x00000b73 (0x4) IX[b]
    [41] -1 0 0x00000970 - 0x00000977 (0x8) IX[b]
    [42] -1 0 0x00000bf0 - 0x00000bf3 (0x4) IX[b]
    [43] -1 0 0x000009f0 - 0x000009f7 (0x8) IX[b]
    [44] -1 0 0x0000f400 - 0x0000f40f (0x10) IX[b]
    [45] -1 0 0x00001c40 - 0x00001c7f (0x40) IX[b]
    [46] -1 0 0x00001c00 - 0x00001c3f (0x40) IX[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 0xfdff8000 - 0xfdffbfff (0x4000) MX[b]
    [5] -1 0 0xfdfff000 - 0xfdfff07f (0x80) MX[b]
    [6] -1 0 0xfd7f4000 - 0xfd7f7fff (0x4000) MX[b]
    [7] -1 0 0xfd7ff000 - 0xfd7ff7ff (0x800) MX[b]
    [8] -1 0 0xfe025000 - 0xfe02500f (0x10) MX[b]
    [9] -1 0 0xfe026000 - 0xfe0260ff (0x100) MX[b]
    [10] -1 0 0xfe027000 - 0xfe027fff (0x1000) MX[b]
    [11] -1 0 0xfe028000 - 0xfe02800f (0x10) MX[b]
    [12] -1 0 0xfe029000 - 0xfe0290ff (0x100) MX[b]
    [13] -1 0 0xfe02a000 - 0xfe02afff (0x1000) MX[b]
    [14] -1 0 0xfe020000 - 0xfe023fff (0x4000) MX[b]
    [15] -1 0 0xfe02b000 - 0xfe02bfff (0x1000) MX[b]
    [16] -1 0 0xfe02c000 - 0xfe02cfff (0x1000) MX[b]
    [17] -1 0 0xfe02d000 - 0xfe02dfff (0x1000) MX[b]
    [18] -1 0 0xfe02e000 - 0xfe02e0ff (0x100) MX[b]
    [19] -1 0 0xfe02f000 - 0xfe02ffff (0x1000) MX[b]
    [20] -1 0 0xfd000000 - 0xfd00ffff (0x10000) MX[b](B)
    [21] -1 0 0xfc800000 - 0xfcffffff (0x800000) MX[b](B)
    [22] -1 0 0xfd7f8000 - 0xfd7fbfff (0x4000) MX[b](B)
    [23] -1 0 0xfb000000 - 0xfbffffff (0x1000000) MX[b](B)
    [24] 0 0 0x000a0000 - 0x000affff (0x10000) MS[b]
    [25] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[b]
    [26] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[b]
    [27] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [28] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
    [29] -1 0 0x0000ac00 - 0x0000ac7f (0x80) IX[b]
    [30] -1 0 0x0000b000 - 0x0000b007 (0x8) IX[b]
    [31] -1 0 0x0000b400 - 0x0000b407 (0x8) IX[b]
    [32] -1 0 0x0000b800 - 0x0000b80f (0x10) IX[b]
    [33] -1 0 0x0000bc00 - 0x0000bc03 (0x4) IX[b]
    [34] -1 0 0x0000c000 - 0x0000c007 (0x8) IX[b]
    [35] -1 0 0x0000c400 - 0x0000c403 (0x4) IX[b]
    [36] -1 0 0x0000c800 - 0x0000c807 (0x8) IX[b]
    [37] -1 0 0x0000cc00 - 0x0000cc0f (0x10) IX[b]
    [38] -1 0 0x00000b60 - 0x00000b63 (0x4) IX[b]
    [39] -1 0 0x00000960 - 0x00000967 (0x8) IX[b]
    [40] -1 0 0x00000be0 - 0x00000be3 (0x4) IX[b]
    [41] -1 0 0x000009e0 - 0x000009e7 (0x8) IX[b]
    [42] -1 0 0x0000e000 - 0x0000e00f (0x10) IX[b]
    [43] -1 0 0x00000b70 - 0x00000b73 (0x4) IX[b]
    [44] -1 0 0x00000970 - 0x00000977 (0x8) IX[b]
    [45] -1 0 0x00000bf0 - 0x00000bf3 (0x4) IX[b]
    [46] -1 0 0x000009f0 - 0x000009f7 (0x8) IX[b]
    [47] -1 0 0x0000f400 - 0x0000f40f (0x10) IX[b]
    [48] -1 0 0x00001c40 - 0x00001c7f (0x40) IX[b]
    [49] -1 0 0x00001c00 - 0x00001c3f (0x40) IX[b]
    [50] 0 0 0x000003b0 - 0x000003bb (0xc) IS[b]
    [51] 0 0 0x000003c0 - 0x000003df (0x20) IS[b]
    (II) Setting vga for screen 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
    (--) MGA(0): Chipset: "mga2164w"
    (**) MGA(0): Depth 24, (--) framebuffer bpp 32
    (==) MGA(0): RGB weight 888
    (**) MGA(0): Option "OldDmaInit" "True"
    (==) MGA(0): Using AGP 1x mode
    (==) MGA(0): Using XAA acceleration
    (--) MGA(0): Linear framebuffer at 0xFB000000
    (==) MGA(0): MMIO registers at 0xFD7F8000
    (--) MGA(0): Pseudo-DMA transfer window at 0xFC800000
    (--) MGA(0): BIOS at 0xFD7E0000
    (II) Attempted to read BIOS 128KB from /sys/bus/pci/devices/0000:01:07.0/rom: got 32KB
    (--) MGA(0): Video BIOS info block at offset 0x07DC0
    (WW) MGA(0): Unable to probe memory amount due to hardware bug. Assuming 4096 KB
    (--) MGA(0): VideoRAM: 4096 kByte
    (II) MGA(0): I2C bus "DDC" initialized.
    (II) MGA(0): Output VGA using monitor section Monitor Genérico
    (==) MGA(0): Write-combining range (0xfb000000,0x400000)
    (II) MGA(0): I2C device "DDC:ddc2" registered at address 0xA0.
    (II) MGA(0): EDID vendor "SAM", prod id 4183
    (II) MGA(0): Using EDID range info for horizontal sync
    (II) MGA(0): Using EDID range info for vertical refresh
    (II) MGA(0): Printing DDC gathered Modelines:
    (II) MGA(0): Modeline "800x600"x0.0 56.25 800 832 896 1048 600 601 604 631 +hsync +vsync (53.7 kHz)
    (II) MGA(0): Modeline "1024x768"x0.0 94.50 1024 1072 1168 1376 768 769 772 808 +hsync +vsync (68.7 kHz)
    (II) MGA(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
    (II) MGA(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz)
    (II) MGA(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz)
    (II) MGA(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 491 520 -hsync -vsync (37.9 kHz)
    (II) MGA(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz)
    (II) MGA(0): Modeline "640x480"x0.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
    (II) MGA(0): Modeline "720x400"x0.0 35.50 720 738 846 900 400 421 423 449 -hsync -vsync (39.4 kHz)
    (II) MGA(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz)
    (II) MGA(0): Modeline "1024x768"x0.0 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz)
    (II) MGA(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz)
    (II) MGA(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
    (II) MGA(0): Modeline "1024x768"x0.0 44.90 1024 1032 1208 1264 768 768 776 817 interlace +hsync +vsync (35.5 kHz)
    (II) MGA(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz)
    (II) MGA(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz)
    (II) MGA(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz)
    (II) MGA(0): Modeline "640x480"x84.6 35.00 640 664 728 816 480 483 487 507 -hsync +vsync (42.9 kHz)
    (II) MGA(0): Modeline "800x600"x84.9 56.75 800 848 928 1056 600 603 607 633 -hsync +vsync (53.7 kHz)
    (II) MGA(0): Modeline "1024x768"x84.9 94.50 1024 1096 1200 1376 768 771 775 809 -hsync +vsync (68.7 kHz)
    (II) MGA(0): Modeline "1280x1024"x59.9 109.00 1280 1368 1496 1712 1024 1027 1034 1063 -hsync +vsync (63.7 kHz)
    (II) MGA(0): EDID vendor "SAM", prod id 4183
    (II) MGA(0): Output VGA connected
    (II) MGA(0): Output VGA using initial mode 1024x768
    (==) MGA(0): Using gamma correction (1.0, 1.0, 1.0)
    (==) MGA(0): Min pixel clock is 17 MHz
    (--) MGA(0): Max pixel clock is 250 MHz
    (--) MGA(0): MCLK used is 50.0 MHz
    (--) MGA(0): Has SDRAM
    (--) MGA(0): Virtual size is 1280x1024 (pitch 0)
    (**) MGA(0): Driver mode "1024x768": 94.5 MHz (scaled from 0.0 MHz), 68.7 kHz, 85.0 Hz
    (II) MGA(0): Modeline "1024x768"x85.0 94.50 1024 1072 1168 1376 768 769 772 808 +hsync +vsync (68.7 kHz)
    (**) MGA(0): Driver mode "1024x768": 94.5 MHz (scaled from 0.0 MHz), 68.7 kHz, 84.9 Hz
    (II) MGA(0): Modeline "1024x768"x84.9 94.50 1024 1096 1200 1376 768 771 775 809 -hsync +vsync (68.7 kHz)
    (**) MGA(0): Driver mode "1024x768": 78.8 MHz (scaled from 0.0 MHz), 60.1 kHz, 75.1 Hz
    (II) MGA(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz)
    (**) MGA(0): Driver mode "1024x768": 75.0 MHz (scaled from 0.0 MHz), 56.5 kHz, 70.1 Hz
    (II) MGA(0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz)
    (**) MGA(0): Driver mode "1024x768": 65.0 MHz (scaled from 0.0 MHz), 48.4 kHz, 60.0 Hz
    (II) MGA(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
    (**) MGA(0): Driver mode "1024x768": 44.9 MHz (scaled from 0.0 MHz), 35.5 kHz, 87.0 Hz (I)
    (II) MGA(0): Modeline "1024x768"x87.0 44.90 1024 1032 1208 1264 768 768 776 817 interlace +hsync +vsync (35.5 kHz)
    (**) MGA(0): Driver mode "832x624": 57.3 MHz (scaled from 0.0 MHz), 49.7 kHz, 74.6 Hz
    (II) MGA(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz)
    (**) MGA(0): Driver mode "800x600": 56.8 MHz (scaled from 0.0 MHz), 53.7 kHz, 84.9 Hz
    (II) MGA(0): Modeline "800x600"x84.9 56.75 800 848 928 1056 600 603 607 633 -hsync +vsync (53.7 kHz)
    (**) MGA(0): Driver mode "800x600": 56.2 MHz (scaled from 0.0 MHz), 53.7 kHz, 85.1 Hz
    (II) MGA(0): Modeline "800x600"x85.1 56.25 800 832 896 1048 600 601 604 631 +hsync +vsync (53.7 kHz)
    (**) MGA(0): Driver mode "800x600": 50.0 MHz (scaled from 0.0 MHz), 48.1 kHz, 72.2 Hz
    (II) MGA(0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz)
    (**) MGA(0): Driver mode "800x600": 49.5 MHz (scaled from 0.0 MHz), 46.9 kHz, 75.0 Hz
    (II) MGA(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz)
    (**) MGA(0): Driver mode "800x600": 40.0 MHz (scaled from 0.0 MHz), 37.9 kHz, 60.3 Hz
    (II) MGA(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
    (**) MGA(0): Driver mode "800x600": 36.0 MHz (scaled from 0.0 MHz), 35.2 kHz, 56.2 Hz
    (II) MGA(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz)
    (**) MGA(0): Driver mode "640x480": 35.0 MHz (scaled from 0.0 MHz), 42.9 kHz, 84.6 Hz
    (II) MGA(0): Modeline "640x480"x84.6 35.00 640 664 728 816 480 483 487 507 -hsync +vsync (42.9 kHz)
    (**) MGA(0): Driver mode "640x480": 31.5 MHz (scaled from 0.0 MHz), 37.5 kHz, 75.0 Hz
    (II) MGA(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz)
    (**) MGA(0): Driver mode "640x480": 31.5 MHz (scaled from 0.0 MHz), 37.9 kHz, 72.8 Hz
    (II) MGA(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 491 520 -hsync -vsync (37.9 kHz)
    (**) MGA(0): Driver mode "640x480": 30.2 MHz (scaled from 0.0 MHz), 35.0 kHz, 66.7 Hz
    (II) MGA(0): Modeline "640x480"x66.7 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz)
    (**) MGA(0): Driver mode "640x480": 25.2 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
    (II) MGA(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
    (**) MGA(0): Driver mode "720x400": 35.5 MHz (scaled from 0.0 MHz), 39.4 kHz, 87.8 Hz
    (II) MGA(0): Modeline "720x400"x87.8 35.50 720 738 846 900 400 421 423 449 -hsync -vsync (39.4 kHz)
    (**) MGA(0): Driver mode "720x400": 28.3 MHz (scaled from 0.0 MHz), 31.5 kHz, 70.1 Hz
    (II) MGA(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz)
    (**) MGA(0): Driver mode "1280x1024": 109.0 MHz (scaled from 0.0 MHz), 63.7 kHz, 59.9 Hz
    (II) MGA(0): Modeline "1280x1024"x59.9 109.00 1280 1368 1496 1712 1024 1027 1034 1063 -hsync +vsync (63.7 kHz)
    (**) MGA(0): Display dimensions: (320, 240) mm
    (**) MGA(0): DPI set to (101, 108)
    Backtrace:
    0: /usr/bin/X(xf86SigHandler+0x7e) [0x80baf4e]
    1: [0xb7fc0420]
    2: /usr/bin/X(InitOutput+0xa10) [0x80a81a0]
    3: /usr/bin/X(main+0x296) [0x8073d46]
    4: /lib/libc.so.6(__libc_start_main+0xe0) [0xb7d8d390]
    5: /usr/bin/X(FontFileCompleteXLFD+0x209) [0x80732b1]
    Fatal server error:
    Caught signal 8. Server aborting
    The error that i get on the screen is:
    Backtrace:
    0: /usr/bin/X(xf86SigHandler+0x7e) [0x80baf4e]
    1: [0xb7fc0420]
    2: /usr/bin/X(InitOutput+0xa10) [0x80a81a0]
    3: /usr/bin/X(main+0x296) [0x8073d46]
    4: /lib/libc.so.6(__libc_start_main+0xe0) [0xb7d8d390]
    5: /usr/bin/X(FontFileCompleteXLFD+0x209) [0x80732b1]
    Fatal server error:
    Caught signal 8. Server aborting
    Please, can someone help me with this?
    I'm now using the vesa driver, but that's not a good solution...
    thanks in advance.
    Last edited by eldarion (2008-03-03 22:54:05)

    @eldarion,
    Have you had a look at the unofficial matrox drivers at:
    http://forum.tuxx-home.at/viewtopic.php?t=153 ?
    Don't know about your card, but this is the mga driver I am using with my Millennium G400 and G450 cards.
    Now, the .run installer might complain about "different X server versions ... because ABI incompatible", so add the following to the [X-:*-Core] section in /opt/kde/share/config/kdm/kdmrc :
    ServerArgsLocal=-ignoreABI
    Also, set in the xorg.conf Device section:
    Option "HWCursor" "false"
    (In fact, you can just copy the files mga_drv.so and mga_hal_drv.so to /usr/lib/xorg/modules/drivers/ if necessary.)
    glxinfo and glxgears should check out okay with this mga driver.

  • Hard Drive Crash-round 2

    Last night, I'm pretty sure my Macbook hard drive crashed. AGAIN. I first ordered it online on July 5th of 2007 brand new right from the Apple Store. On January 11th of 2008, my first hard drive crashed. System locked up, heard clicking under the keyboard, blinking folder with a question mark inside of it whenever it was powered on. I took it to the Apple store, the Genius Bar guy took the HD out and checked it-dead. It was replaced on the 17th-I kept the receipt just incase. Last night I was typing a paper up for my Child Psych class when iTunes stopped responding. When I tried to quit it (command+q), nothing happened. I clicked the Apple in the top left hand corner to force quit it, and the whole system locked up. I heard clicking under the keyboard again, so I manually shut it off. And now I have the same blinking folder with the question mark again, and this time it even makes a beeping sound for me sometimes.
    I called Apple this afternoon, and they keep wanting me to reset this, reset that, try this and try that. I've tried everything just as I did in January when this first happened, and no luck again. I was told to make an appointment at the nearest store (which is 65 miles away, 130 round trip) so they could tell me it was dead and give me a new one just to crash again in a few months and I lose everything all over again.
    Anyway, the whole point of this is to find out what could be causing me to lose HD after HD? I really know nothing about Macs as a whole except for hard drive crashing issue; I've only used the OS for a little over a year so I'm putting this out there to anyone who knows more about them than I do. The machine mainly stays on my computer desk, but sometimes it ventures over to my bed. I charge it as needed, it doesn't leave the house (been too scared to do a lot with it since the first crash) so isn't slammed around in a backpack or dropped. Could it be actual hardware inside that is causing the failures, and if so, is that something that Apple could potentially check out and diagnose?
    Thanks!

    Same for me, MacBook bought in December 2006 in Germany with 2 GHz Processor, 2 GB of RAM and 160 GB hard drive,
    first drive crashed in december 2007, second drive just crashed in november 2008,
    both drives were the Hitachi HTS541616J9SA00
    now the replaced drive is again a Hitachi HTS541616J9SA00
    I asked the Apple Service Center to put in a drive of another brand (I would pay the difference to the drive covered by the Apple Warranty Program) but Apple said they could only put in the HTS541616J9SA00 drive, otherwise I would need to pay the entire price of a different hard drive of my choice.
    After doing some research on the internet, the Hitachi HTS541616J9SA00 seems to be a good hard drive, no known issues of premature breakdowns.
    I have used many Apple and Windows notebooks since 1995 and never experienced a drive crashing after less than one year. Now I have repeated drive crashs in the same Apple notebook.
    Since the drive model seems to be OK, I really have a suspicion of a hardware bug in the MacBook.

Maybe you are looking for