Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 07/13/2020 in all areas

  1. Pavo

    [pre-release] macOS Big Sur

    If your monitor refresh rate is above 60Hz Messages will crash, its a known bug.
    5 points
  2. Hi guys, I'm back and have good news I did it , solved my HEVC problem. In the end I don't know how I did it, but the fact is I solved it, as you can se below... Thanks to @eSaF and @manmo71 for all the help and moral support...
    4 points
  3. Hi @Slice report some issues. 6/19, commit 1072, 109d1f5, kext patcher and kernel patcher work fine on Mojave, Catalina. can't pass the Big Sur ++++++++++++++++++++++++++++++++++ can't boot to Big Sur. 7/13, commit 1091, b79f643, kext patcher and kernel patcher didn't work on Mojave, Catalina, Big Sur, and can boot to Big Sur system, and get panic without kext patch after booting logs. If I replace 109d1f5/kernel_patcher.cpp to b79f643/kernel_patcher.cpp, and modify as diff as below. The commit 1091, b79f643 kext patcher and
    3 points
  4. New method macOS Big Sur Wi Fi Patch for Unsupported macs (Easier Method) Works with beta 2! https://www.youtube.com/watch?v=1rmHb_z6ssQ
    3 points
  5. Gigamaxx

    OpenCore Discussion

    I just did a fresh install of Beta1 using the above link EFI (added correct serials etc). Credentials? I downloaded the Beta2 update and ran it on the install. I used a HDD so it took about 2 1/2 hours total but all is good.
    3 points
  6. Hi @eSaF, @manmo71, Yes I know all of that and this time I made a new build of OpenCore from source and made a new EFI folder from scratch... gathered kexts, graphics and made a new config.plist, tested the new EFi first in my usb install and only then changed my boot EFI, but first I verified if HEVC was working... and it was. As soon I verified that all was working I deleted all the others EFI, but you advice is rock solid and next time I'll do it. Thanks to both of you ...
    2 points
  7. @MorenoAv - Nice one mate determination paid off - Here is a tip for you, when ever there is a new release of OC no matter how small, I tend to build a new EFI Folder on a spare USB Drive and boot off it to make sure it will boot the system before I commit it to the main Drive. When I am satisfied all is working well as before, I will then copy the new folder to the main Drive but here is the thing, I always make a copy of the one I am removing and store it on a spare ssd Drive where I keep all my bits and pieces just incase I have to revert back (I don't trust Time Machine in Betas or any ba
    2 points
  8. By now, everyone here must know that I am not able to connect to my internal drives (hdd, ssd, DVD/ATAPI) when I boot to BS installer or BS Beta 2 installed on an external USB drive. Here is what I see when I boot up. Immediately after what is in the photo, my laptop goes to the apple symbol and progress bar that indicates that graphics drivers have loaded. It then boots up but only detects external USB drives. I have tried every possible OC configuration and have used my native DSDT with no patches and still the problem persists. Ideas would be appreciated. I booted
    2 points
  9. Run macserial with Clover, copy System ID, insert in SystemUUID OpenCore.
    2 points
  10. When new numeration will be clear and the patches will be proved working then we can change the numeration. Not a big deal really. OK, now I'll set 11.1.
    2 points
  11. @chris1111 Actually we do not know how Apple will estampe the future updates. Maybe we'll have something like 11.0.1 ->11.0.6 and 11.0 > 11.11.6. We do not know if the next upgrade will be 12.0 or 11.1 Edit - Oups, @crazybirdy beat me.
    2 points
  12. I think it's 11.1 it means, 10.8.5~10.15.x~10.x.x~11.0.x, not include 11.1.x BS is 11.0.x, next is 11.1.x, if apple wants. But SystemVersion.plist is 10.16 for Big Sur now. - == old value + == new value - return (os_version >= AsciiOSVersionToUint64("10.8.5")) && (os_version < AsciiOSVersionToUint64("10.16")); + return (os_version >= AsciiOSVersionToUint64("10.8.5")) && (os_version < AsciiOSVersionToUint64("11.1"));
    2 points
  13. maybe should be - return (os_version >= AsciiOSVersionToUint64("10.8.5")) && (os_version < AsciiOSVersionToUint64("11.0"));  + return (os_version >= AsciiOSVersionToUint64("10.8.5")) && (os_version < AsciiOSVersionToUint64("11.7")); First non Hybrid BS ?
    2 points
  14. os_version < AsciiOSVersionToUint64("10.16") Maybe we severely should consider that macOS Big Sur is 11.0 and not 10.16? - return (os_version >= AsciiOSVersionToUint64("10.8.5")) && (os_version < AsciiOSVersionToUint64("11.0")); + return (os_version >= AsciiOSVersionToUint64("10.8.5")) && (os_version < AsciiOSVersionToUint64("11.1"));
    2 points
  15. Clover's DSDT Fixes are based on artificial intelligence so they may be wrong. If you encounter an error then you have two ways: 1. Found an exact reason and improve clover's sources. 2. Switch off DSDT fixes.
    2 points
  16. Nice One!!!!!! - That was a good call by Pavo I just got around to checking a few things with Big Sur - Speed Stepping seems to be working with the change of Mac Model.
    2 points
  17. Although the upgrade to Big Sur went smoothly, the system itself was a bit laggy and buggy. So I wiped the drive earlier and did a fresh install. Performance is much better now, although the menu bar still lags even after deleting the APFS snapshots. Possibly it's because I'm running from a hard disk. Previously I couldn't run Chess.app as it would hang on launch. It launches fine now, but instead hangs when trying to quit. I wasn't able to load the Accessibility prefpane last time but it works fine now. Guess there was just too much crud from the old install. Also my h
    2 points
  18. Finally a working beta 2 direct installation with working wifi, had to skip the snapshot creation phase during install and was able to roll back the drivers! Thx guys for all the helpful stuff found on this thread, keep up the good work for developer too obv! P.s on an old optiplex runs perfect! xD
    2 points
  19. I created a Big Sur beta 2 installer USB for my X299 Gigabyte UD4 test system, the install worked. Top tip, after copying the EFI to the SSD, I selected NVRAM reset before booting. Everything seems to be working as expected. I can confirm that the EFI OC 0.6.0 folder for USB installer I shared before here is working fine :
    2 points
  20. Wifi is Connect no kext install in System only DSDT patch Thanks MaldOn The menue bar is Now fast as my Real MacBook Pro Really Happy of BS-2 Only Trackpad in preference system not open
    2 points
  21. Here my theme of OC ➣ Themes OpenCore (Main Project) Background Collections for every theme How to create are own Theme with OpenCanopy Generator an app for create OC Themes ### Setup config.plist - Misc -> Boot -> PickerMode: External - Misc -> Boot -> PickerVariant: Default, Modern or Auto - Auto — Automatically select one set of icons based on DefaultBackground colour. - Default — Default icon set. - Modern — Modern icon set. - UEFI -> Drivers add OpenCanopy.efi ### How to use ➤ PickerVariant:
    1 point
  22. Version 2.0

    26,569 downloads

    Please read me: Ever since macOS Mojave came out (I mean the first DP) Apple removed the support for Atheros based WiFi Adapters from the IO80211Family.kext, so to fix it we need to add the AirPortAtheros40.kext to the Extensions manually. After each clean install the AirPortAtheros40.kext needs to be installed and after clean installing Mojave DPs after few times I decides to create this app to save some time. How to use it: This application will install the missing AirPortAtheros40.kext into /System/Library/Extensions and after the installation is done and once you
    1 point
  23. cvad

    Bootdisk Utility

    Version v2.1.2020.028b

    39,609 downloads

    Make bootable USB Flash Disk for MAC OS X with Latest Clover bootloader revision fast and easy by one click! under OS Windows. Special utility from cvad & russian MAC community for new hackintosh users. Enjoy... For more information and complete instructions please see this topic. Anyone who likes the program, please support its Community Score. Feel free to "Rate File"
    1 point
  24. fantomas

    Site Issues

    I didn't know I was your mate - Never mind, you say you're able to block that ad under Catalina and not under Big Sur. Did you ever think it could be related to Big Sur and nothing do with us?
    1 point
  25. I confirm working wifi with vanilla kexts!
    1 point
  26. IO80211Family.kext
    1 point
  27. Slice

    Clover.app testing

    I propose later to move OcQuirks.plist to config.plist. Just take a time.
    1 point
  28. yes. 11.0 or 10.6 doesn't matter now, but it will if the next update will be 10.16.1 for example.
    1 point
  29. Probably a new revision of the PPT. It shouldn't matter tho. Show me a screenshot of your MPT so I can see the differences you are talking about.
    1 point
  30. Slice

    Clover.app testing

    Hi @vector sigma, help me please to update installer package and you may update Clover.app for new drivers https://www.insanelymac.com/forum/topic/304530-clover-change-explanations/?do=findComment&amp;comment=2729515 These three files OcQuirks.efi OcQuirks.plist OpenRuntime.efi will be recommended replacement for AptioMemoryFix.efi.
    1 point
  31. I have this ACPI issue before. After I cancel all ACPI, it works fine for me.
    1 point
  32. Hello gentlemen, I installed Big Sur from USB using OC, on my Dell Inspiron 15r 3543-A30, i5 5200u, 8gb SSD120gb, Wireless DW1550 everything works great! only Bluetooth that still requires correction, DW1550 My EFI OC! EFI DELL 3543-A30 BIG SUR BETA 2.zip
    1 point
  33. ARE YOU USING OC? WHAT KEXT INJECTED BLUETOOTH?
    1 point
  34. what model of your wireless pci?
    1 point
  35. eSaF

    [pre-release] macOS Big Sur

    Sorry re-upload iMessage Image working on my rig
    1 point
  36. busso

    [pre-release] macOS Big Sur

    csr-active-config parameter w% 08% 00% 00 this corresponds to hexadecimal, base 64? or how to put it correctly to disable csr-active-config. I have it in 67000000. Thank you.
    1 point
  37. Many thanks for this guide @fusion71au! Now my Atheros AR9285 works perfectly! And now the menu bar goes fast, like my real iMac. In my opinion, @chris1111, these snapshots conflict with the menu bar, making it unusable and very slow. Thanks again
    1 point
  38. Taruga

    [pre-release] macOS Big Sur

    Regarding the problem Stuck on ramrod mentioned in the link: https://dortania.github.io/OpenCore-Desktop-Guide/extras/big-sur/#stuck-on-ramrod where the instalation restarts on a infinite loop with a line near the bottom that says: ramrod exited with status 1 - Rebooting I want to inform that I had this problem after installing it on an OCZ Vertex 2 SSD and with or without vsmcgen=1, and with FakeSMC or with VIrtualSMC I could not overcome the problem. I tested the same Open Core configuration without changing anything on a HDD and (it was painful to wait, but...) it worked w
    1 point
  39. Make usb big sur boot installer ( or catalina if big sur not)
    1 point
  40. No need to patch installer if your SMBIOS is officially supported in Big Sur (that patch is to allow install into older Macs, bypassing compatibility checks). IIRC, I only saw Preboot booting into the second stage install (the one with approx 30 minutes remaining). The final boot into the third stage shows only the Big Sur volume to boot from the OpenCore menu. Interrupting half way through the loading bar during this stage (when the progress bar slows to a crawl and the snapshot is being created) ---> Restart to OpenCore Menu now shows both "macOS Installer" and the Big Sur v
    1 point
  41. Blu24

    [pre-release] macOS Big Sur

    Anyone who wants to check their config.plist I highly recommend OpenCore Sanity Checker: https://opencore.slowgeek.com
    1 point
  42. Anyone got any Brain Patches mine hurts Has anyone installed on a Asrock phantom Gaming 9 z390 chip is an intel confin doger 9900k I have two nvme samsung 970 pro drives, and noticed that when I try to install Big Sur that it trys to corrupt Catalina's Lan despite pointing to the correct nvme. tried latest OpenCore 0.60 with new Kernels tried boot arges can any of you guys help does anyone own an Asrock board z390 is there life on Mars? config.plist
    1 point
  43. Slice

    Clover Change Explanations

    Rev 5119 commit 620401d Included OcQuirks and OpenRuntime into Clover repository. The drivers will be built at Clover compilation. Further they will be improved and included into package.
    1 point
  44. This seemed like a great idea but I copied all of the SATA code from my original DSDT and copied it to my custom DSDT, changed SAT0 to SATA to get it to compile but I still had the same problem on reboot. I think you are on the right track for me, however. I will likely be forced to start with a new OC set up that does not include my custom DSDT. If I can get it to boot without my custom DSDT, I can determine whether that was the cause of my laptop's inability to see the SATA-connected drives. Thanks.
    1 point
  45. macOs Big Sur Beta 2 - Ryzen 7 3700x - MSI x570-A PRO - 16GB Ram - RX 580 8 GB Installed beta 1 using bootable USB method Used Opencore Builder to get the latest version of OC 0.6.0 and Virtual SMC , Lillu , Apple ALC , WEG and Realtek8111 kexts Updated to beta 2 using System updater - 10 gb update Note - Serial number - ROM - MLB - UUID removed from plist Attached Config .plist and Kexts screenshot config.plist
    1 point
  46. No luck here but I have made some advances in my understanding of the problem. The problem lies with the new AHCIFamily.kext and more particularly the IOAHCIBlockStorageDriver.kext. It simply cannot read the internal drive information. I tried using the AHCIPortInjector.kext but it did not solve the problem. The problem is NOT that it cannot read internal vs. external drives. The problem is that Big Sur cannot read SATA drives (i.e., drives physically connected to PRT.). You can see this if you use IORegExplorer. I am thinking that this problem is not related to our hardware but I can't
    1 point
  47. 1 point
  48. Latest OpenCore commit is able to boot the installer and pre-existing installed macOS 11 Big Sur with kext injection without using prelinkedkernel nvram variables. It is now able to boot both with the new kernel collections method.
    1 point
  49. No problem,, I shouldn't use custom entry because i have use separated disk for each Operating System. Every disk have own EFI/Boot/Bootx64.efi. So actually i don't need use those features. I just want to change entry name instead default ones, i just need to use ._contentDetails files to edit entry name. Thanks again
    1 point
  • Newsletter

    Want to keep up to date with all our latest news and information?
    Sign Up
×
×
  • Create New...