10.4.3 killed my keyboard

I upgraded to Tiger following the procedures provided by Ken Stone on the LA FCP site. My MacAlly keyboard worked fine in 10.4 but the 4.3 upgrade disabled it. Now it only works with my Mac keyboard with the too short cable that is not set up for FCP. Any ideas guys? Desperation is setting in. Thanks.

Hi Jarkko,
From your info it does indeed sound like the battery is dead. (Sorry)
Or... it was killed, if OS 10.4.3. indeed kills batteries.
In any case, 351 cycles is probably normal to be pretty used up, but the real giveaway is the remaining capacity: 0. As long as there is some remaining capacity, the battery at least has something in it.
My old 4 year old battery with 549 cycles says 333 mAh, which is enough to power my TiBook for about 20 seconds (or less).
So if yours says zero, it's dead. You might leave it plugged in for a long time to see if that makes any difference, but you've probably already tried that.
The question is, what made it go dead? Did it get worse and worse then die, or did it suddenly go dead within days after upgrading to 10.4.3?
If you do not plan on keeping the PB, then you can still use it plugged in. A new battery will cost around $140. (yep, they are not cheap). If you plan to sell it, though, you'll probably need to get a battery first.
Hope this is helpful.

Similar Messages

Killed Helix Keyboard

hi everyone, this is a desparate post from Singapore. Accidentally spilled coffee on my 2 weeks old Helix and killed my keyboard almost instantaneously. Quotation from Service centre for repair is SGD1200 .. a really hefty price to pay for a keyboard repair. Tried the option to buy a new keyboard but Lenovo don't seem to sell them in parts.
Anyone has encountered similar situation and found a more economical way to resolve? Thank you and praying hard that i get some help here. thank you.

Same happened to me... (with tea, but thankfully without suger)
1. You must decide if you are able/willing to disassemble and replace the damaged FRU.
For this, please consult the factory videos:
http://service.lenovo.partner-management.com/content/CourseWarePublic/18124/player.html
and the Hardware Maintenance Manual:
http://support.lenovo.com/en_US/detail.page?DocID=UM017304
2. If yes, you have to check which parts are damaged: is it only the keyboard, or others like Keyboard Dock I/O Board?
Then download the Helix FRU list (Field Replaceable Unit):
http://download.lenovo.com/parts/ThinkPad/helix_fru_bom_20130520.pdf
You can find a description of the Keyboard Dock:
http://support.lenovo.com/en_US/product-and-parts/detail.page?DocID=PD026782
Here is also a link to the Online Shop (in my case, it was IBM Part Sales Germany) My keyboard had only problems with 3 keys, so I just ordered a new one. The shop shows a delivery time of up to 4 weeks, but I was told that they expect the German keyboard for Oct-16.
Price: 145 EUR + Tax + Shipping.
For info: If the I/O Board is OK and only the Keyboard makes trouble, you can use the Dock and connect in parallel a Bluetooth Keyboard meanwhile...
Hope it helps

These power settings will kill your keyboard dock

