Legacy kernel 10.7.0 with custom dyld (now also with atom patch)

[andyvand]

I updated the sources so that dyld builds with Xcode 4.
This fixed the issue of Finder / SystemUIServer crashing with the custom dyld.
/System/Library/CoreServices/pbs still needs to be packed with upx though.
Also some apps that use Auto::zone::zone (for some ObjC apps) still need packing with upx.
The dyld became faster and more stable with the latest patches though.
On the fly patching works fine (tested it) on any app I've tested it on.
I've also added a new patched kernel with cpu model 15 patch (Atom / new Celeron specific, separate kernel).

Download including sources:
http://rapidshare.com/files/457022173/voodoobuild-AnV-0.4.1.zip

Download Atom / new Celeron kernel:
http://rapidshare.com/files/457021711/legacy_kernel_atom.zip

[wastez]

Thatīs fine! Thank you for you hard work!
I will try it today and iīm very agog in the function of the new dyld!!!
Did you use the libunwind from apple or isnīt it available?

Will report immediately after i tried it!

[andyvand]

Thatīs fine! Thank you for you hard work!
I will try it today and iīm very agog in the function of the new dyld!!!
Did you use the libunwind from apple or isnīt it available?

Will report immediately after i tried it!
The libunwind from Apple is unfortunetely privately distributed so the only option is changing the exception code to use -lgcc_eh.
This is also why some apps need to be packed with UPX (like pbs).

[wastez]

Tried it and it worked without problems.;)
There are no problems with the dyld this time.:D
pbs have only to be patched in 32 bit mode, or?

Thank you for your great and hard work.
This kernel is really amazing.:cool:

[wastez]

The only software which doesnīt work is garageband and 32 bit mode of cinebench but all other software works without problems.

[RobertX]

hey andy...i'll give it a go too;) ..the first link for intel p4 right?

[RobertX]

seems ok...still sse3 emu probs tho

[andyvand]

Tried it and it worked without problems.;)
There are no problems with the dyld this time.:D
pbs have only to be patched in 32 bit mode, or?

Thank you for your great and hard work.
This kernel is really amazing.:cool:
Great, bug 1/2 squashed... ;)

[akimoa]

For some reason me and custom dyld willl never get friends to much programms are not responding and i wont upx them all so no use for me

[odin1937]

I updated the sources so that dyld builds with Xcode 4.
This fixed the issue of Finder / SystemUIServer crashing with the custom dyld.
/System/Library/CoreServices/pbs still needs to be packed with upx though.
Also some apps that use Auto::zone::zone (for some ObjC apps) still need packing with upx.
The dyld became faster and more stable with the latest patches though.
On the fly patching works fine (tested it) on any app I've tested it on.

thanks for the share. I assume that this kernel runs also on amd machines? I am asking cause I am running snow 10.6.7 on amd opteron 185 X2 and nforce4 chipset. :D

Also , any info , how we can pack pbs wih upx , patch it for 32bit mode?:-d

[akimoa]

Get the UPX file from Andys other thread and put him where he belongs after open Terminal and put this

upx --force /System/Library/CoreServices/pbs

And yes kernel works for AMD

[odin1937]

Get the UPX file from Andys other thread and put him where he belongs after open Terminal and put this

upx --force /System/Library/CoreServices/pbsAnd yes kernel works for AMD

I believe you mean this thread: http://osx86.co/f36/10-6-6-legacy-kernel-for-intel-amd-t6892/.

thank you for the upx command! :D

[wastez]

For some reason me and custom dyld willl never get friends to much programms are not responding and i wont upx them all so no use for me

Last time (10.6.6) i had the same problem but this time almost all works without upx.

[odin1937]

Last time (10.6.6) i had the same problem but this time almost all works without upx.

bro , I see from your signature that you use AnVAL Bootloader 5.1.4. Since you have AMD Athlon 64 X2 , do you find anval better for amd than chameleon latest releases? My cpu is amd opteron 185.

[wastez]

bro , I see from your signature that you use AnVAL Bootloader 5.1.4. Since you have AMD Athlon 64 X2 , do you find anval better for amd than chameleon latest releases? My cpu is amd opteron 185.

In the moment i would use anval for amd. I tried almost every bootloader and this one works at best.
Just try it and you will have no regrets about.

[odin1937]

In the moment i would use anval for amd. I tried almost every bootloader and this one works at best.
Just try it and you will have no regrets about.

thanks for the tip! ;)

[andyvand]

thanks for the share. I assume that this kernel runs also on amd machines? I am asking cause I am running snow 10.6.7 on amd opteron 185 X2 and nforce4 chipset. :D

Also , any info , how we can pack pbs wih upx , patch it for 32bit mode?:-d
No, use my custom upx and pack it (or any other upx).
E.G. upx -9 /System/Library/CoreServices/pbs

[odin1937]

No, use my custom upx and pack it (or any other upx).
E.G. upx -9 /System/Library/CoreServices/pbs

ok thanks , I have decrypted and patched binaries with marvin's amd utility and some amd_insn_patcher , so things should be smooth with upx.

thanks mate!

[odin1937]

I installed the kernel , packed pbs with upx , but during boot I have the : patch_text_segment failed.

When I got online , I saw that nothing from the important stuff was crashing such as finder , disk uitlity , rest utilities , system preferences e.t.c , only safari , seamonkey and radium.

I managed to fix safari with upx , but not seamonkey and radium. Seamonkey had encrypted binaries which have been fixed with marvin's utility.

So i am booting with std_dyld=Yes with no problems.

[wastez]

I installed the kernel , packed pbs with upx , but during boot I have the : patch_text_segment failed.

When I got online , I saw that nothing from the important stuff was crashing such as finder , disk uitlity , rest utilities , system preferences e.t.c , only safari , seamonkey and radium.

I managed to fix safari with upx , but not seamonkey and radium. Seamonkey had encrypted binaries which have been fixed with marvin's utility.

So i am booting with std_dyld=Yes with no problems.

Thatīs clear because if you use std_kernel=Yes you donīt use the custom dyld which is implemented into the kernel. ;) If you use this kernel flag the kernel differs not to the nawcom kernel.

[odin1937]

Thatīs clear because if you use std_kernel=Yes you donīt use the custom dyld which is implemented into the kernel. ;) If you use this kernel flag the kernel differs not to the nawcom kernel.

yes I know bro , but I didn't have other choice at the moment. About Anval's bootloader I was asking , it doesn't support Amd - Aware , which is my case , just for people to know.

Cheers! :D

[wastez]

yes I know bro , but I didn't have other choice at the moment. About Anval's bootloader I was asking , it doesn't support Amd - Aware , which is my case , just for people to know.

Cheers! :D

Would be interessting to know what for a bootloader does support this?

[maya77]

Short install instructions, please?

I know that kernel must be copied to system root, but what about additional patching you are talking about? What to patch, and how, if that's important part?

[odin1937]

Short install instructions, please?

I know that kernel must be copied to system root, but what about additional patching you are talking about? What to patch, and how, if that's important part?

nothing else to patch , just compress pbs with upx and any other application that is not working!

[RobertX]

...is the sse3 emulator permanently dead?....old asus board here with P4 2.8...i have the kernel booting now...but borked time and installer and stuff make my mac a real pain....:-|

[LinearBurn]

Would patching the libSystem.B.dylib fix this? Seems liek the file is crupted or the on the fly patching is not working

Process: lssave [4349]
Path: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lssave
Identifier: lssave
Version: ??? (???)
Code Type: X86 (Native)
Parent Process: coreservicesd [51]

Date/Time: 2011-04-14 02:00:53.607 -0500
OS Version: Mac OS X 10.6.7 (10J869)
Report Version: 6

Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Crashed Thread: 0

Dyld Error Message:
Library not loaded: /usr/lib/libSystem.B.dylib
Referenced from: /System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Support/lssave
Reason: no suitable image found. Did find:
/usr/lib/libSystem.B.dylib: truncated fat file. file length=4022272, but needed slice goes to 4581264
/usr/lib/libSystem.B.dylib: truncated fat file. file length=4022272, but needed slice goes to 4581264

[LinearBurn]

Also how do i build the kernel? is there instructions some were

[andyvand]

Also how do i build the kernel? is there instructions some were
With the voodoobuild script but building isn't required.
You can just use the mach_kernel (I assure you, it is built quite well, with latest Xcode tools V4.0)

[andyvand]

