Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.

Marco4957

macrumors newbie
Jun 22, 2020
5
28
IMG_0002.jpeg


Got it running on a late 2011 13" MacBook Pro even the magic trackpad works. Although as predicted HW accel isn't present neither is Wifi.
 

Nikita Razinkov

macrumors newbie
Jun 22, 2020
11
17
macOS 11.0 beta has acceleration on Mid 2012 13" Macbook Pro, only thing not working is wifi (should be a simple fix) View attachment 926227
I don't get it, there's no reason for Apple to drop support for these older machines when Big Sur runs just fine and does not demand anything that the hardware can't handle.
I get why they dropped support for open GL but if this works and meets the requirements of Big Sur (technically speaking), then what's the point unnecessarily dropping support for machines that work just fine.
 

vinaypundith

macrumors member
Apr 10, 2020
76
48
I have a Mid 2010 White Macbook and am willing to participate in testing.
When will the patcher become available?
@Marco4957 how did you get it installed? Is the patcher available?
Eager to try it out!
 
  • Like
Reactions: TimothyR734

toru173

macrumors 6502
Apr 5, 2007
332
154
Hey! I figured out kext loading and got the nVidia Tesla framebuffer (including brightness and sleep) working. The annoying part is it doesn't work in single-user mode since kmutil has to talk to some daemon...

Code:
sudo mount -uw /
# copy in the kexts as usual, unchanged from Catalina
chown -R root:wheel /System/Library/Extensions
chmod -R 755 /System/Library/Extensions
sudo kmutil install --update-all # other than this command, it's basically the same
sudo kcditto

Now time to work on real acceleration.

Good work! Is it worth pulling apart kmutil to find it’s dependencies? That way we can launchctl load them.

Edit: spelling!
 
Last edited:

ian87w

macrumors G3
Feb 22, 2020
8,704
12,638
Indonesia
Seems like 2012 Macs are dropped, and I believe many are still using those. Ka-ching? :D
This is why I dislike Apple computers. Arbitrary dropping off from OS support despite the device itself is still perfectly capable. In contrast, Windows 10 is able to be installed even on old machines.

Downside of switching to ARM, now there's no Windows option to extend the life of these older Macs (unless Microsoft announced Windows 10 ARM will support Apple silicon). Just like an iPhone, when Apple dropped your computer from support, that's it. It seems acceptable for phones, but for laptops and desktops, seems unreasonable. Most people don't need the latest performance, with even 10 year old computers still sufficient for many.
 

Barry K. Nathan

macrumors 6502
Jul 6, 2018
387
1,145
Irvine, CA, USA
AVX2 is not required for macOS 11 because the Ivy Bridge CPU of the still supported 2013 Mac Pro doesn't have it.
I've been thinking about whether the 2013 Mac Pro's Ivy Bridge CPU might be different from the others in some way... and it turns out, it is! CVE-2020-0543 (SRBDS) affects most Ivy Bridge CPUs, but not the Xeon E5 series used by the 2013 Mac Pro. For this CVE, Intel provided microcode updates for Haswell and later, but not Ivy Bridge.

Perhaps Apple doesn't want to officially support Macs that have Intel CPU flaws which (more or less) cannot be mitigated. For all I know (since I'm not a lawyer), this could be some legally driven thing. By the way, this would also explain why Apple decided not to officially support Catalina on the 2012 Mac Pro. In that case, the vulnerability was Microarchitectural Data Sampling (MDS).

This still doesn't explain the Late 2013 iMacs, but with that one exception, Apple's choice of models they're supporting in Big Sur now appears to me to be logically consistent and not arbitrary. The goal seems to me to be: avoid supporting Mac models with known unmitigated Intel CPU flaws in any new macOS release. (I almost wrote "support all Macs without known unmitigated Intel CPU flaws as of the OS's release date" but in reality it's probably a little more complicated than that, even if that is basically the result in the end.)
 

redking31591

