mactel-support team mailing list archive

[Martin Capitanio <201711@xxxxxxxxxxxxxxxxxx>]

The best way to fix this (worked well for me for several years)
is to append the needed module parameters to the kernel command line.

sudo vi /etc/default/grub
and change
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
to
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash hid_apple.fnmode=2"

or
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash hid_apple.fnmode=2 hid_apple.iso_layout=0"

--

modinfo hid_apple
parm:           fnmode:Mode of fn key on Apple keyboards (0 = disabled, [1] = fkeyslast, 2 = fkeysfirst) (uint)
parm:           iso_layout:Enable/Disable hardcoded ISO-layout of the keyboard. (0 = disabled, [1] = enabled) (uint)

-- 
You received this bug notification because you are a member of Mactel
Support, which is the registrant for Mactel Support.
https://bugs.launchpad.net/bugs/201711

Title:
  Apple fn key behavior isn't consistent with what's expected

Status in Mactel Support:
  New
Status in “linux” package in Ubuntu:
  Confirmed
Status in “linux” package in Suse:
  Fix Released

Bug description:
  Hi, this is a follow up to bug 162083.  With my newly functional FN
  key on my Aluminum BT keyboard, I realized that the default behavior
  on it doesn't make much sense with what users have come to expect on
  Linux systems.  The default behavior is that the "special keys", like
  f1-f2-f10-f11-etc all act "special" without pressing fn.  They then
  act normally when you hold FN.  This is the default behavior on Mac
  OSX, but on Linux the FN keys are more commonly used.  Eg, it's rather
  awkward to have to press ctrl-alt-fn-f1 to switch to a VT, or FN-F11
  to set a terminal full screen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mactel-support/+bug/201711/+subscriptions