Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30,058 posts in this topic

Recommended Posts

kushwavez
kushwavez
Posted
Posted (edited)

My AGDP KextPatches aren't working anymore on Big Sur, but they are on Catalina. I used them for my VGA, HDMI outputs. I replaced them with agdpmod=vit9696 so it's okay, but I'm still trying to figure out why aren't they working on Big Sur. I used the name "com.apple.driver.AppleGraphicsDevicePolicy" on Catalina and the patch was successful. However on Big Sur it says: 

10:395  0:006  OCAK: Failed to pk find com.apple.driver.AppleGraphicsDevicePolicy - Not Found
10:397  0:002  OC: Kernel patcher result 4 for com.apple.driver.AppleGraphicsDevicePolicy (com.apple.driver.AppleGraphicsDevicePolicy (AGDP Catalina 10.15.X Patch 5)) - Not Found

according to the debug.log. The Terminal shows that the name is correct:  

Executing: /usr/bin/kmutil showloaded
  156    0 0xffffff7f9e556000 0x9000     0x9000     com.apple.driver.AppleGraphicsDevicePolicy (6.1.24) F276DA99-0775-371F-BE61-C8E66EF429F9 <155 115 114 14 13 8 7 6 5 3 1>

Is it renamed or smth?

Patch:

Spoiler 

<dict>
	<key>Comment</key>
	<string>AGDP Catalina 10.15.X Patch 1</string>
	<key>Disabled</key>
	<false/>
	<key>Find</key>
	<data>RURJRAA=</data>
	<key>InfoPlistPatch</key>
	<false/>
	<key>Name</key>
	<string>com.apple.driver.AppleGraphicsDevicePolicy</string>
	<key>Replace</key>
	<data>RURJSQA=</data>
</dict>

 

Here is the debug: debug.log

 

Anyway Clover V5124 is working well on my 3 computers (in my signature):

PC: Windows 10 OK, Catalina 10.15.7 OK, Big Sur Beta 9 OK (on separate HDD)

Spoiler

895184231_Screenshot2020-10-14at13_10_39.png.29e4e3ee0b7195798fb42b36cc78a86e.png

 

Notebook 1: Windows 10 OK, Catalina 10.15.7 OK, Big Sur Beta 9 OK, Fedora Linux OK (on same SSD)

Spoiler

1738226824_Screenshot2020-10-14at10_01_54.png.d98d2cc25b54e7fcbaee3063adba837f.png

 

Notebook 2: Windows 10 OK, Catalina 10.15.7 OK, Big Sur Beta 9 OK (on same SSD)

Spoiler

206766072_ScreenShot2020-10-14at10_35_30AM.png.40b3d0439279f8073b2809cc002db322.png

 

Catalina and Big Sur are running from the same EFI, nothing need to be modified.

Now waiting for the final Big Sur release! :D 

Edited by kushwavez
  • Like 2
Link to comment
Share on other sites
Henry2010
Henry2010
Posted
Posted (edited)
6 hours ago, Slice said:

I have to explain.

There are two main roads leading to purpose.

One, older way supporting by me and still working:

1. FakeSMC.kext+its plugins (IntelCpuMonitor.kext, RadeonMonitor.kext, ITEIT87x.kext, ACPIMonitor.kext, VoodooBatterySMC.kext, SMIMonitor.kext)

2. SMCHelper.efi driver

Second way, developed by vit9696 and Acidanthera group:

1. VirtualSMC.kext+its plugins (.....). It required Lilu.kext to be also installed.

2. VirtualSMC.efi driver.

 

Don't mix these different ways! Don't jump from one road to another on full speed!

 

Thanks, so that means FakeSMC* kexts will continue to work in 5123/5124+, even though OC includes VirtualSMC.efi. There's no conflict.

And if one decided to use VirtualSMC* kexts + Lilu, he wouldn't need to add an extra VirtualSMC.efi in the UEFI folder(?). :whistle:

Edited by Henry2010
Link to comment
Share on other sites
Vampirexx
Vampirexx
Posted
Posted
54 minutes ago, kushwavez said:

My AGDP KextPatches aren't working anymore on Big Sur, but they are on Catalina. I used them for my VGA, HDMI outputs. I replaced them with agdpmod=vit9696 so it's okay, but I'm still trying to figure out why aren't they working on Big Sur. I used the name "com.apple.driver.AppleGraphicsDevicePolicy" on Catalina and the patch was successful. However on Big Sur it says: 


10:395  0:006  OCAK: Failed to pk find com.apple.driver.AppleGraphicsDevicePolicy - Not Found
10:397  0:002  OC: Kernel patcher result 4 for com.apple.driver.AppleGraphicsDevicePolicy (com.apple.driver.AppleGraphicsDevicePolicy (AGDP Catalina 10.15.X Patch 5)) - Not Found

