Jump to content
ErmaC

Clover General discussion

19,692 posts in this topic

Recommended Posts

1 hour ago, Badruzeus said:

It seems, "background.tiff" is disappeared if Appearance=Dark in Mojave.

I just make this image lighter (#000000 > #666666) then rebuilt the package.. but still get same result.. Strange.


~/src/edk2/Clover/CloverPackage/package/Resources/background.tiff

 

No issue here light mode :rofl:

 

882741836_Capturedcranle2018-06-1212_03_22.png.a8e186db8621956f0d8d2b8fbc9cb20a.png

Share this post


Link to post
Share on other sites
Advertisement
6 minutes ago, arsradu said:

imac-2:Clover jimmy$ svn info | grep "Revision" | tr -cd [:digit:]
4535imac-2:Clover jimmy$

So I guess my svn is still on 4535, which causes it to build 4535 instead of 4536.

svn up

Share this post


Link to post
Share on other sites
11 minutes ago, Slice said:

svn up

 

That brings the version to 4537 indeed. BUT I apparently run into some conflicts.

 

   A Drivers/UsbBusDxe/UsbBusDxeExtra.uni
   A Drivers/UsbBusDxe/UsbBus.h
   A Drivers/UsbBusDxe/UsbUtility.h
   A Conf/Tpl/MSFT/config.template
   A gptsync/gptsync.inf
   A gptsync/gptsync.h
   A Certificates/Default/Signing.key
 U   .
Updated to revision 4537.
Summary of conflicts:
  Tree conflicts: 145
Tree conflict on 'BuildTools'
   > local dir unversioned, incoming dir add upon update
Select: (r) mark resolved, (p) postpone, (q) quit resolution, (h) help:

Uhm...help? :)) Or is that intended?

I'm guessing this happened because the initial source was not downloaded via svn? So..it's "unversioned" because of this?

And when I did the svn up it added whatever was different from my local source, but also, couldn't compare versions?

 

I exited the Terminal and went back. Now it says only

imac-2:Clover jimmy$ svn up
Updating '.':
At revision 4537.

 

Edited by arsradu

Share this post


Link to post
Share on other sites
19 minutes ago, chris1111 said:

No issue here light mode :rofl:



 

882741836_Capturedcranle2018-06-1212_03_22.png.a8e186db8621956f0d8d2b8fbc9cb20a.png

 

Oh, I see.. now I just realize that it happened to another package installer too.. a bug with DarkMode, I think.

Spoiler

What a great idea from Apple to make our eyes blind, then they'll release a new device named "iGlass" #LoL

 

Nvidia-Light-Dark.png

Share this post


Link to post
Share on other sites
Delete manually this folder and try again

Yep. Works fine with a fresh environment. Which means that most likely it is/was the fact that I “injected” the Clover sources into the environment instead of downloading them from svn that caused the issues.

 

Thank you so much for your feedback.

By the way, I’m not sure who should I be thanking for this, but building Clover using UDK2018 method is a LOT faster. It is probably also faster because it doesn’t build 32 bit versions anymore. But I don’t know, it just seems really, really fast now.

Well done!

 

Share this post


Link to post
Share on other sites

Guys, a new issue when building the package in Mojave. I'm pretty sure it's something related to the setup. I'm using Xcode 10, obviously. But...the error says Xcode version too old. Which makes no sense.

 

192-168-0-116:CloverPackage jimmy$ ./makepkg

========= Translating Resources ========
/Users/jimmy/src/UDK2018/Clover/CloverPackage/package/../../../../opt/local
XCode version too old. Not extracting locale strings from source XIB file
XCode version too old. Not extracting locale strings from source XIB file
XCode version too old. Don't extracting locale strings from source files

Building CloverUpdater application...
[XCODE]
Building CloverPrefpane preference...
** BUILD FAILED **

make: *** [CloverPrefpane] Error 65
192-168-0-116:CloverPackage jimmy$ 

Did anyone succeed to build Clover in Xcode 10 with this method?

Share this post


Link to post
Share on other sites
1 hour ago, arsradu said:

Guys, a new issue when building the package in Mojave. I'm pretty sure it's something related to the setup. I'm using Xcode 10, obviously. But...the error says Xcode version too old. Which makes no sense.

 


192-168-0-116:CloverPackage jimmy$ ./makepkg

========= Translating Resources ========
/Users/jimmy/src/UDK2018/Clover/CloverPackage/package/../../../../opt/local
XCode version too old. Not extracting locale strings from source XIB file
XCode version too old. Not extracting locale strings from source XIB file
XCode version too old. Don't extracting locale strings from source files

Building CloverUpdater application...
[XCODE]
Building CloverPrefpane preference...
** BUILD FAILED **

make: *** [CloverPrefpane] Error 65
192-168-0-116:CloverPackage jimmy$ 

Did anyone succeed to build Clover in Xcode 10 with this method?

Show, please, output

