I think it has to do with the resolution the monitor is capable of over each cable. Can you run this command with HDMI/DP?It depends how you connect the monitor. With my HyperDrive USB-C to DisplayPort to HDMI, it goes to 20W with DisplayPort but drops down to 5W when that same signal gets converted to HDMI. Go figure. Both in clamshell.
% system_profiler SPDisplaysDataType | grep -C1 Resolution
S32D850:
Resolution: 5120 x 2880 (5K/UHD+)
UI Looks like: 2560 x 1440 @ 60.00Hz
I'm actually using one of these: https://tweakers.net/pricewatch/125...-c-4k60hz-hdmi-en-mini-displayport-zwart.htmlI think it has to do with the resolution the monitor is capable of over each cable. Can you run this command with HDMI/DP?
Code:% system_profiler SPDisplaysDataType | grep -C1 Resolution S32D850: Resolution: 5120 x 2880 (5K/UHD+) UI Looks like: 2560 x 1440 @ 60.00Hz
Thx, but as I said before: I would never use my 1440p monitor in native 2560x1440 in MacOS anyway because everything looks like sh** that way. HiDPI is the way to go and on top the power draw is only 5W in clamshell mode without having to apply any workaround.It depends how you connect the monitor. With my HyperDrive USB-C to DisplayPort to HDMI, it goes to 20W with DisplayPort but drops down to 5W when that same signal gets converted to HDMI. Go figure. Both in clamshell.
It's not a "solution". It's a workaround. If you can't use your laptop with its internal screen on when connecting an external monitor, then it's a faulty laptop.
Because my monitor is a 24" QHD monitor and it's unusable in MacOS in native resolution. 125% scaled is perfect.Why do you use 2048x1152 HiDPI? 1440p HiDPI looks fine to me. Though I use a 32 inch monitor. Maybe 2048x1152 HiDPI looks better on a smaller display?
5120x2160Have you tried using the Default for Display option? My MacBook gets hot using some of the scaled options.
It is a "Solution" for those who are currently using their macbook in clamshell mode and having problem to reduce the Radeon High Side power to around 5 Watt. I never said I solved the heating issue altogther using this method. You may read my original post as well. Clearly i mentioned for Clamshell mode.It depends how you connect the monitor. With my HyperDrive USB-C to DisplayPort to HDMI, it goes to 20W with DisplayPort but drops down to 5W when that same signal gets converted to HDMI. Go figure. Both in clamshell.
It's not a "solution". It's a workaround. If you can't use your laptop with its internal screen on when connecting an external monitor, then it's a faulty laptop.
% system_profiler SPDisplaysDataType | grep -C1 Resolution
S32D850:
Resolution: 2560 x 1440 (QHD/WQHD)
UI Looks like: 2560 x 1440 @ 60.00Hz
% system_profiler SPDisplaysDataType | grep -C1 Resolution
S32D850:
Resolution: 5120 x 2880 (5K/UHD+)
UI Looks like: 2560 x 1440 @ 60.00Hz
_ _ _____ _____ _____ _____
| | | | |_ _| | __ \ | __ \ |_ _|
| |__| | | | | | | | | |__) | | |
| __ | | | | | | | | ___/ | |
| | | | _| |_ | |__| | | | _| |_
|_| |_| |_____| |_____/ |_| |_____|
============================================
(1) Enable HIDPI
(2) Enable HIDPI (with EDID)
(3) Disable HIDPI
Enter your choice [1~3]: 1
-------------------------------------
|********** Display Icon ***********|
-------------------------------------
(1) iMac
(2) MacBook
(3) MacBook Pro
(4) LG Display
(5) Pro Display XDR
(6) Do not change
Enter your choice [1~6]: 6
------------------------------------------
|********** resolution config ***********|
------------------------------------------
(1) 1920x1080 Display
(2) 1920x1080 Display (use 1424x802, fix underscaled after sleep)
(3) 1920x1200 Display
(4) 2560x1440 Display
(5) 3000x2000 Display
(6) Manual input resolution
Enter your choice: 4
Enabled, please reboot.
Rebooting the logo for the first time will become huge, then it will not be
That's exactly what I mentioned a few comments before. HiDPI does the trick.TLDR: My 2019 Macbook Pro 16" 5300M gets hot and noisy when connected to a 2560x1440p60 monitor, even when idle and the lid is closed. This post outlines a partial solution that enables silent operation.
The 2019 MacBook Pro 16" with base 5300M GPU has a problem.
If you connect models with this specific GPU to an external monitor with an extremely specific (but common) resolution, many users report that their MacBook gets really hot and the fans spin up really loudly, even if they close the screen lid.
Specifically, many users report extremely loud fans when connected to 2560x1440p60 monitors. The problem is with this specific resolution and 5300M GPU combination. Tons of users report no problems when using 1080p or 4K monitors or with the upgraded 5600M GPUs.
The solution to this problem, however, is just force enabling HiDPI mode for the monitor (instructions later). Unfortunately though, this solution requires the MacBook lid to be closed. I haven’t found any solution that fixes the problem while also keeping the lid open.
DISCLAIMER: This article only considers a 2019 MacBook Pro 16" on Big Sur 11.5.1 with 5300M graphics connected to a single external 32 inch 2560x1440p60 display. If you have a different setup, no guarantee this will work, since this issue might be a bug with exactly this GPU/resolution combination. I’ve seen many reports of no issues on the 5600M.
***
Before, when connected to a 32 inch 1440p monitor, my MacBook Pro 16 inch reports 18–20W of power draw from the GPU. This is regardless of whether or not the Macbook lid is closed.
Code:% system_profiler SPDisplaysDataType | grep -C1 Resolution S32D850: Resolution: 2560 x 1440 (QHD/WQHD) UI Looks like: 2560 x 1440 @ 60.00Hz
I switched to “Scaled” for demonstration purposes, but I typically just use “Default for Display”.
When I look at the GPU power draw, I see:
Source screenshot from the free Stats app was 2560x1440. The equivalent statistic on iStat Menus is Radeon High Side.
This is insane power draw for a laptop at idle. It doesn’t take long for all this extra power to heat up the laptop and cause the fans to start roaring, even with nothing running, just idle.
Moreover, I noticed that after 50 battery cycles my battery health is already at 90%.
Rocketing fans at nearly 100%
***
But if you force enable HiDPI mode (instructions later) for your external monitor while the lid is closed, this is what happens:
For demonstration purposes, when you look at “Scaled”, you get HiDPI options. When I actually use it, I use “Default for Display”
Code:% system_profiler SPDisplaysDataType | grep -C1 Resolution S32D850: Resolution: 5120 x 2880 (5K/UHD+) UI Looks like: 2560 x 1440 @ 60.00Hz
Now when I look at the GPU power draw, I see:
Source screenshot was 5120x2880, due to HiDPI.
What exactly is HiDPI mode? Well, it’s basically forcing macOS to internally render at 2x resolution. So in the case of a 2560x1440p monitor, macOS is internally rendering at 5120x2880p. (Which happens to be the resolution of the 27" iMac). You can tell, since the new screenshots are twice as sharp.
Now the MacBook is drawing a much more reasonable 6W and stays silent during normal operation, as it should! Now it feels like a Pro machine!
Seeing as how it makes no sense that rendering at 2x resolution cause 1/3 of the power draw, this is most likely a GPU driver bug on Apple or AMD’s end, and a temporary solution could be force enabling HiDPI mode for 1440p monitors in the next release of macOS.
Note, these power draw settings only work if you keep the MacBook lid closed.
Moreover, I noticed that my battery health stayed the same after 50 more cycles with this fix applied.
Basically silent fans
***
You can force enable HiDPI mode yourself. You'll need to use a 3rd party tool. The one I used (one-key-hidpi) looked like:
Code:_ _ _____ _____ _____ _____ | | | | |_ _| | __ \ | __ \ |_ _| | |__| | | | | | | | | |__) | | | | __ | | | | | | | | ___/ | | | | | | _| |_ | |__| | | | _| |_ |_| |_| |_____| |_____/ |_| |_____| ============================================ (1) Enable HIDPI (2) Enable HIDPI (with EDID) (3) Disable HIDPI Enter your choice [1~3]: 1 ------------------------------------- |********** Display Icon ***********| ------------------------------------- (1) iMac (2) MacBook (3) MacBook Pro (4) LG Display (5) Pro Display XDR (6) Do not change Enter your choice [1~6]: 6 ------------------------------------------ |********** resolution config ***********| ------------------------------------------ (1) 1920x1080 Display (2) 1920x1080 Display (use 1424x802, fix underscaled after sleep) (3) 1920x1200 Display (4) 2560x1440 Display (5) 3000x2000 Display (6) Manual input resolution Enter your choice: 4 Enabled, please reboot. Rebooting the logo for the first time will become huge, then it will not be
Please note, MacBooks can get pretty loud after restarting when plugged into monitors. Just wait a few minutes for the fans to ramp down. And once again, this fix only works when the MacBook lid is closed.
Also, don’t forget to set the resolution to “Default for display” in settings.
So welcome to having a silent MacBook when plugged into a monitor now! As it should be!
Footnote: in the first example, before running the script, selecting 1080p also reduces GPU usage to ~6W, but 1080p on a 1440p display looks terrible.
I love this Mantiz eGPU. Even has a 2.5" SSD slot. Sometimes I even get Windows Bootcamp to work. hahaAm I reading this right.....as I consider a EFPU for my MBP
EGPU support is only for Intel ?
Use an external graphics processor with your Mac - Apple Support
Learn how to access additional graphics performance by connecting to an external graphics processor.support.apple.com
So my next (M) chip MBP - the eGPU is a brick - depending on the next upgrade.
I am 80% there on getting a eGPU for this 16"
I have a MBP 16 w/ 5500m (maxed out i9 and 64GB RAM) and it's a piece of crap... even freshly booted and with nothing running plugging in a 1440 monitor causes the temp to skyrocket and the fans to go full speed.Hi,
I was about to open a new thread talking about how pissed I am with my MacBook Pro 16" 32 GB RAM. But I see my problem have been discussed here a lot.
I can't believe I can't use this expensive machine with my 32" 4K external display and Google Meet. As soon as I launch Google Meet, the computer becomes unusable.
This is what happens when I close the Google Meet window (pink arrow indicates when I turn off Meet):
View attachment 1806286
Things start to go back to normal.
So I guess since I'm stuck with the Radeon Pro 5300M, I only have 2 options:
1. Buy an eGPU (expensive and inconvenient)
2. Sell my MacBook and get another one with a 5500M
Is that right? Thanks!
Please read my post from above about 1440p fixes!1440 monitor causes the temp to skyrocket and the fans to go full speed
TLDR: My 2019 Macbook Pro 16" 5300M gets hot and noisy when connected to a 2560x1440p60 monitor, even when idle and the lid is closed. This post outlines a partial solution that enables silent operation.
The 2019 MacBook Pro 16" with base 5300M GPU has a problem.
If you connect models with this specific GPU to an external monitor with an extremely specific (but common) resolution, many users report that their MacBook gets really hot and the fans spin up really loudly, even if they close the screen lid.
Specifically, many users report extremely loud fans when connected to 2560x1440p60 monitors. The problem is with this specific resolution and 5300M GPU combination. Tons of users report no problems when using 1080p or 4K monitors or with the upgraded 5600M GPUs.
The solution to this problem, however, is just force enabling HiDPI mode for the monitor (instructions later). Unfortunately though, this solution requires the MacBook lid to be closed. I haven’t found any solution that fixes the problem while also keeping the lid open.
DISCLAIMER: This article only considers a 2019 MacBook Pro 16" on Big Sur 11.5.1 with 5300M graphics connected to a single external 32 inch 2560x1440p60 display. If you have a different setup, no guarantee this will work, since this issue might be a bug with exactly this GPU/resolution combination. I’ve seen many reports of no issues on the 5600M.
***
Before, when connected to a 32 inch 1440p monitor, my MacBook Pro 16 inch reports 18–20W of power draw from the GPU. This is regardless of whether or not the Macbook lid is closed.
Code:% system_profiler SPDisplaysDataType | grep -C1 Resolution S32D850: Resolution: 2560 x 1440 (QHD/WQHD) UI Looks like: 2560 x 1440 @ 60.00Hz
I switched to “Scaled” for demonstration purposes, but I typically just use “Default for Display”.
When I look at the GPU power draw, I see:
Source screenshot from the free Stats app was 2560x1440. The equivalent statistic on iStat Menus is Radeon High Side.
This is insane power draw for a laptop at idle. It doesn’t take long for all this extra power to heat up the laptop and cause the fans to start roaring, even with nothing running, just idle.
Moreover, I noticed that after 50 battery cycles my battery health is already at 90%.
Rocketing fans at nearly 100%
***
But if you force enable HiDPI mode (instructions later) for your external monitor while the lid is closed, this is what happens:
For demonstration purposes, when you look at “Scaled”, you get HiDPI options. When I actually use it, I use “Default for Display”
Code:% system_profiler SPDisplaysDataType | grep -C1 Resolution S32D850: Resolution: 5120 x 2880 (5K/UHD+) UI Looks like: 2560 x 1440 @ 60.00Hz
Now when I look at the GPU power draw, I see:
Source screenshot was 5120x2880, due to HiDPI.
What exactly is HiDPI mode? Well, it’s basically forcing macOS to internally render at 2x resolution. So in the case of a 2560x1440p monitor, macOS is internally rendering at 5120x2880p. (Which happens to be the resolution of the 27" iMac). You can tell, since the new screenshots are twice as sharp.
Now the MacBook is drawing a much more reasonable 6W and stays silent during normal operation, as it should! Now it feels like a Pro machine!
Seeing as how it makes no sense that rendering at 2x resolution cause 1/3 of the power draw, this is most likely a GPU driver bug on Apple or AMD’s end, and a temporary solution could be force enabling HiDPI mode for 1440p monitors in the next release of macOS.
Note, these power draw settings only work if you keep the MacBook lid closed.
Moreover, I noticed that my battery health stayed the same after 50 more cycles with this fix applied.
Basically silent fans
***
You can force enable HiDPI mode yourself. You'll need to use a 3rd party tool. The one I used (one-key-hidpi) looked like:
Code:_ _ _____ _____ _____ _____ | | | | |_ _| | __ \ | __ \ |_ _| | |__| | | | | | | | | |__) | | | | __ | | | | | | | | ___/ | | | | | | _| |_ | |__| | | | _| |_ |_| |_| |_____| |_____/ |_| |_____| ============================================ (1) Enable HIDPI (2) Enable HIDPI (with EDID) (3) Disable HIDPI Enter your choice [1~3]: 1 ------------------------------------- |********** Display Icon ***********| ------------------------------------- (1) iMac (2) MacBook (3) MacBook Pro (4) LG Display (5) Pro Display XDR (6) Do not change Enter your choice [1~6]: 6 ------------------------------------------ |********** resolution config ***********| ------------------------------------------ (1) 1920x1080 Display (2) 1920x1080 Display (use 1424x802, fix underscaled after sleep) (3) 1920x1200 Display (4) 2560x1440 Display (5) 3000x2000 Display (6) Manual input resolution Enter your choice: 4 Enabled, please reboot. Rebooting the logo for the first time will become huge, then it will not be
Please note, MacBooks can get pretty loud after restarting when plugged into monitors. Just wait a few minutes for the fans to ramp down. And once again, this fix only works when the MacBook lid is closed.
Also, don’t forget to set the resolution to “Default for display” in settings.
So welcome to having a silent MacBook when plugged into a monitor now! As it should be!
Footnote: in the first example, before running the script, selecting 1080p also reduces GPU usage to ~6W, but 1080p on a 1440p display looks terrible.
Thanks for that detailed breakdown... indeed I haven't had an issue when using the MBP in lid closed/ext. monitor... however I consider it a *major* defect that the system can't adequately deal with an external monitor (and I would say potentially legally actionable one... but that may be a bit of a stretch... certainly it's one Apple should be ashamed of if not admitting and doing something about). This has been on-going for many months and still I don't know of a peep from Apple about it.Please read my post from above about 1440p fixes!