victorgaley Posted April 18, 2010 Share Posted April 18, 2010 Post it.....i can try it.....thanxssss Link to comment Share on other sites More sharing options...
javasir Posted April 18, 2010 Share Posted April 18, 2010 oh!!how i wish my x4500 could work fully!!!waiting for great men! Link to comment Share on other sites More sharing options...
bboyg Posted April 18, 2010 Share Posted April 18, 2010 Here is the device id injection in DSDT under GFX0 device: Method (_DSM, 4, NotSerialized) { Store (Package (0×06) { “AAPL,HasPanel”, Buffer (0×04) {0×01, 0×00, 0×00, 0×00}, “model”, Buffer (0×07) {”GMA4500MHD”}, “device-id”, Buffer (0×04) {0×42, 0×2A, 0×00, 0×00} }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } In the {”GMA4500MHD”} section, u can type whatever u want. This will be shown in the System Profiler. Link to comment Share on other sites More sharing options...
shine-away Posted April 18, 2010 Share Posted April 18, 2010 Hmmm, using a hex editor, you need to find something like: 86 80 xx xx and then replace the xx's with 42 2a. I will try messing around with the kexts now. But I need to install snow leopard first, and that requires a GUID mapped drive EDIT: Added device id's to the FB kext. Do you think you could use that DSDT edit but change the device and ids to the 5700, it might load the kext then. Link to comment Share on other sites More sharing options...
bboyg Posted April 18, 2010 Share Posted April 18, 2010 The IntelHD kext requires 10.6.3 so it cant be instaled on previuos version. If u want, u can try hex editing and post results to test Link to comment Share on other sites More sharing options...
TH3L4UGH1NGM4N Posted April 18, 2010 Share Posted April 18, 2010 The IntelHD kext requires 10.6.3 so it cant be instaled on previuos version. If u want, u can try hex editing and post results to test editing good old systemversion.plist saves you the trouble of having to update by just manually changing your version from there and then installing it i haven't been keeping up with the x4500 thread but has anyone tested out pcefi 10.6 with their x4500 with dev 0x2a42 in 64 bit mode with SL? i have pc efi 10.6 on my desktop but i don't have the time to test the new 10.6 boot file to see if it gives native 64 bit x4500 support. On netkas's site it does say something about resolving this but just throwing this out there incase someone has already done this Link to comment Share on other sites More sharing options...
kaswistry Posted April 18, 2010 Share Posted April 18, 2010 According to Georgi from netkas, the following DSDT inject works: Method (_DSM, 4, NotSerialized) { Store (Package (0×06) { “AAPL,HasPanel”, Buffer (0×04) {0×01, 0×00, 0×00, 0×00}, “model”, Buffer (0×07) {”GMA4500MHD”}, “device-id”, Buffer (0×04) {0×42, 0×2A, 0×00, 0×00} }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } The above code allows the system to recognize 4500MHD as the Video Card. However, no kext is loaded. What can we do from this point? Link to comment Share on other sites More sharing options...
shine-away Posted April 18, 2010 Share Posted April 18, 2010 Theres 3 different id's in these kexts; 0042 0044 0046 I have hex edited AppleIntelHDGraphics.kext and AppleIntelHDGraphics.kext, so that the id's are: 2a42, 2a44, 2a46. Also I have added these id's into the plist files too. If anyone has time to try them, here you go: http://www.mediafire.com/?mnljukum4xh Theres like a 95% chance they won't work knowing me Link to comment Share on other sites More sharing options...
bboyg Posted April 18, 2010 Share Posted April 18, 2010 kaswistry, I`m Georgi from the netkas.org Georgi is my real name now let`s try the hexedited kexts Link to comment Share on other sites More sharing options...
litosudo Posted April 18, 2010 Share Posted April 18, 2010 0044 is DRAM controller, in GMA4500 I think it would be 2a40 (memory hub). 0046 is the graphics controller, 2a42 in GMA4500. And 0042 appears to be another graphics controller, maybe because of the differences between the i3, i5 and i7 processors (netkas says that one is for mobile and the other for desktop), or maybe the 2a43 in GMA4500, that is another graphics controller in the same device. Link to comment Share on other sites More sharing options...
l0l0b0nd Posted April 18, 2010 Share Posted April 18, 2010 Theres 3 different id's in these kexts; 0042 0044 0046 I have hex edited AppleIntelHDGraphics.kext and AppleIntelHDGraphics.kext, so that the id's are: 2a42, 2a44, 2a46. Also I have added these id's into the plist files too. If anyone has time to try them, here you go: http://www.mediafire.com/?mnljukum4xh Theres like a 95% chance they won't work knowing me Well I tried your edited kexts and my sony vaio fw250 w/ SL 10.6.3 gets stuck on the spinning wheel screen, so I went in to -s mode and delete AppleIntelHDGraphicsFB.kext and back to "normal". I assume that the problem is with AppleIntelHDGraphicsFB since it was the only one I deleted and SL was able to restart again. Link to comment Share on other sites More sharing options...
bboyg Posted April 18, 2010 Share Posted April 18, 2010 I`m stuck too at the moment before dekstop, even hear the Skype sound but, only the spinning wheel and...thats it. Deleting the AppleIntelHDGraphicsFB brings the things bak to normal. Link to comment Share on other sites More sharing options...
shine-away Posted April 18, 2010 Share Posted April 18, 2010 Rehexed the kexts using originals that were posted earlier on, with the ids that limonada posted; I have got AppleIntelHDGraphics.kext loading on startup using this kext. But it must unload itself due to the FB/FrameBuffer kext not loading. Download AppleIntelHDGraphics.kext here: http://www.mediafire.com/?q4zymntm3wm The other kext (FB one) must need different id's or perhaps hexing in a different way. I will give it a retry later. Link to comment Share on other sites More sharing options...
pkmvancouver Posted April 18, 2010 Share Posted April 18, 2010 Do you think Apple is doing magic in the FB.kext to handle the switching and detection of the nvidia chip. Maybe there is something trying to detect the nvidia chipset and causing it to not load? I think the switching code might cause an issue. The new macbook pros have a system setting that allows them to disable the IntelHD and run directly nvidia. just a thought... Link to comment Share on other sites More sharing options...
shine-away Posted April 18, 2010 Share Posted April 18, 2010 It might be handled in the FB or another kext. I don't think the framebuffer is working due to wrong id's. Link to comment Share on other sites More sharing options...
Rezildans Posted April 18, 2010 Share Posted April 18, 2010 This is called brainstorm. Link to comment Share on other sites More sharing options...
OCM770 Posted April 18, 2010 Share Posted April 18, 2010 Just making sure, There isnt a signature on the kext's to avoid editing right? Just a thought, Apple might have implemented something like this Link to comment Share on other sites More sharing options...
shine-away Posted April 18, 2010 Share Posted April 18, 2010 Method (_DSM, 4, NotSerialized) { Store (Package (0×06) { “AAPL,HasPanel”, Buffer (0×04) {0×01, 0×00, 0×00, 0×00}, “model”, Buffer (0×07) {”GMA5700HD”}, “device-id”, Buffer (0×04) {0×46, 0×00, 0×00, 0×00} }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } Would something like that work? I am going to look over the FB.kext again tomorrow and hex edit it again, also replacing 0x428086 with 0x438086. Link to comment Share on other sites More sharing options...
l0l0b0nd Posted April 19, 2010 Share Posted April 19, 2010 This is the information I get from LSPCI (OSx86Tools) of my Vaio fw250...hope it helps. 00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub [8086:2a40] (rev 07) 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) 00:02.1 Display controller [0380]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a43] (rev 07) Link to comment Share on other sites More sharing options...
charlesterror Posted April 19, 2010 Share Posted April 19, 2010 This is the information I get from LSPCI (OSx86Tools) of my Vaio fw250...hope it helps. 00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub [8086:2a40] (rev 07) 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) 00:02.1 Display controller [0380]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a43] (rev 07) It may be stupid, but that's the info I used to have "Mobile 4 Series Chipset.." in windows using the dxdiag tool Link to comment Share on other sites More sharing options...
Juz Posted April 19, 2010 Share Posted April 19, 2010 Theres 3 different id's in these kexts; 0042 0044 0046 I have hex edited AppleIntelHDGraphics.kext and AppleIntelHDGraphics.kext, so that the id's are: 2a42, 2a44, 2a46. Also I have added these id's into the plist files too. If anyone has time to try them, here you go: http://www.mediafire.com/?mnljukum4xh Theres like a 95% chance they won't work knowing me used kexthelper to install this kext but nothing happen. i didnt get it loaded and no panic... do i need to load another kext? By the way, i cant find the GFX0 in my dsdt.dsl file. which dsdt file should i be looking for? Link to comment Share on other sites More sharing options...
shine-away Posted April 19, 2010 Share Posted April 19, 2010 If we could get a lspci of a 5700 in the new macbooks, then we could match the id's up. Looking at the id's, it tried matching them up again using l0l0b0nd and netkas's info: [8086:0044] >> [8086:2a40] [8086:0046] >> [8086:2a42] [8086:0042] >> [8086:2a43] Link to comment Share on other sites More sharing options...
bboyg Posted April 19, 2010 Share Posted April 19, 2010 Yep, I think it has to be something like that too Link to comment Share on other sites More sharing options...
bboyg Posted April 19, 2010 Share Posted April 19, 2010 Maybe we need the new nvidia kext instaled too, to make those kexts work... Link to comment Share on other sites More sharing options...
Mynzhasar Posted April 19, 2010 Share Posted April 19, 2010 Maybe we need the new nvidia kext instaled too And nvidia graphic adapter installed too Link to comment Share on other sites More sharing options...
Recommended Posts