[SOLVED] How to Report the Keyboard and Mouse Type

des_a · 08-27-2023, 11:02 PM

I am setting up an office computer. I really like my home keyboard and mouse. I want to look up the price for another one for the office, since I can't buy it in town again anymore. It is a matching wireless logitech pair. My city library has the same keyboard mice set. But beyond that, I don't know. How do I have my Linux Mint system report to me by commmand line, exactly the model of keyboard and mouse, so I can go look it up to buy on Amazon? I bet a lot of other people want to do this too. I'm trying:

Code:

inxi -Faz

...that I've used in the past, but no luck. I tried looking at the man page, but it's too hard to understand that for this program. I understand what the program does in general. The other thing I might know to do is have the library find the information for me by using their own computer's device manager.

des_a · 08-27-2023, 11:04 PM

For now, the keyboard and mouse I have is fine, depeding however on this problem's solution and the price. Mainly, I hope the price. But I would hope it's not too mmuch! I really want that keyboard and mouse!

mrmazda · 08-27-2023, 11:15 PM

All available information you're likely to get can be had from /usr/sbin/hwinfo --keyboard and /usr/sbin/hwinfo --mouse. Inxi output is generally limited to commonly useful information, but has many options for controlling verbosity.

camorri · 08-28-2023, 08:40 AM

All the Logitech keyboards and mice I have, have that info on stickers on the mouse bottom, or moulded into the plastic. Have a look there.

pan64 · 08-28-2023, 09:16 AM

probably you can try lsusb too

des_a · 08-28-2023, 01:53 PM

No sticker on the back. There's a serial number, which might be of use later.

des_a · 08-28-2023, 01:54 PM

The mouse, might be M215, as something says that underneath.

des_a · 08-28-2023, 01:56 PM

From lsusb, the reciever is Logitech Inc, Unifying reciever.

des_a · 08-28-2023, 02:01 PM

Code:

14: USB 00.0: 10800 Keyboard                                    
  [Created at usb.122]
  Unique ID: CDia.0PGCqK2HNaA
  Parent ID: KSTc.Bh50YlLnnW6
  SysFS ID: /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.3/1-2.3.1/1-2.3.1.1/1-2.3.1.1:1.0
  SysFS BusID: 1-2.3.1.1:1.0
  Hardware Class: keyboard
  Model: "Logitech Unifying Receiver"
  Hotplug: USB
  Vendor: usb 0x046d "Logitech, Inc."
  Device: usb 0xc52b "Unifying Receiver"
  Revision: "24.10"
  Driver: "usbhid"
  Driver Modules: "usbhid"
  Speed: 12 Mbps
  Module Alias: "usb:v046DpC52Bd2410dc00dsc00dp00ic03isc01ip01in00"
  Driver Info #0:
    XkbRules: xfree86
    XkbModel: pc104
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #13 (Hub)

20: USB 00.0: 10800 Keyboard
  [Created at usb.122]
  Unique ID: 7cgT.OtK1EwWiA37
  Parent ID: Gves.d7FDLX76qXB
  SysFS ID: /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.2/1-2.2.3/1-2.2.3:1.0
  SysFS BusID: 1-2.2.3:1.0
  Hardware Class: keyboard
  Model: "SayoDevice M"
  Hotplug: USB
  Vendor: usb 0x8089 "SayoDevice"
  Device: usb 0x0004 "M"
  Revision: "0.58"
  Serial ID: "0300DA2B71263B38"
  Driver: "usbhid"
  Driver Modules: "usbhid"
  Device File: /dev/input/event8
  Device Files: /dev/input/event8, /dev/input/by-id/usb-SayoDevice_M_0300DA2B71263B38-event-kbd, /dev/input/by-path/pci-0000:00:14.0-usb-0:2.2.3:1.0-event-kbd
  Device Number: char 13:72
  Speed: 12 Mbps
  Module Alias: "usb:v8089p0004d0058dc00dsc00dp00ic03isc01ip01in00"
  Driver Info #0:
    XkbRules: xfree86
    XkbModel: pc104
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #40 (Hub)

