Jump to content

[pre-release] macOS Big Sur


3,698 posts in this topic

Recommended Posts

Spoiler

20200805_205854.thumb.jpeg.ef794e51bd444bbfeabcb1c356d36e7b.jpeg.a7c5acd9ea3bda7458f7afa4bf119b89.jpeg

Here as well. Even compiled a new EFI as suggested.

 

Thanks @ileikcaek !

Quote

 setting UEFI > APFS > JumpstartHotPlug to true worked for me on earlier betas

 

Got my issue fixed . As well as cleaning up my config.plist via opencore sanity checker. Attaching my EFI . Hopefully it helps people with the some issue I had 

EFI.zip

AppleKey.png

Edited by rubenpp
Added EFI
Link to comment
Share on other sites

3 hours ago, Matgen84 said:

Hi All users

OCB: LoadImage failed - Unsupported is always present with Big Sur Beta 4: I can boot the Recovery Partition. With the same EFI folder, the same ScanPolicy, I can boot Catalina Recovery Partition. Strange !

 

Any ideas. Please :)

 

setting UEFI > APFS > JumpstartHotPlug to true worked for me on earlier betas. Recovery Images booted fine after.

  • Like 1
Link to comment
Share on other sites

13 minutes ago, D-an-W said:

Got Beta 4 all installed, if I wanted to use iCloud would it be wise to use slightly different info for the Device in my Config.plist so as not to mess up my Catalina install?

It doesn't matter you can use the same injected data you're using for Catalina or any other OS X because I dare say you'll be switching to BS eventually when it is finally released, that way your iCloud account will only register the one machine, also the advantage is you only need one EFI Folder to boot all OSs' if you're multi-booting.

  • Thanks 1
Link to comment
Share on other sites

Spoiler

sudo /Applications/Install\ macOS\ Big\ Sur\ Beta.app/Contents/Resources/createinstallmedia --volume /Volumes/USB

Password:

objc[952]: Class IASNightInstallSupport is implemented in both /System/Library/PrivateFrameworks/IASUtilities.framework/Versions/A/IASUtilities (0x7fff8d7bdd78) and /Applications/Install macOS Big Sur Beta.app/Contents/Frameworks/OSInstallerSetup.framework/Versions/A/Frameworks/IAESD.framework/Versions/A/Frameworks/IAInstallerUtilities.framework/Versions/A/IAInstallerUtilities (0x10d803ac0). One of the two will be used. Which one is undefined.

objc[952]: Class IASSystemInformation is implemented in both /System/Library/PrivateFrameworks/IASUtilities.framework/Versions/A/IASUtilities (0x7fff8d7bdeb8) and /Applications/Install macOS Big Sur Beta.app/Contents/Frameworks/OSInstallerSetup.framework/Versions/A/Frameworks/IAESD.framework/Versions/A/Frameworks/IAInstallerUtilities.framework/Versions/A/IAInstallerUtilities (0x10d803bd8). One of the two will be used. Which one is undefined.

Ready to start.

To continue we need to erase the volume at /Volumes/USB.

If you wish to continue type (Y) then press return: Y

I am attempting to make a BS BETA 4 USB installer. I have this error, but at the moment it seems to be creating a bootable USB, not sure if it will work during the install
@meaganmargaret I was also using the same USB with my BS BETA3 installer. I did wipe and erase the disk as HFS+ (that worked for you) but still I get this error, let me see if the installation will progress.

Edited by manmo71
  • Like 1
  • Sad 1
Link to comment
Share on other sites

4 minutes ago, manmo71 said:
  Reveal hidden contents

sudo /Applications/Install\ macOS\ Big\ Sur\ Beta.app/Contents/Resources/createinstallmedia --volume /Volumes/USB

Password:

objc[952]: Class IASNightInstallSupport is implemented in both /System/Library/PrivateFrameworks/IASUtilities.framework/Versions/A/IASUtilities (0x7fff8d7bdd78) and /Applications/Install macOS Big Sur Beta.app/Contents/Frameworks/OSInstallerSetup.framework/Versions/A/Frameworks/IAESD.framework/Versions/A/Frameworks/IAInstallerUtilities.framework/Versions/A/IAInstallerUtilities (0x10d803ac0). One of the two will be used. Which one is undefined.

