External monitor support

[MK500]

Just FYI:

I just bought an A2119 to use with my M1 MacBook Air after finding my A1621 would only display 30hz on my 4K TV. I can confirm you need the A2119 to do 4K 60hz, and it works immediately at this resolution on the M1 Macs.

On my 1440p monitor either adapter can do 60hz.

The adapters look identical, but are not.

Apple Releases USB-C Digital AV Multiport Adapter with HDMI 2.0 Support

 

[joevt]

Just FYI:

I just bought an A2119 to use with my M1 MacBook Air after finding my A1621 would only display 30hz on my 4K TV. I can confirm you need the A2119 to do 4K 60hz, and it works immediately at this resolution on the M1 Macs.

On my 1440p monitor either adapter can do 60hz.

The adapters look identical, but are not.

Apple Releases USB-C Digital AV Multiport Adapter with HDMI 2.0 Support

View attachment 1694964

Mac mini: 4k @ 120hz?

That adapter only uses two lanes of DisplayPort 1.4 HBR3, so it must use chroma sub sampling (at least 4:2:2) to do HDR (10bpc) and it can't do 8bpc without chroma sub sampling (something HDMI 2.0 should be able to do). I don't know a method in macOS to tell if it's using 4:2:2 or 4:2:0. I...

forums.macrumors.com

 

[OCDMacGeek]

For those using DisplayLink, there is a new update, and the release notes specifically say M1 Macs are supported in some way.

Download: DisplayLink Manager Graphics Connectivity (1.2)

C.3 Changes in 1.2 release
----------------------------
- Introducing support for Mac using the Apple M1 chip
- Dual 5K Ultrawide (5120x1440 @ 60 Hz) displays now supported on DisplayLink DL-6950 products
- Create technical support requests directly from the application
- Improved stability and reliability
- Monitors light-up quicker after login (32264)
- Fixed stretched image on some monitors (32531)
- Monitor preferred mode is now selected first (32531)
- Added deployment setting option to simplify user startup experience (https://support.displaylink.com/knowledgebase/articles/1960495)
- Improved application architecture

I installed it, and while it may be a bit faster, it didn't affect my biggest issue -- the lack of some HiDPI scaling options with 4k displays. Right now I am using an LG 32UL950-W with a Dell D6000. It gives me most scaling options, but not 3008 x 1692. That is the one I would prefer. It will give me 1920x1080 (slightly big) and 3840x2160 (slightly small).

 

[VitoBotta]

For those using DisplayLink, there is a new update, and the release notes specifically say M1 Macs are supported in some way.

Download: DisplayLink Manager Graphics Connectivity (1.2)

I installed it, and while it may be a bit faster, it didn't affect my biggest issue -- the lack of some HiDPI scaling options with 4k displays. Right now I am using an LG 32UL950-W with a Dell D6000. It gives me most scaling options, but not 3008 x 1692. That is the one I would prefer. It will give me 1920x1080 (slightly big) and 3840x2160 (slightly small).

Does it show up as "Apple" or "Intel" in Activity Monitor? I have 1.2 installed but it still shows "Intel". Which build do you have? Mine is 55.125. Thanks

 

[Pressure]

The script I made to dump M1 Mac display timings is now at https://gist.github.com/joevt/0c75b42171b3fb1a5248b4e2bee8e4d0
Scroll down to the comments section to see how to download and run it.

I finally received my M1 Mac mini and hooked it up to the Dell UP3218K.

This is the output without removing the DisplayProductID-4147 file.

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)
    5120x2880@60.000Hz 0.000kHz 0.00MHz  h(48 32 80 +)  v(3 5 74 -)   (virtual)
    800x600@60.000Hz 0.000kHz 0.00MHz  h(40 128 88 +)  v(1 4 23 +)   (preferred)
    640x480@75.000Hz 0.000kHz 0.00MHz  h(16 64 120 -)  v(1 3 16 -) 
    640x480@60.000Hz 31.500kHz 25.20MHz  h(16 96 48 -)  v(10 2 33 -) 
    1280x1024@75.000Hz 0.000kHz 0.00MHz  h(16 144 248 +)  v(1 3 38 +) 
    1024x768@75.000Hz 0.000kHz 0.00MHz  h(16 96 176 +)  v(1 3 28 +) 
    1024x768@60.000Hz 0.000kHz 0.00MHz  h(24 136 160 -)  v(3 6 29 -) 
    800x600@75.000Hz 0.000kHz 0.00MHz  h(16 80 160 +)  v(1 3 21 +) 
    1280x800@60.000Hz 0.000kHz 0.00MHz  h(48 32 80 +)  v(3 6 14 -) 
    1680x1050@60.000Hz 0.000kHz 0.00MHz  h(48 32 80 +)  v(3 6 21 -) 
    1920x1200@60.000Hz 0.000kHz 0.00MHz  h(48 32 80 +)  v(3 6 26 -) 
    1600x1200@60.000Hz 0.000kHz 0.00MHz  h(64 192 304 +)  v(1 3 46 +) 
    1280x1024@60.000Hz 0.000kHz 0.00MHz  h(48 112 248 +)  v(1 3 38 +) 
    1920x1080@60.000Hz 67.500kHz 148.50MHz  h(88 44 148 +)  v(4 5 36 +)   (preferred)
