Discussion:
New default setup for touchpads in X
Add Reply
Ulf Brosziewski
2017-12-05 22:59:10 UTC
Reply
Permalink
Raw Message
If you're following -current, or if you upgrade your system with the
next or a future snapshot, please note that the default setup for
touchpads in X will change.

X will select ws(4) instead of synaptics(4) as default driver. In a
configuration with ws, touchpad-specific input processing is done by
wsmouse(4). Touchpad configuration parameters are made available in
wsconsctl(4), see
https://marc.info/?l=openbsd-misc&m=150153498920367&w=2
for some hints (the wsmouse man page is not up to date yet).

Using synaptics(4) as input driver is still possible, it will require
a custom xorg.conf file. If you already have such a file - which
overrides the default -, please consider giving ws a try, and help
us by reporting problems if it doesn't work for you.
Base Pr1me
2017-12-05 23:17:43 UTC
Reply
Permalink
Raw Message
Are there plans to have a solution to halt the touchpad when typing is
occurring, similar to what syndaemon does? Otherwise, the driver works fine
for me on ThinkPad T470s.
Post by Ulf Brosziewski
If you're following -current, or if you upgrade your system with the
next or a future snapshot, please note that the default setup for
touchpads in X will change.
X will select ws(4) instead of synaptics(4) as default driver. In a
configuration with ws, touchpad-specific input processing is done by
wsmouse(4). Touchpad configuration parameters are made available in
wsconsctl(4), see
https://marc.info/?l=openbsd-misc&m=150153498920367&w=2
for some hints (the wsmouse man page is not up to date yet).
Using synaptics(4) as input driver is still possible, it will require
a custom xorg.conf file. If you already have such a file - which
overrides the default -, please consider giving ws a try, and help
us by reporting problems if it doesn't work for you.
Ulf Brosziewski
2017-12-06 00:23:28 UTC
Reply
Permalink
Raw Message
Up to now, I have only vaguely considered that, and there are
some other things pending. However, if many users will be
missing that option, my priorities might change ;-) Would
"edge areas" be an alternative for you? synaptics(4) has an
option for defining edge zones. A touch that starts there does
not trigger pointer movement, tapping, and scrolling as long as
it hasn't left the area. The input driver in wsmouse(4) has a
similar mechanism, what's missing up to now is a decent way to
configure it, but it can be done, and it might be a way to mitigate
the effects of accidental touches. Of course, whether it could
help in your case depends on your habits.
Post by Base Pr1me
Are there plans to have a solution to halt the touchpad when typing is
occurring, similar to what syndaemon does? Otherwise, the driver works fine
for me on ThinkPad T470s.
Post by Ulf Brosziewski
If you're following -current, or if you upgrade your system with the
next or a future snapshot, please note that the default setup for
touchpads in X will change.
X will select ws(4) instead of synaptics(4) as default driver. In a
configuration with ws, touchpad-specific input processing is done by
wsmouse(4). Touchpad configuration parameters are made available in
wsconsctl(4), see
https://marc.info/?l=openbsd-misc&m=150153498920367&w=2
for some hints (the wsmouse man page is not up to date yet).
Using synaptics(4) as input driver is still possible, it will require
a custom xorg.conf file. If you already have such a file - which
overrides the default -, please consider giving ws a try, and help
us by reporting problems if it doesn't work for you.
Base Pr1me
2017-12-06 00:33:25 UTC
Reply
Permalink
Raw Message
Honestly, my issues are minimal in regards to the tap-to-click activating during
typing. If I'm typing in bed or at a awkward angle exacerbates it, but it's not
a huge issue. "Edge Zones" might be just the ticket. I always found the
syndaemon a bit odd, anyway, and had to play with the timing to make it feel
like it worked correctly.

