Jump to content
30960 posts in this topic

Recommended Posts

Legacy boot is not possible from fat16 because of fat structure.

And I am not sure if UEFI boot is possible.

 

On 2/1/2020 at 6:31 PM, freakermonguer said:

I noticed something on my system

If I prepare a UEFI install USB for OSx it's shown on the BIOS Boot menu as UEFI USB

If I install Clover on any drive as UEFI boot it doesn't detect it. It only boots Clover if I install the legacy version.

 

My drive is formatted as GPT using the Disk Utility. And made the main partitions using this tool.

 

Is there something missing in the GPT format I did so the computer doesn't detects the EUFI partition as such?

 

I also may suppose that UEFI BIOS exists which allows UEFI boot only from USB not from SATA.

On 2/3/2020 at 7:16 AM, vector sigma said:

I'm pretty sure I haven't seen boot sectors in the source code to load a Fat16 partition. Is not?

Didn't say macOS can't see fat16 partitions, only that the program I made did not allow to select them, right or wrong it is.

Well, GPT formatted disk <= 2GB doesn't even create the EFI partition in macOS (if I'm not mistaken). So for this I can't image why Fat16 should be involved at all.  Had to say that I don't know if some other OS create the ESP in f16 which eventually can make sense for UEFI loading.

 

Booting is entirely different, that was written to load the next stage from the ESP. The ESP is supposed to be FAT32, that does not mean it is, the partition could be formatted to any file system. The reason there is a problem with not explicitly forcing FAT32 is because the specification for FAT specifies the amount of clusters that a specific variant can use. Please see here, https://en.wikipedia.org/wiki/File_Allocation_Table#Nomenclature.

 

On 2/3/2020 at 10:12 AM, bronxteck said:

my drive is a 1 terabyte Samsung ssd with 4k offset the other one is a 256gb M.2 with 512k offset just incase I should have specified.

so can we add that to the clover app. or does Catalina disregard it?

EDIT: after mounting EFI i did a dot_clean -m /volumes/EFI then a sudo mdutil -i off /volumes/EFI lets see how that holds up had to manually remove some of the left over .files

 

The dot_clean only operates on files beginning with both a dot and an underscore, metadata, any other file beginning with dot were created for some other reason.

13 hours ago, Slice said:

Legacy boot is not possible from fat16 because of fat structure.

And I am not sure if UEFI boot is possible.

 

Depends on whether the FAT file system driver only supports FAT32 or detects and supports any variant.

 

13 hours ago, Slice said:

I also may suppose that UEFI BIOS exists which allows UEFI boot only from USB not from SATA.

 

Sometimes, if the disk is internal and it has the legacy boot active flag in the MBR then it will not check for UEFI, I used to have a gigabyte mobo that did this. If you remove the flag by zeroing the last two bytes of the MBR, then the disk will be recognized as GPT and offer the UEFI: option, also \EFI\BOOT\BOOTX64.efi has to exist, obviously or there is nothing to boot. You need to make a boot entry for \EFI\CLOVER\CLOVERX64.efi.

 

EDIT: Slice, that was weirdly a response to you and the person you responded to, lol.

Edited by apianti
47 minutes ago, apianti said:

The ESP is supposed to be FAT32, that does not mean it is, the partition could be formatted to any file system

Exatly. Why only hfs, Fat32 and ExFat are supported by the new program: users cant install on it...so users will not ask why Clover wont boot.

 

e.g. (for the pkg) "I installed Clover... and doesn't work! why? is SIP or Catalina..it's a bug?" ...but:

if [[ -n $(cat /tmp/origbs | grep FAT16) ]]; then
      echo "boot volume format is FAT16" >> "$tmp_log"
      echo "No Stage1 was written" >> "$tmp_log"
    else

Lol

Edited by vector sigma
5 hours ago, vector sigma said:

Exatly. Why only hfs, Fat32 and ExFat are supported by the new program: users cant install on it...so users will not ask why Clover wont boot.

 

e.g. (for the pkg) "I installed Clover... and doesn't work! why? is SIP or Catalina..it's a bug?" ...but:


if [[ -n $(cat /tmp/origbs | grep FAT16) ]]; then
      echo "boot volume format is FAT16" >> "$tmp_log"
      echo "No Stage1 was written" >> "$tmp_log"
    else

Lol

 

Except he is UEFI booting, so why does legacy booting have anything to do with whether or not his ESP is formatted FAT32 correctly? So, yeah... lol.

 

EDIT: Or that you don't need to use the package at all to install...

Edited by apianti

When installing 10.15.x  (or upgrading from 10.14.6), what is the correct value for

<key>DefaultVolume</key> in config.plist - so that it auto selects the correct partition during all the multiple reboots that take place?

  • Like 1
35 minutes ago, exquirentibus said:

When installing 10.15.x  (or upgrading from 10.14.6), what is the correct value for

<key>DefaultVolume</key> in config.plist - so that it auto selects the correct partition during all the multiple reboots that take place?

		<key>DefaultVolume</key>
		<string>LastBootedVolume</string>

 

  • Like 1
1 hour ago, exquirentibus said:

When installing 10.15.x  (or upgrading from 10.14.6), what is the correct value for

<key>DefaultVolume</key> in config.plist - so that it auto selects the correct partition during all the multiple reboots that take place?

 

There is @ellaosx good solution.

 

Personnally, I use this one: my boot volume is called Catalina, replace by yours.

 

<key>DefaultVolume</key>
<string>Catalina</string>

 

14 hours ago, apianti said:

 

Depends on whether the FAT file system driver only supports FAT32 or detects and supports any variant.

 

 

I have to remind that legacy boot have stages:

1. BIOS jumps to a small program written into boot0 sector from MBR block 0 on a device.

2. boot0 program searches a bootable partition containing boot1 program in the first block. Jump to boot1.

3. boot1 searches for file boot on the partition. So it must know file system on the partition.

Because of that we have three kind of boot1

boot1f32 for FAT32 partition

boot1h for HFS+ partition

boot1x for exFAT partition

And I see AnV written boot1n for NTFS partition.

That's all. We have no boot1 for APFS, EXT2/4 etc.

As well boot1f32 will not work on FAT16 because for slightly different offsets of FAT table and different signature. I may propose that good programmer is able to write boot1f16 but I see no such file yet.

 

  • Like 3

does clover function properly from NVME? i just did a fresh install from sata recovery to a NVME drive. after osx booted then new install i mounted the efi on the nvme and transferred the EFI folder i just booted from to it. in bios i set the boot path to point to clover boot file. my dilemma is nvme will boot clover but i have no partitions to select from even if i hit F3. is clover missing a GUID for nvme?

it is seen in bios and from usb with the same efi folder. just no volumes to choose from when clover is booted on nvme efi

as if HFS.plus or APFS was missing

Edited by bronxteck

APFS does not have an MBR type code assigned to it and is not supposed to be installed on MBR.

On a GPT-partitioned disk, if it has an ESP, you can perform legacy boot for legacy Clover

  • Put boot6/boot7 on the ESP
  • Install boot1f32 as the boot sector of the ESP
  • Install boot0 as boot code on the Protective MBR

Once CloverEFI is running, if it has EFI driver for APFS or any other filesystem (NTFS, EXT4), then it will continue to work with the EFI driver.

I was responding to the fat discussion.

 

As for your question - if your EFI firmware can load Clover from the ESP it's an indication that it has nvme dxe loaded.  If it has a nvme dxe loaded then all nvme ssds and their partitions should already be accessible to Clover.

Did you copy the VBoxHfs.efi and ApfsDriverLoader.efi drivers to the drivers directory on the nvme Clover?  Because if it doesn't have those, Clover won't be able to scan HFS+ and APFS partitions respectively.

I suggest you look at your Clover log to see what it's scanning and the result of the scan.  Another thing you can do is start EFI shell from Clover - then go through the fsX: devices (shown when shell starts or with map command), and list them to check if you see your HFS+ or APFS partitions among them.  Also do drivers command from the shell to list the loaded dxe to see if you have nvme dxe and which filesystem dxes you have loaded.

Edited by Zenith432
6 hours ago, bronxteck said:

does clover function properly from NVME? i just did a fresh install from sata recovery to a NVME drive. after osx booted then new install i mounted the efi on the nvme and transferred the EFI folder i just booted from to it. in bios i set the boot path to point to clover boot file. my dilemma is nvme will boot clover but i have no partitions to select from even if i hit F3. is clover missing a GUID for nvme?

it is seen in bios and from usb with the same efi folder. just no volumes to choose from when clover is booted on nvme efi

as if HFS.plus or APFS was missing

I have zero issues with my ADATA SX8200 Pro NVME drive booting clover (or OpenCore for that matter.)

22 hours ago, bronxteck said:

does clover function properly from NVME? i just did a fresh install from sata recovery to a NVME drive. after osx booted then new install i mounted the efi on the nvme and transferred the EFI folder i just booted from to it. in bios i set the boot path to point to clover boot file. my dilemma is nvme will boot clover but i have no partitions to select from even if i hit F3. is clover missing a GUID for nvme?

it is seen in bios and from usb with the same efi folder. just no volumes to choose from when clover is booted on nvme efi

as if HFS.plus or APFS was missing

 

It functions in both legacy and UEFI if your firmware supports NVMe drives (you can see the drive in your firmware boot selection). You can also boot in legacy by using another non-NVMe disk to boot clover and using the NVMe driver that comes from EDK2, then you can boot UEFI from the NVMe using clover legacy.

 

21 hours ago, Zenith432 said:

APFS does not have an MBR type code assigned to it and is not supposed to be installed on MBR.

On a GPT-partitioned disk, if it has an ESP, you can perform legacy boot for legacy Clover

  • Put boot6/boot7 on the ESP
  • Install boot1f32 as the boot sector of the ESP
  • Install boot0 as boot code on the Protective MBR

Once CloverEFI is running, if it has EFI driver for APFS or any other filesystem (NTFS, EXT4), then it will continue to work with the EFI driver.

 

How we get into APFS now? I was literally talking about one specific situation for a UEFI boot and everyone is talking about legacy booting like I don't know how it works, lol. I was just saying that the UEFI FAT driver should be able to recognize any variant of FAT, but that some only recognize FAT32 because that is what the ESP is supposed to be formatted. However, because it is so small, most of the time it is actually formatted FAT16 unless you specifically force that it is FAT32. This is a situation that can lead to unrecognized UEFI boot disk.

 

20 hours ago, bronxteck said:

is that pertaining to my Issue with an NVME drive? or the fat discussion between slice, appi and matgen?

 

This discussion about FAT turned into a discussion about legacy booting... lmao.

 

20 hours ago, Zenith432 said:

I was responding to the fat discussion.

 

As for your question - if your EFI firmware can load Clover from the ESP it's an indication that it has nvme dxe loaded.  If it has a nvme dxe loaded then all nvme ssds and their partitions should already be accessible to Clover.

Did you copy the VBoxHfs.efi and ApfsDriverLoader.efi drivers to the drivers directory on the nvme Clover?  Because if it doesn't have those, Clover won't be able to scan HFS+ and APFS partitions respectively.

I suggest you look at your Clover log to see what it's scanning and the result of the scan.  Another thing you can do is start EFI shell from Clover - then go through the fsX: devices (shown when shell starts or with map command), and list them to check if you see your HFS+ or APFS partitions among them.  Also do drivers command from the shell to list the loaded dxe to see if you have nvme dxe and which filesystem dxes you have loaded.

 

The other UEFI problems, no drivers or incorrect paths... haha

 

16 hours ago, pkdesign said:

I have zero issues with my ADATA SX8200 Pro NVME drive booting clover (or OpenCore for that matter.)

 

