Jump to content
fantomas1

OS X 10.8.3 all Builds !

339 posts in this topic

Recommended Posts

Tested and success in Motherboard GA-H61M-DS2 rev2.2 with F8 bios

i5 3450 ivy bridge cpu

Geforce 210 1gb ddr3

6 GB ram at 1333mhz

 

when updated it showed some unknown error at last but after restart everything updated and working fine except audio.. fixed by installing the alc888/887b again.. and everything works awesome ! new browser is cool and not showing stupid stuff (bookmarks) on its top .. and its more fluid now! Happy hack ! :trumpet:

 

Edit: by the way the build is 12D78 !

Share this post


Link to post
Share on other sites
Advertisement

HP 7700 intel duo 3.5 g ram . 500g HD 750HD >stata >

usb audio . ALC262 did not work ever.

updated 10.8.3 no problems.

 

stopped using Windows 8! ML lot faster and better graphics.

Share this post


Link to post
Share on other sites

12D76 is a no go for me:

 

kextcache[788] <Error>: -[__NSCFData _fastCStringContents:]: unrecognized selector sent to instance 0x7f8481182da0

kextcache[788] <Error>: *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[__NSCFData _fastCStringContents:]: unrecognized selector sent to instance 0x7f8481182da0'
*** First throw call stack:
(
0 CoreFoundation 0x000000010397bb06 __exceptionPreprocess + 198
1 libobjc.A.dylib 0x00007fff931273f0 objc_exception_throw + 43
2 CoreFoundation 0x0000000103a1240a -[NSObject(NSObject) doesNotRecognizeSelector:] + 186
3 CoreFoundation 0x000000010396a02e ___forwarding___ + 414
4 CoreFoundation 0x0000000103969e18 _CF_forwarding_prep_0 + 232
5 CoreFoundation 0x00000001039007cd CFStringFindWithOptionsAndLocale + 541
6 CoreFoundation 0x000000010390a092 CFStringFind + 178
7 kextcache 0x00000001034cdc98 kextcache + 89240
8 kextcache 0x00000001034cd32b kextcache + 86827
9 kextcache 0x00000001034bbcef kextcache + 15599
10 kextcache 0x00000001034bc41c kextcache + 17436
11 kextcache 0x00000001034badfe kextcache + 11774
12 kextcache 0x00000001034b948a kextcache + 5258
13 libdyld.dylib 0x00007fff97bf77e1 start + 0
)

 

ReportCrash[789] <Error>: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
eportCrash[789] <Error>: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.

Not good....

 

I started having this same issue in 12D76 - even with App Store release of 10.8.3.

 

So far I've figured out:

 

1) It only happens when booting from kernelcache.

2) If you have FileNVRAM loading with chameleon, if you try booting nonkernelcache (UseKernelCache=No) after booting via kernelcache, you will still have the issue.

 

You need to not load FileNVRAM and boot without kernelcache in order to get binaries that are kext_tools related to run again (kextcache, kextd, kextload, kextutil).

 

*edit: Removing the generated nvram.plist in /Extra works as well; it will just be remade next boot and will work fine. So you don't have to get rid of FileNVRAM. Didn't think about this. derp.*

 

So the question is why is this happening to some people but not close at all to most people, in specifically 10.8.3 builds? I do not have any clue at all. Not yet anyway. I'll be spending the next few days finding out wtf is wrong. I just wanted to post this here so anyone getting this will know how to get things running fine again (not including iMessages now, unfortunately).

 

I'll be sure and post any updates regarding this.

Share this post


Link to post
Share on other sites

Looks like the latest build of FileNVRAM fixes the issue.

 

http://public.xzenue...NVRAM-1.1.3.zip

 

Replacing ths FileNVRAM module didn't solved my issue. Next step was removing FileNVRAM.dylib and that solved my issues.

The generated NVRAMfile is still there : file://localhost/Extra/nvram.xxxxxxxx-c600-0007-878e-bcaec5219fb2.plist

 

Also another thing to know is that with loading of the FileNVRAM module in 10.8.3 you loose SMB connections to windows systems.

Now they can be conected again with the removal of the FileNVRAM module.

Share this post


Link to post
Share on other sites

I started having this same issue in 12D76 - even with App Store release of 10.8.3.

 

So far I've figured out:

 

1) It only happens when booting from kernelcache.

2) If you have FileNVRAM loading with chameleon, if you try booting nonkernelcache (UseKernelCache=No) after booting via kernelcache, you will still have the issue.

 

You need to not load FileNVRAM and boot without kernelcache in order to get binaries that are kext_tools related to run again (kextcache, kextd, kextload, kextutil).

 

*edit: Removing the generated nvram.plist in /Extra works as well; it will just be remade next boot and will work fine. So you don't have to get rid of FileNVRAM. Didn't think about this. derp.*

 

So the question is why is this happening to some people but not close at all to most people, in specifically 10.8.3 builds? I do not have any clue at all. Not yet anyway. I'll be spending the next few days finding out wtf is wrong. I just wanted to post this here so anyone getting this will know how to get things running fine again (not including iMessages now, unfortunately).

 

I'll be sure and post any updates regarding this.

I got this solved by manually deleteing everything in

/System/Library/Caches/com.apple.kext.caches/Startup/

and running this little script I found that basically repairs permissions and kextcache.

https://www.dropbox....sspw/rebuild.sh

Edit: Also make sure to have nvram boot-args="" to empty.

Share this post


Link to post
Share on other sites

Edit: Also make sure to have nvram boot-args="" to empty.

 

What does that mean | do ?

 

I'll thought that nvram module generated an nvram file which is needed to got iMessage fixed. You mean put back the FileNVRAM module with specify nvram boot-args="" in org.chameleon.Boot.plist?

Share this post


Link to post
Share on other sites

What does that mean | do ?

 

I'll thought that nvram module generated an nvram file which is needed to got iMessage fixed. You mean put back the FileNVRAM module with specify nvram boot-args="" in org.chameleon.Boot.plist?

Run:

 

sudo nvram boot-args

For me it should just output empty but after installing 10.8.3 I saw that my boot-args were set to some gibberish. I just removed it with

sudo nvram boot-args=""

and ran the script,kextcache errors were gone.

Share this post


Link to post
Share on other sites

and ran the script,kextcache errors were gone.

 

Well I build a new USB installer from the the install Mountainlion.10.8.3.app. When the module FileNVRAM is present, and the module is added when deploy Chameleon bootloader (even with latest FileNVRAM), this will fail any atempt to install directly to 10.8.3 as well.

 

So whats best practice just remove the FileNVRAM module when installing | add the module after successfull install and execute [sudo nvram boot-args=""] and repair everything with your script?

Share this post


Link to post
Share on other sites

Replacing ths FileNVRAM module didn't solved my issue. Next step was removing FileNVRAM.dylib and that solved my issues.

The generated NVRAMfile is still there : file://localhost/Extra/nvram.xxxxxxxx-c600-0007-878e-bcaec5219fb2.plist

 

Also another thing to know is that with loading of the FileNVRAM module in 10.8.3 you loose SMB connections to windows systems.

Now they can be conected again with the removal of the FileNVRAM module.

 

My unit had the same issue with accessing afp (linux) shares.

Removing FileNVRAM.dylib remedies the situation

Share this post


Link to post
Share on other sites

still i experienced boot args problem in FileVRAM 1.1.3 and chameleon 2189

if i copy filenvram files from extra. remove it from extra. no problem.

are we waiting fix this problem?

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

  • Recently Browsing   0 members

    No registered users viewing this page.

×