Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 03/08/2021 in Posts

  1. Hackintool 3.5.3 reports correct 0.6.7 version for me... When I "upgrade" from one version of OC to the next, I completely clear my EFI, copy the new (in this case 0.6.7) EFI from github (both BOOT and OC) to my clean EFI and then replace config.plist, Kexts, ACPI. Then I reboot, clear NVRAM and boot with my new OC. Without seeing your EFI, I'd guess that you've accidentally mixed OC file versions in your EFI or you're not booting from the EFI that you think you are.
    2 points
  2. It didn't give me any peace after all. I did everything all over again. Downloaded OpenCorePkg-master, had it compiled, created a fresh config.plist from a sample.plist, did an clean-NVRAM, reset the Linux boot entries in the shell, and so on. The result this time is a working configuration, as it should be. Now I just need to find the error that caused it to fail before, but at the moment I can't see the wood for the trees. Thank you very much for your help, it has motivated me.
    2 points
  3. if you want to compare it with mine 0.6.7-config.plist.zip
    2 points
  4. Since these posts show updates, I am looking for some pointers as to why updates are not showing in Big Sur system preferences. Csrutil enable and csrutil authenticated-root enable in recovery console modifies NVRAM csr-active-config in config.plist to 10000000 and booting is enabled but no updates. Cannot boot Big Sur with SIP completely enabled 00000000 in config.plist due to kernel panic. Any specific pointers as to where and what to look for with boot args set to: no_compat_check keepsyms=1 -lilubetaall -v debug=0x100 lapic_dont_panic=1 What specific log files to look at? What specific boot files to look at?
    1 point
  5. Glad to read you. Sometimes there are strange things in this hackintosh world.
    1 point
  6. @MacKonsti I haven't performed a "from scratch" OC install (all of my installs are migrations from CLOVER), so I haven't had to generate a new ROM value. For new ROM value, you should be able to use the same method that works for CLOVER: use a network MAC Addr. See here.
    1 point
  7. @antuneddu I took the settings from your config.plist and activated my custom entries. The result is the same: Windows can be booted, but the two penguins cannot. As soon as I go back to 0.6.5, everything works again. I give up. Maybe it will work again in 0.6.8 or later.
    1 point
  8. Yes, I see. Your LAN card is Intel and Clover has algo to catch its MAC-address by two ways. First one using UEFI BIOS. But in your case UEFI BIOS does not supply services for reading MAC. Second one is legacy way developed for very old cards. It seems for your case the procedure is no more working. So write into config digits you know <key>ROM</key> <data>112233445566</data> It may be <string> as well.
    1 point
  9. 20210308 * New: All data tables support copying rows and pasting rows between multiple processes or single processes (multiple rows, undo and redo are supported, copied history data is stored using persistent storage policy, if pasting history data is not supported, the paste menu is grayed out) * Other detailed improvements and optimizations
    1 point
  10. maybe c enters the scanpolicy? I set it to 2687747 and it works
    1 point
  11. Reboot and clean NvRAM, see what the result is.
    1 point
  12. but i'm not as good as you or @blackosx for icons i don't know where to start, all the way i'm trying but for now i use your icons they look good on top hope you don't mind, i'll pay you the copyrights .I wonder if you can move the position of the icons upwards, perhaps by modifying the .lbl files? Thanks
    1 point
  13. it's working perfectly thank you again for all your intelligence
    1 point
×
×
  • Create New...