Yeah, they for sure work in both. You will usually have more trouble with macOS than the booter....

 

13 hours ago, bronxteck said:

Zenith your 100% correct my path was wrong i dropped my efi into the blank efi folder /Volumes/EFI/EFI/ instead of replacing the one on root of the NVME drive. LOL i guess old dogs can still wet the floors. thanks for your reply.

 

Weird, you should have still booted. Your firmware should have failed and tried the next boot option, unless it just went back to the boot selection menu and you were unsure why? I do way more stupid stuff on a daily basis....

On 2/5/2020 at 1:07 AM, Matgen84 said:

Hi @vector sigma @apianti

 

I don't understand what is the correct FAT format for ESP: Fat16 or Fat32! for Clover.

 

The ESP is always supposed to be FAT32.

  • Thanks 1

How to solve the addressing error of dual network card in ASUS z87-deluxe? When using OC boot, there will be no problem. When using clover boot, from the start log, we can see that there is a problem in clover days. 0:100 0:000 PCI (00|07:00.00) : 10EC 8168 class=020000。 The address of rtl8111 network card is under Intel. Normally, under Realtek, 0:100 0:000 PCI (00| 09:00.00): 14e4 43b1 class = 028000 will be driven. 

 

preboot.log.zip

Edited by jinbingmao
2 hours ago, jinbingmao said:

How to solve the addressing error of dual network card in ASUS z87-deluxe? When using OC boot, there will be no problem. When using clover boot, from the start log, we can see that there is a problem in clover days. 0:100 0:000 PCI (00|07:00.00) : 10EC 8168 class=020000。 The address of rtl8111 network card is under Intel. Normally, under Realtek, 0:100 0:000 PCI (00| 09:00.00): 14e4 43b1 class = 028000 will be driven. 

 

preboot.log.zip

No, Clover is right.

class=020000 is Ethernet card which driven by Mieze's driver 

4:542  0:006  ->Extra kext: EFI\CLOVER\kexts\10.15\RealtekRTL8111.kext (v.2.3.0d7)

class=028000 is for WiFi card which is not the case.

anyone who has clover pkg build fail?

i'm using catalina 10.15.4 beta1

 



  -------------------------------

  Building Clover Install Package

  -------------------------------

 

====================== Preinstall ======================

[BUILD] Pre

package/buildpkg.sh: line 1609: xar: command not found

===================== Installation =====================

[BUILD] UEFI.only

package/buildpkg.sh: line 1609: xar: command not found

================== Target ESP ==========================

[BUILD] Target.ESP

package/buildpkg.sh: line 1609: xar: command not found

=================== BiosBoot ===========================

[BUILD] BiosBoot

package/buildpkg.sh: line 1609: xar: command not found

===================== Utils ============================

[BUILD] Utils

package/buildpkg.sh: line 1609: xar: command not found

===================== EFI folder =======================

[BUILD] EFIFolder

package/buildpkg.sh: line 1609: xar: command not found

===================== off drivers ======================

[BUILD] off

package/buildpkg.sh: line 1609: xar: command not found

===================== BootLoaders ======================

[BUILD] AltBoot

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] bootNo

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] boot0af

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] boot0ss

package/buildpkg.sh: line 1609: xar: command not found

====================== CloverEFI =======================

[BUILD] cloverEFI.64.sata

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] cloverEFI.64.blockio

package/buildpkg.sh: line 1609: xar: command not found

================= drivers64 mandatory ==================

[BUILD] AudioDxe

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] FSInject

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] SMCHelper

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] XhciDxe

package/buildpkg.sh: line 1609: xar: command not found

===================== drivers64 ========================

=============== drivers64 FileSystem ===================

[BUILD] ApfsDriverLoader

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] GrubEXFAT

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] GrubISO9660

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] GrubNTFS

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] GrubUDF

package/buildpkg.sh: line 1609: xar: command not found

=============== drivers64 FileVault2 ===================

[BUILD] AppleImageCodec

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] AppleKeyAggregator

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] AppleUITheme

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] FirmwareVolume

