Contribute
Register

getCPUIDinfo: this is an unknown CPU model 0x3a -- Power management may be incomplete or unsuppor

Status
Not open for further replies.
Joined
Nov 7, 2012
Messages
8
Motherboard
10.8.2
CPU
GA-Z77-D3H F16 i5 3570k
Graphics
Sapphire HD 6870
Mac
  1. 0
Classic Mac
  1. 0
Mobile Phone
  1. 0
Hi,
I built my first Hack with the specifics you can see in my profile.
I used MB with the settings you can see in the image attached
Schermata 2012-11-20 alle 15.28.03.png
Everything was fine since I started migrate files and software (Adobe CS 5.5 and 6 and many others) from the iMac with the Migration Assistant. When I completed the migration, the Hack worked, but when i restarted, it stuck on the spinning wheel, after I Log in, and nothing displayed on the desktop, even if i boot in safe mode.
I removed video card, connecting DVI on the onboard graphics to use USB key with Unibeast/ML.

When I boot in verbose mode I get this message:
getCPUIDinfo: this is an unknown CPU model 0x3a
-- Power management may be incomplete or unsupported
.

I repaired permissions with Disk Utility from USB key with Unibeast/ML, but nothing happened. I try connecting from the iMac to change extensions, but I got no permissions even if I log in as admin. I can only modify org.chameleon.Boot.plist and smbios.plist.

Someone can help me, please? I'm going crazy! Thanx
 
You do not have to tick FakeSMC. It is included with UserDSDT or DSDT-Free Installation option. I have done that and it corrupted my FakeSMC. I would delete your FakeSMC located in S/L/E and reinstall it with that being your only option. Also, I have read it is not advised to use the migration assistant. Maybe that caused a issue. Best of luck emmekappa.
 
When I boot in verbose mode I get this message:
getCPUIDinfo: this is an unknown CPU model 0x3a
-- Power management may be incomplete or unsupported
.
OS X simply doesn't not know about your 3570K processor; no Apple desktop Ivy Bridge system has shipped to date. Power management is working if you system is configured properly.​
 
Thanx for your replies, Pakalolo and Toleda.
@ Pakalolo: so, your advice is to reinstall ML without FakeSMC, copy files and reinstall software without Migration Assistant, isn't it?
@ Toleda: ok, there are no Ivy Bridge systems known by Mac Os X, but before I tried to migrate files, everything was fine. If the system is not configured properly, why power management worked well?
I'm trying to understand what is the best configuration I can choose and how I can get it with Multibeast or other tools. Can you explain "for dummies", please?
 
Thanx for your replies, Pakalolo and Toleda.
@ Pakalolo: so, your advice is to reinstall ML without FakeSMC, copy files and reinstall software without Migration Assistant, isn't it?
@ Toleda: ok, there are no Ivy Bridge systems known by Mac Os X, but before I tried to migrate files, everything was fine. If the system is not configured properly, why power management worked well?
I'm trying to understand what is the best configuration I can choose and how I can get it with Multibeast or other tools. Can you explain "for dummies", please?

No. I thought maybe your FakeSMC got corrupted. Just open Multibeast 5.1.3 on your current install and only tick the FakeSMC and nothing else after you deleted the old one but, it sounds like Toleda has the fix for your problem.
 
How can I delete the corrupted one, if I can't boot? Hack stuck at the spinning wheel after I log in.

I read many hack-users that managed to use a ivy bridge system, so I imagine that must exist a way to solve the problem, or not?
 
Problem solved!
It's all about Migration Assistant, you don't have to use it. I reinstalled Mac Os X and all the softwares and only copied all my files from my other Mac, and all works properly now.

So guys, if you have tech specs like mine, use settings like in the image attached and avoid Migration Assistant. Good hack!
 
OS X simply doesn't not know about your 3570K processor; no Apple desktop Ivy Bridge system has shipped to date. Power management is working if you system is configured properly.​

it looks like its because the wrong CPU Platform plugin is being loaded, the older default one is being loaded that doesn't recognise that cpu. modern macs use X86PlatformPlugin, you can enable this by injecting plugin-type 0x1 in DSDT under the PR.CPU0 scope. this corrects the error and should somewhat correctly enable power management for the cpu.

i have made a feature request post for this to be included in chimera, maybe it will make it in.

http://www.tonymacx86.com/chimera-f...cope-enable-x86platformplugin.html#post522230
 
it looks like its because the wrong CPU Platform plugin is being loaded, the older default one is being loaded that doesn't recognise that cpu. modern macs use X86PlatformPlugin, you can enable this by injecting plugin-type 0x1 in DSDT under the PR.CPU0 scope. this corrects the error and should somewhat correctly enable power management for the cpu.

i have made a feature request post for this to be included in chimera, maybe it will make it in.

http://www.tonymacx86.com/chimera-f...cope-enable-x86platformplugin.html#post522230


can you tell me exactly what we have to do?step by step ?
please :D
 
can you tell me exactly what we have to do?step by step ?
please :D

i don't want to get into exactly how to extract modify and load DSDT, that's beyond the scope of this post ;)

but this is the code you need to inject

Code:
Method (_DSM, 4, NotSerialized)
        {
            Store ("Writing plugin-type to Registry!", Debug)
            Store (Package (0x02)
                {
                    "plugin-type", 
                    0x01
                }, Local0)
            DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
            Return (Local0)
        }


if you can post a copy of your DSDT i'll add it in there and post it back as an example.
 
Status
Not open for further replies.
Back
Top