Issue with BESL Mod

Discussion in 'Mac Pro' started by strwrsfrk, May 8, 2012.

  1. strwrsfrk, May 8, 2012
    Last edited: May 8, 2012

    macrumors regular

    Mar 1, 2011
    Arlington, VA, USA
    I have a Mac Pro 1,1, which, for the sake of experimentation, I decided to perform the BESL Mod with 2 1.86GHz L5320 Xeons ( Maybe I should have posted in that thread, but I didn't want to post at the back-end of an old thread.

    Basically, the CPUs went in fine. I've performed Mac Pro CPU surgery dozens of times, and there were no surprises. Got the electrical tape on the contacts, replaced the CPUs, booted on the first try. The issue arises when I look at the Hardware Monitor window. It should say: "Nominal clock frequency: 1.86 GHz" and "Clock Frequency: 2.33 GHz." Instead I see 1.9GHz and 1.9GHz, respectively.

    Geekbench tests are returning scores between 8500 and 9100, which seems to be in the correct range for the mod, so I'm very confused.

    Reset PRAM, reapplied BESL Mod and reinstalled CPUs, reinstalled OSX Lion and Hardware Monitor. Even MiniStat2 shows 1.9GHz. Still all the same info.

    Any ideas? Thanks!

    EDIT: Under processor ID I see: "GenuineIntel Family 6 Model 15 Stepping 7." All other posts show "GenuineIntel Family 6 Model 15 Stepping 11." Could this have something to do with it? Is there anything I can do?

    Attached Files:

  2. macrumors 68040


    Dec 7, 2009
    It reads FSB as 1.1GHz too. As it seems to be only read-out issue (your GB score is about right for 2.33 GHz) try reset PRAM and SMC and see if it would change anything.
    You can also upgrade EFI to 2.1 to get rid of "unknown" CPU in ASP (-> netkas forum).
  3. macrumors 601


    Jul 3, 2011
    if your geek bench is 9k the mod worked. Now you just need to get everything to read correctly
  4. thread starter macrumors regular

    Mar 1, 2011
    Arlington, VA, USA
    I've updated to 2,1 for all the x5355 builds; did not know it would work for this as well. Thanks.

    I've reset the PRAM and SMC about a dozen times each to no avail. It's a real bummer.

    Geekbench is showing 9200+ after the 2,1 update, which is great. So the numbers do seem right. It's just annoying. If anyone reads this and ever finds a solution or has an idea, please quote me so i'm notified. Thanks in advance, and thanks to 666sheep and GermanyChris.

Share This Page