Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I read the instructions carefully, and was expecting the loud tone, but it still scared the bejeezus out of me! I was all happy like, "Yay! Flashing li...BONNNNGGGGGG!"

Last Spring, I updated a lab of 14 machines while a class went on in the room next door, and the connecting door was open. :)

I went around the room downloading the update and rebooting as each machine finished. It was quite funny when the professor in the room next door came in after the 8th "BONNNGGG!" in under a minute.

Gotta love them firmware updates.
 
"Fixes Fan Behaviour"

It's about time Apple did something to bring civility to user forums :cool:
 
Rats.

Was hoping this firmware update might fix my "fan behavior". Whenever I turn on my 2 month old Mac Pro, the fans kick into high gear for about 5 seconds before the startup chime kicks in and the fans spin down to normal.

Other than this startup issue, the computer runs normally.

Anyone else experience this? Is it a reported glitch? Maybe a bad power supply?
 
Rats.

Was hoping this firmware update might fix my "fan behavior". Whenever I turn on my 2 month old Mac Pro, the fans kick into high gear for about 5 seconds before the startup chime kicks in and the fans spin down to normal.

Other than this startup issue, the computer runs normally.

Anyone else experience this? Is it a reported glitch? Maybe a bad power supply?

Have you got a ATI 1900 card in it. They're very noisy when your first power on until the fan management stuff kicks in. That's normal.
 
Rats.

Was hoping this firmware update might fix my "fan behavior". Whenever I turn on my 2 month old Mac Pro, the fans kick into high gear for about 5 seconds before the startup chime kicks in and the fans spin down to normal.

Other than this startup issue, the computer runs normally.

Anyone else experience this? Is it a reported glitch? Maybe a bad power supply?

No it is the Radeon 1900XT, is is a powerfull but VERY NOISI gfx-card. If you play games, they spin very fast and make noise. Same when you startup your MacPro, it is no a bug.

Nvidia 7300 is very silent, it depends on what you want.
 
yowza am I nervous! I had to send my MBP in to applecare after the last firmware update...and it's out of warranty now. Would apple still cover it out of warranty if there is an issue?
 
Thanks Captian Obvious, what do you think EFI is? Successor to BIOS.

Actually, it's a replacement for, not a successor to. It's closer in reality to OpenFirmware, popular on workstations for many, many years. PPC macs used OF since the release of the PCI Power Macs.

Many of us were cheesed off at the switch, as OF is actually very versatile and fun.
 
Some might have had their machine bricked maybe?

I'm wondering about an iMac 17 here... Did the restart... Held button in... Got flashing light... Heard tone... Progress bar shows about 5% maybe and that's it... been 1/2 hour now.

Dunno what a forced restart might do if it's part way through the update.

[Edit]: I re-ran it and it seems to be taking ok. Unplugged external devices this time. Guess that was the problem. Dunno.
 
Firmware update 1.1: An unexpected error occured (0)

I seem to be having this problem, which is the first time I've ever had a FW update issue. My 2.16 C2D MacBook is popping up that error when I try to shut down for the update. I've tried all the usual: PRAM zap, permissions, swapping out RAM, etc. No such luck.

I started a thread on Apple's support forum:

http://discussions.apple.com/thread.jspa?threadID=1154109
 
My 2.16 C2D MacBook is popping up that error when I try to shut down for the update.

Just hold down the power button and it will turn off.

I downloaded the patch but didn't read the instructions and just rebooted. The patch popped up again right after the reboot.

I turned it off and help the start button for something like 15 seconds and it beeped and worked.
 
Intel Macs use EFI, not BIOS.

Thanks Captian Obvious, what do you think EFI is? Successor to BIOS.

a) It's 'Captain'.
b) He was answering someone else's question.
c) Since when was it official policy to be rude?
d) EFI is not 'the successor' to BIOS, many consider it as being an improvement and the fact that it can have legacy capability with supporting BIOS, but it's not that simple.

(continues reading thread)
Well this issue was covered quite well by others before me

Never the less, the problems seem to be happening mostly to the MBP C2D 2.16/2.33's?

Oh, also some MacBooks...
That's the impression i'm getting from some of the posters...

edit: apparently someone has found the root of the problem, from applecare forums:

A possible solution (or at least a reason) appears in this thread:

http://forums.macresource.com/read/1/360674

As celliot's post notes:

I did some checking. It appears to be a disk format problem. For those who installed a new disk or reformatted the old. Notice that we get the error message when the utility wants to restart.

Go to disk util. Click on the drive name, then go to the partitions tab. If you then click on options you will see something interesting. three options:

- GUID partition table- use the disk to start up an Intel based Macintosh computer

- Apple Partition Map- use the disk to start up a Power PC based Macintosh computer or to use the disk as a non-startup disk with any Mac

- Master boot record- use the disk to start up DOS. . . . . . .

Anyway, it appears that the way the disk was formatted could impact the disk startup and that might be the problem we are having?
 
This is a little bit off-topic but it relates to the SMC update http://docs.info.apple.com/article.html?artnum=303880. My version is 1.14f5 and the latest version on there is 1.5f10, but when I try to update it, it says the latest version is already installed. My version of the MBP is the 17" 2.33Ghz version from December 2006. Thanks!
Actually it doesn't even list the latest version for yours. It just says "-" where it normally would. Read more closely.
 
My version is 1.14f5 and the latest version on there is 1.5f10, but when I try to update it, it says the latest version is already installed. My version of the MBP is the 17" 2.33Ghz version from December 2006. Thanks!

Your's is the MacBook Pro (Core 2 Duo 17-inch) not the standard. No updates are needed.
 
I got the "unexpected error ocurred (0)" message as well but after a bit of thinking I realised what was causing it (for me anyway). I remembered deleting the 200mb EFI partition when I installed Windows Vista. Obviously this isn't good for the EFI firmware updater as it would need this partition. My first go at rectifying this was to restore the deleted partition but it seemed risky having to use fdisk.

I then found a support page on Apple: Firmware update for Intel-based Mac does not install with non-GUID partition scheme
Using the first solution, I was able to update my EFI by starting up with a properly formated Mac OS X install from an external drive!
 
I got the "unexpected error ocurred (0)" message as well but after a bit of thinking I realised what was causing it (for me anyway). I remembered deleting the 200mb EFI partition when I installed Windows Vista. Obviously this isn't good for the EFI firmware updater as it would need this partition. My first go at rectifying this was to restore the deleted partition but it seemed risky having to use fdisk.

I then found a support page on Apple: Firmware update for Intel-based Mac does not install with non-GUID partition scheme
Using the first solution, I was able to update my EFI by starting up with a properly formated Mac OS X install from an external drive!

Mine is the GUID partition scheme thing. <.<
 
error 0 solved (for me)

The GUID partition was my issue too. I did a mirror back up, repartitioned and restored and the firmware update installed fine. I don't know how I ever got the old style partition as I have not changed the disk since buying my 17" MBP 2.33 last November.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.