Jump to content

[pre-release] macOS Big Sur


3,698 posts in this topic

Recommended Posts

15 hours ago, eSaF said:

I have the strangest phenomenon happening on my rig with this latest update, I just cannot get it to show up on my machine. I say strange because I was abled to D/Load and install all BS Betas both Developers and Public from the beginning but it seems I am stuck on Beta 6. Tried till late in the night and now this morning and the result is unchanged. What am I missing, SIP is fully enabled, I reinstalled Beta 6 again hoping to iron out any anomalies but no change. The config.plist is the latest commit (ver 0.6.2) oppose to the official release (ver 0.6.1) but the machine boots without any panics or quirky outputs so I am baffled, I have included as much info here hoping you guys will toss some ideas my way as to why. @Alex HQuest @Tiem @MorenoAv time you guys earn your pay grade. :hysterical: :hysterical: :hysterical:

config.plist

I got mine to see B7 by resetting NVRAM twice (not sure if once is enough). As soon as I booted back in, no issues pulling down the latest BS.

 

FWIW, there likely won't be any more installers till GM, we are probably going to be running exclusively on OTA updates.

5 hours ago, MorenoAv said:

Well @Alex HQuest

Tried your edited DSDT, and the result is the same... my brightness slider is all grey and "wrinkled" LoL ...

Thanks for your time ...

Captura de ecrã 2020-09-18, às 19.58.58.png

There is nothing to fix here. macOS has never supported third party displays outside of simply enabling picture and sound. They don't support brightness controls. You will either need an Apple display (Thunderbolt, etc.) or the new LG 4-5K displays that have been vetted by Apple to enable the slider.

 

That's just the way macOS goes. Stupid, but go bug Apple.

 

The only workaround to control your display is to use something like https://github.com/fnesveda/ExternalDisplayBrightness which can give you access to brightness controls via your dedicated keyboard keys.

 

With that said, this is just a limitation of the OS. Nothing technically wrong or no way to fix that I'm aware of.

  • Like 2
Link to comment
Share on other sites

2 minutes ago, Tiem said:

I got mine to see B7 by resetting NVRAM twice (not sure if once is enough). As soon as I booted back in, no issues pulling down the latest BS.

 

FWIW, there likely won't be any more installers till GM, we are probably going to be running exclusively on OTA updates.

Judging from the game I had with this one, if that is how it's going to be till GM, then I will stock up on headache pills. :lol:

  • Haha 2
Link to comment
Share on other sites

6 minutes ago, eSaF said:

Judging from the game I had with this one, if that is how it's going to be till GM, then I will stock up on headache pills. :lol:

Resetting NVRAM is pretty trivial. I was glad it was such an easy fix and nothing wrong with the actual EFI.

 

I've noticed lots of new entries as of late. GPUROM, IONVRAM-FORCESYNCNOW-PROPERTY, target-uuid, and then entries for the OTA updates. I'm not sure what's macOS and what's OC at this point. Nor what's garbage and what's required.

 

I used to keep it clean but now have stopped touching it.

 

One thing I did notice was that SU would twitch out. Listing the dev profile but then blinking and coming back without it, then listing that there was an error grabbing updates or there were no updates. That was rampant before the reset, but now, it takes a few seconds to show the profile but doesn't blink it away. So whatever the entries, it looks like SU at least requires some and if they are missing freaks out.

 

With respect the actual conflig.plist, I've pulled out csr entries and keyboard type as those are better left to the OS. Letting OC handle them seems to cause issues (at least for me).

Edited by Tiem
Link to comment
Share on other sites

Important Note: There is an unresolved bug on Beta 6 and Beta 7 you have to open Preferance System Security before starting an installer program or installing kext because otherwise there will be a preferance system error.

  • Like 2
  • Thanks 1
Link to comment
Share on other sites

23 minutes ago, chris1111 said:

Important Note: There is an unresolved bug on Beta 6 and Beta 7 you have to open Preferance System Security before starting an installer program or installing kext because otherwise there will be a preferance system error.

