Jump to content
InsanelyMac Forum
bcc9

Intel HD Graphics 4600 (Haswell) working displayport

Recommended Posts

Hi Toleda.

I'm having this problem with a video card,

NVidia Geforce GT620.

My injection is

by DSDT

using Graphicsinjetion = No in clover.

Share this post


Link to post
Share on other sites
Advertisement

 

I'm having this problem with a video card,
NVidia Geforce GT620.
 

Are you using a Haswell processor with HD4600 graphics?  If not, post is off topic.

Share this post


Link to post
Share on other sites

Not sure what you mean by 7 SSDT. You can use a dsdt edit or an ssdt edit, up to you.

Have you tried other graphics ports on the motherboard?

Perhaps try what mirone23 did - hotplugging the HDMI after boot.

Check also if your system is logging errors in /var/log/system.log

Hi, thanks for the link.

 

Not sure that naming scheme is going to work out very well. The ivy bridge integrated graphics added hd graphics 4000, now the haswell graphics added hd graphics 4600/4400/4200 (and 5000/5100/5200). So thanks to intel's crazy naming scheme, that HD4K-ig key is overloaded.

 

Seems that the keyword doesn't even need the marketing number in it. I'd suggest a more general keyword such as intel-integrated, where the possible choices are built-in, and dynamically determined depending upon the PCI ID of the detected hardware.

For haswell hd graphics 4600, with PCI ID 8086:0412 the choices 0, 1, 2 could be the 3 platform-ids mentioned in this thread.

Thanks for your advice.

Finally got my Intel HD 4600 Graphics working at DP3/DP4 via mDP-->HDMI convertor.

Basically I need editing SSDT.aml and set ig-platform-id to 0000260c or 0000160a, and copy my SSDT-1.aml ~ SSDT-7.aml to /Extra too otherwise it may cause KP during booting.

Another issue bothers me a lot is I need add -f to org.chameleon.Boot.plist otherwise the above-mentioned will not work and freezes during booting

The graphics update 1.0 that was pushed out between DP3 and DP4 broke my system, but when I restored back to DP3, skipped the graphics update, and went straight to DP4, then everything was fine. Maybe it's just the graphics update 1.0 that is causing people problems?

Definitely that Graphics Update broke my Intel HD 4600 Graphics !

Share this post


Link to post
Share on other sites

So it turns out I wasn't able to just add to the existing GFX0 device entry in my DSDT when it isn't declared until an SSDT. (Any GFX0 definition in the DSDT overrides the SSDT one). To add to GFX0 I had to instead move the injection string to an SSDT, and this works. So here's an example alternate way to inject this, in its entirety. Works on my gigabyte system:

/*
 * Intel ACPI Component Architecture
 * AML Disassembler version 20120913-64 [Sep 15 2012]
 * Copyright (c) 2000 - 2012 Intel Corporation
 */

DefinitionBlock ("SSDT.aml", "SSDT", 1, "SaSsd", "SaSsdt", 0x00003000)
{
    External (\_SB_.PCI0.GFX0, DeviceObj)
    Scope (\_SB.PCI0.GFX0)
    {
            Method (_DSM, 4, NotSerialized)
            {
                Store (Package (0x04)
                {
                      "AAPL,ig-platform-id",
                       Buffer (0x04) { 0x03, 0x00, 0x22, 0x0d },
		      "hda-gfx", Buffer () { "onboard-1" }
                  }, Local0)
                DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
                Return (Local0)
                }
    }
    Method (DTGP, 5, NotSerialized)
    {
        If (LEqual (Arg0, Buffer (0x10)
                {
                    /* 0000 */    0xC6, 0xB7, 0xB5, 0xA0, 0x18, 0x13, 0x1C, 0x44, 
                    /* 0008 */    0xB0, 0xC9, 0xFE, 0x69, 0x5E, 0xAF, 0x94, 0x9B
                }))
        {
            If (LEqual (Arg1, One))
            {
                If (LEqual (Arg2, Zero))
                {
                    Store (Buffer (One)
                        {
                            0x03
                        }, Arg4)
                    Return (One)
                }

                If (LEqual (Arg2, One))
                {
                    Return (One)
                }
            }
        }

        Store (Buffer (One)
            {
                0x00
            }, Arg4)
        Return (Zero)
    }
}

