Bug 872925 - ThinkPad X230: Trackpoint does not work on every boot.
Summary: ThinkPad X230: Trackpoint does not work on every boot.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 20
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 905201 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-04 10:59 UTC by Artur M.
Modified: 2014-11-25 17:11 UTC (History)
15 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-11-25 17:11:57 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Artur M. 2012-11-04 10:59:11 UTC
Description of problem:
On random boots the trackpoint does not work at all on ThinkPad X230, and the touchpad is fully functional. It is more likely the trackpoint will not work when I try to move the pointer during the boot.

Version-Release number of selected component (if applicable):
3.6.3-1.fc17.x86_64

How reproducible:
Move the trackpoint during the boot up, and the system should boot into X with the trackpoint "disabled".

Additional info:
The bug seems to be related to: https://bugzilla.redhat.com/show_bug.cgi?id=746208

Comment 1 Artur M. 2012-11-04 11:02:24 UTC
This bug may be also related to the issue described here: https://bbs.archlinux.org/viewtopic.php?id=143228

Comment 2 Artur M. 2013-01-08 16:45:01 UTC
The issue persists with 3.6.10-2.fc17.x86_64. Suspending the system helps, but the settings of trackpoint sensitivity and speed do not take effect after waking it up. Rebooting the system is still the easiest option to get (hopefully) everything back to normal.

Comment 3 Artur M. 2013-01-16 19:16:36 UTC
The issue persists with 3.6.11-1.fc17.x86_64.

Comment 4 Artur M. 2013-01-22 12:25:32 UTC
The issue persists with Fedora 18...

Comment 5 Gabriel 2013-01-28 20:46:10 UTC
*** Bug 905201 has been marked as a duplicate of this bug. ***

Comment 6 Gabriel 2013-01-28 20:50:16 UTC
I'd just like to emphasize here that the trackpoint tends to act broken when I absentmindedly 'wiggle' it during boot. I don't think it's ever happened to me when I let the machine boot hands-off.

There are working/non-working dmesg and Xorg.0.logs attached to Bug 905201.

Comment 7 Artur M. 2013-01-28 22:00:21 UTC
There exists a workaround that seems to be working fine (at least for me). If you don't use the trackpad, just disable it (in BIOS), and the trackpoint should work 100% of the time.

Comment 8 Josh Boyer 2013-04-01 19:44:14 UTC
Is this still an issue with 3.8.x?

Comment 9 Artur M. 2013-04-03 15:11:45 UTC
(In reply to comment #8)
> Is this still an issue with 3.8.x?

Unfortunately, I think it is. I am unable to confirm that with 100% because of how randomly it happens. Now I'm working with the trackpad disabled, which has always solved this issue, but I think it happened to me on 3.8.x too, when the trackpad was enabled.

Comment 10 Gabriel 2013-04-03 19:27:14 UTC
Yes, this is still an issue on 3.8.4-202.fc18.x86_64... I can make it happen most of the time by restarting the machine and wiggling the trackpoint until GDM appears. The only way to make the trackpoint work again is to reboot and not touch it until boot is complete.

I have never had the issue when the trackpoint is not touched turing boot.

Comment 11 Mikhail Kulemin 2013-04-04 09:15:02 UTC
Yes, I also can confirm this issue on 3.8.4-202.fc18.x86_64. I need to say that reboot is not the only way to make trackpoint work. One can go to sleep mode and when notebook wake up trackpoint works again.

Comment 12 Tom Repetti 2013-06-17 09:55:26 UTC
This issue continues on 3.9.5-201.fc18.x86_64. I also upgraded to an X230 and have similar problems. It is also worth noting that there are identical bugs on multiple operating systems. Like, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/986942 for example. They all seem to emerge around kernel 3.2. It is a shame that this is a problem, because linux once supported ThinkPads so well.

Comment 13 Mikhail Kulemin 2013-07-09 18:51:06 UTC
It seems that it is kernel bug
https://bugzilla.kernel.org/show_bug.cgi?id=33292

Comment 14 Justin M. Forbes 2013-10-18 21:11:14 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 18 kernel bugs.

Fedora 18 has now been rebased to 3.11.4-101.fc18.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 19, and are still experiencing this issue, please change the version to Fedora 19.

If you experience different issues, please open a new bug report for those.

Comment 15 Wei Shi 2013-10-26 03:05:45 UTC
Still happened to me on Fedora 19 with X230.

Comment 16 Jeff Iddings 2013-12-21 21:31:50 UTC
I also have a X230 and I can confirm this issue in Fedora 20 as well. It seems to happen after a cold boot most frequently.

Comment 17 Dylan Graham 2014-01-10 06:41:39 UTC
Still present on kernel-3.12.6-300.fc20.x86_64

Comment 18 Justin M. Forbes 2014-03-10 14:38:37 UTC
*********** MASS BUG UPDATE **************

This bug has been in a needinfo state for more than 1 month and is being closed with insufficient data due to inactivity. If this is still an issue with Fedora 19, please feel free to reopen the bug and provide the additional information requested.

Comment 19 Dan Smith 2014-03-29 22:50:26 UTC
This happens for me as well on Fedora 20 with kernel 3.13.3-201.fc20.x86_64. I just noticed it after a cold boot, and doing a suspend/resume cycle resolved the problem. I was not touching the trackpoint during boot.

Machine is a Lenovo X230 running pretty much stock Fedora 20.

Comment 20 Justin M. Forbes 2014-05-21 19:39:11 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs.

Fedora 20 has now been rebased to 3.14.4-200.fc20.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.

Comment 21 Jeff Iddings 2014-05-21 19:46:13 UTC
For what it's worth, I have not experienced this issue in quite some time, though I don't reboot all that often. I'm running fully updated Fedora 20.

Comment 22 Wei Shi 2014-05-22 01:44:37 UTC
Same problem on
3.14.4-200.fc20.x86_64

Comment 23 Justin M. Forbes 2014-11-13 16:00:23 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs.

Fedora 20 has now been rebased to 3.17.2-200.fc20.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 21, and are still experiencing this issue, please change the version to Fedora 21.

If you experience different issues, please open a new bug report for those.

Comment 24 Jesus M. Rodriguez 2014-11-25 16:45:27 UTC
I've had no problems with my X230 on F20 using any of the following 3 kernels:

kernel-3.16.6-203.fc20.x86_64
kernel-3.16.7-200.fc20.x86_64
kernel-3.17.3-200.fc20.x86_64


Note You need to log in before you can comment on or make changes to this bug.