Jump to content
Teresa77

About This Mac - processor wrong recognized

22 posts in this topic

Recommended Posts

Hi, I would like to ask for little help. In "about this Mac" my processor is not correctly recognized and is showing as an Intel Core i7 instead of Xeon E3... My build is using latest Clover, everything is working, sleep etc. Smbios I used iMac14,2 because it is the closest Haswell model to mine.

Can anyone please help me to correct this issue? Thanks a lot.

post-1486797-0-70015200-1441891540_thumb.png

Share this post


Link to post
Share on other sites
Advertisement

Hi Allan, thanks, I know about this possiblity, but I think it is really an issue and not just only cosmetic. System really thinks that has an i7 instead of Xeon, when you change manually about this mac window it does not affect real system settings.


For example in my com.apple.SystemProfiller.plist I have this:

 

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>CPU Names</key>
<dict>
<key>DNMP-en_CZ</key>
<string>iMac (27-inch, Late 2012)</string>
<key>F8JC-en_CZ</key>
<string>iMac (27-inch, Late 2013)</string>
</dict>
<key>NSWindow Frame SystemProfile</key>
<string>1077 60 751 520 0 0 1920 1177 </string>
</dict>
</plist>
 
There is no mention about the Core i7. So the system get the information about i7 somewhere deep in the system. So I need to change it somewhere else, I mean not cgange it, but get the system to recognize it correctly. Bios and other apps like Geekbench see the correct name for the Xeon, So how is that possible?
 
And second strange thing is that in this file you can see "iMac (27-inch, Late 2012)" and also "iMac (27-inch, Late 2013)", so why 2012 vs 2013?
 
Maybe the key is to find out where did Geekbench, Cinebench etc. get the info about Xeon as well the About this mac info about the i7.

Share this post


Link to post
Share on other sites

Go to the About This Mac->System Report->Hardware and see your speed:

and I have two different speed one really 4,4GHz and one wrong 4,3GHz

 

 

 

I do not like to makeup my system!!!

Share this post


Link to post
Share on other sites

The screenshot from geekbench is on my first picture in first post on the right side. The speed and the processor name is correct. About this mac is reporting wrong my CPU as an i7.

Share this post


Link to post
Share on other sites

Hi JuniorGump, thats why I started this thread. Why should a Xeon E3-1241v3 be listed in "about This Mac" as na Core i7. I want to solve this, but noone helped. Why all other applications see it as a Xeon but only About this Mac, System Crash Reporter etc. as na i7?

Share this post


Link to post
Share on other sites

2Sebinouse: No I didn't played with that. Why? All other apps read the correct information about my Xeon from somewhere. So why not About this mac? I don't want to fake it, I want it to be clear and real.

Share this post


Link to post
Share on other sites

Since there's no Mac models w/ a Xeon E3-1241v3 CPU, I doubt you'll be able to get the processor info to display correctly; iMac14,2 only uses i5 and i7.

 

You might try using MacPro6,1. That would at least be closer to what you have.

 

And yes, it's not just a cosmetic issue, as your SMBIOS will influence other aspects of system functionality.

Share this post


Link to post
Share on other sites

As I wrote before I have already tried MacPro6,1 smbios with no effect. So from where are other apps correctly reading info about my Xeon?

Share this post


Link to post
Share on other sites

As I wrote before I have already tried MacPro6,1 smbios with no effect.

Ah, okay.

 

So from where are other apps correctly reading info about my Xeon?

Geekbench is probably reading it from "sysctl machdep.cpu.brand_string" or something of the like.

Share this post


Link to post
Share on other sites

I don't care about what is About this mac showing me. I just want the whole System to know that I have a Xeon and so the system can with deal with it on its level. I think some processor dependend features may the system interpreting wrong when it thinks it has an i7 instead of Xeon. And as I wrote, I see no problem while using the computer, but I can't see under the hood. Maybe the system could perform better if the system correctly recognize my Xeon. Apple always used Xeons in MacPro machines, where the stability, speed and power matters.

Share this post


Link to post
Share on other sites

I just want the whole System to know that I have a Xeon and so the system can with deal with it on its level. I think some processor dependend features may the system interpreting wrong when it thinks it has an i7 instead of Xeon. And as I wrote, I see no problem while using the computer, but I can't see under the hood. Maybe the system could perform better if the system correctly recognize my Xeon.

I know. And what I'm saying, is that if you want OS X to know you've a Xeon CPU and optimize for this accordingly, you'll need to select a SMBIOS most compatible to that CPU. The SMBIOS definitions are what OS X reads from to carry out some of the 'under the hood' stuff you mention.