I was wrong about chameleon too - I add the above to /Extra/SSDT.dsl and chameleon picks it up and osx reads in the rest of the ssdt's as well.

YES!! I was just about to come post about the SSDT edits when I read this! lol I've been looking at this issue for three days now. Then it dawned on me while looking at the DSDT Definitions where "External".  It was staring me right in the face... Well glad to see someone smarter than me figured it out first! 

Share this post


Link to post
Share on other sites

Not sure that naming scheme is going to work out very well. The ivy bridge integrated graphics added hd graphics 4000, now the haswell graphics added hd graphics 4600/4400/4200 (and 5000/5100/5200). So thanks to intel's crazy naming scheme, that HD4K-ig key is overloaded.

 

Seems that the keyword doesn't even need the marketing number in it. I'd suggest a more general keyword such as intel-integrated, where the possible choices are built-in, and dynamically determined depending upon the PCI ID of the detected hardware.

For haswell hd graphics 4600, with PCI ID 8086:0412 the choices 0, 1, 2 could be the 3 platform-ids mentioned in this thread.

Hi bcc9 and all.

I don't have this hardware at all :( so what I post here are just info:

This is the set of "available" FB I will implement in Enoch

	{ 0x00,0x00,0x06,0x04 },	// 0 "AAPL,ig-platform-id" HD5000 //FB: 64MB, Pipes: 3, Ports: 3, FBMem: 3 - mobile GT1
	{ 0x00,0x00,0x06,0x0c },	// 1 "AAPL,ig-platform-id" HD5000 //FB: 64MB, Pipes: 3, Ports: 3, FBMem: 3 - SDV mobile GT1
	{ 0x00,0x00,0x16,0x04 },	// 2 "AAPL,ig-platform-id" HD5000 //FB: 64MB, Pipes: 3, Ports: 3, FBMem: 3 - mobile GT2
	{ 0x00,0x00,0x16,0x0a },	// 3 "AAPL,ig-platform-id" HD5000 //FB: 64MB, Pipes: 3, Ports: 3, FBMem: 3 - ULT mobile GT2
	{ 0x00,0x00,0x16,0x0c },	// 4 "AAPL,ig-platform-id" HD5000 //FB: 64MB, Pipes: 3, Ports: 3, FBMem: 3 - SDV mobile GT2
	{ 0x00,0x00,0x26,0x04 },	// 5 "AAPL,ig-platform-id" HD5000 //FB: 64MB, Pipes: 3, Ports: 3, FBMem: 3 - mobile GT3
	{ 0x00,0x00,0x26,0x0a },	// 6 "AAPL,ig-platform-id" HD5000 //FB: 64MB, Pipes: 3, Ports: 3, FBMem: 3 - ULT mobile GT3
	{ 0x00,0x00,0x26,0x0c },	// 7 "AAPL,ig-platform-id" HD5000 //FB: 64MB, Pipes: 3, Ports: 3, FBMem: 3 - SDV mobile GT3
	{ 0x00,0x00,0x26,0x0d }, 	// 8 "AAPL,ig-platform-id" HD5000 //FB: 64MB, Pipes: 3, Ports: 3, FBMem: 3 - CRW mobile GT3
	{ 0x02,0x00,0x16,0x04 },	// 9 "AAPL,ig-platform-id" HD5000 //FB: 64MB, Pipes: 1, Ports: 1, FBMem: 1 - mobile GT2
	{ 0x03,0x00,0x22,0x0d }, 	// 10 "AAPL,ig-platform-id" HD5000 //FB: 0MB, Pipes: 0, Ports: 0, FBMem: 0 - CRW Desktop GT3
	{ 0x05,0x00,0x26,0x0a },	// 11 "AAPL,ig-platform-id" HD5000 //FB: 32MB, Pipes: 3, Ports: 3, FBMem: 3 - ULT mobile GT3
	{ 0x06,0x00,0x26,0x0a },	// 12 "AAPL,ig-platform-id" HD5000 //FB: 32MB, Pipes: 3, Ports: 3, FBMem: 3 - ULT mobile GT3
	{ 0x07,0x00,0x26,0x0d }, 	// 13 "AAPL,ig-platform-id" HD5000 //FB: 64MB, Pipes: 3, Ports: 4, FBMem: 3 - CRW mobile GT3
	{ 0x08,0x00,0x26,0x0a },	// 14 "AAPL,ig-platform-id" HD5000 //FB: 64MB, Pipes: 3, Ports: 3, FBMem: 3 - ULT mobile GT3
	{ 0x08,0x00,0x2e,0x0a } 	// 15 "AAPL,ig-platform-id" HD5000 //FB: 64MB, Pipes: 3, Ports: 3, FBMem: 3 - ULT reserved GT3
