I can not manage to install Catalina on this legacy Asus machine that runs Mojave fine. When the installer boots up, DiskUtility does not see the internal hard-drives, neither the master SATA one or the the slave, ATA one. I have discussed this already on the Clover section with Slice, he told that some kext seems to have changed from Mojave to Catalina, he told me to use IOReg. Since then, I have postponed my work on Catalina due to the issues regarding the Mojave supplemental updates.
I have decided to start a new topic in here, due to visibility reasons and some new turn. The latest version of the dosdude1 patcher for unsupported Macs, discussed on Macrumors forums, patches the installer so that DiskUtility sees the internal hard-drives, I am able to install Catalina but, on first boot, the OS gets into a kernal panic with the message ”still waiting for root device”. I have searched online for this error, I have found Information regarding previous macOS versions with solutions that seem to have little to no relevance for the present issue.
Before installation finishes, I receive a message like ”Installation finished on Macintosh HD Data”, instead of ”Installation finished on Macintosh HD”. I admit this split between the two in Catalina still confuses me, perhaps this is how it was suppose to be? Perhaps something that was suppose to end up on Macintosh HD ends in Macintosh HD Data?
I admit the DVD-Rom and hard-drives are wired kinda of weird by some guy in a PC service, he said this is the optimum combination, something the ATA hard-drive is slave to the DVD-Rom. Perhaps this causes confusion into Catalina? On Mojave this configuration was fine.
Probably the solution suggested by Slice is the best, to replace one or more kext from Catalina with the Mojave versions of them. I do not know yet how to identify and replace them. If any other solutions seem possible, I am open to them.
Asus P5P41TED motherboard.
Intel Core 2 Duo E 8500
2 gb ram DDR 3
Salve a tutti,
premetto di essere nuovo in questo mondo dell'hackintosh e, come avrete letto dal titolo, ho un problema molto strano al momento dell'installazione.
Creo la chiavetta usb, metto tutti i kext, driver eccetera da un vecchio MacBook Pro ma, quando la vado a mettere sul pc e provo a bootare, Clover non mi trova l'os. In alto c'è lo stemma di clover, in basso i settings ma dove dovrebbero esserci i SO non c'è nulla.
Nel pc avevo ssd e hardest per windows ma ho pensato di toglierli per non creare conflitti con un nuovo ssd da 120gb comprato apposta per il Mac OS.
La penna usb ho provato a farla in tutti i modi che ho trovato e che mi hanno consigliato: sia con Tino, sia con terminale scrivendo il codice. Ho usato clover per selezionare kext e drivers ma nulla.
Questa è la guida che ho seguito inizialmente https://hackintosher.com/builds/asrock-z370-extreme4-pro4-hackintosh-high-sierra-guide/
Okay So I have two PCIe controller cards, both 3rd party, unbranded from eBay.
1st runs off the Marvell 88SE92xx chipset. 4 Internal Ports.
2nd runs off the ASMedia ASM1061 chipset. 2 Internal/ 2 External Ports (selectable by jumpers)
The hack is running stable no issues on 10.4.2 with an i7 8700k ASUS Maximus X Code as iMac 18,3
However, I wanted to add eSATA ports for some older drive enclosures I own, and some extra internal SATA ports as I've used all the SATA ports on the Motherboard.
The 1st Marvell actually works OOB in Mac OSX. No kexts needed. Speeds seem good (350R/400W on an SSD 80R/W on a 5400 HDD)
However, a few things don't seem perfect.
1) the AHCI version is 1.0. I imagine this could and should be a newer version? 1.2 or 1.31? If it should be updated, is this something only able to be flashed from a Windows OS?
2) It can't be used as a boot option. the Maximus doesn't recognise it as a startup option. Is this a possible AHCI version firmware issue? Is booting ever possible from these controllers?
3) TRIM was disabled in system profile. I know it automatically worked OOB for my NVME2 drives connected to the motherboard, But to enable Trim on an SSD 860 EVO I needed to submit the terminal command:
sudo trimforce enable
Now the second ASMedia controller I haven't been able to get to work. I've switched the jumpers (not sure which position is the 1,2,3) so I've made it so that one internal and one external will operate to test the card.
System profiler sees the card like all the others as a "Generic AHCI Controller" with AHCI version 1.20 supported.
However, I cannot get any drive to be recognised in the eSATA ports. I haven't tested the internal ports as I don't need these.
I've attempted using two kexts (attached) AHCI_3rdParty_eSATA.kext and AHCIPortInjector.kext
When I use AHCIPortInjector.kext the SATA device is recognised in system profiler as an ASM1062. However no drive works with this kext. And reading the chip itself on the card it says ASM1061. So not sure why it's preferring the 1062 entry over the 1061 since both are present in the kext.
When I use AHCI_3rdParty_eSATA.kext that SATA device is not recognised at all in the system profiler. It disappears.
I'm not using a custom DSDT for this motherboard and I've attached my config.plist if anyone has some insight on either cards.
Assemblato da me con le seguenti componenti tutte acquistate rispettando la lista compatibilità.
Usato poco, principalmente per qualche ora serale tornando a casa dal lavoro per video editing (fluido in 4K con Premiere Pro).
Mai un problema, sostituita pasta termica 2 mesi fa. Sempre tenuto in condizioni di pulizia interna. Vendo per cambio lavoro.