-> 3840x2160@59.997Hz 133.312kHz 533.25MHz  h(48 32 80 +)  v(3 5 54 -)   (preferred)
    1920x1080@59.940Hz 67.433kHz 148.35MHz  h(88 44 148 +)  v(4 5 36 +)   (preferred)
    1920x1080@50.000Hz 56.250kHz 148.50MHz  h(528 44 148 +)  v(4 5 36 +)   (promoted)
    1920x1080@23.976Hz 26.973kHz 74.18MHz  h(638 44 148 +)  v(4 5 36 +)   (promoted)
    1920x1080@24.000Hz 27.000kHz 74.25MHz  h(638 44 148 +)  v(4 5 36 +)   (promoted)
    1280x720@59.940Hz 44.955kHz 74.18MHz  h(110 40 220 +)  v(5 5 20 +)   (promoted)
    1280x720@60.000Hz 45.000kHz 74.25MHz  h(110 40 220 +)  v(5 5 20 +)   (promoted)
    1280x720@50.000Hz 37.500kHz 74.25MHz  h(440 40 220 +)  v(5 5 20 +) 
    720x576@50.000Hz 31.250kHz 27.00MHz  h(12 64 68 -)  v(5 5 39 -) 
    720x480@59.940Hz 31.469kHz 27.00MHz  h(16 62 60 -)  v(9 6 30 -)   (promoted)
    720x480@60.000Hz 31.500kHz 27.03MHz  h(16 62 60 -)  v(9 6 30 -)   (promoted)
    640x480@59.940Hz 31.469kHz 25.17MHz  h(16 96 48 -)  v(10 2 33 -) 
    3840x2160@29.981Hz 65.688kHz 262.75MHz  h(48 32 80 +)  v(3 5 23 -)   (promoted)
    2560x1440@59.951Hz 88.787kHz 241.50MHz  h(48 32 80 +)  v(3 5 33 -) 
    2048x1080@59.990Hz 66.649kHz 147.16MHz  h(48 32 80 +)  v(3 10 18 -) 
    2048x1080@23.902Hz 26.268kHz 58.00MHz  h(48 32 80 +)  v(3 10 6 -) 
    3840x4320@48.000Hz 212.062kHz 856.73MHz  h(48 32 120 +)  v(3 10 85 -) 
    3840x4320@60.000Hz 262.079kHz 1058.80MHz  h(48 32 120 +)  v(3 10 35 -)

So nothing have changed with Big Sur with regards to this display.

Now to disable SIP with a bluetooth keyboard and delete the override file ...

 

[joevt]

I finally received my M1 Mac mini and hooked it up to the Dell UP3218K.

This is the output without removing the DisplayProductID-4147 file.

disp0:

dispext0:
    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)
    5120x2880@60.000Hz 0.000kHz 0.00MHz  h(48 32 80 +)  v(3 5 74 -)   (virtual)
-> 3840x2160@59.997Hz 133.312kHz 533.25MHz  h(48 32 80 +)  v(3 5 54 -)   (preferred)
    3840x2160@29.981Hz 65.688kHz 262.75MHz  h(48 32 80 +)  v(3 5 23 -)   (promoted)
    2560x1440@59.951Hz 88.787kHz 241.50MHz  h(48 32 80 +)  v(3 5 33 -) 
    2048x1080@59.990Hz 66.649kHz 147.16MHz  h(48 32 80 +)  v(3 10 18 -) 
    2048x1080@23.902Hz 26.268kHz 58.00MHz  h(48 32 80 +)  v(3 10 6 -) 
    3840x4320@48.000Hz 212.062kHz 856.73MHz  h(48 32 120 +)  v(3 10 85 -) 
    3840x4320@60.000Hz 262.079kHz 1058.80MHz  h(48 32 120 +)  v(3 10 35 -)

So nothing have changed with Big Sur with regards to this display.

Now to disable SIP with a bluetooth keyboard and delete the override file ...

At least we see the 3840x4320@60Hz half width mode.
Removing the override should expose the 7680x4320 30Hz single cable mode. Maybe it won't be allowed since it's greater than 6K.
The 7680x4320 60Hz dual cable mode (tiled) may also appear. Or you need an .mtdd file for that.
If you create a .mtdd file, maybe it could work. Or at least it will fail differently than it does on an Intel Mac since the graphics drivers are so different.

If you can't delete the override file, then maybe you can override the override file by placing an override in /Library/System/
You can tell when an override file is being used by putting a custom display name in the override file.

With Big Sur, you may need to disconnect/reconnect the display to get it to use the new override file since the SwitchResX "Activate Immediately" button doesn't work sometimes on Intel Macs and might not work at all on M1 Macs? I don't recall anyone mentioning if the button works on M1 Macs.

 

[Pressure]

At least we see the 3840x4320@60Hz half width mode.
Removing the override should expose the 7680x4320 30Hz single cable mode. Maybe it won't be allowed since it's greater than 6K.
The 7680x4320 60Hz dual cable mode (tiled) may also appear. Or you need an .mtdd file for that.
If you create a .mtdd file, maybe it could work. Or at least it will fail differently than it does on an Intel Mac since the graphics drivers are so different.

If you can't delete the override file, then maybe you can override the override file by placing an override in /Library/System/
You can tell when an override file is being used by putting a custom display name in the override file.

With Big Sur, you may need to disconnect/reconnect the display to get it to use the new override file since the SwitchResX "Activate Immediately" button doesn't work sometimes on Intel Macs and might not work at all on M1 Macs? I don't recall anyone mentioning if the button works on M1 Macs.

I'm facing the trouble that system files are now read only in Big Sur so I cannot delete the override file.

I have created the folders in /Library but not sure what I should put in the file?

