jimmyco2008

Sorry for taking a break from InsanelyMac for a while!  No, the HDD has nothing to do with this, "waiting for root device" with a USB installer basically means that the USB port the flash drive is plugged into is not functioning properly with OS X/the installer.  In other words, the installer, which has been loaded onto the RAM of the ultrabook, can no longer see the flash drive on the USB bus/chipset, it's not being detected.

This is especially true of USB 3.0 because, at least last I checked, USB 3.0 doesn't work right on Hackintoshes, except with USB 3.0 devices.  I suppose you might try a USB 3.0 flash drive in a USB 3.0 port, but I'm not sure, since you can't get this 2.0 drive to boot in a 2.0 port.

Again, really weird situation, it's a perfectly-hackintoshable ultrabook..... Try, when it gets to waiting for root device, plugging the flash drive into EVERY USB port, yes the 3.0 ports, when you plug it in to each, wait a minute, if you have a flash drive that lights up, it should start flashing almost immediately, if it does not, you can move on to the next port.  Otherwise, give it a minute in each port!

Good luck with sleep, I could get it working on the m6-1045dx (check out the guide for that), but only with some kext edits (well not edits, deleting and installing a couple), and even then it was only when on battery power, and it broke Bluetooth.

A little while ago I casually came across a possible fix for the Bluetooth thing, I kind of forget what that was, though :/, but you may not even have that issue.

The m6-1045dx guide also has kexts for battery, there's three, there WAS four, but the fourth kaused KPs, and its removal did not affect operation of the battery meter.  Just google "m6-1045dx guide" it's up there in the list of results.

The CPU, chipset, GPU and mobo would have sufficed!

I just went through this a couple of weeks (or was it last week?..) with an AMD desktop, honestly I forget what I did to get around the waiting on PCI device thing. Maybe PCIRootUID=0, give that a go, I'm pretty sure it was along the lines of the boot flags you're trying (PCIRootUID and npci).  There's something you can run to see if it's supposed to be PCIRootUID=0 or PCIRootUID=1, a command in Terminal, but you'd have to get to the desktop first... Hmm, how'd I do that?.. I remember running it in Terminal and confirming it's PCIRootUID=1 for my mobo....

Anyway, try all those npci combos with PCIrootUID=0.  If that doesn't work, I'm trying to think of all the boot flags I have used... arch=x86_64 was one.. GraphicsEnabler=Yes, I tried No, too, I don't think it made a difference... I DO know, at least for my computer, removing all PCI cards did not stop this from happening, so don't worry about disabling your graphics card or WiFi or anything like that.

Consider using a USB installer with Chameleon (myHack for example!), if only because disk data transfer is slower.  Although I will say that for people without Macs or Hackintoshes or VMs of OS X (basically no access to OS X), disks are "easier".

But yes, Google is your friend in this case.

Good luck!

Thanks for the reply... Keyboard only works in Chameleon, it does not work in OS X at all, including in the -s environment... Unless I can do this via the myHack USB installer?

EDIT: That's a no-go, keyboard doesn't work, either... It's almost like it's frozen, Num lock is on, but I can't turn it off or anything... If I turn on caps lock at the BIOS boot, it stays on "frozen", too.

Makes sense since the same kexts on the myHack are on the HDD.... I forget if keyboard works in the installer menu, but if it does, can I enter the commands into Terminal?

Oh! I have a Macbook Pro and a USB to SATA cable I've been using to install PS2 kexts on the Hackintosh HDD... Can I do something with access to the file system?