Contribute
Register

El Capitan Beta with Dell XPS 13 9343 (Early 2015 Model)

Status
Not open for further replies.
Yes, I had subsequently found that information in the guide and my next post was that result:

"I found this at AppleHDA.kext/Contents/PlugIns/AppleHDAHardwareConfigDriver.kext/Contents/Info.plist

(Which is the proper codecID for alc288):


<key>IOKitPersonalities</key>
<dict>
<key>HDA Hardware Config Resource</key>
<dict>
<key>CFBundleIdentifier</key>
<string>com.apple.driver.AppleHDAHardwareConfigDri ver</string>
<key>HDAConfigDefault</key>
<array>
<dict>
<key>AFGLowPowerState</key>
<data>
AQAAAA==
</data>
<key>CodecID</key>
<integer>283902600</integer>
<key>ConfigData</key>
<data>
ASccEAEnHQABJx6gAScfkAE3HCABNx0AATce
AAE3H0ABRxwwAUcdAAFHHhcBRx+QAYccQAGH
HRABhx6BAYcfAgHXHFAB1x2AAdceZQHXH0AC
FxxgAhcdEAIXHiECFx8BAUcMAg==
</data>
<key>FuncGroup</key>
<integer>1</integer>
<key>LayoutID</key>
<integer>3</integer>
</dict>

Is it safe to say AppleHDA is in fact using the correct layout-id (3)?"

The info above indicates layout-id 3 for 283902600, which is 0x10ec0288, or Realtek ALC288.

There were several codecs listed in this section, but this was the first in the list. Should I edit the info.plist and remove the unneeded codec references, or is that not necessary?

I always remove the extra codecs since the others are not needed and just cause confusion over the applicability of the patched AppleHDA. But it will have no material effect.
 
i'm back with kernel panic (in Windows so is called BSOD maybe?)
And i tried to take a log, would you like to help me what caused it?
 

Attachments

  • system.log.zip
    72.1 KB · Views: 78
i'm back with kernel panic (in Windows so is called BSOD maybe?)
And i tried to take a log, would you like to help me what caused it?

Boot verbose, show photo. Post EFI/Clover folder as ZIP (omit 'themes' folder).
 
Boot verbose, show photo. Post EFI/Clover folder as ZIP (omit 'themes' folder).
I got this kernel panic when the system was running, I watched movies, and suddenly the system went down, then I grabbed the log in the /var/log
 
I got this kernel panic when the system was running, I watched movies, and suddenly the system went down, then I grabbed the log in the /var/log

KPs don't show in system.log. At that point the system has crashed, and can't write to files. KPs will sometimes be stored in NVRAM (assuming you have native NVRAM working) and then reported upon reboot.
 
nah, I did some kexts installation in S/L/E and it seems to make the problems solved(previously I used the kexts inside the clover folder, and now it's time to update to 10.11.3 unfortunately, when the combo updater ask to restart, indeed the system restarts, but nothings shows up and when I check the system it is still the old 10.11.0

Is there any guide? or maybe patches, because when this laptop tries to shuts down, it says unmount and others which I cannot take it because it runs so quick.
 
nah, I did some kexts installation in S/L/E and it seems to make the problems solved(previously I used the kexts inside the clover folder, and now it's time to update to 10.11.3 unfortunately, when the combo updater ask to restart, indeed the system restarts, but nothings shows up and when I check the system it is still the old 10.11.0

Try App Store update.

Or do a fresh install...
 
Thanks! Did not realize you could modify trackpad shortcuts within keyboard section haha.
 
Is there any guide? or maybe patches, because when this laptop tries to shuts down, it says unmount and others which I cannot take it because it runs so quick.

See the first post of this thread, looking for the 10.11.1 update section,. It is the same procedure for 10.11.3 update
 
Thanks! Did not realize you could modify trackpad shortcuts within keyboard section haha.

It is a trick played in the trackpad driver. Since it is integrated with the keyboard driver, it sends fake key events with certain gestures.
 
Status
Not open for further replies.
Back
Top