Would patching the libSystem.B.dylib fix this? Seems liek the file is crupted or the on the fly patching is not working

Process: lssave [4349]
Path: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lssave
Identifier: lssave
Version: ??? (???)
Code Type: X86 (Native)
Parent Process: coreservicesd [51]

Date/Time: 2011-04-14 02:00:53.607 -0500
OS Version: Mac OS X 10.6.7 (10J869)
Report Version: 6

Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Crashed Thread: 0

Dyld Error Message:
Library not loaded: /usr/lib/libSystem.B.dylib
Referenced from: /System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Support/lssave
Reason: no suitable image found. Did find:
/usr/lib/libSystem.B.dylib: truncated fat file. file length=4022272, but needed slice goes to 4581264
/usr/lib/libSystem.B.dylib: truncated fat file. file length=4022272, but needed slice goes to 4581264
I doubt it, it seems your upgrade didn't go well...
Truncated means it lacks some bytes... :-/

[LinearBurn]

Is there step by step instructions for installing this kernel and instaling the anv bootloader for amd? This may also sound kinda dumb but shouldnt it be posable to hard embed the cpuid in to the kernel so that the kernel would not have to be patched just like the native cpuid detection it does on the Intel cpu's ... so ultimately you would have a native kernel that don’t need special patching like in Linux it has all the info it needs ... i may sound stupid but I’m trying to learn, but all the doc on the net are either written for hard core or to noob or really ancient or won’t help because I’m running amd. I’m not just trying to learn to do it i want to understand why I’m doing it and the process in doing it

[LinearBurn]

I have installed 4 time and it has failed 4 times if its trunkated dont supose some one can sed me a copy of one that is working?


Ps please forgive me im still adjusting to hackintosh and still showing my noobish

[wastez]

Is there step by step instructions for installing this kernel and instaling the anv bootloader for amd? This may also sound kinda dumb but shouldnt it be posable to hard embed the cpuid in to the kernel so that the kernel would not have to be patched just like the native cpuid detection it does on the Intel cpu's ... so ultimately you would have a native kernel that don’t need special patching like in Linux it has all the info it needs ... i may sound stupid but I’m trying to learn, but all the doc on the net are either written for hard core or to noob or really ancient or won’t help because I’m running amd. I’m not just trying to learn to do it i want to understand why I’m doing it and the process in doing it

The dyld is exactly for cpuid autopatching. ;)

Did you boot with std_dyld=Yes? Because if you boot without kernelflags it should use the kernel integrated dyld....

[LinearBurn]

please help me what do i do with the kernel i extracted it and now i have the files do i copy mach_kernel some were? or do somthing in terminal

[maya77]

nothing else to patch , just compress pbs with upx and any other application that is not working!
Great, but what bolded part means?

[LinearBurn]

Ok i figured it out i moved the mach_kernel to the root then patched the file that was giving me trouble now weverthing is working Anv kernel rocks thanks so much

[odin1937]

Great, but what bolded part means?

download andy's upx from here or any other ready to use upx:

http://osx86.co/f36/10-6-6-legacy-kernel-for-intel-amd-t6892/Then put it in your usr/bin/ folder.

Then use the command upx to pack pbs which is located in /System/Library/CoreServices.

The packing - compressing can be done with many commands , such as : upx -9 . which means compress better , or --ultra--brute , or --force e.t.c.

So in the terminal area type : upx -9 "here just drag the pbs binany on terminal" and hit enter.

[RayFlower]

hum, are there any tools that i can use to decrypt these apple binaries?

[odin1937]

hum, are there any tools that i can use to decrypt these apple binaries?

you can use andy's amd_insn_patcher.

for info:

http://osx86.co/f36/amd-insn-patcher-instructions-would-be-nice-t6845/

[RayFlower]

uhm, that doesn't decrypt anything though, besides thats done in the kernel now, I only use that to patch some libs that crashes some apps.

Anyhow, if there is a good and safe way to decrypt binaries i would be a lot more likely to use the custom dyld, anyhow nice work andy.

Would be nice if you could explain to us mortals what this does different that the standard dyld for instance:)

[vikernes]

Am I able to start Snow Leopard 10.6.7 in 64bit kernel mode just by copying/pasting the mach_kernel included in the zip and adding the flag -force64?

[wastez]