objc[952]: Class IASSystemInformation is implemented in both /System/Library/PrivateFrameworks/IASUtilities.framework/Versions/A/IASUtilities (0x7fff8d7bdeb8) and /Applications/Install macOS Big Sur Beta.app/Contents/Frameworks/OSInstallerSetup.framework/Versions/A/Frameworks/IAESD.framework/Versions/A/Frameworks/IAInstallerUtilities.framework/Versions/A/IAInstallerUtilities (0x10d803bd8). One of the two will be used. Which one is undefined.

Ready to start.

To continue we need to erase the volume at /Volumes/USB.

If you wish to continue type (Y) then press return: Y

I am attempting to make a BS BETA 4 USB installer. I have this error, but at the moment it seems to be creating a bootable USB, not sure if it will work during the install
@meaganmargaret I was also using the same USB with my BS BETA3 installer. I did wipe and erase the disk as HFS+ (that worked for you) but still I get this error, let me see if the installation will progress.

You did not even had to search, just scroll up...

  • Like 1
Link to comment
Share on other sites

11 hours ago, Matgen84 said:

Hi @fusion71au

I've a question: for Beta 3, I follow your instructions to remove Snapshot. The fact that Snapshot is removed, does it have to do with the fact that I cannot install only the Beta 4 update. Full installer is required by Software Updater on my Big Sur system.

 

Yeah, you need to boot off a snapshot to be offered the OTA update to Beta4...

 

Spoiler

288807596_Beta4OTAsnapshotsenabled.thumb.png.9bac58fa382707b67320429c9ef798af.png

 

Also might help to re-enable SIP (run csrutil enable in Recovery terminal or Installer USB) before you go ahead with the automatic OTA update.

 

Personally, I usually download the full installer to be on the safe side - download,  then run Beta4 Install Assistant to get the Installer app in /Applications.

 

SHA1 hashes below...

fusion71au@fusion71aus-iMac ~ % shasum /Applications/Install\ macOS\ Big\ Sur\ Beta.app/Contents/SharedSupport/SharedSupport.dmg
7e0a988926cd00da28cf28e12386bb8a82e87285

fusion71au@fusion71aus-iMac ~ % shasum /Volumes/Install\ macOS\ Big\ Sur\ Beta/BaseSystem/BaseSystem.dmg
35a1f8a216acdc9177a6a0e49aa67a416c23f14f

Successfully did a clean install to internal SSD volume on my NUC6i5SYH with latest OC 0.6.0 and acidanthera kexts (Lilu, WEG, VirtualSMC, AppleALC etc)...

Spoiler

1196639129_Big_SurBeta4onNUC6i5SYH.thumb.png.b68a8b061e972151fd92821ea8486a9d.png

 

 

 

 

10 hours ago, Matgen84 said:

I read somewhere macOS  Big Sur create Snapshot for each update without remove the previous one.

 

Also successfully upgraded from Beta3 to Beta 4 by directly running the Installer app in Big Sur Beta3 on an external USB HD.  The original Beta3 volume had 2 snapshots - these were deleted in the upgrade process and replaced by only one APFS "install" snapshot which did not increase the overall size taken up on the Big Sur volume :).

 

 

9 hours ago, pico joe said:

I used @fusion71au method and no problem here

 

 

Yeah, the procedure to delete APFS snapshots and replace the wifi kext still works in Beta 4...

 

Spoiler

//First boot to Big Sur Recovery or Installer USB and run the following commands in terminal

-bash-3.2# csrutil disable
Successfully disabled System Integrity Protection.
Please restart the machine for the changes to take effect.
-bash-3.2# csrutil authenticated-root disable
Successfully disabled authenticated root.
Please restart the machine for the changes to take effect.
-bash-3.2# diskutil list
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *128.0 GB   disk0
   1:                        EFI ⁨EFI⁩                     209.7 MB   disk0s1
   2:                 Apple_APFS ⁨Container disk2⁩         30.6 GB    disk0s2
                    (free space)                         268.4 MB   -
   3:       Microsoft Basic Data ⁨Windows 10 SSD⁩          97.0 GB    disk0s3

/dev/disk1 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk1
   1:                        EFI ⁨EFI⁩                     209.7 MB   disk1s1
   2:                  Apple_HFS ⁨Macintosh HD⁩            119.5 GB   disk1s2
   3:                 Apple_Boot ⁨Recovery HD⁩             650.0 MB   disk1s3
   4:       Microsoft Basic Data ⁨HDD⁩                     815.4 GB   disk1s4
   5:         Microsoft Reserved ⁨⁩                        134.2 MB   disk1s5
   6:       Microsoft Basic Data ⁨BOOTCAMP⁩                63.8 GB    disk1s6
   7:           Windows Recovery ⁨⁩                        532.7 MB   disk1s7