xcodebuild -version | sed -nE 's/^Xcode ([0-9]).*/\1/p'

Share this post


Link to post
Share on other sites
Just now, Slice said:

Show, please, output

xcodebuild -version | sed -nE 's/^Xcode ([0-9]).*/\1/p'

 

Seems to be 1.

192-168-0-116:~ jimmy$ xcodebuild -version | sed -nE 's/^Xcode ([0-9]).*/\1/p'
1
192-168-0-116:~ jimmy$ 

 

Share this post


Link to post
Share on other sites
5 hours ago, arsradu said:

 

Seems to be 1.


192-168-0-116:~ jimmy$ xcodebuild -version | sed -nE 's/^Xcode ([0-9]).*/\1/p'
1
192-168-0-116:~ jimmy$ 

 

I excluded Xcode version check in 4538. It was needed for Xcode 3 and 4. Now I think xcode is always >=5.

If anyone want old versions then welcome with your proposition how to do better way.

6 hours ago, arsradu said:

 

Seems to be 1.


192-168-0-116:~ jimmy$ xcodebuild -version | sed -nE 's/^Xcode ([0-9]).*/\1/p'
1
192-168-0-116:~ jimmy$ 

 

Check, please

xcodebuild -version | sed -nE 's/^Xcode ([0-9]+).*/\1/p'

Share this post


Link to post
Share on other sites
15 hours ago, Slice said:

fdisk440 should be revised or just excluded. It is compiled to 32bit which is no more supported.

There is a better way to install mbr0 sector sizeof 440


dd if=/dev/disk0 count=1 bs=512 of=origMBR
cp origMBR newMBR
dd if=boot0 of=newMBR bs=1 count=440 conv=notrunc
dd if=newMBR of=/dev/disk0 count=1 bs=512

Someone can implement this into Clover Package? And completely exclude fdisk440.

 

EDITED.

Or /dev/rdisk0 ?

I'll do that tonight. Did you want to backup original boot sectors?

Share this post


Link to post
Share on other sites
17 minutes ago, vector sigma said:

I'll do that tonight. Did you want to backup original boot sectors?

I don't. See no reason to restore it.

See please all fdisk440 usage in the package.

Share this post


Link to post
Share on other sites
15 minutes ago, Slice said:

I don't. See no reason to restore it.

See please all fdisk440 usage in the package.

Ok, I think that fdisk (shipped with the OS) will works just fine activating partitions

Share this post


Link to post
Share on other sites
2 hours ago, Slice said:

I excluded Xcode version check in 4538. It was needed for Xcode 3 and 4. Now I think xcode is always >=5.

If anyone want old versions then welcome with your proposition how to do better way.

Check, please

xcodebuild -version | sed -nE 's/^Xcode ([0-9]+).*/\1/p'

 

After updating sources, now it says "10".

192-168-0-116:Clover jimmy$ xcodebuild -version | sed -nE 's/^Xcode ([0-9]+).*/\1/p'
10
192-168-0-116:Clover jimmy$ 

Now, it says "updating 'en' strings"... But still fails in the same place:

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

Building CloverUpdater application...
[XCODE]
Building CloverPrefpane preference...
** BUILD FAILED **

make: *** [CloverPrefpane] Error 65
192-168-0-116:CloverPackage jimmy$ 

 

Edited by arsradu

Share this post


Link to post
Share on other sites

@Slice

Sorry, seems like I've missed important changes few months back.

What u mean with --Automatic choose "yourtheme" or "yourtheme@2x" if monitor is 2k or larger.--?

In my case, if there're "Lightness" and "Lightness256" themes on the repo already; do I need to rename Lightness256 to Lightness@2x (is exact naming)..?

"The criteria is ScreenHight > 1100", is this new value on theme.plist or u mean "DesignHeight" and Width will follow? Thanks.

Screenshot 31.png

Edited by Badruzeus

Share this post


Link to post
Share on other sites
4 minutes ago, blackosx said:

Yeah. Slice posted a link to an example theme. I've not had time to look yet.

OK, just curious with "ScreenHeigh" and I have no bigger screen than 768 to test.

A question, can we use similar method to speed up CloverThemeManager sync process when updating just like this? Thanks.

Share this post


Link to post
Share on other sites

@Slice

 

sorry yet another issue under 10.14, while the clover package builds totally fine under 10.13.5.

 

Warning!  Building 4538 can now cause a KP under 10.14 and can make your system totally irresponsive.  

 

1289625263_Screenshot2018-06-13at09_07_13.thumb.png.920e579df01eaf5679c23d250efc99b1.png

Edited by KGP-iMacPro

Share this post


Link to post
Share on other sites
14 minutes ago, KGP-iMacPro said:

@Slice

 

sorry yet another issue under 10.14, while the clover package builds totally fine under 10.13.5.

 

Warning!  Building 4538 can now cause a KP under 10.14 and can make your system totally irresponsive.  