This scenario will kill the power in your keyboard dock, rendering it lifeless:
* Go to the "Lenovo Settings" Windows 8 app
* Enable "30 Day Standby" (may not matter)
* "Battery Stretch" On or Off (doesn't matter)
* Go to "Battery Health Mode" and choose "Automatically optimize for battery life"
Leave your laptop plugged in for a few hours. Battery #2 (the keyboard portion of your Helix) will drain to 0%, and won't resume charging on its own.
At first, I thought my Helix keyboard had lived a really short life. But it turns out you can go back to "Battery Health Mode", change the option to "Always fully charge" and then close the lid to make the Helix sleep. Eventually, your Helix will recognize that Battery #2 is dead and start charging it again.
This is obviously a problem with the software, and should be able to be resolved easily by Lenovo once they see this message. Please comment on this post to draw attention to the matter.
Thanks!

Hi,
We are aware of this problem where the setting for "Battery Health Mode" does not work in the following case:
1. the setting is changed while the system is undocked
2. then, the system is docked.
The dock battery will not know that the setting for "Battery Health Mode" has been changed.
The work-around is to toggle the setting for "Battery Health Mode" while the system is docked, as you noted.

W510 Lenovo Bluetooth windows update killed USB Keyboard

Hi all,
Yesterday afternoon (14 M!R 2012) I ran a windows 7 update that included a Lenovo update. It was some kind of bluetooth thing, but I'm not really sure the exact name. Foolishly, I chose to include this in the update. When I performed the updates and restarted the machine my USB keyboard no longer works. There were 13 updates available for install. 9 of them were critical updates and 4 were optional. I installed 3 of the 4 optional and all of the critical. So when I discovered that the keyboard didn't work, I rollback the update to the last good configuration and the problem persisted. When I looked at what updates were available, 12 of the 13 were there, but the Lenovo bluetooth one wasn't on the list, leading me to believe that it didn't get rolled back.
What I've noticed is that the keyboard is recognized by windows, but I can't type anything. Furthermore, when I do type a few characters with it, after about 5 seconds I hear the "disconnected a USB device" sound. So something is definitely strange, but I don't know what to do. Does anyone have any ideas? I really need the full sized ergo keyboard. The tiny laptop keyboard kills my hands. I have rheumatoid arthritis, and I really need my big keyboard or my hands are killing me.
Thanks,
Tripp

Totally generic. I have no idea why the bluetooth update would affect it. I'm just pointing the finger there b/c that was the only update that doesn't seem to have been undone by the windows restore operation. At one point last night windows performed an update on the usb drivers, but sadly that didn't solve anything. It's bizarre because windows can see the keyboard, it just doesn't work. Windows doesn't seem to think that there's anything wrong with device and it says the drivers are up to date.

Last upgrade killed KDM keyboard/mouse input

Hi, I performed a pacman -Syu last night and a few packages were upgraded. Now, when I reach the KDM login, it does not detect keyboard or mouse input. However during the boot process it detected the keyboard properly. Of course, now I can't use ctrl-alt-f1 to reach a VC from the KDM screen.
The relevant snippet of pacman.log is below. I took a look and I tried downgrading a few packages from a livecd: xproto and xorg-xinit, but without success. I actually cleared my pacman cache a while ago because of a pacman error, so I don't have very many package backups unfortunately. Perhaps somebody can pinpoint the package that is giving me all this trouble?
Thanks!
[2010-12-20 02:05] synchronizing package lists
[2010-12-20 02:12] Running 'pacman -S -u'
[2010-12-20 02:12] starting full system upgrade
[2010-12-20 02:20] removed pycairo (1.8.10-2)
[2010-12-20 02:20] upgraded arandr (0.1.3-5 -> 0.1.4-1)
[2010-12-20 02:20] upgraded bash (4.1.009-1 -> 4.1.009-3)
[2010-12-20 02:20] upgraded bluez (4.80-1 -> 4.82-1)
[2010-12-20 02:20] upgraded run-parts (3.2.3-1 -> 3.4.1-1)
[2010-12-20 02:20] Clearing symlinks in /etc/ssl/certs...done.
[2010-12-20 02:20] Updating certificates in /etc/ssl/certs... 141 added, 0 removed; done.
[2010-12-20 02:20] Running hooks in /etc/ca-certificates/update.d....done.
[2010-12-20 02:20] upgraded ca-certificates (20090814-3 -> 20090814+nmu2-1)
[2010-12-20 02:20] upgraded cdrkit (1.1.10-1 -> 1.1.11-1)
[2010-12-20 02:20] upgraded chromium (8.0.552.215-1 -> 8.0.552.224-1)
[2010-12-20 02:20] upgraded device-mapper (2.02.77-1 -> 2.02.78-1)
[2010-12-20 02:20] upgraded dhcpcd (5.2.8-1 -> 5.2.9-1)
[2010-12-20 02:20] warning: /etc/profile installed as /etc/profile.pacnew
[2010-12-20 02:20] warning: /etc/hosts installed as /etc/hosts.pacnew
[2010-12-20 02:20] warning: /etc/gshadow installed as /etc/gshadow.pacnew
[2010-12-20 02:20] upgraded filesystem (2010.10-1 -> 2010.12-1)
[2010-12-20 02:20] upgraded libpulse (0.9.22-1 -> 0.9.22-2)
[2010-12-20 02:20] upgraded fluidsynth (1.1.3-1 -> 1.1.3-2)
[2010-12-20 02:20] upgraded foomatic-db (4.0.5_20101024-1 -> 4.0.6_20101215-1)
[2010-12-20 02:20] upgraded foomatic-filters (4.0.5_20101024-1 -> 4.0.6_20101215-1)
[2010-12-20 02:20] upgraded foomatic-db-engine (4.0.5_20101024-1 -> 4.0.6_20101215-1)
[2010-12-20 02:20] upgraded zlib (1.2.5-2 -> 1.2.5-3)
[2010-12-20 02:20] upgraded ghostscript (9.00-1 -> 9.00-2)
[2010-12-20 02:21] upgraded git (1.7.3.3-1 -> 1.7.3.4-1)
[2010-12-20 02:21] upgraded gnutls (2.8.6-1 -> 2.10.4-1)
[2010-12-20 02:21] upgraded gparted (0.7.0-1 -> 0.7.1-1)
[2010-12-20 02:21] upgraded gpsd (2.95-7 -> 2.95-8)
[2010-12-20 02:21] upgraded graphicsmagick (1.3.7-3 -> 1.3.12-1)
[2010-12-20 02:21] upgraded libdrm (2.4.22-1 -> 2.4.22-3)
[2010-12-20 02:21] upgraded libgl (7.9-1 -> 7.9.0.git20101207-2)
[2010-12-20 02:21] upgraded intel-dri (7.9-1 -> 7.9.0.git20101207-2)
[2010-12-20 02:21] upgraded opencv (2.2.0-1 -> 2.2.0-2)
[2010-12-20 02:21] upgraded kipi-plugins (1.6.0-1 -> 1.6.0-2)
[2010-12-20 02:21] upgraded libdbusmenu-qt (0.6.4-1 -> 0.6.6-1)
[2010-12-20 02:21] upgraded libdvdcss (1.2.10-1.1 -> 1.2.10-2)
[2010-12-20 02:21] upgraded libindi (0.7-1 -> 0.7.2-1)
[2010-12-20 02:21] upgraded libmpdclient (2.2-1 -> 2.3-1)
[2010-12-20 02:21] upgraded libogg (1.2.1-1 -> 1.2.2-1)
[2010-12-20 02:21] upgraded libpcap (1.1.1-1 -> 1.1.1-2)
[2010-12-20 02:21] upgraded lvm2 (2.02.77-1 -> 2.02.78-1)
[2010-12-20 02:21] upgraded mesa (7.9-1 -> 7.9.0.git20101207-2)
[2010-12-20 02:21] upgraded mpd (0.15.15-2 -> 0.16-2)
[2010-12-20 02:21] upgraded pkg-config (0.25-2 -> 0.25-3)
[2010-12-20 02:21] upgraded procps (3.2.8-2 -> 3.2.8-3)
[2010-12-20 02:21] installed python2-cairo (1.8.10-1)
[2010-12-20 02:21] upgraded pycups (1.9.51-2 -> 1.9.53-1)
[2010-12-20 02:21] upgraded pysmbc (1.0.9-1 -> 1.0.10-1)
[2010-12-20 02:21] upgraded python-beautifulsoup (3.0.8.1-1 -> 3.2.0-1)
[2010-12-20 02:21] upgraded raptor (1.4.21-1 -> 1.4.21-2)
[2010-12-20 02:21] upgraded rasqal (0.9.20-1 -> 0.9.21-1)
[2010-12-20 02:21] upgraded redland (1.0.12-2 -> 1.0.12-3)
[2010-12-20 02:21] upgraded sdparm (1.05-1 -> 1.06-1)
[2010-12-20 02:21] upgraded system-config-printer-common (1.2.5-3 -> 1.2.5-4)
[2010-12-20 02:21] upgraded telepathy-glib (0.12.5-1 -> 0.12.6-1)
[2010-12-20 02:21] upgraded unrar (4.0.2-1 -> 4.0.3-1)
[2010-12-20 02:21] upgraded vpnc (0.5.3-2 -> 0.5.3-3)
[2010-12-20 02:21] upgraded xorg-xauth (1.0.4-1 -> 1.0.5-1)
[2010-12-20 02:21] upgraded xorg-xbacklight (1.1.1-1 -> 1.1.2-1)
[2010-12-20 02:21] upgraded xorg-xinit (1.3.0-1 -> 1.3.0-2)
[2010-12-20 02:21] upgraded xproto (7.0.19-1 -> 7.0.20-1)

Alright, disabled KDM and logged into virtual console and startx. Same issue when I get into X/KDE, keyboard and mouse input not detected. Any idea as to which package might be the culprit? Unfortunately I am away from home for a couple weeks and can't get to my backup clones...

T410 external monitor kills mouse/keyboard with dock

WinXP with SP3.
Hi there! I'm trying to use an external monitor. I also have a usb mouse and usb keyboard connected to the dock, When the external monitor is connected I have have keyboard and mouse function both external and on the laptop. I also have display on the external monitor. Once I boot windows, I loose function of the mouse and keyboard both externally and on the laptop. It's driving me nuts!! Any ideas??
If I just boot at the dock with only the monitor plugged in, I loose the mouse/keyboard on the laptop. Using the VGA plug.
Any help would be so grand!

I've tried 3 different mice and keyboards. The issue presents even if I just plug the monitor into the laptop without the dock either vga or div-x. The dock is a series 3 mini.

4.2.1 killed the Keyboard Clicks on my iPad

Keyboard Clicks worked right up to the point that I installed 4.2.1. Now they don't work at all. Or almost at all. They will work on the initial password screen. They also work on the Settings->General->Sounds page. But no where else.
I've turned all of the sounds (including Keyboard Clicks) off and on again several times. I've cranked the volume up all the way. I've also played with the new Mute switch just in case that was giving me the problems. Nothing seems to work.
Has anyone else experienced this problem?

Just a thought- have you got the new Airplay feature turned on in iTunes or the video app?
Now this is an interesting question. However I checked it out and I don't think so. First because I don't own an Apple TV or compatible speakers. Indeed I've never even used Airplay and had to consult the web to find out how it works.
So I checked. I brought up a video and then a song, and did not see the Airplay up arrow icon on the control window as shown in the Apple demo videos. So I'm pretty sure it is not currently enabled on my iPad. I also went into iTunes, and the only reference I could see to Airplay was under iTunes->Preferences->Devices. There were options to look for remote speakers and for remote devices. Those options were selected so I turned them off. I didn't see any other Airplay features in iTunes, that I could find. So I'm guessing this isn't the problem for me.
I did find one other place where Keyboard Clicks works. In addition to the initial screen-lock password page, and also the Settings->General->Sounds page, I also discovered that Clicks works on the search page that you get when you swipe to the right on the home page. But, other than those three pages, Clicks doesn't work anywhere else.
I'm still thinking that it is a 4.2.1 bug, since it appeared exactly when I did the upgrade, but it is odd that no one else has (yet) reported this same problem. It's still possible that there is a weird configuration issue (like Airplay - thanks for the suggestion) but if so I haven't found it yet.

10.4.8 killed my keyboard buttons

On my iMac G4 20" I have now lost the ability to control the volume or eject a CD from the keyboard. This problem isn't true for my PowerBook G4 which I updated at the same time.
Does anyone have any suggestions to resolve this probem as it's bleeding annoying.
Marky

I haven't installed 10.4.8 yet, but in 10.4.7, go to System Preferences:Keyboard and Mouse:Keyboard, then look at, and toggle-a-few-times the "Use the F1-F12 keys to control software features"-checkbox, and make sure it is un-checked.
On portables, with this setting, one must hold-down the "fn"-keyboard-key and hit a function-key(F1-F12), to affect an application. If you don't hold-down the "fn"-keyboard-key, and type a function-key(F1-F12), you get-to-control hardware-features (for example, the "F12"-keyboard-key on some Mac laptops does an "Eject").
Got it?

Update Killed my Keyboard?

I just performed the most recent Security Update on my iMac G5. Everything seemed okay, but then I realized I couldn't type an "m", or an "i", or any letter on the right half of the keyboard. I couldn't type my password to try and reinstall the update. More keys lost function as I looked for a solution on the web. Now only 3 keys seem to be working and they are constantly bombarding whatever has focus.
I am on my laptop now to try and desperately get some help. I tried to do the System Repair from my startup disk, but since I can't type a "C", no luck there. I tried accessing the disk to see if I could run anything that way, but again I need my password, which I obviously can't type.
Can somebody out there help me?
Thanks ~ Kim

Hi Jeff,
Thanks so much for the quick reply!
I have a wireless keyboard and mouse for my Mac Mini, and I was able to successfully pair them and use the keyboard with no problems.
I have one question though - wouldn't the drivers be different for the 2 keyboards? I don't want to buy a new keyboard and find I have the same problem. It just seems to coincidental that moments after I install the update that my keyboard zonks out on me! I guess stranger things have happened though.
~Kim

10.5.1 killed my Keyboard

So, after the 10.5.1 update I can no longer type with my built in keyboard. An Apple USB keyboard with Logitech mouse works fine.
Apple System Profiler seems to find it just fine
Version: 0.67
Bus Power (mA): 220
Speed: Up to 1.5 Mb/sec
Manufacturer: Apple, Inc
Product ID: 0x0220
Vendor ID: 0x05ac (Apple Computer, Inc.)
No haxies installed. I did have USB overdrive installed for the mouse, but uninstalling it did no good.
I started up from the Leopard DVD and repaired permissions. The re-applied the 10.5.1 update.
Still no keyboard.
Help?

I seem to have found something different... mine wasn't intermittent, it was complete failure.
But, with that somewhat solved, I'm now trying to find out why this thing won't get DHCP. At all. Other computers on the network are good, but this one won't get DHCP... its one thing after another after installing Leopard.

Yosemite kill french keyboard and switch to english

Hi,
I am on Yosemite system.
The keyboard is switched to english each time I switch off and on my imac ( 2011). I generally see it when trying to surf and I can't enter some of my passwords because of the qwerty keyboard.
So basically when I go to the preferences and then to keyboard options, french keyboard disappeared and I have to manually add it again each time I am opening my imac.
As I am french it's highly annoying to have to change each time this way.
It was working perfectly before updating to yosemite.
Any idea to fix this ?
All the best for this new year starting :-).

