btwise Posted February 25, 2020 Share Posted February 25, 2020 8 minutes ago, eng_redaesm said: @btwise and @Awesome Donkey For your information latest opencore upstream is working with NDKbootpicker release 11 (the problem with rel 12) except one issue custom entries is vanished so i revered back to older stream Yes, with the original OC+GUI, the custom WINDOWS entry will still appear in the first entry, if you press the space, the custom WINDOWS and the scanned WINDOWS will appear at the same time, but with the FORK, you won't have this problem! Link to comment Share on other sites More sharing options...
mhaeuser Posted February 25, 2020 Share Posted February 25, 2020 *sigh* This is not about admiting a bug, it's just likely not our bug again. The password code has been updated and likely you have not recompiled the GUI to correct the call (-> invalid memory access). If we got a proper report with exact info and logs, that'd help over "does not work, muh fix" for when it is fine for all known testers. Link to comment Share on other sites More sharing options...
eng_redaesm Posted February 25, 2020 Share Posted February 25, 2020 @n.d.k the problem of the password issue i can confirm started with latest OC upstream after adding the option Miss->boot->pickeraudioassist with Ndkbootpicker release 12 but with ndkbootpicker release 11 latest OC upstream working but without custom entries 1 Link to comment Share on other sites More sharing options...
n.d.k Posted February 25, 2020 Author Share Posted February 25, 2020 (edited) 1 hour ago, eng_redaesm said: @n.d.k the problem of the password issue i can confirm started with latest OC upstream after adding the option Miss->boot->pickeraudioassist with Ndkbootpicker release 12 but with ndkbootpicker release 11 latest OC upstream working but without custom entries NdkBootPicker.efi 0.1.2 binary has been recompiled and updated to reflect OcInterface revision bump to 2. All audio features has not yet implemented on NdkBootPicker.efi. And for those who has trouble compiling the source, please do a fresh git clone and compile before reporting here. All new commits are always compiled successfully before pushed out to github. Keep in mind, when trying out the new features or any changes that just landed, bugs are expected!. Edited February 25, 2020 by n.d.k 1 1 Link to comment Share on other sites More sharing options...
eng_redaesm Posted February 25, 2020 Share Posted February 25, 2020 1 hour ago, n.d.k said: NdkBootPicker.efi 0.1.2 binary has been recompiled and updated to reflect OcInterface revision bump to 2. All audio features has not yet implemented on NdkBootPicker.efi. And for those who has trouble compiling the source, please do a fresh git clone and compile before reporting here. All new commits are always compiled successfully before pushed out to github. Keep in mind, when trying out the new features or any changes that just landed, bugs are expected!. @n.d.k you are a star thanks i confirm now working like a charm thank you Link to comment Share on other sites More sharing options...
Awesome Donkey Posted February 25, 2020 Share Posted February 25, 2020 I did a clean build of the latest upstream OpenCore commit, and the password thing still happens. Only thing I retained from the OC fork was my config.plist file, so I'm thinking it's probably cause by an option or a combination of options set in config.plist. When I get some time, I'll start turning options off to see if I can narrow down which option(s) seem to be causing it. 2 Link to comment Share on other sites More sharing options...
cpla Posted February 25, 2020 Share Posted February 25, 2020 (edited) Yeah same here, tried with the default oc + ndkbootpicker and was getting the password thing still, reverted to an older version from 2 days ago or so for now. Tried changing some stuff and checking the sample config but everything seemed to match so dunno. Edited February 25, 2020 by cpla 1 Link to comment Share on other sites More sharing options...
btwise Posted February 26, 2020 Share Posted February 26, 2020 @下载-Fritz@ndk,Yes, the password prompt has not been fixed！！ 1 Link to comment Share on other sites More sharing options...
Andrey1970 Posted February 26, 2020 Share Posted February 26, 2020 8 hours ago, n.d.k said: All audio features has not yet implemented on NdkBootPicker.efi. Support of the voice assistant is present in official OpenCore. What do you want to do on another? BootChimeDxe.efi isn't required for OpenCore, Chime is implemented in OpenCore. Therefore isn't necessary this note. 1 Link to comment Share on other sites More sharing options...
mhaeuser Posted February 26, 2020 Share Posted February 26, 2020 @btwise Provide a vanilla(!) OC (without this GUI) folder with logs with the bug happening, preferably on the bugtracker: https://github.com/acidanthera/bugtracker/issues/737 Link to comment Share on other sites More sharing options...
n.d.k Posted February 26, 2020 Author Share Posted February 26, 2020 3 hours ago, Andrey1970 said: Support of the voice assistant is present in official OpenCore. What do you want to do on another? What I meant is all audio functions which OC just implemented are not yet working with NdkBootPicker.efi. Link to comment Share on other sites More sharing options...
btwise Posted February 26, 2020 Share Posted February 26, 2020 3 minutes ago, n.d.k said: What I meant is all audio functions which OC just implemented are not yet working with NdkBootPicker.efi. How do I get rid of the "Password:" prompt? Link to comment Share on other sites More sharing options...
n.d.k Posted February 26, 2020 Author Share Posted February 26, 2020 (edited) 49 minutes ago, btwise said: How do I get rid of the "Password:" prompt? You misconfigure somewhere...i never seen a password prompt... remove the EnablePassword key if you have it in your config.plist. Edited February 26, 2020 by n.d.k Link to comment Share on other sites More sharing options...
btwise Posted February 26, 2020 Share Posted February 26, 2020 28 minutes ago, n.d.k said: You misconfigure somewhere...i never seen a password prompt... remove the EnablePassword key if you have it in your config.plist. The configuration file has not been changed except for the addition of new options, and many people have encountered this problem, why do you all say that you have not encountered it, strange! Link to comment Share on other sites More sharing options...
btwise Posted February 26, 2020 Share Posted February 26, 2020 44 minutes ago, n.d.k said: You misconfigure somewhere...i never seen a password prompt... remove the EnablePassword key if you have it in your config.plist. The upstream of this problem seems to have been fixed, please synchronize Link to comment Share on other sites More sharing options...
matgeo Posted February 26, 2020 Share Posted February 26, 2020 Pawword thing still exists with latest commits. There is no EnablePassword option anywhere to disable. Link to comment Share on other sites More sharing options...
btwise Posted February 26, 2020 Share Posted February 26, 2020 50 minutes ago, matgeo said: Pawword thing still exists with latest commits. There is no EnablePassword option anywhere to disable. The n.d.k has been updated synchronously just now, please recompile it 1 Link to comment Share on other sites More sharing options...
Matgen84 Posted February 26, 2020 Share Posted February 26, 2020 (edited) 4 hours ago, btwise said: The n.d.k has been updated synchronously just now, please recompile it Right, password issue is solved with latest commit sync upstream But strangely, my custom entry (Windows 10) don't work anymore: Halting on critical error . Any ideas! <key>Entries</key> <array> <dict> <key>Arguments</key> <string></string> <key>Auxiliary</key> <false/> <key>Comment</key> <string>Not signed for security reasons</string> <key>Enabled</key> <true/> <key>Name</key> <string>Windows 10</string> <key>Path</key> <string>PciRoot(0x0)/Pci(0x17,0x0)/Sata(0x2,0xFFFF,0x0)/HD(2,GPT,F15186C6-F501-4C1C-9BCF-990FF40BB10D,0x109000,0x31800)/\EFI\Microsoft\Boot\bootmgfw.efi</string> </dict> </array> SOLVED: I forget to rename Windows icons to os_win10.icns in Icons folder. Edited February 26, 2020 by Matgen84 2 Link to comment Share on other sites More sharing options...
matgeo Posted February 26, 2020 Share Posted February 26, 2020 Can someone please explain the values of : a) under debug DisplayDelay DisplayLevel Target b) under Security ExposeSensitiveData ScanPolicy Link to comment Share on other sites More sharing options...
n.d.k Posted February 26, 2020 Author Share Posted February 26, 2020 Ok, everything is updated with upstream, new OC audio things are in both This fork and NdkBootPicker driver. 4 Link to comment Share on other sites More sharing options...
cpla Posted February 26, 2020 Share Posted February 26, 2020 Yeah all good here with the latest upstream + ndkbootpicker at least, going to compile the newest version of the fork again and switch back to it. 1 Link to comment Share on other sites More sharing options...
btwise Posted February 26, 2020 Share Posted February 26, 2020 If I keep pressing the ESC key in the GUI interface, this will happen! Link to comment Share on other sites More sharing options...
Awesome Donkey Posted February 26, 2020 Share Posted February 26, 2020 (edited) No more password issue here either using the latest built commit of the customized fork, YAY! 5 hours ago, Matgen84 said: SOLVED: I forget to rename Windows icons to os_win10.icns in Icons folder. Icons not named correctly causing an OS not to boot due to a critical error sounds like a potential bug to me, IMO. At the very least if an icon is missing or not named correctly the OC fork should ignore it and allow it to boot without the critical error. 3 minutes ago, btwise said: If I keep pressing the ESC key in the GUI interface, this will happen! Can confirm this. You can 'fix' it by pressing the spacebar a couple of times and it'll reset back to normal. Edited February 26, 2020 by Awesome Donkey 1 Link to comment Share on other sites More sharing options...
Matgen84 Posted February 26, 2020 Share Posted February 26, 2020 (edited) 53 minutes ago, Awesome Donkey said: Icons not named correctly causing an OS not to boot due to a critical error sounds like a potential bug to me, IMO. At the very least if an icon is missing or not named correctly the OC fork should ignore it and allow it to boot without the critical error. Absolutely. I'm agree with you. This issue doesn't exist in Clover, if I remember well. I think that @n.d.k found the solution for OC fork and NDKBootPicker. Edited February 26, 2020 by Matgen84 Link to comment Share on other sites More sharing options...
talebabatto Posted February 26, 2020 Share Posted February 26, 2020 Can confirm password issue is not an issue anymore with the last build. Has anything changed about custom entries? I cannot boot into windows 10 anymore or being more specific now I have a Bootcamp windows option in boot menu but instead of booting Windows it boots my linux partition. I set as usual a new entry under Misc-->Entries, the path is correct checked through shell and clover boot loader. While the other entry that is named Pop_OS! linux doesn't work at all. Maybe I wrote the wrong path the device is correct then \EFI\BOOT\BOOTX64.EFI Oh and now the default mode is showing all the optional entries. Need to press spacebar to hide. Thank you Link to comment Share on other sites More sharing options...
Recommended Posts