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

raknor

macrumors regular
Sep 11, 2020
136
150
There is no such thing as 8 lanes of DisplayPort. Max lanes is 4, even when using Thunderbolt.

Look at the iMac 5K display or LG 5K display with the AGDCDiagnose command on an intel Mac. It shows two 4 lane connections of HBR2 (DisplayPort 1.2) just like it does for a Dell UP2715K or a HP Z27q. Doesn't matter if they go through Thunderbolt or not. The DisplayPort connections are separate.

Look at the iMac 5K display or LG 5K display with the AGDCDiagnose command on an intel Mac. It shows two 4 lane connections of HBR2 (DisplayPort 1.2) just like it does for a Dell UP2715K or a HP Z27q. Doesn't matter if they go through Thunderbolt or not. The DisplayPort connections are separate.
Yes they are. Two 4 lanes encoded into thunderbolt stream i.e 8 lanes of display port traffic on the link. I didn’t say they are all 8 lanes going to the same sink. The display has two sinks and traffic from both of them a total of 8 lanes is tunnelthrough thunderbolt.

I agree that the DisplayPort connections may occur at different times or appear in a different order or have tile info specified in the EDID in a different way, but Apple has handled these issues ever since they added support for multi tiled-displays a long time ago.

The M1 doesn’t seem to have the same display resources like those systems in the last. Intel is capable of 3 displays so when one is taken up for built-in the other two are bonded together for tiled displays. That’s why you get 2 displays or one tiled display. AMD GPUs support more displays that’s why the 16” model can support more but tiled displays will alway reduce the total number of displays by and extra one. I don’t see why Apple would restrict things to one display if there were more resources to support more displays like the Intel or AMD GPUs.

The M1 doesn’t support 3 displays so ergo it it doing some thing to share one display resowith tiled displays. How apple handled things in the past doesn’t really matter.

They mention these same displays in their support documents (have to find them on the wayback machine now). For example, with the Dell or HP display, I can connect either cable, then connect the other cable any time later to get 5K.

For M1 Macs? I couldn’t find it in the support documents.
The order and timing do not matter. The system gets the EDID for one connection, then when it gets the EDID of the other connection, it can see that all tiles are connected, then create the single spanning frame buffer.

Yes on intel Macs. We are not talking about intel Macs.
This flaky behaviour we're seeing on M1 Macs is a regression in functionality caused by a change of the graphics system (it's using iPhone graphics instead of Mac graphics) and Apple's inadequate testing.

Not if Apple never claimed to support two cable tiled displays. I’d like to see the support document that says M1 Macs support two displays or two cable tiled displays. Also it has nothing to do with graphics, the display engine on all GPUs/SoC is different blocks on silicon. The M1 SoC has 7-8 core GPUs vs 4 on iPhone. I have no idea what Mac graphics means in this context when it clearly outclasses most integrated GPUs on Macs or even PCs.
 
Last edited:

joevt

macrumors 604
Jun 21, 2012
6,963
4,257
Yes they are. Two 4 lanes encoded into thunderbolt stream i.e 8 lanes of display port traffic on the link. I didn’t say they are all 8 lanes going to the same sink. The display has two sinks and traffic from both of them a total of 8 lanes is tunnelthrough thunderbolt.
The LG UltraFine 5K display is connected exactly the same as a dual cable display connected to a Thunderbolt 3 to dual DisplayPort adapter. In either case, the two DisplayPort connections are tunnelled through Thunderbolt.

I don’t see why Apple would restrict things to one display if there were more resources to support more displays like the Intel or AMD GPUs.

The M1 doesn’t support 3 displays so ergo it it doing some thing to share one display resowith tiled displays.
Right. The M1 has two DisplayPort connections for Thunderbolt, but some restriction makes Apple allow only one display, either single or dual tile display.

How apple handled things in the past doesn’t really matter.
It kind of does. In the past it worked. A user of past machines expects it to continue working for the present machine. It works, but only after you do a magic dance.

For M1 Macs? I couldn’t find it in the support documents.
I said wayback machine. It's a website that archives webpages. The pages I refer to predate the M1 Macs.
Here's the old page from Nov 23, 2019:

This page mentions dual link SST (which is what LG UltraFine 5K and the dual cable displays are):

Yes on intel Macs. We are not talking about intel Macs.
We are talking about tiled displays. It is the nature of tiled displays that the order of connection and the timing of connection is not deterministic. Apple cannot depend on connection order or connection timing to support tiled displays, whether the display has a built-in Thunderbolt controller like the LG UltraFine 5K, or uses an external Thunderbolt controller like the Dell UP2715K or HP Z27q connected to a Thunderbolt 3 dock or a Thunderbolt 3 to Dual DisplayPort adapter.

