10.6.5 legacy kernel for INTEL/AMD 32+64bit ready to download by qoopz/nawcom/AnV/BlackKnight/mucha - a few new features

[Andy Vandijck]

This is the latest xnu release:

- Supports everything the previous legacy kernel support

+ 64bit working kernel (Intel/AMD) thanks to Azimutz

 

New V2:

+ VMWare and Mac model override fix thanks to Nawcom

+ Removed bad (causing reset) routines from x86_64 kernel (smaller kernel advantage)

 

Download (V2):

http://rapidshare.com/files/433298253/lega...l_10.6.5_V2.zip

 

Source diff (V2):

http://rapidshare.com/files/433298660/lega....17-v2.diff.zip

 

I decided to repost the amd instruction patcher

Download:

http://rapidshare.com/files/432036976/amd_insn_patcher.zip

[Mohamed Khairy]

This is the latest xnu release:

- Supports everything the previous legacy kernel support

+ 64bit working kernel (Intel/AMD) thanks to Azimutz

 

Download:

http://rapidshare.com/files/431601452/mach....5.0_legacy.zip

 

Sources:

http://rapidshare.com/files/431601624/lega...4.9.17.diff.zip

 

thanks andy very much

i was waitng it

[MacKonsti]

Is there any benefit to running this legacy 10.6.5 mach_kernel instead of the vanilla one, for us users with "non-Apple compliant" CPUs like mine, the Intel Q9550 Core2Quad at 2.83GHz? I would really be interested to know... It's faked as Xeon on my machine, obviously...

[scififan68]

Working better than other kernels I've used, but still not prefect for my AMD x2 5600+.

"mDNSPlatformRawTime: last_mach_absolute_time 30ECEED300000064" printed in console over.

Also odd cpu uages numbers in mplayer:

seems the tsc issues for amd x2, are still there, but if you could look into, it would be highly appreciated.

[Mohamed Khairy]

arch x86-64 dosent work

also same problem with quick time crashes on 64

i am so sad

but thanks for your work andy

[chickeneyes]

Can anyone tell me how to install the kernel and update to 10.6.5...????

 

Had some serious USB problems after updating via combo updater 10.6.5

[xdoom7]

Hello,

 

I installed the legacy 10.5.0 kernel with arch=x86-64, but get a kernel panic with continuing scrolling error messages which i stopped by using the power button.

With the boot option -force64 the kernel is working very good and i can say that the system is more responsive than with legacy kernel 10.4.0.

 

cheers

[dickhouse]

Instant reboot on my rigs, have to use arch=i386 to get pass still havent taste 64bit flavor. but its all good, boot-up takes a lil bit longer from previous legacy_kernel 10.6.4. Can force64 ext but 32bit apps crashed just like usual./

 

mem. consumption on 1st boot, took approx total 500mb rather than 800mb on prev kernel. i use i-stat for that up from 11.2 to 11.5 well as you can see it doesnt matter for me but there's a good sign for this new legacy kernel, lot of room for improvement.. good job!

 

 

 

btw thanks for your hard work Andy...

[VampireMI2]

I wait it long time.

but i very happy

[XoVoX]

Instant reboot.. nor I386 nor x86_64 work.. damn

 

With Chameleon r5 it works now (32bit)

 

But now I get this error message:

dyld: shared cached file was build against a different libSystem.dylib, ignoring cache

 

What does this mean? What went wrong?

[Thunderburn]

Keep rebotting after instaling legacy 10.5.0 kernel, try using -v, -f , -v -f, arch=i386, x86-64 , still no progress, any suggestion?

[Andy Vandijck]

Keep rebotting after instaling legacy 10.5.0 kernel, try using -v, -f , -v -f, arch=i386, x86-64 , still no progress, any suggestion?

Try the following boot arguments for 64bit:

arch=x86_64 -notscverify -force64

 

32 bit part needs following:

arch=i386 -force64

 

Instant reboot.. nor I386 nor x86_64 work.. damn

 

With Chameleon r5 it works now (32bit)

 

But now I get this error message:

dyld: shared cached file was build against a different libSystem.dylib, ignoring cache

 

What does this mean? What went wrong?

You need to update the dyld shared cache.

 

Under Terminal run:

sudo update_dyld_shared_cache

 

Wait till it finishes and no more ignoring cache warnings.

[scififan68]

