Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Late 2009/Mid 2010 iMac, 2010 15"/17" MBP: 1st gen Intel Core i kernel panic #2

Open
vinc3m1 opened this issue Aug 3, 2020 · 9 comments

Comments

@vinc3m1
Copy link

vinc3m1 commented Aug 3, 2020

Core i5 with ATI Radeon 4850.

Tried steps 1, 2, and 4. Booting to USB loads apple logo, screen goes black, and then just restarts boots my regular partition. And then, will restart again soon after booting my regular partition (just before I can type in my filevault password), before booting finally the 3rd time normally allowing me to type in my filevault password and boot into macOS (patched Mojave).

I can boot to USB in verbose mode, however the text scrolls by too quickly for me to be able to see anything meaningful. Perhaps I can try to capture the text output in slomo tomorrow to see what it says.

@barrykn
Copy link
Owner

barrykn commented Aug 3, 2020

The problem is the 1st-gen Core i5 CPU. I got another report already via Discord a few days ago (on a 2010 iMac). I've already updated the README on the dev-v0.0.18 branch (I'll release v0.0.18 tonight or tomorrow morning).

However, I do want to enhance micropatcher.sh to detect these models/CPUs and warn users, so I'll keep this issue open until then (probably later this week).

By the way, once you boot back into Mojave, does it ask if you want to send an error report to Apple?

@vinc3m1
Copy link
Author

vinc3m1 commented Aug 4, 2020

Ah yeah I noticed the updated comments this morning, sucks that the CPUs are unsupported now without changed to ACPI kexts.

I didn't see anything about error reports after booting back into Mojave no. If you have any idea where any sorts of logs/dumps may be written I'm happy to try to look next time I try.

@barrykn
Copy link
Owner

barrykn commented Aug 4, 2020

I didn't see anything about error reports after booting back into Mojave no. If you have any idea where any sorts of logs/dumps may be written I'm happy to try to look next time I try.

I just remembered that if the kernel panic happens too early in boot, nothing gets logged, so never mind.

Once I make some more changes to my patcher (probably by v0.0.19 or v0.0.20), it'll be possible for me to try a crazy experiment with ACPI kexts...

@barrykn barrykn changed the title Late 2009 iMac (11,1) reporting in Late 2009/Mid 2010 iMac, 2010 15"/17" MBP: 1st gen Intel Core i kernel panic Aug 8, 2020
@toshibochan
Copy link

If replace cpu to 2.8 i7 860 you think will work?

@vinc3m1
Copy link
Author

vinc3m1 commented Aug 9, 2020

If replace cpu to 2.8 i7 860 you think will work?

Exact same architecture, shouldn't make a difference.

@barrykn
Copy link
Owner

barrykn commented Aug 9, 2020

Replacing with a Core 2 Duo (I think this might require replacing the motherboard as well) would work. However, make sure you can also upgrade to a Metal GPU, or this will not be worth doing.

Edit: Actually, it might not be worth doing anyway. There's a considerable speed difference between Core 2 Duo and 2nd gen Intel Core ("Sandy Bridge", used in 2011 Macs) or later. Also, for what it's worth, Apple's Japanese IME in Big Sur requires a Sandy Bridge or later CPU (unless someone can create a patch).

@toshibochan
Copy link

anyone can make a patch for iMac (27-inch, Late 2009),2.66 GHz Quad-Core Intel Core i5,ATI Radeon HD 4850 512 MB?

@barrykn
Copy link
Owner

barrykn commented Sep 25, 2020

anyone can make a patch for iMac (27-inch, Late 2009),2.66 GHz Quad-Core Intel Core i5,ATI Radeon HD 4850 512 MB?

In my comment about this issue on August 4, I mentioned something about trying a crazy kext experiment. I didn't get a chance to try that yet. Maybe I'll get a chance to try it this weekend.

@barrykn
Copy link
Owner

barrykn commented Oct 31, 2020

There has been significant progress on this issue (it's fixable after all):
https://forums.macrumors.com/threads/macos-11-big-sur-on-unsupported-macs-thread.2242172/post-29137636

It's possible that issue #80 will be a prerequisite for fixing this, in which case it might be a while before I can add the fix to the patcher. However, in the near term I'll still add the kexts that these Macs need. (Probably not for v0.5.0, but for a release soon after.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants