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

Matgen84
Matgen84
Posted
Posted

@eSaF

I'm a little bit annoying since Beta is published. I can't update from BS Beta 6. I don't understand why: using SWUschitcher, reboot, clear NVRAM, reboot... No succeed
I also try macOSDeveloperBetaAccessUtility: Software Update don't show enrollment.

Two troubleshooting: Software Update don't show enrollment or show it but don't find BS Beta 7. Have a look to screenshot below. Please.

This issue make me crazy

 

Spoiler

1253705477_Capturedcran2020-09-2009_39_32.png.8b7c05478cf31ef24a67440d855fc13d.png

 

Link to comment
Share on other sites
eng_redaesm
eng_redaesm
Posted
Posted
12 minutes ago, Matgen84 said:

I'm a little bit annoying since Beta is published. I can't update from BS Beta 6. I don't understand why: using SWUschitcher, reboot, clear NVRAM, reboot... No succeed
I also try macOSDeveloperBetaAccessUtility: Software Update don't show enrollment.

Two troubleshooting: Software Update don't show enrollment or show it but don't find BS Beta 7. Have a look to screenshot below. Please.

This issue make me crazy

I used this https://github.com/chris1111/Beta-Access-Software-Utility/releases/tag/V1

worked for me

  • Like 1
  • Thanks 2
Link to comment
Share on other sites
eSaF
eSaF
Posted
Posted
10 minutes ago, Blu24 said:

@Matgen84

 

I curious where you got the F11K firmware for your Gigabyte Aorus master motherboard?

Look here -https://www.tweaktownforum.com/- but be aware if you install the wrong version for your board you could cause irreplaceable damage to the board. Please read the 'Cautionary Notes' before downloading and applying any BIOS files. Good luck.

 

MODS - Please remove if against Site Rules.

  • Like 3
Link to comment
Share on other sites
eSaF
eSaF
Posted
Posted (edited)

@eng_redaesm see my post above on a possible fix how to overcome this problem.

 

Guys if you're having trouble with getting the Update to Beta7 notification, cleaning the NVRAM once or twice will possibly trigger the Update message on your machine as reported by member @Tiem.

Edited by eSaF
Link to comment
Share on other sites
eSaF
eSaF
Posted
Posted
5 minutes ago, vmlage said:

@@eSaF can you explain why on Beta 7 (20A5374g) running installScript_110fullapp, GibMacos, and curl, I can only download Beta 6 (20A5364e)

  Reveal hidden contents

904846884_Capturadeecra2020-09-20as10_51_35.thumb.png.6f489430970923f4379d71de3949e133.png

 

 

 

Ok - As far as I know it is as this, all the versions shown in the list are available as Stand Alone downloads, meaning they can be installed on a USB to be used as a fresh installed. Beta7 is not in that list because it is an incremental update (not a full install) so Beta6 must be on the System to be able to get Beta7. Iv'e tried to explain in my ham fisted way as best as possible, hope it's clear to you. :)

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

 

@eSaF thanks for the explanation, but it doesn't fit, there's more into it... yesterday you should still remember I was on 20A5323l after updating from Beta 6 (20A5364e) which isn't, I think, a known Beta version, and still managed to update to Beta 7. Still I recall someone telling the update is about 3 point something Gb whilst mine was 8 something.
Probably someone can help to brighten this. :)

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

 

@eSaF thanks for the explanation, but it doesn't fit, there's more into it... yesterday you should still remember I was on 20A5323l after updating from Beta 6 (20A5364e) which isn't, I think, a known Beta version, and still managed to update to Beta 7. Still I recall someone telling the update is about 3 point something Gb whilst mine was 8 something.
Probably someone can help to brighten this. :)

Ok - Updating to Beta7 may not necessary need to be from Beta6 but as long as any BS Beta is installed on the System. In saying and knowing that, Apple at this stage is not offering Beta7 as a stand alone install (you cannot do a clean/fresh install of Beta7). This is my speculation, at this stage of BS maybe the next one or two Betas Apple will only offer updates like this one until the GM which will be a stand alone install in time for the official release of BS.

