Mac OS X on x86 Hardware 2008–2024 Technical Archive
InfiniteMac OSx86 › OSx86 Core & 10.X › Just updated to 10.6.8 (combo update), KP at boot
6,403 reads · 2011-07-24 – 2011-07-26
Note 10.X Core

Just updated to 10.6.8 (combo update), KP at boot

Here is a screenshot of the kernel panic I get. 10.6.7 worked flawlessly with me so wanted to take the plunge to 10.6.8 thinking it would be just as easy… Guess I was wrong. Interesting thing is that on top it says 64 bit mode enabled but…

Primary Author
@adnbek Published 2011-07-24
Collection
OSx86 Core & 10.X
Archival Footprint
6,403 historical reads · 2 curated field notes (from 6 dispatches) · 2011-07-24 – 2011-07-26
Credited Voices (2)
@adnbek (4)@wastez (2)

Here is a screenshot of the kernel panic I get. 10.6.7 worked flawlessly with me so wanted to take the plunge to 10.6.8 thinking it would be just as easy… Guess I was wrong.

Interesting thing is that on top it says 64 bit mode enabled but I specifically added the flags to boot in 32 bit mode (arch=i386). Could that be related somehow?

Author Updates & Technical Revisions

Follow-up dispatches by @adnbek

Author Update #1 @adnbek 2011-07-25 ↳ Re: @wastez
@wastezDid you install the new kernel after installing the update? I can´t read it exactly but it looks like you are using 10.6.8 with kernel 10.0.0, is that right? If you didn´t update the kernel, install legacy_kernel 10.8.0 and also the right sleepenabler for it. Did you remove the old sleepenabler before you update your system? Did you…

Hey Wastez,

Seems like you're always there to help. I really appreciate it! The picture is not too clear but the kernel is 10.8.0. As for sleep enabler, i didn't remove it, I just changed pm version to 23. Seems to be working fine as shown at the top of the screenshot.

As a test, I'll remove sleep enabler tonight and see if that helps. Problem with this KP is that there is no kext mentioned at all in the backtrace. And I don't seem to have a PCI configuration begin issue but I did replace ACPIplatform and IOpcifamily (unsure of the name, I'm at work now) and it made no difference.

I don't think I need legacy kernel. It's always worked fine on vanilla (up until 10.6.7).

Author Update #2 @adnbek 2011-07-25

Haha! It worked! It was sleepenabler after all. Taking it out from extra/extensions (thank GOD for Macdrive) helped. I replaced it with a newer version that doesn't KP the system.

USB wasn't working so replaced with 10.6.7 usb kexts and got that working. Lost QE/CI so replaced with 10.6.7 gma kexts and framebuffer kexts and graphics restored.

So now it's working perfectly again!

Wastez, you're awesome. (Y) How did you know it was sleepenabler? Nowhere in the KP did it hint at it.

Author Update #3 @adnbek 2011-07-26 ↳ Re: @wastez
@wastezThat´s fine when your system is working again. I knew that about sleepenabler because it has to be changed on every update where the kernel has changed. A other reason was because it was one of the last things which loaded before the kernel paniced.

Ah cool. I thought simply changing pmversion number was enough but now I know.

But anyway, it works great now. I had the appstore login issue but fixed that too.

Synthesized Community Field Notes

2 technical responses curated from 6 original dispatches

Field Note #1 @wastez 2011-07-25

Did you install the new kernel after installing the update?
I can´t read it exactly but it looks like you are using 10.6.8 with kernel 10.0.0, is that right?
If you didn´t update the kernel, install legacy_kernel 10.8.0 and also the right sleepenabler for it.

Did you remove the old sleepenabler before you update your system?

Did you fix the problem with "PCI Configuration"?

These would be the possibilities which can be done wrong by updating to 10.6.8!

The infos are too less, i need more to help you.

Field Note #2 @wastez 2011-07-26

That´s fine when your system is working again.

I knew that about sleepenabler because it has to be changed on every update where the kernel has changed.
A other reason was because it was one of the last things which loaded before the kernel paniced.

Sources & Contributor Provenance (2 credited usernames · Thread #7284)
UsernameDossier ContributionDispatchesActive Window
@adnbekPrimary Author42011-07-24 → 2011-07-26
@wastezContributor22011-07-25 → 2011-07-26