Jump to content

xalp

Members
  • Content count

    2
  • Joined

  • Last visited

About xalp

  • Rank
    InsanelyMac Protégé
  1. I just got back to OSX'ing my old computer and while googling for information about mach_sse42_only I came across a site scraping content off InsanelyMac: http://www.likelyanswer.com/10105451/Ml-With-Mach_sse42_only-Lots-Of-Kxld%5Bcomapple%5D-In-Interface-Comapple-Of-__kernel__-Couldnt-Find-Symbol- Is scraping this post: http://www.insanelymac.com/forum/topic/288528-ml-with-mach-sse42-only-lots-of-kxldcomapple-in-interface-comapple-of-kernel-couldnt-find-symbol/ Just wanted to point this out if there's something that should be done about it (don't know what the policy about content is on this site, didn't find a quick link to it either) since it doesn't look like there's any form of attribution or link to InsanelyMac on that page. I must say it ranked higher on Google than InsanelyMac. Best regards, -------- Edit: Meh, nevermind. Just realized searching on the site "mach_sse42_only" results in a link to the original post.
  2. The messages are gone after upgrading to 10.8.3. Guess it might have something to do with symbols from other components in the update getting embedded in the kernel, or similar. I'm leaving this question here just in case it could be useful to other users. ______________________________________________________________________________________ Hello all, I installed ML on this old computer (check sig) using the Install Mountain Lion app from the App Store + myHack and mach_sse42_only with the patched corecrypto.kext. I manually edited OSInstall.mpkg to lower the minimum memory check to 1GB. I noticed during boot of the installation media a lot of log traces like this one: kxld[com.apple.iokit.SCSITaskUserClient]: In interface com.apple.kpi.iokit of __kernel__. couldn't find symbol __ZM8IOMapper18_RESERVEDIOMapper3Ev With many different values for com.apple.* and the symbol name. The installer ran fine, and the installation is also running OK. However, I'm also getting these log traces when booting the installation. Does someone know what do they mean, what effects can they have, and what can be done about them, if there is something? Didn't have time to test the installation thoroughly, but it seems everything is fine. Just wanted to make sure if something can be done about this before tuning kexts for hardware support. Thanks!
×