Do a backup.
Quit the application.
Go to Finder and select your user/home folder. With that Finder window as the front window, either select Finder/View/Show View options or go command - J. When the View options opens, check ’Show Library Folder’. That should make your user library folder visible in your user/home folder. Select Library. Then go to Preferences/com.apple.systempreferences.plist. Move the .plist to your desktop.
Restart, open the application and test. If it works okay, delete the plist from the desktop.
If the application is the same, return the .plist to where you got it from, overwriting the newer one.
Thanks to leonie for some information contained in this.

I have killed my keyboard

I spilled liquid resin on my laptop. It settled overnight into hard plastic, and it makes the b, n, and m keys as well as the spacebar almost unusable. Should I pry the keys up and scrape away the resin, or should I send it someplace to get the keyboard repaired?

I think you're probably going to need a new keyboard. I doubt very much that you'll be able to restore the keyboard to full operation by scraping away the resin, though of course at this point there's probably little harm in trying. You will also have to hope that the resin didn't get down into the other parts of the computer or things could get really expensive.
Good luck.

How to fix the Superdrive from killing the keyboard usb port?

IF the Superdrive is plugged into the iMac USB port, the keyboard USB port indicates that there is not enough power for the thumb drive or other device. If the Superdrive is unplugged, all is well on the keyboard USB port.
Any fixes for this?

