Logitech K270 keyboard scroll lock issue

Questions about hardware, drivers and peripherals
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
toi_classified
Level 1
Level 1
Posts: 9
Joined: Fri May 14, 2021 5:53 am

Logitech K270 keyboard scroll lock issue

Post by toi_classified »

Dear Linux Mint experts - I am having a strange issue where the scroll lock key is not responsive on my Linux Mint 19 installation. I see that the scroll lock key is mapped (see xmodmap dump below). I want to use the scroll key to switch between different machines connected to a KVM switch.

Note that I have tested the keyboard without the KVM connected and the scroll lock key is still not responsive.
  • Also, I see the same issue with this particular keyboard on another Ubuntu 18.10 machine
Thanks for any pointers!
Edit: Just to add that the scroll lock functions works fine on Windows 10

Code: Select all

$ xmodmap -pm
xmodmap:  up to 4 keys per modifier, (keycodes in parentheses):

shift       Shift_L (0x32),  Shift_R (0x3e)
lock        Caps_Lock (0x42)
control     Control_L (0x25),  Control_R (0x69)
mod1        Alt_L (0x40),  Alt_R (0x6c),  Meta_L (0xcd)
mod2        Num_Lock (0x4d)
mod3        Scroll_Lock (0x4e)
mod4        Super_L (0x85),  Super_R (0x86),  Super_L (0xce),  Hyper_L (0xcf)
mod5        ISO_Level3_Shift (0x5c),  Mode_switch (0xcb)

Code: Select all

 System:    Host: HP-Mint Kernel: 4.15.0-137-generic x86_64 bits: 64 gcc: 7.5.0
           Desktop: Cinnamon 3.8.9 (Gtk 3.22.30-1ubuntu4) Distro: Linux Mint 19 Tara
Machine:   Device: laptop System: Hewlett-Packard product: HP EliteBook 2570p v: A1029D1102 serial: N/A
           Mobo: Hewlett-Packard model: 17DF v: KBC Version 61.23 serial: N/A
           BIOS: Hewlett-Packard v: 68ISB Ver. F.44 date: 10/08/2013
Battery    BAT0: charge: 45.6 Wh 100.0% condition: 45.6/45.6 Wh (100%)
           model: Hewlett-Packard Primary status: Full
CPU:       Dual core Intel Core i5-3320M (-MT-MCP-) arch: Ivy Bridge rev.9 cache: 3072 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 10375
           clock speeds: max: 3300 MHz 1: 1202 MHz 2: 1238 MHz 3: 1201 MHz 4: 1224 MHz
Graphics:  Card: Intel 3rd Gen Core processor Graphics Controller bus-ID: 00:02.0
           Display Server: x11 (X.Org 1.19.6 ) driver: modesetting Resolution: 1920x1080@59.96hz
           OpenGL: renderer: Mesa DRI Intel HD Graphics 4000 (IVB GT2)
           version: 4.2 Mesa 20.0.8 Direct Render: Yes
Audio:     Card-1 Intel 7 Series/C216 Family High Def. Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0
           Card-2 Plantronics driver: USB Audio usb-ID: 001-003
           Sound: Advanced Linux Sound Architecture v: k4.15.0-137-generic
Network:   Card-1: Intel 82579LM Gigabit Network Connection (Lewisville)
           driver: e1000e v: 3.2.6-k port: 4060 bus-ID: 00:19.0
           IF: enp0s25 state: up speed: 100 Mbps duplex: full mac: a0:48:1c:dc:2a:92
           Card-2: Intel Centrino Advanced-N 6205 [Taylor Peak] driver: iwlwifi bus-ID: 24:00.0
           IF: wlo1 state: down mac: a4:4e:31:42:f6:bc
Drives:    HDD Total Size: 256.1GB (22.5% used)
           ID-1: /dev/sda model: SAMSUNG_SSD_830 size: 256.1GB
Partition: ID-1: / size: 234G used: 54G (25%) fs: ext4 dev: /dev/sda1
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 51.0C mobo: 0.0C
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 259 Uptime: 1 day Memory: 2967.6/7840.0MB Init: systemd runlevel: 5 Gcc sys: 7.5.0
           Client: Shell (bash 4.4.201) inxi: 2.3.56 
Output of xev (looks like the scroll lock input is getting to the kernel):

Code: Select all

