Clover General discussion

[apianti]

My base frequency is

0:102  0:000  BrandString = Intel® Core i5-6400 CPU @ 2.70GHz

but I show in About Mac my custom value

	<key>CPU</key>
	<dict>
		<key>FrequencyMHz</key>
		<integer>3300</integer>

His result is higher may be because of RAM.

He also may has overclocked FSB.

 

And there is no twice difference as you say about 20W <-> 65W

 

I understood why yours said 3.3.GHz was just pointing it out so it's clear they are the same. Here's several examples with only 8GB, still a lot higher than yours, 1, 2, 3, and there are plenty more. Also the Windows values are into the high 5000s (a few in the 6000s) and 16/17000 multicore, with the same CPU and amount of ram (either 8GB or 16GB). Although it does not really appear ram amount affects the score since there are plenty of results directly right next to each other with both. As for overclocking, there are way too many scores, some for prebuilt machines, to think that they are all overclocked, and most prebuilt machines can't overclock. And two other things, I seem to recall that geekbench uses the frequency to calculate the score in some way, and it would say the base frequency as something higher than 2.7GHz (since the multiplier would still be 27, but the bus clock would be different than 100MHz). That CPU is locked so it can't be overclocked in any other way. I'm not sure about what you mean twice difference between 20W <-> 65W? If you are saying there is no difference between operating at 20W or 65W, then that's not correct. Your CPU will function faster the more power it uses.... This is the reason for the U, Y, T, P, L, etc, endings, they have a reduced TDP compared to the models that do not, like i5-6500 has 65W TDP, and i5-6500T has 35W. Under the premise you said these otherwise identical CPUs perform similarly, however the only difference is the TDP and the i5-6500T has lower operating frequency and turbo...

 

Hi apianti

you think bad :-)

I have also modified my bios in all way I can (deleting microcode or changing it to old e newest one)

 

I also have used in clover a Haswell EP fakecpuid to understand if it is possible to have some changes..but for now I am loosing

Many people with V3 Xeon had success using this "exploit"

And I was asking here if maybe it is possible to change after Bios post those parameters..

Thank you for your attention

 

It's just a driver that configures the CPU differently. You can just use that driver already, the problem is you need to modify your firmware to remove the code that already setups the CPU for that stuff. If you're going to modify your firmware (or have) then just add that driver as well, or set it up to be loaded by your firmware or clover.

 

EDIT: Oh, realized you were asking if you could do this after post without modifying firmware? No not possible, I imagine what's going on is that the CPU has a MSR that is read/write-once, and once it is written cannot be changed.

[Guest]

In xeon V4 , in my case removing from bios V4 related microcode inhibits system to boot with an error code (A2 on Asus motherboard, it is IDE related but I don't understand well)

 

I think it is a problem with tdp and also like OSX or windows act with it when cpu is loaded @ his max for all cores.

In my case I have a TDP of 150 (max)

OSX during cpu Cinebench test reaches a frequency of 2,6 Ghz for all cores and a tdp of about 124 

Windows reaches 2.8 Ghz and a tdp of 137

test result is 2950 for OSX and 3150 foe MS Windows

 

I am asking if it is possible to "bypass" in safe way some limitation..

then it would be great to be able to use Xeon V3 bug..but for now in my test it is not possible

 

It's just a driver that configures the CPU differently. You can just use that driver already, the problem is you need to modify your firmware to remove the code that already setups the CPU for that stuff. If you're going to modify your firmware (or have) then just add that driver as well, or set it up to be loaded by your firmware or clover.

[Slice]

You said my CPU is underpowered? 20W while it should be 65W? But I see no such differencies in CPU score.

I set SavingMode to 15. It means slow transition from low frequency to high frequency. In the case of gigbench it may leads to lower result because ot many transition up and back as we see in Intel Power Gadget.

At evening I will try to overclock my BIOS.

[Guest]

@apianti

your Edit destroy my little hope to that task..:-(

[Slice]

Having locked MSR 0xE2 we have no chance to control C-state PM?

[apianti]

You said my CPU is underpowered? 20W while it should be 65W? But I see no such differencies in CPU score.

I set SavingMode to 15. It means slow transition from low frequency to high frequency. In the case of gigbench it may leads to lower result because ot many transition up and back as we see in Intel Power Gadget.

At evening I will try to overclock my BIOS.

 

But I just showed you multiple examples of geekbench scores much higher than yours, also it should be running at full load, so the taking more steps to get up there shouldn't matter. I have a feeling it's actually more related to how often and how long it enters turbo. And even in Intel power gadget, there is some telling evidence. In your first one which is 65W TDP, you can see that it doesn't really bounce around at the top power levels, it's almost a flat line, but the frequency bounces. The second one with a 35W TDP, both lines bounce accordingly.

Having locked MSR 0xE2 we have no chance to control C-state PM?

 

No, it means we have no way to change the mode that CPU reports it supports:

15    CFG Lock (R/WO) When set, lock bits 15:0 of this register until next reset.
14:11 Reserved.
10    I/O MWAIT Redirection Enable (R/W) When set, will map IO_read instructions sent to IO register specified by MSR_PMG_IO_CAPTURE_BASE to MWAIT instructions
9:3   Reserved.
2:0   Package C-State Limit (R/W) Specifies the lowest processor-specific C-state code name (consuming the least power). for the package. The default is set as factory-configured package C-state limit.
      The following C-state code name encodings are supported:
        000b: C0/C1 (no package C-sate support)
        001b: C2
        010b: C6 no retention
        011b: C6 retention
        100b: C7
        101b: C7s
        111b: No package C-state limit. Note: This field cannot be used to limit package C-state to C3.

[qqcapcom]

I installed Clover in ESP in macOS,after that I packed it to EFI.zip,then I reinstalled Windows 7 x64,I unpacked EFI.zip to ESP,but nothing happened in AMI UEFI Boot Entry,I have to rename bootmgfw.efi to bootmgfw.old(in Ubuntu Live,because bootmgfw.efi is the only boot efi for Windows 7 x64) so that UEFI OS (Clover) Boot Entry is automatic add to AMI UEFI Boot Entry,after that AMI UEFI can Boot Clover,Clover boot bootmgfw.efi,bootmgfw.efi boot Windows 7 x64,.The question is does install Windows 7 x64 under Windows 7 UEFI retail DVD or install Clover under macOS installer automatic add Windows Boot Manager(bootmgfw.efi) or UEFI OS(CLOVERX64.efi)?If I want to manually add them in EFI environment,how to do that?I know that is a stupid question but I don't get any answer on Internet.Thank you.

[Guest]

@apianti

do you know if it exixts something similar in OSX?

 

https://labs.vmware.com/flings/vmware-cpu-microcode-update-driver

 

In Windows it is possible to update microcode

https://downloadcenter.intel.com/download/26925/Linux-Processor-Microcode-Data-File

[LockDown]

is it bad to install clover legacy on the hfs partition where macOS resides?

[apianti]

I installed Clover in ESP in macOS,after that I packed it to EFI.zip,then I reinstalled Windows 7 x64,I unpacked EFI.zip to ESP,but nothing happened in AMI UEFI Boot Entry,I have to rename bootmgfw.efi to bootmgfw.old(in Ubuntu Live,because bootmgfw.efi is the only boot efi for Windows 7 x64) so that UEFI OS (Clover) Boot Entry is automatic add to AMI UEFI Boot Entry,after that AMI UEFI can Boot Clover,Clover boot bootmgfw.efi,bootmgfw.efi boot Windows 7 x64,.The question is does install Windows 7 x64 under Windows 7 UEFI retail DVD or install Clover under macOS installer automatic add Windows Boot Manager(bootmgfw.efi) or UEFI OS(CLOVERX64.efi)?If I want to manually add them in EFI environment,how to do that?I know that is a stupid question but I don't get any answer on Internet.Thank you.

 

Well, first change your windows back, that's not how to do it. Then boot into ubuntu, to add your boot entry. Get the disk identifier of the disk where the ESP is, usually /dev/sda (but check with disks or gparted). Get the partition number of the ESP, it's usually 1, but if you installed Windows 10 first for some reason windows puts it's recovery before the ESP, so it's 2. Then type this into terminal (remember to change the options for -d and -p):

sudo modprobe efivars
sudo efibootmgr -d /dev/sda -p 1 -c -l "\\EFI\\CLOVER\\CLOVERX64.efi" -L "Clover"

Now restart and you should have another option in your boot menu for clover.

 

@apianti

do you know if it exixts something similar in OSX?

 

https://labs.vmware.com/flings/vmware-cpu-microcode-update-driver

 

In Windows it is possible to update microcode

https://downloadcenter.intel.com/download/26925/Linux-Processor-Microcode-Data-File

 

I am not sure what you mean.... A microcode update is not the same as what you were asking for before. Microcode allows the CPU to be updated if there are errors or manufacturing defects on the chip. Almost every OS has microcode drivers that are used, boot into linux and look at the restricted drivers being used, one will be Intel microcode. Maybe there is microcode that will be able to change what you want, or maybe not. But even if there is it doesn't mean it will work. Give it a try if you want, I don't see the benefit of that much effort for something that isn't really affecting anyone...

 

is it bad to install clover legacy on the hfs partition where macOS resides?

 

It's not bad, you can do it, but that means you are going to lose the ability to do some things. The big one is no disk writing, so no logs or any other dumps. It's a much better idea to install to the ESP that way you don't lose clover if you need to reinstall or an update goes bad or you suddenly get converted to an APFS container without knowing. You should just install to the ESP.... lol

[apianti]

Hey ladies and gentlemen,

 

I am on a new medicine that seems to be working well (at least for now) and I'd like to take this time to try to get some development done on v3. However, here's the dilemma, I need to make money, I can't do both my own business and clover. I want to devote some time like a month or two to nothing but clover v3. If you want this to happen (and you should) please donate some money to me, any amount is helpful. I'm hoping to get enough to take a break from my job entirely while I write this. Anyone who donates will get to give feature requests, do alpha/beta testing (I'm not going to release the source until it's stable, and public betas will be further down the line), my help and eternal gratitude, and maybe a little letter and sticker or something letting you know you rock!

 

Donate to my paypal here:

 

 

 

EDIT: Some donations are coming in, thanks guys! If you donate would you mind sending me a PM so I know that it was you and I can compile a list.

EDIT2: Forgot to mention, this is a business account, so I'm paying the fees, there's no extra charge for a donator.

[Sherlocks]

@cecekpawon

hi, can you check pm? thanks in advance

[zxv]

What's the reasoning for assigning framebuffer Exmoor to 380X in r4318? Lagotto is a perfect match for 380/380X.

[Slice]

What's the reasoning for assigning framebuffer Exmoor to 380X in r4318? Lagotto is a perfect match for 380/380X.

I can make Lagotto but it doesn't exists in ElCapitan.

Anyway there are no perfect matches between DeviceID and Apple's framebuffer. It is a question about connectors and they can be different for different OEM.

[zxv]

I can make Lagotto but it doesn't exists in ElCapitan.

Anyway there are no perfect matches between DeviceID and Apple's framebuffer. It is a question about connectors and they can be different for different OEM.

No problem. Easy enough for me to assign Lagotto manually. Was just curious about the reasoning, and you explained it.

[mitch_de]

Yep, i would also say that Clover should only config most used things (for GPUs) and let special configs made manually by the users.

Also Clover must not include all kind of fixes - they to support over many OS X versions maybe too much and can line into more probs than they fix.

Also too many functions may be a problem for outdated config.plists if some update clover and run into reports " not booting after clover update"... even clover has no bug - they bug is the outdated (wrong) config.plist. Maybe later Clover installer could check config.plist for known missconfigured/ outdated keys, settings at the install process & give at least some warings to look after that.

Or someone which have time, could make an Clover_config_Check tool which checks existing configs for known problems and give advices to fix that?

[maxb2000]

@Slice

 

I have a feature request for Clover and maybe you can implement it:

 

If it's fastboot enabled in the Clover option, then there is no way accessing recovery.

 

So can you make like a 0.5 sec or even smaller delay so it can detected a key like "D" hold down and show the boot selection screen ?

 

Thanks !

[mhaeuser]

@Slice

 

I have a feature request for Clover and maybe you can implement it:

 

If it's fastboot enabled in the Clover option, then there is no way accessing recovery.

 

So can you make like a 0.5 sec or even smaller delay so it can detected a key like "D" hold down and show the boot selection screen ?

 

Thanks !

Just unset fastboot and set Timeout=0.

[WinstonAce]

Something in KextPatch changed (I guess in commit 4305)

now this patch doesn't work (doesn't even appear in debug mode)

it's inside  IO80211Family.kext

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Comment</key>
<string>Wi-Fi Region to 0x64</string>
<key>Disabled</key>
<false/>
<key>Find</key>
<data>D7eH3AQAAA==</data>
<key>Name</key>
<string>AirPortAtheros40</string>
<key>Replace</key>
<data>uGQAAACQkA==</data>
</dict>
</plist>

[smolderas]

 

Something in KextPatch changed (I guess in commit 4305)

now this patch doesn't work (doesn't even appear in debug mode)

