MakAsus Posted January 15 Share Posted January 15 (edited) @Jief_Machak Am I the only one who has lost startup sound? BootChimeCfg.efi plays it as before. HdaCodecDump.txt Edited January 18 by MakAsus Link to comment Share on other sites More sharing options...
chris1111 Posted January 16 Share Posted January 16 Latest Commit All Good latest Sonoma Beta WifI Broadcom, Bluetooth, Audio , Display Slider , Battery Thanks @Jief_Machak 😎 Spoiler 2 Link to comment Share on other sites More sharing options...
mariosun Posted January 16 Share Posted January 16 (edited) @Jief_Machak I don't know if it is a user problem or Clover related problem i can't use in Clover the same Opencore kext combination VirtualSMC has inside a plugin folder with inside some kext for radeon and Sensor for CPU and motherboard they all are loaded in Clover Bootloader and they conflict with two other kexts I use: SMCProcessorAMD.kext SMCSuperIO.kext In Opencore no problem and system boots fine In Clover I solved deleting inside VirtualSMC plugin folder SMCProcessor and SMCSuperIO kexts Then it seems that another kext does not work at all in Clover Bootloader: RestrictEvents.kext I use Restrictevents to manage memory module misconfiguration and AMD CPU name Is it your work related or it is unrelated to what you can do adjusting and fixing things in Clover Bootloader? Thank you Edited January 16 by mariosun 1 Link to comment Share on other sites More sharing options...
Slice Posted January 16 Share Posted January 16 The author of VirtualSMC, vit9696 said that VirtualSMC is not compatible with Clover. For me FakeSMC is better and provide additional features when using Clover. RestrictEvents should work but you have to load also AMFIpass.kext as far as I remember. 2 1 Link to comment Share on other sites More sharing options...
mariosun Posted January 16 Share Posted January 16 12 minutes ago, Slice said: RestrictEvents should work but you have to load also AMFIpass.kext as far as I remember. Thanks for your answer no it is not needed. i use also Amfipass.kext for other reasons VirtualSMC works perfectly with Clover Bootloader and using Clover Kext block feature or if you delete additional plugin he has insite it boots fine(obviusly if you load also other similar kext) I will try FakeSMC as you advised...i am trying to have the same kext for both bootloaders and i have found this different beahviour 1 Link to comment Share on other sites More sharing options...
Slice Posted January 16 Share Posted January 16 21 minutes ago, mariosun said: Thanks for your answer no it is not needed. i use also Amfipass.kext for other reasons VirtualSMC works perfectly with Clover Bootloader and using Clover Kext block feature or if you delete additional plugin he has insite it boots fine(obviusly if you load also other similar kext) I will try FakeSMC as you advised...i am trying to have the same kext for both bootloaders and i have found this different beahviour See please https://www.insanelymac.com/forum/topic/304530-clover-change-explanations/?do=findComment&comment=2789856 1 Link to comment Share on other sites More sharing options...
PG7 Posted January 16 Share Posted January 16 (edited) @Slice @Jief_Machak With these NVRAM2 steps, is it possible to install and update Ventura and Sonoma on a PC with Legacy bios? Edited January 16 by PG7 1 Link to comment Share on other sites More sharing options...
Jief_Machak Posted January 16 Share Posted January 16 5 hours ago, mariosun said: Then it seems that another kext does not work at all in Clover Bootloader: RestrictEvents.kext Openan issue, we'll look into it. 2 Link to comment Share on other sites More sharing options...
Slice Posted January 16 Share Posted January 16 2 hours ago, PG7 said: @Slice @Jief_Machak With these NVRAM2 steps, is it possible to install and update Ventura and Sonoma on a PC with Legacy bios? I propose this. And hope to success. 2 1 Link to comment Share on other sites More sharing options...
mariosun Posted January 16 Share Posted January 16 31 minutes ago, Jief_Machak said: Openan issue, we'll look into it. done thank you 1 Link to comment Share on other sites More sharing options...
PG7 Posted January 16 Share Posted January 16 On 1/15/2024 at 6:37 PM, PG7 said: no, I use exactly the same ones without changing anything only change is the Clover.efi nothing else! * up excuse me, this preboot.log is true that it is another test I immediately update a new Preboot preboot 5157 No boot.log 57.89 kB · 2 downloads preboot Clover r5156 work.log 60.19 kB · 2 downloads Spoiler Clover r5157 Work Thanks 1 Link to comment Share on other sites More sharing options...
iCanaro Posted January 16 Share Posted January 16 6 hours ago, mariosun said: @Jief_Machak I don't know if it is a user problem or Clover related problem i can't use in Clover the same Opencore kext combination VirtualSMC has inside a plugin folder with inside some kext for radeon and Sensor for CPU and motherboard they all are loaded in Clover Bootloader and they conflict with two other kexts I use: SMCProcessorAMD.kext SMCSuperIO.kext In Opencore no problem and system boots fine In Clover I solved deleting inside VirtualSMC plugin folder SMCProcessor and SMCSuperIO kexts Then it seems that another kext does not work at all in Clover Bootloader: RestrictEvents.kext I use Restrictevents to manage memory module misconfiguration and AMD CPU name Is it your work related or it is unrelated to what you can do adjusting and fixing things in Clover Bootloader? Thank you https://github.com/acidanthera/VirtualSMC/releases/tag/1.3.2 if this is the latest version of virtualsmc, no plug in is contained within it 2 Link to comment Share on other sites More sharing options...
mariosun Posted January 16 Share Posted January 16 Clover bootloader uses also kext inside plugin folder and this feature was also useful to WiFi fenvi problem (and we were lucky it uses these kext in the correct order) Opencore needs to declare exactly any kext user want to use also the ones hidden inside contents/plugin folder and this way it is possible to ‘give’ an order as needed as I said in my previous post I would like to use the same kexts combinations for both bootloaders it seems not possible but it is not a big problem 1 Link to comment Share on other sites More sharing options...
jackacc Posted January 17 Share Posted January 17 oclp Skip compatibility check <key>Booter</key> <dict> <key>MmioWhitelist</key> <array/> <key>Patch</key> <array> <dict> <key>Arch</key> <string>x86_64</string> <key>Comment</key> <string>Skip Board ID check</string> <key>Count</key> <integer>0</integer> <key>Enabled</key> <true/> <key>Find</key> <data>AFAAbABhAHQAZgBvAHIAbQBTAHUAcABwAG8AcgB0AC4AcABsAGkAcwB0</data> <key>Identifier</key> <string>Apple</string> <key>Limit</key> <integer>0</integer> <key>Mask</key> <data></data> <key>Replace</key> <data>AC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAu</data> <key>ReplaceMask</key> <data></data> <key>Skip</key> <integer>0</integer> </dict> oc>clover？ Link to comment Share on other sites More sharing options...
mariosun Posted January 17 Share Posted January 17 @Slice CPU type parameter is always working also in latest Clover Bootloader release? Thank you 1 Link to comment Share on other sites More sharing options...
Slice Posted January 17 Share Posted January 17 10 hours ago, jackacc said: oclp Skip compatibility check <key>Booter</key> <dict> <key>MmioWhitelist</key> <array/> <key>Patch</key> <array> <dict> <key>Arch</key> <string>x86_64</string> <key>Comment</key> <string>Skip Board ID check</string> <key>Count</key> <integer>0</integer> <key>Enabled</key> <true/> <key>Find</key> <data>AFAAbABhAHQAZgBvAHIAbQBTAHUAcABwAG8AcgB0AC4AcABsAGkAcwB0</data> <key>Identifier</key> <string>Apple</string> <key>Limit</key> <integer>0</integer> <key>Mask</key> <data></data> <key>Replace</key> <data>AC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAu</data> <key>ReplaceMask</key> <data></data> <key>Skip</key> <integer>0</integer> </dict> oc>clover？ Don't skip board-id. It is much better to write it explicitly. This is the Clover way inaccessible by OC. 41 minutes ago, mariosun said: @Slice CPU type parameter is always working also in latest Clover Bootloader release? Thank you Why the question? Any doubts? 2 Link to comment Share on other sites More sharing options...
mariosun Posted January 17 Share Posted January 17 25 minutes ago, Slice said: Why the question? Any doubts? spent some time with Jief to understand a problem to solve i have to put this: With 0x0F01 i see correct CPU name using RestrictEvents kext or Intel Xeon without using that kext Is it documented in your WIKI? Thank you 1 Link to comment Share on other sites More sharing options...
cankiulascmnfye Posted January 17 Share Posted January 17 12 hours ago, jackacc said: oclp Skip compatibility check <key>Booter</key> <dict> <key>MmioWhitelist</key> <array/> <key>Patch</key> <array> <dict> <key>Arch</key> <string>x86_64</string> <key>Comment</key> <string>Skip Board ID check</string> <key>Count</key> <integer>0</integer> <key>Enabled</key> <true/> <key>Find</key> <data>AFAAbABhAHQAZgBvAHIAbQBTAHUAcABwAG8AcgB0AC4AcABsAGkAcwB0</data> <key>Identifier</key> <string>Apple</string> <key>Limit</key> <integer>0</integer> <key>Mask</key> <data></data> <key>Replace</key> <data>AC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAu</data> <key>ReplaceMask</key> <data></data> <key>Skip</key> <integer>0</integer> </dict> Workaround for Clover: use boot-args: -no_compat_check and revpatch=sbvmm and add RestrictEvents.kext. The first one skips the board-id check, the 2nd one re-enables updates. 1 Link to comment Share on other sites More sharing options...
Slice Posted January 18 Share Posted January 18 12 hours ago, mariosun said: spent some time with Jief to understand a problem to solve i have to put this: With 0x0F01 i see correct CPU name using RestrictEvents kext or Intel Xeon without using that kext Is it documented in your WIKI? Thank you It is the question to RestrictEvents.kext if it set CPU name depending on CPU type. If we speak about OS without RestrictEvents then CPU type must be one present in real MACs and than you'll see CPU name as in the real MAC. No matter of you real CPU. 1 Link to comment Share on other sites More sharing options...
mariosun Posted January 18 Share Posted January 18 (edited) 1 hour ago, Slice said: It is the question to RestrictEvents.kext if it set CPU name depending on CPU type. If we speak about OS without RestrictEvents then CPU type must be one present in real MACs and than you'll see CPU name as in the real MAC. No matter of you real CPU. Yes i think we are saying the same thing In my case without RestrictEvents.kext and processor type set to 0 About my Mac has Xeon 16 Cores as CPU and this is the same with Clover Bootloader using Type set to 0x0F01 For both bootloaders with RestrictEvents.kext about my mac has AMD Ryzen 9 7950X 16-Core Processor common "problem" for both bootloaders is the frequency posted in About My Mac (4.3 Ghz) It should be 4.5 Ghz OSX put the remain part here: And this should be a common OSX problem for both AMD and Intel platform Have you any experience in this? (For cpu with frequency greater than 4.3 GHz I mean) Edited January 18 by mariosun 1 Link to comment Share on other sites More sharing options...
Slice Posted January 18 Share Posted January 18 If the value 4.3GHz came from CPUID BrandString that I can do nothing. It is ROM. But for System Profilier I can set own value CPU->FrequencyMHz=4500 1 Link to comment Share on other sites More sharing options...
Marcinho Posted January 18 Share Posted January 18 Hello everyone, I would like to know if anyone else is having problems with booting in version 5157. For me, since commit 00466c6 "reduce clover size" of version 5156 I have early boot hang on my z390 setup. Sorry for my English and I appreciate any help. thanks Link to comment Share on other sites More sharing options...
miliuco Posted January 18 Share Posted January 18 @Marcinho No issue here. 5157 boots fine my Z390. Please add a signature to your user profile, so your specs are always visible in the posts. 1 Link to comment Share on other sites More sharing options...
mariosun Posted January 18 Share Posted January 18 6 hours ago, Slice said: CPU->FrequencyMHz=4500 using this my system hangs i think apple support CPU frequency till 4.3Ghz it is weird that system sees missing 205 Mhz in detailed system report 1 Link to comment Share on other sites More sharing options...
Stefanalmare Posted January 18 Share Posted January 18 18 minutes ago, miliuco said: @Marcinho No issue here. 5157 boots fine my Z390. Please add a signature to your user profile, so your specs are always visible in the posts. Hey man! Please give me your z390 clover EFI. 1 Link to comment Share on other sites More sharing options...
Recommended Posts