Jump to content
3390 posts in this topic

Recommended Posts

@Cyberdevs Yeah, I think so, too! :D Thanks for the info! Didn't know that.

 

Quick question (to everyone): do you guys also experience delays showing the Volume and Wifi/Network controls in the menubar? Meaning you click the icon aaand..wait. :)) Not a lot. Only a few seconds or so. But it's not instantaneously like it was with Catalina and pretty much every other MacOS version I've tried before that.

 

I suppose this could also be a bug somewhere, but it doesn't occur with my MBP so...I guess it's probably specific to our "custom" setup. I'm only curious if anyone else encountered this issue.

  • Like 1
[mention=1011040]Cyberdevs[/mention] Yeah, I think so, too!  Thanks for the info! Didn't know that.
 
Quick question (to everyone): do you guys also experience delays showing the Volume and Wifi/Network controls in the menubar? Meaning you click the icon aaand..wait. :)) Not a lot. Only a few seconds or so. But it's not instantaneously like it was with Catalina and pretty much every other MacOS version I've tried before that.
 
I suppose this could also be a bug somewhere, but it doesn't occur with my MBP so...I guess it's probably specific to our "custom" setup. I'm only curious if anyone else encountered this issue.

I had that delay in the menu bar when my wifi was not functioning. After getting wifi working it’s as quick as ever.


Sent from my iPhone using Tapatalk
  • Like 1
2 minutes ago, arsradu said:

@Cyberdevs Yeah, I think so, too! :D Thanks for the info! Didn't know that.

 

Quick question (to everyone): do you guys also experience delays showing the Volume and Wifi/Network controls in the menubar? Meaning you click the icon aaand..wait. :)) Not a lot. Only a few seconds or so. But it's not instantaneously like it was with Catalina and pretty much every other MacOS version I've tried before that.

 

I suppose this could also be a bug somewhere, but it doesn't occur with my MBP so...I guess it's probably specific to our "custom" setup. I'm only curious if anyone else encountered this issue.

You're welcome man,

Yeah the delay happens to me as well, the first beta was way more responsive but the second beta is laggy, to be honest I was really impressed with the first beta's performance but this release well meh, only time will tell if that is a bug or it is how it's gonna be with the next releases.

  • Like 2
1 minute ago, SavageAUS said:

I had that delay in the menu bar when my wifi was not functioning. After getting wifi working it’s as quick as ever.
Sent from my iPhone using Tapatalk

Yep, I don't have Wifi on my rig, so I would expect the system to be "confused" about that. :))) But the volume controls... I don't know. Those were working properly before. There's no delay when pressing the dedicated volume up/volume down keys to adjust the volume. But if you try to do it from the menubar, there's a delay.

 

As Cyber also said, I guess we'll see. :) Thank you very much for sharing your experience. My guess (and it's only a guess) is that this could be related to the new Kernel Collections feature. I could be wrong though... So yeah, we'll see what the future holds. So far so good. Really good job @acidanthera team.

  • Like 1
38 minutes ago, arsradu said:

@Cyberdevs Yeah, I think so, too! :D Thanks for the info! Didn't know that.

 

Quick question (to everyone): do you guys also experience delays showing the Volume and Wifi/Network controls in the menubar? Meaning you click the icon aaand..wait. :)) Not a lot. Only a few seconds or so. But it's not instantaneously like it was with Catalina and pretty much every other MacOS version I've tried before that.

 

I suppose this could also be a bug somewhere, but it doesn't occur with my MBP so...I guess it's probably specific to our "custom" setup. I'm only curious if anyone else encountered this issue.

Volume and Wifi/Network controls in the menubar shows instantly. No delay :thumbsup_anim:

  • Like 1

@arsradu

I forgot to mention that I'm using big sur on a conventional HDD and the lags are expected but the first beta was also setup on the same rig and the performance was better, using big sur on the SSD is not that bad though.

  • Like 2
1 minute ago, d5aqoep said:

It works but Clover log says port limit reached. So need new kext patch.

The 15 port limit is enforced since Catalina. This is not new to Big Sur. You should use it to configure your system to be under 15 ports as per Apple’ specification.

  • Like 1
  • Haha 1
36 minutes ago, Alex HQuest said:

The 15 port limit is enforced since Catalina. This is not new to Big Sur. You should use it to configure your system to be under 15 ports as per Apple’ specification.

Its 15 port limit per controller, not the entire system.

  • Like 2
1 minute ago, d5aqoep said:

Hi Pavo, can you help me to enable USB 3 ports on my MSI X299 system with DP2 installed?

USB port mapping hasn't changed with BigSur. So.... if you mapped your ports correctly, your USB 3 ports should work without issues.

  • Like 1

@lvs1974 thanks to support to work wifi in Big Sur 

but AirportBrcmFixup.kext still persist problem to finding the network 

when i click wifi icon it is not scanning network automatically

this is work only in system preference

i attached blow

Spoiler
Spoiler

677412457_ScreenShot2020-07-19at8_25_30PM.jpg.2a5dbb24c6016594205793923165641a.jpg

1113864092_ScreenShot2020-07-19at8_25_01PM.jpg.a51b9f8c0daa9edaa81f55afacf8a30f.jpg

 

 

 

  • Like 1
11 minutes ago, ameenjuz said:

@lvs1974 thanks to support to work wifi in Big Sur 

but AirportBrcmFixup.kext still persist problem to finding the network 

when i click wifi icon it is not scanning network automatically

this is work only in system preference

i attached blow

  Hide contents
  Reveal hidden contents

677412457_ScreenShot2020-07-19at8_25_30PM.jpg.2a5dbb24c6016594205793923165641a.jpg

1113864092_ScreenShot2020-07-19at8_25_01PM.jpg.a51b9f8c0daa9edaa81f55afacf8a30f.jpg

 

 

 

Thats not a kext injection issue, that's how wifi works in BigSur, you scan networks in the menu bar or in Network section of System Preferences.

 

Screenshot 2020-07-19 15.19.44.png

  • Like 1
  • Thanks 1

@Pavo 

1 hour ago, Pavo said:

Thats not a kext injection issue, that's how wifi works in BigSur, you scan networks in the menu bar or in Network section of System Preferences

thanks pavo for information i was wrong

Spoiler

2083296217_ScreenShot2020-07-19at10_39_50PM.jpg.05bd36f380686522c71d7ff31cbc9db1.jpg

 

interrupting phase3 installation to avoid snapshot and sealing but after installation still macOS Installer icon exist in boot menu

how to remove this i already reset nvram not removing icon

Spoiler

19195409.thumb.png.126ca02dbf75a70e00b3c42ab0d82ff1.png

 

  • Like 1
1 hour ago, ameenjuz said:

interrupting phase3 installation to avoid snapshot and sealing but after installation still macOS Installer icon exist in boot menu

how to remove this i already reset nvram not removing icon

  Reveal hidden contents

19195409.thumb.png.126ca02dbf75a70e00b3c42ab0d82ff1.png

 

Well.... interrupting an installation phase that shouldn't be interrupted is going to have unforeseen consequences.

Edited by Pavo
  • Like 2
  • Thanks 1

@Pavo yep, I agree. I had the same result when I couldn't complete the installation (due to reboots). Personally I don't see it as a problem. It's kind of how it's supposed to work, for what I'm concerned. And...now that I was able to fix whatever was holding it back and finish the installation successfully, the "installer" volume is gone from the boot picker and I've only got the main BigSur boot volume and the corresponding Recovery partition.

 

@ameenjuz Sorry, I haven't followed along with all the discussion. But...I'm curious, is the system bootable at this stage? I mean, if you try to select BigSur, can you successfully boot it? Cause if you can...then I guess it's probably only a matter of cleaning up the installation files. And about that, aren't the installation files placed onto the root of the system partition with Big Sur? If so, have you tried deleting them? I think they should be in a folder called "macOS install data". I'm sorry if I'm talking non-sense. Just trying to help. So please forgive me if I'm wrong.

Edited by arsradu
2 hours ago, ameenjuz said:

interrupting phase3 installation to avoid snapshot and sealing but after installation still macOS Installer icon exist in boot menu

how to remove this i already reset nvram not removing icon

 

15 minutes ago, arsradu said:

 

@ameenjuz it's probably only a matter of cleaning up the installation files.

 

Just mount the Big_Sur Preboot volume, then delete/remove the boot.efi file from the hidden folder /System/Volumes/Preboot/UUID/com.apple.installer...

 

eg

fusion71au@fusion71aus-iMac ~ % diskutil list
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *53.7 GB    disk0
   1:                        EFI ⁨EFI⁩                     209.7 MB   disk0s1
   2:                 Apple_APFS ⁨Container disk2⁩         53.5 GB    disk0s2

