Welcome to the MacNN Forums.

newtech · 05:31 PM

My Mac pro MLB has atypical firmware on it. The EFI firmware updaters wont recognise the board preventing updates. Any help appreciated.

Model Name: Mac *( should read Mac Pro )*
Model Identifier: M43ADP1,1 *(should read MacPro1,1)*
Processor Speed: 3.0 GHz
Number Of Processors: 2
Total Number Of Cores: 8
L2 Cache (per processor): 8 MB
Memory: 4 GB
Bus Speed: 1.33 GHz
Boot ROM Version: AAPLM431.004E.B00 *( should start MP....)*
SMC Version: 1.7f0
Serial Number: System Serial#

FTR

Processors are overclocked Xeon E5340 engineering samples.

Macadvo · Dec 20, 2007, 01:50 PM

Try replacing the original processors, applying the firmware update then re-installing the overclocked engineering samples. If this works, my payment for the tech advice is 2 (two) x Xeon E5340 engineering samples

newtech · 02:07 PM

Sorry, only have one spare E5340 ES ( the other two are on the board ). Processors are NOT the issue. The issue is the firmware update app looks at the the machine ID string and Boot ROM version and concludes that the machine is not a Mac Pro, this all happens in the GUI ( as far as I have been able see ).

My current avenue of investigation is using the executable module via the console, however I am not 100% certain I have all the needed parameters needed to pass to the .exe to successfully do a blind flash.

Alternately, spoofing the ID string and Boot ROM version "might" be possible, if in fact they are not being read directly from the flash ROM. Even for a programmer tracing undocumented code is time consuming and a practice of getting into someone else's head.

mduell · Dec 20, 2007, 05:27 PM

I want to know how you overclocked your Xeons with the Mac Pro firmware. Even if the engineering samples are unlocked, you still need to tell the firmware to use a higher multiplier.

newtech · Dec 20, 2007, 05:43 PM

By holding the BSEL2 line high ( tape over the land ) on Xeon E53X0 chips, FSB is forced from 1066 to 1333 which also ups the clock frequency by 25% as well ( ie 2.4 -> 3.0 ).

so...

E5310 1.60 -> 2.00

E5320 1.86 -> 2.33

E5330 2.13 -> 2.66

E5340 2.40 -> 3.0

There are windows utilities that will do a hardware based BSEL2 overclock as well but they do not hold through a reboot.

E53X5 = 1333 FSB nominal

E53X0 = 1066 FSB nominal, 1333 BSEL2 overclocked

nagal · Jan 3, 2008, 12:59 AM

Having the exact same issue. Did you ever find a fix?

seanc · Jan 3, 2008, 03:25 AM

Nagal, are you also running engineering samples of CPUs in your Mac Pro? Have you also overclocked it?
It would be good to see if there are any similarities/differences between yours and Newtechs hardware so that we can narrow it down to something.

Macadvo · Jan 3, 2008, 06:10 AM

I've seen this thread on another forum, can't remember which now grrr. The concensus of opinion there was that the OP had somehow managed to get hold of one of the original developers boards and that was why he couldn't flash the EFI.

Hope I'm wrong and he gets it sorted though

nagal · Jan 3, 2008, 09:58 AM

I am using Engineering Samples but no over clocking. I was planning on doing the BSEL mod later on just have not gotten around to it yet. Being a computer guy in general for a long time now, I would hate to think that not-using "Apple" CPUs would cause this problem. As far as my logic board it better not be a developers board as I bought it from an Apple Reseller as a new part.

Just like the OP, I have managed to piece together my MacPro from parts. At the end of the day, it is a minor thing if the firmware never updates as I have not encountered any issues that I know of.

newtech · 10:07 AM

My boot ROM is closely related to the ROM in the intel developer box ( ie ADP2,1 ) and there also is some evidence for another similar MachineID ( M42ADP1,1 vs my M43ADP1,1). The MachineID and MachineName ID strings can be altered as to what System Profiler sees but it is not clear if the EFI update actually checks ROM or OS global values from RAM.