43: PS/2 00.0: 10800 Keyboard
  [Created at input.226]
  Unique ID: 9ui9.+49ps10DtUF
  Hardware Class: keyboard
  Model: "AT Translated Set 2 keyboard"
  Vendor: 0x0001 
  Device: 0x0001 "AT Translated Set 2 keyboard"
  Compatible to: int 0x0211 0x0001
  Device File: /dev/input/event3
  Device Files: /dev/input/event3, /dev/input/by-path/platform-i8042-serio-0-event-kbd
  Device Number: char 13:67
  Driver Info #0:
    XkbRules: xfree86
    XkbModel: pc104
  Config Status: cfg=new, avail=yes, need=no, active=unknown

The bottom, I think, is what I want, but it's not so helpful. Unless I'm decoding it wrong? What now? I know the reciever name now, and I will try, but I bet it won't find what I'm looking for.

des_a · 08-28-2023, 02:01 PM

I had to install hwinfo.

des_a · 08-28-2023, 02:03 PM

Code:

43: USB 00.0: 10503 USB Mouse                                   
  [Created at usb.122]
  Unique ID: X7GA.eMbi7i8sZu0
  Parent ID: k4bc.2DFUsyrieMD
  SysFS ID: /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0
  SysFS BusID: 1-7:1.0
  Hardware Class: mouse
  Model: "G2Touch Multi-Touch by G2TSP"
  Hotplug: USB
  Vendor: usb 0x2a94 "G2Touch"
  Device: usb 0x5009 "Multi-Touch by G2TSP"
  Revision: "2.02"
  Compatible to: int 0x0210 0x0000
  Driver: "usbhid"
  Driver Modules: "usbhid"
  Device File: /dev/input/mice (/dev/input/mouse2)
  Device Files: /dev/input/mice, /dev/input/mouse2, /dev/input/event7, /dev/input/by-id/usb-G2Touch_Multi-Touch_by_G2TSP-event-if00, /dev/input/by-path/pci-0000:00:14.0-usb-0:7:1.0-event
  Device Number: char 13:63 (char 13:34)
  Speed: 12 Mbps
  Module Alias: "usb:v2A94p5009d0202dc00dsc00dp00ic03isc01ip02in00"
  Driver Info #0:
    Buttons: 0
    Wheels: 0
    XFree86 Protocol: explorerps/2
    GPM Protocol: exps2
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #48 (Hub)

44: USB 00.1: 10503 USB Mouse
  [Created at usb.122]
  Unique ID: fOye.x2LcURBGx5F
  Parent ID: KSTc.Bh50YlLnnW6
  SysFS ID: /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.3/1-2.3.1/1-2.3.1.1/1-2.3.1.1:1.1
  SysFS BusID: 1-2.3.1.1:1.1
  Hardware Class: mouse
  Model: "Logitech Unifying Receiver"
  Hotplug: USB
  Vendor: usb 0x046d "Logitech, Inc."
  Device: usb 0xc52b "Unifying Receiver"
  Revision: "24.10"
  Compatible to: int 0x0200 0x0001 "Generic USB Mouse"
  Driver: "usbhid"
  Driver Modules: "usbhid"
  Speed: 12 Mbps
  Module Alias: "usb:v046DpC52Bd2410dc00dsc00dp00ic03isc01ip02in01"
  Driver Info #0:
    XFree86 Protocol: explorerps/2
    GPM Protocol: exps2
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #30 (Hub)

