keyboard and touchpad stuck [Solved]

[doguito]

Not secure boot option on the Bios, I am thinking that the disk NVMe can be the cause of the problems with touchpad and keyboard, o may be the type of filesystem, ext4 is not recommendable for NVMe disks? I discard hardware problems because Windows does not give any problem with keyboard and touchpad. The pc has only 7 months. Info about my system:

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-5mx-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-5mx-amd64
           root=UUID=<filter> ro quiet splash thermal.off=1 
           Desktop: Xfce 4.14.2 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-19.4_ahs_x64 patito feo March 31  2021 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Laptop System: HP product: HP 250 G7 Notebook PC v: Type1ProductConfigId 
           serial: <filter> Chassis: type: 10 serial: <filter> 
           Mobo: HP model: 86C1 v: 89.35 serial: <filter> UEFI: Insyde v: F.33 date: 07/31/2020 
Battery:   ID-1: BAT1 charge: 18.1 Wh condition: 38.6/41.0 Wh (94%) volts: 11.3/11.4 
           model: COMPAL PABAS0241231 type: Li-ion serial: <filter> status: Discharging 
CPU:       Topology: Dual Core model: Intel Core i3-1005G1 bits: 64 type: MT MCP arch: Ice Lake 
           family: 6 model-id: 7E (126) stepping: 5 microcode: A6 L2 cache: 4096 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 9523 
           Speed: 1617 MHz min/max: 400/3400 MHz Core speeds (MHz): 1: 1056 2: 1224 3: 823 
           4: 1042 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Enhanced IBRS, IBPB: conditional, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel Iris Plus Graphics G1 vendor: Hewlett-Packard driver: i915 v: kernel 
           bus ID: 00:02.0 chip ID: 8086:8a56 
           Display: x11 server: X.Org 1.20.10 driver: intel resolution: 1366x768~60Hz 
           OpenGL: renderer: Mesa DRI Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 20.3.4 
           compat-v: 3.0 direct render: Yes 
Audio:     Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Hewlett-Packard 
           driver: snd_hda_intel v: kernel bus ID: 00:1f.3 chip ID: 8086:34c8 
           Sound Server: ALSA v: k5.10.0-5mx-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
           vendor: Hewlett-Packard driver: r8169 v: kernel port: 4000 bus ID: 01:00.0 
           chip ID: 10ec:8168 
           IF: eth0 state: down mac: <filter> 
           Device-2: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter 
           vendor: Hewlett-Packard driver: rtl8821ce v: v5.5.2.1_35598.20191029 port: 3000 
           bus ID: 02:00.0 chip ID: 10ec:c821 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 238.47 GiB used: 6.42 GiB (2.7%) 
           ID-1: /dev/nvme0n1 model: KBG40ZNV256G KIOXIA size: 238.47 GiB block size: 
           physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 serial: <filter> 
           rev: HP00AE00 scheme: GPT 
RAID:      Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci v: 3.0 
           port: 5060 bus ID: 00:17.0 chip ID: 8086.282a rev: 30 
Partition: ID-1: / raw size: 78.12 GiB size: 76.40 GiB (97.79%) used: 6.39 GiB (8.4%) fs: ext4 
           dev: /dev/nvme0n1p4 
Sensors:   System Temperatures: cpu: 47.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian buster-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian buster main contrib non-free
           2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://ftp.cica.es/mirrors/Linux/MX-Packages/mx/repo/ buster main non-free
           2: deb http://ftp.cica.es/mirrors/Linux/MX-Packages/mx/repo/ buster ahs
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 206 Uptime: 24m Memory: 7.46 GiB used: 1.54 GiB (20.7%) Init: SysVinit 
           v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 

Mouse usb works, when gets frozen keyboard and touchpad, screen keeps working (time, battery...)

[Huckleberry Finn]

I was just going to add: "Change sata mode to Ahci (from Raid) , especially if you have SSDs" and saw your QSI.

Just, before going to Bios, open Regedit in Windows and make 2 simple changes there (not to make Windows unbootable), finally change to Ahci in Bios.

[az2020]

The pc has only 7 months. Info about my system:

Code: Select all

Machine:   Type: Laptop System: HP product: HP 250 G7 Notebook PC v: Type1ProductConfigId 
           serial: <filter> Chassis: type: 10 serial: <filter> 
           Mobo: HP model: 86C1 v: 89.35 serial: <filter> UEFI: Insyde v: F.33 date: 07/31/2020 

