Contribute
Register

[XPS-9360] USB-C to HDMI Audio still not working

Status
Not open for further replies.
Joined
Jun 25, 2011
Messages
179
Motherboard
Dell XPS 13 9360/(Clover v.4411)
CPU
Intel Skylake i7-7500U 2.70GHz (Kaby Lake)
Graphics
Intel Iris 620 3200 x 1800
Mac
  1. MacBook Pro
Mobile Phone
  1. iOS
I have the XPS9360 laptop and I've tried using the FakePCIID.kext and FakePCIID_Intel_HDMI_Audio.kext and 2 different types of USB-C to HDMI cables and adapter and still unable to get audio through TV, but I do have video. I read several of @RehabMan threads and instructions, but still confused as to what could be the problem or how to fix it. Cable and adapter tested under Windows fine. Please see attached files for ioreg, clover and files for problem troubleshooting.
 

Attachments

  • rmntna_ioreg_and_files.zip
    3.3 MB · Views: 129
Last edited:
I have the XPS9360 laptop and I've tried using the FakePCIID.kext and FakePCIID_Intel_HDMI_Audio.kext and 2 different types of USB-C to HDMI cables and adapter and still unable to get audio through TV, but I do have video. I read several of @RehabMan threads and instructions, but still confused as to what could be the problem or how to fix it. Cable and adapter tested under Windows fine. Please see attached files for ioreg, clover and files for problem troubleshooting.

If the monitor that is shown in ioreg at framebuffer@1 is connected to HDMI, you have not patched the connector for HDMI. connector-type still shows DP <00 04 00 00> instead of HDMI <00 08 00 00>.

Also, "hda-gfx"="onboard-1" is not injected in HDEF. Must be injected on IGPU and HDEF.
 
If the monitor that is shown in ioreg at framebuffer@1 is connected to HDMI, you have not patched the connector for HDMI. connector-type still shows DP <00 04 00 00> instead of HDMI <00 08 00 00>.

Also, "hda-gfx"="onboard-1" is not injected in HDEF. Must be injected on IGPU and HDEF.

Ok that's where I was getting confused after reading your guide here- https://www.tonymacx86.com/threads/...o-sandy-ivy-haswell-broadwell-skylake.189495/
Do I do this in the clover config.plist or patch the DSDT with your github patches. or something else?

Thanks
 
Last edited:
DP->HDMI is a framebuffer patch (via config.plist KextsToPatch).
Injecting "hda-gfx" is usually done with ACPI (various ways to do it though...)

Ok so in order to determine the correct port number, can I just get that from the lspci values?

Audio device [0403]: Intel Corporation Device [8086:9d71] (rev 21)
or
somewhere in the AppleIntelframebuffer ioreg?

UPDATE: I found the port# 0x5 in ioreg. but I reread your guide and I still don't understand where to get the numbers from.
 
Last edited:
Ok so in order to determine the correct port number, can I just get that from the lspci values?

Audio device [0403]: Intel Corporation Device [8086:9d71] (rev 21)
or
somewhere in the AppleIntelframebuffer ioreg?

UPDATE: I found the port# 0x5 in ioreg. but I reread your guide and I still don't understand where to get the numbers from.

Each connector in the framebuffer (ig-platform-id data) is positional with respect to [email protected]@3 in ioreg.
 
Each connector in the framebuffer (ig-platform-id data) is positional with respect to [email protected]@3 in ioreg.

So if ig-platform-id value is <04 00 26 19> and framebuffer@1 would be port 0401 or do I use the propertyname for port and value 0x5 then it would be 0405 or simply 0401?
I'm sorry @RehabMan but I still cannot wrap my ADD brain around what I'm looking for and what these mean. I learn better visually. I'm very confused by all these property names and values.

w6g4apwp1

w6g4apwp1
 
Last edited:
So if ig-platform-id value is <04 00 26 19> and framebuffer@1 would be port 0401 or do I use the propertyname for port and value 0x5 then it would be 0405 or simply 0401?
I'm sorry @RehabMan but I still cannot wrap my ADD brain around what I'm looking for and what these mean. I learn better visually. I'm very confused by all these property names and values.

w6g4apwp1
https://postimg.org/image/w6g4apwp1/ [/IMG]
w6g4apwp1

ig-platform data for 0x19260004:

04 00 26 19 00 00 00 00 5D 09 08 00 00 00 00 00 01 03 03 03 00 00 20 02 00 00 00 00 00 00 00 60 6C 05 00 00 6C 05 00 00 00 00 00 00 00 00 00 00
00 00 08 00 02 00 00 00 98 04 00 00
01 05 09 00 00 04 00 00 C7 01 00 00
02 04 0A 00 00 04 00 00 C7 01 00 00
FF 00 00 00 01 00 00 00 20 00 00 00
0A 0B 03 00 00 07 06 00 03 00 00 00 04 00 00 00 80 DF 17 10 00 00 00 00 78 05 00 00 D2 05 00 00 40 06 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20 23 1B 00 00 00 00 00 D0 23 1B 00 00 00 00 00 D0 23 1B 00 00 00 00 00 02 00 00 00 08 00 00 00 00 00 00 00 00 00 00 00

So framebuffer@1 is the connector data:
01 05 09 00 00 04 00 00 C7 01 00 00
 
ig-platform data for 0x19260004:

04 00 26 19 00 00 00 00 5D 09 08 00 00 00 00 00 01 03 03 03 00 00 20 02 00 00 00 00 00 00 00 60 6C 05 00 00 6C 05 00 00 00 00 00 00 00 00 00 00
00 00 08 00 02 00 00 00 98 04 00 00
01 05 09 00 00 04 00 00 C7 01 00 00
02 04 0A 00 00 04 00 00 C7 01 00 00
FF 00 00 00 01 00 00 00 20 00 00 00
0A 0B 03 00 00 07 06 00 03 00 00 00 04 00 00 00 80 DF 17 10 00 00 00 00 78 05 00 00 D2 05 00 00 40 06 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20 23 1B 00 00 00 00 00 D0 23 1B 00 00 00 00 00 D0 23 1B 00 00 00 00 00 02 00 00 00 08 00 00 00 00 00 00 00 00 00 00 00

So framebuffer@1 is the connector data:
01 05 09 00 00 04 00 00 C7 01 00 00

Ok, thank you for that, but that doesn't really answer my question and now you've just confused me even more. What am I supposed to do with these numbers? Where do I look to get that information, so that I know and learn where and what for next time or can help others down the road. Did you just need to convert that ig-platform data into Hex?

 
Last edited:
Ok, thank you for that, but that doesn't really answer my question. Where do I look to get that information, so that I know and learn where and what. Or do I just need to convert that ig-platform data into Hex?


I pulled that data directly from the AppleIntelSKLGraphicsFramebuffer kext binary.
You can use a hex editor (I use Hex Fiend) and search for 04 00 26 19. What follows is the data (184 bytes) for the related ig-platform-id up to the next ig-platform-id (which happens to be 0x19270004).
 
Status
Not open for further replies.
Back
Top