Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30,171 posts in this topic

Recommended Posts

Matgen84
Matgen84
Posted
Posted (edited)
37 minutes ago, Jief_Machak said:

Even in an UEFI virtual machine (VMWare) ?


New screenshot from Parallels Desktop v16 (from USB Big Sur Installer connected)

 

Spoiler

84602535_Capturedcran2020-09-1417_19_34.thumb.png.4f4c688256b150295659ecfc5208a061.png

 

Edited by Matgen84
  • Haha 1
Link to comment
Share on other sites
Slice
Slice
Posted
Posted
3 hours ago, Jief_Machak said:

Even in an UEFI virtual machine (VMWare) ? 

        if (FileExists(Volume->RootDir, CLOVER_MEDIA_FILE_NAME)) {
          DBG(" Found Clover\n");
          // Volume->BootType = BOOTING_BY_EFI;
          AddCloverEntry(CLOVER_MEDIA_FILE_NAME, L"Clover Boot Options", Volume);
          break;
        }

 

  • Like 1
Link to comment
Share on other sites
fusion71au
fusion71au
Posted
Posted
9 hours ago, Jief_Machak said:

Sorry to come back to that but I'm intrigued. I boot UEFI, so I understand I should see this entry. For me, the clover is the about menu. Could someone send me a screenshot of where is it ?

 

 

7 hours ago, Slice said:

"Clover" entry will be absent in virtual machine. It is for real boot.

 

For me, "Clover Boot Options" menu appears in real hardware and VMware but icon varies depending on the theme eg BGM_SVG theme on real hardware (system1 NUC6i5SYH in signature) has 4 leaf Clover icon...

 

Spoiler

screenshot0.thumb.png.29956d691249efa7755c4cd8088c818c.pngscreenshot1.thumb.png.fbabbf805c2c8f3cea9fb9facd2e324c.png

 

eg embedded theme on VMware has triangle icon for "Clover Boot Options", 4 leaf Clover icon for "About" menu...

Spoiler

1283429558_CloverBootOptions1.thumb.png.0efcabaf7d7280c016b2d08918574133.png1397181919_CloverBootOptions2.thumb.png.38cba0005d77327e5ce2956f7a9862bc.png

 

  • Like 1
Link to comment
Share on other sites
Jief_Machak
Jief_Machak
Posted
Posted

I think I understood why I don't have it : I usually change the GPT type of my EFI partition to Basic Mircrosoft Data, so the partition mount at startup. Although I should try fstab instead of changing type because with no EFI type partition, Apple tools to install, partition, resize usually silently fail...

  • Like 2
Link to comment
Share on other sites
Jief_Machak
Jief_Machak
Posted
Posted
1 hour ago, maclinuxG4 said:

only legacy EFI (mac os) are to use

Is that an answer to my message? I was talking about the GPT type of the partition. "Mircrosoft basic Data" is the type 0700 in gdisk. EFI is EF00. It's partition type, nothing todo with OS that's on it.

 

On my computer at least, if there is no EF00 partition, the first 0700 partition will be use to boot. So, after installation, I usually change the type to 0700. That way, macOS sees it as a regular FAT partition and therefore mount it without the need to use command line.

I just have to remember to switch back to EF00 if I want to install something new with the Apple installer.

Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted
43 minutes ago, mifjpn said:

Thank you for your effort.
I tried the following
% git pull
Updating f4b344513..acc2fea81
% sh ./ebuild.sh --buildtarget=DEBUG
Copy .../CloverBootloader/Build/Clover/DEBUG_XCODE8/X64/CLOVERX64.efi to ../EFI/CLOVERX64.efi,and ../EFI/BOOT/BOOTX64.efi

I select Boot Big Sur from preboot,(with/without OcQuirks.efi)

 

I select catalina,(with/without OcQuirks.efi)

 

debug.log

Thank you.

 

Idem here with Z390 Aorus Master :bye: when try to boot USB Big Sur installer.

 

 

  • Sad 1
Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted

Thank you for your great job @Jief_Machak
I tried the following
% git pull
Updating acc2fea81..346661efd
 ./ebuild.sh --xcode8 --buildtarget=DEBUG --define=DEBUG_ON_SERIAL_PORT

Magic copy (your script) /EFI/CLOVERX64.efi,and ../EFI/BOOT/BOOTX64.efi

 

I try to boot Big Sur USB Installer without success: stuck at OC: failed to load configuration

 

Spoiler

1.thumb.jpg.d9a015cb4f9c38781082e6400925dadd.jpg

 

Some compilation messages comes back 

 

Spoiler

Compressing DUETEFIMainFv.FV ...

Encoding

Compressing DxeCore.efi ...

Encoding

Compressing DxeIpl.efi ...

Encoding

Generate Loader Image ...

Created /Users/mathieu/test_src/cloverbootloader/Build/Clover/DEBUG_XCODE8/FV/Efildr64

warning: boot file bigger than low-ebda permits, switching to --std-ebda

GenPage...

/Users/mathieu/test_src/cloverbootloader/Build/Clover/DEBUG_XCODE8/FV/Efildr20Pure: ERROR 16386: Invalid parameter option

  Input file size (0x825ac) exceeds the Page Table Offset (0x70000)

 

Debug.log attached

 

 

debug.log

Link to comment
Share on other sites
Slice
Slice
Posted
Posted
7 minutes ago, Matgen84 said:

Thank you for your great job @Jief_Machak
I tried the following
% git pull
Updating acc2fea81..346661efd
 ./ebuild.sh --xcode8 --buildtarget=DEBUG --define=DEBUG_ON_SERIAL_PORT

