Jump to content
30960 posts in this topic

Recommended Posts

4 hours ago, arsradu said:

 

Slice, I'd love to confirm for other languages, but I was never able to see Clover's prefPane in other language than English. I don't know why... Right now, system language is set to RO, but Clover's prePane language is still EN. Not sure if that's intended. And for EN, yes, the bug reported before where на was not translated to EN, is now fixed (build 4631). But still...not sure how to check other languages when the prefPane language is always EN for me.

 

I checked the installer though. And that one seems to be correctly translated to RO. But...prefPane was always in EN for me, despite the fact that there is a translation for it (in RO), inside the build.

 

 

 

As I see prefPane contains only en.lproj. I don't know how to do it with other languages.

But Clover package already contains ro.po file.

  • Like 2
20 minutes ago, Sherlocks said:

 

1356450388_2018-08-037_08_46.png.3a21656d9cd7c3030e92417a7a81bb44.png

korean lang is no problem in prefPane

 

 

Lol. What the....? :)))) Then I'm confused. Also, I can't really test the issue described before, since my PrefPane is only in EN...and for EN, it's been already fixed.

 

Can you confirm the drop-down for "Force mount selected ESP at startup" doesn't contain any translation errors?

2 minutes ago, vector sigma said:

@arsradu please try r4634 and let me know

 

On it, sir. :)

33 minutes ago, Slice said:

As I see prefPane contains only en.lproj. I don't know how to do it with other languages.

But Clover package already contains ro.po file.

 

Yep, it does. :) And the ro.po file itself already has the necessary translations for PrefPane, for as far as I could see. I mean, I should probably be more confident about this, cause I added them there. :))) But yeah...not sure why it doesn't use them... Maybe there's something missing somewhere. But I don't think it will just not display any of those translations and only in PrefPane... That seems weird.

 

Also, even weirder is the fact that it seems to work for KO. :)) I mean...what the hell? :))

  • Like 1

Actually no. :) Works fine now with clean sources in HS using Xcode 9 with CLT set to CLT 10.

I’m testing Mojave as we speak (same CLT, only Xcode 10 Beta 5).

Since it didn’t work before with the HS setup above, and it does now, I’m expecting it to work with Mojave as well.

I’ll update you as soon as possible. I’m doing it with clean sources on both. So that will take a little bit more than just the building itself.

But so far, yeah, seems to be working.

Edited by arsradu
  • Like 2
26 minutes ago, arsradu said:

Actually no. :) Works fine now with clean sources in HS using Xcode 9 with CLT set to CLT 10.

I’m testing Mojave as we speak (same CLT, only Xcode 10 Beta 5).

Since it didn’t work before with the HS setup above, and it does now, I’m expecting it to work with Mojave as well.

I’ll update you as soon as possible. I’m doing it with clean sources on both. So that will take a little bit more than just the building itself.

But so far, yeah, seems to be working.

Let me know then :wink_anim:, last night I've set up a new hack (asus) and finally I was able to see the error 65 you mentioned that is nothing than a known bug in Xcode 10 build system (it is already in the radar ). Basically new Xcode didn't find generated resources (by ibtool) for just a matter of timing (they get generated, but Xcode looks for it before are in place) and my workaround is just to create and traslate xibs before invoke the make file.... so stuff are already there.

Edited by vector sigma
typo
  • Like 3

Guys, in the meantime, since this is the second time this happens...is there any way that Clover could just remove FakeSMC.kext from Clover/kexts/Other upon installation?

 

It's the second time this happens, and I don't think it's a coincidence. And it's a bit annoying, cause that's one of the things you really cannot boot without. And it's the only thing that's missing from the kexts folder.

 

Could you, please, take a look if the post-install script does something funny here?

  • Like 2
29 minutes ago, vector sigma said:

Let me know then :wink_anim:, last night I've set up a new hack (asus) and finally I was able to see the error 65 you mentioned that is nothing than known bug in Xcode 10 build system (it is already in the radar ). Basically new Xcode didn't find generated resources (ibtool) and my workaround is just to create and traslate xib before invoke the make file.... so stuff are already there.

 

I see. So Beta 2 doesn't have this issue, but Beta 4 and 5 do. So yeah, looks like an Xcode bug...

 

Anyway, I promised I'll make a new clean install in Mojave. And...here I am. :)

 

Yes, it does work. Clover 4634 can now be built successfully with Xcode Beta 5.

 

And...I see what you did there. LOL

========= Translating Resources ========
/Users/jimmy/src/UDK2018/Clover/CloverPackage/package/../../../../opt/local
Updating 'en' strings file for CloverUpdater... done
Updating 'en' strings file for Clover Preference Panel... done
Updating strings file for Clover Preference Panel... done
 (190 entries)
