не работают кнопки F1, F2 и т.д.

yafantik · 2026-01-06 10:05:08

абсолютно не работают кнопки F1, F2 и т.д. а также Fn. Как бы когда я кликаю на f1 у меня уменшается яркость моника, f2 увеличивается. я не понимаю прикола это такая фишка у KDE Plasma на Wayland? Я до этого сидел с тестового стэнда чисто по приколу тестил и веселился с линуксом, и вот поставил этот мой хард с линуксом в свой основной пк, и тут такое. alt+f4 не работает.
здесь распишу что делает каждая моя кнопка:
F1 - уменшает яркость
F2 - увеличивает яркость
F3 - ничего
F4 - ничего
F5 - ничего
F6 - ничего
F7 - переключает на предыдущий трэк в плейлисте (когда я кнч слушаю музыку)
F8 - пауза/пуск песни
F9 - переключает на следующий трэк в плейлисте
F10 - audio muted
F11 - volume -
F12 - volume +

я ещё новый в этой теме линукса и мне надо порой задать тупой но важный для меня вопрос, как бы даже уверен что нет тупых ответов есть только негативная реакция на то что человек чего то не знает.
буду благодарен любым советам, и хочу найти решение этой истории, так как я даже не могу выйти в TTY если поломается графическая оболочка.

вывод screenfetch (ненужные детали вырезал*)
OS: Arch Linux
Kernel: x86_64 Linux 6.18.3-arch1-1
Packages: 1441
Shell: zsh 5.9
Resolution: 1920x1080
DE: KDE
WM: KWin
GTK Theme: Breeze-Dark [GTK2], Breeze [GTK3]
Icon Theme: breeze-dark
Disk: 939G / 1.9T (53%)
CPU: AMD Ryzen 5 3600 6-Core @ 12x 4.90986GHz
GPU: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] (rev a1)
RAM: 5169MiB / 15911MiB

Last edited by yafantik (2026-01-06 10:14:30)

seth · 2026-01-06 10:55:16

That's the fnlock, most notebooks have a physical feature for this - but it depends very much on the exact hardware (notebook model/vendor) where and how to trigger this.

yafantik · 2026-01-06 23:00:37

seth wrote:

That's the fnlock, most notebooks have a physical feature for this - but it depends very much on the exact hardware (notebook model/vendor) where and how to trigger this.

yes, but i use a normal computer, not notebook. it's different problem then other.
i remember write a keybord model:
ajazz ak816 pro
so i have no idea how to fix it
and idk can i post that at any other topic on forum?

Last edited by yafantik (2026-01-06 23:04:39)

seth · 2026-01-07 08:02:44

Did you already try Fn+escape ?

yafantik · 2026-01-07 08:08:32

seth wrote:

That's the fnlock, most notebooks have a physical feature for this - but it depends very much on the exact hardware (notebook model/vendor) where and how to trigger this.

and currently i saw on the keyboard manual and test the fn keys with f2-f3, and that keybinds work correctly.
https://epomaker.com/cdn/shop/files/AK816-Manual.pdf?v=
i want to use alt + f4 for rageexit but this impossible.
i think that is kde problem, maybe by wayland.

Last edited by yafantik (2026-01-07 08:12:24)

yafantik · 2026-01-07 08:17:00

seth wrote:

Did you already try Fn+escape ?

yes

seth · 2026-01-07 09:00:18

sudo evtest

What events to F4 and Fn+F4 generate?

yafantik · 2026-01-07 15:13:13

seth wrote:

sudo evtest
What events to F4 and Fn+F4 generate?

Event: time 1767797780.859589, -------------- SYN_REPORT ------------
Event: time 1767797784.550588, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7003a
Event: time 1767797784.550588, type 1 (EV_KEY), code 224 (KEY_BRIGHTNESSDOWN), value 1.........} F1
Event: time 1767797784.550588, -------------- SYN_REPORT ------------
Event: time 1767797784.618589, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7003a
Event: time 1767797784.618589, type 1 (EV_KEY), code 224 (KEY_BRIGHTNESSDOWN), value 0


Event: time 1767797784.618589, -------------- SYN_REPORT ------------
Event: time 1767797787.311584, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7003b
Event: time 1767797787.311584, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), value 1................. }F2
Event: time 1767797787.311584, -------------- SYN_REPORT ------------
Event: time 1767797787.349586, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7003b
Event: time 1767797787.349586, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), value 0


Event: time 1767797787.349586, -------------- SYN_REPORT ------------
Event: time 1767797800.996650, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7003c
Event: time 1767797800.996650, type 1 (EV_KEY), code 120 (KEY_SCALE), value 1.................................... }F3
Event: time 1767797800.996650, -------------- SYN_REPORT ------------
Event: time 1767797801.086648, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7003c
Event: time 1767797801.086648, type 1 (EV_KEY), code 120 (KEY_SCALE), value 0