KeyPress event, serial 38, synthetic NO, window 0x8400001,
    root 0x168, subw 0x8400002, time 76417860, (47,44), root:(908,497),
    state 0x20, keycode 78 (keysym 0xff14, Scroll_Lock), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyRelease event, serial 38, synthetic NO, window 0x8400001,
    root 0x168, subw 0x8400002, time 76418020, (47,44), root:(908,497),
    state 0x20, keycode 78 (keysym 0xff14, Scroll_Lock), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyPress event, serial 38, synthetic NO, window 0x8400001,
    root 0x168, subw 0x8400002, time 76418190, (47,44), root:(908,497),
    state 0x20, keycode 78 (keysym 0xff14, Scroll_Lock), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyRelease event, serial 38, synthetic NO, window 0x8400001,
    root 0x168, subw 0x8400002, time 76418356, (47,44), root:(908,497),
    state 0x20, keycode 78 (keysym 0xff14, Scroll_Lock), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
User avatar
SMG
Level 25
Level 25
Posts: 31815
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Logitech K270 keyboard scroll lock issue

Post by SMG »

toi_classified wrote: Fri May 14, 2021 6:08 am Dear Linux Mint experts - I am having a strange issue where the scroll lock key is not responsive on my Linux Mint 19 installation. I see that the scroll lock key is mapped (see xmodmap dump below). I want to use the scroll key to switch between different machines connected to a KVM switch.
Is this a new issue on an existing system? Or is it a new KVM? Not all KVM's work well with Linux.

I do not know that it would make a difference, but I noticed you are not running the most up-to-date 4.15 kernel. The latest is 4.15.0-143.

System:
Host: HP-Mint Kernel: 4.15.0-137-generic x86_64 bits: 64 gcc: 7.5.0
Desktop: Cinnamon 3.8.9 (Gtk 3.22.30-1ubuntu4) Distro: Linux Mint 19 Tara
Image
A woman typing on a laptop with LM20.3 Cinnamon.
toi_classified
Level 1
Level 1
Posts: 9
Joined: Fri May 14, 2021 5:53 am

Re: Logitech K270 keyboard scroll lock issue

Post by toi_classified »

SMG wrote: Thu May 20, 2021 3:49 pm
toi_classified wrote: Fri May 14, 2021 6:08 am Dear Linux Mint experts - I am having a strange issue where the scroll lock key is not responsive on my Linux Mint 19 installation. I see that the scroll lock key is mapped (see xmodmap dump below). I want to use the scroll key to switch between different machines connected to a KVM switch.
Is this a new issue on an existing system? Or is it a new KVM? Not all KVM's work well with Linux.

I do not know that it would make a difference, but I noticed you are not running the most up-to-date 4.15 kernel. The latest is 4.15.0-143.

System:
Host: HP-Mint Kernel: 4.15.0-137-generic x86_64 bits: 64 gcc: 7.5.0
Desktop: Cinnamon 3.8.9 (Gtk 3.22.30-1ubuntu4) Distro: Linux Mint 19 Tara
It is a new issue on an existing system. KVM is old. The only difference is that I am using a new keyboard. Old logitech keyboard 'scroll lock' works fine. New logitech keyboard 'scroll lock' key seems to be the issue.
User avatar
SMG
Level 25
Level 25
Posts: 31815
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Logitech K270 keyboard scroll lock issue

Post by SMG »

toi_classified wrote: Sat May 22, 2021 1:27 pmOld logitech keyboard 'scroll lock' works fine. New logitech keyboard 'scroll lock' key seems to be the issue.
Is there any difference in the output of xev for each of them (old keyboard and new keyboard) which might give an indication of what is happening?
Image
A woman typing on a laptop with LM20.3 Cinnamon.
toi_classified
Level 1
Level 1
Posts: 9
Joined: Fri May 14, 2021 5:53 am

Re: Logitech K270 keyboard scroll lock issue

Post by toi_classified »

SMG wrote: Sat May 22, 2021 5:48 pm
toi_classified wrote: Sat May 22, 2021 1:27 pmOld logitech keyboard 'scroll lock' works fine. New logitech keyboard 'scroll lock' key seems to be the issue.
Is there any difference in the output of xev for each of them (old keyboard and new keyboard) which might give an indication of what is happening?
Please see output of env for 2x scroll lock press/releases. The only difference I see is the "serial" field remains unchanged in the non-working keyboard.

Logitech K270 NEW (NOT WORKING SCROLL LOCK)

