Wireless aluminum keyboard won't stay on

I'm trying to pair my wireless aluminum keyboard with my Mac Mini. I have OS10.5.8 and I've run the aluminum keyboard 2.0 update. My keyoard light comes on for about 2 seconds then goes out. batteries are new and in correctly. My mini is able to discover the keyboard after a bit of fooling with the on/off or removing and replacing the batteries, but when it goes to pair it always fails.

Hello:
Try resetting the PRAM (if you can) and the SMC.
If that does not help, I would suspect a faulty KB.
Barry

Similar Messages

My wireless keyboard won't stay on long enough to pair with ipad

my wireless keyboard will not stay on long enough to be recognized with my ipad to pair it. It pairs just fine with my macbook pro (i'm using it right now to prove my point.) I bought it to use for the ipad not with the macbook. I have replaced batteries and tried the aluminum trick as well. it's obvious to me that it is not a case of it not working but why it won't work with the ipad is beyond me. Help is appreciated.

I'm having the same problem. The light on my keyboard won't stay lit. Have changed to new batteries. It used to work fine and when I opened Bluetooth this morning (I have not used the keyboard in a while) it recognized "Apple Wireless Keyboard". After trying to connect and getting an error message (tried this about a dozen times) I clicked on Forget this Device. Turned off Bluetooth and back on. Sometimes it will pull up "Keyboard" but not Apple Wireless keyboard as in the past and which is what shows on my iphone (it connects automatically). Then I thought maybe the iPhone Bluetooth was interfering with the keyboard connecting so I turned it off on the iPhone. Same issue. Shows keyboard as discoverable but will not connect. I have the ipad3 and my keyboard is only 3 or 4 months old.

Wireless Aluminum Keyboard Troubleshooting

If you're having issues with your Apple Wireless (Aluminum) Keyboard disconnecting, there are a few things you can try.
First, check your wireless network configuration to see if you can avoid interference. See this post in another topic:
http://discussions.apple.com/message.jspa?messageID=5783742#5783742
Although I did have success with tweaking my wifi setup, my keyboard disconnect problem returned again a couple of weeks ago. I had recently upgraded to Leopard (10.5.1) which may have contributed - although I had been using wired ethernet, and switched back to wifi around the same time as my Leopard upgrade.
Like others have posted, I also noticed the bluetooth daemon log errors in my system log. To look for them, you can open console.app, and search for "blued" in the system.log and also its archive history. Here's an example:
+Jan 25 09:17:22 Macintosh-2 kernel[0]: IOBluetoothHCIRequest::Create [0x55da000] Request OpCode 0000 Generated by: blued (47) status: 0 timeout 1000. has a too small timeout, a reasonable value would be 5000 (5 seconds)+
Here are some other things to try. You should only try one at a time - so that you can tell which change fixed your problem.
1. In the Bluetooth System Preferences panel, unpair your keyboard, and re-pair it again
2. Also in the Bluetooth System Preferences panel, add the keyboard to your favorites. To do this in Leopard: select the keyboard in the bluetooth devices list. Click on the tasks cog at the foot of that pane (just beside the plus and minus). Select "Show more info". Select "Add To Favorites".
3. Reset the bluetooth preferences by moving system preference files. Warning: only try this if you are comfortable using the OS X terminal!! :
sudo mv /var/root/Library/Preferences/blued.plist /var/root/Library/Preferences/blued.plist.old
sudo mv /var/root/Library/Preferences/com.apple.Bluetooth.plist /var/root/Library/Preferences/com.apple.Bluetooth.plist.old
(you will need to enter your password at least once, and then will need to restart your machine).
Keep a log of all the things you've tried. If none of these work, its probably time to call AppleCare. If you have one of the new Apple (Aluminum) Wireless Keyboards, it is still covered by warranty at this point.

It sounds like the bluetooth in both of your keyboards has simply died. If it's still under warranty (if it has one), take it to the apple store and show them. They may give you a new one. For future reference, the new wired USB keyboard is now exactly the same as the wireless (except that it has a wire), and you won't face any bluetooth issues like that. You can get the new wired keyboard here:
http://store.apple.com/us/product/MB869LL/A?fnode=MTY1NDA1Mg&mco=NDE4NjI4Mg
Also, if you're willing to spend a bit more money, Macworld rated the Logitech DiNovo Edge Keyboard very highly. Here's a link to that:
http://store.apple.com/us/product/TU938LL/A?fnode=MTY1NDA1Mg&mco=MjgzMTkxNA
Hope this helps.

Delayed Response on Wireless Aluminum Keyboard Since the Update

I just updated the firmware on my wireless aluminum keyboard and now there is an annoying noticeable delay between pressing a key and seeing it on the screen. Any ideas how to fix this?

Sorry that I can't help you with this, but FYI I have just updated the firmware on my Aluminium keyboard and haven't noticed any difference in the response.

My wireless Apple keyboard won't connect, it just keeps blinking to pair, but nothing connects. I even tried hooking up another wireless I have and it does the same thing. Should I delete it and set it up again?

My wireless Apple keyboard won't connect, it just keeps blinking to pair, but nothing connects. I even tried hooking up another wireless I have and it does the same thing. Should I delete it and set it up again?

Hey Apple Health,
Welcome to Apple Support Communities! There's an article that helps to resolve issues with wireless keyboards. I'd take a look at it, go through the troubleshooting steps, and see if that resolves the issue for you:
Troubleshooting wireless mouse and keyboard issues
http://support.apple.com/kb/TS3048
Best,
David

Aluminum Keyboard won't wake Mac mini from sleep (sometimes)

I just bought the new aluminum keyboard (wired). Its great, and looks amazing next to my mac mini......except it won't wake mac mini from sleep sometimes. When this occurs, I can tap on any key but the machine won't wake up. The only work around I have is to attach my ipod, which wakes the mini. Oddly this only happens sometimes. I can't isolate any other variable which may be influencing this behavior.
I'm running leopard and didn't think I needed to install the 1.2 keyboard software update.
I called Apple support, and they told me the problem is that I'm using a non-apple mouse (I have a microsoft optical wired mouse connected to the keyboard's USB port). I don't believe them as i've used this mouse connected to my previous Apple keyboard for years and never had a problem.
Can anyone help?

Regrettably, I can't offer a solution to the problem stated in the title. Instead, I experience the same problem.
Wireless Mighty Mouse circa 2007
Wireless Apple Keyboard circa 2007
Bluetooth dongle (a bluetooth thingy connected to a USB port)
Things worked fine until an upgrade from Tiger to Snow Leopard. Following the upgrade there were several mouse related issues. Those were resolved. One issue remains: waking by use of mouse or keyboard.
The setup (Same for keyboard and mouse)
System Preferences --- Bluetooth --- Keyboard Connected --- Keyboard Paired. The "Discoverable" box is checked.
Digging deeper
System Preferences --- Bluetooth --- Advanced --- "Allow Bluetooth device to wake this computer" --- This option is unchecked and is greyed out, inaccessible. Two of the other options are checked and available: the options about opening the Bluetooth assistant and the one about prompting incoming audio.
I've searched other posts. However, many of the other posts seem to conflate this Wake/Sleep issue with various connection issues. Thus, the advice given is a bit confusing to this amateur. Might one of you experts have a solution to this annoying little problem?
Thanks for your interest.
Lxloco

Aluminum keyboard won´t work ? has the caps lock on !

i have a imac power g5 with 10.5.8 os x it have the key caps lock on but the imac won't recognize the keyboard and any key dont work so please i need help to fix it i don't have another keyboard right now
Thank you everyones
i have a imac powerPC G5
processor 1.9 GHz
memory 1.5GB
version 10.5.8
and the keyboard aluminum model A1243

