Catalina (10.15) public beta 4 to public beta 5

[samdeane]

It’s the developer version - might be on a different schedule from the public beta.

They also stagger the releases sometimes, so it rolls out slowly. Gives them a better chance of stopping it early if they missed something bad.

 

[kaygusuz91]

I'm not convinced that it's stuck at "apfs_module_start:1682:" by the way.

I added a few more Kexts to my Clover config - ones that I had installed in the system but not in Clover - and that resulted in a few more log messages after the apfs one during a verbose boot.

I suspect what's actually happening is that something quite early on in the boot is disabling/redirecting the log output - and that apfs message is just pretty much the last one that makes it through.

Which is going to make it tricky to work out what the hell is actually going on.

Which Kexts did you add?

 

[foster]

new build updated just fine
I am using newer clover build of 2.5 5028
lilu
applealc
whatevergreen

 

[kaygusuz91]

new build updated just fine
I am using newer clover build of 2.5 5028
lilu
applealc
whatevergreen

Would you share your clover folder with us?

 

[foster]

here
I removed things specific for my motherboard

 

[kaygusuz91]

here
I removed things specific for my motherboard

Thanks to you I successfully installed the update. Also after copying the ACPI patches you used I was able to boot with my bootloader too. Where did you find those ACPI patches?

 

[foster]

Those patches came from blouse build post

[SUCCESS] blouse's "Hack Pro" :: i9-9900K + Z390 Aorus Pro + Vega 64 + TB3 + USB3 :: 100% working

 

[samdeane]

I ditched my corrupted beta 4, re-ran an earlier beta installer I had on my Mojave partition and got back up & running.

Then upgraded to Clover 5033.

Downloaded the beta 5 updater again.

Had just started running the install, and... had a power outage!

I live on an island... these things happen.

Typical though!

Still waiting for the power to come back up, I really hope it's not all corrupted again!

 

[fegasa11]

samdeane, the same thing happened to me and it was solved by adding the SSDT-ECUSBX.aml in ACPI / patched.

 

[Kylex427]

samdeane, the same thing happened to me and it was solved by adding the SSDT-ECUSBX.aml in ACPI / patched.

What does the SSDT-ECUSBX.aml actually do for the system? I'm very curious.

-Kyle