Pene Posted April 3, 2020 Share Posted April 3, 2020 (edited) 20 minutes ago, Awesome Donkey said: Interesting, I can boot both Windows 10 and Arch Linux through this OC fork with OpenRuntime enabled with no issues observed. It depends on the specific firmware. Not all need this. Take a look at: https://github.com/acidanthera/bugtracker/issues/491 Edited April 3, 2020 by Pene Link to comment Share on other sites More sharing options...
crusher Posted April 3, 2020 Share Posted April 3, 2020 (edited) 1 hour ago, Pene said: It depends on the specific firmware. Not all need this. Take a look at: https://github.com/acidanthera/bugtracker/issues/491 Why u dont add comment on bugtracker to say what u think how to fix? Edited April 3, 2020 by crusher Link to comment Share on other sites More sharing options...
Matgen84 Posted April 3, 2020 Share Posted April 3, 2020 5 minutes ago, crusher said: Why u dont add comment on bugtracker to say what u think how to fix? Because @Pene is already register with another pseudo Link to comment Share on other sites More sharing options...
crusher Posted April 3, 2020 Share Posted April 3, 2020 1 minute ago, Matgen84 said: Because @Pene is already register with another pseudo which? Link to comment Share on other sites More sharing options...
Matgen84 Posted April 3, 2020 Share Posted April 3, 2020 1 minute ago, crusher said: which? Ask him, bro. Link to comment Share on other sites More sharing options...
crusher Posted April 3, 2020 Share Posted April 3, 2020 1 minute ago, Matgen84 said: Ask him, bro. Ok we wait him!! 1 Link to comment Share on other sites More sharing options...
Pene Posted April 3, 2020 Share Posted April 3, 2020 (edited) 1 hour ago, crusher said: Why u dont add comment on bugtracker to say what u think how to fix? What? You are confusing some things. The thread was for a firmware bug belonging to investigations in Mainline OpenCore, which is already partially addressed. I posted a link just for who was interested in more details. It is in the works, and a solution is being implemented (also, in mainline OpenCore). My comment here was a suggestion for ndk, to make some changes in his form to allow the solution implemented in mainline OpenCore to run on this fork as well. These are two different things. Edit: some corrections Edited April 3, 2020 by Pene 1 Link to comment Share on other sites More sharing options...
crusher Posted April 3, 2020 Share Posted April 3, 2020 5 minutes ago, Pene said: What? You are confusing some things. The thread was for a bug in Mainline OpenCore, which is already partially addressed. I posted a link just for who was interested in more details. It is in the works, and a solution is being implemented (also, in mainline OpenCore). My comment here was a suggestion for ndk, to make some changes in his form to allow the solution implemented in mainline OpenCore to run on this fork as well. These are two different things. I know and this is reason why I ask u to give ur comment on bugtracker. Cuz I know your knowledge. 1 1 Link to comment Share on other sites More sharing options...
mhaeuser Posted April 3, 2020 Share Posted April 3, 2020 27 minutes ago, Pene said: The thread was for a bug in Mainline OpenCore, which is already partially addressed. There was and is no bug in OC, I'm afraid it's entirely firmware bugs of different iterations. The spec does not mandate Runtime Drivers to be aligned by 4 KB, this is a security feature requirements. 21 minutes ago, crusher said: I know and this is reason why I ask u to give ur comment on bugtracker. Cuz I know your knowledge. N-D-K issues belong to the N-D-K thread and not to our bugtracker. Link to comment Share on other sites More sharing options...
Pene Posted April 3, 2020 Share Posted April 3, 2020 (edited) 4 minutes ago, Download-Fritz said: There was and is no bug in OC, I'm afraid it's entirely firmware bugs of different iterations. The spec does not mandate Runtime Drivers to be aligned by 4 KB, this is a security feature requirements. N-D-K issues belong to the N-D-K thread and not to our bugtracker. Exactly, you put it better. That's what I was trying to say - that the issue with the firmware bug belongs to mainline OpenCore and ndk issue does not Unfortunately that is a side effect of forks, sometimes people don't realize what belongs where. I was trying to say that the two are unrelated. I agree that "bug" was the wrong word though Edited April 3, 2020 by Pene 2 Link to comment Share on other sites More sharing options...
crusher Posted April 3, 2020 Share Posted April 3, 2020 3 minutes ago, Download-Fritz said: N-D-K issues belong to the N-D-K thread and not to our bugtracker. I know DF this is reason why ask Pene to give propose for fix Windows. I send mail to u several days ago. Link to comment Share on other sites More sharing options...
mhaeuser Posted April 3, 2020 Share Posted April 3, 2020 2 minutes ago, crusher said: I know DF this is reason why ask Pene to give propose for fix Windows. I send mail to u several days ago. There is nothing to be fixed, your ACPI is borked, and you need to fix it, as you were told before on the forums. The answer will not change if you mail several people individually. 2 Link to comment Share on other sites More sharing options...
n.d.k Posted April 4, 2020 Author Share Posted April 4, 2020 12 hours ago, Pene said: Hi @n.d.k Currently your fork restricts OcLoadBooterUefiSupport to only Mac OS X booting. This is not really right anymore, as some quirks (the most obvious example being the recently introduced SyncRuntimePermissions) are actually meant to fix Linux (or Windows) booting when OpenRuntime is present. For example, I cannot boot Linux without it with OpenRuntime loaded. When OpenRuntime gets loaded, it already replaces GetVariable(), SetVariable(), and some other RunTime services in the firmware, so some quirks are needed on some firmware to fix the resulting issues. If you wish to be able to control this, I think you should probably introduce an EnableForAll quirk also for Booter section (currently it exists only for Acpi). Optional Booter->Quirks->EnableForAll has been added to the fork in recent commit, default is NO. 2 1 Link to comment Share on other sites More sharing options...
eSaF Posted April 5, 2020 Share Posted April 5, 2020 (edited) Hi guys I know this is probably a big ask, but can some one look through my Opencore EFI Folder and make any necessary corrections or additions so that I can use NDK's OC version with a Boot Menu of my choosing minus the verbose readout. I chose to build the EFI plus all relevant files based on my setup instead of using a ready made one floating around the forum. As It stands at the moment it loads and boots much faster than my Clover setup, but the Boot Menu in it's simplicity is not to my liking. I have tried numerous times to convert it to NDK's fork but it always boots to the bland readout interface, I have removed all relevant sensitive info from the config.plist - Thanks. P.S - I am dual booting with win10. EFI.zip Edited April 5, 2020 by eSaF Link to comment Share on other sites More sharing options...
AudioGod Posted April 5, 2020 Share Posted April 5, 2020 1 hour ago, eSaF said: Hi guys I know this is probably a big ask, but can some one look through my Opencore EFI Folder and make any necessary corrections or additions so that I can use NDK's OC version with a Boot Menu of my choosing minus the verbose readout. I chose to build the EFI plus all relevant files based on my setup instead of using a ready made one floating around the forum. As It stands at the moment it loads and boots much faster than my Clover setup, but the Boot Menu in it's simplicity is not to my liking. I have tried numerous times to convert it to NDK's fork but it always boots to the bland readout interface, I have removed all relevant sensitive info from the config.plist - Thanks. P.S - I am dual booting with win10. EFI.zip Check your inbox 1 Link to comment Share on other sites More sharing options...
AudioGod Posted April 5, 2020 Share Posted April 5, 2020 (edited) 4 minutes ago, meaganmargaret said: So, I reported earlier that Linux wasn't booting, and then I downloaded and compiled the latest NDK fork (this morning), but now Windows is not booting. Mac and Linux works, but Windows does not. It looks like issues with OpenRuntime are the source of the issue.....I saw a recent post in the bugtracker that it was fixed on the main Opencore release. So, @NDK have you updated your fork with this change? @meaganmargaret go into the plist and under the booter quirks set EnableForAll to Yes and you might need to set the quirks up like so too. Edited April 5, 2020 by AudioGod 1 Link to comment Share on other sites More sharing options...
AudioGod Posted April 5, 2020 Share Posted April 5, 2020 Just now, meaganmargaret said: AudioGod, you are a star! Thanks! Your welcome, Happy to help 1 Link to comment Share on other sites More sharing options...
eSaF Posted April 6, 2020 Share Posted April 6, 2020 13 hours ago, AudioGod said: Check your inbox Iv'e already PM you, but just wanted to report here - Brilliant work as usual and problem solved perfectly, my humble thanks as always. 1 Link to comment Share on other sites More sharing options...
eSaF Posted April 6, 2020 Share Posted April 6, 2020 (edited) 22 minutes ago, IDON-NO said: Can you share the changes please ? I am in the same situation Thanks I don't know if the files will be any good for you unless you'll use them for comparison only as we have different chipset boards judging from what is listed in your signature. It is best to upload your OC EFI Folder and ask AG to have a look, nevertheless I've attached the Folders. Good luck. Edited April 6, 2020 by eSaF 1 Link to comment Share on other sites More sharing options...
eSaF Posted April 6, 2020 Share Posted April 6, 2020 @ Meganmargaret 12 hours ago, meaganmargaret said: AudioGod, you are a star! Thanks! The guy is just awesome @ Meganmargaret 12 hours ago, meaganmargaret said: AudioGod, you are a star! Thanks! The guy is just awesome Link to comment Share on other sites More sharing options...
foster Posted April 7, 2020 Share Posted April 7, 2020 (edited) How do I compile opencore so it does the GUI interface not text one. Every time I compile or build from source I loose GUI, unless I use this fork. Edited April 7, 2020 by foster Link to comment Share on other sites More sharing options...
Matgen84 Posted April 7, 2020 Share Posted April 7, 2020 24 minutes ago, foster said: How do I compile opencore so it does the GUI interface not text one. Every time I compile or build from source I loose GUI, unless I use this fork. You must use ndkbootpicker.efi (put it in EFI/OC/Drivers, declare it drivers section to your config.plist), put Icons folder to EFI/OC. In config.plist, type external instead of builtin (PickerMode). If I remember well. Link to comment Share on other sites More sharing options...
MorenoAv Posted April 7, 2020 Share Posted April 7, 2020 Hi guys, Finally after various tries and error's I have finally install macOS Catalina 10.15.4 with OpenCore, but like so many others I don't like the simplicity of the boot menu from the regular build and I wanted to change to this n-d-k fork but until this moment I can't, could anyone of you take a look at my EFI, and point me to the right direction to make it work? Thanks in Advance EFI.zip Link to comment Share on other sites More sharing options...
kaoskinkae Posted April 7, 2020 Share Posted April 7, 2020 How can the system say that it always starts with the SSD Catalina and not with the HDD Catalina that it sets as the start. I Have two systems and always set me the HDD Catalina as Link to comment Share on other sites More sharing options...
n.d.k Posted April 7, 2020 Author Share Posted April 7, 2020 4 hours ago, MorenoAv said: Hi guys, Finally after various tries and error's I have finally install macOS Catalina 10.15.4 with OpenCore, but like so many others I don't like the simplicity of the boot menu from the regular build and I wanted to change to this n-d-k fork but until this moment I can't, could anyone of you take a look at my EFI, and point me to the right direction to make it work? Thanks in Advance EFI.zip Hi MorenoAv, If you have your OC working, All you have to do is replacing the BOOTx64.efi and OpenCore.efi with the one from this fork and copy the Icons folder to EFI\OC folder. And if you want to use Original OC and like the look of boot picker from this fork, you can just download the NdkBootPicker.efi and use it as driver. 3 hours ago, kaoskinkae said: How can the system say that it always starts with the SSD Catalina and not with the HDD Catalina that it sets as the start. I Have two systems and always set me the HDD Catalina as You need to set SSD Catalina as default boot drive by simply hold down your option key while click HDD Catalina Icon, your next boot will be default to HDD Catalina. (you need to set AllowSetDefault to YES in your config.plist) or you use mac preference startup disk to set default boot drive as well. 3 Link to comment Share on other sites More sharing options...
Recommended Posts