foskvs Posted December 9, 2017 Share Posted December 9, 2017 The GPU is recognized anyway without lilu.kext ... why? Is Whatevergreen.kext loaded? BTW, AMD HD6000 series should work OOB. Link to comment Share on other sites More sharing options...
EdoardoConti Posted December 9, 2017 Author Share Posted December 9, 2017 Is Whatevergreen.kext loaded? Nope. BTW, AMD HD6000 series should work OOB. You are right but when I added this GPU ( macOS 10.13.1 ) it makes trouble without lilu.kext , so I installed it. Should I have to remove lilu.kext and his bootflag? Link to comment Share on other sites More sharing options...
foskvs Posted December 9, 2017 Share Posted December 9, 2017 You are right but when I added this GPU ( macOS 10.13.1 ) it makes trouble without lilu.kext , so I installed it. Should I have to remove lilu.kext and his bootflag? WhateverGreen.kext on 6000 and 7000 series is used only to fix sleep problems. If you don't have them, remove it. Link to comment Share on other sites More sharing options...
EdoardoConti Posted December 9, 2017 Author Share Posted December 9, 2017 I replaced Lilu.kext here /Library/Extension and I rebuilded the kextcache. Booting time slightly slower than before the update... I should have solved almost all my problems. 1 Link to comment Share on other sites More sharing options...
foskvs Posted December 9, 2017 Share Posted December 9, 2017 I replaced Lilu.kext here /Library/Extension and I rebuilded the kextcache. Booting time slightly slower than before the update... I should have solved almost all my problems. Lilu and its plugins should always be placed in EFI. Link to comment Share on other sites More sharing options...
EdoardoConti Posted December 9, 2017 Author Share Posted December 9, 2017 Lilu and its plugins should always be placed in EFI. Why? My E/C/kexts/Other : My Library/Extensions : Do I have to move some kexts in the right place ? Link to comment Share on other sites More sharing options...
foskvs Posted December 9, 2017 Share Posted December 9, 2017 Why? According to vit9696 (developer of Lilu), they need to be loaded with high priority. IMHO, you should place "hack related" kexts in EFI. Remove duplicated kexts. Link to comment Share on other sites More sharing options...
EdoardoConti Posted December 9, 2017 Author Share Posted December 9, 2017 According to vit9696 (developer of Lilu), they need to be loaded with high priority. IMHO, you should place "hack related" kexts in EFI. Remove duplicated kexts. lilu.kext moved to EFI . Should IntelMausiEthernet.kext be located in EFI? Now audio not working, AppleALC.kext in EFI. Source visible in preferences but no sound... Tried audio_cloverALC-130_v0.3 with no success. Link to comment Share on other sites More sharing options...
foskvs Posted December 9, 2017 Share Posted December 9, 2017 Should IntelMausiEthernet.kext be located in EFI? In my opinion, S/L/E and L/E should be as "vanilla" as possible. Many other users think that kexts should be loaded into kernel cache (then placed in L/E or S/L/E) like on real macs. So... do as you want Drag Hack_Info into terminal and add -sp flag. Attach the file generated. Hack_Info.zip Link to comment Share on other sites More sharing options...
EdoardoConti Posted December 9, 2017 Author Share Posted December 9, 2017 In my opinion, S/L/E and L/E should be as "vanilla" as possible. Many other users think that kexts should be loaded into kernel cache (then placed in L/E or S/L/E) like on real macs. So... do as you want Drag Hack_Info into terminal and add -sp flag. Attach the file generated. HackInfo_Report.zip Link to comment Share on other sites More sharing options...
foskvs Posted December 9, 2017 Share Posted December 9, 2017 To get audio working with AppleALC, AppleHDA.kext must be original. You AppleHDA is patched. Link to comment Share on other sites More sharing options...
EdoardoConti Posted December 9, 2017 Author Share Posted December 9, 2017 To get audio working with AppleALC, AppleHDA.kext must be original. You AppleHDA is patched. So, do I have to remove current AppleHDA.kext from EFI and put the original v. into L/E ? Where I get a "vanilla" one? Link to comment Share on other sites More sharing options...
foskvs Posted December 9, 2017 Share Posted December 9, 2017 So, do I have to remove current AppleHDA.kext from EFI and put the original v. into L/E ? "vanilla" kexts should be placed in S/L/E. Where I get a "vanilla" one? Reinstall macOS without erasing the disk. The installer will rewrite system kexts. 1 Link to comment Share on other sites More sharing options...
EdoardoConti Posted December 9, 2017 Author Share Posted December 9, 2017 "vanilla" kexts should be placed in S/L/E. Reinstall macOS without erasing the disk. The installer will rewrite system kexts. Can I do it in recovery mode? I've never done it before... Link to comment Share on other sites More sharing options...
foskvs Posted December 9, 2017 Share Posted December 9, 2017 Can I do it in recovery mode? I've never done it before... Surely. Keep in mind that Recovery HD uses only "vanilla" kext (different S/L/E than "normal" macOS). You need necessary kexts in EFI. Link to comment Share on other sites More sharing options...
EdoardoConti Posted December 9, 2017 Author Share Posted December 9, 2017 Surely. Keep in mind that Recovery HD uses only "vanilla" kext (different S/L/E than "normal" macOS). You need necessary kexts in EFI. So I'm not going to erase document, apps and other files right? Link to comment Share on other sites More sharing options...
foskvs Posted December 9, 2017 Share Posted December 9, 2017 So I'm not going to erase document, apps and other files right? Exactly. Don't erase the disk (or partition) with disk utility. The installer will overwrite the current installation. Link to comment Share on other sites More sharing options...
EdoardoConti Posted December 9, 2017 Author Share Posted December 9, 2017 Exactly. Don't erase the disk (or partition) with disk utility. The installer will overwrite the current installation. After I've to re-install Clover or it won't be affected? Link to comment Share on other sites More sharing options...
foskvs Posted December 9, 2017 Share Posted December 9, 2017 After I've to re-install Clover or it won't be affected? Nope. It won't touch ESP. Link to comment Share on other sites More sharing options...
EdoardoConti Posted December 10, 2017 Author Share Posted December 10, 2017 Finally I installed macOS from recovery HD and now I get sound working. But now there’s a new problem... Hackintosh often freeze because of 100% usage of the SSD ( Samsung 850 EVO ) also without a real high workload... it’s very frustrating. What’s the matter? Inviato dal mio iPhone utilizzando Tapatalk Link to comment Share on other sites More sharing options...
foskvs Posted December 10, 2017 Share Posted December 10, 2017 According to the report from post #35, you have installed HS on APFS partition with TRIM enabled. Try to disable TRIM. 1 Link to comment Share on other sites More sharing options...
EdoardoConti Posted December 10, 2017 Author Share Posted December 10, 2017 I disabled TRIM successfully. sudo trimforce disable But on the system report I get TRIM support: Yes . Does it means that the SSD supports TRIM? How can I detect if it's enabled or not? Link to comment Share on other sites More sharing options...
foskvs Posted December 10, 2017 Share Posted December 10, 2017 Do you have any patch on config.plist about TRIM? (Kernel and Kext Patch section) Link to comment Share on other sites More sharing options...
EdoardoConti Posted December 10, 2017 Author Share Posted December 10, 2017 Do you have any patch on config.plist about TRIM? (Kernel and Kext Patch section) Yes. TRIM support removed by deleting IOAHCIBlockStorage. Link to comment Share on other sites More sharing options...
foskvs Posted December 10, 2017 Share Posted December 10, 2017 Do you have the same problems with the SSD? Link to comment Share on other sites More sharing options...
Recommended Posts