I'll keep an eye out for your future posts and report any (and then when I went
to type anomalies, the tap-to-click got me, even though I'm not at an odd angle)
anomalies. So, parenthetically, edge zones might be the ticket! :D
Post by Ulf Brosziewski
Up to now, I have only vaguely considered that, and there are
some other things pending. However, if many users will be
missing that option, my priorities might change ;-) Would
"edge areas" be an alternative for you? synaptics(4) has an
option for defining edge zones. A touch that starts there does
not trigger pointer movement, tapping, and scrolling as long as
it hasn't left the area. The input driver in wsmouse(4) has a
similar mechanism, what's missing up to now is a decent way to
configure it, but it can be done, and it might be a way to mitigate
the effects of accidental touches. Of course, whether it could
help in your case depends on your habits.
Post by Base Pr1me
Are there plans to have a solution to halt the touchpad when typing is
occurring, similar to what syndaemon does? Otherwise, the driver works fine
for me on ThinkPad T470s.
Post by Ulf Brosziewski
If you're following -current, or if you upgrade your system with the
next or a future snapshot, please note that the default setup for
touchpads in X will change.
X will select ws(4) instead of synaptics(4) as default driver. In a
configuration with ws, touchpad-specific input processing is done by
wsmouse(4). Touchpad configuration parameters are made available in
wsconsctl(4), see
https://marc.info/?l=openbsd-misc&m=150153498920367&w=2
for some hints (the wsmouse man page is not up to date yet).
Using synaptics(4) as input driver is still possible, it will require
a custom xorg.conf file. If you already have such a file - which
overrides the default -, please consider giving ws a try, and help
us by reporting problems if it doesn't work for you.
Christoph R. Murauer
2017-12-10 00:34:23 UTC
Reply
Permalink
Raw Message
Hello !

I tried the touchpad with -current #261 from Dec 8. But wsconsctl
still reports mouse.type=synaptics. Should that be ?

If it is as it should be, the touchpad worked as before (but I had not
much time to play around with it). IMHO the touchpad on this machine
is sometimes a kind of sluggish. Specially with the pinch to zoom
(ctrl and 2 finger to scale). If all works as it should, I also could
try it on a MacBook Pro the next days.

thinkpad-w541# wsconsctl | grep 'mouse'
wsconsctl: Use explicit arg to view keyboard.map.
mouse.type=synaptics
mouse.rawmode=0
mouse.scale=1266,5676,1096,4758,0,45,68
mouse.tp.tapping=1
mouse.tp.scaling=0.160
mouse.tp.swapsides=0
mouse.tp.disable=0
mouse1.type=ps2

I changed the tapping as you suggested and, I don't have a xorg.conf
in /etc. Search with wildcard to get a result.

thinkpad-w541# find / -name 'xorg.conf*'
/usr/X11R6/man/man5/xorg.conf.5
/usr/X11R6/man/man5/xorg.conf.d.5
/usr/X11R6/share/X11/xorg.conf.d
/usr/xenocara/xserver/hw/xfree86/man/xorg.conf.d.man
/usr/xenocara/xserver/hw/xfree86/man/xorg.conf.man

dmesg :