/dev/disk2 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +30.6 GB    disk2
                                 Physical Store disk0s2
   1:                APFS Volume ⁨Macintosh SSD — Data⁩    4.3 GB     disk2s1
   2:                APFS Volume ⁨Preboot⁩                 82.2 MB    disk2s2
   3:                APFS Volume ⁨Recovery⁩                525.7 MB   disk2s3
   4:                APFS Volume ⁨VM⁩                      3.2 GB     disk2s4
   5:                APFS Volume ⁨Macintosh SSD⁩           11.0 GB    disk2s5

/dev/disk3 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *320.1 GB   disk3
   1:                        EFI ⁨EFI⁩                     209.7 MB   disk3s1
   2:                 Apple_APFS ⁨Container disk5⁩         59.7 GB    disk3s2
   3:       Microsoft Basic Data ⁨MACRIUM Backups⁩         166.4 GB   disk3s3
   4:                 Apple_APFS ⁨Container disk6⁩         53.6 GB    disk3s4
                    (free space)                         268.4 MB   -
   5:                 Linux Swap ⁨⁩                        4.3 GB     disk3s5
   6:       Microsoft Basic Data ⁨⁩                        314.6 MB   disk3s6
   7:           Linux Filesystem ⁨⁩                        35.1 GB    disk3s7

/dev/disk4 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *15.9 GB    disk4
   1:                        EFI ⁨EFI⁩                     209.7 MB   disk4s1
   2:                  Apple_HFS ⁨Install macOS Big Su...⁩ 15.5 GB    disk4s2

/dev/disk5 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +59.7 GB    disk5
                                 Physical Store disk3s2
   1:                APFS Volume ⁨Big_Sur — Data⁩          10.7 GB    disk5s1
   2:                APFS Volume ⁨Preboot⁩                 300.6 MB   disk5s2
   3:                APFS Volume ⁨Recovery⁩                880.9 MB   disk5s3
   4:                APFS Volume ⁨VM⁩                      1.1 MB     disk5s4
   5:                APFS Volume ⁨Big_Sur⁩                 16.5 GB    disk5s5

/dev/disk6 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +53.6 GB    disk6
                                 Physical Store disk3s4
   1:                APFS Volume ⁨Catalina - Data⁩         4.9 GB     disk6s1
   2:                APFS Volume ⁨Preboot⁩                 80.7 MB    disk6s2
   3:                APFS Volume ⁨Recovery⁩                731.6 MB   disk6s3
   4:                APFS Volume ⁨VM⁩                      2.1 GB     disk6s4
   5:                APFS Volume ⁨Catalina⁩                11.4 GB    disk6s5

/dev/disk7 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        +2.2 GB     disk7
   1:                 Apple_APFS ⁨Container disk8⁩         2.2 GB     disk7s1

/dev/disk8 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +2.2 GB     disk8
                                 Physical Store disk7s1
   1:                APFS Volume ⁨macOS Base System⁩       1.9 GB     disk8s1
   2:                APFS Volume ⁨Preboot⁩                 131.9 MB   disk8s2

-bash-3.2# diskutil mountDisk disk5s5
Volume(s) mounted successfully
-bash-3.2# mount -uw /Volumes/Big_Sur
-bash-3.2# /System/Library/Filesystems/apfs.fs/Contents/Resources/apfs_systemsnapshot -v /Volumes/Big_Sur -r ""
Attempting tagging of snapshot  on volume: /Volumes/Big_Sur 
-bash-3.2# diskutil apfs listSnapshots /Volumes/Big_Sur
Snapshots for disk5s5 (3 found)
|
+-- 5F4CD43E-8409-4F52-84A8-AE7481A22E66
|   Name:        com.apple.os.update-CB91AC289F495CB98E833BD15889FF8BBB8C1B5DF1DC747EA1449634D3F238DF
|   XID:         16807
|   Purgeable:   No
|
+-- 8EEEC314-FD68-4728-8311-53B492AD5A42
|   Name:        com.apple.bless.AB3111FC-F35C-4AD0-867E-6C05CCDC5D6A
|   XID:         17817
|   Purgeable:   Yes
|
+-- A3F5A6FA-7E48-4E4E-BEF3-92615DADE9F8
    Name:        com.apple.bless.44E81ED0-C080-4D58-95DB-DF1D1F418E1F
    XID:         18448
    Purgeable:   Yes
-bash-3.2# diskutil apfs deleteSnapshot /Volumes/Big_Sur -uuid A3F5A6FA-7E48-4E4E-BEF3-92615DADE9F8
Deleting APFS Snapshot A3F5A6FA-7E48-4E4E-BEF3-92615DADE9F8 "com.apple.bless.44E81ED0-C080-4D58-95DB-DF1D1F418E1F" from APFS Volume disk5s5
Started APFS operation
Finished APFS operation
-bash-3.2# diskutil apfs deleteSnapshot /Volumes/Big_Sur -uuid 8EEEC314-FD68-4728-8311-53B492AD5A42
Deleting APFS Snapshot 8EEEC314-FD68-4728-8311-53B492AD5A42 "com.apple.bless.AB3111FC-F35C-4AD0-867E-6C05CCDC5D6A" from APFS Volume disk5s5
Started APFS operation
Finished APFS operation
-bash-3.2# diskutil apfs deleteSnapshot /Volumes/Big_Sur -uuid 5F4CD43E-8409-4F52-84A8-AE7481A22E66
Deleting APFS Snapshot 5F4CD43E-8409-4F52-84A8-AE7481A22E66 "com.apple.os.update-CB91AC289F495CB98E833BD15889FF8BBB8C1B5DF1DC747EA1449634D3F238DF" from APFS Volume disk5s5
Started APFS operation
Finished APFS operation
-bash-3.2# diskutil apfs listSnapshots /Volumes/Big_Sur
No snapshots for disk5s5
-bash-3.2# reboot


//System rebooted into Big_Sur.  Now replace wifi kext with older one by running the following commands in terminal...

fusion71au@fusion71ausiMac ~ % sudo mount -uw /
Password:
fusion71au@fusion71ausiMac ~ % csrutil status
System Integrity Protection status: disabled.
fusion71au@fusion71ausiMac ~ % csrutil authenticated-root status
Authenticated Root status: disabled
fusion71au@fusion71ausiMac ~ % nvram csr-active-config
csr-active-config	w%08%00%00
fusion71au@fusion71ausiMac ~ % sudo mv /System/Library/Extensions/IO80211Family.kext /System/Library/Extensions/IO80211Family.orig
fusion71au@fusion71ausiMac ~ % sudo cp -R /Volumes/Install\ macOS\ Big\ Sur\ Beta/Kexts/IO80211Family.kext /System/Library/Extensions 
fusion71au@fusion71ausiMac ~ % sudo chown -R 0:0 /System/Library/Extensions/IO80211Family.kext && sudo chmod -R 755 /System/Library/Extensions/IO80211Family.kext
fusion71au@fusion71ausiMac ~ % sudo touch /System/Library/Extensions && sudo kmutil install --update-all
checking collections...
updated extension 'com.ATTO.driver.ATTOExpressSASRAID2' found in collection 'auxiliary kext collection' (mach-o UUID changed from <unknown> to 09E2D3CD-9959-56F9-15D9-620C7B7CCCE1)
updated extension 'com.ATTO.driver.ATTOExpressSASHBA2' found in collection 'auxiliary kext collection' (mach-o UUID changed from <unknown> to 6B01EE8B-9786-614A-7E03-D14C16EE2646)
updated extension 'com.promise.driver.stex' found in collection 'auxiliary kext collection' (mach-o UUID changed from <unknown> to AE253556-66D8-38D2-B9D1-179B78F29153)
updated extension 'com.realtek.driver.RtWlanU' found in collection 'auxiliary kext collection' (mach-o UUID changed from <unknown> to B377B783-938E-3EAD-8A33-265C0292B14E)
updated extension 'com.realtek.driver.RtWlanU1827' found in collection 'auxiliary kext collection' (mach-o UUID changed from <unknown> to EBE4C4E2-E918-3D37-B698-E545712E0766)
updated extension 'com.softraid.driver.SoftRAID' found in collection 'auxiliary kext collection' (mach-o UUID changed from <unknown> to 58844C00-8FB7-3DE4-84CC-F023DAD09DC6)
updated extension 'com.Areca.ArcMSR' found in collection 'auxiliary kext collection' (mach-o UUID changed from <unknown> to 05FBCBFC-1AE6-3BF9-BD0F-7655CC822E34)
updated extension 'com.CalDigit.driver.HDPro' found in collection 'auxiliary kext collection' (mach-o UUID changed from <unknown> to 7AB5C9DC-46D9-2868-5660-CE03CD4950C7)
updated extension 'com.ATTO.driver.ATTOCelerityFC8' found in collection 'auxiliary kext collection' (mach-o UUID changed from <unknown> to C88E0E7A-8F11-57D8-10EB-D83BD64E529E)
updated extension 'com.highpoint-tech.kext.HighPointIOP' found in collection 'auxiliary kext collection' (mach-o UUID changed from <unknown> to 2795A2E4-27BC-333B-BE4D-EA04D25270EE)
updated extension 'com.highpoint-tech.kext.HighPointRR' found in collection 'auxiliary kext collection' (mach-o UUID changed from <unknown> to A0C06D9F-5C9F-39E2-BA85-8720A8FF5BA6)
updated extension 'com.Accusys.driver.Acxxx' found in collection 'auxiliary kext collection' (mach-o UUID changed from <unknown> to 105F22C2-A690-33E0-BEB2-F65D14857FC3)
rebuilding release collections: boot, system
rebuilding release collections:
	boot kernel collection
	system kext collection