I have goofed around with SwitchResX and can enable 3840x4320@60Hz (1920x2160 HiDPI).

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)
    5120x2880@60.000Hz 0.000kHz 0.00MHz  h(48 32 80 +)  v(3 5 74 -)   (virtual)
    800x600@60.000Hz 0.000kHz 0.00MHz  h(40 128 88 +)  v(1 4 23 +)   (preferred)
    640x480@75.000Hz 0.000kHz 0.00MHz  h(16 64 120 -)  v(1 3 16 -)  
    640x480@60.000Hz 31.500kHz 25.20MHz  h(16 96 48 -)  v(10 2 33 -)  
    1280x1024@75.000Hz 0.000kHz 0.00MHz  h(16 144 248 +)  v(1 3 38 +)  
    1024x768@75.000Hz 0.000kHz 0.00MHz  h(16 96 176 +)  v(1 3 28 +)  
    1024x768@60.000Hz 0.000kHz 0.00MHz  h(24 136 160 -)  v(3 6 29 -)  
    800x600@75.000Hz 0.000kHz 0.00MHz  h(16 80 160 +)  v(1 3 21 +)  
    1280x800@60.000Hz 0.000kHz 0.00MHz  h(48 32 80 +)  v(3 6 14 -)  
    1680x1050@60.000Hz 0.000kHz 0.00MHz  h(48 32 80 +)  v(3 6 21 -)  
    1920x1200@60.000Hz 0.000kHz 0.00MHz  h(48 32 80 +)  v(3 6 26 -)  
    1600x1200@60.000Hz 0.000kHz 0.00MHz  h(64 192 304 +)  v(1 3 46 +)  
    1280x1024@60.000Hz 0.000kHz 0.00MHz  h(48 112 248 +)  v(1 3 38 +)  
    1920x1080@60.000Hz 67.500kHz 148.50MHz  h(88 44 148 +)  v(4 5 36 +)   (preferred)
    3840x2160@59.997Hz 133.312kHz 533.25MHz  h(48 32 80 +)  v(3 5 54 -)   (preferred)
    1920x1080@59.940Hz 67.433kHz 148.35MHz  h(88 44 148 +)  v(4 5 36 +)   (preferred)
    1920x1080@50.000Hz 56.250kHz 148.50MHz  h(528 44 148 +)  v(4 5 36 +)   (promoted)
    1920x1080@23.976Hz 26.973kHz 74.18MHz  h(638 44 148 +)  v(4 5 36 +)   (promoted)
    1920x1080@24.000Hz 27.000kHz 74.25MHz  h(638 44 148 +)  v(4 5 36 +)   (promoted)
    1280x720@59.940Hz 44.955kHz 74.18MHz  h(110 40 220 +)  v(5 5 20 +)   (promoted)
    1280x720@60.000Hz 45.000kHz 74.25MHz  h(110 40 220 +)  v(5 5 20 +)   (promoted)
    1280x720@50.000Hz 37.500kHz 74.25MHz  h(440 40 220 +)  v(5 5 20 +)  
    720x576@50.000Hz 31.250kHz 27.00MHz  h(12 64 68 -)  v(5 5 39 -)  
    720x480@59.940Hz 31.469kHz 27.00MHz  h(16 62 60 -)  v(9 6 30 -)   (promoted)
    720x480@60.000Hz 31.500kHz 27.03MHz  h(16 62 60 -)  v(9 6 30 -)   (promoted)
    640x480@59.940Hz 31.469kHz 25.17MHz  h(16 96 48 -)  v(10 2 33 -)  
    3840x2160@29.981Hz 65.688kHz 262.75MHz  h(48 32 80 +)  v(3 5 23 -)   (promoted)
    2560x1440@59.951Hz 88.787kHz 241.50MHz  h(48 32 80 +)  v(3 5 33 -)  
    2048x1080@59.990Hz 66.649kHz 147.16MHz  h(48 32 80 +)  v(3 10 18 -)  
    2048x1080@23.902Hz 26.268kHz 58.00MHz  h(48 32 80 +)  v(3 10 6 -)  
    3840x4320@48.000Hz 212.062kHz 856.73MHz  h(48 32 120 +)  v(3 10 85 -)  
 -> 3840x4320@60.000Hz 262.079kHz 1058.80MHz  h(48 32 120 +)  v(3 10 35 -)

 

[joevt]

I'm facing the trouble that system files are now read only in Big Sur so I cannot delete the override file.

I have created the folders in /Library but not sure what I should put in the file?

I have goofed around with SwitchResX and can enable 3840x4320@60Hz (1920x2160 HiDPI).

All the timings are the same as before. You didn't actually change anything with SwitchResX? Next step is use SwitchResX to change the name of the display (click "Use custom display name system-wide, change the display name, type Command-S to save, reconnect display to see if the name changes in the Displays preferences panel). This will create a new override file in the /Library location (it will use year and date for the name instead of product ID). Examine it to make sure it doesn't have a EDID override or patches (the original EDID override has a patch to remove the 8K modes).

 

[Pressure]

All the timings are the same as before. You didn't actually change anything with SwitchResX? Next step is use SwitchResX to change the name of the display (click "Use custom display name system-wide, change the display name, type Command-S to save, reconnect display to see if the name changes in the Displays preferences panel). This will create a new override file in the /Library location (it will use year and date for the name instead of product ID). Examine it to make sure it doesn't have a EDID override or patches (the original EDID override has a patch to remove the 8K modes).

Yeah, I changed the name of the display with SwitchResX.

It created the necessary files under a new DisplayVendorID but it doesn't expose any resolutions above 3840 pixels horizontal.

I have contacted Apple for clarification both online through their chat support which escalated me to a "senior supervisor". Next they called me up and I talked to two different people who both were wondering why it would work in Windows through BootCamp but not in MacOS. The last one wrote the case down and sent it "through" (whatever that means) and asked me to use their Product Feedback and tell about the issues with the Dell UP3218K.

For now I would settle for 7680x4320@30Hz ... otherwise this Mac mini goes back.

Weird though that 3840x4320 @ 60Hz works.

 

[joevt]

It created the necessary files under a new DisplayVendorID but it doesn't expose any resolutions above 3840 pixels horizontal.

