No HDMI sound from iGPU

[agstrato]

Hello guys it seems now i can post anywhere so here's my thread. I have a Z390 Asus Maximus XI Extreme paired with a 9900KS and pretty much everything works fine after framebuffers patching. I am using the iGPU connected to another monitor for my hack, the problem i am having is that the sound slider is greyed out for the monitor sound. I can also see macOS thinks i have 2 monitors which is also incorrect and no it's not monitored or anything, i'm not sure why it detects 2 mons. I attach my EFI and a screenshot, do note that i kept adding and changing things to it, i just want to fix the hdmi sound and that's pretty much just it. In my mind i like to believe that the incorrect detection of the monitors is the problem. Do you guys have any suggestions?

Z390-Asus-M11Extreme.zip

Edited November 7, 2025 by agstrato

[deeveedee]

@agstrato You are overriding EDID for two connectors.  Why would you think that macOS doesn't think you have two monitors?  Also, overriding EDID can affect HDMI audio.

 

EDIT: If you comment-out your EDID overrides (put a # at the beginning of #AAPL00,override-no-connect and #AAPL01,override-no-connect), does macOS find a single monitor and does HDMI audio work?

 

Also, are you certain that you need the following DeviceProperties:

• enable-hdmi20 (WhateverGreen does not use this for macOS 11+)
• enable-lspcon-support, framebuffer-con3-has-lspcon, framebuffer-con3-preferred-lspcon-mode

 

I might have more feedback, but it would be easier for the reader if you break out your "all data" properties to be individual properties that are easily interpreted (e.g., framebuffer-con0-busid, frame buffer-con0-flags, etc.)

Edited November 7, 2025 by deeveedee

[agstrato]

Just now, deeveedee said:

@agstrato You are overriding EDID for two connectors.  Why would you think that macOS doesn't think you have two monitors?  Also, overriding EDID can affect HDMI audio.

Ok as i said i kept adding and modifying stuff, it works fine without those 2 lines anyway. I do have 2 monitors but the other one is connected to the RTX video card with DisplayPort and is disabled by boot-args -wegnoegpu. It's certainly not the same monitor as it shows in that screenshot. So bottom line, the Acer exists but the second Acer doesn't. I tried without the EDID lines a few days ago and still the same issue. Also if i choose Main Display all the windows i open are probably going to the "other inexistent" monitor because i can't see nothing on this one.

[deeveedee]

@agstrato When you are making graphics DeviceProperties changes, do not make any conclusions about changes until you reboot a few times.  If you change things too quickly, you will not know what property change produces which result.

 

EDIT: Also, try deleting /Library/Preferences/com.apple.windowserver.plist and reboot.  This will let macOS rebuild your Display preferences.  You may need to reconfigure Display preferences after doing this, but if you have two displays showing because preferences are borked, this might fix the problem.

Edited November 7, 2025 by deeveedee

[agstrato]

Sure i can do that here are the values you asked:

framebuffer-con0-busid        d    00000000
framebuffer-con0-enable      d    01000000
framebuffer-con0-flags         d    C7030000
framebuffer-con0-index        d    01000000
framebuffer-con0-pipe          d    09000000
framebuffer-con0-type          d    01000000
framebuffer-con1-busid         d    02000000
framebuffer-con1-enable       d    01000000
framebuffer-con1-flags          d    C7030000
framebuffer-con1-index         d    02000000
framebuffer-con1-pipe           d    0A000000
framebuffer-con1-type           d    00080000
framebuffer-con2-busid        d    00000000
framebuffer-con2-enable      d    01000000
framebuffer-con2-flags         d    C7030000
framebuffer-con2-index        d    03000000
framebuffer-con2-pipe          d    08000000
framebuffer-con2-type          d    01000000

[deeveedee]

@agstrato Ok - that's a good start.  Which of these are changes from the default values in your selected frame buffer?  My point was that your config.plist should not use the "all data" properties until you have a fully working configuration.  Modify your config.plist to use the individual properties and includes only the properties that change the default values.  That way, when you share your config.plist when asking for help, your reviewer won't have to waste time figuring everything out.

@agstrato I was editing my posts as you were reading.  I think there are things in my posts that you missed (my fault).  Please go back to each of my posts and re-read.

[agstrato]

Just now, deeveedee said:

@agstrato Ok - that's a good start.  Which of these are changes from the default values in your selected frame buffer?  My point was that your config.plist should not use the "all data" properties until you have a fully working configuration.  Modify your config.plist to use the individual properties and includes only the properties that change the default values.  That way, when you share your config.plist when asking for help, your reviewer won't have to waste time figuring everything out.

@agstrato I was editing my posts as you were reading.  I think there are things in my posts that you missed (my fault).  Please go back to each of my posts and re-read.

It's OK i did scroll up and see what you wrote about the removing of that file etc. After i removed the file the Acer monitor 1 moved to the left. I also modify the EFI in order for people to be able to work properly on it. BTW i will reinstall macOS after getting the hdmi sound. Also if you believe i could go Tahoe it's no problem for me i'm all in... but i think even the motherboard sound needs a patch there so this is why i tried Sequoia

Some things to note in this "original" EFI. As per information from hackintool i have changed device-id to 9B3E0000 instead of 983E0000 it's confusing but number 8 changes to letter b and i also added con3 which honestly i don't have a clue why it's there.

Some other relevant information i found around for my specific motherboard is:

Index 1, BusID 0x00, Type Dummy
Index 2, BusID 0x02, Type HDMI
Index 3, BusID 0x00, Type DUMMY

 

EFI-simple.zip

[deeveedee]

@agstrato Why are you overriding device-id? 0x3e98 (the id of your CPU) is natively supported.

 

I think you'll find that minimizing changes will make it easier if you're collaborating with others to fix the problem.

 

Don't try Tahoe until you get Sequoia working.

 

After you delete device-id (allowing default device-id) and test, please summarize the problems you're still having.

[agstrato]

Just now, deeveedee said:

@agstrato Why are you overriding device-id? 0x3e98 (the id of your CPU) is natively supported.

 

I think you'll find that minimizing changes will make it easier if you're collaborating with others to fix the problem.

 

Don't try Tahoe until you get Sequoia working.

 

After you delete device-id (allowing default device-id) and test, please summarize the problems you're still having.

I don't really know i thought i just try it. Just for confirming i should remove device-id and is 07009B3E OK for AAPL,ig-platform-id? It's exactly what i thought i won't go Tahoe until i get this one properly setup.

[agstrato]

Ok i deleted device-id, left AAPL,ig-platform-id with 07009B3E and same thing. I honestly think the problem is that it detects 2 monitors and i only have 1...

[deeveedee]

@agstrato Ok - I get it.  It is tempting to make arbitrary changes to see what happens.  It's a great way to learn.  But it's generally not a good way to problem solve.

 

This document is my primary reference for Intel HD framebuffer patching.

 

Your CPU has device-id 0x3E98.  As stated in the document, your CPU's device-id is natively supported.  There is no reason to change it, so delete device-id from your DeviceProperties.

 

Also, your list of DeviceProperties is complete, but it's overkill and doesn't help others who are reviewing.  Remove the DeviceProperties that do not change the default value.

 

As stated in the document linked above, your selected frame buffer is defined as

 

ID: 3E9B0007, STOLEN: 57 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x00801302
TOTAL STOLEN: 58 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 172 MB, MAX OVERALL: 173 MB (181940224 bytes)
Model name: Intel UHD Graphics 630
Camellia: CamelliaDisabled (0), Freq: 0 Hz, FreqMax: 0 Hz
Mobile: 0, PipeCount: 3, PortCount: 3, FBMemoryCount: 3
[1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x000003C7 - ConnectorDP
[2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x000003C7 - ConnectorDP
[3] busId: 0x06, pipe: 8, type: 0x00000400, flags: 0x000003C7 - ConnectorDP
01050900 00040000 C7030000
02040A00 00040000 C7030000
03060800 00040000 C7030000

You don't need to re-define the following in your config.plist and so these should be deleted (they don't hurt, but they certainly don't help).  You can include them later when the problem is solved, but while you're working with others, keep the DeviceProperties simple so others don't have to figure out what is changed and what is not changed.

• framebuffer-con0-flags
• framebuffer-con0-index
• framebuffer-con0-pipe
• framebuffer-con1-flags
• framebuffer-con1-index
• framebuffer-con1-pipe
• framebuffer-con2-flags
• framebuffer-con2-index
• framebuffer-con2-pipe

 

I made what I think are the simplifications in the attached config.plist.  Please check my work, test it and then post the problems that still need to be fixed.

 

Also, since your selected frame buffer has only 3 connectors, you don't need to define any properties for con3.  I've seen others do this, but it's not necessary.

config.plist.zip

[agstrato]

The EFI you posted works just fine, I think I'm going to reinstall this Sequoia OS after so many tests who knows if there's something wrong with it.

[deeveedee]

@agstrato I don't think you need to reinstall Tahoe (just delete /Library/Preferences/com.apple.windowserver.plist and reboot as I mentioned earlier).

 

Also, I'm curious - if deleting /Library/Preferences/com.apple.windowserver.plist doesn't fix your "two monitor problem," what happens to the "two monitor problem" if you disconnect the display from your dGPU?

Edited November 7, 2025 by deeveedee

[carlo_67]

4 hours ago, agstrato said:

It's exactly what i thought i won't go Tahoe until i get this one properly setup.

I don't think you can get HDMI Audio in Tahoe unless you get the VoodooHDA, it doesn't work for me with that either (correct me if I'm wrong)

unless you want to break the security seals with other tools

[agstrato]

Just now, deeveedee said:

@agstrato I don't think you need to reinstall Tahoe (just delete /Library/Preferences/com.apple.windowserver.plist and reboot as I mentioned earlier).

 

Also, I'm curious - if deleting /Library/Preferences/com.apple.windowserver.plist doesn't fix your "two monitor problem," what happens to the "two monitor problem" if you disconnect the display from your dGPU?

I tried to disconnect the dGPU displayport cable and start up it still shows the 2 acer monitors... i could try to disconnect it while it's on just to see but something tells me it's gonna be the same.

Just now, carlo_67 said:

I don't think you can get HDMI Audio in Tahoe unless you get the VoodooHDA, it doesn't work for me with that either (correct me if I'm wrong)

unless you want to break the security seals with other tools

Well honestly i thought it's an option as i'm not getting any hdmi sound and i have this weird 2 monitor problem. My mobo only has 1 HDMI port behind i don't understand why macOS shows i have 2 monitors and less why is the second monitor a copy of the first one lol....

[carlo_67]

Here too you feed too many things to the properties, look at mine, id is not needed and neither is onboard-1

 

 

in addition to the others you put on the video card properties as it says Deeveede

 

 

[deeveedee]

@agstrato I have observed problems with patching con0 as a "dummy."  Did you test with con0 and con2 connectors unpatched before you patched them as dummy connectors?  Also, I thought you said that you did not need the EDID overrides.  Did I misunderstand you?

 

Attached is a revised config.plist with con0 and con2 left unpatched and the EDID override removed.  Please test this and report your findings.

config.plist.zip

[LockDown]

If you have acceleration and only want to get rid of the "extra display", check ioreg for the port and disable it using alldata

Edited November 8, 2025 by LockDown

[agstrato]

1 hour ago, deeveedee said:

@agstrato I have observed problems with patching con0 as a "dummy."  Did you test with con0 and con2 connectors unpatched before you patched them as dummy connectors?  Also, I thought you said that you did not need the EDID overrides.  Did I misunderstand you?

 

Attached is a revised config.plist with con0 and con2 left unpatched and the EDID override removed.  Please test this and report your findings.

config.plist.zip 6.93 kB · 1 download

Well with this config i only get 1 monitor which is how it's supposed to be so i think we're getting somewhere now. The volume slider is still greyed out though.

[agstrato]

One question guys, does alcid value matter for this or it should work even without it? I admit I haven't tested a lot I just liked the sound quality from alcid=28 and I kept with it...

[LockDown]

13 minutes ago, agstrato said:

does alcid value matter

yes

[deeveedee]

@agstrato That is progress.  Let's not try to disable any of the connectors (con0, con1 or con2) until we have evertything working.

 

Are you certain that your display is connected to con1 and not to con0 or con2?  You should be able to open IORegistryExplorer or Hackintool to see the connected display when booting with the config.plist that I provided.

 

alcid value matters since you are using AppleALC.  You'll need to match the alcid to the your board's audio codec.

 

EDIT: @LockDown didn't mean to step on your posts - I just realized that we're responding at the same time.  Why don't you take it from here.  Good luck!

Edited November 8, 2025 by deeveedee

[agstrato]

15 minutes ago, deeveedee said:

@agstrato That is progress.  Let's not try to disable any of the connectors (con0, con1 or con2) until we have evertything working.

 

Are you certain that your display is connected to con1 and not to con0 or con2?  You should be able to open IORegistryExplorer or Hackintool to see the connected display when booting with the config.plist that I provided.

 

alcid value matters since you are using AppleALC.  You'll need to match the alcid to the your board's audio codec.

 

EDIT: @LockDown didn't mean to step on your posts - I just realized that we're responding at the same time.  Why don't you take it from here.  Good luck!

I am not certain, honestly i found these values on a forum after battling for 2 days between God knows how many reboots and buffers. It said there these values are for my specific motherboard and hardware acceleration worked after adding them to my config.

I will see if i can test the framebuffer for each con.

21 minutes ago, LockDown said:

yes

Well damn, what do you suggest, first i try the framebuffer patch for each connector and then try all alcids or ?

[deeveedee]

1 minute ago, agstrato said:

I am not certain, honestly i found these values on a forum after battling for 2 days between God knows how many reboots and buffers. It said there these values are for my specific motherboard

 

If it's any consolation, I'm currently patching the frame buffer for an HP Elitebook 850 G7 laptop.  There are numerous EFIs shared for this laptop.  I haven't found one of them without mistakes and not a single one with the correct, fully patched frame buffer.  This may be a shock, but not everything you find on the internet is true.

[LockDown]

22 minutes ago, deeveedee said:

 

EDIT: @LockDown didn't mean to step on your posts - I just realized that we're responding at the same time.  Why don't you take it from here.  Good luck!

No No @deeveedee im just passing by 🙂