Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Weird random reboot -- thinkpad x220

70 views
Skip to first unread message

Ivan Kovnatsky

unread,
Apr 28, 2014, 2:10:01 PM4/28/14
to
Hi Guys,

Today returned home from work, saw that instead of X on my laptop virtual
console is opened. That pretty amused me, -- almost never shutdown my laptop
if it stays home. Looking into last command output I saw that a reboot
happened around 11:29 Apr 28:

__
sevenfou pts/1 :0 Mon Apr 28 19:23 - down (00:31)
sevenfou pts/0 :0 Mon Apr 28 19:21 - down (00:32)
root tty3 Mon Apr 28 19:21 - 19:30 (00:08)
sevenfou pts/0 XXXXXXXXXXXXX Mon Apr 28 15:56 - 16:38 (00:41)
reboot system boot 3.13-1-amd64 Mon Apr 28 11:29 - 19:54 (08:24)
sevenfou pts/9 :0 Sun Apr 27 10:31 - 16:50 (06:18)
sevenfou pts/9 :0 Sun Apr 27 01:26 - 01:36 (00:10)
__


here is /var/log/syslog:
__
Apr 28 11:25:01 lefrat /USR/SBIN/CRON[28141]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 28 11:25:16 lefrat kernel: [306970.108480] iptables denied: IN=wlan1 OUT= MAC=e0:94:67:0c:20:2c:54:04:a6:e8:1d:a4:08:00 SRC=173.194.39.132 DST=192.168.1.218 LEN=40 TOS=0x00 PREC=0x00 TTL=50 ID=43730 PROTO=TCP SPT=443 DPT=60021 WINDOW=0 RES=0x00 RST URGP=0
Apr 28 11:25:16 lefrat kernel: [306970.109093] iptables denied: IN=wlan1 OUT= MAC=e0:94:67:0c:20:2c:54:04:a6:e8:1d:a4:08:00 SRC=173.194.39.132 DST=192.168.1.218 LEN=40 TOS=0x00 PREC=0x00 TTL=50 ID=43731 PROTO=TCP SPT=443 DPT=60021 WINDOW=0 RES=0x00 RST URGP=0
Apr 28 11:25:16 lefrat kernel: [306970.109670] iptables denied: IN=wlan1 OUT= MAC=e0:94:67:0c:20:2c:54:04:a6:e8:1d:a4:08:00 SRC=173.194.39.132 DST=192.168.1.218 LEN=40 TOS=0x00 PREC=0x00 TTL=50 ID=43732 PROTO=TCP SPT=443 DPT=60021 WINDOW=0 RES=0x00 RST URGP=0
Apr 28 11:27:01 lefrat /USR/SBIN/CRON[30771]: (root) CMD (/usr/local/sbin/batlow)
Apr 28 11:29:37 lefrat rsyslogd: [origin software="rsyslogd" swVersion="7.6.3" x-pid="2239" x-info="http://www.rsyslog.com"] start
Apr 28 11:29:37 lefrat kernel: [ 0.000000] Initializing cgroup subsys cpuset
Apr 28 11:29:37 lefrat kernel: [ 0.000000] Initializing cgroup subsys cpu
Apr 28 11:29:37 lefrat kernel: [ 0.000000] Initializing cgroup subsys cpuacct
Apr 28 11:29:37 lefrat kernel: [ 0.000000] Linux version 3.13-1-amd64 (debian...@lists.debian.org) (gcc version 4.8.2 (Debian 4.8.2-16) ) #1 SMP Debian 3.13.10-1 (2014-04-15)
Apr 28 11:29:37 lefrat kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-3.13-1-amd64 root=/dev/sda1 ro
Apr 28 11:29:37 lefrat kernel: [ 0.000000] Disabled fast string operations
Apr 28 11:29:37 lefrat kernel: [ 0.000000] e820: BIOS-provided physical RAM map:
__