Can you post the file? Next step is try to get a 5K resolution to work (or at least be accepted into the list of current resolutions in SwitchResX as a non-scaled timing). And then 6K. And 8K. Use CVT-RB timing. When you use SwitchResX to add custom timings with width > 4096, SwitchResX will create a EDID override (in the override file) containing the new timings.
5120x2880@60Hz
6016x3384@45Hz
7680x4320@29.932Hz 130.742kHz 1030.25MHz h(30 10 160 +) v(3 5 40 -)

I have contacted Apple for clarification both online through their chat support which escalated me to a "senior supervisor". Next they called me up and I talked to two different people who both were wondering why it would work in Windows through BootCamp but not in MacOS. The last one wrote the case down and sent it "through" (whatever that means) and asked me to use their Product Feedback and tell about the issues with the Dell UP3218K.

You were talking to people that don't even know that Apple has purposefully removed 8K capability for the UP3218K with their override file.

Windows has drivers that properly supports dual cable displays and MST. macOS drivers are not as smart and only supports specific dual cable displays (e.g. LG UltraFine 5K, Dell UP2715K, iMac display, old 4K MST displays).

 

[Pressure]

Can you post the file? Next step is try to get a 5K resolution to work (or at least be accepted into the list of current resolutions in SwitchResX as a non-scaled timing). And then 6K. And 8K. Use CVT-RB timing. When you use SwitchResX to add custom timings with width > 4096, SwitchResX will create a EDID override (in the override file) containing the new timings.
5120x2880@60Hz
6016x3384@45Hz
7680x4320@29.932Hz 130.742kHz 1030.25MHz h(30 10 160 +) v(3 5 40 -)


You were talking to people that don't even know that Apple has purposefully removed 8K capability for the UP3218K with their override file.

Windows has drivers that properly supports dual cable displays and MST. macOS drivers are not as smart and only supports specific dual cable displays (e.g. LG UltraFine 5K, Dell UP2715K, iMac display, old 4K MST displays).

I made it very clear that the override file were blocking the native resolution of the display and its location both over the phone and with the chat support.

I have tried adding the custom resolutions with SwitchResX but nothing changes. It will simply not expose any resolutions above 3840 pixels horizontal. The display also keeps saying it's receiving a 2160p signal unless I pick the the 3840x4320 resolution (be it 1:1 or HiDPI). So I believe the original override file under system is still blocking something.

 

[joevt]

So I believe the original override file under system is still blocking something.

I don't recall anyone showing that anything other than the display name can be changed with the override. Well, maybe try some custom 4K timings. They should work since they are 4K or less. try 35Hz, 40Hz, etc. something unique that doesn't already exist in the current list of timings.

The file you posted has the product id. Is there another file in the same vendor folder with the week and year name? I think week/year takes precedence over product id. SwitchResX creates overrides with the week/year style of name. Did that change on the M1 Macs?

Also one thing I don't understand is when the vendor id for DEL changes from the proper value 0x10ac to 0x90ac (which is the same value with the hi bit set). Maybe make sure the folder is vendor 0x10ac - or put the same override in both the 10ac and 90ac folders to be sure (use a different name for each and see which one gets chosen).

 

[ojobson]

I have a few things to report for people wanting to try DisplayLink with their M1 device. I have a MacBook Pro M1 with 16 GB RAM.

I have a Pro Display XDR that looks great when driven by the MacBook (True Tone works). I have an Asus PQ321Q 4k display I would like to set up as a second display.

First, I tried this DisplayLink dock. It didn't work at all for me and my Asus PQ321Q 4k display, using DisplayPort or HDMI.

So, I then tried the Dell D6000. That one does work with my my Asus PQ321Q 4k display, when using the "default for display" resolution. Of course, that makes the text really small. Also, the mouse cursor lags a bit. When I try to scale it, my only scaled options drop the resolution substantially (unusable). I don't think I can use this setup unless I can scale it, and get rid of the lag. I need to do some research in the forums as it seems this is an issue with DisplayLink that may not be resolved.

I wonder if another 4k display would work better with DisplayLink and why that would be.

Another problem is that when a DisplayLink monitor is connected, the Pro Display XDR looks much worse. Its far less bright. This seems to be because once a DisplayLink monitor is connected, the settings change. Now the "Pro Display XDR (P3-1600 nits)" preset is gone and True Tone is also gone. I don't know if that explains why it drops some brightness and color.

So, the DisplayLink solution isn't working that great for me so far.