32bit and 64bit both work for me on my AMD x2 5600+ when I used the bootflags "arch=x86_64 -notscverify -force64"(for pure 64bit) but for some reason I can't load 32bit apps, with or without the patched dyld. With -force64 everything loads fine(even 32bit apps!), but Im not sure if thats because of the patched dyld or not.

[Mohamed Khairy]

tried

busratio=16 -notscverify -force64

but also do restart

it is hopless case

[xdoom7]

Try the following boot arguments for 64bit:

arch=x86_64 -notscverify -force64

 

-with above boot commands osx crashed with mach_kernel 10.5.0

 

 

-with arch=i386 -force64 osx boots well with mach_kernel 10.5.0

and see several apps in activity monitor like safari, finder etc are loaded 64bit

but in system profiler i see this.

 

 

Systeemsoftwareoverzicht:

 

Systeemversie: Mac OS X 10.6.5 (10H574)

Kernelversie: Darwin 10.5.0

Opstartvolume: Snow Leopard OSX

Opstartmodus: Normaal

Computernaam:

Gebruikersnaam:

Beveiligd virtueel geheugen: Geactiveerd

64-bits kernel en extensies: Nee <-----------------------

Tijd sinds opstarten: 2 minuten

 

 

cu

[apatsufas]

Thanks Andy work great!! (using arch=i386)

 

I only get one message

 

disk3s2: ioctl(_IOW,'d',9,0) is unsupported

 

Do you have any suggestions?

[PRISACARU]

hi, just a KP, on INTEL P4 640... tried -v, -f, arch=86_64 -notscverify -force64... with BETA legacy kernel 10.5.0 (10.6.5) work 32/64.... this new kernel give error something with ACPI. kernel needs ACPI v 1.3.5

 

[scififan68]

tried

busratio=16 -notscverify -force64

but also do restart

it is hopless case

 

What bootloader are you using?

[Azimutz]

Hi guys.. Andy, looks fine besides two annoyances; first, this stuff seems ok:

Nov 18 22:36:45 localhost kernel[0]: npvhash=4095
Nov 18 22:36:45 localhost kernel[0]: PAE enabled
Nov 18 22:36:45 localhost kernel[0]: 64 bit mode enabled
Nov 18 22:36:45 localhost kernel[0]: rtclock_init: Taking bus ratio path 4 (Intel / Apple)
Nov 18 22:36:45 localhost kernel[0]: TSC: Verification of clock speed PASSED.
Nov 18 22:36:45 localhost kernel[0]: TSC: Frequency =   3001.21500MHz, FSB frequency =  200.68100MHz, bus ratio = 15
Nov 18 22:36:45 localhost kernel[0]: Darwin Kernel Version 10.5.0: Thu Nov 18 21:13:50 WET 2010; annappirtrvh v4 :xnu-1504.9.17/BUILD/obj/RELEASE_I386...

Nov 18 14:43:52 localhost kernel[0]: npvhash=4095
Nov 18 14:43:52 localhost kernel[0]: rtclock_init: Taking bus ratio path 4 (Intel / Apple)
Nov 18 14:43:52 localhost kernel[0]: TSC: Verification of clock speed not available in x86_64.
Nov 18 14:43:52 localhost kernel[0]: TSC: Frequency =   3001.9995MHz, FSB frequency =  200.67333MHz, bus ratio = 15
Nov 18 14:43:52 localhost kernel[0]: Darwin Kernel Version 10.5.0: do 18 nov 2010 12:39:02 CET; annappirtrvh v4 :xnu-1504.9.17-legacy/BUILD/obj/RELEASE_X86_64...

this is, keeping in mind that i'm not the best test subject around, since i usually use only that minimal stuff i posted on 10.6.4 topic.

About the annoyances:

- i think it's time to remove the -force64 argument and return the normal behavior to the kernel!? It was never needed... arch and -legacy arguments do the job. What do you think? The question is not necessarily just for Andy

- i'm getting my old friend "NOT_IMPLEMENTED bora/vmx/main/vmmonPosix.c:312" when starting a vm and VMWare installer saying i need an Intel cpu, "only" with the legacy kernel; i remember this from long time ago, but can't remember the reason and google is not helping much.. any thoughts?

[xdoom7]

- i think it's time to remove the -force64 argument and return the normal behavior to the kernel!? It was never needed... arch and -legacy arguments do the job. What do you think? The question is not necessarily just for Andy

 

 

Hi,

 

Removing the -force64 argument is not a good idea. I 'am only able to run apps in 64bits mode on a Pentium4-641 with EMT64 support when i use mach_kernel 10.5.0 so all works well and stable and no panics at all.

 

