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

wastez · #41 04-19-2011, 08:52 AM

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 · #42 04-19-2011, 11:26 AM

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 · #43 04-19-2011, 10:31 PM

Quote:

Originally Posted by odin1937

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

Code:

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 · #44 04-20-2011, 07:48 AM

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 · #45 04-20-2011, 08:24 AM

Thanks.

GringoVermelho@InsanelyMac said:

Quote:

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 · #46 04-20-2011, 08:55 AM

Quote:

Originally Posted by maya77

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 · #47 04-20-2011, 02:24 PM

Quote:

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 · #48 04-20-2011, 02:53 PM

Quote:

Originally Posted by wastez

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 · #49 04-20-2011, 03:44 PM

Quote:

Originally Posted by andyvand

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 · #50 04-23-2011, 08:42 AM

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

Thanks for your explanation, I appreciate that.