Jump to content

Clover General discussion


ErmaC
30,171 posts in this topic

Recommended Posts

6 hours ago, Jief_Machak said:

So DEBUG compile fine, although you'l have at the end 


Created /JiefLand/5.Devel/Clover/Clover-projects/Clover--CloverHackyColor--master.opencore/Build/Clover/DEBUG_GCC53/FV/Efildr64
warning: boot file bigger than low-ebda permits, switching to --std-ebda
GenPage...
/JiefLand/5.Devel/Clover/Clover-projects/Clover--CloverHackyColor--master.opencore/Build/Clover/DEBUG_GCC53/FV/Efildr20Pure: ERROR 16386: Invalid parameter option
  Input file size (0x84532) exceeds the Page Table Offset (0x70000)

 

CloverX64.efi is still generated in Build/Clover/DEBUG_XCODE8/X64 (you've just got caught no reading the posts :hysterical:)

RELEASE compiles too.

  • Thanks 1
Link to comment
Share on other sites

13 hours ago, Jief_Machak said:

There is a bug in OpenCore, sometime it goes back to the menu, sometime it crash at boot. So this version will do the same, of course.

We don't mind usage of the code under the license of course, but please consider developer culture and submit a short report or if you like of course patches for bugs found.

  • Like 1
Link to comment
Share on other sites

1 minute ago, Download-Fritz said:

We don't mind usage of the code under the license of course, but please consider developer culture and submit a short report or if you like of course patches for bugs found.

If I had found a bug, for sure I would have submitted it. But I didn't look why, on VMWare, it sometimes crash or reboot. It's one out of approx. 3. So I just reboot until it works.

6 hours ago, Matgen84 said:

Do you need some tests for OpenCore_integration branch ? I can on my Z390 config, if you want.

Yes sure.

In that branch, every 11 version will boot the new way. So I don't know if an installed version of 11 will boot. Also, I didn't handle Quirks (yet). Do you have some in your config ?

So yes, if you have a bit a space, that'll be nice to confirm that the installer can boot and that the installation goes well. 

1 minute ago, Matgen84 said:

Right ! @Jief_Machak  you are a very funny guy :hammer:

Is there some irony in that ?

  • Like 2
Link to comment
Share on other sites

20 minutes ago, Jief_Machak said:

Is there some irony in that ?

 

Just a joke @Jief_Machak I try your CLOVERX64. Maybe I make a mistake: but stuck at GUI, no keyboard and mouse after click on Big Sur USB Installer, and no BigSur HD detected :cry:

Edited by Matgen84
Link to comment
Share on other sites

Thanks @Jief_Machak

Second test:

 

Like @mifjpn I installed Big Sur Beta 6 with OpenCore, but on a HDD. There is no entry for it. Only BigSur USB installer and my Windows drive.

When I try to boot BigSur USB installer: some Busy time out error 'AppleACICPU, ARTC.

 

Edit: I just see your post and create now a 11 folder for third test

Edited by Matgen84
Link to comment
Share on other sites

Third test:

 

Kexts in 11 folder

 

I installed Big Sur Beta 6 with OpenCore, but on a HDD. There is no entry for it. Only BigSur USB installer and my Windows drive.

When I try to boot BigSur USB installer: some Busy time out [0] (240s) error 'AppleACPICPU', 'ARTC.' and Purple Line on the screen. :cry: 
Finally after this longest boot that I never see before,  boot succeed :)

 

 

preboot.log

debug.log

Edited by Matgen84
  • Like 1
Link to comment
Share on other sites

Thanks @Jief_Machak

Fourth test:

 

 I installed Big Sur Beta 6 with OpenCore, but on a HDD. There is no entry for it. Only BigSur USB installer and my Windows drive. So this time, I remove Hide Preboot from config.plist

There are entries for "Boot Mac OS X from BigSur - Data via Preboot" and "Boot Mac OS X Install BigSur - Data via Preboot". (The HDD containing my BigSur is named BigSur)

 

When I select "Boot Mac OS X Install BigSur", there is some Busy time out [0] (240s) error 'AppleACPICPU', 'ARTC.' and Purple Line on the screen. I can't boot Big Sur Install.
When I select "Boot Mac OS X from BigSur-Data via Preboot", a purple line appears on the screen, some Busy time out [0] (60s) error 'AppleACPICPU', 'ARTC.' 3 times and Black screen instead of Desktop

 

Link to comment
Share on other sites

Did you remove AptioMemoryFix from drivers ?

Did you put at least Lilu.kext and virtualsmc.kext in a folder named 11 under kexts.

 