macrumors 6502
Jul 10, 2008
393
62
I've been thinking about whether the 2013 Mac Pro's Ivy Bridge CPU might be different from the others in some way... and it turns out, it is! CVE-2020-0543 (SRBDS) affects most Ivy Bridge CPUs, but not the Xeon E5 series used by the 2013 Mac Pro. For this CVE, Intel provided microcode updates for Haswell and later, but not Ivy Bridge.

Perhaps Apple doesn't want to officially support Macs that have Intel CPU flaws which (more or less) cannot be mitigated. For all I know (since I'm not a lawyer), this could be some legally driven thing. By the way, this would also explain why Apple decided not to officially support Catalina on the 2012 Mac Pro. In that case, the vulnerability was Microarchitectural Data Sampling (MDS).

This still doesn't explain the Late 2013 iMacs, but with that one exception, Apple's choice of models they're supporting in Big Sur now appears to me to be logically consistent and not arbitrary. The goal seems to me to be: avoid supporting Mac models with known unmitigated Intel CPU flaws in any new macOS release. (I almost wrote "support all Macs without known unmitigated Intel CPU flaws as of the OS's release date" but in reality it's probably a little more complicated than that, even if that is basically the result in the end.)

Leaving out the one model, the 2013 iMac, also has some prior precedent. When Apple announced Handoff, it required a 2012 or forward Mac with Bluetooth 4.0. The 2011 MacBook Air and Mac mini both shipped with BT 4.0 and when someone tweaked a file, worked perfectly with Handoff. Apple likely wanted a clean "2012 and forward" for the feature, instead of "2012 and forward for everything except these two specific 2011 models". In this case they maybe wanted "x years forward" and not "x years forward except these specific iMac model, they're good".
 

Macbookprodude

Suspended
Jan 1, 2018
3,306
898
Thanks for the link. Yes, Windows 10 runs on ARM PCs, like Microsoft's Surface Pro X, so it should run fine on Apple Silicon based Macs. So those who Boot Camp should have nothing to fear. The Boot Camp utility is still present in Big Sur.


My mistake, I did not know Windows supports ARM, so bootcamp should not be an issue on the new "PowerPC like ARM macs"
 

haralds

macrumors 68030
Jan 3, 2014
2,994
1,259
Silicon Valley, CA
Tried in VMware Fusion 11.5.5 and 12 Tech preview but the installer stops with "BIErrorDomain Error 3" when trying to select the existing 10.15 install to upgrade View attachment 926316
You need to install on a host that officially support macOS Big Sur. Doing that right now. Will see whether I can transplant the resulting VM to a non supporting 5,1.
 
  • Like
Reactions: TimothyR734

Macbookprodude

Suspended
Jan 1, 2018
3,306
898
Thanks for the link.

Currently using a PowerPC Mac to access this - The link just shows a smiley face. Should I be on an intel mac to access this cvha
I loaded the HD3000 kexts although still no HW Acel. Night Shift and Brightness control is working and it successfuly detects the HD3000.

Without acceleration, it will suck running it.
 
  • Like
Reactions: TimothyR734

revmouse

macrumors newbie
Nov 2, 2013
5
7
Waiting eagerly for the patcher with my Early 2011 17" Macbook Pro (faulty radeon gpu desoldered and bypassed, intel graphics only)
 
  • Like
Reactions: TimothyR734

ChefBapeSupreme

macrumors newbie
Jun 22, 2020
3
5
I have a 2010 Mac Pro 5,1 with an 8gb Sapphire RX580 gpu with metal support currently running Mojave. It should be able to run Catalina by simply installing a patcher. At that point, would it be possible to upgrade to Big Sur via patcher, assuming one can be made?

It's so stupid that Apple has cut support on these machines especially since they are significantly more powerful and capable than the majority of the 2013 computers they are continuing to support. Apple should cut support on macs like they do on iPhones. Support should only be cut when the device no longer has the hardware needed to run the operating system. I should not have to downgrade to a less capable but newer mac just to get the latest operating system Apple has to offer.

Anyway, if anyone has any idea if a Big Sur patcher is possible for a Mac Pro 5,1, let me know. And if not, any suggestions on what to upgrade to would be helpful aswell.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.