Jump to content


  • Content Count

  • Joined

  • Last visited

About TatsuArekku

  • Rank
    InsanelyMac Protégé
  1. TatsuArekku

    Black screen after 10.9.4 combo update

    My apologies for the delayed response. Just thought I'd offer the courtesy of an update for anyone with a similar problem. Successfully running 10.9.5 with Intel HD kexts, DSDT, and "GraphicsEnabler=No"; just need to enable graphics acceleration. Thanks for your time and suggestions, artur-pt.
  2. TatsuArekku

    Black screen after 10.9.4 combo update

    Many thanks for the link! I'll get back sometime soon and let you now about any progress.
  3. TatsuArekku

    Black screen after 10.9.4 combo update

    Hi, artur-pt, I've actually scoured the internet looking for solutions and have read very much on what I'm attempting to do. I only posted as a last resort (maybe don't always assume so much?). Anyway, I realize that a kernel panic when attempting to use more than one CPU on an HP is common. I've already tried using a lapic kernel as well as the kernel patcher; neither worked. I will, of course, try again, but I don't know why it would be any different. Fingers crossed, though. I'd love to have done something wrong the first time and for that to be the reason it didn't work. As far as my other issue—having sound but no display after booting into 10.9.4—do you have any ideas? I was thinking it was a kext issue, but I've no earthly idea, really. Thanks for your help, TatsuArekku
  4. Hi, I've got an issue for which I can't seem to find a solution. I had OS X Mavericks 10.9 installed on a hard drive connected to my HP ENVY dv6-7247cl via a SATA-to-USB 3.0 cable. After using the 10.9.4 combo update, I get a black screen when I boot. I have sound (I can push the volume buttons on my laptop and hear the typical accompanying click), so I'm assuming I'm reaching the desktop fine. The screen, however, is absolutely blank. When I boot using verbose mode, I can spot no errors that might be related to the problem. In fact, the readout proceeds and ends like one would expect, only it's followed by blackness. The boot flags I currently use are -v, ncpi=0x2000, cpus=1, and dart=0. I've also tried GraphicsEnabler=Yes and GraphicsEnabler=No, though neither seems to help. Specs are in my sig. Any suggestions would be greatly appreciated! (Also, any fixes for those boot flags I'm having to use—cpus=1, especially—would be awesome.) Thanks, TatsuArekku
  5. Ah, okay, thanks for the clarification. Got me curious.
  6. I hate to post just to be a buzzkill, but I've an HP ENVY dv6-7247cl, and I've yet to be able to upgrade beyond 10.8.1. After weeks of researching and trying possible solutions, I'm pretty sure it's because of the lack of a SATA controller mode option in the BIOS (which, as you noted, shouldn't matter because AHCI is supposedly already enabled ). I, too, get the "Still waiting for root device" on both my 10.8.4 installation and 10.9 installation. I don't want to say "give up" since that would mean I should as well, but just know that anyone with an HP has had the same issue, and as of yet, I can't find a solution. Edit: Just thought I'd clarify about AHCI already being enabled--what I mean is that RAID mode apparently has the features of AHCI, but that doesn't help the situation of it not actually being AHCI.
  7. Thanks for the link, but trust me, I've had a look over that page many times. Thanks for the info; I realize hackintoshing is never 100% and that's it's mostly just for the fun of it, so don't worry, I'm not particularly irritated or anything. I'm not sure what kexts you're referring to by "several kexts for PATA." Could you direct me to them? Thanks!
  8. But you already had the option to change your SATA controller mode to AHCI regardless, correct? Why would you have flashed your BIOS for any reason?
  9. Well, I've replaced the IOAHCIFamily.kext, edited its contents, attempted to patch it, etc, but all to no avail; I feel as if I've exhausted my options concerning it. And yes, I really believe the issue is my inability to switch my SATA controller mode to AHCI; however, I've honestly no idea how to make up for that. I've heard about flashing one's BIOS, but considering how risky it sounds (if I've read the correct information), I think I'd like to avoid that.
  10. Well, the patch didn't work, so I'm fairly sure my problem isn't related to the IOAHCIFamily.kext or its contents in any way.
  11. Eh, the script doesn't seem to work, and an endless array of attempted boot arguments don't seem to either. Thanks for your assistance, though. I'll get it one day.
  12. Thanks for all your help! It's greatly appreciated. I'll give your advice a try. Edit: I just realized I linked the wrong page! Here is what I was talking about, which as you can see is not a kext (I knew those were easily install-able from both Windows and OS X): http://www.insanelymac.com/forum/topic/280062-waiting-for-root-device-when-kernel-cache-used-only-with-some-disks-fix/.
  13. Thanks for the suggestion. I installed both the AHCI patch and the AHCI3rdParty.kext, but I nevertheless receive "Still waiting for root device" when booting without npci=0x3000 and a kernel panic when booting with it. Do you have any knowledge or experience concerning this patch: http://www.insanelymac.com/forum/files/file/36-patched-ioahciblockstorage-for-ioahcifamily/ I feel like it'd be worth trying, but I don't think I can use it from my Mountain Lion partition since the patch employs Terminal. Do you (or anyone else?) know of a way I can make Terminal operations like the patch apply to a separate OS on another partition? Many thanks.
  14. Unfortunately, my BIOS doesn't have the option to change the SATA controller mode to AHCI (which, coincidentally, is why I was amazed that the 10.9 installation recognized my hard drive in the first place). Do you know where can I get an AHCI patch for 10.9? Or, if it's only available and working for 10.8.4, I'd be happy with that too, as I can't upgrade Mountain Lion past 10.8.1 or else I get "Still waiting for root device." Thank you, TatsuArekku
  15. Thank you for your suggestion, artur-pt. When booting with -v npci=0x2000, I receive the same result as before. When booting with -v npci=0x3000, however, I receive a kernel panic. Attached is a photograph of my verbose readout when booting with -v npci=0x3000. Thanks, TatsuArekku