Code: Select all

KeyPress event, serial 38, synthetic NO, window 0x8400001,
    root 0x168, subw 0x8400002, time 76417860, (47,44), root:(908,497),
    state 0x20, keycode 78 (keysym 0xff14, Scroll_Lock), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyRelease event, serial 38, synthetic NO, window 0x8400001,
    root 0x168, subw 0x8400002, time 76418020, (47,44), root:(908,497),
    state 0x20, keycode 78 (keysym 0xff14, Scroll_Lock), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyPress event, serial 38, synthetic NO, window 0x8400001,
    root 0x168, subw 0x8400002, time 76418190, (47,44), root:(908,497),
    state 0x20, keycode 78 (keysym 0xff14, Scroll_Lock), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyRelease event, serial 38, synthetic NO, window 0x8400001,
    root 0x168, subw 0x8400002, time 76418356, (47,44), root:(908,497),
    state 0x20, keycode 78 (keysym 0xff14, Scroll_Lock), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

Logitech OLD (WORKING SCROLL LOCK)

Code: Select all

KeyPress event, serial 39, synthetic NO, window 0x8400001,
    root 0x168, subw 0x0, time 76339879, (104,85), root:(965,538),
    state 0x20, keycode 78 (keysym 0xff14, Scroll_Lock), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyRelease event, serial 40, synthetic NO, window 0x8400001,
    root 0x168, subw 0x0, time 76339999, (104,85), root:(965,538),
    state 0x20, keycode 78 (keysym 0xff14, Scroll_Lock), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyPress event, serial 40, synthetic NO, window 0x8400001,
    root 0x168, subw 0x0, time 76340135, (104,85), root:(965,538),
    state 0x20, keycode 78 (keysym 0xff14, Scroll_Lock), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyRelease event, serial 40, synthetic NO, window 0x8400001,
    root 0x168, subw 0x0, time 76340239, (104,85), root:(965,538),
    state 0x20, keycode 78 (keysym 0xff14, Scroll_Lock), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False
User avatar
SMG
Level 25
Level 25
Posts: 31815
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Logitech K270 keyboard scroll lock issue

Post by SMG »

From what I could find, serial 38 is bluetooth. I do not know why there would be a difference between the two serial numbers for the working keyboard unless there is something in the design of that keyboard that makes a difference?

I do not really know enough about the topic to be of more help. The only other ideas I have are to check for any errors in /var/log/Xorg.0.log. Or check that file to see if there is something about how the two keyboards are recognized in that file that might give a clue as to what is happening.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
toi_classified
Level 1
Level 1
Posts: 9
Joined: Fri May 14, 2021 5:53 am

Re: Logitech K270 keyboard scroll lock issue

Post by toi_classified »

Thanks a lot for your replies. I plugged and unplugged the keyboards from the KVM switch. These are the events captured in /var/log/Xorg.0.log.
NEW LOGITECH KEYBOARD (NOT WORKING SCROLL LOCK)

Code: Select all


[467918.208] (**) Logitech K270: always reports core events
[467918.208] (**) Option "Device" "/dev/input/event20"
[467918.208] (**) Option "_source" "_driver/libinput"
[467918.208] (II) libinput: Logitech K270: is a virtual subdevice
[467918.208] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3.4/3-3.4:1.2/0003:046D:C52B.01F3/0003:046D:4003.01F4/input/input556/event20"
[467918.208] (II) XINPUT: Adding extended input device "Logitech K270" (type: KEYBOARD, id 20)
[467918.208] (**) Option "xkb_model" "pc105"
[467918.208] (**) Option "xkb_layout" "us"
[467918.208] (WW) Option "xkb_variant" requires a string value
[467918.208] (WW) Option "xkb_options" requires a string value

OLD (WORKING SCROLL LOCK) LOGITECH KEYBOARD

Code: Select all

[468208.372] (**) Logitech USB Receiver: always reports core events
[468208.372] (**) Option "Device" "/dev/input/event18"
[468208.372] (**) Option "_source" "_driver/libinput"
[468208.372] (II) libinput: Logitech USB Receiver: is a virtual subdevice
[468208.372] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3.1/3-3.1:1.1/0003:046D:C505.01F6/input/input558/event18"
[468208.372] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD, id 17)
[468208.372] (**) Option "xkb_model" "pc105"
[468208.372] (**) Option "xkb_layout" "us"
[468208.372] (WW) Option "xkb_variant" requires a string value
[468208.372] (WW) Option "xkb_options" requires a string value

When I hit scroll lock, these are the logs in the working keyboard. No logs are registered in the non-working keyboard.

Code: Select all

[467830.084] (**) Logitech USB Receiver: (accel) selected scheme none/0
[467830.084] (**) Logitech USB Receiver: (accel) acceleration factor: 2.000
[467830.084] (**) Logitech USB Receiver: (accel) acceleration threshold: 4
[467830.085] (II) event18 - Logitech USB Receiver: is tagged by udev as: Keyboard Mouse Joystick
[467830.086] (II) event18 - Logitech USB Receiver: device is a pointer
[467830.086] (II) event18 - Logitech USB Receiver: device is a keyboard
[467830.087] (**) Logitech USB Receiver: Applying InputClass "libinput pointer catchall"
[467830.087] (**) Logitech USB Receiver: Applying InputClass "libinput keyboard catchall"
[467830.087] (II) Using input driver 'libinput' for 'Logitech USB Receiver'
[467830.087] (**) Logitech USB Receiver: always reports core events
[467830.088] (**) Option "Device" "/dev/input/event18"
[467830.088] (**) Option "_source" "_driver/libinput"
[467830.088] (II) libinput: Logitech USB Receiver: is a virtual subdevice
[467830.088] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3.1/3-3.1:1.1/0003:046D:C505.01EF/input/input554/event18"
[467830.088] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD, id 17)
[467830.088] (**) Option "xkb_model" "pc105"
[467830.088] (**) Option "xkb_layout" "us"
[467830.088] (WW) Option "xkb_variant" requires a string value
[467830.088] (WW) Option "xkb_options" requires a string value


User avatar
SMG
Level 25
Level 25
Posts: 31815
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Logitech K270 keyboard scroll lock issue

Post by SMG »

It appears the "not working" keyboard has info for both the receiver and the keyboard
0003:046D:C52B.01F3/0003:046D:4003.01F4
while the working one has info for just the keyboard.
0003:046D:C505.01F6

Maybe somehow the hand-off between the devices (receiver and keyboard) is the issue? I do not know.

Have you checked for information on the Logitech website's support section?
Image
A woman typing on a laptop with LM20.3 Cinnamon.
toi_classified
Level 1
Level 1
Posts: 9
Joined: Fri May 14, 2021 5:53 am

Re: Logitech K270 keyboard scroll lock issue

Post by toi_classified »

I have checked the Logitech support forums but couldn't find anything similar. I just purchased a new Logitech MX keys keyboard and I am seeing the exact same issues as with the K270 keyboard. So it does look like some issue with the 'Logitech Unifying receiver' that plugs into the KVM switch. I am wondering if there is a way to send a scroll lock signal to the KVM switch without using the physical keyboard. All I need the scroll lock button for is to switch the KVM.
User avatar
SMG
Level 25
Level 25
Posts: 31815
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Logitech K270 keyboard scroll lock issue

Post by SMG »

toi_classified wrote: Thu May 27, 2021 9:58 am I am wondering if there is a way to send a scroll lock signal to the KVM switch without using the physical keyboard.
I do not know if that is possible. Maybe someone else will know.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
toi_classified
Level 1
Level 1
Posts: 9
Joined: Fri May 14, 2021 5:53 am

Re: Logitech K270 keyboard scroll lock issue

Post by toi_classified »

I am running a small script now to monitor the exact events. I am not sure if this is a problem, but the "not-working" keyboard is being identified as a mouse. Not really sure what is going on here.

With the NOT-WORKING SCROLL LOCK KEYBOARD:

/dev/input/by-id/usb-Logitech_USB_Receiver-if02-event-mouse: event at 1622180636.181765, code 04, type 04, val 458823
/dev/input/by-id/usb-Logitech_USB_Receiver-if02-event-mouse: key event at 1622180636.181765, 70 (KEY_SCROLLLOCK), down
/dev/input/by-id/usb-Logitech_USB_Receiver-if02-event-mouse: synchronization event at 1622180636.181765, SYN_REPORT

