Jump to content
30960 posts in this topic

Recommended Posts

Just now, KGP-iMacPro said:

 

AptioMemoryFix.efi for me works flawless and also is up-to-date.. Give it a try.. The same states for VBoxHfs.efi.. you might realise that HFSPlus.efi is not needed when using VBoxHfs.efi :wink_anim:

 

Yes, it is not needed. For as far as I know, they both do the same thing. BUT....I head VBoxHFs is slower. That's why I'm using HFSPlus in the first place. But maybe I was wrong about this, as well... 

  • Like 1
2 hours ago, Slice said:

And how much VBofHFS is slower? Did you notice?

It is better supported links and listings.

 

 

You're right. I'm sorry. Last time I used it, and that was a long time ago, no, I can't say I've noticed any huge difference. I just went for what I thought it would be the better option. But no, I can't say it's noticeable.

 

Can't really test that right now, since all my drives are using APFS now. I guess I could try that with a USB drive, right? Since those are formatted HFS by default, for as far as I know.

 

Anyway, thank you very much for your feedback.

 

Update: yep, same thing with or without HFSPlus. Also tried AptioMemoryFix. And...so far so good. At least on this system. 

Thank you guys for your feedback.

Edited by arsradu
  • Like 1
1 hour ago, arsradu said:

Can't really test that right now, since all my drives are using APFS now. I guess I could try that with a USB drive, right? Since those are formatted HFS by default, for as far as I know.

For me no.

I formatted USB drive to GPT with two partitions: EFI (fat32) and OSInstall (HFS+).

  • Like 3
20 minutes ago, arsradu said:

By the way, I tried AptioMemoryFix instead of OsxAptioFix3Drv on a second system, one with no hardware NVRAM and...everything ok. :) Nice job. So I guess I'll be switching to this one by default from now on.

 

Thank you.

With AptiomemoryFix, you can use apfsDriverLoader. This driver is compatible only with Aptiomemory. :)

3 hours ago, Matgen84 said:

With AptiomemoryFix, you can use apfsDriverLoader. This driver is compatible only with Aptiomemory. :)

I don't think so. Just AptioMemoryFix R20- had a bug so why you have to update it.

ApfsDriverLoader need no any Fix.

  • Like 2
27 minutes ago, Slice said:

I don't think so. Just AptioMemoryFix R20- had a bug so why you have to update it.

ApfsDriverLoader need no any Fix.

Yes, you're right. But I don't wrote apfsdriverloader need any fix

 

On readme.md from apfsupportPkg: I read that "WARNING: Compatible only with AptioMemoryFix R21+ and loaded PartitionDriver (PartitionDXE)"

11 minutes ago, Matgen84 said:

Yes, you're right. But I don't wrote apfsdriverloader need any fix

 

On readme.md from apfsupportPkg: I read that "WARNING: Compatible only with AptioMemoryFix R21+ and loaded PartitionDriver (PartitionDXE)"

 

I'm using ApfsDriverLoader with OsxAptioFixDrv3 with no problems and working hardware NVRAM.

 

So far, IDK if placebo or not, but I do experience less glitches with OsxAptioFixDrv3 than AptioMemoryFix on my Sandy Bridge laptop.

  • Like 1

weird issue with the vboxhfs-64.efi

 

I created 3 striped array.

1. 2x 80GB

2. 3x 1TB

3. 5x 1TB

 

I get a bootloop on the 2 and 3. No issues on 1. Clover doesn't even display the volume/HDD selection screen. Bootloops immediately before it gets to this screen.

 

As a test, I replaced vboxhfs with hfsplus and and I can finally boot on 3. I'm guessing 2 shouldn't be a problem anymore.

 

does this mean vboxhfs has some sort of storage limit?

 

Thanks!

-------------

Another question please: Is it advisable to install all the provided drivers?

 

I'm not installing anything extra for drivers64. Just the already selected options. For drivers64UEFI, I'm adding AptioMemoryFix and EmuVariableUefi-64.

 

