GDataPath: /Users/leo/Library/ssdtPRGen/Data SsdtPRGen.sh v0.9 Copyright (c) 2011-2012 by † RevoGirl There is plenty of things for you to do and think about while you are waiting for the replacement BT dongle! The system should reboot automatically and when you next boot the system it should be set to use the current Nvram settings only. You can clear the Nvram while on the Clover boot screen by pressing the 'F11' key. As you are now using VirtualSMC.kext I would recommend you clear the NVRAM on your system, to remove these old unused Nvram settings. The ist shows that you have a lot of settings hanging over from when you were using FakeSMC.kext. Neither ist is well constructed, with common rename patches, ACPI fixes and settings missing, incorrect and unnecessary boot arguments, poorly set device and graphics options, the wrong SMBIOS for your Sandy Bridge system running Catalina or no SMBIOS in the second ist. The system bootleg (bdmesg.txt) looks OK, it shows the system setup could be improved but that is a different issue. It also shows that the kexts in the /EFI/CLOVER/kexts/Other folder on disk0s1 are being used by the system. Kext 110 in the 'kextstat.txt' file shows the system is using with your CRS Bluetooth dongle. This is not needed and should be removed, with the system permissions repaired and kext cache rebuilt - BEFORE YOU REBOOT THE SYSTEM. You have a duplicate of Lilu.kext in your /Library/Extensions folder, it is also an older version than the one in the /CLOVER/kexts/Other folder. The second folder lacks a number of essential drivers in the UEFI folder. I don't know if this is a good or a bad thing. As this is missing from the first CLOVER folder it is not being used by the system. The second/bottom /CLOER/ACPI/patched folder contains what I assume is a Power Management SSDT. Neither folder uses any Custom SSDT's, which is usually a pre-requisite for running Catalina on a Hack. The Kexts are totally missing from the second/bottom folder. The Kexts in the first/top folder are out of date, but at least they are present. ![]() You should really only have one CLOVER folder and it shouldn't have CLOVERX64.efi and BOOTX64.efi files from different versions of Clover bootloader, which the top CLOVER folder has. I have no idea which one you are using to boot but would hope it is the first/top folder and it is on disk0s1. These are located in the EFI on disk0s1 and disk3s5. Neither of which make good reading, as can be seen in the screenshot taken form the '-Overview-.txt' file:Ĭontents and locations of the two Clover folders on your system. I'm just going through the EsentialsList folder you provided in post #3 and have noticed that you have two CLOVER folders in your system. I would then suggest you have a read and follow this guide by UtterDisbelief for creating a custom USB configuration for your laptop. Have you created a custom USBPorts.kext or USBMap.kext or SSDT-UIAC.aml for your macOS Sierra setup? This could be an issue with the USB as much as it is likely to be an issue with the Bluetooth adapter and any kexts. Move the USB dongle to another USB port, one you know works, i.e.Reboot the system, after repairing the permissions and rebuilding the kext cache!.Repair permissions and Rebuild the kext cache, either with Hackintool, Terminal commands or Kext Utility app.Delete the Broadcom kexts you added to the /Library/Extensions (/L/E) folder.When I used a similar CSR Bluetooth dongle it simply worked in macOS Mojave, without the need for any additional kexts, patches or fixes. ![]() Building a CustoMac Hackintosh: Buyer's GuideĪs you are using a Bluetooth adapter that uses the Cambridge Silicon Radio (CSR) chip you don't need to use any of the BrcmPatchRam series of kexts, as you are not using a Broadcom Bluetooth adapter.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |