Jump to content

[pre-release] macOS Big Sur

gengik84

By gengik84,
in New Releases and Updates

 Share
3,698 posts in this topic

Recommended Posts

iCanaro
iCanaro
Posted
Posted
7 hours ago, eSaF said:

I've seen a few posts discussing the difficulty booting Catalina with Big Sur, I don't have the problem, as a matter of fact I moved Big Sur onto my main drive and have Catalina on an external drive. I did start off with BS on the external but swopped them around as I saw BS running stable even though it is still Beta. I have the one EFI Folder which is on the BS Partition that boots both as well as Windows.

 

Confirm

 

Z370 with disk NVMe 2Tb multiboot Win10 Pro and LTSC, High Sierra, Mojave, Catalina and BigPurge, start all correctly with both Clover 5119 mod and OC 060

 

T-RyZo with SSD 2TB multiboot Win10 Pro and LTSC, High Sierra, Mojave, Catalina and BigPurge, seamless start with OC 060

  • Like 1
Link to comment
Share on other sites
Guest ricoc90
Guest ricoc90
Posted
Posted
11 hours ago, fusion71au said:

Bingo. With APFS snapshots disabled, I can mount the Big_Sur volume from High Sierra and Catalina...


Yep I've read about it however it didn't work for me since I'd always get a "operation not permitted" error on running apfs_systemsnapshot (SIP and ARV both disabled).

My workaround was to boot stage 3 of the installer in verbose mode. Once it reached this line:

Quote

executing /System/Library/Filesystems/apfs.fs/Contents/Resources/apfs_sealvolume 


I restarted my system and booted from the BS volume instead. No sealing, no snapshot booting.

Link to comment
Share on other sites
pico joe
pico joe
Posted
Posted
18 minutes ago, ricoc90 said:


Yep I've read about it however it didn't work for me since I'd always get a "operation not permitted" error on running apfs_systemsnapshot (SIP and ARV both disabled).

My workaround was to boot stage 3 of the installer in verbose mode. Once it reached this line:


I restarted my system and booted from the BS volume instead. No sealing, no snapshot booting.

don't foget  "" after command  

/System/Library/Filesystems/apfs.fs/Contents/Resources/apfs_systemsnapshot -v /Volumes/Big_Sur -r ""
  • Like 2
Link to comment
Share on other sites
Alex HQuest
Alex HQuest
Posted
Posted (edited)
23 hours ago, Pavo said:

I really don't see this big need for everyone to disable security features like SIP. These security features do not effect the installation nor use of macOS BigSur or any other version of macOS in anyway. I can understand if you need to overwrite a system file or something but after the fact, it should be re-enabled.

Until there is a true need, I’m running my system in a full enabled SIP/CSR state on my machines. Been this way since High Sierra, zero reasons for me to do so - same rationale as yours: lift the restrictions for a specific system file replacement, move it back afterwards.

 

This is kinda like the folks now going great lengths to disable the snapshot BigSur runs on top of, to have access to the real files. You might have your need to overwrite a system file, but leaving it off afterwards, you are just compromising the security of your own machine. And not running a true “vanilla” system.

Edited by Alex HQuest
  • Like 1
Link to comment
Share on other sites
JahStories
JahStories
Posted
Posted (edited)
On 7/14/2020 at 6:47 PM, JahStories said:

With iMac 15,1 I can't see anything DRM protected anywhere (VideoProc hevc not supported h264 not supported)

Using iMacPro 1,1 I can see AppleTV and NetFlix on chrome (VideoProc hevc supported h264 supported)

But using safari I just get a red screen and using AppleTV app a green striped screen (audio works on both)

Old movies bought from iTunes when played on the AppleTV app show just a red screen as NetFlix.

I solved on Catalina using these boot-args, sadly shiki is not working on BigSur, let's hope some developer will find a solution... 

"shikigva=80 shiki-id=Mac-7BA5B2D9E42DDD94"

I'm already using an iMacPro smbios, but had to add that id too to make it work...

 

Spoiler

Schermata 2020-07-17 alle 16.27.04.png

 

Edited by JahStories
  • Like 1
Link to comment
Share on other sites
Pavo
Pavo
Posted
Posted
40 minutes ago, JahStories said:

I solved on Catalina using these boot-args, sadly shiki is not working on BigSur, let's hope some developer will find a solution...

"shikigva=80 shiki-id=Mac-7BA5B2D9E42DDD94"

 

 

Spoiler

Schermata 2020-07-17 alle 16.27.04.png

 

This is a known issue https://github.com/acidanthera/bugtracker/issues/1034#issuecomment-656701712

  • Like 1
Link to comment
Share on other sites
eSaF
eSaF
Posted
Posted

