Anto65 Posted March 10 Share Posted March 10 (edited) 🙂 From HDD CLOVER-5157 ( 19 SEC. ) CLOVER-5137 ( 11 SEC. ) From USB CLOVER-5137 ( 2 SEC. ) 😛 CLOVER-5157 ( 9 SEC. ) Edited March 10 by Antonuccio 3 Link to comment Share on other sites More sharing options...
cankiulascmnfye Posted March 10 Share Posted March 10 (edited) @Antonuccio Sounds to me like a config issue. My 12 year old Lenovo T530 boots into Sonoma 14.4 in the same time. Enable "NoEarlyProgress" in Boot sections Edited March 10 by cankiulascmnfye 1 Link to comment Share on other sites More sharing options...
Slice Posted March 10 Share Posted March 10 5 hours ago, Antonuccio said: 🙂 From HDD CLOVER-5157 ( 19 SEC. ) CLOVER-5137 ( 11 SEC. ) From USB CLOVER-5137 ( 2 SEC. ) 😛 CLOVER-5157 ( 9 SEC. ) Same config, same drivers, same theme etc? 2 Link to comment Share on other sites More sharing options...
Anto65 Posted March 10 Share Posted March 10 3 hours ago, cankiulascmnfye said: @Antonuccio Sounds to me like a config issue. My 12 year old Lenovo T530 boots into Sonoma 14.4 in the same time. Enable "NoEarlyProgress" in Boot sections Thanks, "NoEarlyProgress" enabled but it doesn't change... I'm also trying to understand what's holding up the GUI 46 minutes ago, Slice said: Same config, same drivers, same theme etc? Yes it's more or less the same, the theme is different between 5137 and 5157, could this influence this? I attach config. and preboot log of 5157 if you have the desire and time take a look at it... Thanks Spoiler preboot+config.zip 1 Link to comment Share on other sites More sharing options...
Slice Posted March 10 Share Posted March 10 56 minutes ago, Antonuccio said: Thanks, "NoEarlyProgress" enabled but it doesn't change... I'm also trying to understand what's holding up the GUI Yes it's more or less the same, the theme is different between 5137 and 5157, could this influence this? I attach config. and preboot log of 5157 if you have the desire and time take a look at it... Thanks Reveal hidden contents preboot+config.zip 19.79 kB · 1 download Huh! First pause 3 seconds. 0:105 0:000 Warning: Ignored memory module with slot >= SlotCount at '/SMBIOS/Memory:801' 0:105 0:000 Use CloverConfigPlistValidator or look in the log 3:105 2:999 === [ LoadUserSettings ] ======================== 3:105 0:000 Cannot find smbios.plist at path '\EFI\CLOVER' : Not Found Second pause 5 seconds!!! 3:157 0:000 Searching for invalid DiskIo BY_DRIVER connects: not found, all ok 8:154 4:997 === [ InitScreen ] ============================== Third is your sitting in GUI during 7 seconds. 9:033 0:136 GUI ready 16:863 7:830 Boot option Boot0000 not found Final time 17:117 0:000 Closing log But I have no explanation for your first two pauses. Looks like broken booted drive. Same places in my log 0:297 0:015 Using config.plist at path: \EFI\CLOVER 0:298 0:000 === [ LoadUserSettings ] ======================== 0:298 0:000 Cannot find smbios.plist at path '\EFI\CLOVER' : Not Found 0:831 0:000 Searching for invalid DiskIo BY_DRIVER connects: not found, all ok 2:958 2:126 === [ InitScreen ] ============================== I have slow HDD with many partitions so searching DiskIO is really slow operation. Anyway only 3 sec. I should think about excluding it. And after disks inspection I went to GUI 7:874 0:035 GUI ready 2 Link to comment Share on other sites More sharing options...
Anto65 Posted March 10 Share Posted March 10 Thanks , I booted from USB I have an old HDD I'll try to disable it and try again Strange that it doesn't find Smbios and yet it's configured, I noticed it too On the memory I also tried 2channel now it's like this Spoiler but I always get the error With Rel. 5157 there is no validator or am I wrong? Link to comment Share on other sites More sharing options...
Slice Posted March 10 Share Posted March 10 Yes, no validator. 1 Link to comment Share on other sites More sharing options...
Anto65 Posted March 10 Share Posted March 10 If I don't define anything in Smbios > Memory it shows 24GB 😛 Spoiler Disable the old HDD and the result does not change ... There are always those 7 seconds. which loses in seeking smbios and memory 1 Link to comment Share on other sites More sharing options...
Anto65 Posted March 10 Share Posted March 10 The memory problem seems to have been solved.... it would remain " GetDefault Model()=iMac18,3 " ☺️ " Cannot find smbios.plist at path '\EFI\CLOVER' : Not Found " preboot.log 1 Link to comment Share on other sites More sharing options...
LockDown Posted March 21 Share Posted March 21 (edited) @Slice audiodxe still not on working state? Also in config.plist, SMBIOS_sonoma will only work if i manually select it. It seems that AUTO does not work because after reboot, it goes back to SMBIOS. Im sure i have my nvram working. Edited March 21 by LockDown Link to comment Share on other sites More sharing options...
Slice Posted March 21 Share Posted March 21 Should work. Link to comment Share on other sites More sharing options...
LockDown Posted March 21 Share Posted March 21 2 hours ago, Slice said: Should work. Sadly no 😔 Not that important for me though 🙂 Link to comment Share on other sites More sharing options...
Slice Posted March 21 Share Posted March 21 AudioDxe I was testing a week ago. It worked in my config. 2 Link to comment Share on other sites More sharing options...
LockDown Posted March 21 Share Posted March 21 2 hours ago, Slice said: AudioDxe I was testing a week ago. It worked in my config. I was referring to the smbios_sonoma Link to comment Share on other sites More sharing options...
Slice Posted March 22 Share Posted March 22 13 hours ago, LockDown said: I was referring to the smbios_sonoma I will look again when I return home 1 Link to comment Share on other sites More sharing options...
cankiulascmnfye Posted March 24 Share Posted March 24 Most recent Github Actions Runs all exited with errors: Link to comment Share on other sites More sharing options...
chris1111 Posted March 24 Share Posted March 24 (edited) 11 hours ago, cankiulascmnfye said: Most recent Github Actions Runs all exited with errors: I known slice to Do you have any solution because the Workflow stop at the same point for all broken workflow NASM again If you build yourself there is no issue EDIT** I created a new branch Workflow_test if some one with the acces would like to try to repair this workflow First test work here Edited March 25 by chris1111 3 Link to comment Share on other sites More sharing options...
chris1111 Posted March 25 Share Posted March 25 (edited) Secound test OK on test Branch Workflow is fix Pull Request Edited March 26 by chris1111 4 1 Link to comment Share on other sites More sharing options...
Slice Posted March 30 Share Posted March 30 Clover 5158 is out. It was compiled in Sonoma 14.4.1 with gcc13.1 and Python 3.12.1, xcode 15.3 6 1 Link to comment Share on other sites More sharing options...
Anto65 Posted March 30 Share Posted March 30 Done ! Spoiler 1 1 Link to comment Share on other sites More sharing options...
datafeedexpert Posted March 30 Share Posted March 30 Done... 1 Link to comment Share on other sites More sharing options...
Slice Posted March 30 Share Posted March 30 "Bootloader Apple UEFI" 😏 Link to comment Share on other sites More sharing options...
datafeedexpert Posted March 30 Share Posted March 30 10 minutes ago, Slice said: "Bootloader Apple UEFI" 😏 About this Hack from 0xCUB3's github Repo https://github.com/0xCUB3/About-This-Hack Link to comment Share on other sites More sharing options...
deeveedee Posted March 30 Share Posted March 30 (edited) @datafeedexpert You're reporting in the CLOVER thread, but this indicates that ""Apple UEFI" shows up as the bootloader when NOT using OpenCore/Clover ". Is this a bug in About this Hack? Or maybe About This Hack is not recognizing the new CLOVER (because something's wrong with the new CLOVER identification)? EDIT: Just read your response and see that CLOVER is shown in your System Profiler screenshot. Clearly an 0XCUB version bug. Edited March 30 by deeveedee 1 Link to comment Share on other sites More sharing options...
datafeedexpert Posted March 30 Share Posted March 30 15 minutes ago, deeveedee said: @datafeedexpert You're reporting in the CLOVER thread, but this indicates that ""Apple UEFI" shows up as the bootloader when NOT using OpenCore/Clover ". Is this a bug in About this Hack? Or maybe About This Hack is not recognizing the new CLOVER (because something's wrong with the new CLOVER identification)? There is a 3 Versions of AboutThisHack 1 From matxpa 2 From Slice 3 From 0XCUB , Slice's build shows Clover as Boot Loader , 0XCUB's version shows AppleUEFI when using clover, While 0XCUB's AboutThisHack shows Opencore Versions Perfectly... i also posted a screenshot of System Profiler where Clovers Build shows perfectly so don't worry about 0xCUB's AboutThisHack's Bug 2 Link to comment Share on other sites More sharing options...
Recommended Posts