I’ve filed a bug with them on Sep 6. Posted about it here on the forums a few pages ago. There seems to be currently more than 10 reports but still on Open status.

 

A very dirty workaround/“fix”, aside of the panel being open prior to the kext install by the package installer, is for one to play around the software protection database to manually enable the offending kext (hint: under recovery mode, use “spctl” CLI command). PikerAlpha has described this behavior years ago and the information is still available on his blog.

Edited by Alex HQuest
  • Like 1
Link to comment
Share on other sites

1 hour ago, Tiem said:

macOS has never supported third party displays outside of simply enabling picture and sound. They don't support brightness controls. You will either need an Apple display (Thunderbolt, etc.) or the new LG 4-5K displays that have been vetted by Apple to enable the slider.

Are you saying this is a behavior for non-laptops? Because the slider on my Dell laptop works just fine (and so are the Fn keys), and I was able to “reproduce” the brightness slider on my desktop computer, as seen by MorenoAV, by adding a fake ALS0 device on my iHack19.1, complete with the kexts loading and binding to the correct device. The screens are regular Dell 24” DP devices. I did made no further progress though as my PSU died and new ones are still way overpriced... :( so for now I’m just playing with my laptop and the real Apple gear.

Link to comment
Share on other sites

2 hours ago, polyzargone said:


@fusion71au

 

I have deleted all snapshots as per your guide but now I can’t update through OTA because macOS complains about not being booted from a sealed snapshot.

 

I tried to bless my /Volume/Big_Sur in recovery but it didn’t solved the issue.

 

Any idea to fix that?

 

Unfortunately you will have to wait until full installer available to perform upgrade install.  Looks like OTA upgrade process has hard coded the sealed snapshot requirement :(.

 

 

2 hours ago, Donw35 said:

clock settings are in Dock and Menu Bar

 

Thanks.  Found the settings now moved to System Preferences/Dock and Menu Bar...

Spoiler

675313296_DockMenuBar.png.c11a81221311dafbe5f88db3a2fe776b.png

 

  • Like 2
Link to comment
Share on other sites

4 hours ago, fusion71au said:

 

Unfortunately you will have to wait until full installer available to perform upgrade install.  Looks like OTA upgrade process has hard coded the sealed snapshot requirement :(.

 

 

 

Thanks.  Found the settings now moved to System Preferences/Dock and Menu Bar...

  Hide contents

675313296_DockMenuBar.png.c11a81221311dafbe5f88db3a2fe776b.png

 

Holy smokes and the love of all things good!!!!!!!!!!!!!!!! As simple as that!!!!!!!!!!!!!! Thank you, thank you!!!!!!!!!!!!!!!!!! -  So I wonder why two settings? Even though the one in System Preferences is semi redundant.

  • Like 1
  • Haha 1
Link to comment
Share on other sites

Any body using the script fie  installScript_1016fullapp to download  BS I highly recommend they start it with sudo -s

as sudo only has a limited time.

Edited by STLVNUB
  • Like 1
  • Thanks 1
Link to comment
Share on other sites

Thanks @Alex HQuest, for your efforts, but now we know better that is macOS intended behavior I can rest my quest to make it work as in the first beta. 

It's stupid and irksome but it's the weirdness of macOS BS, at their best...

I rest my case, and put the guitar in the bag ... LoL

To all you guys my eternal gratitude... 

  • Haha 1
Link to comment
Share on other sites

My recent rant about Apple fixing one thing and breaking another was unfounded, the only thing that was broken was my eyesight and inability to search properly for the Clock/Date settings which now resides in the Dock & Menu bar :angel:. One of the noticeable fixes in this Beta I am happy with is the correction of the flickering BS Disk Icon in 'System Preferences/Startup Disk menu.

Spoiler

855843885_Screenshot2020-09-19at09_04_02.png.773d365e43d317e5b6fa29bc08d2f5fc.png

 

  • Like 2
Link to comment
Share on other sites

9 hours ago, Alex HQuest said:

I’ve filed a bug with them on Sep 6. Posted about it here on the forums a few pages ago. There seems to be currently more than 10 reports but still on Open status.

 

A very dirty workaround/“fix”, aside of the panel being open prior to the kext install by the package installer, is for one to play around the software protection database to manually enable the offending kext (hint: under recovery mode, use “spctl” CLI command). PikerAlpha has described this behavior years ago and the information is still available on his blog.

Yea I also noted that at the same time as you because I perform tests on programs and I realized it quickly

  • Like 1
Link to comment
Share on other sites

10 hours ago, eSaF said:

My recent rant about Apple fixing one thing and breaking another was unfounded, the only thing that was broken was my eyesight and inability to search properly for the Clock/Date settings which now resides in the Dock & Menu bar :angel:. One of the noticeable fixes in this Beta I am happy with is the correction of the flickering BS Disk Icon in 'System Preferences/Startup Disk menu.

  Hide contents

855843885_Screenshot2020-09-19at09_04_02.png.773d365e43d317e5b6fa29bc08d2f5fc.png

 

HP ProBook 4540s, it does.

But not flickering on z390 Aorus Master.

Edited by Stefanalmare
Link to comment
Share on other sites

20 hours ago, eSaF said:

C'est la même chose sur mon wifi Z390 Pro, donc vous n'êtes pas seul, vous avez toujours le sentiment que cette fonctionnalité concerne davantage les ordinateurs portables mais pas absolument sûr de cela, cela n'a jamais fonctionné dans les BS Betas précédentes ou je n'ai jamais remarqué si cela fonctionnait ou ne pas. D'une manière ou d'une autre, je ne pense pas que cette mise à jour soit directement sur mon système car dans la précédente, j'avais l'horloge, le jour, le mois et la date, mais maintenant c'est tout ce que je peux montrer comme sur la photo, plus aucun fuseau horaire supplémentaire comme avant dans «Préférences système / Date et heure».

  Masquer le contenu

2040109747_Screenshot2020-09-18at21_18_54.png.54e8f9f15fe8ae692330d95afbc2ef17.png1182559506_Screenshot2020-09-18at21_26_47.png.5f3a96261a1f97e6ea79cf5390d87ec4.png

 

Update 

version error!
sorry for my mistake !

 

Clean Install BigSur Beta 7 = Print

Update BigSur Beta6 -> a beta 7 = Problem ! 

 

Spoiler

 

1127036834_Capturedecran2020-09-19a15_54_47.thumb.png.b879a6dca50dce46a6870362a5c308f9.png

Edited by PG7
Link to comment
Share on other sites

7 minutes ago, Matgen84 said:

Hi All Guys

 

I can't update Beta 6 to B7 using Software Update despite Developer access.

Any solutions ?

 

  Hide contents

430213240_Capturedcran2020-09-1915_57_31.png.e04ba965f21d62bbd4f648df4aeeb0be.png

 

Try cleaning NVRAM a few times as reported by @Tiem he reckoned that method worked for him. Good luck.

  • Thanks 1
Link to comment
Share on other sites

16 minutes ago, Matgen84 said:

Salut tous les gars

 

Je ne peux pas mettre à jour la bêta 6 vers la B7 à l'aide de la mise à jour logicielle malgré l'accès développeur

Des solutions?

 

  Masquer le contenu

430213240_Capturedcran2020-09-1915_57_31.png.e04ba965f21d62bbd4f648df4aeeb0be.png

 

RW = 0x00000000 

Non 0xFF0F0000

Non 0x77080000

Non 0x67000000

Yes 0x00000000 = Update 

  • Thanks 1
Link to comment
Share on other sites

23 minutes ago, PG7 said:

RW = 0x00000000 

Non 0xFF0F0000

Non 0x77080000

Non 0x67000000

Yes 0x00000000 = Update 

 

Thanks. I try it

What is RW ! I don't know

 

EDIT: 0x00000000 = No Update on my Z390 config :cry:

Edited by Matgen84
Link to comment
Share on other sites

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