blak24 Posted August 29, 2012 Author Share Posted August 29, 2012 you id is 01268086 575] Modelo de chipset: Intel HD Graphics 3000 575] Tipo: GPU 575] Bus: Integrado 575] VRAM (total): 64 MB de memoria de sistema compartida 575] Fabricante: Intel (0x8086) 575] ID del dispositivo: 0x0126 enable the HD 3000 graphics built into Intel processors no fire... my IDs are that I told you before... also windows shows these numbers... anyway, I will try to that guide... Link to comment Share on other sites More sharing options...
iFIRE Posted August 29, 2012 Share Posted August 29, 2012 YES!!!! V.S Link to comment Share on other sites More sharing options...
blak24 Posted August 29, 2012 Author Share Posted August 29, 2012 this is taken from my files? it's strange though... windows continues showing that IDs... I will let you know... EDIT: ok, I will try editing the two kexts using this IDs... thanks Link to comment Share on other sites More sharing options...
blak24 Posted August 29, 2012 Author Share Posted August 29, 2012 fire, I think it's 0x01128086, and not that one you told me... I just reinstalled the OS, with GraphicsEnabler=No in safe mode, without installed any kext, systeminfo (the program you told me in the 3rd or 4th page) shows as Device ID 0112 and not 0126... Link to comment Share on other sites More sharing options...
iFIRE Posted August 30, 2012 Share Posted August 30, 2012 systeminfo (the program you told me in the 3rd or 4th page) shows as Device ID 0112 and not 0126... / False/ its Display Controller 8086 0126 install this kext, repairPermissions/rebuilCaches/KextWiizard/Reboot/*Now/open and run in terminal app this comand for see all pci devices ids of the your hardware: lspci -nn lspcidrv.kext.zip Link to comment Share on other sites More sharing options...
blak24 Posted August 30, 2012 Author Share Posted August 30, 2012 systeminfo (the program you told me in the 3rd or 4th page) shows as Device ID 0112 and not 0126... / False/ its Display Controller 8086 0126 install this kext, repairPermissions/rebuilCaches/KextWiizard/Reboot/*Now/open and run in terminal app this comand for see all pci devices ids of the your hardware: lspci -nn lspcidrv.kext.zip terminal says command not found... I installed the kext, rebuilt cache/permissions and rebooted... Link to comment Share on other sites More sharing options...
blak24 Posted August 30, 2012 Author Share Posted August 30, 2012 try this: sudo kextload /System/Library/Extensions/lspcidrv.kext in terminal app ths is mine: bash-3.2# lspci -nn 00:00.0 Host bridge [0600]: Intel Corporation Clarksfield/Lynnfield DMI [8086:d131] (rev 11) 00:03.0 PCI bridge [0604]: Intel Corporation Clarksfield/Lynnfield PCI Express Root Port 1 [8086:d138] (rev 11) 00:08.0 System peripheral [0880]: Intel Corporation Clarksfield/Lynnfield System Management Registers [8086:d155] (rev 11) 00:08.1 System peripheral [0880]: Intel Corporation Clarksfield/Lynnfield Semaphore and Scratchpad Registers [8086:d156] (rev 11) 00:08.2 System peripheral [0880]: Intel Corporation Clarksfield/Lynnfield System Control and Status Registers [8086:d157] (rev 11) 00:08.3 System peripheral [0880]: Intel Corporation Clarksfield/Lynnfield Miscellaneous Registers [8086:d158] (rev 11) 00:10.0 System peripheral [0880]: Intel Corporation QPI Link [8086:d150] (rev 11) 00:10.1 System peripheral [0880]: Intel Corporation QPI Routing and Protocol Registers [8086:d151] (rev 11) 00:1a.0 USB Controller [0c03]: Intel Corporation Ibex Peak USB Universal Host Controller [8086:3b3b] (rev 05) 00:1a.1 USB Controller [0c03]: Intel Corporation Ibex Peak USB Universal Host Controller [8086:3b3e] (rev 05) 00:1a.2 USB Controller [0c03]: Intel Corporation Ibex Peak USB Universal Host Controller [8086:3b3f] (rev 05) 00:1a.7 USB Controller [0c03]: Intel Corporation Ibex Peak USB2 Enhanced Host Controller [8086:3b3c] (rev 05) 00:1b.0 Audio device [0403]: Intel Corporation Ibex Peak High Definition Audio [8086:3b56] (rev 05) 00:1c.0 PCI bridge [0604]: Intel Corporation Ibex Peak PCI Express Root Port 1 [8086:3b42] (rev 05) 00:1c.1 PCI bridge [0604]: Intel Corporation Ibex Peak PCI Express Root Port 2 [8086:3b44] (rev 05) 00:1c.2 PCI bridge [0604]: Intel Corporation Ibex Peak PCI Express Root Port 3 [8086:3b46] (rev 05) 00:1c.3 PCI bridge [0604]: Intel Corporation Ibex Peak PCI Express Root Port 4 [8086:3b48] (rev 05) 00:1c.6 PCI bridge [0604]: Intel Corporation Ibex Peak PCI Express Root Port 7 [8086:3b4e] (rev 05) 00:1d.0 USB Controller [0c03]: Intel Corporation Ibex Peak USB Universal Host Controller [8086:3b36] (rev 05) 00:1d.1 USB Controller [0c03]: Intel Corporation Ibex Peak USB Universal Host Controller [8086:3b37] (rev 05) 00:1d.2 USB Controller [0c03]: Intel Corporation Ibex Peak USB Universal Host Controller [8086:3b38] (rev 05) 00:1d.3 USB Controller [0c03]: Intel Corporation Ibex Peak USB Universal Host Controller [8086:3b39] (rev 05) 00:1d.7 USB Controller [0c03]: Intel Corporation Ibex Peak USB2 Enhanced Host Controller [8086:3b34] (rev 05) 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev a5) 00:1f.0 ISA bridge [0601]: Intel Corporation Ibex Peak LPC Interface Controller [8086:3b02] (rev 05) 00:1f.2 SATA controller [0106]: Intel Corporation Ibex Peak 6 port SATA AHCI Controller [8086:3b22] (rev 05) 00:1f.3 SMBus [0c05]: Intel Corporation Ibex Peak SMBus Controller [8086:3b30] (rev 05) 01:00.0 VGA compatible controller [0300]: nVidia Corporation G96 [GeForce 9500 GT] [10de:0640] (rev a1) 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 03) 03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 03) 04:00.0 IDE interface [0101]: JMicron Technology Corp. 20360/20363 Serial ATA Controller [197b:2363] (rev 02) 05:00.0 IDE interface [0101]: JMicron Technology Corp. 20360/20363 Serial ATA Controller [197b:2363] (rev 03) 06:00.0 IDE interface [0101]: JMicron Technology Corp. 20360/20363 Serial ATA Controller [197b:2363] (rev 03) 07:06.0 FireWire (IEEE 1394) [0c00]: Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link) [104c:8024] when I type the sudo command and try to load the kext, it says that at the current boot level it's impossible to load that kext (remember I am booting with -x) anyway the ID you gave me is present in both the AppleIntelHD3000 kext and the AppleSNB kext... so it would be okay.. I found this, maybe helpful, in another forum. it is related with Z77 BOARD (for Ivybridge) where a Sandy Bridge CPU is installed, and I have a Z68 for Sandybridge: The other "gotcha" involved in using a Sandy Bridge processor for this Ivy Bridge board is that while full graphics acceleration is possible some edits to the AppleIntelSNBGraphicsFB.kext are needed and also the AppleIntelFramebufferCapri.kext needs a small plist edit. Both these edits are needed (for Sandy Bridge processor ONLY) because of the MEI driver device ID of the board not being Sandy Bridge friendly. Basically the system will try to load the AppleIntelFramebufferCapri.kext and not the AppleIntelSNBGraphicsFB.kext so the MEI driver device ID from the Capri kext needs to be taken from that kext and put into the AppleIntelSNBGraphicsFB.kext and you need to then either delete the Capri kext completely or modify the device ID in it so it does not load. In the attached folder I have put some pre-edited kexts though to make that easier which just need to be loaded via Kext Wizard (Kext Beast or Kext Utility could alternatively be used) I know it is for another chipset, but I'm stuck at the same point during process boot... I see "DSMOS has arrived" and then nothing... could it be this problem? Link to comment Share on other sites More sharing options...
iFIRE Posted August 30, 2012 Share Posted August 30, 2012 "DSMOS has arrived" is graphics problems, try backup all ATI kexts from terminal with command and repair permissions /reboot only with -v copy paste in app terminal only the code and put your passw sudo -s mkdir /atibackup cp -R /System/Library/Extensions/ATI*.* /atibackup rm -R /System/Library/Extensions/ATI*.* sudo rm -rf /System/Library/Caches/* Link to comment Share on other sites More sharing options...
blak24 Posted August 30, 2012 Author Share Posted August 30, 2012 "DSMOS has arrived" is graphics problems, try backup all ATI kexts from terminal with command and repair permissions /reboot only with -v copy paste in app terminal only the code and put your passw sudo -s mkdir /atibackup cp -R /System/Library/Extensions/ATI*.* /atibackup rm -R /System/Library/Extensions/ATI*.* sudo rm -rf /System/Library/Caches/* from terminal taken from the mountain lion installed right? "DSMOS has arrived" means that there is a graphic problem? if everything worked correctly I would not have this message? Link to comment Share on other sites More sharing options...
blak24 Posted August 31, 2012 Author Share Posted August 31, 2012 ok, open this kext AppleIntelSNBGraphicsFB.kext and add this device id from capri.kext <string>0x010b8086</string>, now backup and delete AppleIntelFramebufferCapri.kext repairPermissions and reboot just adding the device ID you gave me at the end of the text in info.plist? Link to comment Share on other sites More sharing options...
blak24 Posted August 31, 2012 Author Share Posted August 31, 2012 ok, so I have to take my ID from the CAPRI.kext and then copy it to the SNBGraphics.kext? or just copy the ID you gave me? sorry for the questions, but I must be sure I'm not doing wrong thank you EDIT: got a problem. yesterday I changed SMBIOS to MacMini, but now it goes on KP.. any idea? I have NOT changed the ID because it gets KP now... Link to comment Share on other sites More sharing options...
iFIRE Posted August 31, 2012 Share Posted August 31, 2012 yes, the plist what I post, make the same in your plist and save changes, see my post 111 Link to comment Share on other sites More sharing options...
blak24 Posted August 31, 2012 Author Share Posted August 31, 2012 yes, the plist what I post, make the same in your plist and save changes, see my post 111 ok, thank you. the problem is that I got kernel panics and I can't change the .plist file. I just changed the SMBIOS to macmini and then KP... it says "machine check"... so I think it's related to the smbios... EDIT: could it be because I installed a new hard disk yersterday? maybe it can't recognized the hardware because there is something new... Link to comment Share on other sites More sharing options...
blak24 Posted August 31, 2012 Author Share Posted August 31, 2012 ok, I reinstalled the system, now no KP, tried to modify the kexts taking the ID wich for me was 0x1E3A8086 if I remember well... but still stuck... :S Link to comment Share on other sites More sharing options...
iFIRE Posted August 31, 2012 Share Posted August 31, 2012 this fix not work for you, post your DSDT.aml Link to comment Share on other sites More sharing options...
iFIRE Posted August 31, 2012 Share Posted August 31, 2012 hello Blak24, I modified your DSDT.aml an inject method "AAPL00,DualLink", for HD 3000 Change your for this DSDT.aml. Now this work. Also check that the info.plist of AppleIntelSNBGraphicsFB.kext has DeviceID "01268086" & not "0x01268086". Also check "Extensions" in system profiler if both AppleIntelHDGraphics.kext & AppleIntelSNBGraphicsFB.kext are getting loaded. Also use SMBIOS MacMini5,1 or MAcBookPro8,1 Also not boot with -x or this flag not load yours graphics kexts Good Luck!!!! dsdtBlak24.zip Link to comment Share on other sites More sharing options...
blak24 Posted August 31, 2012 Author Share Posted August 31, 2012 hello Blak24, I modified your DSDT.aml an inject method "AAPL00,DualLink", for HD 3000 Change your for this DSDT.aml. Now this work. Also check that the info.plist of AppleIntelSNBGraphicsFB.kext has DeviceID "01268086" & not "0x01268086". Also check "Extensions" in system profiler if both AppleIntelHDGraphics.kext & AppleIntelSNBGraphicsFB.kext are getting loaded. Also use SMBIOS MacMini5,1 or MAcBookPro8,1 Also not boot with -x or this flag not load yours graphics kexts Good Luck!!!! dsdtBlak24.zip HD3000.kext or HD.kext? I will let you know, thank you very much!! EDIT: I just injected the DSDT with chameleon wizard... well, it goes on kernel panic... the same KP of today, where I posted the two photos... KP machine check... from win 7 I deleted the DSDT and it booted with -x as usual... don't know why it goes on KP :S Link to comment Share on other sites More sharing options...
iFIRE Posted August 31, 2012 Share Posted August 31, 2012 man, why you use chameleon wizard????????? why??? download of the DSDT.aml from my post and copy by hand and put this in your Extra folder, "copy and paste"is very difficult this for you!!!!! Also check that the info.plist of AppleIntelSNBGraphicsFB.kext has DeviceID "01268086" & not "0x01268086". Also check "Extensions" in system profiler if both AppleIntelHDGraphics.kext & AppleIntelSNBGraphicsFB.kext are getting loaded. Also use SMBIOS MacMini5,1 or MAcBookPro8,1 Also not boot with -x or this flag not load yours graphics kexts I think that for you the beast option is Buy a iMAC !!!!!! Link to comment Share on other sites More sharing options...
blak24 Posted August 31, 2012 Author Share Posted August 31, 2012 man, why you use chameleon wizard????????? why??? download of the DSDT.aml from my post and copy by hand and put this in your Extra folder, "copy and paste"is very difficult this for you!!!!! Also check that the info.plist of AppleIntelSNBGraphicsFB.kext has DeviceID "01268086" & not "0x01268086". Also check "Extensions" in system profiler if both AppleIntelHDGraphics.kext & AppleIntelSNBGraphicsFB.kext are getting loaded. Also use SMBIOS MacMini5,1 or MAcBookPro8,1 Also not boot with -x or this flag not load yours graphics kexts I think that for you the beast option is Buy a iMAC !!!!!! for point 3 and 5 I can't, because if I boot with -x graphics kexts are not loaded, if I boot normally it is stuck so I can't check that graphics kexts are loaded... point 2 is ok, point 4 ok, macmini 5,1EDIT: two hours ago it booted with -x without DSDT, now it is stuck again during boot... my god... it's impossible... together with this I have this f***ing keyboard that is not recognized... I lost half an hour before it decided to work for just a try to boot... I'm going crazy... Link to comment Share on other sites More sharing options...
Recommended Posts