Re: 6.3/amd64 Thinkpad T530 touchpad problem (was ok in 6.2/amd64)

2018-04-25 Thread Jonathan Thornburg
Ulf Brosziewski wrote
> First, could you deactivate synaptics again, start X and
> capture the output of
> # wsconsctl | grep mouse
> when the touchpad has started to produce nonsense? (You must run
> that command as root or configure doas(1) for it).

Here is the output:

mouse.type=synaptics
mouse.rawmode=0
mouse.scale=1472,5470,1408,4498,0,60,85
mouse.tp.tapping=0
mouse.tp.scaling=0.182
mouse.tp.swapsides=0
mouse.tp.disable=0
mouse.tp.edges=0.0,5.0,0.0,5.0
mouse1.type=ps2


> And btw, does
> the trackpoint work normally when this happens?

Unfortunately I can't tell -- I physically removed the trackpoint
"nipple" a long time ago.

Thanks for all your efforts!
ciao,
-- 
-- "Jonathan Thornburg [remove -animal to reply]" 

   Dept of Astronomy & IUCSS, Indiana University, Bloomington, Indiana, USA
   currently visiting Max-Plack-Institute fuer Gravitationsphysik
  (Albert-Einstein-Institut), Potsdam-Golm, Germany
   "There was of course no way of knowing whether you were being watched
at any given moment.  How often, or on what system, the Thought Police
plugged in on any individual wire was guesswork.  It was even conceivable
that they watched everybody all the time."  -- George Orwell, "1984"



Re: 6.3/amd64 Thinkpad T530 touchpad problem (was ok in 6.2/amd64)

2018-04-23 Thread Ulf Brosziewski
Hi Jonathan,

would you mind to make further tests in order to help us to
identify the cause of that phenomenon?

First, could you deactivate synaptics again, start X and
capture the output of
# wsconsctl | grep mouse
when the touchpad has started to produce nonsense? (You must run
that command as root or configure doas(1) for it). And btw, does
the trackpoint work normally when this happens?


On 04/23/2018 10:14 PM, Jonathan Thornburg wrote:
> On Sun, Apr 22, 2018 at 12:48:11AM +0300, IL Ka wrote:
>> +1 for trying synaptics(4).
> [[...]]
> 
> Success!  With synaptics(4) enabled via the xorg.conf you suggested
> in , the
> touchpad works perfectly.  (I haven't experimented with multitouch
> gestures yet.)
> 
> Thanks to both of you (IL and Ulf) for pointing me to the solution!
> 
> ciao,
> 



Re: 6.3/amd64 Thinkpad T530 touchpad problem (was ok in 6.2/amd64)

2018-04-23 Thread Jonathan Thornburg
On Sun, Apr 22, 2018 at 12:48:11AM +0300, IL Ka wrote:
> +1 for trying synaptics(4).
[[...]]

Success!  With synaptics(4) enabled via the xorg.conf you suggested
in , the
touchpad works perfectly.  (I haven't experimented with multitouch
gestures yet.)

Thanks to both of you (IL and Ulf) for pointing me to the solution!

ciao,
-- 
-- "Jonathan Thornburg [remove -animal to reply]" 

   Dept of Astronomy & IUCSS, Indiana University, Bloomington, Indiana, USA
   currently visiting Max-Plack-Institute fuer Gravitationsphysik
  (Albert-Einstein-Institut), Potsdam-Golm, Germany
   "There was of course no way of knowing whether you were being watched
at any given moment.  How often, or on what system, the Thought Police
plugged in on any individual wire was guesswork.  It was even conceivable
that they watched everybody all the time."  -- George Orwell, "1984"



Re: 6.3/amd64 Thinkpad T530 touchpad problem (was ok in 6.2/amd64)

2018-04-21 Thread Ulf Brosziewski
Does it make a difference if you use synaptics(4) as touchpad
input driver?

You can activate it by adding the following entry to
/etc/xorg.conf (if the file isn't present, simply create it
with these lines):

Section "InputClass"
Identifier "wsmouse touchpad"
Driver "synaptics"
MatchIsTouchpad "on"
EndSection