Hi there, I have the same problem on a 27" iMac: when the superdrive is connected to a USB port on the Mac, the USB ports on the keyboard seem to lose all power, even for a USB key.
I called Apple and they told me to reset SMC, PRAM and VRAM but to no avail.
I will try with another keyboard as they seem to say it could be a keyboard problem (which a very much doubt...)

Migration assistant killed my keyboard

i migrated everything from my macbook to my brand new mbp last night, and it went well, until i got passed the registration form, at which point my keyboard crapped out. none of the keys respond except the function keys 1-12.
is it possible that i also transfered my internal keyboard drives when i migrated? if so, how do i reverse this?
thanks.
x-posting to mac osx 10.5

You probably solved this by now, but I just had the same issue. But here's my 2 cents.
I had the same problem migrating from a MacBook purchased 8/2007 to a brand new MacBook purchased 8/2008. The old MacBook originally ran Tiger, but was running Leopard since Spring '08 with no issues.
Typing the account password worked fine. But after login, it acted as if the NumLock Key was on. I'm positive that the keys on the right side that have the little gray numbers on the older MacBook (U,I,O, J,K,L, etc.) responded at first. The new MacBook doesn't have the little numbers and does not have "NumLock" on the F6 key. Pressing the F6 made no difference.
The fix was to go to the Universal Access, Mouse & Trackpad tab and click Mouse Keys off (or press the option key 5 times). I checked the old UA prefs on the old MacBook and Mouse Keys was on also, but the keyboard worked fine. I suspect the newer keyboard has a different configuration since the function key presets across he top are different than the older MacBook (Exposé, Dashboard, Rewind, Play/Pause, FForward, etc.). Turning Mouse Keys back on makes the keyboard non-functional except for the arrow keys, delete key and the Function keys. I can't explain it but it's working fine now.
The archived Discussion pointed me to the fix:
http://discussions.apple.com/thread.jspa?threadID=1455732

Did Yoesmite kill my keyboard?

Hi all,
My iMac 2009 flat alu numeric pad keyboard (USB) suddenly decided to not work anymore. No keys respond.
Upgraded to Yoesmite (with some issues) 4 days previously.
The iMac is fine - I've connected another keyboard that works fine.
All usb ports work
The caps lock light is lit and goes strong when depressed (like me )
The mouse connected to the keyboard usb port still worked.
It just doesn't feel as if this keyboard has died though I'm beginning to think that. It feels more like it's been disabled by a key-stroke combination.
That said, after having spent a good amount of time reading these posts, I'm about ready to try the dishwasher solution.
Has anyone any ideas before I go drastic?

Try resetting the PRAM: boot with these keys held down: Option, Command, P, and R keys and continue holding them down until you hear the startup sound for the second time: OS X Mavericks: Reset your computer’s PRAM

10.4.3 killed my keyboard

Similar Messages

Maybe you are looking for