Yes — that sounds good. Run the 1‑hour Slax capture and upload the created tarball; I’ll parse it as soon as you attach it and tell you the single next action. A few short notes and the exact commands to copy/paste while you’re in Slax.
Short reminders before you start
- Do NOT reboot the PC if a drop happens — reboot clears the logs we need.
- Keep the K800 paired if you need to type in the forum — you don’t have to unpair it. We can still diagnose with the keyboard present.
- Use the same physical USB port you normally use on the problem PC (or a rear motherboard USB2 port) so we replicate the same host environment.
Exact one‑hour capture (copy/paste in Slax terminal)
1) Save USB / input snapshots now (run as root; Slax may not have sudo):
lsusb > /tmp/lsusb_before.txt
lsusb -t > /tmp/lsusb_tree_before.txt
cat /proc/bus/input/devices > /tmp/inputdev_before.txt
2) Start kernel/USB capture for 1 hour (preferred; uses timeout if present):
timeout 3600 dmesg -wH > /tmp/dmesg_live.log & echo $! > /tmp/dmesg_pid.txt
3) Start raw input capture for 1 hour (try hexdump, fallback to cat)
command -v hexdump >/dev/null 2>&1 && timeout 3600 hexdump -C /dev/input/eventN > /tmp/mouse_event_hexdump.log 2>/dev/null & echo $! > /tmp/mouse_event_pid.txt || timeout 3600 cat /dev/input/eventN > /tmp/mouse_event_raw & echo $! > /tmp/mouse_event_pid.txt
- Replace eventN with the event number for your mouse. If you didn’t get that earlier, run:
awk '/^N: Name=/{name=$0} /^H: Handlers=/{print name " -> " $0}' /tmp/inputdev_before.txt
and copy the line that contains the Logitech mouse to find eventN.
Fallback (if timeout isn’t available)
- Start continuous dmesg: sh -c "dmesg -wH > /tmp/dmesg_live.log" & echo $! > /tmp/dmesg_pid.txt
- Start raw capture and then you can stop manually after ~3600s (I’ll show stop commands below).
4) Use the mouse normally for 1 hour (or until a permanent disconnect). Note wall‑clock time(s) of any drop(s). Watch whether the mouse Easy‑Switch LED goes out or whether Slax auto‑reconnects.
After the hour (or immediately after any permanent disconnect) — stop captures and collect files
kill $(cat /tmp/dmesg_pid.txt) 2>/dev/null || true
kill $(cat /tmp/mouse_event_pid.txt) 2>/dev/null || true
lsusb > /tmp/lsusb_after.txt
cat /proc/bus/input/devices > /tmp/inputdev_after.txt
START=$(date --iso-8601=seconds)
tar -czf /tmp/mouselinuxlogs_${START}.tgz /tmp/dmesg_live.log /tmp/lsusb_before.txt /tmp/lsusb_after.txt /tmp/lsusb_tree_before.txt /tmp/inputdev_before.txt /tmp/inputdev_after.txt /tmp/mouse_event_hexdump.log /tmp/mouse_event
raw 2>/dev/null && echo "/tmp/mouselinuxlogs${START}.tgz created"
Copy the tarball off Slax so you can attach it to the forum
- If a USB stick auto‑mounts:
cp /tmp/mouselinuxlogs_${START}.tgz /media/$(ls /media | head -n1)/
- If you can’t copy it, tell me the full path and I’ll tell you how to get it off the live session.
What I’ll look for in the logs (and what each outcome means)
- dmesg lines like “usb X‑Y: USB disconnect”, “device descriptor read/failed”, “reset high-speed USB device”, or xhci_hcd/ehci_hcd errors → Windows‑style host/controller resets are likely on the problem PC (we’d then focus on chipset/USB drivers or BIOS/host controller).
- If lsusb BEFORE shows the receiver but lsusb AFTER no longer lists it at the drop time → USB enumeration/port issue (host).
- If the receiver stays present in lsusb but the mouse event capture stops (no more input events) → radio/session loss (device side or pairing), which would normally reproduce on other hosts; your Slax brief auto‑reconnect already points away from a hard hardware failure.
When you upload
- Attach the /tmp/mouselinuxlogs_*.tgz file here and tell me the approximate time(s) of any drop(s) during the hour (wall clock). I’ll parse dmesg, lsusb, and the input event capture and give the single next action (driver/BIOS update, keep using extension, re‑pair/RMA, etc.). fileciteturn8file6turn8file11
If you want, I’ll wait here while you run it and then parse immediately after you attach the tarball. Otherwise run the test and post the tarball when you’re back in Windows — I’ll analyze and reply the moment it’s attached. Sound good?