And Yep also for each deviceID will be add the correct name… or alternatively could be used a "range" of IDs

 

Fabio (ErmaC)

Share this post


Link to post
Share on other sites

...

Thanks and hope you can implement these in your bootloader as soon as possible.

I can confirm that because Asus Z87 Deluxe Dual has fixed 64 MB FBMem, both 0x00 0x00 0x16 0x0a  and 0x00 0x00 0x26 0x0c are working at DP3/DP4.

But 0x03 0x00 0x22 0x0d (0 MB) will cause KP for it immediately.

Share this post


Link to post
Share on other sites

Also would be nice get the complete name scheme:

Here the incomplete (probably with error) list:

	/* Haswell */
//	{ 0x80860402, "HD Graphics ????"        }, // Haswell Integrated Graphics Controller
	{ 0x80860406, "HD Graphics 4200 Mobile" }, // Haswell Integrated Graphics Controller - AppleIntelHD5000Graphics.kext
//	{ 0x8086040a, "HD Graphics 4400"        }, // Haswell Integrated Graphics Controller
	{ 0x80860412, "HD Graphics 4600"        }, // Haswell Integrated Graphics Controller - AppleIntelHD5000Graphics.kext
	{ 0x80860416, "HD Graphics 4600 Mobile"	}, // Haswell Integrated Graphics Controller - AppleIntelHD5000Graphics.kext
//	{ 0x8086041a, "HD Graphics P4600/P4700" }, // Haswell Integrated Graphics Controller
//	{ 0x80860422, "HD Graphics "		}, // Haswell Integrated Graphics Controller
	{ 0x80860426, "HD Graphics 4600 Mobile"	}, // Haswell Integrated Graphics Controller - AppleIntelHD5000Graphics.kext
//	{ 0x8086042a, "HD Graphics "		}, // Haswell Integrated Graphics Controller
	/* - - */
//	{ 0x80860a06, "HD Graphics ???? Mobile" }, // Haswell-ULT Integrated Graphics Controller
//	{ 0x80860a0e, "HD Graphics ???? Mobile" },
//	{ 0x80860a16, "HD Graphics ???? Mobile" }, // Haswell-ULT Integrated Graphics Controller - AppleIntelHD5000Graphics.kext
//	{ 0x80860a1e, "HD Graphics ???? Mobile" },
//	{ 0x80860a22, "????"                    }, // Haswell-ULT Integrated Graphics Controller
	{ 0x80860a26, "HD Graphics 5000 Mobile" }, // Haswell-ULT Integrated Graphics Controller - AppleIntelHD5000Graphics.kext
//	{ 0x80860a2a, "????"                    }, // Haswell-ULT Integrated Graphics Controller
	{ 0x80860a2e, "HD Graphics 5100 Mobile" }, // AppleIntelHD5000Graphics.kext

//	{ 0x80860c02, "Haswell HD Graphics"	},
	{ 0x80860c06, "HD Graphics Mobile"	}, // AppleIntelHD5000Graphics.kext
//	{ 0x80860c12, "Haswell HD Graphics"	},
	{ 0x80860c16, "HD Graphics Mobile"	}, // AppleIntelHD5000Graphics.kext
	{ 0x80860c22, "HD Graphics"		}, // AppleIntelHD5000Graphics.kext
	{ 0x80860c26, "HD Graphics Mobile"	}, // AppleIntelHD5000Graphics.kext
//	{ 0x80860d12, "HD Graphics 4600"	},
	{ 0x80860d22, "HD Graphics 5200"	}, // AppleIntelHD5000Graphics.kext
//	{ 0x80860d16, "HD Graphics 4600 Mobile"	}, // Crystal Well Integrated Graphics Controller
	{ 0x80860d26, "HD Graphics 5200 Mobile" }, // Crystal Well Integrated Graphics Controller - AppleIntelHD5000Graphics.kext
//	{ 0x80860d36, "????"			}, // Crystal Well Integrated Graphics Controller

	/* - - */

Share this post


Link to post
Share on other sites

Thanks and hope you can implement these in your bootloader as soon as possible.

I can confirm that because Asus Z87 Deluxe Dual has fixed 64 MB FBMem, both 0x00 0x00 0x16 0x0a  and 0x00 0x00 0x26 0x0c are working at DP3/DP4.

But 0x03 0x00 0x22 0x0d (0 MB) will cause KP for it immediately.

My gigabyte bios has 'Internal Graphics Memory Size' set to the default of 64M; no panic with any of the 3 discussed ig-platform-ids. 0x03 0x00 0x22 0x0d is not 0MB. If you look at offset 0xc for that layout, FramebufferMemorySize, it is 0x1 which is 64MB.

YES!! I was just about to come post about the SSDT edits when I read this! lol I've been looking at this issue for three days now. Then it dawned on me while looking at the DSDT Definitions where "External".  It was staring me right in the face... Well glad to see someone smarter than me figured it out first!

Thanks, seems like we need a master how-to thread on simplified SSDT edits for uefi systems.

Basically I need editing SSDT.aml and set ig-platform-id to 0000260c or 0000160a, and copy my SSDT-1.aml ~ SSDT-7.aml to /Extra too otherwise it may cause KP during booting.

I don't believe you. At least with chameleon, the system SSDTs should be picked up regardless unless you've configured dropssdt.

For example, I'm patching HDEF and GFX0 via /Extra/SSDT.dsl, and my ioregistry has:

"PCITopLevel" = ("GFX0","B0D3","XHC","GLAN","EHC2","HDEF","EHC1","LPCB","SAT0","SBUS")

 

where B0D3 is only defined in my BIOS's SSDT4. So SSDT4 is being picked up automatically.

Another issue bothers me a lot is I need add -f to org.chameleon.Boot.plist otherwise the above-mentioned will not work and freezes during booting

Maybe you need my dart=0 recommendation to avoid the VT-d booting problem? http://www.insanelymac.com/forum/topic/282989-vtd0-fault-after-1082-google-hasnt-heard-of-it-any-help/?do=findComment&comment=1867000

Also would be nice get the complete name scheme:

Here the incomplete (probably with error) list:

The most authoritative list of intel graphics PCIids is probably that from intel_driver.h in intel's xf86-video-intel source code release. Unfortunately that list is mapping the PCIids to the internal GT[123] names, not the marketing names...

I think it's a losing battle to make your config command use intel's marketing name. For haswell they already have 2 different naming schemes besides the internal GT[123] names (iris and hd graphics 4/5xxx)

 

Maybe you should just have a keyword like intel-integrated-hd and let the user specify all 4 bytes for AAPL,ig-platform-id as the value.

Share this post


Link to post
Share on other sites

For example, I'm patching HDEF and GFX0 via /Extra/SSDT.dsl, and my ioregistry has:

"PCITopLevel" = ("GFX0","B0D3","XHC","GLAN","EHC2","HDEF","EHC1","LPCB","SAT0","SBUS")

 

Is the 8086 2807 codec visible in B0D3/AppleHDAController/IOHDACodecDevice?

Share this post


Link to post
Share on other sites