/var/log/debug:
__
Apr 28 11:25:16 lefrat kernel: [306970.108480] iptables denied: IN=wlan1 OUT= MAC=e0:94:67:0c:20:2c:54:04:a6:e8:1d:a4:08:00 SRC=173.194.39.132 DST=192.168.1.218 LEN=40 TO
S=0x00 PREC=0x00 TTL=50 ID=43730 PROTO=TCP SPT=443 DPT=60021 WINDOW=0 RES=0x00 RST URGP=0
Apr 28 11:25:16 lefrat kernel: [306970.109093] iptables denied: IN=wlan1 OUT= MAC=e0:94:67:0c:20:2c:54:04:a6:e8:1d:a4:08:00 SRC=173.194.39.132 DST=192.168.1.218 LEN=40 TO
S=0x00 PREC=0x00 TTL=50 ID=43731 PROTO=TCP SPT=443 DPT=60021 WINDOW=0 RES=0x00 RST URGP=0
Apr 28 11:25:16 lefrat kernel: [306970.109670] iptables denied: IN=wlan1 OUT= MAC=e0:94:67:0c:20:2c:54:04:a6:e8:1d:a4:08:00 SRC=173.194.39.132 DST=192.168.1.218 LEN=40 TO
S=0x00 PREC=0x00 TTL=50 ID=43732 PROTO=TCP SPT=443 DPT=60021 WINDOW=0 RES=0x00 RST URGP=0
Apr 28 11:29:37 lefrat kernel: [ 0.000000] DMI: LENOVO 4286CTO/4286CTO, BIOS 8DET69WW (1.39 ) 07/18/2013
Apr 28 11:29:37 lefrat kernel: [ 0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Apr 28 11:29:37 lefrat kernel: [ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Apr 28 11:29:37 lefrat kernel: [ 0.000000] MTRR default type: uncachable
Apr 28 11:29:37 lefrat kernel: [ 0.000000] MTRR fixed ranges enabled:
Apr 28 11:29:37 lefrat kernel: [ 0.000000] 00000-9FFFF write-back
Apr 28 11:29:37 lefrat kernel: [ 0.000000] A0000-BFFFF uncachable
Apr 28 11:29:37 lefrat kernel: [ 0.000000] C0000-FFFFF write-protect
Apr 28 11:29:37 lefrat kernel: [ 0.000000] MTRR variable ranges enabled:
__


/var/log/auth.log:
__
Apr 28 11:25:01 lefrat CRON[28140]: pam_unix(cron:session): session opened for user root by (uid=0)
Apr 28 11:25:01 lefrat CRON[28140]: pam_unix(cron:session): session closed for user root
Apr 28 11:27:01 lefrat CRON[30770]: pam_unix(cron:session): session opened for user root by (uid=0)
Apr 28 11:27:01 lefrat CRON[30770]: pam_unix(cron:session): session closed for user root
Apr 28 11:29:38 lefrat sshd[2527]: Server listening on 0.0.0.0 port xxxxx.
Apr 28 11:30:03 lefrat CRON[2635]: pam_unix(cron:session): session opened for user sevenfourk by (uid=0)
Apr 28 11:30:03 lefrat CRON[2633]: pam_unix(cron:session): session opened for user root by (uid=0)
Apr 28 11:30:03 lefrat CRON[2634]: pam_unix(cron:session): session opened for user sevenfourk by (uid=0)
Apr 28 11:30:03 lefrat CRON[2633]: pam_unix(cron:session): session closed for user root
__


Also there was no any power losses for sure:
__
Apr 28 11:18:01 /usr/local/sbin/batlow: Battery: Normal: 99%
Apr 28 11:21:01 /usr/local/sbin/batlow: Battery: Normal: 99%
Apr 28 11:24:01 /usr/local/sbin/batlow: Battery: Normal: 99%
Apr 28 11:27:01 /usr/local/sbin/batlow: Battery: Normal: 99%
Apr 28 11:30:03 /usr/local/sbin/batlow: Battery: Normal: 99%
Apr 28 11:33:01 /usr/local/sbin/batlow: Battery: Normal: 99%
__


Very strange, hopefully I'm not paranoid. No one was at home at that time.
Maybe I'm missing something, maybe another log to check. I would be glad if
someone shares some thoughts on looking into details on reboot info.


Thanks,
Ivan.

signature.asc

Ivan Kovnatsky

unread,
Apr 29, 2014, 3:00:02 PM4/29/14
to
signature.asc

Paul Seyfert

unread,
Apr 29, 2014, 4:00:02 PM4/29/14
to
Hi,

you're not paranoid, I've seen sudden reboots running wheezy (when it
was testing and i think even since it's stable) on my x220 as well.
though very rarely. i don't recall having seen it since September. but i
remember it even happened once when i was sitting in front of it.

I'm sorry i have to date not the slightest idea how to reproduce the
behaviour.

the time i happened to see it, it looked like the power went out (with
PSU connected and battery fully charged). after about a second in which
i wondered what was going on, the computer booted as if it was switched
off and somebody pressed the power button.

It's not triggered by high CPU temperature (reached heavier loads and
higher package temperatures often). It's also not electrostatic sparks
(my office chair + clothes quite often gave sparkes over the keyboard or
headset connector which didn't harm the device).
It's also not triggered by large uptimes (also reached much larger
values than when the sudden-reboot happened often).

Cheers,
Paul
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/535FF974...@mathphys.fsk.uni-heidelberg.de

Zenaan Harkness

unread,
Apr 30, 2014, 4:40:02 AM4/30/14
to
Please bottom-post, not top-post.

See below for my comments.


On 4/30/14, Paul Seyfert <psey...@mathphys.fsk.uni-heidelberg.de> wrote:
> you're not paranoid, I've seen sudden reboots running wheezy (when it
> was testing and i think even since it's stable) on my x220 as well.
> though very rarely. i don't recall having seen it since September. but i
> remember it even happened once when i was sitting in front of it.
>
> I'm sorry i have to date not the slightest idea how to reproduce the
> behaviour.

See below.

> the time i happened to see it, it looked like the power went out (with
> PSU connected and battery fully charged). after about a second in which
> i wondered what was going on, the computer booted as if it was switched
> off and somebody pressed the power button.

I run sid, and have reproduced this when x220 is connected to power/
"battery slice" which is like a docking station, but it's just a
battery.

When connecting power to the slice (recommended, apparently when slice
is connected, should not connect power to laptop (which has its own
power connector of course) but to slice power connector.

This causes instant reboot for me.

I have not had time to check out LENOVO bios updates yet.

This is a known problem. I haven't finished reading giyf search
results to determine how to fix, would like to know myself of course.

So x220 laptops have known power problems. Also with regular internal
battery: battery can reach a state where the ACPI (or whatever it is)
can no longer reliably tell you what charge state the battery is. I
have reverted to disabling automatic shutdown and power-low
notifications, since the battery status can change back and forth to
eg 2hrs to go, empty, 1hr55 to go, empty etc. and each "empty" causes
annoying pop ups.

There was a recommended option to properly power cycle the battery by
disconnecting from power, and run the laptop till auto shutoff, then
fully charge, but this doesn't reset the battery internal status (or
whatever it is) properly, in my experience.

I have two different internal batteries I have tried, 6-cell and
9cell, and the slice battery. All seem to display this latter problem
eventually.

So, at least two known battery/ power problems with the x220s. Very
annoying. I just put up with it, and don't rely on the slice battery
any more. Looks great. Great in theory. Sort of gives you more uptime,
but "reboot on power-connect" is unacceptable, and makes the
internal/slice combo kinda useless anyway - just use the 9cell
internal battery!

DAMN how we need an open source libre BIOS! I can _smell_ the nature
of the problem, but we have no access to code to create solutions...

Good luck
Zenaan


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/CAOsGNSRd+SOHdi=iSGE_gvZRaPbAq0OS...@mail.gmail.com

Paul Seyfert

unread,
Apr 30, 2014, 5:00:03 AM4/30/14
to
On 30.04.2014 10:35, Zenaan Harkness wrote:
> Please bottom-post, not top-post.

> On 4/30/14, Paul Seyfert <psey...@mathphys.fsk.uni-heidelberg.de> wrote:
>> you're not paranoid, I've seen sudden reboots running wheezy (when it
>> was testing and i think even since it's stable) on my x220 as well.
>> though very rarely. i don't recall having seen it since September. but i
>> remember it even happened once when i was sitting in front of it.
>>
>> I'm sorry i have to date not the slightest idea how to reproduce the
>> behaviour.
>
> See below.
>
>> the time i happened to see it, it looked like the power went out (with
>> PSU connected and battery fully charged). after about a second in which
>> i wondered what was going on, the computer booted as if it was switched
>> off and somebody pressed the power button.
>
> I run sid, and have reproduced this when x220 is connected to power/
> "battery slice" which is like a docking station, but it's just a
> battery.
>
> When connecting power to the slice (recommended, apparently when slice
> is connected, should not connect power to laptop (which has its own
> power connector of course) but to slice power connector.
>
> This causes instant reboot for me.
>

hm, i use various combinations.
* 9 cell
* 9 cell + PSU
* 9 cell + docking station + PSU connected to notebook
* 9 cell + docking station + PSU connected to docking station
* 9 cell + slice
* 9 cell + slice + PSU connected to slice
* 9 cell + slice + PSU connected to notebook (yes, rarely i end up in
the not-recommended setting)

it didn't occur to me that the random reboot is due to a particular
setting, none of the settings reliably triggers the reboot.

> I have not had time to check out LENOVO bios updates yet.
>

this is different for me. i had quite some problems with the very early
bios versions of the x220 when I got it. After three updates I ended up with

UEFI: 1.17 / ECP: 1.08


> This is a known problem. I haven't finished reading giyf search
> results to determine how to fix, would like to know myself of course.
>
> So x220 laptops have known power problems. Also with regular internal
> battery: battery can reach a state where the ACPI (or whatever it is)
> can no longer reliably tell you what charge state the battery is. I
> have reverted to disabling automatic shutdown and power-low
> notifications, since the battery status can change back and forth to
> eg 2hrs to go, empty, 1hr55 to go, empty etc. and each "empty" causes
> annoying pop ups.


I think this is a different problem. For the random reboot, let me
repeat that i didn't see a shutdown when i was present at the random
shutdown event. the notebook was suddenly off. like removing the battery
and unplugging the PSU. so the random reboot doesn't seem acpi related
to me.

>
> [...]

Cheers,
Paul


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/5360BB4...@mathphys.fsk.uni-heidelberg.de

Zenaan Harkness

unread,
Apr 30, 2014, 5:30:03 AM4/30/14
to
Thanks for the reference. I shall look into this at some point.

>> This is a known problem. I haven't finished reading giyf search
>> results to determine how to fix, would like to know myself of course.
>>
>> So x220 laptops have known power problems. Also with regular internal
>> battery: battery can reach a state where the ACPI (or whatever it is)
>> can no longer reliably tell you what charge state the battery is. I
>> have reverted to disabling automatic shutdown and power-low
>> notifications, since the battery status can change back and forth to
>> eg 2hrs to go, empty, 1hr55 to go, empty etc. and each "empty" causes
>> annoying pop ups.
>
>
> I think this is a different problem. For the random reboot, let me
> repeat that i didn't see a shutdown when i was present at the random
> shutdown event. the notebook was suddenly off. like removing the battery
> and unplugging the PSU. so the random reboot doesn't seem acpi related
> to me.

If you had a power brownout whilst you were away, then your random
reboot _may_ have been similar to mine - that was my suggestion. I do
not know of course.

Mine reboot can be triggered by:
a) 9-cell+slice, PSU disconnected, laptop started (even at console)
b) connect PSU to slice, witness instant reboot

Either way, it appears there are various battery issues, of one form
or another, with x220 laptop.

Good luck
Zenaan


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/CAOsGNSRh1WAPKt-1ZQCv3EUD...@mail.gmail.com

Ivan Kovnatsky

unread,
May 1, 2014, 11:30:02 AM5/1/14
to

Hi Guys,
Just bought a used x220, pretty happy to have it. Haven't looked into BIOS
updates yet too. Thanks for the hint.

> >> This is a known problem. I haven't finished reading giyf search
> >> results to determine how to fix, would like to know myself of course.
> >>
> >> So x220 laptops have known power problems. Also with regular internal
> >> battery: battery can reach a state where the ACPI (or whatever it is)
> >> can no longer reliably tell you what charge state the battery is. I
> >> have reverted to disabling automatic shutdown and power-low
> >> notifications, since the battery status can change back and forth to
> >> eg 2hrs to go, empty, 1hr55 to go, empty etc. and each "empty" causes
> >> annoying pop ups.
> >
> >
> > I think this is a different problem. For the random reboot, let me
> > repeat that i didn't see a shutdown when i was present at the random
> > shutdown event. the notebook was suddenly off. like removing the battery
> > and unplugging the PSU. so the random reboot doesn't seem acpi related
> > to me.
>
> If you had a power brownout whilst you were away, then your random
> reboot _may_ have been similar to mine - that was my suggestion. I do
> not know of course.
>
> Mine reboot can be triggered by:
> a) 9-cell+slice, PSU disconnected, laptop started (even at console)
> b) connect PSU to slice, witness instant reboot
>
> Either way, it appears there are various battery issues, of one form
> or another, with x220 laptop.
>
> Good luck
> Zenaan

Firstly thanks for pointing on possible ideas why reboot could happen.
Initially I've thought more to software issue side, but not the hardware.
Honestly this upsetting a bit, so nice laptop nowadays, not much could be
comparable to it, in design and comfort also.

I see you guys seen reboots more often then me obviously using it more. Will
monitor the situation.


Ivan.
signature.asc

Zenaan Harkness

unread,
May 1, 2014, 11:00:02 PM5/1/14
to
On 5/2/14, Ivan Kovnatsky <seven...@gmail.com> wrote:
...

Unrelated, but how do you find the trackpad? I completely disabled
mine in BIOS, since the "textured bumps" on it make the pointer (even
at extreme settings) useless for fine mouse work - I could not make it
work in non-extremely-annoying way.


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/CAOsGNSSyFMuiuMnRt7J8MB4f...@mail.gmail.com

Ivan Kovnatsky

unread,
May 2, 2014, 4:20:02 AM5/2/14
to
On May 02, 2014 at 05:54, Zenaan Harkness <z...@freedbms.net> wrote:
> On 5/2/14, Ivan Kovnatsky <seven...@gmail.com> wrote:
> ...
>
> Unrelated, but how do you find the trackpad? I completely disabled
> mine in BIOS, since the "textured bumps" on it make the pointer (even
> at extreme settings) useless for fine mouse work - I could not make it
> work in non-extremely-annoying way.

Hm, I used to it. I thought you meant touchpad, which I definitely disabled.
I do not do any complex sensitive mouse work, sometimes GIMPing, but for my
work it suits pretty well. Of course there's some cursor drifting while moving
mouse with trackpad , that's the case. But as I understood nothing can be done
here. For this small kind of laptops, I think trackpad is pretty useful.
Would one get a mouse if (rarely, nowadays in modern tiling managers mouse
work can be decreased to 5% of most time or even less) mouse can be replaced
with trackpoint ? Of course if one find it useful for him/her-self.


Ivan.

signature.asc

Steve Litt

unread,
May 2, 2014, 11:30:03 AM5/2/14
to
On Fri, 2 May 2014 12:54:24 +1000
Zenaan Harkness <z...@freedbms.net> wrote:

> On 5/2/14, Ivan Kovnatsky <seven...@gmail.com> wrote:
> ...
>
> Unrelated, but how do you find the trackpad? I completely disabled
> mine in BIOS, since the "textured bumps" on it make the pointer (even
> at extreme settings) useless for fine mouse work - I could not make it
> work in non-extremely-annoying way.

I'll go one step farther and say I *hate* the pads on most laptops.
Being a touch-typist, I don't pussy-foot around the keyboard, I hammer
it, and invariably my wrists or the heels of my hands tweak the
mousepad and doubleclick it or move off the field I'm filling in or
something. So I usually disable my mousepad. The following shellscript,
called "touchtoggle", toggles the pad on and off:

=========================================================
#!/bin/bash

curstate=`synclient | grep -i TouchpadOff | sed -e"s/.*= //"`
if test "$curstate" = "1"; then
synclient TouchpadOff=0
else
synclient TouchpadOff=1
fi
=========================================================

I always hook that shellscript to a hotkey, so I can instantly toggle
the state of the pad: off for general typing, on when I simply MUST use
the pad.

Also, in every carrying case for every laptop, I carry a trusty
Logitech M310 wireless led mouse. These mice are shaped well, have
enough sensitivity to be "fast enough" even with LXDE, and the scroll
wheel is stiff enough and its rotational clicks are discrete enough
that middle clicking can be done without fear of turning. So, unless
I'm trying to work where there's no table, I just use a regular mouse.

Have you ever tried the xxxterm browser? It might be called xombrero on
your Debian version. It's a browser made to be used with keystrokes
reminiscent of Vim: No mouse required. Here are the few commands you
must know in order to start being productive with xxxterm:

j: Move down
k: Move up
F6: Input a URL
:fav: Add current page to favorites
Alt+F: Show favorites
f: Toggle numbering of links. When links are numbered, you can follow
one by typing its number and pressing Enter. Sometimes pressing
Enter is optional.

As an added bonus, unlike all the bloatware browsers, xxxterm never
decides to take 50% to 100% of CPU, heating things up and forcing your
CPU fan to sound like a turbojet. I switched my default browser from
Firefox to xxxterm after one too many times when Firefox made my CPU
temperature go up to 79C.

SUMMARY:

I know nothing about the mouse pad on a thinkpad x220, but mouse pads
on most laptops are PITAs, and there are plenty of ways to render them
unnecessary for 90% of your work, and there's a 1 keystroke way to
toggle the mouse pad on and off.

SteveT

Steve Litt * http://www.troubleshooters.com/
Troubleshooting Training * Human Performance


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/20140502112342.2670238a@mydesk

Karl E. Jorgensen

unread,
May 2, 2014, 2:10:02 PM5/2/14
to
Hi

Jumping in late in the thread...

On Fri, May 02, 2014 at 11:23:42AM -0400, Steve Litt wrote:
[snip]
> Also, in every carrying case for every laptop, I carry a trusty
> Logitech M310 wireless led mouse. These mice are shaped well, have
> enough sensitivity to be "fast enough" even with LXDE, and the scroll
> wheel is stiff enough and its rotational clicks are discrete enough
> that middle clicking can be done without fear of turning. So, unless
> I'm trying to work where there's no table, I just use a regular mouse.
>
> Have you ever tried the xxxterm browser? It might be called xombrero on
> your Debian version. It's a browser made to be used with keystrokes
> reminiscent of Vim: No mouse required.

For the emacs users out there: Obviously w3m ! But for a graphical
browser: conkeror. If you're used to emacs, it should be natural.

--
Karl E. Jorgensen


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/20140502180500.GA18737@hawking

Zenaan Harkness

unread,
May 3, 2014, 12:40:01 AM5/3/14
to
On 5/2/14, Ivan Kovnatsky <seven...@gmail.com> wrote:
> On May 02, 2014 at 05:54, Zenaan Harkness <z...@freedbms.net> wrote:
>> On 5/2/14, Ivan Kovnatsky <seven...@gmail.com> wrote:
>> ...
>>
>> Unrelated, but how do you find the trackpad? I completely disabled
>> mine in BIOS, since the "textured bumps" on it make the pointer (even
>> at extreme settings) useless for fine mouse work - I could not make it
>> work in non-extremely-annoying way.
>
> Hm, I used to it. I thought you meant touchpad, which I definitely
> disabled.

Actually, yes I meant touchpad. And yes, sounds like we have both
disabled touchpad. The trackpoint is fine - in fact, it is close to as
good as it gets for fine mouse work.

It is the X220 touchpad/trackpad which is amazing in its NON-usability
(I nearly always prefer touchpad/trackpad) - because of all the little
bumps over it.

Those bumps, as I said, cause the cursor to move in a "predictably
unpredictable" way which is, to me, excruciatingly annoying and
frustrating, even way back when I got it and still had windows on
there and changed all the settings as recommended - simply not
functional I say.

So, sadly, for the first time ever, I had to disable trackpad/touchpad
functionality in BIOS to solve the problem. I really miss having a
usable touchpad.


> I do not do any complex sensitive mouse work, sometimes GIMPing, but for my
> work it suits pretty well.

I find trackpoint excellent for fine work, just not as fast to target
something across the other side of the screen (worse with two
monitors/ external/ larger monitors).

Also, it's adequate for regular GUI mouse work.

> Of course there's some cursor drifting while
> moving mouse with trackpad , that's the case.

I assume you mean trackpoint at this stage in the conversation.

Drifting happens much less, IME, on the modern Lenovo's (like the
X220), and was worse on the old A31p for example.

