InfiniteMac OSx86  


Reply
Page 3 of 7 < 12 3 45 > Last »
 
Thread tools Display modes
  #21  
Old 08-23-2010, 12:17 AM
davisin666 davisin666 is offline
 
Join Date: Feb 2010
Location: Santiago, Chile
Posts: 98
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!
Last edited by davisin666; 08-23-2010 at 11:31 PM.
Reply With Quote
  #22  
Old 08-25-2010, 04:27 PM
fumoboy007 fumoboy007 is offline
Jaguar
  
Join Date: Jul 2010
Posts: 40
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
EDIT: forgot to add that my processor is AMD Athlon X2 4400+
Last edited by fumoboy007; 08-27-2010 at 04:01 AM.
Reply With Quote
  #23  
Old 08-25-2010, 09:08 PM
eMatoS's Avatar
eMatoS eMatoS is offline
 
Join Date: Jan 2008
Location: Argentina
Posts: 185
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
CPU: AMD Athlon 64 3000+ @2.3Ghz - Motherboard: ASUS A8N-SLI nForce4 SLI - nForceLAN by eno - SuperNForceATA by Medevil - RAM:2 GB DDR 333Mhz Audio: ALC850 Video: XFX nVidia GeForce 8400GS 256Mb (0x06e4) QE & CI from Chameleon 2 RC4Ethernet: Realtek RTL 8139 Series (working out of the box) OS: Snow Leopard 10.6.4 (aryajuanda's guide) + Windows XP 64bits
Reply With Quote
  #24  
Old 08-26-2010, 08:30 AM
gedna gedna is offline
Jaguar
  
Join Date: May 2009
Posts: 52
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
Reply With Quote
  #25  
Old 08-26-2010, 02:05 PM
RayFlower RayFlower is offline
Jaguar
  
Join Date: Jan 2010
Posts: 93
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.
Reply With Quote
  #26  
Old 08-26-2010, 03:01 PM
eMatoS's Avatar
eMatoS eMatoS is offline
 
Join Date: Jan 2008
Location: Argentina
Posts: 185
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.



CPU: AMD Athlon 64 3000+ @2.3Ghz - Motherboard: ASUS A8N-SLI nForce4 SLI - nForceLAN by eno - SuperNForceATA by Medevil - RAM:2 GB DDR 333Mhz Audio: ALC850 Video: XFX nVidia GeForce 8400GS 256Mb (0x06e4) QE & CI from Chameleon 2 RC4Ethernet: Realtek RTL 8139 Series (working out of the box) OS: Snow Leopard 10.6.4 (aryajuanda's guide) + Windows XP 64bits
Reply With Quote
  #27  
Old 08-26-2010, 04:09 PM
gedna gedna is offline
Jaguar
  
Join Date: May 2009
Posts: 52
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


64bit
Reply With Quote
  #28  
Old 08-26-2010, 05:48 PM
RayFlower RayFlower is offline
Jaguar
  
Join Date: Jan 2010
Posts: 93
Thanks eMatos, that did the trick!

Also for my benchmarking:


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:



and

Reply With Quote
  #29  
Old 08-26-2010, 06:25 PM
diskeeper's Avatar
diskeeper diskeeper is offline
Jaguar
  
Join Date: Jun 2008
Location: Hungary
Posts: 64
Mine seems to be normal:

32-bit Geekbench on 32-bit Snow:


32-bit Geekbench on 64-bit Snow:


64-bit Geekbench on 64-bit Snow:
Mac OS X 10.7.2 11C40 - Vanilla kernel
Gigabyte GA-P43T-ES3G - Intel Q8300 - 4 GB Geil DDRIII 1333MHz
EVGA GeForce GTX 460 SC 1024 MB - Linksys WMP54GS PCI
Reply With Quote
  #30  
Old 08-27-2010, 07:12 PM
andyvand's Avatar
andyvand andyvand is offline
 
Join Date: Apr 2009
Location: Tienen
Posts: 515
Quote:
Originally Posted by fxwizrd View Post
Thank you Andy for providing the new kernel and patches.
I Installed the kernel + AMD sysenter trap patch and added the following kernel flags to the boot string:
arch=i386 patcher_opts=2 -force64

Everything now seems to be working fine. Although I noticed I am still getting cs_invalid_page errors. Here are some of them:

CODE SIGNING: cs_invalid_page(0x1000): p=47[loginwindow] clearing CS_VALID
CODE SIGNING: cs_invalid_page(0x1000): p=46[mds] clearing CS_VALID
CODE SIGNING: cs_invalid_page(0x1000): p=88[fontd] clearing CS_VALID
CODE SIGNING: cs_invalid_page(0x1000): p=110[Dock] clearing CS_VALID
CODE SIGNING: cs_invalid_page(0x1000): p=111[SystemUIServer] clearing CS_VALID
CODE SIGNING: cs_invalid_page(0x1000): p=112[Finder] clearing CS_VALID
CODE SIGNING: cs_invalid_page(0x1000): p=115[fontd] clearing CS_VALID

Is there a way to get rid of them?

Thank you!
FX
Ignore these, the kernel has a patch integrated which forces CS_VALID after detecting any com.apple.xxx code signature...


💡 Deploy cloud instances seamlessly on DigitalOcean. Free credits ($100) for InfMac readers.

Reply With Quote
Reply
Page 3 of 7 < 12 3 45 > Last »



Archive - Privacy - Top