51: USB 00.1: 10503 USB Mouse
  [Created at usb.122]
  Unique ID: anwX.wQqJzCL5BRF
  Parent ID: Gves.d7FDLX76qXB
  SysFS ID: /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.2/1-2.2.3/1-2.2.3:1.1
  SysFS BusID: 1-2.2.3:1.1
  Hardware Class: mouse
  Model: "SayoDevice M"
  Hotplug: USB
  Vendor: usb 0x8089 "SayoDevice"
  Device: usb 0x0004 "M"
  Revision: "0.58"
  Serial ID: "0300DA2B71263B38"
  Compatible to: int 0x0210 0x0028
  Driver: "usbhid"
  Driver Modules: "usbhid"
  Device File: /dev/input/mice (/dev/input/mouse3)
  Device Files: /dev/input/mice, /dev/input/mouse3, /dev/input/event10, /dev/input/by-path/pci-0000:00:14.0-usb-0:2.2.3:1.1-event-mouse, /dev/input/by-id/usb-SayoDevice_M_0300DA2B71263B38-if01-event-mouse, /dev/input/by-id/usb-SayoDevice_M_0300DA2B71263B38-if01-mouse, /dev/input/by-path/pci-0000:00:14.0-usb-0:2.2.3:1.1-mouse
  Device Number: char 13:63 (char 13:35)
  Speed: 12 Mbps
  Module Alias: "usb:v8089p0004d0058dc00dsc00dp00ic03isc00ip00in01"
  Driver Info #0:
    Buttons: 8
    Wheels: 2
    XFree86 Protocol: explorerps/2
    GPM Protocol: exps2
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #57 (Hub)

61: PS/2 00.0: 10500 PS/2 Mouse
  [Created at input.249]
  Unique ID: AH6Q.XYKFbHS1I_7
  Hardware Class: mouse
  Model: "ELAN0709:00 04F3:30A0 Mouse"
  Vendor: 0x04f3 
  Device: 0x30a0 "ELAN0709:00 04F3:30A0 Mouse"
  Compatible to: int 0x0210 0x0002
  Device File: /dev/input/mice (/dev/input/mouse0)
  Device Files: /dev/input/mice, /dev/input/mouse0, /dev/input/event4
  Device Number: char 13:63 (char 13:32)
  Driver Info #0:
    Buttons: 2
    Wheels: 0
    XFree86 Protocol: explorerps/2
    GPM Protocol: exps2
  Config Status: cfg=new, avail=yes, need=no, active=unknown

62: PS/2 00.0: 10500 PS/2 Mouse
  [Created at input.249]
  Unique ID: AH6Q.XYKFbHS1I_7
  Hardware Class: mouse
  Model: "ELAN0709:00 04F3:30A0 Touchpad"
  Vendor: 0x04f3 
  Device: 0x30a0 "ELAN0709:00 04F3:30A0 Touchpad"
  Compatible to: int 0x0210 0x0002
  Device File: /dev/input/mice (/dev/input/mouse1)
  Device Files: /dev/input/mice, /dev/input/mouse1, /dev/input/event5, /dev/input/by-path/pci-0000:00:15.0-platform-i2c_designware.0-event-mouse, /dev/input/by-path/pci-0000:00:15.0-platform-i2c_designware.0-mouse
  Device Number: char 13:63 (char 13:33)
  Driver Info #0:
    Buttons: 2
    Wheels: 0
    XFree86 Protocol: explorerps/2
    GPM Protocol: exps2
  Config Status: cfg=new, avail=yes, need=no, active=unknown

I can't make any sense out of this.

des_a · 08-28-2023, 02:05 PM

When I google the reciever, I can see from a picture, I must have a Logitech MK320 keyboard.

des_a · 08-28-2023, 02:11 PM

Comes up on amazon too. Problem avoided, but not really fully solved, as I was trying to get it to report to me that. But it did get me what I was looking for. So closing, but if someone knows how to report, don't hesitate to post.

computersavvy · 12-02-2023, 02:10 PM

If the keyboard and mouse are battery powered (mine are) then running 'inxi -Bxx' should show the devices (as will inxi -Fzxx). For example

Code:

# inxi -Bxx
Battery:
  Device-1: hidpp_battery_0 model: Logitech MX Ergo Multi-Device Trackball
    serial: 06-e4-a3-3c charge: 55% (should be ignored) status: discharging
  Device-2: hidpp_battery_1 model: Logitech K350 serial: e6-28-b0-cb
    charge: 70% (should be ignored) status: discharging

shows mine as a Logitech K350 & Logitech MX Ergo which is exactly what they are.