Jump to content

Clover General discussion


ErmaC
30,058 posts in this topic

Recommended Posts

1 minute ago, Slice said:

For Mojave yes. But AFAIK AptioMemoryFix is not compatible with BigSur.


@Slice  I want to leave my IvyBridge with Mojave (or update it to Catalina), but I don't want to install Big Sur on it. If I understand correctly what you are telling me: I can leave my current config.plist (old version) and update normally.

That's right. Tell me.

Link to comment
Share on other sites

I can't boot Catalina 10.15.7 with v5124. Should I change anything inside config.plist's Quirk section for this update? I see it's changed in config-sample, but can't boot with that either.

Now it's looks like this:

Spoiler

<key>Quirks</key>
	<dict>
		<key>DisableLinkeditJettison</key>
		<true/>
		<key>PanicNoKextDump</key>
		<true/>
		<key>LapicKernelPanic</key>
		<false/>
		<key>ThirdPartyDrives</key>
		<false/>
		<key>SyncRuntimePermissions</key>
		<true/>
		<key>XhciPortLimit</key>
		<true/>
		<key>EnableWriteUnprotector</key>
		<true/>
		<key>PowerTimeoutKernelPanic</key>
		<true/>
		<key>DummyPowerManagement</key>
		<false/>
		<key>ProvideMaxSlide</key>
		<integer>0</integer>
		<key>ProvideCustomSlide</key>
		<false/>
		<key>EnableSafeModeSlide</key>
		<true/>
		<key>ForceExitBootServices</key>
		<false/>
		<key>ProtectSecureBoot</key>
		<false/>
		<key>DisableVariableWrite</key>
		<false/>
		<key>AppleXcpmCfgLock</key>
		<true/>
		<key>DisableIoMapper</key>
		<true/>
		<key>AvoidRuntimeDefrag</key>
		<true/>
		<key>MmioWhitelist</key>
		<array>
			<dict>
				<key>Address</key>
				<integer>4275159040</integer>
				<key>Comment</key>
				<string>Haswell: SB_RCBA is a 0x4 page memory region, containing SPI_BASE at 0x3800 (SPI_BASE_ADDRESS)</string>
				<key>Enabled</key>
				<false/>
			</dict>
			<dict>
				<key>Address</key>
				<integer>4278190080</integer>
				<key>Comment</key>
				<string>Generic: PCI root is a 0x1000 page memory region used by some firmwares</string>
				<key>Enabled</key>
				<false/>
			</dict>
		</array>
		<key>DisableRtcChecksum</key>
		<false/>
		<key>ProtectMemoryRegions</key>
		<false/>
		<key>ProvideConsoleGopEnable</key>
		<true/>
		<key>SetupVirtualMap</key>
		<true/>
		<key>ExternalDiskIcons</key>
		<false/>
		<key>DevirtualiseMmio</key>
		<false/>
		<key>ProtectUefiServices</key>
		<false/>
		<key>AppleXcpmForceBoost</key>
		<false/>
		<key>CustomSMBIOSGuid</key>
		<false/>
		<key>IncreasePciBarSize</key>
		<false/>
		<key>DisableSingleUser</key>
		<false/>
		<key>DiscardHibernateMap</key>
		<false/>
		<key>FuzzyMatch</key>
		<true/>
		<key>AppleXcpmExtraMsrs</key>
		<false/>
		<key>RebuildAppleMemoryMap</key>
		<false/>
		<key>AppleCpuPmCfgLock</key>
		<false/>
		<key>KernelCache</key>
		<string>Auto</string>
		<key>SignalAppleOS</key>
		<false/>
	</dict>

 

It's from v5123 config-sample. 

drivers: 

411823260_Screenshot2020-10-12at18_08_39.png.006a2e2584ffbf51b7e726c0a6a3d92b.png

On v5124 it's stopping at [EB|#LOG:EXITBS:START] 2020-10-12T15:49:15

After reverting the CLOVERX64.efi back to v5123 I could boot back to Desktop fine. I did NVRAM reset but same.