OpenBSD 6.2-current (GENERIC.MP) #261: Fri Dec 8 11:22:29 MST 2017
***@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 33938599936 (32366MB)
avail mem = 32903114752 (31378MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0x7cd2d000 (69 entries)
bios0: vendor LENOVO version "GNET81WW (2.29 )" date 11/24/2016
bios0: LENOVO 20EFS00B00
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP DBGP ECDT HPET APIC MCFG SSDT SSDT SSDT SSDT
SSDT SSDT SSDT PCCT SSDT UEFI POAT ASF! BATB FPDT UEFI DMAR
acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP2(S4) EXP3(S4)
XHCI(S3) EHC1(S3) EHC2(S3)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpiec0 at acpi0
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz, 2794.06 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,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu0: 256KB 64b/line 8-way L2 cache
acpihpet0: recalibrated TSC frequency 2793530785 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.2.4, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz, 2793.54 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,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 1, core 0, package 0
cpu2 at mainbus0: apid 2 (application processor)
cpu2: Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz, 2793.54 MHz
cpu2:
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,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 1, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz, 2793.54 MHz
cpu3:
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,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
cpu4 at mainbus0: apid 4 (application processor)
cpu4: Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz, 2793.54 MHz
cpu4:
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,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu4: 256KB 64b/line 8-way L2 cache
cpu4: smt 0, core 2, package 0
cpu5 at mainbus0: apid 5 (application processor)
cpu5: Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz, 2793.54 MHz
cpu5:
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,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu5: 256KB 64b/line 8-way L2 cache
cpu5: smt 1, core 2, package 0
cpu6 at mainbus0: apid 6 (application processor)
cpu6: Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz, 2793.54 MHz
cpu6:
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,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu6: 256KB 64b/line 8-way L2 cache
cpu6: smt 0, core 3, package 0
cpu7 at mainbus0: apid 7 (application processor)
cpu7: Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz, 2793.54 MHz
cpu7:
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,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu7: 256KB 64b/line 8-way L2 cache
cpu7: smt 1, core 3, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec00000, version 20, 24 pins
acpimcfg0 at acpi0 addr 0xf8000000, bus 0-63
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (PEG_)
acpiprt2 at acpi0: bus 2 (EXP1)
acpiprt3 at acpi0: bus 3 (EXP2)
acpiprt4 at acpi0: bus 4 (EXP3)
acpiprt5 at acpi0: bus 6 (EXP5)
acpicpu0 at acpi0: C2(***@148 ***@0x33), C1(***@1 mwait.1), PSS
acpicpu1 at acpi0: C2(***@148 ***@0x33), C1(***@1 mwait.1), PSS
acpicpu2 at acpi0: C2(***@148 ***@0x33), C1(***@1 mwait.1), PSS
acpicpu3 at acpi0: C2(***@148 ***@0x33), C1(***@1 mwait.1), PSS
acpicpu4 at acpi0: C2(***@148 ***@0x33), C1(***@1 mwait.1), PSS
acpicpu5 at acpi0: C2(***@148 ***@0x33), C1(***@1 mwait.1), PSS
acpicpu6 at acpi0: C2(***@148 ***@0x33), C1(***@1 mwait.1), PSS
acpicpu7 at acpi0: C2(***@148 ***@0x33), C1(***@1 mwait.1), PSS
acpipwrres0 at acpi0: PUBS, resource for XHCI, EHC1, EHC2
acpipwrres1 at acpi0: NVP3, resource for PEG_
acpipwrres2 at acpi0: NVP2, resource for PEG_
acpitz0 at acpi0: critical temperature is 200 degC
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
"LEN0071" at acpi0 not configured
"LEN004A" at acpi0 not configured
acpibat0 at acpi0: BAT0 model "45N1779" serial 1830 type LION oem
"SANYO"
acpiac0 at acpi0: AC unit online
acpithinkpad0 at acpi0
"PNP0C14" at acpi0 not configured
"PNP0C14" at acpi0 not configured
"PNP0C14" at acpi0 not configured
"INT340F" at acpi0 not configured
acpivideo0 at acpi0: VID_
acpivout at acpivideo0 not configured
acpivideo1 at acpi0: VID_
acpivout at acpivideo1 not configured
cpu0: Enhanced SpeedStep 2794 MHz: speeds: 2801, 2800, 2700, 2500,
2400, 2200, 2100, 1900, 1800, 1700, 1500, 1400, 1200, 1100, 900, 800
MHz
pci0 at mainbus0 bus 0
0:28:4: bridge mem address conflict 0xb8000000/0x16100000
0:28:4: bridge mem address conflict 0xd0000000/0x22000000
pchb0 at pci0 dev 0 function 0 "Intel Core 4G Host" rev 0x06
ppb0 at pci0 dev 1 function 0 "Intel Core 4G PCIE" rev 0x06: msi
pci1 at ppb0 bus 1
1:0:0: mem address conflict 0xfff80000/0x80000
vendor "NVIDIA", unknown product 0x11fc (class display subclass VGA,
rev 0xa1) at pci1 dev 0 function 0 not configured
inteldrm0 at pci0 dev 2 function 0 "Intel HD Graphics 4600" rev 0x06
drm0 at inteldrm0
inteldrm0: msi
inteldrm0: 2880x1620, 32bpp
wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1-5 added (std, vt100 emulation)
azalia0 at pci0 dev 3 function 0 "Intel Core 4G HD Audio" rev 0x06: msi
azalia0: No codecs found
xhci0 at pci0 dev 20 function 0 "Intel 8 Series xHCI" rev 0x04: msi
usb0 at xhci0: USB revision 3.0
uhub0 at usb0 configuration 1 interface 0 "Intel xHCI root hub" rev
3.00/1.00 addr 1
"Intel 8 Series MEI" rev 0x04 at pci0 dev 22 function 0 not configured
puc0 at pci0 dev 22 function 3 "Intel 8 Series KT" rev 0x04: ports: 1 com
com4 at puc0 port 0 apic 2 int 17: ns16550a, 16 byte fifo
com4: probed fifo depth: 0 bytes
em0 at pci0 dev 25 function 0 "Intel I217-LM" rev 0x04: msi, address
54:ee:75:49:9a:da
ehci0 at pci0 dev 26 function 0 "Intel 8 Series USB" rev 0x04: apic 2
int 16
usb1 at ehci0: USB revision 2.0
uhub1 at usb1 configuration 1 interface 0 "Intel EHCI root hub" rev
2.00/1.00 addr 1
azalia1 at pci0 dev 27 function 0 "Intel 8 Series HD Audio" rev 0x04: msi
azalia1: codecs: Realtek ALC292
audio0 at azalia1
ppb1 at pci0 dev 28 function 0 "Intel 8 Series PCIE" rev 0xd4: msi
pci2 at ppb1 bus 2
sdhc0 at pci2 dev 0 function 0 vendor "O2 Micro", unknown product
0x8520 rev 0x01: apic 2 int 16
sdhc0: SDHC 4.0, 208 MHz base clock
sdmmc0 at sdhc0: 8-bit, sd high-speed, mmc high-speed, dma
ppb2 at pci0 dev 28 function 1 "Intel 8 Series PCIE" rev 0xd4: msi
pci3 at ppb2 bus 3
iwm0 at pci3 dev 0 function 0 "Intel Dual Band Wireless AC 7260" rev
0xbb, msi
ppb3 at pci0 dev 28 function 2 "Intel 8 Series PCIE" rev 0xd4: msi
pci4 at ppb3 bus 4
ppb4 at pci0 dev 28 function 4 "Intel 8 Series PCIE" rev 0xd4: msi
pci5 at ppb4 bus 6
ehci1 at pci0 dev 29 function 0 "Intel 8 Series USB" rev 0x04: apic 2
int 23
usb2 at ehci1: USB revision 2.0
uhub2 at usb2 configuration 1 interface 0 "Intel EHCI root hub" rev
2.00/1.00 addr 1
pcib0 at pci0 dev 31 function 0 "Intel QM87 LPC" rev 0x04
ahci0 at pci0 dev 31 function 2 "Intel 8 Series AHCI" rev 0x04: msi,
AHCI 1.3
ahci0: port 0: 6.0Gb/s
ahci0: port 5: 1.5Gb/s
scsibus1 at ahci0: 32 targets
sd0 at scsibus1 targ 0 lun 0: <ATA, ST2000LM007-1R81, SBK2> SCSI3
0/direct fixed naa.5000c5009b9b083d
sd0: 1907729MB, 512 bytes/sector, 3907029168 sectors
cd0 at scsibus1 targ 5 lun 0: <HL-DT-ST, DVDRAM GU90N, LU20> ATAPI
5/cdrom removable
ichiic0 at pci0 dev 31 function 3 "Intel 8 Series SMBus" rev 0x04:
apic 2 int 18
iic0 at ichiic0
isa0 at pcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pms0 at pckbc0 (aux slot)
wsmouse0 at pms0 mux 0
wsmouse1 at pms0 mux 0
pms0: Synaptics clickpad, firmware 8.1, 0x1e2b1 0x943300
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
vmm0 at mainbus0: VMX/EPT
cdce0 at uhub0 port 3 configuration 1 interface 0 "ZTE,Incorporated
ZTE Wireless Ethernet Adapter" rev 2.00/52.45 addr 2
cdce0: address 36:4b:50:b7:ef:da
umass0 at uhub0 port 3 configuration 1 interface 2 "ZTE,Incorporated
ZTE Wireless Ethernet Adapter" rev 2.00/52.45 addr 2
umass0: using SCSI over Bulk-Only
scsibus2 at umass0: 2 targets, initiator 0
cd1 at scsibus2 targ 1 lun 0: <CWID, USB SCSI CD-ROM, 2.31> SCSI2
5/cdrom removable
sd1 at scsibus2 targ 1 lun 1: <ZTE, MMC Storage, 2.31> SCSI2 0/direct
removable
sd1: 29724MB, 512 bytes/sector, 60874752 sectors
ugen0 at uhub0 port 5 "Generic EMV Smartcard Reader" rev 2.01/1.20 addr 3
ugen0: setting configuration index 0 failed
ugen1 at uhub0 port 7 "Validity Sensors VFS5011 Fingerprint Reader"
rev 1.10/0.78 addr 4
umb0 at uhub0 port 10 configuration 1 interface 0 "Sierra Wireless
Inc. Sierra Wireless EM7345 4G LTE" rev 2.00/17.29 addr 5
umodem0 at uhub0 port 10 configuration 1 interface 2 "Sierra Wireless
Inc. Sierra Wireless EM7345 4G LTE" rev 2.00/17.29 addr 5
umodem0: data interface 3, has no CM over data, has break
umodem0: status change notification available
ucom0 at umodem0
ugen2 at uhub0 port 11 "Intel product 0x07dc" rev 2.00/0.01 addr 6
uvideo0 at uhub0 port 12 configuration 1 interface 0 "SunplusIT INC.
Integrated Camera" rev 2.00/0.03 addr 7
video0 at uvideo0
uhidev0 at uhub0 port 13 configuration 1 interface 0 "vendor 0x0765
product 0x5010" rev 2.00/0.00 addr 8
uhidev0: iclass 3/0
uhid0 at uhidev0: input=8, output=8, feature=0
uhub3 at uhub1 port 1 configuration 1 interface 0 "Intel Rate Matching
Hub" rev 2.00/0.04 addr 2
uhub4 at uhub2 port 1 configuration 1 interface 0 "Intel Rate Matching
Hub" rev 2.00/0.04 addr 2
vscsi0 at root
scsibus3 at vscsi0: 256 targets
softraid0 at root
scsibus4 at softraid0: 256 targets
sd2 at scsibus4 targ 1 lun 0: <OPENBSD, SR CRYPTO, 006> SCSI2 0/direct
fixed
sd2: 1907726MB, 512 bytes/sector, 3907023473 sectors
softraid0: volume sd2 is roaming, it used to be sd1, updating metadata
root on sd2a (7ce0c0ab452c63b1.a) swap on sd2b dump on sd2b
iwm0: hw rev 0x140, fw ver 16.242414.0, address cc:3d:82:52:2b:5a

EOF

Regards,

Christoph
Christoph R. Murauer
2017-12-10 16:19:04 UTC
Reply
Permalink
Raw Message
Hello Ulf !

Thanks for your answer.
I assume that your touchpad is actually running with ws, and that no
xorg ".conf" file - in /etc or in /usr/X11R6/share/X11/xorg.conf.d/ -
overrides the default ;-) If that is the case, then
"works-as-before" is a good result,