On 04/21/2018 09:07 PM, Jonathan Thornburg wrote:
> In  I wrote
> | I have a Lenovo Thinkpad T530.  Everything (including the builtin
> | touchpad) was fine under 6.2/amd64, but under 6.3/amd64 there is a
> | severe problem with the builtin touchpad when running X (autoconfigured
> | with no xorg.conf; all other aspects of X operation are fine).
> | 
> | The problem is this: when I first start X the touchpad operates normally.
> | But a minute or so of use the X cursor starts jumping to the left and/or
> | top side of the screen each time I start a new finger-movement.
> | 
> | [[...]]
> 
> In , IL Ka replied:
>> Try to start ``wsmoused(8)`` and check if mouse works in console.
>> ``/etc/rc.d/wsmoused start`` and move mouse around for minute or two.
>> Does it work?
>>
>> It will help us to understand if it is a X problem or wmouse(4) problem
> 
> With wsmoused(8) running the console mouse works fine.
> 
> ciao,
> 



Re: 6.3/amd64 Thinkpad T530 touchpad problem (was ok in 6.2/amd64)

2018-04-21 Thread IL Ka
+1 for trying synaptics(4).
It uses  wsmouse "absolute mode"  (covered by wsmouse(4))
and has a lot of Options (more than ws(4) which is used by default), some
of them may help.
Check log file then, you should see "synaptics" driver there.

You can also try to stop wsmoused(8) before launching X.
Although its man page says it should coexist with X (at least when wsmouse
is used)

But if your USB mouse also has troubles, it could also be accel. issue:
You may try to play with "xinput --set-ptr-feedback " or "xset m"


Re: 6.3/amd64 Thinkpad T530 touchpad problem (was ok in 6.2/amd64)

2018-04-21 Thread Jonathan Thornburg
In  I wrote
| I have a Lenovo Thinkpad T530.  Everything (including the builtin
| touchpad) was fine under 6.2/amd64, but under 6.3/amd64 there is a
| severe problem with the builtin touchpad when running X (autoconfigured
| with no xorg.conf; all other aspects of X operation are fine).
| 
| The problem is this: when I first start X the touchpad operates normally.
| But a minute or so of use the X cursor starts jumping to the left and/or
| top side of the screen each time I start a new finger-movement.
| 
| [[...]]

In , IL Ka replied:
> Try to start ``wsmoused(8)`` and check if mouse works in console.
> ``/etc/rc.d/wsmoused start`` and move mouse around for minute or two.
> Does it work?
> 
> It will help us to understand if it is a X problem or wmouse(4) problem

With wsmoused(8) running the console mouse works fine.

ciao,
-- 
-- "Jonathan Thornburg [remove -animal to reply]" 

   Dept of Astronomy & IUCSS, Indiana University, Bloomington, Indiana, USA
   currently visiting Max-Plack-Institute fuer Gravitationsphysik
  (Albert-Einstein-Institut), Potsdam-Golm, Germany
   "There was of course no way of knowing whether you were being watched
at any given moment.  How often, or on what system, the Thought Police
plugged in on any individual wire was guesswork.  It was even conceivable
that they watched everybody all the time."  -- George Orwell, "1984"



Re: 6.3/amd64 Thinkpad T530 touchpad problem (was ok in 6.2/amd64)

2018-04-19 Thread IL Ka
I forgot to mention that you can disable extended input devices.
Ie.
$ xinput --list
Then look at list of "Virtual core XTEST pointer" children
And ``xinput --disable [id]`` everything but the first one. It _may_ help.

On Thu, Apr 19, 2018 at 2:38 PM, Jonathan Thornburg <
jth...@astro.indiana.edu> wrote:

