msi gt70 hd4000 acceleration

[DLPmt]

Hi!

Since I install OSX 10.9.1 and almost all devices are ok, i try to get that ...things -Intel HD4000- properly working. I updated to OSX 10.9.2 and it doesn't change anything, at least not worse..

I can't boot in normal mode with AppleIntelHD4000Graphics.kext in S/L/E, else the boot stops after DRMStatus line without showing any error.

After reading some threads, I tried lots of things but no success on that. I attach the dsdt I made after hours/days of googling. In the ioreg(see attach) I don't see what's wrong or what i miss...unless no intelaccelerator so no qe/ci

Thanks in advance for any helps !

 

[RehabMan]

Hi!

Since I install OSX 10.9.1 and almost all devices are ok, i try to get that ...things -Intel HD4000- properly working. I updated to OSX 10.9.2 and it doesn't change anything, at least not worse..

I can't boot in normal mode with AppleIntelHD4000Graphics.kext in S/L/E, else the boot stops after DRMStatus line without showing any error.

After reading some threads, I tried lots of things but no success on that. I attach the dsdt I made after hours/days of googling. In the ioreg(see attach) I don't see what's wrong or what i miss...unless no intelaccelerator so no qe/ci

Thanks in advance for any helps !

Please provide complete details in your profile.

System: manufacturer/model
CPU: detailed CPU model + motherboard chipset
Graphics: all graphics devices + laptop internal screen resolution

For example, typical Ivy laptop:
System: HP ProBook 4540s
CPU: i5-3320m/HM76
Graphics: HD4000, 1366x768

Use CPU-Z on Windows to find CPU (Core iX-xxx) and motherboard chipset (HMxx). For a laptop, these details are important and affect critical installation procedures.

 

[DLPmt]

I added few more détails in my profile, I don't know if it's enought ? I found this : http://img.gawkerassets.com/post/9/2012/05/gtspecs.jpg, specs match with GT70 0NC-008US

Thank you for your answer

 

[RehabMan]

Hi!

Since I install OSX 10.9.1 and almost all devices are ok, i try to get that ...things -Intel HD4000- properly working. I updated to OSX 10.9.2 and it doesn't change anything, at least not worse..

I can't boot in normal mode with AppleIntelHD4000Graphics.kext in S/L/E, else the boot stops after DRMStatus line without showing any error.

After reading some threads, I tried lots of things but no success on that. I attach the dsdt I made after hours/days of googling. In the ioreg(see attach) I don't see what's wrong or what i miss...unless no intelaccelerator so no qe/ci

Thanks in advance for any helps !

Since you have both HD4000 and nvidia, you will probably need to delete the nvidia kexts (NV*, Geforce*; rebuild cache after).

Your ioreg is corrupt. If you want me to look: http://www.tonymacx86.com/audio/58368-guide-how-make-copy-ioreg.html

Your dsdt sets ig-platform-id = 01660009. Some high res laptops need 01660004 instead.

 

[DLPmt]

Well...I tried as you said and it's not working, it doesn't change anything. Boot always stops after DRMStatus : iTunes/Apple Store... :/

About the ig-platform-id, I edited the Framebuffer binaries (I forget which guide I used but if someone is interested in, must be easy to find) with Hex Fiend app as follow :

"/System/Library/Extensions/AppleIntelFramebufferCapri.kext/Contents/MacOS/AppleIntelFramebufferCapri"
Original(ver:8.24.11) : - - - - Modified :
09 00 66 01 01 03 03 03 00 00 00 04 - - - - - - 09 00 66 01 01 03 03 03 00 00 00 04
00 00 00 01 00 00 00 40 10 07 00 00 - - - - - - 00 00 00 01 00 00 00 80 10 07 00 00
10 07 00 00 00 00 00 00 00 00 00 00 - - - - - - 10 07 00 00 00 00 00 00 00 00 00 00
00 00 00 00 60 46 05 00 00 00 00 00 - - - - - - 00 00 00 00 60 46 05 00 00 00 00 00
01 00 00 00 02 00 00 00 30 00 00 00 -LVDS - 05 03 00 00 02 00 00 00 30 02 00 00
02 05 00 00 00 04 00 00 07 01 00 00 -HDMI - 04 06 00 00 00 08 00 00 06 00 00 00
03 04 00 00 00 04 00 00 07 01 00 00 -VGA? - 00 00 00 00 00 00 00 00 00 00 00 00
After some trials, it makes LVDS+HDMI working. 80 value in orange, makes the IntelHD4000 appears with 2048 Mo instead of 1024 Mo, I don't know if it's really useful..In Windows7 Aida64 shows ~2gb usage sometimes.
I fill the last line with 00 because it seems impossible to get VGA working, at least for the values I tried. It results in Kernel Panic(unless with 00) when pushing the detect button in Monitor pref. But it's not a main issue for me.

The LVDS orange line is the same as the one with 01660004 related binaries. It's the only values which not gave black screen or weird other things...but always when trying in safe-mode, otherwise boot stop after the DRMStatus usual message :/ and whatever the ig-platform-id is. So, removing the AppleIntelHD4000Graphics.kext seems to be the only things to do

I attach new ioregs, saved with IORegistryExplorer from the link you give me (I was using ver3.0.2), I hope they are not corrupted. The first "1", is when ig-platform-id = 01660009, Nvidia related kext in /S/L/E in normal mode without Hd4000 kext. The second "2", is when ig-platform-id = 01660004, Nvidia related kext removed from /S/L/E in safe-mode with Hd400 kext. Thanks to have a look

 

