hello ,

C1E is disable in the bios ?

idlehalt=0 as a line?

just tried that, same result

et avec UsekernelCache=No -f -v

always using this line, still hangs on waiting for dsmos

Can anyone tell me how to apply this patch the kernel?

I´ve got a problem after patching the two dyld files.

I always get the message AuthorizationCreate failed while trying to use appstore or every other app whice needs authentification!
The only thing I am able to use is the terminal.

I also reinstalled lion completely but the error returns as soon as I patch the two files. I also changed the permissions of the two files with chown 0:0 and chmod 755 and used the updatescript.

Any idea?

I downloaded both kernerls from first post, which one is the latest one?

v0.9.26 or v3_rev_b?

...so would I be correct in assuming this still would not provide 64bit support for a Phenom II X6 1075T...?

What about iCloud support?

I believe only Bulldozer & above AMD CPU's have 64-bit support. Lack of SSSE3 on older AMD CPU's?

how to apply the patch to run on 64bit in the bulldozers???³³³³ :(

You have to do the following steps:

-First download the amd_insn_patcher

-Open a terminal and type "sudo su" to without quotes to become root

-Change into your downloaded amd_insn_patcher directory with the terminal
You can do this by typing "cd " (without quotes) and then droping the amd_insn_patcher directory from finder into the terminal and hit enter.

-Type the following commands one line at a time:

cp /usr/lib/dyld ./dyld.orig
cp /usr/lib/system/libsystem_kernel.dylib ./libsystem_kernel.dylib.orig
./amd_insn_patcher dyld.orig dyld.patched
./amd_insn_patcher libsystem_kernel.dylib.orig libsystem_kernel.dylib.patched
chown 0:0 dyld.patched
chown 0:0 libsystem_kernel.dylib.patched
chmod 755 dyld.patched
chmod 755 libsystem_kernel.dylib.patched

Now open 2 more terminal tabs and type sudo su (otherwise your system may freeze in the next step! )
In the first tab type:
mv dyld.patched /usr/lib/dyld

In the second one:
mv libsystem_kernel.dylib.patched /usr/lib/system/libsystem_kernel.dylib

and in the third:
update_dyld_shared_cache

Now you are done!

Has anyone tried this on a non-bulldozer CPU? Patching the kernel to enable 64bit apps?

I just can tell you that even on bulldozer its not running perfect.

As you can see a few posts above I have heavy authentication issues with a clean bulldozer install and problems like diskutilty doesnt show any device ;)

You can try it but its far away from stable!

R.A.W

Already this off.
Do you have another idea to help me?
V4 driver, not the problema.A this version of your kernel performs great.
Only this little problem.

http://http://www.orkut.com.br/Main#...335620826&fr=1
http://www.orkut.com.br/Main#Album?u...335620826&fr=1

I'll do some quote from another thread... :-|

There are 10 types of persons: The ones who read the previous posts and the ones who doesn't.

Someone concernd around here, who has a CCC-Back-up or similiar & could do some testing?

Cause I wonder if launchd would come up during Boot-Up when using the Snow Leopard one...
Be warned that testing this will make the system unbootable (/sbin/launchd from SL will NOT work in Lion!!)!

To know wether it will show up during (non-legacy) boot or not could bring us closer to a 64-Bit solution for the old CPUs...

As long as there is noone, whose able to write an SSSE3 emulation, the only hope for the old CPUs will be to figure out the problematic software & try to patch it.

Authentication in iCloud, Facetime & AppStore has been an issue for a lot Hackintosh users, caused by various reasons.

Regarding iCloud & Facetime I dunno - I am not using these.
I will test AppStore when I am back home...

btw: misterfrista, Thanks for posting a detailed guide for patching sysenter traps. :)
I PMed you with some instructions for further testing on the AppStore thing.

What's your hardware?

By replacing the launchd with the one from the snow-leo,

the GUI failed to load

http://s13.postimage.org/69myb5693/launchd_2.gif



but I was still able to boot the osx into the single-user mode

http://s8.postimage.org/57m8hdppx/launchd_1.gif




FYI, I've even tried to replace the launchd with the ones from LION DP1 & DP2,
but the results still remain the same




I'm just wondering,
why the osx snow-leo lets the legacy-AMD users to run some 64-bits apps without SSSE3 support (by booting it with: -legacy -force64) ?

And please correct me if I'm wrong but no SSSE3 emulator is required there
since it has not been applied into the 10.x.x legacy kernel yet

Thanks for testing...

In order to verify:

You are sure that you have NOT been using the -legacy flag, when taking that screenshot?

(org.chameleon.boot.plist etc)

Nothing else has been expected - I have written in my previous post, that it won't work.

The only idea behind this test was to see if it would boot furhter than "BSD root: blaba" - so we would have some clue, where work on this could be started.

Sorry, but I do not realy understand what you are talking about here...

On previous versions of OS X there has not been any essential software that has been using that SIMD extensions, only stuff like QTX etc...

launchd is the most basic process required for OS X to work.
If my assumption is right, then there will be only two ways for the old AMD & Intel Netburst to boot non-legacy, either emulating the unsupported instructions in the Kernel or making a patch for the concerned software...

http://s13.postimage.org/6cl4g2jjb/launchd_3.gif



but I could boot into the single-user mode only with the -legacy flag
without it, the boot would remain stuck at the same "USBF..." line




It's okay mate, nothing to worry about :)

If you need more testing, please just let me know





Please excuse my stupidity :D

what I mean is 64-bits userland on 32-bits kernel

for example, running the 64-bits version of the Geekbench with the 32-bits kernel of the snow-leo (-legacy -force64)

is there any chance that the -force64 method can also be applied to your kernel ?
so we'll be able to run the 64-bits apps, which are not using the SIMD extensions, with the 32-bits kernel of the lion too ?

Yes more testing!^^

Some idea that came across my mind:

launchd works 32-Bit on the old AMD machines.
So why the hell not just run it 32 instead of 64-Bit? :cool:

Please someone try the following:

if run applications under root through terminal, then they work ok, including disk utility. the other way is to enable root user in pref and work as root user... not good though...

Can you test wether this is related to the Kernel or patching sysenter traps?

Actualy I have not been using amd_insn_patcher - I applied the sysenter patch manualy. (5A 89 E1 0F 34 90 has to be replaced with 59 CD FC 51 C3 90)
The patcher by AnV does some more patching then only sysenter trap.

Disk Utility has been working.
misterfrista also tried doing that single patch only and reported that the AppStore was working way better altough the install fails sometimes...

I don't have my AMD machine in place, so I cannot do testing atm.

with -legacy, I can boot the osx into the GUI

without -legacy, I got stuck at the same "USBF..." line

http://s16.postimage.org/iu7edsekl/launchd_4.gif


But compared to the previous screenshots,
there were no "com.apple.launchd 1" lines exist after the "BSD root..." line like these ones

http://s14.postimage.org/iclfphoc1/launchd_5.gif

damn :-|

I just tried that on my Xeon E3 and it is possible to boot em64t mode with 32-Bit launchd...

Can you please also try to boot without -legacy flag + 32-Bit launchd + sysenter traps patched in dyld & libsystem_kernel.dylib ?

I am loosing hope that the fix might be that easy - but we won't know until we haven't tried....

Hello,

With your kernel my system just restarts after loading kexts.

I´m using a Phenom II 945.
Maybe you look for the issue if you got some time.

Thanks for your hard work.

Greetz

Unfortunately, I already did all those tricks
with lion & snow-leo 's launchd + sysenter patches, with/without -legacy




http://s16.postimage.org/48840t0w5/e...re_refusal.jpg



Thanks again for all your efforts. It's really appreciated! :)

R: A: W: X86

Hopefully with the information you can help me!
I really want to use your kernel!
http://a8.sphotos.ak.fbcdn.net/hphot...21601097_o.jpg
Processor: Phemon II X6 1075T
motherboard: M4785TD-V EVO

As i remember the problem started right after patching libs. I'll take your libs and check when i am at home.

Sorry I was wrong previously. Now I took 2 those libs and patch them manually using the pattern rawx86 gave. So there are no changes at all. There are same authentication problems as before.
fx-8150

ps i chown and chmod libs and of course did update_dyld_shared_cache
pps rawx - you definitely don't have authentication problem? How did you install mac os x? I just expanded the preinstalled distro, it already had user. May it be the problem?

emm... just don't understand anything... finished writing this post i launched "users and groups" in sysprefs, and i managed to use the lock and password window appeared :\ i swear it didn't work when i started writing the post :D
btw i made another user and now use it, not preinstalled one... now restarted diskutil and it works ok without sudo.

after a while locks don't work again ))))) and disk utility too... %) but it seems it starts working when input any command with sudo in terminal and enter sudo password.. then exit. eg. type sudo su then exit - and all locks work.

in console:

10.06.12 0:18:15,554 postfix/master: fatal: open lock file /Library/Server/Mail/Data/mta/master.lock: cannot open file: Permission denied
10.06.12 0:18:16,556 com.apple.launchd: (org.postfix.master[1290]) Exited with code: 1
10.06.12 0:18:16,556 com.apple.launchd: (org.postfix.master) Throttling respawn: Will start in 9 seconds
10.06.12 0:18:25,567 postfix/master: fatal: open lock file /Library/Server/Mail/Data/mta/master.lock: cannot open file: Permission denied
10.06.12 0:18:26,568 com.apple.launchd: (org.postfix.master[1292]) Exited with code: 1
10.06.12 0:18:26,568 com.apple.launchd: (org.postfix.master) Throttling respawn: Will start in 9 seconds
10.06.12 0:18:35,578 postfix/master: fatal: open lock file /Library/Server/Mail/Data/mta/master.lock: cannot open file: Permission denied
10.06.12 0:18:36,580 com.apple.launchd: (org.postfix.master[1293]) Exited with code: 1
10.06.12 0:18:36,580 com.apple.launchd: (org.postfix.master) Throttling respawn: Will start in 9 seconds

use:
sudo chown postfix /var/lib/postfix/master.lock
sudo chgrp postfix /var/lib/postfix/master.lock
sudo chown postfix /Library/Server/Mail/Data/mta/master.lock
sudo chgrp postfix /Library/Server/Mail/Data/mta/master.lock

hello all,

I tested the kernel Bronzovka aka Dmitrik amended by AnV, it's not terrible, I have a lot of bug. I have a much better result with the change of R: A: W: X: 86.

http://www.osx86.net/view/2804-bronz...oo_0.9.26.html

Doesn't work :-(
 

Hi! I tired your and Bronzovka's kernel, but both didn't work. It's stuck at "BSD Root : .." .
More information : http://www.insanelymac.com/forum/ind...owtopic=279629

How to fix that?

Thanks in advance! :-)

assoricks

KP
 

i start to get random kernel panic like in the pic :
http://s15.postimage.org/5samxigtz/I...611_165047.jpg

hehehehe i like what the panic says :)

this is awesome . i want that to be my desktop background.

hhhh lol when i saw it, i was dafuq :confused:

lol they got mad AMD on SL :p and now Lion ^_^

na i think RAW had a fun playing :P

The amd_insn_patcher, must be installed with the kernel?-

"XNU-1699.26.8_v3_rev_b" OR "bronzovkAnVoodoo_0_9_26"?? :confused:

I tried with "bronzovkAnVoodoo_0_9_26," and actually 32bit apps work now in 64bit mode :D:D:D:D

But my account was limited as I think, because for almost everything that does not have permission says, why is that?? :mad:

Disk Utility also does not recognize any device:o

Wastez, I apologize! I have not read your answer.
Where can I learn how to fix FBS?

You can get your frontsidebus with the program cpu-z and add 6 zeros.
for example if you have 200mhz then add fsb=200000000

I think RAW posted this before...

Hello to all and keep up the good work!

I didn't even got to the installer.
When i am trying to boot with -legacy -v arch=i386 npci=0x3000 busratio=19, i am getting the sbin/launchd failed kernel panic.
When i am trying to boot without the -legacy, i am stuck in the USBF.
What i should do?
I have the latest mach kernel and the CPU is the AMD Phenom II X4 965 Black Edition.

Thank you very much!

Avec busratio=17 , c'est mieux .

Thank you very much for your answer!

I gave busratio=19 because i have overclocked my CPU to 3800MHz.
I put back my CPU to the default clock (3400MHz) and i gave the busratio=17 kernel flag, but still no luck (sbin/launchd failed kernel panic).:( This with the following kernel flags: -legacy -v arch=i386 npci=0x3000 (or npci=0x2000) busratio=17.
When i boot only with -v, i am stucked in the USBF "AppleUSBOHCI::CheckSleepCapability - OHCI Controller will be unloaded across sleep" .
What other thing i must check?

Thanks again!!

I didn't think the installer was bootable at all...? I thought you had to run it from an existing SL partition in order to even launch it?

You have to use the stable kernel for the installer.
I installed a clean 10.7.4 created with myhack and the stable kernel without any issues!

Thanks a lot for your replies!

When i say installer i mean the first screen of Mac OS X with the "choose language" etc. [i have made a USB stick with the Mac OS X 10.7.4 (i have restored the basesystem.dmg to the usb, copied the packages folder from the installesd.dmg to the usb, copied the mach kernel to the root of the usb, copied the facesmc and the nullcpupowermanangement kexts to the usb and finally i installed the latest Chameleon with the Chameleon Wizard)].
I will check with the other mach kernel and i will tell you.

Still the same with the other mach kernel (the first mach kernel of the first post of the topic).

If you have a retail image, you should use the myhack installer! It creates an installer usbstick from your retail image with fakesmc and other features! No need to create it manually!

My kernel flags for installer: -v -f -legacy busratio=155 npci=0x2000 GraphicsEnabler=Yes

You just have to change the busratio to your needs and maybe GraphicsEnabler=No!

Its also possible that it has to do with my Cpu, i´ve got a bulldozer 8120 with ssse3 support, maybe the installer just works with ssse3 !

Thanks a lot!! I will try it.

The same.:( "Sbin/launchd failed" kernel panic.

This kernel is the first that lets me boot Lion, but when I start using Lion it freezes after 2 minutes. Any Ideas why?