I've looked in the log and it seems the wrong efi. You must have "=== [ StartLoader11 ] =============================" instead of "=== [ StartLoader ] =============================".

 

Here the efi.

 

CloverX64.efi.zip

Link to comment
Share on other sites

I found a problem in Oc init. Try the latest efi I've sent.

I was able to launch the installer that is seen as a CD-ROM in my virtual machine.

I can start the boot form a partition like "xxxx - Data via Preboot" (which is a properly installed big sur) but vm stops at "still waiting for root device". I'm curious if it does the same on real hardware.

 

  • Thanks 1
Link to comment
Share on other sites

15 minutes ago, Jief_Machak said:

I found a problem in Oc init. Try the latest efi I've sent.

I was able to launch the installer that is seen as a CD-ROM in my virtual machine.

I can start the boot form a partition like "xxxx - Data via Preboot" (which is a properly installed big sur) but vm stops at "still waiting for root device". I'm curious if it does the same on real hardware.

 

 

I try latest efi file  you've sent: same issue Busy Time out  error AppleACPICPU, ARTC + Black screen :cry:

 

@Jief_Machak Do you see @mifjpn post: I try master-bulid-f4e10b1.It's same blankscreen state occured.

Edited by Matgen84
Link to comment
Share on other sites

Do you have a working OC installation ? If yes, send it to me. All the "features" of OC are not "bridged" yet. For example, there is kernel patching, etc.

Send me your OC config.plist, and I'll plug your needed features to OC.

 

 

Edited by Jief_Machak
Link to comment
Share on other sites

2 minutes ago, Jief_Machak said:

Do you have a working OC installation ? If yes, send it to me. All the "features" of OC are not "bridged" yet. For example, there is kernel patching, etc.

Send me your OC config.plist, and I'll plug your needed features to OC.

 

 

 

I send to you my latest work OC EFI folder for my Z390  (without credentials information in config.plist)

 

 

EFI_OC_061 06-09-2020_db87b32.zip

Link to comment
Share on other sites

55 minutes ago, Matgen84 said:

credentials

?? I don't know OC, but what do you mean by credentials. Could you send me a config.plist with a clear view of what you voided. Like replace by *************************** or something, so I can regenerate some for me ?

Or at least tell with node you removed ?

Link to comment
Share on other sites

3 minutes ago, Jief_Machak said:

?? I don't know OC, but what do you mean by credentials. Could you send me a config.plist with a clear view of what you voided. Like replace by *************************** or something, so I can regenerate some for me ?

Or at least tell with node you removed ?

 

By credentials, I mean MLB, Serial, SMUUID for example. I remove in PlatformInfo/Generic section in config.plist 

Done with ******** attached

 

config.plist

Link to comment
Share on other sites

2 minutes ago, Jief_Machak said:

And your clover config mimic what's in OC config.plist, in term of ACPI patch, kext, Device properties etc. ?

 

The Clover config.plist is different because I use DSDT patched by MaLdOn. For OC, have a look to Dortania Guide: there are explanations for the config.plist for processors from IvyBridge to comet lake

Clover config.plist attached


 

config.plist

Link to comment
Share on other sites

3 minutes ago, Matgen84 said:

 

The Clover config.plist is different because I use DSDT patched by MaLdOn. For OC, have a look to Dortania Guide: there are explanations for the config.plist for processors from IvyBridge to comet lake

Clover config.plist attached


 

config.plist

So maybe your config in Clover can't boot big sur because of some missing patch or something ?

Wouldn't it be interesting that you try a Clover config.plist that has the same ACPI/Kernel patch configuration ? Just so we're sure, if you can't boot, that's not the problem. I'm saying it'll boot with the EFI I made. There is still missing things. Just try to isolate the problems first, so if you report it doesn't boot, we are not looking at the wrong place.

Link to comment
Share on other sites

7 minutes ago, Jief_Machak said:

So maybe your config in Clover can't boot big sur because of some missing patch or something ?

Wouldn't it be interesting that you try a Clover config.plist that has the same ACPI/Kernel patch configuration ? Just so we're sure, if you can't boot, that's not the problem. I'm saying it'll boot with the EFI I made. There is still missing things. Just try to isolate the problems first, so if you report it doesn't boot, we are not looking at the wrong place.

 

My Clover config.plist works fine with Catalina. But why not try another to isolate the problems with Big Sur. It's a good idea. I'm happy to try the EFI you created. It's nice.

Link to comment
Share on other sites

×
×
  • Create New...