Jump to content
3390 posts in this topic

Recommended Posts

32 minutes ago, SavageAUS said:

Ok let me know how you go, Like i said, you may need to change this part


<key>compatible</key>
<string>pci14e4,43a0</string>

To match your card.

@SavageAUS this is how the card is recognized in MacOS Catalina. Based on that, what device id should I use? 

pci14e4,4331?

Update: @SavageAUS, In the other hand, the readme of the AirportBrcmFixup says something about blocking the two new plugins using maxkernel 19.9.9 in the config file which is also suggested by MadL0n.

A18935AB-284B-4097-8FC6-4A5B16A51D16.jpeg

Edited by jlrycm
52 minutes ago, jlrycm said:

@SavageAUS this is how the card is recognized in MacOS Catalina. Based on that, what device id should I use? 


pci14e4,4331?

Update: @SavageAUS, In the other hand, the readme of the AirportBrcmFixup says something about blocking the two new plugins using maxkernel 19.9.9 in the config file which is also suggested by MadL0n.

 

Spoiler

A18935AB-284B-4097-8FC6-4A5B16A51D16.jpeg

 

I'm far from an exper on this but yes you can try.

<key>compatible</key>
<string>pci14e4,4331</string>
	
Edited by SavageAUS
18 minutes ago, SavageAUS said:

I'm far from an exper on this but yes you can try.


<key>compatible</key>
<string>pci14e4,4331</string>
	

 

Also, be vary of how you add the kexts to OC - otherwise they won't load properly. The order in Kernel -> Add should be:

BrcmBluetoothInjector

BrcmFirmwareData

BrcmPatchRAM3

55 minutes ago, Alex HQuest said:

 

Also, be vary of how you add the kexts to OC - otherwise they won't load properly. The order in Kernel -> Add should be:

BrcmBluetoothInjector

BrcmFirmwareData

BrcmPatchRAM3

We were discussing AirportBrcmFixup and its plugins which i put in the correct order.

If there are other issues in his config i didn't look at it.

  • Like 1
8 minutes ago, SavageAUS said:

We were discussing AirportBrcmFixup and its plugins which i put in the correct order.

If there are other issues in his config i didn't look at it.

Hi savage, use your airportbrcm kext and your deviceproperties but wifi doesn't work.
I have a dw1560 BCM94352Z and I also tried pci14e4,43b1 but it still goes undetected.
I share my config and if you could take a look to see what is missing, thanks.

config.plist

32 minutes ago, lasn2096 said:

Hi savage, use your airportbrcm kext and your deviceproperties but wifi doesn't work.
I have a dw1560 BCM94352Z and I also tried pci14e4,43b1 but it still goes undetected.
I share my config and if you could take a look to see what is missing, thanks.

config.plist

Have you tried without it?
I thought that card worked natively?

7 hours ago, meaganmargaret said:

So, has anyone fixed the issue of SIGABRT and SIGILL on a USB installer?  I'm actually just trying to get to a recovery/install console.  I'm not trying to install.  But with an EFI that boots both Beta 1 and 2 just fine, I can't get there with my USB installer, just get the loop of SIGABRT and SIGILL.....

 

Anyone got past this, and if so, can you share how you did it?

 

Try with this EFI but you have to adapt it to your system :

 

Before to boot the installer reset nvram x 2 in OC boot screen.

 

I've turned to false in config.plist the IntelMausi.kext for the USB installer. The config.plist needs to be modified a bit for the EFI SSD after installation.

 

 

Edited by Loloflat6
9 minutes ago, Moviemakergr said:

Goodmorning PPL

Two quick questions please.

Can anyone to boot on recovery mode on Big Sur ?

and which is the newone csr-active-config value for Big Sur ?

Thanks.

Set UEFI/APFS/JumpstartHotPlug to YES/True in config.plist.

  • Like 2
  • Thanks 1
5 hours ago, jlrycm said:

@SavageAUS It’s a Brcm94331cd mini pcie WiFi and BT combo card that I purchased back in 2014. About the serials, I had them already included but for some reason when I open About this MAC it shows the following wording: To be filled by OEM.
Update: I booted the system with the config file you edited but still no WiFi. I checked in Ioreg and nothing in there.

I have same WiFi card , and it worked OOP for me , but AirDrop and continuity don’t work , 

1 minute ago, ham4ever said:

I have same WiFi card , and it worked OOP for me , but AirDrop and continuity don’t work , 

I am using BT4LEContinuityFixup.kext for that.

Dont forget to update your config.plist

BT4LEContinuityFixup.kext.zip

  • Like 1
17 hours ago, aben said:

Whoa ! Seriously didn’t expect it to be that easy and smooth to update my current Catalina partition to Big Sur in a matter of minutes on my Dell Skylake laptop !

 

All I had to do was replace Lilu with latest “debug” version along with latest master builds of WEG and VirtualSMC, that’s it ! Didn’t even have to modify or edit my existing OC config.plist either ! Booted the Big Sur install media off my external HDD, tapped update directly onto my internal Catalina SSD partition and voila !
Update and install process smoothly took only about the usual 20 minutes with one additional reboot. Everything works just like it did on Catalina except for DRM/Netflix and the Trackpad preferences.

 

Massive respect to all developers and contributors for having reached this far of a milestone with the OC development.

HI. May i have your efi folder, i have skylake and i cannot update or install bigsur on the internal ssd, only booting via usb image, waiting

13 hours ago, Moviemakergr said:
That works ! and thank you

but somenthing make wrong ?

i have try csr-active-config

67000000 - FF0F0000 - 30000000 - E7030000

But has error 66

Spoiler 

 

 

Try 77080000 I think (in ProperTree). I may be wrong but I think that’s what I’m using and I still get error 66. I didn’t delete apfs snapshots, left it vanilla, that could be why I still get error 66.

 

I’ll upload my config later.

 

 

Sent from my iPhone using Tapatalk

Edited by SavageAUS
  • Like 1
  • Thanks 1

Hi All

I can't Install.

If I choose Insatll MacOS -> Hard Drive->Enter back to this screen.

 

Spoiler

image0.thumb.jpeg.d55a71c0851b07ce2f325c437034b32d.jpeg

 

12 minutes ago, SavageAUS said:

Try 77080000 I think (in ProperTree). I may be wrong but I think that’s what I’m using and I still get error 66. I didn’t delete apfs snapshots, left it vanilla, that could be why I still get error 66.

 

I’ll upload my config later.

 

 

Sent from my iPhone using Tapatalk

agree try use 77080000

pico@picos-iMac ~ % csrutil status                   

System Integrity Protection status: disabled (Apple Internal).

pico@picos-iMac ~ % csrutil authenticated-root status

Authenticated Root status: disabled

pico@picos-iMac ~ %

  • Like 1
49 minutes ago, Moviemakergr said:

But has error 66

 

  1. Disable authenticated root SIP by setting csr-active-config to 77080000 in OC's config.plist, then reset NVRAM through the OC boot menu.  Alternatively, with blank csr-active-config setting, boot to Recovery/Big Sur Installer and run csrutil disable, then csrutil authenticated-root disable in terminal
  2. Need to also disable APFS snapshots.  I posted a guide several pages ago on how to do this and also replace/installing old kexts.

 

Good Luck!

  • Like 6
  • Thanks 1
16 hours ago, lasn2096 said:

@SavageAUS could you share your config?

Could you add your hardware specs to your signature?

 

Attached my EFI folder minus resource folder and minus serial numbers.

This works 100% on my laptop in my signature.

 

 

EFI.zip

Edited by SavageAUS
Updated battery kext
  • Thanks 2
59 minutes ago, fusion71au said:

 

  1. Disable authenticated root SIP by setting csr-active-config to 77080000 in OC's config.plist, then reset NVRAM through the OC boot menu.  Alternatively, with blank csr-active-config setting, boot to Recovery/Big Sur Installer and run csrutil disable, then csrutil authenticated-root disable in terminal
  2. Need to also disable APFS snapshots.  I posted a guide several pages ago on how to do this and also replace/installing old kexts.

 

Good Luck!

Do you have EFI OpenCore for your Desktop1? It would probably work for my system because it matches mine for 95%. I would need it for Catalina 10,15.5
Thanks

38 minutes ago, Moviemakergr said:

Thanks, i have try but i can't find my fault..  :borg:

I have try also from recovery mode.

  Hide contents

1194979918_movieuefi__-bash__9046_and__pre-release__macOS_Big_Sur_-_Page_28_-_New_Releases_and_Updates_-_InsanelyMac_Forum.jpg.6d5181a8a2b5b20a05a536fbfbadd889.jpg

 

  1. First, boot to Recovery or your Big_Sur USB installer
  2. Type in terminal diskutil mountDisk1s5
  3. Then mount -uw "/Volumes/BigSur II" since you have spaces in your Big_Sur volume name.

 

Also hint for using terminal:  you can type some letters of a file path, then press <Tab> button and it will autocomplete ;)

 

 

 

32 minutes ago, luky35 said:

Do you have EFI OpenCore for your Desktop1? It would probably work for my system because it matches mine for 95%. I would need it for Catalina 10,15.5
Thanks

 

Already posted it back here.

Edited by fusion71au
  • Like 1
6 minutes ago, fusion71au said:

Try mount -uw "/Volumes/BigSur II" since you have spaces in your Big_Sur volume name.

 

Also hint for using terminal:  you can type some letters of a file path, then press <Tab> button and it will autocomplete ;)

 

 

 

 

Already posted it back here.

Thanks

 

1 hour ago, SavageAUS said:

Could you add your hardware specs to your signature?

 

Attached my EFI folder minus resource folder and minus serial numbers.

This works 100% on my laptop in my signature.

 

EFI.zip

Reviewing I realized you had another key, maybe it must be that, how can I identify my key?

thanks great job @lvs1974  finally have been fixed SMCBatteryManager by lvs1974

i compiled latest commit changes of https://github.com/acidanthera/VirtualSMC/tree/smcbat_bigsur_adaptation

SMCBatteryManager.kext Worked perfectly 

once again thanks and great job 

credit goes to @lvs1974

VirtualSMC-1.1.5-RELEASE.zip

Edited by ameenjuz
  • Like 2
1 minute ago, ameenjuz said:

thanks great job @lvs1974  finally have been fixed SMCBatteryManager by lvs1974

i compiled latest commit changes of https://github.com/acidanthera/VirtualSMC/tree/smcbat_bigsur_adaptation

SMCBatteryManager.kext Worked perfectly 

once again thanks and great job 

credit goes to @lvs1974

Thanks, credit also goes to @vit9696, who helped me to find missing SMC keys.

  • Like 6
Guest
This topic is now closed to further replies.
×
×
  • Create New...