Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
29,869 posts in this topic

Recommended Posts

Jief_Machak
Jief_Machak
Posted
Posted
7 minutes ago, Slice said:

SMBIOS data and UUID was changed that is not good because I switched off iCloud.

Older Clover (my compilation without your news) has such screen

Снимок экрана 2021-04-24 в 18.10.42.png

You mean that your UUID is not the same as before ?

Very possible to have a bug there, Smbios wasn't an easy part.

Ok, I'll check.

Of yes, and I see the 2.11f16 instead 2.34f3.

Where does this info come from (sorry can't read) ? Which key in config.plist/SMBIOS ?

Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted (edited)
2 hours ago, Jief_Machak said:

No, he's using his plist where all boolean are like <true /> or <false /> (with a space). New parser doesn't support that... Although it's possible...

 

@Matgen84 Fixed a problem with patches. Better ? CloverX64-2021-04-24-17-52-19-afa09cc-dirty-jief.zip


@Jief_Machak I can boot fine (I hope without F11) but can't wake up :cry: :bye::wacko:

 I've got a new problem: boolean value requires !

 

Sample.plist

<key>InjectKexts</key>

 <string>Yes</string>

My config.plist

<key>InjectKexts</key>

 <string>Yes</string>

  

iMac-de-Mathieu:~ mathieu$ /Users/mathieu/Downloads/Outils_Bootloader/Outils\ Clover/Outils\ New\ Clover\ +\ BootloaderChooser/CloverConfigPlistValidator0.8 '/Users/mathieu/Desktop/config.plist' 
Cannot stat file 'config-nowarning-noerror.plist'

 

Spoiler

1.thumb.jpg.7f921dddc404e898306422aeebe4d201.jpg

 

2021-4-24_14-59_CloverX64-2021-04-24-17-52-19-afa09cc-dirty-jief.efi.log

Edited by Matgen84
Link to comment
Share on other sites
Slice
Slice
Posted
Posted
54 minutes ago, Jief_Machak said:

No, he's using his plist where all boolean are like <true /> or <false /> (with a space). New parser doesn't support that... Although it's possible...

 

Spaces should be allowed because it used in our svg themes which is also XML format. 

<!-- Roboto Condensed is a trademark of Google. -->
<!-- Copyright: Copyright 2020 Adobe System Incorporated. All rights reserved. -->
<font-face font-family="RobotoCondensed-Regular" units-per-em="2048" underline-position="-150" underline-thickness="100" bbox="-200 -340 1848 1708"  />
<missing-glyph horiz-adv-x="433"/>

Hope later we will parse svg with the same procedures.

Link to comment
Share on other sites
Slice
Slice
Posted
Posted
37 minutes ago, Jief_Machak said:

You mean that your UUID is not the same as before ?

Very possible to have a bug there, Smbios wasn't an easy part.

Ok, I'll check.

Of yes, and I see the 2.11f16 instead 2.34f3.

Where does this info come from (sorry can't read) ? Which key in config.plist/SMBIOS ?

Yes, UUID changed. It's a pity I didn't save the picture.

2.11f16  comes from model iMac13,2 

  { "iMac13,2"_XS8, "IM131.88Z.F000.B00.2004121616"_XS8, "291.0.0.0.0"_XS8, "Mac-FC02E91DDD3FA6A4"_XS8, // Intel Core i5-3470 @ 3.20 GHz
    "iMac"_XS8, "1.0"_XS8, "C02JB041DNCW"_XS8, "iMac-Aluminum"_XS8,
    0x02, 0x11, 0x0f, 0, 0, 0x16, "d8"_XS8, "d8"_XS8, 0x79006 },

while my model is iMac17,1 

  { "iMac17,1"_XS8, "IM171.88Z.F000.B00.2004240904"_XS8, "178.0.0.0.0"_XS8, "Mac-B809C3757DA9BB8D"_XS8, // Intel Core i7-6700K @ 4.00 GHz
    "iMac17,1"_XS8, "1.0"_XS8, "C02QFHACGG7L"_XS8, "iMac-Aluminum"_XS8, // i5: Mac-65CE76090165799A/Mac-DB15BD556843C820, i7: Mac-B809C3757DA9BB8D
    0x02, 0x34, 0x0f, 0, 0, 0x03, "j95j95am"_XS8, "j95"_XS8, 0xf0c008 }, //Note: why? i5: 2.33f12 but for i7: 2.34f3

UINT8 smcRevision[6];

Link to comment
Share on other sites
Slice
Slice
Posted
Posted
6 hours ago, STLVNUB said:

Some ideas that Opencore devs thought rubbish

May be better in Clover anyway

 

 

 

With Clover-5133 I can switch between Mojave, Big Sur and Windows 10 without iCloud problems.

  • Like 3
Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted

@Slice Idem here.

 

My model Imac19,1 

 //iMac19,1 / iMac (Retina 5K, 27-inch, 2019)
  { "iMac19,1"_XS8, "IM191.88Z.F000.B00.2004232100"_XS8, "1037.120.79.0.0"_XS8, "Mac-AA95B1DDAB278B95"_XS8, // Intel Core i9-9900K @ 3.60 GHz
    "iMac"_XS8, "1.0"_XS8, "C02Y9HACJV3P"_XS8, "iMac-Aluminum"_XS8,
    0x02, 0x46, 0x0f, 0, 0, 0x12, "j138_9"_XS8, "j138"_XS8, 0xf0d009 },

 

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

With Clover-5133 I can switch between Mojave, Big Sur and Windows 10 without iCloud problems.

Maybe I switch to Clover, Thanks Slice 

Link to comment
Share on other sites
deeveedee
deeveedee
Posted
Posted (edited)
On 1/28/2020 at 12:28 AM, Slice said:

I made the follow 





        Device (PRRE)
        {
... 
//                    Memory32Fixed (ReadWrite,
//                        0xFE000000,         // Address Base
//                        0x00020000,         // Address Length
//                        )
...
                })

And then add PMC device as in example.

 

Slice - I didn't realize you had already addressed this potential conflict and I had posted this.  The solution that is currently working for me on my rig is to leave PRRE unpatched and to implement a new PMCR that does not include a Memory32Fixed resource setting.  To be honest, I'm not noticing any difference in behavior after implementing the change.

 

EDIT: I have concluded that there is no need to patch PRRE and that the PMCR patch is ok as-is.  See here.  My opinion is that the Memory32Fixed memory reservation in PRRE (and in PMCR) are simply marking reserved memory for OperationRegions PWMR (on a PC) and PMST (on a real Mac).  The overlapping memory reservations in PRRE and PMCR don't hurt anything.  I suspect that others, like me, will find that their systems behave just fine when including the PMCR patch and leaving PRRE unpatched.

Edited by tonyx86
Concluded that there is no need to patch PRRE
Link to comment
Share on other sites
Slice
Slice
Posted
Posted
6 minutes ago, Jief_Machak said:

New version !

CloverX64-2021-04-25-19-03-21-afa09cc-dirty-jief.zip 820.23 kB · 0 downloads

 

@Slice smcRevision is fixed, and some others.

 

@everyone, SMBIOS was a particularly pain ! So if you'd like to help, use dmidecode before and after booting this version and tell me if there is a difference.

Thanks.

Qemu crashed

Снимок экрана 2021-04-25 в 20.28.30.png

 

config.plist.zip

Link to comment
Share on other sites
Jief_Machak
Jief_Machak
Posted
Posted
2 hours ago, Slice said:

Qemu crashed

Снимок экрана 2021-04-25 в 20.28.30.png

 

config.plist.zip 3.66 kB · 1 download

It's not a crash, it's a bug revealator :lol:

Arg, we all knew that : don't call getModel() if ProductName is not defined. Stupid me !:D Fixed.

CloverX64-2021-04-25-19-03-21-afa09cc-dirty-jief.zip

Just now, yapan4 said:

@Jief_Machak

My hack boot OK. What is dmidecode?

zsh: command not found: dmidecode

Screen Shot 2021-04-25 at 22.25.57.png

2021-4-25_19-23_BOOTX64.EFI.log 55.06 kB · 0 downloads

dmidecode

Just run "./dmidecode > dmiok.txt" before booting with my version, then run "./dmidecode > dminew.txt". Compare or send me the 2 files. They should be identical except for the build id of Clover.

  • Thanks 1
Link to comment
Share on other sites
yapan4
yapan4
Posted
Posted (edited)

In my case: 

 

after boot

 

Version: Intel(R) Xeon(R) W-2123 CPU @ 3.60GHz

Voltage: 1.6 V

External Clock: 25 MHz

Max Speed: 3601 MHz

Current Speed: 3600 MHz

 

before boot

 

Version: Intel(R) Xeon(R) W-2123 CPU @ 3.60GHz

Voltage: 1.6 V

External Clock: 25 MHz

Max Speed: 3600 MHz

Current Speed: 3600 MHz

 

for before boot used Github release v.5133

Edited by yapan4
Link to comment
Share on other sites
Jief_Machak
Jief_Machak
Posted
Posted
10 minutes ago, yapan4 said:

In my case after boot

 

Version: Intel(R) Xeon(R) W-2123 CPU @ 3.60GHz

Voltage: 1.6 V

External Clock: 25 MHz

Max Speed: 3601 MHz

Current Speed: 3600 MHz

Fine, I don't need your clock. I was just explaining what can be ok to be different in dmidecode produced output.

Did you use dmidecode with "normal" Clover and with my version ?

Link to comment
Share on other sites
yapan4
yapan4
Posted
Posted (edited)
6 minutes ago, Jief_Machak said:

Did you use dmidecode with "normal" Clover and with my version ?

Yes, for "normal" used release v.5133, for "after boot" - your version.  Upload full dmidecode dump?

Edited by yapan4
Link to comment
Share on other sites
Jief_Machak
Jief_Machak
Posted
Posted
2 minutes ago, yapan4 said:

Yes, for "normal" used release v.5133, for "after boot" - your version.  Upload full dmidecode dump?

Great. You can compare it if you have a file diff software. I can also compare them myself. You can send me them here or on private message.

Link to comment
Share on other sites
Slice
Slice
Posted
Posted
4 hours ago, Jief_Machak said:

New version. Solve a small thing when SmUUID is not defined.

@Slice You'll probably see a difference in Qemu as your config.plist doesn't have a SMBIOS section. The SmUUID was swapped compare to current Clover version.

 

CloverX64-2021-04-26-01-34-12-afa09cc-dirty-jief.zip 818.68 kB · 2 downloads

Booting to real hardware #1 in sig.

There are two major differences:

1. MaxSpeed in table 4 can be redefined by config.plist

-    Max Speed: 3300 MHz
+    Max Speed: 2712 MHz 

            <key>FrequencyMHz</key>
            <integer>3300</integer>


2. There is no table 132.

DMIdiff.txt.zip

Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted (edited)
14 hours ago, Jief_Machak said:

New version !

CloverX64-2021-04-25-19-03-21-afa09cc-dirty-jief.zip 820.23 kB · 3 downloads

 

@Slice smcRevision is fixed, and some others.

 

@everyone, SMBIOS was a particularly pain ! So if you'd like to help, use dmidecode before and after booting this version and tell me if there is a difference.

Thanks.


@Jief_Machak I use bootloader chooser for test. At boot before Clover GUI, there is a warning message: ask to check with configplistValidator, and to put boolean <true> for InjectKexts instead of usual <string>Yes</string> in Z390 config.plist. Why ?

  

iMac-de-Mathieu:~ mathieu$ /Users/mathieu/Downloads/Outils_Bootloader/Outils\ Clover/Outils\ New\ Clover\ +\ BootloaderChooser/CloverConfigPlistValidator0.7 '/Users/mathieu/Desktop/config.plist' 
Your plist looks so wonderful. Well done!
iMac-de-Mathieu:~ mathieu$ /Users/mathieu/Downloads/Outils_Bootloader/Outils\ Clover/Outils\ New\ Clover\ +\ BootloaderChooser/CloverConfigPlistValidator0.8 '/Users/mathieu/Desktop/config.plist' 
Cannot stat file 'config-nowarning-noerror.plist'


This commit boot fine Big Sur 11.4 Beta 1. SMBIOS is correct in Clover-Options and macOS SystemInfo with the good smcRevision :D

One issue remains: can't wake up after sleep (press space bar or mouse not working) 

 

Spoiler

185462574_Capturedcran2021-04-2609_30_28.png.b11cb87df7b029b434e2ced170fd496f.png



 

Dmidecode_out.txt 2021-4-24_16-20_CloverX64-2021-04-25-19-03-21-afa09cc-dirty-jief.efi.log

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

Booting to real hardware #1 in sig.

There are two major differences:

1. MaxSpeed in table 4 can be redefined by config.plist

-    Max Speed: 3300 MHz
+    Max Speed: 2712 MHz 


            <key>FrequencyMHz</key>
            <integer>3300</integer>


2. There is no table 132.

DMIdiff.txt.zip 1.54 kB · 0 downloads

To get table 132 I had to define QPI CloverX64-2021-04-26-15-06-03-afa09cc-dirty-jief.zip, but I have it now.

Max Speed too.

Thanks for the test.

4 hours ago, Matgen84 said:

put boolean <true> for InjectKexts instead of usual <string>Yes</string> in Z390 config.plist. Why ?

I personally think it's best to be more restrictive in technical files. A boolean is supposed to be <true/> or <false/>. Avoiding many ways to say the same thing ( <true/>, <string>yes</string>, <string>true</string>, <integer>1<integer> ) is always easier in the code.

It's still recognize, for historic reason, but I thought the new validation capabilities could help as it can tell exactly where and what to do.

If many voices are against that, I can remove that warning, of course.

  • Like 1
Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted (edited)
23 minutes ago, Jief_Machak said:

I personally think it's best to be more restrictive in technical files. A boolean is supposed to be <true/> or <false/>. Avoiding many ways to say the same thing ( <true/>, <string>yes</string>, <string>true</string>, <integer>1<integer> ) is always easier in the code.

It's still recognize, for historic reason, but I thought the new validation capabilities could help as it can tell exactly where and what to do.

If many voices are against that, I can remove that warning, of course.


@Jief_Machak The latest CloverconfiguratorPlist does not recognize the need for a boolean for InjectKext.
If you think, it's best to be more restrictive in technical files. You can introduce a boolean <true/> or <false/> for InjectKext directly in the repo config sample.plist. 

What do you think about sleep/wake up issue with your dirty_efi (2021-04-25-19-03-21-afa09cc-dirty-jief)? My Z390 rig can't wake up after sleep ! Please tell me.

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


@Jief_Machak The latest CloverconfiguratorPlist does not recognize the need for a boolean for InjectKext.
If you think, it's best to be more restrictive in technical files. You can introduce a boolean <true/> or <false/> for InjectKext directly in the repo config sample.plist. 

What do you think about sleep/wake up issue with your dirty_efi (2021-04-25-19-03-21-afa09cc-dirty-jief)? My Z390 rig can't wake up after sleep ! Please tell me.

Do you have the problem with this one : https://github.com/jief666/CloverCommits/blob/master/C-20210423175459-afa09cc.efi ?

CloverconfiguratorPlist will be up to date when I'll first commit this version with the new parser.

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