Trouble with HD4000

[khronnuz]

Hey guys,

I've installed Mountain Lion and Mavericks on a Dell 3421 laptop using Unibeast 3.0. It features a 3rd generation i5 processor and Intel HD 4000 GPU. It loads the system, but is not loading the Intel HD kexts, rather, it is only showing as '64MB of Shared System Memory'.

What I have tried so far:

- GraphicsEnabler=Yes/No, IGPEnabler=Yes
- IGPEnabler=Yes, IGPlatformID, all suggested IDs.
- adding GraphicsMode to org.chameleon.Boot.plist

Weird thing about Graphics Mode is that when booting in safe mode I get native resolution ( 1366 x 768) but I boot in normal mode, I am stuck at 1024x768. In both cases, I get 64MB thing.

That behaviour happens on both ML and Mavericks

Does anyone know what else I can try?

 

[RehabMan]

Hey guys,

I've installed Mountain Lion and Mavericks on a Dell 3421 laptop using Unibeast 3.0. It features a 3rd generation i5 processor and Intel HD 4000 GPU. It loads the system, but is not loading the Intel HD kexts, rather, it is only showing as '64MB of Shared System Memory'.

What I have tried so far:

- GraphicsEnabler=Yes/No, IGPEnabler=Yes
- IGPEnabler=Yes, IGPlatformID, all suggested IDs.
- adding GraphicsMode to org.chameleon.Boot.plist

Weird thing about Graphics Mode is that when booting in safe mode I get native resolution ( 1366 x 768) but I boot in normal mode, I am stuck at 1024x768. In both cases, I get 64MB thing.

That behaviour happens on both ML and Mavericks

Does anyone know what else I can try?

Try with "GraphicsEnabler=No IGPEnabler=Yes IGPlatformID=01660003 -f"

If it does not work, capture ioreg after using those flags: http://www.tonymacx86.com/audio/58368-guide-how-make-copy-ioreg.html

Eventually, you should just patch your DSDT so the flags/bootloader won't matter (plus there is other patches you'll want to implement).

 

[mslily]

Hey guys,

I've installed Mountain Lion and Mavericks on a Dell 3421 laptop using Unibeast 3.0. It features a 3rd generation i5 processor and Intel HD 4000 GPU. It loads the system, but is not loading the Intel HD kexts, rather, it is only showing as '64MB of Shared System Memory'.

What I have tried so far:

- GraphicsEnabler=Yes/No, IGPEnabler=Yes
- IGPEnabler=Yes, IGPlatformID, all suggested IDs.
- adding GraphicsMode to org.chameleon.Boot.plist

Weird thing about Graphics Mode is that when booting in safe mode I get native resolution ( 1366 x 768) but I boot in normal mode, I am stuck at 1024x768. In both cases, I get 64MB thing.

That behaviour happens on both ML and Mavericks

Does anyone know what else I can try?

It happened to me when I first tried to install ML on my laptop, you may try RahabMan's flag. If it doesn't work, you may try my method which worked for me:

GraphicsEnabler=Yes, IGPEnabler=No, dart=0
In this way I got native HD4000 support

Good Luck~

 

[khronnuz]

Hi RehabMan and mslily,

Thanks for your time.

RehabMan, unfortunately it didn't work with your flags. In fact, it won't even boot neither shows any error. Adding the -f makes it simply stop during load around the time the network/bluetooth adapters start to work. I waited about 10 minutes to see if it still start. Since it won't start with those flags, not sure if still worth sending ioreg. It boots with those flags if I add -x. Also interesting is the fact no matter what IGPlatformID I use, System Profiler->/ Graphics/Displays shows:

Display:
Type: GPU
Bus: Built-In
VRAM (Total): 64 MB of Shared System Memory
Vendor: Intel (0x8086)
Device ID: 0x0166
Revision ID: 0x0009
Kernel Extension Info: No Kext Loaded

EDIT: It stops at "[IOBluetoothHCIController::setConfigState] calling registerService", which seems to be common.

mslily, adding dart=0 does not seem to have any effect

 

[RehabMan]

Hi RehabMan and mslily,

Thanks for your time.

RehabMan, unfortunately it didn't work with your flags. In fact, it won't even boot neither shows any error. Adding the -f makes it simply stop during load around the time the network/bluetooth adapters start to work. I waited about 10 minutes to see if it still start. Since it won't start with those flags, not sure if still worth sending ioreg. It boots with those flags if I add -x. Also interesting is the fact no matter what IGPlatformID I use, System Profiler->/ Graphics/Displays shows:

