AnV XNU 9.7.0 V1.5

andyvand · #1 07-03-2009, 12:42 AM

I recently had a lot to do with my life so... no time....
But now I've found the time for the new and improved AnV kernel with extra good memory management and Core i7 optimizations.
Enjoy...

Download for the new version (including source):
http://rapidshare.com/files/26536154...-970-1.5.1.zip
Legacy AppleIntelClock driver download:
http://rapidshare.com/files/25123900...IntelClock.zip

It could be a little while longer when you'll hear from me (unfortunetely).
You'll hear from me in a little while (I'm not done/gone yet...)

maya77 · #2 07-03-2009, 12:55 AM

Thanks, I'm going to try it and let you know how it works.

maya77 · #3 07-03-2009, 12:57 AM

Do I need to install IPFirewall.kext ?

What it's used for?

andyvand · #4 07-03-2009, 01:03 AM

IPFirewall.kext is the firewall pseudoextension...
It is used for controlling the firewall in the kernel

maya77 · #5 07-03-2009, 01:27 AM

No luck.

Renamed kernel file to mach_kernel, copied it to system partition root w/replace. Installed System.kext, seatbelt.kext, and IPFirewall.kext using OSXTools. When I reboot and select my Leo partition in Chameleon boot menu it goes to Apple logo screen where it just loads forever.

Reverted to 1.4, all works fine again.

-AMD Opteron 180
-Leopard 10.5.6 retail installed
-10.5.7 Update applied
-Chameleon 2 RC1 used to boot

eMatoS · #6 07-03-2009, 04:55 PM

Working great so far in my pc (signature)
I've installed only the kernel and used original system, seatbelt and ipfirewall kexts.
Andy, what's the difference between vanilla and your system.kext??

Thank you very much andy for taking the time to do this.

maya77 · #7 07-17-2009, 10:43 PM

Andy should fix this.

I miss Voodoo :-(
They have problems with human resources and there is no ETA for Voodoo v2 9.7.0.

maya77 · #8 07-18-2009, 01:08 AM

UPDATE:

I've found a way to fix this all:
http://www.infinitemac.com/f19/how-t...-pc-efi-t3402/

andyvand · #9 07-24-2009, 04:57 PM

I would need some more info on why it gets stuck immediately after booting...
If somebody could build a debugging build (I can't publish for the moment) we could trace it down...
It could have something to do with the new i7 cpu starting procedures...
I'll check it from here and if anybody can test it with a serial debugging console on a debug build... please do... everything is working fine for me...
you can still set the model name with macmodel=MacPro2,1 e.g. or with -nomacmodeloverride boot arguments (to disable it)

windsor · #10 07-24-2009, 06:51 PM

dear andy, i have same error (boot stop on "using 16384 buffer headers and 4096 cluster IO buffer headers") after i do fresh install my hack, and using this kernel.

i can boot with "cpus=1" boot arg.