Jump to content
ErmaC

Clover General discussion

19,684 posts in this topic

Recommended Posts

Posted (edited)
6 minutes ago, Sherlocks said:

hi apianti.
recently i change asus wifi router rt-ac66u to ac rt68u. first i suspected router issue. but most of korean people suffered this issue for only sf.

except only sf, i don't have problem to access source site(github and etc)

나의 SM-N960N 의 Tapatalk에서 보냄
 

 

I expect that sourceforge was maybe being barraged by korean traffic so it had no choice but to block an entire regional subnet of IP addresses. May even be attacks that are not originating in korea but those IP addresses have now been deemed as compromised by sourceforge's firewall/filtering.

 

EDIT: Maybe put in a support ticket and see why?

Edited by apianti

Share this post


Link to post
Share on other sites
Advertisement
Posted (edited)
19 hours ago, apianti said:
 
I expect that sourceforge was maybe being barraged by korean traffic so it had no choice but to block an entire regional subnet of IP addresses. May even be attacks that are not originating in korea but those IP addresses have now been deemed as compromised by sourceforge's firewall/filtering.
 
EDIT: Maybe put in a support ticket and see why?

thank you for explanation.
as result, if i need to commit, i always use VPN :(

나의 SM-N960N 의 Tapatalk에서 보냄

 

EDIT1

best way is TouchVPN.

it's a simple UI. and can find app from appstore.

Edited by Sherlocks

Share this post


Link to post
Share on other sites
Posted (edited)

UEFI Shell tip:

 

It is important to be able to type a colon for file management purposes.  The only answer I've found is to use an older Mac wired keyboard.   Wired windows keyboards, wireless keyboards don't work.   The only solution for me was to use the full size wired Apple keyboard.

Edited by meaganmargaret

Share this post


Link to post
Share on other sites
Posted (edited)
2 hours ago, meaganmargaret said:

UEFI Shell tip:

 

It is important to be able to type a colon for file management purposes.  The only answer I've found is to use an older Mac wired keyboard.   Wired windows keyboards, wireless keyboards don't work.   The only solution for me was to use the full size wired Apple keyboard.

What are you talking about?? I use Wired Windows Keyboard, and i can type "colon" in UEFI Shell

Edited by Andres ZeroCross

Share this post


Link to post
Share on other sites
14 hours ago, meaganmargaret said:

UEFI Shell tip:

 

It is important to be able to type a colon for file management purposes.  The only answer I've found is to use an older Mac wired keyboard.   Wired windows keyboards, wireless keyboards don't work.   The only solution for me was to use the full size wired Apple keyboard.

 

Actually i use usb full apple keyboard and i can't type colon !

Share this post


Link to post
Share on other sites
Posted (edited)
On 5/4/2019 at 10:37 AM, Andres ZeroCross said:

What are you talking about?? I use Wired Windows Keyboard, and i can type "colon" in UEFI Shell

 

Well, it didn't for me.  It appears there's a bug in the UEFI shell in Clover, and there appears to be a wide variety of methods that work for some and not for others.  In fact, I had to be directly connected (no usb extension cable) via an Apple wired keyboard to a USB 2.0 port (and only USB 2.0) to get my keyboard to type this -> :  in the UEFI shell.

Edited by meaganmargaret

Share this post


Link to post
Share on other sites
Posted (edited)

I have a wireless usb 3.0 keyboard and have no problem in the shell. Try using one of the other shell variations. It may be a limitation of your firmware or the keyboard as well since the simple text input protocol doesn't have shift/alt/control/etc key support so it relies on the driver. If the driver doesn't properly check whether the shift key is pressed to alter the character that is retrieved from the keyboard then it will just use the character represented by the key scan code. The keyboard may also be to blame by having a different scan code for keys, especially if it is not an ANSI english keyboard.

 

EDIT: You can also try using either the ps2 keyboard driver from edk2, or the usb keyboard driver from clover or unmodified from edk2. Though if you are legacy booting you already have the clover modified one.

Edited by apianti

Share this post


Link to post
Share on other sites
Posted (edited)

Uhm...guys? Is this intended? Cause it looks like a bug to me... Looks like VBoxHfs-64.uefi is present as both Mandatory and non-mandatory driver.

 

My guess is that it should probably be removed from non-mandatory...?

 

Point is, I can't build Clover anymore due to that error. If there is something I've missed, please, let me know.

 

2115821658_Screenshot2019-05-06at13_19_17.png.1eee70800bcb751fe4e1f301009b3c2a.png

Edited by arsradu

Share this post


Link to post
Share on other sites
On 5/6/2019 at 12:19 PM, arsradu said:

Uhm...guys? Is this intended? Cause it looks like a bug to me... Looks like VBoxHfs-64.uefi is present as both Mandatory and non-mandatory driver.

 

My guess is that it should probably be removed from non-mandatory...?

 

Point is, I can't build Clover anymore due to that error. If there is something I've missed, please, let me know.

 

2115821658_Screenshot2019-05-06at13_19_17.png.1eee70800bcb751fe4e1f301009b3c2a.png

 

 

I don't have this problem with both edk2 and udk2018 script. Which one do you use?

Share this post


Link to post
Share on other sites
Posted (edited)
2 hours ago, Matgen84 said:

I don't have this problem with both edk2 and udk2018 script. Which one do you use?

 

Well, the same one I've always used (attached)... And I'm using UDK2018. Not sure what changed and where. Which one are you using? :)) Also, is this with a clean environment?

CloverNew

Edited by arsradu

Share this post


Link to post
Share on other sites

I see no problem

total 43360
drwxr-xr-x  13 sergey  staff      442 May  7 21:28 .
drwxr-xr-x  15 sergey  staff      510 May  7 21:28 ..
drwxr-xr-x   5 sergey  staff      170 May  7 21:28 CloverCD
drwxr-xr-x   3 sergey  staff      102 May  7 21:28 CloverISO-4928
-rw-r--r--   1 sergey  staff  2882689 May  7 21:28 CloverISO-4928.tar.lzma
-rw-r--r--@  1 sergey  staff  9467800 May  7 21:28 Clover_v2.4k_r4928.pkg
-rw-r--r--   1 sergey  staff       68 May  7 21:28 Clover_v2.4k_r4928.pkg.md5
-rw-r--r--   1 sergey  staff  9385613 May  7 21:28 Clover_v2.4k_r4928.zip
drwxr-xr-x   3 sergey  staff      102 May  7 21:26 Resources
drwxr-xr-x   6 sergey  staff      204 May  7 21:27 build
drwxr-xr-x   3 sergey  staff      102 May  7 21:28 i386
drwxr-xr-x   3 sergey  staff      102 May  7 21:28 package
drwxr-xr-x   6 sergey  staff      204 May  7 21:27 utils
done!

 

Share this post


Link to post
Share on other sites
Posted (edited)
6 minutes ago, Slice said:

I see no problem


total 43360
drwxr-xr-x  13 sergey  staff      442 May  7 21:28 .
drwxr-xr-x  15 sergey  staff      510 May  7 21:28 ..
drwxr-xr-x   5 sergey  staff      170 May  7 21:28 CloverCD
drwxr-xr-x   3 sergey  staff      102 May  7 21:28 CloverISO-4928
-rw-r--r--   1 sergey  staff  2882689 May  7 21:28 CloverISO-4928.tar.lzma
-rw-r--r--@  1 sergey  staff  9467800 May  7 21:28 Clover_v2.4k_r4928.pkg
-rw-r--r--   1 sergey  staff       68 May  7 21:28 Clover_v2.4k_r4928.pkg.md5
-rw-r--r--   1 sergey  staff  9385613 May  7 21:28 Clover_v2.4k_r4928.zip
drwxr-xr-x   3 sergey  staff      102 May  7 21:26 Resources
drwxr-xr-x   6 sergey  staff      204 May  7 21:27 build
drwxr-xr-x   3 sergey  staff      102 May  7 21:28 i386
drwxr-xr-x   3 sergey  staff      102 May  7 21:28 package
drwxr-xr-x   6 sergey  staff      204 May  7 21:27 utils
done!

 

 