package/buildpkg.sh: line 1609: xar: command not found

=============== drivers64 UEFI mandatory ===============

[BUILD] AudioDxe.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] DataHubDxe.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] FSInject.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] SMCHelper.UEFI

package/buildpkg.sh: line 1609: xar: command not found

=================== drivers64 UEFI =====================

============= drivers64 UEFI HID ========================

[BUILD] AptioInputFix.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] Ps2MouseDxe.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] UsbKbDxe.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] UsbMouseDxe.UEFI

package/buildpkg.sh: line 1609: xar: command not found

============= drivers64 UEFI FileSystem =================

[BUILD] ApfsDriverLoader.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] Fat.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] VBoxExt2.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] VBoxExt4.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] VBoxHfs.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] VBoxIso9600.UEFI

package/buildpkg.sh: line 1609: xar: command not found

============= drivers64 UEFI MemoryFix =================

[BUILD] AptioMemoryFix.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] OsxAptioFix3Drv.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] OsxAptioFixDrv.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] OsxLowMemFixDrv.UEFI

package/buildpkg.sh: line 1609: xar: command not found

============= drivers64 UEFI FileVault2 ================

[BUILD] AppleImageCodec.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] AppleKeyAggregator.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] AppleKeyFeeder.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] AppleUITheme.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] FirmwareVolume.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] HashServiceFix.UEFI

package/buildpkg.sh: line 1609: xar: command not found

============= drivers64 UEFI Other ======================

[BUILD] CsmVideoDxe.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] EmuVariableUefi.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] EnglishDxe.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] NvmExpressDxe.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] OsxFatBinaryDrv.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] PartitionDxe.UEFI

package/buildpkg.sh: line 1609: xar: command not found

===================== RC Scripts =======================

[BUILD] rc.scripts.on.target

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] rc.scripts.on.all.volumes

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] rc.scripts.core

package/buildpkg.sh: line 1609: xar: command not found

================= Optional RC Scripts ==================

[BUILD] disable_sleep_proxy_client

package/buildpkg.sh: line 1609: xar: command not found

======================== Themes ========================

[BUILD] Clovy

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] BGM

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] cesium

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] CloverThemeManager

package/buildpkg.sh: line 1609: xar: command not found

==================== Clover Prefpane ===================

[BUILD] CloverPrefpane

package/buildpkg.sh: line 1609: xar: command not found

================= Post =================

[BUILD] Post

package/buildpkg.sh: line 1609: xar: command not found

4 minutes ago, Sherlocks said:

anyone who has clover pkg build fail?

i'm using catalina 10.15.4 beta1

 

 

  Reveal hidden contents

 

 


  -------------------------------

  Building Clover Install Package

  -------------------------------

 

====================== Preinstall ======================

[BUILD] Pre

package/buildpkg.sh: line 1609: xar: command not found

===================== Installation =====================

[BUILD] UEFI.only

package/buildpkg.sh: line 1609: xar: command not found

================== Target ESP ==========================

[BUILD] Target.ESP

package/buildpkg.sh: line 1609: xar: command not found

=================== BiosBoot ===========================

[BUILD] BiosBoot

package/buildpkg.sh: line 1609: xar: command not found

===================== Utils ============================

[BUILD] Utils

package/buildpkg.sh: line 1609: xar: command not found

===================== EFI folder =======================

[BUILD] EFIFolder

package/buildpkg.sh: line 1609: xar: command not found

===================== off drivers ======================

[BUILD] off

package/buildpkg.sh: line 1609: xar: command not found

===================== BootLoaders ======================

[BUILD] AltBoot

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] bootNo

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] boot0af

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] boot0ss

package/buildpkg.sh: line 1609: xar: command not found

====================== CloverEFI =======================

[BUILD] cloverEFI.64.sata

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] cloverEFI.64.blockio

package/buildpkg.sh: line 1609: xar: command not found

================= drivers64 mandatory ==================