Not if Apple never claimed to support two cable tiled displays. I’d like to see the support document that says M1 Macs support two displays or two cable tiled displays. Also it has nothing to do with graphics, the display engine on all GPUs/SoC is different blocks on silicon. The M1 SoC has 7-8 core GPUs vs 4 on iPhone. I have no idea what Mac graphics means in this context when it clearly outclasses most integrated GPUs on Macs or even PCs.
All M1 Macs support two displays. I think you mean M1 Macs don't support two displays from Thunderbolt - we agree on that.

I think the Apple Store page is the only page that says the M1 Macs are compatible with the LG UltraFine 5K display. It doesn't say if the display support 4K or 5K in that case. Apple usually doesn't mention compatibility about third party displays, except in that past support article, and except for the LG displays that it sells. Usually displays that are similar should have similar compatibility (they follow the same standards and specifications - DisplayPort, EDID, etc; the purpose of such standards is to allow compatibility). The Dell and HP displays, when connected through a Thunderbolt 3 dock or adapter, are similar to the LG UltraFine 5K and therefore work as the LG UltraFine 5K does (but may require jumping through some hoops).

Mac graphics means all the software that Macs used to handle displays.
- CoreDisplay, AGDC, IOGraphicsDevice:IOFramebuffer, IODisplay:AppleDisplay, ?

iPhone graphics means all the software+hardware that iOS devices use to handle displays.
- IOMobileFramebuffer:IOMobileFramebufferService:IOMobileFramebufferAP:UnifiedPipeline2:AppleCLCD2 ?
 

raknor

macrumors regular
Sep 11, 2020
136
150
The LG UltraFine 5K display is connected exactly the same as a dual cable display connected to a Thunderbolt 3 to dual DisplayPort adapter. In either case, the two DisplayPort connections are tunnelled through Thunderbolt.
That’s still not the same. Displays that use a single thunderbolt cable have firmware that manage when the tiles come online the thunderbolt adapter doesn’t.
It kind of does. In the past it worked. A user of past machines expects it to continue working for the present machine. It works, but only after you do a magic dance.
In the past two <=4K displays + Internal worked too that doesn’t mean anything. When the spec says one display and doesn’t explicitly say it is supported. Past performance is not a guarantee for future results.

I said wayback machine. It's a website that archives webpages. The pages I refer to predate the M1 Macs.
Here's the old page from Nov 23, 2019:

This page mentions dual link SST (which is what LG UltraFine 5K and the dual cable displays are):
So still no on the documented support for M1 macs then? Also Apple never officially supported the Dell and HP display one anything other than iMac and Mac Pro as listed in your first link, none of the MacBooks or Mac Mini are listed and only the LG UltraFine is supported on them. So the fact that it worked means nothing to be honest and doesn't guarantee compatibility will be maintained when it was never officially listed as supported.

Dual-cable displays​

Some displays with resolutions higher than 4K require two DisplayPort cables to connect the display at full resolution:
  • The Dell UP2715K 27-inch 5K display is supported by iMac (Retina 5K, 27-inch, Late 2014) and later and Mac Pro (Late 2013) running OS X Yosemite 10.10.3 and later.
  • The HP Z27q 5K display is supported by iMac (Retina 5K, 27-inch, Late 2014) and later and Mac Pro (Late 2013) running macOS Sierra.
divider.png

LG UltraFine Displays​

The LG UltraFine 5K Display is supported on these Mac computers with Thunderbolt 3 (USB-C):
  • iMac (21.5-inch, 2017)
  • iMac (Retina 4K, 21.5-inch, 2017)
  • iMac (Retina 5K, 27-inch, 2017)
  • iMac Pro (2017)
  • Mac mini (2018)
  • MacBook Air (Retina, 13-inch, 2018)
  • MacBook Pro (2016 and later)

Dell is also very specific about what systems and cards support the dual cable 5K display. So using Display Port and EDID means nothing for compatibility.


We are talking about tiled displays. It is the nature of tiled displays that the order of connection and the timing of connection is not deterministic.

Wrong again. Displays like the LG 5K have firmware that can sequence when the tiles come online in a deterministic manner. The fact that LG pushes FW upgrades for bug fixes should clue you in.

The individual tiles have display port lanes going into the thunderbolt controller on the display when the display powers up the FW sequences the main tile to power on first and generates the hot plug for the main link into the the Thunderbolt controller and then the second tile. The Host on the other end always sees the main tile come online first and reads the EDID and the DisplayID block. Then when the second tile comes on line it can combine the displays.

It is trivial for the display FW to implement this in a deterministic manner because both lanes will always be plumbed when the display is connected via thunderbolt.

Apple cannot depend on connection order or connection timing to support tiled displays, whether the display has a built-in Thunderbolt controller like the LG UltraFine 5K, or uses an external Thunderbolt controller like the Dell UP2715K or HP Z27q connected to a Thunderbolt 3 dock or a Thunderbolt 3 to Dual DisplayPort adapter.

