Re: Virtio fix for testing
Andrew Cagney writes: > Ref: https://marc.info/?l=openbsd-tech&m=168458764424059&w=2 > https://marc.info/?l=openbsd-misc&m=168071258109433&w=2 I see you found a similar issue and even a fix, good job. I believe misc@ is a better place for such questions, so I'm cc'ing that. > Is there a way to get an updated ISO or kernel with the fix? Have you tried a snapshot? They are produced pretty regularly. The project only has resource for the releases and snapshots. So if you need a build with a back port, you are likely in the best position to do that. Thanks Greg
Re: testing 7.2-beta ( tftpd )
On Wed, Jul 27, 2022 at 6:39 PM Sven F. wrote: > Dear readers, > > I ran tftpd like this : > > route -T 10 exec /usr/sbin/tftpd -d -v -c -l 192.168.2.1 /var/tftpd > > when trying to upload , it created an empty file in /var/tftpd > > # ls -ld /var/tftpd/; ls -l /var/tftpd/ > drwxr-xr-x 2 _tftpd wheel 512 Jul 27 18:31 /var/tftpd/ > total 4 > -rw-rw-rw- 1 _tftpd wheel 0 Jul 27 18:34 board.json > > and log errors on stderr : > tftpd: 192.168.2.32: write request for 'board.json' > tftpd: tftp_wrq recv: Connection refused > > get does similar > tftpd: 192.168.2.32: recv: Connection refused > tftpd: 192.168.2.32: read request for 'foo' > > Am I missing something obvious ? > > Thank you for reading that far. > Another client program is able to download. So i guess it s expected
testing 7.2-beta ( tftpd )
Dear readers, I ran tftpd like this : route -T 10 exec /usr/sbin/tftpd -d -v -c -l 192.168.2.1 /var/tftpd when trying to upload , it created an empty file in /var/tftpd # ls -ld /var/tftpd/; ls -l /var/tftpd/ drwxr-xr-x 2 _tftpd wheel 512 Jul 27 18:31 /var/tftpd/ total 4 -rw-rw-rw- 1 _tftpd wheel 0 Jul 27 18:34 board.json and log errors on stderr : tftpd: 192.168.2.32: write request for 'board.json' tftpd: tftp_wrq recv: Connection refused get does similar tftpd: 192.168.2.32: recv: Connection refused tftpd: 192.168.2.32: read request for 'foo' Am I missing something obvious ? Thank you for reading that far.
Re: How much does battle-testing weigh?
Economics 101: doesn't matter what you say, it matters what you DO. Everyone says security is important; few actually give a shit about it. Amen brother! That's right to the point! Nick.
Re: How much does battle-testing weigh?
On 3/14/22 4:31 PM, the guy who couldn't solve a trivial problem without vi on the install media wrote: Billions of companies world wide use the Linux kernel and several of the major Linux distributions daily. It would stand to reason that that would make a lot more bugs be discovered. The OpenBSD project can have the best coding practice, the best handle on security mitigations, the best default options, but if very few companies worldwide use the system, then it's not very battle-tested. The famous old message on the website has been removed, but the "Only two remote holes in the default install, in a heck of a long time!" is maybe because "no one" is using the system in production except very few. That's a fascinating leap of (il)logic. "I found a change on the website, and it must be proof of my point!" How much does battle-testing matter? By your logic, Windows is the best, as it is most "battle tested", by probably an order of magnitude greater than all Linux installs combined. What matters is people actively looking for problems. That's not a popular activity with most projects and most OSs. It is much more rewarding to most people to add features, not to debug existing code...and thus, you end up with ... Linux and Mozilla products. Economics 101: doesn't matter what you say, it matters what you DO. Everyone says security is important; few actually give a shit about it. Nick.
Re: How much does battle-testing weigh?
On Tue, Mar 15, 2022 at 01:08:38AM +0100, i...@tutanota.com wrote: >Do you believe that OpenBSD has less attack vectors? I fail to see >that. If I install a basic Debian, just as an example, with only the >base system, there is nothing running to attack. If I install NGINX on >OpenBSD and on Debian, about equal attack vectors exist. You probably meant to write "if I install NGINX on OpenBSD and on Debian, about equal attack vectors exist in NGINX". >In this case I would perhaps prefer to use NGINX over httpd for the >exact reason mentioned, it is much more battle tested. Fantastic. Congratulations! Now put it in a chroot on OpenBSD and, assuming the Nginx team has actually created a legitimate port using the security features available in OpenBSD, you have threat mitigations at the operating system level that likely are not available in Debian.
Re: How much does battle-testing weigh?
On Mon, Mar 14, 2022 at 8:13 PM wrote: > Please see "Are all BSDs created equally. OpenBSD vs NetBSD vs FreeBSD" > https://www.youtube.com/watch?v=AvSPqo3_3vM > > How they are handled is another matter, but its just as easy as it is in > other OS's. > > Do you believe that OpenBSD has less attack vectors? I fail to see > that. That video you referenced indicates that OpenBSD has *less* attack vectors than the other BSDs, and that is stated several times in several different ways in that video. (Check out the text displayed 40 minutes, 30 seconds in, for example.) Less attack vectors is of course not the same as no attack vectors. And it's often worth understanding what the issues are (not only in the kernel, but at the hardware levels). That said, we have to live with imperfect security, so we also have to live with mitigation efforts. Thanks, -- Raul
Re: How much does battle-testing weigh?
It depends on your threat model. All else being equal, using a less known OS can even be safer. A popular OS will have many people motivated to dedicate time to find flaws and thus, will have many more known vulnerabilities plus a number of holes that are not disclosed by the reearchers. If vulnerabilities are already found, automating attacks becomes cheap. That means that you can end up being pawned even if no one was targetting you specifically. While automating attacks using known vulnerabilites is cheap, finding new vulnerabilities is expensive because it requires expertise that is rare and well paid. So if you are using some niche OS that no one knows, you are only in risk if your threat model includes motivated people with resources being focused on you. If this is not the case, it is not too hard to find a handful of OS who never had a single remote hole found in the default install since forever. Popularity aside, it pays to take your time to understand why it is harder to find new security flaws on OpenBSD than on your average OS. Understanding the concept of attack surface could be a good start. Em Mon, 2022-03-14 às 21:31 +0100, i...@tutanota.com escreveu: > Billions of companies world wide use the Linux kernel and several of > the major Linux distributions daily. It would stand to reason that > that > would make a lot more bugs be discovered. > > The OpenBSD project can have the best coding practice, the best > handle > on security mitigations, the best default options, but if very few > companies worldwide use the system, then it's not very battle-tested. > > The famous old message on the website has been removed, but the "Only > two remote holes in the default install, in a heck of a long time!" > is > maybe because "no one" is using the system in production except very > few. > > How much does battle-testing matter? > > Kind regards. >
Testing
Sent from my iPad
Re: DNS lookups on a different port for testing?
On Thu, Jan 23, 2020, Stuart Henderson wrote: > On 2020-01-22, Claus Assmann wrote: > > The functional tests for sendmail use ldns-testns as DNS server > > which provides specific test data and error behaviours. > > It runs on a port > 1024 to avoid requiring root access. > For the libbind port, to avoid the conflict with libc/asr, those two > symbols are renamed. You need to set cpp flags to make sure you're > getting the version of resolv.h from /usr/local/include *not* the one in > /usr/include. With these flags (CPP/LD): -I/usr/local/include/bind -L/usr/local/bind/libbind -lbind and a little bit more hacking of the code (only to call res_init() in the "right" place) this work! Thank you, now I can continue to use my OpenBSD machine for testing the DANE code in sm8. -- Address is valid for this mailing list only, please do not reply to it direcly, but to the list.
Re: DNS lookups on a different port for testing?
On 2020-01-22, Claus Assmann wrote: > The functional tests for sendmail use ldns-testns as DNS server > which provides specific test data and error behaviours. > It runs on a port > 1024 to avoid requiring root access. > There's code in sendmail to set the IP and port for a NS: > _res.nsaddr_list[0].sin_family = AF_INET; > _res.nsaddr_list[0].sin_addr = *ns; > _res.nsaddr_list[0].sin_port = htons(port); > _res.nscount = 1; > but this does not work (anymore) on OpenBSD -- AFAICT the > resolver implementation (asr?) has a hardcoded port (53). > Is there some way to set a different port for testing? I also tried > to link sendmail against libbind but then it fails during executtion: > > sendmail:/usr/lib/libc.so.95.0: ../sendmail/sendmail : WARNING: > symbol(__p_type_syms) size mismatch, relink your program > sendmail:/usr/lib/libc.so.95.0: ../sendmail/sendmail : WARNING: symbol(_res) > size mismatch, relink your program > fill_fd: before readcf: fd 0 not open: Bad file descriptor > > Any (simple?) suggestion to get this working on OpenBSD (just for > functional testing)? > For the libbind port, to avoid the conflict with libc/asr, those two symbols are renamed. You need to set cpp flags to make sure you're getting the version of resolv.h from /usr/local/include *not* the one in /usr/include.
Re: DNS lookups on a different port for testing?
Claus Assmann wrote: > The functional tests for sendmail use ldns-testns as DNS server > which provides specific test data and error behaviours. > It runs on a port > 1024 to avoid requiring root access. you can use a combination of pf.conf rdr-to and 127.0.0.2 etc. i.e., bind to port 5353, have pf rdr 127.0.0.2:53 to 5353. this requires root to setup, but not afterwards.
DNS lookups on a different port for testing?
The functional tests for sendmail use ldns-testns as DNS server which provides specific test data and error behaviours. It runs on a port > 1024 to avoid requiring root access. There's code in sendmail to set the IP and port for a NS: _res.nsaddr_list[0].sin_family = AF_INET; _res.nsaddr_list[0].sin_addr = *ns; _res.nsaddr_list[0].sin_port = htons(port); _res.nscount = 1; but this does not work (anymore) on OpenBSD -- AFAICT the resolver implementation (asr?) has a hardcoded port (53). Is there some way to set a different port for testing? I also tried to link sendmail against libbind but then it fails during executtion: sendmail:/usr/lib/libc.so.95.0: ../sendmail/sendmail : WARNING: symbol(__p_type_syms) size mismatch, relink your program sendmail:/usr/lib/libc.so.95.0: ../sendmail/sendmail : WARNING: symbol(_res) size mismatch, relink your program fill_fd: before readcf: fd 0 not open: Bad file descriptor Any (simple?) suggestion to get this working on OpenBSD (just for functional testing)? -- Address is valid for this mailing list only, please do not reply to it direcly, but to the list.
Re: request for testing: bootstrapping time
On Mon, Jun 03, 2019 at 10:18:38AM -0400, sven falempin wrote:
> On Mon, Jun 3, 2019 at 1:44 AM Otto Moerbeek wrote:
> >
> > Hi,
> >
> > If you ever wanted to be more involved in OpenBSD here's a chanche:
> >
> > https://marc.info/?l=openbsd-tech&m=155950103825035&w=2
> >
> > It requires setting up a test machine running a recent snapshot, so
> > that's a nice first step. Then get the sources and apply the patch,
> > build and test
> >
> > You'll find help getting src and bulding the system in the FAQ.
> >
> > Much appreciated!
> >
> > -Otto
> >
>
> Dear readers,
>
> I'd like to share some result regarding ntpd , I did not yet configure
> DNSSEC and will try that later.
> I use a local unbound, and have some issue regarding time on some devices.
>
> on 6.0 I was unable to use constraint: it was not working.
> my current production version is 6.4, and I have 'problems' similar to
> the one nicely explain above,
> I still feel like a STDERR warning would be nice for -s flag failure,
> because reading log in rcctl like management script
> when time is not set is 'incomplete'.
>
> This is an important feature to TEST. ( thank you Otto for working on ntpd )
>
> I m running a slightly modified HEAD version in the test, see __why not__
> this is a * pre test *
>
> First I stopped ntpd and changed the date , then run with -ds
>
> badblock# rcctl stop ntpd && date 20180603.00 && ntpd -s
> ntpd(ok)
> Sun Jun 3 00:00:00 EDT 2018
> ntp engine ready
> trying to resolve www.google.com
> resolve www.google.com done: 2
> trying to resolve pool.ntp.org
> resolve pool.ntp.org done: 4
> constraint request to 2607:f8b0:4020:804::2004
> constraint request to 172.217.13.196
> tls connect failed: 2607:f8b0:4020:804::2004 (www.google.com):
> connect: No route to host
> no constraint reply from 2607:f8b0:4020:804::2004 received in time,
> next query 900s
> constraint reply from 172.217.13.196: offset 31567971.561072
> reply from 206.108.0.131: offset 31567971.791870 delay 0.016370, next query
> 8s
> set local clock to Mon Jun 3 08:53:04 EDT 2019 (offset 31567971.791870s)
> reply from 154.11.146.39: offset 15783985.894667 delay
> 31567971.873626, next query 5s
> reply from 209.115.181.107: offset 15783985.890166 delay
> 31567971.885181, next query 7s
> reply from 205.206.70.2: offset 15783985.888720 delay
> 31567971.886449, next query 6s
> reply from 154.11.146.39: offset -0.000489 delay 0.082025, next query 6s
> reply from 205.206.70.2: offset -0.011286 delay 0.087997, next query 6s
> reply from 206.108.0.131: offset 0.003587 delay 0.022641, next query 8s
> reply from 209.115.181.107: offset -0.006413 delay 0.091241, next query 9s
> reply from 154.11.146.39: offset 0.013697 delay 0.110286, next query 7s
> reply from 205.206.70.2: offset -0.010733 delay 0.091208, next query 9s
> reply from 206.108.0.131: offset 0.010468 delay 0.036784, next query 9s
> reply from 209.115.181.107: offset -0.01 delay 0.096816, next query 8s
> peer 154.11.146.39 now valid
>
> as we can read here in basic scenario the constraint will force the
> setup, when everything s fine, ….everything s fine !
> Assuming you have a nicely place anchor
> Let 's do : echo 'block on egress proto {tcp,udp} from any to any port
> ntp' | pfctl -f - -a 'top'
> or echo 'block on egress proto {tcp,udp} from any to any port ntp' >>
> /etc/pf.conf && pfctl -f /etc/pf.conf in a default setup.
> Things can get more interesting. I m not sure why but I had to modify
> my /etc/hosts to force ipv4 , no matter.
> Nevertheless:
>
> badblock# ntpd -sd
> ntp engine ready
> trying to resolve www.google.com
> resolve www.google.com done: 1
> trying to resolve pool.ntp.org
> resolve pool.ntp.org done: 4
> constraint request to 172.217.13.132
> constraint reply from 172.217.13.132: offset 31568246.201761
> set local clock to Sun Jun 3 00:42:25 EDT 2018 (offset 0.00s)
>
> ^Cntp engine exiting
> Terminating
> badblock# date
> Sun Jun 3 00:42:35 EDT 2018
> badblock# ntpd -sd
> ntp engine ready
> trying to resolve www.google.com
> resolve www.google.com done: 1
> trying to resolve pool.ntp.org
> resolve pool.ntp.org done: 4
> constraint request to 172.217.13.132
> constraint reply from 172.217.13.132: offset 31568246.593501
> set local clock to Sun Jun 3 00:42:39 EDT 2018 (offset 0.00s)
> ^Cntp engine exiting
> Terminating
>
> The clock suddenly refuse to be set up correctly with the HTTP header.
> And it is logged that clock is set : set local clock to Sun Jun 3
> 00:42:39 EDT 2018 (offset 0.00s)
> wrongly.
>
> Given the above proposition, the ULTRA_VIOLENCE mode may not be working
> as the clock wont be offset by the http header.
>
> I hope this *pretest* log may help other user to test this important
> bootstrapping.
> The above result is for me a problem, and I will have to thwart this
> first ( and find time for DNSSEC setup).
>
> NB: it is possible to have a network where HTTPS
Re: request for testing: bootstrapping time
On Mon, Jun 3, 2019 at 1:44 AM Otto Moerbeek wrote:
>
> Hi,
>
> If you ever wanted to be more involved in OpenBSD here's a chanche:
>
> https://marc.info/?l=openbsd-tech&m=155950103825035&w=2
>
> It requires setting up a test machine running a recent snapshot, so
> that's a nice first step. Then get the sources and apply the patch,
> build and test
>
> You'll find help getting src and bulding the system in the FAQ.
>
> Much appreciated!
>
> -Otto
>
Dear readers,
I'd like to share some result regarding ntpd , I did not yet configure
DNSSEC and will try that later.
I use a local unbound, and have some issue regarding time on some devices.
on 6.0 I was unable to use constraint: it was not working.
my current production version is 6.4, and I have 'problems' similar to
the one nicely explain above,
I still feel like a STDERR warning would be nice for -s flag failure,
because reading log in rcctl like management script
when time is not set is 'incomplete'.
This is an important feature to TEST. ( thank you Otto for working on ntpd )
I m running a slightly modified HEAD version in the test, see __why not__
this is a * pre test *
First I stopped ntpd and changed the date , then run with -ds
badblock# rcctl stop ntpd && date 20180603.00 && ntpd -s
ntpd(ok)
Sun Jun 3 00:00:00 EDT 2018
ntp engine ready
trying to resolve www.google.com
resolve www.google.com done: 2
trying to resolve pool.ntp.org
resolve pool.ntp.org done: 4
constraint request to 2607:f8b0:4020:804::2004
constraint request to 172.217.13.196
tls connect failed: 2607:f8b0:4020:804::2004 (www.google.com):
connect: No route to host
no constraint reply from 2607:f8b0:4020:804::2004 received in time,
next query 900s
constraint reply from 172.217.13.196: offset 31567971.561072
reply from 206.108.0.131: offset 31567971.791870 delay 0.016370, next query 8s
set local clock to Mon Jun 3 08:53:04 EDT 2019 (offset 31567971.791870s)
reply from 154.11.146.39: offset 15783985.894667 delay
31567971.873626, next query 5s
reply from 209.115.181.107: offset 15783985.890166 delay
31567971.885181, next query 7s
reply from 205.206.70.2: offset 15783985.888720 delay
31567971.886449, next query 6s
reply from 154.11.146.39: offset -0.000489 delay 0.082025, next query 6s
reply from 205.206.70.2: offset -0.011286 delay 0.087997, next query 6s
reply from 206.108.0.131: offset 0.003587 delay 0.022641, next query 8s
reply from 209.115.181.107: offset -0.006413 delay 0.091241, next query 9s
reply from 154.11.146.39: offset 0.013697 delay 0.110286, next query 7s
reply from 205.206.70.2: offset -0.010733 delay 0.091208, next query 9s
reply from 206.108.0.131: offset 0.010468 delay 0.036784, next query 9s
reply from 209.115.181.107: offset -0.01 delay 0.096816, next query 8s
peer 154.11.146.39 now valid
as we can read here in basic scenario the constraint will force the
setup, when everything s fine, ….everything s fine !
Assuming you have a nicely place anchor
Let 's do : echo 'block on egress proto {tcp,udp} from any to any port
ntp' | pfctl -f - -a 'top'
or echo 'block on egress proto {tcp,udp} from any to any port ntp' >>
/etc/pf.conf && pfctl -f /etc/pf.conf in a default setup.
Things can get more interesting. I m not sure why but I had to modify
my /etc/hosts to force ipv4 , no matter.
Nevertheless:
badblock# ntpd -sd
ntp engine ready
trying to resolve www.google.com
resolve www.google.com done: 1
trying to resolve pool.ntp.org
resolve pool.ntp.org done: 4
constraint request to 172.217.13.132
constraint reply from 172.217.13.132: offset 31568246.201761
set local clock to Sun Jun 3 00:42:25 EDT 2018 (offset 0.00s)
^Cntp engine exiting
Terminating
badblock# date
Sun Jun 3 00:42:35 EDT 2018
badblock# ntpd -sd
ntp engine ready
trying to resolve www.google.com
resolve www.google.com done: 1
trying to resolve pool.ntp.org
resolve pool.ntp.org done: 4
constraint request to 172.217.13.132
constraint reply from 172.217.13.132: offset 31568246.593501
set local clock to Sun Jun 3 00:42:39 EDT 2018 (offset 0.00s)
^Cntp engine exiting
Terminating
The clock suddenly refuse to be set up correctly with the HTTP header.
And it is logged that clock is set : set local clock to Sun Jun 3
00:42:39 EDT 2018 (offset 0.00s)
wrongly.
Given the above proposition, the ULTRA_VIOLENCE mode may not be working
as the clock wont be offset by the http header.
I hope this *pretest* log may help other user to test this important
bootstrapping.
The above result is for me a problem, and I will have to thwart this
first ( and find time for DNSSEC setup).
NB: it is possible to have a network where HTTPS is possible but NTP
blocked or invalid (or hacked), and
/etc/ssl/cert.pem + a valid ip/domain ( why not constraint https://a
valid ip/ ) trust level is above the BIOS for me.
Best.
tl;dr
And by the way, restricting or having custom certificate would be a
strong feature ntpd -c /etc/ssl/restricted.pem ,
also se
request for testing: bootstrapping time
Hi, If you ever wanted to be more involved in OpenBSD here's a chanche: https://marc.info/?l=openbsd-tech&m=155950103825035&w=2 It requires setting up a test machine running a recent snapshot, so that's a nice first step. Then get the sources and apply the patch, build and test You'll find help getting src and bulding the system in the FAQ. Much appreciated! -Otto
Re: Request for testing
On Fri, Jan 04, 2019 at 06:42:18PM +0100, Otto Moerbeek wrote: > On Fri, Jan 04, 2019 at 06:31:50PM +0200, Mihai Popescu wrote: > > > > 2. Apply diff, build and install userland. > > Is Xenocara/X considered as userland? > > > > > MALLOC_OPTIONS=++ chrome > > Do one needs to compile chromium port for this? > > > > I can do some testing of application, but I am not sure if I can > > finish kernel/userland compile actions correctly. > > > > ATM you need to build the base system, but no need to build chrome if you > install it from a snap. > > But this diff will be in snaps soon, so then it amounts to installing > a snap and making sure yourt packages are up to date (as old packages > may use an older libc without the diff). > > -Otto > The diff is in snaps. You can use snaps dated later than now for testing. -Otto
Re: Request for testing
On Fri, Jan 04, 2019 at 06:31:50PM +0200, Mihai Popescu wrote: > > 2. Apply diff, build and install userland. > Is Xenocara/X considered as userland? > > > MALLOC_OPTIONS=++ chrome > Do one needs to compile chromium port for this? > > I can do some testing of application, but I am not sure if I can > finish kernel/userland compile actions correctly. > ATM you need to build the base system, but no need to build chrome if you install it from a snap. But this diff will be in snaps soon, so then it amounts to installing a snap and making sure yourt packages are up to date (as old packages may use an older libc without the diff). -Otto
Re: Request for testing
> 2. Apply diff, build and install userland. Is Xenocara/X considered as userland? > MALLOC_OPTIONS=++ chrome Do one needs to compile chromium port for this? I can do some testing of application, but I am not sure if I can finish kernel/userland compile actions correctly.
Re: Request for testing
On Fri, Jan 04, 2019 at 02:23:19PM +0100, Otto Moerbeek wrote: > I'm looking for tests that cover a variety of use-cases. So use > whatever multi-threaded applications you would normally use. Play with > the options mentioned in the test request and report your findings. > > -Otto > Sorry I didn't get back to you. Some things came up ... and out. Ate the wrong thing at a party. I will update -current and try to get something out. Pun intended. Could you actually name some applications that are right for what you need. Or explain how to get that out of ports? Thanks, Chris Bennett
Re: Request for testing
On Fri, Jan 04, 2019 at 03:52:31PM +0300, Consus wrote: > On 13:05 Fri 04 Jan, Otto Moerbeek wrote: > > On Fri, Jan 04, 2019 at 01:05:37PM +0300, Consus wrote: > > > > > On 08:17 Fri 04 Jan, Otto Moerbeek wrote: > > > > Hi, > > > > > > > > If you ever thought about getting more involved and learning a bit > > > > about buikdling a current OpenBSD, there's a call for testing at > > > > > > > > https://marc.info/?l=openbsd-tech&m=154521488707434&w=2 > > > > > > > > Testing would provide me with valuable data about performance of > > > > memory management in multi-threaded applications. > > > > > > Whay kind of performance (e.g. more/less responssive application)? Any > > > particular improvements should be looked for? Does number of CPUs > > > matter? > > > > > > > Responsiveness would be a main thing to look for. You might also have > > some other benchmark. Number of CPUs likely matters, that's one of the > > things I'm trying to find out. > > > > -Otto > > Okay, I'll test some stuff on Ryzen 1800X by the end of this week. If > you have some particular test in mind, shoot. > I'm looking for tests that cover a variety of use-cases. So use whatever multi-threaded applications you would normally use. Play with the options mentioned in the test request and report your findings. -Otto
Re: Request for testing
On 13:05 Fri 04 Jan, Otto Moerbeek wrote: > On Fri, Jan 04, 2019 at 01:05:37PM +0300, Consus wrote: > > > On 08:17 Fri 04 Jan, Otto Moerbeek wrote: > > > Hi, > > > > > > If you ever thought about getting more involved and learning a bit > > > about buikdling a current OpenBSD, there's a call for testing at > > > > > > https://marc.info/?l=openbsd-tech&m=154521488707434&w=2 > > > > > > Testing would provide me with valuable data about performance of > > > memory management in multi-threaded applications. > > > > Whay kind of performance (e.g. more/less responssive application)? Any > > particular improvements should be looked for? Does number of CPUs > > matter? > > > > Responsiveness would be a main thing to look for. You might also have > some other benchmark. Number of CPUs likely matters, that's one of the > things I'm trying to find out. > > -Otto Okay, I'll test some stuff on Ryzen 1800X by the end of this week. If you have some particular test in mind, shoot.
Re: Request for testing
On Fri, Jan 04, 2019 at 01:05:37PM +0300, Consus wrote: > On 08:17 Fri 04 Jan, Otto Moerbeek wrote: > > Hi, > > > > If you ever thought about getting more involved and learning a bit > > about buikdling a current OpenBSD, there's a call for testing at > > > > https://marc.info/?l=openbsd-tech&m=154521488707434&w=2 > > > > Testing would provide me with valuable data about performance of > > memory management in multi-threaded applications. > > Whay kind of performance (e.g. more/less responssive application)? Any > particular improvements should be looked for? Does number of CPUs > matter? > Responsiveness would be a main thing to look for. You might also have some other benchmark. Number of CPUs likely matters, that's one of the things I'm trying to find out. -Otto
Re: Request for testing
On 08:17 Fri 04 Jan, Otto Moerbeek wrote: > Hi, > > If you ever thought about getting more involved and learning a bit > about buikdling a current OpenBSD, there's a call for testing at > > https://marc.info/?l=openbsd-tech&m=154521488707434&w=2 > > Testing would provide me with valuable data about performance of > memory management in multi-threaded applications. Whay kind of performance (e.g. more/less responssive application)? Any particular improvements should be looked for? Does number of CPUs matter?
Request for testing
Hi, If you ever thought about getting more involved and learning a bit about buikdling a current OpenBSD, there's a call for testing at https://marc.info/?l=openbsd-tech&m=154521488707434&w=2 Testing would provide me with valuable data about performance of memory management in multi-threaded applications. Thanks, -Otto
call for testing: rad(8) - a rtadvd(8) replacement
During g2k18 I commited rad(8). The latest amd64 and i386 snapshots should contain it with enough features to replace rtadvd(8). If you are using rtadvd(8) I'd appreciate if you could switch to rad(8) and report back if any features are missing. The plan is to unhook rtadvd(8) from the build sooner rather than later and to ship 6.4 with rad(8) only. If you are running rtadvd(8) with out any configuration and only have rtadvd_flags=em1 the /etc/rad.conf file will be ---8<--- interface em0 ---8<--- Once that is inplace disable rtadvd and enable rad: # rcctl stop rtadvd # rcctl disable rtadvd # rcctl enable rad # rcctl start rad see man rad.conf for documentation on the config file format. Good news: it's no longer termcap based! Thanks! -- I'm not entirely sure you are real.
User-space TCP/IP testing with tap, bridge and PF
Hello list, I am developing a userspace TCP/IP stack. Most of the time on my servers I use special NICs and API to bypass the kernel. When on the go I'd like to do the same on my OpenBSD dev laptop. I chose to use tap + bridge and some PF-fu to try to make it work, but after several fruitless hours i am stumped. Here is my setup: userspace <-> tap0 <-> bridge0 <-> iwm0 TAP0 is left unconfigured (except for link0). No route is present for my userspace stack. I added the following in pf.conf to get out to the Internet: > pass out on $lan_if proto tcp from 10.1.0.1 to any nat-to ($lan_if:0) 10.1.0.1 being my userspace stack's IP. I've gone as far as having one of my packet sent to its destination address and come back to iwm0. Then, OpenBSD does the reverse translation and schlepts the packet back on the bridge. However, because of the lack of route to my userspace stack, openbsd uses the defaut route's MAC, which is not the one for my tap0 device and therefore the packet never reaches its destination through bridge0. I tried to add a static route for the userspace stack's IP but I don't seem to be able to do that (route fails between "address unreachable" and "invalid argument" when specifying either the device of the link address). Is my approach correct? If so, how get I get openbsd to use the proper MAC address on the return path? Thanks! xavier
How to disable privilege separation mode in SSHD? - for testing
Hello, What is the method to do a "UsePrivilegeSeaparation=no" on source code level? Is it the following?: sed -i 's/^int use_privsep = -1;$/int use_privsep = 0;/g' /home/user/src/usr.bin/ssh/sshd.c or am I wrong? only for testing purposes! cannot check childs. Many thanks.
Re: vmctl and 6.3/testing
On Tue, Mar 27, 2018 at 03:56:53PM -0400, sven falempin wrote: > Readers, > > I was able to setup a 6.3 openbsd inside a vmd (neat) > but i had to use '-b /bsd.rd' because '-d install63.fs' > always crashed inside the guest kernel at 'mount'. > > Now testing snapshots inside snapshots. > > Feels good man. > > -- > -- > - > Knowing is not enough; we must apply. Willing is not enough; we must do You need to remember to "set tty com0" if using install63.fs Did you do that?
vmctl and 6.3/testing
Readers, I was able to setup a 6.3 openbsd inside a vmd (neat) but i had to use '-b /bsd.rd' because '-d install63.fs' always crashed inside the guest kernel at 'mount'. Now testing snapshots inside snapshots. Feels good man. -- -- - Knowing is not enough; we must apply. Willing is not enough; we must do
Re: Testing IKEv2 with Android devices
On 2017-11-29, C. L. Martinez wrote: > On Wed, Nov 29, 2017 at 9:33 AM, Stuart Henderson > wrote: >> On 2017-11-26, C. L. Martinez wrote: >>> >>> Ok, it is seems the prolem is that iked(8) does not know how to perform >>> Diffie-Hellman group negotiation: >>> >>> https://marc.info/?l=openbsd-tech&m=151136800328145&w=2 >>> >>> Am I correct? What is the current status for Tim's fix? >> >> patrick@ has been following this rabbit hole, try his latest diff. >> > > Thanks Stuart. Are you referring to this one: > https://marc.info/?l=openbsd-tech&m=151187345915827&w=2? I think you'll need the "don't include DH transform in IKE_AUTH msgs" one as well. But basically just look for all of his recent tech@ mails about iked.
Re: Testing IKEv2 with Android devices
On Wed, Nov 29, 2017 at 9:33 AM, Stuart Henderson wrote: > On 2017-11-26, C. L. Martinez wrote: >> >> Ok, it is seems the prolem is that iked(8) does not know how to perform >> Diffie-Hellman group negotiation: >> >> https://marc.info/?l=openbsd-tech&m=151136800328145&w=2 >> >> Am I correct? What is the current status for Tim's fix? > > patrick@ has been following this rabbit hole, try his latest diff. > Thanks Stuart. Are you referring to this one: https://marc.info/?l=openbsd-tech&m=151187345915827&w=2?
Re: Testing IKEv2 with Android devices
On 2017-11-26, C. L. Martinez wrote: > > Ok, it is seems the prolem is that iked(8) does not know how to perform > Diffie-Hellman group negotiation: > > https://marc.info/?l=openbsd-tech&m=151136800328145&w=2 > > Am I correct? What is the current status for Tim's fix? patrick@ has been following this rabbit hole, try his latest diff.
Re: Testing IKEv2 with Android devices
On Sun, Nov 26, 2017 at 09:02:46PM +0100, C. L. Martinez wrote: > Hi all, > > I am testing IKEv2 for Android roadwarriors clients ... I have done a very > basic config: > > ikev2 "roadwarriors" passive esp \ > from 0.0.0.0/0 to 172.22.55.0/27 \ > peer any \ > config name-server 172.22.55.1 \ > psk "stargazer" > > Launching "iked -dvv" returns me: > > ikev2_recv: IKE_SA_INIT request from initiator 172.17.35.20:500 to > 172.17.35.9:500 policy 'roadwarriors' id 0, 652 bytes > ikev2_recv: ispi 0xe525d6e2b940fdb1 rspi 0x > ikev2_policy2id: srcid FQDN/lowlands.lab.uxdom.org length 26 > ikev2_pld_parse: header ispi 0xe525d6e2b940fdb1 rspi 0x > nextpayload SA version 0x20 exchange IKE_SA_INIT flags 0x08 msgid 0 length > 652 response 0 > ikev2_pld_payloads: payload SA nextpayload KE critical 0x00 length 244 > ikev2_pld_sa: more than one proposal specified > ikev2_pld_sa: more 2 reserved 0 length 136 proposal #1 protoid IKE spisize 0 > xforms 15 spi 0 > ikev2_pld_xform: more 3 reserved 0 length 12 type ENCR id AES_CBC > ikev2_pld_attr: attribute type KEY_LENGTH length 256 total 4 > ikev2_pld_xform: more 3 reserved 0 length 12 type ENCR id AES_CBC > ikev2_pld_attr: attribute type KEY_LENGTH length 128 total 4 > ikev2_pld_xform: more 3 reserved 0 length 8 type INTEGR id HMAC_SHA2_512_256 > ikev2_pld_xform: more 3 reserved 0 length 8 type INTEGR id HMAC_SHA2_384_192 > ikev2_pld_xform: more 3 reserved 0 length 8 type INTEGR id HMAC_SHA2_256_128 > ikev2_pld_xform: more 3 reserved 0 length 8 type INTEGR id HMAC_SHA1_96 > ikev2_pld_xform: more 3 reserved 0 length 8 type PRF id HMAC_SHA2_512 > ikev2_pld_xform: more 3 reserved 0 length 8 type PRF id HMAC_SHA2_384 > ikev2_pld_xform: more 3 reserved 0 length 8 type PRF id HMAC_SHA2_256 > ikev2_pld_xform: more 3 reserved 0 length 8 type PRF id HMAC_SHA1 > ikev2_pld_xform: more 3 reserved 0 length 8 type DH id > ikev2_pld_xform: more 3 reserved 0 length 8 type DH id ECP_384 > ikev2_pld_xform: more 3 reserved 0 length 8 type DH id ECP_256 > ikev2_pld_xform: more 3 reserved 0 length 8 type DH id MODP_2048 > ikev2_pld_xform: more 0 reserved 0 length 8 type DH id MODP_1536 > ikev2_pld_payloads: payload KE nextpayload NONCE critical 0x00 length 264 > ikev2_pld_ke: dh group reserved 0 > ikev2_pld_payloads: payload NONCE nextpayload NOTIFY critical 0x00 length 36 > ikev2_pld_payloads: payload NOTIFY nextpayload NOTIFY critical 0x00 length 28 > ikev2_pld_notify: protoid NONE spisize 0 type NAT_DETECTION_SOURCE_IP > ikev2_nat_detection: peer source 0xe525d6e2b940fdb1 0x > 172.17.35.20:500 > ikev2_pld_notify: NAT_DETECTION_SOURCE_IP detected NAT, enabling UDP > encapsulation > ikev2_pld_payloads: payload NOTIFY nextpayload NOTIFY critical 0x00 length 28 > ikev2_pld_notify: protoid NONE spisize 0 type NAT_DETECTION_DESTINATION_IP > ikev2_nat_detection: peer destination 0xe525d6e2b940fdb1 0x > 172.17.35.9:500 > ikev2_pld_payloads: payload NOTIFY nextpayload NOTIFY critical 0x00 length 16 > ikev2_pld_notify: protoid NONE spisize 0 type SIGNATURE_HASH_ALGORITHMS > ikev2_pld_notify: signature hash SHA1 (1) > ikev2_pld_notify: signature hash SHA2_256 (2) > ikev2_pld_notify: signature hash SHA2_384 (3) > ikev2_pld_notify: signature hash SHA2_512 (4) > ikev2_pld_payloads: payload NOTIFY nextpayload NONE critical 0x00 length 8 > ikev2_pld_notify: protoid NONE spisize 0 type REDIRECT_SUPPORTED > sa_state: INIT -> SA_INIT > ikev2_sa_negotiate: score 4 > sa_stateok: SA_INIT flags 0x, require 0x > sa_stateflags: 0x -> 0x0020 sa (required 0x ) > ikev2_sa_keys: SKEYSEED with 32 bytes > ikev2_sa_keys: S with 80 bytes > ikev2_prfplus: T1 with 32 bytes > ikev2_prfplus: T2 with 32 bytes > ikev2_prfplus: T3 with 32 bytes > ikev2_prfplus: T4 with 32 bytes > ikev2_prfplus: T5 with 32 bytes > ikev2_prfplus: T6 with 32 bytes > ikev2_prfplus: T7 with 32 bytes > ikev2_prfplus: Tn with 224 bytes > ikev2_sa_keys: SK_d with 32 bytes > ikev2_sa_keys: SK_ai with 32 bytes > ikev2_sa_keys: SK_ar with 32 bytes > ikev2_sa_keys: SK_ei with 32 bytes > ikev2_sa_keys: SK_er with 32 bytes > ikev2_sa_keys: SK_pi with 32 bytes > ikev2_sa_keys: SK_pr with 32 bytes > ikev2_add_proposals: length 44 > ikev2_next_payload: length 48 nextpayload KE > ikev2_next_payload: length 264 nextpayload NONCE > ikev2_next_payload: length 36 nextpayload NOTIFY > ikev2_nat_detection: local source 0xe525d6e2b940fdb1 0xc417a42f151005cb > 172.17.35.9:500 > ikev2_next_payload: length 28 nextpayload NOTIFY > ikev2_nat_detection: local destination 0xe525d6e2b940fdb1 0xc417a42f151005cb > 172.17.35.20:500 >
Testing IKEv2 with Android devices
Hi all, I am testing IKEv2 for Android roadwarriors clients ... I have done a very basic config: ikev2 "roadwarriors" passive esp \ from 0.0.0.0/0 to 172.22.55.0/27 \ peer any \ config name-server 172.22.55.1 \ psk "stargazer" Launching "iked -dvv" returns me: ikev2_recv: IKE_SA_INIT request from initiator 172.17.35.20:500 to 172.17.35.9:500 policy 'roadwarriors' id 0, 652 bytes ikev2_recv: ispi 0xe525d6e2b940fdb1 rspi 0x ikev2_policy2id: srcid FQDN/lowlands.lab.uxdom.org length 26 ikev2_pld_parse: header ispi 0xe525d6e2b940fdb1 rspi 0x nextpayload SA version 0x20 exchange IKE_SA_INIT flags 0x08 msgid 0 length 652 response 0 ikev2_pld_payloads: payload SA nextpayload KE critical 0x00 length 244 ikev2_pld_sa: more than one proposal specified ikev2_pld_sa: more 2 reserved 0 length 136 proposal #1 protoid IKE spisize 0 xforms 15 spi 0 ikev2_pld_xform: more 3 reserved 0 length 12 type ENCR id AES_CBC ikev2_pld_attr: attribute type KEY_LENGTH length 256 total 4 ikev2_pld_xform: more 3 reserved 0 length 12 type ENCR id AES_CBC ikev2_pld_attr: attribute type KEY_LENGTH length 128 total 4 ikev2_pld_xform: more 3 reserved 0 length 8 type INTEGR id HMAC_SHA2_512_256 ikev2_pld_xform: more 3 reserved 0 length 8 type INTEGR id HMAC_SHA2_384_192 ikev2_pld_xform: more 3 reserved 0 length 8 type INTEGR id HMAC_SHA2_256_128 ikev2_pld_xform: more 3 reserved 0 length 8 type INTEGR id HMAC_SHA1_96 ikev2_pld_xform: more 3 reserved 0 length 8 type PRF id HMAC_SHA2_512 ikev2_pld_xform: more 3 reserved 0 length 8 type PRF id HMAC_SHA2_384 ikev2_pld_xform: more 3 reserved 0 length 8 type PRF id HMAC_SHA2_256 ikev2_pld_xform: more 3 reserved 0 length 8 type PRF id HMAC_SHA1 ikev2_pld_xform: more 3 reserved 0 length 8 type DH id ikev2_pld_xform: more 3 reserved 0 length 8 type DH id ECP_384 ikev2_pld_xform: more 3 reserved 0 length 8 type DH id ECP_256 ikev2_pld_xform: more 3 reserved 0 length 8 type DH id MODP_2048 ikev2_pld_xform: more 0 reserved 0 length 8 type DH id MODP_1536 ikev2_pld_payloads: payload KE nextpayload NONCE critical 0x00 length 264 ikev2_pld_ke: dh group reserved 0 ikev2_pld_payloads: payload NONCE nextpayload NOTIFY critical 0x00 length 36 ikev2_pld_payloads: payload NOTIFY nextpayload NOTIFY critical 0x00 length 28 ikev2_pld_notify: protoid NONE spisize 0 type NAT_DETECTION_SOURCE_IP ikev2_nat_detection: peer source 0xe525d6e2b940fdb1 0x 172.17.35.20:500 ikev2_pld_notify: NAT_DETECTION_SOURCE_IP detected NAT, enabling UDP encapsulation ikev2_pld_payloads: payload NOTIFY nextpayload NOTIFY critical 0x00 length 28 ikev2_pld_notify: protoid NONE spisize 0 type NAT_DETECTION_DESTINATION_IP ikev2_nat_detection: peer destination 0xe525d6e2b940fdb1 0x 172.17.35.9:500 ikev2_pld_payloads: payload NOTIFY nextpayload NOTIFY critical 0x00 length 16 ikev2_pld_notify: protoid NONE spisize 0 type SIGNATURE_HASH_ALGORITHMS ikev2_pld_notify: signature hash SHA1 (1) ikev2_pld_notify: signature hash SHA2_256 (2) ikev2_pld_notify: signature hash SHA2_384 (3) ikev2_pld_notify: signature hash SHA2_512 (4) ikev2_pld_payloads: payload NOTIFY nextpayload NONE critical 0x00 length 8 ikev2_pld_notify: protoid NONE spisize 0 type REDIRECT_SUPPORTED sa_state: INIT -> SA_INIT ikev2_sa_negotiate: score 4 sa_stateok: SA_INIT flags 0x, require 0x sa_stateflags: 0x -> 0x0020 sa (required 0x ) ikev2_sa_keys: SKEYSEED with 32 bytes ikev2_sa_keys: S with 80 bytes ikev2_prfplus: T1 with 32 bytes ikev2_prfplus: T2 with 32 bytes ikev2_prfplus: T3 with 32 bytes ikev2_prfplus: T4 with 32 bytes ikev2_prfplus: T5 with 32 bytes ikev2_prfplus: T6 with 32 bytes ikev2_prfplus: T7 with 32 bytes ikev2_prfplus: Tn with 224 bytes ikev2_sa_keys: SK_d with 32 bytes ikev2_sa_keys: SK_ai with 32 bytes ikev2_sa_keys: SK_ar with 32 bytes ikev2_sa_keys: SK_ei with 32 bytes ikev2_sa_keys: SK_er with 32 bytes ikev2_sa_keys: SK_pi with 32 bytes ikev2_sa_keys: SK_pr with 32 bytes ikev2_add_proposals: length 44 ikev2_next_payload: length 48 nextpayload KE ikev2_next_payload: length 264 nextpayload NONCE ikev2_next_payload: length 36 nextpayload NOTIFY ikev2_nat_detection: local source 0xe525d6e2b940fdb1 0xc417a42f151005cb 172.17.35.9:500 ikev2_next_payload: length 28 nextpayload NOTIFY ikev2_nat_detection: local destination 0xe525d6e2b940fdb1 0xc417a42f151005cb 172.17.35.20:500 ikev2_next_payload: length 28 nextpayload CERTREQ ikev2_add_certreq: type RSA_KEY length 1 ikev2_next_payload: length 5 nextpayload NOTIFY ikev2_next_payload: length 14 nextpayload NONE ikev2_pld_parse: header ispi 0xe525d6e2b940fdb1 rspi 0xc417a42f151005cb nextpayload SA version 0x20 exchange IKE_SA_INIT flags 0x20 msgid 0 length 451 response 1 ikev2_pld_payloads: payload SA nextpayload KE critical 0x00 length 48 ikev2_pld_sa: more 0 reserved 0 length 44 proposal #1 protoid IKE spisize 0 xforms 4 spi 0 ikev2_pld_x
Re: cvs diff FAQ Ports Testing
> if I understand correctly: provide a short explanation, isn't-it?! exactly. > > yeah, the spacing around = in that file is somewhat arbitrary and > > inconsistent. i'll have to think a bit what to do there. this one patch > > doesn't really solve the problem, so i won't commit it as-is. > OK. > How can i help? on second thought: i committed your diff. this tab looked too odd. the other whitespace is somewhat inconsistent, but it isn't too bad. i'll let it be. thanks, but i don't think you can help with that.
Re: cvs diff FAQ Ports Testing
Le 11/22/17 à 19:57, Theo Buehler a écrit : > (...) > it would be more helpful if you said what you intend to do, like "remove > an extra closing parenthesis". if I understand correctly: provide a short explanation, isn't-it?! > (...) > >> Previously, i mailed other diff, who has remained unanswered. > yeah, the spacing around = in that file is somewhat arbitrary and > inconsistent. i'll have to think a bit what to do there. this one patch > doesn't really solve the problem, so i won't commit it as-is. OK. How can i help? -- ~ " Fully Basic System Distinguish Life! " ~ " Libre as a BSD " +=<<< Stephane HUC as PengouinBSD or CIOTBSD b...@stephane-huc.net
Re: cvs diff FAQ Ports Testing
> A new diff for page FAQ > Ports > Testing. thanks, i committed this one. note that the path to the file is already listed four times below, so the above info is not particularly useful :) it would be more helpful if you said what you intend to do, like "remove an extra closing parenthesis". > Index: faq/ports/testing.html > === > RCS file: /cvs/www/faq/ports/testing.html,v > retrieving revision 1.37 > diff -u -p -r1.37 testing.html > --- faq/ports/testing.html16 Oct 2017 21:21:27 - 1.37 > +++ faq/ports/testing.html22 Nov 2017 17:55:43 - > Previously, i mailed other diff, who has remained unanswered. yeah, the spacing around = in that file is somewhat arbitrary and inconsistent. i'll have to think a bit what to do there. this one patch doesn't really solve the problem, so i won't commit it as-is.
cvs diff FAQ Ports Testing
Hi, all...
A new diff for page FAQ > Ports > Testing.
Index: faq/ports/testing.html
===
RCS file: /cvs/www/faq/ports/testing.html,v
retrieving revision 1.37
diff -u -p -r1.37 testing.html
--- faq/ports/testing.html 16 Oct 2017 21:21:27 - 1.37
+++ faq/ports/testing.html 22 Nov 2017 17:55:43 -
@@ -196,7 +196,7 @@ that all files can be easily packaged up
The port should never install files outside of the fake directory
-such as into /usr/local).
+such as into /usr/local.
GNU libtool occasionally has trouble relinking libraries during the fake
Previously, i mailed other diff, who has remained unanswered.
Is correct|normal the tabulation in TT text?
(into FAQ > Ports > SpecialTopics)
Index: faq/ports/specialtopics.html
===
RCS file: /cvs/www/faq/ports/specialtopics.html,v
retrieving revision 1.71
diff -u -p -r1.71 specialtopics.html
--- faq/ports/specialtopics.html12 Oct 2017 16:44:00 - 1.71
+++ faq/ports/specialtopics.html22 Nov 2017 17:55:43 -
@@ -325,7 +325,7 @@ Make sure you read the section about tro
This script is normally run during the configure stage of ports building.
To invoke the configure script, one only has to set
-CONFIGURE_STYLE= gnu
+CONFIGURE_STYLE=gnu
which will automatically invoke ${WRKSRC}/configure.
--
~ " Fully Basic System Distinguish Life! " ~ " Libre as a BSD " +=<<<
Stephane HUC as PengouinBSD or CIOTBSD
b...@stephane-huc.net
Re: testing cabling and NIC hardware with one machine
On 10/25/17 10:20 PM, Tony Sarendal wrote: Configure the interfaces into separate rdomains. /T Yup that works. For sure I know the packets are traveling along the wire using rdomains now. But I wonder how much of the RTT on each packet is due to the kernel/driver/rdomain code now. And also due to this test platform being a virtual machine in Linux/XEN environment. The ping response I get is, across the wire, more than what I got without the rdomains: round-trip min/avg/max/std-dev = 0.415/0.530/0.890/0.165 ms, not bad but not what I'd like to see from 10GbE. A large std-dev, relatively, and not quite as low as I'd expect for 10GbE. As this test instance currently is a Xen guest, the interface is an xnf driver; the 10GbE is bridged on a Linux Xen server's device. But based on this working, I may be able to justify some hardware allocations happening so I can build a platform natively OpenBSD. Thanks, Tony, for the good tip. CP
Re: testing cabling and NIC hardware with one machine
Configure the interfaces into separate rdomains. /T 2017-10-25 21:17 GMT+02:00 Christopher Paul : > Hi Misc, > > I have been tasked with setting up a benchmark platform to test NICs and > network cables. I'd like to do this on one PC. So I want to send packets of > different protocols out of one interface and into the other, across/thru > the NICs and whatever type/lengths of cabling I am using. The problem I am > having is that if I configure two interfaces on the same server, either on > the same network or not, the kernel is smart enough to know to not need to > use the actual wire (ethernet cable) in order to transmit the packet from > one interface to the other. Which I guess I was aware of, and of course it > makes a lot of good sense for a normal situation, but in this case, is a > block on my project. > > So I'm wondering is this sort of kernel-fooling I want to do possible with > OpenBSD? Or for that matter, any OS? > > May be I need to set them up as a bridge? If I did that I could set it up > with forwarding, yeah? Something like that I guess I will try next. > > Many thanks for those of you who read this and offer any ideas && Long > Live OpenBSD, > > CP > >
testing cabling and NIC hardware with one machine
Hi Misc, I have been tasked with setting up a benchmark platform to test NICs and network cables. I'd like to do this on one PC. So I want to send packets of different protocols out of one interface and into the other, across/thru the NICs and whatever type/lengths of cabling I am using. The problem I am having is that if I configure two interfaces on the same server, either on the same network or not, the kernel is smart enough to know to not need to use the actual wire (ethernet cable) in order to transmit the packet from one interface to the other. Which I guess I was aware of, and of course it makes a lot of good sense for a normal situation, but in this case, is a block on my project. So I'm wondering is this sort of kernel-fooling I want to do possible with OpenBSD? Or for that matter, any OS? May be I need to set them up as a bridge? If I did that I could set it up with forwarding, yeah? Something like that I guess I will try next. Many thanks for those of you who read this and offer any ideas && Long Live OpenBSD, CP
Re: OpenBSD fuzzy testing
Hi there. > On Aug 23, 2017, at 3:56 AM, Infoomatic wrote: > > Hi, > As nowadays I read quite a lot of projects being fuzzy tested or > vulnerabilities detected by fuzzy testing, I am quite curious: what is the > status of OpenBSD kernel/base system concerning fuzzy testing? yes fuzzers have been used for a very long time. if you search through the commit archives you'll see that one recent example is afl which has been used on both userland and kernel. Some links: http://www.undeadly.org/cgi?action=article&sid=20150121093259 http://lcamtuf.coredump.cx/afl/ https://github.com/nccgroup/TriforceOpenBSDFuzzer other fuzzers have been used too as far as I know. More work in this space is always welcome too. > Is there a plan on using the Google fuzzer? thanks to be clear, you're asking about oss-fuzz? if yes, then someone motivated enough might be able to get it going but it looks like a good amount of work to set it all up in a docker environment, etc. I might explore... at some point... maybe. But right now I'm personally more focused on static analysis of the kernel using tools like coverity. > > regards, > infoomatic >
OpenBSD fuzzy testing
Hi, As nowadays I read quite a lot of projects being fuzzy tested or vulnerabilities detected by fuzzy testing, I am quite curious: what is the status of OpenBSD kernel/base system concerning fuzzy testing? Is there a plan on using the Google fuzzer? thanks regards, infoomatic
Re: touchpad input driver: testing needed
Hi Ulf, On Mon, Aug 07, 2017 at 10:14:20PM +0200, Ulf Brosziewski wrote: | Hi Paul, | | thanks for the feedback. | | With respect to tapping, I'm already running out of hypotheses | that can be tested without fine-grained debugging. You might | check whether pressure thresholds play a role, but I wouldn't be | too optimistic about it. You could clear them as follows: |# wsconsctl mouse.tp.param=2:0,3:0 | and see whether it helps. This command restores the defaults: |# wsconsctl mouse.tp.param=2:25,3:30 I tried playing with this too, but unfortunately it didn't help. | As to your observations concerning click-and-drag, I might have | thought of that, it concerns some basics: If you want to move | the pointer while there are two or more contacts on the touchpad, | which one should control the movement? I think that's not totally | trivial. Linux gives a simple, but somewhat problematic answer: | The "oldest" touch controls the pointer. But if a driver does | nothing else about it, this has the effect that the outcomes of | your two-finger gestures can depend on the order in which you make | the contacts. You can still observe that on some Linux laptops | when your are scrolling with two fingers, but leave one finger | simply resting on the surface. | | In your case, it's the firmware, not the driver, that does this | work, but the principle seems to be the same. But how are users | supposed to know it? It's not evident. | | The synaptics driver adds up the differences of the coordinates | when it receives multi-touch data, and moves the pointer by those | "accumulated" values. Older versions applied the method to | click-and-drag operations, newer versions to both click-and-drag | and two-finger scrolling. | | The wsmouse driver implements a different approach: when it | receives multi-touch data - up to now, from Apple or Elantech-4 | models - it assigns pointer-control to touches that are moving (if | such a touch exists). Thanks for the detailed explanation. I guess it's just another weird oddity in this machine, it has a few small other nits (otherwise it's a fine laptop). Cheers! Paul -- >[<++>-]<+++.>+++[<-->-]<.>+++[<+ +++>-]<.>++[<>-]<+.--.[-] http://www.weirdnet.nl/
Re: touchpad input driver: testing needed
Ulf Brosziewski wrote: > Hi Jeff, > > thanks for the test and the report. I'm pleased with the > result, of course. But there is a strange thing in > the wsconsctl output: The touchpad reports its vertical > but not its horizontal resolution. By itself, that's no > problem if the ratio of X and Y units is - exactly or > nearly - 1:1. However, if the ratio is much smaller or > higher, it distorts the angles in the input-output mapping, > and under certain circumstances - slightly diagonal > movements with moderate speed - it may cause sine-wave-like > cursor paths in the output. If you notice something like > that, could you inform me about it? Hmmm well... I sure haven't notice anything like that, but if I do, I'll certainly let you know. On the bright side, your driver functions better on my hardware than the synaptics one. For example, it recognizes my finger movements, scrolling, and tapping with more certainty and less force. That's a win in my book =) > Thanks again, > Ulf Sure thing; the thanks goes both ways; Jeff > On 08/06/2017 04:20 PM, J.A. Neitzel wrote: > > Hello, > > > > The outputs from 'dmesg' and 'wsconsctl | grep mouse' on my > > Dell Inspiron 5567 follow: > > > > % dmesg > > OpenBSD 6.1-current (GENERIC.MP) #34: Tue Aug 1 18:56:18 MDT 2017 > > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > real mem = 8389611520 (8000MB) > > avail mem = 8128987136 (7752MB) > > mpath0 at root > > scsibus0 at mpath0: 256 targets > > mainbus0 at root > > bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xe9ca0 (93 entries) > > bios0: vendor Dell Inc. version "1.0.2" date 09/09/2016 > > bios0: Dell Inc. Inspiron 5567 > > acpi0 at bios0: rev 2 > > acpi0: sleep states S0 S3 S4 S5 > > acpi0: tables DSDT FACP APIC FPDT FIDT MCFG HPET SSDT BOOT SSDT HPET SSDT > > UEFI SSDT LPIT SSDT SSDT DBGP DBG2 MSDM SSDT SLIC DMAR TPM2 > > acpi0: wakeup devices PXSX(S4) RP09(S4) PXSX(S4) RP10(S4) PXSX(S4) RP11(S4) > > PXSX(S4) RP12(S4) PXSX(S4) RP13(S4) PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) > > PXSX(S4) RP03(S4) [...] > > acpitimer0 at acpi0: 3579545 Hz, 24 bits > > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > > cpu0 at mainbus0: apid 0 (boot processor) > > cpu0: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz, 2712.00 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,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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT > > cpu0: 256KB 64b/line 8-way L2 cache > > cpu0: TSC frequency 271200 Hz > > cpu0: smt 0, core 0, package 0 > > mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges > > cpu0: apic clock running at 24MHz > > cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE > > cpu1 at mainbus0: apid 2 (application processor) > > cpu1: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz, 2712.00 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,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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT > > cpu1: 256KB 64b/line 8-way L2 cache > > cpu1: smt 0, core 1, package 0 > > cpu2 at mainbus0: apid 1 (application processor) > > cpu2: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz, 2712.00 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,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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT > > cpu2: 256KB 64b/line 8-way L2 cache > > cpu2: smt 1, core 0, package 0 > > cpu3 at mainbus0: apid 3 (application processor) > > cpu3: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz, 2712.00 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,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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT > > cpu3: 256KB 64b/line 8-way L2 cache > > cpu3: smt 1, core 1, package 0 > > ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 120 pins > > acpimcfg0 at acpi0 addr 0xe000, bus 0-255 > > acpihpet0 at acpi0: 2399 Hz > > acp
Re: touchpad input driver: testing needed
On 08/10/2017 01:47 AM, Ulf Brosziewski wrote: > On 08/09/2017 02:12 PM, Matthias Schmidt wrote: >> Hi, >> >> >> * Marcus MERIGHI wrote: >>> Hello, >>> >>> just as Josh I have a X220 which works fine, thanks! >>> >>> notes: two-finger-scrolling has changed; it takes a little more to >>> start scrolling; it scrolls a little slower; it stops scrolling >>> instantly when I lift my fingers (formerly, if I scrolled with a swing >>> and then released the touchpad it kept scrolling and slowed down slowly, >>> unless I tapped the touchpad). >> >> Same HW here and all works as excepted. Interestingly my touchpad keeps >> scrolling when I lift my fingers. >> > > Hi, > > are you sure that this isn't just Firefox trying to catch up > with your inputs? I may actually look like the "coasting" feature. s/I may/It may/ > > Thanks for the feedback, > Ulf > >> $ doas wsconsctl | grep 'mouse' >> wsconsctl: Use explicit arg to view keyboard.map. >> mouse.type=synaptics >> mouse.rawmode=0 >> mouse.scale=1472,5472,1408,4448,0,75,129 >> mouse.tp.tapping=0 >> mouse.tp.scaling=0.183 >> mouse.tp.swapsides=0 >> mouse.tp.disable=0 >> mouse1.type=ps2 >> >> Cheers >> >> Matthias >> >> OpenBSD 6.1-current (GENERIC.MP) #52: Tue Aug 8 23:36:00 MDT 2017 >> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP >> RTC BIOS diagnostic error 80 >> real mem = 17041059840 (16251MB) >> avail mem = 16518242304 (15753MB) >> mpath0 at root >> scsibus0 at mpath0: 256 targets >> mainbus0 at root >> bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xdae9c000 (66 entries) >> bios0: vendor LENOVO version "8DET56WW (1.26 )" date 12/01/2011 >> bios0: LENOVO 4290W1B >> acpi0 at bios0: rev 2 >> acpi0: sleep states S0 S3 S4 S5 >> acpi0: tables DSDT FACP SLIC SSDT SSDT SSDT HPET APIC MCFG ECDT ASF! TCPA >> SSDT SSDT DMAR UEFI UEFI UEFI >> acpi0: wakeup devices LID_(S3) SLPB(S3) IGBE(S4) EXP4(S4) EXP7(S4) 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) i5-2520M CPU @ 2.50GHz, 2492.28 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,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT >> cpu0: 256KB 64b/line 8-way L2 cache >> cpu0: TSC frequency 2492279720 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 1 (application processor) >> cpu1: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz, 2491.91 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,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,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) i5-2520M CPU @ 2.50GHz, 2491.91 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,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,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) i5-2520M CPU @ 2.50GHz, 2491.91 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,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT >> cpu3: 256KB 64b/line 8-way L2 cache >> cpu3: smt 1, core 1, package 0 >> ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins >> acpimcfg0 at acpi0 addr 0xf800, bus 0-63 >> acpiec0 at acpi0 >> 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 -1 (EXP4) >> acpiprt5 at acpi0: bus 13 (EXP5) >> acpiprt6 at acpi0: bus -1 (EXP7) >> acpicpu0 at acpi0: C3(350@104 io@0x415), C1(1000@1 halt), PSS >> acpicpu1 at acpi0: C3(350@104 io@0x415), C1(1000@1 halt), PSS >> acpicpu2 at acpi0: C3(350@104 io@0x415), C1(1000@1 halt), PSS >> acpicpu3 at acpi0: C3(350@104 io@0x415), C1(1000@1 halt), PSS >> acpipwrres0 at acpi0: PUBS, resource for EHC1, EHC2 >> acpitz0 at acpi0: critical temperature is 99 degC >> acpibtn0 at acpi0: LID_ >>
Re: touchpad input driver: testing needed
On 08/09/2017 02:12 PM, Matthias Schmidt wrote: > Hi, > > > * Marcus MERIGHI wrote: >> Hello, >> >> just as Josh I have a X220 which works fine, thanks! >> >> notes: two-finger-scrolling has changed; it takes a little more to >> start scrolling; it scrolls a little slower; it stops scrolling >> instantly when I lift my fingers (formerly, if I scrolled with a swing >> and then released the touchpad it kept scrolling and slowed down slowly, >> unless I tapped the touchpad). > > Same HW here and all works as excepted. Interestingly my touchpad keeps > scrolling when I lift my fingers. > Hi, are you sure that this isn't just Firefox trying to catch up with your inputs? I may actually look like the "coasting" feature. Thanks for the feedback, Ulf > $ doas wsconsctl | grep 'mouse' > wsconsctl: Use explicit arg to view keyboard.map. > mouse.type=synaptics > mouse.rawmode=0 > mouse.scale=1472,5472,1408,4448,0,75,129 > mouse.tp.tapping=0 > mouse.tp.scaling=0.183 > mouse.tp.swapsides=0 > mouse.tp.disable=0 > mouse1.type=ps2 > > Cheers > > Matthias > > OpenBSD 6.1-current (GENERIC.MP) #52: Tue Aug 8 23:36:00 MDT 2017 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > RTC BIOS diagnostic error 80 > real mem = 17041059840 (16251MB) > avail mem = 16518242304 (15753MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xdae9c000 (66 entries) > bios0: vendor LENOVO version "8DET56WW (1.26 )" date 12/01/2011 > bios0: LENOVO 4290W1B > acpi0 at bios0: rev 2 > acpi0: sleep states S0 S3 S4 S5 > acpi0: tables DSDT FACP SLIC SSDT SSDT SSDT HPET APIC MCFG ECDT ASF! TCPA > SSDT SSDT DMAR UEFI UEFI UEFI > acpi0: wakeup devices LID_(S3) SLPB(S3) IGBE(S4) EXP4(S4) EXP7(S4) 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) i5-2520M CPU @ 2.50GHz, 2492.28 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,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT > cpu0: 256KB 64b/line 8-way L2 cache > cpu0: TSC frequency 2492279720 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 1 (application processor) > cpu1: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz, 2491.91 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,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,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) i5-2520M CPU @ 2.50GHz, 2491.91 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,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,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) i5-2520M CPU @ 2.50GHz, 2491.91 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,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT > cpu3: 256KB 64b/line 8-way L2 cache > cpu3: smt 1, core 1, package 0 > ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins > acpimcfg0 at acpi0 addr 0xf800, bus 0-63 > acpiec0 at acpi0 > 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 -1 (EXP4) > acpiprt5 at acpi0: bus 13 (EXP5) > acpiprt6 at acpi0: bus -1 (EXP7) > acpicpu0 at acpi0: C3(350@104 io@0x415), C1(1000@1 halt), PSS > acpicpu1 at acpi0: C3(350@104 io@0x415), C1(1000@1 halt), PSS > acpicpu2 at acpi0: C3(350@104 io@0x415), C1(1000@1 halt), PSS > acpicpu3 at acpi0: C3(350@104 io@0x415), C1(1000@1 halt), PSS > acpipwrres0 at acpi0: PUBS, resource for EHC1, EHC2 > acpitz0 at acpi0: critical temperature is 99 degC > acpibtn0 at acpi0: LID_ > acpibtn1 at acpi0: SLPB > "PNP0303" at acpi0 not configured > "LEN0020" at acpi0 not configured > "SMO1200" at acpi0 not configured > acpibat0 at acpi0: BAT0 model "45N1029" serial
Re: touchpad input driver: testing needed
Hi,
thanks for testing and for these hints. You are not the first
one who thinks that scrolling is a bit slow. I will consider
increasing the default speed, but such a change would need some
checks because the speed is not uniform on different touchpads -
which is due to the fact that many models don't provide (reliable)
resolution values.
As to the initial delay before scrolling starts, I believe I can
do something about it - when I have time for that ;-)
There is no plan to add "coasting" to the features of the driver
("coasting" means that scrolling continues after the fingers have
been lifted). I made a somewhat sketchy implementation in a
prototype, but I have the impression that it is not very popular
and not as essential as some other things.
On 08/09/2017 01:01 PM, Marcus MERIGHI wrote:
> Hello,
>
> just as Josh I have a X220 which works fine, thanks!
>
> notes: two-finger-scrolling has changed; it takes a little more to
> start scrolling; it scrolls a little slower; it stops scrolling
> instantly when I lift my fingers (formerly, if I scrolled with a swing
> and then released the touchpad it kept scrolling and slowed down slowly,
> unless I tapped the touchpad).
>
> Former synclient settings:
>
> syndaemon -i 0.75 -t -K -d -R
> synclient TapButton1=1
>
> I like tapping, so I enabled it (mouse.tp.tapping=1).
>
> Thanks, Marcus
>
> wsconsctl:
>
> mouse.type=synaptics
> mouse.rawmode=0
> mouse.scale=1472,5472,1408,4448,0,75,129
> mouse.tp.tapping=1
> mouse.tp.scaling=0.183
> mouse.tp.swapsides=0
> mouse.tp.disable=0
> mouse1.type=ps2
>
> dmesg:
>
> OpenBSD 6.1-current (GENERIC.MP) #49: Mon Aug 7 22:06:26 MDT 2017
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> RTC BIOS diagnostic error 80
> real mem = 4156157952 (3963MB)
> avail mem = 4023840768 (3837MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xdae9c000 (64 entries)
> bios0: vendor LENOVO version "8DET73WW (1.43 )" date 10/12/2016
> bios0: LENOVO 4290N49
> acpi0 at bios0: rev 2
> acpi0: sleep states S0 S3 S4 S5
> acpi0: tables DSDT FACP SLIC SSDT SSDT SSDT HPET APIC MCFG ECDT ASF! TCPA
> SSDT SSDT DMAR UEFI UEFI UEFI
> acpi0: wakeup devices LID_(S3) SLPB(S3) IGBE(S4) EXP4(S4) EXP7(S4) 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-2620M CPU @ 2.70GHz, 2691.66 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,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
> cpu0: 256KB 64b/line 8-way L2 cache
> cpu0: TSC frequency 2691663210 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 1 (application processor)
> cpu1: Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz, 2691.26 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,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,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-2620M CPU @ 2.70GHz, 2691.25 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,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,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-2620M CPU @ 2.70GHz, 2691.26 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,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
> cpu3: 256KB 64b/line 8-way L2 cache
> cpu3: smt 1, core 1, package 0
> ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
> acpimcfg0 at acpi0 addr 0xf800, bus 0-63
> acpiec0 at acpi0
> acpip
Re: What about some automated testing for X programs? Re: Libreoffice calc crash
> As of today, what package testing is automated by anyone? None. So you can be first to do it...
Re: touchpad input driver: testing needed
open...@xosc.org (Matthias Schmidt), 2017.08.09 (Wed) 14:12 (CEST): > * Marcus MERIGHI wrote: > > notes: two-finger-scrolling has changed; it takes a little more to > > start scrolling; it scrolls a little slower; it stops scrolling > > instantly when I lift my fingers (formerly, if I scrolled with a swing > > and then released the touchpad it kept scrolling and slowed down slowly, > > unless I tapped the touchpad). > > Same HW here and all works as excepted. Interestingly my touchpad keeps > scrolling when I lift my fingers. Thanks for sharing! I've compared your wsconsctl/dmesg to mine and I see no difference appart from mouse.tp.tapping. I set it to 0 but to no avail. I use cwm(1) as window manager and test scrolling with iridium and firefox on simple but lengthy web pages. My attempts on finding reasons for the different behaviour below. Thanks, Marcus $ xinput --test /dev/wsmouse0 button press 5 # two-finger scroll down button release 5 button press 4 # two-finger scroll up button release 4 $ xset q Keyboard Control: auto repeat: onkey click percent: 0LED mask: XKB indicators: 00: Caps Lock: off01: Num Lock:off02: Scroll Lock: off 03: Shift Lock: off04: Group 2: off05: Mouse Keys: off auto repeat delay: 660repeat rate: 25 auto repeating keys: 00fedbbf fadfffdfe5ef bell percent: 50bell pitch: 400bell duration: 100 Pointer Control: acceleration: 2/1threshold: 0 Screen Saver: prefer blanking: yesallow exposures: yes timeout: 0cycle: 600 Colors: default colormap: 0x20BlackPixel: 0x0WhitePixel: 0xff Font Path: /usr/local/share/fonts/terminus/,/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/TTF/,/usr/X11R6/lib/X11/fonts/OTF/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/100dpi/,/usr/X11R6/lib/X11/fonts/75dpi/,built-ins DPMS (Energy Star): Standby: 20Suspend: 60Off: 120 DPMS is Enabled Monitor is On Font cache: Server does not have the FontCache Extension $ cat /etc/xorg.conf Section "InputClass" Identifier "wsmouse touchpad" Driver "ws" MatchIsTouchpad "on" EndSection $ cat /var/log/Xorg.0.log [ 59823.438] (WW) checkDevMem: failed to open /dev/xf86 and /dev/mem (Operation not permitted) Check that you have set 'machdep.allowaperture=1' in /etc/sysctl.conf and reboot your machine refer to xf86(4) for details [ 59823.438]linear framebuffer access unavailable [ 59823.445] (--) Using wscons driver on /dev/ttyC4 [ 59823.454] X.Org X Server 1.18.4 Release Date: 2016-07-19 [ 59823.454] X Protocol Version 11, Revision 0 [ 59823.454] Build Operating System: OpenBSD 6.1 amd64 [ 59823.454] Current Operating System: OpenBSD dax.tor.at 6.1 GENERIC.MP#49 amd64 [ 59823.454] Build Date: 07 August 2017 10:22:24PM [ 59823.454] [ 59823.454] Current version of pixman: 0.34.0 [ 59823.454]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 59823.454] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 59823.454] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Aug 9 12:53:22 2017 [ 59823.454] (==) Using config file: "/etc/xorg.conf" [ 59823.454] (==) Using system config directory "/usr/X11R6/share/X11/xorg.conf.d" [ 59823.454] (==) No Layout section. Using the first Screen section. [ 59823.454] (==) No screen section available. Using defaults. [ 59823.454] (**) |-->Screen "Default Screen Section" (0) [ 59823.454] (**) | |-->Monitor "" [ 59823.454] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 59823.454] (==) Disabling SIGIO handlers for input devices [ 59823.454] (==) Automatically adding devices [ 59823.454] (==) Automatically enabling devices [ 59823.454] (==) Not automatically adding GPU devices [ 59823.454] (==) Max clients allowed: 256, resource mask: 0x1f [ 59823.455] (==) FontPath set to: /usr/X11R6/lib/X11/fonts/misc/, /usr/X11R6/lib/X11/fonts/TTF/, /usr/X11R6/lib/X11/fonts/OTF/, /usr/X11R6/lib/X11/fonts/Type1/, /usr/X11R6/lib/X11/fonts/100dpi/, /usr/X11R6/lib/X11/fonts/75dpi/ [ 59823.455] (==) ModulePath set to "/usr/X11R6/lib/modules" [ 59823.455] (II) The server relies on wscons to provide the list of input devices. If no devices become available, reconfigure wscons or disable AutoAddDevices. [ 59823.455] (II) Loader magic: 0x14e3e0639000 [ 59823.455] (II) Module ABI versions: [ 59823.455]X.Org ANSI C Emulation: 0.4 [ 59823.455]X.Org Video Driver: 20.0 [ 59823.455]X.Org XInput driver : 22.1 [ 59823.455]
Re: touchpad input driver: testing needed
Hi, * Marcus MERIGHI wrote: > Hello, > > just as Josh I have a X220 which works fine, thanks! > > notes: two-finger-scrolling has changed; it takes a little more to > start scrolling; it scrolls a little slower; it stops scrolling > instantly when I lift my fingers (formerly, if I scrolled with a swing > and then released the touchpad it kept scrolling and slowed down slowly, > unless I tapped the touchpad). Same HW here and all works as excepted. Interestingly my touchpad keeps scrolling when I lift my fingers. $ doas wsconsctl | grep 'mouse' wsconsctl: Use explicit arg to view keyboard.map. mouse.type=synaptics mouse.rawmode=0 mouse.scale=1472,5472,1408,4448,0,75,129 mouse.tp.tapping=0 mouse.tp.scaling=0.183 mouse.tp.swapsides=0 mouse.tp.disable=0 mouse1.type=ps2 Cheers Matthias OpenBSD 6.1-current (GENERIC.MP) #52: Tue Aug 8 23:36:00 MDT 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP RTC BIOS diagnostic error 80 real mem = 17041059840 (16251MB) avail mem = 16518242304 (15753MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xdae9c000 (66 entries) bios0: vendor LENOVO version "8DET56WW (1.26 )" date 12/01/2011 bios0: LENOVO 4290W1B acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SLIC SSDT SSDT SSDT HPET APIC MCFG ECDT ASF! TCPA SSDT SSDT DMAR UEFI UEFI UEFI acpi0: wakeup devices LID_(S3) SLPB(S3) IGBE(S4) EXP4(S4) EXP7(S4) 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) i5-2520M CPU @ 2.50GHz, 2492.28 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,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT cpu0: 256KB 64b/line 8-way L2 cache cpu0: TSC frequency 2492279720 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 1 (application processor) cpu1: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz, 2491.91 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,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,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) i5-2520M CPU @ 2.50GHz, 2491.91 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,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,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) i5-2520M CPU @ 2.50GHz, 2491.91 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,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpiec0 at acpi0 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 -1 (EXP4) acpiprt5 at acpi0: bus 13 (EXP5) acpiprt6 at acpi0: bus -1 (EXP7) acpicpu0 at acpi0: C3(350@104 io@0x415), C1(1000@1 halt), PSS acpicpu1 at acpi0: C3(350@104 io@0x415), C1(1000@1 halt), PSS acpicpu2 at acpi0: C3(350@104 io@0x415), C1(1000@1 halt), PSS acpicpu3 at acpi0: C3(350@104 io@0x415), C1(1000@1 halt), PSS acpipwrres0 at acpi0: PUBS, resource for EHC1, EHC2 acpitz0 at acpi0: critical temperature is 99 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB "PNP0303" at acpi0 not configured "LEN0020" at acpi0 not configured "SMO1200" at acpi0 not configured acpibat0 at acpi0: BAT0 model "45N1029" serial76 type LION oem "LGC" acpiac0 at acpi0: AC unit online acpithinkpad0 at acpi0 "PNP0C14" at acpi0 not configured "PNP0C14" at acpi0 not configured acpidock0 at acpi0: GDCK not docked (0) acpivideo0 at acpi0: VID_ acpivout at acpivideo0 not configured acpivideo1 at acpi0: VID_ cpu0: Enhanced SpeedStep 2492 MHz: speeds: 2501, 2500, 2200, 2000, 1800, 1600, 1400, 1200, 1000, 800 MHz pci0 at mainbus0 bu
Re: touchpad input driver: testing needed
Hello, just as Josh I have a X220 which works fine, thanks! notes: two-finger-scrolling has changed; it takes a little more to start scrolling; it scrolls a little slower; it stops scrolling instantly when I lift my fingers (formerly, if I scrolled with a swing and then released the touchpad it kept scrolling and slowed down slowly, unless I tapped the touchpad). Former synclient settings: syndaemon -i 0.75 -t -K -d -R synclient TapButton1=1 I like tapping, so I enabled it (mouse.tp.tapping=1). Thanks, Marcus wsconsctl: mouse.type=synaptics mouse.rawmode=0 mouse.scale=1472,5472,1408,4448,0,75,129 mouse.tp.tapping=1 mouse.tp.scaling=0.183 mouse.tp.swapsides=0 mouse.tp.disable=0 mouse1.type=ps2 dmesg: OpenBSD 6.1-current (GENERIC.MP) #49: Mon Aug 7 22:06:26 MDT 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP RTC BIOS diagnostic error 80 real mem = 4156157952 (3963MB) avail mem = 4023840768 (3837MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xdae9c000 (64 entries) bios0: vendor LENOVO version "8DET73WW (1.43 )" date 10/12/2016 bios0: LENOVO 4290N49 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SLIC SSDT SSDT SSDT HPET APIC MCFG ECDT ASF! TCPA SSDT SSDT DMAR UEFI UEFI UEFI acpi0: wakeup devices LID_(S3) SLPB(S3) IGBE(S4) EXP4(S4) EXP7(S4) 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-2620M CPU @ 2.70GHz, 2691.66 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,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT cpu0: 256KB 64b/line 8-way L2 cache cpu0: TSC frequency 2691663210 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 1 (application processor) cpu1: Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz, 2691.26 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,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,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-2620M CPU @ 2.70GHz, 2691.25 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,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,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-2620M CPU @ 2.70GHz, 2691.26 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,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpiec0 at acpi0 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 -1 (EXP4) acpiprt5 at acpi0: bus 13 (EXP5) acpiprt6 at acpi0: bus 14 (EXP7) acpicpu0 at acpi0: C3(200@109 io@0x416), C2(500@80 io@0x414), C1(1000@1 halt), PSS acpicpu1 at acpi0: C3(200@109 io@0x416), C2(500@80 io@0x414), C1(1000@1 halt), PSS acpicpu2 at acpi0: C3(200@109 io@0x416), C2(500@80 io@0x414), C1(1000@1 halt), PSS acpicpu3 at acpi0: C3(200@109 io@0x416), C2(500@80 io@0x414), C1(1000@1 halt), PSS acpipwrres0 at acpi0: PUBS, resource for EHC1, EHC2 acpitz0 at acpi0: critical temperature is 99 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB "PNP0303" at acpi0 not configured "LEN0020" at acpi0 not configured acpibat0 at acpi0: BAT0 model "45N1172" serial 13541 type LION oem "SANYO" acpiac0 at acpi0: AC unit offline acpithinkpad0 at acpi0 "PNP0C14" at acpi0 not configured "PNP0C14" at acpi0 not configured acpidock0 at acpi0: GDCK not docked (0) acpivideo0 at acpi0: VID_ acpivout at acpivideo0 not configured acpivideo1 at acpi0: VID_ cpu0: Enhanced SpeedStep 2691 MHz: speeds: 2701, 2700, 2400, 2200, 2000, 1800, 1600, 1400, 1200, 1000, 800 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function
What about some automated testing for X programs? Re: Libreoffice calc crash
It would be worthwhile that someone set up a testing environment that automatically downloads and installs the latest OpenBSD and package versions, and runs these standard tasks through standard programs, as a way for users to be more spared from being the first to discover these bugs (and with the associated latency of taking a couple of days for someone to debug it, I guess normally this means the user will have no given-program for a couple of days). Webdriver provides an API to operate a web browser, http://webdriver.io/api.html . I wonder what API is out there to operate X in a similar fashion. Such a testing suite could send automated emails to bugs@ or misc@ . I know failed builds are detected and reported in this way automatically today using, what's the name, the.. laundry build bot, which sends emails with the list of packages that don't build on a given architecture. As of today, what package testing is automated by anyone? >> I'm running -current snapshot dated Thu Aug 3 12:12:07 MDT 2017 with >> libreoffice-5.2.7.2p5v0 and have been doing some heavy work in Calc for the >> last hour without any issues. >> > > Good to know it's seems ok on next snapshot. (I'm on -stable ont this > machine). > >> What exactly you mean by "write changes" and "validate"; just typing values >> in a cell and pressing Enter to finish your entry? Does it happen on a >> blank spreadsheet? > > Just typing values in a cell ans finish entry, yes. > > It doesn't happen in blank spreadsheet, only when I modify a cell. > >> Do you have the user account set to the "staff" class, or somehow assigning >> it a high datasize limit in login.conf? > > Yes, I run libreoffice with this user. > > -- > thuban
Re: touchpad input driver: testing needed
Hi, unfortunately, the input driver won't work in this configuration, but I hope we can change that soon ;-) On 08/07/2017 09:16 PM, Michele Curti wrote: > On Mon, Jul 31, 2017 at 11:02:28PM +0200, Ulf Brosziewski wrote: >> >> If you have a new snapshot (from July 27 or later) on a laptop with a >> Synaptics, Apple, Alps, or Elantech-4 touchpad, you could help with >> tests, more tests, and tests. In order to activate the driver, add the > > Hi, > I'm using an August 3 snapshot on an asus x205ta where the touchpad > never worked really well. It's an elantech touchpad detected as HID > over I2C bus, through the ims driver. > > Partial dmesg: > dwiic4 at acpi0: I2C4 addr 0x9092c000/0x1000 irq 35 > iic3 at dwiic4 > ihidev1 at iic3 addr 0x15 irq 72, vendor 0x4f3 product 0x401, ELAN0100 > ihidev1: 93 report ids > ims0 at ihidev1 reportid 1: 2 buttons, Z dir > wsmouse0 at ims0 mux 0 > hid at ihidev1 reportid 11 not configured > hid at ihidev1 reportid 12 not configured > hid at ihidev1 reportid 13 not configured > hid at ihidev1 reportid 93 not configured > "ELAN0100" at acpi0 not configured > "INTCFD9" at acpi0 not configured > > It's a a version 4 touchpad? Will tests on this hardware be of any > help? > > Regargs, > Michele > > > > Full dmesg: > > OpenBSD 6.1-current (GENERIC.MP) #44: Thu Aug 3 12:12:07 MDT 2017 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > RTC BIOS diagnostic error 3f > real mem = 2056572928 (1961MB) > avail mem = 1987952640 (1895MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.7 @ 0x7c31a010 (16 entries) > bios0: vendor American Megatrends Inc. version "X205TA.212" date 09/04/2015 > bios0: ASUSTeK COMPUTER INC. X205TA > acpi0 at bios0: rev 2 > acpi0: sleep states S0 S5 > acpi0: tables DSDT FACP TCPA UEFI OEM0 DBG2 HPET LPIT APIC MCFG SSDT SSDT > SSDT SSDT FPDT SSDT SSDT SSDT SSDT TPM2 BGRT CSRT MSDM > acpi0: wakeup devices WLAN(S0) > acpihpet0 at acpi0: 14318179 Hz > acpimadt0 at acpi0 addr 0xfee0 > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: Intel(R) Atom(TM) CPU Z3735F @ 1.33GHz, 1333.58 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,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT > cpu0: 1MB 64b/line 16-way L2 cache > cpu0: TSC frequency 1333579040 Hz > cpu0: smt 0, core 0, package 0 > mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges > cpu0: apic clock running at 83MHz > cpu0: mwait min=64, max=64, C-substates=0.2.0.0.0.0.3.3, IBE > cpu1 at mainbus0: apid 2 (application processor) > cpu1: Intel(R) Atom(TM) CPU Z3735F @ 1.33GHz, 1333.34 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,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT > cpu1: 1MB 64b/line 16-way L2 cache > cpu1: smt 0, core 1, package 0 > cpu2 at mainbus0: apid 4 (application processor) > cpu2: Intel(R) Atom(TM) CPU Z3735F @ 1.33GHz, 1333.34 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,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT > cpu2: 1MB 64b/line 16-way L2 cache > cpu2: smt 0, core 2, package 0 > cpu3 at mainbus0: apid 6 (application processor) > cpu3: Intel(R) Atom(TM) CPU Z3735F @ 1.33GHz, 1333.34 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,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT > cpu3: 1MB 64b/line 16-way L2 cache > cpu3: smt 0, core 3, package 0 > ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 87 pins > acpimcfg0 at acpi0 addr 0xe000, bus 0-255 > acpiprt0 at acpi0: bus 0 (PCI0) > acpiec0 at acpi0: not present > acpicpu0 at acpi0 > C3: state 7: substate 4 >= num 3: C2(10@500 mwait.1@0x51), C1(1000@1 > mwait.1), PSS > acpicpu1 at acpi0 > C3: state 7: substate 4 >= num 3: C2(10@500 mwait.1@0x51), C1(1000@1 > mwait.1), PSS > acpicpu2 at acpi0 > C3: state 7: substate 4 >= num 3: C2(10@500 mwait.1@0x51), C1(1000@1 > mwait.1), PSS > acpicpu3 at acpi0 > C3: state 7: substate 4 >= num 3: C2(10@500 mwait.1@0x51), C1(1000@1 > mwait.1), PSS > acpipwrres0 at acpi0: PLPE > acpipwrres1 at acpi0: USBC, resource for XHC1, EHC1, OTG1 > acpipwrres2 at acpi0: CLK0, resource for CAM1 > acpipwrres3 at acpi0: CLK1, resource for CAM0 > acpipwrres4 at a
Re: touchpad input driver: testing needed
Hi Paul, thanks for the feedback. With respect to tapping, I'm already running out of hypotheses that can be tested without fine-grained debugging. You might check whether pressure thresholds play a role, but I wouldn't be too optimistic about it. You could clear them as follows: # wsconsctl mouse.tp.param=2:0,3:0 and see whether it helps. This command restores the defaults: # wsconsctl mouse.tp.param=2:25,3:30 As to your observations concerning click-and-drag, I might have thought of that, it concerns some basics: If you want to move the pointer while there are two or more contacts on the touchpad, which one should control the movement? I think that's not totally trivial. Linux gives a simple, but somewhat problematic answer: The "oldest" touch controls the pointer. But if a driver does nothing else about it, this has the effect that the outcomes of your two-finger gestures can depend on the order in which you make the contacts. You can still observe that on some Linux laptops when your are scrolling with two fingers, but leave one finger simply resting on the surface. In your case, it's the firmware, not the driver, that does this work, but the principle seems to be the same. But how are users supposed to know it? It's not evident. The synaptics driver adds up the differences of the coordinates when it receives multi-touch data, and moves the pointer by those "accumulated" values. Older versions applied the method to click-and-drag operations, newer versions to both click-and-drag and two-finger scrolling. The wsmouse driver implements a different approach: when it receives multi-touch data - up to now, from Apple or Elantech-4 models - it assigns pointer-control to touches that are moving (if such a touch exists). Regards, Ulf On 08/07/2017 09:48 AM, Paul de Weerd wrote: > On Mon, Aug 07, 2017 at 01:13:22AM +0200, Ulf Brosziewski wrote: > | On 08/05/2017 11:10 PM, Paul de Weerd wrote: > | > Hi Ulf, > | > > | > On Fri, Aug 04, 2017 at 11:26:12PM +0200, Ulf Brosziewski wrote: > | > | Hi Paul, > | > | > | > | thanks for your help. Does tapping work when you use > | > | the synaptics driver? > | > > | > Nope, it doesn't. > | > > | > | which probably means there is either something happening that > | our hardware driver doesn't cover, or there is a hardware/firmware > | bug. Anyhow, it's strange because the drivers only need very > | basic data to identify a tap: the start of a contact, its > | end, and the duration. Have you checked - with the synaptics > | driver - whether a higher tap timeout helps? If not, would you > | mind to make a short test? Could you increase the tap timeout > | to a very high value, say, two seconds, and test whether a tap > | works (with a slight delay)? For the wsmouse-internal driver, > | the following command will set a two-second timeout: > | # wsconsctl mouse.tp.param=137:2000 > | Of course you could not work reasonably with such a timeout, > | you might want to check then whether something between 200 > | 350 milliseconds would do. The default is 180. > > I tried that: > > [weerd@drop] $ doas wsconsctl mouse.tp.param=137:2000 > mouse.tp.param -> 137:999 > > But I still can't tap. > > | > | > This doesn't work on my touchpad. Also, I can't click-and-drag (never > | > | > worked, in any combination I while playing with the driver settings). > | > > | > This 'click-and-drag' behaviour does work if I click, keep the button > | > depressed and then move that same finger around. [...] > | > | Does this also work if you put a second finger on the touchpad (which > | does nothing)? > > No, but you helped me find something useful / interesting: > > 1. click button (keep depressed) > 2. second finger doesn't do anything > > however > > 1. touch 'second finger' first > 2. click button (keep depressed); now the 2nd finger can drag (1st >finger doesn't work for dragging now) > > This in addition to > > 1. click button (keep depressed) > 2. move 1st finger around on small clickable area to drag > > So, with this new approach, I have more surface area to drag around > and I can release my second finger to scroll beyond the end of the > touchpad. Never knew this was an option, I feel like an idiot now :) > > Thanks! > > Paul >
Re: touchpad input driver: testing needed
On Mon, Jul 31, 2017 at 11:02:28PM +0200, Ulf Brosziewski wrote: > > If you have a new snapshot (from July 27 or later) on a laptop with a > Synaptics, Apple, Alps, or Elantech-4 touchpad, you could help with > tests, more tests, and tests. In order to activate the driver, add the Hi, I'm using an August 3 snapshot on an asus x205ta where the touchpad never worked really well. It's an elantech touchpad detected as HID over I2C bus, through the ims driver. Partial dmesg: dwiic4 at acpi0: I2C4 addr 0x9092c000/0x1000 irq 35 iic3 at dwiic4 ihidev1 at iic3 addr 0x15 irq 72, vendor 0x4f3 product 0x401, ELAN0100 ihidev1: 93 report ids ims0 at ihidev1 reportid 1: 2 buttons, Z dir wsmouse0 at ims0 mux 0 hid at ihidev1 reportid 11 not configured hid at ihidev1 reportid 12 not configured hid at ihidev1 reportid 13 not configured hid at ihidev1 reportid 93 not configured "ELAN0100" at acpi0 not configured "INTCFD9" at acpi0 not configured It's a a version 4 touchpad? Will tests on this hardware be of any help? Regargs, Michele Full dmesg: OpenBSD 6.1-current (GENERIC.MP) #44: Thu Aug 3 12:12:07 MDT 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP RTC BIOS diagnostic error 3f real mem = 2056572928 (1961MB) avail mem = 1987952640 (1895MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0x7c31a010 (16 entries) bios0: vendor American Megatrends Inc. version "X205TA.212" date 09/04/2015 bios0: ASUSTeK COMPUTER INC. X205TA acpi0 at bios0: rev 2 acpi0: sleep states S0 S5 acpi0: tables DSDT FACP TCPA UEFI OEM0 DBG2 HPET LPIT APIC MCFG SSDT SSDT SSDT SSDT FPDT SSDT SSDT SSDT SSDT TPM2 BGRT CSRT MSDM acpi0: wakeup devices WLAN(S0) acpihpet0 at acpi0: 14318179 Hz acpimadt0 at acpi0 addr 0xfee0 cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Atom(TM) CPU Z3735F @ 1.33GHz, 1333.58 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,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT cpu0: 1MB 64b/line 16-way L2 cache cpu0: TSC frequency 1333579040 Hz cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 83MHz cpu0: mwait min=64, max=64, C-substates=0.2.0.0.0.0.3.3, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Atom(TM) CPU Z3735F @ 1.33GHz, 1333.34 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,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT cpu1: 1MB 64b/line 16-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Atom(TM) CPU Z3735F @ 1.33GHz, 1333.34 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,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT cpu2: 1MB 64b/line 16-way L2 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Atom(TM) CPU Z3735F @ 1.33GHz, 1333.34 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,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT cpu3: 1MB 64b/line 16-way L2 cache cpu3: smt 0, core 3, package 0 ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 87 pins acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpiprt0 at acpi0: bus 0 (PCI0) acpiec0 at acpi0: not present acpicpu0 at acpi0 C3: state 7: substate 4 >= num 3: C2(10@500 mwait.1@0x51), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0 C3: state 7: substate 4 >= num 3: C2(10@500 mwait.1@0x51), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0 C3: state 7: substate 4 >= num 3: C2(10@500 mwait.1@0x51), C1(1000@1 mwait.1), PSS acpicpu3 at acpi0 C3: state 7: substate 4 >= num 3: C2(10@500 mwait.1@0x51), C1(1000@1 mwait.1), PSS acpipwrres0 at acpi0: PLPE acpipwrres1 at acpi0: USBC, resource for XHC1, EHC1, OTG1 acpipwrres2 at acpi0: CLK0, resource for CAM1 acpipwrres3 at acpi0: CLK1, resource for CAM0 acpipwrres4 at acpi0: P28X acpipwrres5 at acpi0: P18X acpipwrres6 at acpi0: P28P acpipwrres7 at acpi0: P18P acpipwrres8 at acpi0: P28T, resource for CAM0, CAM1 acpipwrres9 at acpi0: P18T, resource for CAM0, CAM1 acpipwrres10 at acpi0: P1XT acpitz0 at acpi0: no critical temperature defined "INT3396" at acpi0 not configured bytgpio0 at acpi0: GPO2 uid 3 addr 0xfed0e000/0x
Re: touchpad input driver: testing needed
On Mon, Aug 07, 2017 at 01:13:22AM +0200, Ulf Brosziewski wrote: | On 08/05/2017 11:10 PM, Paul de Weerd wrote: | > Hi Ulf, | > | > On Fri, Aug 04, 2017 at 11:26:12PM +0200, Ulf Brosziewski wrote: | > | Hi Paul, | > | | > | thanks for your help. Does tapping work when you use | > | the synaptics driver? | > | > Nope, it doesn't. | > | | which probably means there is either something happening that | our hardware driver doesn't cover, or there is a hardware/firmware | bug. Anyhow, it's strange because the drivers only need very | basic data to identify a tap: the start of a contact, its | end, and the duration. Have you checked - with the synaptics | driver - whether a higher tap timeout helps? If not, would you | mind to make a short test? Could you increase the tap timeout | to a very high value, say, two seconds, and test whether a tap | works (with a slight delay)? For the wsmouse-internal driver, | the following command will set a two-second timeout: | # wsconsctl mouse.tp.param=137:2000 | Of course you could not work reasonably with such a timeout, | you might want to check then whether something between 200 | 350 milliseconds would do. The default is 180. I tried that: [weerd@drop] $ doas wsconsctl mouse.tp.param=137:2000 mouse.tp.param -> 137:999 But I still can't tap. | > | > This doesn't work on my touchpad. Also, I can't click-and-drag (never | > | > worked, in any combination I while playing with the driver settings). | > | > This 'click-and-drag' behaviour does work if I click, keep the button | > depressed and then move that same finger around. [...] | | Does this also work if you put a second finger on the touchpad (which | does nothing)? No, but you helped me find something useful / interesting: 1. click button (keep depressed) 2. second finger doesn't do anything however 1. touch 'second finger' first 2. click button (keep depressed); now the 2nd finger can drag (1st finger doesn't work for dragging now) This in addition to 1. click button (keep depressed) 2. move 1st finger around on small clickable area to drag So, with this new approach, I have more surface area to drag around and I can release my second finger to scroll beyond the end of the touchpad. Never knew this was an option, I feel like an idiot now :) Thanks! Paul -- >[<++>-]<+++.>+++[<-->-]<.>+++[<+ +++>-]<.>++[<>-]<+.--.[-] http://www.weirdnet.nl/
Re: touchpad input driver: testing needed
On 08/05/2017 11:10 PM, Paul de Weerd wrote: > Hi Ulf, > > On Fri, Aug 04, 2017 at 11:26:12PM +0200, Ulf Brosziewski wrote: > | Hi Paul, > | > | thanks for your help. Does tapping work when you use > | the synaptics driver? > > Nope, it doesn't. > which probably means there is either something happening that our hardware driver doesn't cover, or there is a hardware/firmware bug. Anyhow, it's strange because the drivers only need very basic data to identify a tap: the start of a contact, its end, and the duration. Have you checked - with the synaptics driver - whether a higher tap timeout helps? If not, would you mind to make a short test? Could you increase the tap timeout to a very high value, say, two seconds, and test whether a tap works (with a slight delay)? For the wsmouse-internal driver, the following command will set a two-second timeout: # wsconsctl mouse.tp.param=137:2000 Of course you could not work reasonably with such a timeout, you might want to check then whether something between 200 350 milliseconds would do. The default is 180. > | In the test setup with ws and the internal driver there > | are some restrictions on tapping: > | 1) It is suppressed when the position is an edge area > | (presumably the software button area at the bottom > | edge in this case). > > Normally, I'm tapping in the center of the touchpad. But I've tried > various locations, all don't work. > > | 2) The finger must not move by more than a certain > | distance, otherwise, the contact doesn't count as > | "tap". > > I've tried quite a few times, but no luck. I'm pretty sure at least > some of those attempts were in basically the same spot :) > > | 3) It is suppressed when hardware buttons are being > | pressed. > > I don't even try this :) > > | Just to be sure, can you exclude that 1), 2), or 3) is > | the reason for the problem? And neither one-, two-, nor > | three-finger taps work? > > I can: no tapping works, with any number of fingers. I should, > however, clarify one thing: > > | > This doesn't work on my touchpad. Also, I can't click-and-drag (never > | > worked, in any combination I while playing with the driver settings). > > This 'click-and-drag' behaviour does work if I click, keep the button > depressed and then move that same finger around. [...] Does this also work if you put a second finger on the touchpad (which does nothing)? > [...] So I can't click > with one finger and drag with another. > > Cheers, > > Paul >
Re: touchpad input driver: testing needed
Hello, The outputs from 'dmesg' and 'wsconsctl | grep mouse' on my Dell Inspiron 5567 follow: % dmesg OpenBSD 6.1-current (GENERIC.MP) #34: Tue Aug 1 18:56:18 MDT 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8389611520 (8000MB) avail mem = 8128987136 (7752MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xe9ca0 (93 entries) bios0: vendor Dell Inc. version "1.0.2" date 09/09/2016 bios0: Dell Inc. Inspiron 5567 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT FIDT MCFG HPET SSDT BOOT SSDT HPET SSDT UEFI SSDT LPIT SSDT SSDT DBGP DBG2 MSDM SSDT SLIC DMAR TPM2 acpi0: wakeup devices PXSX(S4) RP09(S4) PXSX(S4) RP10(S4) PXSX(S4) RP11(S4) PXSX(S4) RP12(S4) PXSX(S4) RP13(S4) PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz, 2712.00 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,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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT cpu0: 256KB 64b/line 8-way L2 cache cpu0: TSC frequency 271200 Hz cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 24MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz, 2712.00 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,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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz, 2712.00 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,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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 1, core 0, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz, 2712.00 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,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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 120 pins acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpihpet0 at acpi0: 2399 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PEG0) acpiprt2 at acpi0: bus -1 (PEG1) acpiprt3 at acpi0: bus -1 (PEG2) acpiprt4 at acpi0: bus -1 (RP09) acpiprt5 at acpi0: bus -1 (RP10) acpiprt6 at acpi0: bus -1 (RP11) acpiprt7 at acpi0: bus -1 (RP12) acpiprt8 at acpi0: bus -1 (RP13) acpiprt9 at acpi0: bus -1 (RP01) acpiprt10 at acpi0: bus -1 (RP02) acpiprt11 at acpi0: bus -1 (RP03) acpiprt12 at acpi0: bus -1 (RP04) acpiprt13 at acpi0: bus 1 (RP05) acpiprt14 at acpi0: bus 2 (RP06) acpiprt15 at acpi0: bus -1 (RP07) acpiprt16 at acpi0: bus -1 (RP08) acpiprt17 at acpi0: bus -1 (RP17) acpiprt18 at acpi0: bus -1 (RP18) acpiprt19 at acpi0: bus -1 (RP19) acpiprt20 at acpi0: bus -1 (RP20) acpiprt21 at acpi0: bus -1 (RP14) acpiprt22 at acpi0: bus -1 (RP15) acpiprt23 at acpi0: bus -1 (RP16) acpiec0 at acpi0 acpiec at acpi0 not configured acpicpu0 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu3 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpipwrres0 at acpi0: WRST acpipwrres1 at acpi0: WRST acpipwrres2 at acpi0: WRST acpipwrres3
Re: touchpad input driver: testing needed
Hello, The outputs from 'dmesg' and 'wsconsctl | grep mouse' on my Dell Inspiron 5567 follow: % dmesg OpenBSD 6.1-current (GENERIC.MP) #34: Tue Aug 1 18:56:18 MDT 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8389611520 (8000MB) avail mem = 8128987136 (7752MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xe9ca0 (93 entries) bios0: vendor Dell Inc. version "1.0.2" date 09/09/2016 bios0: Dell Inc. Inspiron 5567 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT FIDT MCFG HPET SSDT BOOT SSDT HPET SSDT UEFI SSDT LPIT SSDT SSDT DBGP DBG2 MSDM SSDT SLIC DMAR TPM2 acpi0: wakeup devices PXSX(S4) RP09(S4) PXSX(S4) RP10(S4) PXSX(S4) RP11(S4) PXSX(S4) RP12(S4) PXSX(S4) RP13(S4) PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz, 2712.00 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,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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT cpu0: 256KB 64b/line 8-way L2 cache cpu0: TSC frequency 271200 Hz cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 24MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz, 2712.00 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,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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz, 2712.00 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,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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 1, core 0, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz, 2712.00 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,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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 120 pins acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpihpet0 at acpi0: 2399 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PEG0) acpiprt2 at acpi0: bus -1 (PEG1) acpiprt3 at acpi0: bus -1 (PEG2) acpiprt4 at acpi0: bus -1 (RP09) acpiprt5 at acpi0: bus -1 (RP10) acpiprt6 at acpi0: bus -1 (RP11) acpiprt7 at acpi0: bus -1 (RP12) acpiprt8 at acpi0: bus -1 (RP13) acpiprt9 at acpi0: bus -1 (RP01) acpiprt10 at acpi0: bus -1 (RP02) acpiprt11 at acpi0: bus -1 (RP03) acpiprt12 at acpi0: bus -1 (RP04) acpiprt13 at acpi0: bus 1 (RP05) acpiprt14 at acpi0: bus 2 (RP06) acpiprt15 at acpi0: bus -1 (RP07) acpiprt16 at acpi0: bus -1 (RP08) acpiprt17 at acpi0: bus -1 (RP17) acpiprt18 at acpi0: bus -1 (RP18) acpiprt19 at acpi0: bus -1 (RP19) acpiprt20 at acpi0: bus -1 (RP20) acpiprt21 at acpi0: bus -1 (RP14) acpiprt22 at acpi0: bus -1 (RP15) acpiprt23 at acpi0: bus -1 (RP16) acpiec0 at acpi0 acpiec at acpi0 not configured acpicpu0 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu3 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpipwrres0 at acpi0: WRST acpipwrres1 at acpi0: WRST acpipwrres2 at acpi0: WRST acpipwrres3
Re: touchpad input driver: testing needed
Hi Ulf, On Fri, Aug 04, 2017 at 11:26:12PM +0200, Ulf Brosziewski wrote: | Hi Paul, | | thanks for your help. Does tapping work when you use | the synaptics driver? Nope, it doesn't. | In the test setup with ws and the internal driver there | are some restrictions on tapping: | 1) It is suppressed when the position is an edge area | (presumably the software button area at the bottom | edge in this case). Normally, I'm tapping in the center of the touchpad. But I've tried various locations, all don't work. | 2) The finger must not move by more than a certain | distance, otherwise, the contact doesn't count as | "tap". I've tried quite a few times, but no luck. I'm pretty sure at least some of those attempts were in basically the same spot :) | 3) It is suppressed when hardware buttons are being | pressed. I don't even try this :) | Just to be sure, can you exclude that 1), 2), or 3) is | the reason for the problem? And neither one-, two-, nor | three-finger taps work? I can: no tapping works, with any number of fingers. I should, however, clarify one thing: | > This doesn't work on my touchpad. Also, I can't click-and-drag (never | > worked, in any combination I while playing with the driver settings). This 'click-and-drag' behaviour does work if I click, keep the button depressed and then move that same finger around. So I can't click with one finger and drag with another. Cheers, Paul -- >[<++>-]<+++.>+++[<-->-]<.>+++[<+ +++>-]<.>++[<>-]<+.--.[-] http://www.weirdnet.nl/
Re: touchpad input driver: testing needed
This is from a Dell xps 9333 model which has a Synaptics touchpad which has been working fine otherwise and appears to continue to work fine with your driver. wsconsctl mouse.type=synaptics mouse.rawmode=0 mouse.scale=1472,5676,1408,4722,0,45,60 mouse.tp.tapping=1 mouse.tp.scaling=0.172 mouse.tp.swapsides=0 mouse.tp.disable=0 dmesg: Aug 5 09:06:14 dark /bsd: OpenBSD 6.1-current (GENERIC.MP) #44: Thu Aug 3 12:12:07 MDT 2017 Aug 5 09:06:14 dark /bsd: dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP Aug 5 09:06:14 dark /bsd: real mem = 8068243456 (7694MB) Aug 5 09:06:14 dark /bsd: avail mem = 7817363456 (7455MB) Aug 5 09:06:14 dark /bsd: mpath0 at root Aug 5 09:06:14 dark /bsd: scsibus0 at mpath0: 256 targets Aug 5 09:06:14 dark /bsd: mainbus0 at root Aug 5 09:06:14 dark /bsd: bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xe0fc0 (69 entries) Aug 5 09:06:14 dark /bsd: bios0: vendor Dell Inc. version "A08" date 08/31/2015 Aug 5 09:06:14 dark /bsd: bios0: Dell Inc. XPS13 9333 Aug 5 09:06:14 dark /bsd: acpi0 at bios0: rev 2 Aug 5 09:06:14 dark /bsd: acpi0: sleep states S0 S1 S3 S4 S5 Aug 5 09:06:14 dark /bsd: acpi0: tables DSDT FACP ASF! HPET LPIT APIC MCFG SSDT SSDT SSDT SSDT UEFI POAT BATB FPDT SLIC UEFI CSRT Aug 5 09:06:14 dark /bsd: acpi0: wakeup devices P0P1(S4) GLAN(S4) EHC1(S4) EHC2(S4) XHC_(S4) HDEF(S4) PXSX(S4) RP01(S4) PXSX(S4) PXSX(S4) RP03(S4) PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4) […] Aug 5 09:06:14 dark /bsd: acpitimer0 at acpi0: 3579545 Hz, 24 bits Aug 5 09:06:14 dark /bsd: acpihpet0 at acpi0: 14318179 Hz Aug 5 09:06:14 dark /bsd: acpimadt0 at acpi0 addr 0xfee0: PC-AT compat Aug 5 09:06:14 dark /bsd: cpu0 at mainbus0: apid 0 (boot processor) Aug 5 09:06:14 dark /bsd: cpu0: Intel(R) Core(TM) i7-4510U CPU @ 2.00GHz, 2594.44 MHz Aug 5 09:06:14 dark /bsd: 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,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,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 Aug 5 09:06:14 dark /bsd: cpu0: 256KB 64b/line 8-way L2 cache Aug 5 09:06:14 dark /bsd: cpu0: TSC frequency 2594437250 Hz Aug 5 09:06:14 dark /bsd: cpu0: smt 0, core 0, package 0 Aug 5 09:06:14 dark /bsd: mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges Aug 5 09:06:14 dark /bsd: cpu0: apic clock running at 99MHz Aug 5 09:06:14 dark /bsd: cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE Aug 5 09:06:14 dark /bsd: cpu1 at mainbus0: apid 1 (application processor) Aug 5 09:06:14 dark /bsd: cpu1: Intel(R) Core(TM) i7-4510U CPU @ 2.00GHz, 2594.00 MHz Aug 5 09:06:14 dark /bsd: 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,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,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 Aug 5 09:06:14 dark /bsd: cpu1: 256KB 64b/line 8-way L2 cache Aug 5 09:06:14 dark /bsd: cpu1: smt 1, core 0, package 0 Aug 5 09:06:14 dark /bsd: cpu2 at mainbus0: apid 2 (application processor) Aug 5 09:06:14 dark /bsd: cpu2: Intel(R) Core(TM) i7-4510U CPU @ 2.00GHz, 2594.00 MHz Aug 5 09:06:14 dark /bsd: 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,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,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 Aug 5 09:06:14 dark /bsd: cpu2: 256KB 64b/line 8-way L2 cache Aug 5 09:06:14 dark /bsd: cpu2: smt 0, core 1, package 0 Aug 5 09:06:14 dark /bsd: cpu3 at mainbus0: apid 3 (application processor) Aug 5 09:06:14 dark /bsd: cpu3: Intel(R) Core(TM) i7-4510U CPU @ 2.00GHz, 2594.00 MHz Aug 5 09:06:14 dark /bsd: 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,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,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 Aug 5 09:06:14 dark /bsd: cpu3: 256KB 64b/line 8-way L2 cache Aug 5 09:06:14 dark /bsd: cpu3: smt 1, core 1, package 0 Aug 5 09:06:14 dark /bsd: ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins Aug 5 09:06:14 dark /bsd: acpimcfg0 at acpi0 addr 0xf800, bus 0-63 Aug 5 09:06:14 dark /bsd: acpiprt0 at acpi0: bus 0 (PCI0) Aug 5 09:06:14 dark /bsd: acpiprt1 at acpi0: bus -1 (P0P1) Aug 5 09:06:14 dark /bsd: acpiprt2 at acpi0: bu
Re: touchpad input driver: testing needed
Hi there! A ThinkPad T460s over here working like a charm; some verbose output below. Regards, $ $ doas wsconsctl | grep mouse wsconsctl: Use explicit arg to view keyboard.map. mouse.type=synaptics mouse.rawmode=0 mouse.scale=1472,5676,1408,4762,0,45,69 mouse.tp.tapping=1 mouse.tp.scaling=0.171 mouse.tp.swapsides=0 mouse.tp.disable=0 mouse1.type=ps2 $ $ dmesg OpenBSD 6.1-current (GENERIC.MP) #44: Thu Aug 3 12:12:07 MDT 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8304578560 (7919MB) avail mem = 8046538752 (7673MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xcf054000 (65 entries) bios0: vendor LENOVO version "N1CET58W (1.26 )" date 06/30/2017 bios0: LENOVO 20F9005CMS acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP TCPA SSDT SSDT TPM2 UEFI SSDT SSDT ECDT HPET APIC MCFG SSDT DBGP DBG2 BOOT BATB SLIC SSDT SSDT MSDM DMAR ASF! FPDT UEFI acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP2(S4) XHCI(S3) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiec0 at acpi0 acpihpet0 at acpi0: 2399 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2400.00 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,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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT cpu0: 256KB 64b/line 8-way L2 cache cpu0: TSC frequency 24 Hz cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 23MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2400.00 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,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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2400.00 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,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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 1, core 0, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2400.00 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,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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 120 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PEG0) acpiprt2 at acpi0: bus -1 (PEG1) acpiprt3 at acpi0: bus -1 (PEG2) acpiprt4 at acpi0: bus 2 (EXP1) acpiprt5 at acpi0: bus -1 (EXP2) acpiprt6 at acpi0: bus 4 (EXP3) acpiprt7 at acpi0: bus -1 (EXP5) acpiprt8 at acpi0: bus -1 (RP09) acpicpu0 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu3 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpipwrres0 at acpi0: PUBS, resource for XHCI acpipwrres1 at acpi0: PG00, resource for PEG0 acpipwrres2 at acpi0: PG01, resource for PEG1 acpipwrres3 at acpi0: PG02, resource for PEG2 acpipwrres4 at acpi0: WRST acpipwrres5 at acpi0: WRST acpitz0 at acpi0: critical temperature is 128 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB "LEN0071" at acpi0 not configured "LEN004B" at acpi0 not configured "INT3F0D" at acpi0 not configured acpibat0 at acpi0: BAT0 model "00H
Re: touchpad input driver: testing needed
Hi Paul, thanks for your help. Does tapping work when you use the synaptics driver? In the test setup with ws and the internal driver there are some restrictions on tapping: 1) It is suppressed when the position is an edge area (presumably the software button area at the bottom edge in this case). 2) The finger must not move by more than a certain distance, otherwise, the contact doesn't count as "tap". 3) It is suppressed when hardware buttons are being pressed. Just to be sure, can you exclude that 1), 2), or 3) is the reason for the problem? And neither one-, two-, nor three-finger taps work? Regards, Ulf On 08/04/2017 11:24 AM, Paul de Weerd wrote: > Hi Ulf, > > This really helps a lot on my touchpad. I used to have the following > config: > > Section "InputClass" > Identifier "Sony VAIO touchpad" > MatchIsTouchpad "on" > Option "TapButton1" "1" > Option "HasSecondarySoftButtons" "true" > Option "ClickPad" "true" > Option "TouchpadOff" "1" > Option "AreaTopEdge" "20%" > Option "SoftButtonAreas" "60% 0 82% 0 40% 60% 82% 0" > Option "SecondarySoftButtonAreas" "60% 0 0 20% 40% 60% 0 20%" > EndSection > > All from some experimentation with a bunch of buttons to try to get > sane behaviour out of my touchpad. Without a config, there was no > scrolling and no right button (and probably other problems I now > forget). With your wsmouse touchpad stuff, I can scroll and have > right click again. Speed seems also fine. > > On Mon, Jul 31, 2017 at 11:02:28PM +0200, Ulf Brosziewski wrote: > | For now, X will treat the device like a mouse, please don't look for > | touchpad-specific configuration options there. Tapping can be enabled > | by the command > | # wsconsctl mouse.tp.tapping=1 > > This doesn't work on my touchpad. Also, I can't click-and-drag (never > worked, in any combination I while playing with the driver settings). > > Thanks! > > Paul > > [weerd@drop] $ wsconsctl mouse > mouse.type=synaptics > mouse.rawmode=0 > mouse.scale=1472,5768,1408,4748,0,66,66 > mouse.tp.tapping=1 > mouse.tp.scaling=0.169 > mouse.tp.swapsides=0 > mouse.tp.disable=0 > > OpenBSD 6.1-current (GENERIC.MP) #3: Fri Aug 4 07:49:26 CEST 2017 > we...@drop.weirdnet.nl:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 8485335040 (8092MB) > avail mem = 8221806592 (7840MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xe6020 (18 entries) > bios0: vendor INSYDE version "R1010H5" date 07/28/2011 > bios0: Sony Corporation VPCZ23C5E > acpi0 at bios0: rev 2 > acpi0: sleep states S0 S3 S4 S5 > acpi0: tables DSDT FACP TCPA ASF! HPET APIC MCFG SLIC WDAT SSDT BOOT SSDT > ASPT SSDT SSDT SSDT SSDT > acpi0: wakeup devices EHC1(S3) EHC2(S3) HDEF(S0) WLAN(S0) RP01(S0) RMSC(S0) > RP02(S0) NXUC(S3) RP03(S3) RLAN(S3) RP04(S3) RP07(S3) PEG0(S0) PEGP(S0) > 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-2640M 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,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT > cpu0: 256KB 64b/line 8-way L2 cache > cpu0: TSC frequency 2794061280 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 1 (application processor) > cpu1: Intel(R) Core(TM) i7-2640M CPU @ 2.80GHz, 2793.66 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,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,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-2640M CPU @ 2.80GHz, 2793.66 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,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,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-2640M CPU @ 2.80GHz, 2793.66 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
Re: touchpad input driver: testing needed
Hi Ulf, This really helps a lot on my touchpad. I used to have the following config: Section "InputClass" Identifier "Sony VAIO touchpad" MatchIsTouchpad "on" Option "TapButton1" "1" Option "HasSecondarySoftButtons" "true" Option "ClickPad" "true" Option "TouchpadOff" "1" Option "AreaTopEdge" "20%" Option "SoftButtonAreas" "60% 0 82% 0 40% 60% 82% 0" Option "SecondarySoftButtonAreas" "60% 0 0 20% 40% 60% 0 20%" EndSection All from some experimentation with a bunch of buttons to try to get sane behaviour out of my touchpad. Without a config, there was no scrolling and no right button (and probably other problems I now forget). With your wsmouse touchpad stuff, I can scroll and have right click again. Speed seems also fine. On Mon, Jul 31, 2017 at 11:02:28PM +0200, Ulf Brosziewski wrote: | For now, X will treat the device like a mouse, please don't look for | touchpad-specific configuration options there. Tapping can be enabled | by the command | # wsconsctl mouse.tp.tapping=1 This doesn't work on my touchpad. Also, I can't click-and-drag (never worked, in any combination I while playing with the driver settings). Thanks! Paul [weerd@drop] $ wsconsctl mouse mouse.type=synaptics mouse.rawmode=0 mouse.scale=1472,5768,1408,4748,0,66,66 mouse.tp.tapping=1 mouse.tp.scaling=0.169 mouse.tp.swapsides=0 mouse.tp.disable=0 OpenBSD 6.1-current (GENERIC.MP) #3: Fri Aug 4 07:49:26 CEST 2017 we...@drop.weirdnet.nl:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8485335040 (8092MB) avail mem = 8221806592 (7840MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xe6020 (18 entries) bios0: vendor INSYDE version "R1010H5" date 07/28/2011 bios0: Sony Corporation VPCZ23C5E acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP TCPA ASF! HPET APIC MCFG SLIC WDAT SSDT BOOT SSDT ASPT SSDT SSDT SSDT SSDT acpi0: wakeup devices EHC1(S3) EHC2(S3) HDEF(S0) WLAN(S0) RP01(S0) RMSC(S0) RP02(S0) NXUC(S3) RP03(S3) RLAN(S3) RP04(S3) RP07(S3) PEG0(S0) PEGP(S0) 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-2640M 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,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT cpu0: 256KB 64b/line 8-way L2 cache cpu0: TSC frequency 2794061280 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 1 (application processor) cpu1: Intel(R) Core(TM) i7-2640M CPU @ 2.80GHz, 2793.66 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,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,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-2640M CPU @ 2.80GHz, 2793.66 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,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,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-2640M CPU @ 2.80GHz, 2793.66 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,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 0 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 2 (RP01) acpiprt2 at acpi0: bus 3 (RP02) acpiprt3 at acpi0: bus 4 (RP03) acpiprt4 at acpi0: bus 5 (RP04) acpiprt5 at acpi0: bus 8 (RP07) acpiprt6 at acpi0: bus -1 (PEG0) acpiec0 at acpi0 acpicpu0 at acpi0: C3(350@104 mwait.1@0x20), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C3(350@104 mwait.1@0x20), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0: C3(350@104 mwait.1@0x20), C1(1000@1 mwait.1), PSS acpicpu3 at acpi0: C3(350@104 mwait.1@0x20), C1(1000@1 mwait.1), PSS acpitz0 at acpi0: critical temperature is 98 degC ac
Re: touchpad input driver: testing needed
On Thu, Aug 03, 2017 at 10:48:12PM +0200, Ulf Brosziewski wrote: > Sorry, I should have been more explicit in my message: Not all > hardware and driver setups are supported yet. Your touchpad is > a HID device, a "Windows Precision Touchpad". Up to now, the > hardware driver (imt(4)) hasn't been adapted to the new wsmouse > functionality, only models that run with pms(4) or ubcmtp(4) > can use the input driver. > > What you see with ws is your touchpad emulating a PS2 mouse. I see. Thanks for the info. > Of course, updating the other touchpad hardware drivers belongs > to the next steps on the agenda. In case you want to test kernel > patches for your case, please tell me ;-) Sure, I can test patches ;-)
Re: touchpad input driver: testing needed
Sorry, I should have been more explicit in my message: Not all hardware and driver setups are supported yet. Your touchpad is a HID device, a "Windows Precision Touchpad". Up to now, the hardware driver (imt(4)) hasn't been adapted to the new wsmouse functionality, only models that run with pms(4) or ubcmtp(4) can use the input driver. What you see with ws is your touchpad emulating a PS2 mouse. Of course, updating the other touchpad hardware drivers belongs to the next steps on the agenda. In case you want to test kernel patches for your case, please tell me ;-) On 08/03/2017 01:32 PM, Remi Locherer wrote: > On Mon, Jul 31, 2017 at 11:02:28PM +0200, Ulf Brosziewski wrote: >> for you. As always, a dmesg would be appreciated. The output of >> # wsconsctl | grep 'mouse' >> could also be of interest here (you must run it as root). > > This is from a Dell XPS 13 9343. The mouse pointer moves into the > wrong (opposite) direction. Only the left soft button is available. > > mistral ~$ doas wsconsctl | grep mouse > wsconsctl: Use explicit arg to view keyboard.map. > wsconsctl: mousecfg error: WSMOUSEIO_GETPARAMS (-1) > mouse.type=elantech > mouse.rawmode=0 > mouse.scale=0,1013,0,566,0,0,0 > mistral ~$ > > > With the synaptics driver I use this configuration: > > Section "InputDevice" > Identifier "clickpad" > Driver "synaptics" > Option "Device" "/dev/wsmouse0" > Option "AutoServerLayout" "true" > Option "ClickPad" "true" > Option "EmulateMidButtonTime" "0" > Option "SoftButtonAreas""80% 0 82% 0 40% 79% 82% 0" > Option "VertTwoFingerScroll""true" > Option "TapButton1" "1" > EndSection > > > > OpenBSD 6.1-current (GENERIC.MP) #40: Wed Aug 2 18:53:06 MDT 2017 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 8473636864 (8081MB) > avail mem = 8210477056 (7830MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xed7d0 (84 entries) > bios0: vendor Dell Inc. version "A12" date 05/09/2017 > bios0: Dell Inc. XPS 13 9343 > acpi0 at bios0: rev 2 > acpi0: sleep states S0 S3 S4 S5 > acpi0: tables DSDT FACP APIC FPDT FIDT MCFG HPET SSDT UEFI SSDT ASF! SSDT > SSDT SSDT SSDT PCCT SSDT SSDT SSDT SLIC MSDM DMAR CSRT BGRT > acpi0: wakeup devices PEGP(S4) PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4) > PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) > PXSX(S4) RP05(S4) [...] > acpitimer0 at acpi0: 3579545 Hz, 24 bits > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz, 2195.26 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,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,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,PT,SENSOR,ARAT > cpu0: 256KB 64b/line 8-way L2 cache > cpu0: TSC frequency 2195263540 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.1.1.1, IBE > cpu1 at mainbus0: apid 2 (application processor) > cpu1: Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz, 2194.92 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,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,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,PT,SENSOR,ARAT > cpu1: 256KB 64b/line 8-way L2 cache > cpu1: smt 0, core 1, package 0 > cpu2 at mainbus0: apid 1 (application processor) > cpu2: Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz, 2194.92 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,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,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,PT,SENSOR,ARAT > cpu2: 256KB 64b/line 8-way L2 cache > cpu2: smt 1, core 0, package 0 > cpu3 at mainbus0: apid 3 (application processor) > cpu3: Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz, 2194.92 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,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PA
Re: touchpad input driver: testing needed
Thanks a lot. Again, there seems to be a misunderstanding concerning the 'swapsides' flag. I have described its meaning in my answer to Tom, and I hope it's clearer this time. On 08/03/2017 06:30 PM, Bruno Flueckiger wrote: > I've tested it on my HP ProBook 450 G3 with the snapshot from July 30. > In xorg.conf I've put the block you've proposed, there is nothing else > in it. > > Cursor moves: OK > Tapping: OK one finger = left click, two fingers = right click > Swapsides:not OK, scroll bar moves the same way my fingers move on > the touchpad, no matter what the setting is > Scaling/Speed:OK > > Thank you very much for your work! > > # wsconsctl | grep mouse > > mouse.type=synaptics > mouse.rawmode=0 > mouse.scale=1472,5716,1408,4886,0,46,80 > mouse.tp.tapping=1 > mouse.tp.scaling=0.167 > mouse.tp.swapsides=0 > mouse.tp.disable=0 > > OpenBSD 6.1-current (GENERIC.MP) #21: Sun Jul 30 09:58:05 MDT 2017 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 17055059968 (16264MB) > avail mem = 16531820544 (15765MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xd9a23000 (34 entries) > bios0: vendor HP version "N78 Ver. 01.14" date 08/08/2016 > bios0: HP HP ProBook 450 G3 > acpi0 at bios0: rev 2 > acpi0: sleep states S0 S3 S4 S5 > acpi0: tables DSDT FACP SSDT SSDT TCPA SSDT UEFI SSDT SSDT MSDM SLIC HPET > APIC MCFG SSDT SSDT SSDT SSDT SSDT NHLT FPDT BGRT SSDT > acpi0: wakeup devices PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4) PEGP(S4) PEG0(S4) > GLAN(S4) XHC_(S3) XDCI(S4) HDAS(S4) PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) > PXSX(S4) RP03(S4) [...] > acpitimer0 at acpi0: 3579545 Hz, 24 bits > acpihpet0 at acpi0: 2399 Hz > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2400.00 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,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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT > cpu0: 256KB 64b/line 8-way L2 cache > cpu0: TSC frequency 24 Hz > cpu0: smt 0, core 0, package 0 > mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges > cpu0: apic clock running at 23MHz > cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE > cpu1 at mainbus0: apid 2 (application processor) > cpu1: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2400.00 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,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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT > cpu1: 256KB 64b/line 8-way L2 cache > cpu1: smt 0, core 1, package 0 > cpu2 at mainbus0: apid 1 (application processor) > cpu2: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2400.00 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,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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT > cpu2: 256KB 64b/line 8-way L2 cache > cpu2: smt 1, core 0, package 0 > cpu3 at mainbus0: apid 3 (application processor) > cpu3: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2400.00 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,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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT > cpu3: 256KB 64b/line 8-way L2 cache > cpu3: smt 1, core 1, package 0 > ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 120 pins > acpimcfg0 at acpi0 addr 0xf800, bus 0-63 > acpiprt0 at acpi0: bus 0 (PCI0) > acpiprt1 at acpi0: bus -1 (PEG1) > acpiprt2 at acpi0: bus -1 (PEG2) > acpiprt3 at acpi0: bus -1 (PEG0) > acpiprt4 at acpi0: bus -1 (RP01) > acpiprt5 at acpi0: bus -1 (RP02) > acpiprt6 at acpi0: bus -1 (RP03) > acpiprt7 at acpi0: bus -1 (RP04) > acpiprt8 at acpi0: bus 1 (RP05) > acpiprt9 at acpi0: bus 2 (RP06) > acpiprt10 at acpi0: bus -1 (RP07) > acpiprt11 at acpi0: bus -1 (RP08) > acpiprt12 at acpi0: bus 3 (RP09
Re: touchpad input driver: testing needed
Thanks for testing. It looks like my description of the 'swapsides' flag has caused misunderstandings here: It doesn't invert scroll directions, rather it sets up button areas or scroll areas for left-handed use: An area for vertical scrolling - if present - will be at the left edge of the touchpad if the flag is set (the default is, as usual, the right edge). Moreover, on clickpads the order of the software button areas will be changed to: right-button area - middle-button area - left-button area, instead of the usual "LMR": default: swapsides == 1: +--+ +--+ | | | | | | | | | MM | | MM | +--+ +--+ You can revert scroll directions in X. There are various ways to do it. If there isn't a "Mouse and Touchpad" tool in your desktop environment, you could add a "ZAxisMapping" to your xorg.conf: Section "InputClass" Identifier "wsmouse touchpad" Driver "ws" MatchIsTouchpad "on" Option "ZAxisMapping" "5 4" EndSection On 08/03/2017 11:58 AM, tomr wrote: > On my Thinkpad X1 Carbon (first gen, I think) it looks pretty good. The > only thing in xorg.conf is your proposed block. > > Cursor moves: Yes > Pad tapping: Yes, honours enable/disable > Pad speed/scaling: Honours setting > Swapsides: not honoured > Regardless of setting, the scroll bar moves in sync with fingers (ie > fingers away from me makes scroll bar go up / sends the page down) > Looking at `xinput --test /dev/wsmouse0` I see button 4 scrolling up and > 5 scrolling down, either way. > > wsconsctl output: > $ wsconsctl mouse > > wsconsctl: /dev/wsmouse0: Permission denied > $ wsconsctl | grep mouse > wsconsctl: /dev/wskbd0: Permission denied > wsconsctl: /dev/wsmouse0: Permission denied > wsconsctl: /dev/ttyC0: Permission denied > $ doas wsconsctl | grep mouse > wsconsctl: Use explicit arg to view keyboard.map. > mouse.type=synaptics > mouse.rawmode=0 > mouse.scale=1472,5678,1408,4732,0,46,63 > mouse.tp.tapping=0 > mouse.tp.scaling=0.200 > mouse.tp.swapsides=1 > mouse.tp.disable=0 > mouse1.type=ps2 > $ > > > dmesg: > OpenBSD 6.1-current (GENERIC.MP) #34: Tue Aug 1 18:56:18 MDT 2017 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 8383655936 (7995MB) > avail mem = 8123219968 (7746MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xdae9d000 (68 entries) > bios0: vendor LENOVO version "G6ET96WW (2.56 )" date 04/29/2013 > bios0: LENOVO 34486T7 > acpi0 at bios0: rev 2 > acpi0: sleep states S0 S3 S4 S5 > acpi0: tables DSDT FACP TCPA SSDT SSDT SSDT HPET APIC MCFG ECDT FPDT > ASF! UEFI UEFI MSDM SSDT SSDT DMAR UEFI SSDT DBG2 BGRT > acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP2(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) i5-3337U CPU @ 1.80GHz, 1796.26 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,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,D > EADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT > cpu0: 256KB 64b/line 8-way L2 cache > cpu0: TSC frequency 1796264010 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 1 (application processor) > cpu1: Intel(R) Core(TM) i5-3337U CPU @ 1.80GHz, 1795.92 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,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,D > EADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,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) i5-3337U CPU @ 1.80GHz, 1795.92 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,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC
Re: touchpad input driver: testing needed
Thanks for the report. The speed of scrolling is indeed independent of the scale factor. Internally, these are distinct settings. (I've been vaguely considering to couple them, but there is nothing settled yet; it might be a bad idea if the initial values don't match). As to the pointer movement, there is still the option of increasing the "acceleration factor" of X. That's not the same as changing the base speed, you might want to check which option is better for you. If the base speed is too high, you may have difficulties to move the pointer with "pixel precision". If the acceleration factor is too high, you may have difficulties to predict the pointer speed that results from normal or higher input speed. On 08/03/2017 10:21 AM, Henrik Friedrichsen wrote: > No apparent problems here on my ThinkPad x220i. > > Base pointer speed was slightly slower which I was able to adjust by > setting mouse.tp.scaling. This did, however, not affect the > two-finger-scrolling, which required more mileage on my trackpad to > scroll compared to the synaptics driver. > > Nice work! > > wsconsctl: > mouse.type=synaptics > mouse.rawmode=0 > mouse.scale=1472,5472,1408,4448,0,75,129 > mouse.tp.tapping=0 > mouse.tp.scaling=0.200 > mouse.tp.swapsides=0 > mouse.tp.disable=0 > > dmesg: > OpenBSD 6.1-current (GENERIC.MP) #34: Tue Aug 1 18:56:18 MDT 2017 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 8451125248 (8059MB) > avail mem = 8188628992 (7809MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xdae9c000 (66 entries) > bios0: vendor LENOVO version "8DET73WW (1.43 )" date 10/12/2016 > bios0: LENOVO 4290W1A > acpi0 at bios0: rev 2 > acpi0: sleep states S0 S3 S4 S5 > acpi0: tables DSDT FACP SLIC SSDT SSDT SSDT HPET APIC MCFG ECDT ASF! TCPA > SSDT SSDT UEFI UEFI UEFI > acpi0: wakeup devices LID_(S3) SLPB(S3) IGBE(S4) EXP4(S4) EXP7(S4) 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) i3-2310M CPU @ 2.10GHz, 2093.51 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,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT > cpu0: 256KB 64b/line 8-way L2 cache > cpu0: TSC frequency 2093506380 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 1 (application processor) > cpu1: Intel(R) Core(TM) i3-2310M CPU @ 2.10GHz, 2093.20 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,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,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) i3-2310M CPU @ 2.10GHz, 2093.20 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,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,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) i3-2310M CPU @ 2.10GHz, 2093.20 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,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT > cpu3: 256KB 64b/line 8-way L2 cache > cpu3: smt 1, core 1, package 0 > ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins > acpimcfg0 at acpi0 addr 0xf800, bus 0-63 > acpiec0 at acpi0 > 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 5 (EXP4) > acpiprt5 at acpi0: bus 13 (EXP5) > acpiprt6 at acpi0: bus -1 (EXP7) > acpicpu0 at acpi0: C3(200@109 io@0x416), C2(500@80 io@0x414), C1(1000@1 > halt), PSS > acpicpu1 at acpi0: C3(200@109 io@0x416), C2(500@80 io@0x414), C1(1000@1 > halt), PSS > acpicpu2 at acpi0: C3(200@109 io@0x416), C2(500@80 io@0x414), C1(1000@1 > halt), PSS > acpicpu3 at acpi0: C3(200@109 io@0x416), C2(500@80 io@0x414), C1(1000@1 > halt), PSS > acpipwrres0 at acpi0: PUBS, resource for EHC1, EHC2 > acpitz0 at acpi0:
Re: touchpad input driver: testing needed
I've tested it on my HP ProBook 450 G3 with the snapshot from July 30. In xorg.conf I've put the block you've proposed, there is nothing else in it. Cursor moves: OK Tapping:OK one finger = left click, two fingers = right click Swapsides: not OK, scroll bar moves the same way my fingers move on the touchpad, no matter what the setting is Scaling/Speed: OK Thank you very much for your work! # wsconsctl | grep mouse mouse.type=synaptics mouse.rawmode=0 mouse.scale=1472,5716,1408,4886,0,46,80 mouse.tp.tapping=1 mouse.tp.scaling=0.167 mouse.tp.swapsides=0 mouse.tp.disable=0 OpenBSD 6.1-current (GENERIC.MP) #21: Sun Jul 30 09:58:05 MDT 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17055059968 (16264MB) avail mem = 16531820544 (15765MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xd9a23000 (34 entries) bios0: vendor HP version "N78 Ver. 01.14" date 08/08/2016 bios0: HP HP ProBook 450 G3 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT SSDT TCPA SSDT UEFI SSDT SSDT MSDM SLIC HPET APIC MCFG SSDT SSDT SSDT SSDT SSDT NHLT FPDT BGRT SSDT acpi0: wakeup devices PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4) PEGP(S4) PEG0(S4) GLAN(S4) XHC_(S3) XDCI(S4) HDAS(S4) PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 2399 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2400.00 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,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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT cpu0: 256KB 64b/line 8-way L2 cache cpu0: TSC frequency 24 Hz cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 23MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2400.00 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,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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2400.00 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,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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 1, core 0, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2400.00 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,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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 120 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PEG1) acpiprt2 at acpi0: bus -1 (PEG2) acpiprt3 at acpi0: bus -1 (PEG0) acpiprt4 at acpi0: bus -1 (RP01) acpiprt5 at acpi0: bus -1 (RP02) acpiprt6 at acpi0: bus -1 (RP03) acpiprt7 at acpi0: bus -1 (RP04) acpiprt8 at acpi0: bus 1 (RP05) acpiprt9 at acpi0: bus 2 (RP06) acpiprt10 at acpi0: bus -1 (RP07) acpiprt11 at acpi0: bus -1 (RP08) acpiprt12 at acpi0: bus 3 (RP09) acpiprt13 at acpi0: bus -1 (RP10) acpiprt14 at acpi0: bus -1 (RP11) acpiprt15 at acpi0: bus -1 (RP12) acpiprt16 at acpi0: bus -1 (RP13) acpiprt17 at acpi0: bus -1 (RP14) acpiprt18 at acpi0: bus -1 (RP15) acpiprt19 at acpi0: bus -1 (RP16) acpiprt20 at acpi0: bus -1 (RP17) acpiprt21 at acpi0: bus -1 (RP18) acpiprt22 at acpi0: bus -1 (RP19) acpiprt23 at acpi0: bus -1 (RP20) acpiec0 at acpi0 ac
Re: touchpad input driver: testing needed
On Mon, Jul 31, 2017 at 11:02:28PM +0200, Ulf Brosziewski wrote: > for you. As always, a dmesg would be appreciated. The output of > # wsconsctl | grep 'mouse' > could also be of interest here (you must run it as root). This is from a Dell XPS 13 9343. The mouse pointer moves into the wrong (opposite) direction. Only the left soft button is available. mistral ~$ doas wsconsctl | grep mouse wsconsctl: Use explicit arg to view keyboard.map. wsconsctl: mousecfg error: WSMOUSEIO_GETPARAMS (-1) mouse.type=elantech mouse.rawmode=0 mouse.scale=0,1013,0,566,0,0,0 mistral ~$ With the synaptics driver I use this configuration: Section "InputDevice" Identifier "clickpad" Driver "synaptics" Option "Device" "/dev/wsmouse0" Option "AutoServerLayout" "true" Option "ClickPad" "true" Option "EmulateMidButtonTime" "0" Option "SoftButtonAreas""80% 0 82% 0 40% 79% 82% 0" Option "VertTwoFingerScroll""true" Option "TapButton1" "1" EndSection OpenBSD 6.1-current (GENERIC.MP) #40: Wed Aug 2 18:53:06 MDT 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8473636864 (8081MB) avail mem = 8210477056 (7830MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xed7d0 (84 entries) bios0: vendor Dell Inc. version "A12" date 05/09/2017 bios0: Dell Inc. XPS 13 9343 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT FIDT MCFG HPET SSDT UEFI SSDT ASF! SSDT SSDT SSDT SSDT PCCT SSDT SSDT SSDT SLIC MSDM DMAR CSRT BGRT acpi0: wakeup devices PEGP(S4) PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4) PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) RP05(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz, 2195.26 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,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,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,PT,SENSOR,ARAT cpu0: 256KB 64b/line 8-way L2 cache cpu0: TSC frequency 2195263540 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.1.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz, 2194.92 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,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,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,PT,SENSOR,ARAT cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz, 2194.92 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,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,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,PT,SENSOR,ARAT cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 1, core 0, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz, 2194.92 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,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,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,PT,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins acpimadt0: bogus nmi for apid 0 acpimadt0: bogus nmi for apid 2 acpimadt0: bogus nmi for apid 1 acpimadt0: bogus nmi for apid 3 acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PEG0) acpiprt2 at acpi0: bus -1 (PEG1) acpiprt3 at acpi0: bus -1 (PEG2) acpiprt4 at acpi0: bus 1 (RP01) acpiprt5 at acpi0: bus -1 (RP02) acpiprt6 at acpi0: bus -1 (RP03) acpiprt7 at acpi0: bus 2 (RP04) acpiprt8 at acpi0: bus -1 (RP05) acpiprt9 at a
Re: touchpad input driver: testing needed
On my Thinkpad X1 Carbon (first gen, I think) it looks pretty good. The only thing in xorg.conf is your proposed block. Cursor moves: Yes Pad tapping: Yes, honours enable/disable Pad speed/scaling: Honours setting Swapsides: not honoured Regardless of setting, the scroll bar moves in sync with fingers (ie fingers away from me makes scroll bar go up / sends the page down) Looking at `xinput --test /dev/wsmouse0` I see button 4 scrolling up and 5 scrolling down, either way. wsconsctl output: $ wsconsctl mouse wsconsctl: /dev/wsmouse0: Permission denied $ wsconsctl | grep mouse wsconsctl: /dev/wskbd0: Permission denied wsconsctl: /dev/wsmouse0: Permission denied wsconsctl: /dev/ttyC0: Permission denied $ doas wsconsctl | grep mouse wsconsctl: Use explicit arg to view keyboard.map. mouse.type=synaptics mouse.rawmode=0 mouse.scale=1472,5678,1408,4732,0,46,63 mouse.tp.tapping=0 mouse.tp.scaling=0.200 mouse.tp.swapsides=1 mouse.tp.disable=0 mouse1.type=ps2 $ dmesg: OpenBSD 6.1-current (GENERIC.MP) #34: Tue Aug 1 18:56:18 MDT 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8383655936 (7995MB) avail mem = 8123219968 (7746MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xdae9d000 (68 entries) bios0: vendor LENOVO version "G6ET96WW (2.56 )" date 04/29/2013 bios0: LENOVO 34486T7 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP TCPA SSDT SSDT SSDT HPET APIC MCFG ECDT FPDT ASF! UEFI UEFI MSDM SSDT SSDT DMAR UEFI SSDT DBG2 BGRT acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP2(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) i5-3337U CPU @ 1.80GHz, 1796.26 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,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,D EADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT cpu0: 256KB 64b/line 8-way L2 cache cpu0: TSC frequency 1796264010 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 1 (application processor) cpu1: Intel(R) Core(TM) i5-3337U CPU @ 1.80GHz, 1795.92 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,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,D EADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,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) i5-3337U CPU @ 1.80GHz, 1795.92 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,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,D EADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,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) i5-3337U CPU @ 1.80GHz, 1795.92 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,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,D EADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpiec0 at acpi0 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PEG_) acpiprt2 at acpi0: bus 2 (EXP1) acpiprt3 at acpi0: bus 3 (EXP2) acpicpu0 at acpi0: C3(200@87 mwait.1@0x30), C2(500@59 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C3(200@87 mwait.1@0x30), C2(500@59 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0: C3(200@87 mwait.1@0x30), C2(500@59 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpicpu3 at acpi0: C3(200@87 mwait.1@0x30), C2(500@59 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpipwrres0 at acpi0: PUBS, resource for XHCI, EHC1, EHC2 acpitz0 at acpi0: critical temperature is 200 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB "MSFT9000" at acpi0 not configured "MSFT9001" at acpi0 not configured "LEN0071" at acpi0 not configured "LEN0030" at acpi0 not configured "SMO1200" at acpi0 not configured acpibat0 at acpi0: BAT0 model "45N1071" serial 9485 type LiP oem "SMP" acpiac0 at acpi0: A
Re: touchpad input driver: testing needed
No apparent problems here on my ThinkPad x220i. Base pointer speed was slightly slower which I was able to adjust by setting mouse.tp.scaling. This did, however, not affect the two-finger-scrolling, which required more mileage on my trackpad to scroll compared to the synaptics driver. Nice work! wsconsctl: mouse.type=synaptics mouse.rawmode=0 mouse.scale=1472,5472,1408,4448,0,75,129 mouse.tp.tapping=0 mouse.tp.scaling=0.200 mouse.tp.swapsides=0 mouse.tp.disable=0 dmesg: OpenBSD 6.1-current (GENERIC.MP) #34: Tue Aug 1 18:56:18 MDT 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8451125248 (8059MB) avail mem = 8188628992 (7809MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xdae9c000 (66 entries) bios0: vendor LENOVO version "8DET73WW (1.43 )" date 10/12/2016 bios0: LENOVO 4290W1A acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SLIC SSDT SSDT SSDT HPET APIC MCFG ECDT ASF! TCPA SSDT SSDT UEFI UEFI UEFI acpi0: wakeup devices LID_(S3) SLPB(S3) IGBE(S4) EXP4(S4) EXP7(S4) 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) i3-2310M CPU @ 2.10GHz, 2093.51 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,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT cpu0: 256KB 64b/line 8-way L2 cache cpu0: TSC frequency 2093506380 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 1 (application processor) cpu1: Intel(R) Core(TM) i3-2310M CPU @ 2.10GHz, 2093.20 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,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,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) i3-2310M CPU @ 2.10GHz, 2093.20 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,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,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) i3-2310M CPU @ 2.10GHz, 2093.20 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,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpiec0 at acpi0 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 5 (EXP4) acpiprt5 at acpi0: bus 13 (EXP5) acpiprt6 at acpi0: bus -1 (EXP7) acpicpu0 at acpi0: C3(200@109 io@0x416), C2(500@80 io@0x414), C1(1000@1 halt), PSS acpicpu1 at acpi0: C3(200@109 io@0x416), C2(500@80 io@0x414), C1(1000@1 halt), PSS acpicpu2 at acpi0: C3(200@109 io@0x416), C2(500@80 io@0x414), C1(1000@1 halt), PSS acpicpu3 at acpi0: C3(200@109 io@0x416), C2(500@80 io@0x414), C1(1000@1 halt), PSS acpipwrres0 at acpi0: PUBS, resource for EHC1, EHC2 acpitz0 at acpi0: critical temperature is 99 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB "PNP0303" at acpi0 not configured "LEN0020" at acpi0 not configured "SMO1200" at acpi0 not configured acpibat0 at acpi0: BAT0 model "42T4861" serial 5714 type LION oem "SANYO" acpiac0 at acpi0: AC unit offline acpithinkpad0 at acpi0 "PNP0C14" at acpi0 not configured "PNP0C14" at acpi0 not configured acpidock0 at acpi0: GDCK not docked (0) acpivideo0 at acpi0: VID_ acpivout at acpivideo0 not configured acpivideo1 at acpi0: VID_ cpu0: Enhanced SpeedStep 2093 MHz: speeds: 2100, 2000, 1900, 1800, 1700, 1600, 1500, 1400, 1300, 1200, 1100, 1000, 900, 800 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Core 2G Host" rev 0x09 inteldrm0 at pci0 dev 2 function 0 "Intel HD Graphics 3000" rev 0x09 drm0 at inteldrm0 inteldrm0: msi inteldrm0: 1366x768, 32bpp wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std,
Re: touchpad input driver: testing needed
Lenovo T430 here, everything seems to be in order. I didn't have to make any changes to the defaults, and didn't have any synaptics config before. It seems to behave the same, so I don't see any difference. 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 mouse1.type=ps2 OpenBSD 6.1-current (GENERIC.MP) #34: Tue Aug 1 18:56:18 MDT 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8256528384 (7874MB) avail mem = 738560 (7629MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xdae9c000 (68 entries) bios0: vendor LENOVO version "G1ETB1WW (2.71 )" date 08/08/2016 bios0: LENOVO 2347H76 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 DMAR 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) i5-3320M CPU @ 2.60GHz, 2594.55 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,ES T,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,SENSOR,ARAT cpu0: 256KB 64b/line 8-way L2 cache cpu0: TSC frequency 2594554920 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 1 (application processor) cpu1: Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz, 2594.12 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,ES T,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,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) i5-3320M CPU @ 2.60GHz, 2594.12 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,ES T,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,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) i5-3320M CPU @ 2.60GHz, 2594.12 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,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,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpiec0 at acpi0 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) acpicpu0 at acpi0: C3(200@87 mwait.1@0x30), C2(500@59 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C3(200@87 mwait.1@0x30), C2(500@59 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0: C3(200@87 mwait.1@0x30), C2(500@59 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpicpu3 at acpi0: C3(200@87 mwait.1@0x30), C2(500@59 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpipwrres0 at acpi0: PUBS, resource for XHCI, EHC1, EHC2 acpitz0 at acpi0: critical temperature is 200 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB "LEN0071" at acpi0 not configured "LEN0015" at acpi0 not configured "SMO1200" at acpi0 not configured acpibat0 at acpi0: BAT0 model "45N1011" serial 49124 type LION oem "LGC" acpiac0 at acpi0: AC unit offline "LEN0078" at acpi0 not configured acpithinkpad0 at acpi0 "PNP0C14" at acpi0 not configured "PNP0C14" at acpi0 not configured "PNP0C14" at acpi0 not configured acpivideo0 at acpi0: VID_ acpivout at acpivideo0 not configured acpivideo1 at acpi0: VID_ cpu0: Enhanced SpeedStep 2594 MHz: speeds: 2601, 2600, 2500, 2400, 2300, 2200, 2100, 2000, 1900, 1800, 1700, 1600, 1500, 1400, 1300, 1200 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Core 3G Host" rev 0x09 inteldrm0 at pci0 dev 2 function 0 "Intel HD Graphics 4000" rev 0x09 drm0 at inteldrm0 inteldrm0: msi inteldrm0: 1366x76
Re: touchpad input driver: testing needed
a[0]=876 a[1]=497 > > button press 3 > > button release 3 > > button press 3 > > button release 3 > > button press 3 > > button release 3 > > button press 1 > > button release 1 > > button press 1 > > button release 1 > > button press 1 > > button release 1 > > button press 1 > > button release 1 > > button press 3 > > button release 3 > > button press 1 > > button release 1 > > button press 1 > > button release 1 > > button press 3 > > button release 3 > > button press 3 > > button release 3 > > > > > > > > On Tue, Aug 1, 2017 at 9:53 PM, Ulf Brosziewski < > ulf.brosziew...@t-online.de > >> wrote: > > > >> Hi, > >> > >> thanks for testing! Does "NOT OK" mean that two-finger > >> scrolling works badly, or that it doesn't work at all? > >> If possible, could you record the output of > >> $ xinput --test /dev/wsmouse0 > >> for a short period of time and perform the scroll gesture? > >> > >> Ulf > >> > >> On 08/01/2017 11:09 AM, Olivier Antoine wrote: > >>> Mouse move: OK > >>> Mouse tapping: OK > >>> Two-fingers scrolling: NOT OK > >>> > >>> Machine Lenovo Thinkpad E130 > >>> > >>> # wsconsctl | grep 'mouse' > >>> mouse.type=synaptics > >>> mouse.rawmode=0 > >>> mouse.scale=1472,5768,1408,5236,0,66,175 > >>> mouse.tp.tapping=1 > >>> mouse.tp.scaling=0.160 > >>> mouse.tp.swapsides=0 > >>> mouse.tp.disable=0 > >>> mouse1.type=ps2 > >>> > >>> > >>> > >>> On Mon, Jul 31, 2017 at 11:02 PM, Ulf Brosziewski < > >>> ulf.brosziew...@t-online.de> wrote: > >>> > >>>> In the long run the synaptics driver, which handles touchpad inputs in > >>>> X, may be a dead end of the input framework, and it's time to prepare > >>>> an alternative. The kernel contains an internal touchpad input driver > >>>> now, it's a part of wsmouse(4). It provides standard features - > >>>> two-finger/edge scrolling, software buttons for clickpads, tapping - > >>>> and various kinds of plankton required for usability. > >>>> > >>>> If you have a new snapshot (from July 27 or later) on a laptop with a > >>>> Synaptics, Apple, Alps, or Elantech-4 touchpad, you could help with > >>>> tests, more tests, and tests. In order to activate the driver, add > the > >>>> following entry to /etc/xorg.conf and restart X (if the file isn't > >>>> present, simply create it with this content): > >>>> > >>>> Section "InputClass" > >>>> Identifier "wsmouse touchpad" > >>>> Driver "ws" > >>>> MatchIsTouchpad "on" > >>>> EndSection > >>>> > >>>> While I dont't expect bugs in the input processing part of the > >>>> driver ;-), it is difficult to assess how well the automatic > >>>> configuration covers the zoo of models out there, presumably it will > >>>> need some more fine-grained distinctions of hardware properties. I > >>>> would like to know where it works, works only halfway, or doesn't work > >>>> for you. As always, a dmesg would be appreciated. The output of > >>>> # wsconsctl | grep 'mouse' > >>>> could also be of interest here (you must run it as root). > >>>> > >>>> For now, X will treat the device like a mouse, please don't look for > >>>> touchpad-specific configuration options there. Tapping can be enabled > >>>> by the command > >>>> # wsconsctl mouse.tp.tapping=1 > >>>> If there is more than one wsmouse device, you should look up which one > >>>> has the "tp" fields and if it's not the first one (wsmouse0), add the > >>>> index to the prefix, e.g. > >>>> # wsconsctl mouse2.tp.tapping=1 > >>>> > >>>> The base speed of the pointer can be adjusted by increasing or > >>>> decreasing the value of > >>>> # wsconsctl mouse.tp.scaling > >>>> Please don't confuse it with the 'mouse.scale' field. > >>>> > >>>> # wsconsctl mouse.tp.swapsides=1 > >>>> will invert the order of software buttons areas (swapping external > >>>> buttons must still be configured in X). If edge scrolling is > >>>> enabled, the scroll area will be at the left edge of the touchpad. > >>>> > >>>> If you are using an external mouse device or a trackpoint, the command > >>>> # wsconsctl mouse.tp.disable=1 > >>>> may be helpful. It will disable pointer movement, scrolling, and > >>>> tapping. External buttons and software buttons remain enabled. > >>>> > >>>> > >>> > >> > >> > > > >
Re: touchpad input driver: testing needed
On Tue, Aug 01, 2017 at 10:12:05PM +0200, Ulf Brosziewski wrote: > I have the impression that multi-finger clicks are popular > among Mac users, is it correct? However, if the new driver > works it should offer software button areas at the bottom > edge of the touchpad, as elsewhere. Are they missing? > Are they too small? Or is it "simply" not your habit? Anyway, > there must be some bug or misconfiguration, the "tp" fields > are missing in the wsconsctl output: You are correct. Having used Macs for years and years, I am very accustomed to multi-finger clicks and they are my "habit" now. I was not aware of the software button areas. If I hold down a click in the middle of the touchpad but at the bottom edge for about one second or a little more, when I release that click, I get a button2 which allows paste. That works well enough. I have not yet figured out how to get button3 except for Ctrl click. > > # wsconsctl | grep mouse > > mouse.type=usb > > mouse.rawmode=1 > > mouse.scale=0,0,0,0,0,0,0 > > mouse1.type=elantech > > mouse1.rawmode=0 > > mouse1.scale=-4620,5140,-150,6600,0,0,0 > > > > Would you mind to report the output of the following command? > # wsconsctl mouse1.tp.param=64,65 Here is the output: mouse1.tp.param -> 64:1,65:1 > And special thanks again for all your work, Thank you for your development. I am very excited to see these changes in OpenBSD. Bryan
Re: touchpad input driver: testing needed
The event codes look wrong, they are for right-clicks and left-clicks, if I'm not mistaken. Is there a "ButtonMapping" defined for X somewhere (in your xorg.conf, or by a script), or a "ZAxisMapping"? Could you have a look at the output of $ xmodmap -pp ? On 08/02/2017 12:22 AM, Olivier Antoine wrote: > Two-fingers scrolling doesn't work at all. Under a firefox window, it open > context menu, or act like pressing button. > > $ xinput --test /dev/wsmouse0 > button press 3 > button release 3 > button press 3 > button release 3 > button press 3 > button release 3 > motion a[0]=876 a[1]=497 > button press 3 > button release 3 > button press 3 > button release 3 > button press 3 > button release 3 > button press 1 > button release 1 > button press 1 > button release 1 > button press 1 > button release 1 > button press 1 > button release 1 > button press 3 > button release 3 > button press 1 > button release 1 > button press 1 > button release 1 > button press 3 > button release 3 > button press 3 > button release 3 > > > > On Tue, Aug 1, 2017 at 9:53 PM, Ulf Brosziewski > wrote: > >> Hi, >> >> thanks for testing! Does "NOT OK" mean that two-finger >> scrolling works badly, or that it doesn't work at all? >> If possible, could you record the output of >> $ xinput --test /dev/wsmouse0 >> for a short period of time and perform the scroll gesture? >> >> Ulf >> >> On 08/01/2017 11:09 AM, Olivier Antoine wrote: >>> Mouse move: OK >>> Mouse tapping: OK >>> Two-fingers scrolling: NOT OK >>> >>> Machine Lenovo Thinkpad E130 >>> >>> # wsconsctl | grep 'mouse' >>> mouse.type=synaptics >>> mouse.rawmode=0 >>> mouse.scale=1472,5768,1408,5236,0,66,175 >>> mouse.tp.tapping=1 >>> mouse.tp.scaling=0.160 >>> mouse.tp.swapsides=0 >>> mouse.tp.disable=0 >>> mouse1.type=ps2 >>> >>> >>> >>> On Mon, Jul 31, 2017 at 11:02 PM, Ulf Brosziewski < >>> ulf.brosziew...@t-online.de> wrote: >>> >>>> In the long run the synaptics driver, which handles touchpad inputs in >>>> X, may be a dead end of the input framework, and it's time to prepare >>>> an alternative. The kernel contains an internal touchpad input driver >>>> now, it's a part of wsmouse(4). It provides standard features - >>>> two-finger/edge scrolling, software buttons for clickpads, tapping - >>>> and various kinds of plankton required for usability. >>>> >>>> If you have a new snapshot (from July 27 or later) on a laptop with a >>>> Synaptics, Apple, Alps, or Elantech-4 touchpad, you could help with >>>> tests, more tests, and tests. In order to activate the driver, add the >>>> following entry to /etc/xorg.conf and restart X (if the file isn't >>>> present, simply create it with this content): >>>> >>>> Section "InputClass" >>>> Identifier "wsmouse touchpad" >>>> Driver "ws" >>>> MatchIsTouchpad "on" >>>> EndSection >>>> >>>> While I dont't expect bugs in the input processing part of the >>>> driver ;-), it is difficult to assess how well the automatic >>>> configuration covers the zoo of models out there, presumably it will >>>> need some more fine-grained distinctions of hardware properties. I >>>> would like to know where it works, works only halfway, or doesn't work >>>> for you. As always, a dmesg would be appreciated. The output of >>>> # wsconsctl | grep 'mouse' >>>> could also be of interest here (you must run it as root). >>>> >>>> For now, X will treat the device like a mouse, please don't look for >>>> touchpad-specific configuration options there. Tapping can be enabled >>>> by the command >>>> # wsconsctl mouse.tp.tapping=1 >>>> If there is more than one wsmouse device, you should look up which one >>>> has the "tp" fields and if it's not the first one (wsmouse0), add the >>>> index to the prefix, e.g. >>>> # wsconsctl mouse2.tp.tapping=1 >>>> >>>> The base speed of the pointer can be adjusted by increasing or >>>> decreasing the value of >>>> # wsconsctl mouse.tp.scaling >>>> Please don't confuse it with the 'mouse.scale' field. >>>> >>>> # wsconsctl mouse.tp.swapsides=1 >>>> will invert the order of software buttons areas (swapping external >>>> buttons must still be configured in X). If edge scrolling is >>>> enabled, the scroll area will be at the left edge of the touchpad. >>>> >>>> If you are using an external mouse device or a trackpoint, the command >>>> # wsconsctl mouse.tp.disable=1 >>>> may be helpful. It will disable pointer movement, scrolling, and >>>> tapping. External buttons and software buttons remain enabled. >>>> >>>> >>> >> >> >
Re: touchpad input driver: testing needed
Two-fingers scrolling doesn't work at all. Under a firefox window, it open context menu, or act like pressing button. $ xinput --test /dev/wsmouse0 button press 3 button release 3 button press 3 button release 3 button press 3 button release 3 motion a[0]=876 a[1]=497 button press 3 button release 3 button press 3 button release 3 button press 3 button release 3 button press 1 button release 1 button press 1 button release 1 button press 1 button release 1 button press 1 button release 1 button press 3 button release 3 button press 1 button release 1 button press 1 button release 1 button press 3 button release 3 button press 3 button release 3 On Tue, Aug 1, 2017 at 9:53 PM, Ulf Brosziewski wrote: > Hi, > > thanks for testing! Does "NOT OK" mean that two-finger > scrolling works badly, or that it doesn't work at all? > If possible, could you record the output of > $ xinput --test /dev/wsmouse0 > for a short period of time and perform the scroll gesture? > > Ulf > > On 08/01/2017 11:09 AM, Olivier Antoine wrote: > > Mouse move: OK > > Mouse tapping: OK > > Two-fingers scrolling: NOT OK > > > > Machine Lenovo Thinkpad E130 > > > > # wsconsctl | grep 'mouse' > > mouse.type=synaptics > > mouse.rawmode=0 > > mouse.scale=1472,5768,1408,5236,0,66,175 > > mouse.tp.tapping=1 > > mouse.tp.scaling=0.160 > > mouse.tp.swapsides=0 > > mouse.tp.disable=0 > > mouse1.type=ps2 > > > > > > > > On Mon, Jul 31, 2017 at 11:02 PM, Ulf Brosziewski < > > ulf.brosziew...@t-online.de> wrote: > > > >> In the long run the synaptics driver, which handles touchpad inputs in > >> X, may be a dead end of the input framework, and it's time to prepare > >> an alternative. The kernel contains an internal touchpad input driver > >> now, it's a part of wsmouse(4). It provides standard features - > >> two-finger/edge scrolling, software buttons for clickpads, tapping - > >> and various kinds of plankton required for usability. > >> > >> If you have a new snapshot (from July 27 or later) on a laptop with a > >> Synaptics, Apple, Alps, or Elantech-4 touchpad, you could help with > >> tests, more tests, and tests. In order to activate the driver, add the > >> following entry to /etc/xorg.conf and restart X (if the file isn't > >> present, simply create it with this content): > >> > >> Section "InputClass" > >> Identifier "wsmouse touchpad" > >> Driver "ws" > >> MatchIsTouchpad "on" > >> EndSection > >> > >> While I dont't expect bugs in the input processing part of the > >> driver ;-), it is difficult to assess how well the automatic > >> configuration covers the zoo of models out there, presumably it will > >> need some more fine-grained distinctions of hardware properties. I > >> would like to know where it works, works only halfway, or doesn't work > >> for you. As always, a dmesg would be appreciated. The output of > >> # wsconsctl | grep 'mouse' > >> could also be of interest here (you must run it as root). > >> > >> For now, X will treat the device like a mouse, please don't look for > >> touchpad-specific configuration options there. Tapping can be enabled > >> by the command > >> # wsconsctl mouse.tp.tapping=1 > >> If there is more than one wsmouse device, you should look up which one > >> has the "tp" fields and if it's not the first one (wsmouse0), add the > >> index to the prefix, e.g. > >> # wsconsctl mouse2.tp.tapping=1 > >> > >> The base speed of the pointer can be adjusted by increasing or > >> decreasing the value of > >> # wsconsctl mouse.tp.scaling > >> Please don't confuse it with the 'mouse.scale' field. > >> > >> # wsconsctl mouse.tp.swapsides=1 > >> will invert the order of software buttons areas (swapping external > >> buttons must still be configured in X). If edge scrolling is > >> enabled, the scroll area will be at the left edge of the touchpad. > >> > >> If you are using an external mouse device or a trackpoint, the command > >> # wsconsctl mouse.tp.disable=1 > >> may be helpful. It will disable pointer movement, scrolling, and > >> tapping. External buttons and software buttons remain enabled. > >> > >> > > > >
Re: touchpad input driver: testing needed
Hi Bryan, I have the impression that multi-finger clicks are popular among Mac users, is it correct? However, if the new driver works it should offer software button areas at the bottom edge of the touchpad, as elsewhere. Are they missing? Are they too small? Or is it "simply" not your habit? Anyway, there must be some bug or misconfiguration, the "tp" fields are missing in the wsconsctl output: > > # wsconsctl | grep mouse > mouse.type=usb > mouse.rawmode=1 > mouse.scale=0,0,0,0,0,0,0 > mouse1.type=elantech > mouse1.rawmode=0 > mouse1.scale=-4620,5140,-150,6600,0,0,0 > Would you mind to report the output of the following command? # wsconsctl mouse1.tp.param=64,65 And special thanks again for all your work, Ulf On 08/01/2017 05:13 PM, Bryan Vyhmeister wrote: > On Mon, Jul 31, 2017 at 05:37:00PM -0700, Bryan Vyhmeister wrote: >> On Mon, Jul 31, 2017 at 08:09:31PM -0400, Ted Unangst wrote: >>> Bryan Vyhmeister wrote: On Mon, Jul 31, 2017 at 11:02:28PM +0200, Ulf Brosziewski wrote: > for you. As always, a dmesg would be appreciated. The output of > # wsconsctl | grep 'mouse' > could also be of interest here (you must run it as root). This report is from a MacBookAir7,2 which is a 2015 13-inch MacBook Air. Anything more than a regular click is not working as can be seen from the wsconsctl output. I was using synclient to configure previously which did allow the other settings. >>> >>> Can you also share your synclient settings? >> >> Sure. I was using synclient(1) with the following settings but >> synclient(1) no longer works with this driver. >> >> synclient ClickFinger2=2 ClickFinger3=3 PalmDetect=0 PalmMinWidth=4 >> PalmMinZ=100 > > I wanted to clarify this for the record. Regular click is working fine > as is two finger scrolling on the MacBook Air. What is not working is > multi-finger click but that is not currently part of the driver which is > probably why my synclient settings are significant. I noticed this on > the MacBook Air because there are no separate touchpad buttons as there > are on everything else I tested. I would love to see multi-finger click > as part of the driver since it is essential on any touchpad without > separate buttons which seems to be the more common scenario these days > for laptops. Thanks again. > > Bryan > >
Re: touchpad input driver: testing needed
Hi, thanks for testing! Does "NOT OK" mean that two-finger scrolling works badly, or that it doesn't work at all? If possible, could you record the output of $ xinput --test /dev/wsmouse0 for a short period of time and perform the scroll gesture? Ulf On 08/01/2017 11:09 AM, Olivier Antoine wrote: > Mouse move: OK > Mouse tapping: OK > Two-fingers scrolling: NOT OK > > Machine Lenovo Thinkpad E130 > > # wsconsctl | grep 'mouse' > mouse.type=synaptics > mouse.rawmode=0 > mouse.scale=1472,5768,1408,5236,0,66,175 > mouse.tp.tapping=1 > mouse.tp.scaling=0.160 > mouse.tp.swapsides=0 > mouse.tp.disable=0 > mouse1.type=ps2 > > > > On Mon, Jul 31, 2017 at 11:02 PM, Ulf Brosziewski < > ulf.brosziew...@t-online.de> wrote: > >> In the long run the synaptics driver, which handles touchpad inputs in >> X, may be a dead end of the input framework, and it's time to prepare >> an alternative. The kernel contains an internal touchpad input driver >> now, it's a part of wsmouse(4). It provides standard features - >> two-finger/edge scrolling, software buttons for clickpads, tapping - >> and various kinds of plankton required for usability. >> >> If you have a new snapshot (from July 27 or later) on a laptop with a >> Synaptics, Apple, Alps, or Elantech-4 touchpad, you could help with >> tests, more tests, and tests. In order to activate the driver, add the >> following entry to /etc/xorg.conf and restart X (if the file isn't >> present, simply create it with this content): >> >> Section "InputClass" >> Identifier "wsmouse touchpad" >> Driver "ws" >> MatchIsTouchpad "on" >> EndSection >> >> While I dont't expect bugs in the input processing part of the >> driver ;-), it is difficult to assess how well the automatic >> configuration covers the zoo of models out there, presumably it will >> need some more fine-grained distinctions of hardware properties. I >> would like to know where it works, works only halfway, or doesn't work >> for you. As always, a dmesg would be appreciated. The output of >> # wsconsctl | grep 'mouse' >> could also be of interest here (you must run it as root). >> >> For now, X will treat the device like a mouse, please don't look for >> touchpad-specific configuration options there. Tapping can be enabled >> by the command >> # wsconsctl mouse.tp.tapping=1 >> If there is more than one wsmouse device, you should look up which one >> has the "tp" fields and if it's not the first one (wsmouse0), add the >> index to the prefix, e.g. >> # wsconsctl mouse2.tp.tapping=1 >> >> The base speed of the pointer can be adjusted by increasing or >> decreasing the value of >> # wsconsctl mouse.tp.scaling >> Please don't confuse it with the 'mouse.scale' field. >> >> # wsconsctl mouse.tp.swapsides=1 >> will invert the order of software buttons areas (swapping external >> buttons must still be configured in X). If edge scrolling is >> enabled, the scroll area will be at the left edge of the touchpad. >> >> If you are using an external mouse device or a trackpoint, the command >> # wsconsctl mouse.tp.disable=1 >> may be helpful. It will disable pointer movement, scrolling, and >> tapping. External buttons and software buttons remain enabled. >> >> >
Re: touchpad input driver: testing needed
On Mon, Jul 31, 2017 at 05:37:00PM -0700, Bryan Vyhmeister wrote: > On Mon, Jul 31, 2017 at 08:09:31PM -0400, Ted Unangst wrote: > > Bryan Vyhmeister wrote: > > > On Mon, Jul 31, 2017 at 11:02:28PM +0200, Ulf Brosziewski wrote: > > > > for you. As always, a dmesg would be appreciated. The output of > > > > # wsconsctl | grep 'mouse' > > > > could also be of interest here (you must run it as root). > > > > > > This report is from a MacBookAir7,2 which is a 2015 13-inch MacBook Air. > > > Anything more than a regular click is not working as can be seen from > > > the wsconsctl output. I was using synclient to configure previously > > > which did allow the other settings. > > > > Can you also share your synclient settings? > > Sure. I was using synclient(1) with the following settings but > synclient(1) no longer works with this driver. > > synclient ClickFinger2=2 ClickFinger3=3 PalmDetect=0 PalmMinWidth=4 > PalmMinZ=100 I wanted to clarify this for the record. Regular click is working fine as is two finger scrolling on the MacBook Air. What is not working is multi-finger click but that is not currently part of the driver which is probably why my synclient settings are significant. I noticed this on the MacBook Air because there are no separate touchpad buttons as there are on everything else I tested. I would love to see multi-finger click as part of the driver since it is essential on any touchpad without separate buttons which seems to be the more common scenario these days for laptops. Thanks again. Bryan
Re: touchpad input driver: testing needed
Mouse move: OK Mouse tapping: OK Two-fingers scrolling: NOT OK Machine Lenovo Thinkpad E130 # wsconsctl | grep 'mouse' mouse.type=synaptics mouse.rawmode=0 mouse.scale=1472,5768,1408,5236,0,66,175 mouse.tp.tapping=1 mouse.tp.scaling=0.160 mouse.tp.swapsides=0 mouse.tp.disable=0 mouse1.type=ps2 On Mon, Jul 31, 2017 at 11:02 PM, Ulf Brosziewski < ulf.brosziew...@t-online.de> wrote: > In the long run the synaptics driver, which handles touchpad inputs in > X, may be a dead end of the input framework, and it's time to prepare > an alternative. The kernel contains an internal touchpad input driver > now, it's a part of wsmouse(4). It provides standard features - > two-finger/edge scrolling, software buttons for clickpads, tapping - > and various kinds of plankton required for usability. > > If you have a new snapshot (from July 27 or later) on a laptop with a > Synaptics, Apple, Alps, or Elantech-4 touchpad, you could help with > tests, more tests, and tests. In order to activate the driver, add the > following entry to /etc/xorg.conf and restart X (if the file isn't > present, simply create it with this content): > > Section "InputClass" > Identifier "wsmouse touchpad" > Driver "ws" > MatchIsTouchpad "on" > EndSection > > While I dont't expect bugs in the input processing part of the > driver ;-), it is difficult to assess how well the automatic > configuration covers the zoo of models out there, presumably it will > need some more fine-grained distinctions of hardware properties. I > would like to know where it works, works only halfway, or doesn't work > for you. As always, a dmesg would be appreciated. The output of > # wsconsctl | grep 'mouse' > could also be of interest here (you must run it as root). > > For now, X will treat the device like a mouse, please don't look for > touchpad-specific configuration options there. Tapping can be enabled > by the command > # wsconsctl mouse.tp.tapping=1 > If there is more than one wsmouse device, you should look up which one > has the "tp" fields and if it's not the first one (wsmouse0), add the > index to the prefix, e.g. > # wsconsctl mouse2.tp.tapping=1 > > The base speed of the pointer can be adjusted by increasing or > decreasing the value of > # wsconsctl mouse.tp.scaling > Please don't confuse it with the 'mouse.scale' field. > > # wsconsctl mouse.tp.swapsides=1 > will invert the order of software buttons areas (swapping external > buttons must still be configured in X). If edge scrolling is > enabled, the scroll area will be at the left edge of the touchpad. > > If you are using an external mouse device or a trackpoint, the command > # wsconsctl mouse.tp.disable=1 > may be helpful. It will disable pointer movement, scrolling, and > tapping. External buttons and software buttons remain enabled. > > dmesg Description: Binary data
Re: touchpad input driver: testing needed
Feedback report --- Hardware: Thinkpad X220. Results:Excellent! wsconsctl configuration changes:None. mouse.type=synaptics mouse.rawmode=0 mouse.scale=1472,5768,1408,5062,0,65,136 mouse.tp.tapping=0 mouse.tp.scaling=0.163 mouse.tp.swapsides=0 mouse.tp.disable=0 mouse1.type=ps2 mouse2.type=usb OpenBSD 6.1-current (GENERIC.MP) #23: Sun Jul 30 17:07:49 MDT 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP RTC BIOS diagnostic error 80 real mem = 8451125248 (8059MB) avail mem = 8188645376 (7809MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xdae9c000 (66 entries) bios0: vendor LENOVO version "8DET73WW (1.43 )" date 10/12/2016 bios0: LENOVO 4291G26 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SLIC SSDT SSDT SSDT HPET APIC MCFG ECDT ASF! TCPA SSDT SSDT DMAR UEFI UEFI UEFI acpi0: wakeup devices LID_(S3) SLPB(S3) IGBE(S4) EXP4(S4) EXP7(S4) 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) i5-2520M CPU @ 2.50GHz, 2492.30 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,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT cpu0: 256KB 64b/line 8-way L2 cache cpu0: TSC frequency 2492296960 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 1 (application processor) cpu1: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz, 2491.91 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,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,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) i5-2520M CPU @ 2.50GHz, 2491.91 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,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,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) i5-2520M CPU @ 2.50GHz, 2491.91 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,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpiec0 at acpi0 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 -1 (EXP4) acpiprt5 at acpi0: bus 13 (EXP5) acpiprt6 at acpi0: bus -1 (EXP7) acpicpu0 at acpi0: C3(350@104 io@0x415), C1(1000@1 halt), PSS acpicpu1 at acpi0: C3(350@104 io@0x415), C1(1000@1 halt), PSS acpicpu2 at acpi0: C3(350@104 io@0x415), C1(1000@1 halt), PSS acpicpu3 at acpi0: C3(350@104 io@0x415), C1(1000@1 halt), PSS acpipwrres0 at acpi0: PUBS, resource for EHC1, EHC2 acpitz0 at acpi0: critical temperature is 99 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB "PNP0303" at acpi0 not configured "LEN0020" at acpi0 not configured "SMO1200" at acpi0 not configured acpibat0 at acpi0: BAT0 model "42T4875" serial94 type LION oem "Panasonic" acpiac0 at acpi0: AC unit online acpithinkpad0 at acpi0 "PNP0C14" at acpi0 not configured "PNP0C14" at acpi0 not configured acpidock0 at acpi0: GDCK not docked (0) acpivideo0 at acpi0: VID_ acpivout at acpivideo0 not configured acpivideo1 at acpi0: VID_ cpu0: Enhanced SpeedStep 2492 MHz: speeds: 2501, 2500, 2200, 2000, 1800, 1600, 1400, 1200, 1000, 800 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Core 2G Host" rev 0x09 inteldrm0 at pci0 dev 2 function 0 "Intel HD Graphics 3000" rev 0x09 drm0 at inteldrm0 inteldrm0: msi inteldrm0: 1366x768, 32bpp wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) "Intel 6 Series MEI" rev 0x04 at pci0 dev 22 function 0 not configured em0 at pci0 dev 25 function 0 "Intel 82579LM" rev
Re: touchpad input driver: testing needed
On Mon, Jul 31, 2017 at 11:02:28PM +0200, Ulf Brosziewski wrote: > for you. As always, a dmesg would be appreciated. The output of > # wsconsctl | grep 'mouse' > could also be of interest here (you must run it as root). Here is another report from a Lenovo N22. This system has a Synaptics touchpad as well and works perfectly with the new driver. # wsconsctl | grep mouse mouse.type=synaptics mouse.rawmode=0 mouse.scale=1472,5788,1408,4966,0,58,94 mouse.tp.tapping=0 mouse.tp.scaling=0.164 mouse.tp.swapsides=0 mouse.tp.disable=0 Bryan OpenBSD 6.1-current (GENERIC.MP) #27: Mon Jul 31 12:56:47 MDT 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 4117872640 (3927MB) avail mem = 3986718720 (3802MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xe0840 (61 entries) bios0: vendor Lenovo version "0YCN17WW" date 03/31/2016 bios0: LENOVO 80S6 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP UEFI MCFG SSDT SSDT SSDT SSDT SSDT APIC UEFI MSDM BATB FPDT UEFI BGRT tCSR acpi0: wakeup devices XHC1(S4) BRC1(S0) PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimcfg0 at acpi0 addr 0xe000, bus 0-63 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Celeron(R) CPU N3050 @ 1.60GHz, 1600.36 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,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT cpu0: 1MB 64b/line 16-way L2 cache cpu0: TSC frequency 1600363400 Hz cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 80MHz cpu0: mwait min=64, max=64, C-substates=0.2.0.0.0.0.3.3, IBE cpu1 at mainbus0: apid 4 (application processor) cpu1: Intel(R) Celeron(R) CPU N3050 @ 1.60GHz, 1600.01 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,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT cpu1: 1MB 64b/line 16-way L2 cache cpu1: smt 0, core 2, package 0 ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 115 pins acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (RP01) acpiprt2 at acpi0: bus -1 (RP02) acpiprt3 at acpi0: bus 2 (RP03) acpiprt4 at acpi0: bus -1 (RP04) acpiec0 at acpi0 acpicpu0 at acpi0 C2: state 6: substate 8 >= num 3 C3: state 7: substate 4 >= num 3: C1(1000@1 mwait.1), PSS acpicpu1 at acpi0 C2: state 6: substate 8 >= num 3 C3: state 7: substate 4 >= num 3: C1(1000@1 mwait.1), PSS acpipwrres0 at acpi0: CLK0 acpipwrres1 at acpi0: CLK1 acpipwrres2 at acpi0: ID3C, resource for ISP3 acpipwrres3 at acpi0: USBC, resource for XHC1 acpipwrres4 at acpi0: FN00, resource for FAN0 acpitz0 at acpi0: critical temperature is 90 degC acpibat0 at acpi0: BAT1 model "Harris Beach" serial 123456789 type LION oem "Intel SR 1" "VPC2004" at acpi0 not configured "MSFT0001" at acpi0 not configured "SYN2F02" at acpi0 not configured sdhc0 at acpi0: SDHA addr 0x91319000/0x1000 irq 45 sdhc0: SDHC 3.0, 200 MHz base clock sdmmc0 at sdhc0: 8-bit, sd high-speed, mmc high-speed, dma sdhc1 at acpi0: SDHB addr 0x91317000/0x1000 irq 46 sdhc1: SDHC 3.0, 200 MHz base clock sdmmc1 at sdhc1: 4-bit, sd high-speed, mmc high-speed, dma acpiac0 at acpi0: AC unit online acpibtn0 at acpi0: LID0 acpibtn1 at acpi0: PWRB "INT3400" at acpi0 not configured "INT3403" at acpi0 not configured "PNP0C0B" at acpi0 not configured acpivideo0 at acpi0: GFX0 acpivout0 at acpivideo0: DD1F cpu0: Enhanced SpeedStep 1600 MHz: speeds: 1601, 1600, 1520, 1440, 1360, 1280, 1200, 1120, 1040, 960, 880, 800, 720, 640, 560, 480 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Braswell Host" rev 0x21 inteldrm0 at pci0 dev 2 function 0 "Intel HD Graphics" rev 0x21 drm0 at inteldrm0 inteldrm0: msi inteldrm0: 1366x768, 32bpp wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) "Intel Braswell Power" rev 0x21 at pci0 dev 11 function 0 not configured sdhc2 at pci0 dev 18 function 0 vendor "Intel", unknown product 0x2296 rev 0x21: apic 1 int 18 sdhc2: SDHC 3.0, 200 MHz base clock sdmmc2 at sdhc2: 4-bit, sd high-speed, mmc high-speed, dma ahci0 at pci0 dev 19 function 0 "Intel Braswell AHCI" rev 0x21: msi, AHCI 1.3.1 ahci0: PHY offline on port 0 ahci0: PHY offline on port 1 scsibus1 at ahci0: 32 targets xhci0 at pci0 dev 20 function 0 "Intel Braswell xHCI" rev 0x21: 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 Braswell TXE" rev 0x21 at pci0 dev 26 function
Re: touchpad input driver: testing needed
On Mon, Jul 31, 2017 at 08:09:31PM -0400, Ted Unangst wrote: > Bryan Vyhmeister wrote: > > On Mon, Jul 31, 2017 at 11:02:28PM +0200, Ulf Brosziewski wrote: > > > for you. As always, a dmesg would be appreciated. The output of > > > # wsconsctl | grep 'mouse' > > > could also be of interest here (you must run it as root). > > > > This report is from a MacBookAir7,2 which is a 2015 13-inch MacBook Air. > > Anything more than a regular click is not working as can be seen from > > the wsconsctl output. I was using synclient to configure previously > > which did allow the other settings. > > Can you also share your synclient settings? Sure. I was using synclient(1) with the following settings but synclient(1) no longer works with this driver. synclient ClickFinger2=2 ClickFinger3=3 PalmDetect=0 PalmMinWidth=4 PalmMinZ=100 Bryan
Re: touchpad input driver: testing needed
Bryan Vyhmeister wrote: > On Mon, Jul 31, 2017 at 11:02:28PM +0200, Ulf Brosziewski wrote: > > for you. As always, a dmesg would be appreciated. The output of > > # wsconsctl | grep 'mouse' > > could also be of interest here (you must run it as root). > > This report is from a MacBookAir7,2 which is a 2015 13-inch MacBook Air. > Anything more than a regular click is not working as can be seen from > the wsconsctl output. I was using synclient to configure previously > which did allow the other settings. Can you also share your synclient settings?
Re: touchpad input driver: testing needed
On Mon, Jul 31, 2017 at 11:02:28PM +0200, Ulf Brosziewski wrote: > for you. As always, a dmesg would be appreciated. The output of > # wsconsctl | grep 'mouse' > could also be of interest here (you must run it as root). This report is from a MacBookAir7,2 which is a 2015 13-inch MacBook Air. Anything more than a regular click is not working as can be seen from the wsconsctl output. I was using synclient to configure previously which did allow the other settings. # wsconsctl | grep mouse mouse.type=usb mouse.rawmode=1 mouse.scale=0,0,0,0,0,0,0 mouse1.type=elantech mouse1.rawmode=0 mouse1.scale=-4620,5140,-150,6600,0,0,0 Bryan OpenBSD 6.1-current (GENERIC.MP) #27: Mon Jul 31 12:56:47 MDT 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP RTC BIOS diagnostic error ff real mem = 8469352448 (8077MB) avail mem = 8206315520 (7826MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0x8afad000 (32 entries) bios0: vendor Apple Inc. version "MBA71.88Z.0166.B26.1703211638" date 03/21/2017 bios0: Apple Inc. MacBookAir7,2 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP HPET APIC SBST ECDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT DMAR MCFG acpi0: wakeup devices PEG0(S3) EC__(S3) HDEF(S3) RP01(S3) RP02(S3) RP03(S4) ARPT(S4) RP05(S3) RP06(S3) SPIT(S3) XHC1(S3) ADP1(S3) LID0(S3) 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-5650U CPU @ 2.20GHz, 2200.37 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,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,SENSOR,ARAT cpu0: 256KB 64b/line 8-way L2 cache cpu0: TSC frequency 2200371760 Hz cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 100MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i7-5650U CPU @ 2.20GHz, 2200.00 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,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,SENSOR,ARAT cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Core(TM) i7-5650U CPU @ 2.20GHz, 2200.00 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,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,SENSOR,ARAT cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 1, core 0, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i7-5650U CPU @ 2.20GHz, 2200.00 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,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins acpiec0 at acpi0 acpimcfg0 at acpi0 addr 0xe000, bus 0-155 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PEG0) acpiprt2 at acpi0: bus 1 (RP01) acpiprt3 at acpi0: bus 2 (RP02) acpiprt4 at acpi0: bus 3 (RP03) acpiprt5 at acpi0: bus 5 (RP05) acpiprt6 at acpi0: bus 4 (RP06) acpicpu0 at acpi0: C3(200@530 mwait.1@0x60), C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C3(200@530 mwait.1@0x60), C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0: C3(200@530 mwait.1@0x60), C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu3 at acpi0: C3(200@530 mwait.1@0x60), C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpisbs0 at acpi0: SBS0 model "bq20z451" serial 36068 type LION oem "DP" "APP0001" at acpi0 not configured "ACPI0008" at acpi0 not configured "ACPI0001" at acpi0 not configured "APP000D" at acpi0 not configur
Re: touchpad input driver: testing needed
On Mon, Jul 31, 2017 at 11:02:28PM +0200, Ulf Brosziewski wrote: > for you. As always, a dmesg would be appreciated. The output of > # wsconsctl | grep 'mouse' > could also be of interest here (you must run it as root). Here is another report. This one is from a Lenovo LaVie Z with an Elantech touchpad. So far seems to work just fine as well. # wsconsctl | grep mouse mouse.type=elantech mouse.rawmode=0 mouse.scale=0,2800,0,1820,0,0,0 mouse.tp.tapping=0 mouse.tp.scaling=0.275 mouse.tp.swapsides=0 mouse.tp.disable=0 Thanks again! Bryan OpenBSD 6.1-current (GENERIC.MP) #27: Mon Jul 31 12:56:47 MDT 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8485908480 (8092MB) avail mem = 8222367744 (7841MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xdcef (23 entries) bios0: vendor LENOVO version "/763A0400" date 04/02/2015 bios0: LENOVO 20FG0013US acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT FIDT ECDT MCFG HPET SSDT UEFI SSDT ASF! MSDM SSDT SSDT SSDT BGRT SSDT acpi0: wakeup devices PEGP(S4) PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4) LID0(S3) PXSX(S3) RP01(S4) PXSX(S3) RP02(S4) PXSX(S3) RP03(S4) PXSX(S3) RP04(S4) PXSX(S3) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz, 2394.86 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,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,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,PT,SENSOR,ARAT cpu0: 256KB 64b/line 8-way L2 cache cpu0: TSC frequency 2394859830 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.1.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz, 2394.47 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,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,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,PT,SENSOR,ARAT cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz, 2394.47 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,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,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,PT,SENSOR,ARAT cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 1, core 0, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz, 2394.47 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,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,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,PT,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins acpimadt0: bogus nmi for apid 2 acpimadt0: bogus nmi for apid 1 acpimadt0: bogus nmi for apid 3 acpiec0 at acpi0 acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PEG0) acpiprt2 at acpi0: bus -1 (PEG1) acpiprt3 at acpi0: bus -1 (PEG2) acpiprt4 at acpi0: bus 1 (RP01) acpiprt5 at acpi0: bus -1 (RP02) acpiprt6 at acpi0: bus 2 (RP03) acpiprt7 at acpi0: bus 3 (RP04) acpiprt8 at acpi0: bus -1 (RP05) acpiprt9 at acpi0: bus -1 (RP06) acpiprt10 at acpi0: bus -1 (RP07) acpiprt11 at acpi0: bus -1 (RP08) acpiec at acpi0 not configured acpiec at acpi0 not configured acpicpu0 at acpi0: C3(200@506 mwait.1@0x60), C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C3(200@506 mwait.1@0x60), C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0: C3(200@506 mwait.1@0x60), C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu3 at acpi0: C3(200@506 mwait.1@0x60), C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpipwrres0 at acpi0: PG00, resource for
Re: touchpad input driver: testing needed
On Mon, Jul 31, 2017 at 11:02:28PM +0200, Ulf Brosziewski wrote: > for you. As always, a dmesg would be appreciated. The output of > # wsconsctl | grep 'mouse' > could also be of interest here (you must run it as root). This is from a Lenovo ThinkPad X1 Carbon (4th Gen) which has a Synaptics touchpad which has been working fine otherwise and appears to continue to work fine with your driver. # wsconsctl | grep mouse mouse.type=synaptics mouse.rawmode=0 mouse.scale=1472,5678,1408,4754,0,46,68 mouse.tp.tapping=0 mouse.tp.scaling=0.171 mouse.tp.swapsides=0 mouse.tp.disable=0 mouse1.type=ps2 Thanks for your work on this! Bryan OpenBSD 6.1-current (GENERIC.MP) #26: Mon Jul 31 08:42:35 MDT 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17011994624 (16223MB) avail mem = 16490065920 (15726MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xb705e000 (65 entries) bios0: vendor LENOVO version "N1FET49W (1.23 )" date 02/08/2017 bios0: LENOVO 20FBCTO1WW acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP UEFI SSDT SSDT ECDT HPET APIC MCFG SSDT SSDT DBGP DBG2 BOOT BATB SSDT SSDT MSDM DMAR ASF! FPDT UEFI acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP9(S4) XHCI(S3) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiec0 at acpi0 acpihpet0 at acpi0: 2399 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz, 2808.00 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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT cpu0: 256KB 64b/line 8-way L2 cache cpu0: TSC frequency 280800 Hz cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 24MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz, 2808.00 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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz, 2808.00 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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 1, core 0, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz, 2808.00 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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 120 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PEG0) acpiprt2 at acpi0: bus -1 (PEG1) acpiprt3 at acpi0: bus -1 (PEG2) acpiprt4 at acpi0: bus 2 (EXP1) acpiprt5 at acpi0: bus 4 (EXP3) acpiprt6 at acpi0: bus 5 (EXP5) acpiprt7 at acpi0: bus -1 (EXP9) acpicpu0 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu3 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpipwrres0 at acpi0: PUBS, resource for XHCI acpipwrres1 at acpi0: PG00, resource for PEG0 acpipwrres2 at acpi0: PG01, resource for PEG1 acpipwrres3 at acpi0: PG02, resource for PEG2 acpi
touchpad input driver: testing needed
In the long run the synaptics driver, which handles touchpad inputs in X, may be a dead end of the input framework, and it's time to prepare an alternative. The kernel contains an internal touchpad input driver now, it's a part of wsmouse(4). It provides standard features - two-finger/edge scrolling, software buttons for clickpads, tapping - and various kinds of plankton required for usability. If you have a new snapshot (from July 27 or later) on a laptop with a Synaptics, Apple, Alps, or Elantech-4 touchpad, you could help with tests, more tests, and tests. In order to activate the driver, add the following entry to /etc/xorg.conf and restart X (if the file isn't present, simply create it with this content): Section "InputClass" Identifier "wsmouse touchpad" Driver "ws" MatchIsTouchpad "on" EndSection While I dont't expect bugs in the input processing part of the driver ;-), it is difficult to assess how well the automatic configuration covers the zoo of models out there, presumably it will need some more fine-grained distinctions of hardware properties. I would like to know where it works, works only halfway, or doesn't work for you. As always, a dmesg would be appreciated. The output of # wsconsctl | grep 'mouse' could also be of interest here (you must run it as root). For now, X will treat the device like a mouse, please don't look for touchpad-specific configuration options there. Tapping can be enabled by the command # wsconsctl mouse.tp.tapping=1 If there is more than one wsmouse device, you should look up which one has the "tp" fields and if it's not the first one (wsmouse0), add the index to the prefix, e.g. # wsconsctl mouse2.tp.tapping=1 The base speed of the pointer can be adjusted by increasing or decreasing the value of # wsconsctl mouse.tp.scaling Please don't confuse it with the 'mouse.scale' field. # wsconsctl mouse.tp.swapsides=1 will invert the order of software buttons areas (swapping external buttons must still be configured in X). If edge scrolling is enabled, the scroll area will be at the left edge of the touchpad. If you are using an external mouse device or a trackpoint, the command # wsconsctl mouse.tp.disable=1 may be helpful. It will disable pointer movement, scrolling, and tapping. External buttons and software buttons remain enabled.
Re: HEADS up: how to cope with pre-release testing with pkg_add(1)
On Fri, Mar 31, 2017 at 10:28:42PM +0300, Mihai Popescu wrote: > > So pkg_add will look for the release directory, and not find it yet because > > it's not out > yet. > > Is PKG_PATH ignored then? RTFM, I'm just making people aware of recent stuff that's fully documented. > > until the release is done. > > So this is for people wanting to install release only? This is for people working on current right now.
Re: HEADS up: how to cope with pre-release testing with pkg_add(1)
> So pkg_add will look for the release directory, and not find it yet because > it's not out > yet. Is PKG_PATH ignored then? > until the release is done. So this is for people wanting to install release only?
HEADS up: how to cope with pre-release testing with pkg_add(1)
Just so that the subject makes it clear. This info already made it in various messages ont the mailing list. Right now, if you install OpenBSD, it says 6.1 without beta. So pkg_add will look for the release directory, and not find it yet because it's not out yet. pkg_add -Dsnap will make pkg_add bypass its usual heuristics and locate packages in the snapshots directory, where they will live until the release is done.
Re: Testing stability of internet connection for VPn tunnel
Hi there, maybe its important to notice that the provider change also changed the way we connect to the net. we had a provider router that was basically transperent so my soekris could add a static route with her internal ip and it worked. now we have a modem7router that is not transperent and not manageable at all (telecolumbus for the german readers). so I can define a route with the internal ip as gateway but its not really working for me, at least not with a ping. Beside that the traffic is going through somehow maybe because pf is doing some of the work here. So maybe someone out there has some ideas how to overcome this problem too. Regards Markus Am 24.01.2017 um 10:05 schrieb Markus Rosjat: Hey there, like the topic says I just need to get an idea how to really check if the internet connection can handle the traffic over my vpn tunnel. I was thinking of doing a ping with a bigger size of payload and check how many packages get droped over a fixed amount of time but if there is a better and more reliable way to do this then it wood be most appreciated to hear it :) Regards -- Markus Rosjatfon: +49 351 8107223mail: ros...@ghweb.de G+H Webservice GbR Gorzolla, Herrmann Königsbrücker Str. 70, 01099 Dresden http://www.ghweb.de fon: +49 351 8107220 fax: +49 351 8107227 Bitte prüfen Sie, ob diese Mail wirklich ausgedruckt werden muss! Before you print it, think about your responsibility and commitment to the ENVIRONMENT
Testing stability of internet connection for VPn tunnel
Hey there, like the topic says I just need to get an idea how to really check if the internet connection can handle the traffic over my vpn tunnel. I was thinking of doing a ping with a bigger size of payload and check how many packages get droped over a fixed amount of time but if there is a better and more reliable way to do this then it wood be most appreciated to hear it :) Regards -- Markus Rosjatfon: +49 351 8107223mail: ros...@ghweb.de G+H Webservice GbR Gorzolla, Herrmann Königsbrücker Str. 70, 01099 Dresden http://www.ghweb.de fon: +49 351 8107220 fax: +49 351 8107227 Bitte prüfen Sie, ob diese Mail wirklich ausgedruckt werden muss! Before you print it, think about your responsibility and commitment to the ENVIRONMENT
Testing the waters - BUG in Indianapolis, IN USA
All, If anyone is in the area and would be interested, please let me know through the form below: http://techpoint.org/2016/09/indianapolis-bsd-user-group/ Thanks, Bryan
Re: Interesting error message from disk testing
On Tue, 28 Jun 2016, STeve Andre' wrote: I am testing some new 8TB disks. I've taken to doing dd if=/dev/zero of=/dev/rsd3c bs=64k and dd if=/dev/rsd3c of=/dev/null bs=64k as a first test. It's depressing how often I've found problems on big disks. Today, the read test produced an error in the messages file I've not seen before: Jun 28 16:17:39 paladin /bsd: sd3(umass0:1:0): Check Condition (error 0x70) on opcode 0x28 Jun 28 16:17:39 paladin /bsd: SENSE KEY: Aborted Command Jun 28 16:17:39 paladin /bsd: ASC/ASCQ: Information Unit iuCRC Error Detected So it isn't a soft read error -- what is it? It might be useful to indicate where the error occurred? This is the second of three disks to be tested. It's connected to a Thermaltake USB 3.0 disk enclosure. I have seen CRC errors number of times when working with different USB enclosures. My guess is that either the connectors inside the boxes aren't 100% tight, the electronics is not shielded properly or it has some flaws. If I am not mistaken, it is the transfer between the HDD electronics and the controller (ie. the bridge chip) that failed. Also see this thread: http://marc.info/?t=10989807768&r=1&w=2 I would also monitor the drive with smartctl from sysutils/smartmontools. Regards, David
Interesting error message from disk testing
I am testing some new 8TB disks. I've taken to doing dd if=/dev/zero of=/dev/rsd3c bs=64k and dd if=/dev/rsd3c of=/dev/null bs=64k as a first test. It's depressing how often I've found problems on big disks. Today, the read test produced an error in the messages file I've not seen before: Jun 28 16:17:39 paladin /bsd: sd3(umass0:1:0): Check Condition (error 0x70) on opcode 0x28 Jun 28 16:17:39 paladin /bsd: SENSE KEY: Aborted Command Jun 28 16:17:39 paladin /bsd: ASC/ASCQ: Information Unit iuCRC Error Detected So it isn't a soft read error -- what is it? It might be useful to indicate where the error occurred? This is the second of three disks to be tested. It's connected to a Thermaltake USB 3.0 disk enclosure. Thanks for any pointers. --STeve Andre'