I solve that by moving the cursor briefly left, release, then right,
release, then repeat if necessary.

But I don't get that so much, as said, on the X220.

But I never experience that on what I call trackPAD (what I think you
call touchpad). Not because I have it disabled either - but because
drifting does not happen with trackpad/touchpad.


> But as I understood nothing can be done
> here. For this small kind of laptops, I think trackpad is pretty useful.

Trackpoint is great for certain things. See my solution above to the
drifting problem. My solution has also trained me to release the
trackpoint more frequently too, which also reduces drifting problem.

Good luck
Zenaan


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/CAOsGNSTwq6LBxXfMWQkCqdk82Ce=38zAm+-otB_=pYaru...@mail.gmail.com

Joel Rees

unread,
May 3, 2014, 1:40:02 AM5/3/14
to
That's a nice script. I think I want to try it out sometime.
 
Also, in every carrying case for every laptop, I carry a trusty
Logitech M310 wireless led mouse. These mice are shaped well, have
enough sensitivity to be "fast enough" even with LXDE, and the scroll
wheel is stiff enough and its rotational clicks are discrete enough
that middle clicking can be done without fear of turning. So, unless
I'm trying to work where there's no table, I just use a regular mouse.

Heh. I put my wallet in my front pocket, and that is usually flat enough to use an IR mouse, even standing up. No table.

> [...]
--
Joel Rees

Be careful where you see conspiracy.
Look first in your own heart.
0 new messages