There were two versions of the model A1243 keyboard, and some G5 PowerMac (tower) users found that one of them worked, and the other didn't. There is an A version and a B version. And likely the same one which worked for the tower G5 would function with the iMac G5.
However this numbered designator is not an Aluminum keyboard
Model Number
A1243
Order Number
MB110LL/A, MB110LL/B
Or use a white USB keyboard from the early 2003-05 era such as those shipped with the iMac G4, and early iMac G5.
This is an aluminum keyboard:
Model Number
A1242
Order Number
MB869LL/A
There were compact keyboards without numeric keypad, and with BTO computers, a full-size keyboard with numberic keypad were available only as an option. Several later model keyboards worked well with the Intel-based Mac computers of their era; so when there is an issue with an earlier PPC-based Mac, look into those keyboards fitted to the computer vintage.
So if the keyboard you have does not work, could be it was intended for use with a later Mac computer after 2005. I was sure to get at least one as-new spare Apple USB keyboard, to have on hand for my older Macs.
Good luck & happy computing!

HT3932 Wireless Aluminum Keyboard Firmware Update

I am trying to install the Aluminum keyboard software update. When I click on the file I downloaded from apple (Jan 25, 2010 - long file name) I get a message that says no aluminum keyboard is connected. The keyboard is on, paired and connected (I can type things; show up under bluetooth, etc). What am I doing wrong? The firmware version is way old (050 vs 321).
Thanks,
Justin

Hello:
Your profile simply says "iPad." What, exactly, are you trying to do?
Barry

New Wireless Keyboard won't stay linked

I use a MBP running Leopard in closed lid configuration at work and at home most of the time unless I'm on the road. My old white wireless keyboard never forget it is synched with my laptop. However, at home I constantly have to re-introduce my new aluminum wireless keyboard to my closed lid laptop. This gets old because when I restart at home I usually like to boot off of an external drive, and of course with no active keyboard I can't use the "option" key to select my boot drive.
This did not do this under Tiger BTW.
Any ideas? I reset PRAM. Should I delete all wireless keyboards and start again? Can more than one wireless keyboard be used on the same computer (at separate times)?
Any suggestions would be helpful in order to avoid having to crack the laptop lid open to get to the non-wireless keyboard on the laptop. This sometimes confuses my external video output to my

May the new wireless keyboard itself has connecting problem, restore the factory default settings.

Wireless aluminum keyboard Firmware 1.0 update: Command-accent keystroke.

Hi,
I applied firmware update (1.0) for the aluminum wireless keyboard several days ago and have lost my ability to move to the next/previous window using command-accent/tilde. Has anyone else encountered this?
All other keystrokes are functional and it affects both command keys.
Thanks!

Solution: I reset my Keyboard Shortcuts (preferences/keyboard & mouse) even there there were no conflicts present.

Yoga 2-11 Onscreen Keyboard won't stay up when in tablet mode

I have seen many topics about the onscreen keyboard not staying on when in tablet mode but most of it from 2013. I am having this problem and I cannot find a solution. I have to go to laptop mode to sign in and then go back to tablet mode. The keyboard pops up but as soon as it does it goes away. What is the fix? Yoga 2-11 purchased Dec 2014 from Best Buy.

Thank you for your swift suggestion! I think it has worked I will monitor it for a couple of days

Wireless Logitech keyboard won't work

Hi guys,
I have a wireless Logitech diNovo edge keyboard that used to work fine. A few months ago it stopped working and I never bothered to look at it. The keyboard works fine in other PCs running Windows. When I plug it into the Archlinux box the keyboard never synchs to the bluetooth dongle (just blinks).
This is what happens when I plug the keyboard in (NOVATEK is a wired USB keyboard):
dmesg
[ 51.878109] usb 4-2: USB disconnect, device number 2
[ 55.840026] usb 4-2: new full-speed USB device number 4 using ohci_hcd
[ 56.045166] hub 4-2:1.0: USB hub found
[ 56.048080] hub 4-2:1.0: 3 ports detected
[ 56.345080] usb 4-2.2: new full-speed USB device number 5 using ohci_hcd
[ 56.479450] input: Logitech Logitech BT Mini-Receiver as /devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2.2/4-2.2:1.0/input/input11
[ 56.479739] generic-usb 0003:046D:C713.0004: input,hidraw0: USB HID v1.11 Keyboard [Logitech Logitech BT Mini-Receiver] on usb-0000:00:06.0-2.2/input0
[ 56.548115] usb 4-2.3: new full-speed USB device number 6 using ohci_hcd
[ 56.703434] input: Logitech Logitech BT Mini-Receiver as /devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2.3/4-2.3:1.0/input/input12
[ 56.704162] logitech 0003:046D:C714.0005: input,hiddev0,hidraw1: USB HID v1.11 Mouse [Logitech Logitech BT Mini-Receiver] on usb-0000:00:06.0-2.3/input0
[ 56.948094] usb 4-2.1: new full-speed USB device number 7 using ohci_hcd
[ 57.089411] Bluetooth: Core ver 2.16
[ 57.090507] NET: Registered protocol family 31
[ 57.090518] Bluetooth: HCI device and connection manager initialized
[ 57.090529] Bluetooth: HCI socket layer initialized
[ 57.090535] Bluetooth: L2CAP socket layer initialized
[ 57.090563] Bluetooth: SCO socket layer initialized
[ 57.093514] usbcore: registered new interface driver btusb
[ 90.226597] usb 4-2: USB disconnect, device number 4
[ 90.226605] usb 4-2.1: USB disconnect, device number 7
[ 90.227663] usb 4-2.2: USB disconnect, device number 5
[ 90.283551] usb 4-2.3: USB disconnect, device number 6
[ 93.210021] usb 4-2: new full-speed USB device number 8 using ohci_hcd
[ 93.415200] hub 4-2:1.0: USB hub found
[ 93.418081] hub 4-2:1.0: 3 ports detected
[ 93.715081] usb 4-2.2: new full-speed USB device number 9 using ohci_hcd
[ 93.849470] input: Logitech Logitech BT Mini-Receiver as /devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2.2/4-2.2:1.0/input/input13
[ 93.849808] generic-usb 0003:046D:C713.0006: input,hidraw0: USB HID v1.11 Keyboard [Logitech Logitech BT Mini-Receiver] on usb-0000:00:06.0-2.2/input0
[ 93.918121] usb 4-2.3: new full-speed USB device number 10 using ohci_hcd
[ 94.057378] input: Logitech Logitech BT Mini-Receiver as /devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2.3/4-2.3:1.0/input/input14
[ 94.058052] logitech 0003:046D:C714.0007: input,hiddev0,hidraw1: USB HID v1.11 Mouse [Logitech Logitech BT Mini-Receiver] on usb-0000:00:06.0-2.3/input0
[ 94.291136] usb 4-2.1: new full-speed USB device number 11 using ohci_hcd
[ 96.400094] usb 4-2: USB disconnect, device number 8
[ 96.400102] usb 4-2.1: USB disconnect, device number 11
[ 96.402936] usb 4-2.2: USB disconnect, device number 9
[ 96.460224] usb 4-2.3: USB disconnect, device number 10
[ 99.843366] usb 4-2: new low-speed USB device number 12 using ohci_hcd
[ 100.047501] input: NOVATEK USB Keyboard as /devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2:1.0/input/input15
[ 100.047781] generic-usb 0003:0603:00F2.0008: input,hidraw0: USB HID v1.10 Keyboard [NOVATEK USB Keyboard] on usb-0000:00:06.0-2/input0
[ 100.060244] input: NOVATEK USB Keyboard as /devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2:1.1/input/input16
[ 100.060670] generic-usb 0003:0603:00F2.0009: input,hiddev0,hidraw1: USB HID v1.10 Device [NOVATEK USB Keyboard] on usb-0000:00:06.0-2/input1
See here for udev events.
Xorg log:
[ 56.500] (II) config/udev: Adding input device Logitech Logitech BT Mini-Receiver (/dev/input/event2)
[ 56.500] (**) Logitech Logitech BT Mini-Receiver: Applying InputClass "evdev keyboard catchall"
[ 56.500] (II) Using input driver 'evdev' for 'Logitech Logitech BT Mini-Receiver'
[ 56.500] (**) Logitech Logitech BT Mini-Receiver: always reports core events
[ 56.500] (**) evdev: Logitech Logitech BT Mini-Receiver: Device: "/dev/input/event2"
[ 56.500] (--) evdev: Logitech Logitech BT Mini-Receiver: Vendor 0x46d Product 0xc713
[ 56.500] (--) evdev: Logitech Logitech BT Mini-Receiver: Found keys
[ 56.501] (II) evdev: Logitech Logitech BT Mini-Receiver: Configuring as keyboard
[ 56.501] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2.2/4-2.2:1.0/input/input11/event2"
[ 56.501] (II) XINPUT: Adding extended input device "Logitech Logitech BT Mini-Receiver" (type: KEYBOARD, id 8)
[ 56.501] (**) Option "xkb_rules" "evdev"
[ 56.501] (**) Option "xkb_model" "evdev"
[ 56.501] (**) Option "xkb_layout" "us"
[ 56.720] (II) config/udev: Adding input device Logitech Logitech BT Mini-Receiver (/dev/input/mouse1)
[ 56.720] (II) No input driver specified, ignoring this device.
[ 56.720] (II) This device may have been added with another device file.
[ 56.721] (II) config/udev: Adding input device Logitech Logitech BT Mini-Receiver (/dev/input/event3)
[ 56.721] (**) Logitech Logitech BT Mini-Receiver: Applying InputClass "evdev pointer catchall"
[ 56.721] (**) Logitech Logitech BT Mini-Receiver: Applying InputClass "evdev keyboard catchall"
[ 56.721] (II) Using input driver 'evdev' for 'Logitech Logitech BT Mini-Receiver'
[ 56.721] (**) Logitech Logitech BT Mini-Receiver: always reports core events
[ 56.721] (**) evdev: Logitech Logitech BT Mini-Receiver: Device: "/dev/input/event3"
[ 56.721] (--) evdev: Logitech Logitech BT Mini-Receiver: Vendor 0x46d Product 0xc714
[ 56.721] (--) evdev: Logitech Logitech BT Mini-Receiver: Found 16 mouse buttons
[ 56.722] (--) evdev: Logitech Logitech BT Mini-Receiver: Found scroll wheel(s)
[ 56.722] (--) evdev: Logitech Logitech BT Mini-Receiver: Found relative axes
[ 56.722] (--) evdev: Logitech Logitech BT Mini-Receiver: Found x and y relative axes
[ 56.722] (--) evdev: Logitech Logitech BT Mini-Receiver: Found absolute axes
[ 56.722] (II) evdev: Logitech Logitech BT Mini-Receiver: Forcing absolute x/y axes to exist.
[ 56.722] (--) evdev: Logitech Logitech BT Mini-Receiver: Found keys
[ 56.722] (II) evdev: Logitech Logitech BT Mini-Receiver: Configuring as mouse
[ 56.722] (II) evdev: Logitech Logitech BT Mini-Receiver: Configuring as keyboard
[ 56.722] (II) evdev: Logitech Logitech BT Mini-Receiver: Adding scrollwheel support
[ 56.722] (**) evdev: Logitech Logitech BT Mini-Receiver: YAxisMapping: buttons 4 and 5
[ 56.722] (**) evdev: Logitech Logitech BT Mini-Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 56.722] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2.3/4-2.3:1.0/input/input12/event3"
[ 56.722] (II) XINPUT: Adding extended input device "Logitech Logitech BT Mini-Receiver" (type: KEYBOARD, id 9)
[ 56.722] (**) Option "xkb_rules" "evdev"
[ 56.722] (**) Option "xkb_model" "evdev"
[ 56.722] (**) Option "xkb_layout" "us"
[ 56.723] (II) evdev: Logitech Logitech BT Mini-Receiver: initialized for relative axes.
[ 56.723] (WW) evdev: Logitech Logitech BT Mini-Receiver: ignoring absolute axes.
[ 56.724] (**) Logitech Logitech BT Mini-Receiver: (accel) keeping acceleration scheme 1
[ 56.724] (**) Logitech Logitech BT Mini-Receiver: (accel) acceleration profile 0
[ 56.725] (**) Logitech Logitech BT Mini-Receiver: (accel) acceleration factor: 2.000
[ 56.725] (**) Logitech Logitech BT Mini-Receiver: (accel) acceleration threshold: 4
[ 90.266] (II) config/udev: removing device Logitech Logitech BT Mini-Receiver
[ 90.267] (II) evdev: Logitech Logitech BT Mini-Receiver: Close
[ 90.267] (II) UnloadModule: "evdev"
[ 90.363] (II) config/udev: removing device Logitech Logitech BT Mini-Receiver
[ 90.364] (II) evdev: Logitech Logitech BT Mini-Receiver: Close
[ 90.364] (II) UnloadModule: "evdev"
[ 93.870] (II) config/udev: Adding input device Logitech Logitech BT Mini-Receiver (/dev/input/event2)
[ 93.870] (**) Logitech Logitech BT Mini-Receiver: Applying InputClass "evdev keyboard catchall"
[ 93.870] (II) Using input driver 'evdev' for 'Logitech Logitech BT Mini-Receiver'
[ 93.871] (**) Logitech Logitech BT Mini-Receiver: always reports core events
[ 93.871] (**) evdev: Logitech Logitech BT Mini-Receiver: Device: "/dev/input/event2"
[ 93.871] (--) evdev: Logitech Logitech BT Mini-Receiver: Vendor 0x46d Product 0xc713
[ 93.871] (--) evdev: Logitech Logitech BT Mini-Receiver: Found keys
[ 93.871] (II) evdev: Logitech Logitech BT Mini-Receiver: Configuring as keyboard
[ 93.871] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2.2/4-2.2:1.0/input/input13/event2"
[ 93.871] (II) XINPUT: Adding extended input device "Logitech Logitech BT Mini-Receiver" (type: KEYBOARD, id 8)
[ 93.871] (**) Option "xkb_rules" "evdev"
[ 93.871] (**) Option "xkb_model" "evdev"
[ 93.871] (**) Option "xkb_layout" "us"
[ 94.083] (II) config/udev: Adding input device Logitech Logitech BT Mini-Receiver (/dev/input/event3)
[ 94.083] (**) Logitech Logitech BT Mini-Receiver: Applying InputClass "evdev pointer catchall"
[ 94.083] (**) Logitech Logitech BT Mini-Receiver: Applying InputClass "evdev keyboard catchall"
[ 94.083] (II) Using input driver 'evdev' for 'Logitech Logitech BT Mini-Receiver'
[ 94.084] (**) Logitech Logitech BT Mini-Receiver: always reports core events
[ 94.084] (**) evdev: Logitech Logitech BT Mini-Receiver: Device: "/dev/input/event3"
[ 94.090] (--) evdev: Logitech Logitech BT Mini-Receiver: Vendor 0x46d Product 0xc714
[ 94.090] (--) evdev: Logitech Logitech BT Mini-Receiver: Found 16 mouse buttons
[ 94.090] (--) evdev: Logitech Logitech BT Mini-Receiver: Found scroll wheel(s)
[ 94.090] (--) evdev: Logitech Logitech BT Mini-Receiver: Found relative axes
[ 94.090] (--) evdev: Logitech Logitech BT Mini-Receiver: Found x and y relative axes
[ 94.090] (--) evdev: Logitech Logitech BT Mini-Receiver: Found absolute axes
[ 94.090] (II) evdev: Logitech Logitech BT Mini-Receiver: Forcing absolute x/y axes to exist.
[ 94.090] (--) evdev: Logitech Logitech BT Mini-Receiver: Found keys
[ 94.090] (II) evdev: Logitech Logitech BT Mini-Receiver: Configuring as mouse
[ 94.090] (II) evdev: Logitech Logitech BT Mini-Receiver: Configuring as keyboard
[ 94.090] (II) evdev: Logitech Logitech BT Mini-Receiver: Adding scrollwheel support
[ 94.090] (**) evdev: Logitech Logitech BT Mini-Receiver: YAxisMapping: buttons 4 and 5
[ 94.090] (**) evdev: Logitech Logitech BT Mini-Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 94.090] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2.3/4-2.3:1.0/input/input14/event3"
[ 94.090] (II) XINPUT: Adding extended input device "Logitech Logitech BT Mini-Receiver" (type: KEYBOARD, id 9)
[ 94.090] (**) Option "xkb_rules" "evdev"
[ 94.091] (**) Option "xkb_model" "evdev"
[ 94.091] (**) Option "xkb_layout" "us"
[ 94.091] (II) evdev: Logitech Logitech BT Mini-Receiver: initialized for relative axes.
[ 94.091] (WW) evdev: Logitech Logitech BT Mini-Receiver: ignoring absolute axes.
[ 94.092] (**) Logitech Logitech BT Mini-Receiver: (accel) keeping acceleration scheme 1
[ 94.092] (**) Logitech Logitech BT Mini-Receiver: (accel) acceleration profile 0
[ 94.092] (**) Logitech Logitech BT Mini-Receiver: (accel) acceleration factor: 2.000
[ 94.092] (**) Logitech Logitech BT Mini-Receiver: (accel) acceleration threshold: 4
[ 94.094] (II) config/udev: Adding input device Logitech Logitech BT Mini-Receiver (/dev/input/mouse1)
[ 94.094] (II) No input driver specified, ignoring this device.
[ 94.094] (II) This device may have been added with another device file.
[ 96.443] (II) config/udev: removing device Logitech Logitech BT Mini-Receiver
[ 96.444] (II) evdev: Logitech Logitech BT Mini-Receiver: Close
[ 96.444] (II) UnloadModule: "evdev"
[ 96.536] (II) config/udev: removing device Logitech Logitech BT Mini-Receiver
[ 96.537] (II) evdev: Logitech Logitech BT Mini-Receiver: Close
[ 96.538] (II) UnloadModule: "evdev"
[ 100.084] (II) config/udev: Adding input device NOVATEK USB Keyboard (/dev/input/event3)
[ 100.084] (**) NOVATEK USB Keyboard: Applying InputClass "evdev keyboard catchall"
[ 100.084] (II) Using input driver 'evdev' for 'NOVATEK USB Keyboard'
[ 100.084] (**) NOVATEK USB Keyboard: always reports core events
[ 100.084] (**) evdev: NOVATEK USB Keyboard: Device: "/dev/input/event3"
[ 100.084] (--) evdev: NOVATEK USB Keyboard: Vendor 0x603 Product 0xf2
[ 100.084] (--) evdev: NOVATEK USB Keyboard: Found 20 mouse buttons
[ 100.084] (--) evdev: NOVATEK USB Keyboard: Found keys
[ 100.084] (II) evdev: NOVATEK USB Keyboard: Configuring as mouse
[ 100.084] (II) evdev: NOVATEK USB Keyboard: Configuring as keyboard
[ 100.085] (**) evdev: NOVATEK USB Keyboard: YAxisMapping: buttons 4 and 5
[ 100.085] (**) evdev: NOVATEK USB Keyboard: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 100.085] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2:1.1/input/input16/event3"
[ 100.085] (II) XINPUT: Adding extended input device "NOVATEK USB Keyboard" (type: KEYBOARD, id 8)
[ 100.085] (**) Option "xkb_rules" "evdev"
[ 100.085] (**) Option "xkb_model" "evdev"
[ 100.085] (**) Option "xkb_layout" "us"
[ 100.087] (II) config/udev: Adding input device NOVATEK USB Keyboard (/dev/input/event2)
[ 100.088] (**) NOVATEK USB Keyboard: Applying InputClass "evdev keyboard catchall"
[ 100.088] (II) Using input driver 'evdev' for 'NOVATEK USB Keyboard'
[ 100.088] (**) NOVATEK USB Keyboard: always reports core events
[ 100.088] (**) evdev: NOVATEK USB Keyboard: Device: "/dev/input/event2"
[ 100.088] (--) evdev: NOVATEK USB Keyboard: Vendor 0x603 Product 0xf2
[ 100.088] (--) evdev: NOVATEK USB Keyboard: Found keys
[ 100.088] (II) evdev: NOVATEK USB Keyboard: Configuring as keyboard
[ 100.088] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2:1.0/input/input15/event2"
[ 100.088] (II) XINPUT: Adding extended input device "NOVATEK USB Keyboard" (type: KEYBOARD, id 9)
[ 100.088] (**) Option "xkb_rules" "evdev"
[ 100.088] (**) Option "xkb_model" "evdev"
[ 100.088] (**) Option "xkb_layout" "us"
Anyone have a clue what's wrong? Thanks,