rebuilding local auxiliary collection
kmutil done
fusion71au@fusion71ausiMac ~ % sudo kcditto
Copying deferred prelinked kernels in /...
/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/kext_tools/kext_tools-692.0.0.141.1/kc_staging.m.279: Encountered error while inspecting path: Error Domain=NSCocoaErrorDomain Code=260 "The folder “PrelinkedKernels” doesn’t exist." UserInfo={NSFilePath=/Library/Apple/System/Library/PrelinkedKernels, NSUserStringVariant=(
    Folder
), NSUnderlyingError=0x7ff2ffc07150 {Error Domain=NSOSStatusErrorDomain Code=-43 "fnfErr: File not found"}}
/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/kext_tools/kext_tools-692.0.0.141.1/kc_staging.m.279: Encountered error while inspecting path: Error Domain=NSCocoaErrorDomain Code=260 "The folder “PrelinkedKernels” doesn’t exist." UserInfo={NSFilePath=/Library/Apple/System/Library/PrelinkedKernels, NSUserStringVariant=(
    Folder
), NSUnderlyingError=0x7ff2ffc0df30 {Error Domain=NSOSStatusErrorDomain Code=-43 "fnfErr: File not found"}}
Copying KCs in /...
System Volume UUID: 1224F1BE-00FA-465D-A741-231471142A76
Volume Group UUID: 2194BDE3-CD19-36D0-9293-00C9BB111011
Preboot disk: /dev/disk5s2
Preboot volume: /System/Volumes/Preboot
Copying: /System/Library/KernelCollections/BootKernelExtensions.kc.elides -> /System/Volumes/Preboot/2194BDE3-CD19-36D0-9293-00C9BB111011/boot/System/Library/KernelCollections
Copying: /System/Library/KernelCollections/BootKernelExtensions.kc -> /System/Volumes/Preboot/2194BDE3-CD19-36D0-9293-00C9BB111011/boot/System/Library/KernelCollections
Copying: /System/Library/PrelinkedKernels/immutablekernel -> /System/Volumes/Preboot/2194BDE3-CD19-36D0-9293-00C9BB111011/System/Library/PrelinkedKernels
Copying: /System/Library/PrelinkedKernels/prelinkedkernel -> /System/Volumes/Preboot/2194BDE3-CD19-36D0-9293-00C9BB111011/System/Library/PrelinkedKernels

 

 

Spoiler

1184647686_MacMini62DeleteSnapshotsandReplacewifikextinBeta4.thumb.png.fc0571e50cd4e0cf2d70a03972e1feea.png

 

Edited by fusion71au
  • Like 4
  • Thanks 2
Link to comment
Share on other sites

11 hours ago, eSaF said:

@Matgen84 - I should imagine since you altered the structure of Beta3 by removing the Seal from the volume (Snapshot) you cannot now update only will allow a clean and full install and probably have to go through the whole process again if you want to remove Snapshot from Beta4. Quite frankly I think it's too much of a hassle having to do that each time for every update/upgrade.

Yes, that's right what you write .. but many people are too lazy or ignorant to remove this seal, because ONLY then you can configure everything correctly.

They are just happy that they were able to update successfully, but cannot intervene in the system because it is sealed.

I ALWAYS bother and use good instructions from the German user @ResEdit (again thank you !!) on how to successfully remove the seal and

then you can edit and adapt the macOS Big Sur just like Mojave or other optmal.

  • Like 1
Link to comment
Share on other sites

6 hours ago, rubenpp said:

 

Here as well. Even compiled a new EFI as suggested.

 

