Lenovo T430 laptop osX 11.4 Opencore 0.6.3 - sound chip ALC3202 not working

aloysius

New member
Joined
Jul 18, 2021
Motherboard
Lenovo Thinkpad T430
CPU
I5-3320
Graphics
Intel HD Graphics 4000
OS X/macOS
11.0.x
Bootloader
  1. OpenCore
Mobile Phone
  1. Android
  2. iOS
I hope this is the good one :
I've used v2 like you told me.
sshot.png
 

Attachments

  • T430 MacBook Pro.ioreg.zip
    648.3 KB · Views: 7

EliteMacx86

Administrator
Staff member
Joined
Jul 22, 2018
Motherboard
Supermicro X11SPA-T
CPU
Intel Xeon W-3275 28 Core
Graphics
2xAMD RX 580 8GB
OS X/macOS
11.0.x
Bootloader
  1. OpenCore
Mac
  1. MacBook Pro
Mobile Phone
  1. Android
  2. iOS
I hope this is the good one :
I've used v2 like you told me.
View attachment 3600
MBP15,2 is a poor choice for your hardware. Use MBP9,2 instead. For Audio, use SSDT-HDEF and make sure to add the correct layout ID. The same layout ID must be used in your config.plist too. In Device Properties and in boot-args.
 

aloysius

New member
Joined
Jul 18, 2021
Motherboard
Lenovo Thinkpad T430
CPU
I5-3320
Graphics
Intel HD Graphics 4000
OS X/macOS
11.0.x
Bootloader
  1. OpenCore
Mobile Phone
  1. Android
  2. iOS
Thank you for this tip.
Unfortunately, I didn't manage to make sound work.
:/
First, using MBP9,2 leads to :
bad_OS.png

No booting process allowed anymore.
After some search, I had to add "-no_compat_check" in the "boot-args" section in order to allow the operating system to boot on a prohibited mac hardware.
Now, it's fine :)
ID.png

Yes, I'm kind of a newbie, that's why I need help and maybe detailed help.
I tried anything using SSDT-HDEF but I probably missed something important because it's impossible to see the sound device in macOS.
I can see it in ioreg though with ALC-layout-id 23 (0x17) :
01.png

This alc-layout-id is the same in config.plist :
in boot-args section :
03.png

and in device properties section :
04.png


Note that there is also a "layout-id" (value : 07) which is not "alc-layout-id" and is confusing...

Your SSDT-HDEF evocation leads to there :
Nothing in this website seems to be made for ALC3202 or ALC269 chips except these two SSDTs :

"ssdt_hdef-3-no_ioreg/hdef
Supports Realtek ALC/Audio ID; 3 - HD3000/HD4000 HDMI and motherboard audio
Injects Device (HDEF) and Audio ID: 3 (layout-id: 0x03, 0x00, 0x00, 0x00)

ssdt_hdef-3-with_ioreg/hdef
Supports Realtek ALC/Audio ID; 3 - HD3000/HD4000 HDMI and motherboard audio
Injects Audio ID: 3 (layout-id: 0x03, 0x00, 0x00, 0x00)"

One more time a "layout-id" appears here which is neither 0x17 nor 0X07 but 0x03 and is a bit more confusing... I imagine that this audio-ID refers to the type of SSDT-HDEF used (ssdt_hdef-3) but I'm not sure.

I tried those two : no success. Then I tried those two again but this time with a patched DSDT using RehabMan's [Audio layer 3] (like higher) patch. Again : does not work.

Every time, "Pin configurations" is empty in ioreg and it should not be empty, am I wrong ?
02.png

Could you please be more precise concerning the right way to activate audio ? It appears that doing random stuff without knowing exactly where it's leading and what every patch is doing is not really efficient :).
Of course, I've joined ioreg, and verbose log if it can help.
Thanks.
 

Attachments

  • PR.zip
    651.2 KB · Views: 4

EliteMacx86

Administrator
Staff member
Joined
Jul 22, 2018
Motherboard
Supermicro X11SPA-T
CPU
Intel Xeon W-3275 28 Core
Graphics
2xAMD RX 580 8GB
OS X/macOS
11.0.x
Bootloader
  1. OpenCore
Mac
  1. MacBook Pro
Mobile Phone
  1. Android
  2. iOS
Thank you for this tip.
Unfortunately, I didn't manage to make sound work.
:/
First, using MBP9,2 leads to :
View attachment 3606
No booting process allowed anymore.
After some search, I had to add "-no_compat_check" in the "boot-args" section in order to allow the operating system to boot on a prohibited mac hardware.
Now, it's fine :)
View attachment 3607
Yes, I'm kind of a newbie, that's why I need help and maybe detailed help.
I tried anything using SSDT-HDEF but I probably missed something important because it's impossible to see the sound device in macOS.
I can see it in ioreg though with ALC-layout-id 23 (0x17) :
View attachment 3609
This alc-layout-id is the same in config.plist :
in boot-args section :
View attachment 3610
and in device properties section :
View attachment 3611

Note that there is also a "layout-id" (value : 07) which is not "alc-layout-id" and is confusing...

Your SSDT-HDEF evocation leads to there :
Nothing in this website seems to be made for ALC3202 or ALC269 chips except these two SSDTs :