[BUILD] AudioDxe

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] FSInject

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] SMCHelper

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] XhciDxe

package/buildpkg.sh: line 1609: xar: command not found

===================== drivers64 ========================

=============== drivers64 FileSystem ===================

[BUILD] ApfsDriverLoader

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] GrubEXFAT

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] GrubISO9660

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] GrubNTFS

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] GrubUDF

package/buildpkg.sh: line 1609: xar: command not found

=============== drivers64 FileVault2 ===================

[BUILD] AppleImageCodec

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] AppleKeyAggregator

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] AppleUITheme

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] FirmwareVolume

package/buildpkg.sh: line 1609: xar: command not found

=============== drivers64 UEFI mandatory ===============

[BUILD] AudioDxe.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] DataHubDxe.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] FSInject.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] SMCHelper.UEFI

package/buildpkg.sh: line 1609: xar: command not found

=================== drivers64 UEFI =====================

============= drivers64 UEFI HID ========================

[BUILD] AptioInputFix.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] Ps2MouseDxe.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] UsbKbDxe.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] UsbMouseDxe.UEFI

package/buildpkg.sh: line 1609: xar: command not found

============= drivers64 UEFI FileSystem =================

[BUILD] ApfsDriverLoader.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] Fat.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] VBoxExt2.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] VBoxExt4.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] VBoxHfs.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] VBoxIso9600.UEFI

package/buildpkg.sh: line 1609: xar: command not found

============= drivers64 UEFI MemoryFix =================

[BUILD] AptioMemoryFix.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] OsxAptioFix3Drv.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] OsxAptioFixDrv.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] OsxLowMemFixDrv.UEFI

package/buildpkg.sh: line 1609: xar: command not found

============= drivers64 UEFI FileVault2 ================

[BUILD] AppleImageCodec.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] AppleKeyAggregator.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] AppleKeyFeeder.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] AppleUITheme.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] FirmwareVolume.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] HashServiceFix.UEFI

package/buildpkg.sh: line 1609: xar: command not found

============= drivers64 UEFI Other ======================

[BUILD] CsmVideoDxe.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] EmuVariableUefi.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] EnglishDxe.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] NvmExpressDxe.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] OsxFatBinaryDrv.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] PartitionDxe.UEFI

package/buildpkg.sh: line 1609: xar: command not found

===================== RC Scripts =======================

[BUILD] rc.scripts.on.target

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] rc.scripts.on.all.volumes

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] rc.scripts.core

package/buildpkg.sh: line 1609: xar: command not found

================= Optional RC Scripts ==================

[BUILD] disable_sleep_proxy_client

package/buildpkg.sh: line 1609: xar: command not found

======================== Themes ========================

[BUILD] Clovy

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] BGM

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] cesium

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] CloverThemeManager

package/buildpkg.sh: line 1609: xar: command not found

==================== Clover Prefpane ===================

[BUILD] CloverPrefpane

package/buildpkg.sh: line 1609: xar: command not found

================= Post =================

[BUILD] Post

package/buildpkg.sh: line 1609: xar: command not found
 

 

 

But no issue on 10.15.3 right ?

21 minutes ago, Slice said:

I have no 10.15.4 to check. What is happen? What are the messages?

 

hi slice.

pkg build will be broken with this message.

 

i'm not sure this issue in only 10.15.4 beta1.

 

        # Create the package

        (cd "${packagePath}/Temp" && xar -c -f "${packagePath}/../${packageName}.pkg" --compression none .)

 

 

 


 -------------------------------

  Building Clover Install Package

  -------------------------------

 

====================== Preinstall ======================

[BUILD] Pre

package/buildpkg.sh: line 1609: xar: command not found

===================== Installation =====================

[BUILD] UEFI.only

package/buildpkg.sh: line 1609: xar: command not found

================== Target ESP ==========================

[BUILD] Target.ESP

package/buildpkg.sh: line 1609: xar: command not found

=================== BiosBoot ===========================

[BUILD] BiosBoot

