Ok so I have Zephyroth 10.5.2 rev. 1 and the dvd boots up fine. Originally I used to be able to install and boot right up. After a few re-installs (broke my system a few times) I get "still waiting for root device after the install". I chose all the same options. I must have tried to install it 10 different ways from just essential system software to clicking everything. The weird thing is, if I put my hard drive in an external usb case I can boot up and use the system just fine. But now after the first reboot when i boot externally (this didn't happen before by the way) I get an error like this: USBF: 34.293 AppleUSBEHCI[0x3910800] : : Found a transaction past the completion deadline on bus 0x53, timing out! (addr: 2,EP:1).

I have no idea what that means.

I have a HP Pavilion dv5000
AMD Turion 64.
ATI radeon express 200
IDE hard drive.
2 gig ram.

I don't know the motherboard, let me know if any more info would help in solving this problem and I'll try and look it up.

Any ideas to why this is happening, I don't understand why at one point it would boot internally and now it wont. And now it crashes externally as well. Any ideas, input or help is appreciated. I would really like to figure this out!

thanks!

I've had that happen before as well. 1) timing out might be a sign of a disk failing. 2) check that you've reinitialized the disk the same way... if you've wiped it in the past to work on it, that may be the ticket again. 3) check that you've got it plugged in to a good connection. I know this sounds dumb but the ports on the front of my case aren't as responsive when booting up as the ones that are built-in to the motherboard in the back. Also, try reinitializing with
<b>diskutil list</b> Note X for later
<b>diskutil unmount diskX</b> (unmount it so when you write the MBR code in FDISK it will work the first time)
<b>fdisk -e /dev/rdiskX</b> X being disk #
<b>reinit</b>
<b>update</b>
<b>f Y</b> Y being partition #
<b>w</b>
<b>q</b>

---

hmm... those are the same problems i had on my hp T3310 before it died, the cause was the chipset it wasn't cooled properly and over time it got destroyed

---

http://filebeam.com/ed1d2cc264d475f3...b57f7de191.jpg

Nah, you need to mod your chipset kexts, search in insanelymac, theres a guide with all the requiered kexts. ^^!

I need to mod my chipset kexts? I don't have much experience with that because everything seemed to work the first time for me. Can you tell me what that means? I don't even know where to begin.

Thanks for the input, I suppose the disk could be failing, I didn't really think of that. I have had problems with my computer overheating before, so maybe I'll open it up today and clean it out.

But anyhelp would be great for the kext thing, even just an example and from there I could just figure it out. (or just a link to a guide)

thanks!