Help me train a mouse

[utu]

I have a Microsoft Nano wireless mouse.

In Linux, the scroll-wheel response is too fast.
In Win7 its ok.

I can't seem to get xset or the gnome config tool
to slow this down.

Are there any other options to adjust this thing?

[utu]

Excerpts from /etc/X11/xorg.conf

Section "ServerLayout"
Identifier "XFree86 Configured"
Screen 0 "Screen0" 0 0

# Since evdev, manual keyboard/mice entries are mostly ignored:
# Keyboard auto-probed

# Touchpad auto-probed
# USB mouse auto-probed
# Serial Mouse auto-probed
### AIGLX for compiz 3D-Support with DRI & Composite
### This option doesn't hurt even if it's not supported by the individual card
Option "AIGLX" "true"

EndSection

Section "ServerFlags"
Option "AllowMouseOpenFail" "true"
Option "DPMS" "true"

EndSection

[mecho]

I read in some ubuntu forum about this problem with MS wireless mouse. Don't have the link to send it to you, but the workaround was: when you logout of windows and boot in knoppix just unplug the wireless adapter and plug it back in again. Try it and see if it works :) It's not a real solution, but its better then nothing, until you find a real one

[mecho]

This may be very tricky mouse to configure. You have to be lucky to find someone in this forums who has this kind of mouse AND to have it configured properly. So don't look in this forum. What I can see by googling is that the number of buttons (wheel tilting is a button too) has to be properly configured and the right protocol used in xorg.conf.
Here are some links I was looking at, hope might be of some help to you:
http://ubuntuforums.org/archive/index.php/t-22203.html
http://linuxreviews.org/howtos/xfree/mouse/

[mecho]

One more link which cold be of good use to you:
http://wiki.eeeuser.com/configure_logitech_vx_nano?s=nano

[utu]

@mecho

Many thanks once again.
It may be my imagination, but I think the unplugging had the desired effect.

I will study the Logitech article tomorrow.
I don't know if M$ Nano=Logitech Nano.

Also, thanks for getting Marietto straightened out.
I could never see what he (or she) was trying to do.

[utu]

@mecho

I am embarassed to note that Main Menu/Preferences/Keyboard & Mouse
provides a nice little gui which purports to affect mouse
sensitivity and acceleration. I can't see that it does for the
M$-Nano species of Rodenta, however.

The unplugging seemed to have got the rodent's attention. It
works now in Knoppix about like it does in Win7.

I can't see that any of the choices: xset, gnome config, or this
latest revelation have any effect toward making any changes on
my Nano.

The hunt-and-peck effort toward 'mapping' the mouse dimensions,
mentioned in one of your references, doesn't appeal to me.

Somewhere in my error-message treks I think I recall some note
to the effect that one of the 'dimensions' of the mouse was
unaccounted-for. The number accounted-for was rather large.

No hint as usual as to what one might do with this precious
revelation.

[mecho]

The GUI included in LXDE does nothing more then configuring xset and storing the velues in /home/knoppix/.config/lxsession/LXDE/desktop.conf
The important elements in setting your mouse would be in xorg.conf - mainly the "driver" "protocol" type, "SendCoreEvents" and "Buttons" value.
For a mouse like this it might take a lot of trial and error. Changing values in xorg.conf and restarting X.
The protocol name which works best for you might have nothing to do with your mouse. After you have found the best working config, you might want to edit knoppix-autoconfig and put your working mouse config there, so xorg.conf will be automatically recreated with you working config
Why I love Knoppix so much is because it makes you learn everything the hard way :)

[utu]

An excerpt from dmesg, concerning M$-Nano ( 6 lines broken with '\' for readability )

[ 4.074228] usb 7-1: new full speed USB device using uhci_hcd and address 2
[ 4.233044] usb 7-1: New USB device found, idVendor=045e, idProduct=0745
[ 4.233049] usb 7-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 4.233054] usb 7-1: Product: Microsoft® Nano Transceiver v1.0
[ 4.233058] usb 7-1: Manufacturer: Microsoft
[ 4.233356] usb 7-1: configuration #1 chosen from 1 choice
[ 4.239505] input: Microsoft Microsoft® Nano Transceiver v1.0 as /devices/pci0000:00/0000:00:1d.1\
/usb7/7-1/7-1:1.0/input/input9
[ 4.239838] generic-usb 0003:045E:0745.0001: input,hidraw0: USB HID v1.11 Keyboard\
[Microsoft Microsoft® Nano Transceiver v1.0] on usb-0000:00:1d.1-1/input0
[ 4.247210] input: Microsoft Microsoft® Nano Transceiver v1.0 as /devices/pci0000:00/0000:00:1d.1\
/usb7/7-1/7-1:1.1/input/input10
[ 4.247696] generic-usb 0003:045E:0745.0002: input,hidraw1: USB HID v1.11 Mouse\
[Microsoft Microsoft® Nano Transceiver v1.0] on usb-0000:00:1d.1-1/input1
[ 4.273514] input: Microsoft Microsoft® Nano Transceiver v1.0 as /devices/pci0000:00/0000:00:1d.1\
/usb7/7-1/7-1:1.2/input/input11
[ 4.274098] generic-usb 0003:045E:0745.0003: input,hiddev96,hidraw2: USB HID v1.11 Device\
[Microsoft Microsoft® Nano Transceiver v1.0] on usb-0000:00:1d.1-1/input2

[mecho]

I don't know Utu - seems like you should search for some kind of hal fdi policy, or udev rule to correct the scrolled number of lines at every boot. I can be of no help to you, unless I have the same kind of mouse and play with until I figure it out.

[mecho]

You can try and see if some xinput commands may work. Check if
xinput list-props "Microsoft® Nano Transceiver v1.0"
shows up your device and its available options. If it does you might be in luck

[mecho]

Because I am not sure about the name by which your mouse is listed can you post the output of :

cat /proc/bus/input/devices

[utu]

@mecho

You have already solved my immediate problem with the unplugging.
M$-Nano is behaving now. I don't need to change any settings right now.

It looks like we have to guess at some combination to get the
interface specified. That's too much work.

I though by posting dmesg that perhaps a fellow MS-Nano owner may
happen along and give us the magic combination.

You should stop work on this.
Once again you've bailed me out. Thanks.
Will post what you requested subsequently.

Ciao, as they say in Roma.

[utu]

@mecho

I tried to cut and paste your copyright, but it didn't work

knoppix@Microknoppix:~$ xinput list-props "Microsoft(R) Nano Transceiver v1.0"
unable to find device Microsoft(R) Nano Transceiver v1.0

device.txt too long to post, am attempting to create an enclosure.

Now stop working on this.

[mecho]

Yes, I was right the name is listed as Microsoft Microsoft® Nano Transceiver v1.0 by the kernel - there is one more thing I will ask you to send me-it is the output of:
xinput list-props "Microsoft Microsoft® Nano Transceiver v1.0"
It has 2 times Microsoft Microsoft not 1 as I was guessing
:) And - I can see that you are OK with it. I will not bother anymore

[utu]

How do I enter the 'Registered trademark' symbol?
I cut and pasted your text and it came out just (R).
The trademark symbol is probably important.

You are never a bother.

[mecho]

Try to change the font you use in lxterminal

[mecho]

And you don't have to list the device by its name - it can be listed by it's ID. You do it like this
xinput list
It will output all devices with their ID number. The output of cat /proc/bus/input/devices shows me that your mouse is id=10, but you just make sure, then:
xinput list-props 10
don't type id= just the number, and it should list all evdev options for the device.Post that output here

[utu]

@mecho

I don't think you want id=10, that's webcam; see xinputlist.txt.
Id's 11, 12 and 13 may be what you want; see props11thru13.txt

[mecho]

From what I see, you have 2 identical devices id=12 and 13. One of them has more complete evdev prop-list. I assume the second one was created after you unpluged the wireless adapter and is the one in use. I was thinking to create a script with xinput commands to restore the good working values, but it can not work if the prop is not there. Another way is to tell the kernel to rescan all usb devices after you log in in X, but I am not sure how to do that. I give up :)

[utu]

@mecho

Thanks for all the hard work.

Since the M$-Nano is behaving itself, perhaps
previous efforts have at least recorded workable settings
should someone able to do so need to set or re-set these
values.

You've also given us some invaluable lessons in
diagnostic techniques, for which thanks.

[utu]

@mecho

I likely have underestimated both my M$-Nano and yourself in regard
to the unplugging and re-plugging maneuver you suggested in post #3.

Replugging USB devices usually triggers some sort of discovery
and adjustment somewhere or other. Maybe in the device firm-ware,
maybe in the OS, or both.

My M$-Nano now works just as well in Linux as it does in Win7.
I'm happy enough right now with the settings chosen for me in
both situations.

In Win7, I think there may be some further adjustments possible.
In Knoppix 6.2.1, I've found three mouse adjustment avenues;
none of these affect my M$-Nano.

I think this thread has accomplished what I was looking for initially.
Someone else may want to start a thread on 'Linux tricks for a Nano',
I'm not that obsessive.

[mecho]

I am glad it works for you :-D happy NANO mousing

[mecho]

If you want to map all your mouse buttons there is very easy gui tool called btnx-config, you might want to give it a try

[utu]

@mecho

btnx-config is not in Debian stable, and I notice some complaints
in Ubuntu. So I think I'll pass on that. Remind me again when
it's in Debian stable.

Thanks for the idea. You seem to find a lot of good things out there.

[utu]

Postscript:

After a week or so, my nano began misbehaving again.
Unplugging and replugging fixed the behavior, again.

I frequently boot up in Win7, maybe nano gets confused.