FYI: This device-properties EFI string is the same as applying patch to DSDT:
Code:
into method label _DSM parent_adr 0x00020000 remove_entry;
into device name_adr 0x00020000 insert
begin
Method (_DSM, 4, NotSerialized)\n
{\n
If (LEqual (Arg2, Zero)) { Return (Buffer() { 0x03 } ) }\n
Return (Package()\n
{\n
"hda-gfx",\n
Buffer (0x0A) { "onboard-1" },\n
"AAPL,ig-platform-id",\n
Buffer (0x04) { 0x03, 0x00, 0x66, 0x01 },\n
})\n
}\n
end;
I prefer the DSDT patch because you can tell what it does by looking at it, and sometimes you need to make changes/additions to the _DSM for injecting other properties (common one in this case is if you have HD4000 w/ high-res display, and therefore need AAPL00,DualLink inject.
Hi Ikkoko, RehabMan.
Thank you very much for your responses.
I did not have a DSDT to start with and used the multibeast method "User DSDT or DSDT free"
How do I patch DSDT if I never had one, or is it created when I install Multibeast?
The system install perfectly, except LAN and wireless. USB works, webcam, sound works OTB.
Graphics also but only through the HDMI port.
I tried to extract with 2 different DSDT editors but with both of them it picked up errors when compiling and then after reboot the intrnal still did't work and the image on the HDMI monitor turned to garbage.
I have tried 6 times now, so obviously I am doing it wrong.
Starting over now.
I have dual boot with Windows 8 and no problems there.
I have built about 10 Hackintoshes over the last couple of years, but always managed with the hardware.
Problem is now I can't change the hardware.
Regards.