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

[odin1937]

Originally Posted by wastez 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!

[wastez]

Originally Posted by odin1937 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!

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]

Originally Posted by 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?

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]

Originally Posted by LinearBurn 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]

Originally Posted by 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

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