HD4600 kernel panic when plugging HDMI external monitor

[monsieurgateau]

[SOLVED] HD4600 kernel panic when plugging HDMI external monitor

Hi,

My Laptop, a Toshiba R30-A, has an Intel HD 4600 graphic controller that works beautifully on Yosemite 10.10.5 with FacePCIID + FakePCIID_HD4600_HD4400 and according modifications to Clover, but I discovered that when I plug in an HDMI external monitor, it would instantly KP. If I plug the monitor before booting, it will KP when entering graphic mode. Did quite a lot of research without finding anything better than "it's an HD4600 bug, live with it". Can you confirm that? I've seen various successes reports with multiple screens and that GPU.
I initially intended to use the VGA port, but as I understand, Apple does not support such ports anymore.

FWIW, here's the KP screenshot

 

[RehabMan]

Hi,

My Laptop, a Toshiba R30-A, has an Intel HD 4600 graphic controller that works beautifully on Yosemite 10.10.5 with FacePCIID + FakePCIID_HD4600_HD4400 and according modifications to Clover, but I discovered that when I plug in an HDMI external monitor, it would instantly KP. If I plug the monitor before booting, it will KP when entering graphic mode. Did quite a lot of research without finding anything better than "it's an HD4600 bug, live with it". Can you confirm that? I've seen various successes reports with multiple screens and that GPU.
I initially intended to use the VGA port, but as I understand, Apple does not support such ports anymore.

FWIW, here's the KP screenshot

You need to implement HDMI audio.

http://www.tonymacx86.com/el-capita...faq-read-first-laptop-frequent-questions.html

 

[monsieurgateau]

You need to implement HDMI audio.

http://www.tonymacx86.com/el-capita...faq-read-first-laptop-frequent-questions.html

Thank you for your reply, I totally missed that FAQ, sorry.
Nevertheless, I now have HDMI audio but the laptop still panics when plugging the HDMI cable, I guess the framebuffer edit isn't done correctly.

In your FAQ, you say that you can guess the ports can be guessed with IOreg, but I can't figure out how, what field does correspond to the port number (105. 204 and so on)?
In short, which value / method should we use to guess the port number?
Once patched, how can you tell the framebuffer is actually patched for HDMI?
Also, I've noted that every guide regarding the framebuffer edits explicitly say "Desktop only", any pointer on a laptop-centric documentation?

Thanks again

 

[RehabMan]

Thank you for your reply, I totally missed that FAQ, sorry.
Nevertheless, I now have HDMI audio but the laptop still panics when plugging the HDMI cable, I guess the framebuffer edit isn't done correctly.

In your FAQ, you say that you can guess the ports can be guessed with IOreg, but I can't figure out how, what field does correspond to the port number (105. 204 and so on)?
In short, which value / method should we use to guess the port number?
Once patched, how can you tell the framebuffer is actually patched for HDMI?
Also, I've noted that every guide regarding the framebuffer edits explicitly say "Desktop only", any pointer on a laptop-centric documentation?

Thanks again

Post ioreg: http://www.tonymacx86.com/audio/58368-guide-how-make-copy-ioreg.html. Please, use the IORegistryExplorer v2.1 attached to the post! DO NOT reply with an ioreg from any other version of IORegistryExplorer.app.


Post EFI/Clover folder.

How do you know you have HDMI audio if there is a crash upon connecting an HDMI device?

 

[monsieurgateau]

Post ioreg: http://www.tonymacx86.com/audio/58368-guide-how-make-copy-ioreg.html. Please, use the IORegistryExplorer v2.1 attached to the post! DO NOT reply with an ioreg from any other version of IORegistryExplorer.app.


Post EFI/Clover folder.

How do you know you have HDMI audio if there is a crash upon connecting an HDMI device?

Here comes the ioreg copy and Clover directory. I know you recommend AppleHDA, and you'll see I'm using VoodooHDA, but it seems the HDMI audio is recognized by it, plus I see it in Prefs/Sound.

Thanks for the help!

 

[RehabMan]

Here comes the ioreg copy and Clover directory. I know you recommend AppleHDA, and you'll see I'm using VoodooHDA, but it seems the HDMI audio is recognized by it, plus I see it in Prefs/Sound.

Thanks for the help!

You need to take a look at the HDMI audio patches in the plist files linked from my guide: http://www.tonymacx86.com/el-capita...de-booting-os-x-installer-laptops-clover.html

Use both the 0105 and 0204 since you have no idea which port your HDMI is attached to. Also there are two variants of each a "(12)" variant and one without the "(12)" in the comment (it uses 09). You will probably need the 12 variants.

Currently, you're patching only port 0105, not the 0204 port.

 

[monsieurgateau]

You need to take a look at the HDMI audio patches in the plist files linked from my guide: http://www.tonymacx86.com/el-capita...de-booting-os-x-installer-laptops-clover.html

Use both the 0105 and 0204 since you have no idea which port your HDMI is attached to. Also there are two variants of each a "(12)" variant and one without the "(12)" in the comment (it uses 09). You will probably need the 12 variants.

Currently, you're patching only port 0105, not the 0204 port.

Thanks a lot for your quick reply! Unfortunately it still panics, I added all the variants you have in your plist example without luck
Is there any way I can check if those patches applied correctly? I can see that AppleIntelFramebuffer@1 and 2 are correctly set to HDMI ("connector-type" = <00080000>)
Can this be linked to VoodooHDA being used instead of AppleHDA?

 

[RehabMan]

Thanks a lot for your quick reply! Unfortunately it still panics, I added all the variants you have in your plist example without luck

Adding all is invalid! Only the first one wins.

 

[monsieurgateau]

Adding all is invalid! Only the first one wins.

YES! port 0105(12) was the one! Thank you so much!

Yet, I'd like to understand, I thought that those patches role was to modify output of "connector-type", and as a matter of fact, that patch did not modify any of them, could you sum up what those patches do please?

 

[RehabMan]

YES! port 0105(12) was the one! Thank you so much!

Yet, I'd like to understand, I thought that those patches role was to modify output of "connector-type", and as a matter of fact, that patch did not modify any of them, could you sum up what those patches do please?

The patches *are* changing connector-type from <00 04 00 00> to <00 08 00 00>. But the the "(12)" variants also change something that is thought to be a delay. And changing it from 12 (from 09) tends to fix that reboot. It comes from an earlier version of the kext, without this reboot problem, where it was using 12 instead of 09 (I forget the version of OS X where that was the case). As if Apple made a delay shorter as it was ok for their hardware, but not PCs. Of course, it is all guessing...