Thanks again.

Edited by mrjayviper
On 6/18/2018 at 12:28 AM, arsradu said:

Hi guys,

 

Are the drivers that Clover proposes for installation documented anywhere? I know some of them are. But I couldn't find a proper description for most of them.

And the description within the installer itself is far from being...descriptive enough. :))

 

So, unless you used them before, or you somehow know what they are good for, it's very hard to choose the right ones. Rule of thumb is usually start with only a few ones. But how do you know WHICH ones? Especially since they're not grouped in any way. You don't know which ones are good for what.

 

Some of them are documented here, for as far as I could see. Some of them are in Clover Change Explanations thread...and some others probably scattered throughout the forum.

 

I can collect them in a single thread, that's not a problem (in case nobody did that already). Although, in my opinion, the first place where they should be documented, is on the Clover Wiki. After that, they should be in the actual description box of the installer itself.

 

Still, in order to do that, I would still need a good description for each one of them, in terms of what they are, and what are they good for. Also, whether or not they create conflicts with other drivers.

 

I totally agree on the lack of proper documentation on the drivers, I'll be more than happy to help on creating a thread with you but if some of our streamed coders and devs can point us in the right direction.

  • Like 4
On 6/15/2018 at 9:13 PM, savvamitrofanov said:

Yep you can remove apfs.efi. 

This loader loads apfs.efi from JSDR section inside APFS Container which located on blockio device

 

hi. i tested latest ApfsDriverLoader.efi with latest AptioMemoryFix.efi and PartitionDxe-64.efi. but i can't see apfs partition entry in GUI. 

there is no problem in v1.0.2

since v1.1.0, i never get entry in GUI.

thanks

  • Like 2
13 hours ago, ellaosx said:

PartitionDXE is needed by ApfsDriverLoader?

 

12 hours ago, MICKHAEL said:

false.

But according to the dev of apfsloader, it is.

https://github.com/acidanthera/ApfsSupportPkg/blob/master/README.md

13 hours ago, ellaosx said:

PartitionDXE is needed by ApfsDriverLoader?

 

12 hours ago, MICKHAEL said:

false.

But according to the dev of apfsloader, it is.

https://github.com/acidanthera/ApfsSupportPkg/blob/master/README.md

17 minutes ago, ellaosx said:

 

But according to the dev of apfsloader, it is.

https://github.com/acidanthera/ApfsSupportPkg/blob/master/README.md

 

But according to the dev of apfsloader, it is.

https://github.com/acidanthera/ApfsSupportPkg/blob/master/README.md

 

in my case, i never get apfs entry. 

already i followed readme. but still not success.

only ApfsDriverLoader v1.0.2 works for me.

12 hours ago, Sherlocks said:

 

hi. i tested latest ApfsDriverLoader.efi with latest AptioMemoryFix.efi and PartitionDxe-64.efi. but i can't see apfs partition entry in GUI. 

there is no problem in v1.0.2

since v1.1.0, i never get entry in GUI.

thanks

I had the same problem with legacy booting of apfs Mojave partition on my GA-P55aUD3 (system 2 in signature). 

 

ApfsDriverLoader.efi v1.0.2 works but not 1.1.0 or newer (even with PartitionDxe-64.efi in /drivers64).

 

No problems with UEFI booting apfs volumes on my NUC6i5SYH however, using ApfsDriverLoader.efi v1.1.0 & newer, no PartitionDxe-64.efi. in /drivers64UEFI.

 

  • Like 3

I bet the problem in drivers boot order in Clover, so Clover loads drivers from drivers64uefi by alphabet starting from A ... Z that means that ApfsDriverLoader loads before PartitionDXE - thats the problem. You can try to rename PartitionDxe to something like A1 and ApfsDriverLoader to A2 and report

I'll fix it in next version

Edited by savvamitrofanov
  • Like 3
1 hour ago, savvamitrofanov said:

I bet the problem in drivers boot order in Clover, so Clover loads drivers from drivers64uefi by alphabet starting from A ... Z that means that ApfsDriverLoader loads before PartitionDXE - thats the problem. You can try to rename PartitionDxe to something like A1 and ApfsDriverLoader to A2 and report

I'll fix it in next version

 

insanelymac's upload isn't working. so i uploaded image in imagur.

here

https://imgur.com/a/f92xtg5

 

i'm using CLOVER UEFI. i tested both PartitionDxe and without PartitionDxe and changed name. but still not work..

only v1.0.2 works

7 minutes ago, Sherlocks said:

 

insanelymac's upload isn't working. so i uploaded image in imagur.

here

https://imgur.com/a/f92xtg5

 

i'm using CLOVER UEFI. i tested both PartitionDxe and without PartitionDxe and changed name. but still not work..

only v1.0.2 works

Hello! Try to load debug 1.1.1 version manually from shell and give me debug information from ApfsDriverLoader and drivers list from shell

  • Like 2
39 minutes ago, savvamitrofanov said:

Hello! Try to load debug 1.1.1 version manually from shell and give me debug information from ApfsDriverLoader and drivers list from shell

 

i can't get log.

i followed this

change name ApfsDriverLoader.efi to 1

then place 1.efi in ESP 

load -nc 1.efi > 1.txt

 

- ApfsSupport-v1.1.1-DEBUG -

Image 'FS0:\1.efi' loaded at D4E69000 - Success

 

- ApfsSupport-v1.0.2-DEBUG -

Image 'FS0:\2.efi' loaded at D4DCE000 - Success
Apfs Container found.
CsbMagic: 4253584E
Should be: 4253584E
Container Blocksize: 4096 bytes
ContainerSuperblock checksum: 4659DE52DE399B7E 
EfiBootRecord located at: 1479746 block
EfiBootRecordBlock offset: 175D42000 
EfiBootRecordBlock checksum: 3EEB3E142E7E793F
ApfsDriver located at: 2835065 block
ApfsDriver offset: 2C0B79000 
ApfsDriver size: 610304 bytes
Loading apfs.efi from memory!

 

- PartitionDxe / ApfsSupport-v1.1.1-DEBUG -

3.efi = PartitionDxe

1.efi = ApfsSupport-v1.1.1-DEBUG

Image 'FS0:\3.efi' loaded at D4E5D000 - Success

Image 'FS0:\1.efi' loaded at D4E58000 - Success

still no luck

Edited by Sherlocks
53 minutes ago, Sherlocks said:

 

i can't get log.

i followed this

change name ApfsDriverLoader.efi to 1

then place 1.efi in ESP 

load -nc 1.efi > 1.txt

 

- ApfsSupport-v1.1.1-DEBUG -

Image 'FS0:\1.efi' loaded at D4E69000 - Success

 

- ApfsSupport-v1.0.2-DEBUG -

Image 'FS0:\2.efi' loaded at D4DCE000 - Success
Apfs Container found.
CsbMagic: 4253584E
Should be: 4253584E
Container Blocksize: 4096 bytes
ContainerSuperblock checksum: 4659DE52DE399B7E 
EfiBootRecord located at: 1479746 block
EfiBootRecordBlock offset: 175D42000 
EfiBootRecordBlock checksum: 3EEB3E142E7E793F
ApfsDriver located at: 2835065 block
ApfsDriver offset: 2C0B79000 
ApfsDriver size: 610304 bytes
Loading apfs.efi from memory!

 

- PartitionDxe / ApfsSupport-v1.1.1-DEBUG -

3.efi = PartitionDxe

1.efi = ApfsSupport-v1.1.1-DEBUG

Image 'FS0:\3.efi' loaded at D4E5D000 - Success

Image 'FS0:\1.efi' loaded at D4E58000 - Success

still no luck

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

Edited by savvamitrofanov
×
×
  • Create New...