/dev/disk1 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *53.7 GB    disk1
   1:                        EFI ⁨EFI⁩                     209.7 MB   disk1s1
   2:                 Apple_APFS ⁨Container disk3⁩         53.5 GB    disk1s2

/dev/disk2 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +53.5 GB    disk2
                                 Physical Store disk0s2
   1:                APFS Volume ⁨macOS — Data⁩            5.2 GB     disk2s1
   2:                APFS Volume ⁨Preboot⁩                 83.7 MB    disk2s2
   3:                APFS Volume ⁨Recovery⁩                528.8 MB   disk2s3
   4:                APFS Volume ⁨VM⁩                      1.1 MB     disk2s4
   5:                APFS Volume ⁨macOS⁩                   11.0 GB    disk2s5

/dev/disk3 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +53.5 GB    disk3
                                 Physical Store disk1s2
   1:                APFS Volume ⁨Big_Sur — Data⁩          3.1 GB     disk3s1
   2:                APFS Volume ⁨Preboot⁩                 320.4 MB   disk3s2
   3:                APFS Volume ⁨Recovery⁩                833.9 MB   disk3s3
   4:                APFS Volume ⁨VM⁩                      1.1 MB     disk3s4
   5:                APFS Volume ⁨Big_Sur⁩                 13.7 GB    disk3s5

fusion71au@fusion71aus-iMac ~ % sudo diskutil mount disk3s2
Password:
Volume Preboot on disk3s2 mounted
fusion71au@fusion71aus-iMac ~ % ls -l /System/Volumes/Preboot 
total 0
drwxr-xr-x  12 fusion71au  staff  384 18 Jul 19:39 B6AB1C78-8039-45DD-B98A-4DF87261D0BA
fusion71au@fusion71aus-iMac ~ % ls -l /System/Volumes/Preboot/B6AB1C78-8039-45DD-B98A-4DF87261D0BA
total 0
drwxr-xr-x  87 fusion71au  staff  2784 18 Jul 17:22 Firmware
drwxr-xr-x   4 root        wheel   128 18 Jul 18:53 Library
drwxr-xr-x   4 root        staff   128 18 Jul 18:59 PreLoginData
drwxr-xr-x   4 fusion71au  staff   128 18 Jul 19:40 System
drwxr-xr-x   3 fusion71au  staff    96 18 Jul 17:22 boot
d-w-r-xr--  80 root        admin  2560 20 Jul 08:32 com.apple.installer
drwxr-xr-x   3 root        wheel    96 18 Jul 17:35 restore
drwxr-xr-x   3 fusion71au  staff    96 18 Jul 17:22 usr
drwxr-xr-x   3 root        wheel    96 18 Jul 17:29 var
fusion71au@fusion71aus-iMac ~ % sudo mv /System/Volumes/Preboot/B6AB1C78-8039-45DD-B98A-4DF87261D0BA/com.apple.installer/boot.efi /Users/fusion71au/Downloads/Backups
Password:

 

Spoiler

418534181_BigSurPrebootInstallerdeleteboot_efi.thumb.png.091b0f05012a628e63dd6d27f5653a8a.png

 

Press <Command><Shift><.> to show hidden files in Finder.

  • Like 4
  • Thanks 1
On 7/18/2020 at 9:29 AM, gengik84 said:

Or...

Eg: if you don't have separate drive for modify UpdateOption.plist
After first phase, boot installer again, open terminal and write


/usr/libexec/PlistBuddy -c "Set DoNotSeal true" /volumes/bigsur/"macos install data"/UpdateOptions.plist 

reboot

 

note: change /volumes/bigsur with your /volumes/disk_name

@fusion71au thanks great guide  worked

you are always understanding my point that what i want 

now i m going to testing above procedure of this @gengik84 to disabling the sealing only

after that deleting snapshot

  • Like 1
5 hours ago, ameenjuz said:

@fusion71au thanks great guide  worked

you are always understanding my point that what i want 

now i m going to testing above procedure of this @gengik84 to disabling the sealing only

after that deleting snapshot

When opting for DoNotSeal true, for some reason, I cannot delete snapshot following @fusion71au's great guide.  The system always returns with operation not permitted when trying to tag snapshot.  Please do let me know, how yours goes. Thanks.

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