it's inside  IO80211Family.kext

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Comment</key>
<string>Wi-Fi Region to 0x64</string>
<key>Disabled</key>
<false/>
<key>Find</key>
<data>D7eH3AQAAA==</data>
<key>Name</key>
<string>AirPortAtheros40</string>
<key>Replace</key>
<data>uGQAAACQkA==</data>
</dict>
</plist>

 

I have the same problem, after r4305 or so is kextpatching broken. It says in the log, that it patched, but it does not...

[zxv]

Clover SSDT patches now appear to be occurring after insertion of custom SSDTs (instead of before). Is this expected behavior?

 

e.g.: 

5:576  0:000  === [ ACPIPatchedAML ] ====================================
…
5:576  0:000  Inserting SSDT-AMD.aml from EFI\CLOVER\ACPI\patched: size=463 ... Success
…
5:576  0:000  === [ PatchAllSSDT ] ======================================
…
5:577  0:000  Patch table: SSDT  SSDTAMDG len=0x1CF
…
5:577  0:000  3. [GFX0 → IGPU]: pattern 47465830, patched at: [ (42) (17) ]

[Slice]

Clover SSDT patches now appear to be occurring after insertion of custom SSDTs (instead of before). Is this expected behavior?

 

e.g.: 

5:576  0:000  === [ ACPIPatchedAML ] ====================================
…
5:576  0:000  Inserting SSDT-AMD.aml from EFI\CLOVER\ACPI\patched: size=463 ... Success
…
5:576  0:000  === [ PatchAllSSDT ] ======================================
…
5:577  0:000  Patch table: SSDT  SSDTAMDG len=0x1CF
…
5:577  0:000  3. [GFX0 → IGPU]: pattern 47465830, patched at: [ (42) (17) ]

It is better, isn't it?

[WinstonAce]

Nope...

It should be choosable.

 

Sent from my ONEPLUS A5000 using Tapatalk

[zxv]

It is better, isn't it?

Probably better, yes.

 

I don't mind the change, but you may want to give a heads up in Clover Change Explanations, as it can introduce quirky behavior for custom SSDT users.

 

For instance I've Clover replace GFX0 → IGPU, followed by PEGP → GFX0… but in my AMD SSDT I already had device defined as GFX0, thus it became IGPU. Easy fix though once I realized what was going on.

 

Nope...

It should be choosable.

Nah… I don't think we want special config parameters for myriad possible use cases. Keep it simple.

[WinstonAce]

But it change the current situation, it shouldn't be the default because it can break things for people which already use on the fly patching with appropriate ssdt. (For example renaming gfx0 to igpu and pegp to gfx and ssdt with appropriate names will lead to ssdt with two igpu devices).

 

Sent from my ONEPLUS A5000 using Tapatalk