Yes, I can confirm, that it is ws. Because I had synclient settings
including tabbing in my .xsession file which had no effect after
upgrading to the last snapshot. No, there is no xorg.conf (see search
results below from my original email).

I experienced no differences compared to the synaptics driver from
before.
I had no intention to break user expectations.
I know.
Maybe you want give it a try on your MacBook, which has MT support ;-)
Yes, I wait for a new battery (I hope only the battery is died).
Just give me some days.
I'm not sure what your comparison is based on. I remember that some
reviewers were unhappy with the touchpads of the w540 series,
especially
because of the button handling. Or do you refer to the fact that
there
is no support for "smooth" scrolling? (The classical scroll-method is
event-based, that is, wheel movements on a mouse - or scroll gestures
on a touchpad - are translated into a series of button events, which
is
coarse compared to coordinate-based scrolling.)
It is not really a comparison, the experience is like, if I zoom in or
out the zoom steps are bigger. Like if you zoom - lets say in 10%
steps instead of something like 1 or 2% steps. Yes, I readed that
about the touchpad experiences but after I bought it already ;-)

I will try it with the MacBook as soon as possible and then report a
comparison about that.

Is the new ws driver also in the macppc port included ? I have no idea
which hardware is in it but maybe I have the chance to try it out on a
G4 PowerBook.

