lilu.kext kernel panic

[acidanthera-bot]

@fixpol opened vit9696/Lilu#9

I have constant Kernel Panic trying to fix HD530 with lilu.kext. and IntelGraphixsFixup.kext.
My hardware is asrock mini itx h170m, core -i3 6100. My issues are described in this threadhttps://www.tonymacx86.com/threads/solved-update-10-12-5-initialize-graphic-firmware-failed.222582/page-3 . So may be it will be helpful in next release of lilu.kext

[acidanthera-bot]

@vit9696 commented

Hello, withouts keepsyms=1 in boot-args the panic log is not very helpful. Could you copy the debug versions of the plugins add keepsyms=1 to the boot-args and repeat?

I think you do not have a problem with the Lilu code though, at least it is not even mentioned in the backtrace, so closing the issue.

Also, since you are using Lilu from /L/E, consider building a custom https://github.com/PMheart/LiluFriend plugin.

[acidanthera-bot]

@fixpol commented

Hi,

Please find attached  kp report with keepsyms=1 in boot-args. Regarding Liluhelper where i cen find this kext?

Thanks for your time  .

Rgds,

Mark

Od: vit9696 notifications@github.com
Odpowiedź do: vit9696/Lilu reply@reply.github.com
Data: czwartek, 8 czerwca 2017 10:36
Do: vit9696/Lilu Lilu@noreply.github.com
DW: fixpol ms@halolamp.pl, Author author@noreply.github.com
Temat: Re: [vit9696/Lilu] lilu.kext kernel panic (#9)

Hello, withouts keepsyms=1 in boot-args the panic log is not very helpful. Could you copy the debug versions of the plugins add keepsyms=1 to the boot-args and repeat?

I think you do not have a problem with the Lilu code though, at least it is not even mentioned in the backtrace, so closing the issue.

Also, since you are using Lilu from /L/E, consider building a custom https://github.com/PMheart/LiluFriend plugin.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[acidanthera-bot]

@fixpol commented

Please check kP with keepsyms=1. Unfortunately I am an expert in mackintosh thus your advise as well as Lilufrienf manual are far to complicated to be done by myself.
kp 8.06.17 lilu.pdf

[acidanthera-bot]

@vit9696 commented

Do you see a difference between keepsyms=1 and -keepsyms=1 you added :^)?

[acidanthera-bot]

@fixpol commented

Rather not

Od: vit9696 notifications@github.com
Odpowiedź do: vit9696/Lilu reply@reply.github.com
Data: sobota, 10 czerwca 2017 17:07
Do: vit9696/Lilu Lilu@noreply.github.com
DW: Marek Siudym ms@halolamp.pl, Author author@noreply.github.com
Temat: Re: [vit9696/Lilu] lilu.kext kernel panic (#9)

Do you see a difference between keepsyms=1 and -keepsyms=1 you added :^)?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[acidanthera-bot]

@fixpol commented

Just checked that Lilu.kext is OK. Sorry for bothering you. KP is caused by intelgraphiksfixup.kext  starting from 1.1.1 version. 1.1.0  do not make KP , but also do not fix hd530  intel graphics.

Rgds

Od: vit9696 notifications@github.com
Odpowiedź do: vit9696/Lilu reply@reply.github.com
Data: sobota, 10 czerwca 2017 17:07
Do: vit9696/Lilu Lilu@noreply.github.com
DW: Marek Siudym ms@halolamp.pl, Author author@noreply.github.com
Temat: Re: [vit9696/Lilu] lilu.kext kernel panic (#9)

Do you see a difference between keepsyms=1 and -keepsyms=1 you added :^)?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[acidanthera-bot]

@vit9696 commented

Would you stop spamming and start reading already? Stuff like that:

0xffffff81f895b9f0 : 0xffffff800a0ea53c
0xffffff81f895ba70 : 0xffffff800a1ff2dd
0xffffff81f895bc50 : 0xffffff800a09b593
0xffffff81f895bc70 : 0xffffff7f0d10fa80
0xffffff81f895bda0 : 0xffffff800a6408f4
0xffffff81f895be10 : 0xffffff800a64d6b2
0xffffff81f895be60 : 0xffffff800a6b4870
0xffffff81f895be80 : 0xffffff800a696bae
0xffffff81f895bf10 : 0xffffff800a696836
0xffffff81f895bf60 : 0xffffff800a69824e
0xffffff81f895bfb0 : 0xffffff800a0988f7

Is not helpful in any sense. If you want anybody to understand where it panic'ed without doing manual symbolication (that nobody would do), you must add keepsyms=1 to your boot-args. And NOT -keepsyms=1 you added.

[acidanthera-bot]

@fixpol commented

Sorry for misuderstanding. I am novice in  hackintosh.