WORKING SCROLL LOCK KEYBOARD
/dev/input/event9: synchronization event at 1622180736.580291, SYN_REPORT
/dev/input/by-id/usb-Logitech_USB_Receiver-event-kbd: event at 1622180736.633204, code 04, type 04, val 458823
/dev/input/by-id/usb-Logitech_USB_Receiver-event-kbd: key event at 1622180736.633204, 70 (KEY_SCROLLLOCK), down
/dev/input/by-id/usb-Logitech_USB_Receiver-event-kbd: synchronization event at 1622180736.633204, SYN_REPORT
User avatar
SMG
Level 25
Level 25
Posts: 31815
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Logitech K270 keyboard scroll lock issue

Post by SMG »

toi_classified wrote: Fri May 28, 2021 2:04 am I am running a small script now to monitor the exact events. I am not sure if this is a problem, but the "not-working" keyboard is being identified as a mouse.
Are you using a mouse with the Logitech Unifying Receiver?

Maybe something in this thread My keyboard identifies as a mouse will be helpful as part of the troubleshooting process.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
toi_classified
Level 1
Level 1
Posts: 9
Joined: Fri May 14, 2021 5:53 am

Re: Logitech K270 keyboard scroll lock issue

Post by toi_classified »

Thanks for the helpful hints. I tried to understand the issue with the link you provided. It looks like the other OP was looking to map some extra keys (scancode > 255). In my case when I ran the evetest script (linked in your post), I can see the scroll lock key registering in the kernel. So the mystery is why the KVM is not seeing this key stroke.

