[pre-release] macOS Big Sur

[Moviemakergr]

15 minutes ago, aziiz3 said:

your english is fine, maybe better be blunt rather quoting scary

well i thought it's better hotpatching SSDT rather than using a single DSDT, incase there will be a bios update or hardware change. so you could boot bigsur installer ?

Yeap for me it is absolutely necessary a DSDT to take boot on a Laptop.

[lottenow]

1 hour ago, MICKHAEL said:

hello
just like @mnfesq @lottenow @hohoho, I have issues with detecting my ssd storage from big sur installer. in my case its a pci8086,a103.
guys, did you found a solution for that? or we could try to use IOAHCIFamily.kext from Catalina?

 

I tried loading IOAHCIFamily.kext from Catalina with OC, but I could not boot as the IOAHCIFamily.kext is pre-loaded from Big Sur.

 

I do not know how to work around that... I think Clover might allow to block certain kexts from loading with KextsToPatch?

 

Is anyone able to upload/PM the IOAHCIFamily.kext from Big Sur? I would really appreciate it!

Edited July 21, 2020 by lottenow

[MICKHAEL]

5 minutes ago, lottenow said:

 

I tried loading IOAHCIFamily.kext from Catalina with OC, but I could not boot as the IOAHCIFamily.kext is pre-loaded from Big Sur.

 

I do not know how to work around that... I think Clover might allow to block certain kexts from loading with KextsToPatch?

 

Is anyone able to upload/PM the IOAHCIFamily.kext from Big Sur? I would really appreciate it!

hi. sure https://www.dropbox.com/s/j9qcvcr2qa4vg8t/IOAHCIFamily.kext.zip?dl=0

 

the problem its bigger I think, clover are unable to patch preloaded kernel cache

Edited July 21, 2020 by MICKHAEL

[nmano]

10GB Ethenet card not work in MacOS Big Sur

 

10.15.5

Aquantia AQC107:

 

  Name: ethernet

  Type: Ethernet Controller

  Driver Installed: Yes

  MSI: Yes

  Bus: PCI

  Slot: J8B4@35,0,0

  Vendor ID: 0x1d6a

  Device ID: 0x07b1

  Subsystem Vendor ID: 0x1043

  Subsystem ID: 0x8741

  Revision ID: 0x0002

  Link Width: x4

  Link Speed: 8.0 GT/s

 

 

MacOS Big Sur