> I have a Lenovo Thinkpad T530.  Everything (including the builtin
> touchpad) was fine under 6.2/amd64, but under 6.3/amd64 there is a
> severe problem with the builtin touchpad when running X (autoconfigured
> with no xorg.conf; all other aspects of X operation are fine).
>
> The problem is this: when I first start X the touchpad operates normally.
> But a minute or so of use the X cursor starts jumping to the left and/or
> top side of the screen each time I start a new finger-movement.
>
> That is, a normal sequence of touchpad operation is
> 1. touch finger to touchpad
> 2. drag finger to move X cursor to desired location
> 3. remove finger from touchpad
> but once this problem starts, step 2 causes the X cursor to jump to the
> left side of the screen (if the finger-drag is in a horizontal direction),
> the top side of the screen (if the finger-drag is in a vertical direction),
> or the top-left corner of the screen (if the finger-drag is in a diagonal
> direction).
>
> I see the same symptoms if ...
> * ... I boot GENERIC instead of usual GENERIC.MP
> * ... I comment out the line 'xset m 1/4' (which is the only 'xset m' line)
>   from my $HOME/.xinitrc.
> * ... I change from my usual window manager (twm, started from
> $HOME/.xinitrc),
>   to the OpenBSD default fvwm (started if there is no $HOME/.xinitrc).
> * ... I plug in a USB (optical) mouse, but continue to use the builtin
>   touchpad,
> * ... I plug in a USB (optical) mouse, and use that as a pointer device
>   instead of the builtin touchpad.  In this case mouse movements trigger
>   the X-cursor-jumping behavior: the X cursor jumps to the left side of
>   the screen (if the mouse movement is in a horizontal direction), the top
>   side of the screen (if the mouse movement is in a vertical direction),
>   or the top-left corner of the screen (if the mouse movement is in a
>   diagonal direction).
>
> Once this problem starts, the only "cure" I have found is to kill the
> X server (either 'pkill X' or Ctrl-Shift-Backspace -- the window-manager
> menu is inaccessable due to the X cursor jumping) and start a new X
> session.
> This gets me a minute or so of normal operation before the problem
> reoccurs.
>
> I am not running xenodm -- I login on the console and start (or restart)
> X via 'startx'.
>
> Below I give my dmesg (6.3/amd64), a dmesg from 6.2/amd64 on this same
> machine for comparison, and /var/log/Xorg.0.log (6.3/amd64).
>
> Have other Thinkpad users encountered this behavior?  Is there a known
> workaround?  Is there additional information I could supply to help
> diagnose the problem?  (I could run with a debugging kernel or X server
> for a while if that would help.)
>
> Thanks, ciao,
> -- "Jonathan Thornburg [remove -animal to reply]" <
> jth...@astro.indiana-zebra.edu>
>currently visiting Max-Plack-Institute fuer Gravitationsphysik
>   (Albert-Einstein-Institut), Potsdam-Golm, Germany
>
> --- begin 6.3/amd64 /var/run/dmesg.boot ---
> OpenBSD 6.3 (GENERIC.MP) #107: Sat Mar 24 14:21:59 MDT 2018
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> real mem = 16845565952 (16065MB)
> avail mem = 16327950336 (15571MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xdae9c000 (69 entries)
> bios0: vendor LENOVO version "G4ETA7WW (2.67 )" date 08/24/2016
> bios0: LENOVO 24292A9
> acpi0 at bios0: rev 2
> acpi0: sleep states S0 S3 S4 S5
> acpi0: tables DSDT FACP SLIC TCPA SSDT SSDT SSDT HPET APIC MCFG ECDT FPDT
> ASF! UEFI UEFI POAT SSDT SSDT UEFI DBG2
> acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP3(S4) XHCI(S3)
> EHC1(S3) EHC2(S3) HDEF(S4)
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpihpet0 at acpi0: 14318179 Hz
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz, 2893.80 MHz
> cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,
> CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,
> PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,
> CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,
> AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,
> FSGSBASE,SMEP,ERMS,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
> cpu0: 256KB 64b/line 8-way L2 cache
> acpihpet0: recalibrated TSC frequency 2893437769 Hz
> cpu0: smt 0, core 0, package 0
> mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
> cpu0: apic clock running at 99MHz
> cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE
> cpu1 at mainbus0: apid 2 (application processor)
> cpu1: Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz, 2893.43 MHz

Re: 6.3/amd64 Thinkpad T530 touchpad problem (was ok in 6.2/amd64)

2018-04-19 Thread IL Ka
Try to start ``wsmoused(8)`` and check if mouse works in console.
``/etc/rc.d/wsmoused start`` and move mouse around for minute or two.
Does it work?

It will help us to understand if it is a X problem or wmouse(4) problem


6.3/amd64 Thinkpad T530 touchpad problem (was ok in 6.2/amd64)

2018-04-19 Thread Jonathan Thornburg
I have a Lenovo Thinkpad T530.  Everything (including the builtin
touchpad) was fine under 6.2/amd64, but under 6.3/amd64 there is a
severe problem with the builtin touchpad when running X (autoconfigured
with no xorg.conf; all other aspects of X operation are fine).

The problem is this: when I first start X the touchpad operates normally.
But a minute or so of use the X cursor starts jumping to the left and/or
top side of the screen each time I start a new finger-movement.

That is, a normal sequence of touchpad operation is
1. touch finger to touchpad
2. drag finger to move X cursor to desired location
3. remove finger from touchpad
but once this problem starts, step 2 causes the X cursor to jump to the
left side of the screen (if the finger-drag is in a horizontal direction),
the top side of the screen (if the finger-drag is in a vertical direction),
or the top-left corner of the screen (if the finger-drag is in a diagonal
direction).

I see the same symptoms if ...
* ... I boot GENERIC instead of usual GENERIC.MP
* ... I comment out the line 'xset m 1/4' (which is the only 'xset m' line)
  from my $HOME/.xinitrc.
* ... I change from my usual window manager (twm, started from $HOME/.xinitrc),
  to the OpenBSD default fvwm (started if there is no $HOME/.xinitrc).
* ... I plug in a USB (optical) mouse, but continue to use the builtin
  touchpad,
* ... I plug in a USB (optical) mouse, and use that as a pointer device
  instead of the builtin touchpad.  In this case mouse movements trigger
  the X-cursor-jumping behavior: the X cursor jumps to the left side of
  the screen (if the mouse movement is in a horizontal direction), the top
  side of the screen (if the mouse movement is in a vertical direction),
  or the top-left corner of the screen (if the mouse movement is in a
  diagonal direction).

Once this problem starts, the only "cure" I have found is to kill the
X server (either 'pkill X' or Ctrl-Shift-Backspace -- the window-manager
menu is inaccessable due to the X cursor jumping) and start a new X session.
This gets me a minute or so of normal operation before the problem reoccurs.

I am not running xenodm -- I login on the console and start (or restart)
X via 'startx'.

Below I give my dmesg (6.3/amd64), a dmesg from 6.2/amd64 on this same
machine for comparison, and /var/log/Xorg.0.log (6.3/amd64).

Have other Thinkpad users encountered this behavior?  Is there a known
workaround?  Is there additional information I could supply to help
diagnose the problem?  (I could run with a debugging kernel or X server
for a while if that would help.)

Thanks, ciao,
-- "Jonathan Thornburg [remove -animal to reply]" 

   currently visiting Max-Plack-Institute fuer Gravitationsphysik
  (Albert-Einstein-Institut), Potsdam-Golm, Germany

--- begin 6.3/amd64 /var/run/dmesg.boot ---
OpenBSD 6.3 (GENERIC.MP) #107: Sat Mar 24 14:21:59 MDT 2018
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 16845565952 (16065MB)
avail mem = 16327950336 (15571MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xdae9c000 (69 entries)
bios0: vendor LENOVO version "G4ETA7WW (2.67 )" date 08/24/2016
bios0: LENOVO 24292A9
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SLIC TCPA SSDT SSDT SSDT HPET APIC MCFG ECDT FPDT ASF! 
UEFI UEFI POAT SSDT SSDT UEFI DBG2
acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP3(S4) XHCI(S3) EHC1(S3) 
EHC2(S3) HDEF(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz, 2893.80 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu0: 256KB 64b/line 8-way L2 cache
acpihpet0: recalibrated TSC frequency 2893437769 Hz
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz, 2893.43 MHz
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
acpimcfg0 at