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, MacBook Pro Keyboard Firmware Update 1.0
- Thread starter cwalex18
- Start date
- Sort by reaction score
I hope this hasn't been posted already, but I noticed that the update doesn't concern Core Duo machines. Out of curiosity, would it have something to do with Core 2 Duo being 64-bit and the drivers for the keyboard not being as...'good' for lack of a better term than 32-bit ones?
Not that it matters a great deal, my keyboard works fine
Although I wish Apple would release a patch for Tiger...I mean, the latest revision of Tiger is only, what, 4 months old now?
india349
Not that it matters a great deal, my keyboard works fine
Although I wish Apple would release a patch for Tiger...I mean, the latest revision of Tiger is only, what, 4 months old now?
india349
Removal of battery drops the CPU speed down, thus less heat. More info here:
https://forums.macrumors.com/threads/414106/
very confused
this was fixed two months ago...
and it worked just fine. it's not available as an update for me for that reason I assume. this exact problem was fixed on a firmware update I believe around christmas. doesn't anyone remember?:|
this was fixed two months ago...
and it worked just fine. it's not available as an update for me for that reason I assume. this exact problem was fixed on a firmware update I believe around christmas. doesn't anyone remember?:|
So here's the dilemma. Stick with Tiger and lose the first key stroke after keyboard inactivity or reinstall Leopard, fix the keyboard issue but lose airport connectivity. Hmmm.....
Thanks Apple for finding a fix.
F-U Apple for making it for Leopard only.
Most people said it's a Leopard only issue.
You can always boot into Leopard (firewire drive, target disk mode of a leopard computer, etc), download the update manually, and run it.
I have severe drop outs in Tiger with the older Airport Extreme(g), I agree with ya 110%
F U
Had that problem at a location that had Airport Extreme (g), updating the base station firmware solves that problem.
It's good that they fixed the issue, but if you ask me Apple should be ashamed that it was an issue at all. After all, they control both the hardware and the software, which is supposed to prevent problems like these. I mean, we're talking about the built-in keyboard, not some exotic 3rd party add-on. And keyboards are only the primary computer input device since before Apple even existed as a company. How they could screw up something as basic as that (see also the other fix, were the keyboard become unresponsive at random times) is really beyond me
Actually, since switching to intel, within 2 years, there has been at least 4 different type of hardware (perhaps more).
- Core Duo
- Core 2 Duo
- Core 2 Duo on Santa Rosa
- Xeon
I am assuming each processor / hardware combination would need its own firmware, but looks like Apple is working on it.
Err, we're talking about keyboards here. Built-in keyboards that Apple selected to go with their own laptops. It would be a pretty messed up design if they have to tweak or rewrite drivers or firmware for keyboard support every time they switched CPU / chipsets (not to mention that the initial C2D on 945G chipsets were a drop-in replacements for the CD).
I am all up to date, but thank you for reminding me.I am not gonna shell out 100+ for an OS that I have no faith in.This should be fixed irregardless of OS.A built in keyboard is a core hardware issue and its well documented on Apples forums that 10.4 is affected.Apple is way too arrogant as of late and its only getting worse as they gain market share.
appy!
installed on MBP's 15" and 17" C2D without a problem. I thought Apple was not going to solve this one anymore, but appily they did
installed on MBP's 15" and 17" C2D without a problem. I thought Apple was not going to solve this one anymore, but appily they did
Hi, this is just a firmware update, that means it should not be OS dependent.
Now, I understand that apple may want to lock this to leopard only just to make some people upgrade (companies do that all the time), but since this is just firmware it SHOULD be able to install under tiger.
My point? Last time I installed a firmware in my MBP by changing the version string in a plist file (forgot which one) and it worked perfectly, it may be the case for this one too.
Note that I haven't tested it, and it may not be safe at all, if somebody out there feels confident enough give it a try.
Cya, btw I faked the version string from leopard to tiger, dunno if it'll work the other way around
cya
Now, I understand that apple may want to lock this to leopard only just to make some people upgrade (companies do that all the time), but since this is just firmware it SHOULD be able to install under tiger.
My point? Last time I installed a firmware in my MBP by changing the version string in a plist file (forgot which one) and it worked perfectly, it may be the case for this one too.
Note that I haven't tested it, and it may not be safe at all, if somebody out there feels confident enough give it a try.
Cya, btw I faked the version string from leopard to tiger, dunno if it'll work the other way around
cya
I can trash the "Built-in Keyboard Firmware Update.app" from my utilities folder once the update is complete, correct? Or is there a reason to keep it?
This is great and all, but the bare cold facts are that it gets us no closer to a release date for the next generation MBP! Honestly whats going with that?
Not here. I run in that mode every day and bring the machine in and out of sleep multiple times a day. It worked fine before and continues to work fine after the update to which you refer.
I figured this as well, but the download is in a .pkg format that Tiger doesn't understand.
Fortunately for science, 'most' doesn't matter when falsifying a hypothesis.
Since we're talking about Tiger users, let's not encourage them to pirate Leopard for a keybaord update.
I use both and have plenty of reasons not to upgrade to Leopard on a few machines - it ain't quite out of 'public beta' yet. Here's hoping .3 really kicks.
But it's not Leopard only issue. It's been happening to me since I bought my MBP in 11/2006 - way before Leopard's time.
Why should I have to upgrade (or downgrade according to how you look at it) to Leopard (which STILL is unstable on my MBP) to get a fix? I thought I was dealing with Apple, not Microsoft.
Just signed it.