...

Where's the proof that your KP issue under 10.14 is caused by "Building 4538"..???

Share this post


Link to post
Share on other sites
15 hours ago, Badruzeus said:

 

Oh, I see.. now I just realize that it happened to another package installer too.. a bug with DarkMode, I think.

  Reveal hidden contents

What a great idea from Apple to make our eyes blind, then they'll release a new device named "iGlass" #LoL

 

Nvidia-Light-Dark.png

 

Hmm...where did you get this driver? :D

1 hour ago, KGP-iMacPro said:

@Slice

 

sorry yet another issue under 10.14, while the clover package builds totally fine under 10.13.5.

 

Warning!  Building 4538 can now cause a KP under 10.14 and can make your system totally irresponsive.  

 

1289625263_Screenshot2018-06-13at09_07_13.thumb.png.920e579df01eaf5679c23d250efc99b1.png

 

Have you tried building with UDK2018? I see you're still using edk2.

Also, no issues booting Mojave using Clover 4538. So...I'm guessing it might be something specific either to your config...or to your Clover build. It's just an idea. I could be wrong. But...as I said, doesn't happen to me.

If you want, you can give it a try.

Clover_v2.4k_r4538.pkg

Edited by arsradu

Share this post


Link to post
Share on other sites
2 hours ago, Badruzeus said:

Where's the proof that your KP issue under 10.14 is caused by "Building 4538"..???

 

I got a KP while building 4538. It was the first and only one since one year. What else you want yo be proven? You should know yourself that it is impossible to provide proof and reason for a KP once the PC is totally frozen. 

 

Anyway, you can also just ignore my advice. Fine with me. 

Share this post


Link to post
Share on other sites
1 hour ago, arsradu said:

 

Hmm...where did you get this driver? :D

 

Have you tried building with UDK2018? I see you're still using edk2.

Also, no issues booting Mojave using Clover 4538. So...I'm guessing it might be something specific either to your config...or to your Clover build. It's just an idea. I could be wrong. But...as I said, doesn't happen to me.

If you want, you can give it a try.

Clover_v2.4k_r4538.pkg

 

I did not say that I had problems in booting Mojave with 4538. I did say that I witnessed a KP and another error while building 4538 on X299 under Mojave. 

 

I guess one should be able to use the Build_Clover.Command, isn’t it? If the latter requires some update to use UDK2018 instead of edk2, I hope somebody can implement it. 

 

All my previous replies about remaining errors have been valid and kindly removed/fixed by @Slice

 

I don't think that now the remaining error is at my side.. 

Edited by KGP-iMacPro

Share this post


Link to post
Share on other sites

The only issue I had building Clover in Mojave is the one I posted above. That’s why I thought I would suggest using UDK2018 method.

 

As for build_clover.command, while an awesome script, it uses SF svn. Which...has been really bad for me recently. Very unstable. By the way, even with VPN.

I don’t know by which miracle it worked last night when downloading Clover sources. But otherwise...man, that was garbage. So...if it works fine for you, that’s great. But an unstable connection like that can create issues building anything. Since you can’t be 100% you got all the sources and nothing is corrupted.

Edited by arsradu

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Pentothal.Z
      Hello all,
      I have a working hackintosh....ok.....but it takes a lot to boot and according to the boot.log there are a few problems.
      One of them is a black screen that stays on for a long time.
      I would like to ask anyone in this community some help to fine tune my machine.
      Boot.log and config.plist attached


      Any help would be appreciated.
      bootlog.txt
      config.plist
    • By metaphysician
      hi folks! i'm just checking for opinions here on a Clover based install of High Sierra. currently i can't boot directly from the internal drive on my hackbook, an ASUS ROG GL502-VS laptop (with the replaced WiFi card), though i can boot from the USB bootloader/installer

      i installed 10.13.6 fine using a prepared vanilla installer on HFS+ (not APFS), but my configuration is somewhat unusual. i have two drives. the first SSD has the Windows system, the second has two partitions with the 2nd partition holding the macOS system. when i ran Clover installer i could not use the UEFI option to copy to the EFI partition because it couldn't find one on that drive. so it installed the EFI folder on the root of the macOS partition instead.
       
      however, after a bit of tinkering around, i found out that there is an existing EFI partition on the primary drive called SYSTEM. it has a EFI folder and underneath that is a Windows folder, a Boot folder, and one called APPLE. i can mount this partition with Clover Configurator and copy files to it, but i don't know if this is a good or risky solution. i was thinking i would manually copy the CLOVER folder and the uefi64.boot file to this partition , making sure not to overwrite anything existing. using the UEFI setup, i can create a boot path from the SYSTEM partition to the Clover boot file, but i'm just curious if this is a useful solution or not, and i don't want to ruin the existing Windows 10 installation for sure. any advice appreciated!
    • By Slice
      OK, 4988 released.
      Now, @vector sigma, what have we do to update translations?
×