Magic copy (your script) /EFI/CLOVERX64.efi,and ../EFI/BOOT/BOOTX64.efi

 

I try to boot Big Sur USB Installer without success: stuck at OC: failed to load configuration

 

  Reveal hidden contents

 

Some compilation messages comes back 

 

  Reveal hidden contents

 

Debug.log attached

 

 

debug.log

The compilation error was resolved by commit f4b3445135826420d270b395b35704159e51030c

 

  • Like 1
Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted
2 minutes ago, Slice said:

The compilation error was resolved by commit f4b3445135826420d270b395b35704159e51030c

 

 

Thanks. I saw that commit who solved the error messages. Now, came back. I think because @Jief_Machak want to know some OC error message: commit 346661e

Link to comment
Share on other sites
iCanaro
iCanaro
Posted
Posted

Cloverx64.efi in Clover, I added an entries in the BIOS that points to
EFI CLOVER Cloverx64.efi
for new Clover test
and the normal entries starts
EFI BOOT BOOTX64.efi

I have folder 11
then the rest of my EFI is the default

need to perform some other particular settings?
in my Z370 does not start any macOS, it does as when the memory manager, ocquirks is not set correctly, does not exit the initial phase

Link to comment
Share on other sites
Slice
Slice
Posted
Posted
1 hour ago, Jief_Machak said:

ok, I've made some progress.

I can now boot High Sierra and Big Sur installer on real hardware.

 

Let's try !

 

CloverX64.efi.zip

Is a pity the same result. Except 3.5 seconds before start Clover :whistle:

0:100  0:000  Clover : Image base = 0x4BBF3000
3:600  3:500  
3:600  0:000  Now is 16.09.2020,  19:01:50 (GMT)
3:600  0:000  Starting Clover revision: 5122 (opencore_integration, commit 346661efd) on American Megatrends EFI
3:601  0:000  Build with: [Args: --gcc53 --target=DEBUG --define=DEBUG_ON_SERIAL_PORT -n 9 | build -D DEBUG_ON_SERIAL_PORT --conf=/JiefLand/5.Devel/Clover/Clover-projects/Clover--CloverHackyColor--opencore_integration/Conf -D USE_LOW_EBDA -a X64 -b DEBUG -t GCC53 -n 9 | OS: 10.14.6]
3:601  0:000

 

  • Like 1
Link to comment
Share on other sites
Jief_Machak
Jief_Machak
Posted
Posted
45 minutes ago, Slice said:

Is a pity the same result. Except 3.5 seconds before start Clover :whistle:


0:100  0:000  Clover : Image base = 0x4BBF3000
3:600  3:500  
3:600  0:000  Now is 16.09.2020,  19:01:50 (GMT)
3:600  0:000  Starting Clover revision: 5122 (opencore_integration, commit 346661efd) on American Megatrends EFI
3:601  0:000  Build with: [Args: --gcc53 --target=DEBUG --define=DEBUG_ON_SERIAL_PORT -n 9 | build -D DEBUG_ON_SERIAL_PORT --conf=/JiefLand/5.Devel/Clover/Clover-projects/Clover--CloverHackyColor--opencore_integration/Conf -D USE_LOW_EBDA -a X64 -b DEBUG -t GCC53 -n 9 | OS: 10.14.6]
3:601  0:000

 

How is that even possible ? You don't have "DBG("SelfDevicePath=%ls @%llX\n", ...)". means tt crashes at the beginning of InitRefitLib() ???

 

Did you try the efi I posted or you recompiled ?

 

1 hour ago, MICKHAEL said:

Hi @Jief_Machak, thanks for your work. I propose, for exclude future questions and boot fails, attache a model EFI.

If you have a working Clover folder, adding Openruntime.efi is supposed to be enough... I'll clean mine and post if you'd like. But you'll have to change it (ACPI, kext, config.plist).

 

1 hour ago, iCanaro said:

it does as when the memory manager, ocquirks is not set correctly, does not exit the initial phase

No idea. What's your debug log?

What I don't understand is that I didn't modify Clover itself, only the startloader function. If you put back the previous CloverX64.efi in the same exact Clover folder, it works ?

 

@Slice and @iCanaro send me your whole CLOVER folder, so I'll have a chance to reproduce.

  • Like 1
Link to comment
Share on other sites
iCanaro
iCanaro
Posted
Posted (edited)
On 9/16/2020 at 10:28 PM, Jief_Machak said:

What I don't understand is that I didn't modify Clover itself, only the startloader function. If you put back the previous CloverX64.efi in the same exact Clover folder, it works ?

my EFI hack Z370 

 

Edited by iCanaro
free up space
Link to comment
Share on other sites
Jief_Machak
Jief_Machak
Posted
Posted
1 hour ago, iCanaro said:

my EFI hack Z370 

EFI_Z370_iCan.zip

The name of the Quirks section in config.plist, for the opencore_integration branch was different than the one for the master branch. That explains why they were just ignored.

We don't have warnings for unrecognised elements in config.plist like OpenCore do. That's why you couldn't see it. I'll do that... one day...

I updated so now your quirks should be considered.

 

Let me know.

CloverX64.efi.zip

Link to comment
Share on other sites
SavageAUS
SavageAUS
Posted
Posted

Ok using the latest release of clover I’ve successfully booted my Catalina install (converted back from OC) using a USB. 
I already have Big Sur beta 6 installed and am happy to offer a hand testing booting and installing Big Sur with Clover. 
what changes / files do I need to begin?

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