Legacy kernel 10.6.8 with custom dyld and new SSE3 emulator and VIA Nano cpu support
The full package included, as usual. I've also added support for VIA (Nano) cpu's (the cpuid of those can be modified by a few rdmsr/wrmsr instructions). Furthermore I included the new SSE3 emulator as default (thanks for the person who…
- Primary Author
- @andyvand Published 2011-08-10
- Collection
- OSx86 Core & 10.X
- Archival Footprint
- 165,733 historical reads · 199 curated field notes (from 291 dispatches) · 2011-08-10 – 2012-04-06
- Credited Voices (29)
- @andyvand (68)@akimoa (50)@wastez (28)@davisin666 (27)@$The-King$ (21)@m28ew (13)@bassie86 (11)@nightf4ll (8)@hans88 (7)@fumoboy007 (6)@Imkantus (6)@scififan68 (6)@Sn0wStorm (6)@Unrealized (5)@blackknight (5)@kocoman (3)+13 more
The full package included, as usual.
I've also added support for VIA (Nano) cpu's (the cpuid of those can be modified by a few rdmsr/wrmsr instructions).
Furthermore I included the new SSE3 emulator as default (thanks for the person who supplied it, I forgot his name, credits go to him).
It also includes the custom dyld.
BTW: Sorry for the late entry but at work my workstation wouldn't allow rapidshare so I had to bring along my netbook (to link it to the corporate WLAN network, then it worked).
Download including sources:
rapid share.com/files/2811076327/voodoobuild-AnV-0.4.1.zip
Author Updates & Technical Revisions
Follow-up dispatches by @andyvand
@wastezDid you fix the problem with the fsb detection for amd if the bootloader detect it´s fsb correct? Because the old fsb "fix" take the default fsb and multiply it x2.
No, I haven't done that yet.
Haven't updated the FSB algo's (just added there support for Via Nano, which is mostly Intel compatible).
BTW: If you could point me to the patch I may be able to add it.
@UnrealizedWhat about Lion? Could your diff work for Lion's kernel?
Not without modifications.
Somebody (some geekXXXX) made a patch for Lion to run on 32bit kernel.
With my diff it wouldn't work for 32bit so I need his patch too before I can make a new diff for Lion.
If somebody could contact him (I believe you can find him on InsanelyMac forum somewhere) and ask him the diff + get it to me I could get to work...
I allready compiled up a test kernel from within Snow Leopard in case of Lion and I can make one from within my environment (untill I can get the final version of Lion + suitable kernel).
I just need his diff...
EDIT: Oh yeah, if anybody could upload me the final version of the Mac OS X 10.7.sdk (from under /Developer/SDKs) I would be very grateful. it will be used for the new custom dyld.
@UnrealizedNice, gonna look on InsanelyMac if I can find him and ask for the diff. Lion on AMD/Via Nano would be so awesome. From what I've understood, Lion requires a "full 64-bit mode" ? It's like finding a needle in a haystack, but I think it's worth it. Not sure if I can find him though..
Yes but that guy, geek (with a number behind it) would have a kernel that works in 32bit mode too.
If we can get our hands on that patch, we can make the legacy kernel also available for 32bit booting.
If we can't, it's gonna require 64bit cpu's (64bit Intel/AMD/Via).
@fumoboy007I know about 32-bit kernel + 64-bit userland mode. What I'm wondering is...if Finder is a 64-bit only app, 32-bit processors won't be able to run it. So what's the point of making a 32-bit kernel?
Ok, if all Lion apps are 64bit only I'll construct the current kernel as I will make it.
It'll only work on 64bit computers then too...
@akimoathe only guy with a lion 32bit kernel is smartie77 all he did is he compiled one from the sources but he didn't involve any patching talked to him about that and exualy the rest without one boots it with arch=i386 so why would it need a patch if it boots already in 32bit mode ? vanilla offcourse only
Then you have a point.
I've tried it with Atom (32bit only) but it didn't work...
If he only compiled the sources there won't be any additional additions.
Legacy kernel as current work thus...
@ImkantusAs you should know, Finder (and some other stuff) is 64-Bit only since Lion DP2 (and any later release). I have tried Lion GM using your DP1 Kernel on Atom N230, apart from not having Finder, there were problems caused by launchd not working properly... it was kinda eating up my 1GB RAM - so I gave up on that... So a 64-Bit capable…
With some minor code modifications.
Mods for custom dyld (for Lion) are complete, custom dyld for Lion builds now.
Mods for xnu are coming along (I just worked the entire night yesterday, I think it compiles allready for 32bit but requires some minor fixes for 64bit (warning fixes)... work continues).
I'll release all my work once it's done, somebody with Xcode 4.1 could recompile the kernel in order to make it fully Lion compiled.
Compiling the kernel under Snow Leopard (with Xcode 3.2.6/4.0) is possible with some minor code fixes (variables used uninitialized, just set them to 0 on the beginning of the defines).
Also Apple didn't change much on their decryption algo's, current implementation should work, however I had to rewrite amd_insn_patcher (and also add the changes to the kernel) because of a new 6 byte (instead of 8) _sysenter_trap routine.
Code mods on that part are complete and it puts it into it as it was doing with 10.6 (but uses a uint32_t as first and uint16_t as second code wrapper).
I've left the patcher for Snow Leopard's _sysenter trap into it, it just checks which precise _sysenter_trap is used and patches accordingly.
The change was just a nopl (%eax) to nop... (3B -> 1B).
I guess it will take at most a week to get the code wrapped up completely (and fixed for Lion), it'll work on all 64bit machines, even though having SSSE3 is really recommended since Lion.
I've checked for any SSSE3 checks in the kernel, there where none, it just catalogs the available instruction sets so if there would be any messages, they aren't coming from the kernel.
I should really check how these SSSE3 instructions (it aren't that many) work so I can devise a solution for them.
But first... the kernel ofcourse...
BTW: On InsanelyMac I uploaded Rev2 of the V8 (10.8.0) kernel with some minor fixes for AMD K10 FSB (as latest chameleon fixes that) with the option to double the FSB on those AMD models with -doublefsb boot arg.
I also did some minor changes for Via Nano, it now gets the CPU frequency through EFI booter.
Besides that it includes the custom dyld built with Apple's libunwind-30 code (which compiles fine on Snow Leopard too) but it didn't fully fix some apps crashing.
pbs still gave me some issues (unless I upxed it with my custom upx, then it worked fine).
I'll look into a solution for this as most crashes come from libauto.dylib (Auto::Zone::Zone).
QuickDraw (QD) also gave for some apps a crash.
Too bad we haven't got Apple's libCoreSymbolication library (with matching header) or we would be able to fix the last issues with the custom dyld.
Work continues thus and new solutions are sure to surface (I'm thinking hard for improvements/expansions).
I'll keep you posted...
I have one more request.
Could somebody please zip and upload the dyld from Lion GM?
I need it because it checks for code signatures and I need to devise a patch against it.
It is required because if you patch the stock dyld (and/or libSystem.dylib) the code signatures won't be valid anymore.
If I have the stock dyld I can disassemble my custom one (which has this code excluded) and the stock one and check the differences.
If I find this difference I can make a patch (using amd_insn_patcher) which also nops out the code that does the actual code signature check in dyld.
It'll then work with the stock Apple Lion dyld too.
It's important because we need to get these things working 100% for AMD under Lion.
BTW: Don't use rapidshare/mediafire/upload.to/etc as my works internet blocks these in the proxy, upload directly here or on InsanelyMac please.
EDIT: Anyone? Please do it ASAP as I would like to devise a patch against it today... Just zip /usr/lib/dyld please + upload...
@wastez@ anv I could compile the kernel on Lion if you want to?! Just need the source to do that.
Ok, when I finish with the final revisions I'll send you the version to compile under Lion.
You could allready compile the LLVM library for i386 + x86_64... you need it to build the tools...
@wastezI already did that. Compiled the source a few days ago.
Ok no worries then
I'll put in an extra script in case the voodoobuild.sh does everything but the kernel (extra script to build kernel after build halt, do after building dyld + patching dyld + rebasing dyld + injections in xnu when it's patched).
We'll get there soon... and it'll work great... :
@davisin666What about libunwind and the custom dyld, will be fixed the issues with that? Thanks for the kernel
No, unfortunetely probably not.
There are still some libraries which we don't have (libCoreSymbolication for example).
It works better but there are still some apps which don't work with the custom dyld.
I finished making the kernel patches yesterday.
The code compiles well, now just some minor changes to the build script and we'll be on our way.
I'll build the sources under Snow, upload sources and built product, then wastez can build it with Xcode 4.1 GM and then I'll patch those built products also up for Atom...
I'll probably finish the building (and adapting) this evening, uploading the sources and built products tomorrow.
@wastezOk that´s really fine. Just tell me if you have finished it.
I modified the script for building the Lion dyld + kernel.
It's currently building on my netbook (@ work).
I'll upload it when the build finishes.
It'll be uploaded @ insanelymac in my current legacy kernel thread (I'll post the link here).
I've also made a compile_kernel.sh script to start the build in an allready patched + injected xnu-xxx directory.
Both will need to be runned from within the voodoobuild-AnV-0.5.1 folder.
@davisin666One more question, the kernel is for 10.7.0 or 10.7.1? Thanks for the kernel! I'm anxious to try it
It will be the xnu 11.0.0 for 10.7.0.
Apple hasn't released the 10.7.1 sources yet...
@nightf4llhmm... ok i m preparing Xmove and install partition lets pray to god this kernel works even if it doesnt, still thank you for the hard work..
We'll know tomorrow.
My battery ran flat before I could get the kernel compiled so this evening I'm compiling the kernel (with dyld injected).
I'll upload the sources and binaries tomorrow thus.
NOTE: The sources will need to be recompiled by Wastez in order to be completely perfect (currently compiling under Snow Leopard, also doing tests of using dyld-195.5 on Snow Leopard by using Snow Leopard libc libraries and new dyld with some mods to it... keep you posted on this as well).
@wastezDid you activate the sse3 emulator for 10.6.8? There is no ssse3 emulator until now but the lion kernel is also not available now. But today the lion kernel is gona to release.
http://www.insanelymac.com/forum/index.php?showtopic=26… ↗
It's released... last post when I started it...
Recompile it for me please and send me the results (and prefereably upload them).
I compiled it under 10.6.8 but Wastez will compile for the rest.
NOTE: Wastez: I forgot to change in the voodoobuild.sh script the patch to LibcXXX instead of LibcXXX_SL
Change it please and recompile (it's a case of adding a # and removing one)
@wastezOk... Compiled the kernel. But it created 2 mach_kernel. One in the root from voodoo build folder and one in the source in /build/sym. The one in the root has 15,4 mb and the one in the source has 18.7 mb. Which one is the right one?
You need the one in BUILD/dst
it copies automatically in voodoobuild-AnV-0.5.1 (with running ./compile_kernel.sh).
Make sure you have done ./voodoobuild.sh first.
@wastezOk… Then it´s the one with 15.4 mb. I also edited the voodoobuild file. Akimoa tested it on his amd but it doesn´t work --> instant reboot. Could the be the same problem like on snow in pure 64 mode?
Probably: yes
Unfortuntely I have no idea of what precisely changed that doesn't allow 32bit only boot.
Otherwise I could track it down...
@akimoaOk that what i was just wondering myself but it seems in the voodooscript the 32bit part didnt got adressed at all or am i missing something and it doesn't boot in userland 64 either with or without custom dyld
try -force64 (patches come from Snow Leopard so...)
@akimoaOk that what i was just wondering myself but it seems in the voodooscript the 32bit part didnt got adressed at all or am i missing something and it doesn't boot in userland 64 either with or without custom dyld
@ImkantusIt is still instant reboot after Chameleon says "Staring Darwin x86" I have also tried stripping the Kernel with lipo in order to be ensure booting i386 Kernel...
Damn... I have no idea what it could be...
It probably still needs some work thus...
@wastezThis time it´s gona to be funny for amd´s. Last time there was time to get a solution until get 64 bit Userland working. Now it won´t work without it. @$The-King$ The problem isn´t the boot loader for sure. @anv Did you change something on the 32 Bit Kernel this time, or did you just edit the 64 bit kernel?
I added the code of the patch for both 32 and 64bit kernel.
I think Apple removed some routines which are required for AMD or changed some code which is giving the issues.
I diffed SL 10.6.8 versus 10.7.0 and there are a lot of differences (for example the commpage is a lot more empty).
It's like looking for a needle in a haystack :-|
@akimoathe filesize difference between the 2 released xnu sources (10.7 and 10.7.1) is huge just tried the diff (without custom dyld and sse3emu etc.) on the latest source -> same result sadly any way to debug this ?
I wish... somebody with a vanilla capable cpu should test it to see if it at least boots there...
I'm continuing looking for a solution (but it won't be easy...)
@akimoak and if it Boots there what would u need in logs to dig in kernel.log ? or any other one ?
Unfortunetely the logs don't contain what I need.
I need to know which instruction causes the reset in case of the kernel in order to know what to do against it.
@scififan68It didn't reboot on my 64bit Pentium 4 HT, but it crashed later in the boot. I can take a picture of the kp.
Good idea, it might help...
@wastezOn a vanilla compatible cpu the kernel is working. 32 Bit + 64 Bit.
So it's not the code that's present... it's the code that's absent...
I'll continue to develop this...
Since You have a vanilla cpu could you test the AMD patching routines by booting with the following boot args:
arch=<i386/x86_64> patcher_opts=48 -amd -force64 -v
@scififan68dl.drop box.com/u/38348368/100_1824i386.JPG kp in 32bit mode dl.drop box.com/u/38348368/100_1827x86_64.JPG in 64bit mode This is with andy's kernel complied in Snow Leopard. The one complied in Lion just gives me a black screen.
I can't look it up, my workplace bans dropbox using the proxy.
Please upload them here on the forum.
@andyvandSo it's not the code that's present... it's the code that's absent... I'll continue to develop this... Since You have a vanilla cpu could you test the AMD patching routines by booting with the following boot args: arch=<i386/x86_64> patcher_opts=48 -amd -force64 -v
ASAP please...
If it boots succesfully the auto-patcher works... including the dyld (even though I'm not sure the stock one will work...)
@akimoawell we have someone that tests for us ... where would he see if the routines go thru ?
If you want verbose patching you need the following after patcher_opts:
49
Then it will output everything it loads (and patches) and output to console.
It will warn about decryption failing in the beginning untill DSMOS arrives...
If it all works and the system boots we at least have the patcher right (including the new sysenter trap working)
@scififan68Is there another site I could upload them to that isn't blocked, since my images are too large to upload on the forums.
Can't you compress them to a png or so?
If you can't make it smaller, upload it to a webspace or so (free webspace from a provider or so).
All upload sites are blocked over here so no go there...
@scififan68Well how about I post them on my own website, cefso.doesn texist.org/temp/100_1824i386.JPG cefso.doesn texist.org/temp/100_1827x86_64.JPG
Should be fine...
@akimoait booted all the way thru and apps worked with the vanilla machine when testing patching routine
And patcher patched up the apps?
Did you boot verbosely?
If so at least that allready works...
@akimoawell the apps would not have worked if not rite ?... he did boot verbosly but not recognizable he will hopefully test again and will get a dmesg out if that helps
Even with the increased message buffer it won't be enough to store the 49 option.
It will do for a 48 though...
@akimoaIt doesnt seem to me that this will help ya but here it is with 48
You're right it doesn't.
If you boot with patcher_opts=49 -amd does it show the libraries it loads?
Because I see no reference to any libraries...
EDIT: Could it be that the boot arguments aren't handled correctly? It seems weird -force64 typed didn't work... it seems we have a bug in Chameleon...
@akimoahere is anything he could get out with 49
Damn... it didn't set the boot args...
Editing /Extra/com.apple.Boot.plist may help but it's still with risk...
Which bootloader are you using?
I found the routines that do code signature checks on the pages + through dyld syscall.
I modified the code slightly so it will verify all code signature kernel checks as valid.
This means we can use stock dyld too...
I also noticed the panic.
It panics on map_text_segment_sys (that's where the trap gets called).
I modified the code slightly for the new syscall format (it shouldn't panic anymore).
I'll post the results soon, please test on that P4...
@akimoaAny Progress in the Lion Legacy Mission m8 ?:-d
No, not yet but I've taken a different approach.
I've diffed the standard SL kernel against the standard Lion kernel (to find out what was changed).
Lots of code to go through.
I've also disassembled the Lion DP1 kernel as well as the GM one and have written a little program to strip of the addresses.
I've diffed these together to get instruction changes in the diff.
Studying both may reveal a solution.
I'll upload the diff later.
I've posted the assembly diffs between 10.7.0 DP1 and 10.7.0 GM
I hope somebody can help me identify which instructions enable 32bit (and thus also AMD) support.
They can be found here:
http://www.insanelymac.com/forum/index.php?showtopic=26… ↗
I also included my custom otx tool
NOTE: There is a 64bit part to otx but it is untested. If trouble, run it in 32bit, it also needs Xcode
@akimoaa needle in a haystack looks more sexy wondering if these compare programms would help us in searching by comparing the 2 files next to each other and find our needle … just wondering
yeah, I agree, I've been trying for weeks.
Currently I'm designing a custom 10.7.0 kernel with 10.6.8 osfmk directory (requires a lot of adjustments).
I'll keep you posted if it works, then we at least know where to look.
@hans88AnV heard that you were on the LION kernel for AMD...was just wondering if you were still on it, cause didn't hear you for a while?!
Looooots of work on getting it done... haven't isolated the problem yet...
@wastez@ AnV Is there a possibility to run the Lion GM with the 32 bit kernel of the DP Version? And if it work would it be possible to create an modified version?
Yes DP1 kernel and some other files (like Finder and finder cache), it'll only work on Atom / Yonah though.
Look on the internet (google ;)) for more info.
@wastezDid not think on it that there is no source from dp. I´m also starring at the kernel txt file since yesterday and it´s gona to drive me crazy.
Yeah, I also wish Apple had released their xnu-1699.21.x sources (instead of 1699.22 ones).
With a bit of work they at least would have worked just fine on AMD.
@blackknightI'm curious if with the new AMD fusion processors supporting SSSE3 instructions if they will support full 64-bit mode on Lion and SL. I'm looking to get one of the new AMD FX processors when they release and they effectively support all of the intel instructions. What do you think Andy?
Snow Leopard: no doubt
Lion: Maybe, if they don't cause instant reset... :
We need to test them to be sure...
@davisin666map_text_segment_sys, maybe there is something wrong with the decryption algorithm or Apple encrypted more binaries. Remembers me from Snow Leopard Decryption hasn't succeeded yet (probably will retry) patch_exec_obj_segment failed map_segment failed Damn, I want Lion
I checked the way Lion decrypts, it's the same way.
I should try to add a few patches and drop custom dyld and auto-patcher support.
Without the map_text_segment_sys syscall replacement (syscall 8) it might work...
Keeps you posted...
This weekend I can put some time aside for making a new Lion kernel...
Keep you posted.
@akimoaHows it going on the project guess alot people have that question in mind thats why im asking it ?!
Working on it.
I studied the kernel some more and saw csops routine.
It's a syscall used by dyld which checks code signing (and in dyld code it halts execution if incorrect).
Guess there are a few more corpses that need burying lol.
This weekend I should have a solution...
@wastezIs there something new about the lion kernel? Hope you´ll get it soon.
Still working on it but I don't have a lot of time (lots of work@work :-p)
I'll post results as soon as I can.
I finished the work on the patches.
@Akimoa: Please compile and test both patches (AutoPatcher + NoAutoPatcher).
I also included a new amd_insn_patcher for use with SL / Lion (sysenter trap is slightly different on Lion, needed for dyld and libSystem.B.dylib).
Test it out please and let me know the results.
Also: It will say something like /Users/andyvand/Downloads/10.7.0/voodoobuild-AnV-0.5.1/xnu-1699.22.73/bsd/sys/make_symbol_aliasing.sh: line 85: /usr/local/libexec/availability.pl: No such file or directory
Because the script availability.pl is not available, ignore it, it will compile just fine.
@Akimoa: I just finished doing some fixes (compiling it too) and I fixed up some warnings and 1 error which let it fail.
Uploaded correct versions.
@Akimoa: Another correction, this one for noautopatch-v1.diff.
I forgot to remove the syscall mod for this one...
Normally it should work fine with this one...
@akimoaindeed that went thru better
Don't forget to use the new one for noautopatch version.
@akimoaI will still building 1st
It's extremely important to use the last one I uploaded because syscall 8 may not be modified on the noautopatch version.
@akimoaI will still building 1st and here they are : Legacy Kernel 10.7 No Autopatch cl .ly/0G0R152u09332z0i3E10 Legacy Kernel 10.7 Autopatch cl .ly/1z3j321i2a0g1i171819 theres always both i386 and x86_64 Version of it i wont be testing them now since its to late but will do 1st thing tomorrow Have fun
Has anybody tested these?
@akimoaYes Busy ! with it Instant Reboot on NoPatch i386
And the others (including the x86_64 version)?
I'm also compiling a kernel (using Xcode 3.2.6).
I will post download link when ready
@Sn0wStormInstant Reboot for me too do we have to use special boot flags on the No Autopatch Kernel, or is it just for dyld patching?
Try booting with -force64 boot flag (may work but not sure).
dyld patching on the no autopatch version is done with the new amd_insn_patcher (This works, I tested it).
Soon I'll post my compiled version of the no autopatch kernel (cross the fingers that Xcode 3.2.6 makes a difference).
If this doesn't work I'm out of ideas (same goes for creating a new kernel patch).
@akimoahere the missing one sorry hope it makes a diffrence(link corrected to) cl .ly/0X0w3s300U002z0W0K3t
Any report yet on the x86_64 kernels?
I hope at least those work, then I know where to look. :-|
@akimoawell on both x86 _64 Chameleon stops rite after enter goes back to command prompt at least here
I'm almost done compiling the universal (32+64bit) kernel (using Xcode 3.2.6).
Lets hope that at least works...
Ok, I finished compiling the noautopatch version using Xcode 3.2.6.
It's built as a ub (i386+x86_64 in one bin).
Download:
rapid share.com/files/2791902381/legacy_kernel_lion_noautopatch.zip
Please test and let me know if it works.
I tried it on my 32bit Intel netbook.
It doesn't instant reset but it gets stuck on a black screen.
I'm using Cparm's latest bootloader...
I bet that if you test this kernel on a supported Intel, it works...
Could anybody with vanilla cpu test this hypothesis?
Try both my compiled version as well as Akimoa's... :-|
@m28ewI've tested those new kernels on my AMD P-II x4 965 with flags: arch=i386 ; arch=i386 -force64 there's no KP, but I got stuck at the "No interval found for . Using 8000000" line with flag: arch=x86_64 I got this KP
Can you boot into single user?
Then you could get the dmesg to me... I could use it to look up what goes wrong...
A new hope... :-d
EDIT: The second (the kp) is the classic 64bit AMD AppleACPIPlatform.kext panic...
@m28ewunfortunately, with: arch=i386 (-force64) -s I still got stuck at the same line :'(
Try setting a scheduler with one of the following boot arguments.
traditional scheduler: sched=traditional
traditional scheduler with pset runqueue: sched=traditional_with_pset_runqueue
proto scheduler: sched=proto
grrr scheduler: sched=grrr
fixed priority scheduler: sched=fixedpriority
fixed priority scheduler with pset runqueue: sched=fixedpriority_with_pset_runqueue
Only use one and please test all to see if there is a difference.
These control how the processor schedules instructions.
On AMD you may also want to use boot argument npci=0x2000
Still investigating for the interval lines...
EDIT: Oh yeah... are you booting from a DVD? Try using an USB boot... (may be worth trying)
Also grep for the string "No interval found" in all the .kext files with the following command:
grep -E "No interval found" /System/Library/Extensions/*.kext/Contents/MacOS/* /System/Library/Extensions/*.kext/*
Tell me if one matches...
@davisin666Pthread support ABORTS when sync kernel primitives misused No interval found for . Using 8000000 Looks like we need to compare the log with the vanilla dmesg if these messages appears
I saw this one appearing on my Intel with DP1 too: Pthread support ABORTS when sync kernel primitives misused
But No interval found for is not part of the kernel... either is coming from an app or coming from a kext...
Still investigating...
EDIT: Can't find it anywhere in DP1... don't have GM so can't check...
Did changing the scheduler change anything?
How about booting the installed product? This is the install DVD, right?
EDIT2: Did you patch /usr/lib/dyld and /usr/lib/libSystem.B.dylib with amd_insn_patcher (the new one for Lion)? It is needed for 32bit support under 64bit...
Fixed amd_insn_patcher... :-|
It's IOHIDFamily that causes the misery allright...
Decompiling + checking...
EDIT: Removed check for interval (which causes the failure).
The problem in this case is VoodooPS2 in fact but the kext I posted should do fine (little workaround with hex editor ;))
Back up your original before testing...
@m28ewstill no luck :'( all testings were done by booting the osx from DVD (BSD Root=disk1s3) & HDD (BSD Root=disk0s2) and they all stuck at the same line I haven't patched them yet could you also share the binary of the amd_insn_patcher ?
Should be there under the source... amd_insn_patcher...
@akimoa@m28ew Try using patched IOUSB from AnV (SL) might change a thing and Andy cant we set a debug somewhere ? besides the scheduler aruments ?
There is a debug= boot argument (not sure how to use it though).
The other option would be compiling a debug kernel (with make ARCH_CONFIGS="I386 X86_64" KERNEL_CONFIGS=DEBUG install)
@akimoaAkimoAs-MacBook-Pro:xnu-1699.22.73 akimoa$ make ARCH_CONFIGS="I386 X86_64" KERNEL_CONFIGS=DEBUG"install" /Users/akimoa/xnu-1699.22.73/makedefs/MakeInc.def:164: *** Unsupported KERNEL_CONFIG DEBUGinstall. Stop. AkimoAs-MacBook-Pro:xnu-1699.22.73 akimoa$ make ARCH_CONFIGS="I386 X86_64" KERNEL_CONFIGS=DEBUG"RELEASE"…
Cut and paste the following:
make ARCH_CONFIGS="I386 X86_64" KERNEL_CONFIGS=DEBUG install
note the space after release... and no ""
Right now I have a real Mac and I tested my Lion kernel.
The good and bad news is that it actually works.
I haven't yet been able to find why the Lion kernel doesn't work on AMD.
@$The-King$andyvand if you have time can you please fix FSB to 200 as it cause to me problems on sound lagy sound dont forget me
I'll do it soon, I don't have my hackintosh with me as I work on my real MacBook Pro right now.
I won't forget you.
Synthesized Community Field Notes
199 technical responses curated from 291 original dispatches
Did you fix the problem with the fsb detection for amd if the bootloader detect it´s fsb correct?
Because the old fsb "fix" take the default fsb and multiply it x2.
What about Lion? Could your diff work for Lion's kernel?
Nice, gonna look on InsanelyMac if I can find him and ask for the diff. Lion on AMD/Via Nano would be so awesome.
From what I've understood, Lion requires a "full 64-bit mode" ?
It's like finding a needle in a haystack, but I think it's worth it. Not sure if I can find him though..
@andyvandYes but that guy, geek (with a number behind it) would have a kernel that works in 32bit mode too.
is that him ?
http://www.insanelymac.com/forum/index.php?showtopic=263074
the only guy with a lion 32bit kernel is smartie77 all he did is he compiled one from the sources but he didn't involve any patching talked to him about that and exualy the rest without one boots it with arch=i386 so why would it need a patch if it boots already in 32bit mode ? vanilla offcourse only
@andyvandYes but that guy, geek (with a number behind it) would have a kernel that works in 32bit mode too. If we can get our hands on that patch, we can make the legacy kernel also available for 32bit booting. If we can't, it's gonna require 64bit cpu's (64bit Intel/AMD/Via).
Aren't all of Lion's apps 64-bit only? So what's the point of making the Lion kernel available for 32-bit?
Wow, I guess this will be a lot of work for kernel developers.
@fumoboy007Aren't all of Lion's apps 64-bit only? So what's the point of making the Lion kernel available for 32-bit?
I think it's like Snow Leopard, when using a 32-bit kernel you can still run 64-bit apps (hybrid mode).
@UnrealizedI think it's like Snow Leopard, when using a 32-bit kernel you can still run 64-bit apps (hybrid mode).
I know about 32-bit kernel + 64-bit userland mode. What I'm wondering is...if Finder is a 64-bit only app, 32-bit processors won't be able to run it. So what's the point of making a 32-bit kernel?
I would say it isn´t sure that the 64 Bit Kernel will run on AMD without problems.
Because on snow there are also problems with the 32 bit apps if 64 bit kernel is running.
he made me a list how he succeeded makin one thats what he included
Xcode 4.1 GM ,10.7 GM bootstrap_cmds-79 dtrace-90 kext_tools-180.2.1 cxxfilt-9 +xnu source offcourse
cause it gave me many errors when trying with 10.6.8 using Xcode 3.26 and the SL build tools then i came along his thread and he pointed that out and it ran thru
These are the small tools i zipped them up since wastez was trying to get them these morning and he wasn't able to
these includes
bootstrap_cmds-79
dtrace-90
kext_tools-180.2.1
cl .ly/0A050O2V2D3K0U223o2J
the bigger cxxfilt-9 is still the old version and is still there
just incase u need them
@andyvandOk, if all Lion apps are 64bit only I'll construct the current kernel as I will make it. It'll only work on 64bit computers then too...
Well, 32-bit machines are kinda slow to even run Lion, so It's a good point anyway.
@andyvandOk, if all Lion apps are 64bit only I'll construct the current kernel as I will make it. It'll only work on 64bit computers then too...
Well actually, I'm just speculating...I don't know for sure that all of Lion's apps are 64-bit only. I'll check tonight on my new MacBook Air.
@andyvandOk, if all Lion apps are 64bit only I'll construct the current kernel as I will make it. It'll only work on 64bit computers then too...
As you should know, Finder (and some other stuff) is 64-Bit only since Lion DP2 (and any later release).
I have tried Lion GM using your DP1 Kernel on Atom N230, apart from not having Finder, there were problems caused by launchd not working properly... it was kinda eating up my 1GB RAM - so I gave up on that...
So a 64-Bit capable CPU is definitely required for running Lion & a Kernel running 32-Bit legacy mode only would be practical useless.
Anyway a 32-Bit Kernel capable of booting Lion on AMD / VIA / old Intel forced into 64-Bit mode would be a great success at this point - as even if you cannot make a custom dyld at the moment, we could bin-patch the Apple one manually like been done on Snow Leopard earlier...
How did you manage to compile Lion Kernel in Snow Leopard?
@ImkantusAs you should know, Finder (and some other stuff) is 64-Bit only since Lion DP2 (and any later release).
Confirmed. Time to make legacy kernel 11.0 64-bit exclusive.
@anv
I saw on apple´s open source that there is the source for the libunwind for lion.
Should be perfect for a custom dyld i think!
H.264 and Quicktime
Is there any way i can fix H.264 and Quicktime in 64 bit mode on an AMD procesor? Anything i can do with amd_insn_patcher or should i just give up and go back to 32 bit mode?
@nightf4llIs there any way i can fix H.264 and Quicktime in 64 bit mode on an AMD procesor? Anything i can do with amd_insn_patcher or should i just give up and go back to 32 bit mode?
You will need to run QuickTime in 32-bit mode if your processor does not have SSSE3 support.
@fumoboy007You will need to run QuickTime in 32-bit mode if your processor does not have SSSE3 support.
I have an AMD Athlon 64 X2 just like you, and they support sse3.. I have no idea why quictime crashes when playing .mov and .mp4 files, but only in 64 bit mode..
I ve read somewhere that i need to manually patch quicktimecomponents and h264scalar, thats why i m asking if some1 else managed to get it to work?
I wish i bought that intel processor instead AMD :-|
@nightf4llIs there any way i can fix H.264 and Quicktime in 64 bit mode on an AMD procesor? Anything i can do with amd_insn_patcher or should i just give up and go back to 32 bit mode?
SSE3 != SSSE3
The amd_insn_patcher just removes those nasty SYSENTER traps, code signatutres... that prevent 32-Bit only Apps to work on 64-Bit mode AMD systems.
It is not going to emulate any Intel exclusive instructions.
You do not have to lunch the -legacy mode again, just run Quiktime 32-Bit only.
btw: VLC rules.
@ImkantusSSE3 != SSSE3 The amd_insn_patcher just removes those nasty SYSENTER traps, code signatutres... that prevent 32-Bit only Apps to work on 64-Bit mode AMD systems. It is not going to emulate any Intel exclusive instructions. You do not have to lunch the -legacy mode again, just run Quiktime 32-Bit only. btw: VLC rules.
Thx for clearing that up and i have VLC already, thats first thing i dowloaded One more question.. I ve removed 64 bit part from quicklookd and now it loads only in 32 bit and doesnt crash, but how can i fix preview crash?
P.S. the instructions for that are here ↗ if some1 needs them
@nightf4llThx for clearing that up and i have VLC already, thats first thing i dowloaded One more question.. I ve removed 64 bit part from quicklookd and now it loads only in 32 bit and doesnt crash, but how can i fix preview crash? P.S. the instructions for that are here…
To fix preview crash, you need to remove the x86_64 part of Finder, so, open terminal and type:
sudo cp /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder_bak
sudo ditto -arch i386 /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder_i386
sudo mv -f /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder_i386 /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder
Works f****ing good :
@davisin666To fix preview crash, you need to remove the x86_64 part of Finder, so, open terminal and type: sudo cp /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder_bak sudo ditto -arch i386 /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder…
Ok I did all of that, rebootet and everything works fine.. Now which kernel should i use on my Athlon 64 X2? Whats the difference between Nawcom's Legacy kernel and Andy's? Should I use mach_kernel or mach_kernel atom? They both work for me..
@nightf4llOk I did all of that, rebootet and everything works fine.. Now which kernel should i use on my Athlon 64 X2? Whats the difference between Nawcom's Legacy kernel and Andy's? Should I use mach_kernel or mach_kernel atom? They both work for me..
The difference between nawcom and andys kernel is the custom dyld for on the fly cpuid patching.
But you can also disable the the custom dyld with flag std_dyld=Yes.
If you have a atom cpu you have to choose the mach_kernel atom and if not you have to take the other one.
Uhm am i the only one that desires a ssse3 emulator for snow leopard?
@RayFlowerUhm am i the only one that desires a ssse3 emulator for snow leopard?
No, you are not.
@RayFlowerUhm am i the only one that desires a ssse3 emulator for snow leopard?
Latest AMD Fusion Mobile & Embedded cores have SSSE3 implementation & I think we will see Desktop CPUs with SSSE3 support end of this year.
There are some Mini-ITX boards using AMD Zacate (Brazos) cores - some less then 100€ (like the E350IS-E45 just 88€, 1.6 GHz Dualcore, up to 8GB DDR3).
If those would work with patched XNU, they'd be a real budget friendly alternative to the feeble & expensive Intel Atom platforms...
Anyway working Lion Kernel would be most wanted currently... :
@ImkantusLatest AMD Fusion Mobile & Embedded cores have SSSE3 implementation & I think we will see Desktop CPUs with SSSE3 support end of this year. There are some Mini-ITX boards using AMD Zacate (Brazos) cores - some less then 100€ (like the E350IS-E45 just 88€, 1.6 GHz Dualcore, up to 8GB DDR3). If those would work with patched XNU, they'd…
Hum, time to upgrade then.
A lion kernel would be nice indeed but it would also be nice to have a fully working snow leopard kernel too.
I would like to avoid buying intel the next time i build a new computer but there isn't even power management for AMD yet so I'll stick with my pehom II x4 a bit longer:)
BTW: On InsanelyMac I uploaded Rev2 of the V8 (10.8.0) kernel with some minor fixes for AMD K10 FSB (as latest chameleon fixes that) with the option to double the FSB on those AMD models with -doublefsb boot arg.
Works like a charm Thanx for that !
@andyvandI have one more request. Could somebody please zip and upload the dyld from Lion GM?
Here's the file mate
MD5: 14acaee6a4e4f19b2cb1392bcebfaebb
@ anv
I could compile the kernel on Lion if you want to?!
Just need the source to do that.
Show 169 additional community field notes (#31–#199)
I already did that.
Compiled the source a few days ago.
@andyvandOk no worries then I'll put in an extra script in case the voodoobuild.sh does everything but the kernel (extra script to build kernel after build halt, do after building dyld + patching dyld + rebasing dyld + injections in xnu when it's patched). We'll get there soon... and it'll work great... :
promising work
thanks for your efforts
@andyvandOk no worries then I'll put in an extra script in case the voodoobuild.sh does everything but the kernel (extra script to build kernel after build halt, do after building dyld + patching dyld + rebasing dyld + injections in xnu when it's patched). We'll get there soon... and it'll work great... :
What about libunwind and the custom dyld, will be fixed the issues with that?
Thanks for the kernel
Ok that´s really fine.
Just tell me if you have finished it.
@andyvandI modified the script for building the Lion dyld + kernel. It's currently building on my netbook (@ work). I'll upload it when the build finishes. It'll be uploaded @ insanelymac in my current legacy kernel thread (I'll post the link here). I've also made a compile_kernel.sh script to start the build in an allready patched + injected…
One more question, the kernel is for 10.7.0 or 10.7.1?
Thanks for the kernel! I'm anxious to try it
:)
hmm... ok i m preparing Xmove and install partition lets pray to god this kernel works
even if it doesnt, still thank you for the hard work..
For 10.6.8, has anyone test this kernel with sse2 only cpu? does it still beachball?
for Lion, does anyone know how one can emulate ssse3 ?
Did you activate the sse3 emulator for 10.6.8?
There is no ssse3 emulator until now but the lion kernel is also not available now.
But today the lion kernel is gona to release.
it doesnt seem that it wants to boot on the SL Build but still investigating !
both Builds aint Booting so far don't even get to verbose mode same as in SL with native 64 bit
Ok... Compiled the kernel.
But it created 2 mach_kernel.
One in the root from voodoo build folder and one in the source in /build/sym.
The one in the root has 15,4 mb and the one in the source has 18.7 mb.
Which one is the right one?
Ok…
Then it´s the one with 15.4 mb.
I also edited the voodoobuild file.
Akimoa tested it on his amd but it doesn´t work --> instant reboot.
Could the be the same problem like on snow in pure 64 mode?
this 11.0 kernel do like 10.8 kernel on lion just reboot without entering verbose mode
I uploaded the compiled kernel, so that everyone can try it.
It´s compiled with xcode 4.1.
Here the link for it: rapid share.com/files/2989752953/mach_kernel.zip
i think that the problem may be from thing anther kernel as 10.8 & 11.0 have the same result
will make some tests and return
I think it´s over for amd with lion if nobody can create a 32 bit kernel.
It was also not possible to run amd in 64 kernel mode in snow leopard.
It won't even load in full 64bit on AMD in lion, I just tried and got a reboot. But it loads on my 64bit Pentium 4 in 32bit mode but then kps(Lack of ssse3 maybe?). @ wastez it is possible to run full 64bit mode in Snow Leopard, but no 32bit apps work. proof: public.bay.livefi lestore.com/y1pbpsLLD6e10NLAqQJhsrTCIkpmT8DUhONm73CKdHg9ZIH-uLkvidvuYeZMVQmOMUY_e9aPQ6koa9kRtXhMH6n2w/AMD64bit10.6pbl.png
@wastezI think it´s over for amd with lion if nobody can create a 32 bit kernel. It was also not possible to run amd in 64 kernel mode in snow leopard.
The Kernel you compiled should be multiple architecture.
file ./mach_kernel
should look like this:
./mach_kernel: Mach-O universal binary with 2 architectures
./mach_kernel (for architecture x86_64): Mach-O 64-bit executable x86_64
./mach_kernel (for architecture i386): Mach-O executable i386
So there is still a 32-Bit Kernel on Lion. Just the "-legacy" mode is no longer supported. So we need to boot the -force64 way on Lion...
@ImkantusThe Kernel you compiled should be multiple architecture. file ./mach_kernel should look like this: ./mach_kernel: Mach-O universal binary with 2 architectures ./mach_kernel (for architecture x86_64): Mach-O 64-bit executable x86_64 ./mach_kernel (for architecture i386): Mach-O executable i386 So there is still a 32-Bit Kernel on Lion.…
Ok that what i was just wondering myself but it seems in the voodooscript the 32bit part didnt got adressed at all or am i missing something
and it doesn't boot in userland 64 either with or without custom dyld
How about a bootloader that patches the kernel to allow non-supported Intel and AMD support for lion. Kind of like the Intel atom patch but for more cpus?
Keep patient guys - we had to wait till 10.5.4 for the Voodoo XNU to be released - we had to wait until 10.6.5 till Andy had figured a fully working Kernel patch for Snow Leopard. :
Btw: Mac OS X 10.7.1 source code has been released today.
@akimoait seems in the voodooscript the 32bit part didnt got adressed
Well I do not see, what should be the problem with the build script...
Anyway has someone yet tried to patch using "patch -p0 -i legacy_kernel-1699.22.73-v1.diff" and compile the Kernel using make? Just wondering...
@andyvandtry -force64 (patches come from Snow Leopard so...)
It is still instant reboot after Chameleon says "Staring Darwin x86"
I have also tried stripping the Kernel with lipo in order to be ensure booting i386 Kernel...
what i just did too recompiled it only i386 …
same as above
used valv branch (not support lion)
using 10.8 kernel and platform kexrs it enter verbose and stuck at kexts not loaded
using 11.0 kernel restart
using latest trunk bootloader (support lion )
using 10.8 kernel and platform kexts restart
using 11.0 kernel restart
@ImkantusAnyway has someone yet tried to patch using "patch -p0 -i legacy_kernel-1699.22.73-v1.diff" and compile the Kernel using make? Just wondering...
Yes
Same Result !
This time it´s gona to be funny for amd´s.
Last time there was time to get a solution until get 64 bit Userland working.
Now it won´t work without it.
@$The-King$
The problem isn´t the boot loader for sure.
@anv
Did you change something on the 32 Bit Kernel this time, or did you just edit the 64 bit kernel?
the filesize difference between the 2 released xnu sources (10.7 and 10.7.1)
is huge
just tried the diff (without custom dyld and sse3emu etc.) on the latest source -> same result sadly
any way to debug this ?
k and if it Boots there what would u need in logs to dig in
kernel.log ? or any other one ?
It didn't reboot on my 64bit Pentium 4 HT, but it crashed later in the boot. I can take a picture of the kp.
On a vanilla compatible cpu the kernel is working.
32 Bit + 64 Bit.
dl.drop box.com/u/38348368/100_1824i386.JPG kp in 32bit mode
dl.drop box.com/u/38348368/100_1827x86_64.JPG in 64bit mode
This is with andy's kernel complied in Snow Leopard.
The one complied in Lion just gives me a black screen.
well we have someone that tests for us ... where would he see if the routines go thru ?
Is there another site I could upload them to that isn't blocked, since my images are too large to upload on the forums.
Well how about I post them on my own website, cefso.doesn texist.org/temp/100_1824i386.JPG
cefso.doesn texist.org/temp/100_1827x86_64.JPG
it booted all the way thru and apps worked with the vanilla machine
when testing patching routine
well the apps would not have worked if not rite ?... he did boot verbosly but not recognizable he will hopefully test again and will get a dmesg out if that helps
It doesnt seem to me that this will help ya but here it is with 48
so would a bootloader debug clue u in on that possibility ?:-d
Shit, instant reboot, but I will try with blank HDD and chameleon usb.
he used r1460 on vanilla
and i tried on amd 1095 and 1457 …wastez tried cparm boot also on amd
What bootloader should we be using
I'm interested in helping test your kernel. I have three partitions.
Chameleon bootloader
part0 10.6.8 (my fulltime workstation)
part1 10.6.5 (repair)
part2 10.7.0 GM installed from macpro using ccc
Snow Leopard is running on an AM2+ Phenom x4 9650 2.3 ghz. DAO78l Acer Mainboard with nforce 780a chipset. This is a cheap setup and I believe an excellent candidate for testing the kernel with 4gb of ram. Lion of course does not boot (just blackscreen reboot after chameleon bootloader.) I'm running two other systems with same specs without the Lion partition, snow leopard runs on all three very well. One running osx server.
Should I install the Boot beta or will Chameleon work with your new kernel?
In the moment the kernel is not working until now.
You can download a few pages before but as i said it is not working.
I posted it on Page 7, it is compiled with xcode 4.1 but if you want to you can download the source on insanelymac and compile it by yourself.
I tried running in a modded bootcd but it restarts after the message
Starting Darwin x86
Seems like can't boot on i386, even with arch=i386 -force64, extracting i386 part also doesn't work
Garageband crashes on my AMD x2 cpu, any suggestions?
Here is part of the crash log:
Process: GarageBand [950]
Path: /Applications/GarageBand.app/Contents/MacOS/GarageBand
Identifier: com.apple.garageband
Version: 6.0.4 (427.84)
Build Info: GarageBand_App-4278400~1
Code Type: X86 (Native)
Parent Process: launchd [102]
Date/Time: 2011-08-26 21:34:08.338 -0400
OS Version: Mac OS X 10.6.8 (10K549)
Report Version: 6
Interval Since Last Report: 458742 sec
Crashes Since Last Report: 51
Per-App Interval Since Last Report: 72 sec
Per-App Crashes Since Last Report: 6
Anonymous UUID: 21CC8BE4-B7A4-44C8-8A4A-57425D706890
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
@jblparisiGarageband crashes on my AMD x2 cpu, any suggestions? Here is part of the crash log: Process: GarageBand [950] Path: /Applications/GarageBand.app/Contents/MacOS/GarageBand Identifier: com.apple.garageband Version: 6.0.4 (427.84) Build Info: GarageBand_App-4278400~1 Code Type: X86 (Native) Parent Process: launchd [102] Date/Time:…
Add std_dyld=Yes to your boot flags
@davisin666Add std_dyld=Yes to your boot flags
I thought the whole point of the custom dyld kernel was to avoid that? Or am i missing something, lol
@andyvandI found the routines that do code signature checks on the pages + through dyld syscall. I modified the code slightly so it will verify all code signature kernel checks as valid. This means we can use stock dyld too... I also noticed the panic. It panics on map_text_segment_sys (that's where the trap gets called). I modified the code…
Just give me a Shout when u Updated it will recompile it on lion :-d
I've been following this thread with great interest. I currently run SL quite happily on a Pentium D system. I'm really excited about the possibility of getting Lion to go on my old system. I have tried to install Lion from a USB key. With the real Lion kernel I just get a black screen after the kexts have loaded. With the kernel compiled by Wastez (in Post #65, length 15,400,176) I get the same black screen after loading kexts. With AnV's kernel (posted on I.M. length 19,678,036) the boot does go further but I get the same KP as reported by scififan68 in Post #92. I'm using Chameleon v2.0-RC5 r1083 on the USB key. One other note: when I try AnV's atom kernel (mach_kernel_dp4_atom_apic) the boot proceeds past the kext loading, but stops/hangs after the "BSD root:" line instead of KPing.
We're all rooting for you AnV! Thanks for your efforts.
for Roseman
Because I am experimenting too, I was curious if you have booted in -s single user mode, or -x safe mode with the ANV mach_kernel_dp4_atom_apic kernel? Have you gotten any further in the boot process? In the past I have disabled just about everything with regards to kexts and startup items and found I wasn't having a kernel problem but other system files weren't playing well with each other. I was able to use older files to at least get booted in safe mode. Just wondering about your troubleshooting efforts so I don't duplicate over here. -thx
Can someone split or rename this thread to "Lion on AMD"?
The only other thing I had tried was to remove AppleIntelCPUPowerManagement.kext from S/L/E and it made no visible difference. Just now I tried -s & -x in various combinations on the different kernels and found no changes in behavior. One funny little thing I did notice, though, is that when trying the atom kernel, after it stops/hangs following the "BSR root:" line there is still some process running that echos what I type on my (PS/2) keyboard to the screen.
@acermac3Because I am experimenting too, I was curious if you have booted in -s single user mode, or -x safe mode with the ANV mach_kernel_dp4_atom_apic kernel? Have you gotten any further in the boot process? In the past I have disabled just about everything with regards to kexts and startup items and found I wasn't having a kernel problem…
shot in the dark
I have not experienced this result. I don't know if this has any significance, but did you try to issue any commands while it was in the hang state?
ls
cd ..
while it echoed your keyboard output?
acermac3: You seem to have PM's disabled, my reply to your PM is below:
I'm not sure what/when you mean "before the kexts loaded". I get the keyboard echoed to the screen after Chameleon says it has loaded a particular kernel, then the names of lots of kexts scroll by, then the system changes (text mode) resolution and starts to initialize various things. I think I see the Firewire get setup, and the keyboard, and near the end of what is shown is a listing of my usb key as the boot device, then there is a line that says"BSD root: disk…" (I'm not at my test system right now, so I'm just going from memory). Then the system just sits there. If I type stuff it appears on screen, but I get no response or prompts. I don't see the disks run or anything. I did try entering some commands, but didn't see anything happen. Whatever is echoing the keystrokes though it does take my pressing 'Enter' as both a Carriage Return and a New Line. That is, if I type something and then hit enter, the next things I type will appear at the begining of the next line on the screen. When I get a chance tonight I will compare this behavior to what I get if I boot my SL installer into Single User mode (-s). Also, tonight I will let you know what is in my /extra directory.
I tried both atom and non-atom kernel (on first post) on sse2 only cpu, but I get panic "invalid kernel ip"
Uploaded with ImageShack.us
while at a sse3 supported cpu, it boots fine
both laptops is USB booting, so I didn't change anything expect the kernel
Problem with dyld patcher where Outlook 2011 and Quicken Essentials both will not open. I tried to manually patch both with the amd instruction patch tool, but no luck. Then I tried going back to the 10.6.8 legacy kernel from nawcom, which doesn't have the corrected AMD FSB detection, and sure enough, it worked perfectly. Any ideas on how this can be fixed? I had to manually put FSB=200000000 like back in the 10.6.2 days when I added my FSB patcher to the old kernel. I haven't yet found the source to the nawcom kernel in order to try reversing my patch now that Chameleon has it.
blackknight with anvs kernel u used the bootflag std_dyld=yes ?
wich disables the integrated dyld and uses the standard one (i guess patching the bins doesnt help when they dont get detected cause they switched off
also with anvs kernel u can use doublefsb=Yes to set your fsb rite when its messed up
@akimoablackknight with anvs kernel u used the bootflag std_dyld=yes ? wich disables the integrated dyld and uses the standard one (i guess patching the bins doesnt help when they dont get detected cause they switched off also with anvs kernel u can use doublefsb=Yes to set your fsb rite when its messed up
Thanks for the bootflag for std_dyld, I couldn't remember what it was. Also, the FSB is correct with AnV's kernel, it's nawcom's that doesn't get it right, though it does apparently use the std_dyld.
Yap after meklort fixed the workaround in Chameleon its there double time once with the kernel and with the bootloader and then things get messed up like sound and stuff by the the time that was done nawcom was off due to illness and didnt fix it in his latest legacy version
btw did u see netkas got the 6970 working last nite ;P
Your welcome:-d
That was just what I needed. It works great and now that I can use AnV's kernel without hardcoding the FSB, sound doesn't skip anymore.
Yeah, I did see that netkas got 6970 working. I have a 6950 unlocked to 6970 that I'd love to get working, but I can't yet run Lion since I'm on AMD. I guess once we get a working kernel, I'll get a chance to try it.
What do you with all the files you downloaded? First post link leads to 37MB file and I see boot files and whole bunch of other stuffs. I guess it's the source for dyld.
Do I just replace the kernel only with the one i downloaded?
Can someone lead me to the right direction on what to do with this?
a needle in a haystack looks more sexy
wondering if these compare programms would help us in searching by comparing the 2 files next to each other and find our needle … just wondering
10.7 Kernel for AMD
AnV heard that you were on the LION kernel for AMD...was just wondering if you were still on it, cause didn't hear you for a while?!
but u did read the topic before u posted did ya ? because that would have made things a little clearer and the question would have answered all itself
@ AnV
Is there a possibility to run the Lion GM with the 32 bit kernel of the DP Version?
And if it work would it be possible to create an modified version?
Did not think on it that there is no source from dp.
I´m also starring at the kernel txt file since yesterday and it´s gona to drive me crazy.
@andyvandLooooots of work on getting it done... haven't isolated the problem yet...
Thank you a lot guys and keep it up, I know there's lots of hard work ahead before getting it done...:).
Also, looks like nawcom too is on it, but didn't really heard lots of him since he came back.
May be you guys can rock together and get it done...:)
@akimoabut u did read the topic before u posted did ya ? because that would have made things a little clearer and the question would have answered all itself
I know that this question should have been asked in the 10.7 forum, its just on a hurry that I forgot.
I'm curious if with the new AMD fusion processors supporting SSSE3 instructions if they will support full 64-bit mode on Lion and SL. I'm looking to get one of the new AMD FX processors when they release and they effectively support all of the intel instructions. What do you think Andy?
bah new processor s
id like to see the old ones working 1st
Well, the new processors support all the intel instructions, whereas the old ones need emulators. Emulators that need to be written. I'm hoping that these new processors won't require much work.
10.7.2 Sources are out FYI
i compiled it with only patching it with the old diff from 10.7 no changes made to it patching went tru fine so i thought i compile it with xcode 4.1 maybe someone is eager to test it i havent yet
its compiled only in 32 bit
well here it is
10.7.2
cl .ly/0F0A3n3o0j2K3p3N0u02
@akimoa10.7.2 Sources are out FYI i compiled it with only patching it with the old diff from 10.7 no changes made to it patching went tru fine so i thought i compile it with xcode 4.1 maybe someone is eager to test it i havent yet its compiled only in 32 bit well here it is 10.7.2 cl .ly/0F0A3n3o0j2K3p3N0u02
it gave the similar KP on my AMD PII-X4 965
@m28ewit gave the similar KP on my AMD PII-X4 965
map_text_segment_sys, maybe there is something wrong with the decryption algorithm or Apple encrypted more binaries.
Remembers me from Snow Leopard
Decryption hasn't succeeded yet (probably will retry)
patch_exec_obj_segment failed
map_segment failed
Damn, I want Lion
sounds promising atleast a bit
just post the diff ready to compile :-d whenever u are
this major update from apple with iCloud service, it seems Lion is essential…
Can't wait for the AMD kernel.
don't want to buy Intel system just for that.
I could boot Snow Leopard with arch=x86_64 (V2 10.6.8 kernel), but all apps were crashing after the desktop appeared.
Bootargs in org.chameleon.Boot.plist: arch=i386 -force64 std_dyld=Yes npci=0x2000
Setting -v arch=x86_64 at chameleon boot prompt worked, as appeared in the boot log, Kernel is LP64
Process: Finder [2974]
Path: /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder
Identifier: Finder
Version: ??? (???)
Code Type: X86 (Native)
Parent Process: launchd [125]
Date/Time: 2011-10-19 16:11:25.199 -0300
OS Version: Mac OS X 10.6.8 (10K549)
Report Version: 6
Exception Type: EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes: 0x0000000000000001, 0x0000000000000000
Crashed Thread: 0
Thread 0 Crashed:
0 dyld 0x8fe2b7bf _sysenter_trap + 3
1 dyld 0x8fe2d5ea mach_init + 47
2 dyld 0x8fe01766 dyldbootstrap::start(macho_header const*, int, char const**, long) + 448
3 dyld 0x8fe01057 _dyld_start + 39
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0xffffffe4 ebx: 0x8fe2d4ac ecx: 0xbffffa4c edx: 0x8fe2dcf2
edi: 0x00000000 esi: 0x00000000 ebp: 0xbffffa98 esp: 0xbffffa4c
ss: 0x00000023 efl: 0x00010286 eip: 0x8fe2b7bf cs: 0x0000001b
ds: 0x00000023 es: 0x00000023 fs: 0x00000000 gs: 0x00000000
cr2: 0x8fe2b7bc
Binary Images:
0x8fe00000 - 0x8fe4163b dyld 132.1 (???) <4CDE4F04-0DD6-224E-ACE5-3C06E169A801> /usr/lib/dyld
My finder is 32 bit only
Slowpoke
@andyvandThis weekend I can put some time aside for making a new Lion kernel... Keep you posted.
<B
i hope you do it
@andyvandThis weekend I can put some time aside for making a new Lion kernel... Keep you posted.
<B
Dale compadre, que la fuerza te acompañe
Buena suerte!
Andy, I booted with arch=x86_64 with your latest legacy_kernel for Snow Leopard (With x64 Finder).
I can't run any 32 bit / Rosetta app, only in force64 mode I can run 32 bit apps.
My libSystem.b is patched too.
The dmesg from my pc is in the attached file.
The problem is that there is no solution to run 32 bit apps on an amd with the 64 bit kernel.
It´s just possible to run 32 bit kernel in 64 bit userland.
Sorry dude.
Here something different:
I would have a look on these kexts, because there appears a error on your machine during the startup:
Kext com.PaztalomTechnologiez.nVmon - library kext com.apple.NVDAResman not found.
Can't load kext com.PaztalomTechnologiez.nVmon - failed to resolve library dependencies.
Kext com.PaztalomTechnologiez.nVmon failed to load (0xdc00800e).
Failed to load kext com.PaztalomTechnologiez.nVmon (error 0xdc00800e).
Hows it going on the project guess alot people have that question in mind thats why im asking it ?!
@wastezThe problem is that there is no solution to run 32 bit apps on an amd with the 64 bit kernel. It´s just possible to run 32 bit kernel in 64 bit userland. Sorry dude. Here something different: I would have a look on these kexts, because there appears a error on your machine during the startup: Kext com.PaztalomTechnologiez.nVmon -…
Hahahahahaha, nvmon is from FakeSMC, is for temperature monitoring, since I've bought a Thermaltake DuOrb is really not needed, I'm gonna delete that kext.
@andyvandWorking on it. I studied the kernel some more and saw csops routine. It's a syscall used by dyld which checks code signing (and in dyld code it halts execution if incorrect). Guess there are a few more corpses that need burying lol. This weekend I should have a solution...
Nice to hear that Andy, good luck! Waiting the halloween_kernel hahahahaha
Well i am Curious and eager to get my hands on its almost like a kid in a candystore :-d
Is there something new about the lion kernel?
Hope you´ll get it soon.
@wastezIs there something new about the lion kernel? Hope you´ll get it soon.
ANV ignores us :'(
I am from dutch hackintosh.nl see you my Topic
hacki ntosh.nl/snow-leopard-10-6-x/12327-msi-790fx-gd70-en-amd-phenom-ii-x2-550be.html
Working all good.
Only having problem! All APPS work only Outlook 2011 cannot open
and Premier CS5.5 cannot open.
I having AMD Patcher al ANV and my boot chameloen
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Kernel</key>
<string>mach_kernel</string>
<key>Kernel Flags</key>
<string>-v npci=0x2000</string>
<key>Timeout</key>
<string>5</string>
<key>busratio</key>
<string>16</string>
<key>EthernetBuiltIn</key>
<string>Yes</string>
</dict>
</plist>
@bassie86I am from dutch hackintosh.nl see you my Topic hacki ntosh.nl/snow-leopard-10-6-x/12327-msi-790fx-gd70-en-amd-phenom-ii-x2-550be.html Working all good. Only having problem! All APPS work only Outlook 2011 cannot open and Premier CS5.5 cannot open.
Hmm, I dont think you can run Premiere CS5.5 on amd cpu. I guess Outlook can be fixed, but premiere and latest version of final cut use probably SSE4 instructions for codecs and this might cause them to crash. I had Premiere running, but as soon as i opened a video file it would crash. And now for some reason it crashes right away... You will probably have to run it on Windows -.-
No Legacy_kernel in turn works with Outlook and 4GB Premier CS5.5;-).
Mach_kernel works with 8GB support almost everything except Outlook and Premier CS5.5
This is not strange in outlook and premier cs5.5 can not kernel mach_kernel
where I had MAXMEM = 4086 = 4096 MAXMEM or both can not mach_kernel so wrong outlook remains cs5.5 and Prime! Then I turn to only 4GB Legacy_kernel's great and not 8GB.
Mach_kernel with 8GB work After Effects CS5.5 and Photoshop CS5.5 and Word, Excell, Acces, Publisher working
Only this Outlook en Premiere Pro CS5.5 not work
@andyvandStill working on it but I don't have a lot of time (lots of work@work :-p) I'll post results as soon as I can.
Please let me know if i can help you with searching, comparing code or anything, ive got:
AMD Phenom II X4 955
Gigabyte GA-MA-770T-UD3P
Snow Leopard 10.6.8
I would really appreciate having Lion running on my System
I had always used legacy_kernel 8GB, which can not rotate so all apps do not work with 4GB but the super twist.
I came up against in your topic I have tried as I did order that work be given to 8GB mach_kernel there turn now almost everything works except APPS
Working: (mach_kernel and 8GB)
Firefox
Safari
Itunes
AppStore
After Effect
Photoshop
Illusrator
Word
Excell
Powerpoint
Rush
Zen Bound 2
Plants VS Zombies
Not Working Working: (mach_kernel and 8GB)
Outlook 2011
Premier Pro
Working: (legacy_kernel and 4GB)
Working All
Working: (legacy_kernel and 8GB)
Not working all
I'm using legacy_kernel on msi 790fx-gd70 with 8GB and everything works fine. Try to clean the kernel cache and delete any other kernel like legacy_kernel.old and mach_kernel and reinstall the nawcom's 10.6.8 legacy_kernel it should work.
still testing !
compiled them just waiting for andy to reply if i went the rite way
I will still building 1st
and here they are :
Legacy Kernel 10.7 No Autopatch
cl .ly/0G0R152u09332z0i3E10
Legacy Kernel 10.7 Autopatch
cl .ly/0X0w3s300U002z0W0K3t
theres always both i386 and x86_64 Version of it
i wont be testing them now since its to late but will do 1st thing tomorrow
Have fun
---- yeah! Someone confirm that if is working, so I can install Lion now , thanks Andy for your hard work
Yes Busy ! with it
Instant Reboot on NoPatch i386
Same on Patched i386
will test the others aswell and im also doubting on my system if it is set up proper since it was messed with it alot so
i wont take myself as the best reference
cl .ly/1z3j321i2a0g1i171819
In this download is missing the Autopatch x86_64
Instant Reboot for me too
do we have to use special boot flags on the No Autopatch Kernel, or is it just for dyld patching?
here the missing one sorry hope it makes a diffrence(link corrected to)
cl .ly/0X0w3s300U002z0W0K3t
well on both x86 _64 Chameleon stops rite after i hit enter goes back to command prompt at least here
@andyvandI'm almost done compiling the universal (32+64bit) kernel (using Xcode 3.2.6). Lets hope that at least works...
I'm crossing my fingers :-|
@akimoawell on both x86 _64 Chameleon stops rite after i hit enter goes back to command prompt at least here
Maybe youre using arch=i386 ?
When trying that on the x86_64 Kernels, it goes back to the command promt for me
Otherwise still Instant Reboot
doesnt work tried arch=i386 with/without -force64 and arch=x86_64
maybe I can test vanilla tomorrow.
I've tested those new kernels on my AMD P-II x4 965
with flags: arch=i386 ; arch=i386 -force64
there's no KP,
but I got stuck at the "No interval found for . Using 8000000" line
with flag: arch=x86_64
I got this KP
and wich kernel did u use for that ? bit more specific if u dont mind:-d
@akimoaand wich kernel did u use for that ? bit more specific if u dont mind:-d
I tested all those 5 kernels of yours & Anv's
NoAutopatch & Autopatch @ 32 & 64 bits compiled kernels
and I added them all into the iATKOS L1 disc
@andyvandCan you boot into single user? Then you could get the dmesg to me... I could use it to look up what goes wrong... A new hope... :-d
unfortunately, with: arch=i386 (-force64) -s
I still got stuck at the same line :'(
Pthread support ABORTS when sync kernel primitives misused
No interval found for . Using 8000000
Looks like we need to compare the log with the vanilla dmesg if these messages appears
K did some intence testing with an installed system (cloned from my MBP when it came out in Juli 10.7.0)
only the kexts i used from SL
Disabler ,NULLPower, FakeSMC, rest is via DSDT
Bootloader i tried were cparm boot(latest) and Chameleon Rev1684
with all kernels and with none i came close to see a verbose mode sadly
tried all scheduler arguments as boot args gave me instant reboots too (on all)
all important bootflags were tested aswell offcourse
:'(
Got one match, 10.7.0 Installer Stick
grep -E "No interval found" /Volumes/Mac\ OS\ X\ Base\ System/System/Library/Extensions/*.kext/Contents/MacOS/* /Volumes/Mac\ OS\ X\ Base\ System/System/Library/Extensions/*.kext/*
Binary file /Volumes/Mac OS X Base System/System/Library/Extensions/IOHIDFamily.kext/Contents/MacOS/IOHIDFamily matches
For 32 Bits: the new amd_insn_patcher gives me on both dyld and libSystem.B.dylib:
Code signature removed succesfully (64bit)No patches found, not generating output filePatch report: 0 instructions patched, 208 bad instructions, patches bypassed: NO
It seems like xmove doesn't work very well with amd, gotta mod iatkosx L1, I will have to buy a blank dvd xddd
im starting to think something else in my cloned system is bugging the boot ...investigating
i hadnt entered this forum about 4 days
ad got adream that there are alion kernel done
so i will do testing but can any one compiles 11.2 kernel as i have 10.7.2
any way will begin with 11.0 kernel
will do tests now
@andyvandDid changing the scheduler change anything?
still no luck :'(
@andyvandHow about booting the installed product? This is the install DVD, right?
all testings were done by booting the osx from DVD (BSD Root=disk1s3) & HDD (BSD Root=disk0s2)
and they all stuck at the same line
@andyvandEDIT2: Did you patch /usr/lib/dyld and /usr/lib/libSystem.B.dylib with amd_insn_patcher (the new one for Lion)? It is needed for 32bit support under 64bit...
I haven't patched them yet
could you also share the binary of the amd_insn_patcher ?
@andyvandFixed amd_insn_patcher... :-| It's IOHIDFamily that causes the misery allright... Decompiling + checking... EDIT: Removed check for interval (which causes the failure). The problem in this case is VoodooPS2 in fact but the kext I posted should do fine (little workaround with hex editor ;)) Back up your original before testing...
the new patched IOHIDFamily got rid of the "No Interval found for" error
but now I'm getting stuck after the USBF line
here are the compilied ones for 10.7.2 to test
no patch
cl .ly/191M3B3j3U0M2i2L1D0R
autopatch
cl .ly/2o3z2M1u161N2V3e0p0P
@akimoahere are the compilied ones for 10.7.2 to test no patch cl .ly/191M3B3j3U0M2i2L1D0R autopatch cl .ly/2o3z2M1u161N2V3e0p0P
thanks tried anv kernel just auto restart
tried four kernel no one fo them work just auto restart :'(
@m28ew
Try using patched IOUSB from AnV (SL) might change a thing
and Andy cant we set a debug somewhere ? besides the scheduler aruments ?
@andyvandShould be there under the source... amd_insn_patcher...
thanks Andy
when I patched the dyld, I got these messages:
Patching universal binary (2 architectures)
Patching X86_64 part (processor 16777223, architecture 0)
Code signature removed succesfully (64bit)Patch report (1): 0 instructions patched, 208 bad instructions, patches bypassed: NO
Patching I386 part (processor 7, architecture 1)
Code signature removed succesfully (32bit)Patch report (2): 1 instructions patched, 0 bad instructions, patches bypassed: NO
but when I pacthed the libSystem.B.dylib,
I got the "No patches found, not generating output file" message ?
Patching universal binary (2 architectures)
Patching X86_64 part (processor 16777223, architecture 0)
Code signature removed succesfully (64bit)Patch report (1): 0 instructions patched, 30 bad instructions, patches bypassed: NO
Patching I386 part (processor 7, architecture 1)
Code signature removed succesfully (32bit)Patch report (2): 0 instructions patched, 0 bad instructions, patches bypassed: NO
No patches found, not generating output file
are those reports correct for you ?
btw, is there any difference between the amd_insn_patcher and the amd_insn_patcher_ext ?
@$The-King$tried four kernel no one fo them work just auto restart :'(
Akimoa and me are having the same issue.
Hope someone will fix that.
@anv
Would it be possible to insert a debug mode?
@wastezAkimoa and me are having the same issue. Hope someone will fix that. @anv Would it be possible to insert a debug mode?
downloading fusion and will see if will work or no
i tried kernel on my notebook core i and kernel load
@m28ewthanks Andy when I patched the dyld, I got these messages: Patching universal binary (2 architectures) Patching X86_64 part (processor 16777223, architecture 0) Code signature removed succesfully (64bit)Patch report (1): 0 instructions patched, 208 bad instructions, patches bypassed: NO Patching I386 part (processor 7, architecture 1)…
In the old release the amd_insn_patcher_ext patches up some SSE3 instructions to their SSE2 variants.
I think this release will do the same.
After patching both dyld & libSystem.B.dylib
I got a new KP :'(
For the usb messages, did you disable the usb legacy support (In BIOS, because it seems that in OHCI, usb 1.1, is the problem)?
If doesn't work, maybe using usb kexts from 10.6.8 can do the trick
@davisin666For the usb messages, did you disable the usb legacy support (In BIOS)? If doesn't work, maybe using usb kexts from 10.6.8 can do the trick
After patching both dyld & libSystem.B.dylib
the usb error doesn't appear anymore
but I get a new KP
here are the debug ones
autopatch
cl .ly/28380m2u2f3h0N0a1x1K
no autopatch
cl .ly/3x3V2A2a1V1I2g2n133a
hope we can get anything out of these
So test Guys
@akimoahere are the debug ones autopatch cl .ly/28380m2u2f3h0N0a1x1K no autopatch cl .ly/3x3V2A2a1V1I2g2n133a hope we can get anything out of these So test Guys
still no luck :'(
with your autopatch kernel @ 32-bits
with your no autopatch kernel @ 32-bits
btw, is there any new boot-flag I should use to enable the debug mode ?
EDIT:
and maybe you should split this thread and create a new one: Legacy Kernel 10.7.x / Darwin 11.x.0 ( Still in Progress... )
Just My Two Cents
belong to snow leopard
@ andyvand
since snow cant boot mac on hardware raid
and i got this panic when using force64
and here with out using force64
this annoying me as i must change data mode to a chi every time i enter mac
anther thing can any one help me to learn compiling kernel (tools&steps)
not_interrupts_enabled
It seems like there is a heavy mess with interrupts and threads
@$The-King$belong to snow leopard @ andyvand since snow cant boot mac on hardware raid and i got this panic when using force64 and here with out using force64 this annoying me as i must change data mode to a chi every time i enter mac anther thing can any one help me to learn compiling kernel (tools&steps)
Compiling is no problem.
Just use the command make or in case of anv´s kernel the script which he creates to do this.
@wastezCompiling is no problem. Just use the command make or in case of anv´s kernel the script which he creates to do this.
need i some tools for compiling except xcode ?
need i some tools for compiling except xcode ?
No you need only Xcode and the kernel tools.
But don´t forget to patch the libSystemB_debug.dylib and libSystemB_profile.dylib after installing it.
Sorry.
I forgot to tell you something about the kernel tools you need to do this.
Here is a link for it:
tech edze.com/Thread-compiling-xnu-kernel-on-snow-leopard-10-6-4
@wastezSorry. I forgot to tell you something about the kernel tools you need to do this. Here is a link for it: tech edze.com/Thread-compiling-xnu-kernel-on-snow-leopard-10-6-4
thanks that what i want
nearly i had seen this topic before
this is the compilation log
i see some errors like this
ERROR: OSBoolean.cpp: failed to get mapping for tid 17069
ERROR: ctfconvert: mac_stub.o doesn't have type data to convert
ERROR: ctfconvert: inffast.o doesn't have type data to convert
ERROR: ctfconvert: counters.o doesn't have type data to convert
etc
is this normal ?
also how can i make kernel contain two binary i386 & x86-64 and have no black icon like terminal
Got the Kernel working until the Hang/KP using a Virtual Machine
I might be wrong, but I think the problem is related to the patched dyld.
Because: Using no patcher and the Noautopatch Kernel it hangs after the BSD line.
Using either/both patched dylds and/or Autopatch Kernel it KPs after the BSD line.
Also using the Boot Flag "std_dyld=no" it also KPs, but there is another line "warning: using standard dyld with patcher enabled" after the BSD line, and then it KPs. Thats why i think the dyld kicks in at that point. During boot of my current Snow Leopard system it says that too at that point.
Without patched dyld:
Using Autopatch Kernel:
Using Autopatch Kernel + std_dyld=no
@hans88I'm using legacy_kernel on msi 790fx-gd70 with 8GB and everything works fine. Try to clean the kernel cache and delete any other kernel like legacy_kernel.old and mach_kernel and reinstall the nawcom's 10.6.8 legacy_kernel it should work.
Hello,
having clean the kernel cache and delete old kernel and mach_kernel. Reinstall legacy kernel work for 4GB yes
and
8GB cannot all APPS open or outlook.
and my boot plist is 64bits
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Kernel</key>
<string>legacy_kernel</string>
<key>Kernel Flags</key>
<string>-v arch=i386 -force64 maxmem=4096 npci=0x2000</string>
<key>Timeout</key>
<string>5</string>
<key>busratio</key>
<string>16</string>
<key>SMBIOS</key>
<string>/Extra/smbios.plist</string>
<key>EthernetBuiltIn</key>
<string>Yes</string>
</dict>
</plist>
patch your dyld with the amd_insn_patcher like explained so many times here in the forums and outlook will work or again listen to stupid advises from the above and keep on failing ! enough said !
or use the prepatched dyld files here
Extract the underneath folder on desktop
cl .ly/2V3K170A391v0H3x2A1U
via
Terminal
be shure u hit enter after each line dont copy & paste all)
cd Desktop/dyld
sudo -s
# Password
chown root:wheel *
mv * /usr/lib
restart and run this in terminal again
sudo update_dyld_shared_cache
from now on 8 gig will work fine and outlook and rest of your apps wont crash anymore
I have done nothing helped!.
Well that I mach_kernel with amd patcher! legacy_kernel and I have not amd patcher.
So I did mach_kernel with amdpatcher works with 8GB does everything as well
Plants vs aliens, apshalt 6, photoshop cs5 work except Outlook.
legacy_kernel not amd patcher with 8GB
work all not
legacy_kernel not amd patcher 4GB
everything works and outlook
@bassie86I have done nothing helped!. Well that I mach_kernel with amd patcher! legacy_kernel and I have not amd patcher. So I did mach_kernel with amdpatcher works with 8GB does everything as well Plants vs aliens, apshalt 6, photoshop cs5 work except Outlook. legacy_kernel not amd patcher with 8GB work all not legacy_kernel not amd patcher…
Add std_dyld=Yes to your bootflags
Clik here for Fullscreen (thebassie.dyn dns.org/worknowall.png)
Now working on Legacy Kernel 10.6.8 not mach_kernel
Outlook, Photoshop working yes:)
only now problem
Duken nukem waiting intro logo not start
Adobe Premier Pro CS5.5 see you error message
And thanks now can i 8GB work for patch amd thanks
and i having found download where there gzip amd patch and mach_kernel my stupid now not more mac_kernel only amd patch for my legacy_kernel.
@bassie86Clik here for Fullscreen (thebassie.dyn dns.org/worknowall.png) Now working on Legacy Kernel 10.6.8 not mach_kernel Outlook, Photoshop working yes:) only now problem Duken nukem waiting intro logo not start Adobe Premier Pro CS5.5 see you error message And thanks now can i 8GB work for patch amd thanks and i having found download…
Premier CS5.5 won't work in AMD legacy_kernel because it needs SSSE3, and AMD doesn't implement that instruction set on their pre-bulldozer cpus, so you have to run Premiere in your Core 2 Duo system with the vanilla kernel.
I haven't tried Duke Nukem Forever because I think that performance is gonna be very crappy in OS X, so I play PC games in Windows
Premier CS5.5 won't work in AMD legacy_kernel because it needs SSSE3, and AMD doesn't implement that instruction set on their pre-bulldozer cpus, so you have to run Premiere in your Core 2 Duo system with the vanilla kernel.
I haven't tried Duke Nukem Forever because I think that performance is gonna be very crappy in OS X, so I play PC games in Windows
CPUZ say:
Processor 1 ID = 0
Number of cores 4 (max 4)
Number of threads 4 (max 4)
Name AMD Phenom II X4
Codename Deneb
Specification AMD Phenom(tm) II X4 B50 Processor
Package Socket AM3 (938)
CPUID F.4.2
Extended CPUID 10.4
Brand ID 29
Core Stepping RB-C2
Technology 45 nm
TDP Limit 158 Watts
Core Speed 800.0 MHz
Multiplier x FSB 4.0 x 200.0 MHz
HT Link speed 2000.1 MHz
Instructions sets MMX (+), 3DNow! (+), SSE, SSE2, SSE3, SSE4A, x86-64, AMD-V
L1 Data cache 4 x 64 KBytes, 2-way set associative, 64-byte line size
L1 Instruction cache 4 x 64 KBytes, 2-way set associative, 64-byte line size
L2 cache 4 x 512 KBytes, 16-way set associative, 64-byte line size
L3 cache 6 MBytes, 48-way set associative, 64-byte line size
FID/VID Control yes
Min FID 4.0x
P-State FID 0xF - VID 0x10 - IDD 33 (15.50x - 1.350 V)
P-State FID 0x8 - VID 0x18 - IDD 25 (12.00x - 1.250 V)
P-State FID 0x3 - VID 0x20 - IDD 21 (9.50x - 1.150 V)
P-State FID 0x100 - VID 0x2C - IDD 16 (4.00x - 1.000 V)
Package Type 0x1
Model 50
String 1 0x7
String 2 0x6
Page 0x0
CmpCap 4
ApicIdCoreSize 4
TDC Limit 132 Amps
Attached device PCI device at bus 0, device 24, function 0
Attached device PCI device at bus 0, device 24, function 1
Attached device PCI device at bus 0, device 24, function 2
Attached device PCI device at bus 0, device 24, function 3
Attached device PCI device at bus 0, device 24, function 4
@bassie86Premier CS5.5 won't work in AMD legacy_kernel because it needs SSSE3, and AMD doesn't implement that instruction set on their pre-bulldozer cpus, so you have to run Premiere in your Core 2 Duo system with the vanilla kernel. I haven't tried Duke Nukem Forever because I think that performance is gonna be very crappy in OS X, so I play…
CPUZ say:
Processor 1 ID = 0
Number of cores 4 (max 4)
Number of threads 4 (max 4)
Name AMD Phenom II X4
Codename Deneb
Specification AMD Phenom(tm) II X4 B50 Processor
Package Socket AM3 (938)
CPUID F.4.2
Extended CPUID 10.4
Brand ID 29
Core Stepping RB-C2
Technology 45 nm
TDP Limit 158 Watts
Core Speed 800.0 MHz
Multiplier x FSB 4.0 x 200.0 MHz
HT Link speed 2000.1 MHz
Instructions sets MMX (+), 3DNow! (+), SSE, SSE2, SSE3, SSE4A, x86-64, AMD-V
L1 Data cache 4 x 64 KBytes, 2-way set associative, 64-byte line size
L1 Instruction cache 4 x 64 KBytes, 2-way set associative, 64-byte line size
L2 cache 4 x 512 KBytes, 16-way set associative, 64-byte line size
L3 cache 6 MBytes, 48-way set associative, 64-byte line size
FID/VID Control yes
Min FID 4.0x
P-State FID 0xF - VID 0x10 - IDD 33 (15.50x - 1.350 V)
P-State FID 0x8 - VID 0x18 - IDD 25 (12.00x - 1.250 V)
P-State FID 0x3 - VID 0x20 - IDD 21 (9.50x - 1.150 V)
P-State FID 0x100 - VID 0x2C - IDD 16 (4.00x - 1.000 V)
Package Type 0x1
Model 50
String 1 0x7
String 2 0x6
Page 0x0
CmpCap 4
ApicIdCoreSize 4
TDC Limit 132 Amps
Attached device PCI device at bus 0, device 24, function 0
Attached device PCI device at bus 0, device 24, function 1
Attached device PCI device at bus 0, device 24, function 2
Attached device PCI device at bus 0, device 24, function 3
Attached device PCI device at bus 0, device 24, function 4
SSE3 (Streaming SIMD Extensions 3), not to be confused with SSSE3 (Supplemental Streaming SIMD Extension 3)
Did you get it? Your processor doesn't have SSSE3 and Premiere requires SSSE3, see the Premiere error log in the console app.
You will need to find a 32 bit only NLE video editor, since Premiere CS5 and Final Cut Pro X doesn' t work with AMD due the lack of SSSE3 in the AMD cpus.
Final Cut Studio 3 works awesome with no crashes, and there is Premiere/AVID for Windows too
Okay understand.
But it is not funny Prime apps! Oh I have final cut pro that I am going
Try! but my question after that amd patcher will work with 8GB premier pro cs5.5 no more! but 4GB works premier pro cs5.5 how is that not dealing with SSSE3 either haha I do not now why does Prime 4GB Pro CS5.5 is nice.
Because I like everything to work 100 percent with AMD, I hit and kick Intel is fine by me: D
@davisin666CPUZ say: Processor 1 ID = 0 Number of cores 4 (max 4) Number of threads 4 (max 4) Name AMD Phenom II X4 Codename Deneb Specification AMD Phenom(tm) II X4 B50 Processor Package Socket AM3 (938) CPUID F.4.2 Extended CPUID 10.4 Brand ID 29 Core Stepping RB-C2 Technology 45 nm TDP Limit 158 Watts Core Speed 800.0 MHz Multiplier x FSB 4.0…
@bassie86Okay understand. But it is not funny Prime apps! Oh I have final cut pro that I am going Try! but my question after that amd patcher will work with 8GB premier pro cs5.5 no more! but 4GB works premier pro cs5.5 how is that not dealing with SSSE3 either haha I do not now why does Prime 4GB Pro CS5.5 is nice. Because I like everything…
Hmmmmmmmmmm... amd_insn_patcher won't add SSSE3 replacements, is intended to patch sysenter traps and some other stuff.
I get a SIGILL when I open Premiere CS5 on my amd hackintosh, and in the log file it says that is because AMD doesn't have SSSE3 instructions.
If apps doesn't work with 8 GB, stick in your ass some 4 GB, easy solution ^_^
I having problem
to boot start on mac 10.6.8 and say
Data/Stack emulation not permitted: launchpid 6993 at virtual adress ready only…
what is that problem?
i having new install 10.6.0 and update combo 10.6.8 and legacy kernel 10.6.8 than AMD Patcher and self this problem amd patcher not working
Data/Stack emulation not permitted: launchpid 6993 at virtual adress ready only…
First working good! later not more working
i hope who know what is this
Data/Stack emulation not permitted: launchpid 6993 at virtual adress ready only…
DYLD patcher not more working to my PC
Only 4GB work prettig legacy_kernel no DYLD patcher.
http://www.youtube.com/watch?v=1NqTGjvygzw ↗
YEs working CSS Source, Duke Nukem Forever.
I'm using phenom2 x4 where final cut pro x was not supposed to work, because of the SSSE3 instructions! I don't have a clue, but i got it working, without patching anything! I mean I could even load a movie in it! I messed up with some other things, after re-installation of OS X, its not working anymore. I'm using legacy kernel 10.8 with MSI mobo and phenom 2 x4 965. That means there should be a way out, if it did work once! I leave this to you tech gurus, just wanted to let you know that it did run on an AMD cpu, so...may be you can find out!
Also used it and it worked but after 15-60 mins it will be closed.
It will not work completly on a amd.
The best thing would be if somebody write a emulator for it.
Wat do u mean by emulator, like a patcher? I rather think that its the same case like Quick Time and Safari, it should have been able to run as 32 bit app. If somebody could enable it to run as 32 bit, but I don't think so, as the program itself has written been for only 64-bit, if I'm right! Working with sounds and picture's only is OK, but when concerning to work with videos, then it crashes. I think that its because of the preview thing which cant be run in 64-bit because of the SSSE3 instructions, like for the same case as Quick Time which cant be "previewed" in 64-bit!
Final Cut Pro X will open but when I try to add effects and generators, it will SIGILL
Looks like it's getting ill! loll...There should be a way to get it working!
@hans88Looks like it's getting ill! loll...There should be a way to get it working!
SIGILL means Illegal Instruction, AKA, FCPX called a SSSE3 which doesn't exist on your AMD cpu.
Final Cut Pro X is 64 bit only, the solution could be a SSSE3 emulator (Which doesn't exist yet)
BTW, Final Cut Pro X sucks badly, use Final Cut Pro 7 or Avid
Any progress with the new legacy kernel for the lion ?
Any progress with the new legacy kernel for the lion ?
Doesn´t look good that we will get one.
AnV doesn´t know how to get it working. (A reason is that he have no amd to test it)
So there is just nawcom else which can do it.
So it doesn´t look good for amd and lion
@wastezDoesn´t look good that we will get one. AnV doesn´t know how to get it working. (A reason is that he have no amd to test it) So there is just nawcom else which can do it. So it doesn´t look good for amd and lion
From Nawcom's site:
I'm still alive. I'll have this back up once I find time to work on osx86 stuff. Until then, it will remain inactive. -- nawcom
@andyvandRight now I have a real Mac and I tested my Lion kernel. The good and bad news is that it actually works. I haven't yet been able to find why the Lion kernel doesn't work on AMD.
But wait, isn't this your full time job? Get to work!
I having problem
to boot start on mac 10.6.8 and say
Data/Stack emulation not permitted: launchpid 6993 at virtual adress ready only…
what is that problem?
i having new install 10.6.0 and update combo 10.6.8 and legacy kernel 10.6.8 than AMD Patcher and self this problem amd patcher not working
Data/Stack emulation not permitted: launchpid 6993 at virtual adress ready only…
First working good! later not more working
i hope who know what is this
Data/Stack emulation not permitted: launchpid 6993 at virtual adress ready only…
Bad news on the bulldozer front as well. If I try the standard Lion kernel, the machine just reboots as is expected, but it also happens with all the AMD Lion Kernels in this thread.
Power on machine, select OSX and instant reboot. Actually not true, I see about 2/3rds of the gray boot screen with apple logo then it reboots
My machine specs are Asus Crosshair IV Formula, FX-8120, ATI HD5970 & 4Gb ram. Snow Leopard works OK but Lion is a big no go.
@andyvand
please can you compile 10.8 kernel with out doublication of FSB
there are patch on your diff multiple FSB from chamelon by 2
i cant compile kernel i have problems when applying diff and compling
this is kernel log
Dec 24 11:25:13 localhost kernel[0]: rtclock_init: Taking bus ratio path 3 (AMD Phenom)
Dec 24 11:25:13 localhost kernel[0]: rtclock_init: Phenom MSR 0xc0010071 returned: 0x80000048002010
Dec 24 11:25:13 localhost kernel[0]: TSC: Verification of clock speed PASSED.
Dec 24 11:25:13 localhost kernel[0]: TSC: Frequency = 3210.783729MHz, FSB frequency = 401.347966MHz, bus ratio = 8
andyvand
if you have time can you please fix FSB to 200 as it cause to me problems on sound lagy sound
dont forget me
@$The-King$andyvand if you have time can you please fix FSB to 200 as it cause to me problems on sound lagy sound dont forget me
Damn, that could be the reason my sound was freaking me out. And i thougt it was because of wrong kexts -.-
@andyvandI'll do it soon, I don't have my hackintosh with me as I work on my real MacBook Pro right now. I won't forget you.
thanks very much
and my congratulations to you for your new macbook
@anv
Could it be that the problem are the not available SSSE3 instructions with Lion Legacy Kernel for AMD?
Because i read something that they will be needed on Lion.
And if so would it be possible to write an emulator for it?
I written and compiled xnu 10.7.3 only 32 bit and work on my amd x2 250 LION !
It is picture !
i found that here
and i just may have to cry for joy
osx 86.co/archive/index.php/t-7106.html
media fire.com/?ontvl5nznf58n9h from bronzovka
AMD kernel is here have not tried it yet but let me know?
I have a problem with your kernel and my amd x2 turion : Mac-mini-de-Francesco-Diaz:~ sorafune92$ sysctl -a |grep machdep.cpu.family
machdep.cpu.family: 16
Mac-mini-de-Francesco-Diaz:~ sorafune92$ sysctl -a |grep machdep.cpu.model
machdep.cpu.model: 6
I can't boot with 2 cores, only run one..., when I boot with cpus=2 it stopped on IOAPIC ...
@wastez@anv Could it be that the problem are the not available SSSE3 instructions with Lion Legacy Kernel for AMD? Because i read something that they will be needed on Lion. And if so would it be possible to write an emulator for it?
I was going to ask the exactly same question. an emulator for SSSE3 would be nice.
Sources & Contributor Provenance (29 credited usernames · Thread #7318)
| Username | Dossier Contribution | Dispatches | Active Window |
|---|---|---|---|
| @andyvand | Primary Author | 68 | 2011-08-10 → 2011-12-26 |
| @akimoa | Core Contributor | 50 | 2011-08-11 → 2011-11-14 |
| @wastez | Core Contributor | 28 | 2011-08-10 → 2012-01-09 |
| @davisin666 | Core Contributor | 27 | 2011-08-17 → 2011-12-09 |
| @$The-King$ | Core Contributor | 21 | 2011-08-23 → 2012-01-03 |
| @m28ew | Core Contributor | 13 | 2011-08-11 → 2011-12-09 |
| @bassie86 | Core Contributor | 11 | 2011-11-04 → 2011-12-20 |
| @nightf4ll | Core Contributor | 8 | 2011-08-16 → 2011-12-26 |
| @hans88 | Core Contributor | 7 | 2011-09-20 → 2011-12-08 |
| @fumoboy007 | Core Contributor | 6 | 2011-08-11 → 2011-08-19 |
| @Imkantus | Core Contributor | 6 | 2011-08-13 → 2011-08-26 |
| @scififan68 | Core Contributor | 6 | 2011-08-26 |
| @Sn0wStorm | Core Contributor | 6 | 2011-11-06 → 2011-11-11 |
| @Unrealized | Core Contributor | 5 | 2011-08-11 → 2012-04-06 |
| @blackknight | Core Contributor | 5 | 2011-09-04 → 2011-09-30 |
| @kocoman | Core Contributor | 3 | 2011-08-25 → 2011-08-31 |
| @acermac3 | Core Contributor | 3 | 2011-08-26 → 2011-08-28 |
| @RoseMan | Core Contributor | 3 | 2011-08-27 → 2011-08-29 |
| @RayFlower | Contributor | 2 | 2011-08-19 → 2011-08-23 |
| @jblparisi | Contributor | 2 | 2011-08-27 |
| @todesto | Contributor | 2 | 2011-09-06 → 2011-10-14 |
| @delgadilloalex | Contributor | 2 | 2012-03-28 → 2012-03-29 |
| @jackokk | Contributor | 1 | 2011-08-10 |
| @maceshka | Contributor | 1 | 2011-10-19 |
| @Edihigh | Contributor | 1 | 2011-11-05 |
| @jeckerman | Contributor | 1 | 2011-12-17 |
| @MadMungo@iinet. | Contributor | 1 | 2011-12-24 |
| @Lordadmiral Drake | Contributor | 1 | 2012-02-29 |
| @francesco | Contributor | 1 | 2012-04-01 |