Still waiting for root device

[tauroid]

Hi all,

 

I'm trying to install iATKOS_L2 to my Asus 1015pn netbook; I've made a bootable USB stick of it and installed chameleon to it. When I try to boot iATKOS with -v, however, I stall at the screen in the picture and it keeps writing "still waiting for root device" about once every 30 seconds or so. If anyone knows why this happens that would be great! I've been trying to get this working for a while now.

 

Thanks

 

P.S. cpus=1 -x -v gives me the same thing

 

edit: slightly clearer image

edit: boot -> root

[Gringo Vermelho]

"Still waiting for root device" means that OS X can't see your drives, normally this happens when there is no driver on the install media for your SATA/PATA drive controller. It can also happen because of BIOS settings.

 

Find out which driver or legacy kext works with your hardware and add it to your Chameleon installation's /Extra/Extensions folder.

[tauroid]

yep, root, sorry about the typo there

 

Apparently my SATA controller is ICH7, which should be fine(?). IOATAFamily.kext is in the install medium and I can see it being loaded when I use -x as a boot flag.

 

Should I try to find a modified driver and see if that works? How would I find it?

 

Thanks for your time.

[Gringo Vermelho]

Try ATAPortInjector.kext in /Extra/Extensions. Just drop it in there, Chameleon is responsible for loading everything in the /Extra hierarchy and it doesn't care about permissions or ownership.

[tauroid]

Nope, it just goes back to the same screen. It's definitely loading it too, I can see it in the chameleon "read HFS+ file" log.

[Gringo Vermelho]

Also try AHCIPortInjector.kext, AppleIntelPIIXATA.kext. Not at the same time though.

 

ICH7 works fine but the most common models don't have AHCI, this is why you need a patch for it.

[tauroid]

No luck with AHCIPortInjector.kext, AppleIntelPIIXATA.kext is in IOATAFamily.kext already. Should I try ATAPortInjector.kext with AHCIPortInjector.kext or will that not help? AHCI is enabled in BIOS. Could this be an issue with any of the other drivers?

 

Thanks for your help by the way, this has been quite a frustrating problem for me

[Gringo Vermelho]

AHCI is enabled in BIOS.

In that case it should work with AHCIPortInjector.kext and the drivers that ship with OS X.

 

Open the info.plist inside AHCIPortInjector and verify that the device IDs for ICH7 in AHCI mode match with yours. If not, change them to match.

Compare with Windows Device Manager or run LSPCI -nn from a Linux live CD (Linux Mint is nice). Live distros normally don't come with LSPCI, you will have to install it first. I don't remember how to do that anymore though.

[tauroid]

Is the device ID a number [xxxx:xxxx]? How do I edit it in? Also my copy of AHCIPortInjector.kext only has an info.plist, no executable - is that right?

[Gringo Vermelho]

Yes that's it, if in doubt, just look closely at the other device IDs in the plist to learn how it's put together. Compare with the device IDs in Windows Device Manager (or where ever you get it from). When you see "8086" that means Intel, that's called the vendor ID but you should leave that alone of course.

 

Yes, that's called a legacy/plist-only kext or simply an injector. It adds to or replaces plist contents in already existing drivers. I use the same trick for my Marvell Yukon 88E8056 ethernet but it can be applied in many other cases.

[tauroid]

Okay, well this is the ICH7 section:

<key>ICH7AHCI</key>
	  <dict>
		  <key>CFBundleIdentifier</key>
		  <string>com.apple.driver.AppleAHCIPort</string>
		  <key>Chipset Name</key>
		  <string>ICH7 AHCI</string>
		  <key>IOClass</key>
		  <string>AppleAHCI</string>
		  <key>IOPCIPrimaryMatch</key>
		  <string>0x27c18086</string>
		  <key>IOProbeScore</key>
		  <integer>2000</integer>
		  <key>IOProviderClass</key>
		  <string>IOPCIDevice</string>
		  <key>Vendor Name</key>
		  <string>Intel</string>
	  </dict>

 

I assume 0x27c18086 is the important part because my device ID is 8086:27c1. It seems okay to me...

 

Is all this necessary for it to boot from the USB device? That's what I'm trying to do if I wasn't clear .

[LatinMcG]

theres a run_me.zip maldon uses to get dsdt and kextstat and ioreg..

 

run this and post the send_me.zip

[tauroid]

ah, I don't actually have an OS X installation on it yet so I can't run that. Should I try with an earlier version of OS X and work from there or will the version likely not make a difference?

[LatinMcG]

try booting linux mint on usb or cd and do the steps to get dsdt

in terminal with internet connected to dload acpidump

sudo apt-get install apcidump iasl
mkdir ~/acpiinfo ; cd ~/acpiinfo
sudo acpidump > acpidump.txt
# enter password
sudo acpixtract acpidump.txt
ls *.dat | while read i; do iasl -d "${i}"; done
pid=`sudo dmidecode -s system-product-name`
vid=`sudo dmidecode -s system-version`
name=${pid// /}.${vid// /}
mkdir "${name}" && cp *.dsl "${name}"/

then copy the folder of pc name in /home/mint/ to a zip then post

[tauroid]

here you go

1015PN.x.x.zip

[LatinMcG]

i was looking into it. i think its the _OSI activates the mode of detection. might have to use a simpler Device (IDE1) from dsdt of some other laptop with ich7.

 

i been busy with work and kid .. but i did look into it for good 30 mins.

[tauroid]

OK, sorry for bumping it's just sometimes hard to tell on the internet what has happened to the thread Thanks for your time, I'll try to work it out from here.

[Gringo Vermelho]

OK, sorry for bumping it's just sometimes hard to tell on the internet what has happened to the thread

 

Bumping is against the rules and there is no valid excuse for it.

 

Use the "my content" controls (click your username up top) to see a list of all your topics and all threads you have posted in.

 

The old forum had the same functionality.