InfiniteMac OSx86  


Reply
 
Thread tools Display modes
  #11  
Old 06-25-2009, 03:17 PM
martin255 martin255 is offline
Cheetah
 
Join Date: Jun 2009
Posts: 10
UndeadSurfer, that's because 1280x1024 is a supported VESA mode in the X4500 bios, whereas most widescreen resolutions aren't.

Desktop - Vanilla 10.6.2 using Chameleon v2 RC4
[email protected]
4Gb G.Skill DDR2 800MHz
GA-P35-DS3P Rev1.2
8800GT 512Mb
Raptor 74Gb
Onboard LAN & Audio
LG GGW-H20L

Laptop - Thinkpad X60s - Vanilla 10.6.2 using Chameleon v2 RC4
Reply With Quote
  #12  
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
  #13  
Old 06-30-2009, 03:55 PM
martin255 martin255 is offline
Cheetah
 
Join Date: Jun 2009
Posts: 10
uman, I will try it and report. In fact I already saw the X3100 kext loaded, but I think it was caused by injecting MacBookAir1,1 as model identifier (other kexts that did not match my hardware were loaded).

Desktop - Vanilla 10.6.2 using Chameleon v2 RC4
[email protected]
4Gb G.Skill DDR2 800MHz
GA-P35-DS3P Rev1.2
8800GT 512Mb
Raptor 74Gb
Onboard LAN & Audio
LG GGW-H20L

Laptop - Thinkpad X60s - Vanilla 10.6.2 using Chameleon v2 RC4
Reply With Quote
  #14  
Old 07-01-2009, 12:16 AM
BlackCH BlackCH is offline
Cheetah
 
Join Date: Nov 2008
Posts: 4
The target device IDs are hardcoded on the kexts; you need to edit them with a hex editor
Reply With Quote
  #15  
Old 07-01-2009, 12:43 PM
uman uman is offline
Panther
 
Join Date: May 2009
Location: USA
Posts: 103
Quote:
Originally Posted by BlackCH View Post
The target device IDs are hardcoded on the kexts; you need to edit them with a hex editor
Ughh. Thanks for responding here BlackCH. I just saw your post on insanelymac. I verified that the IDs are indeed in the kexts with hexedit.

