iCanaro Posted October 30, 2020 Share Posted October 30, 2020 (edited) there is still a very strange bug I performed a clean installation on the SSD of the Z68 of BigSur 11.0.1 everything IS OK. After installation and performed a couple of restarts, I saved the SystemVersion present in the BS preboot, then I started high sierra, all regular, but on restart in the GUI I found myself high sierra icon in the BigSur Startup Preboot Here's why you're backing up your systemversion earlier started with OC BS and arranged NB: this BUG occurs only and only at the first start of high sierra when you have a new installation/update of BigSur; after you can start higt sierra and bigsur how many times do you want nothing abnormal to happen. if you need I also saved the Preboot very strange this thing, I understand that there will not be many users who use so many macOS at the same time, but since I happened this thing on 3 hacks (Z370, X570, Z68) Z68_5126 (master, commit 9e7b4311c) _HS_change_SystemVersion_Preboot_BSdebug.log.zip Spoiler PS: other very strange thing, the preboot of Catalina Spoiler Edited October 30, 2020 by iCanaro 1 Link to comment Share on other sites More sharing options...
PG7 Posted October 30, 2020 Share Posted October 30, 2020 good afternoon / night Jieff and Slice after the r5120 version the way to activate the Nvidia Legacy video cards that was working until the r5119 simply stopped activating my GT 320M laptop I tested it from version r5120 to r5126 and the problem continues! with the r5119 active the inject nvidia and it works correctly with the other most recent versions I activate it and at boot time where it should activate the intel it just stays with the black screen without accessing the light I leave debug one where it works with the r5119 another does NOT work with the r5126 thanks for everything Google Translate ! HP DV6 2140EF i5-M430 Nvidia GeForce GT 320M High Sierra Catalina = "Patch Chris1111 Merci Nvidia legacy" No Arrandale ! No IGPU Intel ! Boot legacy inject Nvidia r5119 ok debug.log Boot legacy inject Nvidia r5126 probleme ecran noire debug.log 1 Link to comment Share on other sites More sharing options...
PG7 Posted October 30, 2020 Share Posted October 30, 2020 Ola boot test test with version r5125 version r5126 boot legacy! HP DV6 1340SF intel core2duo P7450 Ati Radeon HD4650 *Don't Arrandale! *No IGPU intel test El Capitan Sierra High Sierra Mojave Catalina BigSur beta 10 I can activate this ATI HD4650 up to Catalina with the Dosdude1 legacy AMD patch (thanks to everyone who works for these patches) Boot with ATI inject + Fake ID 0x94881002 + FB Name = Null + Load VBios + "EDID" (Not required) + FixDisplay Spoiler 1 Link to comment Share on other sites More sharing options...
maclinuxG4 Posted October 30, 2020 Share Posted October 30, 2020 1 hour ago, PG7 said: High Sierra Catalina = "Patch Chris1111 Merci Nvidia legacy" No Arrandale ! No IGPU Intel ! Boot legacy inject Nvidia r5119 ok debug.log Boot legacy inject Nvidia r5126 probleme ecran noire debug.log oups.... any test before on mac os high sierra with nvidia CG ? Link to comment Share on other sites More sharing options...
PG7 Posted October 30, 2020 Share Posted October 30, 2020 3 minutes ago, maclinuxG4 said: oups.... any test before on mac os high sierra with nvidia CG ? all tests have already been done! now passes my knowledge .... 7 minutes ago, maclinuxG4 said: oups.... any test before on mac os high sierra with nvidia CG ? Spoiler Link to comment Share on other sites More sharing options...
D-an-W Posted October 30, 2020 Share Posted October 30, 2020 Apologies for the slightly off topic but your a clever bunch in here! Does anyone know if it's ok / safe to remove this Update partition and if so what's the best way to do it? Spoiler Link to comment Share on other sites More sharing options...
MacKonsti Posted October 30, 2020 Share Posted October 30, 2020 (edited) Hi @Jief_Machak hope you are well. I ran CloverConfigPlistValidator06 on the config-sample.plist found in the latest Clover releases, and got these errors, can I bother you to check them please and potentially fix your great validator tool? Error: Expecting <true/> <false/> or <string> tag containing true, false, yes or no tag '/Devices/DisableFunctions:344' Error: Expecting <true/> <false/> or <string> tag containing true, false, yes or no tag '/Devices/IntelMaxValue:369' Warning: Unknown key '/Graphics/Connectors:729'. Skipped. Warning: Unknown key '/KernelAndKextPatches/KextsToPatch[6]/FindMask:1070'. Skipped. Warning: Unknown key '/RtVariables/Block[0]/UUID:1100'. Skipped. Warning: Unknown key '/Quirks/DisableRtcChecksum:1264'. Skipped. The structure for the errors comes from Devices section, not sure if DisableFunctions and IntelMaxValue are allowed values? They are certainly rarely used (to my experience all this time): <key>Devices</key> <dict> [...] <key>DisableFunctions</key> <string>0x18F6</string> [...] <key>ForceHPET</key> <false/> <key>HDMIInjection</key> <false/> <key>IntelMaxValue</key> <string>0x710</string> [...] Thank you! Edited October 30, 2020 by MacKonsti Link to comment Share on other sites More sharing options...
STLVNUB Posted October 31, 2020 Share Posted October 31, 2020 (edited) Don't know what you've done to the latest release but it flies on my rig edit: after several reboot,It now comes out with prohibition and won't boot Edited October 31, 2020 by STLVNUB 3 Link to comment Share on other sites More sharing options...
PG7 Posted October 31, 2020 Share Posted October 31, 2020 Hello tests with the Clover r5126 with Quircks ASUS A42j intel i5-480M Mobility Radeon 5730 2Go 8Go ram Atheros ar9285 HDD does not have IGPU arrandale! video card can be active correctly up to the High Sierra, in Mojave and Catalina even with the AMD Legacy patch from Dosdude1 activates the correct resolution and even works well even on youtube when reading videos but not with the transparent Dock ....! to activate this card in Clover FixDisplay + EDID + LoadVBios + FB Name = Null + DualLink = 0 + ATI inject Thank you team! Google translate ! Spoiler Link to comment Share on other sites More sharing options...
maclinuxG4 Posted October 31, 2020 Share Posted October 31, 2020 (edited) on mac os sierra, with the last release r5126, I get a KP then halt I restart then ok. (KP with a kext......) there is a something to understand, during phase loaded kext may be unsuccessful Edited October 31, 2020 by maclinuxG4 Link to comment Share on other sites More sharing options...
LockDown Posted October 31, 2020 Share Posted October 31, 2020 Hi Does ForceHPET still have use on newer clover or it has been marked as deprecated? Link to comment Share on other sites More sharing options...
Slice Posted October 31, 2020 Share Posted October 31, 2020 25 minutes ago, ellaosx said: Hi Does ForceHPET still have use on newer clover or it has been marked as deprecated? Not deprecated. But usage depends on hardware if it allow this or not. 1 Link to comment Share on other sites More sharing options...
SavageAUS Posted October 31, 2020 Share Posted October 31, 2020 10 hours ago, D-an-W said: Apologies for the slightly off topic but your a clever bunch in here! Does anyone know if it's ok / safe to remove this Update partition and if so what's the best way to do it? Hide contents +1 bugs me to see it in Catalina. 1 Link to comment Share on other sites More sharing options...
Cyberdevs Posted October 31, 2020 Share Posted October 31, 2020 12 hours ago, D-an-W said: Apologies for the slightly off topic but your a clever bunch in here! Does anyone know if it's ok / safe to remove this Update partition and if so what's the best way to do it? Spoiler Just select the Update volume and remove it by clicking the - button 2 Link to comment Share on other sites More sharing options...
D-an-W Posted October 31, 2020 Share Posted October 31, 2020 4 minutes ago, Cyberdevs said: Reveal hidden contents Just select the Update volume and remove it by clicking the - button Thanks, wasn't sure if thats the best way and if it would impact anything else? Link to comment Share on other sites More sharing options...
Slice Posted October 31, 2020 Share Posted October 31, 2020 @all How do you think will it be useful to implement injecting Device->Properties depending on macOS version? Up for now there is no MatchOS setting. 1 2 Link to comment Share on other sites More sharing options...
Cyberdevs Posted October 31, 2020 Share Posted October 31, 2020 21 minutes ago, D-an-W said: Thanks, wasn't sure if thats the best way and if it would impact anything else? AFIAK it doesn't affect anything. I removed it on Big Sur and I didn't have an issue so far 2 Link to comment Share on other sites More sharing options...
Denisuu Posted October 31, 2020 Share Posted October 31, 2020 21 hours ago, kushwavez said: You should use only BrcmBluetoothInjector, BrcmFirmwareData and BrcmPatchRAM3 if they're in Clover/kexts. BrcmFirmwareRepo is only for L/E. Also I can't really see the texts correctly but for me it saying "Still waiting for root device" That means the system can't see your internal drives. Here I made you a new EFI. Deleted unused kexts: - CpuTscSync.kext (I think it's do nothing for you) - HWPEnabler.kext (not needed) - BrcmFirmwareRepo.kext (wrong, replaced with BrcmFirmwareData.kext) - BrcmNonPatchRAM2.kext (wrong, use BrcmPatchRAM3 only) Added new ones, also added CtlnaAHCIPort.kext for your internal drives, not sure if it's needed or not, I did that because you had "Still waiting for root device" error which is most likely because of an unsupported chipset and your drives aren't recognised. Clover is now v5126 so CLOVERX64.efi is replaced with the new one your config.plist have lot's of unused variables or unnecessary changes, so I modified mine instead, but the old one is also included (config_old.plist) - In your "new" config.plist in ACPI/DSDT/Patches you have two EC renames (EC0 to EC and ECDV to EC) you should figure out which one do you need, and delete the unnecessary ones. - Your SMBIOS is wrong. According to your signature it's a 7700HQ, exactly the same as MacBookPro14,3 so I changed that. - Boot args deleted: dart=0 (not needed), nv_disable=1 (you already disabled it by SSDT), -shikioff (idk why), gfxrst=1 I did not remove -disablegfxfirmware but I think it's not necessary, try to remove and boot. Replaced your drivers with the new one. You also had SMCHelper (for FakeSMC) and VirtualSMC.efi, you should use jsut one. In your case it's VirtualSMC.efi. I had to delete FlashProgrammingTool.efi, FWUpdLcl.efi, MEInfo.efi, MEManuf.efi, ACPI/origin, and themes/minimal because of the zip size is too big to upload because of them, if you want to use them you have to readd them. Take a look EDIT: if you have DSDT errors pls change ACPI/DSDT/Name from "BIOS.aml" to "DSDT.aml" I forgot that. N580VD Clover r5126.zip Wow, thanks for the effort man!!! Yea I knew it would be a big mess, it's was my first Hackintosh machine so I didn't know what I was doing at all. After re-adding CpuTscSync.kext and changing BIOS.aml to DSDT.aml my system booted. I'm not sure why but from BIOS update 317 I needed VoodooTSCSync.kext or CpuTscSync.kext. The system still boots after removing 'CtlnaAHCIPort.kext' and -disablegfxfirmware It looks like there is no ECDV in my DSDT so I removed the 'ECDV to EC' patch from 'ACPI/DSDT/Patches' Sound, full shutdown and sleep aren't working anymore though. I thought it was because the device properties weren't added but it doesn't change anything. I went through all tabs and tried to change all parameters like they were in my old config.plist, that doesn't help either. I would think if I just removed these and injected layout 21 it would work, but it doesn't. Link to comment Share on other sites More sharing options...
Guest Posted October 31, 2020 Share Posted October 31, 2020 (edited) 2 hours ago, Slice said: @all How do you think will it be useful to implement injecting Device->Properties depending on macOS version? Up for now there is no MatchOS setting. Yes for sure but I think MatchOS could be more solid in its working. have you read on GitHub issue I have opened? and it is not a platform problem it seems more deeper to debug Edited October 31, 2020 by Guest Link to comment Share on other sites More sharing options...
kushwavez Posted October 31, 2020 Share Posted October 31, 2020 14 minutes ago, Denisuu said: Wow, thanks for the effort man!!! Yea I knew it would be a big mess, it's was my first Hackintosh machine so I didn't know what I was doing at all. After re-adding CpuTscSync.kext and changing BIOS.aml to DSDT.aml my system booted. I'm not sure why but from BIOS update 317 I needed VoodooTSCSync.kext or CpuTscSync.kext. The system still boots after removing 'CtlnaAHCIPort.kext' and -disablegfxfirmware It looks like there is no ECDV in my DSDT so I removed the 'ECDV to EC' patch from 'ACPI/DSDT/Patches' Sound, full shutdown and sleep aren't working anymore though. I thought it was because the device properties weren't added but it doesn't change anything. I went through all tabs and tried to change all parameters like they were in my old config.plist, that doesn't help either. I would think if I just removed these and injected layout 21 it would work, but it doesn't. For sleep try removing darkwake=0 bootflag and disable Power Nap. For audio I need to know your audio chip. If it's ALC298 you should try these audio layout-ids: 3, 11, 13, 21, 22, 28, 29, 30, 32, 47, 66, 72, 99. Try with 3 first. I suggest you to remove from Properties/Devices, and use just with. alcid=xx bootflag. Then if you got the working one use config.plist/Devices/Audio/Inject=xx Also make sure you are using the native AppleHDA, not a patched one. And Only AppleALC.kext. 1 Link to comment Share on other sites More sharing options...
Denisuu Posted October 31, 2020 Share Posted October 31, 2020 (edited) 20 minutes ago, kushwavez said: For sleep try removing darkwake=0 bootflag and disable Power Nap. For audio I need to know your audio chip. If it's ALC298 you should try these audio layout-ids: 3, 11, 13, 21, 22, 28, 29, 30, 32, 47, 66, 72, 99. Try with 3 first. I suggest you to remove from Properties/Devices, and use just with. alcid=xx bootflag. Then if you got the working one use config.plist/Devices/Audio/Inject=xx Also make sure you are using the native AppleHDA, not a patched one. And Only AppleALC.kext. My chip is Conexant Audio CX8150 so it should be 21 or 22 according to the AppleALC Wiki: https://github.com/acidanthera/AppleALC/wiki/Supported-codecs I'll try to fix sleep first. Edited October 31, 2020 by Denisuu Link to comment Share on other sites More sharing options...
kushwavez Posted October 31, 2020 Share Posted October 31, 2020 (edited) @Denisuu Oh I see. It's Conexant CX8150. Well then You need to add 2 KextToPatch too: Add Properties: and at Devices/Properties add layout-id just like you did. (OR) just start with alcid=21 (or Devices/Auido/Inject=21) to see if it's working or not. Edited October 31, 2020 by kushwavez 2 Link to comment Share on other sites More sharing options...
Matgen84 Posted October 31, 2020 Share Posted October 31, 2020 2 hours ago, Slice said: @all How do you think will it be useful to implement injecting Device->Properties depending on macOS version? Up for now there is no MatchOS setting. @Slice I don't understand the interest of matchOS settings in Devices/Proprieties. Personally, I have only one macOS version by Hack I think: this new feature could remain optional, and used only by those who need it. Link to comment Share on other sites More sharing options...
Denisuu Posted October 31, 2020 Share Posted October 31, 2020 (edited) 1 hour ago, kushwavez said: @Denisuu Oh I see. It's Conexant CX8150. Well then You need to add 2 KextToPatch too: Add Properties: and at Devices/Properties add layout-id just like you did. (OR) just start with alcid=21 (or Devices/Auido/Inject=21) to see if it's working or not. I already re-added those, it doesn't work though. Now the strange thing is if I go back to my old EFI sound isn't working either... I don't understand how it can stop working al of a sudden, it always worked. The alcid=21 and/or Devices/Audio/Inject=21 also don't do anything... The kext is being loaded though. I tried installing it to L/E too but nothing seems to work. Also removing darkwake and disabling powernap doesn't solve sleep. This is the reason I moved back from OpenCore to Clover because it was impossible to get sleep to work. It works perfectly on 5122, so maybe it has something to do with the quirks or OpenRuntime.efi? Edited October 31, 2020 by Denisuu Link to comment Share on other sites More sharing options...
MacKonsti Posted October 31, 2020 Share Posted October 31, 2020 3 hours ago, Slice said: @all How do you think will it be useful to implement injecting Device->Properties depending on macOS version? Up for now there is no MatchOS setting. Hi @Slice thanks for your contributions even if I am still holding on Catalina and don't dare to test BugSur I would suggest the same type of tag as found for kext patches e.g. the SSD one. 10.16 for all versions (or 10.16.x) and 10.16.1 for that particular minor version i.e. release dot major dot minor: <key>MatchOS</key> <string>10.15.x</string> This is clearer to understand, visually, in Config too. And depends if you can do mixing as well, like <string>10.12,10.13</string> Thanks. Do you consider a universal value for all OS? I saw in sample Config: <key>MatchOS</key> <string>All</string> But not sure if it's valid for all expected value and places, nor which Clover forward this is implemented. Cheers Link to comment Share on other sites More sharing options...
Recommended Posts