Jump to content
  • Announcements

    • Allan

      Forum Rules   04/13/2018

      Hello folks! As some things are being fixed, we'll keep you updated. Per hour the Forum Rules don't have a dedicated "Tab", so here is the place that we have our Rules back. New Users Lounge > [READ] - InsanelyMac Forum Rules - The InsanelyMac Staff Team. 
Sign in to follow this  
owiowi

Can't detect display after updating to 10.12.5?

3 posts in this topic

Recommended Posts

Hi everyone, 

I got a very odd problem after updating to 10.12.5 and I'll try explaining it to the best I can along all troubleshooting I did...

 

I have a Macbook Pro retina 13" (early 2015) that I've always used with two Samsung external monitors (both are the same model). One of them is connected directly through the HDMI port located on the right side of the Macbook Pro, the other one connected through a thunderbolt-to-HDMI cable. It has always worked until last week when I updated to 10.12.5.

After the update, I quickly noticed that my Macbook Pro wouldn’t detect any external display via thunderbolt-to-HDMI. Thus, I started a long process of troubleshooting, and here’s all I’ve tried:

  • Assuming it could have been a defective cable, I’ve tried 3 different ones, still no luck
  • I’ve tried both thunderbolt entry, still no luck
  • I’ve tried thunderbolt-to-VGA, it WORKS, yes, I know this is insane.
  • I’ve tried to connect thunderbolt-to-HDMI (still with all 3 cables) on older Samsung monitors (again two older monitors were the same model, it was my old setup)… it worked
  • Then, I assumed it was the Samsung monitors that were broken (the two of them at the same time…? Odd, isn’t it?). Thus, I tried to connect them on my mac mini, the same way I always did on my Macbook pro… And it works…
  • Then I tried to reproduce the problem on my mom’s Macbook Pro retina 13” (exact same model I have the problem with and same update)... It works
  • Then I assumed the problem must be coming from my Macbook Pro. Thus, I booted on Windows 8 (bootcamp), it works.
  • Starting to lose my mind… I booted from an external hard drive I have (running an early sierra version), it didn’t work either (I had used this external hard drive in the past and it was WORKING)
  • I've done a factory reset, still not working

EDIT (forgot to mention):

  • SMC, no luck
  • NVRAM, no luck

 

So in a nutshell, the problem seems to appear only via thunderbolt-to-HDMI, only on this specific Macbook Pro, and specifically on macOS.

 

I’m no expert and I don’t know what else I can do. Of course I've tried contacting Apple many times but they keep blaming me for updating my mac and/or Samsung for making the environment not compatible, which I believe is a total nonsense. 

 

Has anyone encounter any similar problem? Does anyone know what it could be?

 

 

I’m desperate so I’d like to thank y’all in advance for your help.

 

Cheers

Share this post


Link to post
Share on other sites

First of all, thank you for you answer!

Yes, I failed to mention it but I tried SMC and NVRAM but no luck.

I'll try the combo update and update this post with the outcome once I'm done.

 

Again, thank you so much for you help!

 

EDIT:

- I tried to cables that are direct thunderbolt-to-hdmi, it doesn't work BUT...

- I tried an thunderbolt adapter with an HDMI entry (which wasn't working prior trying your suggestion)... and IT WORKS!!!!!!!!! 

 

I guess the problem isn't completely solved but for now I can live with that!

You're a GEM, thanks a ton!

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

Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Posts

    • I've tried these several methods of booting into clover, but it still skips. I even double checked that i was using your Clover folder. Bios settings should be the same too... this is getting really strange here.
    • Did you tried use ACPIBatteryManager.kext for the Battery? And for brightness you can use IntelBacklight  Both created by @RehabMan 
    • I have put it into clover drivers 64uefi folder on Yosemite thru High Sierra which allows me to edit my High Sierra disk if needed in Yosemite system.   There is no functionality of apfs in other versions but it does allow other clover bootloaders and systems to recognize the HS apfs drive or open it for inspection.   If you don’t have it you can’t see your HS drive or access it in another macOS version.
    • Hi! Is it possible to get codec AD1981 running with AppleHDA on HP Compaq 8710w? It works nicely with VoodooHDA. Speakers and HP are switching automatically.  Internal and HP mic also work - no switching in SysPref but it works when mic is plugged in and internal mic works when hp mic is unplugged.   It has same weird pathmap - connected directly:  Playback: nid=5 [pin: Speaker (Analog)] | + <- nid=3 [audio output] [src: pcm] bindSeq=00008001 nid=6 [pin: Headphones (Grey Left)] | + <- nid=3 [audio output] [src: pcm] bindSeq=00008001   But inputs are really weird. There are 5 nodes from input to HP mic/Internal mic nid=4 [audio input] | + <- nid=21 [audio selector] [src: mix] bindSeq=00000003 | + <- nid=12 [audio mixer] [src: mix] bindSeq=00000003 | + <- nid=30 [audio selector] [src: mic] bindSeq=00000001 | + <- nid=8 [pin: Microphone (Grey Left)] [src: mic] bindSeq=00000001 + <- nid=31 [audio selector] [src: monitor] bindSeq=00000002 | + <- nid=24 [pin: Microphone (Analog)] [src: monitor] bindSeq=00000002 Can pathmap like that even work with AppleHDA? What codec should I patch? I tried patches from AD1984 but no luck.    These are manually patched verbs: 00571c10 00571d01 00571e17 00571f90 00570C02 00671c20 00671d10 00671e21 00671f03 00771cf0 00771d00 00771e00 00771f40 00871c30 00871d10 00871e81 00871f03 00971cf0 00971d00 00971e00 00971f40 00a71cf0 00a71d00 00a71e00 00a71f40 01671cf0 01671d00 01671e00 01671f40 01771cf0 01771d00 01771e00 01771f40 01871c40 01871d01 01871ea0 01871f90 01971cf0 01971d00 01971e00 01971f40   Codecgraph and linux codecdump attached. Thx for any help or suggestions.              codec.txt 2.svg codec.txt


×