An iDiot's Guide To Lilu and its Plug-ins

[jaymonkey]

Removed my HDAS to HDEF as its already listed But with it and my IGPU disabled I have full audio. Followed the rest of the guide and it looks like an issue with HPET. Cant find any settings in my bios and even after patching my DSDT, still no joy.

@djashjones,

ioreg shows that AppleALC is loading / initialising.

Are you sure that layout 7 is correct for your Codec ?
Try setting "layout" as Device Property using Method 2 in AppleALC section of the guide.

Cheers
Jay

 

[djashjones]

I tried all the layouts ages ago and 7 was the best. Also read elsewhere that 7 is for the S1220A codec.

Just restore a time machine back as I've lost audio even with my IGPU disabled now, so god knows what's going on?

So now, I've enabled my IGPU (I would like a headless config anyway). Even thou in IOReg I have a HDEF, "alc-layout-id" is not visible unless I add "HDAS to HDEF" in patches.

Using Method 2

Then

kextstat | grep 'Lilu\|AppleALC\|AppleHDA'

I get

17    3 0xffffff7f810ed000 0x22000    0x22000    as.vit9696.Lilu (1.3.1) 2BA44B2C-289E-39B7-A92B-C28291D5FC26 <8 6 5 3 2 1>
18    0 0xffffff7f8110f000 0xdf000    0xdf000    as.vit9696.AppleALC (1.3.3) B60FCBAF-6BC2-36EF-A1E6-D5BE2863C35B <17 13 8 6 5 3 2 1>

Patched my DSDT

17    3 0xffffff7f810ed000 0x22000    0x22000    as.vit9696.Lilu (1.3.1) 2BA44B2C-289E-39B7-A92B-C28291D5FC26 <8 6 5 3 2 1>
18    0 0xffffff7f8110f000 0xdf000    0xdf000    as.vit9696.AppleALC (1.3.3) B60FCBAF-6BC2-36EF-A1E6-D5BE2863C35B <17 13 8 6 5 3 2 1>
121    0 0xffffff7f831d2000 0x1d000    0x1d000    com.apple.driver.AppleHDAController (282.10) 70256EC9-AF38-31BD-A3C5-9C0E30B64AA3 <120 100 42 13 8 7 6 5 3 1>

Still no sound (apart from my monitor)

 

[djashjones]

As a last ditched attempt last night. I updated AppleALC and Lilu to the latest versions and Voila, it's all working now.

AppleALC V.1.3.4
Lilu V1.3.1

   17    3 0xffffff7f810ed000 0x22000    0x22000    as.vit9696.Lilu (1.3.1) 2BA44B2C-289E-39B7-A92B-C28291D5FC26 <8 6 5 3 2 1>
18    0 0xffffff7f8110f000 0xea000    0xea000    as.vit9696.AppleALC (1.3.4) 5A1678E9-EEB8-3646-9244-5B589288D960 <17 13 8 6 5 3 2 1>
121    1 0xffffff7f831dd000 0x1d000    0x1d000    com.apple.driver.AppleHDAController (282.10) 70256EC9-AF38-31BD-A3C5-9C0E30B64AA3 <120 89 86 13 8 7 6 5 3 1>
153    0 0xffffff7f85c3e000 0xb7000    0xb7000    com.apple.driver.AppleHDA (282.10) B2208DA8-8CD9-36D8-BD59-C6D9A5379585 <152 121 120 107 89 86 7 6 5 3 1>
155    0 0xffffff7f85cf5000 0x2000     0x2000     com.apple.driver.AppleHDAHardwareConfigDriver (282.10) C4F674A0-5828-3D97-82BF-A81C8B8BDDBA <5 3>

Thanks very much for your help. I can report this success on my build for others.

Although it seems that headless mode is working for me as I have hardware accerlation but in the frambuffer info its showing blank for the model(s) and imac 18.2 is the closest for my config. Does it matter that its blank?

 

[jaymonkey]

As a last ditched attempt last night. I updated AppleALC and Lilu to the latest versions and Voila, it's all working now.
y build for others.

Although it seems that headless mode is working for me as I have hardware accerlation but in the frambuffer info its showing blank for the model(s) and imac 18.2 is the closest for my config. Does it matter that its blank?

@djashjones,

Yes version 1.3.0 of Lilu had a few issues and I think its taken a while for the plug-in's to catch up with version 1.3.1

Happy to read that all is working now.

It's not a problem that FB-Patcher (soon to be called Hackintool) does not show a Model type for some PlatformID's .. if you take a look at post #2 of this thread and find the headless PlatformID your using it will most likely show the same as FB-Patcher uses the same database.

Cheers
Jay

 

[jaymonkey]

I have a HDEF, "alc-layout-id" is not visible unless I add "HDAS to HDEF" in patches.

As a last ditched attempt last night. I updated AppleALC and Lilu to the latest versions and Voila, it's all working now.

@djashjones,

Is it still necessary for you to use the "HDAS to HDEF" patch in Clover ?

Just curious ...

Cheers
Jay

 

[djashjones]

Yes although I had HDEF listed "alc-layout-id" was not present until I used "HDAS to HDEF"

 

[jaymonkey]

Yes although I had HDEF listed "alc-layout-id" was not present until I used "HDAS to HDEF"

@djashjones,

Thanks for confirming this .. i suspected that some systems may still need the Clover ACPI rename even though Lilu/AppleALC has the code to do it itself ... its probably related the HDMI audio on the IGPU.

I'll update the notes in the guide accordingly.

Cheers
Jay

 

[djashjones]

Funny as I tried to confirm this last might. I disabled the rename, cold reboot and the alc-layout-id was still here. I could of swore blind this was not the case. I wonder if its because Ive updated AppleALC & Lilu? I know i was using 1.3.3 for the appleALC and for lilu whatever version a week before christmas. I could try to roll back if you wish?

 

[luckyal]

This is what the Device Properties look like for the the above example in Clover Configurator :-



Note-1: When using Clover Configurator we define the PCI path of the IGPU in the left panel and the name and data value of each Device Property in the right panel.

Note-2: The value for AAPL, ig-platform-id is entered (and displayed) in Reverse Byte Order without the leading "0x" so for the above example of "0x59160000" the correct value is "00001659".

This is probably not a big deal, but in your screenshot under "Properties" should the device-id read 59160000 instead of 16590000 ?

Also, you state:

For most users injecting the correct PlatformID for "AAPL,ig-platform-id" (and device-id in some cases) should be all that is required

In what cases would adding device-id be appropriate?

 

[jaymonkey]

This is probably not a big deal, but in your screenshot under "Properties" should the device-id read 59160000 instead of 16590000 ?

@luckyal,

Quite form the guide :-

Examples Note-1: In some of these examples you will see the Device Property "device-id" which can be thought of as a IGPU generation identifier (it will always be the first two bytes of the PlatformID in reverse byte order followed by four zero's). The need to set/inject this property is in many cases not necessary, and some users have reported that it can cause problems which is why Hackingtool no longer automatically generates this value. However other users have reported that without this property their system does not work correctly so the need for it is on a by use basis. If you want Hackingtool to generate the patch code for the "device-id" Device Property you can do so by selecting the option in the Advanced sub-tab on the Patch page of Hackingtool.

In what cases would adding device-id be appropriate?

Its a fair question but one without a clear cut answer, l'll try and do a bit more digging into it, if i find a better explanation for when it's required i'll update the guide.

Cheers
Jay