[pre-release] macOS Big Sur

[jlrycm]

On 7/15/2020 at 4:18 PM, jlrycm said:

@ham4ever, thanks a lot for sharing your EFI. @SavageAUS, I believe that I found the problem: I was not defining properly the device path for the WiFi card and the way it’s attached to the mobo is different as I had to install it in a PCI port in which I first installed a Startech PCI to PCIe adapter. I ran out of PCIe ports due to a USB 3.1 card that when installed disabled my PCIe x1 slots. This scenario works well in Catalina as the adapter is recognized OOB by macOS and the WiFi card was also recognized without major issues but with Big Sur everything changed. My only question is if I have to add device properties separately for both the adapter and the WiFi card. I attached the list of devices extracted from hackintool in Catalina.

pcidevices.txt

@ham4ever the WiFi issue was finally fixed with @MaLd0n assistance. In a nutshell, the AirportBrcmFixup kext was modified to remove the two new plugins, and in a DSDT @MaLd0n fixed the WiFi idk issue. I updated the config file removing from kernel section the reference to the two plugins and included the device properties based on the WiFi idk in DSDT. The only matter that I’m still curious is that even though the platform info section in the config file is properly completed based dortania guide for Hasswell, the About This Mac is showing in the serial number the following message: “To be filled by O.E.M.”. Does any of the hackintoshers know why the serial number is not displayed correctly. The serial number is the same one I have in macOS Catalina and has no issues. Big Sur is running from an externally enclosed SSD.

[DarkNeptune0]

I have a question, is the control center lag normal in hackintosh?

[Guest ricoc90]

4 minutes ago, DarkNeptune0 said:

I have a question, is the control center lag normal in hackintosh?

I believe that has to do with your WiFi not properly working. E.g. on my late 2012 Mac Mini I had the same issue until I got Wifi working and I've seen people reporting the same issue on hackintoshes whom reported it as fixed once they've got proper Wifi configuration (kexts, DSDT patches etc).

2 hours ago, ameenjuz said:

@fusion71au Catalina do not recognise Big Sur installed partition to seeing incompatible disk behavior

i think many users are facing this issue using catalina

i hope that you have solution

  Reveal hidden contents

Screenshot

 

Real macs have the same issue. Guess it has something to do with how Big Sur works, since it doesn't boot from the actual volume but rather a sealed snapshot.

[fusion71au]

2 hours ago, ameenjuz said:

@fusion71au Catalina do not recognise Big Sur installed partition

 

19 minutes ago, ricoc90 said:

Real macs have the same issue. Guess it has something to do with how Big Sur works, since it doesn't boot from the actual volume but rather a sealed snapshot.

 

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

Spoiler

 

[SavageAUS]

I don’t have Catalina installed anymore as I can’t get it to boot with my Big Sur EFI anymore. I’ll have to review the changes with an older EFI and see if I can get them both working again, as stable as big sur is it’s still beta and the next one may not install / upgrade then I’m screwed.


Sent from my iPhone using Tapatalk

[Blu24]

Updating to Catalina 10.15.6 fixed the Incompatible Disk issue for me 

[SavageAUS]

[mention]eSaF [/mention] yeah I think I know what it may be from the KP I get. When I get a change I’ll try it out and see if I can get it installed again.


Sent from my iPhone using Tapatalk

[pico joe]

59 minutes ago, fusion71au said:

 

 

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

  Reveal hidden contents

 

I can confirm your method to "open sealed" worked here .. thank you 

[ameenjuz]

1 hour ago, fusion71au said:

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

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

42 minutes ago, Blu24 said:

@Blu24 Updating to Catalina 10.15.6 fixed the Incompatible Disk issue for me 

i have updated catalina to 10.15.6 

still problem persist Incompatible Disk issue

Edited July 17, 2020 by ameenjuz
edited

[Blu24]

25 minutes ago, 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

Reseting the nvram may work

Edited July 17, 2020 by Blu24

[ameenjuz]

7 minutes ago, Blu24 said:

Reseting nvram may work

thanks everytime reset when i restart

i know it

when i mount the big sur volume manually this is appear

Spoiler

 

Edited July 17, 2020 by ameenjuz
edited

[Blu24]

17 minutes ago, ameenjuz said:

thanks everytime reset when i restart

i know it

when i mount the big sur volume manually this is appear

  Hide contents

 

Have you tried repairing the disk in Big Sur?

Edited July 17, 2020 by Blu24

[ameenjuz]

19 minutes ago, Blu24 said:

Have you tried repairing the disk in Big Sur?

yes i tried by repairing in big sur but no luck

[SavageAUS]

I don’t have Catalina installed anymore as I can’t get it to boot with my Big Sur EFI anymore. I’ll have to review the changes with an older EFI and see if I can get them both working again, as stable as big sur is it’s still beta and the next one may not install / upgrade then I’m screwed.

 

 

Sent from my iPhone using Tapatalk

For those interested it was NVMeFix that was causing a KP for Catalina for me. Removing that kext and updating config.plist with it removed has allowed catalina to boot and install.

 

 

Sent from my iPhone using Tapatalk

[SavageAUS]

Now I think the new plugins for AirportBrcmFixup are stopping Catalina booting. Does anyone know how to block them just on Catalina but allow them on Big Sur?

 

 

Sent from my iPhone using Tapatalk

[Matgen84]

44 minutes ago, SavageAUS said:

Now I think the new plugins for AirportBrcmFixup are stopping Catalina booting. Does anyone know how to block them just on Catalina but allow them on Big Sur?

 

 

Sent from my iPhone using Tapatalk

 

There is a new commit for AirportBcrmFixup 20 hours ago. Maybe it would be interesting to build new beta  I don't know if the boot-args works with news plugins.

Have a look to the readme files for Big Sur.

Edited July 17, 2020 by Matgen84

[SavageAUS]

Yeah I just seen that and rebuilt AirPortBrcmFixup now it works with Catalina without anything else.

Thanks [mention]Matgen84 [/mention]

 

 

Sent from my iPhone using Tapatalk

[MICKHAEL]

2 hours ago, SavageAUS said:

 

share it please)

[iCanaro]

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

[SavageAUS]

1 hour ago, MICKHAEL said:

share it please)

Share what?


Sent from my iPhone using Tapatalk

[Guest ricoc90]

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.

[pico joe]

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 ""

[MICKHAEL]

3 hours ago, SavageAUS said:

Share what?


Sent from my iPhone using Tapatalk

AirPortBrcmFixup, if you have it already compiled)

[Matgen84]

 

@MICKHAEL  latest  AirPortBrcmFixup 2.0.8 Beta

 

AirportBrcmFixup.kext.zip

Edited July 17, 2020 by Matgen84

[Alex HQuest]

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 July 17, 2020 by Alex HQuest