Yeah, everything looks fine in your case. 

 

Then it's probably just me... But I can't figure out what am I missing here... It's the same script I've always used. And this is actually the first time I'm encountering this issue...

 

Hmm... which Xcode version are you using? Are you still on High Sierra?

 

I doubt this is an Xcode issue... But then again, we've seen many weird issues in the past that were caused by that. So, I wouldn't be surprised if this is another one of those cases. Right now, I'm on Xcode 10.2.1.

 

If you think it could be Xcode, I can try to get an older version (such as 10.1) and see if that still occurs.

 

Also, I think it might be interesting to see how does it work if I'm trying to force it to build a specific version. Such as 4921 for example. Same environment, of course. Same Xcode. Just a different revision.

 

I'll let you know. :)

Edited by arsradu

Share this post


Link to post
Share on other sites
Posted (edited)

Fine here

11 minutes ago, arsradu said:

Then it's probably just me... But I can't figure out what am I missing here

Is bash the stock one?

echo $BASH_VERSION

result:

3.2.57(1)-release

 

Edited by vector sigma

Share this post


Link to post
Share on other sites
Posted (edited)
7 minutes ago, vector sigma said:

Fine here

Is bash the stock one?


echo $BASH_VERSION

 result:


3.2.57(1)-release

 

 

 

Same here.

 

1945849698_Screenshot2019-05-07at21_51_19.thumb.png.9f7fa4412facbcba853d11ce46e43d6f.png

 

Also, I can build 4291 just fine. I'll try 4293... Maybe there's something in that commit that it doesn't like.

 

One thing I've noticed with build 4291. The name is different.

676635730_Screenshot2019-05-07at21_53_15.thumb.png.91cb48a067c74fcb69f2929a4e6e385a.png

 

Edited by arsradu

Share this post


Link to post
Share on other sites
Posted (edited)
6 minutes ago, vector sigma said:

Using USE_APPLE_HFSPLUS_DRIVER?

 

Bingo! Indeed, I am using HFSPlus. But...does it check for that before it makes the build? Cause it didn't seem to do that with previous versions. Is this something new?

 

Also, 4923 displays the same error which seems to be caused by the same name... but I'm guessing it's not...caused by that? Since Slice was able to build the latest version with no issues?

 

I'm guessing there's something with commit 4923 that causes this. Maybe only when there's HFSPlus driver... But again, we're not talking about installing the build here. Just...creating it in the first place. If there's a check for that during this step, I wasn't aware of it. Of course, I could be wrong.

Edited by arsradu

Share this post


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

 

Bingo! Indeed, I am using HFSPlus. But...does it check for that before it makes the build? Cause it didn't seem to do that with previous versions. Is this something new?

This must be related to a very old commit, but anyway if you want use that functionality you have to ensure that 

Clover/FileSystems/HFSPlus/X64/HFSPlus.efi

exists :)

EDIT

probably VBoxHfs will be copied anyway and a change will be required, but this is another story.

Share this post


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

This must be related to a very old commit, but anyway if you want use that functionality you have to ensure that 


Clover/FileSystems/HFSPlus/X64/HFSPlus.efi

exists :)

 

Wait. I'm using HFSPlus in the sense that I've got it under Clover/CloverUEFIDrivers on the EFI partition. :)) Not that I'm using it to build Clover. That's what I was trying to say before. I wasn't aware that there's a function that checks what you have in your EFI folder before building Clover. :)) If there isn't, then this is not the case we're talking about.

 

And, as I said, building works perfectly fine with 4921, with the exact same setup.

Share this post


Link to post
Share on other sites
Posted (edited)
6 minutes ago, arsradu said:

 

Wait. I'm using HFSPlus in the sense that I've got it under Clover/CloverUEFIDrivers on the EFI partition. :)) Not that I'm using it to build Clover. That's what I was trying to say before. I wasn't aware that there's a function that checks what you have in your EFI folder before building Clover. :)) If there isn't, then this is not the case we're talking about.

 

