MX Linux AHS - Keyboard Not Responding

As memory serves, it's a holdover from the previous thread where something wasn't working and noacpi was the solution. It's worth repeating (for the OP's sake) that it should only be used as a temporary measure.
Yes I realize that but I am thinking the two are intertwined
 


What is the output of
Code:
inxi -Fxz
lord.txt
apm@Linguist:~
$ cat lord.txt
System: Host: Linguist Kernel: 5.14.0-4mx-amd64 x86_64 bits: 64 compiler: N/A
Desktop: Xfce 4.16.0 Distro: MX-21_ahs_x64 Wildflower November 22 2021
base: Debian GNU/Linux 11 (bullseye)
Machine: Type: Laptop System: LENOVO product: 82QT v: IdeaPad Slim 7 Pro 14IHU5
serial: <filter>
Mobo: LENOVO model: LNVNB161216 v: SDK0T76463 WIN serial: <filter> UEFI: LENOVO
v: FJCN65WW date: 07/22/2021
Battery: ID-1: BAT1 charge: 24.1 Wh condition: 59.4/61.0 Wh (97%) model: Sunwoda L19D4PH3
status: Discharging
CPU: Topology: Quad Core model: 11th Gen Intel Core i7-11370H bits: 64 type: MT MCP
arch: N/A L2 cache: 12.0 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 52838
Speed: 673 MHz min/max: 400/4800 MHz Core speeds (MHz): 1: 539 2: 1101 3: 563 4: 788
5: 512 6: 1003 7: 522 8: 496
Graphics: Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] vendor: Lenovo driver: N/A
bus ID: 00:02.0
Display: x11 server: X.Org 1.20.13 driver: vesa unloaded: fbdev,modesetting
resolution: 2880x1800~91Hz
OpenGL: renderer: llvmpipe (LLVM 12.0.1 256 bits) v: 4.5 Mesa 21.2.5
direct render: Yes
Audio: Device-1: Intel Tiger Lake-LP Smart Sound Audio vendor: Lenovo
driver: sof-audio-pci-intel-tgl bus ID: 00:1f.3
Sound Server: ALSA v: k5.14.0-4mx-amd64
Network: Device-1: Intel Wi-Fi 6 AX201 driver: iwlwifi v: kernel port: 3000 bus ID: 00:14.3
IF: wlan0 state: up mac: <filter>
Drives: Local Storage: total: 953.87 GiB used: 7.69 GiB (0.8%)
ID-1: /dev/nvme0n1 vendor: Western Digital model: PC SN730 SDBPNTY-1T00-1101
size: 953.87 GiB
Partition: ID-1: / size: 929.70 GiB used: 7.69 GiB (0.8%) fs: ext4 dev: /dev/nvme0n1p2
ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/nvme0n1p3
Sensors: System Temperatures: cpu: 30.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info: Processes: 279 Uptime: 7m Memory: 15.42 GiB used: 1003.8 MiB (6.4%) Init: SysVinit
runlevel: 5 Compilers: gcc: 10.2.1 Shell: bash v: 5.1.4 inxi: 3.0.36
 
Yes I realize that but I am thinking the two are intertwined
As memory serves, it's a holdover from the previous thread where something wasn't working and noacpi was the solution. It's worth repeating (for the OP's sake) that it should only be used as a temporary measure.
Thanks for that reminder. Believe me, I don't want to stay in this neverneverland any longer than necessary. I removed "noacpi" and it didn't help the keyboard problem. At the same time, I didn't have any problem with the screen blanking. I guess "nomodeset" takes care of the latter. (?)
Since I am using MX Linux - AHS version, should I have some drivers from that repo in my /sources.list.d/mx.list? Thanks again for your comments. I hope Santa is watching!
A
 
I removed "noacpi" and it didn't help the keyboard problem. At the same time, I didn't have any problem with the screen blanking.

While not much, that seems like progress.
 
I think it's a kernel issue - Graphics: Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] vendor: Lenovo driver: N/A
indicates to me that there is no graphics driver in that Kernel

for the keyboard check to see if libinput is installed should be 3 files (xserver-xorg-input-libinput) - (libinput-bin) and (libinput10)
This package provides the driver for input devices using libinput library. It can handle keyboards, mice and touchpads, and essentially replaces the separate -evdev and -synaptics drivers.
 
I think it's a kernel issue - Graphics: Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] vendor: Lenovo driver: N/A
indicates to me that there is no graphics driver in that Kernel
Good catch. But are you saying that I failed to load a driver? Or that a Lenovo driver does not exist? Followup: Can I substitute a "generic" driver? How?

for the keyboard check to see if libinput is installed should be 3 files (xserver-xorg-input-libinput) - (libinput-bin) and (libinput10)
This package provides the driver for input devices using libinput library. It can handle keyboards, mice and touchpads, and essentially replaces the separate -evdev and -synaptics drivers.
I tried "libinput list-devices" and said it was not installed. Is there some other way to check ?Thanks
A
 
I tried to install libinput-tools and this output might mean something to you gurus....
sudo apt install libinput-tools
[sudo] password for apm:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
libinput-tools : Depends: libinput10 (= 1.16.4-3) but 1.19.1-1~mx21ahs+1 is to be installed
E: Unable to correct problems, you have held broken packages.
apm@Linguist:~
 
Good catch. But are you saying that I failed to load a driver? Or that a Lenovo driver does not exist? Followup: Can I substitute a "generic" driver? How?


I tried "libinput list-devices" and said it was not installed. Is there some other way to check ?Thanks
A
Lenovo driver is not present in that kernel - can't load what ain't there

For the Keyboard
Use the Synaptic Package Manager if installed - if it is not installed
Code:
sudo apt install synaptic
I do not think you need libinput-tools
Search in Synaptic for libinput and look for libinput-bin, xserver-xorg--input-libinput and libinput10 or 12 or whatever version it is showing
seems that package libinput-tools has not been upgraded yet for MX

You can also fix broken packages from Synaptic - click on Custom Filters then Broken - right click and mark for removal then apply
Synaptic Package Manager is your friend
 
Last edited by a moderator:
Still coming back with that extra material. :)

@Atheist just checking, but don't forget that whenever you make an adjustment to

/etc/default/grub

even though you save the file, you need to run

sudo update-grub

before you reboot, for the changes to take effect.

Wiz, back soon.
 
Still coming back with that extra material. :)

@Atheist just checking, but don't forget that whenever you make an adjustment to
/etc/default/grub
even though you save the file, you need to run
sudo update-grub
before you reboot, for the changes to take effect.
Wiz, back soon.
As I read that I did the teenager eye roll...like "no duh"...then I had this uneasy feeling so I checked the "history". It's like you read my mind! I had forgotten the update-grub. That explains why the screen was still flickering. <sigh>.... thanks
 
Any suggestions?

I'm a Lubuntu fan!

I'm also heavily biased. I'm actually on the Lubuntu (and Ubuntu!) team officially. Still, it's a great distro with LXQt. I'd suggest 20.04 and then mucking about with the kernel if you absolutely need to. Any underlying stuff like that for Ubuntu works just fine in Lubuntu.
 
I'm a Lubuntu fan!

I'm also heavily biased. I'm actually on the Lubuntu (and Ubuntu!) team officially. Still, it's a great distro with LXQt. I'd suggest 20.04 and then mucking about with the kernel if you absolutely need to. Any underlying stuff like that for Ubuntu works just fine in Lubuntu.
I do like the idea of that oem Intel graphics driver. I will install Lubuntu tonight. Any special choices that you suggest in the install?
 
@Atheist if you want to try something first before installing another

Code:
xinput disable 12

will disable your touchscreen, give it a couple of taps to test.

Then check if your keyboard becomes responsive.

Wiz
 
@Atheist if you want to try something first before installing another

Code:
xinput disable 12

will disable your touchscreen, give it a couple of taps to test.

Then check if your keyboard becomes responsive.

Wiz
Disable 12 certainly does disable the touchscreen. But the keyboard still doesn't work
 
Thanks, what about

Code:
xinput enable 19

Wiz
 
OK, that's interesting - thanks for that.

I think I am close to this, but I have nothing further to offer immediately, so please go ahead with any plans.

Cheers

Wzi
 

Members online


Top