Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 07/19/2020 in all areas

  1. @arsradu Hi there, In my experience only resetting the NVRAM and erasing the hard disk were necessary, the booter-fileset-basesystem and booter-fileset-kernel are not needed anymore with the latest releases of OC they were only needed when you wanted to boot from a preinstalled version of Big Sur. But the reboot issue is now happens with Clover's latest releases (5120) and I think (fingers crossed) it will be resolved soon.
    3 points
  2. Freaking finally! Done. Installed. God dang it! Looks like you were right. It was only a matter of time...and perseverance. :)) Now, the question is: what was different? Well, quite a few things actually. 1. switched back to VirtualSMC from FakeSMC. Same exact version as before. So still up to date. But no other difference there. 2. erased the volume I wanted to install Big Sur on, just to make sure there's no dirt from previous attempts (I believe this might have made the entire difference here). 3. cleared NVRAM right before booting into the installer 4. added corresponding NVRAM info (boot-args, UIScale, all that) to NVRAM -> Delete, as shown in the sample.plist. Previously I didn't have it. Didn't cause any issues with Catalina, but I guess it could be different with Big Sur. I'm still not sure how exactly is this actually working, but I'll try to read a bit more about it. Cause, as a normal user, I find it a bit confusing. 5. added run-efi-updater to NVRAM (7C436110-AB2A-4BBB-A880-FE41995C9F82) and set it to "No" (string). 6. added rtc-blacklist to NVRAM (4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102) but left it empty for now. 7. set csr-active-config in NVRAM to FF0F0000 One thing to note is that, in my attempts to make it boot, I also added booter-fileset-basesystem and booter-fileset-kernel to NVRAM. But that actually made things worse. It wouldn't even reach the first installer screen anymore. So, at least in my particular case, removing that also made a difference. And there were quite a lot of restarts during this installation (about 5 if I'm not mistaken). Anyway, it's all good now. Thank you very much for your support.
    3 points
  3. 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: Press <Command><Shift><.> to show hidden files in Finder.
    2 points
  4. Well.... interrupting an installation phase that shouldn't be interrupted is going to have unforeseen consequences.
    2 points
  5. USB port mapping hasn't changed with BigSur. So.... if you mapped your ports correctly, your USB 3 ports should work without issues.
    2 points
  6. I am testing Legacy issues with @vit9696 and I had the same issue with SL. He told me to use the OsxFatBinaryDrv.efi driver from Clover to boot FAT binaries. Now SL boots fine via OC. Eventually FAT binary support will make into OC (low priority) and in the meantime OsxFatBinaryDrv.efi works fine.
    2 points
  7. Its 15 port limit per controller, not the entire system.
    2 points
  8. @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.
    2 points
  9. 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.
    2 points
  10. Clover Configurator New in Version 5.15.0.0. added new Quirks section I'm testing it with big sur
    2 points
  11. a) Thank you for adding those @headkaze ! b) Please kindly add support for the working IntelBluetoothFirmware kext? Main repo is here: https://github.com/OpenIntelWireless/IntelBluetoothFirmware This BTLE 5.0 module is integrated to the Intel AC-Wireless 9560 controller and works great on Mojave. I asked the developers to also add FirmwareLoaded so you can detect it in Hackintool, please follow/join the thread if you can: https://github.com/OpenIntelWireless/IntelBluetoothFirmware/issues/142 c) Please add to your to-do list the kext-check support for the soon-to-be-officially-announce Intel AC-Wireless driver: https://github.com/OpenIntelWireless/itlwm Kext has been stable in late builds and works great (emulates a LAN device as it's easier to implement, needs HeliPort to control the device: https://github.com/OpenIntelWireless/HeliPort for those interested) When you can, of course. Thanks mate.
    2 points
  12. @arsradu, That screen is the screen of death, it was what happened to me in the first try at install Big Sur beta 1 ... after that with the new commits of OpenCore and new kexts never happened again... but you can do it I know it's a question of time...
    2 points
  13. press ctrl+macos entry number key 나의 SM-N960N 의 Tapatalk에서 보냄
    2 points
  14. Hi @arsradu, how are you my friend? From my limited knowledge the boot.arg vsmcgen=1 isn't necessary anymore with last commits from OpenCore and new kexts, today I installed macOS Big Sur in another ssd that I own and all went well I upload my config.plist for you to see if it helps. Good luck config.plist
    2 points
  15. Disable authenticated root SIP by setting csr-active-config to 77080000 in OC's config.plist, then reset NVRAM through the OC boot menu. Alternatively, with blank csr-active-config setting, boot to Recovery/Big Sur Installer and run csrutil disable, then csrutil authenticated-root disable in terminal Need to also disable APFS snapshots. I posted a guide several pages ago on how to do this and also replace/installing old kexts. Good Luck!
    2 points
  16. @Pavo thanks pavo for information i was wrong i 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
    1 point
  17. Tested commit 762eac695, stable boot 10.15.6, but... ... for experiment I enabled all Quirks, - still boot ok! Then uncheck all Quirks, - boot ok again! So, its looking that Quirk settings have no effect??? Files.zip
    1 point
  18. @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
    1 point
  19. 1 point
  20. 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.
    1 point
  21. That's what is happening. My bios is 1 hour behind real time. If thats the norm then that's fine. Thanks!
    1 point
  22. Volume and Wifi/Network controls in the menubar shows instantly. No delay
    1 point
  23. 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.
    1 point
  24. 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
    1 point
  25. @Cyberdevs 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.
    1 point
  26. Hi mate, automated Intel AC-Wireless builds are now found here, officially: https://github.com/1hbb/OpenIntelWireless-Factory/releases/ Been testing this for a couple of days, works great. The BTLE integrated module is here: https://github.com/OpenIntelWireless/IntelBluetoothFirmware All kexts loaded from CLOVER/kext/Other works great in Mojave
    1 point
  27. Thanks to @MacKonsti's post here, I'll be looking at enabling the factory-installed Intel Wi-Fi/Bluetooth.
    1 point
  28. You likely has something identified to macOS as a battery source (Corsair’s CommanderPro USB module is the most common), which reports 0% charge. This causes the installer to fail, since any battery below a certain threshold will cause the installer to fail, even on real Apple hardware.
    1 point
  29. Fix RTC _STA` should be achieved by using SSDT patch provided in OpenCorePkg->Docs->AcpiSamples
    1 point
  30. I pulled SSDT-PM from my Z390 EFI, power management is working well in HP hack. The SSDT-PM was possibly created by Maldon. My WIFI card and adapters arrived, once installed WIFI was natively recognised and iMessages and FaceTime worked instantly. Have attached photos of the Wifi install.
    1 point
  31. I assume it should work on older macOS performed new test to start high sierra on the Z97, but does exactly as in the previous attempt, crashes to boot and does not get to desktop
    1 point
  32. Not yet but I will soon and I’ll modify this post to reflect the outcome. [mention]Matgen84 [/mention] One successful boot to windows without errors without DSDT so far. All my DSDT was doing was implementing my keys for brightness anyway as I don’t know how else to do it. Will continue to test as one boot isn’t enough Sent from my iPhone using Tapatalk
    1 point
  33. Hi @Slice I build from source, commit 762eac695 Test from USB pendrive connected to USB3 Port (Z390 Aorus Master) Can't boot USB Big Sur Beta 2 Installer : stuck at IOUSBHostInterface followed by crossed out circle Can't boot Big Sur Beta 2 installed: stuck at IOUSBHostInterface followed by crossed out circle Can't boot MacOS Catalina 10.15.5: Black screen instead of macOS login screen All my kexts are up to date. debug.log preboot.log
    1 point
  34. Awesome find. Has anyone been able to figure out killall Finder? Kext modification possibilities?
    1 point
  35. Today I connected my windows ssd and I had to go to system preferences and change the default from windows 10 to macOS Big Sur...
    1 point
  36. Why is Big Sur the default boot in both OC and Clover, clearing NVRAM does not fix the problem ? Or am I the only one with this problem ? Edit: Fixed the problem by hiding it in Clover
    1 point
  37. @thief sorry let me explain further. Every board has unique traits. Quirks. Things you may need to do different than any other board. Maybe some need x kext maybe some don’t. Maybe some need y kext. And so on. Maybe someone set up the ports in another manner. USBPorts.kext isn’t the only way to set it up. The point is nobody here knows your board, your particular set up. To use an analogy, you’re asking a Windows question in a Mac community. Not only will they not know but the 2 OSes are so different you can’t pick some random similarity and assume they are the same. Almost every modern board has an internal USB hub. That doesn’t mean they map the same. And if both are on HS11 that also means nothing. In short go find a thread with your board and ask there. You’ll find people who can actually help. At the very least you’re just being off topic. This is not a general help thread for USB port mapping. That’s why we have a vast forum that caters to every kind of PC out there.
    1 point
  38. When you installed macOS Catalina successfully and you want to connect to the internet with an old $10 N150 USB wifi dongle, you can use Chris1111 wireless USB adapter to drive your Netis WF2111 Wifi. Cheers, Louis
    1 point
  39. I have tried just about every possible configuration of OC and Clover. With both bootloaders, I can boot to the USB installer or to a USB hard drive with an installation of Big Sur on it (made on a real Mac). No matter what configuration I use, or what drivers I use or what kexts I use, or what DSDT/SSDT I use, I cannot get any of the plugins for IOAHCIFamily.kext to work. (I have a DVD drive on my laptop so both SATA and ATAPI devices cannot be read). At this point, I am thinking that the issue may likely be the BIOS on my HP laptop. It cannot be configured and all advanced options are locked. However, SATA is set to AHCI so it should work. I am at a loss to understand what to do next. P.S. I took out my SATA hard drive and slipped it into a USB adapter and was able to install Big Sur on it. I then put it back into the SATA slot in the laptop and it could no longer be located when booting up.
    1 point
  40. Yes quite right I have both enabled. Just for the heck of it I tested the Recovery Partition and it worked flawless, when I got to the 'Disk Utility' Menu, I completely wiped the Disk and done a clean install (With both cheeks clinched as I didn't know if it would work ) and at the end I was abled to boot into a clean install again.
    1 point
  41. @Slice I'm clean installing Big Sur with the new commit 762eac695 and I'm half way through. I hope everything works out they way it should.
    1 point
  42. And where did you get that bit of information from please tell.
    1 point
  43. Looks like I fixed it. Commit 762eac695 Test please. CLOVERX64.efi.zip
    1 point
  44. I'm still having the same problem as well. It's not just you.
    1 point
  45. 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
    1 point
  46. I deleted release 5120 until it will work.
    1 point
  47. 1 point
  48. No need to patch installer if your SMBIOS is officially supported in Big Sur (that patch is to allow install into older Macs, bypassing compatibility checks). IIRC, I only saw Preboot booting into the second stage install (the one with approx 30 minutes remaining). The final boot into the third stage shows only the Big Sur volume to boot from the OpenCore menu. Interrupting half way through the loading bar during this stage (when the progress bar slows to a crawl and the snapshot is being created) ---> Restart to OpenCore Menu now shows both "macOS Installer" and the Big Sur volume ---> Choose Big Sur Volume ---> 1 reboot, keep on choosing Big Sur volume, not the installer. For those getting error 66 trying to mount their root volume despite disabling SIP for authenticated root --> it means your system still has APFS System Snapshots enabled. These can be removed following the steps below (credit to guide on reddit) Fixing APFS Snapshot Procedure Boot into the Big Sur installer USB Open a terminal, type `csrutil disable` and reboot When back into the installer, run `diskutil list` to find the location of the "Macintosh HD" disk, such as disk2s5 Mount it using `diskutil mountDisk <disk identifier>` such as `diskutil mountDisk disk2s5` then run `mount -uw <volume mount point>` such as `mount -uw /Volumes/Macintosh\ HD/` to mount it as read write Run `/System/Library/Filesystems/apfs.fs/Contents/Resources/apfs_systemsnapshot -v <volume mount point> -r ""` Then, to delete the snapshots on the disk, run `diskutil apfs listSnapshots <volume mount point>` and take note of each UUID of the snapshots Run `diskutil apfs deleteSnapshot <volume mount point> -uuid <uuid of snapshot>` for all snapshots on the disk. Verify that there are no more snapshots by running `diskutil apfs listSnapshots <volume mount point>` it should return "No Snapshots for disk" Reboot into the Big Sur desktop and make sure that running `sudo mount -uw /` returns no errors and that running `diskutil info /` returns a disk such as disk2s5 and not a snapshot such as disk2s5s1 Here is actual real world example (output from terminal after booting into Big Sur Recovery or USB Installer). Note in this example, <volume mount point> was /Volumes/Big_Sur, UUID of snapshot was DD99DFC1-7FA2-4B1E-9F75-04380B0AFCA4... -bash-3.2# csrutil status System Integrity Protection status: disabled. -bash-3.2# csrutil authenticated-root status Authenticated Root status: enabled -bash-3.2# csrutil authenticated-root disable Successfully disabled authenticated root. Please restart the machine for the changes to take effect. //After rebooting back into the Big Sur Recovery or USB Installer, open terminal again and check SIP status now disabled... -bash-3.2# csrutil status System Integrity Protection status: disabled. -bash-3.2# csrutil authenticated-root status Authenticated Root status: disabled -bash-3.2# nvram csr-active-config csr-active-config w%08%00%00 -bash-3.2# 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⁩ 14.7 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.6 MB disk3s2 3: APFS Volume ⁨Recovery⁩ 835.0 MB disk3s3 4: APFS Volume ⁨VM⁩ 1.1 GB disk3s4 5: APFS Volume ⁨Big_Sur⁩ 13.1 GB disk3s5 /dev/disk4 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme +1.8 GB disk4 1: Apple_APFS ⁨Container disk5⁩ 1.8 GB disk4s1 /dev/disk5 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +1.8 GB disk5 Physical Store disk4s1 1: APFS Volume ⁨macOS Base System⁩ 1.6 GB disk5s1 2: APFS Volume ⁨Preboot⁩ 130.0 MB disk5s2 -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 Snapshot for disk3s5 (1 found) | +-- DD99DFC1-7FA2-4B1E-9F75-04380B0AFCA4 Name: com.apple.os.update-190312682FDBFD811EAF7E1DE7AA32CC00611E1594F50D161F143E85BF633A4C XID: 330 Purgeable: Yes NOTE: This snapshot limits the minimum size of APFS Container disk3 -bash-3.2# diskutil apfs deleteSnapshot /Volumes/Big_Sur -uuid DD99DFC1-7FA2-4B1E-9F75-04380B0AFCA4 Deleting APFS Snapshot DD99DFC1-7FA2-4B1E-9F75-04380B0AFCA4 "com.apple.os.update-190312682FDBFD811EAF7E1DE7AA32CC00611E1594F50D161F143E85BF633A4C" from APFS Volume disk3s5 Started APFS operation Finished APFS operation -bash-3.2# diskutil apfs listSnapshots /Volumes/Big_Sur No snapshots for disk3s5 Reboot into Big Sur proper and open terminal to install kext(s) eg say you want to replace original /S/L/E/IO80211Family.kext with attached IO80211Family.kext from High Sierra in your ~/Downloads folder fusion71au@fusion71aus-Mac-mini ~ % sudo mount -uw / Password: //Rename original /S/L/E/IO80211Family.kext and replace with older IO80211Family.kext from your ~/Downloads folder fusion71au@fusion71aus-Mac-mini ~ % sudo mv /System/Library/Extensions/IO80211Family.kext /System/Library/Extensions/IO80211Family.orig Password: fusion71au@fusion71aus-Mac-mini ~ % sudo mv ~/Downloads/IO80211Family.kext /System/Library/Extensions fusion71au@fusion71aus-Mac-mini ~ % sudo chown -R root:wheel /System/Library/Extensions/ fusion71au@fusion71aus-Mac-mini ~ % sudo chmod -R 755 /System/Library/Extensions/ fusion71au@fusion71aus-Mac-mini ~ % sudo kmutil install --update-all checking collections... updated extension 'com.apple.driver.AirPort.Brcm4360' found on disk at '/System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortBrcm4360.kext' (mach-o UUID changed from <unknown> to 8DE38A76-B284-34D2-AF4E-DB727D7FF250) updated extension 'com.apple.driver.AirPort.Atheros40' found on disk at '/System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortAtheros40.kext' (mach-o UUID changed from <unknown> to 9753F22E-5C85-3E95-B543-0870CF03838A) updated extension 'com.apple.driver.IO80211NetBooter' found on disk at '/System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/IO80211NetBooter.kext' (mach-o UUID changed from C0A664A0-F3F6-3C63-919F-B33AA52EC96A to 22A50E20-A024-3B8D-9268-B69ECBA918A0) updated extension 'com.apple.iokit.IO80211Family' found on disk at '/System/Library/Extensions/IO80211Family.kext' (mach-o UUID changed from 99011013-0804-3EF6-B433-D33B216C05DB to A879B51A-4562-3B95-B6C3-A2472B508F2F) updated extension 'com.apple.driver.AirPort.BrcmNIC' found on disk at '/System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortBrcmNIC.kext' (mach-o UUID changed from 1BFF3E8B-77F0-3C4B-A6C1-9DF06132B189 to 0F1637EA-51B0-3A81-9433-956A19427984) updated extension 'com.apple.driver.AirPort.Brcm4331' found on disk at '/System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortBrcm4331.kext' (mach-o UUID changed from <unknown> to D4559F1A-005E-353C-B33F-3006C349EE5D) rebuilding release collections: boot, system rebuilding release collections: boot kernel collection system kext collection rebuilding local auxiliary collection kmutil done fusion71au@fusion71aus-Mac-mini ~ % sudo kcditto Copying deferred prelinked kernels in /... /AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/kext_tools/kext_tools-685/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=0x7f8b16d078d0 {Error Domain=NSOSStatusErrorDomain Code=-43 "fnfErr: File not found"}} /AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/kext_tools/kext_tools-685/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=0x7f8b16e07500 {Error Domain=NSOSStatusErrorDomain Code=-43 "fnfErr: File not found"}} Copying KCs in /... System Volume UUID: 3D41E3EC-D061-4315-BF1B-56B1DA8FF19A Volume Group UUID: 1DF588CB-10D4-48C2-BE99-71CF80DD2FBF Preboot disk: /dev/disk5s2 Preboot volume: /System/Volumes/Preboot Copying: /System/Library/KernelCollections/BootKernelExtensions.kc.elides -> /System/Volumes/Preboot/1DF588CB-10D4-48C2-BE99-71CF80DD2FBF/boot/System/Library/KernelCollections Copying: /System/Library/KernelCollections/BootKernelExtensions.kc -> /System/Volumes/Preboot/1DF588CB-10D4-48C2-BE99-71CF80DD2FBF/boot/System/Library/KernelCollections Copying: /System/Library/PrelinkedKernels/immutablekernel -> /System/Volumes/Preboot/1DF588CB-10D4-48C2-BE99-71CF80DD2FBF/System/Library/PrelinkedKernels Copying: /System/Library/PrelinkedKernels/prelinkedkernel -> /System/Volumes/Preboot/1DF588CB-10D4-48C2-BE99-71CF80DD2FBF/System/Library/PrelinkedKernels
    1 point
  49. Modern icons in ApplePicker M1 machine style. Now in https://github.com/acidanthera/OcBinaryData
    1 point
×
×
  • Create New...