Displaylink launched new drivers for Big Sur on the 10th of December. Have you tried these with the D6000?

 

[ojobson]

Displaylink launched new drivers for Big Sur on the 10th of December. Has anyone tried these with Displaylink adapters like the D6000 or otherwise?

https://www.displaylink.com/downloads/macos

Sorry - think I messed up and posted twice, once as an attempted reply.

 

[Sanderr]

I am running the DisplayLink update with my StarTech dual DP 4K-60 adapter, and it's working well. Screen rotation for the DisplayLink screens is still not working however.

 

[OCDMacGeek]

Displaylink launched new drivers for Big Sur on the 10th of December. Has anyone tried these with Displaylink adapters like the D6000 or otherwise?

https://www.displaylink.com/downloads/macos

Sorry - think I messed up and posted twice, once as an attempted reply.

I have. I didn’t notice anything very much different in my case. I’ve had some kernel panics since then, but I also installed 11.1, so I don’t know what the cause of that really is.

 

[petterihiisila]

I have. I didn’t notice anything very much different in my case. I’ve had some kernel panics since then, but I also installed 11.1, so I don’t know what the cause of that really is.

I doubt it’s DisplayLink Manager, because as far as I can tell, it’s just an app, it doesn’t even come with a kernel driver/extension. In principle, regular apps are not able to bring down the whole system. At most, a regular app could trigger some lower level bug that already exists in macOS code.

(The 2019 legacy driver was a kernel extension but that’s for Catalina and earlier only.)

I’ve had my 11.1 M1 Air panic a few times while it was on the desk all by itself, lid closed and not charging. The panic log implied it had trouble with the sleep/wake choreography. And a few times I’ve seen a kernel panic related to APFS/NAS activity.

These don’t seem to be more or less frequent than with Catalina/MBP16, but I do hit Save and close important documents before closing the lid, just in case.

 

[snakes-]

I find out a strange behavior, i set my external display to 75hz but in clamshell mode i must do it again. lucky is that my system now runs without problems. i will test now more the sleep mode.

 

[joevt]

I would like to make a faster version of my ioreg.pl script. Can someone send the result of this command (zip the plist file):
ioreg -alr -k "display-timing-info" > ioreg_M1_displaytimings.plist

 

[saulinpa]

I would like to make a faster version of my ioreg.pl script. Can someone send the result of this command (zip the plist file):
ioreg -alr -k "display-timing-info" > ioreg_M1_displaytimings.plist

M1 mini with LG 5K UltraFine attached via TB3:

 

[joevt]

M1 mini with LG 5K UltraFine attached via TB3:

Thanks. I made a new script which should be much faster now. It is at https://gist.github.com/joevt/e862b0088ef58b9144877d01401bcee8

Run it like this:
bash M1MacTimings.sh

if you have an ioreg plist created by the ioreg -alr -k "display-timing-info" > ioreg_M1_displaytimings.plist command (for example, from someone else) then you can run the script like this:
bash M1MacTimings.sh ioreg_M1_displaytimings.plist

 

[saulinpa]

Something doesn't seem right with the mode detection. With the LG it always shows "->" next to 512x2880 regardless of resolution, including the "low resolution" modes. Could that be the way that the M1 deals with the LG? With an old DVI connectd monitor it stays on the "promoted" setting most of the time but does move to specific resolutions for a few of them (correlates with the monitor resyncing).

Attached when set to 2560 x 1440 (low resolution)

 

[joevt]

Something doesn't seem right with the mode detection. With the LG it always shows "->" next to 512x2880 regardless of resolution, including the "low resolution" modes. Could that be the way that the M1 deals with the LG? With an old DVI connectd monitor it stays on the "promoted" setting most of the time but does move to specific resolutions for a few of them (correlates with the monitor resyncing).

Attached when set to 2560 x 1440 (low resolution)

Did you try any of the non-virtual timings that don't have a corresponding virtual mode? These ones:

    4096x2304@59.999Hz 142.198kHz 593.82MHz  h(8 32 40 +)  v(1 8 57 -)   (preferred)
    3200x1800@59.999Hz 111.119kHz 364.47MHz  h(8 32 40 +)  v(1 8 43 -)  
    2560x2880@60.000Hz 177.720kHz 469.18MHz  h(8 32 40 +)  v(1 8 73 -)

For the first two, there may be a 2048x1152 and 1600x900 HiDPI mode - try those as well.

