Jump to content
30960 posts in this topic

Recommended Posts

12 minutes ago, savvamitrofanov said:

Partitiondxe should start before ApfsDriverLoader. Rename  ApfsDriverLoader to Z.efi and keep partitiondxe it's original name

 

changed name still no luck.

i typed manual load in shell.

first load PartitionDxe.efi

then v1.1.1 debug version.

still no luck. i think i tested all cases enough. i never success v1.1.1

Edited by Sherlocks
  • Like 1

 

17 minutes ago, Sherlocks said:

 

changed name still no luck.

i typed manual load in shell.

first load PartitionDxe.efi

then v1.1.1 debug version.

still no luck. i think i tested all cases enough. i never success v1.1.1

Partitiondxe needs connecting, which implemented in Clover. Push ApfsDriverLoader with name zz.efi and partitiondxe with its name in drivers64uefi and start Clover - it should work 

I'll fix it in next version

Edited by savvamitrofanov
5 minutes ago, savvamitrofanov said:

Partitiondxe needs connecting, which implemented in Clover. Push ApfsDriverLoader with name zz.efi and partitiondxe with its name in drivers64uefi and start Clover - it should work

Partitiondxe needs connecting, which implemented in Clover. Push ApfsDriverLoader with name zz.efi and partitiondxe with its name in drivers64uefi and start Clover - it should work

still no luck.

first checked PartitionDxe efi file load with v1.0.2. yes it's connecting in log.

then i changed name zz.efi from ApfsDriverLoader(1.1.1 Debug). then push it in Drivers64UEFI folder. and reboot. there is still no entry in GUI. it is same like i reported before

4 minutes ago, Sherlocks said:

still no luck.

first checked PartitionDxe efi file load with v1.0.2. yes it's connecting in log.

then i changed name zz.efi from ApfsDriverLoader(1.1.1 Debug). then push it in Drivers64UEFI folder. and reboot. there is still no entry in GUI. it is same like i reported before

Nasty situation! However I'll fix it soon in next version. Thank you for testing

  • Like 1
14 hours ago, Sherlocks said:

still no luck.

first checked PartitionDxe efi file load with v1.0.2. yes it's connecting in log.

then i changed name zz.efi from ApfsDriverLoader(1.1.1 Debug). then push it in Drivers64UEFI folder. and reboot. there is still no entry in GUI. it is same like i reported before

well in my case its loading just ok os x without partitiondxe

(uefi apfs container)

  • Like 1
15 hours ago, Sherlocks said:

still no luck.

first checked PartitionDxe efi file load with v1.0.2. yes it's connecting in log.

then i changed name zz.efi from ApfsDriverLoader(1.1.1 Debug). then push it in Drivers64UEFI folder. and reboot. there is still no entry in GUI. it is same like i reported before

Im on Mojave B2 with APFS {Haswell Laptop currently) and i also do not need PartitionDxe

I have

ApfsDriverLoader-64.efi

AppleImageCodec-64.efi

AppleKeyAggregator-64.efi

AppleUITheme-64.efi

AptioMemoryFix-64.efi

DataHubDxe-64.efi

FirmwareVolume-64.efi

FSInject-64.efi

HFSPlus.efi

SMCHelper-64.efi

The only ones i need are ApfsDriverLoader-64.efi, AptioMemoryFix-64.efi and HFSPlus.efi

The rest Clover keeps insisting on me to install.

 

I'm not sure when ApfsDriverLoader actually loads the apfs from but maybe there is something wrong with yours? Have you tried just adding apfs.efi into drivers64UEFI? Try a fresh install?

Edited by SavageAUS
  • Like 1
2 hours ago, Slice said:

Your driver should not rely on loading order.

If you have a dependency then you must write your driver with check and wait until your dependency satisfied.

Hello! I understood this and just made a bit testing with Sherlock's platform.

However I made test version with PartitionDriver availability check

ApfsDriverLoader 1.1.2

@Sherlocks, test it please

 

  • Like 2
23 minutes ago, savvamitrofanov said:

Hello! I understood this and just made a bit testing with Sherlock's platform.

However I made test version with PartitionDriver availability check

ApfsDriverLoader 1.1.2

@Sherlocks, test it please

 

 

hi.

still no luck

https://imgur.com/a/7VinhTy

 

i tested both PartitionDxe and without PartitionDriver.

here is log in shell

Image 'FS0:\1.efi' error in StartImage: Invalid Parameter

8 minutes ago, Sherlocks said:

 

hi.

still no luck

https://imgur.com/a/7VinhTy

 

i tested both PartitionDxe and without PartitionDriver.

here is log in shell

Image 'FS0:\1.efi' error in StartImage: Invalid Parameter

Thx. Try this ApfsDriverLoader v1.1.3

7 minutes ago, Sherlocks said:

 

no luck

Image 'FS0:\3.efi' is not an image.

i saw partition blah bla message when getting gui on left top

 

Why 3.efi not an image? From what did you load 3.efi? And how?

Did you try to rescan volumes in Clover by pressing ESC?

Edited by savvamitrofanov
12 minutes ago, savvamitrofanov said:

Why 3.efi not an image? From what did you load 3.efi? And how?

Did you try to rescan volumes in Clover by pressing ESC?

 

i renamed apfsloader.efi to 3.efi. no need to type full name when test. also in shell i typed load 3.efi. this process is working v1.0.2 i shell. you can see it i reported above in this thread.

2 minutes ago, Sherlocks said:

 

no luck.

here is log in shell

No partition info protocol, installing event
Image 'FS0:\4.efi' loaded at D4E64000 - Success

No-no-no! It's luck! Now push this driver into drivers64uefi folder and boot Clover!

Don't forget to push PartitionDXE also into drivers64uefi

Edited by savvamitrofanov
6 minutes ago, savvamitrofanov said:

No-no-no! It's luck! Now push this driver into drivers64uefi folder and boot Clover!

Don't forget to push PartitionDXE also into drivers64uefi

 

i already tested it. but still no entry in GUI.

also i followed manual process

1. first load paritiondxe.efi in shell

2. load v1.1.5 in shell with "No partition info protocol, installing event"  message.

then back to Clover GUI. but still no entry. but if follow this process with v1.0.2, i can get entry in GUI.

 

on my signature #1 and #2, this issue happen(v1.1.1 and over). but v1.0.2 is no problem.

Edited by Sherlocks
×
×
  • Create New...