Code: Select all

Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x46d product 0x408a version 0x111
Input device name: "Logitech MX Keys"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 1 (KEY_ESC)
    Event code 2 (KEY_1)
    Event code 3 (KEY_2)
    Event code 4 (KEY_3)
    Event code 5 (KEY_4)
    Event code 6 (KEY_5)
    Event code 7 (KEY_6)
    Event code 8 (KEY_7)
    Event code 9 (KEY_8)
    Event code 10 (KEY_9)
    Event code 11 (KEY_0)
    Event code 12 (KEY_MINUS)
    Event code 13 (KEY_EQUAL)
    Event code 14 (KEY_BACKSPACE)
    Event code 15 (KEY_TAB)
    Event code 16 (KEY_Q)
    Event code 17 (KEY_W)
    Event code 18 (KEY_E)
    Event code 19 (KEY_R)
    Event code 20 (KEY_T)
    Event code 21 (KEY_Y)
    Event code 22 (KEY_U)
    Event code 23 (KEY_I)
    Event code 24 (KEY_O)
    Event code 25 (KEY_P)
    Event code 26 (KEY_LEFTBRACE)
    Event code 27 (KEY_RIGHTBRACE)
    Event code 28 (KEY_ENTER)
    Event code 29 (KEY_LEFTCTRL)
    Event code 30 (KEY_A)
    Event code 31 (KEY_S)
    Event code 32 (KEY_D)
    Event code 33 (KEY_F)
    Event code 34 (KEY_G)
    Event code 35 (KEY_H)
    Event code 36 (KEY_J)
    Event code 37 (KEY_K)
    Event code 38 (KEY_L)
    Event code 39 (KEY_SEMICOLON)
    Event code 40 (KEY_APOSTROPHE)
    Event code 41 (KEY_GRAVE)
    Event code 42 (KEY_LEFTSHIFT)
    Event code 43 (KEY_BACKSLASH)
    Event code 44 (KEY_Z)
    Event code 45 (KEY_X)
    Event code 46 (KEY_C)
    Event code 47 (KEY_V)
    Event code 48 (KEY_B)
    Event code 49 (KEY_N)
    Event code 50 (KEY_M)
    Event code 51 (KEY_COMMA)
    Event code 52 (KEY_DOT)
    Event code 53 (KEY_SLASH)
    Event code 54 (KEY_RIGHTSHIFT)
    Event code 55 (KEY_KPASTERISK)
    Event code 56 (KEY_LEFTALT)
    Event code 57 (KEY_SPACE)
    Event code 58 (KEY_CAPSLOCK)
    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 69 (KEY_NUMLOCK)
    Event code 70 (KEY_SCROLLLOCK)
    Event code 71 (KEY_KP7)
    Event code 72 (KEY_KP8)
    Event code 73 (KEY_KP9)
    Event code 74 (KEY_KPMINUS)
    Event code 75 (KEY_KP4)
    Event code 76 (KEY_KP5)
    Event code 77 (KEY_KP6)
    Event code 78 (KEY_KPPLUS)
    Event code 79 (KEY_KP1)
    Event code 80 (KEY_KP2)
    Event code 81 (KEY_KP3)
    Event code 82 (KEY_KP0)
    Event code 83 (KEY_KPDOT)
    Event code 85 (KEY_ZENKAKUHANKAKU)
    Event code 86 (KEY_102ND)
    Event code 87 (KEY_F11)
    Event code 88 (KEY_F12)
    Event code 89 (KEY_RO)
    Event code 90 (KEY_KATAKANA)
    Event code 91 (KEY_HIRAGANA)
    Event code 92 (KEY_HENKAN)
    Event code 93 (KEY_KATAKANAHIRAGANA)
    Event code 94 (KEY_MUHENKAN)
    Event code 95 (KEY_KPJPCOMMA)
    Event code 96 (KEY_KPENTER)
    Event code 97 (KEY_RIGHTCTRL)
    Event code 98 (KEY_KPSLASH)
    Event code 99 (KEY_SYSRQ)
    Event code 100 (KEY_RIGHTALT)
    Event code 102 (KEY_HOME)
    Event code 103 (KEY_UP)
    Event code 104 (KEY_PAGEUP)
    Event code 105 (KEY_LEFT)
    Event code 106 (KEY_RIGHT)
    Event code 107 (KEY_END)
    Event code 108 (KEY_DOWN)
    Event code 109 (KEY_PAGEDOWN)
    Event code 110 (KEY_INSERT)
    Event code 111 (KEY_DELETE)
    Event code 113 (KEY_MUTE)
    Event code 114 (KEY_VOLUMEDOWN)
    Event code 115 (KEY_VOLUMEUP)
    Event code 116 (KEY_POWER)
    Event code 117 (KEY_KPEQUAL)
    Event code 119 (KEY_PAUSE)
    Event code 121 (KEY_KPCOMMA)
    Event code 122 (KEY_HANGUEL)
    Event code 123 (KEY_HANJA)
    Event code 124 (KEY_YEN)
    Event code 125 (KEY_LEFTMETA)
    Event code 126 (KEY_RIGHTMETA)
    Event code 127 (KEY_COMPOSE)
    Event code 128 (KEY_STOP)
    Event code 129 (KEY_AGAIN)
    Event code 130 (KEY_PROPS)
    Event code 131 (KEY_UNDO)
    Event code 132 (KEY_FRONT)
    Event code 133 (KEY_COPY)
    Event code 134 (KEY_OPEN)
    Event code 135 (KEY_PASTE)
    Event code 136 (KEY_FIND)
    Event code 137 (KEY_CUT)
    Event code 138 (KEY_HELP)
    Event code 139 (KEY_MENU)
    Event code 140 (KEY_CALC)
    Event code 142 (KEY_SLEEP)
    Event code 143 (KEY_WAKEUP)
    Event code 144 (KEY_FILE)
    Event code 150 (KEY_WWW)
    Event code 152 (KEY_SCREENLOCK)
    Event code 155 (KEY_MAIL)
    Event code 156 (KEY_BOOKMARKS)
    Event code 158 (KEY_BACK)
    Event code 159 (KEY_FORWARD)
    Event code 161 (KEY_EJECTCD)
    Event code 163 (KEY_NEXTSONG)
    Event code 164 (KEY_PLAYPAUSE)
    Event code 165 (KEY_PREVIOUSSONG)
    Event code 166 (KEY_STOPCD)
    Event code 167 (KEY_RECORD)
    Event code 168 (KEY_REWIND)
    Event code 169 (KEY_PHONE)
    Event code 171 (KEY_CONFIG)
    Event code 172 (KEY_HOMEPAGE)
    Event code 173 (KEY_REFRESH)
    Event code 174 (KEY_EXIT)
    Event code 176 (KEY_EDIT)
    Event code 177 (KEY_SCROLLUP)
    Event code 178 (KEY_SCROLLDOWN)
    Event code 179 (KEY_KPLEFTPAREN)
    Event code 180 (KEY_KPRIGHTPAREN)
    Event code 181 (KEY_NEW)
    Event code 182 (KEY_REDO)
    Event code 183 (KEY_F13)
    Event code 184 (KEY_F14)
    Event code 185 (KEY_F15)
    Event code 186 (KEY_F16)
    Event code 187 (KEY_F17)
    Event code 188 (KEY_F18)
    Event code 189 (KEY_F19)
    Event code 190 (KEY_F20)
    Event code 191 (KEY_F21)
    Event code 192 (KEY_F22)
    Event code 193 (KEY_F23)
    Event code 194 (KEY_F24)
    Event code 206 (KEY_CLOSE)
    Event code 207 (KEY_PLAY)
    Event code 208 (KEY_FASTFORWARD)
    Event code 209 (KEY_BASSBOOST)
    Event code 210 (KEY_PRINT)
    Event code 212 (KEY_CAMERA)
    Event code 216 (KEY_CHAT)
    Event code 217 (KEY_SEARCH)
    Event code 219 (KEY_FINANCE)
    Event code 223 (KEY_CANCEL)
    Event code 224 (KEY_BRIGHTNESSDOWN)
    Event code 225 (KEY_BRIGHTNESSUP)
    Event code 228 (KEY_KBDILLUMTOGGLE)
    Event code 229 (KEY_KBDILLUMDOWN)
    Event code 230 (KEY_KBDILLUMUP)
    Event code 231 (KEY_SEND)
    Event code 232 (KEY_REPLY)
    Event code 233 (KEY_FORWARDMAIL)
    Event code 234 (KEY_SAVE)
    Event code 235 (KEY_DOCUMENTS)
    Event code 240 (KEY_UNKNOWN)
    Event code 241 (KEY_VIDEO_NEXT)
    Event code 244 (KEY_BRIGHTNESS_ZERO)
    Event code 256 (BTN_0)
    Event code 272 (BTN_LEFT)
    Event code 273 (BTN_RIGHT)
    Event code 274 (BTN_MIDDLE)
    Event code 275 (BTN_SIDE)
    Event code 276 (BTN_EXTRA)
    Event code 277 (BTN_FORWARD)
    Event code 278 (BTN_BACK)
    Event code 279 (BTN_TASK)
    Event code 280 (?)
    Event code 281 (?)
    Event code 282 (?)
    Event code 283 (?)
    Event code 284 (?)
    Event code 285 (?)
    Event code 286 (?)
    Event code 287 (?)
    Event code 353 (KEY_SELECT)
    Event code 354 (KEY_GOTO)
    Event code 358 (KEY_INFO)
    Event code 362 (KEY_PROGRAM)
    Event code 366 (KEY_PVR)
    Event code 370 (KEY_SUBTITLE)
    Event code 372 (KEY_ZOOM)
    Event code 374 (KEY_KEYBOARD)
    Event code 376 (KEY_PC)
    Event code 377 (KEY_TV)
    Event code 378 (KEY_TV2)
    Event code 379 (KEY_VCR)
    Event code 380 (KEY_VCR2)
    Event code 381 (KEY_SAT)
    Event code 383 (KEY_CD)
    Event code 384 (KEY_TAPE)
    Event code 386 (KEY_TUNER)
    Event code 387 (KEY_PLAYER)
    Event code 389 (KEY_DVD)
    Event code 392 (KEY_AUDIO)
    Event code 393 (KEY_VIDEO)
    Event code 396 (KEY_MEMO)
    Event code 397 (KEY_CALENDAR)
    Event code 398 (KEY_RED)
    Event code 399 (KEY_GREEN)
    Event code 400 (KEY_YELLOW)
    Event code 401 (KEY_BLUE)
    Event code 402 (KEY_CHANNELUP)
    Event code 403 (KEY_CHANNELDOWN)
    Event code 405 (KEY_LAST)
    Event code 407 (KEY_NEXT)
    Event code 408 (KEY_RESTART)
    Event code 409 (KEY_SLOW)
    Event code 410 (KEY_SHUFFLE)
    Event code 412 (KEY_PREVIOUS)
    Event code 416 (KEY_VIDEOPHONE)
    Event code 417 (KEY_GAMES)
    Event code 418 (KEY_ZOOMIN)
    Event code 419 (KEY_ZOOMOUT)
    Event code 420 (KEY_ZOOMRESET)
    Event code 421 (KEY_WORDPROCESSOR)
    Event code 422 (KEY_EDITOR)
    Event code 423 (KEY_SPREADSHEET)
    Event code 424 (KEY_GRAPHICSEDITOR)
    Event code 425 (KEY_PRESENTATION)
    Event code 426 (KEY_DATABASE)
    Event code 427 (KEY_NEWS)
    Event code 428 (KEY_VOICEMAIL)
    Event code 429 (KEY_ADDRESSBOOK)
    Event code 430 (KEY_MESSENGER)
    Event code 431 (KEY_DISPLAYTOGGLE)
    Event code 432 (KEY_SPELLCHECK)
    Event code 433 (KEY_LOGOFF)
    Event code 439 (KEY_MEDIA_REPEAT)
    Event code 442 (KEY_IMAGES)
    Event code 576 (KEY_BUTTONCONFIG)
    Event code 577 (KEY_TASKMANAGER)
    Event code 578 (KEY_JOURNAL)
    Event code 579 (KEY_CONTROLPANEL)
    Event code 580 (KEY_APPSELECT)
    Event code 581 (KEY_SCREENSAVER)
    Event code 582 (KEY_VOICECOMMAND)
    Event code 583 (?)
    Event code 592 (KEY_BRIGHTNESS_MIN)
    Event code 593 (KEY_BRIGHTNESS_MAX)
  Event type 2 (EV_REL)
    Event code 0 (REL_X)
    Event code 1 (REL_Y)
    Event code 6 (REL_HWHEEL)
    Event code 7 (REL_DIAL)
    Event code 8 (REL_WHEEL)
  Event type 3 (EV_ABS)
    Event code 32 (ABS_VOLUME)
      Value      0
      Min        1
      Max      652
  Event type 4 (EV_MSC)
    Event code 4 (MSC_SCAN)
  Event type 17 (EV_LED)
    Event code 0 (LED_NUML) state 0
    Event code 1 (LED_CAPSL) state 0
    Event code 2 (LED_SCROLLL) state 0
    Event code 3 (LED_COMPOSE) state 0
    Event code 4 (LED_KANA) state 0