Wrong.. as I explained above.

All M1 Macs support two displays. I think you mean M1 Macs don't support two displays from Thunderbolt - we agree on that.

Yes.

I think the Apple Store page is the only page that says the M1 Macs are compatible with the LG UltraFine 5K display. It doesn't say if the display support 4K or 5K in that case. Apple usually doesn't mention compatibility about third party displays, except in that past support article, and except for the LG displays that it sells. Usually displays that are similar should have similar compatibility (they follow the same standards and specifications - DisplayPort, EDID, etc; the purpose of such standards is to allow compatibility). The Dell and HP displays, when connected through a Thunderbolt 3 dock or adapter, are similar to the LG UltraFine 5K and therefore work as the LG UltraFine 5K does (but may require jumping through some hoops).

The Dell dual cable display is not similar. Show me where the Display Port standard spec talks about tiled displays. Tiled displays were a hack until HBR3 was widely supported that's why there are so few of them out there. The Dell and HP first generation displays were a bigger hack than the LG5K.

DisplayID EDIDs have tile info but topology discovery is out of scope and Display Port doesn't talk about topology discovery other than MST and the tiled displays are not MST.

So which spec garaunteed compatibility of these things?

The LG 5K is apple special with stated MacOS compatibility, so Apple probably went to great lengths to make it work on M1 but that shouldn't automatically mean the Dell and HP gen one dual cable displays, which they never sold will also work unless explicitly specified.

Mac graphics means all the software that Macs used to handle displays.

- CoreDisplay, AGDC, IOGraphicsDevice:IOFramebuffer, IODisplay:AppleDisplay, ?

iPhone graphics means all the software+hardware that iOS devices use to handle displays.
- IOMobileFramebuffer:IOMobileFramebufferService:IOMobileFramebufferAP:UnifiedPipeline2:AppleCLCD2 ?

That's just a software driver and layering choice and means nothing. The M1 is a Apple designed chip. It makes sense that Apple leverages their SW stack for their silicon instead of one designed to support AMD and Intel GPUs and Displays. For all we know the Apple SoCs have dedicated hardware and FW that handle a lot of things the Intel mac did in SW for this stuff. So claiming they are iPhone graphics as some derogatory term is pretty silly to be honest.
 
Last edited:

joevt

macrumors 604
Jun 21, 2012
6,963
4,257
That’s still not the same. Displays that use a single thunderbolt cable have firmware that manage when the tiles come online the thunderbolt adapter doesn’t.

Displays like the LG 5K have firmware that can sequence when the tiles come online in a deterministic manner. The fact that LG pushes FW upgrades for bug fixes should clue you in.

The individual tiles have display port lanes going into the thunderbolt controller on the display when the display powers up the FW sequences the main tile to power on first and generates the hot plug for the main link into the the Thunderbolt controller and then the second tile. The Host on the other end always sees the main tile come online first and reads the EDID and the DisplayID block. Then when the second tile comes on line it can combine the displays.

It is trivial for the display FW to implement this in a deterministic manner because both lanes will always be plumbed when the display is connected via thunderbolt.
Why depend on firmware like that when the system can work much more reliably without it and with a much greater range of displays?

In the past two <=4K displays + Internal worked too that doesn’t mean anything. When the spec says one display and doesn’t explicitly say it is supported. Past performance is not a guarantee for future results.

The LG 5K is apple special with stated MacOS compatibility, so Apple probably went to great lengths to make it work on M1 but that shouldn't automatically mean the Dell and HP gen one dual cable displays, which they never sold will also work unless explicitly specified.
You are saying it's ok for Apple to not support any displays except the XDR and LG UltraFine 4K and LG UltraFine 5K because they don't say they support any other displays. If you're a lawyer then that's fine. If you're a user then maybe less so.

Dell is also very specific about what systems and cards support the dual cable 5K display. So using Display Port and EDID means nothing for compatibility.
Dell and Apple aren't going to update all their docs for every new computer and display that comes out.

Show me where the Display Port standard spec talks about tiled displays. Tiled displays were a hack until HBR3 was widely supported that's why there are so few of them out there. The Dell and HP first generation displays were a bigger hack than the LG5K.
And yet tiled displays still exist even in the days of DisplayPort 1.3 (HBR3) and DisplayPort 1.4 (HDR + DSC). The Dell UP3218K, Acer XV273K, Apple Pro Display XDR, iMac 5K, and LG UltraFine 5K for example. Given your description of the LG UltraFine 5K, with the super special firmware, I say the LG5K is the bigger hack.

DisplayID EDIDs have tile info but topology discovery is out of scope and Display Port doesn't talk about topology discovery other than MST and the tiled displays are not MST.
Topology discovery for tiled displays doesn't need more description than what is in the DisplayID spec. All the needed information is in the EDID. It's up to the driver developers to come up with an algorithm that works - something like: if the system sees a display with tile info, and the other tiles haven't appeared yet, then either output a signal or do nothing until the other tiles appear. Apple failed that in the M1 Mac. Windows handles tiled displays just fine.