Share this post


Link to post
Share on other sites

2crushers: the link you provided is from year 2010 so it will not be actual for 10.10.5. I investigated current system file with file on the site and it differs a very lot. So it is unusable.

 

2mfckr: I am already running on iMac14,2 which is the most closest smbios to my Xeon. Nothing is closest to this one.

Share this post


Link to post
Share on other sites

Hello all, use to use this forum back in my hackintosh days... and it comes back to help me once again!!!!

 

I had the same issue with this unknown cpu in yosemite on a first gen pro. Usually used cpuinjector.kext to fix this problem in previous versions, but not with yosemite!

 

10.10.5 recognized everything about the CPU, except the name in "About This Mac". Everything else like GHz Frequency, Cache, FSB, cores, all there in profiler.

 

Came across and tried several different methods, but this is the one  that worked for me, since the system physically recognized all the specs of CPU. X5355's

 

Found solution here at insanelymac, link:

 

http://www.insanelymac.com/forum/topic/302888-how-to-change-yosemite-about-this-mac/

 

Here are my steps:

 

ran command in terminal to view hidden files

navigated to: System ▸ Library ▸ PrivateFrameworks ▸ AppleSystemInfo.framework ▸ Versions ▸ A ▸ Resources ▸ English.lproj ▸

to find file: AppleSystemInfo.strings

opened that file with textwrangler app

proceeded to:

<key>UnknownCPUKind</key>

<string>Unknown</string>

 

Since it saw the correct speed of my CPUs, I only changed string from unknown to Quad-Core Intel Xeon

 

Example:

<key>UnknownCPUKind</key>

<string>Quad-Core Intel Xeon</string>
 
then clicked file, save a copy, and saved the copy to desktop
then moved that saved copy back to:System ▸ Library ▸ PrivateFrameworks ▸ AppleSystemInfo.framework ▸ Versions ▸ A ▸ Resources ▸ English.lproj ▸
and replaced the existing AppleSystemInfo.strings file with the one i edited and saved to desktop
 
Hope this helps! and big ups to Duran Keeley for his helpful post!

about.tiff

Share this post


Link to post
Share on other sites

 

Hello all, use to use this forum back in my hackintosh days... and it comes back to help me once again!!!!

 

I had the same issue with this unknown cpu in yosemite on a first gen pro. Usually used cpuinjector.kext to fix this problem in previous versions, but not with yosemite!

 

10.10.5 recognized everything about the CPU, except the name in "About This Mac". Everything else like GHz Frequency, Cache, FSB, cores, all there in profiler.

 

Came across and tried several different methods, but this is the one  that worked for me, since the system physically recognized all the specs of CPU. X5355's

 

Found solution here at insanelymac, link:

 

http://www.insanelymac.com/forum/topic/302888-how-to-change-yosemite-about-this-mac/

 

Here are my steps:

 

ran command in terminal to view hidden files

navigated to: System ▸ Library ▸ PrivateFrameworks ▸ AppleSystemInfo.framework ▸ Versions ▸ A ▸ Resources ▸ English.lproj ▸

to find file: AppleSystemInfo.strings

opened that file with textwrangler app

proceeded to:

<key>UnknownCPUKind</key>

<string>Unknown</string>

 

Since it saw the correct speed of my CPUs, I only changed string from unknown to Quad-Core Intel Xeon

 

Example:

<key>UnknownCPUKind</key>

<string>Quad-Core Intel Xeon</string>
 
then clicked file, save a copy, and saved the copy to desktop
then moved that saved copy back to:System ▸ Library ▸ PrivateFrameworks ▸ AppleSystemInfo.framework ▸ Versions ▸ A ▸ Resources ▸ English.lproj ▸
and replaced the existing AppleSystemInfo.strings file with the one i edited and saved to desktop
 
Hope this helps! and big ups to Duran Keeley for his helpful post!

 

Thanks for the help, but for me not served. Continues to show a Core i7. :/

 

 

post-637410-0-73757600-1442422434_thumb.png

Share this post


Link to post
Share on other sites

I have the same problem.

 

My XEON E3-1220 v3 is listed as an "3,09 GHz Intel Core i7" in about this mac.

The rest of the specifications are fine, only the name is wrong.

 

I have a Supermicro x10slm-f server mainboard with ECC memory, so the missing ECC can't be the problem.

 

I use Mac OS X 10.11.2 with the actual clover release and smbios of the Mac Pro 3,1.