Key repeat handling:
  Repeat type 20 (EV_REP)
    Repeat code 0 (REP_DELAY)
      Value    250
    Repeat code 1 (REP_PERIOD)
      Value     33
Properties:
Testing ... (interrupt to exit)
Event: time 1622181243.279949, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70028
Event: time 1622181243.279949, type 1 (EV_KEY), code 28 (KEY_ENTER), value 0
Event: time 1622181243.279949, -------------- SYN_REPORT ------------
Event: time 1622181248.072387, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70047
Event: time 1622181248.072387, type 1 (EV_KEY), code 70 (KEY_SCROLLLOCK), value 1
Event: time 1622181248.072387, -------------- SYN_REPORT ------------
Event: time 1622181248.194400, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70047
Event: time 1622181248.194400, type 1 (EV_KEY), code 70 (KEY_SCROLLLOCK), value 0
Event: time 1622181248.194400, -------------- SYN_REPORT ------------
Event: time 1622181248.314410, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70047
Event: time 1622181248.314410, type 1 (EV_KEY), code 70 (KEY_SCROLLLOCK), value 1
Event: time 1622181248.314410, -------------- SYN_REPORT ------------
Event: time 1622181248.456422, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70047
Event: time 1622181248.456422, type 1 (EV_KEY), code 70 (KEY_SCROLLLOCK), value 0

