Jump to content

Vyzantion

Members
  • Content Count

    25
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Vyzantion

  • Rank
    Member
  • Birthday 05/05/1985

Profile Information

  • Gender
    Other
  1. I was able to install using the dosdude1 patched Catalina, I needed to apply a patch for Intel IDE controller to escape the Still Waiting for Root Device error. The issue on the vanilla Catalina of invisible internal hard-drives still present.I do not know what causes it, probably some modified kexts from Mojave to Catalina.
  2. I have a similar issue. It has something to do, I guess, with the new partition scheme from Catalina, that creates two main partitions: One with the core of the os, and one with the data. For example, if you have a partition called Macintosh HD and try to install it, the Catalina installer shall create another partition called Macintosh HD Data and split the installation between them. I have tried to overcome this requirement, but I have failed each time. On vanilla Catalina, the installer does not see the internal hard-drives at all, this happens on the patched Catalina with dosdude1 patch. So, there may be two separate issues: 1) Apple changed the SATA/ATA core kexts. 2) The split in two of the main partition.
  3. Make sure to use verbose mode, meaning the boot flag -v, too be able to see where it gets stuck. Without verbose mode, nobody can tell what is the nature of the issue.
  4. Why don\t you install Clover directly on the partition where you have installed the macOS?
  5. @Hackintosh On this link there is a IORegistry Explorer file, the EFI partition contents of two pen drive installers, one patched with RMC patch (EFI1) with invisible internal hard-drives, the other of a pen drive patched with the dosdude1 patch (EFI2), that sees the internal hard-drives, but the installation ends up the kernel panic described. On both the f2 test was applied on boot, for information collecting. https://we.tl/t-uah4I8ZQCa If more information or files are required, please let me know.
  6. Created two pen drive installation, one based on the RMC patch EFI1), one based on the dosduide1 patch (Efi2). Both use the lastest software versions and I have booted them with F2, to get boot information. On the RMC patched version, like in vanilla Catalina, the internal hard-drves are inviible to DiskUtility. On the dosdude 1 patched version, the intenral hard-drives are visble, but, on first boot after installation, the OS stops into a kernel panic with |Still waiting for root device|. For a moderator, please move this thread to the Catalian support section. But I can not attach the files. Do I need to upload them into an online storage location and link them?
  7. How can I do that? With IORegistry Explorer? I am kind of lost in it. the LSPCI command from Linux is not present on macOS, and system_profiler or ioreg in Terminal get too much information and it is hard to get it.
  8. First thing, this is not about the Niresh Catalina distro, that is not supported in this hardware, that is a legacy hardware. I have already posted on several forums, no clear answer yet, so I try to post in here as well. I have managed to install a patched version of Mojave (dosdude1 method) on this hardware and ran it fine for about an year: Asus P5P41TED motherboard Intel Core 2 Duo E8500 3 gb ram ddr3 Nvidia GeForce E8500 Two internal hard-drives, a master SATA one, and a slave, ATA one. On this hardware, the vanilla Catalina installer boots up, but on DiskUtility the internal hard-drives are not visible. After creating an installer on the pen drive using the dosdude1 patch for Catalina, the internal hard-drives are visible, I am able to start the install but, on first boot after install, the OS crashes into a kernel panic, the last line being: ”Still waiting for root device.” Both issues seem similar to some issues present on older macOS versions, but not on this hardware. On the case of vanilla Catalina, the invisibility of the hard-drives might be solved with some kexts added. I can not find any. I know there is a new patch called the EC patch, I do not know about yet.
  9. ACPI Dynamic OEM table load error Firstly, on creating the High Sierra beta installation drive, I have edited the config.plist in TextEdit and changed Inject Intel to false and inject Nvidia to True have booted the High Sierra Beta with just the -v boot flag. It went fine. I have proceeded with the installation. On first boot, it said 21 minutes remaining, and then reboot, and then the installation it resumes. On first boot, the internal Macintosh HD has not icon, unlike the installation pen driver, only a blue circle. DDST patch seems over my expertise as of today, this seems the best solution. Dart=0, nv_disable=1 or npci=0x3000 do not seem to work. Also, when I managed to boot the OS using -x boot flag, it moved horribly slow, unlike Sierra or the installation medium of Sierra. It may be something regarding the low ram, yet, but that is, most likely, rather easy to fix. Installation of Clover failed. Specs: Asus P5P41TED Rev X.ox Intel Core2Duo E8500 2gb of ram Nvidia GeForce 6200 Last edited: Today at 2:21 AM
  10. Shut down blocked A new hard configuration, the old motherboard was broken. Things went fine at first. After a few days, noticed a nasty issue that was getting more and more serious: the os tended to block at shut down. It gets to CPUhalted (if offline) or Realtek link down on en0 (if online) and then stop. Overheating was an issue on the previous configuration (Gigabyte) based, but there, at least there was a CPU overheating alarm. On the new one, nothing similar. Specs are: Asus P5P41TED Rev X.ox Intel Core 2 Duo e8500 Nvidia GeForce 6200 To be able to shut down, I do this: 1) Reboot after being logged on; 2) reboot 1-3 times being logged off; 3) shut down being logged off. But sometimes not even this works. Sometimes, the bios seem to fail loading. At one point it even gave an error of loading. At first install, it ran until a Quick boot option, that skipped some tests, to be able to boot faster, but I disabled that, in order to keep the hardware safer, to run the full tests. This a serious issue. Maybe some patching will work. I boot with only verbose mode, -v, no other bootflags. A shut down block would potentially affect the installed OS on the hard drive? Is this a dead lock?
  11. Realtek Ethernet not working in Sierra I have changed thoose days the motherboard, it got fried due to some power failure. It was a Gigabyte S 3. I have found a fairly cheap Gigabyte motherboard, slightly older then the one that was fried. Instalation went well, up until tried to connect for the first time via ethernet. It refused to work. Tried several solutions, including removing and reinstalling the kext, nothing worked. My specs are: gigabyte fsb 1066 ga-945gzm-s2 motherboarrd, Intel Core 2 Duo E8500 CPU, and Nvidia Geforce 6200 Graphics. Installed Windows and device manager it said it is Realtek PCI GBE Family Controller. The standard Realtek kext does no work, it seems.
  12. I have had a similar issue when updating 10.2 to 10.3 . I switched from Clover to Chameleon, I have now 10.5. Maybe you can try a new Clover version. If the latest Chameleon will not boot properly either, try an older version, a few months earlier.
  13. Just a basic question about El Capitan, it may sound dumb for experienced users, but since I am quite new to Hackintoshing (less then a year) and did not tested the public beta of Yosemite, I would like to ask anyone who installed the Niresh version of El Capitan: from beta 1 to beta 2 there is an update that appears in App Store or only a fresh install from scratch can make the switch from beta 1 to beta 2 etc? I am asking this to see if I choose to download and install the latest version of El Capitan uploaded by Niresh.
  14. Graphic card Nvidia GeForce 6200. One old monitor. Search Google for Clover iso . Burn it to a cd-rw or to an usb drive, other then the one on which you have the Yosemite installer. I used the boot flags (boot arguments) npci=0x2000 or npci=0x3000, I have firstly succeded with the first, then with the second, I guess the second is better, but one of them seems crucial for situaitions like this one. In Clover, on first screen, on Options there is a menu where you can get the place where the boot flags can be added.
  15. Try to burn a Clover iso un a cd-rw and, after booting that, try to boot the OS from it. If it works, you can then install Clover on the hard drive, marking all the ps2 keyboard and mouse kexts. I had a similar issue and this worked for me.
×
×
  • Create New...