according to the debug.log. The Terminal shows that the name is correct:  


Executing: /usr/bin/kmutil showloaded
  156    0 0xffffff7f9e556000 0x9000     0x9000     com.apple.driver.AppleGraphicsDevicePolicy (6.1.24) F276DA99-0775-371F-BE61-C8E66EF429F9 <155 115 114 14 13 8 7 6 5 3 1>

Is it renamed or smth?

Patch:

  Reveal hidden contents 


<dict>
	<key>Comment</key>
	<string>AGDP Catalina 10.15.X Patch 1</string>
	<key>Disabled</key>
	<false/>
	<key>Find</key>
	<data>RURJRAA=</data>
	<key>InfoPlistPatch</key>
	<false/>
	<key>Name</key>
	<string>com.apple.driver.AppleGraphicsDevicePolicy</string>
	<key>Replace</key>
	<data>RURJSQA=</data>
</dict>

 

Here is the debug: debug.log

 

Anyway Clover V5124 is working well on my 3 computers (in my signature):

PC: Windows 10 OK, Catalina 10.15.7 OK, Big Sur Beta 9 OK (on separate HDD)

  Reveal hidden contents

895184231_Screenshot2020-10-14at13_10_39.png.29e4e3ee0b7195798fb42b36cc78a86e.png

 

Notebook 1: Windows 10 OK, Catalina 10.15.7 OK, Big Sur Beta 9 OK, Fedora Linux OK (on same SSD)

  Reveal hidden contents

1738226824_Screenshot2020-10-14at10_01_54.png.d98d2cc25b54e7fcbaee3063adba837f.png

 

Notebook 2: Windows 10 OK, Catalina 10.15.7 OK, Big Sur Beta 9 OK (on same SSD)

  Reveal hidden contents

206766072_ScreenShot2020-10-14at10_35_30AM.png.40b3d0439279f8073b2809cc002db322.png

 

Catalina and Big Sur are running from the same EFI, nothing need to be modified.

Now waiting for the final Big Sur release! :D 

 

 

Please can you share your efi folder so i can see your config and drivers settings please i'm desperate with these last clover versions. THX

 

  • Like 1
Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted
49 minutes ago, Henry2010 said:

 

Thanks, so that means FakeSMC* kexts will continue to work in 5123/5124+, even though OC includes VirtualSMC.efi. There's no conflict.

And if one decided to use VirtualSMC* kexts + Lilu, he wouldn't need to add an extra VirtualSMC.efi in the UEFI folder(?). :whistle:

 

The VirtualSmc.efi drivers is only for FileVault. Go to VirtualSMC topic for more informations, if you want. The last @Slice FakeSMC.kext works fine on my system.

  • Like 4
Link to comment
Share on other sites
Mirone
Mirone
Posted
Posted
7 hours ago, ludox said:
 
Hello my dear friend, all right?
Tell me what you use your desktop or notebook, let's see if I can help you this time .. :)
What is the problem ...?
I have no problem with the clover 5123 and 5124 all perfect Big Sur and Catalina both on the desktop PC and on the Acer e1 notebook in signature.
 
 

Hello my friend,
The problem was solved, compiled clover and made some changes now everything works fine.

  • Like 1
  • Thanks 1
Link to comment
Share on other sites
maclinuxG4
maclinuxG4
Posted
Posted (edited)
1 hour ago, Matgen84 said:

 

The VirtualSmc.efi drivers is only for FileVault. Go to VirtualSMC topic for more informations, if you want. The last @Slice FakeSMC.kext works fine on my system.

 

1 hour ago, Matgen84 said:

 

The VirtualSmc.efi drivers is only for FileVault. Go to VirtualSMC topic for more informations, if you want. The last @Slice FakeSMC.kext works fine on my system.

 

Exact, but i notice too restriction of information for Hwmonitor, istat, and not present. In fact, in 5123.pkg they are reduced, but not in r5122.pgk

(IT87, radeonmonitor, etc...).

 

Edited by maclinuxG4
Link to comment
Share on other sites
corint1
corint1
Posted
Posted

important note: I can't load voodooinput, no matter where you can load it ... in other words, voodooI2C and its satellites don't load ... not even a simple acidoodhera voodooinput ... did anyone manage to load this kext? without it the trackpad doesn't work ... I'm waiting for reactions ..thanks
 

Link to comment
Share on other sites
naiclub
naiclub
Posted
Posted
1 minute ago, Mirone said:

The name of my processor is being displayed as "Unknown" on clover r5124, anyone else with this problem?

