[SOLVED - kinda] Xorg updates break mouse acceleration

I have a razer diamondback mouse, which until recently I'd been using xset m 1 0 to rein in.  Without this, the mouse has frighteningly high acceleration and is impossible to control.
After the updates it refuses to move unless I send it halfway across the pad first.  Running "xset m 1 1" suddenly makes the mouse impossible to control again.  There doesn't appear to be any middle ground.
Last edited by buttons (2007-11-06 16:54:20)

Well, it looks like there's a new, undocumented addition to xorg.conf, in the form of Option "Sensitivity" in your mouse section, a la:
Section "InputDevice"
    Identifier     "Configured Mouse"
    Driver          "mouse"
    Option       "Sensitivity" "0.5"
    Option         "CorePointer"
    Option         "Device" "/dev/input/mice"
    Option       "Protocol" "auto"
    Option         "ZAxisMapping" "4 5"
EndSection
Where Sensitivity can be anywhere from 0 to 1.0.  In addition, you must run
xset m 1 1
(disable acceleration and also have a threshold) to have the mouse work smoothly again.  As it is, a Sensitivity of around 0.4 or 0.5 roughly emulates what I had before.
Last edited by buttons (2007-11-06 16:59:34)

Similar Messages

  • [SOLVED] qemu-kvm update breaks libvirt

    I just recently upgraded to qemu-kvm 0.12.1.2-1
    Once I did this I was unable to start my VM's I received:
    error: Failed to start domain dns
    error: internal error unable to start guest: char device redirected to /dev/pts/1
    qemu: '' invalid format
    I just rolled back the package using the packages in
    /var/cache/pacman/pkg by pacman -U qemu-kvm-0.11.0-1-x86_64.pkg.tar.gz
    Last edited by papertigers (2010-02-25 16:01:15)

    After deciding to upgrade to the new one and actually figure out what the problem was I discovered it was a simple fix.
    To fix the problem I was getting I went into virt-manager and all you have to do is remove the machines hard drive and then reattach it.
    I was then able to boot the VM's.

  • [SOLVED] One last remaining hurdle with Xorg update

    [SOLVED] -- apparently one more reboot needed   Well, anyways, here's a working config for an nvidia laptop w/ Synaptics touchpad running LXDE/openbox
    Ok -- I fought through the Xorg update along with everyone else, and with the help of the wiki and the forums, managed to get everything working using the input hotplugging through hal. I have the nvidia driver & synaptics touchpad configured and working properly. The keyboard, including multimedia keys are working (with no .Xmodmap now) with one exception -- when I hit C-Esc to trigger the openbox menu, the menu opens up, but I can only scroll through it using the mouse - can't use the cursor arrows. Before the update, I could use the cursor arrows to scroll through the OB menu. Otherwise, the cursor arrows work normally in the terminal and firefox and other apps -- just that one instance I've found where they don't work. Any ideas? I've restarted X, hal, and the computer several times
    /etc/X11/xorg.conf
    # nvidia-xconfig: X configuration file generated by nvidia-xconfig
    # nvidia-xconfig: version 1.0 (buildmeister@builder58) Thu Jul 17 18:39:00 PDT 2008
    Section "ServerLayout"
    Identifier "X.org Configured"
    Screen 0 "Screen0" 0 0
    Screen 1 "Screen1" RightOf "Screen0"
    EndSection
    Section "Files"
    ModulePath "/usr/lib/xorg/modules"
    FontPath "/usr/share/fonts/misc"
    FontPath "/usr/share/fonts/100dpi:unscaled"
    FontPath "/usr/share/fonts/75dpi:unscaled"
    FontPath "/usr/share/fonts/TTF"
    FontPath "/usr/share/fonts/Type1"
    EndSection
    Section "Module"
    Load "extmod"
    Load "dbe"
    Load "glx"
    Load "xtrap"
    Load "record"
    Load "freetype"
    Load "synaptics"
    Load "evdev"
    EndSection
    Section "Monitor"
    Identifier "Monitor0"
    VendorName "Monitor Vendor"
    ModelName "Monitor Model"
    EndSection
    Section "Monitor"
    Identifier "Monitor1"
    VendorName "Monitor Vendor"
    ModelName "Monitor Model"
    EndSection
    Section "Device"
    Identifier "Card0"
    Driver "nvidia"
    VendorName "nVidia Corporation"
    BoardName "GeForce Go 7200"
    BusID "PCI:5:0:0"
    Option "NoLogo" "true"
    Option "MigrationHeuristic" "greedy"
    EndSection
    Section "Device"
    Identifier "Card1"
    Driver "nvidia"
    VendorName "nVidia Corporation"
    BoardName "MCP51 PMU"
    BusID "PCI:0:10:3"
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Card0"
    Monitor "Monitor0"
    Option "AddARGBGLXVisuals" "True"
    SubSection "Display"
    Viewport 0 0
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 4
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 8
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 15
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 16
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 24
    EndSubSection
    EndSection
    Section "Screen"
    Identifier "Screen1"
    Device "Card1"
    Monitor "Monitor1"
    Option "AddARGBGLXVisuals" "True"
    SubSection "Display"
    Viewport 0 0
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 4
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 8
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 15
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 16
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 24
    EndSubSection
    EndSection
    Section "Extensions"
    Option "Composite" "Enable"
    EndSection
    /etc/hal/fdi/policy/10-keymap.fdi
    <?xml version="1.0" encoding="ISO-8859-1"?> <!-- -*- SGML -*- -->
    <deviceinfo version="0.2">
    <device>
    <match key="info.capabilities" contains="input.keymap">
    <append key="info.callouts.add" type="strlist">hal-setup-keymap</append>
    </match>
    <match key="info.capabilities" contains="input.keys">
    <merge key="input.Xkb.rules" type="string">base</merge>
    <!-- If we're using Linux, we use evdev by default (falling back to
    keyboard otherwise). -->
    <merge key="input.Xkb.model" type="string">keyboard</merge>
    <match key="/org/freedesktop/Hal/devices/computer:system.kernel.name"
    string="Linux">
    <merge key="input.x11_driver" type="string">evdev</merge>
    <merge key="input.Xkb.model" type="string">evdev</merge>
    </match>
    <merge key="input.xkb.layout" type="string">us</merge>
    </match>
    </device>
    </deviceinfo>
    /etc/hal/fdi/policy/11-x11-synaptics.fdi
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <deviceinfo version="0.2">
    <device>
    <match key="info.capabilities" contains="input.touchpad">
    <match key="info.product" contains="Synaptics TouchPad">
    <merge key="input.x11_driver" type="string">synaptics</merge>
    <!-- Arbitrary options can be passed to the driver using
    the input.x11_options property since xorg-server-1.5. -->
    <!-- EXAMPLE:
    -->
    <merge key="input.x11_options.AlwaysCore" type="string">true</merge>
    <merge key="input.x11_options.Protocol" type="string">auto-dev</merge>
    <merge key="input.x11_options.Emulate3Buttons" type="string">true</merge>
    <merge key="input.x11_options.SHMConfig" type="string">false</merge>
    <merge key="input.x11_options.LeftEdge" type="string">1700</merge>
    <merge key="input.x11_options.RightEdge" type="string">5300</merge>
    <merge key="input.x11_options.TopEdge" type="string">1700</merge>
    <merge key="input.x11_options.BottomEdge" type="string">4200</merge>
    <merge key="input.x11_options.FingerLow" type="string">25</merge>
    <merge key="input.x11_options.FingerHigh" type="string">30</merge>
    <merge key="input.x11_options.MaxTapTime" type="string">180</merge>
    <merge key="input.x11_options.VertEdgeScroll" type="string">true</merge>
    <merge key="input.x11_options.HorizEdgeScroll" type="string">true</merge>
    <merge key="input.x11_options.CornerCoasting" type="string">true</merge>
    <merge key="input.x11_options.CoastingSpeed" type="string">0.30</merge>
    <merge key="input.x11_options.VertScrollDelta" type="string">100</merge>
    <merge key="input.x11_options.HorizScrollDelta" type="string">100</merge>
    <merge key="input.x11_options.MinSpeed" type="string">0.10</merge>
    <merge key="input.x11_options.MaxSpeed" type="string">0.60</merge>
    <merge key="input.x11_options.AccelFactor" type="string">0.0020</merge>
    <merge key="input.x11_options.VertTwoFingerScroll" type="string">true</merge>
    <merge key="input.x11_options.HorizTwoFingerScroll" type="string">true</merge>
    <merge key="input.x11_options.TapButton1" type="string">1</merge>
    <merge key="input.x11_options.TapButton2" type="string">2</merge>
    <merge key="input.x11_options.TapButton3" type="string">3</merge>
    </match>
    <match key="info.product" contains="AlpsPS/2 ALPS">
    </match>
    <match key="info.product" contains="appletouch">
    </match>
    <match key="info.product" contains="bcm5974">
    </match>
    </match>
    </device>
    </deviceinfo>
    Xorg.log
    Thanks!
    Scott
    Last edited by firecat53 (2008-12-01 20:45:09)

    https://bbs.archlinux.org/viewtopic.php?id=116791

  • [Solved-ish] problem with autologin after xorg update

    Hi
    I use auto login like described on "Automatic login to virtual console", with the exception that i login as user on VT7 rather than VT1.
    Then execute startx on VT7 from zprofile, as shown in Start X at Login.
    After updating xorg this morning, I was on VT1 after boot. The screen was kind of blinking once a second, and totally unresponsive.
    Booting from the install image on an USB-stick, I commented startx in ~/.zprofile.
    After that I was again on VT1 but able to login and then run startx on VT1. Later I found out that I had a login on VT7 and was able to run startx there as well.
    Why wouldn't startx run automatically, when it runs fine manually.
    This is my [email protected]/autologin.conf
    nagual% cat [email protected]/autologin.conf
    [Service]
    ExecStart=
    ExecStart=-/sbin/agetty --autologin leo --noclear %I 38400 linux
    Type=simple
    startx is run from zprofile with:
    #[[ -z $DISPLAY && $XDG_VTNR == 7 ]] && exec startx -- vt$XDG_VTNR
    could it be because the display doesn't change to VT7, and why would an xorg update change that?
    Last edited by Leo Laursen (2014-07-30 17:54:14)

    mrunion wrote:When the upgrade to xorg-server occurred there was a warning about X starting on the appropriate VT. There was also news on the Arch Linux front page (https://www.archlinux.org/news/xorg-ser … available/). You may want to read that news and then look into an xorg.wrap file if necessary.
    Thanks. I did see this. As far as I can tell, it shouldn't matter in my case, but of course I could be wrong. I'm starting X on VT7, same as the login. I don't do any redirecting of stderr.
    And it is very curious that auto login is affected.

  • Anyone have an xorg mouse acceleration profile that is close to Win7?

    Full disclosure I'm using Fedora but have a base install with only X11 and icewm (arch has better wiki). I'm trying to configure everything through the xserver. Right now I'm using the settings that are supposed to disable mouse acceleration completely found here: https://wiki.archlinux.org/index.php/Mouse_acceleration
    /etc/X11/xorg.conf.d/50-mouse-acceleration.conf
    Section "InputClass"
    Identifier "My Mouse"
    MatchIsPointer "yes"
    Option "AccelerationProfile" "-1"
    Option "AccelerationScheme" "none"
    EndSection
    It's better than what it was with no configuration file (evdev defaults?) but I think I would like to tweak it a little. Since I'm most used to Windows mouse acceleration I was wondering if anybody knew of settings close to that I could use?

    Well since there are many variables to contend with, I thought I might try asking for some sane defaults first that were comparable to those on Windows. I've tried configuring mouse acceleration before via 3rd party drivers and always have to rely on trial and error which is not very productive. That's why I just decided to disable everything as a baseline.

  • Xorg update seems to break ATI Catalyst

    Hi all
    Just a quick note for users of the proprietary ATI Catalyst driver, the latest Xorg update seems to break it (at least on my system).
    Boot sequence proceeds as normal until GDM loads, then the screen oscillates slowly between black and white.
    Any suggested fix?

    Hi there
    Did Pacman upgrade your kernel alongside Xorg?. Maybe you need to rebuild the fglrx module.
    Best of Luck

  • [SOLVED] xorg update has broken nvidia-173xx driver

    Hi,
    I've been using arch for around 2 and a half months on 2 computers (a dell Inspiron 2200 and an old home built pc). So far I've been able to figure out most things myself.  However, following today's xorg update x seems to be broken. My laptop, which does not use nvidia, seems to be fine. On the pc i installed the i686 version and am running kde 4.5.1
    I have reinstalled nvidia-173xx and nvidia-173xx-utils, and run nvidia-xconfig but this has not helped any.
    Although the installation is carried out there is an error stating:
    ERROR: Module nvidia does not exist in /proc/modules In order to use the new nvidia driver, exit xserver and unload it manually
    A google search on the above error didn't advance me any further, either.
    I have also waited for today's kernel update but that hasn't seemed to fix things.
    If I run "startkde" i get an error message stating that it can't connect to the x server.
    "startx" says much the same only more verbose.
    /var/log/Xorg.0.log has the following information :
    dlopen: /usr/lib/xorg/modules/drivers/nvidia_dvr.so undefined sym$
    failed to load /usr/lib/xorg/modules/drivers/nvidia_dvr.so
    unloadable module "nvidia"
    failed to load module "nvidia" (loader failed, 7)
    I've done a lot of esearch but can't find any solutions to my issue. The following thread seems to be related :
    https://bbs.archlinux.org/viewtopic.php?id=103716
    but i can't seem to find an answer there either.
    Any help would be appreciated.
    Cheers
    Last edited by rabid_works (2010-09-29 19:32:42)

    ok, went to downgrade using
    #pacman -U ...
    but i have yet another error due to a conflict between files :
    xorg-server: /usr/lib/xorg/protocol.txt is already present in the file system
              xorg-server: /usr/share/man/Xserver.1.gz is already present on the file system
              xorg-server; /usr/share/xkb/README.compiled is afready present in the file system
    is it possible to safely force the installation?
    sorry if thatś a lazy question but I've been looking at this for so long that i can't fathom the idea of futher searching.
    EDIT: ok, i had a break and realised it'd be safer to simply rename and the delete the problematic files. The downgrade went fine. I have X back.
    thanks for the help.
    Last edited by rabid_works (2010-09-29 18:52:27)

  • [SOLVED] Disabling Mouse Acceleration / Mouse unresponsive

    Hi,
    I play CSGO and need my mouse to be responsive with no mouse acceleration. Everything works find under Ubuntu 15.04 using the old xinput method of disabling mouse acceleration. However under Arch my mouse is really sensitive and unresponsive when making very small movements at slow speed (moving slightly to get a headsot at range in CSGO requires some presision)
    I've read the wiki page a coule of times and tried two different configs. Looking at diffs of my Xorg log the configs are getting picked up but seems to do very little. There doesnt appear to be any errors in Xorg log.
    I installed the full Xorg group am I missing a component of Xorg or a mouse driver?
    My Mouse is Gigabyte M6900
    http://www.gigabyte.com/products/produc … id=3616#ov
    Name           : xorg-server
    Version        : 1.17.1-5
    uname -a
    Linux desktop 4.0.4-1-ARCH #1 SMP PREEMPT Mon May 18 06:43:19 CEST 2015 x86_64 GNU/Linux
    First mouse accelleration config file as described in the wiki
    /etc/X11/xorg.conf.d/50-mouse-acceleration.conf
    Section "InputClass"
    Identifier "Areson USB Device"
    MatchIsPointer "yes"
    Option "AccelerationProfile" "-1"
    Option "AccelerationScheme" "none"
    EndSection
    The very first example of the wiki shows some settings for disabling mouse accelleration but still no joy
    Section "InputClass"
    Identifier "Areson USB Device"
    MatchIsPointer "yes"
    Option "AccelerationProfile" "-1"
    Option "AccelerationScheme" "none"
    Option "AccelerationNumerator" "1"
    Option "AccelerationDenominator" "1"
    Option "AccelerationThreshold" "0"
    EndSection
    A Diff of these Xorg log between the two config files
    < [ ] (==) Log file: "/var/log/Xorg.0.log", Time: Fri May 22 15:53:29 2015
    > [ ] (==) Log file: "/var/log/Xorg.0.log", Time: Fri May 22 17:45:05 2015
    346,347c346,350
    < [ ] (**) Areson USB Device: (accel) acceleration factor: 2.000
    < [ ] (**) Areson USB Device: (accel) acceleration threshold: 4
    > [ ] (**) Option "AccelerationNumerator" "1"
    > [ ] (**) Option "AccelerationDenominator" "1"
    > [ ] (**) Option "AccelerationThreshold" "0"
    > [ ] (**) Areson USB Device: (accel) acceleration factor: 1.000
    > [ ] (**) Areson USB Device: (accel) acceleration threshold: 0
    egrep -i 'error|fail|firmware' /var/log/Xorg.0.log
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 112.912] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    [ 114.973] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
    Last edited by fixles (2015-05-22 20:34:45)

    brebs wrote: Here is the libinput bug report re acceleration - it ain't fully disabling acceleration.
    So it doesnt work but its not broken? lol
    as for AccelSpeed -1, you're correct that it currently does some deceleration below the threshold. having said that, the pointer accel code isn't finished yet either, e.g. it doesn't do any constant deceleration, so the -1 setting is a bit off anyway.
    I can't promise you a timeline or whether this will get fixed in the way you want it to. we're trying to simplify a couple of things, pointer acceleration is one of those, and that means that not every configuration that was previously possible will be possible in the future.
    Followed up by a pretty funny response.
    Honestly that sounds a bit like "we know what you want better than you know what you want". libinput isn't secretly a Gnome project is it?

  • Disabling mouse acceleration temporarily?

    With older versions of the X server I could disable mouse acceleration temporarily using "xset m 0 0", but as the wiki says it doesn't have the same effect anymore: https://wiki.archlinux.org/index.php/Mo … celeration
    I'd like to reconfigure the exact same behavior as the previous mouse algorithms. Is this possible?
    Thank you!

    See AccelerationProfile in xorg wiki.
    You probably want:
    0. classic (the default) similar to old behaviour, but more predictable
    E.g. I use:
    xinput set-prop Mouse "Device Accel Profile" -1
    xinput set-prop Mouse "Device Accel Constant Deceleration" 7.0
    (I defined "Mouse" in xorg.conf)

  • Can't adjust Logitech mouse acceleration, mouse is too fast

    Hi.
    I have setup Arch with XFCE. Almost everything works fine, except mouse. I have Logitech M185 wireless mouse and it is too fast. I have tried to set mouse acceleration and sensitivity in Xfce mouse settings (without any affect) and via xset or xinput as described in this article, but nothing happened - it still goes way too fast.
    Here is an output of xinput list (don't know why, but there is two different "Logitech USB Receiver" devices):
    $ xinput --list
    ⎡ Virtual core pointer id=2 [master pointer (3)]
    ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
    ⎜ ↳ Logitech USB Receiver id=10 [slave pointer (2)]
    ⎜ ↳ Logitech USB Receiver id=11 [slave pointer (2)]
    ⎜ ↳ bcm5974 id=13 [slave pointer (2)]
    ⎣ Virtual core keyboard id=3 [master keyboard (2)]
    ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
    ↳ Power Button id=6 [slave keyboard (3)]
    ↳ Video Bus id=7 [slave keyboard (3)]
    ↳ Power Button id=8 [slave keyboard (3)]
    ↳ Sleep Button id=9 [slave keyboard (3)]
    ↳ Apple Inc. Apple Internal Keyboard / Trackpad id=12 [slave keyboard (3)]
    And devices properties:
    $ xinput list-props 10
    Device 'Logitech USB Receiver':
    Device Enabled (133): 1
    Coordinate Transformation Matrix (135): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
    Device Product ID (251): 1133, 50479
    Device Node (252): "/dev/input/event9"
    Evdev Axis Inversion (266): 0, 0
    Evdev Axes Swap (268): 0
    Axis Labels (269): "Rel X" (143), "Rel Y" (144), "Rel Horiz Wheel" (260), "Rel Vert Wheel" (261)
    Button Labels (270): "Button Left" (136), "Button Middle" (137), "Button Right" (138), "Button Wheel Up" (139), "Button Wheel Down" (140), "Button Horiz Wheel Left" (141), "Button Horiz Wheel Right" (142), "Button Side" (255), "Button Extra" (256), "Button Forward" (257), "Button Back" (258), "Button Task" (259), "Button Unknown" (254), "Button Unknown" (254), "Button Unknown" (254), "Button Unknown" (254), "Button Unknown" (254), "Button Unknown" (254), "Button Unknown" (254), "Button Unknown" (254), "Button Unknown" (254), "Button Unknown" (254), "Button Unknown" (254), "Button Unknown" (254)
    Evdev Middle Button Emulation (271): 0
    Evdev Middle Button Timeout (272): 50
    Evdev Third Button Emulation (273): 0
    Evdev Third Button Emulation Timeout (274): 1000
    Evdev Third Button Emulation Button (275): 3
    Evdev Third Button Emulation Threshold (276): 20
    Evdev Wheel Emulation (277): 0
    Evdev Wheel Emulation Axes (278): 0, 0, 4, 5
    Evdev Wheel Emulation Inertia (279): 10
    Evdev Wheel Emulation Timeout (280): 200
    Evdev Wheel Emulation Button (281): 4
    Evdev Drag Lock Buttons (282): 0
    $ xinput list-props 11
    Device 'Logitech USB Receiver':
    Device Enabled (133): 1
    Coordinate Transformation Matrix (135): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
    Device Accel Profile (262): 0
    Device Accel Constant Deceleration (263): 1.000000
    Device Accel Adaptive Deceleration (264): 1.000000
    Device Accel Velocity Scaling (265): 10.000000
    Device Product ID (251): 1133, 50479
    Device Node (252): "/dev/input/event10"
    Evdev Axis Inversion (266): 0, 0
    Evdev Axes Swap (268): 0
    Axis Labels (269): "Rel X" (143), "Rel Y" (144), "Rel Horiz Wheel" (260)
    Button Labels (270): "Button 0" (283), "Button Unknown" (254), "Button Unknown" (254), "Button Wheel Up" (139), "Button Wheel Down" (140), "Button Horiz Wheel Left" (141), "Button Horiz Wheel Right" (142)
    Evdev Middle Button Emulation (271): 0
    Evdev Middle Button Timeout (272): 50
    Evdev Third Button Emulation (273): 0
    Evdev Third Button Emulation Timeout (274): 1000
    Evdev Third Button Emulation Button (275): 3
    Evdev Third Button Emulation Threshold (276): 20
    Evdev Wheel Emulation (277): 0
    Evdev Wheel Emulation Axes (278): 0, 0, 4, 5
    Evdev Wheel Emulation Inertia (279): 10
    Evdev Wheel Emulation Timeout (280): 200
    Evdev Wheel Emulation Button (281): 4
    Evdev Drag Lock Buttons (282): 0
    I have played around with "Device Accel Constant Deceleration" property, but it does not affect anything.
    How can I slow down my mouse?
    Last edited by ch1p (2013-08-13 09:34:34)

    ch1p wrote:two different "Logitech USB Receiver" devices
    See thread.
    Haven't used it in a while, but my xorg.conf contained:
    Section "InputClass"
    # Logitech VX Nano, 800 DPI
    # http://forums.gentoo.org/viewtopic.php?p=6676035
    Identifier "USB wireless receiver for mouse"
    Driver "evdev"
    Option "AccelerationProfile" "-1"
    Option "ConstantDeceleration" "3.1"
    Option "Resolution" "800"
    Option "SampleRate" "500"
    # Posted at http://forums.gentoo.org/viewtopic-p-7265410.html#7265410
    # From lsusb
    MatchUSBID "046d:c526"
    MatchDevicePath "/dev/input/event*"
    EndSection
    So use lsusb and tweak it.
    Or even easier, use xinput to tweak on-the-fly.

  • Mouse Acceleration Curve Discussion

    First, let me say that I'm familiar with the differences in the Mac OS mouse acceleration curve versus the more linear curve in Windows and X11. I'm a very happy Switcher and am loving my new iMacs and laptop (yes, I have several), except for that darned mouse acceleration curve. (A quick search on Google with "Mac mouse acceleration curve" and you'll see what I mean.)
    I have been trying for a few months to get used to it, and it's okay, but I definitely feel the difference when switching back and forth between Mac and Windows at work.
    I am familiar with SteerMouse, MouseFix, and USBoverdrive, as well as the Microsoft mouse drivers. However, I'm disappointed that none of them feel exactly like my trusty Logitech on Windows (I'm using the wireless Mighty Mouse at home). To be exact, the low end of the acceleration curve requires to much movement, and the Mac curve creates jerky wrist motions.
    I'm not sure I understand why the curve cannot be optionally adjusted to be exactly the same as on other operating systems, and not just a kludged approximation thereof.
    I will continue to try to adapt to switching back and forth between the platforms, but I'm always looking for solutions to this.
    Does anyone out there have any advice on the matter? Any stories about switching back and forth? Do I just need to continue to be patient and adjust? Any word of perhaps an acceleration adjustment option coming in Snow Leopard? I'd like to see some constructive technical discussion on this.

    Unfortunately, mouse acceleration curve is not the only problem with Leopard's mouse handling. I'm very satisfied with my Mac Pro and OS X in general, not a fetishist though. There are always positive and negative things around a particular platform, the Mac is not an exeption either. Every minor issue with the Mac I have stumbled upon so far, however, either admitted straightforward (and cheap) solution, or was simply a matter of taste, not a real headache at all. Not the case for the mouse.
    To say the least, the acceleration curve is not ergonomic, what is more, it is fixed. You can't even switch it off completely unless you make do with the lowest speed (i.e resolution) setting. This behavior is hard wired into the kernel. On the other hand, mouse pointer has a shaky movement (on every Mac and every mouse I assume), with distinct feel of lack of precise control over the pointer. Try a high precision laser mouse (Logitech, Razer, etc.) in OS X (Leopard) and in XP and you'll know what I'm talking about.
    I know there are 3rd party utilities like SteerMouse and USB Overdirve, but 1) they don't resolve the issue completely, 2) the are not freeware. I'm sure that if the same problem had been found in Windows, in no time there would have been around 10 freeware utilities to be found that offer a solution. Why even these 3rd party utilities can't fix the problem? Strange enough when considering the fact that the core of OS X is open source (Darwin) and well documented. Hasn't anybody recognized yet that mouse in OS X doesn't behave the way it should (not even considering the acceleration problem).
    Is the Apple USB HID driver the culprit? My Razer mouse has an OEM driver, not for the better, though. Is the bug in the kernel? Maybe the case. I hope one day a programmer can tell me what kind of OS workings are responsible for the shaky cursor movement. In the ideal and most simple case, the mouse sensor coordinates, which are very precise, high resolution and reliable in case of any professional mouse, would be polled by an USB HID driver with reasonable (and user settable) frequency, and these coordinates would than be forwarded to the graphics routines that map them to screen coordinates. If the user like, the mapping should be 1-to-1 and "realtime". In OS X anything is easier to achive than 1-to-1 and low latency mapping.
    I can set totally useless sensitivity and acceleration values, but how can I set that if I move my 100$ mouse 1/2000 inch to the left, the cursor move exactly(!) one pixel to the left. Let me tell you what I mean by "advanced" in the 21. century: if a modern "cool looking" OS running on a multicore, multigigahertz, multigigabyte, multigeneration, multi1000dollar worth machine is able to track my moderate hand movements with 1/2000 precision with less than noticeable latency and inaccuracy, if I like it to. Talking about professional work...
    And for me the question remains: why the "most advanced OS" struggles with a problem that has never been a problem in any of the less advanced OSs?

  • ITunes 11.3.1 update breaks iTunes on my mac.

    iTunes 11.3.1 update breaks iTunes on my mac. iTunes window will not display following update.

    Launch the Console application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
    The title of the Console window should be All Messages. If it isn't, select
              SYSTEM LOG QUERIES ▹ All Messages
    from the log list on the left. If you don't see that list, select
              View ▹ Show Log List
    from the menu bar at the top of the screen.Click the Clear Display icon in the toolbar. Then take one of the actions that you're having trouble with. Select any messages that appear in the Console window. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
    The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.
    Please don't indiscriminately dump thousands of lines from the log into this discussion.
    Please don't post screenshots of log messages—post the text.
    Some private information, such as your name, may appear in the log. Anonymize before posting.

  • What are the things 10.6.8 update break?

    After the 10.6.8 update I am having so many issues,
    first, the %100 cpu usage of dock, disabled parallels, and now it is ok,
    then, a reboot and I am unable to login, I enter my password, it begins the login process, then logs me out,
    if I persist, it logs me in after a couple of tries, but each time a few of my applications are missing at random, and the environment is very very unstable, sometimes I see no desktop background, sometimes I start firefox and I am logged out again.
    I've seen some people suggesting removal of login items to resolve a similar but not the same issue, so I'm inclined to think overall, there is an issue with some applications which 10.6.8 update breaks.
    For starters my login items are:
    GrowlHelper
    Geektool
    EyeTv Helper
    Canon IJ Network scanner
    ituneshelper
    Magicprefs
    Sophosuiserver
    Does anyone have any problems with any of these?
    I only verified the parallels desktop 6 issue up to now.
    Model Name: MacBook Pro
      Model Identifier: MacBookPro6,2
      Processor Name: Intel Core i7
      Processor Speed: 2.66 GHz
      Number Of Processors: 1
      Total Number Of Cores: 2
      L2 Cache (per core): 256 KB
      L3 Cache: 4 MB
      Memory: 8 GB
      Processor Interconnect Speed: 4.8 GT/s
      Boot ROM Version: MBP61.0057.B0C
      SMC Version (system): 1.58f15

    Actually it is not-so-permitted to remove sophos for this machine, but I did it anyhow. No problem so far, but lack of evidence is not evidence of being lack of something so I am not adding it to the list yet

  • Is there a way to disable mouse acceleration in OSX Yosemite?

    i have used my dads iMac and MBP in the past and always noticed how bad the mouse response was in my opinion. Mind you, some people like the way the mouse responds in OSX and will probably have no idea what my issue is. That is mouse acceleration and the lack of option to disable it in the mouse settings panel. Here is a good explanation about what it is, also in the video is a visual example.
    "Mouse or cursor acceleration, to put it simply, makes the travel distance of your cursor on the screen reliant of the velocity of your physical mouse movement rather than just the distance that you move your mouse. So making one movement of the same distance at two different speeds will cause two different relative cursor movements, with quick movement causing the cursor to travel a greater distance."
    source:
    https://www.youtube.com/watch?v=16diwK6HWbI
    So the thing i want to accomplish, is making the physical mouse movement one-to-one with the cursor speed on the screen. As an example: moving my mouse 10 cm would always make my mouse on the screen go 1000 pixels, no matter how fast i move my mouse.
    I've had my mouse set up like that in windows and linux for quite some time now and i hope there is an easy way to set the mouse response like that in OSX as well.
    I want to make clear that this isn't just an issue in games where you want to have great mouse precision. I have become really accustomed to this way of mouse response in any type of application. So the problem lies not in any mouse settings of any game/program. The problem lies in how OSX translates physical mouse movement to cursor movement.
    Anyway, i ran into this issue about a year ago when i was using my dad's computer. i've had my own windows computer for some time now. An option to disable mouse acceleration in OSX Yosemite might have been implemented properly in the mean time. I have searched this community and found some old posts of people who had this same problem as me, but never read about any fix for it. The main reason i am asking this is because i am considering buying a Macbook.
    I'd rather not use any third party software, but if there is any out that that just works and is easy to use, let me know.

    Please don't be obnoxious to people like tbirdvet trying to help; nobody here owes you an answer, or anything else for that matter.
    Anyway, Yosemite seems to enable mouse acceleration by default. You can disable it to get a constant pixels pointer moves / meters mouse moved ratio by typing this in terminal:
         defaults write .GlobalPreferences com.apple.mouse.scaling -1
    you'll need to logout and log back in for changes to take effect. To restore the standard behaviour:
         defaults write .GlobalPreferences com.apple.mouse.scaling 2
    should do the trick.
    C.

  • XFCE Keyboard Layout applet not working after latest xorg update..

    Is this a bug in the xorg update or most the kbd layou be reompiled or? I am not able to swtich between my two kbd layouts anymore.. Downgrading the org packages made it work again but I guess that's not a long term solution...
    Regards,
    BTJ

    Hi mattywix - can you add any more detail please ?
    I have a recent experience that sounds related to your problem - I have a 15" macbook pro bought new in the UK a couple of years ago (macbookpro 5,3), which has been running perfectly under snow leopard until a couple of days ago when my trackpad stopped recognising the standard "left" click.
    "Right" click, scroll and pointer movement continued to work fine.
    Booting in safe mode seemed to give me back the left click but this was immediately lost when I returned to standard boot up.
    Doing a full reinstall from original disks, all seemed fine. Over 1.6Gb of software updates and everything worked great. Then the final run of S/W update took me from os-x 10.6.6 to 10.6.7 plus a few other changes and again the trackpad stopped recognising "left" click.
    Plugging in an external drive which had a copy of my system as at OS-X 10.6.3 and booting off that - everything works fine again.
    I can only conclude that there's an issue with the 10.6.7 upgrade and my 2 year old MBP hardware so will have to reinstall yet again but stop at 10.6.6
    My concern is that after the first upgrade to 10.6.7 I put the laptop on charge to top it up from about 70% and came back to find the machine abnormally hot. With your comment about toasting the logic board, I wonder if there's a bug in the power control software too which I was lucky enough to catch before my machine suffered the same damage as yours ?
    Sorry to hear about your bad luck but thanks for warning us about it.
    Alick

Maybe you are looking for