Bootloop using rescue mode for new install

Bootloop using rescue mode for new install

Stats are
Mobo: Gigabyte B365M DS3H UHD360

CPU: i3-9100F (coffee lake-s)

RAM:16GB, can't remember specifics like make and model

GPU: GeForce GTX 1660, though out of interest of troubleshooting, I've tried with the integrated GPU to no change.

Network adapter: Netgear A6210, using the kext for rt-2870USB which is the same chipset. Tried without for troubleshooting purposes, with no change.

Hard dive I have a 500GB spinning rust drive in mind for testing, but doesn't really matter yet since I can't even get into setup.

Target OS Version : Ventura

I've been mainly following this guide here: https://youtu.be/s_zlanxCWeM?si=KU3BqSw2K0KEw4p4, which is helpful as it lists out how to make the install media from a PC as I do not have access to a mac. (Well, I have a macbook pro, but is currently nonfunctional ATM)

I get all the tools, though I've tried the current versions first initially, then tried the exact ones he used just to be sure I wasn't using a new version that may have broken something since. Tool versions made no change. I get the recovery DMG file, and write it to my 16GB thumb drive with the open core package for PCs, seems to go ok. Then I've tried to build my own EFI file, as from the video with OCAT, trying the various iterations of the cfglock kernel quirks, though initially using the combination called for for newer CPUs.

However, there's already a prebuilt EFI folder online for my exact motherboard at https://github.com/Vaatu/Hackintosh-Gigabyte-B365M-DS3H-UHD630-Ventura-OC?tab=readme-ov-file. So I tried that EFI, of course whilst generating the serial number a rom as you do, and adding the kext for my wifi adapter. The github page also mentions having both cgflock quirks set, which I tried initially, though I've tried differnt combos too with no help.

It just bootloops, with an error message that pops up so breifly, I couldn't get a pic with my phone before it disappears and reboot, but I took a vid and screencapped that and got it anyway. :-) But I'm thinking some sort of kernel panic? I will add, this is in a 50lb EAATX case that's a pain to move and get cards in and out, so card swapping needs to be minimal. And that it is a functioning windows machine, and my daily driver, so we will not be doing anything that damages that. I'd pull the sata connector to my windows drive, but it's on a board mounted NVME card, and I've been trying to avoid crawling under my desk fully to get into the case to get to it. If it were on a SATA drive, I could just lean down and pull the sata cable. LoL But I've seen people install to computers with an active windows install with no problem anyways, sometime dual or even triple booting them.

https://preview.redd.it/zesm0xzjbgid1.png?width=1520&format=png&auto=webp&s=2da987fd1dce4fd33e7daa5844c33ce6566187a0

submitted by /u/CobraG0318
[link] [comments]