Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #226706 > unrolled thread

Trackpoint not work properly on Thinkpad T470

Back to article view | Back to linux.debian.user

Contents

  Trackpoint not work properly on Thinkpad T470 Aaron Elmquist <elmq0022@umn.edu> - 2020-09-05 02:10 +0200
    Re: Trackpoint not work properly on Thinkpad T470 rhkramer@gmail.com - 2020-09-05 13:20 +0200
      Re: Trackpoint not work properly on Thinkpad T470 Aaron Elmquist <elmq0022@umn.edu> - 2020-09-05 18:40 +0200
        Re: Trackpoint not work properly on Thinkpad T470 rhkramer@gmail.com - 2020-09-05 19:50 +0200
          Re: Trackpoint not work properly on Thinkpad T470 riveravaldez <riveravaldezmail@gmail.com> - 2020-09-06 00:20 +0200
            Re: Trackpoint not work properly on Thinkpad T470 Andrew Cater <amacater@gmail.com> - 2020-09-06 17:00 +0200
              Re: Trackpoint not work properly on Thinkpad T470 Aaron Elmquist <elmq0022@umn.edu> - 2020-09-06 17:40 +0200

#226706 — Trackpoint not work properly on Thinkpad T470

[Multipart message — attachments visible in raw view] — view raw

Hi,

I'm on debian buster using KDE as my GUI. My trackpoint was working quite
well until a month or two ago (maybe more).  Now it has some odd behavior
where it will snap to the bottom of the screen every so often when I'm
using it.

Seems like the input is very sensitive to the bottom direction.  No
snapping to any other location  Really seems like the input in the down
direction became overly sensitive.  I can't really control the rate of a
downward cursor movement consistently.   It's just to fast from time to
time.

Any help would be appreciated.  I would provide more details, configs,
etc., but I'm not really sure what's relevant.

Thanks,
Aaron

[toc] | [next] | [standalone]

#226710

On Friday, September 04, 2020 07:55:43 PM Aaron Elmquist wrote:
> I'm on debian buster using KDE as my GUI. My trackpoint was working quite
> well until a month or two ago (maybe more).  Now it has some odd behavior
> where it will snap to the bottom of the screen every so often when I'm
> using it.
> 
> Seems like the input is very sensitive to the bottom direction.  No
> snapping to any other location  Really seems like the input in the down
> direction became overly sensitive.  I can't really control the rate of a
> downward cursor movement consistently.   It's just to fast from time to
> time.
> 
> Any help would be appreciated.  I would provide more details, configs,
> etc., but I'm not really sure what's relevant.

I suspect you suspect the same thing I do, that it is a hardware problem.

I don't have any idea how hard it may be to get or to replace a trackpoint -- 
you may have to replace the entire keyboard as a unit, which may not be all 
that hard.

If it were mine, I would look for an external tracking device (mouse, 
trackball, ???) and start using it instead of the trackpoint.  For traveling, 
there are some very small mice available.

[toc] | [prev] | [next] | [standalone]

#226713

[Multipart message — attachments visible in raw view] — view raw

Well, I don't think it's a hardware issue.  The computer is less than a
year old and it's been used sporadically over the last year.  Any thoughts
on how to rule hardware out as an issue?

On Sat, Sep 5, 2020 at 6:18 AM <rhkramer@gmail.com> wrote:

> On Friday, September 04, 2020 07:55:43 PM Aaron Elmquist wrote:
> > I'm on debian buster using KDE as my GUI. My trackpoint was working quite
> > well until a month or two ago (maybe more).  Now it has some odd behavior
> > where it will snap to the bottom of the screen every so often when I'm
> > using it.
> >
> > Seems like the input is very sensitive to the bottom direction.  No
> > snapping to any other location  Really seems like the input in the down
> > direction became overly sensitive.  I can't really control the rate of a
> > downward cursor movement consistently.   It's just to fast from time to
> > time.
> >
> > Any help would be appreciated.  I would provide more details, configs,
> > etc., but I'm not really sure what's relevant.
>
> I suspect you suspect the same thing I do, that it is a hardware problem.
>
> I don't have any idea how hard it may be to get or to replace a trackpoint
> --
> you may have to replace the entire keyboard as a unit, which may not be
> all
> that hard.
>
> If it were mine, I would look for an external tracking device (mouse,
> trackball, ???) and start using it instead of the trackpoint.  For
> traveling,
> there are some very small mice available.
>
>

[toc] | [prev] | [next] | [standalone]

#226715

On Saturday, September 05, 2020 12:34:37 PM Aaron Elmquist wrote:
> Well, I don't think it's a hardware issue.  The computer is less than a
> year old and it's been used sporadically over the last year.  Any thoughts
> on how to rule hardware out as an issue?

Sorry, no, not off the top of my head, and no time to dig into it, atm.

Oh, maybe one idea, did it come with Windows and is it still there (I mean, 
can you boot into Windows?) -- if so, do that, and try a similar app in 
Windows.

In Linux, does the problem happen in only one application, or in other 
applications as well?

I hope somebody else will be able to help you.

[toc] | [prev] | [next] | [standalone]

#226717