I have a second MLB from another source but am reluctant to do a complete tear down until I feel I have exhausted all avenues that have reasonable chance of making this board a normal Mac pro.

nagal · Jan 3, 2008, 10:13 AM

I also have that exact same Model Identifier M43ADP1,1. I wonder if we got our logic boards from the same place. I got mine from Mac-Pro.com. I was waiting to contact them about this until I had more info but I am going to go ahead and email them and see if they have any idea. They are a great place as I have bought from them before and never had issues.

EDIT:

I did try using the Apple Firmware Restore CD but it does not work. I get the "Starting Symboi" message with the progress bar but once it hits 100% screens go blank and then nothing.

newtech · Jan 3, 2008, 10:27 AM

Same source, I have been waiting for Ed to return from vacation to discuss with him.

nagal · Jan 3, 2008, 11:01 AM

Originally Posted by newtech

Same source, I have been waiting for Ed to return from vacation to discuss with him.

Now that makes things very interesting. Going to hit him up with an email right now just so he knows it is not an isolated case.

seanc · Jan 3, 2008, 12:21 PM

So have you guys been building Mac Pros from parts then? Which means these aren't normal retail Mac Pros...

nagal · Jan 3, 2008, 01:00 PM

Originally Posted by seanc

So have you guys been building Mac Pros from parts then? Which means these aren't normal retail Mac Pros...

Correct but what is a retail Mac Pro except a bunch of Apple parts?

The BootRom is part of the logic board and *should* have nothing to due with the CPUs. Why it is not a Mac Pro BootRom is the odd thing because it is a Mac Pro logic board and *should* have a Mac Pro BootRom. There is the possibility we got some bogus boards as we got them from the same source and we are having the same issue and this is what I am leaning towards right now.

To me this is half the fun of build a system to tackle these really odd problems

At the end of the day my non-retail MacPro is running great.

For the record here are all the genuine Apple Parts I am using.

Mac Pro Case
Mac Pro Power Supply
Mac Pro Logicboard
Mac Pro memory riser cards
Mac Pro 7300GT Video Card
Leopard Retail

Non-Apple Parts
3 hard drives (used my old PC ones all SATA Seagates 250GB, two 320GB)
DVD-RW (LiteOn from my PC burns and reads CDs/DVDs fine in the OS X)
Memory - got Apple Certified RAM from Other World Computing
CPUs - Using Clovertown Engineer Samples 2.4 GHz 1066 FSB.

If you are wondering why I did this? 8 core Mac Pro with 8 GB RAM for $2700 and I LOVE playing with computers. This being my first Mac opens a whole new world of computer building geekness to me

seanc · Jan 3, 2008, 01:21 PM

Fair enough, the reason I had asked is because it didn't say anywhere before that these weren't retail Mac Pros like I had thought they were, or that they had been built from parts.

I would contact the supplier, as you are already trying to do and try and find out where the boards came from.

newtech · Jan 3, 2008, 03:40 PM

Further facts...

The boards are IDENTICAL and have the same Apple part number as "retail" Mac Pros and in fact sold under the understanding that they ARE Mac Pro MLB. The only thing that prevents them from being EFI updated is that the available EFI update is written to prevent cross flashing ( fair enough ), But I must maintain that this does not constitute cross flashing in any way as it is IDENTICAL Apple built hardware regardless of provenance.

nagal · Jan 3, 2008, 03:50 PM

Originally Posted by newtech

Further facts...

The boards are IDENTICAL and have the same Apple part number as "retail" Mac Pros and in fact sold under the understanding that they ARE Mac Pro MLB. The only thing that prevents them from being EFI updated is that the available EFI update is written to prevent cross flashing ( fair enough ), But I must maintain that this does not constitute cross flashing in any way as it is IDENTICAL Apple built hardware regardless of provenance.

