Clover General discussion

[Jief_Machak]

My point is : is that quirks does the same when enabled in Clover and when enabled in OC. Same can mean crash, it’s ok.

Of course with the same configuration in OC and Clover.

[PG7]

11 minutes ago, Jief_Machak said:

My point is : is that quirks does the same when enabled in Clover and when enabled in OC. Same can mean crash, it’s ok.

Of course with the same configuration in OC and Clover.

 

in my case yes to a great similarity

Edited November 29, 2020 by PG7

[iCanaro]

28 minutes ago, Jief_Machak said:

My point is : is that quirks does the same when enabled in Clover and when enabled in OC. Same can mean crash, it’s ok.

Of course with the same configuration in OC and Clover.

 

OK I understood the purpose, regardless of the result, to see if the behavior between OC and Clover is identical or different.
On Z370 hack with DevirtualiseMmio enabled or disabled the behavior between OC and Clover is identical; no problem, the hack apparently works the same way in all situations

[iCanaro]

I wanted to see what was happening on the X570 with new BIOS and DevirtualiseMmio enabled and with Clover nothing changes, apparently identical operation, no anomaly detected.
On OC 062 instead a nice mess, you have blackscreen, which never happened, then if you add boot-arg agdpmod=pikera you get to the desktop, but you don't have any USB working.. in short, enabling DevirtualiseMmio creates nice problems even worse than in the past.

[Jief_Machak]

7 hours ago, iCanaro said:

I wanted to see what was happening on the X570 with new BIOS and DevirtualiseMmio enabled and with Clover nothing changes, apparently identical operation, no anomaly detected.
On OC 062 instead a nice mess, you have blackscreen, which never happened, then if you add boot-arg agdpmod=pikera you get to the desktop, but you don't have any USB working.. in short, enabling DevirtualiseMmio creates nice problems even worse than in the past.

You are saying there is a behaviour difference ? Works with Clover and not with OC ?

[Matgen84]

10 hours ago, Jief_Machak said:

Hi everyone.

I'd like help to identify a potential Clover bug.

If you have a bootable OC configuration (no need that everything is configured, just bootable), check that you can boot with quirks DevirtualiseMmio enabled, and nothing in MmioWhitelist. It's supposed to be ok from IvyBridge.

Then check the same quirks in Clover config.plist. For me, when this is enabled in Clover, there is a very early crash. And you ?

 

Hi @Jief_Machak I just read several post about DevirtualiseMmio and MmioWhitelist with IvyBridge.

I follow convert guide to build Clover config.plist: the settings are the same for Clover and functional OC for my Asus Z77 (i7 3770K)

 

	<key>MmioWhitelist</key>
        <array/>
        <key>Quirks</key>
        <dict>
            <key>AvoidRuntimeDefrag</key>
            <true/>
            <key>DevirtualiseMmio</key>
            <false/>

There is no crash if disable. Only crash when  DevirtualiseMmio is enable like @PG7

[Slice]

10 hours ago, Jief_Machak said:

Hi everyone.

I'd like help to identify a potential Clover bug.

If you have a bootable OC configuration (no need that everything is configured, just bootable), check that you can boot with quirks DevirtualiseMmio enabled, and nothing in MmioWhitelist. It's supposed to be ok from IvyBridge.

Then check the same quirks in Clover config.plist. For me, when this is enabled in Clover, there is a very early crash. And you ?

 

The quirk is sometimes needed for Z390. Should be Off for IvyBridge.

[Jief_Machak]

@Matgen84 @Slice : The point is NOT to know if it should be enabled or not. The point is : is the behavior the same in Clover and OC ?

For me it's not. So I'd say there is a bug in Clover.

@Matgen84 @iCanaro Do you have the "same" behavior if you enable DevirtualiseMmio ?

[iCanaro]

on the X570 I don't have the same behavior

 

on the Z370 I already knew that if I enabled or did not enable DevirtualiseMmio it made no difference, so it is not possible to detect differences in behavior between Clover and OC

[iCanaro]

35 minutes ago, Jief_Machak said:

Do you have the "same" behavior if you enable DevirtualiseMmio ?

 

specifying that the tests are performed with OC062 and Clover 5127, in the Z68 I have the same behavior, enabling DevirtualiseMmio Kernel Panic to boot with both OC and Clover

[Matgen84]

48 minutes ago, Jief_Machak said:

Do you have the "same" behavior if you enable DevirtualiseMmio ?

 

The tests are performed with OC 0.6.4 Beta and Clover r5127, in my Z77 Ivybridge. Like @iCanaro I have the same behavior, DevirtualiseMmio enable --->> Kernel panic with both bootloader.

[naiclub]

สปอยเลอร์

This version, booting with clover5127, does not work, I just tried to access it and it appears that it cannot boot any more.

I switched back to 5126 recently compiled last time.

[iCanaro]

with hacks z97 and devirtualisemmio enabled oc 062 and clover 5127 have the same behavior kernel panic at boot

[Jief_Machak]

2 hours ago, iCanaro said:

on the X570 I don't have the same behavior

So that's 2 cases where behavior is different, yours and mine.

I guess I'll open a bug on github, but since nobody is annoyed with that (because disabled is OK), we'll keep the resolution for later.

 

On interesting thing. If a put this :

		<key>MmioWhitelist</key>
		<array>
			<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>
				<true/>
			</dict>
		</array>

it boots fine with devirtualisemmio enabled, Clover as well as OC.

 

I'm confused with this bug...

 

Edited November 30, 2020 by Jief_Machak

[JorgeMax]

About the chipset:

Big Sur:

Spoiler

 

Catalina:

Spoiler

 

In the normal Catalina the chipset is recognized, but in Big Sur it shows "Generic"

[iCanaro]

19 minutes ago, Jief_Machak said:

it boots fine with devirtualisemmio enabled, Clover as well as OC.

 

I'm confused with this bug...

 

now I verify, address 4278190080 is among the 12 of my list on the X570 that I got with DEBUG OC and converted values for the MMIO white list

[Guest]

17 minutes ago, Jief_Machak said:

So that's 2 cases where behavior is different, yours and mine.

I guess I'll open a bug on github, but since nobody is annoyed with that (because disabled is OK), we'll keep the resolution for later.

 

On interesting thing. If a put this :

		<key>MmioWhitelist</key>
		<array>
			<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>
				<true/>
			</dict>
		</array>

it boots fine with devirtualisemmio enabled, Clover as well as OC.

 

I'm confused with this bug...

 

 

Have you verified via your debug log if you have that location in your bios...

It seems many of you are testing this stuff without understanding well how they work and if they are useful or not for your rig to use it

But, said this..first thing is to verify if that MMIO location is present or not in your firmware

 

 

[Jief_Machak]

2 minutes ago, fabiosun said:

first thing is to verify if that MMIO location is present or not in your firmware

I'm looking at behavior difference between OC and Clover. Difference that should exist.

I'm NOT looking at mmio addresses accuracy. Even if this address does NOT exist, if it generates a behavior difference, it should be looked at.

[Slice]

13 minutes ago, JorgeMax said:

About the chipset:

Big Sur:

  Hide contents

 

Spoiler

 

 

Catalina:

  Hide contents

 

Spoiler

 

 

In the normal Catalina the chipset is recognized, but in Big Sur it shows "Generic"

Same for me. I don't know why and propose it is BigSur beta bug.

[Guest]

6 minutes ago, Jief_Machak said:

I'm looking at behavior difference between OC and Clover. Difference that should exist.

I'm NOT looking at mmio addresses accuracy. Even if this address does NOT exist, if it generates a behavior difference, it should be looked at.

if it does not exist and if your boot loader works well as OC does..that MMIO in MMIO debug list must be to skip to 0

otherwise..you are devirtualizing some areas randomly...as many of you are doing if I read well here

 

Accuracy is a word  I would not associate at this kind of testing... 

Edited November 30, 2020 by Guest
really instead read

[iCanaro]

37 minutes ago, Jief_Machak said:

So that's 2 cases where behavior is different, yours and mine.

I guess I'll open a bug on github, but since nobody is annoyed with that (because disabled is OK), we'll keep the resolution for later.

 

On interesting thing. If a put this :

		<key>MmioWhitelist</key>
		<array>
			<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>
				<true/>
			</dict>
		</array>

it boots fine with devirtualisemmio enabled, Clover as well as OC.

 

I'm confused with this bug...

 

 

with this MMIO enabled and all others disabled, on the X570 I get:

Clover --> Kernel Panic
OC --> black screen

[iCanaro]

@Jief_Machak I ran new test on X570 with DevirtualiseMmio enabled but without any entry in the white list, that is, all active MMIO, Clover and OC have the same behavior, I arrive at desktop and there does not seem to be any anomalies

[iCanaro]

I recommend to those who want to play with MMIO, first understand which ones it has through OC debug, so as to have the complete list, then convert the HEX value to decimal and add the entries in the MmioWhiteList.
Then with a lot of patience and time to check which ones you need to have active and which do not. Remember that if you change the BIOS the list of MMIO may change

[Matgen84]

17 minutes ago, iCanaro said:

@Jief_Machak I ran new test on X570 with DevirtualiseMmio enabled but without any entry in the white list, that is, all active MMIO, Clover and OC have the same behavior, I arrive at desktop and there does not seem to be any anomalies

@Jief_Machak I do the same test on my Z390: DevirtualiseMmio enabled, without any entry in the MMIO white list. Clover and OC works fine, I reach the Big Sur Desktop successfully. 

Thanks for your effort.

[naiclub]

26 minutes ago, Jief_Machak said:

 

Spoiler

Clover this floor And collect commits
(Powered by Clover revision: 5126 (master, commit d042fa25a))
Definitely the best for me Because it can boot from 10.8-11
Which other versions do not work at all It works like 10.8- 10.10- 10.11- 10.12- 10.13- 10.14- 10.15 11 not 10.9.
I wonder if the reason that works all of them is because of you.
Thank you very much

Spoiler

Now I have another story I want to update everyone to know with this.

And there is no need to add kext .. For SATA as well
It works with all versions