mhaeuser Posted May 1, 2019 Share Posted May 1, 2019 Do the drives show up in Shell ("map -b" to see the mappings, "ls fsX:" to show root content)? Do they show up in Clover? Do they show up in the FW boot selector? Attach an OC boot log please. 1 Link to comment Share on other sites More sharing options...
MrTrip Posted May 1, 2019 Share Posted May 1, 2019 7 minutes ago, vandroiy2012 said: Is this option turned on in your config.plist? Yes. Link to comment Share on other sites More sharing options...
Erroruser Posted May 1, 2019 Share Posted May 1, 2019 Just now, Download-Fritz said: Do the drives show up in Shell ("map -b" to see the mappings, "ls fsX:" to show root content)? Do they show up in Clover? Do they show up in the FW boot selector? Attach an OC boot log please. no they do not show at all only ssd card no nvme evo or pro Link to comment Share on other sites More sharing options...
MrTrip Posted May 1, 2019 Share Posted May 1, 2019 1 minute ago, Download-Fritz said: Do the drives show up in Shell ("map -b" to see the mappings, "ls fsX:" to show root content)? Do they show up in Clover? Do they show up in the FW boot selector? Attach an OC boot log please. Yes the NVME drive shoes up in Shell. It shows up in Clover and I am currently booted to it in Clover. The drive shows up everywhere except OC. How do I dump an OC Boot log when the drive does not show up in OC? 1 Link to comment Share on other sites More sharing options...
mhaeuser Posted May 1, 2019 Share Posted May 1, 2019 If they do not show anywhere, this issue is not related to OpenCore, probably open a dedicated thread in the general UEFI subforum. Link to comment Share on other sites More sharing options...
MacPato Posted May 1, 2019 Share Posted May 1, 2019 2 minutes ago, Download-Fritz said: Do the drives show up in Shell ("map -b" to see the mappings, "ls fsX:" to show root content)? Do they show up in Clover? Do they show up in the FW boot selector? Attach an OC boot log please. He stated they work in clover the issue isn't clover it's opencore not seeing Nvme (PCIEx4) or Sata Mode Link to comment Share on other sites More sharing options...
Erroruser Posted May 1, 2019 Share Posted May 1, 2019 Just now, Download-Fritz said: If they do not show anywhere, this issue is not related to OpenCore, probably open a dedicated thread in the general UEFI subforum. its due to open core as they show in clover just not in the open core boot section Link to comment Share on other sites More sharing options...
MacPato Posted May 1, 2019 Share Posted May 1, 2019 (edited) 4 minutes ago, Download-Fritz said: If they do not show anywhere, this issue is not related to OpenCore, probably open a dedicated thread in the general UEFI subforum. It's not a UEFI issue it's an OC issue if clover can see the drives sorry for the bold no idea why that was on Edited May 1, 2019 by MacFriedIntel Bold text Link to comment Share on other sites More sharing options...
mhaeuser Posted May 1, 2019 Share Posted May 1, 2019 Just now, MacFriedIntel said: It's not a UEFI issue it's an OC issue if clover can see the drives Please tone down the bold font when I draw conclusions from improperly answered questions. None of them was "do they show up in OpenCore?", yet they were answered with "the drives do not show up". Still, no boot log has been provided. 1 Link to comment Share on other sites More sharing options...
MacPato Posted May 1, 2019 Share Posted May 1, 2019 1 minute ago, Download-Fritz said: Please tone down the bold font when I draw conclusions from improperly answered questions. None of them was "do they show up in OpenCore?", yet they were answered with "the drives do not show up". Still, no boot log has been provided. How can you provide a boot log for something that doesn't boot, if you can't boot from the drive where do we generate a log? Link to comment Share on other sites More sharing options...
Erroruser Posted May 1, 2019 Share Posted May 1, 2019 (edited) 4 minutes ago, Download-Fritz said: Please tone down the bold font when I draw conclusions from improperly answered questions. None of them was "do they show up in OpenCore?", yet they were answered with "the drives do not show up". Still, no boot log has been provided. please tell us how to provide a boot log if they are not showing in the boot selection? Edited May 1, 2019 by errorexists Link to comment Share on other sites More sharing options...
MrTrip Posted May 1, 2019 Share Posted May 1, 2019 2 minutes ago, Download-Fritz said: Please tone down the bold font when I draw conclusions from improperly answered questions. None of them was "do they show up in OpenCore?", yet they were answered with "the drives do not show up". Still, no boot log has been provided. I will provide a boot log, tell me where the boot log button is? Or how to extract it from the EFI folder? Here is my OC Menu, and here is my clover menu... How do I provide a log? Link to comment Share on other sites More sharing options...
mhaeuser Posted May 1, 2019 Share Posted May 1, 2019 The OpenCore Reference Manual specifies the possible debug targets in section "7.4 Debug Properties, 4. Target". You can log to serial, NVRAM variable or file to obtain it withour booting an OS. 2 1 Link to comment Share on other sites More sharing options...
MrTrip Posted May 1, 2019 Share Posted May 1, 2019 1 minute ago, Download-Fritz said: The OpenCore Reference Manual specifies the possible debug targets in section "7.4 Debug Properties, 4. Target". You can log to serial, NVRAM variable or file to obtain it withour booting an OS. Where would this manual be? I do not see it on the GitHub. Link to comment Share on other sites More sharing options...
Guest Posted May 1, 2019 Share Posted May 1, 2019 https://github.com/acidanthera/OpenCorePkg/blob/master/Docs/Configuration.pdf 1 minute ago, MrTrip said: Where would this manual be? I do not see it on the GitHub. Link to comment Share on other sites More sharing options...
MrTrip Posted May 1, 2019 Share Posted May 1, 2019 1 minute ago, fabiosun said: https://github.com/acidanthera/OpenCorePkg/blob/master/Docs/Configuration.pdf Expected to be reference manual, named Configuration. Will provide a boot log shortly. Just now, fabiosun said: a thanks could be enough... Thought I hit the heart, missed by an inch <3 just a bit frustrated that this issue kept getting buried and shrugged off. I have no issues providing what is required to assist in fixing the issue. Link to comment Share on other sites More sharing options...
MrTrip Posted May 1, 2019 Share Posted May 1, 2019 Alright guys, so the PDF clearly states... So I tried the Data Hub approach, but I can't boot into macOS using OC to retrieve that log. When I fail booting OC and then boot Clover, the Data Hub output of ioreg -lw0 -p IODeviceTree | grep boot-log | sort | sed 's/.*<\(.*\)>.*/\1/' | xxd -r -p becomes my Clover boot log, and not OC. So what are my options now? Link to comment Share on other sites More sharing options...
mhaeuser Posted May 1, 2019 Share Posted May 1, 2019 1 minute ago, MrTrip said: Alright guys, so the PDF clearly states... I don't have the time to keep up with every little implementation detail of the overall project or to keep replying to such stuff. I gave you three options, one is unavailable, you pick one not part of the list and wonder why it doesn't work... DataHub was intentionally not included because it is volatile and unavailable after a reboot, and, as you can see, collides with Clover's variable, which makes it impossible to use chainloading as a debugging method, at least for the moment. Using the NVRAM variable, one part of my listed options, would have given you both pre-boot and chain-loaded post-boot log availability from within any OS. If you are not happy with getting unrefined instructions to debug, that is just fine, because my system works. 3 Link to comment Share on other sites More sharing options...
cecekpawon Posted May 1, 2019 Share Posted May 1, 2019 @MrTrip If you have Clovers boot-log, then you probably actually booted with Clover / get mixed with OxC. You may try this tool to get OxC log as a temporary solution. Need to be load with: "bcfg driver add x OpenCoreExt.efi OpenCoreExt". Not to put it into "/EFI/OC/Drivers" (or resulting black screen). On OxC config.plist set: <key>Misc</key> <dict> <key>Debug</key> <dict> <key>Delay</key> <integer>0</integer> <key>DisplayLevel</key> <integer>2151678018</integer> <key>Target</key> <integer>1</integer> </dict> Tools.zip 2 Link to comment Share on other sites More sharing options...
MrTrip Posted May 1, 2019 Share Posted May 1, 2019 25 minutes ago, Download-Fritz said: I don't have the time to keep up with every little implementation detail of the overall project or to keep replying to such stuff. I gave you three options, one is unavailable, you pick one not part of the list and wonder why it doesn't work... DataHub was intentionally not included because it is volatile and unavailable after a reboot, and, as you can see, collides with Clover's variable, which makes it impossible to use chainloading as a debugging method, at least for the moment. Using the NVRAM variable, one part of my listed options, would have given you both pre-boot and chain-loaded post-boot log availability from within any OS. If you are not happy with getting unrefined instructions to debug, that is just fine, because my system works. You did not specify those were my only options. Logging to serial I have no idea how that would even work so NVRAM it is.... this is my output Link to comment Share on other sites More sharing options...
MacPato Posted May 1, 2019 Share Posted May 1, 2019 8 minutes ago, cecekpawon said: @MrTrip If you have Clovers boot-log, then you probably actually booted with Clover / get mixed with OxC. You may try this tool to get OxC log as a temporary solution. Need to be load with: "bcfg driver add x OpenCoreExt.efi OpenCoreExt". Not to put it into "/EFI/OC/Drivers" (or resulting black screen). On OxC config.plist set: <key>Misc</key> <dict> <key>Debug</key> <dict> <key>Delay</key> <integer>0</integer> <key>DisplayLevel</key> <integer>2151678018</integer> <key>Target</key> <integer>1</integer> </dict> Tools.zip Where does "bcfg driver add x OpenCoreExt.efi OpenCoreExt". that command go? Link to comment Share on other sites More sharing options...
cecekpawon Posted May 1, 2019 Share Posted May 1, 2019 @MacFriedIntel from shell.efi brother Link to comment Share on other sites More sharing options...
Pavo Posted May 1, 2019 Share Posted May 1, 2019 7 minutes ago, MacFriedIntel said: Where does "bcfg driver add x OpenCoreExt.efi OpenCoreExt". that command go? EFI Shell, everyone needs to remember this project is still in development and it is 100% related to UEFI, so if you are trying to get debug information you need to also be able to search how to debug UEFI..... so look into using EFI Shell a lot. Link to comment Share on other sites More sharing options...
MacPato Posted May 1, 2019 Share Posted May 1, 2019 8 minutes ago, Pavo said: EFI Shell, everyone needs to remember this project is still in development and it is 100% related to UEFI, so if you are trying to get debug information you need to also be able to search how to debug UEFI..... so look into using EFI Shell a lot. Yes got it thanks 1 Link to comment Share on other sites More sharing options...
MrTrip Posted May 1, 2019 Share Posted May 1, 2019 (edited) This is the best I can get at the moment, if it is not correct let me know and I'll keep trying. Edited May 1, 2019 by MrTrip Link to comment Share on other sites More sharing options...
Recommended Posts