Re: Thinkpad X220T digitizer pen stopped no longer works on NetBSD 11.99.1

Kevin Bloom <[email protected]>
Newsgroups gmane.os.netbsd.current
Message-ID <20251017111847.zHZf1%[email protected]>
RVP <[email protected]> wrote:

> On Fri, 10 Oct 2025, Kevin Bloom wrote:
> 
> >>> Note on my NetBSD 10 system I believe there were 4 wsmouse devices.
> >>>
> >>
> >> Can you post,
> >>
> >> 1. the full `/var/run/dmesg.boot` after booting with `boot -vx', and,
> >>
> >> 2. the full `/var/log/Xorg.0.log' on both 10.x and -HEAD?
> >>
> >> -RVP
> >
> > Posted this stuff and got no reply. Any ideas given the information
> > I sent in?
> >
> 
> Ah, sorry! lost track of this completely. From the `dmesg.boot' on -HEAD, it
> looks like you have more that 4 wsmouse devices. Can you post the `dmesg.boot'
> from 10.x too, to compare?

Sadly, I don't have one to get this information.

> Can you also,
> 
> 1. compile xorg-server with this patch:
> ```
> diff -urN a/xorg-server/dist/config/wscons.c b/xorg-server/dist/config/wscons.c
> --- a/xorg-server/dist/config/wscons.c	2021-12-05 21:14:12.000000000 +0000
> +++ b/xorg-server/dist/config/wscons.c	2025-10-11 06:09:19.722366109 +0000
> @@ -233,7 +233,7 @@
>       int fd, i, wsmouse_type;
> 
>       /* Check pointing devices */
> -    for (i = 0; i < 4; i++) {
> +    for (i = 0; i < 10; i++) {
>           snprintf(devname, sizeof(devname), "%s%d", WSCONS_MOUSE_PREFIX, i);
>           LogMessageVerb(X_INFO, 10, "wsmouse: checking %s\n", devname);
>   #ifdef __NetBSD__
> ```

I'm on 11.99.3 now and this patch doesn't seem to have helped.

> 2. make some more /dev/wsmouseN devices to correspond?

I have not tried this yet. I've never done it before so I must read
up on how this is done.

> Let's see if the xorg-server's happy when it can discover the actual
> characteristics of the pointers, rather that reading smooshed-together stuff
> read from the multiplexer device, `/dev/wsmouse'.
> 
> -RVP
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.