Splex wrote:
I also prefer to not run the dongle in bluetooth mode... it causes so many headaches.
There may be a better way to disable the bluetooth mode, but you can comment out the 'Logitech devices' rule in /usr/lib/udev/rules.d/97-bluetooth-hid2hci.rules:
# Logitech devices
#KERNEL=="hiddev*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c70[345abce]|c71[34bc]", \
# RUN+="hid2hci --method=logitech-hid --devpath=%p"
Once you save the changes, simply replug your dongle, hit the connect buttons and it should work as if it is wired.
Whenever udev is upgraded, the rule file will be overwritten... you can add this to your /etc/pacman.conf to prevent it from being overwritten:
NoUpgrade = usr/lib/udev/rules.d/97-bluetooth-hid2hci.rules
If anyone knows of a better way to prevent the default udev rules from switching the dongle to HCI mode, please speak up
Just tried this, didn't work for me :-/
grr.

My bluetooth keyboard won't stay connected. I have to hold the power button to type

wireless keyboard says connected then connection lost. All I did was replace the batteries when the old ones died. Now I have to hold the power button just to type. Seems like a hardware problem not preferences. Any clues?

Hello:
Try resetting the PRAM and SMC.
Then delete a preference file (com.apple.bluetooth.plist) and restart.
Barry

TS1569 Brand new wireless aluminum keyboard will not accept passcode

.......... to pair with brand new macbook air. Apple Care support can't figure this out. Just tried a second, identical keyboard in two days. Same issue. First keyboard worked flawlessly with mid 2010 macbook pro. I'm ******!

I just does not accept that it should be nessecarry to use a usb keyboard when buying a brand new mac!
And luckily I managed to solve this in the end
My setup was is with a keyboard that was previously paired worth my MBP, and I tried a lot of things, but what did it in the end was this:
First I unpaired the keyboard from the MBP using http://support.apple.com/kb/HT1809?viewlocale=en_US&locale=en_US. Only, this time I ignored the first step which reads: "Press and release the On/Off switch on the wireless keyboard to turn it off." Thinking of it, how would the the keyboard know that it is unpaired, if it is turned off?
The 2 thing I did differently this time was that I did not power on the keyboard until it actually said so on the screen. This means that I powered on the Mini, waited until I had selected the language using the Trackpad, waited until the "Connect Keyboard" dialog appeared on the screen. Then I turned on the keyboard in pairing mode...
That's basically what I did to be successful! Hope it will help somebody else

Wireless Aluminum keyboard right half keys not working

THe right half, maybe the right third, keyboard no longer works. I've tried pairing it with different computers and I'm not able to as the return key doesn't work. I tried looking up my warranty online but the serial number keeps coming back as invalid. Is there possibly a way to do a hard reset on the keyboard to see if that would do the trick?

Hello:
Apple does not maintain a database of peripheral devices. The keyboard is under warranty for one year. Either take it to an Apple store or call Applecare (if the device is less than a year old).
Barry

Wireless aluminum keyboard won't stay on

Similar Messages

Maybe you are looking for