Hmm, everything looks correct. Are you running regualr Xorg or Xgl?Quote:
Originally Posted by hubacap
Edit: If you're using two devices on one receiver, the post under this one may be helpful.
Printable View
Hmm, everything looks correct. Are you running regualr Xorg or Xgl?Quote:
Originally Posted by hubacap
Edit: If you're using two devices on one receiver, the post under this one may be helpful.
You have both connecting through one reciever, correct? In that case, you'ld have to set up Xorg a bit differently, and you might have to drop the udev rule. I think some people have gotten it to work, but I haven't, so I can't really say how to have both working through one receiver. It might help to look through some comments in the old thread.Quote:
Originally Posted by ewerx
These may be helpful:
http://ubuntuforums.org/showpost.php...3&postcount=45
http://ubuntuforums.org/showpost.php...7&postcount=62
I was able to get mine working properly using this guide, and mine is a KB/Mouse combo on one receiver. Specifically, I have the Logitech LX700.
My details from the input devices:
My 19-local.rules:Code:I: Bus=0003 Vendor=046d Product=c512 Version=3007
N: Name="Logitech USB Receiver"
P: Phys=usb-0000:00:1d.1-1.2/input0
S: Sysfs=/class/input/input3
H: Handlers=kbd event3
B: EV=120003
B: KEY=10000 7 ff800000 7ff febeffdf ffefffff ffffffff fffffffe
B: LED=1f
I: Bus=0003 Vendor=046d Product=c512 Version=3007
N: Name="Logitech USB Receiver"
P: Phys=usb-0000:00:1d.1-1.2/input1
S: Sysfs=/class/input/input4
H: Handlers=kbd mouse1 event4 ts1
B: EV=7
B: KEY=7fffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff 0 0 1878 d800d100 1e0000 0 0 0
B: REL=143
My xorg.conf before trying what detyabozhye has suggested. It works whenever the mouse is plugged in, but not when the mouse is dosconnected.Code:KERNEL=="event[0-9]*", SYSFS{../name}=="Logitech USB Receiver", NAME="input/event9"
My .xbindkeys is the same as his, with a couple more options added.Code:Section "InputDevice"
Identifier "Configured Mouse"
Driver "evdev"
Option "CorePointer"
Option "Device" "/dev/input/event9"
Option "Buttons" "10"
Option "ZAxisMapping" "4 5"
EndSection
I hope some of this might be of help. Best of luck; I'm off to try this when the mouse is disconnected. BTW, I got the Ctrl-T working. Thanks.
Jay
EDIT: what you suggested worked, thanks. Now, how do I get the xbindkeys daemon to run automatically when I boot?
If you're running Gnome, go to "System > Preferences > Sessions" click on the "Startup Programs" tab, click "Add" and enter "xbindkeys".Quote:
Originally Posted by killerjay_47
In Xfce go to Xfce Menu -> Settings -> Autostarted Applications and click Add.
As for KDE, I'm not sure what the correct way is.
I tried the simple approach, ignoring the udev stuff and just added the lines at the end of my mouse section in xorg.conf. It is as follows:
So now my MX1000 cruise up button instead goes back. And my the thumb button closest to me does too. What I'd really like is to have the cruis up to cruis up and the cruise down to cruise down. I'd also like the side buttons to go band and forth like they are supposed to and the wheel button I'd like to double click when I push it. Any way to do that? Or at least some of it without all this crazy, complicated stuff. could someone post what the button mapping numbers mean and then I could just configure it the way I want.Quote:
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "Buttons" "5"
Option "ZAxisMapping" "4 5"
Option "ButtonMapping" "1 2 3 6 7"
EndSection
Note the Protocol, it's "ExplorerPS/2", it's meant for MS IntelliMouse Explorer. It will not work with all the Logitech buttons correctly no matter what you set the "ButtonMapping" to, I tried it. I don't mind anyone using that method, but you'll have to live with some buttons functioning incorrectly.Quote:
Originally Posted by kpurcell
BTW, you will still need to set up xbindkeys, LMCtl, etc IF you want it to do 800+ CPI, Back/Forward in Nautilus or whatever. The "simple" method is only a replacement for the udev and evdev part, not for the rest of this guide. If I wrote this guide using the "simple method", it would still be two thirds the length.
Lol well this ended for me early, when I first went to change xorg.conf (after the udev thing), the X server kinda booted then didnt. Im using nvidia drivers and indeed the little nvidia picture showed up as it was supposed to. However after that it went back to the loading screen (usually it then proceeds to login). Any reason why this happens?
Don't know, I had that a lot when testing the current evdev. Can you tell me a bit about your mouse, setup, and give me the output of "cat /proc/bus/input/devices"? The current evdev is just a bit too picky. My old guide is a bit more relliable, but a bit hacky as well and longer in length.
I have the Wacom thing too. I'm not sure why it's there, but you can safely comment out the device references if you also comment out "stylus", "cursor", and "eraser" in the "Server Layout" section of xorg.conf, near the bottom.
It doesn't help anything, but it at least supresses those annoying error messages that scroll off the relevant errors when X fails to start.
Heres the output of cat /proc/bus/input/devices
Note that this is after I tried to do the guide.Code:I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/class/input/input0
H: Handlers=kbd event0
B: EV=120013
B: KEY=402000000 3802078f840d001 f2ffffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=7
I: Bus=0010 Vendor=001f Product=0001 Version=0100
N: Name="PC Speaker"
P: Phys=isa0061/input0
S: Sysfs=/class/input/input2
H: Handlers=kbd event2
B: EV=40001
B: SND=6
I: Bus=0000 Vendor=001f Product=001f Version=0000
N: Name="Mouseemu virtual keyboard"
P: Phys=
S: Sysfs=/class/input/input3
H: Handlers=kbd event3
B: EV=100003
B: KEY=1ffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff
I: Bus=0000 Vendor=001f Product=001e Version=0000
N: Name="Mouseemu virtual mouse"
P: Phys=
S: Sysfs=/class/input/input4
H: Handlers=mouse1 event4 ts1
B: EV=7
B: KEY=70000 0 0 0 0
B: REL=103
I: Bus=0005 Vendor=045e Product=007b Version=0039
N: Name="Microsoft Bluetooth keyboard"
P: Phys=00:50:F2:E1:B6:20
S: Sysfs=/class/input/input5
H: Handlers=kbd event5
B: EV=12000b
B: KEY=3 ffff000000000007 ff8018780803ffff fffeffdff3cfffff fffffffffffffffe
B: ABS=1f0000000000
B: LED=407
I: Bus=0003 Vendor=046d Product=c01e Version=2200
N: Name="Logitech USB-PS/2 Optical Mouse"
P: Phys=usb-0000:00:02.0-8/input0
S: Sysfs=/class/input/input14
H: Handlers=mouse0 event1 ts0
B: EV=7
B: KEY=ff0000 0 0 0 0
B: REL=103
As to the setup:
the comps a a64 runnin kubuntu dapper drake (Linux kubuntu 2.6.15-26-amd64-generic)
mouse is a mx518
graphics an evga 7900 gt
hd is a seagate 160 gig
cpu is a 3800
mobo is an asus a8n sli dlx
1 gig ram
Thats pretty much it, oh and thanks for the help :-)