You are not logged in.
Pages: 1
Hello everyone,
I've decided to install Arch on my new laptop after I've been using it for 2 years on my desktop.
The laptop is the new T14 and I'm having issues trying to make the keyboard fully functional.
Here's a pic for reference.
The main issue is regarding the keyboard's layers, which can be accessed by the Fn key or toggled via the combination of Fn+Esc keys.
It seems like that without any configuration, the layers are both accessible (but no backlight/leds), but the function keys are not fully functional.
The brightness cannot be adjusted without further configurations as mentioned in the Wiki, so I've installed brightnessctl which seems to solve the issue with xbacklight.
I've tried to bind the key to the correspondent function via .xbindkeysrc in my home folder and in the i3 config file but neither of those solutions seem to work right now.
I'm not entirely sure if the problem is related to the different drivers needed for the internal AMD Gpu or to the keyboard configuration.
Thanks in advance for having read this, have a good day!
Offline
Hi, I may have the same issue.
What is your output of brightness up key with xev? Mine is
MappingNotify event, serial 34, synthetic NO, window 0x0,
request MappingKeyboard, first_keycode 8, count 248
FocusOut event, serial 34, synthetic NO, window 0x2c00001,
mode NotifyGrab, detail NotifyAncestor
FocusOut event, serial 34, synthetic NO, window 0x2c00001,
mode NotifyUngrab, detail NotifyPointer
FocusIn event, serial 34, synthetic NO, window 0x2c00001,
mode NotifyUngrab, detail NotifyAncestor
KeymapNotify event, serial 34, synthetic NO, window 0x0,
keys: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
MappingNotify event, serial 35, synthetic NO, window 0x0,
request MappingKeyboard, first_keycode 8, count 248
So not showing anything like
XF86KbdBrightnessUp
Also libinput debug-events shows
KEY_BRIGHTNESSDOWN (224) pressed
which is not the keycode expected by xmodmape -pke
Offline
From libinput man page
The libinput debug-events tool creates a libinput context and prints all events from these devices.
This is a debugging tool only, its output may change at any time. Do not rely on the output.
As far as I know, lenovo evaluates key combinations at BIOS level, so at OS level those keycodes are not mapped into anything. That's why xev can't register those keys.
I managed to make something work in my ~/.xbindkeysrc configuration:
# Increase volume
"pactl set-sink-volume @DEFAULT_SINK@ +1000"
XF86AudioRaiseVolume
# Decrease volume
"pactl set-sink-volume @DEFAULT_SINK@ -1000"
XF86AudioLowerVolume
# Mute volume
"pactl set-sink-mute @DEFAULT_SINK@ toggle"
XF86AudioMute
# Mute microphone
"pactl set-source-mute @DEFAULT_SOURCE@ toggle"
XF86AudioMicMute
# Increase backgliht
"brightnessctl -d 'amdgpu_bl0' set +10%"
XF86MonBrightnessUp
# Decrease backlight
"brightnessctl -d 'amdgpu_bl0' set 10%-"
XF86MonBrightnessDown
Right now the AudioMute button lights up when toggled, but the MicMute is not.
Also, the combination Fn+Esc (which toggles the FnLock) doesn't light up.
I have no clue how to map keys from F7 to F12.
Last edited by gab00 (2020-10-03 09:04:23)
Offline
If you don't need to change brightness (often), it probably can be set like I have done for my T440s.
Brightness can be set from command line, but if need to change brightness often, I understand that using brightness keys on keyboard is better way.
Since you have AMD, I guess the command is probably different than for Intel models.
Last edited by euromatlox (2020-10-03 13:34:29)
Offline
Pages: 1