And, as I said, building works perfectly fine with 4921, with the exact same setup.

Doesn't check if exist in your ESP in fact, but we're not talking about building Clover?

I mean that if you pass -DUSE_APPLE_HFSPLUS_DRIVER ...it expect to find Clover/FileSystems/HFSPlus/X64/HFSPlus.efi... in the source code directory.. otherwise Vboxhfs will be copied..

Edited by vector sigma

Share this post


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

Doesn't check if exist in your ESP in fact, but we're not talking about building Clover?

 

We are. That's the thing. I don't want it to build Clover with HFSPlus already included. I can add it myself once it's built. I just want it to build it. :)) It doesn't matter what I have in ESP.

 

And looking at commit 4923 I'm guessing some of that might be causing some of the drivers to have a duplicated name...which might cause the error? I don't know. I might be talking stupid here. But...I don't see why it would show that error with build 4923 (which it does indeed looks like it's trying to build two drivers with the same identical name) and not with 4921 (where it builds the VBoxHfs driver without the "-64" part). 

 

1764849128_Screenshot2019-05-07at22_19_26.thumb.png.763ed687ed4aa50106bec36d26f36f60.png

Share this post


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

 

We are. That's the thing. I don't want it to build Clover with HFSPlus already included. I can add it myself once it's built. I just want it to build it. :)) It doesn't matter what I have in ESP.

 

And looking at commit 4923 I'm guessing some of that might be causing some of the drivers to have a duplicated name...which might cause the error? I don't know. I might be talking stupid here. But...I don't see why it would show that error with build 4923 (which it does indeed looks like it's trying to build two drivers with the same identical name) and not with 4921 (where it builds the VBoxHfs driver without the "-64" part). 

 

1764849128_Screenshot2019-05-07at22_19_26.thumb.png.763ed687ed4aa50106bec36d26f36f60.png

Yes can be, but I though you find the culprit by using USE_APPLE_HFSPLUS_DRIVER. You said "Bingo" Lol

 

Share this post


Link to post
Share on other sites
1 minute ago, vector sigma said:

Yes can be, but I though you find the culprit by using USE_APPLE_HFSPLUS_DRIVER. You said "Bingo" Lol

 

 

Misunderstanding on my side... And lucky coincidence, I guess...? :))) Cause I actually do have HFSPlus in ESP.

 

Sorry, my bad. :) I hope it's all clear now. At least for this part of the problem. :))

Share this post


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

 

Misunderstanding on my side... And lucky coincidence, I guess...? :))) Cause I actually do have HFSPlus in ESP.

 

Sorry, my bad. :) I hope it's all clear now. At least for this part of the problem. :))

Found the problem, and is not a problem with Clover. Go there: https://github.com/acidanthera/AppleSupportPkg/releases

and download latest release.... it contains VBoxHfs.efi:hysterical::hysterical:

512366948_Schermata2019-05-07alle21_35_34.png.78461de2fe891902f483c40065a4285e.png

Share this post


Link to post
Share on other sites

So the fix is to use the one from Clover by skipping duplicated drivers. The change made by Slice per se has nothing to do with the bug. The bug is to copy a duplicated driver

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 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?
    • By fusion71au
      Clover r4989 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation.
       
      Tested with unlocked Workstation 15 running OSX 10.9 -->10.15 guest in Windows X64 host.
       
      Installation
      1. Download and unzip "EFI_Clover_r4989 for VMware.zip". Mount Clover-v2.4k-4989-X64.iso by double clicking on it.
      2. Mount your VM's EFI System Partition eg in terminal
      sudo diskutil mount disk0s1   3. Copy EFI folder from step 1 into the EFI partition
      4. Shutdown the VM, add bios.bootDelay = "3000" to your VM's vmx file
      5. Reboot your VM, press <F2> to access the VMware Boot Manager and add CLOVERX64.efi to the boot menu.
       
      Substitute your own unique and valid MLB and ROM variables in the /EFI/CLOVER/config.plist (Rt Variables section) to activate iMessage/Facetime on your VM.
×