Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30,171 posts in this topic

Recommended Posts

KGP-iMacPro
KGP-iMacPro
Posted
Posted (edited)
1 hour ago, vector sigma said:

Hey Bro', where is the offense to you? You just said a non sense.

 

Because I think Slice... wont answere to a non sense :P, but is my personal thought Lol (more than a sensation since no one dev as answered you). Anyway if that what you want.. be calm that our roads will not cross again, but remembar that you are in a public Forum, send a PM next time!

 

Just feel sorry for your needs to expose yourself in such stupid way.. .hope our ways will not cross further.. take care.. 

Edited by KGP-iMacPro
  • Haha 1
Link to comment
Share on other sites
arsradu
arsradu
Posted
Posted (edited)

Hi guys,

 

I was trying to figure out why Error 65 when building CloverPrefpane in Mojave. So I tried to open up CloverPrefpane.xcodeproj and I got this error. I'm not sure it's the reason why it's not building it...but...I don't think it's intended either. :)) What do you guys think?

 

1304088323_Screenshot2018-06-14at09_56_13.png.08c7c44d969fbd90375043bc4c9fa0cb.png

 

Update:

After switching CloverPrefpane's architecture to 64-bit Intel, it still doesn't build it, but I get a different error (which still seems related to 32-bit, if I'm not mistaken): 

 "_strncmp", referenced from:
      _USER_modify in user.o32
  "_strncpy", referenced from:
      _ask_cmd in misc.o32
  "_strsep", referenced from:
      _MBR_parse_spec in mbr.o32
  "_strspn", referenced from:
      _ask_cmd in misc.o32
  "_strtol", referenced from:
      _parse_number in mbr.o32
      _ask_num in misc.o32
  "_system$UNIX2003", referenced from:
      _Xmanual in cmd.o32
  "_warn", referenced from:
      _main in fdisk.o32
      _PRT_fix_BN in part.o32
  "_warnx", referenced from:
      _AUTO_init in auto.o32
  "_write$UNIX2003", referenced from:
      _MBR_write in mbr.o32
ld: symbol(s) not found for architecture i386
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[1]: *** [/Users/jimmy/src/UDK2018/Clover/CloverPackage/sym/utils/fdisk440] Error 1
make: *** [all-recursive] Error 1

Looks very similar (if not identical) to the error KGP-iMacPro encountered a few pages before.

Edited by arsradu
  • Like 1
Link to comment
Share on other sites
arsradu
arsradu
Posted
Posted (edited)

Hmm.....I'm not sure it's the same thing.

I mean it's not the APFS Driver. It's the APFS Driver Loader. To me, that means that it helps to load the actual apfs.efi, it does not replace it. I could be wrong though. :) But to be perfectly honest, I'm not really sure how exactly is that supposed to work.

 

And...looking at the description on this commit, it says: 

+"ApfsDriverLoader_description" = "64bit driver to load APFS filesystem driver from container";

More info here.

Edited by arsradu
Link to comment
Share on other sites
SavageAUS
SavageAUS
Posted
Posted (edited)
58 minutes ago, ellaosx said:
According to "Clover Changes" thread,  it now has a new ApfsDriverLoader.efi.
So if i got it right, we put this in driver64/driver64uefi instead of apple's apfs.efi?

It certainly reads that way. This would be very helpful. Hopefully a dev can confirm if we can remove apfs from EFI.

 

Edit: Tested before waiting and no it doesn't work like that. You need to get a different driver from here https://github.com/acidanthera/ApfsSupportPkg/releases 