Updating 'en' strings file for CloverUpdater... done
Generating de interface... done
Generating es interface... done
Generating fr interface... done
Generating hr interface... done
Generating id interface... done
Generating it interface... done
Generating ja interface... done
Generating ko interface... done
Generating lv interface... done
Generating nl interface... done
Generating pl interface... done
Generating pt-BR interface... done
Generating pt interface... done
Generating ro interface... done
Generating ru interface... done
Generating tr interface... done
Generating uk interface... done
Generating vi interface... done
Generating zh_CN interface... done
Generating zh_TW interface... done
Building CloverUpdater application...
[XCODE]
Updating 'en' strings file for Clover Preference Panel... done
Generating de interface... done
Generating es interface... done
Generating fr interface... done
Generating hr interface... done
Generating id interface... done
Generating it interface... done
Generating ja interface... done
Generating ko interface... done
Generating lv interface... done
Generating nl interface... done
Generating pl interface... done
Generating pt-BR interface... done
Generating pt interface... done
Generating ro interface... done
Generating ru interface... done
Generating tr interface... done
Generating uk interface... done
Generating vi interface... done
Generating zh_CN interface... done
Generating zh_TW interface... done
Updating strings file for Clover Preference Panel... done
Check de strings... done
Check en strings... done
Check es strings... done
Check fr strings... done
Check hr strings... done
Check id strings... done
Check it strings... done
Check ja strings... done
Check ko strings... done
Check lv strings... done
Check nl strings... done
Check pl strings... done
Check pt-BR strings... done
Check pt strings... done
Check ro strings... done
Check ru strings... done
Check tr strings... done
Check uk strings... done
Check vi strings... done
Check zh_CN strings... done
Check zh_TW strings... done
Building CloverPrefpane preference...
[XCODE]
================= Making all in boot1-install =================
	[XCODE] boot1-install
================= Making all in partutil =================
	[XCODE] partutil
================= Making all in bdmesg =================
	[XCODE] bdmesg
================= Making all in clover-genconfig =================
	[XCODE] clover-genconfig

  -------------------------------
  Building Clover Install Package
  -------------------------------

====================== Preinstall ======================
	[BUILD] Pre
===================== Installation =====================
	[BUILD] UEFI.only
================== Target ESP ==========================
	[BUILD] Target.ESP
=================== BiosBoot ===========================
	[BUILD] BiosBoot
===================== Utils ============================
	[BUILD] Utils
===================== EFI folder =======================
	[BUILD] EFIFolder
===================== BootLoaders ======================
	[BUILD] AltBoot
	[BUILD] bootNo
	[BUILD] boot0af
	[BUILD] boot0ss
====================== CloverEFI =======================
	[BUILD] cloverEFI.64.sata
======================== Themes ========================
	[BUILD] metal
	[BUILD] BGM
	[BUILD] CloverThemeManager
================= drivers64 mandatory ==================
	[BUILD] AppleImageCodec-64
	[BUILD] AppleUITheme-64
	[BUILD] AppleKeyAggregator-64
	[BUILD] XhciDxe-64
	[BUILD] FSInject-64
	[BUILD] FirmwareVolume-64
	[BUILD] SMCHelper-64
===================== drivers64 ========================
	[BUILD] GrubISO9660-64
	[BUILD] ApfsDriverLoader-64
	[BUILD] GrubEXFAT-64
	[BUILD] GrubNTFS-64
	[BUILD] GrubUDF-64
=============== drivers64 UEFI mandatory ===============
	[BUILD] AppleImageCodec-64.UEFI
	[BUILD] AppleUITheme-64.UEFI
	[BUILD] DataHubDxe-64.UEFI
	[BUILD] AppleKeyAggregator-64.UEFI
	[BUILD] VBoxHfs-64.UEFI
	[BUILD] FSInject-64.UEFI
	[BUILD] FirmwareVolume-64.UEFI
	[BUILD] SMCHelper-64.UEFI
=================== drivers64 UEFI =====================
	[BUILD] HashServiceFix-64.UEFI
	[BUILD] UsbMouseDxe-64.UEFI
	[BUILD] OsxAptioFix3Drv-64.UEFI
	[BUILD] OsxFatBinaryDrv-64.UEFI
	[BUILD] UsbKbDxe-64.UEFI
	[BUILD] PartitionDxe-64.UEFI
	[BUILD] OsxAptioFix2Drv-64.UEFI
	[BUILD] CsmVideoDxe-64.UEFI
	[BUILD] VBoxIso9600-64.UEFI
	[BUILD] OsxLowMemFixDrv-64.UEFI
	[BUILD] VBoxExt4-64.UEFI
	[BUILD] Fat-64.UEFI
	[BUILD] EnglishDxe-64.UEFI
	[BUILD] ApfsDriverLoader-64.UEFI
	[BUILD] EmuVariableUefi-64.UEFI
	[BUILD] AptioInputFix-64.UEFI
	[BUILD] Ps2MouseDxe-64.UEFI
	[BUILD] VBoxExt2-64.UEFI
	[BUILD] AptioMemoryFix-64.UEFI
	[BUILD] NvmExpressDxe-64.UEFI
	[BUILD] OsxAptioFixDrv-64.UEFI
===================== RC Scripts =======================
	[BUILD] rc.scripts.on.target
	[BUILD] rc.scripts.on.all.volumes
	[BUILD] rc.scripts.core
================= Optional RC Scripts ==================
	[BUILD] disable_sleep_proxy_client
==================== Clover Prefpane ===================
	[BUILD] CloverPrefpane
================= Post =================
	[BUILD] Post

 --------------------------
 Building process complete!
 --------------------------

 Build info.
 ===========
  Package name: Clover_v2.4k_r4634.pkg
  MD5:          c7da4311fae84f44f120b2c7874f07c0
  Version:      v2.4k
  Stage:        v2.4k
  Date/Time:    2018-08-03 14:19:57
  Built by:     jimmy
  Copyright     2012-2018

  adding: Clover_v2.4k_r4634.pkg (deflated 0%)
  adding: Clover_v2.4k_r4634.pkg.md5 (stored 0%)
total 46016
drwxr-xr-x   9 jimmy  staff       288 Aug  3 14:22 .
drwxr-xr-x  14 jimmy  staff       448 Aug  3 14:22 ..
-rw-r--r--@  1 jimmy  staff  11566527 Aug  3 14:22 Clover_v2.4k_r4634.pkg
-rw-r--r--   1 jimmy  staff        68 Aug  3 14:22 Clover_v2.4k_r4634.pkg.md5
-rw-r--r--   1 jimmy  staff  11530801 Aug  3 14:22 Clover_v2.4k_r4634.zip
drwxr-xr-x   3 jimmy  staff        96 Aug  3 14:21 Resources
drwxr-xr-x   6 jimmy  staff       192 Aug  3 14:22 build
drwxr-xr-x   3 jimmy  staff        96 Aug  3 14:22 package
drwxr-xr-x   6 jimmy  staff       192 Aug  3 14:22 utils
logout
Saving session...
...copying shared history...cp: /Users/jimmy/.bash_history: Permission denied

...saving history...-bash: /Users/jimmy/.bash_history: Permission denied
truncating history files...
...completed.

[Process completed]

 

 

So...in a word: thank you! :) I guess that's two words. lol

Edited by arsradu
  • Like 2
44 minutes ago, arsradu said:

Guys, in the meantime, since this is the second time this happens...is there any way that Clover could just remove FakeSMC.kext from Clover/kexts/Other upon installation?

I never get this kext on ../Other folder upon Clover pkg install #FYI

 

#EDIT: Just installed latest rev, still get no FakeSMC.kext on ../Other dir

Screenshot 32.png

Edited by Badruzeus
  • Like 2
21 minutes ago, arsradu said:

Guys, in the meantime, since this is the second time this happens...is there any way that Clover could just remove FakeSMC.kext from Clover/kexts/Other upon installation?

IMHO can't happen, or better to say not by Clover. Each Payload is just a cpio archive and this program doesn't overwrite existing folders or files while instead create missing ones, like can be the /EFI/CLOVER/kexts directory. So if that instead is happening the only guilty is cpio and we cannot do nothing and cause can be only the problematic file due to some weired circumstances. I can only advice to sosbitute your fakesmc with a new one and delete all the copies.

6 minutes ago, arsradu said:

Yes, it does work. Clover 4634 can now be built successfully with Xcode Beta 5.

So...in a word: thank you! :) I guess that's two words. lol

Good, and thanks to you for testing.

  • Like 1
16 minutes ago, vector sigma said:

IMHO can't happen, or better to say not by Clover. Each Payload is just a cpio archive and this program doesn't overwrite existing folders or files while instead create missing ones, like can be the /EFI/CLOVER/kexts directory. So if that instead is happening the only guilty is cpio and we cannot do nothing and cause can be only the problematic file due to some weired circumstances. I can only advice to sosbitute your fakesmc with a new one and delete all the copies.

Good, and thanks to you for testing.

 

You're most welcome. :)

 

And yeah, it's weird... I just tried reinstalling 4634, with Finder opened to Clover/kexts/Other...and I watched that damn FakeSMC.kext the entire process and it did not go anywhere... Not sure how the hell did it get removed the last time.. And I tried this with both HS and Mojave. Worked perfectly fine with both. And different partitions. :)) So yeah....not sure. I'll keep an eye on this. But as you said, it's most likely not Clover's fault here.

 

