Contribute
Register

X299 Big Sur Support

Status
Not open for further replies.
Yeah, that's exactly what's happening - it is literally booting from the snapshot. Like that Howard guy said: It doesn’t matter about the volume: it’s unmounted, and therefore inaccessible. It’s the snapshot which is the active system, and all that you should worry about.

If you reboot into recovery and then modify files on the System volume, then reboot, nothing will have changed. You first have to re-snapshot the System volume after you've changed something, and set the new snapshot as the one that is booted from.
Yes, It also means that your Mac or Hackintosh knows the exact layout of your system volume, thus on startup all resources are preloaded for faster response and better experience.
 
@apfelnico found the solution for the boot issues on big sur and the error code 97.

"It seems Apple's new USB-ASMedia connection is broken. We use "ASMedia2142" on our boards, but Apple's driver is for "ASMedia3142". This driver runs first, then it doesn't run anymore on further reboots. Then the higher-level driver takes over, and it doesn't work with our chip. But the old working "AppleUSBXHCIPCI" is still in the system, which is included with Catalina. We can fix this by loading this Kext for the ASMedia controllers."
it's worked for me. thanks.
asus z270g built-in ASMedia 3.1 Controller (2142).
 
I installed a new macOS Big Sur.

Now it works normally.
 

Attachments

  • Screen Shot 2563-12-02 at 23.41.17.png
    Screen Shot 2563-12-02 at 23.41.17.png
    433.3 KB · Views: 81
  • Screen Shot 2563-12-02 at 23.41.26.png
    Screen Shot 2563-12-02 at 23.41.26.png
    808.1 KB · Views: 96
  • Screen Shot 2563-12-02 at 23.43.57.png
    Screen Shot 2563-12-02 at 23.43.57.png
    67.1 KB · Views: 92
  • 120048352_2609075202739021_1953227351010039608_n.jpg
    120048352_2609075202739021_1953227351010039608_n.jpg
    76.4 KB · Views: 79
  • 119904280_2609076199405588_8552663732605128492_n.jpg
    119904280_2609076199405588_8552663732605128492_n.jpg
    57.2 KB · Views: 72
Did you change anything on your EFI or config.plist ?
 
Have anyone else encountered the need of approving things more than once?

For example, every now and then, at a reboot, some of my launch agents needs to get approved. altough it's been approved before. Not sure what's going on to be honest. I'm not changing anything in my config when this happens.
 

Attachments

  • Screenshot 2020-12-03 at 11.25.36.png
    Screenshot 2020-12-03 at 11.25.36.png
    100.8 KB · Views: 71
Have anyone else encountered the need of approving things more than once?

For example, every now and then, at a reboot, some of my launch agents needs to get approved. altough it's been approved before. Not sure what's going on to be honest. I'm not changing anything in my config when this happens.

this may have been fixed in 11.1.
I don’t personally use LuLu but I use Little snitch 5.0.4 instead.

apple has completely changed the way these things work and are now network filters instead of root level kexts.
 
this may have been fixed in 11.1.
I don’t personally use LuLu but I use Little snitch 5.0.4 instead.

apple has completely changed the way these things work and are now network filters instead of root level kexts.

i really think it is a OS bug as well, cause it never happened before beta 6 or 7

i’ll update and see. Anyone who’s on 11.1 beta and find it stable?
 
i really think it is a OS bug as well, cause it never happened before beta 6 or 7

i’ll update and see. Anyone who’s on 11.1 beta and find it stable?
I’m on 11.1 public beta and it feels stable. Should be a couple of more weeks and we will get the final update.

I normally wouldn't even recommend betas or even .0 releases of macOS, but I feel comfortable recommending Big Sur in general.

But to be honest I haven't pushed Big Sur a lot yet in real world workflows, very lightly so far, but I can't give my 100% recommendation yet, but I do feel good about using it day to day.
 
Last edited:
Is anyone else running into this? Trying to fix the PCI tab in System Report for GPUs but the Audio Device is duplicating the Display device information. The path looks to be correct in DeviceProperties.

Screen Shot 2020-12-03 at 15.08.30.png

Screen Shot 2020-12-03 at 15.10.19.png
 
Status
Not open for further replies.
Back
Top