Regards,

Christoph
Post by Christoph R. Murauer
thinkpad-w541# find / -name 'xorg.conf*'
/usr/X11R6/man/man5/xorg.conf.5
/usr/X11R6/man/man5/xorg.conf.d.5
/usr/X11R6/share/X11/xorg.conf.d
/usr/xenocara/xserver/hw/xfree86/man/xorg.conf.d.man
/usr/xenocara/xserver/hw/xfree86/man/xorg.conf.man
Ulf Brosziewski
2017-12-10 17:29:10 UTC
Reply
Permalink
Raw Message
Hi Christoph,

under the hood, things are a bit different than you might
think. It's not the ws driver that is new or has changed,
it's the fact it is used in X for all pointing devices now.
The touchpad-specific input processing is done in the kernel,
by a new component of wsmouse(4).

I'm afraid you are out of luck with a Powerbook. The kernel
driver for that hardware, ams(4), offers mouse support only,
that is, the hardware emulates a mouse and that's all. No
extended functionality may be available, apart from things
that its firmware might offer in that mode (I have never
worked with it).

BTW, xorg configuration files in
/usr/X11R6/share/X11/xorg.conf.d/
aren't necessarily named "xorg.conf". The files in that
directory only need the ".conf" extension, and an old version
of 70_synaptics.conf (or an ancient 50_synaptics.conf) would
change the driver assignment.

Cheers,
Ulf
Post by Christoph R. Murauer
Hello Ulf !
Thanks for your answer.
I assume that your touchpad is actually running with ws, and that no
xorg ".conf" file - in /etc or in /usr/X11R6/share/X11/xorg.conf.d/ -
overrides the default ;-) If that is the case, then
"works-as-before" is a good result,
Yes, I can confirm, that it is ws. Because I had synclient settings
including tabbing in my .xsession file which had no effect after
upgrading to the last snapshot. No, there is no xorg.conf (see search
results below from my original email).
I experienced no differences compared to the synaptics driver from
before.
I had no intention to break user expectations.
I know.
Maybe you want give it a try on your MacBook, which has MT support ;-)
Yes, I wait for a new battery (I hope only the battery is died).
Just give me some days.
I'm not sure what your comparison is based on. I remember that some
reviewers were unhappy with the touchpads of the w540 series,
especially
because of the button handling. Or do you refer to the fact that
there
is no support for "smooth" scrolling? (The classical scroll-method is
event-based, that is, wheel movements on a mouse - or scroll gestures
on a touchpad - are translated into a series of button events, which
is
coarse compared to coordinate-based scrolling.)
It is not really a comparison, the experience is like, if I zoom in or
out the zoom steps are bigger. Like if you zoom - lets say in 10%
steps instead of something like 1 or 2% steps. Yes, I readed that
about the touchpad experiences but after I bought it already ;-)
I will try it with the MacBook as soon as possible and then report a
comparison about that.
Is the new ws driver also in the macppc port included ? I have no idea
which hardware is in it but maybe I have the chance to try it out on a
G4 PowerBook.
Regards,
Christoph
Post by Christoph R. Murauer
thinkpad-w541# find / -name 'xorg.conf*'
/usr/X11R6/man/man5/xorg.conf.5
/usr/X11R6/man/man5/xorg.conf.d.5
/usr/X11R6/share/X11/xorg.conf.d
/usr/xenocara/xserver/hw/xfree86/man/xorg.conf.d.man
/usr/xenocara/xserver/hw/xfree86/man/xorg.conf.man
Christoph R. Murauer
2017-12-10 21:43:36 UTC
Reply
Permalink
Raw Message
Hello Ulf !
I'm afraid you are out of luck with a Powerbook. ...
No problem. Just good to know.
BTW, xorg configuration files in
/usr/X11R6/share/X11/xorg.conf.d/
Yes, you are right, there was a
/usr/X11R6/share/X11/xorg.conf.d/70-synaptics.conf (- instead of _).

