bronxteck Posted January 26, 2017 Share Posted January 26, 2017 3989 seems to compile fine using edk 23831 after removing conflicting file EfiShell.h. Booted fine on haswell integrated graphics laptop with beta 10.12.4 also used mick script with latest edk rev edit in it Link to comment Share on other sites More sharing options...
FredWst Posted January 27, 2017 Share Posted January 27, 2017 Hi, Rev 3990 working fine. I've a question I install a fresh Sierra 10.12.3, choose my language French, at second stage install goes in English ? Is-it a Clover bug ? Fred Link to comment Share on other sites More sharing options...
arsradu Posted January 27, 2017 Share Posted January 27, 2017 Hi guys, Has anyone tried 10.12.4 PB1 yet? Does it boot for you? I'm on Clover 3974 and can't boot anymore after upgrading to that Beta. Good thing it's on a different partition. Update: Nvm that. I managed to boot using the patch posted by Slice above. Million thanks! update 2: for anyone wondering, Clover 3994 injection now works fine without the patch above. So if you haven't, you should probably update. 1 Link to comment Share on other sites More sharing options...
Slice Posted January 27, 2017 Share Posted January 27, 2017 this is the same: Get_PreLink() ...should be a good place to dinamically patching the kernel (LC_SEGMENT/LC_SEGMENT_64), since we already iterates through the kernel in that function. Everythings needs is already in loader.h Take into account that we don't know where the kernel is loaded. It is Chameleon who knows. Link to comment Share on other sites More sharing options...
tluck Posted January 27, 2017 Share Posted January 27, 2017 Happy new year! thank you all! reporting good news... clover 3994 and edk2 23831 all working good here for 10.12.3 and 10.12.4 pb1 on Lenovo T420 UEFI and Lenovo T460 UEFI+EmuVariable Link to comment Share on other sites More sharing options...
bronxteck Posted January 27, 2017 Share Posted January 27, 2017 mick do you think its safe now to update the edk version to 23831 in your script seeming as your default edk 23704 is causing issues with boot on some machines? Link to comment Share on other sites More sharing options...
Micky1979 Posted January 27, 2017 Share Posted January 27, 2017 The fact is that I don't know what revision is reccomended by Slice. However the script can be edited for now. Link to comment Share on other sites More sharing options...
Micky1979 Posted January 27, 2017 Share Posted January 27, 2017 Take into account that we don't know where the kernel is loaded. It is Chameleon who knows. I'll test it soon, the idea (ATM is only that) is that there's no need for the kernel itself, but for its segments and relative load commands. Link to comment Share on other sites More sharing options...
bs0d Posted January 27, 2017 Share Posted January 27, 2017 Take into account that we don't know where the kernel is loaded. It is Chameleon who knows. At ExitBootServices once you found the boot args struct. KernelData = (VOID *)(UINTN)(BA2->kernelSlide + 0x00200000); now you know too 5 Link to comment Share on other sites More sharing options...
Slice Posted January 28, 2017 Share Posted January 28, 2017 At ExitBootServices once you found the boot args struct. KernelData = (VOID *)(UINTN)(BA2->kernelSlide + 0x00200000); now you know too It's a pity I saw faults with this algo. I need double check with some signature. The fault is not influence on kernel patches because in this case we just search all memory, long delay but works. Rare users have full faults without ability to start system. This can be one of the reason. Link to comment Share on other sites More sharing options...
mhaeuser Posted January 28, 2017 Share Posted January 28, 2017 AptioFix vs AptioFix2? The text section was always at that address and kernelSlide is always set correctly (otherwise the kernel itself wouldn't know where stuff is... could need fixing if u relocate, idk), this algo cannot be flawed... Link to comment Share on other sites More sharing options...
erice Posted January 28, 2017 Share Posted January 28, 2017 In new 10.12.4 beta Radeon HD 5570 shows flicker. I restored the kext graphics of 12.3 but the situation is the same: hd works but bad for exactly the same way. No idea where the problem may reside for a card whose id is still present in AMDLegacySupport.kext? Sorry for the English and thank you. 1 Link to comment Share on other sites More sharing options...
r2tincan Posted January 29, 2017 Share Posted January 29, 2017 Clover will not go past "Scanning Entries..." if I have SoftRAID drives. This is using the newest release version. My previous version did not have this issue. Please fix! Link to comment Share on other sites More sharing options...
Dajjal Posted January 29, 2017 Share Posted January 29, 2017 Tried r3994 on my X58 system but it killed Audio.Nothing showed up in system prefs but was present system report/audio.Tried rebuilding caches etc but had to roll back to 3974... 1 Link to comment Share on other sites More sharing options...
liujianwei Posted January 29, 2017 Share Posted January 29, 2017 In new 10.12.4 beta Radeon HD 5570 shows flicker. I restored the kext graphics of 12.3 but the situation is the same: hd works but bad for exactly the same way. No idea where the problem may reside for a card whose id is still present in AMDLegacySupport.kext? Sorry for the English and thank you. same here 1 Link to comment Share on other sites More sharing options...
erice Posted January 29, 2017 Share Posted January 29, 2017 In new 10.12.4 beta Radeon HD 5570 shows flicker. Corrections of the personalities of the Ati card, different energy management to the graphics card, different id? Clover can possibly help? Thanks. 1 Link to comment Share on other sites More sharing options...
Laavuska Posted January 29, 2017 Share Posted January 29, 2017 For me the latest version(3994) kept giving CMOS error after I restarted my computer so I had to revert to 3974. Sierra 10.12.3 and a legacy system here. 1 Link to comment Share on other sites More sharing options...
bronxteck Posted January 29, 2017 Share Posted January 29, 2017 what edk version did you build 3994 with. Link to comment Share on other sites More sharing options...
Slice Posted January 30, 2017 Share Posted January 30, 2017 In new 10.12.4 beta Radeon HD 5570 shows flicker. Corrections of the personalities of the Ati card, different energy management to the graphics card, different id? Clover can possibly help? Thanks. Same with 6670. Link to comment Share on other sites More sharing options...
Sherlocks Posted January 30, 2017 Share Posted January 30, 2017 Tried r3994 on my X58 system but it killed Audio.Nothing showed up in system prefs but was present system report/audio.Tried rebuilding caches etc but had to roll back to 3974... try this. and please report thank you r3994 fix.zip 1 Link to comment Share on other sites More sharing options...
pkdesign Posted January 30, 2017 Share Posted January 30, 2017 Same here, v3994 killed my audio using the following patches with a realtekALC kext: <dict> <key>Comment</key> <string>t1-110.9-10.11-AppleHDA/Realtek ALC885 (Optional)</string> <key>Disabled</key> <false/> <key>Find</key> <data>ixnUEQ==</data> <key>Name</key> <string>AppleHDA</string> <key>Replace</key> <data>hQjsEA==</data> </dict> <dict> <key>Comment</key> <string>t1-AppleHDA/Resources/xml>zml</string> <key>Disabled</key> <false/> <key>Find</key> <data>eG1sLnps</data> <key>Name</key> <string>AppleHDA</string> <key>Replace</key> <data>em1sLnps</data> </dict> When I reverted back to v3974 all was okay. Link to comment Share on other sites More sharing options...
mhaeuser Posted January 30, 2017 Share Posted January 30, 2017 I just saw this in the latest AptioFix src in Lib.c: if ((Desc->PhysicalStart < 0xa0000) && (PhysicalEnd >= 0x9e000)) What is this supposed to do? Want to check for a Memory region that is fit in 0x9e000 - 0xa0000? If so, wouldn't it rather need to be this? if ((Desc->PhysicalStart >= 0x9e000) && (PhysicalEnd <= 0xa0000)) Link to comment Share on other sites More sharing options...
nekonoko Posted January 30, 2017 Share Posted January 30, 2017 For me the latest version(3994) kept giving CMOS error after I restarted my computer so I had to revert to 3974. Sierra 10.12.3 and a legacy system here. Yep, I'm having the same issue with 10.12.3 and legacy system. Link to comment Share on other sites More sharing options...
Sherlocks Posted January 31, 2017 Share Posted January 31, 2017 Yep, I'm having the same issue with 10.12.3 and legacy system. http://www.insanelymac.com/forum/index.php?/topic/284656-Clover-General-discussion&do=findComment&comment=2359605 Please test. 나의 LG-F410S 의 Tapatalk에서 보냄 Same here, v3994 killed my audio using the following patches with a realtekALC kext: <dict> <key>Comment</key> <string>t1-110.9-10.11-AppleHDA/Realtek ALC885 (Optional)</string> <key>Disabled</key> <false/> <key>Find</key> <data>ixnUEQ==</data> <key>Name</key> <string>AppleHDA</string> <key>Replace</key> <data>hQjsEA==</data> </dict> <dict> <key>Comment</key> <string>t1-AppleHDA/Resources/xml>zml</string> <key>Disabled</key> <false/> <key>Find</key> <data>eG1sLnps</data> <key>Name</key> <string>AppleHDA</string> <key>Replace</key> <data>em1sLnps</data> </dict> When I reverted back to v3974 all was okay. http://www.insanelymac.com/forum/index.php?/topic/284656-Clover-General-discussion&do=findComment&comment=2359605 Test please. Now, some patches are not working(KextToPatch). I already reported before. Still not resolve issue. If you give us report, we can solve Thank you 나의 LG-F410S 의 Tapatalk에서 보냄 Link to comment Share on other sites More sharing options...
Slice Posted January 31, 2017 Share Posted January 31, 2017 I just saw this in the latest AptioFix src in Lib.c: if ((Desc->PhysicalStart < 0xa0000) && (PhysicalEnd >= 0x9e000)) What is this supposed to do? Want to check for a Memory region that is fit in 0x9e000 - 0xa0000? If so, wouldn't it rather need to be this? if ((Desc->PhysicalStart >= 0x9e000) && (PhysicalEnd <= 0xa0000)) No. Range [0x80000, 0x9f000] satisfies first condition but not second. Link to comment Share on other sites More sharing options...
Recommended Posts