Is the 8086 2807 codec visible in B0D3/AppleHDAController/IOHDACodecDevice?

No, that subtree is empty:

    | |   |   +-o IOHDACodecDevice@3,0  <class IOHDACodecDevice, id 0x1000002de, !registered, !matched, active, busy 0, retain 5>
    | |   |       {
    | |   |       }
    | |   |       
Don't I need an additional injection string for that device before it'd show up ? I don't really care as I don't have HDMI audio at my desk but I could configure it if you'd like...

Share this post


Link to post
Share on other sites

I see that with new MBA6,1 and MBA6,2 Apple is using HDAU for Intel HDMI audio (previously this was only the case for dedicated graphics). Should we be adding a HDAU device to PCI0 bus to mimic this and thus get HDMI (or DP for that matter) audio working? I'm referring to this: http://cl.ly/image/0Q3O3d372M1L

 

P.S. I hate the RMA manager.. it wasn't x-shipped after all...

Share this post


Link to post
Share on other sites

I see that with new MBA6,1 and MBA6,2 Apple is using HDAU for Intel HDMI audio (previously this was only the case for dedicated graphics). Should we be adding a HDAU device to PCI0 bus to mimic this and thus get HDMI (or DP for that matter) audio working? I'm referring to this: http://cl.ly/image/0Q3O3d372M1L

 

P.S. I hate the RMA manager.. it wasn't x-shipped after all...

Hmm, that's right, last time I had hdmi audio working I had to add an HDAU device with an additional hda-gfx injection string.

 

Amazon would have cross-shipped for you...

Share this post


Link to post
Share on other sites

Something of this nature perhaps? Not sure about the address though, this is the one fount on MB Airs.

    Scope (\_SB.PCI0)
    {
        Device (HDAU)
        {
            Name (_ADR, 0x00030000)
            Method (_DSM, 4, NotSerialized)
            {
                Store (Package (0x02)
                    {
                        "hda-gfx", 
                        Buffer (0x0A)
                        {
                            "onboard-1"
                        }
                    }, Local0)
                DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
                Return (Local0)
            }
        }
}

Wish I had access to Amazon, I'm dealing with online retailers here.. 

Share this post


Link to post
Share on other sites

No, that subtree is empty:

    | |   |   +-o IOHDACodecDevice@3,0  <class IOHDACodecDevice, id 0x1000002de, !registered, !matched, active, busy 0, retain 5>
    | |   |       {
    | |   |       }
    | |   |       

That is the problem.  8086 2807 is in 10.9 AppleHDA binary.  Injecting the codec_id and or device_id doesn't work. Renaming B0D3 to HDAU doesn't work.  HD5000 HDAU is similar to AMD/Nvidia HDAU, the difference is that it has it's own address, more like HDEF. There does not seem to be any difference with the GFX0/IGPU hda-gfx injection implementation between HD3000/HD4000 and the new HD5000.  As well, the dsdt code for HDAU and B0D3 is the same except for OperatingRegion and a couple of variables.   Adding hda-gfx to B0D3 does not enable the codec.  In DPCIManager, the codec appears with a null value and it does not appear in lspci while the HDMI codec does (0c0a or 0c0c).  It may be that the codec is disabled in the developer previews or it may be up to us to find the right injection string.  Ideas?

Share this post


Link to post
Share on other sites

I think you'd have to do both at the same time - rename B0D3 to HDAU AND inject hda-gfx onboard-1 before the HDMI audio will show up. That matches what I remember from last time I was looking at the actual AppleHDA code.

You would also need the matching hda-gfx injection string on the GFX0 device so that the driver can match the two devices up, but that's already in our SSDT example.

Under linux, the intel HDMI audio does show up under lspci, and it also shows up at application level (alsamixer).

00:03.0 Audio device [0403]: Intel Corporation Haswell HD Audio Controller [8086:0c0c] (rev 06)
	Subsystem: Intel Corporation Device [8086:2010]
	Flags: bus master, fast devsel, latency 0, IRQ 16
	Memory at f0434000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: snd_hda_intel

