Jump to content

cnrd

Members
  • Content Count

    38
  • Joined

  • Last visited

About cnrd

  • Rank
    InsanelyMac Protégé
  1. cnrd

    OpenCore Discussion

    Okay, so apparently the problem with AirportBrcmFixup.kext is related to Catalina. Another 2 questions: 1. How can I set the default boot volume? (Using Startup Disk does not work) 2. Any way to add my Windows 10 volume? (In Clover I just chain-booted \EFI\Boot\bootx64.efi on the Windows SSD)
  2. cnrd

    OpenCore Discussion

    Hi So I got my system booting using OpenCore, everything is working great except for AirportBrcmFixup.kext I get this error on boot: "OC: Prelink injection AirportBrcmFixup.kext - Invalid Parameter" and the kext is never loaded, all my other injected kexts works just fine. I have attached my (scrubbed) config.plist, if anyone could take a look. config.plist
  3. Hope you may be able to help. I have 2 problems: 1. Disabling Unrestricted FS (SIP) causes all USB ports to not work. 2. Disabling CMS Support and using more than one screen causes black screen on both screens. (Have WhateverGreen.kext installed). The attached files are with CMS enabled (Both screens working) and CMS disabled (One screen unplugged to get output). Thanks :-) Send me Colossus.home-CMS enabled.zip Send me Colossus.home-CMS-Disabled-Single-Screen.zip
  4. cnrd

    [pre-release] macOS High Sierra

    Ended up downloading it on my hack, got the full installer there, not sure why. (Macbook is a rMBP late 2013 15", hack is in sig using iMac17,1).
  5. cnrd

    [pre-release] macOS High Sierra

    How do you guys get the full installer to create a USB? Whenever I download it from the Mac App Store, I only get a 5 MB file.
  6. cnrd

    Clover Problems and Solutions

    What about this? #!/bin/bash mkdir -p "/Library/Application Support/Clover/LogoutHook" gLogoutHookf="/Library/Application Support/Clover/LogoutHook/CloverLogoutHook.sh" saveNVMRAM="/Library/Application Support/Clover/LogoutHook/save_nvram_to_efi.sh" if [[ ! $(defaults read com.apple.loginwindow LogoutHook) && -f "${saveNVMRAM}" ]]; then echo "#!/bin/bash" >> "${gLogoutHookf}" echo -e "\"${saveNVMRAM}\"" >> "${gLogoutHookf}" chown root:wheel "${gLogoutHookf}" chmod 755 "${gLogoutHookf}" defaults write com.apple.loginwindow LogoutHook "${gLogoutHookf}" elif [[ "$(defaults read com.apple.loginwindow LogoutHook)" != ${saveNVMRAM} && -f "${saveNVMRAM}" ]]; then rm "${gLogoutHookf}" echo "#!/bin/bash" >> "${gLogoutHookf}" echo -e "\"$(defaults read com.apple.loginwindow LogoutHook)\"" >> "${gLogoutHookf}" echo -e "\"${saveNVMRAM}\"" >> "${gLogoutHookf}" chown root:wheel "${gLogoutHookf}" chmod 755 "${gLogoutHookf}" defaults write com.apple.loginwindow LogoutHook "${gLogoutHookf}" fi It will add the logoutHook in case there is none, if logoutHook is already set, then create a script contaning old logoutHook and the EFI script, meaning that our EFI script will work, while the old logoutHook will also work. (Yes I know it's fugly, too tired to clean it up). EDIT: This won't work, stuck on reboot.
  7. cnrd

    Clover Problems and Solutions

    I edited the post just above yours, what about that idea? (Not overwriting LogoutHook, and letting people add it to their own scripts if they need to).
  8. cnrd

    Clover Problems and Solutions

    I'm pretty sure we'll only have to write this value once, so I don't think we need to run it on each boot, unless someone were to delete it manually, but then we should probably let them do so? We could probably just let clover write the value as a part of the install, if scripts are chosen. EDIT: Or we could do something like: #!/bin/bash gLogoutHookf="/etc/logoutHook/save_nvram_to_efi.sh" if [[ ! $(defaults read com.apple.loginwindow LogoutHook) && -f "${gLogoutHookf}" ]]; then defaults write com.apple.loginwindow LogoutHook ${gLogoutHookf} fi But that would be the same (But not overwriting LogoutHook if people have something else in there. Also I don't think this should be added to 20.mount_ESP.local, as that file is for mounting ESP on boot, not writing extra config for save_nvram.
  9. cnrd

    Clover Problems and Solutions

    I'm not sure that we should keep the 80.save_nvram_plist.local file in rc.shutdown.d folder, as I think that folder should be reserved for scripts that are run at that time, not for a logoutHook, but I'm not really sure where we should place it then? (I'm sorry, not a reply for you directly, but more for the Clover maintainers). Not sure if there is actually a folder we could use, but I'm thinking: "/etc/logoutHook"?
  10. cnrd

    Clover Problems and Solutions

    Looks like it is (very quick test): sudo defaults write com.apple.loginwindow LogoutHook /etc/rc.boot.d/40.load_msdos_kext.local Reboot sudo kextunload com.apple.filesystems.msdosfs To make sure the msdos kext is not loaded. Reboot and nvram.plist in EFI partition was updated. So LogoutHook should be early enough to allow us to load stuff. I used this page for the logoutHook command.
  11. cnrd

    Clover Problems and Solutions

    Yeah I just created my own simple version: $cat 40.load_msdos_kext.local #!/bin/bash kextload /System/Library/Extensions/msdosfs.kext
  12. cnrd

    Clover Problems and Solutions

    I can confirm that this script also works for my system (Which has had problems with all other scripts), and propose that it is added to Clover. Just one question Syscl: What is the reason you are saving the nvram.plist in both "/" and EFI partition? EDIT: nvram.plist is only saved to EFI partition if I run: sudo kextload /System/Library/Extensions/msdosfs.kext before shutting down. We probably need to load that kext on boot?
  13. cnrd

    Clover General discussion

    Yes that is correct, but if nvram.plist is avaliable in EFI clover will still use that even after the fallback to save it into main partition, meaning that the nvram will not be up to date on the next boot. In my case it will always use the nvram.plist from EFI partition even if the one in main partition is "newer".
×