At the weekend i will try Mac Pro 6,1...

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By glasgood
      CLOVER DUAL BOOT MOJAVE & WINDOWS 10 GUIDE 
       

       
       
      INCLUDES  MBR / LEGACY BIOS  TO  GPT / EFI CONVERSION
      USING MBR2GPT TOOL
       
       
      PREREQUISITE: Two physical discs ( SSD’s or HDD’s )
       
       
       
       
       
      STEP 1 - Clover dual boot configuration 
       
      Open config.plist with Clover Configurator
       
      Boot
       Legacy = PBR Timeout = True ( will remove the Timeout countdown, from Clover boot menu)  

       
      GUI 
      Scan / Custom
       Entries = True  Tool = True  Legacy = False ( removes extra Windows 10 entries )  
      Hide Volume
      - Preboot ( macOS Preboot )
      - Recovery ( macOS Recovery )
       

       
      So at boot you will have two options: boot macOS Mojave or Windows 10 
       
       
       
       
       
       
       
      ————————————————————
       
       
      STEP 2 - Using a drive without Windows 10 installed
       
      Disconnect system drive that contains your macOS Mojave install from computer ( This is so that Windows does not overwrite existing macOS Mojave boot loader )
       
      Proceed with a Windows 10 UEFI install.  
      After installation reconnect macOS Mojave Drive, the Windows installation should now be detected and usable in Clover. 
      If Windows 10 is not detected or able to boot,  then verify you installed Windows 10 as UEFI and not MBR ---->  ( Read step 2 - For a drive with Windows 10 installed )
       
       
      OR
       
       
       
      STEP 2 - Using a drive with Windows 10 already installed
       
      Verify your Windows install is  GPT / UEFI or MBR / Legacy BIOS.   
      If Windows install is GPT UEFI then Windows 10 install is ready to use at Clover boot menu, you should be able to boot into Windows directly from Clover boot screen. 
       

       
       
      But if  Windows drive is detected at Clover boot screen, but when booting Windows you get a black screen with a cursor on the top left,
      then this is most likely because Windows drive is MBR ( Legacy BIOS ).  You can easily convert MBR to GPT using  Windows MBR2GPT tool ( this saves hours work having to reinstall Windows 10 and setting up all your applications again  ) 
       
      If Windows 10 install is MBR / Legacy BIOS  then simply convert to GPT / UEFI  following instructions below ( read video summary and view video )
       
       
      ** To use Windows 10  MBR2GPT tool  you must have Windows 10 version 1703 ( creators update  ) or later and less than 3 partitions on 
      the Windows 10 drive **
       
      Video summary:
       
      Confirm Windows 10 drive is MBR Legacy BIOS ( in Windows Disk Management ) Reboot into Windows PE ( Advanced Startup ) Convert from MBR Legacy BIOS to GPT UEFI ( using commands below ) mbr2gpt /validate mbr2gpt /convert Restart Verify Windows 10 drive has changed to GPT UEFI ( in Windows Disk Management )  
       
       
       
      After conversion Windows 10 is ready to use at the Clover boot menu 
       
       
       
      STEP 3 - Stop Windows Boot manager from overriding Clover boot manager
       
      How to stop Windows boot manager from overriding your Hackintosh Clover boot manager when using dual booting between macOS and Windows
       
       
       
       
       
       
    • By cvad
      Small tool to download, compile and build the latest Clover X64 package.
       
       
       

      The script inside is editable.

       
      Enjoy...
       
      Many thanks to the comrade SunKi for help with creating the script.
       
       
       
       
       
      Best thanks - click "Rate File".
       
    • By blxkspell
      Hey!
      As I have 3 Monitors connected, my RX 570 gets arround 50°C while ideling/ web browsing etc. The problem is, that this temp is apparently just the threshold, when the fans start to spin. So the fans start spinning for a minute then they stop for a while again... This is very annoying for me as the rest of my hackintosh is nearly quiet (SSD, 120mm low RPM cpu fan, nearly silent PSU,...), especially when Im using the pc to revise for school. Does somebody know wether its possible to "change" the threshold till the fans start spinning? Like it would probably not be a problem for the gpu at all, if the temp rises to 55°C but therefore be soundless....
       
       
    • By kylon
      Cloud Clover Editor allows you to manage Clover EFI and Ozmosis configs everywhere!
       
       
      WEB
      Open Cloud Clover Editor
       
      APP (MacOS - Discontinued)
      Clover flying editor ( Micky1979 )
       
       
       
       
      Sources: https://bitbucket.org/kylon/cloud-clover-editor-cce/overview


      To run CCE at home you will need:
       
      An HTTP server (Apache, Nginx, ...) PHP 5.3.3+ (latest PHP version is always recommended for better performances/security) Sqlite3 PHP extension  
       
      Some Features:
       
      Edit text in tables:
      Editable fields are marked with a text cursor.
      Double click, or tap and hold, to open the inline editor.
      You can now press Enter or click outside to save your changes.
       
       
      Tri-state checkboxes:
      There are 3 possible states for a checkbox: Checked, indeterminate and unchecked.
       
      Checked: Value is true;
      Indeterminate: Value is false;
      Unchecked: Value is not set (ie, removed from plist)
       
      Working with multiple configs:
      The right sidebar is your multitasking menu.
      Use the add button to create a new config and add it to the list.
      You can safely switch between all your configs, no changes will be lost.
      You can mix Clover EFI and Ozmosis configs.


      Config Upgrade feature:
      In the case you are using old configuration options, CCE gives you the ability to automatically upgrade your config.
       
       
      Copy to:
      You can copy patches between your configs (you will love this when you need to copy kernel and kext patches ;D ).
      You will find a yellow copy icon if that field does support the copyTo feature.
       
       
      Ozmosis Mode:
      A new setting, Cloud Clover Editor Mode, is now added in Cloud Clover Editor -> CCE Settings.
      This will let you switch from Clover EFI to Ozmosis mode.
      Changes to your current file will be lost.
       
       
      CCE Bank 2.0:
      Thanks to @cecekpawon for the idea.
       
      CCE Bank is a database where you can save/load Clover EFI and Ozmosis configs.
      You can protect your config from unwanted modifications or make a publicly editable config.
       
      To save a config in CCE Bank you only need to check the "Save to CCE Bank" option.
       
      Tick the box generate a new CID, if you don t have one.
       
      A CID (CCE ID) acts like a container and it is your authentication key.
      You can group multiple configs under the same CID or generate as many CIDs as you like.
       
      Edit Modes:
      Public: Anyone can make modifications, only the owner can change its settings. Private: Only the owner can make modifications and change its settings. MyBank: Only the owner can see this config, make modifications or change its settings.  
      MyBank is your private area.
      Change the 'view mode' to switch between the public bank and your personal bank.
       
      To manage your currently loaded config, go to Cloud Clover Editor -> Open config -> click the settings button.
       
       
      Notes:
      Locked/Private configs are marked with a padlock MyBank configs are only visibile in your private area Only the owner of a locked config can save the modifications in CCE Bank, hower you are free to do whatever you want in CCE and download the modified config If you loose your CID you can just reply or pm me No account is required!  
       
      Main Features:
      Left sidebar does support touch swipe on touch devices.
      No changes will be lost on page reload.
       
       
      Credits
      mackie100 - took some ideas from his app Clover EFI dev team Eric Slivka - new serial number Virtual1 - new serial number cecekpawon - PHP 5.3.3 patch, , help with the ACPI Loader Mode flag and more Micky1979 - Clover flying editor crusher. - Help with the ACPI Loader Mode flag Download-Fritz - Help with the ACPI Loader Mode flag Pavo - Ozmosis fields and values stehor - Ozmosis fields and values Sherlocks - General help and support gujiangjiang - General help and support Please let me know if i forgot you!
    • By d2a
      So I'm finally joining the grown-ups and trying to set up a new(ish) hack. In the past I've used legacy Clover with my old Gigabyte board and thought I knew what I was doing. But I've been trying to get a UEFI Clover-based install to work and it's going nowhere.
       
      My new system (listed as SysB in sig) is a Gigabyte Z97X-UD3H-BK rev1.1 with firmware F6, an i7 4790K CPU and 4x4GB Corsair 1866MHz. I have the firmware settings set as per various guides and thought this should be a pretty painless transition...
       
      I have successfully run the installer for El Cap several times, but can't get the machine to boot reliably - it seems to change behaviour each boot. Sometimes boot hangs at the Gigabyte logo after choosing boot volume via F12, sometimes it boots to clover but displays no bootable drives, sometimes displays ElCap SSD in Clover but wont boot from it with kernel cache error, and occasionally it will boot all the way.
       
      What I'd like to know is:
       
      Should I update the mobo firmware to the latest version? This board has two more recent Bios software downloads, but they wont allow me to drop back to the version currently installed. I'm nervous to update unless this is likely to be the culprit. Is this just a UEFI issue? If the simple answer is just go legacy mode, maybe I should just avoid the issue... FInally, does anyone else have a working clover install on this board they could share with me? I think I've got it set up as it should be but the strange inconsistent boot behaviour makes me wonder... Thanks
×