And place that in drivers64UEFI folder and that should load the native apfs. (I think, please correct me if I'm wrong)

Hopefully if this works we can patch apfs on the fly for less verbose and hopefully it can be incorporated into clover package.

 

Edit2: Tested and confirmed in High Sierra and Mojave that the above driver works as it should with no verbose output.

Sent from my SM-G930F using Tapatalk

Edited by SavageAUS
Link to comment
Share on other sites
savvas
savvas
Posted
Posted
1 hour ago, SavageAUS said:

It certainly reads that way. This would be very helpful. Hopefully a dev can confirm if we can remove apfs from EFI.

 

Edit: Tested before waiting and no it doesn't work like that. You need to get a different driver from here https://github.com/acidanthera/ApfsSupportPkg/releases 

And place that in drivers64UEFI folder and that should load the native apfs. (I think, please correct me if I'm wrong)

Hopefully if this works we can patch apfs on the fly for less verbose and hopefully it can be incorporated into clover package.

 

Edit2: Tested and confirmed in High Sierra and Mojave that the above driver works as it should with no verbose output.

Sent from my SM-G930F using Tapatalk

Yep you can remove apfs.efi. 

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

  • Like 12
  • Thanks 2
Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted
1 hour ago, savvamitrofanov said:

Yep you can remove apfs.efi. 

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

 

this is awesome driver.

OsxAptioFix2Drv-free2000

and

OsxAptioFixDrv on sandy laptop(10.6~10.13).

 

there is no problem.

thank you so much.

  • Like 1
Link to comment
Share on other sites
Cyberdevs
Cyberdevs
Posted
Posted
1 hour ago, savvamitrofanov said:

Yep you can remove apfs.efi. 

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

The driver works perfectly fine on my rig as well. I tested it with macOS Mojave haven't tested it with High Sierra but I'm 100% sure that it will work with High Sierra as well.

 

Thanks man!

Link to comment
Share on other sites
LockDown
LockDown
Posted
Posted
6 minutes ago, Sherlocks said:

 

this is awesome driver.

OsxAptioFix2Drv-free2000

and

OsxAptioFixDrv on sandy laptop(10.6~10.13).

 

there is no problem.

thank you so much.

So you mean to say it also works aside from AptioMemoryFix. 

This is great!

Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted (edited)
14 minutes ago, ellaosx said:

So you mean to say it also works aside from AptioMemoryFix. 

This is great!

 

yes. in my case, if i don't use EmuVariableUefi, will get language issue after macOS update(example. 10.13.5 -> 10.13.6)

this issue i reported(related prev-lang:kbd) long time ago in clover thread. but still there is a issue.

so i'm still using OsxAptioFix2Drv-free2000 + EmuVariableUefi. 

 

EDIT1

first report

https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/?do=findComment&comment=2565871

two report

https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/?do=findComment&comment=2566330

Edited by Sherlocks
  • Thanks 1
Link to comment
Share on other sites
SavageAUS
SavageAUS
Posted
Posted
4 hours ago, savvamitrofanov said:
Yep you can remove apfs.efi. 
This loader loads apfs.efi from JSDR section inside APFS Container which located on blockio device

Can this driver please be incorporated into clover package or at least into build_clover script.

Sent from my SM-G930F using Tapatalk
 

Link to comment
Share on other sites
athlonreg
athlonreg
Posted
Posted
2 hours ago, SavageAUS said:

Can this driver please be incorporated into clover package or at least into build_clover script.

Sent from my SM-G930F using Tapatalk

Can this driver please be incorporated into clover package or at least into build_clover script.

Sent from my SM-G930F using Tapatalk
 

Hi, you can try it 

 

Build_Clover.command

 

 

Link to comment
Share on other sites
Pene
Pene
Posted
Posted
20 hours ago, Slice said:

Rev 4540

New driver developed by savvas https://github.com/acidanthera/ApfsSupportPkg/

You may exclude private apfs.efi from drivers64UEFI folder and place here the driver ApfsDriverLoader.efi.

It performs loading the driver from APFS container by DiskIO protocol.

The driver is open source but located not in Clover repository and at link above. It contains macbuild.tool for those who want to compile by himself.

Hi,

I tried this driver (the prebuilt one) and it completely hangs my system in a way that it never gets to Clover. I don't see a topic about it, so I'm not sure where to report...

  • Sad 1
Link to comment
Share on other sites
savvas
savvas
Posted
Posted (edited)
37 minutes ago, Pene said:

Hi,

I tried this driver (the prebuilt one) and it completely hangs my system in a way that it never gets to Clover. I don't see a topic about it, so I'm not sure where to report...

Please update aptiomemoryfix. Hang occured because MOStartImage in aptiofix didn't check null devicepath inside load image, so it hangs. APFSDriverLoader gives LoadImage source buffer and its size with NULL device path. 

Edited by savvamitrofanov
  • Like 5
Link to comment
Share on other sites
Pene
Pene
Posted
Posted
27 minutes ago, savvamitrofanov said:

Please update aptiomemoryfix. Hang occured because MOStartImage in aptiofix didn't check null devicepath inside load image, so it hangs. APFSDriverLoader gives LoadImage source buffer and its size with NULL device path. 

Yes, that fixed it. Nice work!

By the way, if I have two APFS volumes, say High Sierra and Mojave, will it load the most recent driver?

  • Like 2
Link to comment
Share on other sites
Badruzeus
Badruzeus
Posted
Posted (edited)
24 minutes ago, SavageAUS said:

.. Does the ApfsDriverLoader work for USB installs?

On my case, my 10.14 USB installer is formatted as HFS+, not really sure if it's needed (pre-install). I just did test placing it within /drivers~ folder and it works to load macOS Mojave with APFS (post-install). Thanks.

Edited by Badruzeus
Link to comment
Share on other sites
arsradu
arsradu
Posted
Posted

Hi guys,

 

Shouldn't Clover automatically detect if you already have HFSPlus.efi installed, and not push you to install VBoxHfs.efi in this case? I thought it should remember what you have and what you don't have from previous installations, and suggest to keep that configuration by default, when you reinstall/upgrade.

 

Well, in this case, it keeps pushing to install VBoxHfs, although I didn't have it before (it would be a new install) and I already have HFSPlus. Interestingly enough, it doesn't do the same with ApfsDriverLoader.

Is this intended?

 

207371327_Screenshot2018-06-17at00_32_48.png.8c3ee5929b4d8bbd9f2c1d3cfc1773da.png

  • Like 1
Link to comment
Share on other sites
chris1111
chris1111
Posted
Posted (edited)

@savvamitrofanov just report your ApfsDriverLoader.efi works good here HP ProBook 6570B

Compiling the drivers with UDK2018 

Thank you

Capture.png.48bfd34f203eba4e232103181879030a.png

 

Edited by chris1111
  • Like 2
  • Thanks 1
Link to comment
Share on other sites
arsradu
arsradu
Posted
Posted (edited)

@Slice 

 

Thanks to your latest commits regarding mtoc.NEW locations, I was able to compile Clover 4551 using UDK2018 with no errors anymore. Thank you very much! :) 


By the way, since we can build nasm with ./buildnasm.sh (which has also been fixed), I think we can remove the first steps from the instructions page and add a new line for it under Step nr 4 (Prepare sources).

 

Also, to avoid error 

./edksetup.sh: line 149: return: can only `return' from a function or sourced script

when invoking that script with "./" , maybe we can update the instructions so that it will be invoked with  ". edksetup.sh" instead. This should work perfectly fine.

 

Just a few ideas, of course. :)

Edited by arsradu
Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...