I told him I would continue to monitor it as I've read that the fix is temporary also. I've got a case number to call back if it does.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MacBook Pro EFI Firmware Update 1.7 Problems
- Thread starter jlamarp
- Start date
- Sort by reaction score
I told him I would continue to monitor it as I've read that the fix is temporary also. I've got a case number to call back if it does.
It's not luck. If you buy a Macbook and update to the 1.7 firmware you will have no issues. The issues come along when you try to upgrade your hard drive with 3rd party drives which Apple's firmware update does not support as was stated. I just bought the new 13"MBP 2.53 CTO with Apple's SSD drive and no issues here after the firmware update.
There are posts from people with stock drives who are having problems after updating the firmware.
I know I havnt tried to install a 3rd party hdd on my 2.8ghz mbp but after reading through this thread I'm coming to the conclusion that 13" and lower end 15" mbp (same internals with 3mb cache logic boards) have these issues.
I know that the 17" and higher end 15" mbp have identical internal specs with 6mb cache. Maybe it's a hdd controller on the lower end mbp issue?
I know that the 17" and higher end 15" mbp have identical internal specs with 6mb cache. Maybe it's a hdd controller on the lower end mbp issue?
Well, there shouldn't be. We're all using the same machine, same hardware, same OS, same components coming from the same vendor, Apple. I didn't have any problems and many others here haven't either. If anyone having issues with the firmware update with the stock drives may have not followed the firmware updater instructions properly which happens often here. Too many times people take firmware updaters lightly and treat them like a standard software update which they are not.
Yes, it's possible to have legitimate issues with some things, but I wish some of you here would take responsibility for things that go wrong, ever heard of user error? You guys are so quick to defend another forum member because Apple is a big evil giant. You're not sitting in front of the computer with that forum member so you have no idea what they've done that may have created their issues.
I guess I'm going to have to try installing a 3rd party hdd for testing before my 2 week return date is up.
Seeing that some people with 13" mbp has no issues maybe it depends on certain manufacture hdd brands and versions.
Just because you and others don't have a problem with the update doesn't mean it's impossible for people with stock drives to have a problem. Spend some time reading posts on this forum and other forums from people who have stock drives and whose systems have suffered from beachballing and intermittent slowdowns.
User error is possible for some, but not very likely for most, given the number of posts from people with problems immediately after the update. I think there are posts from people with MBPs which came with version 1.7 already installed who are having system slowdowns.
Did I accuse Apple of anything? Sometimes, updates are released with problems that don't surface until they're in the field. There's nothing evil about that.
I finished installing a 320gb hitachi travelstar 7200rpm hdd and JUST finished a new osx install. No problems still whatsoever. I guess I'm super lucky?
Corsair P128
I just ordered the Corsair P128. Does anyone have this or the P256 inside the most recent MBPs? Is it working ok with firmware 1.7?
I haven't upgraded my 13" MBP's firmware yet as I was using it with a HD. I would like to update to 1.7 to take advantage of 3Gbps for my new SSD, but not if the system is going to freeze randomly like many are unfortunately experiencing...
I just ordered the Corsair P128. Does anyone have this or the P256 inside the most recent MBPs? Is it working ok with firmware 1.7?
I haven't upgraded my 13" MBP's firmware yet as I was using it with a HD. I would like to update to 1.7 to take advantage of 3Gbps for my new SSD, but not if the system is going to freeze randomly like many are unfortunately experiencing...
Sorry guys I spoke WAY too soon. My hitachi travelstar 320gb 7200rpm is acting up now with the color wheels. Started doing this when I was transferring files from fw from my 1tb.
Finally a mbp that has eveything I love, awesome perfect display, no loud fan noises, very cool operation.. but a SATA-I controller?!?
I hope it can be fixed with a new efi firmware update in the future. Because I want to upgrade to an SSD drive in the future. Or if my current hdd crashes what do I do? I guess I'm not lucky at all!!
Finally a mbp that has eveything I love, awesome perfect display, no loud fan noises, very cool operation.. but a SATA-I controller?!?
I hope it can be fixed with a new efi firmware update in the future. Because I want to upgrade to an SSD drive in the future. Or if my current hdd crashes what do I do? I guess I'm not lucky at all!!
I'd say no...
I like thousands of others have been following this thing since the efi 1.7 release. I have not heard of anyone having this particular problem with the white macbook. The EFI 1.7 update is only for the 13" and 15" MBP.
The sad reality is the white macbook is not in the PRO class so you can upgrade to your liking with not problems, and probably have SATA-2 natively. I guess "PRO" nowadays means, you'll get what we give you and you'll give us good money for it, now shut up and like it.
I like thousands of others have been following this thing since the efi 1.7 release. I have not heard of anyone having this particular problem with the white macbook. The EFI 1.7 update is only for the 13" and 15" MBP.
The sad reality is the white macbook is not in the PRO class so you can upgrade to your liking with not problems, and probably have SATA-2 natively. I guess "PRO" nowadays means, you'll get what we give you and you'll give us good money for it, now shut up and like it.
Almost 16,000 views and near 200 posts. I wonder if anyone from Apple has read this and is looking for a remedy? I know there are other threads for the same problem.