Aaron Olive Posted April 28, 2010 Share Posted April 28, 2010 okay Update guys it seems that the device ids are not coded into the frame buffer well at least from what i can see so it's the frame buffer but its not the frame buffer, it's really fishy what Apple & Intel did with this. Link to comment Share on other sites More sharing options...
Juz Posted April 28, 2010 Share Posted April 28, 2010 okay Update guysit seems that the device ids are not coded into the frame buffer well at least from what i can see so it's the frame buffer but its not the frame buffer, it's really fishy what Apple & Intel did with this. hi ka, is it possible for u to write what did u load and edit to get to your current state so that others can help out too. More information will be good, thanks! Link to comment Share on other sites More sharing options...
Aaron Olive Posted April 28, 2010 Share Posted April 28, 2010 hi ka, is it possible for u to write what did u load and edit to get to your current state so that others can help out too. More information will be good, thanks! my current state is the same as everyone else i'm using the modified X3100 drivers on Snow Leopard, i have made no changes to code yet i'm only reviewing the two, and testing frame rates and possible outcomes for the kext files. Link to comment Share on other sites More sharing options...
bboyg Posted April 28, 2010 Share Posted April 28, 2010 KA, what modified kexts are you using? I`m with 10.6.3 and the edited X3100 kexta doesn`t work for me Link to comment Share on other sites More sharing options...
bboyg Posted April 28, 2010 Share Posted April 28, 2010 KA, I stuck on the blue screen right before the Desktop. Are you sure that your kexts works on 10.6.3? P.S. Why you remove your post? Link to comment Share on other sites More sharing options...
Aaron Olive Posted April 28, 2010 Share Posted April 28, 2010 yes it works fine for me unless you have a different revision etc.... Link to comment Share on other sites More sharing options...
bboyg Posted April 28, 2010 Share Posted April 28, 2010 GMA 4500M 2a40 2a42 2a43 yes it works fine for me unless you have a different revision etc.... Link to comment Share on other sites More sharing options...
Aaron Olive Posted April 28, 2010 Share Posted April 28, 2010 you can check the plist those ids are already in there Link to comment Share on other sites More sharing options...
bboyg Posted April 28, 2010 Share Posted April 28, 2010 you can check the plist those ids are already in there Yes there are exacly the same device ids. I made the 10.6.3 update for the 6.1 MBPs with Pacifist. Can that be the reason, because this update added new kexts and system files? Link to comment Share on other sites More sharing options...
bboyg Posted April 28, 2010 Share Posted April 28, 2010 Thanks, I`ll try them now Link to comment Share on other sites More sharing options...
Juz Posted April 28, 2010 Share Posted April 28, 2010 delete the entire gmax3100 set in in extensions and use this one Hi KA Your set work for me! i have Native resolution now and no mouse artifact on snow leo 10.6.3! by the way i need to edit your plist device id from 'A' to 'a' in order to work else it didnt load. Thanks a lot!! This kext still display as 3100 in my graphic profile with 144mb ram available! but no qe. Thanks again Link to comment Share on other sites More sharing options...
Ereke Posted April 28, 2010 Share Posted April 28, 2010 Hey guys, what's requirements for getting QE? KA, can you explain step by step Link to comment Share on other sites More sharing options...
bboyg Posted April 28, 2010 Share Posted April 28, 2010 Stuck at the blue screen again. Maybe my system is very broken after all this updates and etc... Link to comment Share on other sites More sharing options...
Juz Posted April 28, 2010 Share Posted April 28, 2010 preview & Grab works fine but no i have not made huge leaps in that area yet Preview App Grab App to get these to work you used this right Link as quote from rDrG' post correct if i m wrong? as for itune to have visualiser, its the qe that you got it to work on your hack right? Link to comment Share on other sites More sharing options...
Aaron Olive Posted April 28, 2010 Share Posted April 28, 2010 Hey guys,what's requirements for getting QE? KA, can you explain step by step Well we have powerful enough hardware for QE/CI it's just a problem of driver support and we need a legitimate coder, it's just like a crossword puzzle you just have to connect the right numbers to right locations for ids and since apple skipped a stepping of the Intel GMA Family we lucked out, but like it's been said before the GMA 5700 is the 4500 just with a slight speed increase and on the die of the i5 Core Processor now if you take a look at one of those screens you'll see that the coding is much more complex compared to the X3100 driver hence most likely why we are having so many damn problems and Apples so called GPU switching is proving to be a failure among customers they screwed up the coding and since all of the apps can run off of integrated they just had to stick a new NVDA GPU in just for bragging rights, well any who i'll see what i can do since quartz doesn't bother me that much since i only use my laptop as a music player and web browsing, but like everyone else it would be a luxury to have QE/CI. to get these to work you used this right Link as quote from rDrG' post correct if i m wrong? as for iTunes to have visualizer, its the qe that you got it to work on your hack right? yes you can use that too to get apps to work and as for iTunes it uses Q/GL-O/GL Link to comment Share on other sites More sharing options...
Juz Posted April 28, 2010 Share Posted April 28, 2010 yes you can use that too to get apps to work and as for iTunes it uses Q/GL-O/GL Hi KA, how do you get q/gl-o/gl to work? its the same link as above post? Thanks for you patient and time. (i m a bit slow/lack of knowledge on QE and Q/GL thingy). I really appreciate all the effort you took to explain everything to us. Thank you once again Link to comment Share on other sites More sharing options...
Balut Posted April 28, 2010 Share Posted April 28, 2010 Hey KA, this guy posted a modified kext for the 3100 and says he has fully working video (QE). Perhaps you can combine efforts to get the 4500 working: Post #4 Hi, i have my Intel 965 (X3100) working 100%... Use this kext: Kext for Intel 965 - x3100 (0x2a02) NOTE: remove all intel GMA(950 -x3100) kext and Natit.kext, then install these kext recently... Info in System Profile: Intel GMA X3100: Chipset Model: GMA X3100 Type: Screen Bus: Integrated VRAM (total): 144 MB Manufacturer: Intel (0x8086), Device ID: 0x2a02 Revision ID: 0x0003 Screens: Display: Resolution: 1280 x 800 @ 75 Hz Depth: 32-bit Color Core Image: Hardware Accelerated Main Display: Yes Mirror: Off Online: Yes Quartz Extreme: Compatible Integrated: Yes QuartzGL: Compatible Display Connector: Status: No display connected Link to comment Share on other sites More sharing options...
Aaron Olive Posted April 28, 2010 Share Posted April 28, 2010 Hey KA, this guy posted a modified kext for the 3100 and says he has fully working video (QE). Perhaps you can combine efforts to get the 4500 working: Post #4 Hi, i have my Intel 965 (X3100) working 100%... Use this kext: Kext for Intel 965 - x3100 (0x2a02) NOTE: remove all intel GMA(950 -x3100) kext and Natit.kext, then install these kext recently... Info in System Profile: Intel GMA X3100: Chipset Model: GMA X3100 Type: Screen Bus: Integrated VRAM (total): 144 MB Manufacturer: Intel (0x8086), Device ID: 0x2a02 Revision ID: 0x0003 Screens: Display: Resolution: 1280 x 800 @ 75 Hz Depth: 32-bit Color Core Image: Hardware Accelerated Main Display: Yes Mirror: Off Online: Yes Quartz Extreme: Compatible Integrated: Yes QuartzGL: Compatible Display Connector: Status: No display connected i'll take a look at them. Link to comment Share on other sites More sharing options...
bboyg Posted April 28, 2010 Share Posted April 28, 2010 I made a clean install of 10.6 and updated to 10.6.3, but stuck again to the blue screen. KA did you touch something in the AppleIntelIntegratedFramebuffer.kext or some other? Or using some patch? When I was on 10.6.2 I was using those kexts and there was not problem, but at 10.6.3 the FB kext failed to load. I`m using the 915resolution fix for now. Keep going with the good work KA Link to comment Share on other sites More sharing options...
deviato Posted April 28, 2010 Share Posted April 28, 2010 ..Some clarifications.. @Killa Aaron: I appreciate your hex-testing, remember that Intel uses little-endian byte order, so you should search for 0x8680422a instead of 0x2a428086, and so on.. P.S.: What decompiler do you use? And what's your notebook? Your X3100 kexts don't work on my Dell Inspiron 1545. However.. I've searched for all Core variants, and collected some information. Here's a scheme with all known graphics ids: | Clarkdale | Arrandale | 4500MHD | |-----------+-----------+-----------+ | 8086:0040 | 8086:0044 | 8086:2a40 | DRAM (Chipset Memory Controller) | 8086:0042 | 8086:0046 | 8086:2a42 | Graphics Controller | - | - | 8086:2a43 | Unknown video device In little endian, for hex editing: | Clarkdale | Arrandale | 4500MHD | |-----------+-----------+-----------+ | 86804000 | 86804400 | 8680402a | DRAM (Chipset Memory Controller) | 86804200 | 86804600 | 8680422a | Graphics Controller | - | - | 8680432a | Unknown video device I think it's pointless to use 2a43 id (but I could be wrong), cause even on linux 'lspci -knn' reports this is not used by any module, maybe it's the vga-out controller? As I said in my blog, I've tried to search for all those hex ids in all kexts mentioned in this thread, and the only ones that I found were on AppleIntelHDGraphics: 8 instances for 86804400 that I replaced with 8680402a, and 8 for 86804600, replaced with 8680422a. Of course you could experiment with other ids.. Maybe there's some 'half' id hardcoded, like 4400, but it's difficult to find, cause it could be simply an opcode or address.. I've also searched for de10290a (nvidia GT330) but nothing.. Another strange thing is that 0040 is completely absent from the original kexts. Good luck! Link to comment Share on other sites More sharing options...
bboyg Posted April 28, 2010 Share Posted April 28, 2010 You can see that KA is using "Hex Fiend" on his screenshots. Crystal clear and simple Link to comment Share on other sites More sharing options...
Aaron Olive Posted April 28, 2010 Share Posted April 28, 2010 I made a clean install of 10.6 and updated to 10.6.3, but stuck again to the blue screen. KA did you touch something in the AppleIntelIntegratedFramebuffer.kext or some other? Or using some patch? When I was on 10.6.2 I was using those kexts and there was not problem, but at 10.6.3 the FB kext failed to load. I`m using the 915resolution fix for now. Keep going with the good work KA when you update to 10.6.3 make sure you delete the gma3100 kext that is already installed all 5 of them and use the one's i provided well, theres is a little question from me. Peoples, what really should i hex edit? the whole kext or just executable found in it? Help me out please! I am total nub in this just the unix executable. ..Some clarifications.. @Killa Aaron: I appreciate your hex-testing, remember that Intel uses little-endian byte order, so you should search for 0x8680422a instead of 0x2a428086, and so on.. P.S.: What decompiler do you use? And what's your notebook? Your X3100 kexts don't work on my Dell Inspiron 1545. However.. I've searched for all Core variants, and collected some information. Here's a scheme with all known graphics ids: | Clarkdale | Arrandale | 4500MHD | |-----------+-----------+-----------+ | 8086:0040 | 8086:0044 | 8086:2a40 | DRAM (Chipset Memory Controller) | 8086:0042 | 8086:0046 | 8086:2a42 | Graphics Controller | - | - | 8086:2a43 | Unknown video device In little endian, for hex editing: | Clarkdale | Arrandale | 4500MHD | |-----------+-----------+-----------+ | 86804000 | 86804400 | 8680402a | DRAM (Chipset Memory Controller) | 86804200 | 86804600 | 8680422a | Graphics Controller | - | - | 8680432a | Unknown video device I think it's pointless to use 2a43 id (but I could be wrong), cause even on linux 'lspci -knn' reports this is not used by any module, maybe it's the vga-out controller? As I said in my blog, I've tried to search for all those hex ids in all kexts mentioned in this thread, and the only ones that I found were on AppleIntelHDGraphics: 8 instances for 86804400 that I replaced with 8680402a, and 8 for 86804600, replaced with 8680422a. Of course you could experiment with other ids.. Maybe there's some 'half' id hardcoded, like 4400, but it's difficult to find, cause it could be simply an opcode or address.. I've also searched for de10290a (nvidia GT330) but nothing.. Another strange thing is that 0040 is completely absent from the original kexts. Good luck! yeah i tried looking for the NVDA code too but it's not there, like i said Apple & Intel really did some fishy stuff in there, to decompile i used otool -vtV line from xCode in terminal it only let's you take a proper look at all the code, i'll do more testing later. Also, what HEX-editor do you recommend?And where can i find DRAM DevID for my GMA4500 (2e32) ? you can use hex fiend Link to comment Share on other sites More sharing options...
bboyg Posted April 29, 2010 Share Posted April 29, 2010 KA, the removing the retail X3100 kexts (even in the Extensions Backup directory) hepls. Now the kexts are loaded. No QE/CI of course, but at least, my System Profiler shows me that I have now some GPU, not only Built in GPU Keep the good job fellas Link to comment Share on other sites More sharing options...
bboyg Posted April 29, 2010 Share Posted April 29, 2010 Did you removed your old/retail X3100 kexts first? Link to comment Share on other sites More sharing options...
bboyg Posted April 29, 2010 Share Posted April 29, 2010 So, you probably copy the retail kexts outside of the S/L/E directory, then edit them. And then you need to remove the retail kexts you have been edited before installing the new. Also you need to check /Backup Extensions folder at the root of the HD where is your system installed, and remove all the X3100 kext that may be inside. Then restart and boot with -f to rebuild the kext cache Link to comment Share on other sites More sharing options...
Recommended Posts