debug.log

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

3 minutes ago, Jief_Machak said:

You can leave it, but it won't be used. It's filtered out by Clover because if it's loaded, it crash the embedded OC.

So you can't escape the new section.


It's a bad news for my old IvyBridge system. :cry: If I want to escape the new section: I keep r5122 :hysterical:

If AptioMemoryFix is loaded, it crashes the built-in OC. It also means that the others are unusable. They are all in the package.
So anyone who doesn't want to upgrade to Big Sur, will be forced to use the Quirks section and Openruntime.efi. I did not understand this. I thought the built-in OC only intervened for Big Sur.

  • Like 1
Link to comment
Share on other sites

1 hour ago, kushwavez said:

On v5124 it's stopping at [EB|#LOG:EXITBS:START] 2020-10-12T15:49:15

After reverting the CLOVERX64.efi back to v5123 I could boot back to Desktop fine. I did NVRAM reset but same.

 

 

Same exact issue here... trying to boot Catalina 10.5.7 with r5124... 

Link to comment
Share on other sites

in my Z370 all right, start all OS

 

on the Z170 instead with this Clover 5124 I just couldn't start Catalina
I updated the config and tried several settings, but I didn't get anything

With Clover 5123-8e0f4ad24, however, it gets started properly

attach debug log @Jief_Machak 

 

Z170_5124_config5124_NOK_debug.log

Z170_5124_config5123_NOK_debug.log

Z170_5123-8e0f4ad24_config5123_OK_debug.log

Z170_5123-8e0f4ad24_config5124_OK_debug.log

Edited by iCanaro
  • Thanks 1
Link to comment
Share on other sites

Unfortunately 5124 will not load the DSDT that I have built and fixed. Go load bios instead Making it impossible to do all the work that the heart desires

edit...But agree that it boots faster than it used to be
The cause is most likely because the sound is not loaded. Graphics are not loaded like I did.

Edited by naiclub
Link to comment
Share on other sites

1 hour ago, biricotico said:

@Slice 

Here is a debug.log

debug.log.zip

Thank You!

All is fine in the log.

23 minutes ago, naiclub said:

Unfortunately 5124 will not load the DSDT that I have built and fixed. Go load bios instead Making it impossible to do all the work that the heart desires

edit...But agree that it boots faster than it used to be
The cause is most likely because the sound is not loaded. Graphics are not loaded like I did.

Do you have such a line in your log?

10:545  0:007  DSDT found in Clover volume OEM folder: \EFI\CLOVER\ACPI\patched\\DSDT.aml

 

  • Like 2
Link to comment
Share on other sites

4 minutes ago, Slice said:

All is fine in the log.

Do you have such a line in your log?


10:545  0:007  DSDT found in Clover volume OEM folder: \EFI\CLOVER\ACPI\patched\\DSDT.aml

26:988  0:021  DSDT found in Clover volume OEM folder: \EFI\CLOVER\ACPI\patched\\DSDT.aml
27:035  0:047  DSDT found in Clover volume: \EFI\CLOVER\ACPI\patched\\DSDT.aml

bdmesg.log

This or not?

 

Link to comment
Share on other sites

4 minutes ago, naiclub said:

26:988  0:021  DSDT found in Clover volume OEM folder: \EFI\CLOVER\ACPI\patched\\DSDT.aml
27:035  0:047  DSDT found in Clover volume: \EFI\CLOVER\ACPI\patched\\DSDT.aml

So DSDT is loaded? Why you tell opposite?

  • Thanks 1
  • Haha 1
Link to comment
Share on other sites

15 minutes ago, Slice said:

All OK?

no ok  Must sue with pictures

Spoiler

433779133_ScreenShot2563-10-13at02_32_55.thumb.png.3cca62010cc197e503109cff53d7ec46.png

Which it should be like this An example from an old photo

Spoiler

1287691590_2563-10-0110_29_02.thumb.png.5645647b00692efcee3bc59f9ab0eb0b.png

 

