10.7.4 AMD Kernel

[hhxq]

Originally Posted by R:A:W:X86 I am sorry for your problem, but using that boot flag or not should not be any matter. And while we're on the subject some more time: Why the ---- are there so many people who do not understand this?! The original Lion (Vanilla) Kernel is a fat binary made up of an i386 and a x86_64 part. All patched Kernel consist of the i386 part ONLY. So far the x86_64 part can be compiled from patched source, but it hasn't worked on all tested machines (instant reboot). In OS X the i386 Kernel supports using EM64T for applications. Those CPUs not capable of EM64T have been booting what we are calling "-legacy mode" till Snow Leopard. (Also capable CPUs could be forced using the -legacy flag.) Support for those Macs (& Hacks) has been droped in Lion (including -legacy mode in XNU). In the patched Kernel the "-legacy mode" has been reimplemented, as Lion appears to require the SSSE3 instruction set (avaible on latest AMD only) to work, when applications are launched in 64-Bit adress space. This is one reason, why I have doubts about running ML on AMD - even Bulldozer. As the ML Kernel will be x86_64 only. Although not impossible of course... ...theoretically. Testing on that CPU is up to you, it doesn't look like someone has done this yet. Choice between native or virtualized installation is of course up to you as well. In case of native installation you should know, that your graphics will remain unsupported / not allow any accerlation etc. this is most likely the main reason, why noone has tried the Llano yet. The good news is, that in case it will boot at all, you should be able to boot Lion with EM64T enabled, as your APU supports the necessary instruction set. There are some tutorials around that may give you some basic orientation i.e. check that link, two postings up from yours...

first i should say thank you for all your work. i have tried to install 10.7.4 in my AMD machine for more than two months. and i don't know how to compile the x86_64 source to a kernel. does your newest kernel (release in 7-18) need to be complied if i would like to run a 64-bit app. PS: i am a Chinese, my english is poor. but i hope you can understand that.

[felipeunix]

Hello!

new kernel + amd_insn_patcher = all problems solved for me

Thank you R:A:W:X86




I'm using VoodooPower, you too?
--> Here are switching stages very well, but the turbo core I do not think it works right?

--> Is there any way to switch the fancy name that appears on the processor? only to not get the same aesthetic as "unknown." it is possible to change this?

---> The kext that is with the patch, ("IOHIDFamily_nointervalcheck.kext.zip") is always necessary to use, or only in some particular case?

[R:A:W:X86]

Originally Posted by hhxq first i should say thank you for all your work. i have tried to install 10.7.4 in my AMD machine for more than two months. and i don't know how to compile the x86_64 source to a kernel. does your newest kernel (release in 7-18) need to be complied if i would like to run a 64-bit app. PS: i am a Chinese, my english is poor. but i hope you can understand that.

Again: No working 64-Bit Kernel.
In OS X no 64-Bit Kernel - but SSSE3 instruction set capable CPU (Lion) - is needed for running 64-Bit applications.

Originally Posted by felipeunix I'm using VoodooPower, you too? --> Here are switching stages very well, but the turbo core I do not think it works right?

I had to remove some old routines from the Kernel patch that had been causing problems during boot. Missing these may cause tsc sync problems, while stepping with that kext - those routines are way old and may no longer be needed in latest VoodoPower provided by AnV - I am not sure though... use with care.

Originally Posted by felipeunix --> Is there any way to switch the fancy name that appears on the processor? only to not get the same aesthetic as "unknown." it is possible to change this?

You could use

<key>SMcputype</key>
 <string>1281</string>

Macintosh used CPU names only of course, i.e. 1281 will report an Quad-Core Xeon...

Originally Posted by felipeunix ---> The kext that is with the patch, ("IOHIDFamily_nointervalcheck.kext.zip") is always necessary to use, or only in some particular case?

That kext is unrelated to the amd_insn_patcher.
It fixes some check that causes boot hang at No interval found for . Using 8000000 - otherwise not needed.

[sulphide]

fx-8150, seems all main issues have gone with the latest kernel...

[gils]

hey !!!










celeron 341 core solo 2,93 / 775 / chip i865 / ram 2x 512 ddr 333 / FX 5500 256 mo AGP 8x

kernel v5 Dimitrik .

[gils]

@ R:A:W:X86




hello,

Thank you for this kernel. I continued my tests, it's a shame he is not running at 100% , really well optimized, it supports the overclock without problems, with a Mugen 2 does not exceeded 45 ° C
the figures speak for themselves !












le même unlocker en x6 à 3,6 turbo désactivé .

[sulphide]

One issue remains... font rendering is wrong in some apps.

[R:A:W:X86]

Originally Posted by sulphide One issue remains... font rendering is wrong in some apps.

Can you describe with more details, what the problem is?

[sulphide]

Originally Posted by R:A:W:X86 Can you describe with more details, what the problem is?

this happens only to third-party apps, as i can see... all native apps look as they should.

ps not all third-party apps, opera e.g. looks good.

[R:A:W:X86]

Be sure to patch dyld & libsystem_kernel.dylib only - do not touch any other files in /usr/lib with amd_insn_patcher