It is interesting Apple would do this, they really should use different part numbers. I do not know about you but I got my reply from Mac-Pro.com "We have no control over Apple's firmware. Sorry, nothing we can do." I find the wording very interesting.

I agree that if these are actually Mac Pro boards they should be able to have their firmware updated. I know my board cames with a 90 day warranty so maybe it is time to place a call to Apple to try and get an official word on the BootRom even if it is go suck an egg

I am still very happy with my system and performance but its the tinker in me that is wanting to find a solution.

newtech · Jan 3, 2008, 04:35 PM

My theory, based on talking to the staff at Mac-Pro, is that these MLB started life in Apples Software test lab sometime between the SDK ( ADP2,1 ) machines being seeded to registered developers and the intro of the MacPro1,1 and would have been the seeded SDK but for low availability and high cost of 51XX processors prior to the MP launch.

Macadvo · Jan 3, 2008, 06:37 PM

OK as you built these systems from "official" Mac Pro parts I have to say I think the problem may be that apple only gives "official" serials to those logic boards that come in complete systems. I didn't even know mac-pro.com existed else I may have built my own from scratch lol.

Best bet is to hassle mac-pro.com for an answer and see how you do, next best thing would be to try and find a helpful "Apple" repair center who may be able to give you a flash for these boards, though I doubt it.

Best of luck guys!

goMac · Jan 3, 2008, 06:57 PM

Honestly, if someone sold me something they claimed was a Mac Pro board, and then after I bought it told me it was a pre-release board, I'd demand they exchange it for a real Mac Pro board.

nagal · Jan 4, 2008, 11:33 AM

Originally Posted by goMac

Honestly, if someone sold me something they claimed was a Mac Pro board, and then after I bought it told me it was a pre-release board, I'd demand they exchange it for a real Mac Pro board.

I agree with you 100% BUT if in the next few days I can find a fix on my own then I am not going to worry. I really do not want to be without a computer for a week or so it would take to return the logic board and then get the replacement.

Stolfi1 · Jan 15, 2008, 03:07 PM

Hmmm now I am worried about my board

newtech · 08:07 PM

Originally Posted by Stolfi1

Hmmm now I am worried about my board

Check the sticker on the board ( between the memory riser slots ), it will say the firmware and SMC revision numbers, an EFI over 004x and SMC over 1.7f0 is good as it will be later than the M43ADP1,1 developer boards.

nagal · Jan 15, 2008, 07:05 PM

Originally Posted by newtech

Check the sticker on the board ( between the memory riser slots ), it will say the firmware and SMC revision numbers, an EFI over 04xx and SMC over 1.7f0 is good as it will be later than the M43ADP1,1 developer boards.

Weird, my board does not have that sticker as I just pulled all the number off it for another reason. Mine had a sticker that said PBA D37625-501

newtech · Jan 15, 2008, 08:00 PM

My backup board ( production ) has three stickers between the riser slots...

[ PBA D37652-501 ] [ EFI: 005C ] [ QAN 6834357 }
center ->[ SMC 1.7f8 }

Did not note the stickers markings on the M43 board before installing the cage.

Middle sticker seems to indicate Boot ROM MP11.005C.xxxx and SMC firmware 1.7f8 are on the board in the flash ROM.

Got the backup board after 90% build of prime board and is an "as is/condition unknown" that I got from eBay so I am reluctant to tear down and use it, unless prime board fails.

nagal · Jan 17, 2008, 07:23 PM

Originally Posted by newtech

My backup board ( production ) has three stickers between the riser slots...

[ PBA D37652-501 ] [ EFI: 005C ] [ QAN 6834357 }
center ->[ SMC 1.7f8 }

Did not note the stickers markings on the M43 board before installing the cage.

Middle sticker seems to indicate Boot ROM MP11.005C.xxxx and SMC firmware 1.7f8 are on the board in the flash ROM.

Got the backup board after 90% build of prime board and is an "as is/condition unknown" that I got from eBay so I am reluctant to tear down and use it, unless prime board fails.

I'll test that backup board for ya