Contribute
Register

Kernel Panic on Assus N550JK (Kexts Problems)

Status
Not open for further replies.
10 / 10 again !

Thank you.


For my curiosity: do you know why the wake problem just happened after the 10.10.4 ?
 
furox said:
...
For my curiosity: do you know why the wake problem just happened after the 10.10.4 ?
Click to expand...

No idea. I have same issue/solution on my u430 (using that patch since 10.10.2).
 
Hi again !

After a half-month of usage everything is working so good,.. except two littles things:

1- The full charged battery power source goes to the battery after minutes, I loose my ac adapter energy saver mode to battery mode (backlight/screen timeout...).
Infos:
kernel[0]: 18636.273428: setWOW_PARAMETERS:wowevents = 0(0)
Click to expand...

I got your applesmartbattery installed

2- Kernel panic when booting with hdmi connected
Infos:
*** Panic Report ***
panic(cpu 0 caller 0xffffff7f822cfeb9): assertmsg@/SourceCache/GPUDriversIntel/GPUDriversIntel-10.6.31/Common/IONDRV/Intel/HSW/AppleIntelFramebuffer/AppleIntelController.cpp:16553
Backtrace (CPU 0), Frame : Return Address
0xffffff81e7cd3a10 : 0xffffff800032bda1
0xffffff81e7cd3a90 : 0xffffff7f822cfeb9
0xffffff81e7cd3ac0 : 0xffffff7f822b7af9
0xffffff81e7cd3ae0 : 0xffffff7f822b7d1f
0xffffff81e7cd3b30 : 0xffffff7f80f51e6c
0xffffff81e7cd3b60 : 0xffffff8000901c0f
0xffffff81e7cd3bc0 : 0xffffff80008ff503
0xffffff81e7cd3d00 : 0xffffff80003e21e7
0xffffff81e7cd3e10 : 0xffffff800033000c
0xffffff81e7cd3e40 : 0xffffff80003149f3
0xffffff81e7cd3e90 : 0xffffff800032531d
0xffffff81e7cd3f10 : 0xffffff80004031ea
0xffffff81e7cd3fb0 : 0xffffff8000435396
Kernel Extensions in backtrace:
com.apple.iokit.IOGraphicsFamily(2.4.1)[6F7F093D-DBEA-356A-9A08-D8EAC7F767DE]@0xffffff7f80f3d000->0xffffff7f80f83fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[D8F585E8-2EE9-3135-8E37-A034123FE45C]@0xffffff7f80b24000
com.apple.driver.AppleIntelFramebufferAzul(10.0.6)[02479236-D51D-3B11-9EE8-58760AEFDF5F]@0xffffff7f822ab000->0xffffff7f822f5fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[D8F585E8-2EE9-3135-8E37-A034123FE45C]@0xffffff7f80b24000
dependency: com.apple.iokit.IOACPIFamily(1.4)[70E2B65E-A91A-3522-A1A0-79FD63EABB4C]@0xffffff7f81732000
dependency: com.apple.iokit.IOAcceleratorFamily2(156.16)[8DA5CE1F-2C00-3CE3-8BF1-1FC07BFCF4E7]@0xffffff7f81c1e000
dependency: com.apple.iokit.IOReportFamily(31)[781C9DD1-4CE9-3AEB-85EA-D420CEC18916]@0xffffff7f8172b000
dependency: com.apple.AppleGraphicsDeviceControl(3.10.24)[B2B5765C-4EC5-3C51-85D9-91B90D38D485]@0xffffff7f80f94000
dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[6F7F093D-DBEA-356A-9A08-D8EAC7F767DE]@0xffffff7f80f3d000
Click to expand...

But I can connect the hdmi after boot with no problem.

Thank you for your time and answers.
 
furox said:
Hi again !

After a half-month of usage everything is working so good,.. except two littles things:

1- The full charged battery power source goes to the battery after minutes, I loose my ac adapter energy saver mode to battery mode (backlight/screen timeout...).
Infos:


I got your applesmartbattery installed
Click to expand...

If you mean the status goes to battery when you still have AC plugged in, problem is in your DSDT (_BST method).

2- Kernel panic when booting with hdmi connected
Infos:


But I can connect the hdmi after boot with no problem.

Thank you for your time and answers.
Click to expand...

You need to implement HDMI audio...

HDMI-audio on Haswell has several requirements:
- the device at address 0x00030000, usually called B0D3, must be renamed to HDAU
- the resulting HDAU device must be recognized by AppleHDAController (config.plist patches required if not natively recognized... or you can use FakePCIID_Intel_HDMI_Audio.kext)
- your framebuffer must be patched for HDMI-audio (there are patches in my default config.plist (disabled) files: https://github.com/RehabMan/OS-X-Clover-Laptop-Config). It is trial/error to determine which port your HDMI is connected (actually, they are positional and you can tell by looking at ioreg).
- patched AppleHDA is required (sometimes VoodooHDA works, but my experience has been not good)
- you have to inject "hda-gfx"="onboard-1" for IGPU and HDAU objects. This is usually done with DSDT/SSDT edits (_DSM methods)
 
RehabMan said:
If you mean the status goes to battery when you still have AC plugged in, problem is in your DSDT (_BST method).
Click to expand...

Is there an actual working fix on dsdt energy mode fix ?

my _BST method:
Method (_BST, 0, NotSerialized) // _BST: Battery Status
{
Store (Zero, Index (PBST, Zero))
Store (Ones, Index (PBST, One))
Store (Ones, Index (PBST, 0x02))
Store (Ones, Index (PBST, 0x03))
If (LNot (^^LPCB.EC0.BATP (Zero)))
{
Store (One, Index (PBST, Zero))
Return (PBST)
}


If (LEqual (^^LPCB.EC0.GBTT (Zero), 0xFF))
{
Return (PBST)
}


If (MES4)
{
Decrement (MES4)
Return (PBST)
}


BATO ()
BATS (Zero)
Store (^^LPCB.EC0.BSTS (), Local0)
Store (^^LPCB.EC0.BCRT (), Local1)
Store (^^LPCB.EC0.BRCP (), Local2)
Store (^^LPCB.EC0.BVOT (), Local3)
If (LNotEqual (Local0, Ones))
{
If (LNotEqual (Local1, Ones))
{
If (LNotEqual (Local2, Ones))
{
If (LNotEqual (Local3, Ones))
{
FBST (Local0, Local1, Local2, Local3)
CBST ()
}
}
}
}


BATR ()
Return (PBST)
}
Click to expand...

RehabMan said:
You need to implement HDMI audio...
Click to expand...

Im not actually interested by patching all my audio driver bunch. I'll look at this later but thanks for the tips.
 
RehabMan said:
Pay attention to fCurrentStatus in the logs.

Here's the info on _BST:
Code: 
...
Click to expand...

Well, I don't know in which way this is related.

I just can see that the Currentrat values are both divided by 2.
 
furox said:
Well, I don't know in which way this is related.
Click to expand...

The status determines whether the the kext sees the battery charging or discharging.

You can read about it in the ACPI spec.

I just can see that the Currentrat values are both divided by 2.
Click to expand...

Not sure what you're referring to.
 
RehabMan said:
The status determines whether the the kext sees the battery charging or discharging.

You can read about it in the ACPI spec.
Click to expand...
So can I fix the discharging rate regards to the dsdt ? the native acpi bios table isnt correct ?
 
furox said:
So can I fix the discharging rate regards to the dsdt ?
Click to expand...

Discharging rate has nothing to do with what you reported previously.

the native acpi bios table isnt correct ?
Click to expand...

No idea. Doesn't seem like you've analysed the output yet.

You need to correlate logs with the point at which the problem occurs.

Also, from the most recent ioreg, you're not using the current ACPIBatteryManager.kext.
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top