Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30960 posts in this topic

Recommended Posts

vector sigma
vector sigma
Posted
Posted (edited)

@fusion71au can you try then this way? 

### Stage 0 ###
echo "Stage 0 - Writing ${diskloader} to ${bootrdisk}" >> "$install_log"
echo dd if=${bootrdisk} count=1 bs=512 of=/tmp/origMBR >> "$install_log"
dd if=${bootrdisk} count=1 bs=512 of=/tmp/origMBR
echo cp /tmp/origMBR /tmp/newMBR >> "$install_log"
cp /tmp/origMBR /tmp/newMBR
echo dd if="${DEST_VOL}/usr/standalone/i386/${diskloader}" of=/tmp/newMBR bs=440 count=1 conv=notrunc >> "$install_log"
dd if="${DEST_VOL}/usr/standalone/i386/${diskloader}" of=/tmp/newMBR bs=440 count=1 conv=notrunc
echo fdisk -f /tmp/newMBR -u -y ${bootrdisk} >> "$install_log"
fdisk -f /tmp/newMBR -u -y ${bootrdisk}
echo "" >> "$install_log"

just to ensure all is good.

 

EDIT
tested my self, working

Edited by vector sigma
  • Thanks 1
Matgen84
Matgen84
Posted
Posted (edited)

Hi

 

Wonderful embedded theme with commit r4639 :thumbsup_anim: 

 

Can we have a usb icon on vol_clover and vol_external. Please. it would be convenient for the macOS Installer pen drive for example.

 

 

Sorry for my bad english

 

Edited by Matgen84
  • Like 1
chris1111
chris1111
Posted
Posted
22 minutes ago, Matgen84 said:

Hi

 

Wonderful embedded theme with commit r4639 :thumbsup_anim: 

 

Can we have a usb icon on vol_clover and vol_external. Please. it would be convenient for the macOS Installer pen drive for example.

 

 

Sorry for my bad english

 

Yes I have USB Installer Mojave

screenshot7.thumb.png.a51149aae46fa7a59874f12592a07fb4.png

fantomas
fantomas
Posted
Posted

Hi Clover team   :)

 

As you can see, this topic has became expansive enough (more than 700 pages, 25 posts per page) and to continue posting further would be more counterproductive, IMO.

 

Without dwelling on that (I think you've all understood that no one is so crazy about reading the 700 pages to be up to date, right?), I suggest you to open another topic (v2.0  :P ) and continue to discuss.

  • Like 4
fusion71au
fusion71au
Posted
Posted (edited)
12 hours ago, vector sigma said:

@fusion71au can you try then this way?

just to ensure all is good.

 

Thanks to @vector sigma and @Slice for recent commits.  Boot0 is now correctly installed in MBR for legacy Clover installation :thumbsup_anim:.

 

Yes, all is good but spelling mistake in log for stage 1 "Writting" should be "Writing" :P.  Install log for r4643...
 

Spoiler

  


Installer version: v2.4k r4643 EFI bootloader
======================================================
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                  Apple_HFS Macintosh HD            121.0 GB   disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
   4:       Microsoft Basic Data WIN10                   334.7 GB   disk0s4
   5:           Windows Recovery                         472.9 MB   disk0s5
   6:           Linux Filesystem                         38.7 GB    disk0s6
   7:                 Linux Swap                         4.3 GB     disk0s7
/dev/disk1 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *15.9 GB    disk1
   1:                        EFI EFI                     209.7 MB   disk1s1
   2:                  Apple_HFS Mojave_Installer        15.5 GB    disk1s2
======================================================
Backing up EFI files

Backing up stage2 file /Volumes/Mojave_Installer/EFIROOTDIR/boot  to /Volumes/Mojave_Installer/EFI-Backups/r4630/2018-08-10-09h17/boot
Backing up /Volumes/Mojave_Installer/EFIROOTDIR/EFI folder to /Volumes/Mojave_Installer/EFI-Backups/r4630/2018-08-10-09h17/EFI
No Active Partition

Stage 0 - Writing boot0af to /dev/rdisk1
dd if=/dev/rdisk1 count=1 bs=512 of=/tmp/origMBR
cp /tmp/origMBR /tmp/newMBR
dd if=/Volumes/Mojave_Installer/usr/standalone/i386/boot0af of=/tmp/newMBR bs=440 count=1 conv=notrunc
fdisk -f /tmp/newMBR -u -y /dev/rdisk1

Stage 1 - Writting boot1f32 to /dev/rdisk1s1
dd if=/dev/rdisk1s1 count=1 bs=512 of=/tmp/origbs
boot volume format is FAT32
cp /tmp/boot1f32 /tmp/newbs
dd if=/tmp/origbs of=/tmp/newbs skip=3 seek=3 bs=1 count=87 conv=notrunc
dd if=/tmp/newbs of=/dev/rdisk1s1

Stage 2 - Written boot6 (x64) to /Volumes/ESP/boot

======================================================
=========== Clover EFI Installation Finish ===========
======================================================

 

 

 

 

Clover_v2.4k_r4643.pkg.zip

Edited by fusion71au
  • Like 2
vector sigma
vector sigma
Posted
Posted
4 minutes ago, fusion71au said:

Yes, all is good but spelling mistake in log for stage 1 "Writting" should be "Writing" :P.  Install log for r4643...

Sorry, I forgot about it. I'm still working on the package so next time I'll do the correction!

  • Like 2
  • Haha 1
Badruzeus
Badruzeus
Posted
Posted (edited)

@fusion71au any explanation why I can boot normally with Clover UEFI on my mach (sig) only with this? 

sudo newfs_msdos -F 32 -b 2048 -v EFI /dev/rdiskXsY

w/o "-b 2048" I get strange behaviour with it (CaseSensitive issue, not loaded EFI kexts, broken themes, etc).

Is this specific BIOS firmware limitation or what? TIA.

 

#EDIT: Yeah, my partition map is GUID for sure.

#EDIT2: Also tried with various ~Aptio*.efi driver, PartitionDxe, but still.. I need this for my ESP: 

Allocation Block Size:    2048 Bytes

 

Edited by Badruzeus
fusion71au
fusion71au
Posted
Posted
14 minutes ago, Badruzeus said:

@fusion71au any explanation why I can boot normally with Clover UEFI on my mach (sig) only with this? 


sudo newfs_msdos -F 32 -b 2048 -v EFI /dev/rdiskXsY

w/o "-b 2048" I get strange behaviour with it (CaseSensitive issue, not loaded EFI kexts, broken themes, etc).

Is this specific BIOS firmware limitation or what? TIA.

 

#EDIT: Yeah, my partition map is GUID for sure.

#EDIT2: Also tried with various ~Aptio*.efi driver, PartitionDxe, but still.. I need this for my ESP: 


Allocation Block Size:    2048 Bytes

 

 

Not sure but I'm guessing its probably something specific to your BIOS firmware. 

 

TBH, I've rarely had the need to format my EFI System partition and never specified block size, -b, when using newfs_msdos to format it - just omitted the setting and it usually works.  Apparently, 2KiB is the sector size for CD/DVD-ROMS?

  • Like 1
  • Thanks 1
Slice
Slice
Posted
Posted
7 hours ago, Badruzeus said:

@fusion71au any explanation why I can boot normally with Clover UEFI on my mach (sig) only with this? 


sudo newfs_msdos -F 32 -b 2048 -v EFI /dev/rdiskXsY

w/o "-b 2048" I get strange behaviour with it (CaseSensitive issue, not loaded EFI kexts, broken themes, etc).

Is this specific BIOS firmware limitation or what? TIA.

 

#EDIT: Yeah, my partition map is GUID for sure.

#EDIT2: Also tried with various ~Aptio*.efi driver, PartitionDxe, but still.. I need this for my ESP: 


Allocation Block Size:    2048 Bytes

 

You should use Fat.efi driver because the one from firmware is not good.

  • Thanks 1
Slice
Slice
Posted
Posted
13 hours ago, fantomas1 said:

Hi Clover team   :)

 

As you can see, this topic has became expansive enough (more than 700 pages, 25 posts per page) and to continue posting further would be more counterproductive, IMO.

 

Without dwelling on that (I think you've all understood that no one is so crazy about reading the 700 pages to be up to date, right?), I suggest you to open another topic (v2.0  :P ) and continue to discuss.

This thread is like a chat for short conversation: a question and an answer that not deserves separate thread.

For long-live solution that can be interesting in history we have to create separate topics.

  • Like 2
Matgen84
Matgen84
Posted
Posted (edited)

Hi

 

With  latest commit r4643, a security check box appears when I launch Clover to update (install). No check box with previous version r4639. I don't understand why?  

Capture d’écran 2018-08-10 à 18.10.32.png

Edited by Matgen84
chris1111
chris1111
Posted
Posted

macOS Mojave 10.14 Beta 6 (18A353d)

Xcode Version 10.0 beta 5 (10L221o)

Clover Revision

4644

UDK2018 Revision

37970

AptioMemoryFix Revision

#define APTIOMEMORYFIX_PROTOCOL_REVISION  22

ApfsDriverLoader Version

#define APFSDRIVERLOADER_VERSION L"1.3.2"

 

All good here

☟

Spoiler

1857826844_Capturedcranle2018-08-1122_13_42.thumb.png.2362dd9b0d5d66212dc12d05a4620ad0.png

 

  • Like 1
Badruzeus
Badruzeus
Posted
Posted
6 minutes ago, chris1111 said:

macOS Mojave 10.14 Beta 6 (18A353d)

Xcode Version 10.0 beta 5 (10L221o)

Clover Revision

4644

UDK2018 Revision

37970

AptioMemoryFix Revision

#define APTIOMEMORYFIX_PROTOCOL_REVISION  22

ApfsDriverLoader Version

#define APFSDRIVERLOADER_VERSION L"1.3.2"

 

All good here

☟

  Hide contents

1857826844_Capturedcranle2018-08-1122_13_42.thumb.png.2362dd9b0d5d66212dc12d05a4620ad0.png

 

Anyway, how to check *.efi driver version / revision using Terminal?

chris1111
chris1111
Posted
Posted (edited)
23 minutes ago, Badruzeus said:

Anyway, how to check *.efi driver version / revision using Terminal?



svn info /$HOME/src/UDK2018/Clover | grep "Revision" | awk '{print $2;}'

svn info /$HOME/src/UDK2018 | grep "Revision" | awk '{print $2;}'

grep REVISION /$HOME/src/UDK2018/AptioFixPkg/Include/Protocol/AptioMemoryFixProtocol.h

grep APFSDRIVERLOADER_VERSION /$HOME/src/UDK2018/ApfsSupportPkg/Platform/ApfsDriverLoader/Version.h

 



 

Edited by chris1111
Badruzeus
Badruzeus
Posted
Posted (edited)
5 minutes ago, chris1111 said:

svn info /$HOME/src/UDK2018/Clover | grep "Revision" | awk '{print $2;}'
svn info /$HOME/src/UDK2018 | grep "Revision" | awk '{print $2;}'
grep REVISION /$HOME/src/UDK2018/AptioFixPkg/Include/Protocol/AptioMemoryFixProtocol.h
grep APFSDRIVERLOADER_VERSION /$HOME/src/UDK2018/ApfsSupportPkg/Platform/ApfsDriverLoader/Version.h

I mean, from prebuilt *.efi binary driver.. but, thank you.

Edited by Badruzeus
Badruzeus
Badruzeus
Posted
Posted
2 minutes ago, chris1111 said:

which efi drivers

Any pre-installed *.efi drivers:

Spoiler 

0:980  0:000  === [ LoadDrivers ] =======================================
0:985  0:004  Loading ApfsDriverLoader-64.efi  status=Success
1:003  0:017   - driver needs connecting
1:003  0:000  Loading AppleImageCodec-64.efi  status=Success
1:004  0:000  Loading AppleKeyAggregator-64.efi  status=Success
1:005  0:000  Loading AppleUITheme-64.efi  status=Success
1:006  0:000  Loading AptioMemoryFix-64.efi  status=Success
1:006  0:000  Loading CsmVideoDxe-64.efi  status=Success
1:007  0:000   - driver needs connecting
1:007  0:000  Loading DataHubDxe-64.efi  status=Success
1:012  0:004  Loading FirmwareVolume-64.efi  status=Success
1:012  0:000  Loading FSInject-64.efi  status=Success
1:013  0:000  Loading HashServiceFix-64.efi  status=Success
1:014  0:000  Loading SMCHelper-64.efi  status=Success
1:015  0:000  Loading VBoxHfs-64.efi  status=Success
1:015  0:000   - driver needs connecting
1:015  0:000  3 drivers needs connecting ...
1:015  0:000  PlatformDriverOverrideProtocol not found. Installing ... Success
1:015  0:000  APFS driver loaded

 

 

chris1111
chris1111
Posted
Posted
34 minutes ago, Badruzeus said:

Any pre-installed *.efi drivers:

  Reveal hidden contents 


0:980  0:000  === [ LoadDrivers ] =======================================
0:985  0:004  Loading ApfsDriverLoader-64.efi  status=Success
1:003  0:017   - driver needs connecting
1:003  0:000  Loading AppleImageCodec-64.efi  status=Success
1:004  0:000  Loading AppleKeyAggregator-64.efi  status=Success
1:005  0:000  Loading AppleUITheme-64.efi  status=Success
1:006  0:000  Loading AptioMemoryFix-64.efi  status=Success
1:006  0:000  Loading CsmVideoDxe-64.efi  status=Success
1:007  0:000   - driver needs connecting
1:007  0:000  Loading DataHubDxe-64.efi  status=Success
1:012  0:004  Loading FirmwareVolume-64.efi  status=Success
1:012  0:000  Loading FSInject-64.efi  status=Success
1:013  0:000  Loading HashServiceFix-64.efi  status=Success
1:014  0:000  Loading SMCHelper-64.efi  status=Success
1:015  0:000  Loading VBoxHfs-64.efi  status=Success
1:015  0:000   - driver needs connecting
1:015  0:000  3 drivers needs connecting ...
1:015  0:000  PlatformDriverOverrideProtocol not found. Installing ... Success
1:015  0:000  APFS driver loaded

 

 

maybe look at UDK2018/Build/Cover ?

  • Like 1
chris1111
chris1111
Posted
Posted (edited)

InstallBootsectors/postinstall

the script not cleanup /tmp file

 

Spoiler

50Capture.thumb.png.90dba32915b994d41b6c926fc8786a07.png

 

not working with the scrip but terminal is ok

Strange now I rebuild new package and the file changing the name

newbs, origbs

I need terminal for removing the file

It is not really important because is remove at reboot

Spoiler

51Capture.png.adcc3691383fa765dd700e3d3ab9e4a1.png

 

Edited by chris1111
put image in spoiler and clean my post
Badruzeus
Badruzeus
Posted
Posted
8 minutes ago, Tetonne said:

how can i upgrade my Window 10 on a dual boot (window/HS) same HD?

the upgrade always failed

==> easy win 10 upgrade on a dual boot clover HD ;) 

It maybe, your configuration issue? Not becaused of Clover. (not mentioning Legacy/UEFI)

  • Like 1
 Share
Go to topic listing
×
×
  • Create New...