tobrien1954 Posted March 20 Share Posted March 20 Hi, I was getting 'stuck' at the STILL WAITING FOR ROOT DEVICE with all my USB attempts so I created a SATA drive of the EFI and Ventura Install, and am booting from that. This setup gets A LOT farther but now is "looping" with a group of 20 or so messages --> launchd system/com.apple.bluetoothd [nnn] <notice> service state running a bunch more lines indicating that there is ... ERROR 3: NO SUCH PROCESS The group ends with com.apple.xpc.launchd ... denied lookup: name=com.apple.private.corewifi-xpc requester = bluetoothd[nnn], ERROR = 159: Sandbox Restriction It waits about 5 seconds and repeats with NNN increasing by 1 I've attached the (sn removed) config.plist and a screen shot config_redacted.plist.zip Screens.zip Quote Link to comment Share on other sites More sharing options...
mek21 Posted March 20 Share Posted March 20 Reduce your boot media to a minimum of kexts, make sure you have a SMBIOS compatible with your hardware, and look on github for an EFI compatible with your hardware. Quote Link to comment Share on other sites More sharing options...
tobrien1954 Posted March 20 Author Share Posted March 20 The only way can see clear to SOME level of installation is to remove all additional h/w (WiFi, Graphics card) and use my 2nd SATA drive as the source. I am using the SATA since I cannot get passed the USB installer getting stuck waiting for ROOT DEVICE. Having read a lot of the Dortania guide(s) I am still unsure how to tune some of the CONFIG.plist as it seems to me that many of the "tools" it calls out have to run ON THE TARGET Hardware to gather that info. How do you do that??? I am hoping to github find an EFI that is based upon my ASUS mobo (as is with it's CPU based-graphics.) Any suggestions would be most welcome. For the time being I am going to update my profile to not include these extras cards to eliminate confusion as to what I am working with. Quote Link to comment Share on other sites More sharing options...
STLVNUB Posted March 20 Share Posted March 20 4 hours ago, tobrien1954 said: Hi, I was getting 'stuck' at the STILL WAITING FOR ROOT DEVICE with all my USB attempts so I created a SATA drive of the EFI and Ventura Install, and am booting from that. T Try A Different USB Slot, Your USB Is Not Configured Correctly 1 Quote Link to comment Share on other sites More sharing options...
Anto65 Posted March 20 Share Posted March 20 tobrien1954 PciRoot(0x0)/Pci(0x2,0x0) > AAPL,ig-platform-id > 0000C087 ??? https://dortania.github.io/OpenCore-Install-Guide/config.plist/comet-lake.html#add-2 or leave blank Try SecureBootModel = Disabled Inject usb with USBInjectAll.kext activate portlimit in kernel > quirks 1 Quote Link to comment Share on other sites More sharing options...
tobrien1954 Posted March 20 Author Share Posted March 20 From that guide... I don't know where I read about the value I have (0000C087) but I'll try the 07009B3E 07009B3E Used when the Desktop iGPU is used to drive a display 00009B3E Alternative to 07009B3E if it doesn't work I'll add USBInjectAll My BIOS already has SECURE BOOT disabled... Thanks ! Quote Link to comment Share on other sites More sharing options...
Anto65 Posted March 20 Share Posted March 20 (edited) SecureBootModel = Disabled in config too ( Misc > Security ) Edited March 20 by Antonuccio 1 Quote Link to comment Share on other sites More sharing options...
tobrien1954 Posted March 20 Author Share Posted March 20 The good news is that the USB installer no longer gets the "WAITING FOR ROOT DEVICE" But adding either of the data values suggested from Dortania, I get a black screen. Even when make it blank ... black screen. Quote Link to comment Share on other sites More sharing options...
tobrien1954 Posted March 20 Author Share Posted March 20 Its hard to tell from the messages all flying by BUT I wonder if this black screen is when the installer is trying to "switch" to the VENTURA install part... The black screen happens after MANY messages Quote Link to comment Share on other sites More sharing options...
tobrien1954 Posted March 21 Author Share Posted March 21 I've read elsewhere that this BLACK screen issue can be quite the rabbit hole. I've read elsewhere that I should build a windows install first, then use a bunch of tools to get the actual h/w config info for the Ventura build. Apparently these tools can indicate which SSDTs, DEVICE Properties and other important info specific to my h/w. I am going to try to find a guide to do this ... It makes me wonder if this path can provide H/W specific OpenCore build info , makes me wonder why this isn't a preferred means to acquire this info instead of the "guess and check" system that seems to be the norm for OpenCore and H/W matching. FYI, I mean no insult to anyone... but it is a bit over whelming trying to decode the Dortania like guides when your particular h/w is not listed and "guess and check" seems to be the answer. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.