|
tried the update and it didn't work actually i got some script error while asu was checking for cpuids then it froze solid. i rebooted and the new bootloader doesn't work. so i used the kalyway disc and booted to hd using the install disc and all is fine. now i need to know how to restore old bootloader. anyone?
|
never mind i repaired bootloader with OSx86 tools, worked like a charm. Still can't update though. gotta be something i am doing wrong.thanks for all the help erick2red
|
The voodoo XNU 9.5.0 kernel only works with 10.5.5 or 10.5.6 correctly. Have you already stated the Activity Monitor to check if both cpu cores are used?
|
I've done the update downloading the dmg from apple (check SHA1 cause it fails many times) and installing just like on an intel pc. I could do that cause I had voodoo kernel and the disabler kext. Voodoo installs itself as mach_kernel.voodoo, so it isn't overwritten by the update, also I don't use any modded kext (except for the ps2 fix that I had to reinstall) Disabler takes care of appleintelcpu.... and that's all I think.
Anyway you should do a backup just in case. Good luck! EDIT: once you got it running you should restore system and seatbelt kexts from a 10.5.5 installation. System kext is included into voodoo's installer and I can send you 10.5.5 seatbelt if you want. |
ya could you send me seatbelt, and what is sha1? kind of a noob. thanks for all your help
:) |
Go to the update download page and you'll see an explanation there, it's just a command to check the file integrity, like md5.
|
thanks i will,and thanks for the other. appreciated.
|
Okay i did a update to 10.5.5 and now i reboot and get this error and it hangs in the boot process. cpu lite is on the whole time but nothing happens. max time left on 10min.
error "failed to load extension com.apple.driver.apple.usbehci" i only assume this is a error b/c of the word failed and the fact that the text is in yellow. Any ideas would be great. for those of you that have helped thank you for your patients with this newbie. But i AM LEARNING...SLOWLY:-| |
try booting "-x" and let us know what shows the boot logs
|
i did what you asked but i took a picture instead
|