Jump to content

Clover General discussion


ErmaC
30,171 posts in this topic

Recommended Posts

3 hours ago, Slice said:

Yes, you have to drop similar tables to avoid symbol duplication.


Thanks @Slice

Something like that to avoid symbol duplication with original SSDT-6-A M I.aml for my Z390 Aorus Master. Decimal (11547) instead of Hex (0x00002D1B) with <integer>. Right ? 

<key>DropTables</key>
		<array>
			<dict>
				<key>Signature</key>
				<string>DMAR</string>
			</dict>
			<dict>
				<key>Signature</key>
				<string>MATS</string>
			</dict>
			<dict>
				<key>Length</key>
				<integer>11547</integer>
				<key>Signature</key>
				<string>SSDT</string>
			</dict>
		</array>

 

Edited by Matgen84
Link to comment
Share on other sites

4 minutes ago, Slice said:

Clover is not Opencore, it supports hexadecimal values

				<key>Length</key>
				<string>0x2D1B</string>

 

 

Ok. Thanks. 

But the config-sample.plist, there is integer instead of string, for the value of Length. CloverConfigPlistValidator accepts both <string>0x2D1B</string> and <integer>1547</integer>. I don't understand why.

 

			<dict>
				<key>#Length</key>
				<integer>720</integer>
				<key>TableId</key>
				<string>Cpu0Ist</string>
				<key>Signature</key>
				<string>SSDT</string>
			</dict>

 

Link to comment
Share on other sites

I have it so ... with TableId

 

<dict>
                <key>DropForAllOS</key>
                <true/>
                <key>Signature</key>
                <string>SSDT</string>
                <key>TableId</key>
                <string>xh_rvp08</string>
            </dict>

 

OC 

 

</dict>
                </array>
                <key>Delete</key>
                <array>
                    <dict>
                        <key>All</key>
                        <false/>
                        <key>Comment</key>
                        <string>Drop OEM SSDT-3-xh_rvp08</string>
                        <key>Enabled</key>
                        <true/>
                        <key>OemTableId</key>
                        <data>
                        </data>
                        <key>TableLength</key>
                        <integer>2592</integer>
                        <key>TableSignature</key>
                        <data>
                        U1NEVA==
                        </data>
                    </dict>

Edited by antuneddu
Link to comment
Share on other sites

1 hour ago, Mr MagOO said:

Hello!

I tried clover 5140 and it does not boot.

Back to 5139 and it boots well.

Too old rig ?

Have you checked with
CloverConfigPlistValidator?
Started fine after update (driver) OpenRuntime.UEFI (extracted from pkg)

 

Schermata 2021-09-28 alle 19.29.43.png

 

screenshot0.png

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

5 minutes ago, Mr MagOO said:

I'm in legacy mode and I boot Catalina.

No OpenRuntime needed.

Maybe new OC integration ?

New Clover requires new OpenRuntime but I am not sure about legacy mode.

Can you make debug.log?

Link to comment
Share on other sites

@Intel6600

Remember Opencore appeared when mostly all hackintosh technologies was developed by Clover team as well as Chameleon team in past.

Yes, Clover still has technologies that OC has no: tuning settings from GUI, SVG themes, ACPI tuning, devices tuning, advance SMBIOS etc.

  • Like 3
  • Thanks 1
Link to comment
Share on other sites

I love and use Clover on a daily basis and I appreciate all the work to update and maintain it and keep it working for free for all of us but the one thing that irks me is the lack of documentation. Latest release says -

Implemented ExtendedFirmwareFeatures which is needed for Monterey beta 7.
Integration with OC 0.7.3

Ok…. But what do we need to do? What else was changed?

I get it we can just use the sample config.plist and compare or cross our fingers and hope it boots. Does the change only effect Intel based machines? Will AMD hacks be affected? Both?

Perhaps I am over thinking things but if a new user was to come to clover now what is out there to help them?

If you feel this post is not needed feel free to delete it.


Sent from my iPhone using Tapatalk

Link to comment
Share on other sites

15 hours ago, Slice said:

New Clover requires new OpenRuntime but I am not sure about legacy mode.

Can you make debug.log?



 

today I will test the r5140 on legacy 1gen laptop

later post the result


Thanks Team

Link to comment
Share on other sites

18 hours ago, Mr MagOO said:

Hello!

I tried clover 5140 and it does not boot.

Back to 5139 and it boots well.

Too old rig ?

◊         

boot OK r5140

HP DV6 2140ef
intel i5 M430
Geforce Nvidia GT320M

Monterey Beta

16 hours ago, Slice said:

New Clover requires new OpenRuntime but I am not sure about legacy mode.

Can you make debug.log?

Boot ok Legacy confirmed

 

Spoiler

1937680420_Capturedecran2021-09-29a14_03_43.thumb.png.1678349fce96d0c5f4645cd9b75c9279.png

 

2021-09-29_11-45_CLOVERX64.EFI.log preboot.log

  • Like 2
Link to comment
Share on other sites

20 hours ago, Slice said:

@Jief_Machak

You changed something?

0:279  0:000  Calibrated TSC Frequency = 0 = 0MHz

Somehow the system works.

Interesting side effect. Because the static objects are constructed, not before main() as in a normal C++ program, but when we call construct_globals_objects(), the assignment of gCPUStructure.TSCCalibr was resetted by the gCPUStructure ctor.

  • Like 2
Link to comment
Share on other sites

3 hours ago, Jief_Machak said:

Interesting side effect. Because the static objects are constructed, not before main() as in a normal C++ program, but when we call construct_globals_objects(), the assignment of gCPUStructure.TSCCalibr was resetted by the gCPUStructure ctor.

Thanks for finding. Now fine

0:265  0:000  Calibrated TSC Frequency = 2712383230 = 2712MHz

Replace 5140 release?

  • Like 1
Link to comment
Share on other sites

4 hours ago, Slice said:

I have a new idea:

OpenRuntime loaded after GUI so we can make manually choose one of OpenRuntime/AptioFix drivers same way as kexts Enable/Disable.

No completely sure of what you mean, but I don't think we have a choice : with a specific OC version goes a specific OpenRuntime version. Giving the choice of loading on old OpenRuntime won't work.

But I might not have understood well the idea.

1 hour ago, antuneddu said:

I extracted it from the pkg yesterday ... if you want

 

 

OpenRuntime.efi.zip 4.1 kB · 0 downloads

Please, rename it to OpenRuntime-v12.efi. That way, the next time (for OpenRuntime v13) it'll be easier.

  • Like 3
Link to comment
Share on other sites

×
×
  • Create New...