@Pavo - Astonishing, how did you manage to get a screen grab of Apple TV because I tried to do it to show I am using Booting shikigva=80 and nothin else with Mac Model 1.1 pro and can show all my Apple movie collection as well as Apple TV+ or am I missing something here. When I try to get a screen grab using OS X builtin method, it results in a black pic, so basically I am asking what app you used if any.

Link to comment
Share on other sites
Pavo
Pavo
Posted
Posted (edited)
2 minutes ago, eSaF said:

@Pavo - Astonishing, how did you manage to get a screen grab of Apple TV because I tried to do it to show I am using Booting shikigva=80 and nothin else with Mac Model 1.1 pro and can show all my Apple movie collection as well as Apple TV+ or am I missing something here. When I try to get a screen grab using OS X builtin method, it results in a black pic, so basically I am asking what app you used if any.

What screen grab of AppleTV are you referring to? You can not take a screenshot of DRM content, it will result in a black screenshot.

Edited by Pavo
Link to comment
Share on other sites
eSaF
eSaF
Posted
Posted
Just now, Pavo said:

What screen grab of AppleTV are you referring to? You can not take a screenshot of DRM content, it will result in a black screenshot.

In the post 3 above this one with the Apple cartoon. Yea I know about DRM content hence I wondering how you got that pic to illustrate your point.

Link to comment
Share on other sites
Pavo
Pavo
Posted
Posted
1 minute ago, eSaF said:

In the post 3 above this one with the Apple cartoon. Yea I know about DRM content hence I wondering how you got that pic to illustrate your point.

That wasn't me, that was @JahStories

Link to comment
Share on other sites
opnoise
opnoise
Posted
Posted
2 minutes ago, Pavo said:

What screen grab of AppleTV are you referring to? You can not take a screenshot of DRM content, it will result in a black screenshot.

 

I think it was a photo that was taken and linked by @JahStories of someone's screen with multiple options of DRM working in Catalina (based off of the background pic), not something @Pavo did. 

 

Speaking of, @Pavo, I've seen you mention getting DRM working on a number of your AMD dGPU setups using without WhateverGreen using only ACPI SSDT patches. Is that something that only works on the Radeon VII and Vega cards you have or something that would also work with the Polaris Ellesmere (RX580) card? Have any pointers or guides to link to on how to accomplish that?

  • Like 1
Link to comment
Share on other sites
Pavo
Pavo
Posted
Posted
2 minutes ago, opnoise said:

Speaking of, @Pavo, I've seen you mention getting DRM working on a number of your AMD dGPU setups using without WhateverGreen using only ACPI SSDT patches. Is that something that only works on the Radeon VII and Vega cards you have or something that would also work with the Polaris Ellesmere (RX580) card? Have any pointers or guides to link to on how to accomplish that?

Not using any patches, just using a SSDT that makes the dGPU identify as it should in macOS. I have used the same SSDT (with slight modifications to Devices under Scope) for R9 290-x, RX 480/580, Vega 64 and now Radeon VII and they all work as intended. The one thing to remember though, I never had a system that had a iGPU at all, so results may vary.

Here is the SSDT I currently use: 

DefinitionBlock ("", "SSDT", 1, "APPLE ", "GFX", 0x00001000)
{
    External (_SB_.PCI0.SE0_, DeviceObj)

    Scope (_SB.PCI0.SE0)
    {
        Device (GFX0)
        {
            Name (_ADR, Zero)  // _ADR: Address
            Method (_DSM, 4, NotSerialized)  // _DSM: Device-Specific Method
            {
                Return (Package (0x02)
                {
                    "hda-gfx", 
                    Buffer (0x0A)
                    {
                        "onboard-1"
                    }
                })
            }
        }

        Device (HDAU)
        {
            Name (_ADR, One)  // _ADR: Address
            Method (_DSM, 4, NotSerialized)  // _DSM: Device-Specific Method
            {
                Return (Package (0x02)
                {
                    "hda-gfx", 
                    Buffer (0x0A)
                    {
                        "onboard-1"
                    }
                })
            }
        }
    }
}

 

  • Like 2
Link to comment
Share on other sites
JahStories
JahStories
Posted
Posted (edited)
1 hour ago, Pavo said:

...

Here is the SSDT I currently use:

...

I tried using this SSDT on BS (with adaptation for my HW) but it does not solve my DRM issues...

 

About the image I posted, is not a screenshot it's a picture took with my phone xD

Edited by JahStories
Link to comment
Share on other sites
Ludox
Ludox
Posted
Posted
Clover r5120 disables the lan and the audio and how it did not load the kexts AppleALC.kext and IntelMausiEthernet.kext, hp had to reset 5119 to have all activated again, how come?
 
  • Thanks 1