Edited by naiclub
Link to comment
Share on other sites

2 hours ago, Slice said:

Catalina is not BigSur.

Spoiler

203989380_2563-10-1303_42_08.thumb.png.eaaa07d2483eb9c4f55b9ea0dd3e469a.png

The result is the same. 13 .14 .15 11.

edit..

Spoiler

500532079_2563-10-1304_12_55.png.f5651bce789b6b9e668531658e930d91.png

Let's move to oem, the result is the same.

This overlap was left with two options.

Noteworthy Is there an exception where I have a black circle?


Let's update again I got your help mifjpn
That gave the code to create a clover until success

From .. ~% cd
  ~% rm -rf CloverBootloader
% git clone -b master --recurse-submodules https://github.com/CloverHackyColor/CloverBootloader.git

.....................................

~ % cd CloverBootloader/

% git status

% ./buildme

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

buildme, Clover r5124 (SHA: a2ffdf864)
TOOLCHAIN: GCC53 (override example: './buildme XCODE8')

 1) build Clover
 2) build Clover with HFSPlus
 3) make pkg
 4) make app
 5) make app (with Clover)
 6) make iso
 7) build all
 8) test build (no autogen, no boot files)
 9) status
10) update Clover
11) show diff
12) open CloverV2/EFI/CLOVER directory
13) update Clover (reset changes)
14) clean BaseTools
15) quit
Please enter your choice:(7)..

.............................
buildme, Clover r5124 (SHA: a2ffdf864)
TOOLCHAIN: GCC53 (override example: './buildme XCODE8')

 1) build Clover
 2) build Clover with HFSPlus
 3) make pkg
 4) make app
 5) make app (with Clover)
 6) make iso
 7) build all
 8) test build (no autogen, no boot files)
 9) status
10) update Clover
11) show diff
12) open CloverV2/EFI/CLOVER directory
13) update Clover (reset changes)
14) clean BaseTools
15) quit
Please enter your choice: (15)
~ % cd      
~ % cd CloverBootloader
% git pull && git fetch
% ./buildme

buildme, Clover r5124 (SHA: a2ffdf864)
TOOLCHAIN: GCC53 (override example: './buildme XCODE8')

 1) build Clover
 2) build Clover with HFSPlus
 3) make pkg
 4) make app
 5) make app (with Clover)
 6) make iso
 7) build all
 8) test build (no autogen, no boot files)
 9) status
10) update Clover
11) show diff
12) open CloverV2/EFI/CLOVER directory
13) update Clover (reset changes)
14) clean BaseTools
15) quit
Please enter your choice: (7)

.................................................

buildme, Clover r5124 (SHA: a2ffdf864)
TOOLCHAIN: GCC53 (override example: './buildme XCODE8')

 1) build Clover
 2) build Clover with HFSPlus
 3) make pkg
 4) make app
 5) make app (with Clover)
 6) make iso
 7) build all
 8) test build (no autogen, no boot files)
 9) status
10) update Clover
11) show diff
12) open CloverV2/EFI/CLOVER directory
13) update Clover (reset changes)
14) clean BaseTools
15) quit
Please enter your choice: (15)

Again..

This time I knew something was missing (OcQuirks.efi), but I tried installing it over the old one and it still works fine. I didn't feel any difference.

But the solved DSDT problem does not load at all.

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

On my Z68 hack with Clover 5124 I managed to start windows, linux mageia, high sierra, mojave and catalina

only a little strange thing, the debug log was generated the first time I started high sierra, and then with all the other macOS, a debug log of zero Kb empty was generated
In case it could serve dev, I attach the generated log debugging and the preboot
starting with quirks and OpenRuntime

1678599298_Schermata2020-10-13alle00_08_15.png.3af034f3b18d698b3e01fcc0e561a1e3.png

 

 

Z68-5124-preboot.log

Z68_5124-d2bec9ba0_OK_high-sierra-debug.log

  • Like 2
  • Thanks 1
  • Confused 1
Link to comment
Share on other sites

×
×
  • Create New...