Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Displaylink is something completely different.

Different to what? Running monitors directly connected to the machine?

Well, yes, but it does put load on the CPU and GPU and move the same number bits of graphical data to external displays.

I can't say I noticed objectionable heat and noise when I have connected one or two monitors directly. I haven't tried 4K monitors, so this may be where the problem lies.
 
It's quite simple:

Plug in a monitor and check what wattage the GPU is using if it's higher than 15W then you have the problem. Whether this problem affects you personally is a whole different story as that is dependant on lots of factors like the environment you're in, usage, hearing........
 
I also tried the DisplayLink solution with the Dell D6000. I returned it because the monitors lag behind one frame and the refresh rate seems to go down to 30hz when a video is playing on one. I find it really noticeable using my mouse on the screen while the video is playing. But it does use less overall wattage and runs more cool. These are my results while watching a fullscreen video on one monitor using an i7 5300M with 3 monitors (1 x 1080p@60hz over HDMI and 2 x 1440p@60hz over DisplayPort)

1600954440797.png
 
  • Like
Reactions: Yurk
Well, yes, but it does put load on the CPU and GPU and move the same number bits of graphical data to external displays.

Nope it doesn't. It moves data over USB (like copying data to a USB drive). It doesn't use the DisplayPort subsystem of the GPU (and the TB controllers). It moves way less data over the wire because it's compressed.
Yeah, it does increase load on the CPU/GPU, but it doesn't fire up the VRAM to full clock speed. Actually it doesn't even fire up the AMD GPU. DisplayLink can be used with the iGPU.

While DisplayLink is technically more inefficient than connecting a monitor directly, it doesn't trigger this flaw on the 16" like directly connected monitors do.
 
The problem is with the 5300m/5500m. Most people with the 5600m stated that the problems were fixed. I think only 2 people have had issues with the 5600m. Search google for 5600m site:https://forums.macrumors.com/threads/16-is-hot-noisy-with-an-external-monitor.2211747 to see what the owners said.
Right, my i7 5600M stay cool at normal use.

Internal monitor plus LG5k connected to the right port at idle:

MBP16_i75600M_LG5k+Internal.png


Internal monitor plus Dell lU3818DW on the right, and Apple LED Cinema Display (27 inch) to the left through a docking at idle:
MBP16_i7_5600M_DellU3818DW+LEDCinema+Internal.png


I do noticed that Thunderbolt is the hot spot when connect to 5k monitor.
 
  • Like
Reactions: Minga089 and Yurk
BigSur Beta 8 (public beta 4) fixed the problem for me (it seems).

My config: MBP 16 5500m 8GB, clamshell mode <--- USB-C DisplayPort cable ----> single 4K 32" Samsung monitor (60 Hz)

USB-C-DP cable - left side
Right side - power and 1 Gbps ethernet cable (1 Gbps internet connection)

