I’m having a problem with the Fn keys. When I press Fn, it turns the microphone on and off. But the F1–F12 shortcuts work as they should without holding down Fn.
I’m using a Gigabyte GAMING A16 3WH laptop. I couldn’t find a setting in the BIOS that controls keyboard shortcuts.
Is there a chance that future updates will fix this issue?
I think this is more something you can change in the settings > keyboard > keyboard shortcuts.
Just for your information, my keyboard is a Logitech K230. If I do press FN & F10 it switches the Audio on/off. While using FN & F11 + F12 It decreases/increases the volume. However I do have the speaker symbols on this keys of my keyboard. Can you confirm something like this too?
Otherwise as mentioned above you can overwrite this shortcuts … I think
In my case, the Fn key mutes the microphone. Fn + F1 is supposed to mute the sound, but nothing happens. However, if I press justF1, the sound is muted or unmuted.
Yes, the keyboard has labels for the shortcut keys.
Different keyboards have different mapping.
My Logitek K350 has a group of keys above the normal key rows that control the media, as well as having specific functions printed on the F1-F12 keys for additional actions when using the Fn key.
As already mentioned, key mappings can be (re)configured under settings → keyboard → keyboard shortcuts.
I use a laptop. Here’s what the keyboard looks like
In my case, the Fn key mutes the microphone. Fn + F1 is supposed to mute the sound, but nothing happens. However, if I press justF1, the sound is muted or unmuted.
You may need to remove the current mapping before creating a new mapping. Be aware that not all key mappings can be altered as some are hard coded.
The defaults do not always match the keycodes that the keyboard provides. The defaults are coded for a standard keyboard and many keyboards vary from the standard.
The key markings show that Fn+F1 should mute/unmute the sound. Similarly it shows that Fn+F4 should mute/unmute the mic. Some keyboards use the Fn as a toggle and it is either on or off, while others require it to be held to provide the function mode. Have you tested with a single push of the Fn if it may be acting as a toggle or not?
The OS immediately recognizes Fn as AudioMicMute, F1 as Audio Mute, F5 as Monitor Brightness Down, and so on.
In my case, the Fn key mutes the microphone. Fn + F1 is supposed to mute the sound, but nothing happens. However, if I press justF1, the sound is muted or unmuted.
Even if we look at the settings using volume adjustment as an example, there are no assigned keyboard shortcuts in the OS settings. Nevertheless, if I press F3 (withoutFn), the volume goes up, and if I press F2 (withoutFn), the volume goes down.
I can’t assign Fn + anything in the settings. I can’t assign F1–F12 + anything in the settings because the OS recognizes these keys and won’t let me combine Fn + F2, for example.
This sound as if the Fn key is locked on by codes from the keyboard and that possibly the generic functions are reached by holding the Fn key down, which would be the opposite of the expected actions.
There is a command that when run would provide on screen the actual keycodes seen when pressing and releasing each key (two separate codes), but it has been so long since I used that command that I don’t remember what it is. Maybe someone else can assist in that regard.
The “supposed to” is in line with the manual, but the actual behaviour isn’t.
I wonder if the expected behaviour depends on some proprietary app running in Windows, and the manufacturer hasn’t properly considered how to support Linux.
First of all, the manual has not to be the correct one. I just took the one I found. I am sure that the OP got a link or first steps to check the correct place. I also think the Laptop was made for windows and not for Linux.
What I would do now:
Checking the correct manual for the specific model and see if this is the same as described on the screenshot.
1.1 verifier hardware (https://linux-hardware.org/)
Try to update with fwupdmgr get-devices
Using a live ISO from windows and check if it is also wrong. If yes
Contacting support from Gigabyte to ask for assistance.
This is the correct manual. I listed the exact laptop model, and I described how things should work in theory and how they actually work in practice.
GIGABYTE GIGABYTE GAMING A16 3WH
│
├─GIGABYTE FHD CAMERA:
│ Device ID: 3ead601f43028c79656941fc3832e6b67412e2b8
│ Current version: 0.3
│ Vendor: Sonix Technology Co., Ltd. (USB:0x3277)
│ Serial Number: SN0001
│ GUID: 56d7b5eb-3c88-5fd2-a265-4b970a26621d ← USB\VID_3277&PID_00B2
│ Device Flags: • Updatable
│ • Can tag for emulation
│
├─OM8PGP41024Q-A0:
│ Device ID: 04e17fcf7d3de91da49a163ffe4907855c3648be
│ Summary: NVM Express solid state drive
│ Current version: ELFK0S.6
│ Vendor: Kingston (PCI:0x2646)
│ Serial Number: 50026B768778B3A3
│ Problems: • Device requires AC power to be connected
│ GUIDs: 8d8bb244-e5f3-566e-b747-6fbc5c6c26df ← NVME\VEN_2646&DEV_501B
│ 4e746dd6-8c81-5e42-86cb-ce12e875b5ea ← NVME\VEN_2646&DEV_501B&SUBSYS_2646501B
│ 7cb2c61b-5edb-51b6-8510-c03fccacb42c ← KINGSTON OM8PGP41024Q-A0
│ Device Flags: • Internal device
│ • System requires external power source
│ • Needs shutdown after installation
│ • Device is usable for the duration of the update
│ • Updatable
│ • Can tag for emulation
│
├─Ryzen 7 260 w/ Radeon 780M Graphics:
│ │ Device ID: 4bde70ba4e39b28f9eab1628f9dd6e6244c03027
│ │ Current version: 0x0a70520a
│ │ Vendor: AMD
│ │ GUIDs: 09243cb6-ee6a-50fb-9438-c5643d6302be ← CPUID\PRO_0&FAM_19&MOD_75
│ │ 88c5027f-27f8-534c-af31-4f0a21d90d5d ← CPUID\PRO_0&FAM_19&MOD_75&STP_2
│ │ Device Flags: • Internal device
│ │
│ ├─Radeon 780M Graphics:
│ │ │ Device ID: 5195f11e5982a0f0c2ff0fe6cf84a36ce3dbc7c5
│ │ │ Summary: AMD AMD_PHOENIX_GENERIC
│ │ │ Current version: 1
│ │ │ Vendor: AMD (PCI:0x1002)
│ │ │ GUID: 4a1501b7-b500-5255-9d9c-41d652a4d5bc ← AMD\113-PHXGEN
│ │ │ Device Flags: • Internal device
│ │ │ • Can tag for emulation
│ │ │
│ │ └─NE160WUM-NX6:
│ │ Device ID: aec1a869eb0df71b7cea6b3ac71d39b830faf164
│ │ Vendor: PNP:BOE
│ │ GUID: b9f4b0eb-bb19-5db3-aaec-eb936ee0c5fa ← DRM\VEN_BOE&DEV_0B77
│ │
│ ├─Secure Processor:
│ │ Device ID: c54ab0237d7a8db8c717b68e0be78e4374a2a079
│ │ Summary: AGESA PhoenixPI-FP8-FP7 1.2.0.0d
│ │ Current version: 00.2d.00.87
│ │ Bootloader Version: 00.2d.00.87
│ │ Vendor: AMD (PCI:0x1022)
│ │ GUID: 9eb6a793-7f97-5fb5-b49c-139d2ce3ee46 ← PCI\VEN_1022&DEV_15C7
│ │ Device Flags: • Internal device
│ │ • Can tag for emulation
│ │
│ ├─System Management Unit (SMU):
│ │ Device ID: db0330716216c629bb2c07256e5d018f499eb6ce
│ │ Summary: Microcontroller used within CPU/APU program 0
│ │ Current version: 76.98.0
│ │ Vendor: AMD
│ │ GUID: 3ac3159e-6eef-5f6b-bc8d-67686b238747 ← /sys/devices/platform/AMDI0009:00
│ │ Device Flags: • Internal device
│ │ • Can tag for emulation
│ │
│ └─TPM:
│ Device ID: 1d8d50a4dbc65618f5c399c2ae827b632b3ccc11
│ Current version: 6.4.1.383
│ Vendor: Microsoft (TPM:MSFT)
│ GUIDs: 2a65d4b6-60a0-5e8c-acfa-d86cc3cbe4c3 ← TPM\VEN_MSFT&DEV_0001
│ 31a7bb1b-f5e1-53ff-b0e5-8692a21caed6 ← TPM\VEN_MSFT&MOD_Pluton.TPM.A
│ 5bea8d58-c840-513e-a5ad-0184cbaa9821 ← TPM\VEN_MSFT&DEV_0001&VER_2.0
│ e02519c6-9139-5de8-89d4-9dca2f5c3b66 ← TPM\VEN_MSFT&MOD_Pluton.TPM.A&VER_2.0
│ Device Flags: • Internal device
│ • System requires external power source
│ • Needs a reboot after installation
│ • Device can recover flash failures
│ • Signed Payload
│ • Can tag for emulation
│
└─System Firmware:
│ Device ID: fa4f90a78027b8ff19e21cea790f8dd55e69f449
│ Summary: UEFI System Resource Table device (updated via NVRAM)
│ Current version: 36
│ Minimum Version: 36
│ Vendor: GIGABYTE (DMI:American Megatrends International, LLC.)
│ Update State: Success
│ Problems: • Device requires AC power to be connected
│ GUID: 0316897e-e260-4f3e-bada-97cdb923f50c
│ Device Flags: • Internal device
│ • System requires external power source
│ • Needs a reboot after installation
│ • Cryptographic hash verification is available
│ • Device is usable for the duration of the update
│ • Updatable
│ Device Requests: • Message
│
├─GIGABYTE:
│ Device ID: 6924110cde4fa051bfdc600a60620dc7aa9d3c6a
│ Summary: UEFI Platform Key
│ Current version: 2023
│ Vendor: Unknown
│ GUID: 5cc35aba-c97c-56a6-a5e9-28371aa1e47c ← UEFI\CRT_84C928EADE77149A64A3000E431757DC6EF5D390
│ Device Flags: • Internal device
│
├─UEFI Key Exchange Key:
│ │ Device ID: 2a4c23bfb79b5dabe474cb7b1b3e604645d6f9c6
│ │ Device Flags: • Internal device
│ │
│ ├─GIGABYTE:
│ │ Device ID: 270d8545b9d737fc201ea763bce6cbf310093a9f
│ │ Current version: 2023
│ │ Update Error: No vendor ID set
│ │ GUID: a8048e4d-1286-5f3f-a3c7-cd7fed322323 ← UEFI\CRT_136A276BEEC8A622D8C9A55DB40A8FC6C5A87329
│ │ Device Flags: • Internal device
│ │ • Needs a reboot after installation
│ │ • Device is usable for the duration of the update
│ │ • Updatable
│ │ • Signed Payload
│ │ • Can tag for emulation
│ │
│ └─KEK CA:
│ Device ID: b7a1d3d90faa1f6275d9a98da4fb3be7118e61c7
│ Current version: 2023
│ Vendor: Microsoft (UEFI:Microsoft)
│ URL: https://fwupd.github.io/libfwupdplugin/uefi-db.html
│ GUIDs: 814e950f-1449-566a-a190-42c9d3a3a2df ← UEFI\VENDOR_Microsoft&NAME_Microsoft-KEK-CA
│ cd94ec34-7163-5f27-8549-1bd4b7872ae8 ← UEFI\CRT_DEC64D7746D983DB3774829A00BF829D9F19E9CF
│ Device Flags: • Internal device
│ • Updatable
│ • Needs a reboot after installation
│ • Device is usable for the duration of the update
│ • Signed Payload
│ • Can tag for emulation
│
├─UEFI Signature Database:
│ │ Device ID: 0352a8acc949c7df21fec16e566ba9a74e797a97
│ │ Device Flags: • Internal device
│ │
│ ├─GIGABYTE:
│ │ Device ID: 9846ded5bff31ca8c4260af8327919d939484bc3
│ │ Current version: 2023
│ │ Update Error: No vendor ID set
│ │ GUID: e851f955-58ee-578e-b2d6-06b8b1ec59c0 ← UEFI\CRT_3B0E79385516792F20EFD2637C2645C3829394E8
│ │ Device Flags: • Internal device
│ │ • Needs a reboot after installation
│ │ • Updatable
│ │ • Signed Payload
│ │ • Can tag for emulation
│ │
│ ├─UEFI CA:
│ │ Device ID: 5bc922b7bd1adb5b6f99592611404036bd9f42d0
│ │ Current version: 2023
│ │ Vendor: Microsoft (UEFI:Microsoft)
│ │ URL: https://fwupd.github.io/libfwupdplugin/uefi-db.html
│ │ GUIDs: 26f42cba-9bf6-5365-802b-e250eb757e96 ← UEFI\VENDOR_Microsoft&NAME_Microsoft-UEFI-CA
│ │ 308281c7-d0c5-52e0-8c1a-810540de03df ← UEFI\CRT_7CD7437C555F89E7C2B50E21937E420C4E583E80
│ │ Device Flags: • Internal device
│ │ • Updatable
│ │ • Supported on remote server
│ │ • Needs a reboot after installation
│ │ • Signed Payload
│ │ • Can tag for emulation
│ │
│ └─Windows UEFI CA:
│ Device ID: d31da5f926c6d962ed810b284fab5a2ef623007b
│ Current version: 2023
│ Vendor: Microsoft (UEFI:Microsoft)
│ URL: https://fwupd.github.io/libfwupdplugin/uefi-db.html
│ GUIDs: 914015a8-9d92-5462-9a9b-f2b361e4faae ← UEFI\VENDOR_Microsoft&NAME_Windows-UEFI-CA
│ 89a825bf-78b5-5f1c-905b-e982b2f02584 ← UEFI\CRT_A794240D25F0CCB2EC8142DC2F7411890717DEAD
│ Device Flags: • Internal device
│ • Updatable
│ • Supported on remote server
│ • Needs a reboot after installation
│ • Signed Payload
│ • Can tag for emulation
│
└─UEFI dbx:
Device ID: 362301da643102b9f38477387e2193e57abaa590
Summary: UEFI revocation database
Current version: 20260402
Minimum Version: 20260402
Vendor: Microsoft (UEFI:Microsoft)
URL: https://uefi.org/revocationlistfile
Install Duration: 1 second
GUIDs: d07ff664-b0e1-5f4e-a723-d7fbcbfcb94f ← UEFI\CRT_3CD3F0309EDAE228767A976DD40D9F4AFFC4FBD5218F2E8CC3C9DD97E8AC6F9D&ARCH_X64
f8ba2887-9411-5c36-9cee-88995bb39731 ← UEFI\CRT_A1117F516A32CEFCBA3F2D1ACE10A87972FD6BBE8FE0D0B996E09E65D802A503&ARCH_X64
b621f4ef-160a-5139-9fb1-6e89d03cc8db ← UEFI\CRT_81CAE10B24C40F687D7E695BBCFA02AF635148588B35712A25C2FCDA16DC776C&ARCH_X64
Device Flags: • Internal device
• Updatable
• Supported on remote server
• Needs a reboot after installation
• Device is usable for the duration of the update
• Only version upgrades are allowed
• Signed Payload
• Can tag for emulation
made for windows and not for Linux
That’s obvious. The manufacturer recommends Windows only, and users have discussed a similar issue with other laptop models from this manufacturer. No, this isn’t about configuring keyboard shortcuts in the settings or a possible lack of knowledge about how to use keyboard shortcuts. I have described the actual experience and the expected experience several times
That sounds interesting, but since my laptop model is from a different manufacturer, I assume the content of the file must be different. Also, the system recognizes the Fn key, but for some reason thinks that this key should control the microphone
