Logitech keyboard won't turn on

Just purchased the iPad mini with a logitech keyboard one month ago. The keyboard will not turn on today. Anyone else with a similar problem?

If they are new, the warranty is in effect. Rather than waste time, I would take it back for diagnosis.
Barry

Similar Messages

  • Keyboard won't turn on since 10.6.8 update

    Hi,
    I downloaded the 10.6.8 update yesterday went to bed, got up this morning, went into my iMac woke it with a press off my mouse, but the keyboard was typing! So changed the batteries now the keyboards not turning back on.
    Anyone else having this issue?
    Hugh

    Did you go through the verification process where Apple sends you an e mail for the purpose of verifying that your address is valid?
    If I remember correctly, you must respond to a link in the e mail to verify.

  • 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.

  • Wireless keyboard won't turn on after changing battery

    This is what happened:
    I got a message yesterday telling me that the battery for my wireless keyboard was low and I should replace them. This morning, before I switched on my Mac, I put in new battery for the wireless keyboard. Then I switched on my Mac. And I got a message on the screen saying that There's no keyboard connected and couldn't find any keyboards. I thought that maybe I need to turn on the keyboard to make it work. So I pressed the power button and noticed that the green light doesn't even come up..
    What's going on? Is my wireless keyboard already dead??
    Any advice would be appreciate it. Thanks.

    Possible fix to non pairing blue tooth devices.....
    I have a BTMMouse- quite new. The original lithium batteries died and I replaced them with alkaline. It would connect but refused to pair. Went on the MM discussion board which had over 300 similar problems with both MM and BT keyboards, with absolutely no solutions from Apple or anyone!
    I have an Apple Care plan, so I called and was told to shut down. Then remove the power cord from the back of my iMac, wait one minute, plug it back in. Fire up, and then attempt to set up a new device in BT. It worked on the first try. Then to double check, I shut down and restarted and the mouse stayed connect and paired!

  • TS3048 My Keyboard won't turn on!

    I forgot on my mac it then it wouldnt reconnect then it wouldnt turn on!

    Sounds like something needs returning, but do you have an old USB KB to test with?
    Or...
    Bootup holding CMD+r, or the Option/alt key to boot from the Restore partition & use Disk Utility from there to Repair the Disk, then Repair Permissions.
    If that doesn't help Reinstall the OS.

  • Brand new iMac 21.5" won't turn on - straight out the box

    I just picked up my new iMac today and unpacked it etc, but it won't turn on. The wireless keyboard and mouse are supposed to be paired with it and ready to go, but the on switch on the keyboard won't turn the screen on (as far as I can tell there is no on switch on the iMac itself). The green light on the keyboard keeps blinking but doesn't connect to the iMac to turn it on. I've tried a different power cable in the iMac but that makes no difference. Does anyone know of a solution, or will it have to go back to the shop ( ) ?

    The power switch is locate in the back on the lower left side as you look from the front. Did you connect the power cord and plug in the computer? There is no power button on the keyboard.
    Read the iMac (21.5-inch and 27-inch, Late 2012) - Quick Start Guide.
    Download the user manual: iMac (21.5-inch, Late 2011) - User Guide.

  • I accidentally dropped macbook air that was in a book bag. The keyboard is working because I can see the light but the screen is black and it won't turn off. How should I fix this? Please Help ME!!

    I accidentally dropped my friend's macbook air that was in a book bag. The keyboard is working because I can see the light but the screen is black and it won't turn off. How should I fix this? Please Help ME!!
    I tried to turn it off and it didn't work... and I held on to the shift key too and it still doesn't work..
    Please help me..

    Accidental damage is not covered under Apple warranty.  And it seems there is much accidental damage.  Only a Genius Bar tech looking at it can tell how much it will cost to repair.
    Cost to repair will be high, I suspect (though Genius Bar will confirm/deny.
    There is no gentle way to say this sir/ma'am ... someone will need to pay for your friend's MBA repairs.

  • My macbook pro keyboard backlight won't turn off, even after pressing F5

    my macbook pro keyboard backlight won't turn off, even after pressing F5

    Try resetting the  SMC http://support.apple.com/kb/ht3964

  • Keyboard Lights won't turn ON

    My keyboard lights suddenly won't turn on. I don't know what the problem is. I tried clicking on the F6 button which will turn the lights on, but this time it appears a NO sign when I clicked on it. Please advice.

    Try resetting the NVRAM and SMC. Only reset the SMC if the resetting the NVRAM doesn't work
    Reset NVRAM
    Resetting the System Management Controller (SMC) - Support - Apple

  • My computer won't recognize my usb keyboard when I turn it on.  It keeps searching for a wireless keyboard. How can I get it to recognize my usb keyboard?

    Why won't my computer recognize my usb keyboard when I turn it on?  It keeps trying to find a wireless keyboard.

    Hi there kmacmomma,
    I would recommend taking a look at the troubleshooting steps found in the article below.
    USB and FireWire Quick Assist
    http://support.apple.com/kb/HT1151
    -Griff W.

  • Im using intel macbook pro 13" and since I'm using the new OSX Lion, the keyboard backlit won't turn off and it's eating up my precious battery. Im always mobile so this is very important. Apple doing something to fix this bug immediately?

    Im using intel macbook pro 13" and since I'm using the new OSX Lion, the keyboard backlit won't turn off and it's eating up my precious battery. Im always mobile so this is very important. Apple doing something to fix this bug immediately?

    multiplryan wrote:
    To be totally honest, about 3 weeks prior I spilled some milk from cereal on the desk and a little bit got onto the battery.
    I don't think you have a case.
    You can replace the logic board yourself if you are a DIY'er and save some money.

  • I accidentally turned off bluetooth and now my keyboard won't connect. I already tried to reboot the computer. I can't use the mouse because I ca't get past the user log-in screen. Please help

    I accidentally turned off bluetooth and now my keyboard won't connect. I already tried to reboot the computer. I can't use the mouse because I ca't get past the user log-in screen. Please help

    http://www.cultofmac.com/247979/whoops-reconnect-your-bluetooth-keyboard-and-mac -after-logging-out-os-x-tips/
    had the same problem and it worked!

  • I spilled wine on my laptop keyboard. Now it won't turn on. What can I do?, I spilled wine on my laptop keyboard. Now it won't turn on. What can I do?

    II spilled wine on my laptop keyboard. Now it won't turn on. What can I do?, I spilled wine on my laptop keyboard. Now it won't turn on. What can I do?

    Don't attempt to turn it back on.  Remove the battery if you have a user removable battery.  Take the mac to an Apple Store or AASP and expect a very large repair bill.  More times then not, a liquid spill on a keyboard results in a damaged logic board, which usually costs several hundreds of dollars to replace.  Liquid damage is not covered under warranty if you have AppleCare.  Check with your renters/homeowners insurance to see if it may be covered.

  • Why won't my Apple Wireless keyboard connect or turn off even after holding the button down?

    I have installed windows 8 release preview on my mac mini through boot camp. When pressing alt to choose to boot into mac, I pressed alt too soon and so windows started to load. When it loaded I realised my keyboard was no longer working. The light just flashed. I tried holding the power button to turn it off and normally this would work fine but this time it wouldn't turn off. I took out the batteries and replaced them and it still won't turn off. And even now, it won't connect to my mac mini or my iPad either. I've read on a forum that it might reset if I take the batteries out for 30 mins so I'll try again tomorrow and then report back, but I'm quite annoyed about this!

    It turns out it was faulty batteries!! Just bought an Apple battery charger so will use that from now on!

  • I spilled a little bit of soda on my keyboard ( more like big drops) and my computer won't turn on but it will still charge.  After i spilled it it kept trying to turn on and off by itself until i finally just shut it down

    I spilled a little bit of soda on my keyboard ( more like big drops) and my computer won't turn on but it will still charge.  After i spilled it it kept trying to turn on and off by itself until i finally just shut it down.  Today i tried to turn it back on ( i spilled it last night) and now it won't turn on but when i plug it in the orange light comes on so it still charges.

    TBF: You may have been lucky enough not to cripple your MBP immediately with your spill, but a spill such as you describe will have left obvious traces if you ever need to take your machine in for a repair of any kind. And as soon as evidence of the spill is found, any chance of the necessary repairs being performed under warranty will be gone.
    Taking the machine in now to be cleaned and have the greasy parts replaced will be expensive, but doing so may save whatever remains of your warranty. For a price, Apple will restore the machine to like-new condition, and at the very least, you will then have a 90-day repair warranty on it. If you have significantly more time than that remaining on your original one-year warranty, and especially if you've bought the extended AppleCare Protection Plan, it would probably be worth taking the machine in to a Genius Bar for a look-over. Ask whether, if you have Apple clean and repair the machine now, your new-computer warranty and AppleCare plan will be reinstated afterward or whether all you'll have is the short repair warranty from now on. If the spill will negate your warranty and AppleCare even if you have Apple clean it, then the cleaning probably isn't worth paying for. But if paying for the cleaning will get your warranty and AppleCare reinstated, it may be worth doing.

Maybe you are looking for

  • USB ethernet does not work in left USB port

    My USB ethernet adapter does not work in the left USB port on my MacBook Air, but it works in the right side. Other devices, like my mouse, work fine in both ports. Could I have a faulty left-side port with too little power for the ethernet adapter,

  • Problem with Outlook2010 icloud calendars sync

    Hi, I use Outlook2010 and icloud and I have the problem that I can only add 14 individual calendars in Outlook with which icloud syncronisation functionates properly. When I want to add a 15th calendar then Outlook doesn't add the calendar to //iclou

  • Using and Sharing a CRT monitor w/a PC

    Hello all, I'm curious if I can use a CRT monitor as a second monitor with my Imac(Intel 24in. 2.4 GHz, for an extended desktop, etc. I'd also like to know if I could share the monitor with a PC with a KVM-type switch... If doing these is possible, w

  • Exception message 20 and reorderpoint

    After searching for information on why SAP gives message 20 if the net requirement is above the reorderpoint i never to the needed information. Yes i am able to see that if reorderpoint is 100 and due to a lot size of 50 pc then naturally we will be

  • Billing Cycle & Payments due by Dates

    I don't understand why the billing cycle ends after the bill/payment is due! For instance if I have to pay by the 30th of the month then why does my billing cycle end a week after I paid you? By the we are going over our already allowed plan of 40GB