It used to be loud as hell, now it seems to be fixed by software (<2600 rpm when normal work, for me it's inaudible, MBP is >1m away from me).

With Catalina I suffered from 3500-5500 rpms for no reason.

Now when I compile something - the CPU spikes - which is natural and expected.
But no more jet engine sound on my right side when typing this post in Safari.
What a relief!

Was literally about to say this worked for me too. Then kernel task kicked in.

I was literally only watching a 4k video on my external monitor in clamshell mode. It did seem to last longer than normal hence why I almost sang the new beta's praises.
 
  • Like
Reactions: Yurk
BigSur Beta 8 (public beta 4) fixed the problem for me (it seems).

My config: MBP 16 5500m 8GB, clamshell mode <--- USB-C DisplayPort cable ----> single 4K 32" Samsung monitor (60 Hz)

USB-C-DP cable - left side
Right side - power and 1 Gbps ethernet cable (1 Gbps internet connection)

It used to be loud as hell, now it seems to be fixed by software (<2600 rpm when normal work, for me it's inaudible, MBP is >1m away from me).

With Catalina I suffered from 3500-5500 rpms for no reason.

Now when I compile something - the CPU spikes - which is natural and expected.
But no more jet engine sound on my right side when typing this post in Safari.
What a relief!
Check your GPU power consumption, I guess it's still around 18W.
 
  • Like
Reactions: Minga089 and dooyou
As you can read here on Macrumors today, the graphics problem of the new iMac 27" is now fixed. Forget this thread, Apple will not do anything more for this MBP.
 
As you can read here on Macrumors today, the graphics problem of the new iMac 27" is now fixed. Forget this thread, Apple will not do anything more for this MBP.

of course Apple won’t fix it. Because they don’t see it as Problem. They designed it that way. So to then, it’s working as expected. Ergo: Nothing to fix.
We can only bug them and let our machines get repaired/replaced over and over again until they might offer you a refund. But I’m afraid that even that won’t make apple change their minds.
As long as YouTubers and the tech press are praising this machine, Apple doesn’t care at all.

At the time, an Apple engineer told me, that the machine is working as designed, I knew it won’t get fixed. And if someone still believes Apple would care about that or even thinking about to fix this, then I have bad news for you: They don’t and they never will until they’re forced to.

the only solution is to buy the 16“ with a 5600M. Sadly this was not an option at the time I bought mine. And upgrading isn’t possible. So I’m stuck with a 4000€ machine that’s broken by design and Apple continues to tell me that it’s „working as designed“ (whatever this is).

To summarize it: there’s no solution and there probably will never be one.
 
  • Like
Reactions: 09872738 and c0ppo
of course Apple won’t fix it. Because they don’t see it as Problem. They designed it that way. So to then, it’s working as expected. Ergo: Nothing to fix.
We can only bug them and let our machines get repaired/replaced over and over again until they might offer you a refund. But I’m afraid that even that won’t make apple change their minds.
As long as YouTubers and the tech press are praising this machine, Apple doesn’t care at all.

At the time, an Apple engineer told me, that the machine is working as designed, I knew it won’t get fixed. And if someone still believes Apple would care about that or even thinking about to fix this, then I have bad news for you: They don’t and they never will until they’re forced to.

the only solution is to buy the 16“ with a 5600M. Sadly this was not an option at the time I bought mine. And upgrading isn’t possible. So I’m stuck with a 4000€ machine that’s broken by design and Apple continues to tell me that it’s „working as designed“ (whatever this is).

To summarize it: there’s no solution and there probably will never be one.

That's why I got the eGPU which by the way might be a dead end with arm anyway lol but since I got it for dirt cheap figured what the hell. At least now I am happy with performance... for most part ;)
 
That's why I got the eGPU which by the way might be a dead end with arm anyway lol but since I got it for dirt cheap figured what the hell. At least now I am happy with performance... for most part ;)

Still a joke that you need an external GPU for an about 4000€ „Pro“ Laptop to behave with an external display.
I also planned to get an eGPU. But the prices for them are ridiculous. Actually I would be glad if Apple would let me upgrade to the 5600M. Even if that means I’m shoving more money down their throats.
I stopped using an external screen for now. I can’t concentrate while sitting next to a jetengine
 
Nope it doesn't. It moves data over USB (like copying data to a USB drive). It doesn't use the DisplayPort subsystem of the GPU (and the TB controllers). It moves way less data over the wire because it's compressed.
Yeah, it does increase load on the CPU/GPU, but it doesn't fire up the VRAM to full clock speed. Actually it doesn't even fire up the AMD GPU. DisplayLink can be used with the iGPU.

While DisplayLink is technically more inefficient than connecting a monitor directly, it doesn't trigger this flaw on the 16" like directly connected monitors do.

Thanks for the information. Interesting!
 
of course Apple won’t fix it. Because they don’t see it as Problem. They designed it that way. So to then, it’s working as expected. Ergo: Nothing to fix.
We can only bug them and let our machines get repaired/replaced over and over again until they might offer you a refund. But I’m afraid that even that won’t make apple change their minds.
As long as YouTubers and the tech press are praising this machine, Apple doesn’t care at all.

At the time, an Apple engineer told me, that the machine is working as designed, I knew it won’t get fixed. And if someone still believes Apple would care about that or even thinking about to fix this, then I have bad news for you: They don’t and they never will until they’re forced to.

the only solution is to buy the 16“ with a 5600M. Sadly this was not an option at the time I bought mine. And upgrading isn’t possible. So I’m stuck with a 4000€ machine that’s broken by design and Apple continues to tell me that it’s „working as designed“ (whatever this is).

To summarize it: there’s no solution and there probably will never be one.


Even if they realize that it is a design flaw, internally They would never let any customer-facing ppl to admit it to the customers. (tho they might decide to quietly 'fix' it in subsequent revisions/models)

But from what I've read. They decided that Intel Macs were 'dead' since Skylake anyway. So I think their rationale would be just to keep the platform on 'life-support' until their ARM64/"Apple Silicon" products comes online.

IMO I see their hardware evolution since 2016 as they start to shift away from conventional X86+EFI platform and letting their T-Series chip taking over more and more functionalities (first security (T1), then adding NVMeController, then HW decoding/Acceleration (X.265) among other processing capabilities and having its own non-standard-PCH-based boot sequence) (T2) )

That's why I am might wait until at least gen 2-3 of ARM64 Macs to hit the market (If I can hold off the temptaion of being their paying guinea pig that is)
 
  • Like
Reactions: Yurk
For those using DisplayLink, how is the system stabilty, particularly across sleep/wake cycles? Any issues apart from the expected performance overhead?
 
For those using DisplayLink, how is the system stabilty, particularly across sleep/wake cycles? Any issues apart from the expected performance overhead?

No issues in regular use to report so far. I did have one time where I couldn't see the external screens and had to reboot, but I've had similar issues in the past with directly-connected external monitors. It may have been unrelated to DisplayLink. Quality and refresh rates are good. I can't really see any difference on my FHD monitors between DisplayPort via a dock and direct connections.
 
  • Like
Reactions: topcat001
He never mentioned that he uses Windows 10 though
I
BigSur Beta 8 (public beta 4) fixed the problem for me (it seems).

My config: MBP 16 5500m 8GB, clamshell mode <--- USB-C DisplayPort cable ----> single 4K 32" Samsung monitor (60 Hz)

USB-C-DP cable - left side
Right side - power and 1 Gbps ethernet cable (1 Gbps internet connection)

It used to be loud as hell, now it seems to be fixed by software (<2600 rpm when normal work, for me it's inaudible, MBP is >1m away from me).

With Catalina I suffered from 3500-5500 rpms for no reason.

Now when I compile something - the CPU spikes - which is natural and expected.
But no more jet engine sound on my right side when typing this post in Safari.
What a relief!
Are you using clamshell mode or open lid? Most people have no issue with DisplayPort and clamshell mode. The problem is when you use open lid or HDMI. So what you are reporting is not really a fix. Check your Radeon High Side power consumption with the lid open. It will probably still be 18-20 Watts.
 
Last edited:
  • Like
Reactions: dooyou
For those using DisplayLink, how is the system stabilty, particularly across sleep/wake cycles? Any issues apart from the expected performance overhead?
There is little CPU overhead, certainly less energy and heat than what the Radeon 5500M consumes. Stability, sleep, wake are all fine with displaylink. The only issue is that 4K HiDPI resolutions are laggy. 4K native or 1080p native are fine.
 
  • Like
Reactions: topcat001
Different to what? Running monitors directly connected to the machine?

Well, yes, but it does put load on the CPU and GPU and move the same number bits of graphical data to external displays.

I can't say I noticed objectionable heat and noise when I have connected one or two monitors directly. I haven't tried 4K monitors, so this may be where the problem lies.
Displaylink does not load the GPU at all. It only uses the CPU (less than one core, and you havee 6-8 cores available). That energy and heat is a lot less than what the awful Radeon 5500M consumes.
 
  • Like
Reactions: johngwheeler
I

Are you using clamshell mode or open lid? Most people have no issue with DisplayPort and clamshell mode. The problem is when you use open lid or HDMI. So what you are reporting is not really a fix. Check your Radeon High Side power consumption with the lid open. It will probably still be 18-20 Watts.

I use DisplayLink with the MBP16 open and two external displays. No issues so far.
 
Right, my i7 5600M stay cool at normal use.

Internal monitor plus LG5k connected to the right port at idle:

View attachment 958701

Internal monitor plus Dell lU3818DW on the right, and Apple LED Cinema Display (27 inch) to the left through a docking at idle:
View attachment 958703

I do noticed that Thunderbolt is the hot spot when connect to 5k monitor.
How many hours did you use your MBP at idle before making those screenshots?
 
Right, my i7 5600M stay cool at normal use.

Internal monitor plus LG5k connected to the right port at idle:

View attachment 958701

Internal monitor plus Dell lU3818DW on the right, and Apple LED Cinema Display (27 inch) to the left through a docking at idle:
View attachment 958703

I do noticed that Thunderbolt is the hot spot when connect to 5k monitor.
Do you mind trying to run all of your screens with higher resolutions with this app? It's a terrific app that gives you so much extra real estate and extra pixels.

www.madrau.com

It's a cool thing and every Mac user should try it. I use it on all of my computers and it make them warmer when I double native resolutions. So would love to see what your 5600m is capable of.
 
BigSur Beta 8 (public beta 4) fixed the problem for me (it seems).

My config: MBP 16 5500m 8GB, clamshell mode <--- USB-C DisplayPort cable ----> single 4K 32" Samsung monitor (60 Hz)

USB-C-DP cable - left side
Right side - power and 1 Gbps ethernet cable (1 Gbps internet connection)

It used to be loud as hell, now it seems to be fixed by software (<2600 rpm when normal work, for me it's inaudible, MBP is >1m away from me).

With Catalina I suffered from 3500-5500 rpms for no reason.

Now when I compile something - the CPU spikes - which is natural and expected.
But no more jet engine sound on my right side when typing this post in Safari.
What a relief!


Don't give me a false hope :(
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.