Edited by eSaF
  • Like 2
Link to comment
Share on other sites
fusion71au
fusion71au
Posted
Posted (edited)

Hi guys.

 

Just want to confirm the “Recovery” method of installing kexts in Big_Sur/S/L/E and creating a blessed, boot-able APFS snapshot still works in Beta7.  Below is the output from terminal, after booting to Big_Sur Recovery/InstallerUSB, and replacing IO80211Family.kext with an older one from High Sierra to enable wifi on my unsupported IvyBridge Macmini6,2…  

 

Spoiler 

-bash-3.2# csrutil status
System Integrity Protection status: enabled.
-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# nvram csr-active-config
csr-active-config	%7f%08%00%00
-bash-3.2# diskutil list
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk0
   1:                        EFI ⁨EFI⁩                     209.7 MB   disk0s1
   2:                  Apple_HFS ⁨Macintosh HD⁩            119.5 GB   disk0s2
   3:                 Apple_Boot ⁨Recovery HD⁩             650.0 MB   disk0s3
   4:       Microsoft Basic Data ⁨HDD⁩                     815.4 GB   disk0s4
   5:         Microsoft Reserved ⁨⁩                        134.2 MB   disk0s5
   6:       Microsoft Basic Data ⁨BOOTCAMP⁩                63.8 GB    disk0s6
   7:           Windows Recovery ⁨⁩                        532.7 MB   disk0s7

/dev/disk1 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *128.0 GB   disk1
   1:                        EFI ⁨EFI⁩                     209.7 MB   disk1s1
   2:                 Apple_APFS ⁨Container disk2⁩         30.6 GB    disk1s2
                    (free space)                         268.4 MB   -
   3:       Microsoft Basic Data ⁨Windows 10 SSD⁩          97.0 GB    disk1s3

/dev/disk2 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +30.6 GB    disk2
                                 Physical Store disk1s2
   1:                APFS Volume ⁨Macintosh SSD — Data⁩    4.7 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.1 GB    disk2s5

/dev/disk3 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *16.4 GB    disk3
   1:               Windows_NTFS ⁨USB⁩                     14.1 GB    disk3s1
   2:                  Apple_HFS ⁨Recovery HD⁩             2.3 GB     disk3s2

/dev/disk4 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *320.1 GB   disk4
   1:                        EFI ⁨EFI⁩                     209.7 MB   disk4s1
   2:                 Apple_APFS ⁨Container disk6⁩         59.7 GB    disk4s2
   3:       Microsoft Basic Data ⁨MACRIUM Backups⁩         166.4 GB   disk4s3
   4:                 Apple_APFS ⁨Container disk5⁩         53.6 GB    disk4s4
                    (free space)                         268.4 MB   -
   5:                 Linux Swap ⁨⁩                        4.3 GB     disk4s5
   6:       Microsoft Basic Data ⁨⁩                        314.6 MB   disk4s6
   7:           Linux Filesystem ⁨⁩                        35.1 GB    disk4s7

/dev/disk5 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +53.6 GB    disk5
                                 Physical Store disk4s4
   1:                APFS Volume ⁨Catalina - Data⁩         8.6 GB     disk5s1
   2:                APFS Volume ⁨Preboot⁩                 80.7 MB    disk5s2
   3:                APFS Volume ⁨Recovery⁩                731.6 MB   disk5s3
   4:                APFS Volume ⁨VM⁩                      2.1 GB     disk5s4
   5:                APFS Volume ⁨Catalina⁩                11.4 GB    disk5s5

/dev/disk6 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +59.7 GB    disk6
                                 Physical Store disk4s2
   1:                APFS Volume ⁨Big_Sur — Data⁩          8.0 GB     disk6s1
   2:                APFS Volume ⁨Preboot⁩                 366.0 MB   disk6s2
   3:                APFS Volume ⁨Recovery⁩                761.5 MB   disk6s3
   4:                APFS Volume ⁨VM⁩                      1.1 MB     disk6s4
   5:                APFS Volume ⁨Big_Sur⁩                 15.1 GB    disk6s5

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

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

