vit9696 Posted June 25, 2020 Share Posted June 25, 2020 Initial set of patches for 11 is pushed to master. @btwise, that's Google domain, I strongly doubt it is down. Try calling your ISP support. If you think it is not your ISP, then ask Google or Tianocore. Our UDK is just a mirror of tianocore/edk2. 2 3 Link to comment Share on other sites More sharing options...
vit9696 Posted June 25, 2020 Share Posted June 25, 2020 @MacNB, try editing LogoutHook.command by replacing: getKey "8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Boot0080" > Boot0080 getKey "efi-boot-device-data" > efi-boot-device-data if [ -n "$(/usr/bin/hexdump "Boot0080" )" ] && [ -n "$(/usr/bin/hexdump "efi-boot-device-data" )" ]; then /bin/dd seek=24 if=efi-boot-device-data of=Boot0080 bs=1 count="$(/usr/bin/stat -f%z efi-boot-device-data)" || abort "Failed to fill Boot0080 with efi-boot-device-data!" /usr/libexec/PlistBuddy -c "Import Add:8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Boot0080 Boot0080" ./nvram.plist || abort "Failed to import Boot0080!" fi with: getKey "8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Boot0080" > Boot0080 if [ -n "$(/usr/bin/hexdump "Boot0080" )" ]; then /usr/libexec/PlistBuddy -c "Import Add:8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Boot0080 Boot0080" ./nvram.plist || abort "Failed to import Boot0080!" fi Please note, that insanely often borks text, so better do not copy-paste from here. Just delete the relevant parts. 1 Link to comment Share on other sites More sharing options...
SavageAUS Posted June 25, 2020 Share Posted June 25, 2020 Initial set of patches for 11 is pushed to master. [mention=88369]btwise[/mention], that's Google domain, I strongly doubt it is down. Try calling your ISP support. If you think it is not your ISP, then ask Google or Tianocore. Our UDK is just a mirror of tianocore/edk2.Great work on the 11 patches. Does this mean we should be able to get Big Sur running with OC now?Sent from my iPhone using Tapatalk 1 Link to comment Share on other sites More sharing options...
Common_Sense Posted June 25, 2020 Share Posted June 25, 2020 I checked some config.plist examples for Open Core and I see people are specifying in the config.plist file what EFI drivers and KEXTs they are using, is this mandatory or can I just copy the EFI files and KEXTs to their respective directory and skip specifying them manually i config.plist? Link to comment Share on other sites More sharing options...
SavageAUS Posted June 25, 2020 Share Posted June 25, 2020 I checked some config.plist examples for Open Core and I see people are specifying in the config.plist file what EFI drivers and KEXTs they are using, is this mandatory or can I just copy the EFI files and KEXTs to their respective directory and skip specifying them manually i config.plist? For OpenCore Kexts, drivers and tools need to be in config.plist and in the correct order. Read guides (dortania) and check out propertree. Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
MacNB Posted June 25, 2020 Share Posted June 25, 2020 1 hour ago, vit9696 said: @MacNB, try editing LogoutHook.command by replacing: getKey "8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Boot0080" > Boot0080 getKey "efi-boot-device-data" > efi-boot-device-data if [ -n "$(/usr/bin/hexdump "Boot0080" )" ] && [ -n "$(/usr/bin/hexdump "efi-boot-device-data" )" ]; then /bin/dd seek=24 if=efi-boot-device-data of=Boot0080 bs=1 count="$(/usr/bin/stat -f%z efi-boot-device-data)" || abort "Failed to fill Boot0080 with efi-boot-device-data!" /usr/libexec/PlistBuddy -c "Import Add:8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Boot0080 Boot0080" ./nvram.plist || abort "Failed to import Boot0080!" fi with: getKey "8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Boot0080" > Boot0080 if [ -n "$(/usr/bin/hexdump "Boot0080" )" ]; then /usr/libexec/PlistBuddy -c "Import Add:8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Boot0080 Boot0080" ./nvram.plist || abort "Failed to import Boot0080!" fi Please note, that insanely often borks text, so better do not copy-paste from here. Just delete the relevant parts. Yeh ! That fixed the Default Boot setting. Great teamwork you guys. Thanks. I made the suggested mod & rebooted. Bootpicker now shows a "*" against the default boot drive. Here's the log dump looking correct : 01:394 00:002 OCB: MacNB: InternalDebugBootEnvironment: IN BootGuid == 8BE4DF61-93CA-11D2-AA0D-00E098032B8C 01:396 00:001 OCB: efi-boot-device-data = PciRoot(0x1)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0)/HD(2,GPT,829755CD-439B-46B8-944E-B377F33FCF5F,0x64028,0x116940B8) 01:398 00:001 OCB: efi-backup-boot-device-data - Not Found 01:400 00:001 OCB: efi-apple-recovery-data - Not Found 01:402 00:001 OCB: Dumping BootOrder 01:405 00:002 OCB: MacNB: InternalGetBootOptionData: Post GetVariable2 call. Status == Success 01:407 00:001 OCB: 0 -> Boot0080 = PcieRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0)/HD(2,GPT,829755CD-439B-46B8-944E-B377F33FCF5F,0x64028,0x116940B8)/\System\Library\CoreServices\boot.efi 01:409 00:001 OCB: MacNB: InternalGetBootOptionData: Post GetVariable2 call. Status == Success 01:411 00:001 OCB: 1 -> Boot0000 = PcieRoot(0x0)/Pci(0x1D,0x7)/USB(0x4,0x0)/Unit(0x0) 01:413 00:001 OCB: MacNB: InternalGetBootOptionData: Post GetVariable2 call. Status == Success 01:416 00:002 OCB: 2 -> Boot0001 = PcieRoot(0x0)/Pci(0x1D,0x7)/USB(0x4,0x0)/Unit(0x1) 01:418 00:001 OCB: MacNB: InternalGetBootOptionData: Post GetVariable2 call. Status == Success 01:420 00:001 OCB: 3 -> Boot0002 = PcieRoot(0x0)/Pci(0x1D,0x7)/USB(0x4,0x0)/Unit(0x2) 01:422 00:001 OCB: MacNB: InternalGetBootOptionData: Post GetVariable2 call. Status == Success 01:425 00:002 OCB: 4 -> Boot0003 = PcieRoot(0x0)/Pci(0x1D,0x7)/USB(0x4,0x0)/Unit(0x3) 01:427 00:001 OCB: MacNB: InternalGetBootOptionData: Post GetVariable2 call. Status == Success 01:429 00:001 OCB: 5 -> Boot0004 = PcieRoot(0x0)/Pci(0x1F,0x2)/Sata(0x4,0x0,0x0) 01:430 00:001 OCB: MacNB: InternalGetBootOptionData: Post GetVariable2 call. Status == Success 01:432 00:001 OCB: 6 -> Boot0005 = PcieRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0) 01:435 00:002 OCB: MacNB: InternalGetBootOptionData: Post GetVariable2 call. Status == Success 01:437 00:001 OCB: 7 -> Boot0006 = PcieRoot(0x0)/Pci(0x1F,0x2)/Sata(0x1,0x0,0x0) 01:439 00:001 OCB: MacNB: InternalGetBootOptionData: Post GetVariable2 call. Status == Success 01:441 00:001 OCB: 8 -> Boot0007 = PcieRoot(0x0)/Pci(0x1F,0x2)/Sata(0x5,0x0,0x0) 01:444 00:002 OCB: Parsing predefined list... 01:446 00:001 OCB: MacNB: InternalGetBootOptionData: Post GetVariable2 call. Status == Success 01:448 00:002 OCB: 0 -> Boot0080 = PcieRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0)/HD(2,GPT,829755CD-439B-46B8-944E-B377F33FCF5F,0x64028,0x116940B8)/\System\Library\CoreServices\boot.efi 01:450 00:001 OCB: MacNB: InternalGetBootOptionData: Post GetVariable2 call. Returning NULL. Status == Not Found 01:452 00:001 OCB: 1 -> Boot0081 - failed to read 01:455 00:002 OCB: MacNB: InternalGetBootOptionData: Post GetVariable2 call. Returning NULL. Status == Not Found 01:457 00:001 OCB: 2 -> Boot0082 - failed to read 01:459 00:001 OCB: Building entry from Boot0080 01:461 00:001 OCB: MacNB: InternalGetBootOptionData: Post GetVariable2 call. Status == Success 01:464 00:003 OCB: Fixed DP - PcieRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0)/HD(2,GPT,829755CD-439B-46B8-944E-B377F33FCF5F,0x64028,0x116940B8)/\System\Library\CoreServices\boot.efi 01:466 00:001 OCB: Assuming DP is full-form or lacks suffix 01:468 00:001 OCB: Expanded DP - PcieRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0)/HD(2,GPT,829755CD-439B-46B8-944E-B377F33FCF5F,0x64028,0x116940B8)/\System\Library\CoreServices\boot.efi 01:470 00:002 OCB: Expanded DP remainder - \System\Library\CoreServices\boot.efi 01:472 00:001 OCB: Matched fs AE434798 01:477 00:005 OCB: Adding entry type (T:2|F:0|G:0) - PcieRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0)/HD(2,GPT,829755CD-439B-46B8-944E-B377F33FCF5F,0x64028,0x116940B8)/\System\Library\CoreServices\boot.efi 01:479 00:001 OCB: Trying to get label from \System\Library\CoreServices\.contentDetails Also attached the modified logouthook.command just in case someone needs a fix in the mean time. Can I assume that this will also work during macOS Updates (when the installer changes the default boot drive to "Boot from macOS Install..." ?? Now...onto the next issue I reported here for Legacy systems...the boot file installed installed by OC BootInstall.command does not detect any SATA on my system. I have been using "another" one I mentioned but prefer to use OC's. Let me me know how I can help debug that one ?? LogoutHook.command 2 Link to comment Share on other sites More sharing options...
REKTIMU2 Posted June 25, 2020 Share Posted June 25, 2020 16 hours ago, sudoali said: I have one question about using `-l` flag, would the bytecode for a specific method be changed if I recompile the .aml file? no, it shouldn't Link to comment Share on other sites More sharing options...
PropoFlexWX4 Posted June 25, 2020 Share Posted June 25, 2020 3 hours ago, SavageAUS said: Great work on the 11 patches. Does this mean we should be able to get Big Sur running with OC now? Sent from my iPhone using Tapatalk I think not quite yet. But relatively soon. Link to comment Share on other sites More sharing options...
MorenoAv Posted June 25, 2020 Share Posted June 25, 2020 (edited) Hi all, today I tried to build new SSDTS from the OpenCore 0.6.0 that I downloaded and it gives me this errors, anyone knows why ? Solved it was the MacIASL that was bad... Edited June 25, 2020 by MorenoAv Link to comment Share on other sites More sharing options...
vit9696 Posted June 25, 2020 Share Posted June 25, 2020 6 hours ago, MacNB said: Yeh ! That fixed the Default Boot setting. Great teamwork you guys. Thanks. I made the suggested mod & rebooted. Bootpicker now shows a "*" against the default boot drive. Here's the log dump looking correct : 01:394 00:002 OCB: MacNB: InternalDebugBootEnvironment: IN BootGuid == 8BE4DF61-93CA-11D2-AA0D-00E098032B8C 01:396 00:001 OCB: efi-boot-device-data = PciRoot(0x1)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0)/HD(2,GPT,829755CD-439B-46B8-944E-B377F33FCF5F,0x64028,0x116940B8) 01:398 00:001 OCB: efi-backup-boot-device-data - Not Found 01:400 00:001 OCB: efi-apple-recovery-data - Not Found 01:402 00:001 OCB: Dumping BootOrder 01:405 00:002 OCB: MacNB: InternalGetBootOptionData: Post GetVariable2 call. Status == Success 01:407 00:001 OCB: 0 -> Boot0080 = PcieRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0)/HD(2,GPT,829755CD-439B-46B8-944E-B377F33FCF5F,0x64028,0x116940B8)/\System\Library\CoreServices\boot.efi 01:409 00:001 OCB: MacNB: InternalGetBootOptionData: Post GetVariable2 call. Status == Success 01:411 00:001 OCB: 1 -> Boot0000 = PcieRoot(0x0)/Pci(0x1D,0x7)/USB(0x4,0x0)/Unit(0x0) 01:413 00:001 OCB: MacNB: InternalGetBootOptionData: Post GetVariable2 call. Status == Success 01:416 00:002 OCB: 2 -> Boot0001 = PcieRoot(0x0)/Pci(0x1D,0x7)/USB(0x4,0x0)/Unit(0x1) 01:418 00:001 OCB: MacNB: InternalGetBootOptionData: Post GetVariable2 call. Status == Success 01:420 00:001 OCB: 3 -> Boot0002 = PcieRoot(0x0)/Pci(0x1D,0x7)/USB(0x4,0x0)/Unit(0x2) 01:422 00:001 OCB: MacNB: InternalGetBootOptionData: Post GetVariable2 call. Status == Success 01:425 00:002 OCB: 4 -> Boot0003 = PcieRoot(0x0)/Pci(0x1D,0x7)/USB(0x4,0x0)/Unit(0x3) 01:427 00:001 OCB: MacNB: InternalGetBootOptionData: Post GetVariable2 call. Status == Success 01:429 00:001 OCB: 5 -> Boot0004 = PcieRoot(0x0)/Pci(0x1F,0x2)/Sata(0x4,0x0,0x0) 01:430 00:001 OCB: MacNB: InternalGetBootOptionData: Post GetVariable2 call. Status == Success 01:432 00:001 OCB: 6 -> Boot0005 = PcieRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0) 01:435 00:002 OCB: MacNB: InternalGetBootOptionData: Post GetVariable2 call. Status == Success 01:437 00:001 OCB: 7 -> Boot0006 = PcieRoot(0x0)/Pci(0x1F,0x2)/Sata(0x1,0x0,0x0) 01:439 00:001 OCB: MacNB: InternalGetBootOptionData: Post GetVariable2 call. Status == Success 01:441 00:001 OCB: 8 -> Boot0007 = PcieRoot(0x0)/Pci(0x1F,0x2)/Sata(0x5,0x0,0x0) 01:444 00:002 OCB: Parsing predefined list... 01:446 00:001 OCB: MacNB: InternalGetBootOptionData: Post GetVariable2 call. Status == Success 01:448 00:002 OCB: 0 -> Boot0080 = PcieRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0)/HD(2,GPT,829755CD-439B-46B8-944E-B377F33FCF5F,0x64028,0x116940B8)/\System\Library\CoreServices\boot.efi 01:450 00:001 OCB: MacNB: InternalGetBootOptionData: Post GetVariable2 call. Returning NULL. Status == Not Found 01:452 00:001 OCB: 1 -> Boot0081 - failed to read 01:455 00:002 OCB: MacNB: InternalGetBootOptionData: Post GetVariable2 call. Returning NULL. Status == Not Found 01:457 00:001 OCB: 2 -> Boot0082 - failed to read 01:459 00:001 OCB: Building entry from Boot0080 01:461 00:001 OCB: MacNB: InternalGetBootOptionData: Post GetVariable2 call. Status == Success 01:464 00:003 OCB: Fixed DP - PcieRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0)/HD(2,GPT,829755CD-439B-46B8-944E-B377F33FCF5F,0x64028,0x116940B8)/\System\Library\CoreServices\boot.efi 01:466 00:001 OCB: Assuming DP is full-form or lacks suffix 01:468 00:001 OCB: Expanded DP - PcieRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0)/HD(2,GPT,829755CD-439B-46B8-944E-B377F33FCF5F,0x64028,0x116940B8)/\System\Library\CoreServices\boot.efi 01:470 00:002 OCB: Expanded DP remainder - \System\Library\CoreServices\boot.efi 01:472 00:001 OCB: Matched fs AE434798 01:477 00:005 OCB: Adding entry type (T:2|F:0|G:0) - PcieRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0)/HD(2,GPT,829755CD-439B-46B8-944E-B377F33FCF5F,0x64028,0x116940B8)/\System\Library\CoreServices\boot.efi 01:479 00:001 OCB: Trying to get label from \System\Library\CoreServices\.contentDetails Also attached the modified logouthook.command just in case someone needs a fix in the mean time. Can I assume that this will also work during macOS Updates (when the installer changes the default boot drive to "Boot from macOS Install..." ?? Now...onto the next issue I reported here for Legacy systems...the boot file installed installed by OC BootInstall.command does not detect any SATA on my system. I have been using "another" one I mentioned but prefer to use OC's. Let me me know how I can help debug that one ?? LogoutHook.command No, it will not work with updates. The current command is written in a way for the choice in preference pane to work. If you use ctrl+enter, it will not work, and you will need the change I mentioned, but this will break the preference pane switch. Please retry with the original file and startup disk preference pane. Link to comment Share on other sites More sharing options...
markl18 Posted June 25, 2020 Share Posted June 25, 2020 (edited) hi this message for @Andrey1970 and @vit9696 or any one else who actually knows what they are taliking about my hub for yoga touch is found once and everything works perfectly and then it takes like 20 times of kp before it finds its register that it is looking for I think it is 22 are you doing anything fancy to register tables Scope (_SB.PCI0.I2C1.TPL0) { Name (SBFX, ResourceTemplate () { Interrupt (ResourceConsumer, Level, ActiveHigh, Exclusive, ,, ) { 0x00000022, } }) Method (_CRS, 0, NotSerialized) // _CRS: Current Resource Settings { Name (SBFI, ResourceTemplate () { I2cSerialBusV2 (0x0010, ControllerInitiated, 0x00061A80, AddressingMode7Bit, "\\_SB.PCI0.I2C1", 0x00, ResourceConsumer, , Exclusive, ) GpioIo (Exclusive, PullDefault, 0x0000, 0x0000, IoRestrictionOutputOnly, "\\_SB.PCI0.GPI0", 0x00, ResourceConsumer, , ) { // Pin list 0x0032 } }) Return (ConcatenateResTemplate (SBFI, SBFX)) Edited June 25, 2020 by markl18 actual quote from aml file Link to comment Share on other sites More sharing options...
ltooz_audis Posted June 25, 2020 Share Posted June 25, 2020 (edited) Hello OpenCore experts, I really need help on this crazy problem. 1. I bought a cheap $20 dw1820a for my Elitebook 820 G3 to try out since dw1560 is too high, although I could afford it but I want something different. The Clover won't see the Wifi but the OpenCore would with both BT hand off and wifi full speed. 2. The problem is I can't boot with patched DSDT for my battery to show up, it will go to a black screen after everything is done and hang. I could boot and everything works perfectly with sleep/wake without DSDT at all (with those acpi errors displays) but NO battery showing since I couldn't patch it. It looks like the PNLF wasn't working with the backlight, at night I could see the apple logo extremely dim and the bar, but stuck there. Fixed it: The problem was using the DSDT & SSDTs extracted from rweverything (10 SSDTs), use Clover to extract DSDT and SSDTs (8), disassembled and patched - use all SSDTs (8), SSDT power from SSDT pike Alpha generation. https://www.youtube.com/watch?v=46hanWDwZLA 3. My question is why it works with native DSDT and not patched one? Attached is my config file. 4. If I can't solve this, I would be ok with the current config but is there anyway for the SMCBattery to display native battery with some kind of on the fly patching? Thanks, Louis configdw1820anosn.plist.zip Edited June 30, 2020 by ltooz_audis fixed the problem Link to comment Share on other sites More sharing options...
MacNB Posted June 25, 2020 Share Posted June 25, 2020 3 hours ago, vit9696 said: No, it will not work with updates. That's a shame. That means we will need to enable the bootpicker just before we do a macOS update and lookout for the Installer in the menu list so that it can be selected (as that's a guaranteed way of being able to make a selection). Ah well if there's no solution, so be it. In which case, it would be good to mention the limitation in the Configuration.pdf The current command is written in a way for the choice in preference pane to work. If you use ctrl+enter, it will not work, and you will need the change I mentioned, but this will break the preference pane switch. Please retry with the original file and startup disk preference pane. I had already tested the original logouthook command and Startup Disk from system preferences as I reported before. It does not work. I tried it again with the original command and I can confirm does not work. Neither does CTRL+ENTER (as you said). So there's still a problem. With the modified logouthook command, CTRL+ENTER works but selection via Startup Disk from system preferences does not work (I just tried it again). Thanks for the attention to fix this problem. Link to comment Share on other sites More sharing options...
Common_Sense Posted June 25, 2020 Share Posted June 25, 2020 (edited) Hello! Switch from Clover to OC went very well, I have a few questions that I hope you might have an answer to: - In bios I can select "Opencore" as a boot option, don't know how it got there but it exists, it doesn't work however. Selecting "UEFI OS" does boot OC. Can I make the "Opencore" boot option to work, or maybe remove it? - There are 2 error messages that seem a little off: 1. "OCS: NO schema for HideSelf at 8 index, contect <Boot>" 2. "OCS: NO schema for BlacklistAppleUpdate at index 3, context <Security>" Thanks! // CS EDIT: removed a question that I found the answer to Picker menu can be temporarily enabled by pressing alt/option key during boot EDIT2: Scanpolicy to hide ESP partition insted of HideSelf Edited June 26, 2020 by Common_Sense Link to comment Share on other sites More sharing options...
zisqo Posted June 26, 2020 Share Posted June 26, 2020 5 hours ago, Common_Sense said: Hello! Switch from Clover to OC went very well, I have a few questions that I hope you might have an answer to: - In bios I can select "Opencore" as a boot option, don't know how it got there but it exists, it doesn't work however. Selecting "UEFI OS" does boot OC. Can I make the "Opencore" boot option to work, or maybe remove it? - There are 2 error messages that seem a little off: 1. "OCS: NO schema for HideSelf at 8 index, contect <Boot>" 2. "OCS: NO schema for BlacklistAppleUpdate at index 3, context <Security>" Thanks! // CS EDIT: removed a question that I found the answer to Picker menu can be temporarily enabled by pressing alt/option key during boot remove Security/BlacklistAppleUpdate on your config.plist Link to comment Share on other sites More sharing options...
zisqo Posted June 26, 2020 Share Posted June 26, 2020 (edited) @vit9696 - recently OC 0.6.0 was stuck at here and my Logitech G512 and G1 LED won't initialized. (turn off that LED, this meant not initialized) - same stuck point when i inject USBports.kext or USBInjectAll.kext. - also USBports.kext was sort out under 15ports. - but this Big Sur OC bootloader is possible to boot for Catalina 10.15.5 perfectly. also i tried ncpi=0x2000, npci=0x3000 option but still looks that. ASUS X299 TUF mark 1 RX5700XT + i will gonna test a ubuntu kvm or proxmox system with this big sur pre-installed disk and this oc setting on. including a Debug log and APIC files. (there's no Panic log because of it doesn't Panic spot) opencore-2020-06-26-003255.txt ASUS X299 TUF mark 1 - APIC.dsl Edited June 26, 2020 by zisqo Link to comment Share on other sites More sharing options...
Common_Sense Posted June 26, 2020 Share Posted June 26, 2020 3 hours ago, zisqo said: remove Security/BlacklistAppleUpdate on your config.plist Thanks! Link to comment Share on other sites More sharing options...
MacPato Posted June 26, 2020 Share Posted June 26, 2020 3 hours ago, zisqo said: - recently OC 0.6.0 was stuck at here and my Logitech G512 and G1 LED won't initialized. (turn off that LED, this meant not initialized) - same stuck point when i inject USBports.kext or USBInjectAll.kext. - also USBports.kext was sort out under 15ports. - but this Big Sur OC bootloader is possible to boot for Catalina 10.15.5 perfectly. also i tried ncpi=0x2000, npci=0x3000 option but still looks that. ASUS X299 TUF mark 1 RX5700XT + i will gonna test a ubuntu kvm or proxmox system with this big sur pre-installed disk and this oc setting on. opencore-2020-06-26-003255.txt mine stops there also on my X99 system, but I'm up and running on my x79 system! just the Ryzen to go!!! Link to comment Share on other sites More sharing options...
vit9696 Posted June 26, 2020 Share Posted June 26, 2020 13 hours ago, MacNB said: That's a shame. That means we will need to enable the bootpicker just before we do a macOS update and lookout for the Installer in the menu list so that it can be selected (as that's a guaranteed way of being able to make a selection). Ah well if there's no solution, so be it. In which case, it would be good to mention the limitation in the Configuration.pdf I had already tested the original logouthook command and Startup Disk from system preferences as I reported before. It does not work. I tried it again with the original command and I can confirm does not work. Neither does CTRL+ENTER (as you said). So there's still a problem. With the modified logouthook command, CTRL+ENTER works but selection via Startup Disk from system preferences does not work (I just tried it again). Thanks for the attention to fix this problem. Could you provide the dumps with Startup Disk and the original script? Link to comment Share on other sites More sharing options...
MacNB Posted June 26, 2020 Share Posted June 26, 2020 (edited) 1 hour ago, vit9696 said: Could you provide the dumps with Startup Disk and the original script? Hi @vit9696 Please see attached Log, Config & screenshots. I put the original logouthook script back. This is what I selected from Sys Pref: On Reboot, OC boot picker shows (Entry 1 as Default instead of 3): (Yes, I do have two Windows partitions). I selected Entry 3 and pressed ENTER to boot the OS. Log shows the same issue: 01:560 00:003 OCB: MacNB: InternalGetBootOptionData: FilePathListSize (154) > LoadOptionSize (92) so Returning NULL 01:562 00:002 OCB: 0 -> Boot0080 - failed to read Thanks. MacNB-opencore-2020-06-26-100826.txt MacNB-config-3.plist Edited June 26, 2020 by MacNB Link to comment Share on other sites More sharing options...
Rodion2010 Posted June 26, 2020 Share Posted June 26, 2020 On 6/24/2020 at 11:18 AM, MacNB said: @vit9696 I assume Duet is the latest as I assumed it is now included with OC. I just did a git pull and ran the build_oc.tool on the 19th June. I noticed the 0 -> Boot0080 - failed to read so I added the extra DEBUG_INFO to see why and it shows FilePathListSize (154) > LoadOptionSize (92) so Returning NULL. LogoutHook.command 2.zip try this version Link to comment Share on other sites More sharing options...
MacNB Posted June 26, 2020 Share Posted June 26, 2020 3 hours ago, Rodion2010 said: LogoutHook.command 2.zip try this version Thanks @Rodion2010 I tried your script. Same result as @vit9696's modified version. That is, when using Startup Disk from System Pref to set the default, it does not work. Boot picker shows entry 1. When in boot picker, if I select the OS and hit CTRL+ENTER, then it remembers this as default. See two logs attached - one for Startup Disk selection and the other for CTRL+ENTER selection. After using CTRL+ENTER, OC always boots the selected Default Entry but there's an interesting line in the log which still shows DEF:0 12:370 10:002 OCB: Should boot from 3. EVO250 (T:2|F:0|G:0|E:0|DEF:0) Thanks for your help. MacNB-STARTUP-DISK-opencore-2020-06-26-152917.txt MacNB-CRTL-ENTER2-opencore-2020-06-26-153608.txt Link to comment Share on other sites More sharing options...
dayo Posted June 26, 2020 Share Posted June 26, 2020 On 6/23/2020 at 7:10 AM, volatile-memory said: How does OpenCore generate the disk labels in the boot menu? I changed the name of my APFS start up disk using Disk Utility after a successful installation, but OpenCore still displays the old label in the boot menu. Thanks! See: https://github.com/acidanthera/bugtracker/issues/886 and https://github.com/acidanthera/bugtracker/issues/957 Link to comment Share on other sites More sharing options...
PropoFlexWX4 Posted June 26, 2020 Share Posted June 26, 2020 Hi everyone. I am following the Githubs for OpenCore, Lilu, WEG, AppleALC and VirtualSMC... Noticed all of them are in the process of being updated for macOS 11.0. Receiving several commits related to it. Does this mean the next release of OC as well as these kexts, will offer full support for Big Sur, and we'll be able to update to it or clean install as normal? Link to comment Share on other sites More sharing options...
GOOGE Posted June 27, 2020 Share Posted June 27, 2020 Boot chime issue ? Opencore DEBUG 0.6.0 If I reset NVRAM, my Boot Chime works (chimes). After I reboot and until I reset NVRAM, Boot Chime does not work (no chime). My DEBUG log shows this after NVRAM reset: 07:832 00:004 OCAU: System volume is 98 (calculated from 70) - Success 07:836 00:003 OCAU: Matching PciRoot(0x0)/Pci(0x1F,0x3)/VenMsg(A9003FEB-D806-41DB-A491-5405FEEF46C3,00000000)... 07:840 00:004 OCAU: 1/3 PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x1)/VenMsg(A9003FEB-D806-41DB-A491-5405FEEF46C3,00000000) (6 outputs) - Success 07:844 00:003 OCAU: 2/3 PciRoot(0x0)/Pci(0x1F,0x3)/VenMsg(A9003FEB-D806-41DB-A491-5405FEEF46C3,00000000) (5 outputs) - Success 07:848 00:004 OCAU: Setting language to en-US:0 07:852 00:003 OCAU: Language for audio en-US:0 - Success 07:856 00:003 OC: Starting to play chime... 07:860 00:004 OC: Wave Resources\Audio\OCEFIAudio_VoiceOver_Boot.wav was requested 07:867 00:006 OCAU: File 59 for lang 7 is 32 2 2 (440576) - Success On the next reboot (and and reboot until NVRAM reset) My DEBUG log shows this: 07:807 00:007 OCAU: System volume is 0 (calculated from 0) - Success 07:814 00:007 OCAU: Matching PciRoot(0x0)/Pci(0x1F,0x3)/VenMsg(A9003FEB-D806-41DB-A491-5405FEEF46C3,00000000)... 07:818 00:004 OCAU: 1/3 PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x1)/VenMsg(A9003FEB-D806-41DB-A491-5405FEEF46C3,00000000) (6 outputs) - Success 07:822 00:004 OCAU: 2/3 PciRoot(0x0)/Pci(0x1F,0x3)/VenMsg(A9003FEB-D806-41DB-A491-5405FEEF46C3,00000000) (5 outputs) - Success 07:827 00:004 OCAU: Setting language to en:0 07:831 00:004 OCAU: Language for audio en:0 - Success Does anyone know why the System volume becomes 0 (and no Boot Chime plays), unless I reset the NVRAM? Link to comment Share on other sites More sharing options...
Recommended Posts