"ssdt_hdef-3-no_ioreg/hdef
Supports Realtek ALC/Audio ID; 3 - HD3000/HD4000 HDMI and motherboard audio
Injects Device (HDEF) and Audio ID: 3 (layout-id: 0x03, 0x00, 0x00, 0x00)

ssdt_hdef-3-with_ioreg/hdef
Supports Realtek ALC/Audio ID; 3 - HD3000/HD4000 HDMI and motherboard audio
Injects Audio ID: 3 (layout-id: 0x03, 0x00, 0x00, 0x00)"

One more time a "layout-id" appears here which is neither 0x17 nor 0X07 but 0x03 and is a bit more confusing... I imagine that this audio-ID refers to the type of SSDT-HDEF used (ssdt_hdef-3) but I'm not sure.

I tried those two : no success. Then I tried those two again but this time with a patched DSDT using RehabMan's [Audio layer 3] (like higher) patch. Again : does not work.

Every time, "Pin configurations" is empty in ioreg and it should not be empty, am I wrong ?
View attachment 3612
Could you please be more precise concerning the right way to activate audio ? It appears that doing random stuff without knowing exactly where it's leading and what every patch is doing is not really efficient :).
Of course, I've joined ioreg, and verbose log if it can help.
Thanks.
For Laptops, i recommend patching full set ACPI, Hotpatch can work but requires more advance knowledge.

Incomplete PR files attached. Although, i checked your config.plist. I don't understand, why are you injecting Layout ID=17 in Device Properties, Layout ID=23 in bootargs and as the complete PR files were not attached, i'm not sure what Layout ID you have injected in SSDT-HDEF. The recommended Layout ID for your Laptop Audio Codec is 28.
 

aloysius

New member
Joined
Jul 18, 2021
Motherboard
Lenovo Thinkpad T430
CPU
I5-3320
Graphics
Intel HD Graphics 4000
OS X/macOS
11.0.x
Bootloader
  1. OpenCore
Mobile Phone
  1. Android
  2. iOS
Fast answer, thank you :)
I'm sorry, I forgot to attach the content of ACPI folder. It's done now.

Layout ID=17 00 00 00 in Device Properties is hex value (0x17 = 23 decimal value) and alcid=23 in boot-args is directly decimal value. I thought that it was the right way to declare these values but if I'm wrong, what's the good way to declare these values ?
Declaring value "3" should have been simpler since 3 is decimal 3 and hex 0x3 :D

In SSDT-HDEF, layout-id seems to be 03 and Pinconfigurations is empty, should I change these parameters and recompile this SSDT ?
"
Return (Package (0x06)
{
"hda-gfx",
Buffer (0x0A)
{
"onboard-1"
},

"layout-id",
Buffer (0x04)
{
0x03, 0x00, 0x00, 0x00
},

"PinConfigurations",
Buffer (Zero){}
"
I can't find out what is a "full set ACPI" patch and google does not help, so what do you mean by "full set ACPI" ?

Should I put decimal 28 value in every place refering to a layout-id ?
Thanks again for your time ;)
 

Attachments

  • ACPI.zip
    43.3 KB · Views: 4

EliteMacx86

Administrator
Staff member
Joined
Jul 22, 2018
Motherboard
Supermicro X11SPA-T
CPU
Intel Xeon W-3275 28 Core
Graphics
2xAMD RX 580 8GB
OS X/macOS
11.0.x
Bootloader
  1. OpenCore
Mac
  1. MacBook Pro
Mobile Phone
  1. Android
  2. iOS
Layout ID=17 00 00 00 in Device Properties is hex value (0x17 = 23 decimal value) and alcid=23 in boot-args is directly decimal value. I thought that it was the right way to declare these values but if I'm wrong, what's the good way to declare these values ?
In ACPI, it's Decimal to Hexadecimal. For e.g., if you want to use Layout ID=13, the Hexadecimal value will be D. In ACPI, it will be changed to 0x0D. If you want to use Layout iD=28, the Hexadecimal value will be 1C. In ACPI, it will be changed to 0x1C.

For Device Properties, you can have two options, DATA method and NUMBER Method. I prefer to use Number Method for ease. Here, you can directly use the Layout ID. For the above example, you can use 13 or 28. If you want to use DATA method, you need to convert it.

For Boot args, which was introduced later on, you can use the Layout ID directly with the syntax "alcid=XX." It's all explained in the config.plist creation guide for OpenCore.

Should I put decimal 28 value in every place refering to a layout-id ?
For SSDT-HDEF, the layout ID will be 0x1C
For Device Properties, use the Number Method and the Layout ID will be 28
For boot arg, the layout ID will be 28.
 

aloysius

New member
Joined
Jul 18, 2021
Motherboard
Lenovo Thinkpad T430
CPU
I5-3320
Graphics
Intel HD Graphics 4000
OS X/macOS
11.0.x
Bootloader
  1. OpenCore
Mobile Phone
  1. Android
  2. iOS
Thank you EliteMacx86 for your explanation. I'll try this asap. See you soon.
 
Similar threads
Thread starter Title Forum Replies Date
P Intel Laptop display not working Big Sur 23

Similar threads

Forum statistics

Threads
516
Messages
4,882
Members
4,419
Latest member
renzolperez