Mavericks only boots in Safe mode

[venu2062]

Try using Kext Wizard.

By downloading the kexts (both ACPIBatteryManager and ApplePS2ElanTouchpad) from the source, I got them to successfully install into /S/L/E using DPCIManager.

The battery symbol shows up on the status bar with an X on it. On the drop down, it says No Battery Available. Do I need to patch the DSDT?. I found a number of battery related patches in your repo but none for my laptop.

Similarly, the Elan Touchpad does not work with the latest kext (2.8.3). Do you have any suggestions?

I am attaching current IOReg.

 

[RehabMan]

By downloading the kexts (both ACPIBatteryManager and ApplePS2ElanTouchpad) from the source, I got them to successfully install into /S/L/E using DPCIManager.

The battery symbol shows up on the status bar with an X on it. On the drop down, it says No Battery Available. Do I need to patch the DSDT?. I found a number of battery related patches in your repo but none for my laptop.

Your DSDT needs battery patches. Your patches will be super easy as there are only six 16-bit registers to convert. See here for a guide: http://www.tonymacx86.com/mavericks-laptop-support/116102-how-patch-dsdt-working-battery-status.html

Similarly, the Elan Touchpad does not work with the latest kext (2.8.3). Do you have any suggestions?

No suggestions on Elan. I don't have any laptops with it...

 

[venu2062]

Your DSDT needs battery patches.

My SSDT was generated using your HP pro book installation app.

It seems to have a range of frequencies from 800 to 3200. But the P States of the DPCImanager does not go below 1200.

Do you have any idea why and what I can do to change that? I would like it to go down to 800 when idle.

 

[RehabMan]

My SSDT was generated using your HP pro book installation app.

It seems to have a range of frequencies from 800 to 3200. But the P States of the DPCImanager does not go below 1200.

Do you have any idea why and what I can do to change that? I would like it to go down to 800 when idle.

SSDT doesn't have anything to do with battery status.

And it may be that your CPU cannot go to x8. You will need to build AppleIntelCPUPowerManagementInfo.kext, install it, and look at the output in system.log to determine what your CPU capabilities are, so you know how to set your expectations. (Not all Ivy CPUs can idle at x8, some idle at x12).

You could also post your ioreg and I'll see if you have PM implemented correctly. See: http://www.tonymacx86.com/audio/58368-guide-how-make-copy-ioreg.html

 

[venu2062]

You could also post your ioreg and I'll see if you have PM implemented correctly. See: http://www.tonymacx86.com/audio/58368-guide-how-make-copy-ioreg.html

My IOReg is attached. Please let me know if there are any changes needed in the config.

The laptop also crashes spontaneously once in a while and occassionally gives a KP while booting.

The highest frequency level entry in the SSDT appears incorrect (0x0C80 instead of 0x0C1D) . I am also attaching the SSDT.

Thanks.

 

[RehabMan]

My IOReg is attached. Please let me know if there are any changes needed in the config.

The laptop also crashes spontaneously once in a while and occassionally gives a KP while booting.

The highest frequency level entry in the SSDT appears incorrect (0x0C80 instead of 0x0C1D) . I am also attaching the SSDT.

Thanks.

PM looks correct. The SSDT anomalies are probably (not knowing what CPU you have) work arounds for what I think are incomplete understanding of how x86platformplugin works.

Your instability could be caused by VoodooHDA, known to be buggy/unstable. Better would be to use patched AppleHDA.

 

[venu2062]

PM looks correct. The SSDT anomalies are probably (not knowing what CPU you have) work arounds for what I think are incomplete understanding of how x86platformplugin works.

I experimented a little more with the PM. I added some more frequency entries into the SSDT at the lower end: one each for x7 and x6 and brought down the lower end of the P States to x10 (very strange). When I try to reduce it further it started KP on boot. So, I left it at x10 with SSDT going down to x6.

Your instability could be caused by VoodooHDA, known to be buggy/unstable. Better would be to use patched AppleHDA.

For AppleHDA, I found some post on another site and used a combination of your audio patch and the information provided to patch the DSDT. I also installed the kexts provided (AppleHDA and IOAudioFamily).

The audio device seems to be properly identified (at least from what is displayed in DPCIManager). But the sound devices do not appear in system preferences. I am hoping that you may be able to find what I am doing wrong.

I am attaching the current DSDT (HDEF patched) and IOReg.

Another question I have is if I should apply the fan patch from your list and if there is a way of creating a custom patch for my laptop fan control.

 

[RehabMan]

I experimented a little more with the PM. I added some more frequency entries into the SSDT at the lower end: one each for x7 and x6 and brought down the lower end of the P States to x10 (very strange). When I try to reduce it further it started KP on boot. So, I left it at x10 with SSDT going down to x6.

Did you run AppleIntelCPUPowerManagementInfo.kext to find out what your CPU is capable of first???

For AppleHDA, I found some post on another site and used a combination of your audio patch and the information provided to patch the DSDT. I also installed the kexts provided (AppleHDA and IOAudioFamily).

The audio device seems to be properly identified (at least from what is displayed in DPCIManager). But the sound devices do not appear in system preferences. I am hoping that you may be able to find what I am doing wrong.

I am attaching the current DSDT (HDEF patched) and IOReg.

Hard to tell without seeing the AppleHDA. You're injecting layout-id=28, so you should verify that your AppleHDA expects that.

FYI: I believe most of the other injections you have there are unnecessary. I should probably remove the "advanced" patch from the repo, as I don't think there has been a single case where it is actually necessary to inject the other properties.

Another question I have is if I should apply the fan patch from your list and if there is a way of creating a custom patch for my laptop fan control.

I did an adaptation of the ProBook fan control for an Acer as a request. The person who requested it never tested it or followed up.

For custom fan control, you first have to figure out what controls the fan and how. It requires poking around in the DSDT and playing around in RW-Everything to find a way to control it from the EC. In the Acer case, there was a Windows fan control software package with source, so I was able to adapt what I saw in the source code for that into DSDT code.

 

[venu2062]

Did you run AppleIntelCPUPowerManagementInfo.kext to find out what your CPU is capable of first???

I am not sure how to do it?

Hard to tell without seeing the AppleHDA. You're injecting layout-id=28, so you should verify that your AppleHDA expects that.

FYI: I believe most of the other injections you have there are unnecessary. I should probably remove the "advanced" patch from the repo, as I don't think there has been a single case where it is actually necessary to inject the other properties.

How do I check the AppleHDA? I am attaching it here. But, if you give me pointers, I would like to do it myself.

Most of the DSDT injections in your patch are suggested by the other person also.

 

[RehabMan]

I am not sure how to do it?



How do I check the AppleHDA? I am attaching it here. But, if you give me pointers, I would like to do it myself.

Most of the DSDT injections in your patch are suggested by the other person also.

That AppleHDA uses layout-id=12.