-bash-3.2# diskutil mountDisk disk6s5
Volume(s) mounted successfully
-bash-3.2# mount -uw /Volumes/Big_Sur
-bash-3.2# mv /Volumes/Big_Sur/System/Library/Extensions/IO80211Family.kext /Volumes/Big_Sur/System/Library/Extensions/IO80211Family.orig
-bash-3.2# cp -R /Volumes/Image\ Volume/Kexts/IO80211Family.kext /Volumes/Big_Sur/System/Library/Extensions
-bash-3.2# ls -l /Volumes/Big_Sur/System/Library/Extensions/IO8*
/Volumes/Big_Sur/System/Library/Extensions/IO80211Family.kext:
total 0
drwxr-xr-x@ 7 root  wheel  224 20 Sep 11:01 Contents

/Volumes/Big_Sur/System/Library/Extensions/IO80211Family.orig:
total 0
drwxr-xr-x  7 root  wheel  224  1 Jan  2020 Contents

/Volumes/Big_Sur/System/Library/Extensions/IO80211FamilyV2.kext:
total 0
drwxr-xr-x  7 root  wheel  224  1 Jan  2020 Contents
-bash-3.2# chown -R 0:0 /Volumes/Big_Sur/System/Library/Extensions/IO80211Family.kext && chmod -R 755 /Volumes/Big_Sur/System/Library/Extensions/IO80211Family.kext
-bash-3.2# touch /Volumes/Big_Sur/System/Library/Extensions && kmutil install --volume-root /Volumes/Big_Sur --update-all --force
checking collections...
Warning: com.apple.driver.KextExcludeList was not found!
considering release out-of-date because of --force
rebuilding release collections: boot, system
rebuilding release collections:
	boot kernel collection
	system kext collection
rebuilding local auxiliary collection
kmutil done
-bash-3.2# /Volumes/Big_Sur/usr/sbin/kcditto 
Copying deferred prelinked kernels in /Volumes/Big_Sur...
/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/kext_tools/kext_tools-692.40.5/kc_staging.m.279: Encountered error while inspecting path: Error Domain=NSCocoaErrorDomain Code=260 "The folder “PrelinkedKernels” doesn’t exist." UserInfo={NSFilePath=/Volumes/Big_Sur/Library/Apple/System/Library/PrelinkedKernels, NSUserStringVariant=(
    Folder
), NSUnderlyingError=0x6000037aca80 {Error Domain=NSOSStatusErrorDomain Code=-43 "fnfErr: File not found"}}
/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/kext_tools/kext_tools-692.40.5/kc_staging.m.279: Encountered error while inspecting path: Error Domain=NSCocoaErrorDomain Code=260 "The folder “PrelinkedKernels” doesn’t exist." UserInfo={NSFilePath=/Volumes/Big_Sur/Library/Apple/System/Library/PrelinkedKernels, NSUserStringVariant=(
    Folder
), NSUnderlyingError=0x6000037a40f0 {Error Domain=NSOSStatusErrorDomain Code=-43 "fnfErr: File not found"}}
Copying KCs in /Volumes/Big_Sur...
System Volume UUID: 4C48C4E5-CD41-47BC-BD2C-08C53A659C7E
Volume Group UUID: 1CB19FEA-D19B-32A7-BC50-80084D7DA75F
Preboot disk: /dev/disk6s2
Preboot volume: /Volumes/Preboot
Copying: /Volumes/Big_Sur/System/Library/KernelCollections/BootKernelExtensions.kc.elides -> /Volumes/Preboot/1CB19FEA-D19B-32A7-BC50-80084D7DA75F/boot/System/Library/KernelCollections
Copying: /Volumes/Big_Sur/System/Library/KernelCollections/BootKernelExtensions.kc -> /Volumes/Preboot/1CB19FEA-D19B-32A7-BC50-80084D7DA75F/boot/System/Library/KernelCollections
Copying: /Volumes/Big_Sur/System/Library/PrelinkedKernels/immutablekernel -> /Volumes/Preboot/1CB19FEA-D19B-32A7-BC50-80084D7DA75F/System/Library/PrelinkedKernels
Copying: /Volumes/Big_Sur/System/Library/PrelinkedKernels/prelinkedkernel -> /Volumes/Preboot/1CB19FEA-D19B-32A7-BC50-80084D7DA75F/System/Library/PrelinkedKernels
-bash-3.2# bless --folder /Volumes/Big_Sur/System/Library/CoreServices --bootefi --create-snapshot
-bash-3.2# reboot

