InfiniteMac OSx86

InfiniteMac OSx86 (http://infinitemac.com/forum.php)
-   10.X (http://infinitemac.com/forumdisplay.php?f=36)
-   -   Legacy kernel 10.4.0 updated (http://infinitemac.com/showthread.php?t=6578)

RayFlower 09-17-2010 03:28 PM

Thanks for yet another kernel andy!

I still have the problems i had before with steam and abobe cs3 pse and cs5 and some au plugins though.

Just out of curiosity, does this make any sense to you?:

Code:

/Users/my_user/Library/Application\ Support/Steam/SteamApps/[email protected]/half-life\ 2/hl2_osx ; exit;
dyld: Library not loaded: @rpath/libtier0.dylib
  Referenced from: /Users/my_user/Library/Application Support/Steam/SteamApps/[email protected]/half-life 2/hl2_osx
  Reason: image not found
Trace/BPT trap
logout


$The-King$ 09-18-2010 03:57 AM

thanks andy for yours hard work

after tests with new clean install
i must use sysenter patcher if not many programs crashes
i put amd instruction patcher on usr/bin but i can't see any benefit for it
no more patcher_opts=2

on 32bit mode every things work good except sound volume dont change and and quicktime crashes when use subtitles

on 64bit mode sound volume change work but qiucktime totally not work

thanks andy keep your good working

Imkantus 09-18-2010 01:11 PM

Quote:

Originally Posted by $The-King$ (Post 50758)
i put amd instruction patcher on usr/bin but i can't see any benefit for it

The patcher is made to patch out bad instructions from single binary files - not made for patching complete folders...

For example:

sudo -s
amd_insn_patcher /usr/lib/libSystem.B.dylib /usr/lib/libSystem.B.dylib.patched
cp /usr/lib/libSystem.B.dylib.patched /usr/lib/libSystem.B.dylib

Patcher is working great and Kernel is able to boot without patcher_opts=2 now, thanks Andy. ;) I am going to do further testing once I am back from work this evening. :cool:

$The-King$ 09-18-2010 02:19 PM

Quote:

Originally Posted by Imkantus (Post 50768)
The patcher is made to patch out bad instructions from single binary files - not made for patching complete folders...

For example:

sudo -s
amd_insn_patcher /usr/lib/libSystem.B.dylib /usr/lib/libSystem.B.dylib.patched
cp /usr/lib/libSystem.B.dylib.patched /usr/lib/libSystem.B.dylib

Patcher is working great and Kernel is able to boot without patcher_opts=2 now, thanks Andy. ;) I am going to do further testing once I am back from work this evening. :cool:

which files is needed to be patched with this tool
and is there need for sysenter patcher ?
thanks

diskeeper 09-18-2010 02:38 PM

Hey Andy! Thanks for your work!

Installed your updated kernel and VmWare Fusion stopped working. With the 10.4.0 rel 4 kernel everything good.

http://img819.imageshack.us/img819/9...0918153445.png

Code:

Sep 18 15:34:37.735: vmx| Log for VMware Fusion pid=287 version=3.1.1 build=build-282344 option=Release
Sep 18 15:34:37.735: vmx| The process is 64-bit.
Sep 18 15:34:37.735: vmx| Host codepage=UTF-8 encoding=UTF-8
Sep 18 15:34:37.735: vmx| Hostname=diskeeper-Mac-Pro.local
Sep 18 15:34:37.735: vmx| IP=::1 (lo0)
Sep 18 15:34:37.735: vmx| IP=fe80::1 (lo0)
Sep 18 15:34:37.735: vmx| IP=127.0.0.1 (lo0)
Sep 18 15:34:37.735: vmx| IP=fe80::21e:8cff:fec9:3a4d (en0)
Sep 18 15:34:37.735: vmx| IP=192.168.2.101 (en0)
Sep 18 15:34:37.735: vmx| IP=192.168.211.1 (vmnet1)
Sep 18 15:34:37.735: vmx| IP=192.168.82.1 (vmnet8)
Sep 18 15:34:37.735: vmx| Command line: "/Library/Application Support/VMware Fusion/vmware-vmx" "-E" "en" "-D" "w+gVbXFDnoYDPQAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=" "-s" "vmx.stdio.keep=TRUE" "-#" "product=1;name=VMware Fusion;version=3.1.1;buildnumber=282344;licensename=VMware Fusion for Mac OS;licenseversion=3.0 build-282344;" "-@" "pipe=/var/folders/Bb/Bb5kr8hCFQq0qHcq9UoweU+++TI/-Tmp-//vmware-diskeeper/vmx23433769ca3d0533;readyEvent=31" "/Volumes/OSX/XP.vmwarevm/XP.vmx"
Sep 18 15:34:37.735: vmx| Msg_SetLocale: HostLocale=UTF-8 UserLocale=en
Sep 18 15:34:37.735: vmx| Msg_Reset:
Sep 18 15:34:37.735: vmx| [msg.dictionary.load.openFailed] Cannot open file "/Library/Application Support/VMware Fusion/messages/en/vmware.vmsg": No such file or directory.
Sep 18 15:34:37.735: vmx| ----------------------------------------
Sep 18 15:34:37.755: vmx| Ready event: 31
Sep 18 15:34:37.785: vmx| UI Connecting to pipe '/var/folders/Bb/Bb5kr8hCFQq0qHcq9UoweU+++TI/-Tmp-//vmware-diskeeper/vmx23433769ca3d0533' with user '(null)'
Sep 18 15:34:37.785: vmx| VMXVmdb: Local connection timeout: 60000 ms.
Sep 18 15:34:37.786: vmx| UUID: Unable to open /dev/mem: No such file or directory
Sep 18 15:34:37.787: vmx| /Volumes/OSX/XP.vmwarevm/XP.vmx: Setup symlink /var/run/vmware/e155f65b6d40c0055927d152657b9538 -> /var/run/vmware/diskeeper_501/1284816877755659_287
Sep 18 15:34:37.787: vmx| Vix: [140735088876576 mainDispatch.c:374]: VMAutomation: Initializing VMAutomation.
Sep 18 15:34:37.788: vmx| Vix: [140735088876576 mainDispatch.c:397]: VMAutomation: Detected the VM is not managed
Sep 18 15:34:37.788: vmx| Vix: [140735088876576 mainDispatch.c:658]: VMAutomationOpenListenerSocket() listening
Sep 18 15:34:37.788: vmx| Sig_Init already initialized
Sep 18 15:34:37.790: vmx| Vix: [140735088876576 mainDispatch.c:3661]: VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1870, success=1
Sep 18 15:34:37.790: vmx| Transitioned vmx/execState/val to poweredOff
Sep 18 15:34:37.790: vmx| Vix: [140735088876576 mainDispatch.c:3661]: VMAutomation_ReportPowerOpFinished: statevar=1, newAppState=1873, success=1
Sep 18 15:34:37.790: vmx| Vix: [140735088876576 mainDispatch.c:3661]: VMAutomation_ReportPowerOpFinished: statevar=2, newAppState=1877, success=1
Sep 18 15:34:37.790: vmx| Vix: [140735088876576 mainDispatch.c:3661]: VMAutomation_ReportPowerOpFinished: statevar=3, newAppState=1881, success=1
Sep 18 15:34:37.790: vmx| Panic: dropping lock (was bug 49968)
Sep 18 15:34:37.790: vmx| NOT_IMPLEMENTED bora/vmx/main/vmmonPosix.c:312
Sep 18 15:34:37.791: vmx| Core dump limit is 0 KB.
Sep 18 15:34:37.920: vmx| Child process 288 failed to dump core (status 0x6).
Sep 18 15:34:37.921: vmx| Backtrace:
Sep 18 15:34:37.923: vmx| Backtrace[0] 00007fff5fbfef60 rip=00000001003fdb05 rbx=0000000000000000 rbp=00007fff5fbfef90 r12=00000001003fd560 r13=00007fff5fbfef6c r14=00007fff5fbff500 r15=00007fff5fbff6e0
Sep 18 15:34:37.923: vmx| Backtrace[1] 00007fff5fbfefa0 rip=0000000100019df0 rbx=0000000000000000 rbp=00007fff5fbff480 r12=00007fff5fbfefa0 r13=00007fff5fbff4c0 r14=00007fff5fbff500 r15=00007fff5fbff6e0
Sep 18 15:34:37.923: vmx| Backtrace[2] 00007fff5fbff490 rip=000000010003e011 rbx=0000000000000001 rbp=00007fff5fbff490 r12=00007fff5fbff4a0 r13=00007fff5fbff4c0 r14=00007fff5fbff500 r15=00007fff5fbff6e0
Sep 18 15:34:37.923: vmx| Backtrace[3] 00007fff5fbff4a0 rip=000000010003e969 rbx=0000000000000001 rbp=00007fff5fbff4f0 r12=00007fff5fbff4a0 r13=00007fff5fbff4c0 r14=00007fff5fbff500 r15=00007fff5fbff6e0
Sep 18 15:34:37.923: vmx| Backtrace[4] 00007fff5fbff500 rip=000000010003f0ee rbx=00007fff5fbff500 rbp=00007fff5fbff680 r12=000000000000000a r13=0000000000000004 r14=0000000000000000 r15=00007fff5fbff6e0
Sep 18 15:34:37.923: vmx| Backtrace[5] 00007fff5fbff690 rip=00000001000039bb rbx=00000001006931d0 rbp=00007fff5fbff6b0 r12=00000001006931c0 r13=0000000100693020 r14=00007fff5fbff6e0 r15=00007fff5fbff6e0
Sep 18 15:34:37.923: vmx| Backtrace[6] 00007fff5fbff6c0 rip=0000000100019b39 rbx=0000000113801000 rbp=00007fff5fbff6c0 r12=0000000000000001 r13=0000000000000003 r14=00007fff5fbff6e0 r15=00007fff5fbff6e0
Sep 18 15:34:37.923: vmx| Backtrace[7] 00007fff5fbff6d0 rip=0000000100003079 rbx=0000000113801000 rbp=00007fff5fbff750 r12=0000000000000001 r13=0000000000000003 r14=00007fff5fbff6e0 r15=00007fff5fbff6e0
Sep 18 15:34:37.923: vmx| Backtrace[8] 00007fff5fbff760 rip=0000000100003857 rbx=0000000000000003 rbp=00007fff5fbff890 r12=0000000000000003 r13=00007fff5fbff770 r14=000000000000000c r15=0000000000000000
Sep 18 15:34:37.924: vmx| SymBacktrace[0] 00007fff5fbfef60 rip=00000001003fdb05 in function (null) in object /Library/Application Support/VMware Fusion/vmware-vmx loaded at 0000000100000000
Sep 18 15:34:37.924: vmx| SymBacktrace[1] 00007fff5fbfefa0 rip=0000000100019df0 in function (null) in object /Library/Application Support/VMware Fusion/vmware-vmx loaded at 0000000100000000
Sep 18 15:34:37.924: vmx| SymBacktrace[2] 00007fff5fbff490 rip=000000010003e011 in function (null) in object /Library/Application Support/VMware Fusion/vmware-vmx loaded at 0000000100000000
Sep 18 15:34:37.924: vmx| SymBacktrace[3] 00007fff5fbff4a0 rip=000000010003e969 in function (null) in object /Library/Application Support/VMware Fusion/vmware-vmx loaded at 0000000100000000
Sep 18 15:34:37.924: vmx| SymBacktrace[4] 00007fff5fbff500 rip=000000010003f0ee in function (null) in object /Library/Application Support/VMware Fusion/vmware-vmx loaded at 0000000100000000
Sep 18 15:34:37.924: vmx| SymBacktrace[5] 00007fff5fbff690 rip=00000001000039bb in function (null) in object /Library/Application Support/VMware Fusion/vmware-vmx loaded at 0000000100000000
Sep 18 15:34:37.924: vmx| SymBacktrace[6] 00007fff5fbff6c0 rip=0000000100019b39 in function (null) in object /Library/Application Support/VMware Fusion/vmware-vmx loaded at 0000000100000000
Sep 18 15:34:37.924: vmx| SymBacktrace[7] 00007fff5fbff6d0 rip=0000000100003079 in function (null) in object /Library/Application Support/VMware Fusion/vmware-vmx loaded at 0000000100000000
Sep 18 15:34:37.924: vmx| SymBacktrace[8] 00007fff5fbff760 rip=0000000100003857 in function (null) in object /Library/Application Support/VMware Fusion/vmware-vmx loaded at 0000000100000000
Sep 18 15:34:37.925: vmx| Msg_Post: Error
Sep 18 15:34:37.925: vmx| [msg.log.error.unrecoverable] VMware Fusion unrecoverable error: (vmx)
Sep 18 15:34:37.925: vmx| NOT_IMPLEMENTED bora/vmx/main/vmmonPosix.c:312
Sep 18 15:34:37.925: vmx| [msg.panic.haveLog] A log file is available in "/var/folders/Bb/Bb5kr8hCFQq0qHcq9UoweU+++TI/-Tmp-//vmware-diskeeper/vmware-diskeeper-287.log".  [msg.panic.requestSupport.withLog] Please request support and include the contents of the log file.  [msg.panic.requestSupport.vmSupport.apple.menu]
Sep 18 15:34:37.925: vmx| To collect data to submit to VMware support, choose "Collect Support Information" from the Help menu.
Sep 18 15:34:37.925: vmx| You can also run "/Library/Application Support/VMware Fusion/vm-support.tool" directly.
Sep 18 15:34:37.925: vmx| [msg.panic.response] We will respond on the basis of your support entitlement.
Sep 18 15:34:37.925: vmx| ----------------------------------------


opiniatre 09-18-2010 06:22 PM

Wow it does feel snappier compare to legacy 10.4.0 kernel.
Vmware not working for me too parallel is.
Great work ! thanks

Imkantus 09-18-2010 11:46 PM

Quote:

Originally Posted by $The-King$ (Post 50769)
which files is needed to be patched with this tool
and is there need for sysenter patcher ?
thanks

Well the tool patches out sysenter traps as well as it is able to patch cpuid checks into interrupt 0xfb, like we already have been doing using good old maxxus patcher.
I would recommend you to use the kernel in order with -force64 bootflag, as the 64-Bit code of OS X doesn't contain any cpuid trouble, what is making our lifes much easier and working great thanks to Andys hard work. :cool:

On my testing installation I have actually patched only these files and no issues (mp4 Playback and DivX De- & Encoder Plugins in QTX, iTunes etc all working just great):

/usr/lib/libSystem.B.dylib

/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore

/System/Library/QuickTime/QuickTimeComponents.component/Contents/MacOS/QuickTimeComponents

/System/Library/QuickTime/AppleProResDecoder.component/Contents/MacOS/AppleProResDecoder

If Developer Tools are installed libSystem.B_debug.dylib & libSystem.B_profile.dylib need to be patched as well.
The two Quiktime folder ones might not be required, but I patched them as I am still having QT7 in use - I haven't tried without patching those, yet. (going to try that later)
[EDIT]OK. Those two files have to be patched furthermore QTX needs to be executed in 32-Bit mode for mp4 playback to work - I haven't seen that the coresponding checkbox was still set true.[/EDIT]

Quote:

Originally Posted by andyvand (Post 50750)
It does now for dyld.
libSystem.B(_debug/_profile).dylib won't get patched as I haven't been able to build a stable custom dyld yet.
There is however now a tool for AMD which can do the hard work for you...

Anyway this is the best Snow Leopard XNU release for the AMD folks out there by now.
You have done a realy great job to the point and I hope you'll keep it going. ;)

$The-King$ 09-19-2010 01:18 AM

when patching with amd ins patcher
it says bus error

RayFlower 09-19-2010 02:52 AM

Quote:

Originally Posted by $The-King$ (Post 50781)
when patching with amd ins patcher
it says bus error

Same here:S

fumoboy007 09-19-2010 04:53 AM

Can't boot into 64-bit mode
 
I tried using arch=x86_64 and -force64 together but it just won't boot into 64-bit mode, it always goes into 32-bit mode.