It is not the 64 bit kernel mode, it is just 64 bit userland. You should also repair the permissions and youīve to check if the bootloader will load the kernel. For that check your boot.plist.

[vikernes]

Sorry for the dumb questions, but I just started learning about all of this a few days ago. Pretty interesting stuff.

So, if I understood well, by drag/dropping the kernel file I'm going to enable 64bit mode for applications, but the kernel will still be run at 32bit? As in, almost every process reporting as intel 64bit kind (in activity monitor) and kernel_task reporting as Intel (32bit) ?

I already managed this, and that's how my system has been running, and so far so good, everything seems to be working OK.

Is there a way to have the kernel_task also in 64bit ? If so, are there many advantages of also having the kernel in 64bit mode, compared to having only 64bit enabled for applications?

Thank you. :)

[maya77]

download andy's upx from here or any other ready to use upx:

http://osx86.co/f36/10-6-6-legacy-kernel-for-intel-amd-t6892/Then put it in your usr/bin/ folder.

Then use the command upx to pack pbs which is located in /System/Library/CoreServices.

The packing - compressing can be done with many commands , such as : upx -9 . which means compress better , or --ultra--brute , or --force e.t.c.

So in the terminal area type : upx -9 "here just drag the pbs binany on terminal" and hit enter.
Thank you very much for your explanation.

But I have no luck with this kernel anyway.

Using nawcom legacy kernel I'm able to run my hackintosh pretty good. The only problem is I must use following flags:
-force64
arch=i386

Some people said that this combination is strange, and no good, but my system won't boot without it.

With AnV kernel I must use same flags to boot + several programs does not work, including iTunes, Smultron, Little Snitch, etc...

Anyone has idea on how to avoid mentioned kernel flags?

-Asus M4A89GTD PRO/USB3
-AMD Phenom II X6 1090T
-16GB DDR3 1333
-Asus GTX-460
-OSX 10.6.7
-Chameleon build752
-Legacy Kernel 10.7.0

[RayFlower]

There is nothing wrong with using the nawcom kernel, Anv kernel has a custom dyld and it does not work with every application.

Your flags look right but also add "std_dyld=yes", it will work the same way as the nawcom kernel.

Custom dyld is a nice project but for me its not usable since I practically live inside Logic.

Just patch the mentioned libs with the amd patcher, i have to patch some extra things with the "amd-ext" patcher to use some AudioUnits plugins though, if you have some problems you just have to go trough the traceback and try to find the lib that crashes your apps, tedious but worth it.

[maya77]

Thanks.

