|
Front Row doesn't work
I have patched /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A /System/Library/Quicktime Also Marvin's AMD utility doesn't work too and iTunes stops itself the reproduction. Sorry for my bad english Anyway, thx! |
Thank you..but patching is not working
Only patcher_opts=2 works and all others like patcher_opts=18 or patcher_opts=34 or the no patcher_opts gives me a KP saying:
Code:
warning: invalid kernel ip, won't attempt to handle trap |
After a few days everything is running as it should, (except for Marvin, crashlog below) although I've noticed that the system seems a bit slow sometimes. Another thing I've noticed is that some soft, like pacifist, won't open with qoopz kernel but it runs fine with yours.
Thanks again for this Andy. Code:
ReportCrash[184:1407] Failed to create CSSymbolicatorRef for Marvin's AMD Utility |
agree, system is slower than using nawcom kernel, every benchmark i have tested confirm that, and graphics ar glitchy also, that was not the case using just 32bit system... dont know where is the problem.. but my experience is that
|
I noticed with -force64 its rather slow myself but without that flag its as efficient as it should be, anyhow this is the first revision of a kernel/dyld that can use 64bit binaries simultaneously as 32 bit on amd so i guess it can take a bit time until its as reliable as it is on a intel cpu:)
Also, my terminal gets bombarded with: dyld: shared cached file was build against a different libSystem.dylib, ignoring cache not a big deal though I guess I should do some benchmarks myself to confirm the slow downs, working with anything coreaudio with -force64 at the moment is just too glitchy. |
Well, I've done some benchmarks and I got the oppposite result as you guys, my system gets better scores in 64bit, and quite better as you can see. As for the slowdown problem, maybe it's something else, like the graphics, don't know what I can do to find the issue.
@Rayflower: try rebuilding the prebindings, I got that problem the first time and that solved it. I always use mainmenu for that purpose but there are many tools for that. http://img832.imageshack.us/img832/4...reencap.th.jpg |
ok here my benchmark, as i sed, there is differences, and quit a bit,
booted without -force64 flag, and my god. how everything was smooth (was on 64-32 by 2 or 3 days) it was so obvious that, that with -force64 system was on some lag on performance and especially on graphics, you can feel that on naked eye.. (google earth was just lagging like crazy) almost every app was taking longer time to boot, (but i have to admit, pictures files and pdf's was opened damn quick much quicker than on 32bit system) strange.. anyways maybe better patch coming soon :) lets hope so. 32bit http://i33.tinypic.com/1zu6tk.jpg 64bit http://i33.tinypic.com/2nv6wyp.jpg |
Thanks eMatos, that did the trick!
Also for my benchmarking: http://img840.imageshack.us/img840/2015/92920607.png Turns out the tests done there gives -force64 the better hand but my results there are marginal. An on other news i noticed some new(to me) errors in some software i have: http://img101.imageshack.us/img101/1888/aics5.png and http://img824.imageshack.us/img824/9525/pscs3.png |
Mine seems to be normal:
32-bit Geekbench on 32-bit Snow: http://i33.tinypic.com/jf94dw.png 32-bit Geekbench on 64-bit Snow: http://i36.tinypic.com/2061oa9.png 64-bit Geekbench on 64-bit Snow: http://i37.tinypic.com/m8e99t.png |
Quote:
|