Event: time 1767797801.086648, -------------- SYN_REPORT ------------
Event: time 1767797802.474574, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7003d
Event: time 1767797802.474574, type 1 (EV_KEY), code 204 (KEY_DASHBOARD), value 1.........................}F4
Event: time 1767797802.474574, -------------- SYN_REPORT ------------
Event: time 1767797802.557600, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7003d
Event: time 1767797802.557600, type 1 (EV_KEY), code 204 (KEY_DASHBOARD), value 0


Event: time 1767797802.557600, -------------- SYN_REPORT ------------
Event: time 1767797803.704634, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7003e
Event: time 1767797803.704634, type 1 (EV_KEY), code 229 (KEY_KBDILLUMDOWN), value 1...................}F5
Event: time 1767797803.704634, -------------- SYN_REPORT ------------
Event: time 1767797803.765570, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7003e
Event: time 1767797803.765570, type 1 (EV_KEY), code 229 (KEY_KBDILLUMDOWN), value 0


Event: time 1767797803.765570, -------------- SYN_REPORT ------------
Event: time 1767797804.642565, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7003f
Event: time 1767797804.642565, type 1 (EV_KEY), code 230 (KEY_KBDILLUMUP), value 1..........................}F6
Event: time 1767797804.642565, -------------- SYN_REPORT ------------
Event: time 1767797804.702568, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7003f
Event: time 1767797804.702568, type 1 (EV_KEY), code 230 (KEY_KBDILLUMUP), value 0


Event: time 1767797804.702568, -------------- SYN_REPORT ------------
Event: time 1767797805.895571, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70040
Event: time 1767797805.895571, type 1 (EV_KEY), code 165 (KEY_PREVIOUSSONG), value 1.....................}F7
Event: time 1767797805.895571, -------------- SYN_REPORT ------------
Event: time 1767797805.963655, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70040
Event: time 1767797805.963655, type 1 (EV_KEY), code 165 (KEY_PREVIOUSSONG), value 0    

            
Event: time 1767797805.963655, -------------- SYN_REPORT ------------
Event: time 1767797806.420564, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70041
Event: time 1767797806.420564, type 1 (EV_KEY), code 164 (KEY_PLAYPAUSE), value 1..............................}F8
Event: time 1767797806.420564, -------------- SYN_REPORT ------------
Event: time 1767797806.480565, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70041
Event: time 1767797806.480565, type 1 (EV_KEY), code 164 (KEY_PLAYPAUSE), value 0


Event: time 1767797806.480565, -------------- SYN_REPORT ------------
Event: time 1767797807.666562, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70042
Event: time 1767797807.666562, type 1 (EV_KEY), code 163 (KEY_NEXTSONG), value 1..............................}F9
Event: time 1767797807.666562, -------------- SYN_REPORT ------------
Event: time 1767797807.726563, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70042
Event: time 1767797807.726563, type 1 (EV_KEY), code 163 (KEY_NEXTSONG), value 0


Event: time 1767797807.726563, -------------- SYN_REPORT ------------
Event: time 1767797808.619632, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70043
Event: time 1767797808.619632, type 1 (EV_KEY), code 113 (KEY_MUTE), value 1.........................................}F10
Event: time 1767797808.619632, -------------- SYN_REPORT ------------
Event: time 1767797808.686563, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70043
Event: time 1767797808.686563, type 1 (EV_KEY), code 113 (KEY_MUTE), value 0


Event: time 1767797808.686563, -------------- SYN_REPORT ------------
Event: time 1767797809.654559, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70044
Event: time 1767797809.654559, type 1 (EV_KEY), code 114 (KEY_VOLUMEDOWN), value 1.........................}F11
Event: time 1767797809.654559, -------------- SYN_REPORT ------------
Event: time 1767797809.722563, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70044
Event: time 1767797809.722563, type 1 (EV_KEY), code 114 (KEY_VOLUMEDOWN), value 0


Event: time 1767797809.722563, -------------- SYN_REPORT ------------
Event: time 1767797810.570555, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70045
Event: time 1767797810.570555, type 1 (EV_KEY), code 115 (KEY_VOLUMEUP), value 1.................................}F12
Event: time 1767797810.570555, -------------- SYN_REPORT ------------
Event: time 1767797810.630557, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70045
Event: time 1767797810.630557, type 1 (EV_KEY), code 115 (KEY_VOLUMEUP), value 0

and how it must output:

   Event code 59 (KEY_F1)
    Event code 60 (KEY_F2)
    Event code 61 (KEY_F3)
    Event code 62 (KEY_F4)
    Event code 63 (KEY_F5)
    Event code 64 (KEY_F6)
    Event code 65 (KEY_F7)
    Event code 66 (KEY_F8)
    Event code 67 (KEY_F9)
    Event code 68 (KEY_F10)
    Event code 87 (KEY_F11)
    Event code 88 (KEY_F12)