20200805_205854.thumb.jpeg.ef794e51bd444bbfeabcb1c356d36e7b.jpeg.a7c5acd9ea3bda7458f7afa4bf119b89.jpeg

Thanks @ileikcaek !

 

Got my issue fixed . As well as cleaning up my config.plist via opencore sanity checker. Attaching my EFI . Hopefully it helps people with the some issue I had 

EFI.zip

AppleKey.png

 

nothing has worked for me i've got a x99 board with a haswell-e processor

Link to comment
Share on other sites

what's exactly the fix for AppleKeyStore boot delay issue with Beta 4?

 

Boot stops at AppleKeyStore, then move on a bit more, then it stops again at 

 

"tx_flush:1075: disk3 xid 18185 tx stats : 20 finish 20 enter 320 wait 0 0us close out flush 22494us"

 

Thanks!

 

Edited by markpenn
Link to comment
Share on other sites

23 minutes ago, Blu24 said:

*You need to remove vsmcgen=1

*Try OpenCore Sanity Checker:https://opencore.slowgeek.com

*This may also help you:https://github.com/Pavo-IM/OC-Gen-X

 

thank you so much on my specific case, the computer wont but without vsmcgen=1

 

i've already solved this on my x99 build by removing both:

booter-fileset-kernel and booter-fileset-basesystem

 

  • Like 3
Link to comment
Share on other sites

Spoiler

 

@Alex HQuest I did manage to create the installer USB for BS B4.

It boots up and went all the way to the install screen at which point I decided to do the clean install later.

 

With the downloaded full installer, when I attempt an upgrade from BS B3 to B4 I get this error.

I downloaded the installer using the script twice now, but still the same error.

 

Spoiler

808030481_ScreenShot2020-08-06at7_25_56AM.thumb.png.56616ad1e54ca03dba9ac089bdebb531.png

 

Link to comment
Share on other sites

8 hours ago, ileikcaek said:

 

setting UEFI > APFS > JumpstartHotPlug to true worked for me on earlier betas. Recovery Images booted fine after.

 

JumpstartHotPlug is activate since Beta 1. I can't boot Big Sur Recovery Partition, no problem for Catalina Recovery :)

Link to comment
Share on other sites

12 hours ago, Pavo said:

Phantom GPU is still there, just not as a device now, its a IOResource

 

Screenshot 2020-08-05 13.14.51.png

First time I'm hearing about this thing with phantom gpu.

Checked and I have it also , on a Dell 5570 with only an Intel UHD 620.

 

Is there something I can to to make it go away?

If not , do you thing it can cause any problems?

Only thing I noticed on Big Sur is that sometimes (not all of the time) afrer waking from sleep GPU hangs at max 1.1ghz and the only solution is to reboot.

Link to comment
Share on other sites

Is anyone able to boot to beta 4 using Clover?  Could you please post your EFI if you can?  Thanks. (I can boot using OC but would prefer to use Clover.  When I use Clover, I have problems with my custom kexts not loading.)

Link to comment
Share on other sites

3 minutes ago, mnfesq said:

Is anyone able to boot to beta 4 using Clover?  Could you please post your EFI if you can?  Thanks. (I can boot using OC but would prefer to use Clover.  When I use Clover, I have problems with my custom kexts not loading.)

 

@mnfesq Despite of the last commit, Clover is not ready yet for Big Sur. All my tests are unsucessed :cry:

  • Like 1
Link to comment
Share on other sites

4 hours ago, manmo71 said:
  Reveal hidden contents

 

@Alex HQuest I did manage to create the installer USB for BS B4.

It boots up and went all the way to the install screen at which point I decided to do the clean install later.

 

With the downloaded full installer, when I attempt an upgrade from BS B3 to B4 I get this error.

I downloaded the installer using the script twice now, but still the same error.

 

  Reveal hidden contents

808030481_ScreenShot2020-08-06at7_25_56AM.thumb.png.56616ad1e54ca03dba9ac089bdebb531.png

 

Since it manages to begin the install process, but fails loading something from it and doesn’t tell you what, I would suggest you to make sure you are connected to your Network before click Install macOS (check the wireless icon on the top right during the USB boot, and if you can open any web site using the provided Safari browser). Any files missing from the USB, even under the beta, can be obtained “on the fly” by the installer from Apple if your system is connected to the network.

 

Which file is missing and why it is missing, I don’t know - there should be an option to view the install log file somewhere (this log is created on the update partition everybody deletes) on the installer screen itself.

Link to comment
Share on other sites

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