Re: [DNG] mouse driver question

2022-05-12 Thread Fred

On 5/12/22 15:23, Florian Zieboll via Dng wrote:



On May 12, 2022 9:44:39 PM GMT+02:00, Fred  wrote:


Hi Karl,
I don't use a DE, just openbox and xterm.  The regular scroll wheel mouse works 
correctly in both xev and the application.  Button 2 is identified as 2 so I 
contend it has to have something to do with program(s) run to use the serial 
mouse.

xmodmap -pp shows the buttons mapped correctly with both mice.

The Xorg.log file has entries for USB Optical Mouse, Mouse Systems mouse and 
Sun mouse (when I gave that protocol to inputattach and gpm) but nothing about 
mouse buttons.
Best regards,
Fred



A very interesting thread, never have I
been so close to hardware!

There's just one question itching me for a
little while now: Is it possible, that this
old mouse simply has some physical
issue, triggered by using button 2?

And if so, what would be the best way to
prove it?

libre Grüße,
Florian



Hi Florian,
No, the mouse is fine.  I have an application that I have used for 20 
years running on Solaris 2.6.  The Sun is retired but I still need the 
application.  I was able to get it to compile and run happily on Devuan 
Beowulf and it works fine with the standard pc scroll wheel mouse.  The 
program makes extensive use of the middle button which is a pain with 
the pc mouse.  I would like to continue using the Sun three button mouse 
which works except the middle button.  I have studied the output of the 
mouse with an oscilloscope and software and it is working exactly as a 
Mouse Systems mouse.  There is some defugalty in getting the middle 
button information into user programs.  Maybe a bug somewhere?


Best regards,
Fred

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] mouse driver question

2022-05-12 Thread Florian Zieboll via Dng


On May 12, 2022 9:44:39 PM GMT+02:00, Fred  wrote:

> Hi Karl,
> I don't use a DE, just openbox and xterm.  The regular scroll wheel mouse 
> works correctly in both xev and the application.  Button 2 is identified as 2 
> so I contend it has to have something to do with program(s) run to use the 
> serial mouse.
> 
> xmodmap -pp shows the buttons mapped correctly with both mice.
> 
> The Xorg.log file has entries for USB Optical Mouse, Mouse Systems mouse and 
> Sun mouse (when I gave that protocol to inputattach and gpm) but nothing 
> about mouse buttons.
> Best regards,
> Fred


A very interesting thread, never have I
been so close to hardware! 

There's just one question itching me for a 
little while now: Is it possible, that this 
old mouse simply has some physical 
issue, triggered by using button 2? 

And if so, what would be the best way to 
prove it?

libre Grüße,
Florian


-- 

[message sent otg]



___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] mouse driver question

2022-05-12 Thread Fred

On 5/12/22 03:15, k...@aspodata.se wrote:

Fred:
...

With xev, buttons 1 and 3 are correctly identified but the middle button
is randomly assigned 4,5,6 or 7.  Possibly this is the problem as I know
the application is expecting button 2.


Maybe it is the desktop environment or the window manager that messes
this up.

Try installing and using fvwm1 or something of similar age instead of
what you are using currently and do the same test, or if you know how,
run bare Xorg.

///

It can also be the xserver config if you happens to have a xorg.conf
that is picked up by X. Configs like buttonmapping and things related
to emulateweel can mess this up. Look in man evdev (or man mousedrv).

  Look in your X11 log file for clues:
$ man xorg | grep -A8 ' -logfile'
-logfile filename
Use  the file called filename as the Xorg server log file.  The
default log file when running as  root  is  /var/log/Xorg.n.log
and  for  non root it is $XDG_DATA_HOME/xorg/Xorg.n.log where n
is the display number of the Xorg server.  The default  may  be
in  a  different  directory  on some platforms.  This option is
only available when the server is run as root (i.e, with  real-
uid 0).

Regards,
/Karl Hammar


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Hi Karl,
I don't use a DE, just openbox and xterm.  The regular scroll wheel 
mouse works correctly in both xev and the application.  Button 2 is 
identified as 2 so I contend it has to have something to do with 
program(s) run to use the serial mouse.


xmodmap -pp shows the buttons mapped correctly with both mice.

The Xorg.log file has entries for USB Optical Mouse, Mouse Systems mouse 
and Sun mouse (when I gave that protocol to inputattach and gpm) but 
nothing about mouse buttons.

Best regards,
Fred
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] mouse driver question

2022-05-12 Thread karl
Fred:
...
> With xev, buttons 1 and 3 are correctly identified but the middle button 
> is randomly assigned 4,5,6 or 7.  Possibly this is the problem as I know 
> the application is expecting button 2.

Maybe it is the desktop environment or the window manager that messes
this up.

Try installing and using fvwm1 or something of similar age instead of
what you are using currently and do the same test, or if you know how,
run bare Xorg.

///

It can also be the xserver config if you happens to have a xorg.conf
that is picked up by X. Configs like buttonmapping and things related
to emulateweel can mess this up. Look in man evdev (or man mousedrv).

 Look in your X11 log file for clues:
$ man xorg | grep -A8 ' -logfile'
   -logfile filename
   Use  the file called filename as the Xorg server log file.  The
   default log file when running as  root  is  /var/log/Xorg.n.log
   and  for  non root it is $XDG_DATA_HOME/xorg/Xorg.n.log where n
   is the display number of the Xorg server.  The default  may  be
   in  a  different  directory  on some platforms.  This option is
   only available when the server is run as root (i.e, with  real-
   uid 0).

Regards,
/Karl Hammar


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] mouse driver question

2022-05-12 Thread Daniel Abrecht via Dng
To find out what's behind which /dev/input/event* device, and generally 
what's going on with the input stuff on the kernel side, I usually 
check: "cat /proc/bus/input/devices"




___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng