[Bug 9068] Re: Serial mice are not autodetected

piotrko piotrekk at kolos.math.uni.lodz.pl
Sun Apr 29 07:02:58 UTC 2007


Serial mouse can work in xubuntu 7.04 !!! I also couldn't make it work
for years :] on my old PC, but this time I did it :)

I'm just showing what helped for me. Read on and get your own
conclusions.

I had a serial mouse, inserted directly to a COM. The problem was not
only about X. cat /dev/ttyS0 didn't work.

I can't recall exact steps, but the command inputattach was essential. I
did it in somehow ugly way, something like this... (case study):

1. Install xubuntu, logged into X (normally) - mouse doesn't work yet.
2. Switched to virtual console and log as root (i. e. Ctrl-Alt-F1).
Note: There is no root account explicitly given to you in (x)ubuntu. I made it this (ugly?) way by changing root's password using sudo:
2.1. Log in as the "ordinary" user (suppose his login is johnny)
2.2. Change root's password:
 Type:  sudo passwd
 (type johnnyspasswd - sudo needs this)
 (set new rootpasswd)
 (confirm rootpasswd)
2.3 Log in as root with the new rootpasswd
3. Kill gdm. 
To see gdm's PID, you can type:  pstree -p |grep gdm. (the leftmost gdm! You'll see two on the output)
4. Typing:
cat /dev/ttyS0   
and moving mouse makes no output. (press Ctrl-C after testing)
(also type cat /dev/ttyS1 if you're not sure which COM you are using)
5. Type:
inputattach -bare /dev/ttyS0
(you may need to change -bare to other protocol; inputattach --help gives a list of them)
This command also locks screen (should it?), so make a few movements with the mouse and press Ctrl-C.
6. Type again:
cat /dev/ttyS0.
If you see strange characters-junk on the screen while moving your mouse, you're a happy person!
Press Ctrl-C, type: reset (to clear the screen, if you can't see normal letters) and... what's left to do is to configure mouse in X.

Sorry for such a bloated post, but I prefered to write too much than to
less.

Hope it helps someone. Cheers.

-- 
Serial mice are not autodetected
https://bugs.launchpad.net/bugs/9068
You received this bug notification because you are a member of Kubuntu
Team, which is a subscriber of a duplicate bug.




More information about the kubuntu-bugs mailing list