Skip to content

Instantly share code, notes, and snippets.

@AnotherKamila
Last active April 14, 2021 18:09
Show Gist options
  • Star 1 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save AnotherKamila/c14c3ebd66ac6a25c0193f8e103e66e3 to your computer and use it in GitHub Desktop.
Save AnotherKamila/c14c3ebd66ac6a25c0193f8e103e66e3 to your computer and use it in GitHub Desktop.
# Put me into /usr/local/etc/X11/xorg.conf.d/
# Replace XXX by the appropriate device:
# guess from `sudo libinput list-devices` (TODO I should write more precise instructions)
Section "ServerLayout"
Identifier ":-("
InputDevice "Trackpoint0" "CorePointer"
InputDevice "Touchpad0" "CorePointer"
EndSection
Section "InputDevice"
Identifier "Touchpad0"
Driver "libinput"
Option "Device" "/dev/input/event6"
Option "DisableWhileTyping" "on"
Option "ScrollMethod" "twofinger"
Option "Tapping" "on"
Option "TappingButtonMap" "lrm"
Option "ClickMethod" "clickfinger"
EndSection
Section "InputDevice"
Identifier "Trackpoint0"
Driver "libinput"
Option "Device" "/dev/input/event3"
EndSection
@dacracker
Copy link

@ltning:

If you have a gen8 I'd be very interested in knowing how it works for you. Mine hard-wedges under load after a minute or two (no X running, just building pkg immediately after install), and at random intervals if idle. I did get drm-devel-kmod working and after many many reboots plasma5 runs (for a short while). Basically nothing else works.

I am assuming you are running CURRENT. My gen7 started hard-wedging (first only under heavy load, later just "a minute or two after startup") too. It seems like someone was fiddling with CPU powersaving sometime around February and messed up for these CPUs. I have not had time to bisect for the exact commit, it would be great if someone could. In the meantime, my (sad) workaround is to disable all CPU powersaving:

/boot/loader.conf

hint.hwpstate_intel.0.disabled="1"

Any news regarding this issue? I upgraded my Thinkpad X1 Carbon to
FreeBSD 13.0-RELEASE and experience the same issue. I have applied
the suggested workaround for now. Do you know if this issue has been
reported as a bug?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment