Jump to content
10 posts in this topic

Recommended Posts

I am trying to migrate from Clover 2999 (I know, I know) to 5070.

 

With 5070 if I have HFSPlus.efi installed in drivers/UEFI, I hang at black screen.

 

BUT, if I rename HFSPlus.efi to HFSPlus so the driver is not loaded, then Clover 5070 starts fine!

 

The I can use Shell to load the HFSPlus and the driver loads just fine, no hang!

 

Then when I exit Shell, clover shows my Mac volumes and I can boot.

 

The exact same thing happens with APFSLoader, too...

No, UEFI boot from USB...

 

Or did I misread your reply...?

 

When I use VboxHFS driver, it hangs at scanning entries (I have RAID volumes). Sorry to be so slow, but could you explain why drivers have such a hard time when loaded automatically, but can be loaded from Shell once Clover is booted? I would really like to sort it out! Thanks!

I don't even know how to trouble shoot it. I just know that Clover starts up fine with no drivers, but drop APFS or HFSPlus in and it freezes. Load them from shell, and all is good. It makes no sense to me. VboxHFS I don't know if it is technically a hang, but it stops at Scanning Entries, and I get impatient after like a minute or two. And I read somewhere that VboxHFS won't pass scanning entries if you have RAID volumes.

 

What do you mean by "Manually you see no time. It may be much more than automatic loading."?

Sorry if I am talking not clear. English is not my native language.

When you started a driver manually then it may occupy a long time but you didn't see this because you did all manually and see no delay. Much more remarkable is automatic loading with 1 second delay. It is noticeable because it is very long time for automatic. Same 1 second you will never notice when load the driver manually.

 

HFS driver has no relation to RAID or SSD because it deals with logical blocks order no matter by what driver read from a device.

It is a problem of a SATA driver to support RAID.

 

VboxHFS.efi is slower the apple's HFSplus.efi and in rare cases it may fail with complex HFS+ structures (encrypted of embedded). It always better to use HFSplus.efi just to take into account it is private.

  • Like 1

I am very honoured and thankful that you are helping me—and trust me, your Russian (or whatever!) is MUCH better than mine. ;-)

 

But I just can't make out what you're saying. It's not a matter of degrees of delay. It is the difference between NEVER boots, and boots fine. Fact is, HFSPlus.efi prevents Clover from loading AT ALL when it is in the UEFI drivers directory, and I have NO clue why... :-(

×
×
  • Create New...