[RehabMan]

I attach new ioregs, saved with IORegistryExplorer from the link you give me (I was using ver3.0.2), I hope they are not corrupted. The first "1", is when ig-platform-id = 01660009, Nvidia related kext in /S/L/E in normal mode without Hd4000 kext.

Not really a valid configuration for your laptop, but I looked at it anyway. FYI: Intel HD kexts are still present (Intel HD kexts are AppleIntelFrame*, AppleIntelHD*, AppleIntelSNB*).

The second "2", is when

ig-platform-id = 01660004, Nvidia related kext removed from /S/L/E in safe-mode with Hd400 kext. Thanks to have a look

Try booting normally (but verbose). Provide photo of where it stops.

Also:
- you might try Chameleon (trunk) instead of Enoch branch
- you should verify that Intel MEI device is present (use DPCIManager->PCI List). I do not see it in the ioreg, so that is a bad sign (no 8086:1e3a)

 

[DLPmt]

Not really a valid configuration for your laptop, but I looked at it anyway. FYI: Intel HD kexts are still present (Intel HD kexts are AppleIntelFrame*, AppleIntelHD*, AppleIntelSNB*).

I removed only AppleIntelHD4000Graphics.kext. Removing the others kexts seems to have no effect, and keeps boot stop.

Try booting normally (but verbose). Provide photo of where it stops.

Also:
- you might try Chameleon (trunk) instead of Enoch branch
- you should verify that Intel MEI device is present (use DPCIManager->PCI List). I do not see it in the ioreg, so that is a bad sign (no 8086:1e3a)

- Can't take photo until hours...I'll edit later. The line where it stops is exactly : "DRMStatus: iTunes/Apple Store Content Access Problem. Content playback may be disabled on this computer. You can continue to use the machine, but you should contact an Apple support representative. ErrorCode: 8877652". After it I can type everything I want without any effect.

- I tried Chimera, Chameleon, Clover and finally Enoch(that's why I keep it). Chimera shows (at boot with verbose) lots of errors related to failed dependencies...I forget exactly what it was about. I don't see any differences in kernel log using Chameleon, Clover or Enoch.
Now, I replaced Enoch with Chameleon r2377 using Chameleon Wizard.

-DPCIManager->PCI List (see picture), there is no Intel MEI device..? It's a really bad sign ? :s

 

[RehabMan]

I removed only AppleIntelHD4000Graphics.kext. Removing the others kexts seems to have no effect, and keeps boot stop.

AppleIntelHD4000 is the QE part of the drivers...

- Can't take photo until hours...I'll edit later. The line where it stops is exactly : "DRMStatus: iTunes/Apple Store Content Access Problem. Content playback may be disabled on this computer. You can continue to use the machine, but you should contact an Apple support representative. ErrorCode: 8877652". After it I can type everything I want without any effect.

The last line is generally not helpful or meaningful.

-DPCIManager->PCI List (see picture), there is no Intel MEI device..? It's a really bad sign ? :s

Definitely a bad sign. QE will not work without an MEI device. I don't know if there is a work around. We run into the same issue from time-to-time with the ProBook 4x40s. Some just don't have a working MEI device. Must be a hardware problem...

 

[DLPmt]

The last line is generally not helpful or meaningful.

In fact, you clearly identified the problem(no MEI device), so a photo is no more needed. There is no differences when booting normally with verbose, if the boot "succeed"(AppleIntelHD4000Graphics.kext removed) or not.

Definitely a bad sign. QE will not work without an MEI device. I don't know if there is a work around. We run into the same issue from time-to-time with the ProBook 4x40s. Some just don't have a working MEI device. Must be a hardware problem...

I tried a few things..but none works :

- Adding Device MEI and _DSM method with device-id, vendor-id to the dsdt makes the Intel MEI Controller recognized in DPCIManager->PCI List, but not working properly when have a look at ioreg.
- When entering bios settings, in a menu called System Information, I saw "ME FW: N/A". It's probably mean no Intel Management Engine firmware installed ? So the device can't work ?
- Then I flashed the bios with same version previously installed, nothing change, always "ME FW: N/A". So, the ME FW is something to install (if possible..) separately ?
- I found this : http://www.win-raid.com/t171f39-Intel-Management-Engine-Drivers-Firmware-and-Tools.html, it looks clear but I don't want to brick anything...so just reading. From others websites, some MSI GT60/70 where using ME FW Version : 8.0.0.1351 but I can't find it.
- Is it possible, OS X "erased" ME FW or break it ? Or it's my laptop no luck :/ ...I'm not even sur it's the solution

 

[RehabMan]

?
- I found this : http://www.win-raid.com/t171f39-Intel-Management-Engine-Drivers-Firmware-and-Tools.html, it looks clear but I don't want to brick anything...so just reading. From others websites, some MSI GT60/70 where using ME FW Version : 8.0.0.1351 but I can't find it.
- Is it possible, OS X "erased" ME FW or break it ? Or it's my laptop no luck :/ ...I'm not even sur it's the solution

MEI firmware is commonly updated when applying BIOS updates. I remember seeing this when I update my BIOS on my desktop, as Intel's tool tells you about the individual components of the firmware as it updates. Is there a BIOS update for your machine?