That's just a software driver and layering choice and means nothing. The M1 is a Apple designed chip. It makes sense that Apple leverages their SW stack for their silicon instead of one designed to support AMD and Intel GPUs and Displays. For all we know the Apple SoCs have dedicated hardware and FW that handle a lot of things the Intel mac did in SW for this stuff. So claiming they are iPhone graphics as some derogatory term is pretty silly to be honest.
I did not say there was anything wrong with the iPhone graphics (maybe iOS graphics is a better term?). Only that it was different. The drivers need more work to match the capabilities of previous Macs. For example, software that supported brightness control using DDC/CI on Intel Macs needs to be rewritten for M1 Macs (if a DDC/CI interface is still exposed somewhere - I assume if the system can get EDID then DDC/CI should be possible).
 

petterihiisila

macrumors 6502
Nov 7, 2010
404
304
Finland
Only the frame buffer size is shown in System Information > Graphics/Displays. It says 5120 x 2880 but it could be outputting something else, like 4K.
The ioreg will show the current output resolution.

ioreg output is huge, and I couldn't grep out the truth from there, other than multiple mentions of "5120" embedded into all kinds of entries.

However, I can set the resolution to native (non-hiDPI) 5120x2880 with RDM.app. It is definitely showing all 5k pixels, familiar to the eye all the way back from late 2014 iMac 5k. Full screen shot inspection results in 5120x2880, and zooming into pixels in Preview, it's no doubt 5k down there.

Second gen LG 5k direct connect to M1 Air, no dongles. It would be quite controversial if it wouldn't work as the only monitor sans dongles, since the M1 is mentioned without any asterisks as a compatible device in the LG5k product page at Apple.com.

Planning to connect more displays next week with a Targus DisplayLink dock.
 

joevt

macrumors 604
Jun 21, 2012
6,963
4,257
ioreg output is huge, and I couldn't grep out the truth from there, other than multiple mentions of "5120" embedded into all kinds of entries.

However, I can set the resolution to native (non-hiDPI) 5120x2880 with RDM.app. It is definitely showing all 5k pixels, familiar to the eye all the way back from late 2014 iMac 5k. Full screen shot inspection results in 5120x2880, and zooming into pixels in Preview, it's no doubt 5k down there.

Second gen LG 5k direct connect to M1 Air, no dongles. It would be quite controversial if it wouldn't work as the only monitor sans dongles, since the M1 is mentioned without any asterisks as a compatible device in the LG5k product page at Apple.com.

Planning to connect more displays next week with a Targus DisplayLink dock.
I created a perl script to parse the ioreg.
- It treats the ioreg as a flat list of nodes (doesn't have code to group child nodes but we don't need that to get a list of screen resolutions).
- It can convert ioreg output to json with minor modifications (mostly - need handling of data type properties that are output by ioreg as strings).
- Slow - takes three minutes to parse an ioreg, or 30 seconds just for the display info.
- Doesn't handle name collisions (but for this the names are unique for the parts we are looking for).

You run it like this:
ioreg -firw0 -k TimingElements | perl -0777 ~/Downloads/ioreg.pl

The output will look something like this (this is with an XDR display connected to a M1 MacBook Air):
Code:
disp0:
    2560x1600@60.00 (preferred)

dispext0:
    640x480@60.00 (virtual)
    800x600@60.00 (virtual)
    1024x768@60.00 (virtual)
    1280x720@60.00 (virtual)
    1280x768@60.00 (virtual)
    1280x1024@60.00 (virtual)
    1400x1050@60.00 (virtual)
    1680x1050@60.00 (virtual)
    1600x1200@60.00 (virtual)
    1920x1080@60.00 (virtual)
    1920x1200@60.00 (virtual)
    2048x1536@60.00 (virtual)
    2560x1440@60.00 (virtual)
    2560x1600@60.00 (virtual)
    3840x2160@60.00 (virtual)
    4096x2160@60.00 (virtual)
    5120x2160@60.00 (virtual)
    5120x2880@60.00 (virtual)
    3840x2160@60.00 (preferred)
    3840x2160@50.00 (promoted)
    2560x1440@60.00
    3840x2160@59.94 (promoted)
    3840x2160@48.00 (promoted)
    3840x2160@47.95 (promoted)
    2560x2880@60.00
    2560x2880@59.94
    2560x2880@50.00
    2560x2880@48.00
    2560x2880@47.95
    5120x2880@60.00
    5120x2880@59.94
    5120x2880@50.00
    5120x2880@48.00
    5120x2880@47.95
 -> 6016x3384@60.00 (preferred)
    6016x3384@59.94 (promoted)
    6016x3384@50.00 (promoted)
    6016x3384@48.00 (promoted)
    6016x3384@47.95 (promoted)
    5120x2880@60.00 (preferred) (tiled)
    5120x2880@59.94 (promoted) (tiled)
    5120x2880@50.00 (promoted) (tiled)
    5120x2880@48.00 (promoted) (tiled)
    5120x2880@47.95 (promoted) (tiled)

If there's an issue then post a compressed copy of the output generated by the following command:
ioreg -firw0 -k TimingElements > ioreg_M1_timingelements.txt

EDIT: removed ioreg.pl attachment. Get it at https://gist.github.com/joevt/0c75b42171b3fb1a5248b4e2bee8e4d0
 
Last edited:
  • Like
Reactions: Amethyst1 and zoltm

petterihiisila

macrumors 6502
Nov 7, 2010
404
304
Finland
The output will look something like this
Nice script, that was a lot of work. I don't do much Perl anymore, but did check that you're not trying to pwn us :rolleyes:

2nd gen LG 5k attached directly on an M1 Air:

Code:
640x480@60.00 (virtual)
    800x600@60.00 (virtual)
    1024x768@60.00 (virtual)
    1280x720@60.00 (virtual)
    1280x768@60.00 (virtual)
    1280x1024@60.00 (virtual)
    1400x1050@60.00 (virtual)
    1680x1050@60.00 (virtual)
    1600x1200@60.00 (virtual)
    1920x1080@60.00 (virtual)
    1920x1200@60.00 (virtual)
    2048x1536@60.00 (virtual)
    2560x1440@60.00 (virtual)
    2560x1600@60.00 (virtual)
    3840x2160@60.00 (virtual)
    4096x2160@60.00 (virtual)
    5120x2160@60.00 (virtual)
    640x480@60.00
    3840x2160@60.00 (preferred)
    2560x1440@60.00
    3200x1800@60.00
    2560x2880@60.00
 -> 5120x2880@60.00 (preferred) (tiled)
 

joevt

macrumors 604
Jun 21, 2012
6,963
4,257
Nice script, that was a lot of work. I don't do much Perl anymore, but did check that you're not trying to pwn us :rolleyes:

2nd gen LG 5k attached directly on an M1 Air:

Code:
640x480@60.00 (virtual)
    800x600@60.00 (virtual)
    1024x768@60.00 (virtual)
    1280x720@60.00 (virtual)
    1280x768@60.00 (virtual)
    1280x1024@60.00 (virtual)
    1400x1050@60.00 (virtual)
    1680x1050@60.00 (virtual)
    1600x1200@60.00 (virtual)
    1920x1080@60.00 (virtual)
    1920x1200@60.00 (virtual)
    2048x1536@60.00 (virtual)
    2560x1440@60.00 (virtual)
    2560x1600@60.00 (virtual)
    3840x2160@60.00 (virtual)
    4096x2160@60.00 (virtual)
    5120x2160@60.00 (virtual)
    640x480@60.00
    3840x2160@60.00 (preferred)
    2560x1440@60.00
    3200x1800@60.00
    2560x2880@60.00
 -> 5120x2880@60.00 (preferred) (tiled)
Did the disp0 and dispext0 names not appear? If not then let me know what the following gives:
ioreg -firw0 -k TimingElements > ioreg_M1_timingelements.txt
 

petterihiisila

macrumors 6502
Nov 7, 2010
404
304
Finland
Did the disp0 and dispext0 names not appear? If not then let me know what the following gives:
ioreg -firw0 -k TimingElements > ioreg_M1_timingelements.txt

I'm running the 5k in clamshell mode, if that makes a difference. Here's the output of the above. Not sure what question you're trying to answer, but hope this helps :)
 

Attachments

  • ioreg_M1_timingelements.txt.zip
    5.7 KB · Views: 149

joevt

macrumors 604
Jun 21, 2012
6,963
4,257
I'm running the 5k in clamshell mode, if that makes a difference. Here's the output of the above. Not sure what question you're trying to answer, but hope this helps :)
Oh, I see what I did wrong. The following command will produce the result I was looking for (I want the root to be disp0 or dispext0, not AppleCLCD2, so that you can see what the display is connected to).

ioreg -firw0 -k "display-timing-info" | perl -0777 ~/Downloads/ioreg.pl
 

petterihiisila

macrumors 6502
Nov 7, 2010
404
304
Finland
Oh, I see what I did wrong. The following command will produce the result I was looking for (I want the root to be disp0 or dispext0, not AppleCLCD2, so that you can see what the display is connected to).

ioreg -firw0 -k "display-timing-info" | perl -0777 ~/Downloads/ioreg.pl

Sorry, close but no cigar...

Code:
disp0:


dispext0:
 

joevt

macrumors 604
Jun 21, 2012
6,963
4,257
Sorry, close but no cigar...

Code:
disp0:


dispext0:
This is kind of hard to do without an M1 Mac... Well, at least this time the names appeared. What does the following produce?
ioreg -firw0 -k "display-timing-info" > ioreg_M1_displaytiminginfo.txt

Otherwise, this should work:
{ ioreg -firw0 -n "disp0"; ioreg -firw0 -n "dispext0" } | perl -0777 ~/Downloads/ioreg.pl

And if that doesn't work, then I guess I need to look at the output of this:
{ ioreg -firw0 -n "disp0"; ioreg -firw0 -n "dispext0" } > ioreg_M1_disp0_dispexp.txt
 

petterihiisila

macrumors 6502
Nov 7, 2010
404
304
Finland
This is kind of hard to do without an M1 Mac... Well, at least this time the names appeared. What does the following produce?
ioreg -firw0 -k "display-timing-info" > ioreg_M1_displaytiminginfo.txt

Otherwise, this should work:
{ ioreg -firw0 -n "disp0"; ioreg -firw0 -n "dispext0" } | perl -0777 ~/Downloads/ioreg.pl

And if that doesn't work, then I guess I need to look at the output of this:
{ ioreg -firw0 -n "disp0"; ioreg -firw0 -n "dispext0" } > ioreg_M1_disp0_dispexp.txt

Here are the outputs. A short text snippet and two zip files.

Code:
disp0:


dispext0:
 

Attachments

  • ioreg_M1_disp0_dispexp.txt.zip
    1.8 KB · Views: 116
  • ioreg_M1_displaytiminginfo.txt.zip
    1.8 KB · Views: 147

petterihiisila

macrumors 6502
Nov 7, 2010
404
304
Finland
Oops. I forgot a flag:
ioreg -filrw0 -k "display-timing-info" | perl -0777 ~/Downloads/ioreg.pl

Output:

Code:
disp0:


dispext0:
    640x480@60.00 (virtual)
    800x600@60.00 (virtual)
    1024x768@60.00 (virtual)
    1280x720@60.00 (virtual)
    1280x768@60.00 (virtual)
    1280x1024@60.00 (virtual)
    1400x1050@60.00 (virtual)
    1680x1050@60.00 (virtual)
    1600x1200@60.00 (virtual)
    1920x1080@60.00 (virtual)
    1920x1200@60.00 (virtual)
    2048x1536@60.00 (virtual)
    2560x1440@60.00 (virtual)
    2560x1600@60.00 (virtual)
    3840x2160@60.00 (virtual)
    4096x2160@60.00 (virtual)
    5120x2160@60.00 (virtual)
    640x480@60.00
    3840x2160@60.00 (preferred)
    2560x1440@60.00
    3200x1800@60.00
    2560x2880@60.00
 -> 5120x2880@60.00 (preferred) (tiled)
 

joevt

macrumors 604
Jun 21, 2012
6,963
4,257
Output:

Code:
disp0:


dispext0:
    640x480@60.00 (virtual)
    800x600@60.00 (virtual)
    1024x768@60.00 (virtual)
    1280x720@60.00 (virtual)
    1280x768@60.00 (virtual)
    1280x1024@60.00 (virtual)
    1400x1050@60.00 (virtual)
    1680x1050@60.00 (virtual)
    1600x1200@60.00 (virtual)
    1920x1080@60.00 (virtual)
    1920x1200@60.00 (virtual)
    2048x1536@60.00 (virtual)
    2560x1440@60.00 (virtual)
    2560x1600@60.00 (virtual)
    3840x2160@60.00 (virtual)
    4096x2160@60.00 (virtual)
    5120x2160@60.00 (virtual)
    640x480@60.00
    3840x2160@60.00 (preferred)
    2560x1440@60.00
    3200x1800@60.00
    2560x2880@60.00
 -> 5120x2880@60.00 (preferred) (tiled)
I think that looks correct now. If you weren't in clamshell mode, then you would see something for disp0.
 
  • Like
Reactions: petterihiisila

fabdub

macrumors newbie
Nov 6, 2020
28
11
Hi!

I used to "force" HiDPI with this command on my Intel Air:

Code:
sudo defaults write /Library/Preferences/com.apple.windowserver.plist DisplayResolutionEnabled -bool true

I did that on my new Air and it doesn't activate anything .. if I read the string it is there, but no result!



This also outputs nothing (it does on intel mac)

Code:
ioreg -lw0 | grep -i "IODisplayEDID"

Yes I have tried running it after disable SIP ... Help would be appreciated.
 

petterihiisila

macrumors 6502
Nov 7, 2010
404
304
Finland
Hi!

I used to "force" HiDPI with this command on my Intel Air:

Code:
sudo defaults write /Library/Preferences/com.apple.windowserver.plist DisplayResolutionEnabled -bool true

