• Smbios Serial Generator For Mac

SMBios.plist is a preference file that tells Mac OS X that your Hackintosh is a real Mac. You usually don't need to edit the SMBios to make Mac OS X work, but sometimes, doing so will activate certain features (i.e. The integrated HD 3000 graphics on Intel's Sandy Bridge processors ). Get the latest working version of Guitar Pro 6 Crack now. We also offer free full version keygen serial free download.

First off, thanks for the awesome reads on your blog. I’ve learn far more about the internals of OS X here than I’m proud to admit, but it’s all good reading none the less. Also, my computer now shows itself as a small black “trash can” in About This Mac screen, which is really awesome. Now, I’ve created a SSDT with the latest ssdtPRGen.sh (for the i7-3820 – Sandy Bridge) and added the DSM Method for plugin-type=1 in it, but I still can’t get machdep.xcpm.mode to be set as one, which won’t allow me to run on a cooler power state. I’m running Chameleon 2283 (I really like Clover, but it always breaks sleep for me). Now, I get the Unknown CPU: family = 0x6, model = 0x2d, stepping = 0x7 error which makes me think it’s ignoring plugin-type, but alas I’m not as versed on PM as you are. Any words of advice?

I’m in a similar situation to Michael. I have a 3930k and have been trying a few things to get PM working, without success. First off, I injected plugintype 1 via DSDT to get X86PlatformPlugin to load. I know it’s for Ivy and not SB-E but it seems to be somewhat of a requirement for MacPro6,1. My AGPM edit didn’t load until I did this as MacPro6,1 is in X86PlatformPlugin.kext Without dropping my SSDT I had no CST or such errors in the console. The X86PlatformPlugin.kext loads but the CPU stays running at 32x. In the console there’s a line “IOPPF: AppleIntelCPUPowerManagement mode”.

However AppleIntelCPUPowerManagement.kext isn’t loaded. So does X86PlatformPlugin have some sort of backwards compatibility? If I drop the SSDT and try to inject states via Chameleon or a SSDT (generated with ssdtPRGen.sh) I get those X86PlatformPlugin::getCPUCStates console errors. I know Clover has an option to inject Ivybridge states, so perhaps they’re different and both of these methods are injecting SB ones? I’m not at all familiar with IB on OS X. The -xcpm boot arg doesn’t seem to have any effect (always machdep.xcpm.mode = 0). I’m not convinced that you need XCPM for power management with your processor, but I understand that people use every opportunity to try something new.

Smbios Serial Generator For Mac

I would stick to the SSDT generated by ssdtPRGen.sh, not because we wrote it, but because I know that it generates the correct data, as far as I know, so what errors do you get? It should not trigger any errors, but perhaps we need to check the CPU data. And “IOPPF: AppleIntelCPUPowerManagement mode” means that it detected a none-Ivy Bridge / Haswell processor. In which case it falls back to AppleIntelCPUPowerManagement.kext Do you have Linux installed? In that case check if power management works, and then check what you need in the SSDT.

This tells you that it relies on the SSDT, meaning that we must get it functional on OS X as well. Oh and can you dump the MSR’s that AppleintelCPUPowerManagement.kext dumps in /var/log/system.log? This will tell us if Linux is initialising the hardware differently. Actually I think there might be a problem with the SSDT script (v6.9): Generating ssdtpr.dsl for a MacPro6,1 Mac-F60DEB81FF30ACF6 Sandy Bridge Core i7-3930K processor 0x206D7 setup 0x0501 With a maximum TDP of 130 Watt, as specified by Intel Warning: Low Frequency Mode is 0 (unknown) Now using 1600 MHz for Server/Desktop processors Number logical CPU’s: 12 (Core Frequency: 3200 MHz) Number of Turbo States: 6 (3300-3800 MHz) Number of P-States: 23 (1600-3800 MHz) The low frequency mode is 1200 MHz so the first few steps from 1200 to 1600 are missing. I got a little muddled-up there.

AppleIntelCPUPowerManagement.kext is indeed loaded. It’s ACPISMCPlatformPlugin.kext that wasn’t loading when I added the plugintype DSDT edit. With the DSDT edit removed it went back to loading ACPISMCPlatformPlugin.kext. There are no errors in the console log with this and the generated SSDT.aml. The errors I was getting (the same ones Michael mentions: “C001 ACST and CST evaluations failed!” for each core) were obviously due to trying to use X86PlatformFamily.kext. Maybe trying to use MacPro6,1 is a waste of time with a SB-E processor.

