Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30,171 posts in this topic

Recommended Posts

Slice
Slice
Posted
Posted
3 minutes ago, arsradu said:

@Slice 

 

 

 

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.

 

 

I don't know it. Never encounter.

Link to comment
Share on other sites
arsradu
arsradu
Posted
Posted (edited)
2 minutes ago, Slice said:

I don't know it. Never encounter.

 

Really? :)))

 

Cause I always do...when building with UDK2018. And, even though I'm building in Mojave (Xcode 10)...I doubt this has anything to do with it.

  

192-168-0-116:UDK2018 jimmy$ ./edksetup.sh
Loading previous configuration from /Users/jimmy/src/UDK2018/Conf/BuildEnv.sh
WORKSPACE: /Users/jimmy/src/UDK2018
EDK_TOOLS_PATH: /Users/jimmy/src/UDK2018/BaseTools
CONF_PATH: /Users/jimmy/src/UDK2018/Conf
./edksetup.sh: line 149: return: can only `return' from a function or sourced script
192-168-0-116:UDK2018 jimmy$

 

Edited by arsradu
Link to comment
Share on other sites
arsradu
arsradu
Posted
Posted (edited)
6 minutes ago, Slice said:

But it is not our script. Report to EDK2-devel group.

 

I think it's already been reported...here: https://patches.linaro.org/patch/79255/

 

If I got this right, they say that invoking the script with ./ is actually not ok for this case. I'm not sure why. I'm not an expert. This is just what I got from it...

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

bdmesg started to report faulty version number: 

3:616  0:000  Starting Clover revision: 01314556 on CLOVER EFI

Do the ebuild.sh script update the Version.h file?

Here is mine: 

#define FIRMWARE_BUILDDATE "2018-06-17 15:46:09"
#define FIRMWARE_REVISION L"01314556"
#define REVISION_STR "Clover revision: 01314556"
#define BUILDINFOS_STR "Args: -n 9 -t XCODE8 --vbios-patch-cloverefi --only-sata0 --no-ext -D USE_LOW_EBDA -D NO_GRUB_DRIVERS -D NO_GRUB_DRIVERS_EMBEDDED -D EXIT_USBKB=1 --x64 | -D USE_LOW_EBDA -D NO_GRUB_DRIVERS -D NO_GRUB_DRIVERS_EMBEDDED -D EXIT_USBKB=1 -D ENABLE_VBIOS_PATCH_CLOVEREFI -D ONLY_SATA_0 -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE8 -n 9 | OS: 10.13.5 | XCODE: 9.4"

So the script should be faulty...

Link to comment
Share on other sites
HmO
HmO
Posted
Posted
1 minute ago, smolderas said:

bdmesg started to report faulty version number: 


3:616  0:000  Starting Clover revision: 01314556 on CLOVER EFI

Do the ebuild.sh script update the Version.h file?

Here is mine: 


#define FIRMWARE_BUILDDATE "2018-06-17 15:46:09"
#define FIRMWARE_REVISION L"01314556"
#define REVISION_STR "Clover revision: 01314556"
#define BUILDINFOS_STR "Args: -n 9 -t XCODE8 --vbios-patch-cloverefi --only-sata0 --no-ext -D USE_LOW_EBDA -D NO_GRUB_DRIVERS -D NO_GRUB_DRIVERS_EMBEDDED -D EXIT_USBKB=1 --x64 | -D USE_LOW_EBDA -D NO_GRUB_DRIVERS -D NO_GRUB_DRIVERS_EMBEDDED -D EXIT_USBKB=1 -D ENABLE_VBIOS_PATCH_CLOVEREFI -D ONLY_SATA_0 -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE8 -n 9 | OS: 10.13.5 | XCODE: 9.4"

So the script should be faulty...

All OK

0:100  0:000  Now is 17.6.2018,  15:52:50 (GMT)
0:100  0:000  Starting Clover revision: 4558 on American Megatrends EFI

Link to comment
Share on other sites
smolderas
smolderas
Posted
Posted
6 minutes ago, Ukr55 said:

All OK

0:100  0:000  Now is 17.6.2018,  15:52:50 (GMT)
0:100  0:000  Starting Clover revision: 4558 on American Megatrends EFI

I removed the file, and tried to build with ebuild.sh, same issue. Somewhere along there is an error.

Link to comment
Share on other sites
smolderas
smolderas
Posted
Posted
9 minutes ago, Ukr55 said:

All OK

0:100  0:000  Now is 17.6.2018,  15:52:50 (GMT)
0:100  0:000  Starting Clover revision: 4558 on American Megatrends EFI

I removed the file, and tried to build with ebuild.sh, same issue. Somewhere along there is an error.

 

Edit: I found the culprit:

Change the line 614 in the ebuild.sh to  

		repoRev=$(svn info|awk '{ if ($1=="Revision:") {print $2}}')

So here is the diff: 

614c614
< 		repoRev=$(svn info | grep "Revision" | tr -cd [:digit:])
---
> 		repoRev=$(svn info|awk '{ if ($1=="Revision:") {print $2}}')

 

Link to comment
Share on other sites
Slice
Slice
Posted
Posted
33 minutes ago, smolderas said:

I removed the file, and tried to build with ebuild.sh, same issue. Somewhere along there is an error.

 

Edit: I found the culprit:

Change the line 614 in the ebuild.sh to  


		repoRev=$(svn info|awk '{ if ($1=="Revision:") {print $2}}')

So here is the diff: 


614c614
< 		repoRev=$(svn info | grep "Revision" | tr -cd [:digit:])
---
> 		repoRev=$(svn info|awk '{ if ($1=="Revision:") {print $2}}')

 

Why ome method is better then another? What is your subversion client version?

What is full output of "svn info" in EDK2 folder? In UDK2018 folder?

Link to comment
Share on other sites
ApexDE
ApexDE
Posted
Posted

I tried some hours getting iMessage to work, after updating to 10.13.5. After many testing, i found that CLOVER was to blame. Before i updated to 10.13.5, i installed CLOVER 4498 (coming from 4428).

 

Any CLOVER Version i tried prevented activating iMessage (iMessage Error in systemlog: 13)

 

I tried 4497, 4509, 4458 and 4522. Rolling back to CLOVER 4428 brought back the capability to activate iMessage. iMessage is set up correctly regarding ROM and MLB and never was a issue before.

 

 

Any ideas?

 

Link to comment
Share on other sites
arsradu
arsradu
Posted
Posted (edited)

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.

 

Edited by arsradu
  • Like 3
  • Thanks 1
Link to comment
Share on other sites
smolderas
smolderas
Posted
Posted
17 hours ago, ApexDE said:

I tried some hours getting iMessage to work, after updating to 10.13.5. After many testing, i found that CLOVER was to blame. Before i updated to 10.13.5, i installed CLOVER 4498 (coming from 4428).

 

Any CLOVER Version i tried prevented activating iMessage (iMessage Error in systemlog: 13)

 

I tried 4497, 4509, 4458 and 4522. Rolling back to CLOVER 4428 brought back the capability to activate iMessage. iMessage is set up correctly regarding ROM and MLB and never was a issue before.

 

 

Any ideas?

 

I too have the same issue, I was trying to find the culprit. I'll take a look at it on the weekend.

Link to comment
Share on other sites
el_charlie
el_charlie
Posted
Posted (edited)
On 6/15/2018 at 9:29 AM, 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.

 

Do you use both OsxAptioFix2 together on the same laptop? I have a sandy bridge laptop and use AptioFixDrv and works but I have some glitches and sometimes the display freezes.

 

What about you? no freezes/glitches? I have 8GB of RAM.

 

I'm gonna try OsxAptioFix2Drv-free2000 alone later.

Edited by el_charlie
Link to comment
Share on other sites
pkdesign
pkdesign
Posted
Posted
On 6/18/2018 at 6:30 AM, smolderas said:

I too have the same issue, I was trying to find the culprit. I'll take a look at it on the weekend.

UGH!! Right about June 6 my Messages/Facetime, which have been working for many years, just stopped working. It wouldn’t activate. I spent at least eight hours on Monday trying to figure out why. I deleted pref files, even changed my rock solid config file with new serial number, board serial, ROM, MLB, etc. I even called Apple which I know was a stupid idea.

 

So others are having this same issue? I tried to go back to version 4497 but it didn't work. I think I've screwed something up with Apple activation servers now.

Link to comment
Share on other sites
MICKHAEL
MICKHAEL
Posted
Posted
1 hour ago, pkdesign said:

UGH!! Right about June 6 my Messages/Facetime, which have been working for many years, just stopped working. It wouldn’t activate. I spent at least eight hours on Monday trying to figure out why. I deleted pref files, even changed my rock solid config file with new serial number, board serial, ROM, MLB, etc. I even called Apple which I know was a stupid idea.

 

So others are having this same issue? I tried to go back to version 4497 but it didn't work. I think I've screwed something up with Apple activation servers now.

i am not alone!!! right, something like that. yesterday I tried to fix but...

Link to comment
Share on other sites
Pene
Pene
Posted
Posted (edited)

Following the discussion from the separate topic (good investigation, guys!), it seems that the iMessage problem originates from the change at device-inject.c from commit 4497.

 

Before this commit, built-in property injection for LAN was being made by default.

Starting with 4497, an option to control this feature was added, with its default being set to FALSE (so built-in property is being injected only when LANInjection setting is activated).

 

And as we already confirmed in the past, iMessage activation is insisting on the built-in property to exist on some device in order to activate, even if the actual connection is from a different network device.

Perhaps we could consider setting LANInjection default to TRUE, to avoid breaking iMessage for people that are relying on this.

 

Edited by Pene
  • Like 3
  • Thanks 1
Link to comment
Share on other sites
arsradu
arsradu
Posted
Posted
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
Link to comment
Share on other sites
arsradu
arsradu
Posted
Posted (edited)
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
Link to comment
Share on other sites
Slice
Slice
Posted
Posted
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
Link to comment
Share on other sites
arsradu
arsradu
Posted
Posted

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.

  • Like 1
Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted
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. :)

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