Posted 27 January 2010 - 01:22 AM
1..download a Voodoo Kernel from one of the links below that matches the system version you're upgrading to.
2..rename the kernel.
3..set correct permissions and ownership on the kernel.
4..Optionally use a symlink to the renamed kernel to allow software that requires the kernel to be named mach_kernel to run. Here's how:
http://www.insanelym...p...t&p=1234670 (As you can see, VMWare requires this for example)
Name the kernel whatever you want, as long as it's not mach_kernel. You can name it mach_kernel.voodoo for example. Drop it at the root of your system drive, open /Library/Preferences/SystemConfiguration/com.apple.Boot.plist and change where it says "mach_kernel" to whatever you renamed your kernel to, and then set the correct permissions/ownership on the kernel (more details below).
If you're using the Chameleon 2.0 Bootloader, you should use /Extra/org.chameleon.Boot.plist instead. Anything in this plist will override what's in /Library/Preferences/SystemConfiguration/com.apple.Boot.plist, which you can safely leave unmodified.
You can use plistedit pro (google it) or the free plist editor that comes with Apple Xcode to edit this file.
This way, you can safely install a 10.5.x update, because when mach_kernel gets updated your system will still boot using the renamed kernel.
Hackintosh history lesson: The original Voodoo 9.5.0 kernel installer did that for you automatically and even came with its own 9.5.0 system.kext.
To avoid issues with System/Seatbelt kext (these must match kernel version number, you will run into various problems if they don't) use a kernel that matches the system version you're upgrading to - there have been releases for 10.5.7 and 10.5.8 - see links below.
I think anyone will agree that it's a lot less hassle just to rename and copy a single file to your root directory than to mess around with kernel extensions.
You don't need to use Disabler.kext or Netkas' good old "while sleep 1 ; do rm -rf (...)" - the Voodoo Kernel has built-in blacklisting of non-vanilla-hackintosh-unfriendly kexts such as AppleIntelCPUPowerManagement.kext. As long as you keep your Voodoo kernel renamed you don't have to worry about it. If you don't believe me, read the manual. I've attached it below.
Don't forget you need to have a decrypter installed, such as FakeSMC.kext* by Netkas (make sure to get correct version for 10.5.x). Older ones are DSMOS.kext and AppleDecrypt.kext. Do not install more than one of these.
*notes on fakesmc.kext
fakesmc topic at Netkas' blog: http://netkas.org/?cat=15
next-gen fakesmc w/plugin support: http://www.projectos...p?showforum=165
fakesmc.kext is meant to be used on full retail (that includes the kernel) installations and will not work with the voodoo kernel as-is because it requires that one of the extensions that the Voodoo Kernel disables is loaded.
If you want to use fakesmc kext with the Voodoo Kernel, you have to disable the Voodoo Kernel's kext-blacklisting feature first. You will then need to use a disabler.kext that disables at least AppleIntelCPUPowerManagement.kext. Some disablers that are in circulation also disable some other kexts that may or may not be incompatible with your particular configuration. It's easy to add kexts to (or remove from) the plist in disabler.kext, open the plist inside in a plist editor to see how its done. To disable Voodoo Kernel kext-blacklisting, add blacklist=0 to the kernel flags key in /Extra/org.chameleon.Boot.plist.
This concludes the basics that are the same for everyone - the rest will be different depending on hardware and what your basic Hackintosh approach is - as in, if you're running Vanilla or Distro and whether you've set up Chameleon with all mods in /Extra or if you do it the old fashioned, dangerous way with all your modded kexts in /System/Library/Extensions. Please respect that further discussion of this is outside the scope of this thread, there are too many unknowns.
This is the Voodoo Kernel manual - a must-read for anyone who can't use the Vanilla kernel:
Voodoo_Kernel_User_Documentation.pdf.zip 122.63KB 345 downloads
Voodoo kernel developer interview:
Qoopz 9.8.0 v2 Voodoo kernel release thread:
Voodoo.Based.XNU.980.v2.zip 3.18MB 102 downloads
Qoopz 9.7.0 Voodoo kernel (with source diff - download both parts and open w/ Stuffit Expander):
Qoopz_9.7.0_Voodoo_XNU_kernel.part01.sitx 1.5MB 118 downloads Qoopz_9.7.0_Voodoo_XNU_kernel.part02.sitx 1.26MB 111 downloads
For 10.5.6 you can use the original 9.5.0 Voodoo Kernel along with System.kext and Seatbelt.kext from 10.5.5.
For more information go here: http://www.insanelym...howtopic=148566
The original 9.5.0 Voodoo Kernel is available at the xnu-dev google code site: http://code.google.com/p/xnu-dev/
I don't recommend using the AnV 9.6.0 kernel as it has a few (and now obsolete) modifications that could complicate things for you:
If you decide to use this kernel anyway, please refer to the release thread for support questions and issues, I can not help you.
Setting correct ownership and permissions for the kernel:
Open Terminal, type sudo - s (and your password)
chown 0:0 /kernel_name_here
Good Luck. If you post a reply in this thread, please do not quote the whole post as I might update the contents.
Posted 28 February 2010 - 01:06 AM
Could you please be specific on how to proceed as you've been with getting the kernel ready. I got and installed the 9.8.0 Voodoo Kernel, installed it and have no problems. I had to boot with -v -f after the install but since then it's working. Please help on how to proceed to update to 10.5.8 from the options above, or any ideas outside of those you might have.
Thanks a lot. Your explanation on Kernels make a ton of sense and has been very helpful this far.
Posted 28 February 2010 - 08:34 PM
Please start a new thread.
Could you please be specific on how to proceed as you've been with getting the kernel ready.
I would prefer not to turn this into a support thread for issues that has nothing to do with the topic (updating/installing a kernel). The main idea is to keep it as universal as possible, providing support for your specific case here would undermine the topic and confuse the issue.
I would like to encourage anyone posting here to only discuss the topic at hand - thanks for your understanding.
Posted 03 May 2010 - 05:14 PM
I downloaded the 10.5.8 combo update and figured I could do the same method, install the update, reboot into single user mode and copy my backup of mach_kernel and said extensions over... HOWEVER.... the 10.5.8 combo update froze up my whole system at Writing Files (14%).
My question is, will this method of updating you've presented avoid this problem? Do you presume it froze because it updated the kernel to the Vanilla one from the combo update or maybe those blacklisted extensions got in somehow...? I'm asking before I do the procedure because as a result of the above, I had to clear my partition and reinstall 10.5.2 :'-(
Thank you for your instruction ;-)
Posted 04 May 2010 - 12:27 PM
If you don't rename the kernel it will get overwritten by the vanilla kernel when installing an update. That's the reason why you should rename it (and adjust /Extra/org/chameleon.Boot.plist accordingly).
Do you presume it froze because it updated the kernel to the Vanilla one from the combo update or maybe those blacklisted extensions got in somehow...?
Logically, since it's the Voodoo kernel that does the blacklisting, if it gets replaced with the Apple kernel, then there's no more blacklisting.
I already explained this in the first post.
The (obsolete) modbin kernel had its own set of features and limitations. I don't remember what they were.
If you're using the modbin kernel then I can't help you. This thread is about the Voodoo Kernel and Voodoo kernel derivatives, please stay on topic!
A Voodoo kernel derivative uses the Voodoo Kernel codebase and inherits all its features.
The kernels linked to and attached in the first post are all Voodoo-based and share the same features.
About org.chameleon.Boot.plist (or com.apple.Boot.plist, if you're using an older version of Chameleon) and where to put it, I believe I was clear enough about that in the first post and so I see no reason to repeat it.
Posted 18 May 2010 - 03:05 AM
Posted 20 May 2010 - 02:33 PM
Asking about whatever else you need to do is off topic and does not belong in this thread
Please read this post before posting here:
Posted 20 June 2010 - 02:57 AM
Posted 20 June 2010 - 03:03 AM
If you were able to extract the contents then you're good.
Posted 20 June 2010 - 03:05 AM
Just to confirm, what is the size you got when you expand it? Just to make sure I have the correct size file.
mines are 6,035 & 6,773kb
Posted 20 June 2010 - 03:09 AM
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users