I've now tried some CVT modes:
Seems like a VRAM limit. Instead of counting pixels, you need to count bytes. It's probably 4 bytes per pixel. It may be that each row needs to have extra pixels for hardware cursor data (I remember that from built-in video of Power Mac 8600 but newer GPUs probably do it differently). Or maybe each row needs to be a multiple of 16 bytes or some power of 2. I think AllRez might show rowBytes for each mode. Also you should verify that timings are allowed to have width with the least 4 significant bits set to an arbitrary value. For example, take the 2048x4096 mode which works, and try widths 2032 ... 2047.
There was a setting to make macOS create scaled modes for all timings that have the base resolution but I think that might be for 10.14.6 and above. The setting can be changed by selecting the "Show all refresh rates for scaled resolutions" option in SwitchResX.
I wonder if there's some processing happening to the pixels (frame buffer pixel conversion or transformation) which takes some resource (time or heat) from the GPU so that the more pixels there are, the lower the max pixel clock.
Testing the UP2715K, I can't seem to get 5K working in Windows 10 with Maxwell and it doesn't show a 6bpc mode in Nvidia Control Panel (but there's a 4:2:2 and 4:4:4 option - no 4:2:0 since this is DisplayPort 1.2). I'll try Radeon card to make sure the display is still working.
Yosemite is an interesting release, it has the new UI, yet keeps the good version of Disk Utility, uses the short-lived Helvetica Neue and best yet, doesn't have SIP!
You can install later versions of OS X/macOS on that 2009 MBP. Just sayin'
Yeah, that's a good point, and I only mentioned it just in case. I find Yosemite to be a bit of an odd release too (disclaimer: I'm a huge fan of Mavericks) but as long as it works for you there's nothing wrong with sticking with it.
IMHO it's not just a question of affordability. I don't "lightheartedly" spend money on a new machine just to run a new(er) OS and applications anymore when the current one is still perfectly adequate. I no longer feel the thrill of "upgrading because I can!".
I stuck to Mojave on my main system but have recently run across several applications I needed that would no longer install on it, so am now dual-booting Monterey (I thought I might as well use the last officially supported version for best application support etc.) with it.
On 10.9.5, widths 2032, 2033, ..., 2047, 2048 all work at a height of 4096.
I've attached AllRez output from 10.15.7 including a 3712×2400 mode (3713×2400 was also present but is rejected and not listed in the output). As far as I can read and understand the output, rowBytes is 14848 for that mode (?).
Yup, that option is not there in 10.9.5, but it is in 12.6.3.
I'll give that a try.
It's interesting that the 4850 does >360 MHz via HBR without (apparently) going down to 6bpc since I don't see any obvious colour banding in wallpapers (I do see it at 5bpc framebuffer depth at least).
Thanks for testing. I was wondering since Maxwell can handle the pixel clock required for non-tiled 5K60 but is limited to HBR2.
Yeah, that's alright. I reset my MBA 2014 back to Yosemite because I am looking to sell it. So far, no takers. I bet Yosemite runs amazing on it, though, since it's the default that it came with (or seems to have came with, I think this was a late year release). Yosemite is alright, from what I have experienced of it, but yeah, the system fonts are a bit weird, specially coming from SL or Mojave/Big Sur, but you get used to it.
That mean the width doesn't need to be a multiple of pixels.
If you print all the rowBytes as hex, then you can see that they are all a multiple of 512 bytes. If you calculate row bytes for 3712 you see that it is 0x3a00. When you go to 3713, it is 0x3c00. Multiplying rowbytes by number of lines gives the size in bytes of the frame buffer. The maximum size of the frame buffer is in the range [33.984375 MiB .. 33.99853515625 MiB). If you want a greater size, then you'll have to look into some Intel GPU FrameBuffer mods. See WhateverGreen and Hackintool to learn about Intel FrameBuffer info.
vram () {
local res="$1"
local w="${res%×*}"
local h="${res#*×}"
local rowbytes=$((($w * 4 + 0x1ff) / 0x200 * 0x200))
printf "%d %04x $2 %d×%d %x×%x\n" $((rowbytes * $h)) $rowbytes $w $h $w $h
}
{
# 10.9.5
vram 4095×2174 √
vram 4095×2175 √ # (but bottom line of pixels shows anomalies)
vram 4095×2176 x
vram 4094×2174 √
vram 4094×2175 √
vram 4094×2176 x
vram 3840×2320 √
vram 3840×2322 x
vram 3840×2324 x
vram 3840×2400 x
vram 3840×2560 x
vram 3600×2400 √
vram 3603×2402 x
vram 3606×2404 x
vram 3456×2560 √
vram 3458×2560 x
vram 3072×2880 √
vram 3073×2880 x
vram 2560×3384 √
vram 2561×3384 x
vram 2048×4096 √
vram 2049×4096 x
# 10.15.7
vram 2032×4096 x
vram 2048×4096 x
vram 2049×4096 x
vram 3600×2400 √
vram 3600×2401 x
vram 3600×2402 x
vram 3600×2404 x
vram 3700×2400 √
vram 3712×2400 √
vram 3713×2400 x
vram 3714×2400 x
vram 3716×2400 x
vram 3718×2400 x
vram 3720×2400 x
vram 3840×2320 √
vram 3840×2322 x
} | sort
33554432 2000 x 2032×4096 7f0×1000
33554432 2000 x 2048×4096 800×1000
33554432 2000 √ 2048×4096 800×1000
34652160 2800 √ 2560×3384 a00×d38
35389440 3000 √ 3072×2880 c00×b40
35389440 3600 √ 3456×2560 d80×a00
35618816 4000 √ 4094×2174 ffe×87e
35618816 4000 √ 4095×2174 fff×87e
35635200 3a00 √ 3600×2400 e10×960
35635200 3a00 √ 3600×2400 e10×960
35635200 3a00 √ 3700×2400 e74×960
35635200 3a00 √ 3712×2400 e80×960
35635200 3c00 √ 3840×2320 f00×910
35635200 3c00 √ 3840×2320 f00×910
35635200 4000 √ 4094×2175 ffe×87f
35635200 4000 √ 4095×2175 fff×87f
35650048 3a00 x 3600×2401 e10×961
35651584 2200 x 2049×4096 801×1000
35651584 2200 x 2049×4096 801×1000
35651584 4000 x 4094×2176 ffe×880
35651584 4000 x 4095×2176 fff×880
35664896 3a00 x 3600×2402 e10×962
35664896 3a00 x 3603×2402 e13×962
35665920 3c00 x 3840×2322 f00×912
35665920 3c00 x 3840×2322 f00×912
35694592 3a00 x 3600×2404 e10×964
35694592 3a00 x 3606×2404 e16×964
35696640 3c00 x 3840×2324 f00×914
36384768 2a00 x 2561×3384 a01×d38
36700160 3800 x 3458×2560 d82×a00
36864000 3200 x 3073×2880 c01×b40
36864000 3c00 x 3713×2400 e81×960
36864000 3c00 x 3714×2400 e82×960
36864000 3c00 x 3716×2400 e84×960
36864000 3c00 x 3718×2400 e86×960
36864000 3c00 x 3720×2400 e88×960
36864000 3c00 x 3840×2400 f00×960
39321600 3c00 x 3840×2560 f00×a00A Lilu or WhateverGreen patch to make macOS add scaled modes for all base resolution refresh rates would be complicated - I don't think it would be just modifying a few bytes. You would need to inject an entire subroutine's worth of code. I'm not sure how to do that.
Maybe AllRez can get more info from the Radeon HD 4850. I'm still working on it. I have it working in 10.6 and 10.4. I am working on 10.5. It should be pretty quick after this.
I'm not sure if the UP2715K has a single tile 5K60 (6bpc) mode or a 5K30 mode. I should test with Navi or Pascal.
Thanks for the detailed info and the pointers.
I did some more testing on 10.15.7. Height is limited to 2400 regardless of width (like on the Iris Pro 6200). A width of 4096 works.
It works.
Once it's ready for release, I'll be happy to try it on my DisplayPort-equipped 10.6 Macs. Tests using CVT timings have lifted the 4850's pixel clock limit to 425.7 MHz.
I think we've found that it does not. What about the Acer XV273K? Can it handle these?
Ok, so the problem in 10.15.7 is not with aspect ratio (since you can do 1000x2400). The problem is with vertical height > 2400 which 10.9.5 had no problem with.
That's not significantly more than the 425.600MHz that you reported before so I'm not sure why you're reporting 425.7 now.
Scaled modes may be limited by VRAM or aspect ratio or by the scaling amount.
I think the Acer XV273K can handle anything up to 8K30 single tile. I think it only does the 4K144 for dual tile mode (requires Windows / PC). I haven't tested recently.
Did you try 10.9 (Mavericks) in the middle? I expect you'll get much better performance than Yosemite (albeit not quite as good as Snow Leopard) alongside much better app compatibility than Snow Leopard.
The best CPUs you can put in are a pair of X5365s. They are each quad-core chips at 3GHz, so together you'd get 8 cores running at 3.0GHz. Not bad. You will also have to patch the firmware with the 2,1 version.
It's the best midpoint right now for looks/speed and modern apps. You get the old Aqua design, but with slightly less linen, and a much better chance of modern apps running.I'm eager to know what's the source of your admiration.
Perhaps there are benefits which I can put to use.
Go, go, go get 'em.I've just checked eBay and there's a number of pairs for sale from Chinese vendors. Thanks.
According to this thread, only Firefox 78 ESR and iCab 5.9.2 run on Mavericks, but don't on older versions.Such as browsers?
SLAED is the recommended G0 stepping.
AGDCDiagnose revealed it uses two lanes of HBR so up to 180 MHz pixel clock at 8bpc RGB is theoretically possible.* 3: kAGDCPortCapability is not supported on the current platform
[DP 1.1 2 x HBR ] Status: [2 x HBR 77 0] caps [features 0x0, p_encoding 0x0] DVI/HDMI Branch OUI:000-028-248 161AB3 [049-054-049-065-066-051] HW Version: 0 FW Version: 149.24