I just thought it might help getting native PM working on my setup. What are the MSRs that I should look for in system.log? I don’t have linux installed but I have a ubuntu live-cd that I use when needed. What’s the best way to check Speedstep in this?

Is there anything built-in or should I install something like indicator-cpufreq? I guess that confirms I don’t need to patch my BIOS. Here’s all the output in case there’s anything helpful in it.

My board is a P9X79 PRO with the latest 4502 BIOS. Why is MSR 0x1AD set to 0×252626? That should only be used for 8 core processors. Not for six core processors.

This may confuse AppleIntelCPUPowerManagement.kext Also. Your 3930K runs at a clock speed of 3.2 GHz and support turbo frequencies up to 3.8 GHz but MSR 0x1AD starts with 0x23 aka 3.5 GHz instead of 0x21. And this is important; The first turbo frequency must be set to the next bank aka only 100 MHz higher. Not anything else (lower/higher). Can you change the (UEFI) BIOS settings in a way that MSR 0x1AD reports 0x26?

If not, then you need to set it in the boot loader (simple add it somewhere). Luckily for you MSRPLATFORMINFO28 = 1 so you can read/write MSR 0x1AD. MSRPKGCSTCONFIGCONTROL(0xE2) is set to 0x1E000400 but that means that there is no package C-State support. Look here: 000b: C0/C1 (no package C-sate support) 001b: C2 010b: C6 no retention 011b: C6 retention 100b: C7 101b: C7s 111: No package C-state limit. You want at least C6 so OR it with 3.

Same story; Just do this from the boot loader. After this change it should start showing a none-zero value for: MSRPKGC2RESIDENCY(0x60D). I’m glad you’re seeing some issues as I’ve suspected something isn’t quite right with this setup.

First off, there are two entries in my BIOS to enable Turbo and one was turned off. So enabling that one has changed the line AICPUPMI: Max Frequency: 3200 MHz to AICPUPMI: Max Turbo Frequency: 5700 MHz I know 5700 is wrong but I read somewhere this is some sort of known bug. In my BIOS I had the “Package C State Limit” set to Auto (the optimized default). It can be set to Auto, C0, C2, C6, C7 or “No Limit”. Setting it to C6 gave me 0xE1000403 for 0xE2.

Setting it to “No Limit” gave me 0xE1000407. In both cases all of the MSRPKGCxRESIDENCY values remain at zero. Also the optimized defaults had “CPU C3 Report” and CPU C7 Report” set to Disabled. I’ve set them to Enabled for now. I can’t see any way to get 0x1AD starting at 21 in the BIOS. With Turbo now fully enabled and Package C State Limit set to either C6 or “No Limit” it reads 0x393939. Disabling C3 and C7 report still gives me this value.

Pike, Am I in the same boat then, because my 0x1AD shows 21 while my clock speed is 2600MHz so next turbo should be 2700MHz? I do not see anything in my BIOS that can change my turbo stuff. I think they even disabled turbo for some reason according to EVGA forums (it’s a beta bios so everyone hopes they fix it). I’ve patched my AICPM and nop-ed all wrmsr relating to 0xE2 but that does not seem to help, except preventing KPs.

I also get ACPISMCPlatformPlugin::pushCPUCSTData – CST evaluation failed and X86PlatformPlugin::getCPUCStates – CP00 ACST and CST evaluations failed!, depending on the platform I pick when using your ssdtPRGen. If I don’t I don’t get those errors but then nothing happens either. I am not sure anymore what platform should I use in SMBios.plist, it’s a SB-E Xeon v1 system.

Pike hello, thank you for your explanation, but now that it’s released the new Mac Pro, you think you can solve the problem of energy management on x79 platforms? You know very well that there are problems on x79 speed step, I am one of those that I have this platform, and I had to disable the speed step from bios and now it works just two steps, the minimum and the maximum, and not the intermediate ones. I also tried with a SSDT with your script, but without positive results. Ps: many experts have said that it was necessary to wait for the release of the new Mac Pro, to study and solve this problem permanently, but for now I have not found yet a good news.

I’m available to do tester Thz Pike. Hi PikerAlpha, You never cease to amaze me with your knowledge of what is going on under the hood in OS X. It sounds like we’re still a little ways off from native CPUPM on x79 with SanyB-E. I have a rampage iv extreme w a 3930k and use chameleon.

I’m currently getting bios controlled speed step (2 states 12 & 44x) by using NullCPUPM with bios settings: eist=disabled, c1e=enabled and all other states (reporting) =disabled. 2 questions for you: 1) Could you detail in your opinion what smbios/dsdt/ssdt configurations and combinations I should be using to get me as close as possible to native CPUPM at the moment?