Thank you very much for all the time and effort you put into fixing these issues.

  • Like 1
  • Thanks 1
23 minutes ago, Badruzeus said:

#EDIT: Just installed latest rev, still get no FakeSMC.kext on ../Other dir

I think @arsradu talking of existing one. Clover doesn't provide it for installation even though an old copy is present inside the ThirdParty directory, but is unused.

  • Like 3

If the kext was install with some other clover package which had the kext then new package will consider that the option is unchecked and will remove it.

If you always use official installer then it will never happen.

  • Like 2
26 minutes ago, Badruzeus said:

I never get this kext on ../Other folder upon Clover pkg install #FYI

 

#EDIT: Just installed latest rev, still get no FakeSMC.kext on ../Other dir

 

2 minutes ago, vector sigma said:

I think @arsradu talking of existing one. Clover doesn't provide it for installation even though an old copy is present inside the ThirdParty directory, but is unused.

 

Correct. :) I was talking about Clover (which...doesn't seem to be the case) removing FakeSMC.kext (and ONLY FakeSMC.kext) from Clover/kexts/Other. Not adding it. :)) It will not added it, cause it doesn't have it anywhere.

  • Like 1
2 minutes ago, vector sigma said:

Guys, any problems with ApfsDriverLoader? What about make it now mandatory and ban apfs.efi(I mean deleting it if found during the build process and at installation time)? Please advice..

 

All fine from my side.  I mean, I already switched to it on all my systems. So yeah, from my experience, I'd say we could use it by default.

  • Like 1
9 minutes ago, Slice said:

If the kext was install with some other clover package which had the kext then new package will consider that the option is unchecked and will remove it.

If you always use official installer then it will never happen.

 

But...does Clover have FakeSMC inside it...? Cause I didn't find an option in the installer to check/uncheck it... I mean, you do have this for drivers. But not for kexts. I could be very wrong though.

 

And yeah, this happened when upgrading from one Clover version to the other. But still...there was no checkbox for FakeSMC.kext in Clover installer.

  • Like 1
52 minutes ago, arsradu said:

 

But...does Clover have FakeSMC inside it...? Cause I didn't find an option in the installer to check/uncheck it... I mean, you do have this for drivers. But not for kexts. I could be very wrong though.

 

And yeah, this happened when upgrading from one Clover version to the other. But still...there was no checkbox for FakeSMC.kext in Clover installer.

No, official installer never had FakeSMC as an option. It is unofficial installer should be.

But Clover.iso does contain some version of FakeSMC but it will not delete anything, it is iso and no more.

  • Like 4
  • Thanks 1
29 minutes ago, Slice said:

No, official installer never had FakeSMC as an option. It is unofficial installer should be.

But Clover.iso does contain some version of FakeSMC but it will not delete anything, it is iso and no more.

 

You are right. Now I remember I did use a custom script to build Clover once. Not the one I use on a daily basis. Which is based on official instructions and doesn't add any custom kexts. But another one. I used it just to see if the Error 65 still occurs. Which it did. And that had absolutely nothing to do with the script.

But yeah, that was the point of testing this theory in the first place. :)) To see if the method used for building Clover makes any difference for that error. In this case, it didn't. But I remember now that this script also installs FakeSMC. So you're definitely right.

 

Now it's perfectly clear what happened. :) Many thanks!

Edited by arsradu
11 minutes ago, arsradu said:

 

You are right. Now I remember I did use a custom script to build Clover once. Not the one I use on a daily basis. Which is based on official instructions and doesn't add any custom kexts. But another one. I used it just to see if the Error 65 still occurs. Which it did. And that had absolutely nothing to do with the script. But yeah, that was the point of testing this theory in the first place. :)) To see if the method used for building makes any difference. In this case, it didn't. But I remember now that this script also installs FakeSMC. So you're definitely right.

 

Now it's perfectly clear what happened. :) Many thanks!

It's too bad to install the FakeSMC among Clover:

1) user can have it in SLE already

2) user can have plugins from an incompatible branch anywhere, and cause kp.

really a bad thing mixing stuff.

Edited by vector sigma
  • Like 1
Just now, vector sigma said:

It's to bad to install the FakeSMC among Clover:

1) user can have it in SLE already

2) user can have plugins from an incompatible branch anywhere, and cause kp.

really a bad thing mixing stuff.

 

Yeah, but in this case, it was all automatic. Good thing I was paying attention to the log, so I could see what was it doing. :))) Otherwise, it would continue to be a mystery forever.

  • Like 1
×
×
  • Create New...