Jump to content
Welcome to InsanelyMac.com - No more ads! And some exciting news... Read more... ×

kushwavez

Members
  • Content Count

    198
  • Joined

  • Last visited

About kushwavez

  • Rank
    InsanelyMac Geek

Contact Methods

  • Skype
    ogbratyo.cj

Profile Information

  • Gender
    Male
  • Location
    Hungary

Recent Profile Visitors

1,834 profile views
  1. kushwavez

    Clover General discussion

    Working fine on notebook 1, minor thing: Keyboard settings, Display settings are resetted with this update, I had to re-login to iCloud even though I didn't change SMBIOS. At devices it's duplicated, I had two devices with same SMBIOS.
  2. kushwavez

    Clover General discussion

    You're the best! Is it possible to include your "AppleKeyFeeder.efi" and "AppleUiSupport.efi" in further releases?
  3. kushwavez

    Clover General discussion

    So after some more testing I figured out my PS2 built-in kb doesn't work with AppleUiSupport.efi (because of the built-in AppleKeyAggregator?), so I can't input my password. If I add the separate AppleKeyAggregator.efi the error msg appears as mentioned above, no PS2 kb. I've had to add your "AppleKeyFeeder.efi" to get it working, now with that it's finally okay.
  4. kushwavez

    Clover General discussion

    Thanks @Slice, @Jief_Machak! You're right, I deleted all of the FileVault drivers, put just AppleUiSupport.efi in and it worked fine. That's also explains the red error msg, AppleUiSupport simply initialized AppleKeyAggregator first. Also I found a source if it helps: https://github.com/acidanthera/AppleSupportPkg/releases/tag/2.0.9
  5. kushwavez

    Clover General discussion

    @Jief_Machak Yes I only deleted that file then tried. But thanks! Deleting "AppleImageCodec.efi" and adding "AppleUiSupport.efi" fixed my problem, booted in a flash. But I needed to grab this .efi from elsewhere, it's not in the Clover.zip However now a red Error msg appears before the Clover GUI says: "Error: Device Error returned from AppleKeyAggregator.efi". Doesn't seems to affect anything tho. And yes, DataHubDxe.efi and FSInject.efi are not needed in my case. They were just there by default and I didn't delete them. Maybe it's a good idea to replace "AppleImageCodec.efi" with "AppleUiSupport.efi" and move DataHubDxe and FSInject to drivers/off in further releases [...] 0:106 0:000 === [ LoadDrivers ] ============================= 0:107 0:000 Loading AppleUiSupport.efi status=Success 0:210 0:103 Loading AppleKeyAggregator.efi status=Success 0:213 0:002 Fatal Error: Device Error returned from AppleKeyAggregator.efi [...] EDIT: after more testing seems like there is no need to delete "AppleImageCodec.efi" only need to add "AppleUiSupport.efi" to get it working. debug_fvault_appleuisupport_working.log
  6. kushwavez

    Clover General discussion

    @Jief_Machak thanks I deleted that, but now it won't start at all. debug log says: ... 8:005 0:001 OCOS: Should use black background 8:013 0:007 OC: Opening file System\Library\Kernels\kernel with 1 mode gave - Not Found 8:013 0:000 OC: Opening file \A838CD58-89D9-41AC-913B-D444CC445D42 with 1 mode gave - Success 8:015 0:001 OC: Opening file \A838CD58-89D9-41AC-913B-D444CC445D42\System\Library\CoreServices\com.apple.Boot.plist with 1 mode gave - Not Found 8:117 0:102 OC: Opening file Library\Preferences\SystemConfiguration\com.apple.Boot.plist with 1 mode gave - Success 8:569 0:451 OC: Opening file \A838CD58-89D9-41AC-913B-D444CC445D42\System\Library\CoreServices\PlatformSupport.plist with 1 mode gave - Success 9:108 0:539 OC: Opening file System\Library\Caches\com.apple.corestorage\EncryptedRoot.plist.wipekey with 1 mode gave - Success 10:156 1:048 OC: Opening file A838CD58-89D9-41AC-913B-D444CC445D42\BaseSystem.dmg with 1 mode gave - Not Found 10:168 0:011 OC: Opening file A838CD58-89D9-41AC-913B-D444CC445D42\BaseSystem.dmg with 1 mode gave - Success 20:754 10:586 OCB: InternalEfiExit 65553218 - Aborted / Unsupported //Exiting in 10 seconds... EDIT: photo debug_v5126_fvault_woutimagecodec.log
  7. kushwavez

    Clover General discussion

    @Jief_Machak Quite while ago I posted something about FileVault not working. So I was wrong, it's working, but. Now I've had some time and tested again with an encrypted Big Sur drive, it boots to the password input screen but just after an enormously long wait time (2 min). And it's just to the password input, after that the system needs to boot to the desktop. Looking at the debug.log I see these lines, something is happening but I don't know why it is waiting for so long: ... 13:161 0:010 OC: Opening file System with 1 mode gave - Success 13:162 0:001 OC: Opening file Library with 1 mode gave - Success 13:163 0:000 OC: Opening file Caches with 1 mode gave - Success 13:164 0:001 OC: Opening file com.apple.corestorage with 1 mode gave - Success 13:165 0:000 OC: Opening file EFILoginLocalizations with 1 mode gave - Success 13:166 0:001 OC: Opening file loginui.efires with 1 mode gave - Success 142:608 129:442 OC: Opening file System with 1 mode gave - Success 142:610 0:001 OC: Opening file Library with 1 mode gave - Success 142:611 0:001 OC: Opening file Caches with 1 mode gave - Success 142:612 0:000 OC: Opening file com.apple.corestorage with 1 mode gave - Success 142:613 0:000 OC: Opening file EFILoginLocalizations with 1 mode gave - Success 142:614 0:000 OC: Opening file Lucida13White.efires with 1 mode gave - Success 142:954 0:340 OC: Opening file System with 1 mode gave - Success 142:955 0:001 OC: Opening file Library with 1 mode gave - Success 142:956 0:001 OC: Opening file Caches with 1 mode gave - Success 142:958 0:001 OC: Opening file com.apple.corestorage with 1 mode gave - Success 142:958 0:000 OC: Opening file EFILoginLocalizations with 1 mode gave - Success 142:959 0:001 OC: Opening file flag_picker.efires with 1 mode gave - Success 143:141 0:181 OC: Opening file System with 1 mode gave - Success 143:142 0:000 OC: Opening file Library with 1 mode gave - Success 143:143 0:000 OC: Opening file Caches with 1 mode gave - Success 143:144 0:000 OC: Opening file com.apple.corestorage with 1 mode gave - Success 143:145 0:001 OC: Opening file EFILoginLocalizations with 1 mode gave - Success 143:146 0:001 OC: Opening file battery.efires with 1 mode gave - Success 143:167 0:020 OCSMC: SmcReadValue Key 4242494E Size 1 //Then the login screen appeared //Input password //System is booting ... //Arrived at desktop As you can see, there is something at line "142:608 129:442 OC: Opening file System with 1 mode gave - Success" Why is there a huge delay? drivers are in place from off/UEFI/FileVault Here, a full debug.log debug_v5126_filevault.log
  8. kushwavez

    Clover General discussion

    @PG7 Yep, sounds about right. Unfortunately as I can see it's only connecting at 20Mhz mode on 5 GHz too, so that's why it's so slow. I hope they'll improve this soon.
  9. kushwavez

    Clover General discussion

    I just tried itlwm with an Intel AC-7260 to see if it's improved or not, it's good for light browsing, but nothing else really at this state. I barely hit 7 MB/s speed on 5 GHz, that normally would be like ~80 MB/s. I also had some very annoying bug when using it with OpenCore, after booting to Windows the wifi cannot be launched and used (error code: 10). Even a CMOS reset couldn't help! The only way to get it working again was to boot with Clover (or delete OC and boot with Windows loader)...strange! I opened a bug report but they said it's a problem with OC. Well, nice work anyway, not gonna lie.
  10. On some OS versions it's working without agdpmod=pikera bootflag, but not on other. It's better to just leave that in boot-args, no problems with that.
  11. Oh I see. I've never tried OCing when iGPU is enabled so that's good to know. This is unfortunate. Well, back to the question "Is it better to disable or not", depends on your use-case. Do you need CPU horse power more for your applications? If yes, then go for the OC and disabled iGPU. If your use-case is more GPU demanding than CPU, then go for iGPU and dGPU. Experiment it.
  12. @albertoacj I think headless mode is a good choice because then iGPU QuickSync will be enabled for light encoding tasks (for example QuickTime Screen recording is really good on QuickSync, while the quality is quite bad on AMD), and the RX 5700 will be used for heavy tasks (3D applications, render applications, Safari VP9 decoding, etc.). Is better have a good overclock and disable igpu or just make quick sync and dgpu with low frequency ? I don't understand this. Overclock the GPU? If my knowledge is good enough you can't really OverClock your GPU on macOS. Anyway I did overclock my GPU on Windows but I've had little to no differences, so I just went with the factory default. It performs well enough I changed my order to an RX 5700, this hackintosh is flawless, it's deserve it. Yes, it's a really solid hackintosh, the card is also working well, I really like it.
  13. kushwavez

    [Pre-Release] macOS Big Sur 11.1

    Could someone test if the RAM usage problem still exists on Beta 11.1 or not in Safari? Here, a video of it. I could reproduce this even on real Macs, issue has been reported to Apple. https://drive.google.com/file/d/1GPrsdu2z9szGwJKLezEkdQsBu9ivYJB-/view?usp=sharing 1. Open a preferably 1080p video (from any site except YouTube, it’s not working on every site) 2. Open a new tab, with any site (doesn’t matter, for example apple.com) 3. Start the video, watch the RAM usage of “kernel_task”. As you can see it’s normal. 3. Now pause the video and go to the other opened tab 4. Go back to the video and unpause it 5. Watch the RAM usage, it’s going really high, taking up all of the RAM (2x8 GB DDR4 2133 MHz), swap too. 6. It’s going back to normal after a reload. System becomes unresponsive, have to quit and reopen the site. On an original iMac, Safari says “This webpage is using significant memory.” Then it force-reloading every time.
  14. @Alesss Boot only from Preboot after the first restart. (I think there is two Preboot entry after the first restart, pick "Boot Install Mac OS X from Preboot" until it disappears
×