Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30960 posts in this topic

Recommended Posts

arsradu
arsradu
Posted
Posted
Quote

I don't understand why everybody has to comment on my latest post which originally was addressed solely to @Slice and to no-one else...  

 

Well, because we're a community, trying to help each other. :) 

 

Sometimes, a reply from someone else can actually help you figure out the problem before the person your post was meant for, actually gets to read it and reply. At least I can tell you that it did help me before. It's not a bad thing, in my opinion... I personally don't see it like that. But also, I do agree that sometimes people get angry and probably emotional over these things and they take it personally. Which I'm sure it's not the case here. But...as I said, it does happen. Try not to take them personally.

 

As for clover_build.command script (if that's what you want to use) issues ...well, in my opinion, they would be better off addressed in the corresponding thread. Not necessarily because it would be off-topic for this one. But because you would have a better chance of someone answering and helping you with that, knowing that script better and using it on a daily basis. Also, the dev (Micky1979) is probably gonna monitor that thread more often than this one, you know? I'm just saying.

 

Again, please, don't take these things the wrong way. They're (at least from my point of view) not meant to make you feel bad or any other way. People are trying to contribute with whatever they can on helping you figure out this issue, since, by the looks of it, and could be because of the different hardware you're using, the issue you're reporting seems to be specific to your setup. Maybe people with a similar hardware would encounter the same issue...? I don't know. But...what I'm trying to say, is that, from my point of view, having feedback from different people, is not a bad thing.

Please, accept my apologies if my previous posts made you feel uncomfortable in any way. I can assure you they were not meant like that.

Cheers! :)

  • Like 4
  • Thanks 1
Slice
Slice
Posted
Posted
6 minutes ago, mrjayviper said:

Hello. Is it possible to disable the Nvidia web setting while I'm at the clover boot screen? I looked around but cannot find any setting that might disable it. Thanks

 

PS. I'm using high Sierra

Press space on macOS entry

 

or mouse right click

  • Like 1
mrjayviper
mrjayviper
Posted
Posted
10 minutes ago, Slice said:

Press space on macOS entry

 

or mouse right click

 

not sure what you meant but I can see the option to configure by boot flags, GUI settings (including themes), Graphics injection and etc.

 

What I cannot find is an option to disable the nvidiaweb setting while in the clover boot screen. Thanks again!

apianti
apianti
Posted
Posted
1 minute ago, mrjayviper said:

 

not sure what you meant but I can see the option to configure by boot flags, GUI settings (including themes), Graphics injection and etc.

 

What I cannot find is an option to disable the nvidiaweb setting while in the clover boot screen. Thanks again!

 

He means, select the boot entry you want to boot with disabled nvidiaweb and press space bar or right click it to get the menu that allows you to toggle the nvidiaweb option.

  • Like 1
mrjayviper
mrjayviper
Posted
Posted

another question please:

 

I installed High Sierra using vboxhfs-64.efi. I was reading some discussion on the net about hfsplus.efi (this was inside the clover.zip from a mod who was helping me) and I decided to replace vboxhfs-64 with hfsplus.

 

On reboot, the only visible volume in the Clover boot screen is the USB installer. I replaced hfsplus with vboxhfs-64 and the SSD volume showed up again.

 

The SSD was formatted as HFS+ using Disk Utility inside the Installer.

 

1. Is this normal behavior?

2. If yes, does it mean volumes formatted using different HFS drivers are incompatible even though they are both formatted as HFS+?

 

Thanks! 

vector sigma
vector sigma
Posted
Posted (edited)
5 hours ago, KGP-iMacPro said:

no idea why I get offended by you

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

5 hours ago, KGP-iMacPro said:

Just ignore my related post if you are more happy like this! 

 

5 hours ago, KGP-iMacPro said:

I don't understand why everybody has to comment on my latest post which originally was addressed solely to @Slice and to no-one else...   

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!

Edited by vector sigma
  • Haha 1
kgp
kgp
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
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
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
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
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
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
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!

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
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
 

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

 

 

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
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
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
 Share
Go to topic listing
×
×
  • Create New...