View Single Post
 
Old 06-30-2009, 02:58 PM
uman uman is offline
Panther
 
Join Date: May 2009
Location: USA
Posts: 103
Quote:
Originally Posted by martin255 View Post
uman, as far as I know the X4500 architecture is really different of the X3100 (according to Intel marketing, anyway). It's not like with the X3500, which was just a variation. But maybe you can join forces with this happy person: http://www.insanelymac.com/forum/ind...post&p=1184892
Martin, and *anyone* who has a 4500:

I've looked over Intel's docs on the 4500, and I find broad compatibility in the architectures. Intel has moved more features into the chipset (versus relying on the CPU) in the evolution from the GMA900 to the GMA4500, and they've added support for different display connections like LDVS.

I think it's worth trying to see if the GMAX3100 kexts in Leopard can drive the 4500 series. So could someone try the following experiment and report back?

1. Verify that your AppleIntelGMAX3100.kext/Contents/Info.plist has:

Code:
<key>IOPCIClassMatch</key>
<string>0x03000000&amp;0xff000000</string>
<key>IOPCIMatch</key>
<string>0x00008086&amp;0x0000ffff</string>
The translation is that this matches any PCI device of class code 0x03 (which I presume is graphics, as 0x02 is network) and vendor 8086 (Intel). It doesn't check device or subsystem ids.

2. Verify that AppleIntelGMAX3100FB.kext/Info.plist has:

Code:
<key>IOPCIClassMatch</key>
<string>0x03000000&amp;0xff000000</string>
<key>IOPCIPrimaryMatch</key>
<string>0x2A028086</string>
The translation is that this matches any PCI device of class code 0x03 and vendor 8086 (Intel) AND vendor Intel (8086) and device id: 0x2A02.

3. Edit AppleIntelGMAX3100FB.kext/Info.plist to be:

Code:
<key>IOPCIClassMatch</key>
<string>0x03000000&amp;0xff000000</string>
<key>IOPCIPrimaryMatch</key>
<string>0x2A42 0x2A43 0x2E12 0x2E13 0x2E02 0x2E03 0x2E22 0x2E23 0x2E32 0x2E33</string>
These are the device IDs for the 4500MHD (2A42 2A43), 4500 (2E12 2E13), X4500 and X4500HD (2E02 2E03 2E22 2E23 2E32 2E33).

4. Reboot with -v. Check Utilities/Console and look for any text related to the GMA kexts. Also open a terminal window and do:
Code:
$> kextstat | grep AppleIntelGMAX3100
If it's not running, there will be no output.

It's quite possible that this won't work at all, since the kext will be doing probing for properties that are not exposed via the Info.plist. But it's worth a try.

Thanks!
-u

--
MacBook Pro - have allergy to nickel in the aluminum casing. So my kid gets an expensive toy!

Gateway MX 8738 - Retail, vanilla Snow Leopard 10.6.2 (thanks kizwan!) with Chameleon RC4, modified DSDT. Upgraded to Core 2 CPU (easy to do). Upgraded to 640GB drive. Everything but SD card working. Minor niggles. GMA950 with QE/CI and *no* artifacts.

iMac (luxo/lamp) G4 with Tiger.
Reply With Quote