1567981743_BigSurBeta7_20A5374gonMacmini62.thumb.png.b9723d380718ca346d8762f121e620ae.png

 

I now recommend this method over deleting APFS snapshots from Recovery and then installing kexts while booted in the main Big_Sur volume (since a sealed APFS snapshot is a necessary pre-requisite for an automatic OTA Software Update).

Also noticed the NVRAM variable for disabled authenticated root SIP in Beta7 has changed from csr-active-config w%08%00%00 to %7f%08%00%00.

 

 

5 hours ago, Matgen84 said:

@eSaF

I'm a little bit annoying since Beta is published. I can't update from BS Beta 6. I don't understand why: using SWUschitcher, reboot, clear NVRAM, reboot... No succeed
I also try macOSDeveloperBetaAccessUtility: Software Update don't show enrollment.

Two troubleshooting: Software Update don't show enrollment or show it but don't find BS Beta 7. Have a look to screenshot below. Please.

This issue make me crazy

 

  Reveal hidden contents

1253705477_Capturedcran2020-09-2009_39_32.png.8b7c05478cf31ef24a67440d855fc13d.png

 

 

@Matgen84,


IIRC, from a clean installed Beta6 using the full installer app, the Seed Program was initially set to public “Beta Program Members”. 

 

@cvad’s SWUSwitcher utility enabled me to change to the “Developer Program Members” but I had to click the “Set” button a few times before the change stuck.  Then ran System Preferences/Software Update to search for new updates (I had to do this a few times over 5 minutes before the delta update to Beta7 eventually showed up - don't accept the full installer download as I believe this will only download Beta6 at the moment, if anything).

Edited by fusion71au
  • Like 4
  • Thanks 1
Link to comment
Share on other sites
htanh034
htanh034
Posted
Posted
On 9/9/2020 at 8:58 PM, Alex HQuest said:

Workaround: If you open the Security & Privacy pane before the application install is started, it will be auto refreshed during the install process and it allows you to click the Allow extension button.

Beta 7 not fix problem. Everyone fixed it ?. it not allow apps on privacy :wallbash::wallbash:

 

Link to comment
Share on other sites
analise
analise
Posted
Posted

Hi,

 

Needing some help!

After some testing and with some luck, I manage to restore an image(Beta 5) to an ssd internal disk, boot and complete the installation.

Now I was trying to update, but even through OTA or full installation over, the system always reboots, after de 12 minutes remaining at the full installation or after reboot over the OTA update.

I imagine that as something to do with the snapshot. I attach an image of the apfs volumes of the ssd.

Can anyone give me a clue of what to do?

Thanks!

 

Screenshot 2020-09-20 at 14.56.26.png

Link to comment
Share on other sites
eSaF
eSaF
Posted
Posted
2 hours ago, analise said:

Hi,

 

Needing some help!

After some testing and with some luck, I manage to restore an image(Beta 5) to an ssd internal disk, boot and complete the installation.

Now I was trying to update, but even through OTA or full installation over, the system always reboots, after de 12 minutes remaining at the full installation or after reboot over the OTA update.

I imagine that as something to do with the snapshot. I attach an image of the apfs volumes of the ssd.

Can anyone give me a clue of what to do?

Thanks!

 

Screenshot 2020-09-20 at 14.56.26.png

I have a plausible theory as to why the update failed, somehow the Snapshot was not restored in the Backup. We now know OTA updates will fail if it cannot find a previous Snapshot. Why your system failed to restore the Snapshot also is questionable, it can't be an intentional action by Apple, surely that would make 'Time Machine' pointless, so at this point it maybe a BS Bug or a speculative theory on my part.

  • Like 1
Link to comment
Share on other sites
analise
analise
Posted
Posted
6 minutes ago, eSaF said:

I have a plausible theory as to why the update failed, somehow the Snapshot was not restored in the Backup. We now know OTA updates will fail if it cannot find a previous Snapshot. Why your system failed to restore the Snapshot also is questionable, it can't be an intentional action by Apple, surely that would make 'Time Machine' pointless, so at this point it maybe a BS Bug or a speculative theory on my part.

 

Yes, I think you have a point there, but that would apply to the OTA update, right? The thing here is that I can't do a full install over it also. Maybe is the hack system that I am using, something about the USB ports that are legacy usb2. I can't even boot from a usb stick, only from an internal disk, that's why a made an image restore in the first place.

But after that the system is working very well, the problem is updating, or will have t wait for someone to post a pre-install image to restore.

Thanks. 

Link to comment
Share on other sites
HenryV
HenryV
Posted
Posted

Anyone have working Atheros 9565 wifi  kexts/firmware for BS?

 

NGFF m.2 card/Dell 1707.

 

Shows in menu bar as searching networks but not finding.

.

What do I need to get this working?  Seem to have seen a post recently.

 

Please message with details for open core config.

 

Thank you.

Link to comment
Share on other sites
Tiem
Tiem
Posted
Posted
16 hours ago, eSaF said:

Ok - Updating to Beta7 may not necessary need to be from Beta6 but as long as any BS Beta is installed on the System. In saying and knowing that, Apple at this stage is not offering Beta7 as a stand alone install (you cannot do a clean/fresh install of Beta7). This is my speculation, at this stage of BS maybe the next one or two Betas Apple will only offer updates like this one until the GM which will be a stand alone install in time for the official release of BS.

It does. You need to be on beta 6 to update to 7. And there is no full installer for 7. Which means that you must update to BS beta 6 from any previous version and then pull the beta 7 from OTA.

 

Anyone claiming otherwise is wrong and anyone wondering if this is true, it is. Stop already. This is how it’s going to be till likely the GM as we get closer to final.

 

Please stop asking as the same questions over and over :wallbash:

  • Like 3
  • Thanks 1
  • Haha 1
Link to comment
Share on other sites
vmlage
vmlage
Posted
Posted (edited)
4 hours ago, Tiem said:

It does. You need to be on beta 6 to update to 7. And there is no full installer for 7. Which means that you must update to BS beta 6 from any previous version and then pull the beta 7 from OTA.

 

Anyone claiming otherwise is wrong and anyone wondering if this is true, it is. Stop already. This is how it’s going to be till likely the GM as we get closer to final.

 

Please stop asking as the same questions over and over :wallbash:

@Tiem So maybe you can explain how I did it...?

From Beta 6 (20A5364e) to Beta ?? (20A5323l) and thanks to @eSaF advice, reset NVRAM and update to Beta 7 (20A5374g).

 

Update: 20A5323l is Beta 3

 

I keep making the same question, how is this still possible? beta6 to beta3 and directly to beta7

Edited by vmlage
  • Confused 1
Link to comment
Share on other sites
eSaF
eSaF
Posted
Posted (edited)

@vmiage - Bro it's obviously a question only you can answer if you managed to jump from Beta3 directly to Beta7. So in conclusion I would say congratulation on achieving the update to the latest after having a problem now let us move on to something more constructive and away from the why and the wherefore conversation. :angel: 

Edited by eSaF
  • 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...