When I google your laptop's model number, HP says the current bios is F.36 rev A (released May 18 2021).

I wouldn't listen to me either.

[doguito]

Not option to change to ahci in Bios. I do not like to update Bios, I think I can brick PC. In forum linux, they told me to open "journalctl -f" to see if the event (when freezes keyboard and touchpad) throw some message that would clarifies a bit the problem. Right now running with systemd option, to see the log with "journalctl -f" command.

[az2020]

I do not like to update Bios, I think I can brick PC.

I agree, I don't chase bios updates trying to stay current for no reason. That would be unnecessary risk. / But, if I were having a problem like yours, I'd do it. You're two versions behind. The "fixes" info doesn't mention your problem. But, that info doesn't seem very informative either. One says "enhances security." That could be good to have(?).

Maybe you'll find the cause of the problem with what you're doing. But, if not, I'd reach for that bios update. That's the usual suggestion I've seen on forums: ensure your bios is current. I wouldn't look at this as chasing updates for no reason.

[doguito]

Is there some manual in this forum to update Bios?

[az2020]

Is there some manual in this forum to update Bios?

That's usually specific to the laptop. I was looking at this HP product page. Choose the OS and version. Then you'll be presented with the bios available. The details or the downloaded file will usually explain how.

I didn't look far, but I bet the update can only be done from within Windows. That's how my Acers are. I remove their boot media when I received them, and keep that for use like this. To me, it's easier to buy new media with a new laptop (save the original media. It's expensive, but easier when I'm in a jam.).

You could continue watching that journalctl log to see if you get info. Maybe the update won't fix the problem. You are right it's a risk (I'm backpeddling now because I don't want to be blamed if you brick your computer). But, typically updating is the first suggestion when having a problem like this. I've never bricked a computer updating the bios. I don't know how common it is. It's never happened to me. But, I don't update for the sake of staying current. If things work, I leave it alone. It is a risk. But, when things don't work, I don't hesitate to do it. I don't worry. (But, I try to be extra careful, and read everything twice.).

[Huckleberry Finn]

Not option to change to ahci in Bios.

Are you sure? What happens when you go to "sata mode" and try to change "Raid" ? No other options?

Is there some manual in this forum to update Bios?

Just as a general rule, do it when the power adapter is plugged: double click the downloaded .exe file in Windows. That's it. (Don't worry, Be happy).

[doguito]

Hi again, I am reading about to update the bios, this is the enhancement :

Description:

This package provides an update to the System BIOS. The update installs on supported computer models using a supported Windows Operating System. Restart the system to complete the installation.

Fix and enhancements:
- Provides support for additional notebook models

What I cannot understand is, what kind of support? Hardware, security,..? I am not native english, sorry.

In the other way, I have setup the touchpad with touchpad-indicator, and it seems that is working 100% well, so, I have this question, should I update the Bios?

[az2020]

Hi again, I am reading about to update the bios, this is the enhacement :

- Provides support for additional notebook models.

What I cannot understand is, what kind of support? Hardware, security,..? I am not native english, sorry.

Most bios "release notes" aren't great. But, I agree, those are the worst. It's like they're not even trying to communicae anything. It's possible the update contains more fixes than that web site's one-liner. Also, try downloading the two missed updates, and see if the zip? file has notes? Maybe there's a text file saying more than the website. You'll have the opportunity to cancel the update. You don't have to worry about running it to see what it looks like, or says. There will be a point where it flashes "yes/no". That would be worth looking further into. Maybe there are better release notes in that process?

In the other way, I have setup the touchpad with touchpad-indicator, and it seems that is working 100% well, so, I have this question, should I update the Bios?

If things are working, then I'd say leave the bios alone. I only look at bios updating if I'm having a problem. (I don't even care if the release notes say what it fixes. I just update.). OTOH: that uninformative "improved security" makes you think it might be good to have that. I would probably do it. But, logically, if things are working: leave it alone.

I've never had a problem flashing the bios. As huck said, be plugged into power. Also, don't be impatient. Sit on your hands (it might look hung at some point). I think you'd be fine doing it. But, it is a risk. If things are working for you now, the smart thing would be to leave the bios alone. If/when you have to do it, you'll probably get more in that shot.