and how it look in my situation:

    Event code 224 (KEY_BRIGHTNESSDOWN).........F1

    Event code 225 (KEY_BRIGHTNESSUP)...............F2

    Event code 120 (KEY_SCALE)................................F3

    Event code 204 (KEY_DASHBOARD)....................F4

    Event code 229 (KEY_KBDILLUMDOWN)............F5

    Event code 230 (KEY_KBDILLUMUP)...................F6

    Event code 165 (KEY_PREVIOUSSONG)..............F7

    Event code 164 (KEY_PLAYPAUSE).......................F8

    Event code 163 (KEY_NEXTSONG).......................F9

    Event code 113 (KEY_MUTE).................................F10

    Event code 114 (KEY_VOLUMEDOWN)................F11

    Event code 115 (KEY_VOLUMEUP).......................F12

*I personally indicated everything with a dotted line, cuz i'm autistic and i must do this;3

And on result using Fn+F* just provoke keyboard default keybinds (who's manual i'll leaved in this post/topic(idk currently xddddd))

Last edited by yafantik (2026-01-07 15:31:59)

seth · 2026-01-07 16:08:22

Please use [code][/code] tags, the BBS predates markdown. Edit your post in this regard.

This doesn't change at all when pressing the Fn key?
Have you consulted the keyboards manual about this?
This *is* some fnlock, but there's no standard on that (fn+esc is just a very common toggle)

yafantik · 2026-01-07 18:47:26

seth wrote:

Please use [code][/code] tags, the BBS predates markdown. Edit your post in this regard.
This doesn't change at all when pressing the Fn key?
Have you consulted the keyboards manual about this?
This *is* some fnlock, but there's no standard on that (fn+esc is just a very common toggle)

When I noticed that my formatting wasn’t working as expected, I checked the official Arch BBS help page:
https://bbs.archlinux.org/help.php#code:~:text=Code

That’s where I confirmed how code blocks are supposed to be used here.

Regarding the actual issue:

When Fn is held, all factory-programmed bindings on my keyboard work correctly.

I already checked the manual and even linked it earlier (I can re-check or look for additional information online if needed).

As for the third point — yes, I also came to the conclusion that Fn handling can be hit-or-miss on Linux. However, the same keyboard works perfectly fine under Windows. I also tried switching the keyboard into macOS mode, but that didn’t change anything.

This is actually the first time I used an AI tool — specifically to help break someone else’s explanation into clearer, more understandable parts.

At this point, I still believe there should be a way to adjust how the system interprets key codes. Since F1–F12 generate identifiable key events, it seems plausible that this could be fixed or remapped at a lower level.

Linux is often described as an OS where the user has full control over the system, so I’m going to keep digging until I either find a solution or understand exactly where the limitation is.

Last edited by yafantik (2026-01-07 18:53:59)

seth · 2026-01-07 20:08:02

can be hit-or-miss on Linux. However, the same keyboard works perfectly fine under Windows.

This isn't necessarily a "linux" thing, if the keyboard sends the "wrong" keycodes - there isn't much the OS could do about that (see below in case this shows up as an Apple keyboard)

As for "works perfectly fine under Windows":
See the 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.
Also and especially https://wiki.archlinux.org/title/Blueto … ot_pairing if you're using bluetooth.

Since F1–F12 generate identifiable key events, it seems plausible that this could be fixed or remapped at a lower level.

Sure, https://wiki.archlinux.org/title/Input_remap_utilities - it's just the "wrong" solution and you'd lose access to the "special" keys if you cannot make Fn+F1 and F1 generate different events.

I also tried switching the keyboard into macOS mode

Do you load

lsmod | grep hid_apple

?
https://wiki.archlinux.org/title/Apple_ … le_options

specifically to help break someone else’s explanation into clearer, more understandable parts

Or to translate them into a language you actually speak…

Arch Linux

#1 2026-01-06 10:05:08

не работают кнопки F1, F2 и т.д.

#2 2026-01-06 10:55:16

Re: не работают кнопки F1, F2 и т.д.

#3 2026-01-06 23:00:37

Re: не работают кнопки F1, F2 и т.д.

#4 2026-01-07 08:02:44

Re: не работают кнопки F1, F2 и т.д.

#5 2026-01-07 08:08:32

Re: не работают кнопки F1, F2 и т.д.

#6 2026-01-07 08:17:00

Re: не работают кнопки F1, F2 и т.д.

#7 2026-01-07 09:00:18

Re: не работают кнопки F1, F2 и т.д.

#8 2026-01-07 15:13:13

Re: не работают кнопки F1, F2 и т.д.

#9 2026-01-07 16:08:22

Re: не работают кнопки F1, F2 и т.д.

#10 2026-01-07 18:47:26

Re: не работают кнопки F1, F2 и т.д.

#11 2026-01-07 20:08:02

Re: не работают кнопки F1, F2 и т.д.

Board footer