kushwavez Posted October 14, 2020 Share Posted October 14, 2020 (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 Notebook 1: Windows 10 OK, Catalina 10.15.7 OK, Big Sur Beta 9 OK, Fedora Linux OK (on same SSD) Spoiler Notebook 2: Windows 10 OK, Catalina 10.15.7 OK, Big Sur Beta 9 OK (on same SSD) Spoiler Catalina and Big Sur are running from the same EFI, nothing need to be modified. Now waiting for the final Big Sur release! Edited October 14, 2020 by kushwavez 2 Link to comment Share on other sites More sharing options...
Henry2010 Posted October 14, 2020 Share Posted October 14, 2020 (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(?). Edited October 14, 2020 by Henry2010 Link to comment Share on other sites More sharing options...
Vampirexx Posted October 14, 2020 Share Posted October 14, 2020 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 Notebook 1: Windows 10 OK, Catalina 10.15.7 OK, Big Sur Beta 9 OK, Fedora Linux OK (on same SSD) Reveal hidden contents Notebook 2: Windows 10 OK, Catalina 10.15.7 OK, Big Sur Beta 9 OK (on same SSD) Reveal hidden contents Catalina and Big Sur are running from the same EFI, nothing need to be modified. Now waiting for the final Big Sur release! 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 1 Link to comment Share on other sites More sharing options...
Matgen84 Posted October 14, 2020 Share Posted October 14, 2020 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(?). 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. 4 Link to comment Share on other sites More sharing options...
kushwavez Posted October 14, 2020 Share Posted October 14, 2020 @Vampirexx Here you go. PC: Z170-DELUXE_5124.zip Notebook 1: Acer_Catalina_5124.zip Notebook 2: ThinkPad_T440_5124.zip (still need improvements & cleanup) 1 1 Link to comment Share on other sites More sharing options...
Mirone Posted October 14, 2020 Share Posted October 14, 2020 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. 1 1 Link to comment Share on other sites More sharing options...
maclinuxG4 Posted October 14, 2020 Share Posted October 14, 2020 (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 October 14, 2020 by maclinuxG4 Link to comment Share on other sites More sharing options...
corint1 Posted October 14, 2020 Share Posted October 14, 2020 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 More sharing options...
naiclub Posted October 14, 2020 Share Posted October 14, 2020 Bad news for me Latest compiled version 5124 can't boot into High_Sierra, the line says cpu is not supported. 1 Link to comment Share on other sites More sharing options...
Mirone Posted October 14, 2020 Share Posted October 14, 2020 The name of my processor is being displayed as "Unknown" on clover r5124, anyone else with this problem? 1 Link to comment Share on other sites More sharing options...
naiclub Posted October 14, 2020 Share Posted October 14, 2020 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 More sharing options...
galisrule Posted October 14, 2020 Share Posted October 14, 2020 (edited) Early boot processes is not visible even though it boots in the end. Any idea anyone attached also is the debug file please and thanks booting3.mp4 debug.log.zip Edited October 14, 2020 by galisrule adding debug log file Link to comment Share on other sites More sharing options...
kushwavez Posted October 14, 2020 Share Posted October 14, 2020 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" 2 1 Link to comment Share on other sites More sharing options...
naiclub Posted October 14, 2020 Share Posted October 14, 2020 14 minutes ago, galisrule said: no early boot process booting3.mp4 -V 1 Link to comment Share on other sites More sharing options...
Matgen84 Posted October 14, 2020 Share Posted October 14, 2020 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. 1 Link to comment Share on other sites More sharing options...
Matgen84 Posted October 14, 2020 Share Posted October 14, 2020 (edited) 51 minutes ago, mifjpn said: By the way, how can I get information about fans with FakeSMC? Have a look to repo FakeSMC3 GitHub FakeSMC 3 or HWSensor3 Edited October 14, 2020 by Matgen84 Link to comment Share on other sites More sharing options...
JorgeMax Posted October 14, 2020 Share Posted October 14, 2020 42 minutes ago, Mirone said: The name of my processor is being displayed as "Unknown" on clover r5124, anyone else with this problem? I have this problem How long Mirone, welcome back 2 Link to comment Share on other sites More sharing options...
galisrule Posted October 14, 2020 Share Posted October 14, 2020 12 minutes ago, Matgen84 said: Idem here on Z77 system, don't try in Z390. My temporary solution: cpu type in config.plist. same here processor unknown 1 Link to comment Share on other sites More sharing options...
iCanaro Posted October 14, 2020 Share Posted October 14, 2020 (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 October 14, 2020 by iCanaro 2 1 Link to comment Share on other sites More sharing options...
naiclub Posted October 14, 2020 Share Posted October 14, 2020 (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 Edited October 14, 2020 by naiclub Link to comment Share on other sites More sharing options...
maclinuxG4 Posted October 14, 2020 Share Posted October 14, 2020 plz check the installer clvoer .pkg, but if you need opentime.efi, the installer don' t update EFI , and you have openrutinme.efi in your folder. 1 Link to comment Share on other sites More sharing options...
corint1 Posted October 14, 2020 Share Posted October 14, 2020 (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 October 14, 2020 by corint1 Link to comment Share on other sites More sharing options...
kushwavez Posted October 14, 2020 Share Posted October 14, 2020 (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 October 14, 2020 by kushwavez 1 Link to comment Share on other sites More sharing options...
corint1 Posted October 14, 2020 Share Posted October 14, 2020 (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 October 14, 2020 by corint1 Link to comment Share on other sites More sharing options...
kushwavez Posted October 14, 2020 Share Posted October 14, 2020 (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 October 14, 2020 by kushwavez 1 Link to comment Share on other sites More sharing options...
Recommended Posts