package/buildpkg.sh: line 1609: xar: command not found

===================== Utils ============================

[BUILD] Utils

package/buildpkg.sh: line 1609: xar: command not found

===================== EFI folder =======================

[BUILD] EFIFolder

package/buildpkg.sh: line 1609: xar: command not found

===================== off drivers ======================

[BUILD] off

package/buildpkg.sh: line 1609: xar: command not found

===================== BootLoaders ======================

[BUILD] AltBoot

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] bootNo

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] boot0af

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] boot0ss

package/buildpkg.sh: line 1609: xar: command not found

====================== CloverEFI =======================

[BUILD] cloverEFI.64.sata

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] cloverEFI.64.blockio

package/buildpkg.sh: line 1609: xar: command not found

================= drivers64 mandatory ==================

[BUILD] AudioDxe

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] FSInject

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] SMCHelper

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] XhciDxe

package/buildpkg.sh: line 1609: xar: command not found

===================== drivers64 ========================

=============== drivers64 FileSystem ===================

[BUILD] ApfsDriverLoader

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] GrubEXFAT

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] GrubISO9660

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] GrubNTFS

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] GrubUDF

package/buildpkg.sh: line 1609: xar: command not found

=============== drivers64 FileVault2 ===================

[BUILD] AppleImageCodec

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] AppleKeyAggregator

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] AppleUITheme

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] FirmwareVolume

package/buildpkg.sh: line 1609: xar: command not found

=============== drivers64 UEFI mandatory ===============

[BUILD] AudioDxe.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] DataHubDxe.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] FSInject.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] SMCHelper.UEFI

package/buildpkg.sh: line 1609: xar: command not found

=================== drivers64 UEFI =====================

============= drivers64 UEFI HID ========================

[BUILD] AptioInputFix.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] Ps2MouseDxe.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] UsbKbDxe.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] UsbMouseDxe.UEFI

package/buildpkg.sh: line 1609: xar: command not found

============= drivers64 UEFI FileSystem =================

[BUILD] ApfsDriverLoader.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] Fat.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] VBoxExt2.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] VBoxExt4.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] VBoxHfs.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] VBoxIso9600.UEFI

package/buildpkg.sh: line 1609: xar: command not found

============= drivers64 UEFI MemoryFix =================

[BUILD] AptioMemoryFix.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] OsxAptioFix3Drv.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] OsxAptioFixDrv.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] OsxLowMemFixDrv.UEFI

package/buildpkg.sh: line 1609: xar: command not found

============= drivers64 UEFI FileVault2 ================

[BUILD] AppleImageCodec.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] AppleKeyAggregator.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] AppleKeyFeeder.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] AppleUITheme.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] FirmwareVolume.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] HashServiceFix.UEFI

package/buildpkg.sh: line 1609: xar: command not found

============= drivers64 UEFI Other ======================

[BUILD] CsmVideoDxe.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] EmuVariableUefi.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] EnglishDxe.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] NvmExpressDxe.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] OsxFatBinaryDrv.UEFI

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] PartitionDxe.UEFI

package/buildpkg.sh: line 1609: xar: command not found

===================== RC Scripts =======================

[BUILD] rc.scripts.on.target

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] rc.scripts.on.all.volumes

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] rc.scripts.core

package/buildpkg.sh: line 1609: xar: command not found

================= Optional RC Scripts ==================

[BUILD] disable_sleep_proxy_client

package/buildpkg.sh: line 1609: xar: command not found

======================== Themes ========================

[BUILD] Clovy

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] BGM

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] cesium

package/buildpkg.sh: line 1609: xar: command not found

[BUILD] CloverThemeManager

package/buildpkg.sh: line 1609: xar: command not found

==================== Clover Prefpane ===================

[BUILD] CloverPrefpane

package/buildpkg.sh: line 1609: xar: command not found

================= Post =================

[BUILD] Post

package/buildpkg.sh: line 1609: xar: command not found
 

 

Edited by Sherlocks
×
×
  • Create New...