Attached is the complete output ofYes, HDMI would be interesting as well. HDMI EDID is usually much different than DisplayPort EDID.
AGDCDiagnose -a
with the MateView hooked up via HDMI to the RX 460. Sorry for the delay.Attached is the complete output ofYes, HDMI would be interesting as well. HDMI EDID is usually much different than DisplayPort EDID.
AGDCDiagnose -a
with the MateView hooked up via HDMI to the RX 460. Sorry for the delay.It's running full rez at 50Hz.Attached is the complete output ofAGDCDiagnose -a
with the MateView hooked up via HDMI to the RX 460. Sorry for the delay.
Interestingly, the HDMI EDID doesn’t have the 2560×1440 60Hz or 3840×2560 30Hz modes the DisplayPort one has, but adds 3600×2400 30Hz.It's running full rez at 50Hz.
There you go - two external 4K60 monitors (confirmed by their OSD) on the iMacApple tech specs say that iMac can only connect one external display.
Strange that you couldn't connect the Dell directly to the iMac even though it can handle two 4K60 displays. Were you using one DisplayPort connection per Thunderbolt 2 port? I used to have a 2015 MacBook Pro that could connect the Dell but that had a discrete AMD for external displays.There you go - two external 4K60 monitors (confirmed by their OSD) on the iMac
@eyoungren - I'm gaining on youActually, that is six monitors. One of them is so high-rez (5120×2880) that it requires two separate connections from the graphics card, with each driving one half (2560×2880) of the monitor. macOS combines the halves so they appear as a single monitor.
Yes. Maybe the physical height of 2880 pixels is a problem? I just connected the MateView to the Iris and it came up at 6720×3780 (scaled) at 30 Hz. 3840×2560 wasn't listed at all in RetinaDisplayMenu or the Displays preference pane - the highest 3:2 resolution available was 3000×2000, at 60 Hz. However'sWere you using one DisplayPort connection per Thunderbolt 2 port?
AGDCDiagnose
's output contained this - so does this mean it was physically running 3840×2560 at 30 Hz? (The monitor's OSD doesn't list the current mode, argh...)HW State @ 0 DICT 5
Source Window 3840 x 2560
Destination Window 3840 x 2560
Scaling Taps 1 x 1
Line Buffer Depth 4 - 30 bpp
Interlaced No
SW State @ 0 DICT 5
Source Window 3840 x 2560
Destination Window 3840 x 2560
Scaling Taps 1 x 1
Line Buffer Depth 4 - 30 bpp
Interlaced No
I stopped at six.@eyoungren - I'm gaining on youActually, that is six monitors. One of them is so high-rez (5120×2880) that it requires two separate connections from the graphics card, with each driving one half (2560×2880) of the monitor. macOS combines the halves so they appear as a single monitor.
View attachment 1850674
I use three (four if you count that dual-cable monster as two). That suits me fine, and I think I'd be hard-pressed to come up with a use for another for the stuff I do right now. On the other hand, there was a time when I tried two monitors and couldn't make sense of it so...I stopped at six.
Your previous AGDCDiagnose outputs did not include any Intel GPU detail so I don't know what you're looking at there without the rest of the file.Yes. Maybe the physical height of 2880 pixels is a problem? I just connected the MateView to the Iris and it came up at 6720×3780 (scaled) at 30 Hz. 3840×2560 wasn't listed at all in RetinaDisplayMenu or the Displays preference pane - the highest 3:2 resolution available was 3000×2000, at 60 Hz. However'sAGDCDiagnose
's output contained this - so does this mean it was physically running 3840×2560 at 30 Hz? (The monitor's OSD doesn't list the current mode, argh...)
Code:HW State @ 0 DICT 5 Source Window 3840 x 2560 Destination Window 3840 x 2560 Scaling Taps 1 x 1 Line Buffer Depth 4 - 30 bpp Interlaced No SW State @ 0 DICT 5 Source Window 3840 x 2560 Destination Window 3840 x 2560 Scaling Taps 1 x 1 Line Buffer Depth 4 - 30 bpp Interlaced No
My wife used to think two monitors were ridiculous and that I was just being extreme. Then she went back to school for her teacher's degree and school is different now. She had to get up to speed with computers and the internet and on and on.I use three (four if you count that dual-cable monster as two). That suits me fine, and I think I'd be hard-pressed to come up with a use for another for the stuff I do right now. On the other hand, there was a time when I tried two monitors and couldn't make sense of it so...
Sorry. I've attached the full output with the MateView hooked up to the Iris.Your previous AGDCDiagnose outputs did not include any Intel GPU detail so I don't know what you're looking at there without the rest of the file.
We've seen that 605 MHz works on the iMac's internal display. But 594 MHz does not work on an external display.maybe the Iris has a limit on max pixel clock?
I'm not sure what the LineBuffers info signifies. I suppose you could see what differs when you disconnect the MateView. I'm pretty sure it's only AMD info. Maybe it could be stuff on the MateView (connected with Intel GPU) that is accelerated by the AMD?Sorry. I've attached the full output with the MateView hooked up to the Iris.
Doesn't look like it. I would look at the timing info shown by SwitchResX (when you double click the current resolution to see the pixel clock, active pixels, scale pixels, and other info).@joevt - Does anything inAGDCDiagnose
's output indicate that the Iris is driving the MateView at 3840×2560?
Just did:I would look at the timing info shown by SwitchResX
AGDCDiagnose
=> EDIDUtil.sh
) attached.great results!One can do this on an early intel Mac.![]()
Well…not exactly sure what's going on with the drive. It won't boot. Get's stuck at opendirectory "too many corpses". Tried a solution, didn't work, so now I'm just moving the Mac on to Catalina.
Not stressed. This Mac is non-critical and has sat off for the past several months so no biggie. And it gets updated to Catalina.
Found this inside though…
View attachment 1852699
60GB SATA 3 SSD. Was not expecting that.
No, good thought, but the drive was actually booting. It just got stuck at a certain point. And Recovery sees the drive just fine.Possibly a long shot, but might this be a situation of the Mac mini having a SATA I bus (as memory serves, didn’t Apple move everything to SATA III at around the same time they moved to iX-series CPUs?) and an SSD whose controller doesn’t auto-detect a pre-SATA-III bus and set its speed to that slower/earlier protocol?
M.b. it's woth to look in direction to OpenCore?again, dosdude hack
Say hello to 201160GB SATA 3 SSD.
2011 Macs gained SATA III along with Sandy Bridge.didn’t Apple move everything to SATA III at around the same time they moved to iX-series CPUs?)