9.8.0 v2 kernel by Qoopz - based on Voodoo - for Intel/AMD/i7.

Download:
http://rapidshare.com/files/266666710/Vood....XNU.980.v2.zip

Introduction:

The Voodoo XNU kernel is a fork of the XNU kernel shipped with Apple®
Darwin operating system – the open-source foundation of Mac OS X.
Voodoo kernel aims to expand the range of processors supported by XNU, and
provide technologies to enable Darwin and associated applications to run on a
variety of x86 platform combinations. Technologies included in the Voodoo kernel
range from emulation of SSE3 instructions, to on-the-fly patching of loadable
binaries. The kernel also fixes issues with multi-processor timing synchronization,
SpeedStep™ support and sleep/resume.

Tested, working perfectly here. I have installed it since yesterday, and I hadn't have any problem with it. Previously I used qoopz 9.7 kernel and I needed this one to have a complete 10.5.8 upgrade.

I used qoopz 9.7.0 kernel from iATKOS v7 and Parallels Desktop & VMWare causing Kernel Panic.
I have to downgrade my kernel back to 9.5.0 to make them work.
Is this new release address this issue?

I had no problems with qoopz 9.7.0 and qoopz 9.8.0 with parallels. Are you using this kernel as mach_kernel or is it named differently (I've heard about some problems with vmware when the kernel has a different name than mach_kernel).

Exactly.  Parallels kernel panics when the kernel is not named mach_kernel.




Exciting stuff, huh?

Out of respect for the Voodoo team can we have the source code published as well?

Qoopz 9.8 diff patch is released with the kernel, is it what you are looking for?

Oops missed it. Thanks for pointing it out.

try this script, it downloads and builds xnu and all dependencies. if for some rare reason, libc fails to build, temporarily mv /usr/lib/dtrace while building it.

Tried on AMD, it works.
There is no crash or bug so far.

Keep going!

Tried on AMD too. Everything went perfect until I tried to run the Dropbox application. I was prompted to enter the admin password and voila - kernel panic

Here's the screenshot: http://dl.getdropbox.com/u/442960/DSC00622.JPG

BTW I tried to install Qoopz 9.8.0, AnV 9.7.0 and even Voodoo 9.5.0 and it's still absolutely the same I use iDeneb v1.6.

Can be something done about that? Or can it be caused by some other extension or fix installed during the installation of iDeneb?

man i have the same thing. it started after 10.5.6 update and switching to voodoo kernel, so it seems that problem in it. i don't know, how to fix it to avoid the kp, so used to delete dropbox, though it's rather useful app.

No need to delete Dropbox. Go in to



and delete the file FinderLoadCM. If you can't do this on startup because Dropbox starts up before you can delete the file, you will have to delete it in single user mode (-s boot flag).

Boots up, but stops loading before a Logins screen apears...

same here boots up but it's stuck at apple logo . it doesn't log in. i had to put back vanilla.

I run the voodoo2 kernels and both Paralels and VMware-Fusion. The method I use to get around this issue is a symlink. It also has the advantage of protecting you if an apple update replaces mach_kernel.

For example, assuming your kernel is named mach_kernel.voodoo2 You can do the following:


On my system it looks like this:


Then, edit your com.apple.Boot.plist and change the kernel name to mach_kernel.voodoo2

That should help Parallels or VMware-Fusion run and if apple updates the kernel the worst you should need is to rebuild the symlink.

i have had problem going from 9.5 and higher. Parrallels crashes. And kp at startup, but i have always be able to get in the desktop by using cpus=1, than you can reinstall or whatever you have to fixed.

hopefully this helps

i had the same problem, and i found out why. iATKOS boots with /custom for the kernel, i fixed it for myself by following the symlink post made in this thread after i copied the kernel "custom" and renamed it mach_kernel.voodoo2 and then there's no need to edit booting or anything, and it ran right off the bat! hope that helps better with the iATKOS install!

i have one question. etqw and call of duty 4 1.7 single player cracked work on amd machine?

on all voodoo kernel i don't have working crack for call of duty 4 for single player((

Quick question...I am using xnu 9.6.0 and OS X 10.5.7
I am upgrading the OS X to 10.5.8 and installing the xnu 9.8.0
on an Intel P4 w/HT. What System.kext and Seatbelt.kext do I need?

Thanks Maya 77!

Im on a AMD with Nvdia MP65 Chipset - OSX 10.5.8.
Almost everything is working, except sleep (never worked) and USB 2.0 (it was working with voodoo kernel 9.5.0)
But im very satisfied with this kernel, it made my system to work realy fast and stable!
I'm still testing it, and i can tell you there's no more "kernel_Task" consuming my CPU.



I was seaching for those files and i found one on this topic

http://www.insanelymac.com/forum/index.php?showtopic=148566

this solved my problem mounting DMG files, but i'm still searching for a System.kext to make my USB to work properly.
If someone find a solution let us all to know.

Good kernel except I'm getting kernel panics on my AMD when trying to run VMWARE. . .

Newbie question. I've googled, searched the forum, but can't figure it out. How does one upgrade the kernel from 9.7.0 to 9.8.0 v2? The documentation PDF reads "The best way to install the Voodoo kernel is to run the included installer package." - but there isn't an installer package in the download.

There are manual instructions, but a host of problems noted with them so I'd much rather use the other way which fixes all of those.

Thanks.

snokarver, install the Kernel with pcwiz osxtools. 

http://code.google.com/p/osx86tools/

Thanks. I tried osx86tools multiple times. It makes a backup of the kernel, but after reboot I go back to check and see which one it's using, it's still using 9.7.0.

Then I realized the iATKOS boot plist defines the kernel as "custom" - I renamed that to mach_kernel and now it work. Thanks again!

Thanks a lot boba899, you just saved my day...

Qoopz 9.8.0 get's crashing always until dual (only!) cores based AMD mobile processor get's hot enough (on single core ones it isn't happening ever).
maybe, before that happened it seems like frequency is floating and doesn't match sync between cores, so kernel panic on some miss-sync operations. and so we are having different tasks crashing during the boot, but only until that. and so when it get's hot enought it starts working fine for a while (during one session), and even after that it's fine to reboot and nothing will crash anymore.

please confirm anybody having same behavior.

I think this fix is working for me too ... thanks! How the heck did you figure that out?