Serial mouse - Revision history

Zcrayfish: /* Solution: Inform the Linux input subsystem */ Link to linuxconsole tools and change "testing" repo reference to "community". Correct command to start service . . .

2024-01-19T05:03:40Z

Solution: Inform the Linux input subsystem: Link to linuxconsole tools and change "testing" repo reference to "community". Correct command to start service . . .

← Older revision		Revision as of 05:03, 19 January 2024
Line 33:		Line 33:
	{{Cmd\|udevadm info --name=/dev/ttyS0 --query=path}}		{{Cmd\|udevadm info --name=/dev/ttyS0 --query=path}}
	<pre>/devices/platform/serial8250/tty/ttyS0</pre>		<pre>/devices/platform/serial8250/tty/ttyS0</pre>
	But in the output of {{cmd\|cat /proc/bus/input/devices}} there is no hint of its existence. Installing the package ~~<code>~~linuxconsoletools~~</code>~~ from the ~~testing~~ repository and executing		But in the output of {{cmd\|cat {{path\|/proc/bus/input/devices}}}} there is no hint of its existence. Installing the package {{pkg\|linuxconsoletools\|arch=}} from the community repository and executing
	{{cmd\|inputattach --mouseman /dev/ttyS0}}		{{cmd\|inputattach --mouseman /dev/ttyS0}}
	should give us a working mouse for the X server.		should give us a working mouse for the X server.
Line 39:		Line 39:
	{{cmd\|inputattach --help}} prints a list of the available protocols. In our case the line		{{cmd\|inputattach --help}} prints a list of the available protocols. In our case the line
	<pre> --mouseman -mman 3-button Logitech / Genius mouse</pre>		<pre> --mouseman -mman 3-button Logitech / Genius mouse</pre>
	tells us which one to use. Now the output of {{cmd\|cat /proc/bus/input/devices}} should contain a section like:		tells us which one to use. Now the output of {{cmd\|cat {{path\|/proc/bus/input/devices}}}} should contain a section like:
	<pre>		<pre>
	I: Bus=0013 Vendor=0004 Product=0001 Version=0100		I: Bus=0013 Vendor=0004 Product=0001 Version=0100
Line 53:		Line 53:
	</pre>		</pre>

	To start the <code>inputattach</code> command automatically create a file ~~<code>~~/etc/local.d/sermouse.start~~</code>~~ with the content:		To start the <code>inputattach</code> command automatically create a file {{path\|/etc/local.d/sermouse.start}} with the content:
	<pre>		<pre>
	#!/bin/sh		#!/bin/sh
Line 61:		Line 61:
	{{cmd\|rc-update add local default}}		{{cmd\|rc-update add local default}}
	Then the command		Then the command
	{{cmd\|rc}} should start the new service. If you want to stop <code>inputattach</code> when stopping the <code>local</code> service, create an executable file ~~<code>~~/etc/local.d/sermouse.stop~~</code>~~ with content		{{cmd\|rc-service local start}} should start the new service. If you want to stop <code>inputattach</code> when stopping the <code>local</code> service, create an executable file {{path\|/etc/local.d/sermouse.stop}} with content
	<pre>		<pre>
	#!/bin/sh		#!/bin/sh
	killall inputattach		killall inputattach
	</pre>		</pre>
	Alternatively you can create a script in ~~<code>~~/etc/init.d~~</code>~~ to define a service for the serial mouse.		Alternatively you can create a script in {{path\|/etc/init.d}} to define a service for the serial mouse.

	=Solution: Configure the X.org server=		=Solution: Configure the X.org server=

Zcrayfish: /* Getting information about the mouse */ Link to gpm pkg.

2024-01-19T04:58:46Z

Getting information about the mouse: Link to gpm pkg.