User avatar
SMG
Level 25
Level 25
Posts: 31815
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Logitech K270 keyboard scroll lock issue

Post by SMG »

toi_classified wrote: Sat May 29, 2021 9:02 am In my case when I ran the evetest script (linked in your post), I can see the scroll lock key registering in the kernel. So the mystery is why the KVM is not seeing this key stroke.
You might have to research that answer through the KVM manufacturer.

In this thread KVM issues with newer keyboard and mice a person had issues using an older KVM with a newer keyboard. Maybe what you are experiencing is a similar issue? I do not know enough about the differences between KVMs to know how to investigate.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
toi_classified
Level 1
Level 1
Posts: 9
Joined: Fri May 14, 2021 5:53 am

Re: Logitech K270 keyboard scroll lock issue

Post by toi_classified »

Thank you again! I will do a bit more searching around. The frustrating bit about this problem is that all my windows machines connected to the KVM switch play nice with this new keyboard (scroll lock key works, hot keys work on kvm switch). However, all the Linux distros (Linux mint and and another ubuntu distro) I have connected to the KVM don't play nice with the scroll lock key (all other keys seem to work normally with Linux distros). So I almost have things working except for this scroll lock key.

Everything seem to point to the new logitech "unifying" wireless receiver because I tried the KVM switch with a new microsoft sculpt keyboard and I was fully back in business (KVM switch worked fine across Windows/Linux).
Locked

Return to “Hardware Support”