Date: Tue, 21 Jun 2016 07:23:54 +0200 From: Polytropon <freebsd@edvax.de> To: emailrob@emailrob.com Cc: freebsd-questions@freebsd.org Subject: Re: slowing_down a super_fast mouse Message-ID: <20160621072354.575ae5a3.freebsd@edvax.de> In-Reply-To: <57689E95.2090502@emailrob.com> References: <57689E95.2090502@emailrob.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 21 Jun 2016 01:55:33 +0000, spellberg_robert wrote: > howdy , folks --- > > i hope that everyone is well . > > > > in anticipation of installing 10.3 , i have been buying new hardware > [ probably , intel "skylake" and "z170" , of some kind ] . > this new mechanical keyboard , "daskeyboard" , > with the cherry "blue" switches , is really nice , Yes, those are great, but nothing beats "IBM model M". :-) > [ before i did any editing , this post looked like > traudl junge's first effort for her new boss , > in that scene in "downfall" , at the beginning of the film > ] . Then compare to the "typist audition" in "Schindler's List" for improvement. :-) > the ps2 keyboards and mice actually have usb interfaces , > with usb/ps2 adapters , plugged into ps2 ports . > from what i read on wikipedia , > these should look like ps2 devices to the ps2 ports . > the six_years_old moboes --do-- have usb ports of some kind , > but this is my first usb equipment , > therefore , i have no usb experience . Then why don't you use them natively via USB? Basically, it should work out of the box (as the kernel provides ukbd and ums drivers). > so i start reading [ man_pages , handbook , et_cetera ] ; > eventually , i find the man_page about "/boot/device.hints" . > i find words like "flags" , "resolution" and "acceleration" . > i find an example for "psm0" . > this looks promising . > i check my boot messages ; > > psm0: <PS/2 Mouse> irq 12 on atkbdc0 > psm0: [GIANT-LOCKED] > psm0: model Intellimouse, device ID 3 > > these are the same messages as those for > the old mitsumi mouse on the 10.2 box ; > i get the impression that all ps2 mice are pretty much the same . The easiest way to configure the mouse behaviour for the console is using moused. In this case, accessing the settings via /dev/psm0 (through the PS/2->USB adapter) is quite easy: moused_enable="YES" moused_type="auto" moused_flags="-z 4" moused_port="/dev/cuaa0" moused_type="mousesystems" moused_flags="-r 300 -a 2.0" This is an example from one of my older systems where a serial mouse with 3 buttons needed adjustment for resolution and accelleration. See "man moused" for details about the required flags. In your case, you'd probably have to use moused_type="auto" moused_port="/dev/psm0" instead. You can try out various settings by first invoking moused with the -d -f flags (print debugging messages, run in foreground), and when you're happy with the settings, add them to /etc/rc.conf accordingly. Note that using moused with USB devices is not that trivial as it is controlled "dynamically" via devfs/devd, if I remember correctly. > i note that there are no "flags" ; so i try that . > i "guess" that flags of "0x01" and "0x04" will > disable "acceleration" and > set "resolution" to either extreme , one way or the other . > if this works , > then i should observe a 8:1 ratio for cursor distance ; > all that i have to do is to pick a "comfortable" setting . > > well , that was the plan . > it failed . As expected. :-) > let me emphasize : the new hardware --works-- . > it is just that the cursor goes flying across the screen , > for a small mouse_on_pad motion . > positioning --is-- challenging . > > the flags --are-- recognized ; they appear in the boot messages ; > for example , > > psm0: <PS/2 Mouse> flags 0x1 irq 12 on atkbdc0 > > but the behavior does not change on either the console or the xterm . The console has a different mouse driver than X. For X, you need to configure the mouse parameters using the tool your desktop environment provides. If you're not using a DE, consider using /etc/X11/xorg.conf. Again an example: Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Device" "/dev/sysmouse" Option "Protocol" "Auto" Option "ZAxisMapping" "4 5" Option "Emulate3Buttons" Option "EmulateWheel" Option "EmulateWheelButton" "2" EndSection You can set "Samplerate" and "Resolution" as well. You can find even more options in the documentation. > maybe the mouse has hardware limitations . That is possible. > maybe there is some "buzzword" , of which i am unaware . > which ignorance prevents further research by me . Yes, there is dynamic leverage synergetic mouse outsourcing for startup unicorn capital growth inflation. :-) > should i be trying to effect this change in "rc.conf" ? Yes. > should i be trying to effect this change in "X" ? Yes, as well. As I said, console and X use different mechanisms for the mouse, so there are two different configurations needed. > ps --- does anyone know how to > turn_off this narrow 65_column auto_wrap > in the "thunderbird" editor ? Why is that a problem? You should breat your lines between column 60 and 70. If you prefer to do this manually (as I do), you'll find the relevant setting in the message compose configuration, if I remember correctly. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160621072354.575ae5a3.freebsd>