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.
I do not think this is just a bug, I could be wrong but more inclined towards " they are enforcing T2 for encoding " I also read somewhere that now to watch Netflix 4K you have to have a T2 ... Isn't it related?

I hope I am all wrong...

No -- having gone through the the Big Sur Betas -- my personal view is that Apple is gradually through each Big Sur beta trying to make it difficult to get Big Sur running on machines that no longer has the blessings from Apple. It is quite clear to me that this is not a bug that Apple inadvertently introduces.
 
No -- having gone through the the Big Sur Betas -- my personal view is that Apple is gradually through each Big Sur beta trying to make it difficult to get Big Sur running on machines that no longer has the blessings from Apple. It is quite clear to me that this is not a bug that Apple inadvertently introduces.

I had only one issue with Big Sur in fact the only issue was when I went from beta 7 to beta 8 that's the only issue where it would not install, but it was my fault because I had omitted something that was working with the previous beta but not with the 8th, I mean other than that It was smooth. Like I said yesterday I do not understand why they would introduce such bug, and I am kind of thinking what you are thinking and I said I hope I am wrong.

It is kind of weird to me...

Again I hope I am wrong all the way.
 
The writing is on the wall buddy. T2 chip, Apple Silicon, etc.

If the MacPro4,1 and MacPro5,1 have the blessing of Apple, they would not be in the unsupported category as they can still run Big Sur very, very decently.
 
The writing is on the wall buddy. T2 chip, Apple Silicon, etc.

If the MacPro4,1 and MacPro5,1 have the blessing of Apple, they would not be in the unsupported category as they can still run Big Sur very, very decently.
I played 8K videos on earlier Big Sur on my cMP, so the T2 chip is an artificial restriction. So if the smbios spoofs iMacPro1,1 the playback is OK in Safari. The VP9 decoding can be offloaded softwarewise to the GPU and with the 24 cores the CPU load was only 21 percent. I haven't tested latest Big Sur.
 
  • Like
Reactions: kkinto
The writing is on the wall buddy. T2 chip, Apple Silicon, etc.
Sure, but lets not get too negative too quickly. There are still plenty of macs that wont be Apple Silicon for a year or three that will still need support so there's there's still some life in these magnificent beasts for now...enjoy them while you can and the work these amazing people are doing to keep them as up to date as possible. My cMP is 10 years old this year and still doing everything I need from it - well! Thanks to all concerned, the real heroes who are here for us when Apple isn't...
 
  • Like
Reactions: PeterHolbrook
About BigSur through opencore on unsupported MacPro, I could confirm that a MacPro3,1 with Penryn Core2Duo is capable to boot the beta 9 BigSur kernel (even without a Metal GPU) with a working desktop, but I would know, someone with Nehalem or Westmere architecture can boot any BigSur beta version ?
 
Apologies if this been answered at some point, but I couldn't seem to find anything definitive:

I currently have been running OpenCore with various options for sometime now with some basic options on a native Mojave install. The question is, if I wanted to upgrade to Catalina, is it just a matter of toggling the VMM flag, or do I need a separate drive to perform the installation? Thanks in advance for the clarification, and let me know if there is any other info you need? (config.plist for OC, etc.)
 
I'm working through the parts and got to part II but I'm unsure what the path of my graphics card is. I ran the gfxutil but I don't know which of these lines is the path. Which line should I use?
 

Attachments

  • Screen Shot 2020-10-04 at 7.32.30 AM.png
    Screen Shot 2020-10-04 at 7.32.30 AM.png
    588.9 KB · Views: 108
I think I found the path but that was after it started boot looping. I'm not sure what went wrong.
Screen Shot 2020-10-04 at 2.32.30 PM.png
 
Config.plist entry seems ok. Did you also place AppleMCEReporterDisabler.kext in EFI/OC/Kexts?

Also, use /User/user/gfxutil -f display
That just gives you the display path and not the path to everything
The AppleMCEReporterDisabler.kext is in the kexts folder along with the other two kext files.

The path also seemed to match what I found.
 
Question about installing on my 5,1. I have no plans to install Big Sur, the highest i want to go is Catalina for the GPU support. If i were to install opencore, would that change my SMBIOS to show as a different computer? From what i have heard if you mess around with SMBIOS when signed into icloud it can blacklist you from imessage and facetime?
 
Question about installing on my 5,1. I have no plans to install Big Sur, the highest i want to go is Catalina for the GPU support. If i were to install opencore, would that change my SMBIOS to show as a different computer? From what i have heard if you mess around with SMBIOS when signed into icloud it can blacklist you from imessage and facetime?
Whatever I'm not doing I have no problem with imessage and facetime.
 
Updated to 0.6.2 using h9826790's package. Thanks again. Then downloaded the Big Sur installer using gibMac. Installed with UpdateSMBIOS set to true. Booted into Big Sur beta 9. Did not have to use VMM. Then decided to turn off the SMBIOS and see if I can boot into Big Sur. It was successful! I'm hoping this continues. Glad to be able to boot into this after the disaster with Beta 8.
 
  • Like
Reactions: rivangom
Installed with UpdateSMBIOS set to true. Booted into Big Sur beta 9. Did not have to use VMM. Then decided to turn off the SMBIOS and see if I can boot into Big Sur. It was successful! I'm hoping this continues.

Is this just with hybridization spoofing? We will have to investigate the right strategy for installing and updating Big Sur, because temporary full spoofing could cause Apple ID issues...
 
Is this just with hybridization spoofing? We will have to investigate the right strategy for installing and updating Big Sur, because temporary full spoofing could cause Apple ID issues...

Just this below.

Code:
<dict>
<key>BoardProduct</key>
<string>Mac-7BA5B2D9E42DDD94</string>
</dict>

I didn't sign into an Apple ID services yet since I wanted to see if it would run first.
 
I think I'll redo the install with 0.6.2. Would I just need to follow the Uninstalling OpenCore step in Maintenance or would that screw up my Mac since I never finished Advanced Configuration?
 
Just this below.

Code:
<dict>
<key>BoardProduct</key>
<string>Mac-7BA5B2D9E42DDD94</string>
</dict>

I didn't sign into an Apple ID services yet since I wanted to see if it would run first.

Nice. This is good news.

I think I'll redo the install with 0.6.2. Would I just need to follow the Uninstalling OpenCore step in Maintenance or would that screw up my Mac since I never finished Advanced Configuration?

No need to uninstall when updating. If you already have OpenCore working, just carefully replace the files on the EFI volume and reboot.
 
  • Like
Reactions: PeterHolbrook
Nice. This is good news.



No need to uninstall when updating. If you already have OpenCore working, just carefully replace the files on the EFI volume and reboot.
I didn't finish the install and kept getting kernel panics trying to get the kexts to work. I'm on stuck on the step of Enabling Hardware Acceleration so I thought a new install from the beginning might provide better results.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.