Yes, really many problems. Need encouragement to help developers I believe he's tired

Link to comment
Share on other sites
kushwavez
kushwavez
Posted
Posted

If you people having problems with the loader or anything you think related to that, attach debug logs about earlyboot and verbose. They're really helping the developers. They can't just figure out what is the matter from "it's not working"

  • Like 2
  • Thanks 1
Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted
31 minutes ago, Mirone said:

The name of my processor is being displayed as "Unknown" on clover r5124, anyone else with this problem?

 

Idem here on Z77 system, don't try in Z390. My temporary solution: cpu type in config.plist. 

  • Like 1
Link to comment
Share on other sites
iCanaro
iCanaro
Posted
Posted (edited)
1 hour ago, Mirone said:

The name of my processor is being displayed as "Unknown" on clover r5124, anyone else with this problem?

I just tested on Z68, Z97, Z170 and Z370 and the CPU is detected correctly :) 

PS: I used CLOVERX64-5124-1bb8b0dd3.efi compiled today

 

1 hour ago, naiclub said:

Yes, really many problems. Need encouragement to help developers I believe he's tired

I don't think they're tired
but I also think they have a life of their own and they don't work 20 hours a day on Clover's code
it takes a lot of patience and so many debugging logs run correctly :) 

Edited by iCanaro
  • Like 2
  • Haha 1
Link to comment
Share on other sites
naiclub
naiclub
Posted
Posted (edited)
2 hours ago, mifjpn said:

Thank you for your efforts.
I didn't know I didn't need VirtualSmc.efi.

I put VirtualSmc.efi and
SMCProcessor.kext
SMCSuperIO.kext
VirtualSMC.kext
I was using.

Now, delete VirtualSmc.efi and
I have installed SMCHelper.efi.
Then I tried FakeSMC.kext and the kext around it.
It works fine.
It cannot coexist, but it can be selected.
Thank you.

By the way, how can I get information about fans with FakeSMC?

You take a look at AIDA64 Extreme and compare as closely

Spoiler

343648202_Screenshot2020-10-15003805.thumb.png.492e75f823b8570a45484ce9ec4ddd92.png1190256555_Screenshot2020-10-14233812.thumb.png.904c678dc87ad0c19f63c28b6a711eec.png

 

Edited by naiclub
Link to comment
Share on other sites
corint1
corint1
Posted
Posted (edited)

a few hours ago I asked about voodooI2C and I communicated that with the new version of the clover it doesn't load anymore ... as a result the trackpad of the laptop doesn't work anymore ... no reaction ... interesting that the priority is the correct display of the processor type and not the disappearance of some functionalities ... thanks to all those who answered me ...
 

edit : answer from voodooI2C community :
 

@corint1 as already pointed out: you are riding a dead horse. Especially on Big Sur. It's rather unlikely that you'll find someone able and/or willing to help and invest time in that matter. Migrate now. For your own good...
 
I think it is the best option, according to how quickly it responds to problems related to clover and lost functionality
 
Edited by corint1
Link to comment
Share on other sites
kushwavez
kushwavez
Posted
Posted (edited)
12 minutes ago, corint1 said:

a few hours ago I asked about voodooI2C and I communicated that with the new version of the clover it doesn't load anymore ... as a result the trackpad of the laptop doesn't work anymore ... no reaction ... interesting that the priority is the correct display of the processor type and not the disappearance of some functionalities ... thanks to all those who answered me ...
 

See or share your debug.log if it's actually loaded or not, and if not, then why not. I see you're frustrated but again, you didn't share any log about anything, we/they can't really help you without these.

Edited by kushwavez
  • Like 1
Link to comment
Share on other sites
corint1
corint1
Posted
Posted (edited)
9 minutes ago, kushwavez said:

See or share your debug.log if it's actually loaded or not. I see you're frustrated but again, you didn't share any log about anything, we/they can't really help you without these.

I will try this too, although I don't know how to do it ... but I don't think I'm the only one who ran into this problem ... maybe you can explain to me how to get this debug.log, so as not to waste time searching on the net

Edited by corint1
Link to comment
Share on other sites
kushwavez
kushwavez
Posted
Posted (edited)

@corint1 set config.plist/Boot/Debug=True, config.plist/KernelAndKextPatches/Debug=True, set bootflags "-v debug=0x100 keepsyms=1" then boot. After booting is finished you'll find your debug.log inside EFI/CLOVER/misc

 

Also you can obtain the verbose log by this command (it'll save to a bootlog.log file where you're terminal is opened): 

log show --predicate "processID == 0" --start $(date "+%Y-%m-%d") --debug > bootlog.log

 

 

Edited by kushwavez
  • Like 1
Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...