• Become a Premium Member for $25/year with no ads to improve your community experience. Upgrade to Pro Account for faster response and no wait times!

HDMI audio issues with open core (i5 8250u, ALC256) on Asus X507UAR

Yes already done. No change. Attaching latest EFI. What could I possibly be missing? AFAIK all renames are taken care of by whatevergreen.
What's the Device ID without the spoof? To find that out, simply remove the Audio Device Properties spoof and check in Hackintool.
 
I'm assuming this audio device ID will be shown in PCIE devices in Hackintool? In that case it's 0x9D71 (this is after deleting it in audio device properties spoof)
 
What's the Device ID without the spoof? To find that out, simply remove the Audio Device Properties spoof and check in Hackintool.
^^
 
I went ahead and used this layout ID (I put it as 719D0000) but no change. HDMI audio technically works, but have to unplug and replug, that's the whole issue. If I do unplug and replug, Intel Kabylake HDMI audio shows up, like I've mentioned previously. Should I try a different model number such as MacBookPro 15,x?
 
I'm assuming this audio device ID will be shown in PCIE devices in Hackintool?
Yes, correct.
In that case it's 0x9D71 (this is after deleting it in audio device properties spoof)
9D71 is a supported one and it does not need to be spoofed as it's done via WEG and AppleALC together. I installed Mojave on one of my old Laptops having the same ID. I did not need to spoof the Device ID.
I went ahead and used this layout ID (I put it as 719D0000) but no change. HDMI audio technically works, but have to unplug and replug, that's the whole issue. If I do unplug and replug, Intel Kabylake HDMI audio shows up, like I've mentioned previously. Should I try a different model number such as MacBookPro 15,x?
I faced a similar issue with a Coffee Lake Laptop and the solution was to spoof the Device ID. Although, the majority of that was handled via Device Properties with WEG and AppleALC. For your Hardware, MacBookPro14,1 seems to be the correct choice.

Further, your IOReg is still corrupt as you're using v3. The recommended version is v2.1. As per your IOReg, only HDMI seems to be connected with Internal Display not working. Is that the scenario?
 
Yes, correct.

9D71 is a supported one and it does not need to be spoofed as it's done via WEG and AppleALC together. I installed Mojave on one of my old Laptops having the same ID. I did not need to spoof the Device ID.

I faced a similar issue with a Coffee Lake Laptop and the solution was to spoof the Device ID. Although, the majority of that was handled via Device Properties with WEG and AppleALC. For your Hardware, MacBookPro14,1 seems to be the correct choice.

Further, your IOReg is still corrupt as you're using v3. The recommended version is v2.1. As per your IOReg, only HDMI seems to be connected with Internal Display not working. Is that the scenario?
Okay so I downloaded v2.1 and I'll attach the ioreg dump from that over here.

Also yes, my internal display, keyboard, trackpad, webcam, fingerprint sensor, battery etc has been removed. I'm only using the motherboard, RAM, Wifi/BT card, NVME and SATA drives on this system. HDMI is the primary display. The laptop is being used like a desktop so to speak. Could that be causing this issue?
 

Attachments

Also yes, my internal display, keyboard, trackpad, webcam, fingerprint sensor, battery etc has been removed. I'm only using the motherboard, RAM, Wifi/BT card, NVME and SATA drives on this system. HDMI is the primary display. The laptop is being used like a desktop so to speak. Could that be causing this issue?
Bummer. Not really, but it could be. Try the following. Simply replace the existing Device Properties with the following and reply with new PR files.

Code:
<key>DeviceProperties</key>
    <dict>
        <key>Add</key>
        <dict>
            <key>PciRoot(0x0)/Pci(0x1F,0x3)</key>
            <dict>
                <key>hda-gfx</key>
                <string>onboard-1</string>
                <key>layout-id</key>
                <integer>11</integer>
                <key>no-controller-patch</key>
                <integer>1</integer>
            </dict>
            <key>PciRoot(0)/Pci(0x02,0)</key>
            <dict>
                <key>AAPL,ig-platform-id</key>
                <data>AAAbWQ==</data>
                <key>device-id</key>
                <data>FlkAAA==</data>
                <key>framebuffer-con2-enable</key>
                <integer>1</integer>
                <key>framebuffer-con2-flags</key>
                <data>hwEAAA==</data>
                <key>framebuffer-con2-pipe</key>
                <data>EgAAAA==</data>
                <key>framebuffer-con2-type</key>
                <data>AAgAAA==</data>
                <key>framebuffer-fbmem</key>
                <data>AACQAA==</data>
                <key>framebuffer-patch-enable</key>
                <integer>1</integer>
                <key>framebuffer-stolenmem</key>
                <data>AAAwAQ==</data>
                <key>hda-gfx</key>
                <string>onboard-1</string>
            </dict>
        </dict>
        <key>Delete</key>
        <dict/>
    </dict>
 
Bummer. Not really, but it could be. Try the following. Simply replace the existing Device Properties with the following and reply with new PR files.

Code:
<key>DeviceProperties</key>
    <dict>
        <key>Add</key>
        <dict>
            <key>PciRoot(0x0)/Pci(0x1F,0x3)</key>
            <dict>
                <key>hda-gfx</key>
                <string>onboard-1</string>
                <key>layout-id</key>
                <integer>11</integer>
                <key>no-controller-patch</key>
                <integer>1</integer>
            </dict>
            <key>PciRoot(0)/Pci(0x02,0)</key>
            <dict>
                <key>AAPL,ig-platform-id</key>
                <data>AAAbWQ==</data>
                <key>device-id</key>
                <data>FlkAAA==</data>
                <key>framebuffer-con2-enable</key>
                <integer>1</integer>
                <key>framebuffer-con2-flags</key>
                <data>hwEAAA==</data>
                <key>framebuffer-con2-pipe</key>
                <data>EgAAAA==</data>
                <key>framebuffer-con2-type</key>
                <data>AAgAAA==</data>
                <key>framebuffer-fbmem</key>
                <data>AACQAA==</data>
                <key>framebuffer-patch-enable</key>
                <integer>1</integer>
                <key>framebuffer-stolenmem</key>
                <data>AAAwAQ==</data>
                <key>hda-gfx</key>
                <string>onboard-1</string>
            </dict>
        </dict>
        <key>Delete</key>
        <dict/>
    </dict>
Latest PR files attached. no change when I added the new device properties you gave me.
 

Attachments

Latest PR files attached. no change when I added the new device properties you gave me.
The connector has changed to @1 instead of 2. Simply replace con2 with con1 in Device Properties. Reply with new PR files.
 
The connector has changed to @1 instead of 2. Simply replace con2 with con1 in Device Properties. Reply with new PR files.
Okay changed to con1, new PR files attached.
 

Attachments

Forum statistics

Threads
1,935
Messages
18,077
Members
27,823
Latest member
GustavoMdancers