After removing the file and reboot the machine, the outupt of

thinkpad-w541# wsconsctl | grep 'mouse'
wsconsctl: Use explicit arg to view keyboard.map.
mouse.type=synaptics
mouse.rawmode=0
mouse.scale=1266,5676,1096,4758,0,45,68
mouse.tp.tapping=0
mouse.tp.scaling=0.160
mouse.tp.swapsides=0
mouse.tp.disable=0
mouse1.type=ps2

IMHO From my side I see now no need to compare ws to synaptics.
Tabbing after switching it on using wsconsctl mouse.tp.tapping=1,
pointer movement and 2 finger scroll (left, right, up, down, in a
circle) works for me good (quick tested using Xmonad, XTerm and
qutebrowser).

I will compare it with a fresh install on a MacBook Pro as I sayed as
soon as possible.

Pinch to zoom, only tested in qutebrowser, zooms in and out in round
23% steps but I think, that depends on the touchpad (we will see).

Maybe someone could test pinch to zoom in XFCE using the integrated
magnifier from the composting (I also try to have a look at it as soon
as possible).
Lari Rasku
2017-12-10 20:10:14 UTC
Reply
Permalink
Raw Message
Post by Ulf Brosziewski
please consider giving ws a try, and help
us by reporting problems if it doesn't work for you.
ws(4) seems to have much higher limiting friction for me when two-finger
scrolling. In synaptics(4), it was enough to just tilt my fingers to
get the page moving, whereas ws(4) requires me to perceptibly move them.
When tilting just a single finger on the touchpad, the limiting
friction feels the same - but ws(4) moves the pointer much fewer pixels.
From your reply to Christoph ("I hope you can observer a higher
precision when navigating at low speeds"), I gather this is intentional?
I guess I've just gotten too used to the synaptics scaling, the ws
behavior feels too sluggish to me.

My machine is a Thinkpad E530. Here's how the touchpad appears in dmesg:

pms0 at pckbc0 (aux slot)
wsmouse0 at pms0 mux 0
wsmouse1 at pms0 mux 0
pms0: Synaptics clickpad, firmware 8.1, 0x1e2b1 0x940300
Ulf Brosziewski
2017-12-11 21:52:54 UTC
Reply
Permalink
Raw Message
Post by Ulf Brosziewski
please consider giving ws a try, and help
us by reporting problems if it doesn't work for you.
ws(4) seems to have much higher limiting friction for me when two-finger scrolling. In synaptics(4), it was enough to just tilt my fingers to get the page moving, whereas ws(4) requires me to perceptibly move them. When tilting just a single finger on the touchpad, the limiting friction feels the
same - but ws(4) moves the pointer much fewer pixels. From your reply to Christoph ("I hope you can observer a higher precision when navigating at low speeds"), I gather this is intentional? I guess I've just gotten too used to the synaptics scaling, the ws behavior feels too sluggish to me.
Hi, thanks for the comments. The acceleration schemes and coordinate
filters are different in the ws+wsmouse setup, so it's inevitable that
the feel of it is different. Even if I could reproduce the synaptics
behaviour, I wouldn't want it. By and large, it is usable and
acceptable, but I think it has flaws - which lead to a lack of
precision, especially in short movements.

However, if it is only the base speed of the pointer that doesn't suit
you, there is a simple way to adjust it by changing the value of
wsmouse.tp.scaling
in wsconsctl(8).

Scrolling is a different thing. The new driver has actually a
comparatively high threshold before it starts scrolling, and the scroll
speed is moderate. Maybe I'll lower the threshold, that's not settled
yet.
pms0 at pckbc0 (aux slot)
wsmouse0 at pms0 mux 0
wsmouse1 at pms0 mux 0
pms0: Synaptics clickpad, firmware 8.1, 0x1e2b1 0x940300
Loading...