Update: Er, sorry that's just the controller that shows up under lspci, the HDMI codec shows up too however:

Codec: Intel Haswell HDMI
Address: 0
AFG Function Id: 0x1 (unsol 0)
Vendor Id: 0x80862807
Subsystem Id: 0x80860101
Revision Id: 0x100000
No Modem Function Group found
...

Share this post


Link to post
Share on other sites

My gigabyte bios has 'Internal Graphics Memory Size' set to the default of 64M; no panic with any of the 3 discussed ig-platform-ids. 0x03 0x00 0x22 0x0d is not 0MB. If you look at offset 0xc for that layout, FramebufferMemorySize, it is 0x1 which is 64MB.

Thanks, seems like we need a master how-to thread on simplified SSDT edits for uefi systems.

I don't believe you. At least with chameleon, the system SSDTs should be picked up regardless unless you've configured dropssdt.

For example, I'm patching HDEF and GFX0 via /Extra/SSDT.dsl, and my ioregistry has:

"PCITopLevel" = ("GFX0","B0D3","XHC","GLAN","EHC2","HDEF","EHC1","LPCB","SAT0","SBUS")

 

where B0D3 is only defined in my BIOS's SSDT4. So SSDT4 is being picked up automatically.

Maybe you need my dart=0 recommendation to avoid the VT-d booting problem? http://www.insanelymac.com/forum/topic/282989-vtd0-fault-after-1082-google-hasnt-heard-of-it-any-help/?do=findComment&comment=1867000

The most authoritative list of intel graphics PCIids is probably that from intel_driver.h in intel's xf86-video-intel source code release. Unfortunately that list is mapping the PCIids to the internal GT[123] names, not the marketing names...

I think it's a losing battle to make your config command use intel's marketing name. For haswell they already have 2 different naming schemes besides the internal GT[123] names (iris and hd graphics 4/5xxx)

 

Maybe you should just have a keyword like intel-integrated-hd and let the user specify all 4 bytes for AAPL,ig-platform-id as the value.

Thanks for your kind instruction and help.

You are right for that there is no need for /Extra SSDT-1~SSDT-7.aml. Only edited SSDT.aml is required.

However adding dart=0 does not work for my Asus Z87 Deluxe Dual. Originally Intel vd was disabled in BIOS.

I think kernelcache was not completely working because I had edited three kexts for IO80211(Airportbrcm4360), IOBluetoothFamily(BCM chip), and IOAHCIFamily.

By sudo kextcache -system-prelinked-kernel showed warn invalid signature for these 3 kexts.

Still waiting for further solution  from the expert like you.

Share this post


Link to post
Share on other sites

Hi I am trying to make my Intel HD 4600 Graphics work on my machine, I have tried many DSDT edits but they have not worked. When I extracted my DSDT it had errors which I had and it had no IGPU device so I added it with the dsm method but I removed the line DTGP because it had a error now I realise I needed to add the method ! But I think I added it in the wrong scope and much more. As my DSDT didn't have anything about GFX0 or IGPU in it, I'm assuming it it's in the SSDT so I want to do a SSDT edit, I have booted back into windows opened Aida64 to find I have seven SSDTs.. Which one do I use and add the method to? Then do I just put it in /Extra/SSDT.aml? Thanks guys :) My mobo is a Gigabyte z87-hd3 with a i5 4670k no dedicated GPU.

 

edit: Did another edited dsdt with the dsm from the first post and now I black screen like others. Is this because its for display port and I'm hdmi? Do I need to change the aapl Id or edit appleintelftamebuffer.kext?

 

Thanks again. I'm on dp4. Using intel hd 4600 with hdmi did want to use VGA but someone told me this patch doesn't work with it and only hdmi.

Share this post


Link to post
Share on other sites

The most authoritative list of intel graphics PCIids is probably that from intel_driver.h in intel's xf86-video-intel source code release. Unfortunately that list is mapping the PCIids to the internal GT[123] names, not the marketing names...

I think it's a losing battle to make your config command use intel's marketing name. For haswell they already have 2 different naming schemes besides the internal GT[123] names (iris and hd graphics 4/5xxx)

 

Maybe you should just have a keyword like intel-integrated-hd and let the user specify all 4 bytes for AAPL,ig-platform-id as the value.

Hi again... like this?

http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/tree/src/intel_driver.h

 

ErmaC

Share this post


Link to post
Share on other sites
Yes, exactly.

Any news re: HDMi audio on HD4600 ? I finally got my board delivered and after performing all the *usual* edits my HDACodecDevice is dead empty as mentioned earlier in the thread.

If the usual edits don't work (didn't do anything for me either; but then I didn't plug into a device with audio EDID so it shouldn't have worked...), then the next thing to check might be av-signal-type in the ioregistry (has to be 0x8 at least with nvidia HDMI http://www.projectosx.com/forum/index.php?showtopic=465&view=findpost&p=13585)

 

edit: see also connector-type

Share this post


Link to post
Share on other sites

well...

looking at the same "source" we can see useful name "scheme" http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/tree/src/intel_module.c

 

 

 

....

{PCI_CHIP_B43_G1, "B43"},

{PCI_CHIP_IRONLAKE_D_G, "HD Graphics"},

{PCI_CHIP_IRONLAKE_M_G, "HD Graphics"},

{PCI_CHIP_SANDYBRIDGE_GT1, "HD Graphics 2000" },

{PCI_CHIP_SANDYBRIDGE_GT2, "HD Graphics 3000" },

{PCI_CHIP_SANDYBRIDGE_GT2_PLUS, "HD Graphics 3000" },

{PCI_CHIP_SANDYBRIDGE_M_GT1, "HD Graphics 2000" },

{PCI_CHIP_SANDYBRIDGE_M_GT2, "HD Graphics 3000" },

{PCI_CHIP_SANDYBRIDGE_M_GT2_PLUS, "HD Graphics 3000" },

{PCI_CHIP_SANDYBRIDGE_S_GT, "HD Graphics" },

{PCI_CHIP_IVYBRIDGE_M_GT1, "HD Graphics 2500" },

{PCI_CHIP_IVYBRIDGE_M_GT2, "HD Graphics 4000" },

{PCI_CHIP_IVYBRIDGE_D_GT1, "HD Graphics 2500" },

{PCI_CHIP_IVYBRIDGE_D_GT2, "HD Graphics 4000" },

{PCI_CHIP_IVYBRIDGE_S_GT1, "HD Graphics" },

{PCI_CHIP_IVYBRIDGE_S_GT2, "HD Graphics P4000" },

{PCI_CHIP_HASWELL_D_GT1, "HD Graphics" },

{PCI_CHIP_HASWELL_D_GT2, "HD Graphics 4600" },

{PCI_CHIP_HASWELL_D_GT3, "HD Graphics 5000" }, /* ??? */

{PCI_CHIP_HASWELL_M_GT1, "HD Graphics" },

{PCI_CHIP_HASWELL_M_GT2, "HD Graphics 4600" },

{PCI_CHIP_HASWELL_M_GT3, "HD Graphics 5000" }, /* ??? */

{PCI_CHIP_HASWELL_S_GT1, "HD Graphics" },

{PCI_CHIP_HASWELL_S_GT2, "HD Graphics P4600/P4700" },

{PCI_CHIP_HASWELL_S_GT3, "HD Graphics 5000" }, /* ??? */

{PCI_CHIP_HASWELL_B_GT1, "HD Graphics" }, /* ??? */

{PCI_CHIP_HASWELL_B_GT2, "HD Graphics" }, /* ??? */

{PCI_CHIP_HASWELL_B_GT3, "HD Graphics" }, /* ??? */

{PCI_CHIP_HASWELL_E_GT1, "HD Graphics" },

{PCI_CHIP_HASWELL_E_GT2, "HD Graphics" }, /* ??? */

{PCI_CHIP_HASWELL_E_GT3, "HD Graphics" }, /* ??? */

{PCI_CHIP_HASWELL_ULT_D_GT1, "HD Graphics" }, /* ??? */

{PCI_CHIP_HASWELL_ULT_D_GT2, "HD Graphics" }, /* ??? */

{PCI_CHIP_HASWELL_ULT_D_GT3, "Iris™ Graphics 5100" },

{PCI_CHIP_HASWELL_ULT_M_GT1, "HD Graphics" },

{PCI_CHIP_HASWELL_ULT_M_GT2, "HD Graphics 4400" },

{PCI_CHIP_HASWELL_ULT_M_GT3, "HD Graphics 5000" },

{PCI_CHIP_HASWELL_ULT_S_GT1, "HD Graphics" }, /* ??? */

{PCI_CHIP_HASWELL_ULT_S_GT2, "HD Graphics" }, /* ??? */

{PCI_CHIP_HASWELL_ULT_S_GT3, "Iris™ Graphics 5100" },

{PCI_CHIP_HASWELL_ULT_B_GT1, "HD Graphics" }, /* ??? */

{PCI_CHIP_HASWELL_ULT_B_GT2, "HD Graphics" }, /* ??? */

{PCI_CHIP_HASWELL_ULT_B_GT3, "Iris™ Graphics 5100" },

{PCI_CHIP_HASWELL_ULT_E_GT1, "HD Graphics" },

{PCI_CHIP_HASWELL_ULT_E_GT2, "HD Graphics 4200" },

{PCI_CHIP_HASWELL_ULT_E_GT3, "Iris™ Graphics 5100" },

{PCI_CHIP_HASWELL_CRW_D_GT1, "HD Graphics" }, /* ??? */

{PCI_CHIP_HASWELL_CRW_D_GT2, "HD Graphics 4600" },

{PCI_CHIP_HASWELL_CRW_D_GT3, "Iris™ Pro Graphics 5200" },

{PCI_CHIP_HASWELL_CRW_M_GT1, "HD Graphics" }, /* ??? */

{PCI_CHIP_HASWELL_CRW_M_GT2, "HD Graphics 4600" },

{PCI_CHIP_HASWELL_CRW_M_GT3, "Iris™ Pro Graphics 5200" },

{PCI_CHIP_HASWELL_CRW_S_GT1, "HD Graphics" }, /* ??? */

{PCI_CHIP_HASWELL_CRW_S_GT2, "HD Graphics" }, /* ??? */

{PCI_CHIP_HASWELL_CRW_S_GT3, "Iris™ Pro Graphics 5200" },

{PCI_CHIP_HASWELL_CRW_B_GT1, "HD Graphics" }, /* ??? */

{PCI_CHIP_HASWELL_CRW_B_GT2, "HD Graphics" }, /* ??? */

{PCI_CHIP_HASWELL_CRW_B_GT3, "Iris™ Pro Graphics 5200" },

{PCI_CHIP_HASWELL_CRW_E_GT1, "HD Graphics" }, /* ??? */

{PCI_CHIP_HASWELL_CRW_E_GT2, "HD Graphics" }, /* ??? */

{PCI_CHIP_HASWELL_CRW_E_GT3, "Iris™ Pro Graphics 5200" },

 

....

 

 

 

thanks again for point me here.

 

ErmaC

Share this post


Link to post
Share on other sites

If the usual edits don't work (didn't do anything for me either; but then I didn't plug into a device with audio EDID so it shouldn't have worked...), then the next thing to check might be av-signal-type in the ioregistry (has to be 0x8 at least with nvidia HDMI http://www.projectosx.com/forum/index.php?showtopic=465&view=findpost&p=13585)

 

edit: see also connector-type

av-signal-type is reported as digital HDMI (08 00 00 00), connector-type is reported as HDMI (00 08 00 00). No joy here .. codec device won't appear no matter what, as described above by @toleda.

Share this post


Link to post
Share on other sites

This may or may not help. Im not really up on audio injection/HDA patching yet so take it a face value only. But HDMI will show in About this Mac and under speaker options in System preferences as a selectable item. I however, can't test as my monitor only has DVI input.

 

 

AudioDumpVoodoo.txt

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.



×