GringoVermelho@InsanelyMac said (http://www.insanelymac.com/forum/index.php?s=&showtopic=254568&view=findpost&p=1670606):
Using those flags together normally causes a rift in the time-space continuum that will suck in all living tissue. You're lucky to be alive.

"arch=i386 -force64" forces OS X to run in 32-bit kernel and drivers mode but enables OS X to use the EM64T instruction set of the CPU.
It's an odd combination of flags.

arch=i386 is not necessary when using a Voodoo based (aka legacy) kernel because it runs in 32-bit mode by default.

-force64 is never required, it's an override for 64-bit capable AMD CPUs and pre-Core Microarchitecture Intel CPUs that are running a voodoo based kernel. Some systems will not be able to boot when using -force64, some people will not able to run (some or any) 32-bit apps at all; in other words, it's not enabled by default for a reason.

If you aren't using a Voodoo based Kernel, -force64 does nothing.

[andyvand]

Thank you very much for your explanation.

But I have no luck with this kernel anyway.

Using nawcom legacy kernel I'm able to run my hackintosh pretty good. The only problem is I must use following flags:
-force64
arch=i386

Some people said that this combination is strange, and no good, but my system won't boot without it.

With AnV kernel I must use same flags to boot + several programs does not work, including iTunes, Smultron, Little Snitch, etc...

Anyone has idea on how to avoid mentioned kernel flags?

-Asus M4A89GTD PRO/USB3
-AMD Phenom II X6 1090T
-16GB DDR3 1333
-Asus GTX-460
-OSX 10.6.7
-Chameleon build752
-Legacy Kernel 10.7.0
If you want to use my kernel the same way as the nawcom one following boot arguments:
std_dyld=Yes arch=i386 -force64

[wastez]

Using those flags together normally causes a rift in the time-space continuum that will suck in all living tissue. You're lucky to be alive

"arch=i386 -force64" forces OS X to run in 32-bit kernel and drivers mode but enables OS X to use the EM64T instruction set of the CPU.
It's an odd combination of flags.

This user mixed up -force64 and arch=x86_64.
Without it you will start in pure legacy mode and have no chance to run 64 bit software.

[andyvand]

This user mixed up -force64 with arch=x86_64.
Without it you will start in pure legacy mode and have no chance to run 64 bit software.
No, arch=i386 -force64 means 32bit kernel space and 64bit userspace
arch=x86_64 means 64bit kernel space and 64bit userspace (no -force64 should be required)

[wastez]

No, arch=i386 -force64 means 32bit kernel space and 64bit userspace
arch=x86_64 means 64bit kernel space and 64bit userspace (no -force64 should be required)

Thatīs exactly that what i mean.

[maya77]

So I don't need to worry about my boot flags. They are safe to use.

Thanks for your explanation, I appreciate that.

[dragonspeed]

Hi,
Thanks for the hard work here!

I am stucked trying to boot 64bit with this kernel,
Everything goes well until starts bluescreen before "snow leopard space background"
After 2 seconds of bluescreen, everything goes black and the machine reboots.

No, panic, no logs, nothing I could catch.

Has anyone had this problem to give me a clue?
Any special place to look for a log apart form /var/log?
Thanks

[wastez]

Hi,
Thanks for the hard work here!

I am stucked trying to boot 64bit with this kernel,
Everything goes well until starts bluescreen before "snow leopard space background"
After 2 seconds of bluescreen, everything goes black and the machine reboots.

No, panic, no logs, nothing I could catch.

Has anyone had this problem to give me a clue?
Any special place to look for a log apart form /var/log?
Thanks

Do you try to start into 64 bit kernel mode?
Because that will not work with amd! You can only boot into 64 bit userland.
If your amd will start into 64 bit kernel mode, your computer will not be possible to run 32 bit software.

[dragonspeed]

Do you try to start into 64 bit kernel mode?
Because that will not work with amd! You can only boot into 64 bit userland.
If your amd will start into 64 bit kernel mode, your computer will not be possible to run 32 bit software.

Thanks, I am completely confused, I am reading this forum for a long time understanding some people is getting success running 64 bit AMD.

what do you mean with userland. I am trying to boot with arch=X86_64 flag.

At this point my biggest problem is I am trying to run in 32 bit an application that I didn't use since I had 10.6.2 and neither in 10.6.3 nor 10.6.7 works.
It crashes with Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x00000000537465a3.
the application is compressor (from apple)
Mi idea was to try to boot in 64 bit to see if compressor runs.
But with your comments, I suspect my confusion is deeper.

I would appreciate a brief conceptual explanation of what I can do.

Regards!

[chitchit]

Thanks, I am completely confused, I am reading this forum for a long time understanding some people is getting success running 64 bit AMD.

what do you mean with userland. I am trying to boot with arch=X86_64 flag.

At this point my biggest problem is I am trying to run in 32 bit an application that I didn't use since I had 10.6.2 and neither in 10.6.3 nor 10.6.7 works.
It crashes with Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x00000000537465a3.
the application is compressor (from apple)
Mi idea was to try to boot in 64 bit to see if compressor runs.
But with your comments, I suspect my confusion is deeper.

I would appreciate a brief conceptual explanation of what I can do.

Regards!

You should be booting with arch=i386 -force64

Just fyi.

[wastez]

Thanks, I am completely confused, I am reading this forum for a long time understanding some people is getting success running 64 bit AMD.

what do you mean with userland. I am trying to boot with arch=X86_64 flag.

At this point my biggest problem is I am trying to run in 32 bit an application that I didn't use since I had 10.6.2 and neither in 10.6.3 nor 10.6.7 works.
It crashes with Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x00000000537465a3.
the application is compressor (from apple)
Mi idea was to try to boot in 64 bit to see if compressor runs.
But with your comments, I suspect my confusion is deeper.

I would appreciate a brief conceptual explanation of what I can do.

Regards!

Sorry but there is no chance to run 32 bit software in 64 bit kernel mode with amd.
There is a disscusion over the last page where we talked about this.
The only thing is to boot into 32 bit kernel with 64 bit userland which means that your kernel is 32 bit but the apps will run in 64 bit.

[dragonspeed]

Hello,
I have USB problems when I load this kernel,

May 1 18:01:35 localhost kernel[0]: kxld[com.apple.kpi.iokit]: This symbol set has the following unresolved symbols:
May 1 18:01:35 localhost kernel[0]: kxld[com.apple.kpi.iokit]: __ZN14IOPMrootDomain17createPMAssertionEyjP9IOServ icePKc
May 1 18:01:35 localhost kernel[0]: kxld[com.apple.kpi.iokit]: __ZN14IOPMrootDomain18releasePMAssertionEy
May 1 18:01:35 localhost kernel[0]: kxld[com.apple.kpi.iokit]: __ZN14IOPMrootDomain19getPMAssertionLevelEy
May 1 18:01:35 localhost kernel[0]: kxld[com.apple.kpi.iokit]: __ZN14IOPMrootDomain19setPMAssertionLevelEyj
May 1 18:01:35 localhost kernel[0]: kxld[com.apple.kpi.private]: This symbol set has the following unresolved symbols:
May 1 18:01:35 localhost kernel[0]: kxld[com.apple.kpi.private]: _buf_getcpaddr
May 1 18:01:35 localhost kernel[0]: kxld[com.apple.kpi.private]: _buf_setcpaddr
May 1 18:01:35 localhost kernel[0]: kxld[com.apple.kpi.private]: _cp_key_store_action
May 1 18:01:35 localhost kernel[0]: kxld[com.apple.kpi.private]: _cp_register_wraps
May 1 18:01:35 localhost kernel[0]: kxld[com.apple.kpi.private]: _ifnet_clone_attach
May 1 18:01:35 localhost kernel[0]: kxld[com.apple.kpi.private]: _ifnet_clone_detach
May 1 18:01:35 localhost kernel[0]: kxld[com.apple.kpi.private]: _ifnet_idle_flags
May 1 18:01:35 localhost kernel[0]: kxld[com.apple.kpi.private]: _ifnet_set_idle_flags
May 1 18:01:35 localhost kernel[0]: kxld[com.apple.kpi.private]: _mbuf_get_priority
May 1 18:01:35 localhost kernel[0]: kxld[com.apple.kpi.private]: _mbuf_get_traffic_class
May 1 18:01:35 localhost kernel[0]: kxld[com.apple.kpi.private]: _mbuf_set_traffic_class
May 1 18:01:35 localhost kernel[0]: kxld[com.apple.kpi.private]: _vfs_setunmountpreflight


is there any special modification I would need to do?

[mayx]

Hi Andy,I have try this kernel, there is a big problem, i can't run any visualization software, Visual Box, Parallels, VMware... Click on them ,and nothing happen.
I also try nawcom's kernel too, all the visual machines running well,but some application,like Corel Painter,quit unexpectedly every time.but on this kernel,it running well...
Please help,thank you,my cup is AMD 5000+.

[andyvand]

Hi Andy,I have try this kernel, there is a big problem, i can't run any visualization software, Visual Box, Parallels, VMware... Click on them ,and nothing happen.
I also try nawcom's kernel too, all the visual machines running well,but some application,like Corel Painter,quit unexpectedly every time.but on this kernel,it running well...
Please help,thank you,my cup is AMD 5000+.
Do you get any error message or something?
Try putting error reporting in developer mode and get me the results.
The code lying underneath should be the same as nawcom's but try booting with std_dyld=Yes maybe it'll work then.
It may be the custom dyld that prevents launching virtualization...

[mayx]

Do you get any error message or something?
Try putting error reporting in developer mode and get me the results.
The code lying underneath should be the same as nawcom's but try booting with std_dyld=Yes maybe it'll work then.
It may be the custom dyld that prevents launching virtualization...
Thank you for reply,i have try booting with "std_dyld=Yes",it does't work.
I found the error reports in Console.
Here is Parallels Desktop error report. (http://dl.dropbox.com/u/3753352/prl_client_app_2011-05-24-102711_localhost.crash)
Here is Virtual Box error report. (http://dl.dropbox.com/u/3753352/VirtualBox_2011-05-24-110614_localhost.crash)
Here is Kernel log. (http://dl.dropbox.com/u/3753352/kernel.log.txt)

[andyvand]

Thank you for reply,i have try booting with "std_dyld=Yes",it does't work.
I found the error reports in Console.
Here is Parallels Desktop error report. (http://dl.dropbox.com/u/3753352/prl_client_app_2011-05-24-102711_localhost.crash)
Here is Virtual Box error report. (http://dl.dropbox.com/u/3753352/VirtualBox_2011-05-24-110614_localhost.crash)
Here is Kernel log. (http://dl.dropbox.com/u/3753352/kernel.log.txt)
I know the solution:
Pack the binaries with my custom upx, it'll work ;)
EDIT: The one under <Application.app>/Contents/MacOS/<Application>
The errors are both about the same.
In Parallels: before GetDYLDEntry it fetches 0x0000000 which can be resolved with my custom upx

[mayx]

I know the solution:
Pack the binaries with my custom upx, it'll work ;)
EDIT: The one under <Application.app>/Contents/MacOS/<Application>
The errors are both about the same.
In Parallels: before GetDYLDEntry it fetches 0x0000000 which can be resolved with my custom upx
It works,thank you so much!!!
Actually,i had do this before,and i just test it in the 64bit mode.
This time,i remove the "-force64" flag,then it works.:p

Thank you for your hard works!!!

[xmen1]

someone can explain how I install this kernel, I'm noob .... the old kernel at boot I get this error: Warning Kernel was not build with custom dyld blob, someone can help me how to install this kernel ... thanks. i have a pentium D 945

[davisin666]

DO NOT UPDATE TO 10.6.8

It freezes in a [PCI CONFIGURATION BEGIN] and there are missing kernel symbols, in other words, it will break your install :'(

EDIT: You can update to 10.6.8, but using IOPCIFamily.kext and AppleACPIPlatform.kext from 10.6.7

[mindlessmissy]

DO NOT UPDATE TO 10.6.8

It freezes in a [PCI CONFIGURATION BEGIN] and there are missing kernel symbols, in other words, it will break your install :'(

EDIT: You can update to 10.6.8, but using IOPCIFamily.kext and AppleACPIPlatform.kext from 10.6.7

Yep ... I am guessing this only happens on AMD since other people did not run into this problem.

Also ,after swapping out the 10.6.7 kexts, the missing kernel symbols problem still exists BUT hopefully a 10.6.8 kernel will solve that when it is available ...

I read on netkas' blog that the IOPCI kext is similar to the one in Lion ...

[andyvand]

Yep ... I am guessing this only happens on AMD since other people did not run into this problem.

Also ,after swapping out the 10.6.7 kexts, the missing kernel symbols problem still exists BUT hopefully a 10.6.8 kernel will solve that when it is available ...

I read on netkas' blog that the IOPCI kext is similar to the one in Lion ...
Seems Netkas has found another way to fix it:
best fix is adding kernel boot flag npci=0Ũ2000
It should fix it...
My version of the 10.6.8 kernel is coming the latest next week... ;)

[RobertX]

good to hear that Andy....dare I ask about the sse3 emulator?:D

[andyvand]

good to hear that Andy....dare I ask about the sse3 emulator?:D
I have a new one (thanks go to Slice I believe) but I haven't had much time yet to code the 10.6.8 version of the kernel.
It will integrate this new SSE3 emulator.
When I have the time (probably this weekend) I will adapt the build script and build the new kernel.
Currently I'm very occupied by my education and tomorrow I have a very important job interview (which will probably go down in french... ;))
I'll post results as soon as I'm finished...
EDIT: Oh yeah... more good news... the assembly sources for the new SSE3 emulator are included so people can do work on that as well ;):)

[scififan68]

Andy, I just wanted to say thanks for your kernel, I'd have to say it works best out of any kernel out there, and again thank you! :)

[RobertX]

i'll keep my eyes open...here...and at the other place...:D

[RobertX]

:cool:;)...ready here...

[alaskan]

Gonna bump this back into attention getting range.
:-d
AndyV, you make exceptional kernels.
Latest one I have is legacy_kernel_Anv R2 v8 which is for OS X 10.6.8.
Do you still have one for 10.7 or later. One that might work with AMD CPUs?

I would really appreciate a copy, if you do. Thank you.:cool: