NorthAmTrans Posted August 14, 2019 Share Posted August 14, 2019 (edited) Used Debug and Target 67 (bit mask was fun to learn in the doc and with some google) and got my first boot log. Rad. Not sure that's the best value for that but it's what I landed on and seems to have given me a very descriptive log. I see there's a ton of searching going on for my APFS volume. Should I be setting this so boot loader only sees my one APFS drive to avoid needless search and fail? Also this seems funny to me. Normal? @maddie Tagging you because you've been super helpful. I just moved OC off my flash drive. Very happy. 18:770 00:057 OC: OcLoadNvramSupport... 18:827 00:057 OC: Invalid nvram data 18:882 00:055 OC: Deleting NVRAM 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:UIScale - Not Found 18:939 00:056 OC: Setting NVRAM 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:UIScale - Success opencore-2019-08-13-222528.txt Edited August 14, 2019 by NorthAmTrans Link to comment Share on other sites More sharing options...
Pavo Posted August 14, 2019 Share Posted August 14, 2019 (edited) 37 minutes ago, meaganmargaret said: Understandable.....here you go.......also, the AML that initiates the wireless/BT card is: SSDT-X299-ARPT.aml OC_EFI.zip EDIT: But do other folks have BT working? Pavo, do you? Here is your issue 1. You have renames in the ACPI>Patch in the config and specifically you are renaming PC00 to PCI0, renames should not be done in the config using Patch section, this has been stated over and over in this thread and also stated in the OpenCore documentations. 2. While you are patching the ACPI tables with the rename of PC00 to PCI0 your SSDT Scope is _SB.PCI0.RP19 which is not matching the ACPI table path. 3. You are also doing a device rename of PXSX to ARPT in the SSDT itself. What I suggest you do is remove all the renames in the ACPI>Patch section and change all your SSDTs to match against the scope of \_SB.PC00.xxx. Attached is your OC EFI with everything fixed. OC_EFI.zip Edited August 14, 2019 by Pavo 1 Link to comment Share on other sites More sharing options...
Wackymac Posted August 14, 2019 Share Posted August 14, 2019 1 hour ago, Pavo said: Here is your issue 1. You have renames in the ACPI>Patch in the config and specifically you are renaming PC00 to PCI0, renames should not be done in the config using Patch section, this has been stated over and over in this thread and also stated in the OpenCore documentations. 2. While you are patching the ACPI tables with the rename of PC00 to PCI0 your SSDT Scope is _SB.PCI0.RP19 which is not matching the ACPI table path. 3. You are also doing a device rename of PXSX to ARPT in the SSDT itself. What I suggest you do is remove all the renames in the ACPI>Patch section and change all your SSDTs to match against the scope of \_SB.PC00.xxx. Attached is your OC EFI with everything fixed. OC_EFI.zip buy you cannot rename pc00 to pci0 in the ssdt though... can you elaborate on why this rename is not needed? Link to comment Share on other sites More sharing options...
Pavo Posted August 14, 2019 Share Posted August 14, 2019 24 minutes ago, Wackymac said: buy you cannot rename pc00 to pci0 in the ssdt though... can you elaborate on why this rename is not needed? Because its the original device name in the ACPI tables. There is not need to rename PCI bus device name. 1 Link to comment Share on other sites More sharing options...
Wackymac Posted August 14, 2019 Share Posted August 14, 2019 5 minutes ago, Pavo said: Because its the original device name in the ACPI tables. There is not need to rename PCI bus device name. ok i guess ill go about cutting back further i just like some of the renames for cosmetic reasons Link to comment Share on other sites More sharing options...
zisqo Posted August 14, 2019 Share Posted August 14, 2019 1 hour ago, Wackymac said: ok i guess ill go about cutting back further i just like some of the renames for cosmetic reasons there are good enough for 2 options and other options better to remove but don't worry because of working fine. trust me. 1. PCI00 to PCI0 2. LPC0 to LPCB so start up without BT's ssdt and inject a PciRoot id and device properties in DeviceProperties. the Hackintool will export that information to plist file. : ) Link to comment Share on other sites More sharing options...
zisqo Posted August 14, 2019 Share Posted August 14, 2019 On 8/13/2019 at 2:17 AM, maddie said: Always read the configuration carefully for every option in the config.plist. I know it's quite tedious, but it's necessary You have a very similar build as mine, I have high hopes that it would work. Good luck! trying with this config.plist for fix Apple booting logo issue 1 Link to comment Share on other sites More sharing options...
Wackymac Posted August 14, 2019 Share Posted August 14, 2019 9 minutes ago, zisqo said: there are good enough for 2 options and other options better to remove but don't worry because of working fine. trust me. 1. PCI00 to PCI0 2. LPC0 to LPCB so start up without BT's ssdt and inject a PciRoot id and device properties in DeviceProperties. the Hackintool will export that information to plist file. : ) as ive seen on your github. everything else is implemented. so your saying those 2 are fine to patch? Link to comment Share on other sites More sharing options...
maddie Posted August 14, 2019 Share Posted August 14, 2019 2 minutes ago, zisqo said: trying with this config.plist for fix Apple booting logo issue You mean the low resolution first stage boot logo? I've fixed it, disabled SanitiseClearScreen option and it worked perfectly. 1 Link to comment Share on other sites More sharing options...
Matgen84 Posted August 14, 2019 Share Posted August 14, 2019 (edited) 5 hours ago, Download-Fritz said: @Matgen84 createinstallmedia is supported just fine and validated by many users. If you have a specific problem, please elaborate. @justin I think the 'custom' part is a bit abused here, probably @Pavo expected some botchered install method, like the old BaseSystem+Packages nonsense. Apple Recovery DMG ofc is not 'custom', but apparently not Matgen's problem either. @MacFriedIntel May I ask you to not clutter the topic? @Download-Fritz If I understand well: I can install macOS with createinstallmedia method and OC in EFI, without problems. Right. It's awesome Edited August 14, 2019 by Matgen84 Link to comment Share on other sites More sharing options...
Andres ZeroCross Posted August 14, 2019 Share Posted August 14, 2019 24 minutes ago, Matgen84 said: @Download-Fritz If I understand well: I can install macOS with createinstallmedia method and OC in EFI, without problems. Right. It's awesome Hahahaha,,, What's going on here?? I have installed my pc many times with OC bootloader and Create Install Media method here. No problem so far,, I always use createinstallmedia method to make usb installer 1 Link to comment Share on other sites More sharing options...
Matgen84 Posted August 14, 2019 Share Posted August 14, 2019 34 minutes ago, Andres ZeroCross said: Hahahaha,,, What's going on here?? I have installed my pc many times with OC bootloader and Create Install Media method here. No problem so far,, I always use createinstallmedia method to make usb installer OC Configuration docs talks only about Recovery Method. Is why I know if it's available with createinstallmedia Link to comment Share on other sites More sharing options...
Andres ZeroCross Posted August 14, 2019 Share Posted August 14, 2019 Just now, Matgen84 said: OC Configuration docs talks only about Recovery Method. Is why I know if it's available with createinstallmedia It will be "weird" and "strange" if OC Bootloader of hackintosh can't install with native USB Installer from Createinstallmedia. OC Bootloader's habit is like Apple, so it will not drop support of native usb installer (createinstlalemdia) Sorry for bad english 1 Link to comment Share on other sites More sharing options...
Matgen84 Posted August 14, 2019 Share Posted August 14, 2019 3 minutes ago, Andres ZeroCross said: It will be "weird" and "strange" if OC Bootloader of hackintosh can't install with native USB Installer from Createinstallmedia. OC Bootloader's habit is like Apple, so it will not drop support of native usb installer (createinstlalemdia) Sorry for bad english I came to the same conclusion. Still, createinstallmedia is not mentioned in the docs configuration Do you take a look to my personal message post few days Link to comment Share on other sites More sharing options...
Andres ZeroCross Posted August 14, 2019 Share Posted August 14, 2019 (edited) 14 minutes ago, Matgen84 said: I came to the same conclusion. Still, createinstallmedia is not mentioned in the docs configuration Do you take a look to my personal message post few days Download Frit's alway said about "OC's habit/behaviour is like Apple Way", so no need to write about CreateInstallMedia I don't check it yet, will check it when i have free time Edited August 14, 2019 by Andres ZeroCross 1 Link to comment Share on other sites More sharing options...
matgeo Posted August 14, 2019 Share Posted August 14, 2019 Need your help. OC with High Sierra works fine , but I cannot boot on Catalina. Can someone take a look ? opencore-2019-08-14-053406.txt OC.zip Link to comment Share on other sites More sharing options...
maddie Posted August 14, 2019 Share Posted August 14, 2019 1 minute ago, matgeo said: Need your help. OC with High Sierra works fine , but I cannot boot on Catalina. Can someone take a look ? opencore-2019-08-14-053406.txt OC.zip Make sure that XHCI hand-off is enabled in your BIOS Link to comment Share on other sites More sharing options...
matgeo Posted August 14, 2019 Share Posted August 14, 2019 I don't have that option in BIOS. Link to comment Share on other sites More sharing options...
Matgen84 Posted August 14, 2019 Share Posted August 14, 2019 (edited) 47 minutes ago, matgeo said: Need your help. OC with High Sierra works fine , but I cannot boot on Catalina. Can someone take a look ? opencore-2019-08-14-053406.txt OC.zip Do you try boot-args: -v dart=0 debug=0x100 keepsyms=1. Post another screenshot. Complete your signature with your config, please Edited August 14, 2019 by Matgen84 Link to comment Share on other sites More sharing options...
matgeo Posted August 14, 2019 Share Posted August 14, 2019 Sorry , can't figure out how to add my config to profile. My system is a Dell 5570 with : Intel i5-8250u Intel UHD 620 16gb RAM 2 samsung ssd Link to comment Share on other sites More sharing options...
Matgen84 Posted August 14, 2019 Share Posted August 14, 2019 (edited) 23 minutes ago, matgeo said: Sorry , can't figure out how to add my config to profile. My system is a Dell 5570 with : Intel i5-8250u Intel UHD 620 16gb RAM 2 samsung ssd Can you try boot-args: -v dart=0 debug=0x100 keepsyms=1. Reboot then Post another screenshot. For complete signature: left click on your name at top right. Select Account settings then Signature in setting menu (left windows) Edited August 14, 2019 by Matgen84 Link to comment Share on other sites More sharing options...
Andres ZeroCross Posted August 14, 2019 Share Posted August 14, 2019 1 hour ago, matgeo said: Need your help. OC with High Sierra works fine , but I cannot boot on Catalina. Can someone take a look ? opencore-2019-08-14-053406.txt OC.zip WRong ACPI table (DSDT patch) in your configuration. Too many ACPI error about namespace lookup failure in RP09.PXSX, RP04.PXSX, RP05.PXSX, RP08.PSX. This is not good 1 Link to comment Share on other sites More sharing options...
matgeo Posted August 14, 2019 Share Posted August 14, 2019 @Matgen84 , that's what I did. Isn't that right? @Andres ZeroCross , I know about that. But doesn't stop me from booting on High Sierra on both Clover and OC. Is it possible for you to take a look if we can fix that errors? Attaching origin folder. Screenshot 2019-08-14 at 10.35.42 am.pdf origin.zip 1 Link to comment Share on other sites More sharing options...
Andres ZeroCross Posted August 14, 2019 Share Posted August 14, 2019 6 minutes ago, matgeo said: @Matgen84 , that's what I did. Isn't that right? @Andres ZeroCross , I know about that. But doesn't stop me from booting on High Sierra on both Clover and OC. Is it possible for you to take a look if we can fix that errors? Attaching origin folder. Screenshot 2019-08-14 at 10.35.42 am.pdf origin.zip Try to remove VodooI2C.kext and VodooI2CHID.kext first,. and try it. Post for the result 1 Link to comment Share on other sites More sharing options...
matgeo Posted August 14, 2019 Share Posted August 14, 2019 @Andres ZeroCross, that was the first I tried but no luck. Link to comment Share on other sites More sharing options...
Recommended Posts