On 9/5/20, rhkramer@gmail.com <rhkramer@gmail.com> wrote:
> On Saturday, September 05, 2020 12:34:37 PM Aaron Elmquist wrote:
>> Well, I don't think it's a hardware issue.  The computer is less than a
>> year old and it's been used sporadically over the last year.  Any
>> thoughts
>> on how to rule hardware out as an issue?
>
> Oh, maybe one idea, did it come with Windows and is it still there (I mean, can you boot into Windows?) -- if so, do that, and try a similar app in Windows.
>
> In Linux, does the problem happen in only one application, or in other
> applications as well?

Basic thought: grab any-distro LiveUSB and boot from there and check
if the issue persist.

If any other OS makes the hardware works fine then at least that cause
could be ruled out.

Hope this help, best regards.

[toc] | [prev] | [next] | [standalone]

#226725

[Multipart message — attachments visible in raw view] — view raw

Also - check carefully what firmware it might require. You have, for
example, installed firmware-linux-nonfree, firmware-misc-nonfree to enable
non-free firmware possibly?

On Sat, Sep 5, 2020 at 10:12 PM riveravaldez <riveravaldezmail@gmail.com>
wrote:

> On 9/5/20, rhkramer@gmail.com <rhkramer@gmail.com> wrote:
> > On Saturday, September 05, 2020 12:34:37 PM Aaron Elmquist wrote:
> >> Well, I don't think it's a hardware issue.  The computer is less than a
> >> year old and it's been used sporadically over the last year.  Any
> >> thoughts
> >> on how to rule hardware out as an issue?
> >
> > Oh, maybe one idea, did it come with Windows and is it still there (I
> mean, can you boot into Windows?) -- if so, do that, and try a similar app
> in Windows.
> >
> > In Linux, does the problem happen in only one application, or in other
> > applications as well?
>
> Basic thought: grab any-distro LiveUSB and boot from there and check
> if the issue persist.
>
> If any other OS makes the hardware works fine then at least that cause
> could be ruled out.
>
> Hope this help, best regards.
>
>

[toc] | [prev] | [next] | [standalone]

#226726

[Multipart message — attachments visible in raw view] — view raw

Thanks for the tip! I will have to check those out as well.  I believe I
did have the non free when I setup to ensure Wi-Fi support.  I don't know
if the miscellaneous non free was included with that build.

I used an unofficial build from here using the netinst.iso writtento a
USB.

https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/current/amd64/iso-cd/


Here are my apt sources.  Anything you think I should add?

# deb cdrom:[Debian GNU/Linux 10.2.0 _Buster_ - Unofficial amd64 NETINST
with firmware 20191116-09:56]/ buster contrib main non-free

# deb cdrom:[Debian GNU/Linux 10.2.0 _Buster_ - Unofficial amd64 NETINST
with firmware 20191116-09:56]/ buster contrib main non-free

deb http://deb.debian.org/debian/ buster main non-free contrib
deb-src http://deb.debian.org/debian/ buster main non-free contrib

deb http://security.debian.org/debian-security buster/updates main contrib
non-free
deb-src http://security.debian.org/debian-security buster/updates main
contrib non-free

# buster-updates, previously known as 'volatile'
deb http://deb.debian.org/debian/ buster-updates main contrib non-free
deb-src http://deb.debian.org/debian/ buster-updates main contrib non-free

# This system was installed using small removable media
# (e.g. netinst, live or single CD). The matching "deb cdrom"
# entries were disabled at the end of the installation process.
# For information about how to configure apt package sources,
# see the sources.list(5) manual.
deb [arch=amd64] https://download.docker.com/linux/debian buster stable
# deb-src [arch=amd64] https://download.docker.com/linux/debian buster
stable
# deb-src [arch=amd64] https://download.docker.com/linux/debian buster
stable


On Sun, Sep 6, 2020, 9:50 AM Andrew Cater <amacater@gmail.com> wrote:

> Also - check carefully what firmware it might require. You have, for
> example, installed firmware-linux-nonfree, firmware-misc-nonfree to enable
> non-free firmware possibly?
>
> On Sat, Sep 5, 2020 at 10:12 PM riveravaldez <riveravaldezmail@gmail.com>
> wrote:
>
>> On 9/5/20, rhkramer@gmail.com <rhkramer@gmail.com> wrote:
>> > On Saturday, September 05, 2020 12:34:37 PM Aaron Elmquist wrote:
>> >> Well, I don't think it's a hardware issue.  The computer is less than a
>> >> year old and it's been used sporadically over the last year.  Any
>> >> thoughts
>> >> on how to rule hardware out as an issue?
>> >
>> > Oh, maybe one idea, did it come with Windows and is it still there (I
>> mean, can you boot into Windows?) -- if so, do that, and try a similar app
>> in Windows.
>> >
>> > In Linux, does the problem happen in only one application, or in other
>> > applications as well?
>>
>> Basic thought: grab any-distro LiveUSB and boot from there and check
>> if the issue persist.
>>
>> If any other OS makes the hardware works fine then at least that cause
>> could be ruled out.
>>
>> Hope this help, best regards.
>>
>>

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web