Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 10/20/2018 in Posts

  1. Rev 4716 new way for reset native NVRAM in GUI by Sherlocks. thanks to vit9696. - it's perfectly same process by vit9696's CleanNvram.efi. now we can't properly delete NVRAM variables in Mojave. so if you want to clean NVRAM, press F11 in GUI. - caution! your bootorder also will be deleted(it means that bootorder initialized) if you have a dual boot(macos and windows). it's different according to user system Rev 4717 prevent clover boot options from being deleted when NVRAM is reset
    8 points
  2. I'm back to the scene since today (16/10/2018). I've bought myself a new MacBookAir7,2. Will continue to develop for the hackintosh community. I've started by uploading under the Developers Corner a new version of AutoAPBDecrypt 2.0. CommonCrypto is altered to not allow decryption of Apple Protected Binaries. Solved this using an Apple updated version of OpenSSL 1.0.1j (included in the installer package). I can report that I'm very pleased to be back.
    6 points
  3. Like the title says, my screen behaves a little bit weird. I start the machine, all fans turn on and macOS boots with the loading bar. When it's at roughly 90%, my graphics card (Sapphire RX580 Nitro+) ramps the fans up for a second while simultaneously the screen goes white. Then the screen immediately returns back to the loading screen with the GPU fans going to 0 RPM at the exact same time. The short timeframe where the screen is white and the GPU at 100% fan RPM is merely a flicker, but it's not pleasing to look at every time, because it gives me the feeling "something's not right" I would really like to know if anyone had this issue before and how to fix it, if possible. Thank you in advance!
    1 point
  4. Hi, I'm translating all the old c and obj-c code to swift ...but require a lot of time.
    1 point
  5. System running now stable for over an hour on 10.13.6 on my AMD FX 8350. Seems that it had nothing to do with the kexts in my previous post. I have updated Clover to the latest version (4700) and deleted a busratio=20 flag that I was using in 10.13.3. That did the trick. thanks a lot Shaneee for this kernel!!!
    1 point
  6. beh allora dovresti aggiornare la firma
    1 point
  7. Io non vedo la 560 in firma Comunque, è compatibile.
    1 point
  8. it seems to me that the solution to your problem, I do not see the reason that you put links from other forums to go there to sign up with all due respect, but it is not correct
    1 point
  9. Gpu non supportata. Comunque senza vedere la EFI è difficile dire di più.
    1 point
  10. tutto dipende da nvidia possiamo solo aspettare
    1 point
  11. Forse sì, forse no. Al momento si sa poco.
    1 point
  12. I’m not using a freesync monitor no. Sent from my iPhone using Tapatalk
    1 point
  13. clearnvram.efi also freezes machine with a required manual power cycle. result are the same in nvram -p
    1 point
  14. Tested with r4717 Apple NVRAM was cleared, the boot variables were not. Thanks! nvram.zip
    1 point
  15. Yeah, same as @SavageAUS for r4717.. it cleared NVRAM properly, though Clover freeze immediately when pressing "F11" key. Boot Entries are still there (previous r4716 actually, not only changed bootloader entries order, but removed them #LoL).
    1 point
  16. OK, not a big issue for me since I have "Boot entry" options on my Aptio BIOS (firmware) and could be re-ordered easily.
    1 point
  17. try latest version r4717. cleannvram.efi has deleting the boot menu option. i added that disabled this option. i tested again. there is no problem. 나의 LG-F800S 의 Tapatalk에서 보냄
    1 point
  18. right. if you want, press f11 in gui in r4717. it's fixed. some users use virtualsmc. but there is previous fakesmc values in NVRAM. in mojave, it's hard to remove it. because nvram -c command is not working. so you usually use CleanNvram.efi. now in GUI, press f11, you easily remove NVRAM values. 나의 LG-F800S 의 Tapatalk에서 보냄
    1 point
  19. allora togliendo USBinjectall risolve il problema. ho rimosso anche xhci-300-series-injector è sembra funzionare tutto ugualmente quando seleziono la modalità stop il computer si spegne e per richiamarlo basta il tasto power del case. non ce modo di richiamarlo tramite mouse e tastiera bluetooth, ma a questo punto credi funzioni solo in questo modo per i lag del mouse bluetooth al rientro dalla modalità stop, per ora non si è verificato. lo monitorerò perché è un problema che si è presentato ad intermittenza in varie situazioni. levando il flag a kernel IPm invece l'avvio arriva alla schermata Clover, seleziono la partizione solita, e il sistema si riavvia. ho quindi rimesso la spunta non starei a toccare a questo punto i valori di darkwake, giusto? grazie
    1 point
  20. Another great Vega 64 PowerPlay Table for anyone to try out. Should be stable on most cards. Really low temperatures, no coil whine, great performance. Noticeably smoother UI performance due to higher base clocks. Voltage has been lowered significantly. Temps under load should not exceed 70°C and card stays silent. Fans will keep off during normal use. If they turn on they don't get very loud and turn off again after the card cooled down. PowerPlay Settings GPU Clocks: 1150 / 1200 / 1250 / 1300 / 1350 / 1400 / 1450 / 1500 GPU Voltage: 950 / 975 / 1000 / 1025 / 1050 / 1075 / 1100 / 1125 HBM2 Clock: 1045 HBM2 Voltage / Voltage Floor: 950 Min. Fan Speed: 100 (= Stop) Idle Fan Speed: 100 (= Stop) Target Fan Speed: 2600 Max. Fan Speed: 3000 Temperature Target: 55°C Power Target: 100% Use with Kext Injector See file attached. Use with own Kext Injector USE STOCK DRIVER SETTINGS + POWERPLAY TABLE! Don't use own settings like "PP_DisablePowerContaintment" and stuff like that. Refer to the original AMD10000Controller to check stock settings. tgIIAQBcAOEGAADuKwAAGwBIAAAAgKkDAPBJAgBkAAgA AAAAAAAAAAAAAAAAAAIBXABPAkYClACeAb4AKAF6AIwA vAEAAAAAcgIAAJAAqAJtAUMBlwHwSQIAcQICAgAAAAAA AAgAAAAAAAAABQAHAAMABQAAAAAAAAABCLYDzwPoAwEE GgQzBEwEZQQBAbYDAQGEAwAIYOoAAABAGQEAAYA4AQAC 3EoBAAOQXwEABAB3AQAFkJEBAAZssAEABwEIOMEBAAAA gAAAAAAAAMDUAQABAAAAAAAAAABI6AEAAgAAAAAAAAAA 0PsBAAMAAAAAAAAAAFgPAgAEAAAAAAAAAADgIgIABQAA AAABAAAAaDYCAAYAAAAAAQAAAPBJAgAHAAAAAAEAAAAA BWDqAAAAQBkBAACAOAEAANxKAQAAkF8BAAAACChuAAAA LMkAAAH4CwEAAoA4AQADkF8BAAT0kQEABdCwAQAGwNQB AAcACGw5AAAAJF4AAAH8hQAAAqy8AAADNNAAAARobgEA BQiXAQAG7KMBAAcAAWg8AQAAAQQ8QQAAAAAAUMMAAAAA AIA4AQACAAA0mAEABAAAAQgAmIUAAEC1AABg6gAAUMMA AAGAuwAAYOoAAJQLAQBQwwAAAgDhAACUCwEAQBkBAFDD AAADeP8AAEAZAQCIJgEAUMMAAARAGQEAgDgBAIA4AQBQ wwAABYA4AQDcSgEA3EoBAFDDAAAGAHcBAAB3AQCQXwEA UMMAAAeQkQEAkJEBAAB3AQBQwwAAARgAAAAAAAAAC+QS ZAAoCjcACgBUA5ABkAGQAZABkAGQAZABAAAAAAACAR4H 3ADcANwALAEAAFkAaQBKAEoAXwBzAHMAZABAAJCSl2CW AJBVAAAAAAAAAAAAAAAAAAAAAAACAtQwAAACEGDqAAAC EA== Use with Clover Device Properties B6020801 005C00E1 060000EE 2B00001B 00480000 0080A903 00F04902 00640008 00000000 00000000 00000000 00000201 5C004F02 46029400 9E01BE00 28017A00 8C00BC01 00000000 72020000 9000A802 6D014301 9701F049 02007102 02020000 00000000 08000000 00000000 05000700 03000500 00000000 00000108 B603CF03 E8030104 1A043304 4C046504 0101B603 01018403 000860EA 00000040 19010001 80380100 02DC4A01 0003905F 01000400 77010005 90910100 066CB001 00070108 38C10100 00008000 00000000 00C0D401 00010000 00000000 000048E8 01000200 00000000 000000D0 FB010003 00000000 00000000 580F0200 04000000 00000000 00E02202 00050000 00000100 00006836 02000600 00000001 000000F0 49020007 00000000 01000000 000560EA 00000040 19010000 80380100 00DC4A01 0000905F 01000000 08286E00 00002CC9 000001F8 0B010002 80380100 03905F01 0004F491 010005D0 B0010006 C0D40100 0700086C 39000000 245E0000 01FC8500 0002ACBC 00000334 D0000004 686E0100 05089701 0006ECA3 01000700 01683C01 00000104 3C410000 00000050 C3000000 00008038 01000200 00349801 00040000 01080098 85000040 B5000060 EA000050 C3000001 80BB0000 60EA0000 940B0100 50C30000 0200E100 00940B01 00401901 0050C300 000378FF 00004019 01008826 010050C3 00000440 19010080 38010080 38010050 C3000005 80380100 DC4A0100 DC4A0100 50C30000 06007701 00007701 00905F01 0050C300 00079091 01009091 01000077 010050C3 00000118 00000000 0000000B E4126400 280A3700 0A005403 90019001 90019001 90019001 90010000 00000002 011E07DC 00DC00DC 002C0100 00590069 004A004A 005F0073 00730064 00400090 92976096 00905500 00000000 00000000 00000000 00000000 0202D430 00000210 60EA0000 0210 My benchmark results: Geekbench OpenCL: 192,000 Points (average) Luxmark: 29,500 (average) Valley benchmark ran stable for 60 minutes with average GPU temperature being 69°C, fan speed was a low 1,800. Enjoy and let me know how this works for you guys! VegaTab_64.kext.zip
    1 point
  21. USB configuration in 10.11 - 10.14 google translate Настройка USB в 10.11 - 10.14 (627190) _ Страница 18 _ AppleLife.pdf.zip
    1 point
  22. For questions 1-3, these are unfortunately unresolved issues/bugs with VirtualBox itself. Native audio in Mojave doesn't work at present (never tried with VoodooHDA inside VM), VirtualBox BIOS does not remember previously "saved" settings and NVRAM is also non functional (these maybe related). Ofc, AptioMemoryFix driver would be useless since the BIOS is not Aptio ... If you want a "smoother" experience with native sound and working NVRAM, better to try running Mojave in VMware patched with @Donk's unlocker program. Installing VMware tools also improves graphics performance and allows dynamic resizing of the VM window (unlike VirtualBox which doesn't provide macOS guest tools at all). Sorry, don't know about Ozmosis inside VM.
    1 point
  23. With the new version (1.0.1) of the VirtualSMC and SMCBatteryManager plugin (1.0.0d1), I can't see the battery percentage at Menubar. Even if I click to show it (System Preferences > Energy), is not possible, it is unchecked automatically.
    1 point
  24. I did update to 6.7U1 just yesterday and 3.0 continues to work. I shut down my macos VMs, uninstalled unlocker, rebooted, updated ESXI, rebooted, re-installed unlocker again, rebooted and finally ... macos Mojave VM is back running Thanks
    1 point
  25. Da una certa versione di High Sierra, per montare la EFI è necessario avere i permessi di amministratore. Vecchie versioni di Clover Configurator non chiedono la password (permessi di amministratore) quindi non possono montare la EFI su nuove versioni del sistema operativo. Tutto ciò non è collegato in alcun modo con Clover o con il config.plist
    1 point
  26. No longer related to VirtualSMC topic, but from what I read on Clover package description: 64-bits Driver to support non-usual partition maps such as: hybrid GPT/MBR or Apple Partition Map.
    1 point
  27. Actually I don't use HDMI audio. I'm testing audio_CloverALC right now. The audio output works, but input not work because of layout-id = 2 that I'm using in place of layout-id 1 that Mojave drop it. @khamsakamal48 Using AppleALC with Lilu I was able to make the onboard audio and HDMI work perfectly. Even with the microphone. The layout-id = 7 worked that a beauty. Guide updated.
    1 point
  28. No idea with your panic issue then, anyway these drivers seem could be excluded on your case (with FV disabled): - AppleImageCodec - AppleKeyAggregator - AppleKeyFeeder - AppleUITheme - FirmwareVolume - VirtualSmc Also not sure if these drivers are needed: - OsxFatBinaryDrv - PartitionDxe CMIIW; I use this VirtualSMC v1.0.1 on my 10.11.6 up to 10.14.1 Beta (and found no issue, except my laptop battery is not well recognized, yet), OFC.. it'll be diff. result on diff. mach. We could press "F2" upon Clover GUI to generate "preboot.log" and it'll be saved on "/EFI/CLOVER/misc", at least we'll know which kexts used as well. VirtualSMC_v1.0.1-20181006.zip
    1 point
  29. Welcome home, AnV.. thanks for your FixEDID.app!
    1 point
  30. Not a black screen but a bright white flash. Sent from my iPhone using Tapatalk
    1 point
  31. Hello again. I have this bright flash as well also with a sapphire nitro+ rx580 8gb. Sent from my iPhone using Tapatalk
    1 point
  32. you can't see BootOrder nnvram in macos. cleannvram.efi remove BootOrder nvram value and other from filter that has Boot####. it affects our clover boot option entry in BIOS. after press f11, my nvram result(aptiomemoryfix, vitrualsmc). it's very clean status. Last login: Sat Oct 20 21:15:07 on ttys000 SherloccBookPro:~ sherlocks$ nvram -p fmm-computer-name Sherlocks%ec%9d%98 MacBook%c2%a0Pro security-mode none bluetoothActiveControllerInfo z%e0%89%04%00%00%00%000%14%ac%d1%b8%e2%a4%d0 EFILoginHiDPI %00%00%00%00 specialbootdevice %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%00%17%03%12%0a%00%01%00%00%00%00%00%04%01*%00%02%00%00%00%00H%06%00%00%00%00%00%00(*%08%00%00%00%00%8f%0a5%8c%c6P%e6C%ad%a6^%16p%d2e%d9%02%02%04%03$%00%f7%fct%be|%0b%f3I%91G%01%f4%04.hB%ba%afc~%ff%1e%a9M%b0%d2$%86%1e%e2HD%7f%ff%04%00 SystemAudioVolume # SystemAudioVolumeDB %d9 csr-active-config w%00%00%00 backlight-level i%05 flagstate %00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00 SherloccBookPro:~ sherlocks$
    0 points
  33. froze up -> processing -> reboot okay? i know vit9696 nvram clear has bootorder remove. i think he want all nvram value initialized. i will add that avoid to remove boot option. 나의 LG-F800S 의 Tapatalk에서 보냄
    0 points
×
×
  • Create New...