Link to comment
Share on other sites
Max.1974
Max.1974
Posted
Posted (edited)
27 minutes ago, ludox said:
Clover r5120 disables the lan and the audio and how it did not load the kexts AppleALC.kext and IntelMausiEthernet.kext, hp had to reset 5119 to have all activated again, how come?
 

 

Im have no idea...hahahaha its a crazy Horse now...mess around and all charm from Hack...but im will prefer Clover and if is possible AVOID OC----- -r

Captura de Tela 2020-07-17 às 18.56.24.png

Edited by Max.1974
Link to comment
Share on other sites
fusion71au
fusion71au
Posted
Posted (edited)
On 7/17/2020 at 11:32 AM, ameenjuz said:

i have already deleted snapshot using usb installer but i still can't mount the Big Sur Volume in Catalina

Remember i have installed Big Sur and Catalina in one drive

i have updated catalina to 10.15.6 

still problem persist Incompatible Disk issue

 

On 7/17/2020 at 9:39 PM, ricoc90 said:


Yep I've read about it however it didn't work for me since I'd always get a "operation not permitted" error on running apfs_systemsnapshot (SIP and ARV both disabled).

My workaround was to boot stage 3 of the installer in verbose mode. Once it reached this line:


I restarted my system and booted from the BS volume instead. No sealing, no snapshot booting.

 

@ASentientBot posted an excellent summary of Volume Sealing and APFS snapshots @MacRumors forum post#807. 

 

It looks like @ameenjuz's problem is that his Big_Sur volume is sealed, and there is no way to unseal it once already sealed, short of reinstalling again and interrupting phase3 installation (like @ricoc90) or using a patched installer in the first place (based on @ASentientBot's hax2 or hax3.dylib).

 

Re Volume Sealing:

"This is the means by which the boot volume is cryptographically signed and modifications are detected. It also seems to be the reason why BS system volumes cannot be mounted under Catalina or older (specifically due to the APFS_INCOMPAT_SEALED_VOLUME flag, see here). My latest installer hack turns off sealing (but not snapshots, which is why it failed to fix error 66 for most people). There doesn't seem to be any way to fully unseal a volume once it's been sealed: snapshots and verification can be turned off, but it will never mount on an older OS since that flag is still present. So the install-time disabling seems like a must."

 

My guide on deleting APFS snapshots will only solve the "error 66" problem when trying to mount your / as read/write eg when installing/replacing kexts in /S/L/E.  Hope this clarifies things now :).

 

Extra info:  @ResEdit_ResEdit edited "/macOS Install Data/UpdateOptions.plist" file (booted into macOS on separate drive after phase1 reboot) to prevent volume sealing occurring later on during phase3...

 

Spoiler

Big_Sur1.thumb.png.066f48f2890bca035e1128d12f90fbbe.pngBig_Sur2.thumb.png.70f1af227769e3023ea23bde782f6551.png

 

As reported by @AppleBreak and confirmed by @ameenjuz, the "UpdateOptions.plist method" to prevent sealing of the Big_Sur volume has the unfortunate side-effect of later preventing the deletion of APFS snapshots from Recovery/Installer USB, throwing out "Operation not permitted" and "Insufficient privileges" errors.  Therefore recommend interrupting of phase3 installation method or using @ASentientBot's hax2/hax3 patched installer to prevent volume sealing and allowing access to Big_Sur volume from older macOS...

Spoiler

1582477364_BigSur1stphaseinstallation.png.40391b07e71cf8442a201e6c4fc0c352.png1889910682_BigSur2ndphase.thumb.png.6e63fa96d73af33f6eabef9cf5aacae1.png108113237_BigSurendof2ndphase.thumb.png.7a5d10a833de2b4a36437bd271f1baac.png312599120_BigSurmidwaythru3rdphase.thumb.png.872e52b8f4e3a299ddf0477d175d83e5.png1562536386_UnsealedBig_SurVolumefromCatalina.thumb.png.a439b4c92b3074713e4e4bc468dbbbce.png

 

Edited by fusion71au
Extra Info
Link to comment
Share on other sites
jsl2000
jsl2000
Posted
Posted (edited)
20 hours ago, ludox said:
The new clover bootloader (5120) with big sur support has been released
 

This new version can boot Big Sur, Catalina, & 10.14.x without any issue except I need add apfs.efi in addition to ApfsDriverLoader.efi in my Z77 hackintosh. There's one bug I found. It can recognize one of APFS partitions (10.15.x or 10.16 beta) only to boot. OpenCore 0.6.0 can recognize both and select one of them to boot.

Edited by jsl2000
  • Like 1
Link to comment
Share on other sites
Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...