arcaman6 Posted January 22, 2019 Share Posted January 22, 2019 I was hoping someone could help me with an issue on an E5540 regarding loss of audio after sleep. The E5540 is running High Sierra and was installed using this guide and installation went fairly smoothly. I used the E7440_HS.zip bootpack as the E5540 does not have Nvidia (tried to rework for no Nvidia but was not able to get it working). Everything worked except SD card but fixed config and now works fine. However I don't have audio after waking from sleep - works fine (speaker and earphone) when first booted. After sleep no audio on speaker unless you plug/unplug earphones which seems to restart it - but never anything on the earphones themselves after wake. I've checked bootpack kexts and seems to be OK (CodecCommander) and not sure what to do next. Machine has i5-4200U cpu, HD4400 gpu, ALC 3226 audio controller. Cheers and thanks in advance for your help. debug_18128.zip Link to comment Share on other sites More sharing options...
Moderators Jake Lo Posted January 22, 2019 Moderators Share Posted January 22, 2019 Try rebuilding kextcache again. run in terminal to check if CodecCommander is working properly log show | grep CodecCommander 1 Link to comment Share on other sites More sharing options...
arcaman6 Posted January 22, 2019 Author Share Posted January 22, 2019 Thanks for the reply. I have rebuilt it countless time but the result is the same. Here is the output from the rebuild:- sudo ./permission.sh Password: rebuilding //System/Library/PrelinkedKernels/prelinkedkernel kext file:///Library/Extensions/DisableTurboBoostBattery.kext/ is in hash exception list, allowing to load Kext with invalid signatured (-67062) allowed: <OSKext 0x7fba2884aaa0 [0x7fff8e37eaf0]> { URL = "CodecCommander.kext/ -- file:///Library/Extensions/", ID = "org.tw.CodecCommander" } KernelCache ID: 79467EA040F45B7C043B1554575197F2 kextcache updated critical boot files, requesting launchd reboot Finished Every time I repeat I get the same output. There is a lot of repeated information in the log so here is a relevant snippet attached. I'm not familiar with this log so not sure if this says its working properly or not. Cheers. codeccommanderlog.txt.zip Link to comment Share on other sites More sharing options...
Moderators Jake Lo Posted January 23, 2019 Moderators Share Posted January 23, 2019 You're running version .2.6.3 Go ahead and update CodecCommander to latest version 2.7.1 and try again. 1 Link to comment Share on other sites More sharing options...
arcaman6 Posted January 24, 2019 Author Share Posted January 24, 2019 Cheers. That did the trick so everything working 100%. Thanks so much for your help. Link to comment Share on other sites More sharing options...
Recommended Posts