Some of Borad Can't boot sonoma with Beta version
dateno1 opened this issue · 13 comments
GA-B365M-AE EFI 240106.zip
EFI Attatched (It not updated/Serial Removed)
I was success to boot&Recovery BCM94360 with beta version on two board but I was fail to boot with GA-B365M Aorus Elite
Test with 'beta-bd46eeffe' + Sonoma Lastest (14.2.1)
Updated Clover from 5155 to Lastest Beta Can't boot it
If i Replace EFI (or EFI&Drivers&Tools) can't boot with this board
No error (just black screen&Stuck)
VirtualSMC is not compatible with Clover. Use FakeSMC instead. And correspondent plugins.
You also should provide preboot.log (by F2) and ACPI tables (by F4) to show full picture of the issue.
VirtualSMC is not compatible with Clover. Use FakeSMC instead. And correspondent plugins.
I don't think so
Clover 5155 has no problem with VirtualSMC and Other computers used Clover with VirtualSMC
I was used clover with VirtualSMC from Mojave to Sonoma on multiple computers (Some of computer Sensors not work with FakeSMC)
I think Old clover (Pre OC/~5122) is better with FakeSMC but lastest Clover using OC (It recommended using with VirtualSMC)
Atattched EFI work well (exclude BlockSkywalk quirk)
You also should provide preboot.log (by F2) and ACPI tables (by F4) to show full picture of the issue.
5115 : 5155.zip
bd46eef : bd46eeffe.zip
No picture can be shot (black screen)
preboot.log is not enough. There is none of the OC messages. You must set the "debug" key to true to generate a file name something like 2024-01-09_15-06_CloverX64.efi.log.
Do you have a way to boot this motherboard with an older Clover or an OpenCore config ?
preboot.log is not enough. There is none of the OC messages. You must set the "debug" key to true to generate a file name something like 2024-01-09_15-06_CloverX64.efi.log. Do you have a way to boot this motherboard with an older Clover or an OpenCore config ?
Which one do you need? (5155? beta?)
All EFI uploaded (I just updated clover 5155 -> bd46eef)
You can check config file from EFI File
Question : How can i get debug log? (I tried Search 'debug' on config file but nothing found)
Let's go step by step : Do you have a way to boot this motherboard with Clover or OpenCore ?
GA-B365M-AE EFI 240106.zip EFI Attatched (It not updated/Serial Removed)
You can check all files&settings from here
This board work well with Clover 5155 (exclude BlockSkywalk)
I was tried update Clover (Replace BOOTX64.efi, CLOVERX64.efi, Tools, Drivers) for fix broadcom wireless
Now I can't boot sonoma on this board
If the board works well with 5155, and now it's not anymore because of some update, you may try the forum. I'm sure some user will inspect your zip.
I also suggest you revert back to a clover folder that works and then update files one by one.
Sorry, but I can't program Clover AND fix configuration/update problems.
If the board works well with 5155, and now it's not anymore because of some update, you may try the forum. I'm sure some user will inspect your zip. I also suggest you revert back to a clover folder that works and then update files one by one. Sorry, but I can't program Clover AND fix configuration/update problems.
Already tested
Replace Cloverx64.efi = No boot
bd46eef is not public version
I just want to do bug report (I hope fix problem on 5167+)
VirtualSMC is not compatible with Clover. Use FakeSMC instead. And correspondent plugins.
I don't think so
Clover 5155 has no problem with VirtualSMC and Other computers used Clover with VirtualSMC
I was used clover with VirtualSMC from Mojave to Sonoma on multiple computers (Some of computer Sensors not work with FakeSMC)
I think Old clover (Pre OC/~5122) is better with FakeSMC but lastest Clover using OC (It recommended using with VirtualSMC)
Atattched EFI work well (exclude BlockSkywalk quirk)
You also should provide preboot.log (by F2) and ACPI tables (by F4) to show full picture of the issue.
5115 : 5155.zip bd46eef : bd46eeffe.zip
No picture can be shot (black screen)
OK, but new Clover contains new OpenCore which blocks using VirtualSMC.
VirtualSMC is not compatible with Clover. Use FakeSMC instead. And correspondent plugins.
I don't think so
Clover 5155 has no problem with VirtualSMC and Other computers used Clover with VirtualSMC
I was used clover with VirtualSMC from Mojave to Sonoma on multiple computers (Some of computer Sensors not work with FakeSMC)
I think Old clover (Pre OC/~5122) is better with FakeSMC but lastest Clover using OC (It recommended using with VirtualSMC)
Atattched EFI work well (exclude BlockSkywalk quirk)You also should provide preboot.log (by F2) and ACPI tables (by F4) to show full picture of the issue.
5115 : 5155.zip bd46eef : bd46eeffe.zip
No picture can be shot (black screen)OK, but new Clover contains new OpenCore which blocks using VirtualSMC.
I already success to boot Sonoma with Clover + VirtualSMC on another two boards
@dateno1 You said you successfully boot 2 boards. Is this issue still open ?
You sent a zip, but does it contains successful boot (with debug log) ? The unsuccessful boot ?
I'm sorry but yon can't just send a zip and hoping that we'll do all the work guessing what is what.
So first, send me a log with a successful boot with an old clover, and then a log with the unsuccessful boot with the latest Clover from the repo. (If you can't compile yourself, I can send you a Clover efi file).
Thanks.
@dateno1 You said you successfully boot 2 boards. Is this issue still open ?
You sent a zip, but does it contains successful boot (with debug log) ? The unsuccessful boot ? I'm sorry but yon can't just send a zip and hoping that we'll do all the work guessing what is what.
So first, send me a log with a successful boot with an old clover, and then a log with the unsuccessful boot with the latest Clover from the repo. (If you can't compile yourself, I can send you a Clover efi file). Thanks.
I was more boards (not only 2)
Problem is clover work with some of boards but not work with some of boards
I wasn't compiled it myself (Downloaded from this github's action)
I will do new test by v5157 (not beta)
5155 : 5155.log
Copy EFI to USB and Replace bootx64.efi, cloverx64.efi (5155 -> 5157)
5157 : 5157.log