Hi,
I have been tracking various complaints the volume fn keys being disabled but have found no solution yet.
My problem is that since upgrading to ML 10.8.1 (Clean Install) my imac (3.06 GHz Intel Core i3) with wired keyboard and numeric keypad has disabled the Mute (f10) and Volume down (f11) keys, the volume up (f12) still operates.
I can lower the volume by the slider of via my old macbook remote. As regards settings both internal speakers and internal microphone are set as output and input respectively. As regards trouble shooting I have tried:
i) restarting
ii) resetting PRAM/NVRAM (holding down alt+cmd+r=p)
iii) Clean installation of ML
iv) plugging and unplugging headphones
v) remapping keys as a workaround but it seems the keys themselves are disabled to any function
I have not yet tried to delete preference files as I am unsure of the correct procedure and most threads seem to suggest this has only been effective as a temporary fix.
This does appear to be a update issue in across lion generally. Any ideas guys? It's no massive drama but I like my tools to be fit for purpose!
Thanks in advance.
I have been tracking various complaints the volume fn keys being disabled but have found no solution yet.
My problem is that since upgrading to ML 10.8.1 (Clean Install) my imac (3.06 GHz Intel Core i3) with wired keyboard and numeric keypad has disabled the Mute (f10) and Volume down (f11) keys, the volume up (f12) still operates.
I can lower the volume by the slider of via my old macbook remote. As regards settings both internal speakers and internal microphone are set as output and input respectively. As regards trouble shooting I have tried:
i) restarting
ii) resetting PRAM/NVRAM (holding down alt+cmd+r=p)
iii) Clean installation of ML
iv) plugging and unplugging headphones
v) remapping keys as a workaround but it seems the keys themselves are disabled to any function
I have not yet tried to delete preference files as I am unsure of the correct procedure and most threads seem to suggest this has only been effective as a temporary fix.
This does appear to be a update issue in across lion generally. Any ideas guys? It's no massive drama but I like my tools to be fit for purpose!
Thanks in advance.