Slice Posted October 8, 2017 Share Posted October 8, 2017 All Clover versions will not load kexts from 10.13 if the system reported 10.12. // version in boot.efi appears as "Mac OS X 10.?" 1 Link to comment Share on other sites More sharing options...
Matgen84 Posted October 8, 2017 Share Posted October 8, 2017 All Clover versions will not load kexts from 10.13 if the system reported 10.12. // version in boot.efi appears as "Mac OS X 10.?" I have "getOS 10.12" when I boot from USB 10.13 with HDD 10.12 connected to my system. Why? Link to comment Share on other sites More sharing options...
Allan Posted October 8, 2017 Share Posted October 8, 2017 Hello guys, good morning. It's still necessary use the "NTFS.efi" at drivers64UEFI folder in dual-boot UEFI systems? It's a mandatory, to be more specific? Thanks Link to comment Share on other sites More sharing options...
Cyberdevs Posted October 8, 2017 Share Posted October 8, 2017 Hello guys, good morning. It's still necessary use the "NTFS.efi" at drivers64UEFI folder in dual-boot UEFI systems? It's a mandatory, to be more specific? Thanks Hi Allan, good morning I have a rig with dual booting Windows 10 and macOS (El Cap, Sierra, High Sierra) and I don't use NTFS.efi, So I guess having it is not mandatory. I never used it. 1 Link to comment Share on other sites More sharing options...
MakAsus Posted October 8, 2017 Share Posted October 8, 2017 If I choose kext injection control in Clover Gui, go to the folder "other", and do not change anything there, just exit this folder and injection control menu, then try to boot from selected disk, boot fails. if I do all the same, then go into the shell, and exit from it, and only then try to boot, or try to boot from another disk, everything is fine (Clover v2.4k r4243). 4 Link to comment Share on other sites More sharing options...
Sherlocks Posted October 8, 2017 Share Posted October 8, 2017 If I choose kext injection control in Clover Gui, go to the folder "other", and do not change anything there, just exit this folder and injection control menu, then try to boot from selected disk, boot fails. if I do all the same, then go into the shell, and exit from it, and only then try to boot, or try to boot from another disk, everything is fine (Clover v2.4k r4243). Not alone. I wrote this issue above. But my english skill is not good. Thank you for report Edit1. I always used injectkext=detect 나의 LG-F800S 의 Tapatalk에서 보냄 1 Link to comment Share on other sites More sharing options...
Badruzeus Posted October 8, 2017 Share Posted October 8, 2017 So, I reinstalled 10.13 (17A365) using APFS and then boot with r4243 (Legacy). I (by default) got no 10.13 dir inside /kexts, so I mv Other > 10.13 then placed my 3rd party kexts there. But, if using InjectKexts=Detect I was unable tp reach the desktop for unknown reason, all kexts appears on Kexts Inject Mgmt though. Otherwise, it works well by using InjectKexts=Yes. Thanks. (Compiled using GCC5.3 under Ubuntu 16.04, also same results from SF rev & buildclover xcode8.2) #EDIT: My prev tests under 10.13.1 (17B25c) got no problem by using InjectKexts=Detect/Yes, but with HFS+, with same r4243. bootlog.log_r4243_gcc53_ub16.04.txt.zip Link to comment Share on other sites More sharing options...
Matgen84 Posted October 8, 2017 Share Posted October 8, 2017 I have checked my 10.13 installers boot.efi and they shown as 10.12 (created from 10.12 with createinstallmedia), which is bad. Please try this patch (added dbg infos + comment out (Entry->LoaderType == OSTYPE_OSX_INSTALLER) here). Temporarily install mandatory kexts in /L/E/ with CSR_ALLOW_UNTRUSTED_KEXTS so you are able to reach the desktop. ** In xnu-4570.1.46 #define CSR_ALLOW_UNAPPROVED_KEXTS (1 << 9) @cecekpawon Sorry I do not know how to insert your patch or replace the original information in main.c file? Link to comment Share on other sites More sharing options...
Guest ricoc90 Posted October 8, 2017 Share Posted October 8, 2017 @cecekpawon Sorry I do not know how to insert your patch or replace the original information in main.c file? in terminal: patch -i /path/to/4243.diff Example: $ patch -i /Users/rico/Downloads/4243.diff patching file main.c More info: patch --help Usage: patch [OPTION]... [ORIGFILE [PATCHFILE]] Input options: -p NUM --strip=NUM Strip NUM leading components from file names. -F LINES --fuzz LINES Set the fuzz factor to LINES for inexact matching. -l --ignore-whitespace Ignore white space changes between patch and input. -c --context Interpret the patch as a context difference. -e --ed Interpret the patch as an ed script. -n --normal Interpret the patch as a normal difference. -u --unified Interpret the patch as a unified difference. -N --forward Ignore patches that appear to be reversed or already applied. -R --reverse Assume patches were created with old and new files swapped. -i PATCHFILE --input=PATCHFILE Read patch from PATCHFILE instead of stdin. Output options: -o FILE --output=FILE Output patched files to FILE. -r FILE --reject-file=FILE Output rejects to FILE. -D NAME --ifdef=NAME Make merged if-then-else output using NAME. -E --remove-empty-files Remove output files that are empty after patching. -Z --set-utc Set times of patched files, assuming diff uses UTC (GMT). -T --set-time Likewise, assuming local time. --quoting-style=WORD output file names using quoting style WORD. Valid WORDs are: literal, shell, shell-always, c, escape. Default is taken from QUOTING_STYLE env variable, or 'shell' if unset. Backup and version control options: -b --backup Back up the original contents of each file. --backup-if-mismatch Back up if the patch does not match exactly. --no-backup-if-mismatch Back up mismatches only if otherwise requested. -V STYLE --version-control=STYLE Use STYLE version control. STYLE is either 'simple', 'numbered', or 'existing'. -B PREFIX --prefix=PREFIX Prepend PREFIX to backup file names. -Y PREFIX --basename-prefix=PREFIX Prepend PREFIX to backup file basenames. -z SUFFIX --suffix=SUFFIX Append SUFFIX to backup file names. -g NUM --get=NUM Get files from RCS etc. if positive; ask if negative. Miscellaneous options: -t --batch Ask no questions; skip bad-Prereq patches; assume reversed. -f --force Like -t, but ignore bad-Prereq patches, and assume unreversed. -s --quiet --silent Work silently unless an error occurs. --verbose Output extra information about the work being done. --dry-run Do not actually change any files; just print what would happen. --posix Conform to the POSIX standard. -d DIR --directory=DIR Change the working directory to DIR first. --binary Read and write data in binary mode (no effect on this platform). -v --version Output version info. --help Output this help. Report bugs to <bug-patch@gnu.org>. Link to comment Share on other sites More sharing options...
Cyberdevs Posted October 8, 2017 Share Posted October 8, 2017 Hello guys, Is there any relations with OsxAptioFixDrv-64.efi and CsrActiveConfig? On my Asus P8H77-M LE rig I've been using OsxAptioFixDrv-64.efi for a long time and I had no problem, until Today I decided to to change the CsrActiveConfig's value from 0x67 and set it to 0x3 and I constantly get the Error Loading Kernel. If I use OsxAptioFix2Drv-64.efi it will load the OS, so I wonder what could be the cause?! I'm using Clover r4243 1 Link to comment Share on other sites More sharing options...
MICKHAEL Posted October 8, 2017 Share Posted October 8, 2017 Hello guys, Is there any relations with OsxAptioFixDrv-64.efi and CsrActiveConfig? On my Asus P8H77-M LE rig I've been using OsxAptioFixDrv-64.efi for a long time and I had no problem, until Today I decided to to change the CsrActiveConfig's value from 0x67 and set it to 0x3 and I constantly get the Error Loading Kernel. If I use OsxAptioFix2Drv-64.efi it will load the OS, so I wonder what could be the cause?! I'm using Clover r4243 exactly. with OsxAptioFixDrv-64.efi 0x67 ok and in I need to boot with 0x0 I must change to OsxAptioFix2Drv-64.efi Link to comment Share on other sites More sharing options...
Cyberdevs Posted October 8, 2017 Share Posted October 8, 2017 exactly. with OsxAptioFixDrv-64.efi 0x67 ok and in I need to boot with 0x0 I must change to OsxAptioFix2Drv-64.efi So I'm not alone in this 1 Link to comment Share on other sites More sharing options...
MICKHAEL Posted October 8, 2017 Share Posted October 8, 2017 I think this need to be fixed/ Link to comment Share on other sites More sharing options...
Matgen84 Posted October 8, 2017 Share Posted October 8, 2017 in terminal: patch -i /path/to/4243.diff Example: $ patch -i /Users/rico/Downloads/4243.diff patching file main.c More info: patch --help Usage: patch [OPTION]... [ORIGFILE [PATCHFILE]] Input options: -p NUM --strip=NUM Strip NUM leading components from file names. -F LINES --fuzz LINES Set the fuzz factor to LINES for inexact matching. -l --ignore-whitespace Ignore white space changes between patch and input. -c --context Interpret the patch as a context difference. -e --ed Interpret the patch as an ed script. -n --normal Interpret the patch as a normal difference. -u --unified Interpret the patch as a unified difference. -N --forward Ignore patches that appear to be reversed or already applied. -R --reverse Assume patches were created with old and new files swapped. -i PATCHFILE --input=PATCHFILE Read patch from PATCHFILE instead of stdin. Output options: -o FILE --output=FILE Output patched files to FILE. -r FILE --reject-file=FILE Output rejects to FILE. -D NAME --ifdef=NAME Make merged if-then-else output using NAME. -E --remove-empty-files Remove output files that are empty after patching. -Z --set-utc Set times of patched files, assuming diff uses UTC (GMT). -T --set-time Likewise, assuming local time. --quoting-style=WORD output file names using quoting style WORD. Valid WORDs are: literal, shell, shell-always, c, escape. Default is taken from QUOTING_STYLE env variable, or 'shell' if unset. Backup and version control options: -b --backup Back up the original contents of each file. --backup-if-mismatch Back up if the patch does not match exactly. --no-backup-if-mismatch Back up mismatches only if otherwise requested. -V STYLE --version-control=STYLE Use STYLE version control. STYLE is either 'simple', 'numbered', or 'existing'. -B PREFIX --prefix=PREFIX Prepend PREFIX to backup file names. -Y PREFIX --basename-prefix=PREFIX Prepend PREFIX to backup file basenames. -z SUFFIX --suffix=SUFFIX Append SUFFIX to backup file names. -g NUM --get=NUM Get files from RCS etc. if positive; ask if negative. Miscellaneous options: -t --batch Ask no questions; skip bad-Prereq patches; assume reversed. -f --force Like -t, but ignore bad-Prereq patches, and assume unreversed. -s --quiet --silent Work silently unless an error occurs. --verbose Output extra information about the work being done. --dry-run Do not actually change any files; just print what would happen. --posix Conform to the POSIX standard. -d DIR --directory=DIR Change the working directory to DIR first. --binary Read and write data in binary mode (no effect on this platform). -v --version Output version info. --help Output this help. Report bugs to <bug-patch@gnu.org>. Thanks. I use your command. Terminal results: can't find file to patch at input line 5 Link to comment Share on other sites More sharing options...
Il Francy MacPc Posted October 8, 2017 Share Posted October 8, 2017 So I'm not alone in this exactly. with OsxAptioFixDrv-64.efi 0x67 ok and in I need to boot with 0x0 I must change to OsxAptioFix2Drv-64.efi Take a look at: #7 and #13 and #8 Link to comment Share on other sites More sharing options...
mhaeuser Posted October 8, 2017 Share Posted October 8, 2017 All Clover versions will not load kexts from 10.13 if the system reported 10.12. // version in boot.efi appears as "Mac OS X 10.?" Don't rely on the protocol called by boot.efi, its output is often useless. Link to comment Share on other sites More sharing options...
Guest ricoc90 Posted October 8, 2017 Share Posted October 8, 2017 Thanks. I use your command. Terminal results: can't find file to patch at input line 5[/size] cd ~/src/edk2/Clover/rEFIt_UEFI/refit patch -i /path/to/4243.diff Link to comment Share on other sites More sharing options...
MICKHAEL Posted October 8, 2017 Share Posted October 8, 2017 Take a look at: #7 and #13 and #8 dirty RAM? don't know.. tried and tried .. you say I could use AptioFix2 in 0x67 and 0x0 mode? Link to comment Share on other sites More sharing options...
Cyberdevs Posted October 8, 2017 Share Posted October 8, 2017 Take a look at: #7 and #13 and #8 Thanks Link to comment Share on other sites More sharing options...
Matgen84 Posted October 8, 2017 Share Posted October 8, 2017 I have checked my 10.13 installers boot.efi and they shown as 10.12 (created from 10.12 with createinstallmedia), which is bad. Please try this patch (added dbg infos + comment out (Entry->LoaderType == OSTYPE_OSX_INSTALLER) here). Temporarily install mandatory kexts in /L/E/ with CSR_ALLOW_UNTRUSTED_KEXTS so you are able to reach the desktop. ** In xnu-4570.1.46 #define CSR_ALLOW_UNAPPROVED_KEXTS (1 << 9) @cecekpawon Thanks. Great Job Prebootlog from USB Installer 10.13: good 'GetOSversion'. USB Pendrive can boot with using kext management for 10.13 and Other older. Sorry for my english cd ~/src/edk2/Clover/rEFIt_UEFI/refit patch -i /path/to/4243.diff @ricoc93 Thanks for your help preboot_clover_r4244_USBInstaller.log.zip 1 Link to comment Share on other sites More sharing options...
apianti Posted October 8, 2017 Share Posted October 8, 2017 Stop changing SIP. Jesus, you guys are so weird. "I don't understand when I enable restricted access to secure resources I can't access that resource anymore." So stop. Here's what's happening, AptioFix MOVES tables around in memory, AptioFix2 marks them as unmovable memory mapped IO space. Neither approach works 100% for every one, so you need to use the one that works, AptioFix2 should be used because it has a better approach but also it has a much higher rate of failure (and a bug relating to allocation that no one seems to be able to find). Now, if you use AptioFix, then you NEED to have SIP config set to at least 0x67, whatever for AptioFix2, it shouldn't be affected if its working. So in other words it's a matter of the mechanism that is being used to prevent the OS from doing crazy stuff to your tables. AptioFix needs to be able to move the tables (this also probably breaks NVRAM that is SMM locked), so you can't enable restrictions in SIP because they will prevent the moving from being useful... 8 Link to comment Share on other sites More sharing options...
Cyberdevs Posted October 8, 2017 Share Posted October 8, 2017 Stop changing SIP. Jesus, you guys are so weird. "I don't understand when I enable restricted access to secure resources I can't access that resource anymore." So stop. Here's what's happening, AptioFix MOVES tables around in memory, AptioFix2 marks them as unmovable memory mapped IO space. Neither approach works 100% for every one, so you need to use the one that works, AptioFix2 should be used because it has a better approach but also it has a much higher rate of failure (and a bug relating to allocation that no one seems to be able to find). Now, if you use AptioFix, then you NEED to have SIP config set to at least 0x67, whatever for AptioFix2, it shouldn't be affected if its working. So in other words it's a matter of the mechanism that is being used to prevent the OS from doing crazy stuff to your tables. AptioFix needs to be able to move the tables (this also probably breaks NVRAM that is SMM locked), so you can't enable restrictions in SIP because they will prevent the moving from being useful... With all due respect Sir, Being weird doesn't even being to describe us (Me) We all like to look around and change things and install macOS on our PCs, we like to play with things that aren't supposed to played with (I'm talking about myself no offense to our fellow members). But sometimes lack of knowledge will complicate things and that's why we are here (I guess) to learn more and seek for help (I'm talking about myself again) But none the less thanks a lot for you clear and complete answer as always. Cheers 4 Link to comment Share on other sites More sharing options...
Badruzeus Posted October 8, 2017 Share Posted October 8, 2017 .... Cheers ... also sorry, @cyberdev.. we may better play "safe" on this, I've deleted my prev. post about SIP: Enabled and give a clear note that I'm using "Legacy". Thanks. Link to comment Share on other sites More sharing options...
Guest ricoc90 Posted October 8, 2017 Share Posted October 8, 2017 We all like to look around and change things and install macOS on our PCs, we like to play with things that aren't supposed to played with [...] But sometimes lack of knowledge will complicate things and that's why we are here (I guess) to learn more and seek for help +1 I like to learn. I like to figure things out and I like to see the connections between a and b. For that, you'll need to play and experiment a little, since that's the way to knowledge. Link to comment Share on other sites More sharing options...
Cyberdevs Posted October 8, 2017 Share Posted October 8, 2017 ... also sorry, @cyberdev.. we may better play "safe" on this, I've deleted my prev. post about SIP: Enabled and give a clear note that I'm using "Legacy". Thanks. I'm sorry, my friend but I don't quite understand what you mean by "we may better play safe". +1 I like to learn. I like to figure things out and I like to see the connections between a and b. For that, you'll need to play and experiment a little, since that's the way to knowledge. I totally agree, not knowing something created a need for asking questions and therefor science was born This is the whole point of experimenting with macOS and PCs. If I wanted to play safe I would have bought an iMac or a MacPro. Let's not get carried away and stay on topic 2 Link to comment Share on other sites More sharing options...
Recommended Posts