Display:
Type: GPU
Bus: Built-In
VRAM (Total): 64 MB of Shared System Memory
Vendor: Intel (0x8086)
Device ID: 0x0166
Revision ID: 0x0009
Kernel Extension Info: No Kext Loaded

EDIT: It stops at "[IOBluetoothHCIController::setConfigState] calling registerService", which seems to be common.

mslily, adding dart=0 does not seem to have any effect

If it didn't boot, how did you get to System Profiler?

This is a graphics problem and requires DSDT patches. If you're able to get to the desktop, it is time to get the DSDT in order...

 

[mslily]

Hi RehabMan and mslily,

Thanks for your time.

RehabMan, unfortunately it didn't work with your flags. In fact, it won't even boot neither shows any error. Adding the -f makes it simply stop during load around the time the network/bluetooth adapters start to work. I waited about 10 minutes to see if it still start. Since it won't start with those flags, not sure if still worth sending ioreg. It boots with those flags if I add -x. Also interesting is the fact no matter what IGPlatformID I use, System Profiler->/ Graphics/Displays shows:

Display:
Type: GPU
Bus: Built-In
VRAM (Total): 64 MB of Shared System Memory
Vendor: Intel (0x8086)
Device ID: 0x0166
Revision ID: 0x0009
Kernel Extension Info: No Kext Loaded

EDIT: It stops at "[IOBluetoothHCIController::setConfigState] calling registerService", which seems to be common.

mslily, adding dart=0 does not seem to have any effect

Did you disable IGPEnabler by setting it to NO?

For me, I set IGPEnabler=No, and GraphicsEnabler=Yes, then I got native HD4000 support. Otherwise I got some like you: full resolution (FHD in my case) and video card recognized correctly only in safe mode (-x)

 

[khronnuz]

If it didn't boot, how did you get to System Profiler?

I meant that the only new flag was -f, adding it causes the system to hang. Without it, it boots 'normally'.

This is a graphics problem and requires DSDT patches. If you're able to get to the desktop, it is time to get the DSDT in order...

Hmm, sounds scary . I will give that a go then.

Did you disable IGPEnabler by setting it to NO?

Yes. Also, in safe mode the native resolution works, but the card is not recognized. e.g. I still get 'No kext loaded'.

 

[RehabMan]

I meant that the only new flag was -f, adding it causes the system to hang. Without it, it boots 'normally'.

That's a bit weird and points to a kernel cache problem (probably). You should run DPCIManager and rebuild cache. Check for errors from kextcache. Fix as necessary (or report them here).

Hmm, sounds scary . I will give that a go then.

DSDT is not scary... and pretty much necessary for all laptops. Since you can get to the desktop, download and run MaciASL. Then add my patch repo per instructions in the readme: https://github.com/RehabMan/Laptop-DSDT-Patch

MaciASL will load your system DSDT. Attempt to compile it. If you have errors, fix them, or ask for help here (post the DSDT).

After that click, Patch, then apply the following patches:
"HD4000 Low Resolution" or "HD4000 High Resolution" depending on your laptop screen resolution
"Brightness Fix"
optional: "Rename GFX0 to IGPU"

Choose Save As, /Extra/dsdt.aml, format: ACPI Machine Language Binary

Reboot and test. If there is an issue, use DSDT=Null (in addition to whatever other bootflags you require).

 

[cwk9852]

- GraphicsEnabler=Yes/No, IGPEnabler=Yes
- IGPEnabler=Yes, IGPlatformID, all suggested IDs.
- adding GraphicsMode to org.chameleon.Boot.plist

It sounds like you are using chameleon and not chimera

the boot flags

IGPEnabler=Yes IGPlatformID=01660003

is specific to the Chimera fork...

If you are using chameleon the correct boot flag would be

GraphicsEnabler=Yes IntelCapriFB=3

or

GraphicsEnabler=Yes InjectIntel-ig=03006601

I believe that DSDT edits will override these so try adding DSDT=null

 

[RehabMan]

..

I believe that DSDT edits will override these so try adding DSDT=null

Actually, boot flags (using EFI injection) will override DSDT edits...

Let's see how the DSDT patching goes...