No, haven't used the sleep enabler. Like I said, that's not that big of a deal. The only time it's an issue is when it gets too hot and shuts itself down, it's almost like it goes to sleep instead of shutting off. Or hibernate or somet, I'll look into that once the rest gets sorted..
Quote:
|
You can try if NullCPUPwr works better... (Be sure to downlaod Leopard version!)
|
Thing is, I don't know what I need disabler or nullcpu for, so not sure how I'd know it's "working better"...
I read somewhere that having kexts or whatever that did the same thing could jack it up. I know you have to disable/unload/delete some things before you use the voodoops2controller, wasn't sure if this was the same.
Quote:
The problem is quite simple one. When you run update your Kernel Binary is replaced with Vanilla Kernel, which can't boot your system.
You need to create a back-up of it first. Do the following on Terminal:
Quote:
sudo -s
cp /mach_kernel /bak_kernel
cp -R /System/Library/Extensions /Extensions_bak
Then remove any dsmos.kext or AppleDecrypt.kext from your system and replace it withfakesmc v2 Leopard
Then reboot and run the next higher single update (in your case 10.5.5) and use "/bak_kernel -v" to boot into your system again, once done.
Then run the next higher update. Once you are on the version you want, delete mach_kernel using "sudo rm -f /mach_kernel" and copy back your old one using "sudo mv /bak_kernel /mach_kernel"
To fix Kernel Panic on dmg mounting - Reinstall your old seatbelt.kext from /Extensions_bak
To fix USB mounting - reinstall system.kext form /Extensions_bak
|
Okay, I'll be trying this this evening when I get home. Basically, I need to backup the kernel I'm on now, replace dsmos and/or appledecrypt with the fakes you gave, reboot, run the 10.5.5 update from apple using the flags you posted to boot back into osx and repeat until I'm on 10.5.7 or so? Say I go to .7, I can still use voodoo 9.5 to boot into it?
I think one thing I may have been doing wrong before is not using the flag for old kernel at boot, I would just restore it using osx86tools before I rebooted. That's wrong I take it? Should I do anything after the update finishes before I reboot? Also, when I get it all said and done, do I need to restore any of the old kexts, or all of them (not delete, I know!)? Or just assess what's working and what's not then go from there? Doing all this made me think that maybe my system wouldn't go higher than 10.5.4 due to hardware, is that the case or is it user error? If it can't go higher, I'm fine with that, just wanna know so I can stop trying...
Thanks for the help, both the forums I post on you've been the most helpful. Cheers.