I did that on my new Air and it doesn't activate anything .. if I read the string it is there, but no result!



This also outputs nothing (it does on intel mac)

Code:
ioreg -lw0 | grep -i "IODisplayEDID"

Yes I have tried running it after disable SIP ... Help would be appreciated.

What resolution are you trying to achieve, and with what kind of monitor and connection?

I've got a pair of 24" 2560x1440 displays and clicking Option-Scaled in the resolution preference panel provides well-balanced and anti-aliased scaled resolutions without further tweaking. The result looks sharper than the monitor actually is. Is any of those good?

I used this script once to enable HiDPI, can't remember the exact setup anymore. But I do remember that it worked. Changing these overrides is getting trickier by the year, as Apple is actively preventing any tampering of the system files.

On the M1 that wasn't necessary. LG 5k TB3 runs in all resolutions that it supports, and the Display-Linked two Lenovo WQHDs offer usable resolutions through "option-Scaled" + HDMI. Feeling lucky for once.
 

fabdub

macrumors newbie
Nov 6, 2020
28
11
What resolution are you trying to achieve, and with what kind of monitor and connection?

I've got a pair of 24" 2560x1440 displays and clicking Option-Scaled in the resolution preference panel provides well-balanced and anti-aliased scaled resolutions without further tweaking. The result looks sharper than the monitor actually is. Is any of those good?

I used this script once to enable HiDPI, can't remember the exact setup anymore. But I do remember that it worked. Changing these overrides is getting trickier by the year, as Apple is actively preventing any tampering of the system files.

On the M1 that wasn't necessary. LG 5k TB3 runs in all resolutions that it supports, and the Display-Linked two Lenovo WQHDs offer usable resolutions through "option-Scaled" + HDMI. Feeling lucky for once.
Actually I did some more research and yeah I am not the only one with the problem ... even the dev of the script you linked to says for now he has no solution, see in issues of one-key-hipid
EDID not read in Big Sur M1 Macbook Pro
 

Fair Witness

macrumors member
Dec 21, 2006
37
12
Austin, Texas
Oops. I forgot a flag:
ioreg -filrw0 -k "display-timing-info" | perl -0777 ~/Downloads/ioreg.pl

Here's the output from a Dell UP2715K connected to an M1 Air (after doing the rotation trick):

Code:
disp0:

dispext0:
    640x480@60.00 (virtual)
    800x600@60.00 (virtual)
    1024x768@60.00 (virtual)
    1280x720@60.00 (virtual)
    1280x768@60.00 (virtual)
    1280x1024@60.00 (virtual)
    1400x1050@60.00 (virtual)
    1680x1050@60.00 (virtual)
    1600x1200@60.00 (virtual)
    1920x1080@60.00 (virtual)
    1920x1200@60.00 (virtual)
    2048x1536@60.00 (virtual)
    2560x1440@60.00 (virtual)
    2560x1600@60.00 (virtual)
    3840x2160@60.00 (virtual)
    4096x2160@60.00 (virtual)
    5120x2160@60.00 (virtual)
    848x480@59.74 (preferred)
    2560x2880@29.99
    2560x2880@59.98
    5120x2880@29.99 (promoted) (tiled)
 -> 5120x2880@59.98 (promoted) (tiled)
 
  • Like
Reactions: joevt

joevt

macrumors 604
Jun 21, 2012
6,963
4,257
Here's the output from a Dell UP2715K connected to an M1 Air (after doing the rotation trick):

Code:
disp0:

dispext0:
    640x480@60.00 (virtual)
    800x600@60.00 (virtual)
    1024x768@60.00 (virtual)
    1280x720@60.00 (virtual)
    1280x768@60.00 (virtual)
    1280x1024@60.00 (virtual)
    1400x1050@60.00 (virtual)
    1680x1050@60.00 (virtual)
    1600x1200@60.00 (virtual)
    1920x1080@60.00 (virtual)
    1920x1200@60.00 (virtual)
    2048x1536@60.00 (virtual)
    2560x1440@60.00 (virtual)
    2560x1600@60.00 (virtual)
    3840x2160@60.00 (virtual)
    4096x2160@60.00 (virtual)
    5120x2160@60.00 (virtual)
    848x480@59.74 (preferred)
    2560x2880@29.99
    2560x2880@59.98
    5120x2880@29.99 (promoted) (tiled)
 -> 5120x2880@59.98 (promoted) (tiled)
Seems that only the info from the left tile EDID is included in that list. The info for the right tile EDID has more timings. You are missing these:

3840x2160@59.997Hz 133.313kHz 533.25MHz h(48 32 80 +) v(3 5 54 -) 16:9 preferred
3840x2160@59.997Hz 133.313kHz 533.25MHz h(80 32 48 -) v(54 5 3 -)
2560x1440@59.951Hz 88.787kHz 241.50MHz h(48 32 80 +) v(3 5 33 -)

