Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 11/14/2019 in all areas

  1. 3 points
  2. 2 points
  3. https://www.insanelymac.com/forum/topic/282787-clover-v2-instructions/ https://sourceforge.net/p/cloverefiboot/wiki/Home/ Instructions mostly outdated so ask at the forum what you have a question. boot0af is recommended for actual configuration when you have GPT disk with partitions: disk0s1 - EFI disk0s2 - system, and more So legacy boot will follow this algorithm: 1. BIOS will call HDD, read zero sector where boot0af installed. 2. boot0af will transfer execution to first sector in EFI partition where boot1f32 installed. 3. boot1f32 will load boot file (usually the copy of boot6) which is the legacy Clover containing EFI framework (so called CloverEFI). 4. CloverEFI will call CloverX64.efi which is GUI. boot0ss is for old MBR formatted HDD. This is separate story.
    2 points
  4. macOS Catalina 10.15.2 beta 2 (19C39d)
    2 points
  5. Again it is completely wrong. The device name in the ACPI table has nothing to do with getting H264 or HEVC encoding/decoding to work. It all depends on the kexts that supports the GPU and the SMBIOS you are using in combination. I have a Intel hack with Vega 64 and iMacPro1,1 SMBIOS and a AMD hack with a Radeon VII without any device renames in the ACPI table or Whatevergreen enabled and H264 and HEVC encoding/decoding are working perfectly fine. Also DRM with AppleTV, Netflix, Amazon Prime Video and Hulu all working fine in Safari. I have already provided proof that your "required" statement is false.
    1 point
  6. This statement is incorrect. The device name in the ACPI tables does not need to be GFX0 in order to get HEVC to work.
    1 point
  7. Fai le foto alle impostazioni del BIOS. Ho finito le idee. Se fosse impostato correttamente, non saprei più cosa provare.
    1 point
  8. Thanks for the suggestion guys. Now I can't wait to get home to mess with my rig some more.
    1 point
  9. Do the free2000, keep your board if you don't need thunderbolt. I need thunderbolt for my highspeed storage array. You can always add a thunderbolt card to your board. P.S.: Pull the battery, pull that shiit out. Pull it hard. Lolz
    1 point
  10. Maybe I should just do that then and keep my board..lol
    1 point
  11. Equal on that front bud. If you want to stop pulling the battery or hitting f11 at startup then swap out aptiomemoryfix for free2000 and it will end.
    1 point
  12. He had to switch to it because of the troubles. Pre Cat he was using aptiomemoryfix for that guide too. a lot of people have been forced to do the thing tbh, we are some of the lucky ones
    1 point
  13. I love to live dangerously, so... Free2000, I embrace thee. Mald0n used it in his guide too.
    1 point
  14. Depends on your needs but @larabee is right. if you don’t use thunderbolt and have no need for it then get the master. One thing about the designare is that is has a lot of trouble working correctly with aptiomemoryfix.efi and you probably end up having to use the naughty free2000 driver instead.
    1 point
  15. 1 point
  16. Designare is way better in my opinion if you need thunderbolt.
    1 point
  17. 1 point
  18. Nel log non vedo alcun riavvio. Prova a far ripetere il problema ed estrai di nuovo il log.
    1 point
  19. Finding the correct path in Custom Entries have been already explained several times within the last few pages of this thread. It should start with " PciRoot".
    1 point
  20. @hungrywallet I think I might of worked out what your problem is with Apple TV, I noticed when I was repairing your EFI that your not using the Airportfixup.kext and if I remove it from my system everything works as normally or so you think until you online game and then you notice how bad your ping and stutter really is. this also effects players that stream so I just tried now without airportfixup.kext to play a stream via appletv and I got all sorts of trouble like hanging and massive pauses where you think its not playing or a black flash instead of playback but as soon as I put the kext back and reboot its perfect again so in conclusion drop the airportfixup.kext back into your Kexts folder in clover and reboot and try it again (make sure the EFI is as I sent it to you plus your details and no extra flags then what I added) I bet you it works buddy
    1 point
  21. Check your graphics device name. Needs to be GFX0. HEVC works as usual in Beta 2.
    1 point
  22. Thank you very much, it doesn't freeze anymore
    1 point
  23. Yes, you should delete the files in the ACPI-Tables folder and put your own 'clean' .aml files in there (press F4 when you're at the boot drive selection window of Clover during the boot process, and find them under EFI/CLOVER/ACPI/origin). First, you should install the necessary tools, by running Utilities/install_tools.command. Then, run the command, the first one (create_patched_DSDT.command) will generate and compile the necessary dsl files and the second command (install_ACPI_to_ESP.command) wil place then in the appropriate destinations. Correct. If you run Utilities/install_tools.command you should be able to run the command properly.
    1 point
  24. @Tetonne how are you my old friend!? boot with verbose to see what is crashing. then try to boot up without HD3000 gfx (try inject id 0x12345678) and then make sure you use config.2e2 as config.list the latest patches for HD3000 got rid of weird gray menubar and finder panel. woohoo!
    1 point
  25. The site is back again! --Edit-- But no sign from any major staff members. I guess someone revived it for trafic purposes only. Really sad how the story of that site just ended. The site deserves a lot more respect than that, IMHO.
    1 point
  26. Il riavvio allo spegnimento è di solito legato alle USB. Riesci a raccogliere info dal log di sistema? cd ~/Desktop log show --predicate "processID == 0" --start 2019-11-13 --debug > system_log.txt
    1 point
  27. You should install brcmpatchram3, brcmfirmwarerepo and brcmbluetoothinjector from here: https://github.com/acidanthera/BrcmPatchRAM/releases EDIT: Sorry, I missed that you installed 10.14.6 - these files are for Catalina
    1 point
  28. Bluetooth didn't seem to work with Catalina, even though the adapter did show up. I'm now using BrcmBluetoothInjector.kext, BrcmFirmwareRepo.kext and BrcmPatchRAM3.kext on release 2.5.0 (link here), now both WiFi and BT work (using a Dell DW1560)
    1 point
  29. Here we go... Catalina is out, but I've been focused on getting Mojave running on this machine. just as a reminder of the procedure, I'll write here what I've done. Mojave is running on both my internal SSD GPT HFS+ drive and external SSD APFS (managed to boot the latter with enoch v2922 APFS beta v2 but I'm not able to install it onto an APFS partition itself): first of all I've done a full backup clone of my Sierra working system on the second internal hard drive (also cloned the whole system onto my external APFS drive. This is not required for HFS+ installations) downloaded 10.14.2 installer app with dosdude1's Mojave patcher tool (I was not able to boot 10.14.5 and following installer) created a patched install drive following this guide from @crazybirdy with the app at previous point extracted the Kernel file from System/Library/Kernels in Essential.pkg and put it in System/Library/Kernels into the installer drive applied smbios for MacBookPro7,1 (I don't know if it's actually required anymore since the installer is patched) boot the installer (and convert the disk to APFS in case of my external drive. This is not required for HFS+ installations) install onto the previous system (upgrade without problem) reboot from Sierra backup and install up-to-date-lilu/up-to-date-applealc/HS Nvidia kexts & telemetry plugin and repaired S/L/E permissions onto the fresh 10.14.2 installation (thanks to ASentientBot) boot mojave and config update to 10.14.6 using a combo update patched with macOS Patcher from RMC team see details here and here (HFS+ doesn't get software update within system preferences) (APFS get the update through system preferences but I had to download 10.14.5 and install it and then 10.14.6 and install it) reboot from Sierra backup and install HS Nvidia kexts, telemetry plugin and other bundles onto the system - slight different than before since 10.14.4 and later changed nvidia behaviours (pkg thanks to chris1111 but runs only from mojave itself) reapplied MacBookPro5,2 smbios and boot fix GUI glitches with spiramira's hybrid mode method Checking what's working right now. Stay tuned EDIT It seems pretty stable until now. I will post here any issue that would eventually occur. I'm trying a fresh clover installation onto an external usb drive just to collect some experience. Let's see what happens..
    1 point
  30. APFS support is coming! So's XMas 2030
    1 point
×
×
  • Create New...