Now, you can't even boot.
So at the end of a review, what's the conclusion?
Clearly mistakes have been made along the way.
Suggestion?
Go put back your original EFI folder from
post #25 or
post #20. This will remove everything we have tried. The hack was working for you at that point, so should again. You might then want to configure your USB/Thunderbolt ports properly, but not touch anything else that could affect booting.
OK.
A summary from me and then we're done.
Is anyone interested in seeing, if you haven't already (I'm not sure) the EFI folder or config.plist from my USB Boot drive? That boot loader always boots the machine. That boot loader brings me to a Tonymacx86 Clover V4920 boot screen. I can pick any of my HDs that have the OS on it and I'm in business.
At one point early on while I was in Clover V4, trying to do whatever I was trying to do, the dialog box to update to V5 popped up. I did the update to Clover V5.
That presented a problem in booting so I went back to V4.
Booting from V5 has never worked. Booting from V4 has always worked.
I have mentioned this in these posts.
@UtterDisbelief You mentioned a few posts back...
Okay, there is a potential problem for this set-up if you are still using Clover version 49**. There's nothing actually wrong with that, we just have to take into account the different file system structure of the post 5000 versions.
I'm not a code writer but I am fairly analytical. I've said from the start that Multibeast and the way it created the boot loader is the root of all this. Multibeast created the boot loader in V4 not V5.
Multibeast tagged the SMBIOS as 14,2 not 18,3.
I keep seeing the same red flags. I know you are also and trying to work them out.
Don't get me wrong here. I'm trying to follow along with a limited knowledge of the "2nd layer" of all this code writing.
The USB problems I'm having are tied to the SMBIOS.
One of the reasons is because, if I understand this at all, the SMBIOS is wrong for the CPU I'm using (i7-7700K) and the Chipset+ASMedia®ASM2142 USB 3.1 Gen 2 Controller is not a good fit. (I don't know if incompatible is the correct terminology.)
At some point in time, some one else who is having a problem with this chipset will figure this out.
Thank you
@UtterDisbelief
Thank you
@pastrychef
You guys have been wonderful.
Go enjoy some coffee on me.
BillieJo.