← Older revision		Revision as of 04:58, 19 January 2024
Line 11:		Line 11:
	=Getting information about the mouse=		=Getting information about the mouse=

	If the protocol for the serial mouse is unkown, the command {{cmd\|mouse-test /dev/ttyS0}} from the package ~~<code>~~gpm~~</code>~~ can be used to get the necessary information. The program is interactive and will print at the end a message like:		If the protocol for the serial mouse is unkown, the command {{cmd\|mouse-test /dev/ttyS0}} from the package {{pkg\|gpm\|arch=}} can be used to get the necessary information. The program is interactive and will print at the end a message like:
	<pre>		<pre>
	Your mouse seems to be a 'mman' one on "/dev/ttyS0" (24 matches)		Your mouse seems to be a 'mman' one on "/dev/ttyS0" (24 matches)
Line 26:		Line 26:
	</pre>		</pre>
	gives us more information about the protocol. We can test the mouse in a virtual console by running:		gives us more information about the protocol. We can test the mouse in a virtual console by running:
	{{cmd\|gpm -m /dev/ttyS0 -t mman}}		{{cmd\|gpm -m {{path\|/dev/ttyS0}} -t mman}}

	=Solution: Inform the Linux input subsystem=		=Solution: Inform the Linux input subsystem=

Zcrayfish: /* Introduction */ Remove obsolete information, fix typos, and use path template.

2024-01-19T04:57:00Z

Introduction: Remove obsolete information, fix typos, and use path template.

