Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30960 posts in this topic

Recommended Posts

jsl2000
jsl2000
Posted
Posted (edited)
1 hour ago, SavageAUS said:


I can give that a try. I’m just curious as to why I need to set a value. I’ve been using clover on my amd hack for a while and never had this problem before and I don’t see any reports of anyone else having this issue.


Sent from my iPhone using Tapatalk

I found that in my AMD hackintoshs (FX-6300 & Ryzen 1700X) this value will affect the following:

1. Stability of Audio/video output

2. Performance scores of cinebench & geekbench

3. Panic or reboot before login to desktop during booting of Clover

4. Response of sleep/wake-up functions

Edited by jsl2000
MacKonsti
MacKonsti
Posted
Posted (edited)

Hello everyone Season Greetings. I managed to build/compile latest r5142+ commit of Clover (from a few days ago) via Clover Suite Builder and added some parameters in my config that were missing here and there.

Among these I added <key>ConsoleMode</key> and <string>0</string>

@Slice I see that in the log (via Hackintool) there is a missing output related to Console, for example, I see: 

0:420  0:000  Searching for invalid DiskIo BY_DRIVER connects: not found, all ok
0:724  0:303  === [ InitScreen ] ==============================
0:724  0:000  Console modes reported: 7, available modes:
0:724  0:000   - [01]: 320x75 (current mode)
0:724  0:000   - [02]: 80x50
0:724  0:000   - [03]: 100x31
0:724  0:000   - [06]: 128x40
0:724  0:000   - [07]: 80x25
0:724  0:000  SetMaxResolution: found best mode 0: 2560x1440
0:724  0:000   - already set
0:724  0:000  SetScreenResolution: 2560x1440 - already set
[...]
12:345  0:000  OCDM: RBAR is unsupported by device - Device Error
12:345  0:000  OC: Got 0 drivers
12:345  0:000  OCC: Installing GOP (Unsupported) on ConsoleOutHandle...
12:345  0:000  OC: Requested resolution is 0x0@0 (max: 0, force: 0) from 
12:345  0:000  OCC: Using builtin text renderer with 1 scale
12:406  0:060  OCC: Install console control (6D04DA00/0/0), current - Success
12:406  0:000  OCC: Setup ASCII Output - Success
12:406  0:000  OC: Requested console mode is 0x0 (max: 0) from 
12:406  0:000  OC: Requested not to use audio
12:406  0:000  OC: OcLoadAcpiSupport...
12:406  0:000  OC: OcLoadAcpiSupport : nothing to do
12:406  0:000  OC: OcMiscLateInit...
12:406  0:000  OC: Invalid HibernateMode: 
12:406  0:000  OC: Translated HibernateMode  to 0
12:406  0:000  OC: Hibernation activation - Invalid Parameter, hibernation wake - no

...the line Requested console mode is 0x0 (max: 0) from is missing the latter part after from, what is it supposed to show?

 

Also what is RBAR, everyone?
Finally the line OC: Invalid HibernateMode: what makes it invalid?

Where does OC: Hibernation activation - Invalid Parameter come from, any ideas? My hack can sleep just fine...

Thank you.

 

Edited by MacKonsti
Slice
Slice
Posted
Posted

Hi @Jief_Machak,

look please issue #483  RDRAND not patching so can't update to 12.1

I confirm the bug but I see no why it is happen.

 

@MacKonsti,

What is wrong with console mode? Current mode  

[01]: 320x75 (current mode)

And it is good.

0x0 means auto choose.

RBAR is OC quirk.

HibernateMode should be 0 as you are not going to enter hibernation. I don't understand what about the question.

  • Like 1
  • Thanks 1
MacKonsti
MacKonsti
Posted
Posted

Good evening @Slice it's just that the line seems to be missing something at the end, after "from" 

12:406  0:000  OC: Requested console mode is 0x0 (max: 0) from

...from what? :D:D Perhaps a parameter missing?

Also 

12:406  0:000  OC: Invalid HibernateMode: 
12:406  0:000  OC: Translated HibernateMode  to 0

...seems conflicting, no? Just curious. What causes Invalid HibernateMode to be shown in log? OC quirk? Thank you

Slice
Slice
Posted
Posted
23 minutes ago, MacKonsti said:

Good evening @Slice it's just that the line seems to be missing something at the end, after "from" 

12:406  0:000  OC: Requested console mode is 0x0 (max: 0) from

...from what? :D:D Perhaps a parameter missing?

Also 

12:406  0:000  OC: Invalid HibernateMode: 
12:406  0:000  OC: Translated HibernateMode  to 0