The "2560 x 1440 (low resolution)" mode is probably this virtual mode:
2560x1440@60.000Hz 0.000kHz 0.00MHz h(192 272 464 -) v(3 5 45 +) (virtual)
which is scaled up to the indicated 5K timing:
-> 5120x2880@60.000Hz 177.720kHz 938.36MHz h(16 64 80 +) v(1 8 73 -) (preferred) (tiled)
instead of the timing:
2560x1440@60.000Hz 88.860kHz 234.59MHz h(8 32 40 +) v(1 8 32 -)

Maybe we can learn something by comparing full ioreg with 5K display to full ioreg with not 5K display. There's still some mystery about the second DisplayPort connection to the 5K. I would like to know if there's any other indication in the ioreg (besides the (tiled) flag) of the second DisplayPort to Thunderbolt being used.
ioreg -filw0 > ioreg_M1_full_5K.txt
ioreg -filw0 > ioreg_M1_full_not_5K.txt

 

[saulinpa]

Did you try any of the non-virtual timings that don't have a corresponding virtual mode? These ones:

    4096x2304@59.999Hz 142.198kHz 593.82MHz  h(8 32 40 +)  v(1 8 57 -)   (preferred)
    3200x1800@59.999Hz 111.119kHz 364.47MHz  h(8 32 40 +)  v(1 8 43 -)
    2560x2880@60.000Hz 177.720kHz 469.18MHz  h(8 32 40 +)  v(1 8 73 -)

For the first two, there may be a 2048x1152 and 1600x900 HiDPI mode - try those as well.

The "2560 x 1440 (low resolution)" mode is probably this virtual mode:
2560x1440@60.000Hz 0.000kHz 0.00MHz h(192 272 464 -) v(3 5 45 +) (virtual)
which is scaled up to the indicated 5K timing:
-> 5120x2880@60.000Hz 177.720kHz 938.36MHz h(16 64 80 +) v(1 8 73 -) (preferred) (tiled)
instead of the timing:
2560x1440@60.000Hz 88.860kHz 234.59MHz h(8 32 40 +) v(1 8 32 -)

Maybe we can learn something by comparing full ioreg with 5K display to full ioreg with not 5K display. There's still some mystery about the second DisplayPort connection to the 5K. I would like to know if there's any other indication in the ioreg (besides the (tiled) flag) of the second DisplayPort to Thunderbolt being used.
ioreg -filw0 > ioreg_M1_full_5K.txt
ioreg -filw0 > ioreg_M1_full_not_5K.txt

I didn't try those modes as they did not show as options in the regular display resolutions, even with the show low resolution modes checked. Using SwitchResX they are available but got the same results with the first two. With the last one (2560x2880) the display went dark. Used screen sharing to run your script did show it though with the ->.

I went through all of the resolutions showing in SwitchResX and most showed 5120x2880. Tried 1280x1440 HiDPI and shows ->2560x2880, both 1920x1080 HiDPI and 3840x2160 shows ->3840x2160. 640x480 shows ->640x480

 

[joevt]

I didn't try those modes as they did not show as options in the regular display resolutions, even with the show low resolution modes checked. Using SwitchResX they are available but got the same results with the first two. With the last one (2560x2880) the display went dark. Used screen sharing to run your script did show it though with the ->.

I went through all of the resolutions showing in SwitchResX and most showed 5120x2880. Tried 1280x1440 HiDPI and shows ->2560x2880, both 1920x1080 HiDPI and 3840x2160 shows ->3840x2160. 640x480 shows ->640x480

Seems like it's working semi-reasonably then except for some minor things:
1) why does 2560x2880 cause dark display but 1280x1440 HiDPI does not? Or did it?

I compared your 5K with not 5K (4K) output and only found these differences:

5K has the following:
    - a second AppleDCPDPTXHDCP1Controller and a second AppleDCPDPTXHDCP2Controller
    - higher PerformanceStatistics for AGXAcceleratorG13G_B0 (Device Utilization is 61% instead of 11%)

Did you use the same 5K display with Thunderbolt connection for both? The comparison I would like to see is 5K connection (LG UltraFine 5K using Thunderbolt or similar - like you have already done) and single DisplayPort connection (like LG UltraFine 4K or LG UltraFine 5K with USB-C to DisplayPort bidirectional cable with USB-C to DisplayPort adapter).