← Older revision		Revision as of 04:57, 19 January 2024
Line 1:		Line 1:
	=Introduction=		=Introduction=

	A mouse connected to the serial port will not be recognized by an ~~X.Org~~ server automatically. In ~~<code>~~/var/log/Xorg.0.log~~</code>~~ there ~~will~~ be a message:		A mouse connected to the serial port will not be recognized by an Xorg server automatically. In {{path\|/var/log/Xorg.0.log}} there may be a message:
	<pre>		<pre>
	(II) The server relies on udev to provide the list of input devices.		(II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.		If no devices become available, reconfigure udev or disable AutoAddDevices.
	</pre>		</pre>
	~~An existing <code>/etc/X11/xorg.conf</code> with <code>AutoAddDevices</code> enabled will result in~~
	~~<pre>~~
	~~(WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.~~
	~~</pre>~~

	We will describe two ways of getting an usable serial mouse under X.org. In our example we have a ~~Logitec~~ serial mouse of the model M/N: M-M30 associated to the device ~~<code>~~/dev/ttyS0~~</code>~~.		We will describe two ways of getting an usable serial mouse under X.org. In our example we have a Logitech serial mouse of the model M/N: M-M30 associated to the device {{path\|/dev/ttyS0}}.

	=Getting information about the mouse=		=Getting information about the mouse=

Zcrayfish: /* Solution: Configure the X.org server */ Please do not do this.

2024-01-19T04:45:07Z

Solution: Configure the X.org server: Please do not do this.

← Older revision		Revision as of 04:45, 19 January 2024
Line 73:		Line 73:

	=Solution: Configure the X.org server=		=Solution: Configure the X.org server=
			{{obsolete\|Using Xorg -configure causes issues on many modern systems and is totally unnecessary. If the below configuration can be made to work, it should be placed in its own config file as opposed to generating a full-blown xorg.conf (perhaps try making an {{path\|/etc/X11/xorg.conf.d/serial_mouse.conf}}?)}}
	If you don't have a <code>/etc/X11/xorg.conf</code>, then generate one with the command		If you don't have a <code>/etc/X11/xorg.conf</code>, then generate one with the command
	{{cmd\|Xorg -configure}}		{{cmd\|Xorg -configure}}

Zcrayfish: /* References */ Rescued a dead link

2023-07-26T21:35:45Z

References: Rescued a dead link

← Older revision		Revision as of 21:35, 26 July 2023
Line 94:		Line 94:
	*[https://wiki.archlinux.org/index.php/serial_input_device_to_kernel_input Serial input device to kernel input - ArchWiki]		*[https://wiki.archlinux.org/index.php/serial_input_device_to_kernel_input Serial input device to kernel input - ArchWiki]
	*[https://bugs.alpinelinux.org/issues/2532 Feature #2532: Request for package: linuxconsoletools]		*[https://bugs.alpinelinux.org/issues/2532 Feature #2532: Request for package: linuxconsoletools]
	*[https://lists.alpinelinux.org/alpine-devel/1891.html How to run script at startup (alpine-devel Archives)]		*[https://web.archive.org/web/20171125125124/https://lists.alpinelinux.org/alpine-devel/1891.html How to run script at startup (alpine-devel Archives)]
	*[https://wiki.gentoo.org/wiki//etc/local.d local.d Gentoo Wiki]		*[https://wiki.gentoo.org/wiki//etc/local.d local.d Gentoo Wiki]
	[[Category:Hardware]]		[[Category:Hardware]]

Zcrayfish: /* References */ Changed all urls in this section to https. + changed gentoo stuff to canonical url and spelling.

2023-07-26T21:32:04Z

References: Changed all urls in this section to https. + changed gentoo stuff to canonical url and spelling.

← Older revision		Revision as of 21:32, 26 July 2023
Line 92:		Line 92:
	=References=		=References=

	*[~~http~~://wiki.archlinux.org/index.php/serial_input_device_to_kernel_input Serial input device to kernel input - ArchWiki]		*[https://wiki.archlinux.org/index.php/serial_input_device_to_kernel_input Serial input device to kernel input - ArchWiki]
	*[~~http~~://bugs.alpinelinux.org/issues/2532 Feature #2532: Request for package: linuxconsoletools]		*[https://bugs.alpinelinux.org/issues/2532 Feature #2532: Request for package: linuxconsoletools]
	*[~~http~~://lists.alpinelinux.org/alpine-devel/1891.html How to run script at startup (alpine-devel Archives)]		*[https://lists.alpinelinux.org/alpine-devel/1891.html How to run script at startup (alpine-devel Archives)]
	*[~~http~~://wiki.gentoo.org/wiki/~~Local~~.d local.d ~~GEntoo~~ Wiki]		*[https://wiki.gentoo.org/wiki//etc/local.d local.d Gentoo Wiki]
	[[Category:Hardware]]		[[Category:Hardware]]

Arrogance at 07:21, 30 May 2023

2023-05-30T07:21:06Z

← Older revision		Revision as of 07:21, 30 May 2023
Line 1:		Line 1:
	~~[[Category:Installation]]~~

	=Introduction=		=Introduction=

Line 98:		Line 96:
	*[http://lists.alpinelinux.org/alpine-devel/1891.html How to run script at startup (alpine-devel Archives)]		*[http://lists.alpinelinux.org/alpine-devel/1891.html How to run script at startup (alpine-devel Archives)]
	*[http://wiki.gentoo.org/wiki/Local.d local.d GEntoo Wiki]		*[http://wiki.gentoo.org/wiki/Local.d local.d GEntoo Wiki]
			[[Category:Hardware]]

Arrogance: Arrogance moved page Serial Mouse to Serial mouse

2023-05-30T06:53:19Z

Arrogance moved page Serial Mouse to Serial mouse

← Older revision	Revision as of 06:53, 30 May 2023
(No difference)

Theo: how to make use of a serial mouse

2013-12-30T22:26:53Z

how to make use of a serial mouse

New page

[[Category:Installation]]

=Introduction=

A mouse connected to the serial port will not be recognized by an X.Org server automatically. In <code>/var/log/Xorg.0.log</code> there will be a message:
<pre>
(II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
</pre>
An existing <code>/etc/X11/xorg.conf</code> with <code>AutoAddDevices</code> enabled will result in
<pre>
(WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
</pre>

We will describe two ways of getting an usable serial mouse under X.org. In our example we have a Logitec serial mouse of the model M/N: M-M30 associated to the device <code>/dev/ttyS0</code>.

=Getting information about the mouse=

If the protocol for the serial mouse is unkown, the command {{cmd|mouse-test /dev/ttyS0}} from the package <code>gpm</code> can be used to get the necessary information. The program is interactive and will print at the end a message like:
<pre>
Your mouse seems to be a 'mman' one on "/dev/ttyS0" (24 matches)
</pre>
The <code>man</code> page <code>gpm-types</code> contain a list of the protocols. In our case the lines
<pre>
mman Mouseman
The protocol used by the new Logitech devices with three but-
tons. It is backward compatible with the Microsoft protocol, so
if your mouse has three buttons and works with -t ms or similar
decoders you may try -t mman instead to use the middle button.
This mouse decoder accepts standard serial options, although
they should not be needed.
</pre>
gives us more information about the protocol. We can test the mouse in a virtual console by running:
{{cmd|gpm -m /dev/ttyS0 -t mman}}

=Solution: Inform the Linux input subsystem=

The serial port should already be known to udev:
{{Cmd|udevadm info --name=/dev/ttyS0 --query=path}}
<pre>/devices/platform/serial8250/tty/ttyS0</pre>
But in the output of {{cmd|cat /proc/bus/input/devices}} there is no hint of its existence. Installing the package <code>linuxconsoletools</code> from the testing repository and executing
{{cmd|inputattach --mouseman /dev/ttyS0}}
should give us a working mouse for the X server.
The command
{{cmd|inputattach --help}} prints a list of the available protocols. In our case the line
<pre> --mouseman -mman 3-button Logitech / Genius mouse</pre>
tells us which one to use. Now the output of {{cmd|cat /proc/bus/input/devices}} should contain a section like:
<pre>
I: Bus=0013 Vendor=0004 Product=0001 Version=0100
N: Name="Logitech M+ Mouse"
P: Phys=ttyS0/serio0/input0
S: Sysfs=/devices/platform/serial8250/tty/ttyS0/serio8/input/input9
U: Uniq=
H: Handlers=event2 mouse0
B: PROP=0
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=3
</pre>

To start the <code>inputattach</code> command automatically create a file <code>/etc/local.d/sermouse.start</code> with the content:
<pre>
#!/bin/sh
inputattach --daemon --mouseman /dev/ttyS0
</pre>
Make it executable and add the service <code>local</code> to the <code>default</code> runlevel:
{{cmd|rc-update add local default}}
Then the command
{{cmd|rc}} should start the new service. If you want to stop <code>inputattach</code> when stopping the <code>local</code> service, create an executable file <code>/etc/local.d/sermouse.stop</code> with content
<pre>
#!/bin/sh
killall inputattach
</pre>
Alternatively you can create a script in <code>/etc/init.d</code> to define a service for the serial mouse.

=Solution: Configure the X.org server=

If you don't have a <code>/etc/X11/xorg.conf</code>, then generate one with the command
{{cmd|Xorg -configure}}
and modify (and move) the resulting file <code>/root/xorg.conf.new</code> to get a running X server. For instance you might have to know the correct driver for the <code>"InputDevice"</code> section for your graphics card. Include the section
<pre>
Section "ServerFlags"
Option "AutoAddDevices" "False"
EndSection
</pre>
to disable hotplugging and set the <code>"Device"</code> and <code>"Protocol"</code> options in the <code>"InputDevice"</code> section for your mouse. In our case we have:
<pre>
Option "Protocol" "MouseMan"
Option "Device" "/dev/ttyS0"
</pre>
Then restart the X server. For instance:
{{cmd|rc-service lxdm restart}}

=References=

*[http://wiki.archlinux.org/index.php/serial_input_device_to_kernel_input Serial input device to kernel input - ArchWiki]
*[http://bugs.alpinelinux.org/issues/2532 Feature #2532: Request for package: linuxconsoletools]
*[http://lists.alpinelinux.org/alpine-devel/1891.html How to run script at startup (alpine-devel Archives)]
*[http://wiki.gentoo.org/wiki/Local.d local.d GEntoo Wiki]