For me it also happens sometimes on boot, but can also happen during run.
I haven’t had it happen when my device was on battery and not plugged in to power, but my device is plugged in most of the time so I can’t infer much from this.
When it happens during run, the cursor just snaps to its stuck position on the lower right, and stay there until I force it to reboot (either via power button or via opening a terminal with the keyboard).
I managed to reproduce the issue on boot just now, by hot-rebooting 6 times (plugged in).
It it ever matters, my ports are DisplayPort (left back), USB-A (left middle), MicroSD (left front), USB-C (right back, charging port), USB-A (right middle), Ethernet (right front), and I am using the keyboard and the numpad.
I haven’t been able to consistently reproduce it. It seems random. Recently I’ve been doing some data transfers between external drives which crashes often (frustrating… but unrelated) and noticed it more. I’m not sure if it’s related to these crashes, or if I’m just noticing it because I rarely reboot my computer otherwise. I have a USB mouse but it happens whether or not it’s plugged in at boot.
My ports are:
left back USB-C
left mid HDMI
left front: USB-A
right back USB-C
right mid: audio
right front: USB-A
I’m on Framework 16 Ryzen 7040 series, Ubuntu 24.04, kernel linux 6.8.0-39-generic x86_64
Yeah - contrary to my initial probe, the dmesg is different during boot.
A working boot has the lines
input: PIXA3854:00 093A:0274 Mouse as /devices/platform/AMDI0010:03/i2c-1/i2c-PIXA3854:00/0018:093A:0274.0002/input/input3
input: PIXA3854:00 093A:0274 Touchpad as /devices/platform/AMDI0010:03/i2c-1/i2c-PIXA3854:00/0018:093A:0274.0002/input/input4
hid-generic 0018:093A:0274.0002: input,hidraw1: I2C HID v1.00 Mouse [PIXA3854:00 093A:0274] on i2c-PIXA3854:00
hid-sensor-hub 0018:32AC:001B.0001: hidraw0: I2C HID v1.00 Device [FRMW0003:00 32AC:001B] on i2c-FRMW0003:00
after:
Run /init as init process
with arguments:
/init
splash
with environment:
HOME=/
TERM=linux
BOOT_IMAGE=/boot/vmlinuz-6.10.2-061002-generic
hid: raw HID events driver (C) Jiri Kosina
ACPI: video: Video Device [VGA] (multi-head: yes rom: no post: no)
input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:1b/LNXVIDEO:00/input/input2
ACPI: bus type thunderbolt registered
And a non-working boot does not.
A non-working boot does not have 093A:0274 at all.
I do manage to reproduce the issue within 10 hot reboots while plugged in.
Looks like the issue got to Reddit as well.
Just dropped a CS ticket, feel free to drop one with working and non-working logs for CS to get more data points.
I’ve been contacting support for a similar issue Frequent keyboard/trackpad freeze as well. They sent me a new mid-plate and the problem is still happening.
I got Ubuntu 24.04 install on my framework 16 and steam is not opening but system monitor shows it running. I try to run it through the command it says “failed to load driver z ink”
also it is looping this
"BuildCompleteAppOverviewChange: 262 apps
RegisterForAppOverview 1: 4ms
RegisterForAppOverview 2: 4ms
"
please help
I originally had Win 10 then 11 on the SSD and Ubuntu 22.04 on an expansion card. That worked perfeclty untill I had problems with the expansion card.
Currently I have both on the SSD Windows 11 and Ubuntu 24.04
There are two issues I’ve noted with Ubuntu
a) If I don’t wait long enough before I sign in the Wi-Fi doesn’t get enabled, so I have to wait a few seconds not to have to restart.
b) If I use sleep the battery charging icon flashes like the battery is discharging and recharching every minute, just a bit of distraction.
while the alias was fine, i wrote a little script to run on startup. i set it up to run on startup via systemd. you could probably remove the echo commands. i just had them in there for testing purposes
#!/bin/bash
# log file to write in when this script fixes the trackpad
logfile="/home/username/trackpad.log"
# loop in case it doesn't work correctly on the first try
while true; do
hid_search=$(lsmod | grep hid_multitouch)
if [[ -n "$hid_search" ]]; then
echo "TRACKPAD WORKING"
break
else
echo "FIXING TRACKPAD"
rmmod i2c_hid_acpi && modprobe i2c_hid_acpi
if [[ ! -f "${logfile}" ]]; then
touch "${logfile}"
fi
date >> "${logfile}"
echo "TRACKPAD FIXED I GUESS"
sleep 3
fi
done
I’ve been running Ubuntu 24 since the day I got my FW16 in March. When it was pre-release there were some minor issues but since 24.04 was released I’ve not had any problems at all.
It seems like the Touchpad problem is specific to certain timing or ordering between pre-boot and boot environment due to kernel modules. Seems to be a regression rather than a long standing issue as per your experience
What I see here is that in unsuccessful start PIXA3854 does not load at all, however FRMW0003 loads as hidraw0 instead (in contrast to hidraw1 otherwise). Not sure if this can help or not. Would try to send these to support assuming that they would take my ticket at all (I have no idea what is the order id or whatever).
I take it that this log is happening here - linux/drivers/hid/hid-core.c at master · torvalds/linux · GitHub
What we can surmise is that apparently hid_connect was not called for PIXA3854 at all. Just guessing here as it all looks like black magic, but could it be that device saw hidraw0 taken and decided not to load?
Touchpad for me then does not work at all, clicking or moving.
(Ubuntu 24.04 , framework 16)
Commands with modprobe from the internet do not seem to help any. Tried to find ps/2 configuration to disable it that is sometimes recommended - but nothing like that exists in BIOS.
I believe that stability here should be changed to Not Stable or Risky - Framework | Fix Consumer Electronics . Desktop becomes somewhat unusable when touchpad does not work and it does not work a lot.
Hi. What have FW support said about this problem?
It sounds to me like a loose cable / connector somewhere or a faulty touchpad.
If it a faulty part, FW might replace it.
The touchpad wouldn’t respond no matter what I tried. Only rebooting again brought it back.