Legacy kernel 10.4.0 updated

@$The-King$thanks this work my quicktime but it crashes with mp4 and safari when open vedio on it with quick time thanks andy for all your work

try running them in 32 bit.
it is ssse3 related

Try the latest kernel on, lots of updates and it works now like a charm

@ImkantusDoes SYSENTER patch work via Kernel this time? (going to try later by myself...)

It does now for dyld.
libSystem.B(_debug/_profile).dylib won't get patched as I haven't been able to build a stable custom dyld yet.
There is however now a tool for AMD which can do the hard work for you...

@$The-King$when patching with amd ins patcher it says bus error

With v after the 2 binaries it works but I've made a V2.
This release also strips code signatures from the binaries it patches (even on universal binaries).

@fumoboy007I tried using arch=x86_64 and -force64 together but it just won't boot into 64-bit mode, it always goes into 32-bit mode.

I'll make (compile) a 32+64bit kernel soon

There is another update to the kernel.
This time it can auto patch encrypted binaries (decrypting them to the new dsmos_page_transform, I figured out how it works).
Ignore the failures at beginning boot, they are because it waits for "DSMOS has arrived".
It will continue to load the binaries untill they are succesfully loaded
All that is left now is getting a stable custom dyld built (for library + framework auto patching) and then we will have everything where we need it
I could however use some help on this because the issue (I think) is that the coresymbolication functions aren't available.

@eMatoSAnother thing I've noticed is that "About this Mac" says Unknown CPU since V3 of your kernel, though I'm not sure if it's your kernel or Chameleon as I've been testing their latest RC5 release.

It's probably Chameleon, try my branch as it has a CPU auto-detect fix.

@$The-King$who use updated legacy kernel is vmware fusion allowed to be setuped or say non intel cpu anv kernel rev4 vmware work perfect but with legacy not work

Try setting the patcher to forcing for every app it encounters with:
patcher_opts=50

=FORCE+CPUID+SYSENTER
=2+16+32

@$The-King$dont know what is problem with x86-64 build

Yeah, neither do I.
I suspect they removed some code and that is the reason that it doesn't work.

@$The-King$with out patching any thing by tools on 32bit nearly kernel works good just few very few problems you can say fly patching work on 64bit all media programs crashes fly patching not works good if you fixed 64bit fly patching may arch x86-64 works

AFAIK on the fly patching for x86_64 works just fine but the media programs (QuickTime in 64bit) crash because there are no Supplemental SSE3 instructions available.
The only solution is running it in 32bit mode (Get Info, check "run in 32bit")

New version of the AMD instruction patcher.
This version fixes issue of no output file generation on universal binaries when i386 part needed patching but x86_64 part didn't

@kabuuI gave boot With Verbose mode, appears these errors This is normal ? I used Legacy Kernel v4 and instruction patcher booting with "arch=i386 -force64" Thank you Andy for his Hard work Sorry for my English

Yes, look more closely, it gives these from "Waiting for DSMOS"
untill "DSMOS has arrived" message, it's because it waits for the decryptor

Again an update.
This time I fixed CoreSymbolication support and fixing that issue also fixed backtracing issues.
Debugging is thus available
Normally no more CS errors thus
I decided to abandon 64 bit kernel for now (untill I can figure out what's wrong with it)

@RayFlowerThanks for another update, now the backtrace works so it gives a very verbose crash report, for the sake of not flooding this post I pastebin'd it: Steam paste bin.com/dQRYMwtd And this is the crash report i get when i try to use/validate my precious IK multimedia plugins with logic: paste bin.com/7dBdF2hb Again thanks for the update:)

In case of the plugins it seems something to have to do with some functions of the dyld.
In case of steam it is the uninstalling of the exception handler that goes wrong (thread 7)

1. Thread 7 Crashed:
2. 0 crashhandler.dylib 0x1b4c6299 google_breakpad::ExceptionHandler::UninstallHandler(bool) + 133
3. 1 crashhandler.dylib 0x1b4c702f google_breakpad::ExceptionHandler::WaitForMessage(void*) + 381
4. 2 libSystem.B.dylib 0x91c4981d _pthread_start + 345
5. 3 libSystem.B.dylib 0x91c496a2 thread_start + 3

Testing it now, I had to boot with arch=i386 and patcher_opts=2 like before otherwise kp or instant reboot. Seems to work fine for now, I've seen a new message in the console, I guess it's related to the kernel or sysenter patch but I don't know for real.

com.stclairsoft.DefaultFolderX.helper	sysctlbyname_with_pid: sysctl  failed:Invalid argument
com.stclairsoft.DefaultFolderX.helper	proc_native: sysctlbyname_with_pid  failed:Invalid argument

Overall the system feels snappier (advanced tech term hehe) but perhaps it's a placebo effect.
Thank you again Andy for your work

thanks this work my quicktime but it crashes with mp4 and safari when open vedio on it with quick time
thanks andy for all your work

Gracias amigo, no me iba a dar la paja de parchar xDDD

Like for eMatoS:

• without arch=i386 and patcher_opts=2: reboot
• with arch=i386 but without patcher_opts: kernel panic (see attachment but it's similar to those I've reported before)
• with both it boots and somewhat works but still not really usable.

Unlike eMatoS I still have the same problems I wrote about here:
osx 86.net/f36/qoopz-anv-xnu-10-4-0-rel4-t6491/post50208.html
(graphics problems, and missing dates and times) now with a 10.6.3 install on an AMD Athlon64 3200+

@eMatoSsysenter patch but I don't know for real.

Does SYSENTER patch work via Kernel this time? (going to try later by myself...)

Thanks for yet another kernel andy!

I still have the problems i had before with steam and abobe cs3 pse and cs5 and some au plugins though.

Just out of curiosity, does this make any sense to you?:

/Users/my_user/Library/Application\ Support/Steam/SteamApps/[email protected]/half-life\ 2/hl2_osx ; exit;
dyld: Library not loaded: @rpath/libtier0.dylib
  Referenced from: /Users/my_user/Library/Application Support/Steam/SteamApps/[email protected]/half-life 2/hl2_osx
  Reason: image not found
Trace/BPT trap
logout

thanks andy for yours hard work

after tests with new clean install
i must use sysenter patcher if not many programs crashes
i put amd instruction patcher on usr/bin but i can't see any benefit for it
no more patcher_opts=2

on 32bit mode every things work good except sound volume dont change and and quicktime crashes when use subtitles

on 64bit mode sound volume change work but qiucktime totally not work

thanks andy keep your good working

@$The-King$i put amd instruction patcher on usr/bin but i can't see any benefit for it

The patcher is made to patch out bad instructions from single binary files - not made for patching complete folders...

For example:

sudo -s
amd_insn_patcher /usr/lib/libSystem.B.dylib /usr/lib/libSystem.B.dylib.patched
cp /usr/lib/libSystem.B.dylib.patched /usr/lib/libSystem.B.dylib

Patcher is working great and Kernel is able to boot without patcher_opts=2 now, thanks Andy. I am going to do further testing once I am back from work this evening. :

@ImkantusThe patcher is made to patch out bad instructions from single binary files - not made for patching complete folders... For example: sudo -s amd_insn_patcher /usr/lib/libSystem.B.dylib /usr/lib/libSystem.B.dylib.patched cp /usr/lib/libSystem.B.dylib.patched /usr/lib/libSystem.B.dylib Patcher is working great and Kernel is able to boot…

which files is needed to be patched with this tool
and is there need for sysenter patcher ?

Hey Andy! Thanks for your work!

Installed your updated kernel and VmWare Fusion stopped working. With the 10.4.0 rel 4 kernel everything good.

Sep 18 15:34:37.735: vmx| Log for VMware Fusion pid=287 version=3.1.1 build=build-282344 option=Release
Sep 18 15:34:37.735: vmx| The process is 64-bit.
Sep 18 15:34:37.735: vmx| Host codepage=UTF-8 encoding=UTF-8
Sep 18 15:34:37.735: vmx| Hostname=diskeeper-Mac-Pro.local
Sep 18 15:34:37.735: vmx| IP=::1 (lo0)
Sep 18 15:34:37.735: vmx| IP=fe80::1 (lo0)
Sep 18 15:34:37.735: vmx| IP=127.0.0.1 (lo0)
Sep 18 15:34:37.735: vmx| IP=fe80::21e:8cff:fec9:3a4d (en0)
Sep 18 15:34:37.735: vmx| IP=192.168.2.101 (en0)
Sep 18 15:34:37.735: vmx| IP=192.168.211.1 (vmnet1)
Sep 18 15:34:37.735: vmx| IP=192.168.82.1 (vmnet8)
Sep 18 15:34:37.735: vmx| Command line: "/Library/Application Support/VMware Fusion/vmware-vmx" "-E" "en" "-D" "w+gVbXFDnoYDPQAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=" "-s" "vmx.stdio.keep=TRUE" "-#" "product=1;name=VMware Fusion;version=3.1.1;buildnumber=282344;licensename=VMware Fusion for Mac OS;licenseversion=3.0 build-282344;" "-@" "pipe=/var/folders/Bb/Bb5kr8hCFQq0qHcq9UoweU+++TI/-Tmp-//vmware-diskeeper/vmx23433769ca3d0533;readyEvent=31" "/Volumes/OSX/XP.vmwarevm/XP.vmx"
Sep 18 15:34:37.735: vmx| Msg_SetLocale: HostLocale=UTF-8 UserLocale=en
Sep 18 15:34:37.735: vmx| Msg_Reset:
Sep 18 15:34:37.735: vmx| [msg.dictionary.load.openFailed] Cannot open file "/Library/Application Support/VMware Fusion/messages/en/vmware.vmsg": No such file or directory.
Sep 18 15:34:37.735: vmx| ----------------------------------------
Sep 18 15:34:37.755: vmx| Ready event: 31
Sep 18 15:34:37.785: vmx| UI Connecting to pipe '/var/folders/Bb/Bb5kr8hCFQq0qHcq9UoweU+++TI/-Tmp-//vmware-diskeeper/vmx23433769ca3d0533' with user '(null)'
Sep 18 15:34:37.785: vmx| VMXVmdb: Local connection timeout: 60000 ms.
Sep 18 15:34:37.786: vmx| UUID: Unable to open /dev/mem: No such file or directory
Sep 18 15:34:37.787: vmx| /Volumes/OSX/XP.vmwarevm/XP.vmx: Setup symlink /var/run/vmware/e155f65b6d40c0055927d152657b9538 -> /var/run/vmware/diskeeper_501/1284816877755659_287
Sep 18 15:34:37.787: vmx| Vix: [140735088876576 mainDispatch.c:374]: VMAutomation: Initializing VMAutomation.
Sep 18 15:34:37.788: vmx| Vix: [140735088876576 mainDispatch.c:397]: VMAutomation: Detected the VM is not managed
Sep 18 15:34:37.788: vmx| Vix: [140735088876576 mainDispatch.c:658]: VMAutomationOpenListenerSocket() listening
Sep 18 15:34:37.788: vmx| Sig_Init already initialized 
Sep 18 15:34:37.790: vmx| Vix: [140735088876576 mainDispatch.c:3661]: VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1870, success=1
Sep 18 15:34:37.790: vmx| Transitioned vmx/execState/val to poweredOff
Sep 18 15:34:37.790: vmx| Vix: [140735088876576 mainDispatch.c:3661]: VMAutomation_ReportPowerOpFinished: statevar=1, newAppState=1873, success=1
Sep 18 15:34:37.790: vmx| Vix: [140735088876576 mainDispatch.c:3661]: VMAutomation_ReportPowerOpFinished: statevar=2, newAppState=1877, success=1
Sep 18 15:34:37.790: vmx| Vix: [140735088876576 mainDispatch.c:3661]: VMAutomation_ReportPowerOpFinished: statevar=3, newAppState=1881, success=1
Sep 18 15:34:37.790: vmx| Panic: dropping lock (was bug 49968)
Sep 18 15:34:37.790: vmx| NOT_IMPLEMENTED bora/vmx/main/vmmonPosix.c:312
Sep 18 15:34:37.791: vmx| Core dump limit is 0 KB.
Sep 18 15:34:37.920: vmx| Child process 288 failed to dump core (status 0x6).
Sep 18 15:34:37.921: vmx| Backtrace:
Sep 18 15:34:37.923: vmx| Backtrace[0] 00007fff5fbfef60 rip=00000001003fdb05 rbx=0000000000000000 rbp=00007fff5fbfef90 r12=00000001003fd560 r13=00007fff5fbfef6c r14=00007fff5fbff500 r15=00007fff5fbff6e0
Sep 18 15:34:37.923: vmx| Backtrace[1] 00007fff5fbfefa0 rip=0000000100019df0 rbx=0000000000000000 rbp=00007fff5fbff480 r12=00007fff5fbfefa0 r13=00007fff5fbff4c0 r14=00007fff5fbff500 r15=00007fff5fbff6e0
Sep 18 15:34:37.923: vmx| Backtrace[2] 00007fff5fbff490 rip=000000010003e011 rbx=0000000000000001 rbp=00007fff5fbff490 r12=00007fff5fbff4a0 r13=00007fff5fbff4c0 r14=00007fff5fbff500 r15=00007fff5fbff6e0
Sep 18 15:34:37.923: vmx| Backtrace[3] 00007fff5fbff4a0 rip=000000010003e969 rbx=0000000000000001 rbp=00007fff5fbff4f0 r12=00007fff5fbff4a0 r13=00007fff5fbff4c0 r14=00007fff5fbff500 r15=00007fff5fbff6e0
Sep 18 15:34:37.923: vmx| Backtrace[4] 00007fff5fbff500 rip=000000010003f0ee rbx=00007fff5fbff500 rbp=00007fff5fbff680 r12=000000000000000a r13=0000000000000004 r14=0000000000000000 r15=00007fff5fbff6e0
Sep 18 15:34:37.923: vmx| Backtrace[5] 00007fff5fbff690 rip=00000001000039bb rbx=00000001006931d0 rbp=00007fff5fbff6b0 r12=00000001006931c0 r13=0000000100693020 r14=00007fff5fbff6e0 r15=00007fff5fbff6e0
Sep 18 15:34:37.923: vmx| Backtrace[6] 00007fff5fbff6c0 rip=0000000100019b39 rbx=0000000113801000 rbp=00007fff5fbff6c0 r12=0000000000000001 r13=0000000000000003 r14=00007fff5fbff6e0 r15=00007fff5fbff6e0
Sep 18 15:34:37.923: vmx| Backtrace[7] 00007fff5fbff6d0 rip=0000000100003079 rbx=0000000113801000 rbp=00007fff5fbff750 r12=0000000000000001 r13=0000000000000003 r14=00007fff5fbff6e0 r15=00007fff5fbff6e0
Sep 18 15:34:37.923: vmx| Backtrace[8] 00007fff5fbff760 rip=0000000100003857 rbx=0000000000000003 rbp=00007fff5fbff890 r12=0000000000000003 r13=00007fff5fbff770 r14=000000000000000c r15=0000000000000000
Sep 18 15:34:37.924: vmx| SymBacktrace[0] 00007fff5fbfef60 rip=00000001003fdb05 in function (null) in object /Library/Application Support/VMware Fusion/vmware-vmx loaded at 0000000100000000
Sep 18 15:34:37.924: vmx| SymBacktrace[1] 00007fff5fbfefa0 rip=0000000100019df0 in function (null) in object /Library/Application Support/VMware Fusion/vmware-vmx loaded at 0000000100000000
Sep 18 15:34:37.924: vmx| SymBacktrace[2] 00007fff5fbff490 rip=000000010003e011 in function (null) in object /Library/Application Support/VMware Fusion/vmware-vmx loaded at 0000000100000000
Sep 18 15:34:37.924: vmx| SymBacktrace[3] 00007fff5fbff4a0 rip=000000010003e969 in function (null) in object /Library/Application Support/VMware Fusion/vmware-vmx loaded at 0000000100000000
Sep 18 15:34:37.924: vmx| SymBacktrace[4] 00007fff5fbff500 rip=000000010003f0ee in function (null) in object /Library/Application Support/VMware Fusion/vmware-vmx loaded at 0000000100000000
Sep 18 15:34:37.924: vmx| SymBacktrace[5] 00007fff5fbff690 rip=00000001000039bb in function (null) in object /Library/Application Support/VMware Fusion/vmware-vmx loaded at 0000000100000000
Sep 18 15:34:37.924: vmx| SymBacktrace[6] 00007fff5fbff6c0 rip=0000000100019b39 in function (null) in object /Library/Application Support/VMware Fusion/vmware-vmx loaded at 0000000100000000
Sep 18 15:34:37.924: vmx| SymBacktrace[7] 00007fff5fbff6d0 rip=0000000100003079 in function (null) in object /Library/Application Support/VMware Fusion/vmware-vmx loaded at 0000000100000000
Sep 18 15:34:37.924: vmx| SymBacktrace[8] 00007fff5fbff760 rip=0000000100003857 in function (null) in object /Library/Application Support/VMware Fusion/vmware-vmx loaded at 0000000100000000
Sep 18 15:34:37.925: vmx| Msg_Post: Error
Sep 18 15:34:37.925: vmx| [msg.log.error.unrecoverable] VMware Fusion unrecoverable error: (vmx)
Sep 18 15:34:37.925: vmx| NOT_IMPLEMENTED bora/vmx/main/vmmonPosix.c:312
Sep 18 15:34:37.925: vmx| [msg.panic.haveLog] A log file is available in "/var/folders/Bb/Bb5kr8hCFQq0qHcq9UoweU+++TI/-Tmp-//vmware-diskeeper/vmware-diskeeper-287.log".  [msg.panic.requestSupport.withLog] Please request support and include the contents of the log file.  [msg.panic.requestSupport.vmSupport.apple.menu] 
Sep 18 15:34:37.925: vmx| To collect data to submit to VMware support, choose "Collect Support Information" from the Help menu.
Sep 18 15:34:37.925: vmx| You can also run "/Library/Application Support/VMware Fusion/vm-support.tool" directly.
Sep 18 15:34:37.925: vmx| [msg.panic.response] We will respond on the basis of your support entitlement.
Sep 18 15:34:37.925: vmx| ----------------------------------------

Wow it does feel snappier compare to legacy 10.4.0 kernel.
Vmware not working for me too parallel is.
Great work ! thanks

@$The-King$which files is needed to be patched with this tool and is there need for sysenter patcher ?

Well the tool patches out sysenter traps as well as it is able to patch cpuid checks into interrupt 0xfb, like we already have been doing using good old maxxus patcher.
I would recommend you to use the kernel in order with -force64 bootflag, as the 64-Bit code of OS X doesn't contain any cpuid trouble, what is making our lifes much easier and working great thanks to Andys hard work. :

On my testing installation I have actually patched only these files and no issues (mp4 Playback and DivX De- & Encoder Plugins in QTX, iTunes etc all working just great):

/usr/lib/libSystem.B.dylib

/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore

/System/Library/QuickTime/QuickTimeComponents.component/Contents/MacOS/QuickTimeComponents

/System/Library/QuickTime/AppleProResDecoder.component/Contents/MacOS/AppleProResDecoder

If Developer Tools are installed libSystem.B_debug.dylib & libSystem.B_profile.dylib need to be patched as well.
The two Quiktime folder ones might not be required, but I patched them as I am still having QT7 in use - I haven't tried without patching those, yet. (going to try that later)
[EDIT]OK. Those two files have to be patched furthermore QTX needs to be executed in 32-Bit mode for mp4 playback to work - I haven't seen that the coresponding checkbox was still set true.

@andyvandIt does now for dyld. libSystem.B(_debug/_profile).dylib won't get patched as I haven't been able to build a stable custom dyld yet. There is however now a tool for AMD which can do the hard work for you...

Anyway this is the best Snow Leopard XNU release for the AMD folks out there by now.
You have done a realy great job to the point and I hope you'll keep it going.

when patching with amd ins patcher
it says bus error

@$The-King$when patching with amd ins patcher it says bus error

Same here:S

Can't boot into 64-bit mode

I tried using arch=x86_64 and -force64 together but it just won't boot into 64-bit mode, it always goes into 32-bit mode.

Andy, why is it that with the latest kernel I can't get chameleon to take the arch=x86_64 command? If I boot with Wait=Yes arch=x86_64 -force64 when Chameleon stops before the kernel loads it always says Loading i386 System or something similar, not X86_64. Maybe it's just cosmetic? Don't know. Perhaps you forced the loader to boot with the i386 command...

@Fumoboy007, don't pay attention to what System Profiler (and many other apps) says, you should check in activity monitor for 64bit apps.

Anyway, great work again Andy, the system's been very stable, it works better than in 32bit though I have to force some apps to run in 32bit but that's no big deal. Thank you...

@eMatoS@Fumoboy007, don't pay attention to what System Profiler (and many other apps) says, you should check in activity monitor for 64bit apps.

But it seems to be loading 32-bit kexts though…so…iunno. In the kernel logs it says "64 bit mode enabled" but it also says "Darwin Kernel Version 10.4.0: vr 17 sep 2010 14:40:38 CEST; annappirtrvh v4 :xnu-1504.7.4-legacy/BUILD/obj/RELEASE_I386"…i386?

I'm using the binary that andy uploaded…maybe it wasn't compiled for 64-bit? hehe..just a thought.

@fumoboy007maybe it wasn't compiled for 64-bit?

WOAH…im actually right…i just did a "lipo -info" on that file and it's only i386!

@fumoboy007WOAH…im actually right…i just did a "lipo -info" on that file and it's only i386!

…and since I don't know how to apply a patch…could someone upload the hybrid version of the kernel please =).

thanks andy
hope next one will be more featured and x86-64 compile work because i love to work with x86-64 kernel

@fumoboy007WOAH…im actually right…i just did a "lipo -info" on that file and it's only i386!

You should read more precisely, no one here has ever said that the released binaries would be universal. Andy only wrote:

It now builds for both 32/64bit easily.

And as I tried myself, I can confirm that it does. Just that the Kernel in BUILD/obj/RELEASE_X86_64 doesn't work nor it's possible to merge both builds into one universal bin file.

But as eMatoS wrote using 32-Bit Kernel does not mean that 64-Bit support doesn't work. Good explanation is avaible at macw orld.com/article/142379/2009/08/snow_leopard_64_bit.html

What would be the advantage you promise yourself from running 64-Bit Kernel? Even real Macs don't use this by default...

PS: You might want to use next time...

@Andy
Do you have any idea how I could fix IPC for Quiktime to load 32-Bit Codecs & Safari to work with Flash Player?

Imkantus, what is the problem with Flash Player and Safari? Have you tried the beta build? It runs in 64bit now. You can download it from the Adobe Labs.

Thx, just installing latest flash player plugin (no preview release) did the trick for Safari... sometimes solutions are even closer as expected.

@ImkantusWhat would be the advantage you promise yourself from running 64-Bit Kernel? Even real Macs don't use this by default...

iunno…are my EXC_I386_DIV crashes related?

the quick time crashes with latest kernel and patcher
hope it is solved in new kernel and arch x86-64 work also
thanks andy for your time spending it on programing this kernel

anther problem with this kernel is that vmware and parallel software cant be setuped it says it isnt intel cpu
but with anv 10.4 rel4 works fine with this software
thanks andy

after first test
x86-64
not work dont know what is problem with x86-64 bulid

force64 causes instant restart

Great work so far, Andy! There is one more issue which you should add to your list and that is 64-bit. When I use the kernel flag -force64, it just causes my computer to restart.

new kernel work for me and with -force64 now, can some one tell me how to apply those patches? thanks

The kernel patches?
You wont need them unless you plan to modify the source yourself, i haven't done it in osx for ages but check out this if you're interested.

shantonu.blog spot.com/2009/09/mac-os-x-kernel-source-xnu-has-been.html

And please read this:
linux.die .net/man/1/patch

There is no sense in going trough this unless you know what you're doing and actually commit some changes.