Jump to content

[SOLVED] E6420 no sound since 10.11.5


barnum
 Share

Recommended Posts

Since my update to 10.11.5, I have no sound on my E6420 ;(

I have put "AppleHDAIDT.kext"in "/Library/Extensions/"

Ghent I launch kextutil on this kext I have that : 

vincents-macbook-pro:~ root# kextutil /Library/Extensions/AppleHDAIDT.kext 

Can't create kext: invalid CFBundleVersion in identifier cache entry entry 210.

Can't create kext: invalid CFBundleVersion in identifier cache entry entry 10.

Diagnostics for AppleHDAIDT.kext:

Warnings: 

    Personality CFBundleIdentifier differs from containing kext's (not necessarily a mistake, but rarely done): 

        HDA Hardware Config Resource

    The booter does not recognize symbolic links; confirm these files/directories aren't needed for startup: 

        AppleHDA

 

Code Signing Failure: code signature is invalid

Warnings: 

    Personality CFBundleIdentifier differs from containing kext's (not necessarily a mistake, but rarely done): 

        HDA Hardware Config Resource

    The booter does not recognize symbolic links; confirm these files/directories aren't needed for startup: 

        AppleHDA

 

Can't create kext: invalid CFBundleVersion in identifier cache entry entry 210.

Can't create kext: invalid CFBundleVersion in identifier cache entry entry 10.

kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext "AppleHDAIDT.kext"

Can't create kext: invalid CFBundleVersion in identifier cache entry entry 210.

Can't create kext: invalid CFBundleVersion in identifier cache entry entry 10.

kext signature failure override allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext "/Library/Extensions/AppleHDAIDT.kext"

Can't create kext: invalid CFBundleVersion in identifier cache entry entry 210.

Can't create kext: invalid CFBundleVersion in identifier cache entry entry 10.

Can't create kext: invalid CFBundleVersion in identifier cache entry entry 210.

Can't create kext: invalid CFBundleVersion in identifier cache entry entry 10.

Link to comment
Share on other sites

  • Moderators

do you have SIP disabled?

did you run permission fix and rebuild cache?

 

      sudo chmod -Rf 755 /L*/E*

      sudo chown -Rf 0:0 /L*/E*
      sudo touch -f /L*/E*
      sudo chmod -Rf 755 /S*/L*/E*
      sudo chown -Rf 0:0 /S*/L*/E*
      sudo touch -f /S*/L*/E*
      sudo kextcache -Boot -U /
Link to comment
Share on other sites

Sorry to hijack the thread, but I have exactly this issue also.

 

I do have SIP enabled, how do I disable this ?

 

 

System Integrity Protection status: enabled (Custom Configuration).

 

Configuration:

Apple Internal: disabled

Kext Signing: disabled

Filesystem Protections: disabled

Debugging Restrictions: enabled

DTrace Restrictions: enabled

NVRAM Protections: enabled

 

This is an unsupported configuration, likely to break in the future and leave your machine in an unknown state.

Link to comment
Share on other sites

Thanks.

 

I did this, re-did permissions and rebooted.

The cache output was 

 

 

 rebuilding //System/Library/PrelinkedKernels/prelinkedkernel

kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext IOAHCISerialATAPI_Injector.kext

kext file:///Library/Extensions/DisableTurboBoostBattery.kext/ is in hash exception list, allowing to load

kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext AppleHDAIDT.kext

kext-dev-mode allowing invalid signature -67061 0xFFFFFFFFFFFEFA0B for kext IOGraphicsFamily.kext

kextcache updated critical boot files, requesting launchd reboot

 

The SIP is now

 

 

System Integrity Protection status: disabled.

 

However, still no audio.

I should have mentioned it is a E6220.

Anything else I can check?

Link to comment
Share on other sites

Hi Jake Lo

 

No, sorry I haven't actually given you the full story!

It was okay following the upgrade, but I had an issue where the volume would be on maximum each time I booted up, and when I clicked a volume button it would reset to the correct volume, halfway or wherever the slider bar indicated.

 

So what I realised was that, even though I have a build from your instructions, using Clover, my kext arrangements were different to what you had in your boot pack.  So I went ahead and installed your bootlick kexts.  (6 into EFI Kexts Others) and 3 into LE.

 

Looking at the difference in my old Kext - I seemed to be using the VoodooHDA in the EFI Clover.

 

I tried with the boot without caches, rebuild and then reboot, but still the same.

 

Thanks

Mike

Link to comment
Share on other sites

 Share

×
×
  • Create New...