argument arch=x86_64 leaves me behind with kernel panics in relation to ACPI.

When i boot without -force64 my apps are running in 32bits mode and notice a extremely slowdown in performance.

I use bootloader chameleon RC5 trunk 619.

 

 

cu

[yehia2amer]

thanks everyone qoopz, nawcom, AnV, BlackKnight, mucha

 

*the kernel works great with arch=i386

 

*but when i use arch=i386 -force64 everything works well

except Quicktime it always crashes when using "H.264" encoded videos

even when watching a "H.264" encoded video using safari

 

Process: quicklookd [251]

Path: /System/Library/Frameworks/QuickLook.framework/Resources/quicklookd.app/Contents/MacOS/quicklookd

Identifier: com.apple.QuickLookDaemon

Version: 2.3 (327.6)

Build Info: QuickLook-3270600~2

Code Type: X86-64 (Native)

Parent Process: launchd [114]

 

Date/Time: 2010-11-20 01:49:13.267 +0200

OS Version: Mac OS X 10.6.5 (10H574)

Report Version: 6

 

Exception Type: EXC_BAD_INSTRUCTION (SIGILL)

Exception Codes: 0x0000000000000001, 0x0000000000000000

Crashed Thread: 13 com.apple.coremedia.videomediaconverter

the error QuickTime_Error.rtf

hope this is fixed as soon as possible

[Mohamed Khairy]

the first kernel dont tell you that this cpu not intel and vmware work on it

http://www.kexts.com/view/475-qoopz_anv_xn...+dydld_fix.html

but all next kernel vmware didnt setup

i use anval bootloader latest version for who asking

[Andy Vandijck]

thanks everyone qoopz, nawcom, AnV, BlackKnight, mucha

 

*the kernel works great with arch=i386

 

*but when i use arch=i386 -force64 everything works well

except Quicktime it always crashes when using "H.264" encoded videos

even when watching a "H.264" encoded video using safari

 

 

the error QuickTime_Error.rtf

hope this is fixed as soon as possible

Try running QuickTime X in 32bit by getting info on it and checking "run in 32bit"

 

32bit and 64bit both work for me on my AMD x2 5600+ when I used the bootflags "arch=x86_64 -notscverify -force64"(for pure 64bit) but for some reason I can't load 32bit apps, with or without the patched dyld. With -force64 everything loads fine(even 32bit apps!), but Im not sure if thats because of the patched dyld or not.

Did you try patching libSystem.B.dylib with the amd_insn_patcher I listed on first post.

 

From within Terminal you can accomplish this with

amd_insn_patcher /usr/lib/libSystem.B.dylib /usr/lib/libSystem.B.dylib_patched

sudo mv /usr/lib/libSystem.B.dylib_patched /usr/lib/libSystem.B.dylib

sudo update_dyld_shared_cache

 

This should fix the little issue.

Let me know if it worked.

[scififan68]

Hey, Andy

I've did what you told me to do and 32bit apps still crash in true 64bit mode, but they work when I use -force64.

Thanks for this kernel, but i had to revert to an older kernel, for stability reasons, I guess I try this kernel when I get my amd x3!

32bitappcrashlog.txt

[nawcom]

Hey AnV!

 

Great job with this! Without you and Azimutz this probably wouldn't be where it is today

 

A few things I noticed that was missing was 1) Due to chameleon not detecting some AMD Shanghai fsb (like my own) there's a fix to set it to 200mhz by default if it ends up being 0 at boot, in tsc.c. Another small thing was just updating the name of the kernel (so it's v5).

 

The fsb thing is something that could be fixed in the bootloader, but it hasn't yet.

 

I did my usual installer package for it. This does the same thing, but instead of patching the installer files, it runs (if it detects you are using AMD) AnV's patcher against libSystem.B.dylib and updates the dyld cache. Much easier. The -force64 is optional, but I suggest AMD users to use that. It also sets arch=i386, which you can remove yourself or change to x86_64 if you want. Do you think I should make that a customizable option too?

 

http://nawcom.com/osx86/files/10.6/Kernels...-10.5.0.pkg.zip

 

Thank you again AnV and Azimutz One of these days we need to organize this more. I mentioned using the voodooprojects svn for this to zef on IRC but I don't think he's read it yet.

 

Edit: Did some tests - verified that use of Quicktime H264 crashes in 64 bit, but that's not surprising at all. I have yet to test on an older Athlon64. My 4 core Athlon II works great.