Od: vit9696 notifications@github.com
Odpowiedź do: vit9696/Lilu reply@reply.github.com
Data: sobota, 10 czerwca 2017 19:43
Do: vit9696/Lilu Lilu@noreply.github.com
DW: Marek Siudym ms@halolamp.pl, Author author@noreply.github.com
Temat: Re: [vit9696/Lilu] lilu.kext kernel panic (#9)

Would you stop spamming and start reading already? Stuff like that:

0xffffff81f895b9f0 : 0xffffff800a0ea53c
0xffffff81f895ba70 : 0xffffff800a1ff2dd
0xffffff81f895bc50 : 0xffffff800a09b593
0xffffff81f895bc70 : 0xffffff7f0d10fa80
0xffffff81f895bda0 : 0xffffff800a6408f4
0xffffff81f895be10 : 0xffffff800a64d6b2
0xffffff81f895be60 : 0xffffff800a6b4870
0xffffff81f895be80 : 0xffffff800a696bae
0xffffff81f895bf10 : 0xffffff800a696836
0xffffff81f895bf60 : 0xffffff800a69824e
0xffffff81f895bfb0 : 0xffffff800a0988f7

Is not helpful in any sense. If you want anybody to understand where it panic'ed without doing manual symbolication (that nobody would do), you must add keepsyms=1 to your boot-args. And NOT -keepsyms=1 you added.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[acidanthera-bot]

@fixpol commented

If I install  separately lilu  and igfx 1.1.0 no panic , but in combo same panic.

Od: vit9696 notifications@github.com
Odpowiedź do: vit9696/Lilu reply@reply.github.com
Data: sobota, 10 czerwca 2017 19:43
Do: vit9696/Lilu Lilu@noreply.github.com
DW: Marek Siudym ms@halolamp.pl, Author author@noreply.github.com
Temat: Re: [vit9696/Lilu] lilu.kext kernel panic (#9)

Would you stop spamming and start reading already? Stuff like that:

0xffffff81f895b9f0 : 0xffffff800a0ea53c
0xffffff81f895ba70 : 0xffffff800a1ff2dd
0xffffff81f895bc50 : 0xffffff800a09b593
0xffffff81f895bc70 : 0xffffff7f0d10fa80
0xffffff81f895bda0 : 0xffffff800a6408f4
0xffffff81f895be10 : 0xffffff800a64d6b2
0xffffff81f895be60 : 0xffffff800a6b4870
0xffffff81f895be80 : 0xffffff800a696bae
0xffffff81f895bf10 : 0xffffff800a696836
0xffffff81f895bf60 : 0xffffff800a69824e
0xffffff81f895bfb0 : 0xffffff800a0988f7

Is not helpful in any sense. If you want anybody to understand where it panic'ed without doing manual symbolication (that nobody would do), you must add keepsyms=1 to your boot-args. And NOT -keepsyms=1 you added.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[acidanthera-bot]

@vandroiy2013 commented

Lilu & IntelGraphicsFixup should be both LATEST versions. Lilu 1.1.4 & IntelGraphicsFixup 1.1.3

[acidanthera-bot]

@fixpol commented

So when installed both latest get KP as in attaché keepsyms=1 file.

Od: vandroiy2013 notifications@github.com
Odpowiedź do: vit9696/Lilu reply@reply.github.com
Data: sobota, 10 czerwca 2017 20:04
Do: vit9696/Lilu Lilu@noreply.github.com
DW: Marek Siudym ms@halolamp.pl, Author author@noreply.github.com
Temat: Re: [vit9696/Lilu] lilu.kext kernel panic (#9)

Lilu & IntelGraphicsFixup should be both LATEST versions. Lilu 1.1.4 & IntelGraphicsFixup 1.1.3

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[acidanthera-bot]

@dawiddr commented

Hi,
I'm also getting a kernel panic on boot on macOS 10.12.5. I'm using Lilu 1.1.4 & IntelGraphicsFixup 1.1.3. My graphics card is HD530. I inject kexts with Clover.

Here's what I get with-liludbg and keepsyms=1:

I hope it helps!

[acidanthera-bot]

@vit9696 commented

@dawiddr so you cannot boot completely? The panic log is rather interesting, but I don't even see Lilu there, although it should. Does the panic differ across the bots?

[acidanthera-bot]

@dawiddr commented

@vit9696 Correct, I can't boot at all unless I specify -liluoff. But in that case kextstat doesn't mention AppleIntelSKLGraphicsFramebuffer, so I assume it's not being loaded at all (?).

The stack trace is always the same.

The output above is for when I disable binary patches for AppleIntelSKLGraphicsFramebuffer.kext in Clover, disable Inject Intel and insert Fake ID. Otherwise I also get kernel panic, but Lilu also fails to patch AppleIntelSKLGraphicsFramebuffer.kext (it outputs errors about being unable to load MachInfo).

Now that I've written all of this down, I start to think that this could be unrelated to Lilu. Maybe I get the panic whether AppleIntelSKLGraphicsFramebuffer is being loaded, even unpatched.

[acidanthera-bot]

@vit9696 commented

Mixing patches for the same kext in Lilu and clover is not a very good idea. I could imagine all sorts of nastiness to happen.
If Lilu says it is unable to load the MachInfo, then you probably have the file missing on your filesystem or something alike.
I am afraid the issue is indeed unrelated… just there are a lot of things gone wrong, and Lilu is the last one to discover it.