I'm not sure why the two 4K timings have the front and back vertical porch opposite each other.

I made a new ioreg.pl script at https://gist.github.com/joevt/0c75b42171b3fb1a5248b4e2bee8e4d0
It will output more info about the timings. Follow the instructions to download and run.
 

Fair Witness

macrumors member
Dec 21, 2006
37
12
Austin, Texas
Seems that only the info from the left tile EDID is included in that list. The info for the right tile EDID has more timings. You are missing these:

3840x2160@59.997Hz 133.313kHz 533.25MHz h(48 32 80 +) v(3 5 54 -) 16:9 preferred
3840x2160@59.997Hz 133.313kHz 533.25MHz h(80 32 48 -) v(54 5 3 -)
2560x1440@59.951Hz 88.787kHz 241.50MHz h(48 32 80 +) v(3 5 33 -)

I'm not sure why the two 4K timings have the front and back vertical porch opposite each other.

I made a new ioreg.pl script at https://gist.github.com/joevt/0c75b42171b3fb1a5248b4e2bee8e4d0
It will output more info about the timings. Follow the instructions to download and run.

Ok, I ran the updated script on the Dell UP2715K:

Code:
disp0:

dispext0:
    640x480@60.000Hz 0.000kHz 0.00MHz  h(16 64 80 -)  v(3 4 13 +)   (virtual)
    800x600@60.000Hz 0.000kHz 0.00MHz  h(32 80 112 -)  v(3 4 17 +)   (virtual)
    1024x768@60.000Hz 0.000kHz 0.00MHz  h(48 104 152 -)  v(3 4 23 +)   (virtual)
    1280x720@60.000Hz 0.000kHz 0.00MHz  h(64 128 192 -)  v(3 5 20 +)   (virtual)
    1280x768@60.000Hz 0.000kHz 0.00MHz  h(64 128 192 -)  v(3 7 20 +)   (virtual)
    1280x1024@60.000Hz 0.000kHz 0.00MHz  h(80 136 216 -)  v(3 7 29 +)   (virtual)
    1400x1050@60.000Hz 0.000kHz 0.00MHz  h(88 144 232 -)  v(3 4 32 +)   (virtual)
    1680x1050@60.000Hz 0.000kHz 0.00MHz  h(104 176 280 -)  v(3 6 30 +)   (virtual)
    1600x1200@60.000Hz 0.000kHz 0.00MHz  h(112 168 280 -)  v(3 4 38 +)   (virtual)
    1920x1080@60.000Hz 0.000kHz 0.00MHz  h(128 200 328 -)  v(3 5 32 +)   (virtual)
    1920x1200@60.000Hz 0.000kHz 0.00MHz  h(136 200 336 -)  v(3 6 36 +)   (virtual)
    2048x1536@60.000Hz 0.000kHz 0.00MHz  h(152 224 376 -)  v(3 4 49 +)   (virtual)
    2560x1440@60.000Hz 0.000kHz 0.00MHz  h(192 272 464 -)  v(3 5 45 +)   (virtual)
    2560x1600@60.000Hz 0.000kHz 0.00MHz  h(192 280 472 -)  v(3 6 49 +)   (virtual)
    3840x2160@60.000Hz 0.000kHz 0.00MHz  h(312 424 736 -)  v(3 5 69 +)   (virtual)
    4096x2160@60.000Hz 0.000kHz 0.00MHz  h(8 32 40 +)  v(48 8 6 -)   (virtual)
    5120x2160@60.000Hz 0.000kHz 0.00MHz  h(8 32 40 +)  v(48 8 6 -)   (virtual)
    848x480@59.745Hz 29.514kHz 29.75MHz  h(48 32 80 +)  v(3 5 6 -)   (preferred)
    2560x2880@29.987Hz 87.592kHz 238.25MHz  h(48 32 80 +)  v(3 10 28 -) 
    2560x2880@59.982Hz 177.665kHz 483.25MHz  h(48 32 80 +)  v(3 10 69 -) 
    5120x2880@29.987Hz 87.592kHz 476.50MHz  h(96 64 160 +)  v(3 10 28 -)   (promoted) (tiled)
 -> 5120x2880@59.982Hz 177.665kHz 966.50MHz  h(96 64 160 +)  v(3 10 69 -)   (promoted) (tiled)
 
  • Like
Reactions: joevt

joevt

macrumors 604
Jun 21, 2012
6,963
4,257
In the other M1 display thread, I've read that people are finding that the LG UltraFine 5K is better supported in the macOS Big Sur beta. Maybe these fixes will help the Dell UP2715K?
 

matyst

macrumors newbie
May 17, 2012
9
122
Thanks for this thread - I currently have UP2715K connected to MacPro 2013 and considering a swap to M1 Mini.

Has anyone succeeded in using UP2715K with M1 Mini ?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.