matxpa Posted January 8 Share Posted January 8 @Jief_Machak Hi JIef On 1/4/2024 at 3:03 PM, Jief_Machak said: On 1/4/2024 at 3:57 AM, jsl2000 said: Only About this Hack got wrong bootloader at its home page, but its System Report showed correct Clover version. I don't know where "About this hack" got this information. Maybe the developers of "About this hack" can tell me ? About_This_Hack extracts Clover BootLoader (detailed) Info from bootlog generated by "bdmesg", so the reason why ATH displays "Apple UEFI" with Clover bootloader is the lack of "/usr/local/bin/bdmesg". "bdmesg" can be found in https://github.com/CloverHackyColor/CloverBootloader/releases/download/5156/utils.zip Regards 1 1 Link to comment Share on other sites More sharing options...
cankiulascmnfye Posted January 8 Share Posted January 8 (edited) I wrote a guide to fix About this Hack when using Clover some time ago: https://github.com/5T33Z0/Clover-Crate/blob/main/Utilities/About_This_Hack_Fix.md Edited January 8 by cankiulascmnfye 5 1 Link to comment Share on other sites More sharing options...
MakAsus Posted January 8 Share Posted January 8 3 hours ago, Slice said: How do you know what slot on MB is Bank0/Dimm0? Bank1/Dimm0? etc... Probably the same as it was before the appearance of this glitch or as OpenCore recognizes it. Link to comment Share on other sites More sharing options...
Slice Posted January 8 Share Posted January 8 My MB has slot numeration as 4,2,3,1 so Channel1-Dimm1 Channel1-Dimm0 Channel0-Dimm1 Channel0-Dimm0 But System Profiler shows me Is it the same order? Or? Link to comment Share on other sites More sharing options...
MakAsus Posted January 8 Share Posted January 8 (edited) 2 hours ago, Slice said: My MB has slot numeration as 4,2,3,1 so Channel1-Dimm1 Channel1-Dimm0 Channel0-Dimm1 Channel0-Dimm0 But System Profiler shows me Is it the same order? Or? It seems to me that you are also have the same confusion. If I understand correctly, the banks should alternate like this: 8GB, 4GB, 8GB and again 4GB. It's easy to see the correct order using the bdmesg command. I can't check it myself, because in my another computer installed 4 identical memory banks of 4GB each. In my profile hack, the memory were located like this: Channel1-Dimm1 - empty Channel1-Dimm0 - 32 GB Channel0-Dimm1 - empty Channel0-Dimm0 - 32 GB And it is displayed as if it were located like this: Channel1-Dimm1 - empty Channel1-Dimm0 - empty Channel0-Dimm1 - 32 GB Channel0-Dimm0 - 32 GB Although in bdmesg everything is determined correctly: SlotIndex = 1 ModuleSize = 32768MB Type = 0 Frequency = 3200MHz Bank/Device = BANK 0 Controller0-ChannelA-DIMM1 Vendor = Crucial Technology SerialNo = E7908A70 PartNo = CT32G4DFD832A.M16FF Type 17 Index = 2 ------------------------------------ SlotIndex = 3 ModuleSize = 32768MB Type = 0 Frequency = 3200MHz Bank/Device = BANK 0 Controller1-ChannelA-DIMM1 Vendor = Crucial Technology SerialNo = E7908B58 PartNo = CT32G4DFD832A.M16FF Edited January 8 by MakAsus Link to comment Share on other sites More sharing options...
Slice Posted January 9 Share Posted January 9 In your case this is good Channel1-Dimm1 - empty Channel1-Dimm0 - 32 GB Channel0-Dimm1 - empty Channel0-Dimm0 - 32 GB and this is wrong Channel1-Dimm1 - empty Channel1-Dimm0 - empty Channel0-Dimm1 - 32 GB Channel0-Dimm0 - 32 GB While in my case similar modules located in the same "DIMM". Just lines order is in the question. 1 Link to comment Share on other sites More sharing options...
MakAsus Posted January 9 Share Posted January 9 (edited) 4 hours ago, Slice said: In your case this is good Channel1-Dimm1 - empty Channel1-Dimm0 - 32 GB Channel0-Dimm1 - empty Channel0-Dimm0 - 32 GB and this is wrong Channel1-Dimm1 - empty Channel1-Dimm0 - empty Channel0-Dimm1 - 32 GB Channel0-Dimm0 - 32 GB While in my case similar modules located in the same "DIMM". Just lines order is in the question. Yes, most likely so, except for the order of lines in the profiler, I did not find any significant difference in the functioning of Clover and OpenCore. I don’t know if this can affect the operation of the system in some special cases. I guess it's pure cosmetics, but my perfectionism haunts me. system.log 2024-01-09_10-16_CLOVERX64.EFI.log Edited January 9 by MakAsus Link to comment Share on other sites More sharing options...
Jief_Machak Posted January 9 Share Posted January 9 @MakAsus : could open an issue on github ? I'll fix the problem then. 1 1 Link to comment Share on other sites More sharing options...
MakAsus Posted January 9 Share Posted January 9 (edited) 1 hour ago, Jief_Machak said: @MakAsus : could open an issue on github ? I'll fix the problem then. I don't have an account on Github. They ask to generate some kind of key, but I don’t know how. That is, I get a limited account every time. UPD: It seems that this time we succeeded. Issue#660 Edited January 9 by MakAsus Link to comment Share on other sites More sharing options...
rramon Posted January 9 Share Posted January 9 (edited) On 1/3/2024 at 7:32 AM, anonymous writer said: Hello @Slice With the latest Clover build, my FENVI FW-T919 works perfectly under Sonoma. Thanks for your work on Clover. Hi all and a (belated) happy new year! Since I have a BCM94360CS2 running on 13.6.3 Ventura (iMac 19,1) and didn’t update to Sonoma so far due to known WiFi issues: Do I understand correctly that my card will be supported with the upcoming Clover release? If so, would anyone please be so kind and explain what needs to be configured where inside the config.plist? Thank you in advance! 🙂 Edited January 9 by rramon Link to comment Share on other sites More sharing options...
MakAsus Posted January 9 Share Posted January 9 (edited) 4 hours ago, rramon said: Hi all and a (belated) happy new year! Since I have a BCM94360CS2 running on 13.6.3 Ventura (iMac 19,1) and didn’t update to Sonoma so far due to known WiFi issues: Do I understand correctly that my card will be supported with the upcoming Clover release? If so, would anyone please be so kind and explain what needs to be configured where inside the config.plist? Thank you in advance! 🙂 Yes, you can try to update the 13.6.3 Ventura BCM94360CS2 Wi-Fi adapter using OpenCore-Legacy-Patcher 1.3.0 and 3 additional kexts from here https://github.com/dortania/OpenCore-Legacy-Patcher/tree/main/payloads/Kexts / Acidanthera and make changes to config.plist as in the pictures. Place AMFIPass.kex in the EFI/CLOVER/kexts/Other folder and IO80211FamilyLegacy.kext + IOSkywalkFamily.kext in the EFI/CLOVER/kexts/14 folder. After upgrading to Sonoma, OpenCore-Legacy-Patcher 1.3.0 Root Patch should be applied and with any luck, the BCM94360CS2 will work the same as it does on 13.6.3 Ventura. I can assure you that my BCM94360CS2 profile adapter, only in a slightly different version, worked without problems. I cannot guarantee that I will be able to get the IGPU to work. May need to select iMac Pro 1,1 SMBIOS and disable IGPU in MB BIOS. Edited January 10 by MakAsus 2 Link to comment Share on other sites More sharing options...
miliuco Posted January 10 Share Posted January 10 (edited) @MakAsus Good summary. Only one thing: better to have AMFIPass.kext also into EFI/CLOVER/kexts/14 folder to be loaded only in Sonoma, when needed by OCLP. Edited January 10 by miliuco 4 Link to comment Share on other sites More sharing options...
MakAsus Posted January 10 Share Posted January 10 (edited) 2 hours ago, miliuco said: @MakAsus Good summary. Only one thing: better to have AMFIPass.kext also into EFI/CLOVER/kexts/14 folder to be loaded only in Sonoma, when needed by OCLP. I don’t know, but if I put AMFIPass.kext in the EFI/CLOVER/kexts/14 folder with CrActiveConfig >String> 0x0803, The Watsap.app doesn’t work well for me (random crashes) in both Ventura and Sonoma. That's why I put it in the EFI/CLOVER/kexts/Other folder. Edited January 10 by MakAsus 3 Link to comment Share on other sites More sharing options...
rramon Posted January 10 Share Posted January 10 Thanks a lot to both of you! This is what I wanted to ask: is it possible to keep all aforementioned kexts inside the /Other folder? This is how I am doing it right now and never had problems with anything (there's only one MacOS version installed).. By the way, I'm using a Mini-PCIE 12+6 Pin Adapter plugged directly on my motherboard, so no "classic" PCI-E. This should work, no? Oh and one last thing about SIP: currently it's configured (partially disabled) in the config.plist – does OCLP overwrite these settings and/or do I need to adjust anything inside OCLP? Thanks again, very much appreciate your input! 1 Link to comment Share on other sites More sharing options...
miliuco Posted January 10 Share Posted January 10 @rramon If Sonoma is the single system, you can keep all kexts in Other folder. OCLP doesn't set SIP, in fact it says to you if the current SIP value is ok or must be changed. Right value for OCLP is CsrActiveConfig=0x0803. 2 Link to comment Share on other sites More sharing options...
MakAsus Posted January 10 Share Posted January 10 (edited) 2 hours ago, rramon said: Thanks a lot to both of you! This is what I wanted to ask: is it possible to keep all aforementioned kexts inside the /Other folder? This is how I am doing it right now and never had problems with anything (there's only one MacOS version installed).. By the way, I'm using a Mini-PCIE 12+6 Pin Adapter plugged directly on my motherboard, so no "classic" PCI-E. This should work, no? Oh and one last thing about SIP: currently it's configured (partially disabled) in the config.plist – does OCLP overwrite these settings and/or do I need to adjust anything inside OCLP? Thanks again, very much appreciate your input! If you only have one Sonoma, then all the kexts can be put in the folder EFI/CLOVER/kexts/Other, but even in this case, I think it’s more correct to put the problematic kexts in the folder EFI/CLOVER/kexts/"system number". This will allow you, in an emergency, to boot into the installer of the previous version of the OS. Mini-PCIE 12+6 Pin Adapter plugged directly on my motherboard, so no "classic" PCI-E It works exactly the same way for a friend of mine. Otherwise, you set the value 0x0803, then you will fulfill the requirement for the root OCLP patch. I do not recommend disabling SIP completely; most programs will stop working. And you will need to find patches for each of them, and so Lilu and AMFIPass do everything you need automatically. One last thing: I have never used OCPL from Clover before. Always from OpenCore. This is a much more difficult way requiring more power understanding each of the settings. In my case, the order to adding each kext was strictly important. IOSkywalkFamily.kext should be below WhateverGreen.kext like on a picture: Edited January 10 by MakAsus 1 1 Link to comment Share on other sites More sharing options...
fabiosun Posted January 10 Share Posted January 10 @MakAsus if you find a problematic kext in clover bootloader you can easily block in clover boot menu pressing space and block the kext you do not want to use i hope this feature will be maintained in the future 2 Link to comment Share on other sites More sharing options...
MakAsus Posted January 10 Share Posted January 10 (edited) 24 minutes ago, mariosun said: @MakAsus if you find a problematic kext in clover bootloader you can easily block in clover boot menu pressing space and block the kext you do not want to use i hope this feature will be maintained in the future Sure, but I couldn't boot into a Sonoma without the BlockSkywalk quirk working in Clover. That’s why I only used OpenCore for a long time. In Ventura, this was not necessary. Edited January 10 by MakAsus Link to comment Share on other sites More sharing options...
miliuco Posted January 10 Share Posted January 10 Last build bd46eef works fine on my system. Sonoma + Broadcom Fenvi wifi. OCLP + modern wireless root patch. All good. About This Hack shows boot loader including OCLP as expected. Spoiler 2 Link to comment Share on other sites More sharing options...
jsl2000 Posted January 11 Share Posted January 11 Just now, miliuco said: Last build bd46eef works fine on my system. Sonoma + Broadcom Fenvi wifi. OCLP + modern wireless root patch. All good. About This Hack shows boot loader including OCLP as expected. Hide contents Did you apply a special version of About this Hack modified by yourself ? If yes, may I get it ? 1 Link to comment Share on other sites More sharing options...
miliuco Posted January 11 Share Posted January 11 (edited) @jsl2000 The pic is the official version by 0xCUB3. I wanted to show 2 tooltips at the same time so I made 2 screenshots, each of them with one tooltip, and merged them to have both tootips. Edited January 11 by miliuco 1 Link to comment Share on other sites More sharing options...
MakAsus Posted January 11 Share Posted January 11 I compiled CloverBootloader commit 1947d48 which also works fine. I also compiled About This Hack.app Version 1.1.0 (1400). If anyone needs it, I can add it to my GitHub repository. 1 1 Link to comment Share on other sites More sharing options...
Slice Posted January 11 Share Posted January 11 7 hours ago, miliuco said: Last build bd46eef works fine on my system. Sonoma + Broadcom Fenvi wifi. OCLP + modern wireless root patch. All good. About This Hack shows boot loader including OCLP as expected. Hide contents About This Hack shows wrong SIP <03080000> != 0x03080000 It should be 0x0803 I don't know if this is an error in your config.plist or in the application. 2 Link to comment Share on other sites More sharing options...
miliuco Posted January 11 Share Posted January 11 (edited) @Slice Config.plist has the right value: But Hackintool and even nvram command in Terminal or IOReg have reverse order: Since About This Hack gets the value from IOReg, the value is displayed as is. let sipValue = run ("ioreg -fiw0 -p IODeviceTree -rn options | grep \"csr-active-config\" | awk '{print \"(0x\"substr($3,4,2) substr($3,2,2) substr($3,6,4)\")\"}' | tr -d '\n'") What I don't know is why in config.plist it has to be the other way, I suppose Clover and OpenCore expect this value in Little Endian although in other places we see it as Big Endian. Edited January 11 by miliuco 1 Link to comment Share on other sites More sharing options...
miliuco Posted January 11 Share Posted January 11 @Slice More doubts for me as I am not a programmer and my skills are limited. The value 0x803 seems to fit more closely with the sum of bitmasks (1+2+800) and, on the other hand, the value 0x380 (80+100+200) does not match what is expected. However, the value I see on macOS is 03080000. So could it be that Clover or OpenCore save the value correctly and macOS saves it in the reverse order? Please type a CsrActiveConfig value (use 0x prefix for hex): 0x803 Active values for 0x803 (2,051) : CSR_ALLOW_UNTRUSTED_KEXTS - 0x1 (1) CSR_ALLOW_UNRESTRICTED_FS - 0x2 (2) CSR_ALLOW_UNAUTHENTICATED_ROOT - 0x800 (2,048) Please type a CsrActiveConfig value (use 0x prefix for hex): 0x380 Active values for 0x380 (896) : CSR_ALLOW_DEVICE_CONFIGURATION - 0x80 (128) CSR_ALLOW_ANY_RECOVERY_OS - 0x100 (256) CSR_ALLOW_UNAPPROVED_KEXTS - 0x200 (512) (BitMask Decode script by corpnewt). 1 Link to comment Share on other sites More sharing options...
Recommended Posts