InfiniteMac OSx86 - Legacy kernel 10.4.0 updated

Page 5 of 9

« First

Last »

Show 50 post(s) from this thread on one page

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)

gedna

09-24-2010 05:45 PM

what about amd_ins_patcher. ? is it necessary ?

fumoboy007

09-24-2010 10:00 PM

Quote:

Originally Posted by fumoboy007 (Post 50892)

Great work so far, Andy! There is one more issue which you should add to your list and that is 64-bit. When I use the kernel flag -force64, it just causes my computer to restart.

Also…the original legacy kernel allowed me to boot into 64-bit albeit without the ability to run 32-bit apps.

fumoboy007

09-25-2010 12:17 AM

Safari sometimes crashes

This happens sometimes:

Code:

Process:         Safari [885]

Path:            /Applications/Safari.app/Contents/MacOS/Safari

Identifier:      com.apple.Safari

Version:         5.0.2 (6533.18.5)

Build Info:      WebBrowser-75331805~1

Code Type:       X86 (Native)

Parent Process:  launchd [104]



Date/Time:       2010-09-24 19:15:01.943 -0400

OS Version:      Mac OS X 10.6.4 (10F569)

Report Version:  6



Interval Since Last Report:          536347 sec

Crashes Since Last Report:           88

Per-App Interval Since Last Report:  280553 sec

Per-App Crashes Since Last Report:   8

Anonymous UUID:                      E4732136-7A6B-4049-B557-9CD6BCAE719B



Exception Type:  EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x00000000676966ee

davisin666

09-25-2010 01:52 AM

With your latest kernel (v4) iTunes 10 doesn't work, FAIL

Code:

24-09-10 20:55:52        kernel        CODE SIGNING: cs_invalid_page(0x8fe2b000): p=339[iTunes] clearing CS_VALID

24-09-10 20:55:53        com.apple.launchd.peruser.501[104]        ([0x0-0x38038].com.apple.iTunes[339]) Exited: Killed

eMatoS

09-25-2010 02:42 AM

Itunes 10 is working here, at first the system felt slow but maybe it was busy with something cause it runs fine now. This time I needed arch=i386 to boot, otherwise I would get an instant reboot.
Andy, I haven't seen thoes errors before DSMOS you mention in the first post (I guess you have to un an unpatched system to see them), also what does these messages mean:

Code:

24/09/10 19:22:43        kernel        warning: kernel was not built with custom dyld blob

24/09/10 19:22:43        kernel        warning: using standard dyld with patcher enabled

24/09/10 22:25:15        kernel        MPlayer OSX Exte (map: 0x4a35520) triggered DYLD shared region unnest for map: 0x4a35520, region 0x7fff85000000->0x7fff85200000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

Another thing I've noticed is that "About this Mac" says Unknown CPU since V3 of your kernel, though I'm not sure if it's your kernel or Chameleon as I've been testing their latest RC5 release.

davisin666

09-25-2010 04:33 AM

I'll stay in V3 XD

$The-King$

09-25-2010 05:16 AM

hi people who use updated legacy kernel is vmware fusion allowed to be setuped or say non intel cpu
http://img251.imageshack.us/img251/2204/vmware.png
thanks
anv kernel rev4 vmware work perfect but with legacy not work

fxwizrd

09-25-2010 04:59 PM

Thank you Andy for the V4. Everything seems to work fine here.
Though I am still not able to boot with arch=x86_64 kernel flag - getting into reboot loop.
Also I had to patch Firefox as it was randomly crashing. After patching with your AMD patcher it now seems to be stable.

Also I have a question: how do I determine which files need patching? I previously used Marvin AMD utility, which scanned all files in a specified directory and created a patcher package. Unfortunately Marvin utility does not work in 64-bit mode...

Thank you,
FX

andyvand

09-25-2010 08:34 PM

Quote:

Originally Posted by eMatoS (Post 50907)

Another thing I've noticed is that "About this Mac" says Unknown CPU since V3 of your kernel, though I'm not sure if it's your kernel or Chameleon as I've been testing their latest RC5 release.

It's probably Chameleon, try my branch as it has a CPU auto-detect fix.

andyvand

09-25-2010 08:36 PM

Quote:

Originally Posted by $The-King$ (Post 50910)

Try setting the patcher to forcing for every app it encounters with:
patcher_opts=50

=FORCE+CPUID+SYSENTER
=2+16+32