Martin (or anyone else who's game to try):

1. Open up the Info.plist of the AppleIntelGMAX3100FB.kext and replace the 0x2A028086 in this string:

Code:
<key>IOPCIPrimaryMatch</key>
<string>0x2A028086</string>
with one of the following (depends on which 4500 you have):

4500MHD: 0x2A428086 or 0x2A438086
4500: 0x2E128086 or 0x2E138086
X4500 and X4500HD: 0x2E028086 or 0x2E038086 or 0x2E228086 or 0x2E238086 or 0x2E328086 or 0x2E338086

2. Then with an hex editor open the AppleIntelGMAX3100FB contained in the kext and do a Find and Replace...

Find: 86 80 02 2A
Replace: byte-reversed version of what you put in the plist. So 0x2A428086 becomes 86 80 42 2A (do not use the 0x)

do the same for AppleIntelGMAX3100 file of the other kext.

And please post back. Since I don't have a 4500, I can't try this. Thanks.
Oh, also BlackCH's caution on insanely is valid: the kexts all have to match (either all stock leopard 10.5.x, or all the combo graphics update).

-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
  #16  
Old 07-06-2009, 10:28 AM
evb60 evb60 is offline
Cheetah
 
Join Date: May 2008
Posts: 1
Quote:
Originally Posted by uman View Post
Their approach won't work. Apple doesn't release the source for the video drivers.
Well, we didn't write drivers, but we've got framebuffer working, and we believe we're close to QE/CI, only need a little push from other guys, preferably with more insight in injection strings..
Reply With Quote
  #17  
Old 07-14-2009, 08:06 PM
shanwookie shanwookie is offline
Cheetah
 
Join Date: Feb 2009
Posts: 2
Quote:
Originally Posted by Undead Surfer View Post
Strange. I have the 45 on my PC at work and I run it at 1280x1024 using the com.apple.Boot.plist method.

Dunno. Strange stuff.
Confirmed.I have an Intel DG45ID MOBO. I modified my resolution with OSXTools > Add EFI Strings/Boot Flag on 10.5.7

I have [email protected]
Reply With Quote
  #18  
Old 01-23-2010, 06:00 AM
localparty localparty is offline
Cheetah
 
Join Date: Jan 2010
Posts: 1
Modified kext plists and kext binaries won't be loaded

Quote:
Originally Posted by uman View Post
Ughh. Thanks for responding here BlackCH. I just saw your post on insanelymac. I verified that the IDs are indeed in the kexts with hexedit.

Martin (or anyone else who's game to try):

1. Open up the Info.plist of the AppleIntelGMAX3100FB.kext and replace the 0x2A028086 in this string:

Code:
<key>IOPCIPrimaryMatch</key>
<string>0x2A028086</string>
with one of the following (depends on which 4500 you have):

4500MHD: 0x2A428086 or 0x2A438086
4500: 0x2E128086 or 0x2E138086
X4500 and X4500HD: 0x2E028086 or 0x2E038086 or 0x2E228086 or 0x2E238086 or 0x2E328086 or 0x2E338086

2. Then with an hex editor open the AppleIntelGMAX3100FB contained in the kext and do a Find and Replace...

Find: 86 80 02 2A
Replace: byte-reversed version of what you put in the plist. So 0x2A428086 becomes 86 80 42 2A (do not use the 0x)

do the same for AppleIntelGMAX3100 file of the other kext.

And please post back. Since I don't have a 4500, I can't try this. Thanks.
Oh, also BlackCH's caution on insanely is valid: the kexts all have to match (either all stock leopard 10.5.x, or all the combo graphics update).

-u
uman,

Sadly, your solution is not working for my Snow Leopard 10.6.2/Latitude E6500
My Latitude has an Intel GMAX4500 MHD and System Profiler confirmed both, a Vendor "Intel 0x8086" and a Device ID "0x2a42". I did modify Info.plist of both AppleIntelGMAX3100.kext and AppleIntelGMAX3100FB.kext to have

Code:
<key>IOPCIPrimaryMatch</key>
<string>0x2A428086</string>
and also, in both binary resources AppleIntelGMAX3100 and AppleIntelGMAX3100FB --using Hex Fiend-- replaced all the the hex ocurrences of 86 80 02 2A with

Code:
86 80 42 2A
I can confirm that the system tries to load the modified kexts because during boot, the gray apple is shown for a short time and then the screen goes completely black. It seems that OS X loads but the driver is not able to show anything in the screen. When I use the unmodified kexts then the boot process is successful, with the crappy 1024x768 resolution.

I installed "SnowOSX Universal v3.6 (10.6.2) | 3.6 GB", from SnowOSX3.6-A.iso.

For the record, I did succeed in adding audio and a not-so-good resolution of 1600x1200, by using "Graphics Mode"="1920x1200x32" during boot; however my display is not 1600x1200 and I do need the full 1920x1200x32 =(

Also for the record, since you recommend "replace" without specifying if we are supposed to replace "all the occurrences", I also tried to work with kexts with only the first hex instance being replaced. I guess this is pretty obvious, but just wanted you all to know that I also tried this, with the same negative result: a black screen.

I hope you have any ideas on what else can we try here =) Please advise =)
Reply With Quote
  #19  
Old 02-04-2010, 08:48 PM
asert asert is offline
Cheetah
 
Join Date: Oct 2009
Posts: 3
I will pay $200.00 to a developer for a fix of QE/CI on the Intel 4500MHD on Snow Leopard 10.6.2. It must be compatible with future updates. I will pay in cash via paypal or money order once I have confirmation that the patch works. Please contact me via this thread. I will give you details of how to contact me if you sound convincing. The Kext will be used on a Dell 1545 with 4500MHD

Only serious proposals.

Thank You.

Last edited by asert; 02-04-2010 at 08:53 PM.
Reply With Quote
  #20  
Old 02-08-2010, 07:04 AM
sparksthesquid's Avatar
sparksthesquid sparksthesquid is offline
Cheetah
 
Join Date: Sep 2009
Posts: 11
Here is a solution to native resolution at least it is a modified version of Chameleon RC4 remove any 3100 kext and follow the README I found the boot file on Insanely mac and added it to Chameleon so I take no credit for this but it works great gives you more of a "true mac" look and proper resolution to boot screen and menu works with 10.5.x and 10.6.x



💡 Deploy cloud instances seamlessly on DigitalOcean. Free credits ($100) for InfMac readers.

Attached Files
File Type: zip CHMod.zip (940.9 KB, 1261 views)
Reply With Quote
Reply
Thread Tools
Display Modes