Detect Keyboard [Solved]
Detect Keyboard
Is there a way in which my PC can detect the physical keyboard I am using - current config is not working too well
Re: Detect Keyboard
You need to post the output from the QSI utility. The Quick System Info (QSI) utility is located in MX Tools and its output is automatically formatted for use here in the forum. Run the QSI utility, click “Copy for Forum” at the bottom and then just paste it here in your thread.
Forum Rules
Forum Rules
HP 15; ryzen 3 5300U APU; 500 Gb SSD; 8GB ram
HP 17; ryzen 3 3200; 500 GB SSD; 12 GB ram
Idea Center 3; 12 gen i5; 256 GB ssd;
In Linux, newer isn't always better. The best solution is the one that works.
HP 17; ryzen 3 3200; 500 GB SSD; 12 GB ram
Idea Center 3; 12 gen i5; 256 GB ssd;
In Linux, newer isn't always better. The best solution is the one that works.
Re: Detect Keyboard
Thank you
I am not sure how this will help detect the keyboard but here it is
I am not sure how this will help detect the keyboard but here it is
Code: Select all
System:
Kernel: 6.1.0-23-amd64 [6.1.99-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-23-amd64 root=UUID=<filter> ro quiet splash
Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
dm: LightDM v: 1.26.0 Distro: MX-23.3_x64 Libretto May 19 2024 base: Debian GNU/Linux 12
(bookworm)
Machine:
Type: Desktop System: Dell product: OptiPlex 780 v: N/A serial: <superuser required> Chassis:
type: 3 serial: <superuser required>
Mobo: Dell model: 0200DY v: A01 serial: <superuser required> BIOS: Dell v: A14 date: 08/21/2012
CPU:
Info: model: Intel Core2 Quad Q6600 bits: 64 type: MCP arch: Core2 Merom level: v1 built: 2006-09
process: Intel 65nm family: 6 model-id: 0xF (15) stepping: 0xB (11) microcode: 0xBA
Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB
L2: 8 MiB desc: 2x4 MiB
Speed (MHz): avg: 2110 high: 2394 min/max: N/A cores: 1: 1596 2: 2394 3: 2115 4: 2338
bogomips: 19150
Flags: ht lm nx pae sse sse2 sse3 ssse3
Vulnerabilities:
Type: gather_data_sampling status: Not affected
Type: itlb_multihit status: KVM: VMX unsupported
Type: l1tf mitigation: PTE Inversion
Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled
Type: meltdown mitigation: PTI
Type: mmio_stale_data status: Unknown: No mitigations
Type: reg_file_data_sampling status: Not affected
Type: retbleed status: Not affected
Type: spec_rstack_overflow status: Not affected
Type: spec_store_bypass status: Vulnerable
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Retpolines; STIBP: disabled; RSB filling; PBRSB-eIBRS: Not
affected; BHI: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel 4 Series Integrated Graphics vendor: Dell 4 driver: i915 v: kernel arch: Gen-5
process: Intel 45nm built: 2008 ports: active: VGA-1 empty: none bus-ID: 00:02.0
chip-ID: 8086:2e12 class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: intel
dri: crocus gpu: i915 display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1280x1024 s-dpi: 96 s-size: 338x270mm (13.31x10.63") s-diag: 433mm (17.03")
Monitor-1: VGA-1 mapped: VGA1 model: EIZO NANAO S1921 serial: <filter> built: 2009
res: 1280x1024 hz: 60 dpi: 86 gamma: 1.2 size: 376x301mm (14.8x11.85") diag: 482mm (19")
ratio: 5:4 modes: max: 1280x1024 min: 720x400
API: OpenGL v: 2.1 Mesa 22.3.6 renderer: Mesa Intel Q45/Q43 (ELK) direct-render: Yes
Audio:
Device-1: Intel 82801JD/DO HD Audio vendor: Dell driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
chip-ID: 8086:3a6e class-ID: 0403
API: ALSA v: k6.1.0-23-amd64 status: kernel-api tools: alsamixer,amixer
Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel 82567LM-3 Gigabit Network vendor: Dell driver: e1000e v: kernel port: ece0
bus-ID: 00:19.0 chip-ID: 8086:10de class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Realtek RTL8188EUS 802.11n Wireless Network Adapter type: USB driver: r8188eu
bus-ID: 4-6:2 chip-ID: 0bda:8179 class-ID: 0000 serial: <filter>
IF: wlan0 state: down mac: <filter>
RAID:
Hardware-1: Intel SATA Controller [RAID mode] driver: ahci v: 3.0 port: fec0 bus-ID: 00:1f.2
chip-ID: 8086:2822 rev: N/A class-ID: 0104
Drives:
Local Storage: total: 465.76 GiB used: 31.36 GiB (6.7%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Seagate model: ST500DM002-1BD142 size: 465.76 GiB
block-size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 7200 serial: <filter>
rev: KC47 scheme: MBR
Partition:
ID-1: / raw-size: 465.76 GiB size: 457.38 GiB (98.20%) used: 31.36 GiB (6.9%) fs: ext4
dev: /dev/sda1 maj-min: 8:1
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: file size: 3 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
System Temperatures: cpu: 52.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos:
Packages: pm: dpkg pkgs: 2326 libs: 1227 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
pkgs: 0 pm: flatpak pkgs: 0
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
1: deb [signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg] https://brave-browser-apt-release.s3.brave.com/ stable main
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/google-chrome.list
1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mxlinux.mirrors.uk2.net/packages/mx/repo/ bookworm main non-free
Info:
Processes: 225 Uptime: 1h 44m wakeups: 1 Memory: 7.6 GiB used: 2.62 GiB (34.5%) Init: SysVinit
v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: BIOS (legacy, CSM, MBR)
Re: Detect Keyboard
The first thing you have to do is try another keyboard. Either the problem will persist or it won't. If it does persist, then we will have to dig deeper. If it doesn't persist, then the original is the problem and it probably should be replaced.
HP 15; ryzen 3 5300U APU; 500 Gb SSD; 8GB ram
HP 17; ryzen 3 3200; 500 GB SSD; 12 GB ram
Idea Center 3; 12 gen i5; 256 GB ssd;
In Linux, newer isn't always better. The best solution is the one that works.
HP 17; ryzen 3 3200; 500 GB SSD; 12 GB ram
Idea Center 3; 12 gen i5; 256 GB ssd;
In Linux, newer isn't always better. The best solution is the one that works.
Re: Detect Keyboard
So in answer to my question 'Is there a way in which my PC can detect the physical keyboard I am using' I presume the answer is no? ie the actual type layout of keyboard
Re: Detect Keyboard
What does lsusb (or inxi -J) report in a terminal?
This is my Fluxbox . There are many others like it, but this one is mine. My Fluxbox is my best friend. It is my life.
I must master it as I must master my life. Without me, my Fluxbox is useless. Without my Fluxbox, I am useless.
I must master it as I must master my life. Without me, my Fluxbox is useless. Without my Fluxbox, I am useless.
Re: Detect Keyboard
Check if it is detected and configure it accordingly:
Code: Select all
sudo dpkg-reconfigure keyboard-configuration
If your case is solved, and you want to help other users, click on the Solved-Button on the top right of a user's post.
Don't forget a system backup!
Don't forget a system backup!
- Eadwine Rose
- Administrator
- Posts: 14451
- Joined: Wed Jul 12, 2006 2:10 am
Re: Detect Keyboard
Not the question. User wants to see if the keyboard can be identified in MX, I wager something like setxkbmap? Mine gives the following on this line. Is that kind of what you mean with your question?
Code: Select all
$ setxkbmap -query | grep layout
layout: us
MX-23.6_x64 July 31 2023 * 6.1.0-34amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.216.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.216.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Re: Detect Keyboard
No, it's that a malfunctioning keyboard can be improperly detected. You are assuming that MX is the source of the problem, and while that is a real possibility, let's be sure and try to isolate the problem first.
HP 15; ryzen 3 5300U APU; 500 Gb SSD; 8GB ram
HP 17; ryzen 3 3200; 500 GB SSD; 12 GB ram
Idea Center 3; 12 gen i5; 256 GB ssd;
In Linux, newer isn't always better. The best solution is the one that works.
HP 17; ryzen 3 3200; 500 GB SSD; 12 GB ram
Idea Center 3; 12 gen i5; 256 GB ssd;
In Linux, newer isn't always better. The best solution is the one that works.
- rokytnji.1
- Global Moderator
- Posts: 827
- Joined: Sun Apr 13, 2014 9:06 pm
Re: Detect Keyboard
Got xev installed?
Code: Select all
xev
Code: Select all
$ ls -l /dev/input/by-path/*-kbd
lrwxrwxrwx 1 root root 9 Jul 21 12:03 /dev/input/by-path/platform-i8042-serio-0-event-kbd -> ../event0
Code: Select all
$ sudo dmesg | grep keyboard
[sudo] password for harry:
[ 1.637899] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0