Configuring USB mouse in XFree

Hey, I just installed arch, and I'm having trouble getting X to see my mouse.
It gets an error on the line in XF86Config that gives the mouse location
default /dev/mouse doesn't work.
It's a USB Logitech MouseMan Dual Optical.
I've taken a look through /dev and tried anything obvious that I thought would work but still no go...
Is there a way to find out where my mouse is located? Or perhaps someone has had this problem before, and can help me with a solution.
Thanks!

the usb modules are all included directly in the kernel as i can see....
because i am running a microsoft intelli with usb, and it works with this configs in the XF86Config :
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mice"
Option "Buttons" "7"
Option "ZAxisMapping" "6 7"
but i also use imwheel to use all the buttons ... if anyone cares here the configs :
in .xinitrc
xmodmap -e "pointer = 1 2 3 6 7 4 5"
imwheel -k -p -b "67"
_before_ u start the WM
and then in the .imwhellrc
None, Up, Alt_L|Left
None, Down, Alt_L|Right
i guess it should also work with most 5-button+wheel mice.....
greetz

Similar Messages

  • Cant configure Apple USB mouse?

    I have an Apple clear USB mouse (no right click or wheel, but has pressure buttons, model M5769) plugged into my eMac running 10.4.11. For some reason when I go to mouse settings I only get the option to change tracking and click speed, no options for setting up the pressure side buttons at all. Any ideas?
    Thanks
    Ben

    Hi Ben, and a warm welcome to the forums!
    I have no adjustment for that either in 10.4.11 with that Mouse, iirc I did at one time, maybe in 10.2/10.3(?), but when I did have it I had to disable them as they're positioned totally wrong for my paw & were always going off.
    You can likely get their functions with USB Overdrive - 3.0.1 though...
    http://www.versiontracker.com/dyn/moreinfo/macosx/13443

  • MSI 880GM-e35 Wakeing up from sleep by USB mouse or USB keyboard

    I have two 880gm-e35 boards that will not wake up from sleep by Keyboard or mouse. (S3) sleep condition.
    -They wake up by tapping the power button..ok.
    On the E-35 boards If I set the (S1) Sleep condition where the fans stay on and power light does not blink, they wake up by USB mouse.
    I have a 880gm-e43 that does wake up from (S3)  sleep by usb mouse or keyboard.
    They are configured about the same, the E43 has a couple more options in that area but basically the same.
    Is that normal, The Bios kind of implies that it should wake up from S3, but no luck.
    Not a big deal, but I would prefer the USB wakeup, if possible..!

    Thanks for the reply. On the right track, but could not find that option.
    maybe I will look to see if they have other bios options for that board.
    Thanks again...

  • Xorg 1.8 Laser USB Mouse

    I recently bought a wireless usb laser mouse and keyboard, keyboard works fine but the mouse is giving me some headaches.
    Using gnome I can change the acceleration and sensitivity of it but not enough for my liking. I've read on the Xorg wiki about acceleration that can modified in xorg.conf but it makes no sense to me whatsoever. Can someone help me with this please? Below is what I have found is xorg log if it's any help.
    [ 540.718] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event10)
    [ 540.718] (**) Logitech USB Receiver: Applying InputClass "evdev pointer catchall"
    [ 540.718] (**) Logitech USB Receiver: Applying InputClass "evdev keyboard catchall"
    [ 540.718] (**) Logitech USB Receiver: always reports core events
    [ 540.718] (**) Logitech USB Receiver: Device: "/dev/input/event10"
    [ 540.730] (II) Logitech USB Receiver: Found 12 mouse buttons
    [ 540.730] (II) Logitech USB Receiver: Found scroll wheel(s)
    [ 540.730] (II) Logitech USB Receiver: Found relative axes
    [ 540.730] (II) Logitech USB Receiver: Found x and y relative axes
    [ 540.730] (II) Logitech USB Receiver: Found absolute axes
    [ 540.730] (II) Logitech USB Receiver: Found keys
    [ 540.730] (II) Logitech USB Receiver: Configuring as mouse
    [ 540.730] (II) Logitech USB Receiver: Configuring as keyboard
    [ 540.730] (**) Logitech USB Receiver: YAxisMapping: buttons 4 and 5
    [ 540.730] (**) Logitech USB Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    PS. My laser mouse is very sensitive on win7 too despite messing with settings, is this the norm of laser mice?

    To change systemwide defaults you need to create a file in  /etc/X11/xorg.conf.d/ , for example 50-input-mouse.conf
    and then put in:
    Section "InputClass"
    Identifier "mouse slowdown"
    MatchIsPointer "on"
    MatchProduct "yourmousename"
    Option "ConstantDeceleration" "0.5"
    Option "AccelerationProfile" "-1"
    EndSection
    replace yourmousename with what your mouse is called (or part of the name). You can find it with
    xinput --list
    And replace 0.5 and -1 to your liking. In my case I have added a constant little slow down to my mouse, and completely disabled accel.
    Optionally to change it only for your current x session:
    find property name :
    xinput --list-props "yourdevicename"
    set the property:
    xinput --set-prop "yourdevicename" "Device Accel Profile" "-1"
    You need to do this everytime you start x, so put it in some autostart script.
    Last edited by rwd (2010-06-27 09:10:36)

  • Evdev Doesn't Work for the USB Mouse

    Hey There,
    I'm using xorg.conf because Xorg 7.3 doesn't do several things I need.. (keyboard layouts, nvidia driver, synaptics, etc..)
    Any way, my xorg.conf used to work fine until I upgraded to 7.3 today.. I know that nvidia legacy (96xx) driver doesn't work because of the ABI change in this version, so I'm not mentioning about it..
    The biggest problem I have right now is that my USB mouse doesn't work now with evdev.. I had to change evdev to mouse and protocol to auto instead which confuses and distracts me..
    I think that evdev has some problems recognizing..
    This is my xorg.conf file:
    Section "ServerLayout"
        Identifier     "Xorg Configured"
        Screen      0  "Screen0" 0 0
        InputDevice    "Keyboard0" "CoreKeyboard"
        InputDevice    "Synaptics Touchpad" "CorePointer"
            InputDevice    "USB Mouse" "SendCoreEvents"
    EndSection
    Section "ServerFlags"
        Option "AllowMouseOpenFail"  "true"   
    EndSection
    Section "Files"
        RgbPath      "/usr/share/X11/rgb"
        ModulePath   "/usr/lib/xorg/modules"
        FontPath     "/usr/share/fonts/misc:unscaled"
        FontPath     "/usr/share/fonts/misc"
        FontPath     "/usr/share/fonts/75dpi:unscaled"
        FontPath     "/usr/share/fonts/75dpi"
        FontPath     "/usr/share/fonts/100dpi:unscaled"
        FontPath     "/usr/share/fonts/100dpi"
        FontPath     "/usr/share/fonts/PEX"
    # Additional fonts: Locale, Gimp, TTF...
        FontPath     "/usr/share/fonts/cyrillic"
    #    FontPath     "/usr/share/lib/X11/fonts/latin2/75dpi"
    #    FontPath     "/usr/share/lib/X11/fonts/latin2/100dpi"
    # True type and type1 fonts are also handled via xftlib, see /etc/X11/XftConfig!
        FontPath     "/usr/share/fonts/Type1"
        FontPath     "/usr/share/fonts/ttf/western"
        FontPath     "/usr/share/fonts/ttf/decoratives"
        FontPath     "/usr/share/fonts/truetype"
        FontPath     "/usr/share/fonts/truetype/openoffice"
        FontPath     "/usr/share/fonts/truetype/ttf-bitstream-vera"
        FontPath     "/usr/share/fonts/latex-ttf-fonts"
        FontPath     "/usr/share/fonts/defoma/CID"
        FontPath     "/usr/share/fonts/defoma/TrueType"
    EndSection
    Section "Module"
            Load  "ddc"  # ddc probing of monitor
        Load  "dbe"
        Load  "dri"
        Load  "extmod"
        Load  "glx"
            Load  "bitmap" # bitmap-fonts
        Load  "type1"
        Load  "freetype"
        Load  "record"
        Load  "synaptics"
    EndSection
    Section "InputDevice"
        Identifier  "Keyboard0"
        Driver      "keyboard"
        Option "XkbRules" "xorg"
        Option "XkbModel" "pc105"
        Option "XkbLayout" "tr,de"
        Option "XkbVariant" ""
        Option "XkbOptions" "grp:alt_shift_toggle"
    EndSection
    Section "InputDevice"
      Identifier   "Synaptics Touchpad"
      Driver       "synaptics"
      Option        "Device"                "/dev/psaux"
      Option        "Protocol"              "auto-dev"
      Option        "LeftEdge"              "120"
      Option        "RightEdge"             "830"
      Option        "TopEdge"               "120"
      Option        "BottomEdge"            "650"
      Option        "FingerLow"             "14"
      Option        "FingerHigh"            "15"
      Option        "MaxTapTime"            "180"
      Option        "MaxTapMove"            "110"
      Option        "EmulateMidButtonTime"  "75"
      Option        "VertScrollDelta"       "34"
      Option        "HorizScrollDelta"      "42"
      Option        "MinSpeed"              "0.9"
      Option        "MaxSpeed"              "1.2"
      Option        "AccelFactor"           "0.01"
      Option        "EdgeMotionMinSpeed"    "15"
      Option        "EdgeMotionMaxSpeed"    "15"
      Option        "UpDownScrolling"       "1"
      Option        "CircularScrolling"     "0"
      Option        "CircScrollDelta"       "0.1"
      Option        "CircScrollTrigger"     "0"
      Option        "SHMConfig"     "on"
    EndSection
    Section "InputDevice"
            Identifier      "USB Mouse"
            Driver          "mouse"
            Option          "Device"                "/dev/input/mice"
            Option          "Protocol"              "auto"
            Option          "ZAxisMapping"          "4 5 7 6"
            Option          "Buttons"               "9"
        Option        "Emulate3Buttons"    "false"
    EndSection
    # Auto-generated by Archie mkxcfg
    Section "Monitor"
        Identifier "Monitor0"
        Option "DPMS" "true"
        HorizSync    49.68
        VertRefresh  60
        #  Default modes distilled from
        #      "VESA and Industry Standards and Guide for Computer Display Monitor
        #       Timing", version 1.0, revision 0.8, adopted September 17, 1998.
        #  $XFree86: xc/programs/Xserver/hw/xfree86/etc/vesamodes,v 1.4 1999/11/18 16:52:17 tsi Exp $
        # 640x350 @ 85Hz (VESA) hsync: 37.9kHz
        ModeLine "640x350"    31.5  640  672  736  832    350  382  385  445 +hsync -vsync
        # 640x400 @ 85Hz (VESA) hsync: 37.9kHz
        ModeLine "640x400"    31.5  640  672  736  832    400  401  404  445 -hsync +vsync
        # 720x400 @ 85Hz (VESA) hsync: 37.9kHz
        ModeLine "720x400"    35.5  720  756  828  936    400  401  404  446 -hsync +vsync
        # 640x480 @ 60Hz (Industry standard) hsync: 31.5kHz
        ModeLine "640x480"    25.2  640  656  752  800    480  490  492  525 -hsync -vsync
        # 640x480 @ 72Hz (VESA) hsync: 37.9kHz
        ModeLine "640x480"    31.5  640  664  704  832    480  489  491  520 -hsync -vsync
        # 640x480 @ 75Hz (VESA) hsync: 37.5kHz
        ModeLine "640x480"    31.5  640  656  720  840    480  481  484  500 -hsync -vsync
        # 640x480 @ 85Hz (VESA) hsync: 43.3kHz
        ModeLine "640x480"    36.0  640  696  752  832    480  481  484  509 -hsync -vsync
        # 800x600 @ 56Hz (VESA) hsync: 35.2kHz
        ModeLine "800x600"    36.0  800  824  896 1024    600  601  603  625 +hsync +vsync
        # 800x600 @ 60Hz (VESA) hsync: 37.9kHz
        ModeLine "800x600"    40.0  800  840  968 1056    600  601  605  628 +hsync +vsync
        # 800x600 @ 72Hz (VESA) hsync: 48.1kHz
        ModeLine "800x600"    50.0  800  856  976 1040    600  637  643  666 +hsync +vsync
        # 800x600 @ 75Hz (VESA) hsync: 46.9kHz
        ModeLine "800x600"    49.5  800  816  896 1056    600  601  604  625 +hsync +vsync
        # 800x600 @ 85Hz (VESA) hsync: 53.7kHz
        ModeLine "800x600"    56.3  800  832  896 1048    600  601  604  631 +hsync +vsync
        # 1024x768i @ 43Hz (industry standard) hsync: 35.5kHz
        ModeLine "1024x768"   44.9 1024 1032 1208 1264    768  768  776  817 +hsync +vsync Interlace
        # 1024x768 @ 60Hz (VESA) hsync: 48.4kHz
        ModeLine "1024x768"   65.0 1024 1048 1184 1344    768  771  777  806 -hsync -vsync
        # 1024x768 @ 70Hz (VESA) hsync: 56.5kHz
        ModeLine "1024x768"   75.0 1024 1048 1184 1328    768  771  777  806 -hsync -vsync
        # 1024x768 @ 75Hz (VESA) hsync: 60.0kHz
        ModeLine "1024x768"   78.8 1024 1040 1136 1312    768  769  772  800 +hsync +vsync
        # 1024x768 @ 85Hz (VESA) hsync: 68.7kHz
        ModeLine "1024x768"   94.5 1024 1072 1168 1376    768  769  772  808 +hsync +vsync
        # 1152x864 @ 75Hz (VESA) hsync: 67.5kHz
        ModeLine "1152x864"  108.0 1152 1216 1344 1600    864  865  868  900 +hsync +vsync
        # 1280x960 @ 60Hz (VESA) hsync: 60.0kHz
        ModeLine "1280x960"  108.0 1280 1376 1488 1800    960  961  964 1000 +hsync +vsync
        # 1280x960 @ 85Hz (VESA) hsync: 85.9kHz
        ModeLine "1280x960"  148.5 1280 1344 1504 1728    960  961  964 1011 +hsync +vsync
        # 1280x1024 @ 60Hz (VESA) hsync: 64.0kHz
        ModeLine "1280x1024" 108.0 1280 1328 1440 1688   1024 1025 1028 1066 +hsync +vsync
        # 1280x1024 @ 75Hz (VESA) hsync: 80.0kHz
        ModeLine "1280x1024" 135.0 1280 1296 1440 1688   1024 1025 1028 1066 +hsync +vsync
        # 1280x1024 @ 85Hz (VESA) hsync: 91.1kHz
        ModeLine "1280x1024" 157.5 1280 1344 1504 1728   1024 1025 1028 1072 +hsync +vsync
        # 1600x1200 @ 60Hz (VESA) hsync: 75.0kHz
        ModeLine "1600x1200" 162.0 1600 1664 1856 2160   1200 1201 1204 1250 +hsync +vsync
        # 1600x1200 @ 65Hz (VESA) hsync: 81.3kHz
        ModeLine "1600x1200" 175.5 1600 1664 1856 2160   1200 1201 1204 1250 +hsync +vsync
        # 1600x1200 @ 70Hz (VESA) hsync: 87.5kHz
        ModeLine "1600x1200" 189.0 1600 1664 1856 2160   1200 1201 1204 1250 +hsync +vsync
        # 1600x1200 @ 75Hz (VESA) hsync: 93.8kHz
        ModeLine "1600x1200" 202.5 1600 1664 1856 2160   1200 1201 1204 1250 +hsync +vsync
        # 1600x1200 @ 85Hz (VESA) hsync: 106.3kHz
        ModeLine "1600x1200" 229.5 1600 1664 1856 2160   1200 1201 1204 1250 +hsync +vsync
        # 1792x1344 @ 60Hz (VESA) hsync: 83.6kHz
        ModeLine "1792x1344" 204.8 1792 1920 2120 2448   1344 1345 1348 1394 -hsync +vsync
        # 1792x1344 @ 75Hz (VESA) hsync: 106.3kHz
        ModeLine "1792x1344" 261.0 1792 1888 2104 2456   1344 1345 1348 1417 -hsync +vsync
        # 1856x1392 @ 60Hz (VESA) hsync: 86.3kHz
        ModeLine "1856x1392" 218.3 1856 1952 2176 2528   1392 1393 1396 1439 -hsync +vsync
        # 1856x1392 @ 75Hz (VESA) hsync: 112.5kHz
        ModeLine "1856x1392" 288.0 1856 1984 2208 2560   1392 1393 1396 1500 -hsync +vsync
        # 1920x1440 @ 60Hz (VESA) hsync: 90.0kHz
        ModeLine "1920x1440" 234.0 1920 2048 2256 2600   1440 1441 1444 1500 -hsync +vsync
        # 1920x1440 @ 75Hz (VESA) hsync: 112.5kHz
        ModeLine "1920x1440" 297.0 1920 2064 2288 2640   1440 1441 1444 1500 -hsync +vsync
        # Additional modelines
        ModeLine "1800x1440"  230    1800 1896 2088 2392  1440 1441 1444 1490 +HSync +VSync
        ModeLine "1800x1440"  250    1800 1896 2088 2392  1440 1441 1444 1490 +HSync +VSync
        # Extended modelines with GTF timings
        # 640x480 @ 100.00 Hz (GTF) hsync: 50.90 kHz; pclk: 43.16 MHz
        ModeLine "640x480"  43.16  640 680 744 848  480 481 484 509  -HSync +Vsync
        # 768x576 @ 60.00 Hz (GTF) hsync: 35.82 kHz; pclk: 34.96 MHz
        ModeLine "768x576"  34.96  768 792 872 976  576 577 580 597  -HSync +Vsync
        # 768x576 @ 72.00 Hz (GTF) hsync: 43.27 kHz; pclk: 42.93 MHz
        ModeLine "768x576"  42.93  768 800 880 992  576 577 580 601  -HSync +Vsync
        # 768x576 @ 75.00 Hz (GTF) hsync: 45.15 kHz; pclk: 45.51 MHz
        ModeLine "768x576"  45.51  768 808 888 1008  576 577 580 602  -HSync +Vsync
        # 768x576 @ 85.00 Hz (GTF) hsync: 51.42 kHz; pclk: 51.84 MHz
        ModeLine "768x576"  51.84  768 808 888 1008  576 577 580 605  -HSync +Vsync
        # 768x576 @ 100.00 Hz (GTF) hsync: 61.10 kHz; pclk: 62.57 MHz
        ModeLine "768x576"  62.57  768 816 896 1024  576 577 580 611  -HSync +Vsync
        # 800x600 @ 100.00 Hz (GTF) hsync: 63.60 kHz; pclk: 68.18 MHz
        ModeLine "800x600"  68.18  800 848 936 1072  600 601 604 636  -HSync +Vsync
        # 1024x768 @ 100.00 Hz (GTF) hsync: 81.40 kHz; pclk: 113.31 MHz
        ModeLine "1024x768"  113.31  1024 1096 1208 1392  768 769 772 814  -HSync +Vsync
        # 1152x864 @ 60.00 Hz (GTF) hsync: 53.70 kHz; pclk: 81.62 MHz
        ModeLine "1152x864"  81.62  1152 1216 1336 1520  864 865 868 895  -HSync +Vsync
        # 1152x864 @ 85.00 Hz (GTF) hsync: 77.10 kHz; pclk: 119.65 MHz
        ModeLine "1152x864"  119.65  1152 1224 1352 1552  864 865 868 907  -HSync +Vsync
        # 1152x864 @ 100.00 Hz (GTF) hsync: 91.50 kHz; pclk: 143.47 MHz
        ModeLine "1152x864"  143.47  1152 1232 1360 1568  864 865 868 915  -HSync +Vsync
        # 1280x800 @ 60.00 Hz (GTF) hsync: 49.68 kHz; pclk: 83.46 MHz
        Modeline "1280x800"  83.46  1280 1344 1480 1680  800 801 804 828  -HSync +Vsync
        # 1280x960 @ 72.00 Hz (GTF) hsync: 72.07 kHz; pclk: 124.54 MHz
        ModeLine "1280x960"  124.54  1280 1368 1504 1728  960 961 964 1001  -HSync +Vsync
        # 1280x960 @ 75.00 Hz (GTF) hsync: 75.15 kHz; pclk: 129.86 MHz
        ModeLine "1280x960"  129.86  1280 1368 1504 1728  960 961 964 1002  -HSync +Vsync
        # 1280x960 @ 100.00 Hz (GTF) hsync: 101.70 kHz; pclk: 178.99 MHz
        ModeLine "1280x960"  178.99  1280 1376 1520 1760  960 961 964 1017  -HSync +Vsync
        # 1280x1024 @ 100.00 Hz (GTF) hsync: 108.50 kHz; pclk: 190.96 MHz
        ModeLine "1280x1024"  190.96  1280 1376 1520 1760  1024 1025 1028 1085  -HSync +Vsync
        # 1400x1050 @ 60.00 Hz (GTF) hsync: 65.22 kHz; pclk: 122.61 MHz
        ModeLine "1400x1050"  122.61  1400 1488 1640 1880  1050 1051 1054 1087  -HSync +Vsync
        # 1400x1050 @ 72.00 Hz (GTF) hsync: 78.77 kHz; pclk: 149.34 MHz
        ModeLine "1400x1050"  149.34  1400 1496 1648 1896  1050 1051 1054 1094  -HSync +Vsync
        # 1400x1050 @ 75.00 Hz (GTF) hsync: 82.20 kHz; pclk: 155.85 MHz
        ModeLine "1400x1050"  155.85  1400 1496 1648 1896  1050 1051 1054 1096  -HSync +Vsync
        # 1400x1050 @ 85.00 Hz (GTF) hsync: 93.76 kHz; pclk: 179.26 MHz
        ModeLine "1400x1050"  179.26  1400 1504 1656 1912  1050 1051 1054 1103  -HSync +Vsync
        # 1400x1050 @ 100.00 Hz (GTF) hsync: 111.20 kHz; pclk: 214.39 MHz
        ModeLine "1400x1050"  214.39  1400 1512 1664 1928  1050 1051 1054 1112  -HSync +Vsync
        # 1600x1200 @ 100.00 Hz (GTF) hsync: 127.10 kHz; pclk: 280.64 MHz
        ModeLine "1600x1200"  280.64  1600 1728 1904 2208  1200 1201 1204 1271  -HSync +Vsync
    EndSection
    # Auto-generated by Archie mkxcfg
    Section "Device"
        Identifier  "Card0"
        Driver      "nv"
        VendorName  "All"
        BoardName   "All"
        Option       "NvAGP" "1"
        Option       "RenderAccel" "True"
        Option       "NoPowerConnectorCheck"
        #Option       "TripleBuffer" "True"
        #Option       "AddARGBGLXVisuals"
        #Option       "BackingStore" "True"
        #Option       "AllowGLXWithComposite" "true"
    EndSection
    Section "Screen"
        Identifier "Screen0"
        Device     "Card0"
        Monitor    "Monitor0"
        DefaultColorDepth 24
        SubSection "Display"
            Depth     1
            Modes "1024x768" "800x600" "640x480"
        EndSubSection
        SubSection "Display"
            Depth     4
            Modes "1024x768" "800x600" "640x480"
        EndSubSection
        SubSection "Display"
            Depth     8
            Modes "1024x768" "800x600" "640x480"
        EndSubSection
        SubSection "Display"
            Depth     15
            Modes "1024x768" "800x600" "640x480"
        EndSubSection
        SubSection "Display"
            Depth     16
            Modes "1024x768" "800x600" "640x480"
        EndSubSection
        SubSection "Display"
            Depth     24
            Modes "1280x800" "1024x768" "800x600" "640x480"
        EndSubSection
        SubSection "Display"
            Depth     32
            Modes "1024x768" "800x600" "640x480"
        EndSubSection
        #Option "TwinView" "true"
        #Option "TVOutFormat" "COMPOSITE" #S-VIDEO
        #Option "TVStandard" "NTSC-M" #PAL-B
        #Option "MetaModes" "DFP-0: 1280x800, CRT-0: 1280x800" #; NULL, CRT-0: 1280x800"
        ##Option "MetaModes" "1024x768,1024x768; 800x600,800x600; 640x480,640x480; 512x384,512x384" #TV
        ##Option "ConnectedMonitor" "DFP-0, CRT-0"
        #Option "TwinViewOrientation" "LeftOf" #LeftOf
        #Option "SecondMonitorHorizSync" "31-90" #30-50
        #Option "SecondMonitorVertRefresh" "60-60" #60
    EndSection
    Section "DRI"
        Mode 0666
    EndSection

    Try
    Section "InputDevice"
            Identifier  "Configured Mouse"
            Driver      "evdev"
            Option      "CorePointer"
            Option      "Name" "Logitech USB-PS/2 Optical Mouse"
            Option      "Phys" "usb-0000:00:02.0-1/input0" # optional
    EndSection
    where the Name and Phys-options are found by
    cat /proc/bus/input/devices|grep Name
    cat /proc/bus/input/devices|grep Phys

  • Custom kernel (2.6.31) - USB Mouse & Keyboard not working [solved]

    So I've just recompiled the new kernel (2.6.31) as a custom, as is my custom!
    USB Mouse and keyboard no worky (but do as PS/2).
    As a quick thing to check - what kernel .config settings haven't I enabled properly? A quick check though and everything SEEMS to be in order.
    The stock 2.6.31 kernel works fine with the USB inputs.
    Thanks in advance.
    [solved] I realised I was operating off an older kernel26 package (2.6.30), so synching abs and rebuilding using the 2.6.31 package and leaving a few more stock options enabled, seems to have worked.
    Last edited by sultanoswing (2009-10-12 11:46:36)

    sry, idk how to get the error output of a compiled package via mkpkg. i know its a weird error...
    has anyone tryed to open my kerenel configuration with a graphical cofiguration font end, and to see if the 3945 wireless module is marked as module? when i do it its not aviable. maybe today ill find some time to do the config and compile...
    my arch: x86 ; core duo; pentium m (kernel-processor-type); -march=prescott -O2 -pipe -fomit-frame-pointer
    yeah, config from testing *.31 works fine, but the job needs to be done to strip out all useless stuff out of that general kernel

  • USB Mouse autosuspends after 2 seconds

    Hello dear Community
    I have a problem with my USB mouse on my laptop. It autosuspends after 2 seconds when my laptop is on battery power. When AC is plugged in, the mouse works without problems normally. But sometimes (I couldn't find any underling rule for this behaviour) the mouse autosuspends also after 2 seconds when power IS plugged in.
    First things first:
    lsusb yields:
    Bus 002 Device 003: ID 8087:07da Intel Corp.
    Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
    Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 001 Device 003: ID 2232:1045
    Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 003 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
    Bus 003 Device 002: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
    Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    So the Mouse I am talking about has the ID 045e:00cb
    After unplugging the mouse dmesg gives me:
    [ 420.549995] usb 3-2: USB disconnect, device number 2
    [ 422.770284] usb 3-2: new low-speed USB device number 4 using xhci_hcd
    [ 422.789282] usb 3-2: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes
    [ 422.792590] input: Microsoft Microsoft Basic Optical Mouse v2.0 as /devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.0/input/input12
    [ 422.792991] hid-generic 0003:045E:00CB.0002: input,hidraw0: USB HID v1.11 Mouse [Microsoft Microsoft Basic Optical Mouse v2.0 ] on usb-0000:00:14.0-2/input0
    I thought that laptopmode tools is the reason for the problems, so tried the advice posted on this blog. I made a udev rule
    [nikolai@niko-arch ~]$ cat /etc/udev/rules.d/91-local-rules
    # Add rule to turn of autosuspend for specific mouse
    ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="045e", ATTR{idProduct}=="00cb", TEST=="power/control", ATTR{power/control}="on"
    and changed my laptopmode tools settings:
    [nikolai@niko-arch ~]$ cat /etc/laptop-mode/conf.d/usb-autosuspend.conf
    # Configuration file for Laptop Mode Tools module usb-autosuspend.
    # For more information, consult the laptop-mode.conf(8) manual page.
    # USB autosuspend settings
    #__COMMENT If you enable this setting, laptop mode tools will automatically enable the
    #__COMMENT USB autosuspend feature for all devices.
    #__COMMENT
    #__COMMENT NOTE: Some USB devices claim they support autosuspend, but implement it in a
    #__COMMENT broken way. This can mean keyboards losing keypresses, or optical mice turning
    #__COMMENT their LED completely off. If you have a device that misbehaves, add its USB ID
    #__COMMENT to the blacklist below and complain to your hardware vendor.
    # Enable debug mode for this module
    # Set to 1 if you want to debug this module
    DEBUG=0
    # Enable USB autosuspend feature?
    # Set to 0 to disable
    CONTROL_USB_AUTOSUSPEND="auto"
    # Set this to use opt-in/whitelist instead of opt-out/blacklist for deciding
    # which USB devices should be autosuspended.
    # AUTOSUSPEND_USE_WHITELIST=0 means AUTOSUSPEND_*_BLACKLIST will be used.
    # AUTOSUSPEND_USE_WHITELIST=1 means AUTOSUSPEND_*_WHITELIST will be used.
    AUTOSUSPEND_USE_WHITELIST=0
    # The list of USB IDs that should not use autosuspend. Use lsusb to find out the
    # IDs of your USB devices.
    # Example: AUTOSUSPEND_USBID_BLACKLIST="046d:c025 0123:abcd"
    AUTOSUSPEND_USBID_BLACKLIST="045e:00cb"
    # The list of USB driver types that should not use autosuspend. The driver
    # type is given by "DRIVER=..." in a USB device's uevent file.
    # Example: AUTOSUSPEND_USBID_BLACKLIST="usbhid usb-storage"
    AUTOSUSPEND_USBTYPE_BLACKLIST=""
    # The list of USB IDs that should use autosuspend. Use lsusb to find out the
    # IDs of your USB devices.
    # Example: AUTOSUSPEND_USBID_WHITELIST="046d:c025 0123:abcd"
    AUTOSUSPEND_USBID_WHITELIST=""
    # The list of USB driver types that should use autosuspend. The driver
    # type is given by "DRIVER=..." in a USB device's uevent file.
    # Example: AUTOSUSPEND_USBTYPE_WHITELIST="usbhid usb-storage"
    AUTOSUSPEND_USBTYPE_WHITELIST=""
    # Trigger auto-suspension of the USB deivce under conditional circumstances
    BATT_SUSPEND_USB=1
    LM_AC_SUSPEND_USB=0
    NOLM_AC_SUSPEND_USB=0
    # USB Auto-Suspend timeout in seconds
    # Number of seconds after which the USB devices should suspend
    AUTOSUSPEND_TIMEOUT=2
    But I experience still the same issue (after rebooting and unplugging the mouse).
    Then I tried to completely disable laptopmode tools with
    CONTROL_USB_AUTOSUSPEND="0"
    and rebooted, but nothing chances.
    Maybe I am missing somthing obvious. Thanks for any hints!
    Best Regards
    Nikolai
    Last edited by athal (2013-10-26 10:02:29)

    Hi!
    I got the same problem with my external mouse/keyboard here: https://bbs.archlinux.org/viewtopic.php?id=166517
    I tried what you posted, brebs but it also did not work. If I change the power status using powertop my output of your script correctly says:
    1-1.6 auto 480 Integrated Camera
    3-1 auto 5000 Elements 1042
    4-1.2 auto 480 USB2.0 Hub
    4-1.2.2 on 12 Microsoft® SiderWinderTM X6 Keyboard
    4-1.2.3 on 1.5 USB-PS/2 Optical Mouse
    4-1.2.4 auto 480 USB2.0 Hub
    but only with my 91-local.rules, which are basically the same as athal postest, the output is:
    1-1.6 auto 480 Integrated Camera
    3-1 auto 5000 Elements 1042
    4-1.2 auto 480 USB2.0 Hub
    4-1.2.2 auto 12 Microsoft® SiderWinderTM X6 Keyboard
    4-1.2.3 auto 1.5 USB-PS/2 Optical Mouse
    4-1.2.4 auto 480 USB2.0 Hub
    of course i did udevadm control --reload.
    it's somewhat annoying to have to start powertop everytime when you boot your pc with attached external mouse/keyboard.
    Note though, I do not use laptop-tools, I do the rest of my powermanagement with udev rules, too.
    [me@mybox rules.d]$ ls
    42-usb_power_save.rules 91-local.rules pci_pm.rules
    80-net-name-slot.rules disable_wol.rules wifi_power_save.rules
    [me@mybox rules.d]$ cat 42-usb_power_save.rules
    ACTION=="add", SUBSYSTEM=="usb", TEST=="power/control" ATTR{power/control}="auto"
    ACTION=="add", SUBSYSTEM=="usb", TEST=="power/autosuspend" ATTR{power/autosuspend}="2"
    [me@mybox rules.d]$ cat 91-local.rules
    ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="045e", ATTR{idProduct}=="074b", TEST=="power/control", ATTR{power/control}=="on"
    ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="046d", ATTR{idProduct}=="c051", TEST=="power/control", ATTR{power/control}=="on"
    Thanks for any advice !
    Last edited by replax (2013-10-27 08:59:30)

  • MS Usb Mouse Scroll Wheel Problems

    Im having this problem on my laptop running arch.  I have the USB module loaded.  My XF86Config file looks as follows.
    Section "ServerLayout"
    Identifier "XFree86 Configured"
    Screen 0 "Screen0" 0 0
    InputDevice "Mouse0" "CorePointer"
    InputDevice "Mouse1" "SendCoreEvents"
    InputDevice "Keyboard0" "CoreKeyboard"
    EndSection
    Section "InputDevice"
    Identifier "Mouse1"
    Driver "mouse"
    Option "Protocol" "IMPS/2"
    Option "Device" "dev/usbmouse"
    Option "ZAxisMapping" "4 5"
    Option "Buttons" "5"
    EndSection
    I get output from this usbmouse via (cat)
    cat /dev/usbmouse
    or
    cat /dev/input/mouse2
    With both cats, I get output by scrolling the wheel and by depressing the wheel(5th button).
    I really don't know what else to try.  I have tried putting protocol on auto, and switching device path to /dev/input/mouse2 with no luck.

    I have a Twinhead lappie. In /etc/X11/XF86Config-4 ( Arch 0.6 )
    ( which is looked for before XF86Config ) I have :
    Section "ServerLayout"
    # ps/2 mouse not detected
           Inputdevice "PS/2 Mouse "AlwaysCore"
    # Serial mouse not detected
           InputDevice        "USB Mouse" "CorePointer"
    EndSection
    Section "Inputdevice"
    Identifier "Serial Mouse"
    Driver      "mouse"
    Option "Protocol" "Microsoft"
    Option "Device " "/dev/ttyS0"
    Option "SendCoreEvents" "true"
    EndSection
    Section "InputDevice"
    Identifier "PS/2 Mouse"
    Driver "mouse"
    Option "Protocol" "PS/2"
    Option "Device" "/dev/psaux"
    Option "SendCoreEvents" "true"
    EndSection
    Section "inputDevice"
    Identifier "USB Mouse"
    Driver "mouse"
    Option "Device" "/dev/input/mice"
    Option "SendCoreEvents" "true"
    Option "protocol" "IMPS/2"
    Option "ZAxisMapping" "4 5"
    Option Buttons"       "5"
    EndSection
    That gets the touchpad and USB working for me, allowing for the fact that I copied it by hand, and may have made a mistake.
    This works for me, but I must try  'ExploderPS/2'.
    I think it was just a straight copy from whatever Vector-soho decided I needed.
    Remember that X 4 looks for XFConfig-4 before it tries XFConfig. that can be a trap, if you edit config and leave config-4 alone, you make no changes to X runtime.

  • Usb mouse double click

    Hi,
    Im using fluxbox as window manager and after some upgrades the mouse very often doing double click, if I click only once. On touchpad is all right, so I dont know where is the problem. I tryed change xorg configuration - other protocol and some options, but nothing helped. I also tryed change speed double click, but nothing changed too.
    My xorg config is now:
    Section "InputDevice"
    Identifier "USB Mouse"
    Driver "mouse"
    Option "Device" "/dev/input/mice"
    Option "SendCoreEvents" "true"
    Option "Protocol" "IMPS/2"
    Option "ZAxisMapping" "4 5"
    Option "Buttons" "5"
    EndSection
    generated by hwd
    Thanks for all replies
    edit: I have kernel 2.6.33.4 and before in kernel 2.6.33.3 "mouse bug" was there too.
    Last edited by aivi (2010-05-15 11:47:40)

    edit: So Its not working well, xev show still that I pressed and released twice button, any ideas?
    In blackbox too. Its somewhere else.
    --------So it was by .fluxbox/keys I tried move them somewhere else and restart X and Its working right now. -------
    Last edited by aivi (2010-05-15 13:25:12)

  • A4Tech USB mouse detected as Joystick

    I hope there isn't a duplicate to this, I couldn't find one, but my searching skills aren't exactly superb.
    Hello, I'm trying to play FEZ on steam but the game is unplayable due to, what appears to be, my mouse being picked up as a joystick by steam.
    Currently the game behaves as if the walk-left key was stuck, and loads as if a gamepad(which I don't have and there aren't any other input devices other than the keyboard or mouse) was plugged in.
    Based on the console output from Dota2(which happily behaves <3 doto never fails me)
    Found joystick 'A4TECH USB Device' (03000000da0900006690000011010000), but no recognized controller configuration for it.
    I found that the issue might be my USB mouse being detected as a joystick, and so I followed their suggestions to fix the issue with no results.
    Things I tried:
    Deleting the /dev/input/js0 that was being created, I gather, because of the mistaken id.(source)
    Disabling via xinput everything A4TECH except for the one that actually allows me to use the mouse.(source)
    Disabling via xinput the mouse and key events.(source)
    xinput list output:
    $ xinput list
    ⎡ Virtual core pointer id=2 [master pointer (3)]
    ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
    ⎜ ↳ A4TECH USB Device id=8 [slave pointer (2)]
    ⎜ ↳ A4TECH USB Device id=10 [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)]
    ↳ Power Button id=7 [slave keyboard (3)]
    ↳ Webcam C170 id=11 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=12 [slave keyboard (3)]
    ↳ A4TECH USB Device (keys) id=9 [slave keyboard (3)]
    Since steam is not officially supported for Arch I figured this would be the best place to come looking for help. Please, if you need any more information ask me.
    Thank you

    Hi!
    I use A4Tech mouse. With latest updates, appeared the same problem
    Searching, I found a solution that helped me. you should also help.
    I have a game FEZ, same problem. Games use /dev/input/event*. Removing unnecessary. the problem will be solved.
    Yes, I understand that this is a hack, and not the normal fix.
    The mouse is defined as 2 devices, the second we need to remove.
    cat /proc/bus/input/devices
    Find:
    I: Bus=0003 Vendor=09da Product=8090 Version=0111
    N: Name="A4Tech USB Full Speed"
    P: Phys=usb-0000:00:13.5-2.4/input0
    S: Sysfs=/devices/pci0000:00/0000:00:13.5/usb1/1-2/1-2.4/1-2.4:1.0/0003:09DA:8090.003B/input/input70
    U: Uniq=
    H: Handlers=event2 mouse0
    B: PROP=0
    B: EV=17
    B: KEY=ffff0000 0 0 0 0
    B: REL=143
    B: MSC=10
    I: Bus=0003 Vendor=09da Product=8090 Version=0111
    N: Name="A4Tech USB Full Speed"
    P: Phys=usb-0000:00:13.5-2.4/input1
    S: Sysfs=/devices/pci0000:00/0000:00:13.5/usb1/1-2/1-2.4/1-2.4:1.1/0003:09DA:8090.003C/input/input71
    U: Uniq=
    H: Handlers=sysrq kbd event3 js0
    B: PROP=0
    B: EV=12001f
    B: KEY=3007f 0 0 4c3ffff17aff32d bf54445600000000 c00000000000001 130c130b17c007 ffa67bfad951dfff febeffdfffefffff fffffffffffffffe
    B: REL=40
    B: ABS=ffffff01000701ff
    B: MSC=10
    B: LED=1f
    as event3 and js0
    If you remove event3 then the problem is solved. only until you reboot.
    What attributes it has
    udevadm info -a /dev/input/event3
    I chose and made a rule for udev:
    cat /etc/udev/rules.d/52-a4tech.rules
    SUBSYSTEM=="input", ATTRS{name}=="*A4Tech*", ATTRS{phys}=="*/input1", RUN+="/usr/bin/rm /dev/input/%k"
    Use this rule and should all work. FEZ now works correctly.
    more here
    http://stackoverflow.com/questions/6990 … input-stre
    https://bbs.archlinux.org/viewtopic.php?id=190485

  • Usb mouse doesnøt work on snow leopard 10.6.8

    Since upgrading to Snow Leopard 10.6.8 on a MacBook, my USB Mac mouse became erratic then stopped working entirely. I tried a wireless USB mouse. That also worked for a while, but it too then stopped. Please help. I'm not a Mac geek, so need to be held by the hand a little. Thanks for your help.

    Mkeschinger,
    I was using it with 10.6.8 for a long time till now.
    Actually here is how you configure with snow leopard, by apple:
    http://support.apple.com/kb/HT5330
    But is not working for me.
    I gave up already. I will probably use the forward email function in the icloud, and slowly move to gmail.

  • Solaris - USB - Mouse

    I've got some troubles using USB Mouse on my fresh installed Solaris 10. Since it was installed I can't use my Mouse and I've nothing but console to use, what makes me frustrated in the long run :)
    please tell me what to do to make my USB Mouse fully working, really don't know what to configure or sth...
    thanks

    Which release of Solaris 10 did you install? If you have Update 4 or Update 5 you are likely hitting bug 6494635 which causes some types of USB mice to stop working. This bug is already fixed in OpenSolaris and will probably be fixed in Update 6 or possibly a patch before Update 6 is released. If you have a service contract you can open a support case to request an interim relief patch to get the fix before the official patch is released for Solaris 10. Another workaround would be to install Solaris 10 Update 3 or an older release.
    Information on troubleshooting USB devices is in the USB FAQ:
    http://www.sun.com/io_technologies/usb/USB-Faq.html

  • USB mouse disconnects when laptop on battery

    Hello,
    I am using Gnome 3.6 on 3.6.10-1-ARCH. Whenever I run my laptop on battery power, my external usb mouse disconnects after some inactivity period. If I plug it to external power source, it again starts working fine.
    I suspect there must something in gnome 3.6 (weird optimization) or something to do with laptop-tools which disconnects the usb mouse after some time of inactivity to save power. How to fix this.
    I referred this link, but it did not provide me way to fix this.
    https://bbs.archlinux.org/viewtopic.php?id=49503
    https://bbs.archlinux.org/viewtopic.php?id=149530
    Update: I noticed that I had not enabled laptop mode tools so problem must be with gnome3. I have now enabled this and set my USB mouse id in blacklist, so that it does not autosuspend. Still It is getting auto suspend.
    Last edited by ameyjah (2013-01-06 16:38:09)

    I imagine that your usb ports control is set to auto... which will suspend the device after a time of inactivity.  The solution would be to have this not set to auto... though I am not sure how to do this with laptop-mode-tools in place.  I don't use laptop-mode-tools, and it is my opinion that it actually makes things harder when you encounter things like this.  Instead of learning where the configuration for this is within /sys and then creating the necessary configuration to change it, you now learn where it is in /sys, what is changing it automagically for you, then you have to learn the intricacies of that particualr power management tool.
    So although I cannot help you with yout laptop-mode-tools, the file that sets this is /sys/bus/usb/devices/usb[1-9]/power/control or /sys/devices/pci0000:00/0000:00:1a.0/usb1/power without the symlinks on my machine for usb1.
    Just my opinion, but with the power that comes in computers these days (for the past several years in fact), having something like laptop-mode-tools is pretty worthless.  If you just have all the settings set as though it were on "battery" all the time, I bet there would be no discernible difference.  I know I cannot tell, and then my computer probably charges ever so slightly faster because it is not set to consume more power when I plug it in.

  • USB Mouse clicks get registered twice, sometimes

    Hello all
    I am using Arch Linux on my Thinkpad T61, and I usually have a USB mouse hooked up to it (Logitech Nano).
    A while ago I started to do some tweaks in order to enable the Synaptics TouchPad and get proper scrolling behaviour on the TrackPoint. However, I must have done something, because ever since, many of my USB mouse clicks get registered as a double click (not always, but often).
    I started doing some troubleshooting today, by commenting out parts of my xorg.conf file (I use evdev hotplugging, but I tought maybe Xorg was registering my mouse aswell) and I even booted up without an xorg.conf once, to no avail. The problem definately does not lie there.
    The only policy file I have that has anything to do with a mouse is /etc/hal/fdi/policy/mouse-wheel.fdi.
    [rob@rob-thinkpad ~]$ cat /etc/hal/fdi/policy/mouse-wheel.fdi
    <match key="info.product" string="TPPS/2 IBM TrackPoint">
    <merge key="input.x11_options.EmulateWheel" type="string">true</merge>
    <merge key="input.x11_options.EmulateWheelButton" type="string">2</merge>
    <merge key="input.x11_options.YAxisMapping" type="string">4 5</merge>
    <merge key="input.x11_options.XAxisMapping" type="string">6 7</merge>
    <merge key="input.x11_options.Emulate3Buttons" type="string">true</merge>
    <merge key="input.x11_options.EmulateWheelTimeout" type="string">200</merge>
    </match>
    Also, I found multiple entries for my mouse in /proc/bus/input/devices:
    [rob@rob-thinkpad ~]$ egrep "Name|Handlers" /proc/bus/input/devices
    N: Name="Macintosh mouse button emulation"
    H: Handlers=mouse0 event0
    N: Name="AT Translated Set 2 keyboard"
    H: Handlers=kbd event1
    N: Name="ThinkPad Extra Buttons"
    H: Handlers=kbd event2
    N: Name="Power Button (FF)"
    H: Handlers=kbd event3
    N: Name="Lid Switch"
    H: Handlers=event4
    N: Name="Sleep Button (CM)"
    H: Handlers=kbd event5
    N: Name="Video Bus"
    H: Handlers=kbd event6
    N: Name="PC Speaker"
    H: Handlers=kbd event7
    N: Name="SynPS/2 Synaptics TouchPad"
    H: Handlers=mouse1 event8
    N: Name="Logitech USB Receiver"
    H: Handlers=mouse2 event9
    N: Name="Logitech USB Receiver"
    H: Handlers=kbd event10
    N: Name="TPPS/2 IBM TrackPoint"
    H: Handlers=mouse3 event11
    N: Name="ThinkPad HDAPS joystick emulation"
    H: Handlers=event12 js0
    N: Name="ThinkPad HDAPS accelerometer data"
    H: Handlers=event13 js1
    Could someone please help me solve this problem, for I have no more ideas how to go at this... Thanks
    Last edited by robrene (2009-06-05 09:47:18)

    It seems there are multiple entries for my USB mouse in /var/log/Xorg.0.log!
    (II) config/hal: Adding input device Logitech USB Receiver
    (**) Logitech USB Receiver: always reports core events
    (**) Logitech USB Receiver: Device: "/dev/input/event9"
    (II) Logitech USB Receiver: Found 16 mouse buttons
    (II) Logitech USB Receiver: Found x and y relative axes
    (II) Logitech USB Receiver: Found scroll wheel(s)
    (II) Logitech USB Receiver: Configuring as mouse
    (**) Logitech USB Receiver: YAxisMapping: buttons 4 and 5
    (**) Logitech USB Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: MOUSE)
    (**) Logitech USB Receiver: (accel) keeping acceleration scheme 1
    (**) Logitech USB Receiver: (accel) filter chain progression: 2.00
    (**) Logitech USB Receiver: (accel) filter stage 0: 20.00 ms
    (**) Logitech USB Receiver: (accel) set acceleration profile 0
    (II) config/hal: Adding input device Logitech USB Receiver
    (**) Logitech USB Receiver: always reports core events
    (**) Logitech USB Receiver: Device: "/dev/input/event10"
    (II) Logitech USB Receiver: Found 1 mouse buttons
    (II) Logitech USB Receiver: Found scroll wheel(s)
    (II) Logitech USB Receiver: Found keys
    (II) Logitech USB Receiver: Configuring as keyboard
    (II) Logitech USB Receiver: Adding scrollwheel support
    (**) Logitech USB Receiver: YAxisMapping: buttons 4 and 5
    (**) Logitech USB Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD)
    (**) Option "xkb_rules" "evdev"
    (**) Option "xkb_model" "evdev"
    (**) Option "xkb_layout" "de"
    (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
    This looks pretty bad to me... The USB reciever is listed once as a mouse and once as a keyboard. Something went very awry here. This is the output after a fresh boot without xf86-input-mouse installed. The only remaining input drivers I have left from xf86 are:
    [rob@rob-thinkpad ~]$ pacman -Q xf86-input-
    xf86-input-evdev xf86-input-keyboard xf86-input-synaptics
    edit
    I removed xf86-input-keyboard as well now, still no change...
    edit2
    Aha! After some Googling and hooking up the mouse on a Windows XP machine, I noticed that this is a problem with this specific mouse. Under Windows XP, I get the same behaviour (often a double click, sometimes no click at all). It seems it is time to find the warranty papers for this baby. In case anyone ever reads this, this happened to me on a Logitech VX Nano, after about 5-10months of usage (I don't recall when I bought it exactly).
    Last edited by robrene (2009-06-05 15:14:23)

  • Replacing bluetooth mouse with USB mouse

    I have no need for a wireless mouse, and so just plugged in an old usb mouse, which works OK, except that when I reboot the computer, the USB mouse is not recognized at the login screen. Also, after I log in using the keyboard, the USB mouse is still not recognized until I unplug it and plug it back in. Anyone know how to tell the iMac to recognize it on startup?
    thanks

    Hi T-Bob
    People seem to have had variable experiences with at least some versions of the Kensington drivers - see http://www.macupdate.com/reviews.php?id=5805
    I see that their "Mouseworks" driver package is now up to version 2.9 - http://us.kensington.com/html/1385.html#mac28 Is this the version you installed? Have you checked the configuration options in the System Preferences?
    I notice elswhere on their site that you should uninstall any earlier versions first (using the "uninstall option in the installer) before putting on a new one. Not sure if you had an earlier one installed though.
    It is just possible that any OTHER mouse or graphic tablet / game controller software could also be causing conflicts with the Kensington drivers. This could include either the bluetooth or mighty mouse software I guess. I'm reluctant to suggest removing them though, as they are part of the general system software and we don't want to risk leaving you completely rodent free!
    Sounds like you did the PRAM reset properly.
    Another option for you might be the famous "USB Overdrive" - http://www.usboverdrive.com/USBOverdrive/Information.html THis is third party software that has been used to tame many an unruly input device over the years. I haven't used recent versions but it was certainly a worthy product in days gone by. You can download a fully operational trial version.
    Cheers
    Rod

Maybe you are looking for

  • IR COMPUTE OR QUERY?

    IM AM TRYING TO MAKE AN IR REPORT WITH AGING ON OPEN INVOICES. IN ONE COLUMN I HAVE NUMBER OF DAYS PAST DUE. NOW I NEED TO CASE THAT COLUMN IN AN IR AS FOLLOWS: CASE WHEN J > 119 THEN 120 WHEN J < 119 AND > 90 THEN 90 WHEN J < 89 AND > 60 THEN 60 WHE

  • I just bought a new MacBook, but have an iPod with music on it. How do I get to my iTunes?

    How do I copy all my music to my iTunes, even those songs I didn't purchase outright?

  • Tecra S4 -125 shows built-in HDD error

    I've bought Toshiba Tecra S4 -125 and Ive got problem with built-in HDD. New SATA HDD does not work. The message "Built-in HDD ERROR" appears from time to time and system stops booting from HDD and boot is very, very slow. In BIOS settings HDD is not

  • Less number of Records while loading data from one cube to another

    Hi, We are in the process of doing major changes in the existing InfoCube. Before making any changes, we had planned to make a copy of the cube with data. For this we did the following steps : 1. Created the new cube from the original cube. 2. Genera

  • To use SRM Catalog from ECC

    Hi All, there is a way to use the SRM catalog from ECC system? Can I buy items from ECC system selecting them from SRM catalog? Thanks in advance. Antonio.