11.0 Beta (20A4300b

ethernet:

 

  Type: Ethernet Controller

  Driver Installed: No

  MSI: No

  Bus: PCI

  Slot: J8B4@35,0,0

  Vendor ID: 0x1d6a

  Device ID: 0x07b1

  Subsystem Vendor ID: 0x1043

  Subsystem ID: 0x8741

  Revision ID: 0x0002

  Link Width: x4

  Link Speed: 8.0 GT/s

[lottenow]

38 minutes ago, MICKHAEL said:

hi. sure https://www.dropbox.com/s/j9qcvcr2qa4vg8t/IOAHCIFamily.kext.zip?dl=0

 

the problem its bigger I think, clover are unable to patch preloaded kernel cache

 

Yeah, I get a Kernel Panic as the kext from Big Sur is pre-linked and I cannot get around it.

 

Also, thanks for uploading this @MICKHAEL!

[d5aqoep]

I managed to get all USB3 ports on my MSI X299 Tomahawk AC working via Clover. 

Following things are needed

1. Rehabman's USBInjectall.kext in Kexts/Other folder
2. change EHC1 to EH01   45484331    45483031
3. change EHC2 to EH02   45484332    45483032
4. change XHCI to XHC     58484349    5848435F
5. uia_exclude=HS01,HS02,HS07,HS08,HS13,USR1,USR2,SS01,SS02 (Boot Argument)

You can use Hackintool to check which ports you don't need and add to exclude list. The above exclude list works for my specific motherboard. But if you have MSI X299 board, you might need similar exclude list. Depending on which front header you have connected to front panel USB 3 ports. 

I tried the USB map approach but somehow it just doesn't work that well for me. I am fine with disabling non required ports.

 

Anyone managed to install Big Sur via Clover bootable USB? If I used OC 0.6.0, it messes up with my NVRAM and Windows Store loses offline game play permissions.

 

@meaganmargaret My random AQN107 works perfectly in Big Sur

Try this kext patch

• AppleEthernetAquantiaAqtion       0F84B003 0000       660F1F44 0000

 

I have also managed to get my Intel AX200 m.2 card to work in Big Sur. Daily kext builds are available here

https://github.com/1hbb/OpenIntelWireless-Factory

For some GPL reasons the author didn't use Apple's close source IO80211Family but rather spoofed it into Ethernet, just like USB Wi-Fi cards. Make sure to install Heliport companion app to find wireless. We can't always have best things hehe.

Edited July 21, 2020 by d5aqoep

[d5aqoep]

@meaganmargaret The patch worked for me in both Clover and OC.

[gengik84]

20 minutes ago, meaganmargaret said:

and doesn't apply after you've installed

exactly 

UpdateOptions.plist is created after first phase and it's located in /volumes/your_disk_name/"macOS Install Data"

[ameenjuz]

3 minutes ago, gengik84 said:

exactly 

UpdateOptions.plist is create after first phase and it's located in /volumes/your_disk_name/"macOS Install Data"

but in this procedure after installation complete we cannot delete the snapshot 

it is just for disabling sealing

[gengik84]

8 minutes ago, ameenjuz said:

but in this procedure after installation complete we cannot delete the snapshot 

it is just for disabling sealing

Do you have read my post?

mine is just a small addition to the @fusion71au information 

https://www.insanelymac.com/forum/topic/344428-pre-release-macos-big-sur/?do=findComment&comment=2730814

 

[ameenjuz]

6 minutes ago, gengik84 said:

Do you have read my post?

mine is just a small addition to the @fusion71au information 

https://www.insanelymac.com/forum/topic/344428-pre-release-macos-big-sur/?do=findComment&comment=2730814

 

yes i have read your prevouis post

sorry for inconvenience

i m sharing my testing

[gengik84]

5 minutes ago, ameenjuz said:

sorry for inconvenience

no problem

I quoted @fusion71au in a small part of your post...so my speech is only related to this .. nothing more

[mnfesq]

@lottenow @PC IT @hohoho @MICKHAEL It appears that at least 5 of us are all having the same problem - no ability to have Big Sur read our AHCI-connected drives.  Since I have a fully-functioning installation on a USB drive, I swapped the IOAHCIFamily.kext from Catalina with the Big Sur version.  I was able to boot to Big Sur on the USB drive but it didn't change anything - I couldn't see my internal drives.  I will experiment with that a bit more before I rule it a complete failure and will report back.  

[MICKHAEL]

[mention=2453806]lottenow[/mention] [mention=2061806]PC IT[/mention] [mention=1197538]hohoho[/mention] [mention=594753]MICKHAEL[/mention] It appears that at least 5 of us are all having the same problem - no ability to have Big Sur read our AHCI-connected drives.  Since I have a fully-functioning installation on a USB drive, I swapped the IOAHCIFamily.kext from Catalina with the Big Sur version.  I was able to boot to Big Sur on the USB drive but it didn't change anything - I couldn't see my internal drives.  I will experiment with that a bit more before I rule it a complete failure and will report back.  

Yes. That's kind of work around, but just like you say... we could use something like I understand now it's happening with WiFi kext. It injecting Catalina's WIFI driver.

Trimis de pe al meu Pixel folosind Tapatalk

[jlrycm]

My Big Sur beta 2 install booting with OC 0.6.0 in this mobo sometimes freezes after using it for about 15-20 minutes, experiencing the issue while trying to open different apps, not just one in particular. I was wondering if some of you are experiencing the same problem and if it can be just a bug of a beta or if there’s a setting or configuration in OC that needs a fix. I’ll upload my efi folder later today when I access my computer.

 

On a side note, I had a problem with my Big Sur build on mobo GA-Z97-HD3 while booting OC consisting of not being able to access the BIOS and I figured out the problem was related to using Bootstrap in OpenCore. The moment I changed the OC booting entry back to Bootx64.efi using EasyUEFI in Windows, the issue was gone. I read in the OC configuration that some systems don’t react well to bootstrap and this may could have been a side effect of it.  I’m also interested in knowing more about the best way to boot Big Sur and Windows through OpenCore without OC messing Windows by altering the ACPI environment. I see that there’s a NDK release of OpenCore which was not altering ACPI in Windows but not sure it can boot Big Sur.  Maybe some of the moderators and colleagues can give some light about it.

Edited July 21, 2020 by jlrycm

[PC IT]

53 minutes ago, mnfesq said:

@lottenow @PC IT @hohoho @MICKHAEL It appears that at least 5 of us are all having the same problem - no ability to have Big Sur read our AHCI-connected drives.  Since I have a fully-functioning installation on a USB drive, I swapped the IOAHCIFamily.kext from Catalina with the Big Sur version.  I was able to boot to Big Sur on the USB drive but it didn't change anything - I couldn't see my internal drives.  I will experiment with that a bit more before I rule it a complete failure and will report back.  

Thank you all for the efforts to solve the problem in Bigsur ahci not detected, testing many possible solutions, , even seal disable, never shows the ahci for skylake laptops, system boots well only from usb ssd disk, i am thinking to change the port name , sata1 to usb, we may need a patch for that , either rename in dsdt, or fake pci relector kext, also possible try is to have r/w bigsur disk image to try on our systems , we may find the difference, we are on the same boat, hope to find a sooner solution.

 

can anyone who successfully installed bigsur with read/write, seal removed,  make us a disk image so we can test? waiting help from others. thanks

[mnfesq]

1 hour ago, mnfesq said:

@lottenow @PC IT @hohoho @MICKHAEL It appears that at least 5 of us are all having the same problem - no ability to have Big Sur read our AHCI-connected drives.  Since I have a fully-functioning installation on a USB drive, I swapped the IOAHCIFamily.kext from Catalina with the Big Sur version.  I was able to boot to Big Sur on the USB drive but it didn't change anything - I couldn't see my internal drives.  I will experiment with that a bit more before I rule it a complete failure and will report back.  

 

Using Catalina's IOAHCIFamily.kext has not been a complete failure.  It took a few tries to get it to load but once it loaded, it was able to recognize the presence of the devices but could not recognize sufficient information to initialize them.  Here's what I got:

Spoiler

  

 

If anyone has suggestions as to where to go from here, let me know.

[lottenow]

35 minutes ago, mnfesq said:

 

Using Catalina's IOAHCIFamily.kext has not been a complete failure.  It took a few tries to get it to load but once it loaded, it was able to recognize the presence of the devices but could not recognize sufficient information to initialize them.  Here's what I got:

  Hide contents

  

 

If anyone has suggestions as to where to go from here, let me know.

 

@mnfesq: Are you using OC or Clover?

 

If OC, remove the all SATA patches (e.g. SAT0 => SATA, etc) and see if it works.

 

Also, you should try injecting via DeviceProperties on OC, use Hackintool to get the Device Path and input the "name" as String (e.g. pci8086,a103).

 

How did you achieve that? Did you have to "unseal" your sealed System partition? Does the Recovery 11.0 recognises them under Disk Utility or diskutil?

 

Let me know! Well done!

[mnfesq]

6 minutes ago, lottenow said:

 

@mnfesq: Are you using OC or Clover?

 

If OC, remove the all SATA patches (e.g. SAT0 => SATA, etc) and see if it works.

 

Also, you should try injecting via DeviceProperties on OC, use Hackintool to get the Device Path and input the "name" as String (e.g. pci8086,a103).

 

How did you achieve that? Did you have to "unseal" your sealed System partition? Does the Recovery 11.0 recognises them under Disk Utility or diskutil?

 

Let me know! Well done!

 

I am using Clover to boot to Big Sur although I am able to boot via OC as well.  I did not need to unseal anything to use the Catalina version of IOAHCIFamily.kext.  Since I have Big Sur on a USB drive, I booted to Catalina on my laptop with the USB drive connected and just copied the Catalina kext to Big Sur's S/L/E.  Unsealing only applies to installers, not already-installed systems.  As far as injection goes, it doesn't appear to be necessary.  Big Sur properly identifies my VID/PID as 8086,9D03:

Spoiler

 

So it might be as @ameenjuz suggested - that this is a bug in Big Sur that will need to be resolved in later beta versions.  At least, I hope it will.

[ameenjuz]

47 minutes ago, mnfesq said:

 

I am using Clover to boot to Big Sur although I am able to boot via OC as well.  I did not need to unseal anything to use the Catalina version of IOAHCIFamily.kext.  Since I have Big Sur on a USB drive, I booted to Catalina on my laptop with the USB drive connected and just copied the Catalina kext to Big Sur's S/L/E.  Unsealing only applies to installers, not already-installed systems.  As far as injection goes, it doesn't appear to be necessary.  Big Sur properly identifies my VID/PID as 8086,9D03:

  Hide contents

 

So it might be as @ameenjuz suggested - that this is a bug in Big Sur that will need to be resolved in later beta versions.  At least, I hope it will.

look like your ioregistry you are still using SATA patch,  remove all patches related to sata

and also remove Catalina's IOAHCIFamily.kext replace original one

try boot usb 3 installer which i m using

look at my ioregistry screenshot

Spoiler

 

 

Edited July 21, 2020 by ameenjuz
edited

[mnfesq]

21 minutes ago, ameenjuz said:

look like your ioregistry you are still using SATA patch,  remove all patches related to sata

and also remove Catalina's IOAHCIFamily.kext replace original one

try boot usb 3 installer which i m using

look at my ioregistry screenshot

  Reveal hidden contents

 

 

 

Thanks for your suggestion but I was trying that weeks ago with no luck.  I even tried removing all DSDT/SSDT's yesterday and it doesn't work. Period.  I'm glad your system works OOB without any patches or modified kexts but that is not my experience nor the experience of the other 4 people I am working with to resolve this.  If you have any ideas other than to try the vanilla method once again, I would appreciate your input.

[ameenjuz]

6 minutes ago, mnfesq said:

 

Thanks for your suggestion but I was trying that weeks ago with no luck.  I even tried removing all DSDT/SSDT's yesterday and it doesn't work. Period.  I'm glad your system works OOB without any patches or modified kexts but that is not my experience nor the experience of the other 4 people I am working with to resolve this.  If you have any ideas other than to try the vanilla method once again, I would appreciate your input.

i m not using modified kext i think that misunderstanding

only remove sata related patch  and don't remove another patch

if anyone have realmac as a kabylake then they will be checked SATA Controller

we hope that anyone will find solution sooner

sorry for my poor english  isn't my native language

[Pavo]

8 hours ago, d5aqoep said:

Try this kext patch

• AppleEthernetAquantiaAqtion       0F84B003 0000       660F1F44 0000

This patch also worked for my AQN107 for my on board Aquantia NiC on my TRX40 board, thank you.

[MICKHAEL]

1 hour ago, ameenjuz said:

i m not using modified kext i think that misunderstanding

only remove sata related patch  and don't remove another patch

if anyone have realmac as a kabylake then they will be checked SATA Controller

we hope that anyone will find solution sooner

sorry for my poor english  isn't my native language

@ameenjuz haha, I would like to try to boot already installed system on USB, but I got this screen. btw. install are booting without this bug. regards

i will try -disablegfxfirmware, maybe maybe

Edited July 21, 2020 by MICKHAEL

[mnfesq]

22 minutes ago, MICKHAEL said:

@ameenjuz haha, I would like to try to boot already installed system on USB, but I got this screen. btw. install are booting without this bug. regards

i will try -disablegfxfirmware, maybe maybe

 

Yes, definitely use -disablegfxfirmware to get rid of the problem of the igpu boot loop.