2) I followed your sister’s tiny ssdt examples a while back in order to use a ssdt to replace my dsdt but I got stumped when trying to add IRQNoFlags interrupts to hpet. Is there a way to do this via ssdt?

I can’t thank you enough for all the wonderful information and contributions that you and your family have given to the community! I have a SB-EP Xeon which is basically the same chip series as 3930k, just dual capable.

The following are the things that take it in the right direction, but still not 100%: – Run 10.9.2, – Set SMcputype key in SMBios.plist to 2561, – Make sure BIOS does not lock bit 15 of the 0xE2 MSR register (Pike’s tool AppleInteCPUPowerManagementInfo.kext can show that). I opted to patch my BIOS because it was locking, else you can patch AICPM, – Set plugin-type to 1 on my CPU0 in DSDT (important for X86PlatformPlugin.kext to load), – Ensure that AICPM does detect your CPU – it is not for me so that’s still pending. I used my native SSDT (EVGA) without any changes, although you might have to use Pike’s ssdtPRGen.sh. I still do not have full PM because AICPM does not detect my CPU and KPs on boot, so NullCPUPowerManagement is needed to avoid that. But P- and C-States are initiated in the X86PlatformPlugin (check in IOReg) so the only thing missing is the glue (AICPM), I believe, which should come from macpro6,1 hopefully when someone shares AICPM kext from it. You mean this error: “ ACPISMCPlatformPlugin::pushCPUCSTData – CST evaluation failed“?

If yes, then you are using the wrong plugin! If not, and it also names ACST as one of the candidates, then you simply are doing something wrong. No idea what of course. Note: Do not use ‘ a snippet‘ but the generated SSDT. I know that some of you are stubborn and keep using your OEM SSDT data, but that may not be a good idea. The reason I say this is that the power values are usually too high.

What we use is calculated by what biosbits.org says is right. Just look at their test suite.

Hi pike, i had a macbook pro 2013 late with retina. These days i found some errors in console logs like below: SMC::smcReadKeyAction ERROR LsNM kSMCKeyNotFound(0x84) fKeyHashTable=0x0 SMC::smcGetLightshowVers ERROR: smcReadKey LsNM failed (kSMCKeyNotFound) SMC::smcPublishLightshowVersion ERROR: smcGetLightshowVers failed (kSMCKeyNotFound) SMC::smcInitHelper ERROR: smcPublishLightshowVersion failed (kSMCKeyNotFound) what’s that mean? Does it means one sensor on logic board is broken? Because one day i power on my mac, its fan run crazly, and the kerneltask take 300% CPU!，all program is very slow. But it works fine when i leave it for some time. If it is a hardware issue, i should take it to Apple Store to resolve.

Wish your answer, thanks from china.

Okay, found my way here when searching for a way to recover a machines missing serial number. The post that brought me, is pretty dated so. Does anyone have means to recover serial numbers profiler is calling 'not applicable'? The machines I'm dealing with run the list of who's who in Apple models; from iMac's to Towers, in both the G3 and G4 families- running OS9.x. The whole problem started with my netOctopus Admin not seeing all the agents on the network. For an instant, a device would list, but would quickly be replaced by another machine on the network. My best guess is that netOctopus is getting confused by like machine models with 'not applicable' serials.

But if anyone should have other ideas on this particular matter, please chime in. Regardless, I'd love to know how to recover those serials, outside of opening every machine and searching them out. Thanks in advance. I was looking for the machine serial.

I do realize the info is located physically on the machines, but my concern is why profiler doesn't display it anymore. If I could get profiler to retrieve the info as it should, then when I install netOctopus, the agents will automatically grab the serial and model color info from the profiler. This will save me the time manually performing this task for what Institution machines are returning 'not applicable' serial numbers via the profiler.

The original post that lead me to this forum spoke of an Application for OS9 that would retrieve the info. Anyone still around that has it?

Thanks for the input TEG. The thing is, the machines are fresh- well, freshly installed with a standardized image. I'd assume that the image restore is what's killing the serial info in profiler? I don't know.

But essentially, the machines are getting this image restored and updated with the latest netOctopus agent I'm running. I'm also running Norton's 8 on the machine to repair any B-Tree errors. Still no proper feedback from profiler. Guess I could try reformatting one of the machines straight from a factory disc to discern if it in fact is the restore image causing the profiler 'not applicable' info. Thanks again for the input. Still hoping someone has the elusive application I've heard about.