...seems conflicting, no? Just curious. What causes Invalid HibernateMode to be shown in log? OC quirk? Thank you

There are OC messages which I have no relation.

 

@Jief_Machak

Version "12" is not matched to OS 12.2 

12:399  0:000  Filtering KernelPatches:
12:399  0:000   - [00]: Monterey RDRAND instruction #1 :: [OS: 12.2 | MatchOS: 12 | MatchBuild: All]
12:399  0:000   ==> not allowed by OS
12:399  0:000   - [01]: Monterey RDRAND instruction #2 :: [OS: 12.2 | MatchOS: 12 | MatchBuild: All]
12:399  0:000   ==> not allowed by OS

 

Jief_Machak
Jief_Machak
Posted
Posted
4 hours ago, Slice said:

There are OC messages which I have no relation.

 

@Jief_Machak

Version "12" is not matched to OS 12.2 

12:399  0:000  Filtering KernelPatches:
12:399  0:000   - [00]: Monterey RDRAND instruction #1 :: [OS: 12.2 | MatchOS: 12 | MatchBuild: All]
12:399  0:000   ==> not allowed by OS
12:399  0:000   - [01]: Monterey RDRAND instruction #2 :: [OS: 12.2 | MatchOS: 12 | MatchBuild: All]
12:399  0:000   ==> not allowed by OS

 

I'll take a look.

I have to download a version 12 first, which will take some time.

Could you paste me the patch from the config.plist ?

  • Like 1
jsl2000
jsl2000
Posted
Posted (edited)
On 12/20/2021 at 8:55 AM, SavageAUS said:


I can give that a try. I’m just curious as to why I need to set a value. I’ve been using clover on my amd hack for a while and never had this problem before and I don’t see any reports of anyone else having this issue.

  

sysctl -a | grep freq
hw.busfrequency: 400000000
hw.busfrequency_max: 400000000
hw.busfrequency_min: 400000000
hw.cpufrequency: 14400000000
hw.cpufrequency_max: 14400000000
hw.cpufrequency_min: 14400000000
hw.tbfrequency: 1000000000
machdep.tsc.frequency: 6800000006

Setting to 400000 Makes everything go in slow motion, like half speed instead of double speed.

I will try 200000.

Below is at 200000 exactly and system seems to running at normal speed now.

The values in the below saection are still very different from what i get with OpenCore so i am not sure which one is correct. 

sysctl -a | grep freq
hw.busfrequency: 200000000
hw.busfrequency_max: 200000000
hw.busfrequency_min: 200000000
hw.cpufrequency: 7200000000
hw.cpufrequency_max: 7200000000
hw.cpufrequency_min: 7200000000
hw.tbfrequency: 1000000000
machdep.tsc.frequency: 3400000000
  Hide contents

256549259_ScreenShot2021-12-19at5_56_19pm.png.e082369ff3be461e0d9fe1370027a5b5.png



Sent from my iPhone using Tapatalk

With this setting 200000 can you get fully normal audio output now ?

In my Ryzen 1700X it still found minimal crack from YouTube's "Unchained Melody" such as

  or

Because in my Ryzen 1700X hackintosh still found minimal crack background noise during play these video even set it to 200000 without reboot before login to desktop now. No such an issue booted by OpenCore, it occured only booted by Clover 5141/5142.

Edited by jsl2000
SavageAUS
SavageAUS
Posted
Posted


I can give audio a try at 200000 but I’m very hesitant to use Clover at the moment because of the fast speed issue and the differences in values between OpenCore and clover are very big.

Until I can get a resolution I won’t be using clover as my daily driver on my AMD rig.

I have tried the latest build of Clover and 5142 & 5141. I can try older versions when I get time I guess but it only seems to have happened recently since changing my smbios to suit my new hardware.

Surely if it was a config problem it would have been picked up and if it was a bios problem it would happen with OpenCore as well? Just frustrates me as I prefer Clover as my boot loader and to stop using it feels strange.
  • Sad 1
Andres ZeroCross
Andres ZeroCross
Posted
Posted (edited)

I got kernel panic with CLOVER 5142 in Legacy Mode . but if i use CLOVER 5119 Legacy Mode then there is no kernel panic.

I use latest Lilu, AppleALC.kext, VirtualSMC.kext, RestrictEvent.kext, WhateverGreen.kext.

The KP logs show about Lilu and RestrictEvent.kext, i tried to delete RestrictEvent.kext but then KP Logs will show KP about Lilu and VirtualSMC,kext.

Then i revert to Clover 5119 with same version of Lilu, AppleALC.kext, VirtualSMC.kext, RestrictEvent.kext, WhateverGreen.kext and booting is fine.

Any special trick to inject kext in CLOVER 5142???

image.thumb.png.1e202bfd6e7d48ef77f0c8535b820e97.png 

Edited by Andres ZeroCross
Slice
Slice
Posted
Posted
18 hours ago, Jief_Machak said:

I'll take a look.

I have to download a version 12 first, which will take some time.

Could you paste me the patch from the config.plist ? 

		<key>KernelToPatch</key>
		<array>
			<dict>
				<key>Comment</key>
				<string>Monterey RDRAND instruction #1</string>
				<key>MatchOS</key>
				<string>12</string>
				<key>Disabled</key>
				<false/>
				<key>Procedure</key>
				<string>_work_interval_port_type_render_server</string>
				<key>RangeFind</key>
				<integer>3900</integer>
				<key>Find</key>
				<data>D8fxc/sh8TnRc/WJyUiLlM3Q/f//</data>
				<key>Replace</key>
				<data>McmQkJAh8TnRc/WJyUiLlM3Q/f//</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>Monterey RDRAND instruction #2</string>
				<key>MatchOS</key>
				<string>12</string>
				<key>Disabled</key>
				<false/>
				<key>Procedure</key>
				<string>_panic_with_thread_context</string>
				<key>RangeFind</key>
				<integer>10100</integer>
				<key>Find</key>
				<data>D8fyc/uD4g+D+gd38w+3NEE=</data>
				<key>Replace</key>
				<data>MdKQkJCD4g+D+gd38w+3NEE=</data>
			</dict>
		</array>

 

8 hours ago, simmel said:

RDRAND patch is not needed anymore. Apple removed the instruction.

Anyway the bug should be resolved.

Slice
Slice
Posted
Posted
11 hours ago, Jief_Machak said:

@Slice looking at the code that was moved in AbstractMacOsVersion::match(MacOsVersionPattern), "12" will only match version 12. Not 12.0 or 12.1 etc.

To match any version 12, "12.x" should be used as the pattern.

But kexts folder "12" matched to OS 12.2? Expected same logic.

Slice
Slice
Posted
Posted
1 hour ago, Slice said:

But kexts folder "12" matched to OS 12.2? Expected same logic.

OK, let it be 12.x

 

@5T33Z0

Look please your instructions about MatchOS.There should be masked strings 12.x, 11.5.x etc.

 

16 minutes ago, SavageAUS said:

Just to test I tried 5143 and still same result. Double speed.


Sent from my iPhone using Tapatalk

Set BusSpeedkHz as 200000 and give me boot-log.

 

bdmesg > boot-log.txt

SavageAUS
SavageAUS
Posted
Posted
1 hour ago, Slice said:

OK, let it be 12.x

 

@5T33Z0

Look please your instructions about MatchOS.There should be masked strings 12.x, 11.5.x etc.

 

Set BusSpeedkHz as 200000 and give me boot-log.

 

bdmesg > boot-log.txt

zsh: command not found: bdmesg

Jief_Machak
Jief_Machak
Posted
Posted
11 hours ago, Slice said:

But kexts folder "12" matched to OS 12.2? Expected same logic.

Yes, true.

I think it was already like that before refactoring to MacOSVersion object. Not 100% sure though.

The problem of 12 (or any other single number) matching any 12 version is that there would’ve no way of matching the version 12, but not version 12.1

I remember that Big Sur had a version 11, then a version 11.1. Was it the same for Monterey ? 12, then 12.1 ?

Jief_Machak
Jief_Machak
Posted
Posted (edited)

A refactor of the logic, to make it simpler, would be to use “version start” - “version stop” logic ?

The “version stop” would NOT match.

11 : matches only 11

11.2-11.3 : matches 11.2 11.2.1 etc.

11.2.1-11.3.4 matches from 11.2.1 until 11.3.3

11.4-12.5 matches 11.4.x to 12.4.x

12- matches 12 and greater

 

we can then apply the same logic for next folders.

Edited by Jief_Machak
  • Like 2
Jief_Machak
Jief_Machak
Posted
Posted (edited)

Let’s explain why we need “start-stop” to disambiguate.

The problem we have is that, in kext folder naming, no suffix means “match”. 12 matches 12 and 12.1, 12.2, etc. Therefore there is no way of specifying 12 that doesn’t match 12.1

 

For the 12.x notation, 12 matches only 12, but 12.x also matches 12, which is a bit counter-intuitive.

 

Nothing major and because changing something is always a bit of trouble, should we leave it ?…

Edited by Jief_Machak
  • Like 2
 Share
Go to topic listing
×
×
  • Create New...