Magic Mouse and OS X Mavericks

Try resetting the PRAM and SMC...might help.

Barry

I have the same problem..and more!

My Imac cant detect Ethernet either anymore..it says my network cable is not plugged in, but it was perfectly fine before the update.

Also, if i logout, it wont let me login again. I had to enable automatic login to by pass this. Basically when i enter my password it logs me in and then immedeately takes me back to the login page!

I will try the PRAM and SMC stuff tomorrow morning and see.

Anyone else with this problem/solved it?

Tried already, not working thought. Any other ideas? Thanks in advance.

I've tried everything, and nothing works.

I've even reinstalled Mavericks from recovery mode and nothing...the same problems!

I have done the PRAM reset and the SCM...nothing..

What can i do? i need my ethernet to work!! plus i need to be able to re-apply the login features for security..

Hi,

same problem here, MB Aluminum late 2008: PRAM doesn't work while SMC reset fix the problem for... a while, few minutes Maverick freeze. After a reboot bluetooth is again "Not Available".

Alessandro

Ditto - seems that it likley has to do with a Bluetooh problem, as mine reads "Bluetooth: Not Available" in the menu bar. See this thread.

Details on my box:

Model Name: iMac

Model Identifier: iMac12,1

Processor Name: Intel Core i5

Processor Speed: 2.7 GHz

Number of Processors: 1

Total Number of Cores: 4

L2 Cache (per Core): 256 KB

L3 Cache: 6 MB

Memory: 8 GB

Boot ROM Version: IM121.0047.B1F

SMC Version (system): 1.71f21

This is also effecting my keyboard - oddly everything works, at the most basic level, but the scroll functions on the mouse do not, and the volume buttons etc. on the F-keys do not work on the keyboard.

Same issue here on my mid-2010 15" MBP.

same problem

try to open sistem preferenc and set mouse again

now work right

1. Shutdown your Mac.

2. Restart your Mac with CMD + R.

3. Reinstall Mac OSX Mavericks.

Worked for me!!

Guess the same problem: bluetooth is missing from the whole OS , but still works partly (no prefs, and Magic Mouse can't scroll). Just as with ML 10.8.5 (had to roll back to an TM backup there), and the same with first ML upgrade (reinstalling with cmd-R on startup helped that time).

PRAM and SMC resets does not work for this problem...

Mid-´10 MBP 17".

I have the same issue here. iMac mid 2011. I have already tried all sugestions above. No luck. One thing though when I've installed Maveriks I did it on my HSSD and I still have Mountain LIon installed on my HDD. If I start from there bluetooth works fine.

The following worked 100% for me, and as I read all these replies, sounds like nobody has yet done it?

Sure, it takes about 2 hours, but is that worth it to have everything working again? YES!

1. Shutdown your Mac.

2. Restart your Mac with CMD + R.

3. Reinstall Mac OSX Mavericks. <<< not a roll back via Time Machine, or anything, full fledged reinstall.

I have already done that twice with no such luck!

Reinstalled Mavericks twice (not from TM).

Trashed the bluetooth .plist-file twice,

Repaired filepermissions twice.

Added new admin user account.

SMC- and PRAM reset between all of these.

Nothing seems to fix this. Guess going back to 10.8.4 is the only sollution. Silly...

I've found an article about it last night About a problem with bluetooth with a fix, but that was on Mountain Lion! 😕

Apple releases new firmware and OS X 10.8.5 updates for Late-2013 iMacs

http://www.tuaw.com/2013/10/24/apple-releases-new-firmware-and-os-x-10-8-5-updat es-for-late-201/

I do have an opened case service with Apple about it. It seems that i have Maveriks on my HD and Mountain Lion on my SSD, they think that could be the problem.

I am backing up some stuff before let them do anything on my computer, just to be safe! If I boot my computer trough the ML HD Bluetooth is back on line. If I reboot from the SSD no such luck!

I have already upgraded on my MacBook Air mid 2013 and on my iMac 24inch mid 2008 and everything is running smooth! Since on those two i do have only one HD maybe that's really the issue. Let's see.

Message was edited by: Tom Tacla