PDA

View Full Version : Configuring Logitech mice (mx500, etc)



Pages : 1 [2]

detyabozhye
April 25th, 2006, 09:50 AM
I ahve a MS INTELLI MOUSE OPTICAL. And my side 2buttons work great in NAUTILUS. But I still want them to work in NAUTILUS so I followed the following guide to the letter:
:confused: If you have an MS mouse, why are you asking in a Logitech thread?

Golgoth
April 25th, 2006, 07:09 PM
:confused: If you have an MS mouse, why are you asking in a Logitech thread?

I used this method with an MS Intellimouse and Breezy and it worked very well as I explained in a previous post (http://ubuntuforums.org/showpost.php?p=566023&postcount=143)...

That's why he may ask for help.

The problem is that I does not have this mouse anymore so ashrack, I can not help you...

detyabozhye
April 25th, 2006, 10:00 PM
Should I make a full blown guide on how to make the MX500 work with evdev on Dapper?

ashrack
April 26th, 2006, 09:28 AM
I used this method with an MS Intellimouse and Breezy and it worked very well as I explained in a previous post (http://ubuntuforums.org/showpost.php?p=566023&postcount=143)...

That's why he may ask for help.

The problem is that I does not have this mouse anymore so ashrack, I can not help you...
But they still dont work in NAUTILUS! And they even stop workin in FIREFOX if I do:

gedit ~/.xbindkeysrc

"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[left]""
m:0x0 + b:6
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[right]""
m:0x0 + b:7
Could this be because am using DAPPER?

@detyabozhye
Because its pretty similar.

Giga
April 28th, 2006, 10:41 PM
DancingSun,

Do you know if there is logitech applet to install in amd64?
i got a log error that says:


dpkg: error processing /home/giga/logitech-applet-0.4test1/logitech-applet-0.4test1_0.4test1-1_x86_64.deb (--install):
package architecture (x86_64) does not match system (amd64)
Errors were encountered while processing:
/home/giga/logitech-applet-0.4test1/logitech-applet-0.4test1_0.4test1-1_x86_64.deb


Thanks

gzs
April 29th, 2006, 03:09 PM
Logitech MX518

I did everything in the guide (Omitting section 1.4 and I did not install the applet) and X would not start after the initial process.

I went back and completely redid it to insure I did not make a mistake, and again, X was "misconfigured" and would not start.

I used Nano to edit out the previously entered information and left it as default. The scroll wheel and left/right click worked previously so, I just used xbindkeys to get the Forward/Back (mouse 8/9) to work correctly.

All is well! I'm using Dapper Flight-6 by the way.

detyabozhye
April 29th, 2006, 09:35 PM
Look at my post in this thread for (partial) Dapper instructions, the link is in my sig.

Golgoth
April 30th, 2006, 07:59 PM
But they still dont work in NAUTILUS! And they even stop workin in FIREFOX if I do:

gedit ~/.xbindkeysrc

"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[left]""
m:0x0 + b:6
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[right]""
m:0x0 + b:7
Could this be because am using DAPPER?

@detyabozhye
Because its pretty similar.

I used this how-to with breezy... I did NOT try with the intellimouse and dapper.
So Yes, it could be like this because you are using dapper since evdev has changed...
Are "\[Alt_L]\[Left]" and "\[Alt_L]\[Right]" well capitalized in your xbindkeysrc?

mucha
May 2nd, 2006, 03:11 PM
detyabozhye, your guide worked perfect in xgl, but I used xte instead of click. Thanks! :)

detyabozhye
May 3rd, 2006, 12:28 AM
You're welcome! ^_^

Rizado
May 3rd, 2006, 07:30 PM
I got evdev working on Dapper perfectly (requires xmodmap and xbindkeys).
WARNING: This is not a full guide, please refer to post one in this thread for 800dpi resolution, back/forward in nautilus, etc.

First I did this to find out the name of my mouse:

cat /proc/bus/input/devices
Here's my output with the info I need in bold:

I: Bus=0010 Vendor=001f Product=0001 Version=0100
N: Name="PC Speaker"
P: Phys=isa0061/input0
S: Sysfs=/class/input/input0
H: Handlers=kbd event0
B: EV=40001
B: SND=6

I: Bus=0003 Vendor=046d Product=c025 Version=1800
N: Name="Logitech USB-PS/2 Optical Mouse"
P: Phys=usb-0000:00:1d.1-1/input0
S: Sysfs=/class/input/input1
H: Handlers=mouse0 event1 ts0
B: EV=7
B: KEY=ff0000 0 0 0 0 0 0 0 0
B: REL=103

I: Bus=0003 Vendor=049f Product=000e Version=0100
N: Name="Compaq Compaq Internet Keyboard"
P: Phys=usb-0000:00:1d.1-2/input0
S: Sysfs=/class/input/input2
H: Handlers=kbd event2
B: EV=120003
B: KEY=10000 7 ff87207a c14057ff febeffdf ffefffff ffffffff fffffffe
B: LED=7fff

I: Bus=0003 Vendor=049f Product=000e Version=0100
N: Name="Compaq Compaq Internet Keyboard"
P: Phys=usb-0000:00:1d.1-2/input1
S: Sysfs=/class/input/input3
H: Handlers=kbd event3
B: EV=3
B: KEY=20000 87a 5000d000 1e0000 0 0 0

Then I did this:

sudo gedit /etc/udev/rules.d/19-local.rules
and put this into the file and saved it (replace the bold part with the name of your mouse and replace the underlined part with whatever you want to put there, it will be used in xorg.conf):

KERNEL=="event[0-9]*", SYSFS{../name}=="Logitech USB-PS/2 Optical Mouse", NAME="input/mx500"
Then I changed my mouse section in xorg.conf to this:

Section "InputDevice"
Identifier "Configured Mouse"
Driver "evdev"
Option "CorePointer"
Option "Device" "/dev/input/mx500" #this should be that underlined name from 19-local.rules
EndSection
Then I made my ~/.Xmodmap look like this:

pointer = 1 3 2 4 5 8 9 6 7 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
Next I fixed cruise control (requires the compiling stuff; build-essential and all that I believe):
Download this file: http://bg.rifetech.com/click.tgz
untar it to ~/click (or wherever you want, just remember the dir, you'll need it in the .xbindkeysrc)
then compile it:

cd ~/click
make
Then I changed my ~/.xbindkeysrc to include this:

"~/click/click 4"
m:0x0 + b:11
"~/click/click 5"
m:0x0 + b:12

Credits: This article and http://floam.sh.nu/guides/mx1000
Let me know if I made any typos or mistakes.
EDIT: I don't think this works in Xgl, I haven't tried, but I doubt it will.I can't get it working properly :(
Creatin /dev/input/mx510 and using that works perfect but all extra buttons are recognized as a leftmouse click in firefox :confused:

This is what xev tell me when I use my side buttons.
ButtonPress event, serial 31, synthetic NO, window 0x1000001,
root 0x135, subw 0x0, time 4219485450, (169,0), root:(1461,76),
state 0x0, button 8, same_screen YES

ButtonRelease event, serial 31, synthetic NO, window 0x1000001,
root 0x135, subw 0x0, time 4219485578, (169,0), root:(1461,76),
state 0x0, button 8, same_screen YES

ButtonPress event, serial 31, synthetic NO, window 0x1000001,
root 0x135, subw 0x0, time 4219486730, (169,0), root:(1461,76),
state 0x0, button 9, same_screen YES

ButtonRelease event, serial 31, synthetic NO, window 0x1000001,
root 0x135, subw 0x0, time 4219486946, (169,0), root:(1461,76),
state 0x0, button 9, same_screen YES
I guess this looks alright. I'm using Kubuntu Dapper and in konqueror it doesn't seem to use the buttons as left click. And I didn't have any .Xmodmap or .xbindkeysrc so I created them.

detyabozhye
May 4th, 2006, 12:54 AM
I can't get it working properly :(
Creatin /dev/input/mx510 and using that works perfect but all extra buttons are recognized as a leftmouse click in firefox :confused:

This is what xev tell me when I use my side buttons.
ButtonPress event, serial 31, synthetic NO, window 0x1000001,
root 0x135, subw 0x0, time 4219485450, (169,0), root:(1461,76),
state 0x0, button 8, same_screen YES

ButtonRelease event, serial 31, synthetic NO, window 0x1000001,
root 0x135, subw 0x0, time 4219485578, (169,0), root:(1461,76),
state 0x0, button 8, same_screen YES

ButtonPress event, serial 31, synthetic NO, window 0x1000001,
root 0x135, subw 0x0, time 4219486730, (169,0), root:(1461,76),
state 0x0, button 9, same_screen YES

ButtonRelease event, serial 31, synthetic NO, window 0x1000001,
root 0x135, subw 0x0, time 4219486946, (169,0), root:(1461,76),
state 0x0, button 9, same_screen YES
I guess this looks alright. I'm using Kubuntu Dapper and in konqueror it doesn't seem to use the buttons as left click. And I didn't have any .Xmodmap or .xbindkeysrc so I created them.
Do you have xmodmap and xbindkeys installed?
If not:

sudo apt-get install xmodmap

sudo apt-get install xbindkeys
From the description of your problem, it seems xmodmap is not installed.

siorai
May 4th, 2006, 05:01 AM
Next I fixed cruise control (requires the compiling stuff; build-essential and all that I believe):
Download this file: http://bg.rifetech.com/click.tgz
untar it to ~/click (or wherever you want, just remember the dir, you'll need it in the .xbindkeysrc)
then compile it:

cd ~/click
make
Then I changed my ~/.xbindkeysrc to include this:

"~/click/click 4"
m:0x0 + b:11
"~/click/click 5"
m:0x0 + b:12

Credits: This article and http://floam.sh.nu/guides/mx1000
Let me know if I made any typos or mistakes.
EDIT: I don't think this works in Xgl, I haven't tried, but I doubt it will.

I've run into a roadblock here. I've edited my xorg.conf, 19-local.rules, and Xmodmap pretty much well exactly like you have. My mouse is being shown as "B16_b_02 USB-PS/2 Optical Mouse" when I cat /proc/bus/input/devices so I'm of course using that. At least at this point my mouse is working like it was. Everything is fine except the side buttons do nothing in Firefox. When I use xev, it does show the side buttons as 6 and 7 so that looks right, but they're just not doing anything. With xev showing the buttons like that is it something wrong with my config, or is it possibly something wrong with Firefox?

Edit: Just noticed something... In Firefox, the side buttons are actually doing something. In the code windows on this page, the side buttons will cause the scroll bar to move back and forth horizontally...

My second problem is when I try to run make for click. I get the following:


siorai@dagon:~/click$ make
gcc -Wall -c -o click.o click.c
click.c:3:22: error: X11/Xlib.h: No such file or directory
click.c:4:34: error: X11/extensions/XTest.h: No such file or directory
click.c: In function ‘main’:
click.c:9: error: ‘Display’ undeclared (first use in this function)
click.c:9: error: (Each undeclared identifier is reported only once
click.c:9: error: for each function it appears in.)
click.c:9: error: ‘dpy’ undeclared (first use in this function)
click.c:9: warning: implicit declaration of function ‘XOpenDisplay’
click.c:22: warning: implicit declaration of function ‘XTestFakeButtonEvent’
click.c:22: error: ‘True’ undeclared (first use in this function)
click.c:22: error: ‘CurrentTime’ undeclared (first use in this function)
click.c:26: error: ‘False’ undeclared (first use in this function)
click.c:29: warning: implicit declaration of function ‘XCloseDisplay’
make: *** [click.o] Error 1


I'm at a loss as to how to interpret that. I realize the second and third lines show things to be missing, but how would I go about fixing that?



Edit: Ok, got my forward/back working now. I started to think about what I might have changed with the Firefox config. I realized that I had changed the option for changing tabs with the scroll wheel. It's mousewheel.horizscroll.withnokey.action 2. I had set it to 0 to disable that "feature." Well, I put it back to default and the forward/back works and as an added bonus, the mousewheel no longer scrolls between tabs. :D Still at a loss about the click problem, but it's not a huge deal.

detyabozhye
May 4th, 2006, 05:40 AM
My second problem is when I try to run make for click. I get the following:


siorai@dagon:~/click$ make
gcc -Wall -c -o click.o click.c
click.c:3:22: error: X11/Xlib.h: No such file or directory
click.c:4:34: error: X11/extensions/XTest.h: No such file or directory
click.c: In function ‘main’:
click.c:9: error: ‘Display’ undeclared (first use in this function)
click.c:9: error: (Each undeclared identifier is reported only once
click.c:9: error: for each function it appears in.)
click.c:9: error: ‘dpy’ undeclared (first use in this function)
click.c:9: warning: implicit declaration of function ‘XOpenDisplay’
click.c:22: warning: implicit declaration of function ‘XTestFakeButtonEvent’
click.c:22: error: ‘True’ undeclared (first use in this function)
click.c:22: error: ‘CurrentTime’ undeclared (first use in this function)
click.c:26: error: ‘False’ undeclared (first use in this function)
click.c:29: warning: implicit declaration of function ‘XCloseDisplay’
make: *** [click.o] Error 1


I'm at a loss as to how to interpret that. I realize the second and third lines show things to be missing, but how would I go about fixing that?

Seems you're missing these two packages:

libx11-dev
x11proto-xext-dev
Install them via Synaptic cuz they have a bunch of dependencies, so I wouldn't want to try to install them via command line.

Rizado
May 4th, 2006, 02:21 PM
Do you have xmodmap and xbindkeys installed?
If not:

sudo apt-get install xmodmap

sudo apt-get install xbindkeys
From the description of your problem, it seems xmodmap is not installed.xbindkeys wasn't installed but
xmodmap was, the problem was .Xmodmap wasn't autoloaded so I had to make a script to do that.

What is the click tool and script actually doing?

detyabozhye
May 4th, 2006, 06:07 PM
xbindkeys wasn't installed but
xmodmap was, the problem was .Xmodmap wasn't autoloaded so I had to make a script to do that.

What is the click tool and script actually doing?
They're making button 11 and 12 do button 4 and 5 because those buttons act as left click in Opera and Firefox. The cruise control buttons send 4 and 5 as well as 11 and 12 at the same time.

Rizado
May 6th, 2006, 12:48 PM
Well, there was some updates yesterday and today and I think I remember evdev was updated. Anyway when I rebooted evdev driver doesn't work anymore. Am I the only one with the problems?

BTW this is on dapper.

siorai
May 6th, 2006, 03:25 PM
Well, there was some updates yesterday and today and I think I remember evdev was updated. Anyway when I rebooted evdev driver doesn't work anymore. Am I the only one with the problems?

BTW this is on dapper.

I just had this happen as well. Everything was fine until I actually restarted then X won't start, complaining about not having a valid CorePointer. :-(

detyabozhye
May 6th, 2006, 09:58 PM
The new evdev is sort of broken at the moment, they should fix it soon I think. I haven't been able to find a workaround for it to use at the moment, so I have the old version of evdev right now. bug #43100 (https://launchpad.net/distros/ubuntu/+source/xserver-xorg-input-evdev/+bug/43100)

kemosabe79
May 7th, 2006, 06:58 AM
Great HOWTO. I used it with a MX310 and it works great. I tried it because it has essentially the same specs as the MX510, and it worked. Might want to add the MX310 to your list. :)This was done in Breezy, BTW...using 8 buttons not 10.

Rizado
May 7th, 2006, 07:42 AM
Ok, Where can I get the old driver?

EDIT: I found a old working version on the cd.

detyabozhye
May 7th, 2006, 07:36 PM
If anyone else is looking for it, here it is: http://ftp.kfki.hu/linux/ubuntu/pool/main/x/xserver-xorg-input-evdev/xserver-xorg-input-evdev_1.0.0.5-0ubuntu2_i386.deb

siorai
May 8th, 2006, 03:50 AM
If anyone else is looking for it, here it is: http://ftp.kfki.hu/linux/ubuntu/pool/main/x/xserver-xorg-input-evdev/xserver-xorg-input-evdev_1.0.0.5-0ubuntu2_i386.deb

That link isn't working anymore. I was able to find the files here though: http://mir2.ovh.net/ubuntu/pool/main/x/xserver-xorg-input-evdev/ but I'm not sure how to apply the patch, that is what the .diff file is right?

clov
May 10th, 2006, 07:55 PM
I get this when I run .xbindkeysrc


./.xbindkeysrc
./.xbindkeysrc: line 1: /usr/X11R6/bin/xvkbd -xsendevent -text [Alt_L][Left]: No such file or directory
./.xbindkeysrc: line 2: m:0x0: command not found
./.xbindkeysrc: line 3: /usr/X11R6/bin/xvkbd -xsendevent -text [Alt_L][Right]: No such file or directory
./.xbindkeysrc: line 4: m:0x0: command not found


my .xbindkeysrc looks like this:


"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[Left]""
m:0x0 + b:8
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[Right]""
m:0x0 + b:9

(I own a mx610 buttons 8 and 9 are my thumb buttons)

Does anyone knows what my problem is?
I've tried to have .xbindkeysrc without " " but than it says:


^[[3D./.xbindkeysrc: line 2: m:0x0: command not found
^[[3C./.xbindkeysrc: line 4: m:0x0: command not found

](*,)

detyabozhye
May 10th, 2006, 09:26 PM
you're supposed to run xbindkeys, not ./.xbindkeysrc

clov
May 10th, 2006, 11:11 PM
you're supposed to run xbindkeys, not ./.xbindkeysrc

#-o](*,) thkx

daedalusman
May 11th, 2006, 12:41 AM
Does any one have an idea when the evdev driver will work again in dapper? I really want to get my mouse buttons working again, its really annoying having to click on the back foward buttons in firefox and nautilus. I would drop back to the older version but I'm not really sure how to go about doing that, if someone could help me out there in the mean time that would be great for the time being. Thanks for the info.

detyabozhye
May 11th, 2006, 03:48 AM
Here's the old evdev package: http://detyabozhye.com/other/xserver-xorg-input-evdev_1.0.0.5-0ubuntu2_i386.deb

Rizado
May 11th, 2006, 04:41 PM
You can start synaptic and search for xserver-xorg-input-evdev and mark it. Press Ctrl + E, select the older one and press force version, apply and it'll probably ask you to insert your cd. Make sure you don't update it again until the bug is fixed.

siorai
May 11th, 2006, 05:02 PM
Here's the old evdev package: http://detyabozhye.com/other/xserver-xorg-input-evdev_1.0.0.5-0ubuntu2_i386.deb

Awesome. Thank you very much.

makhand
May 11th, 2006, 07:11 PM
Is there a way to not have the mouse as the 'CorePointer', but instead send core events (so you can start without it present), but still be able to plug it in later and have it automatically detected and working? This is for a laptop

tonyo46
May 23rd, 2006, 10:40 PM
Thank you for this HowTo, but I have a problem now :
- my touchpad doesn't work...
- if I unplug my mouse, and then replug it, it doesn't work anymore, and I have to restart x-server

How could I solve those problems ?

detyabozhye
May 24th, 2006, 12:15 AM
I think you'd have to make the touchpad as another pointer using the mouse(?) driver for that. I'm not sure how to make it all work though.

makhand
May 24th, 2006, 12:31 AM
- my touchpad doesn't work...
- if I unplug my mouse, and then replug it, it doesn't work anymore, and I have to restart x-server

I have similar problems and have not gotten much help here. I think to get the touchpad to work, i had to make it 'CorePointer', while making the mouse 'SendCoreEvents'. I'll attach a snippet of my xorg.conf file below


Section "InputDevice"
Identifier "Synaptics Touchpad"
Driver "synaptics"
Option "CorePointer"
Option "Device" "/dev/psaux"
Option "Protocol" "auto-dev"
Option "HorizScrollDelta" "1"
Option "SHMConfig" "on"
Option "AccelFactor" ".0008"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "SendCoreEvents" "true"
Option "Protocol" "evdev"
Option "Dev Name" "Logitech USB Receiver"
Option "Dev Phys" "usb-*/input0"
Option "Device" "/dev/input/event2"
Option "Buttons" "12"
Option "ZAxisMapping" "4 5 7 6"
Option "Resolution" "800"
EndSection

...

Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "Default Screen"
Screen 1 "VGA" RightOf "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
InputDevice "Synaptics Touchpad"
EndSection

as far as how to make it work after unplugging the mouse, I have NO clue and would really appreciate some help also. If you figure it out, please post.

tonyo46
May 24th, 2006, 07:51 AM
thank you makhand but I still don't have my touchpad working !
I tried all the combinations possible...

I'm looking for a way to return to my previous config properly because, now, I can't use my laptop without my mouse.
What do I have to do to return to a basic configuration ? if I only change my xorg.conf, the system crashes...

makhand
May 24th, 2006, 02:36 PM
I'm looking for a way to return to my previous config properly because, now, I can't use my laptop without my mouse.
What do I have to do to return to a basic configuration ? if I only change my xorg.conf, the system crashes...

Yes, xorg.conf is a pretty sensitive file to mess with. Any little mistake screws everything up.

Get to a place where you can type command line commands. For example, if you can get X working at all, you can open a terminal. If X is crashing and giving you error messages, you can press Ctrl +Alt+F6 to get to a place where you can login and type commands. Even if X is sort of working, to where you can use your keyboard, type those keys.

once there, login, then do:

sudo dpkg-reconfigure xserver-xorg
This should take you through the basic configuration ubuntu does on install. Usually you just go with whatever option it gives you and it should be fine. You will probably want to keep your mouse unplugged during this process. (it may be the other way around, but it doesnt take long either way).

Let me know if that restores you to your normal system.

tranzndance
May 27th, 2006, 10:10 PM
Hello,

Thank you for the tutorial. I would like to program the side buttons to do copy and paste. I tried to edit the code myself but can't get it to work.

How can I change the following to use ctrl V and C?

"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[left]""
m:0x0 + b:6
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[right]""
m:0x0 + b:7

I checked out http://homepage3.nifty.com/tsato/xvkbd/ to see the syntax for "control" but I don't really get it, especially since it doesn't match what you use for "alt".

To make sure the setup is correct, I used the code you provided, and I was able to navigate forward and backward with the side buttons.

R3linquish3r
May 29th, 2006, 12:28 PM
I dont have Xmodmap loaded, but I do have Xbindkeys loaded. Weird thing is my cruise control work as they should but my side buttons do nothing and XEV doesn't even seem to recognise them ](*,) . I'm using an MX510. Heres some of my info if it helps:


I: Bus=0003 Vendor=046d Product=c01d Version=2100
N: Name="Logitech USB-PS/2 Optical Mouse"
P: Phys=usb-0000:00:10.3-2/input0
S: Sysfs=/class/input/input2
H: Handlers=mouse0 event1 ts0
B: EV=7
B: KEY=ff0000 0 0 0 0 0 0 0 0
B: REL=103


Section "InputDevice"
Identifier "Configured Mouse"
Driver "evdev"
Option "Dev Name" "Logitech USB-PS/2 Optical Mouse"
Option "Dev Phys" "usb-0000:00:10.3-2/input0"
Option "Device" "/dev/input/event1"
Option "Buttons" "10"
Option "ZAxisMapping" "4 5"
EndSection


# Volume Up
"amixer set Master,0 5%+"
m:0x0 + c:176

# Volume Down
"amixer set Master,0 5%-"
m:0x0 + c:174

# Toggle Volume
"amixer set Master,0 toggle"
m:0x0 + c:160

"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[Left]""
m:0x0 + b:8
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[Right]""
m:0x0 + b:9


Heres the XEV Output for my two side buttons:


MotionNotify event, serial 30, synthetic NO, window 0x2400001,
root 0x135, subw 0x0, time 2145993778, (115,2), root:(325,234),
state 0x10, is_hint 0, same_screen YES

MotionNotify event, serial 30, synthetic NO, window 0x2400001,
root 0x135, subw 0x0, time 2145993786, (115,1), root:(325,233),
state 0x10, is_hint 0, same_screen YES

MotionNotify event, serial 30, synthetic NO, window 0x2400001,
root 0x135, subw 0x0, time 2145993794, (117,1), root:(327,233),
state 0x10, is_hint 0, same_screen YES

MotionNotify event, serial 30, synthetic NO, window 0x2400001,
root 0x135, subw 0x0, time 2145993802, (117,0), root:(327,232),
state 0x10, is_hint 0, same_screen YES

Does anyone see anything wrong? I've been working two days on this and still no solution :(.

R3linquish3r
May 29th, 2006, 01:01 PM
Well after a half hour of working with Xmodmap I finally have my forward and back buttons working. The only thing still broken is my top cruise control which xev seems to think is bound the button 4 AND button 6. I never use it anyway so it isn't really a big deal I'm just glad to have a side buttons :)

gelse
May 31st, 2006, 01:54 PM
after some struggle i managed to get my mouse working with evdev - seems that driver "mouse" doesnt recognize the evdev protocol, but it works with driver "evdev".
but there is still one problem left:
i have an (old) MX500, which reports as "B16_b_02 USB-PS/2 Optical Mouse"
here the relevant parts of my xorg.conf:

Section "InputDevice"
Identifier "evdev Mouse"
Driver "evdev"
Option "Protocol" "evdev"
Option "SendCoreEvents" "true"
Option "Dev Name" "B16_b_02 USB-PS/2 Optical Mouse"
Option "Dev Phys" "usb-0000:00:1d.0-1/input0"
Option "Device" "/dev/input/event4"
Option "Buttons" "10"
Option "ZAxisMapping" "4 5 7 6"
EndSection
Section "InputDevice"
Identifier "Synaptics Touchpad"
Driver "synaptics"
Option "CorePointer"
Option "Device" "/dev/psaux"
Option "Protocol" "auto-dev"
Option "HorizScrollDelta" "0"
EndSection
the relevant output from xorg.log:

(II) evdev brain: Rescanning devices (1).
(**) Option "SendCoreEvents" "true"
(**) evdev Mouse-usb-0000:00:1d.0-1/input0: always reports core events
(II) evdev Mouse-usb-0000:00:1d.0-1/input0: Found 3 relative axes.
(II) evdev Mouse-usb-0000:00:1d.0-1/input0: Configuring as pointer.
(**) evdev Mouse-usb-0000:00:1d.0-1/input0: WHEELRelativeAxisButtons: 4 5.
(II) evdev Mouse-usb-0000:00:1d.0-1/input0: Found 8 mouse buttons
(II) evdev Mouse-usb-0000:00:1d.0-1/input0: Configured 10 mouse buttons
....
(II) XINPUT: Adding extended input device "evdev Mouse-usb-0000:00:1d.0-1/input0" (type: MOUSE)
(II) XINPUT: Adding extended input device "evdev brain" (type: evdev brain)
....
(**) evdev Mouse-usb-0000:00:1d.0-1/input0: 3 valuators.
(**) ../../src/evdev_btn.c (90): Registering 10 buttons.
(II) evdev Mouse-usb-0000:00:1d.0-1/input0: Init
....
(II) evdev brain: Rescanning devices (2).
(II) evdev Mouse-usb-0000:00:1d.0-1/input0: On

and here some output from xev:
mwheel up:

ButtonPress event, serial 30, synthetic NO, window 0x3a00001,
root 0x52, subw 0x0, time 2323091254, (162,119), root:(176,550),
state 0x0, button 4, same_screen YES

ButtonRelease event, serial 30, synthetic NO, window 0x3a00001,
root 0x52, subw 0x0, time 2323091254, (162,119), root:(176,550),
state 0x800, button 4, same_screen YES

mwheel down:

ButtonPress event, serial 27, synthetic NO, window 0x3a00001,
root 0x52, subw 0x0, time 2323134100, (173,14), root:(187,445),
state 0x0, button 5, same_screen YES

ButtonRelease event, serial 27, synthetic NO, window 0x3a00001,
root 0x52, subw 0x0, time 2323134100, (173,14), root:(187,445),
state 0x1000, button 5, same_screen YES
button in above the mwheel:

ButtonPress event, serial 27, synthetic NO, window 0x3a00001,
root 0x52, subw 0x0, time 2323300554, (175,19), root:(189,450),
state 0x0, button 9, same_screen YES

ButtonPress event, serial 27, synthetic NO, window 0x3a00001,
root 0x52, subw 0x0, time 2323300554, (175,19), root:(189,450),
state 0x0, button 4, same_screen YES

ButtonRelease event, serial 27, synthetic NO, window 0x3a00001,
root 0x52, subw 0x0, time 2323300554, (175,19), root:(189,450),
state 0x800, button 4, same_screen YES

ButtonRelease event, serial 27, synthetic NO, window 0x3a00001,
root 0x52, subw 0x0, time 2323300706, (175,19), root:(189,450),
state 0x0, button 9, same_screen YES
as long as that button is pressed, it toggles button 4 press and release in between the button9 events.
the button below the mwheel:

ButtonPress event, serial 27, synthetic NO, window 0x3a00001,
root 0x52, subw 0x0, time 2323388549, (178,9), root:(192,440),
state 0x0, button 5, same_screen YES

ButtonRelease event, serial 27, synthetic NO, window 0x3a00001,
root 0x52, subw 0x0, time 2323388549, (178,9), root:(192,440),
state 0x1000, button 5, same_screen YES

the button below that button:

ButtonPress event, serial 27, synthetic NO, window 0x3a00001,
root 0x52, subw 0x0, time 2323451513, (177,22), root:(191,453),
state 0x0, button 8, same_screen YES

ButtonRelease event, serial 27, synthetic NO, window 0x3a00001,
root 0x52, subw 0x0, time 2323451673, (177,22), root:(191,453),
state 0x0, button 8, same_screen YES
the two buttons on the side work like a charm as buttons 6 and 7

my problem is:
when i DID NOT use evdev, it reported and recognized MORE buttons than it did now with evdev (have to relog to check it with evdev again, i'll post it if you tell me to)
in both cases the front button reported the mwheelup and an own button as described above, when i used the mouse-protocol, it reported the button on the other side of the mwheel as an own event.

any ideas how i can get rid of that extra-toggling the mwheel in the front, and how i can get all 10 buttons to work?

(using ubuntu dapper drake with xgl working - like a charm on dell inspiron 9300, even the side-slot for SD-cards works! had to tell that, sorry... ;) )
ah, and btw - no xmodmap yet, as that doesnt affect the xev at all - does it?

NT4usB
June 2nd, 2006, 01:07 AM
Configuring Logitech mice... with a twist.
Following your guide, I was able to get my Mx310 to work as advertized.
Thank you for that!
Now for the twist.
I would like the left (thumb/back) button to act like the middlebutton. Several apps I run require use of middlebutton and trying to click the scrollwheel without spazzing is tough. In Firefox, I rarely use back and when I do, rightclick contextmenu is fine. (In windoz) I use left (back) button to open links in new tabs and close tabs.
I don't use the right (forward) button at all and use the top button for closeapp.
Any tips on how to tweak the left (back) button to act like middlebutton?
ed: While we're at it, any way to get the scroll wheel to go a page at a time instead of three lines (or whatever) it does now? I'm wearing the poor thing out browsing these forums!
:o
Happy Linux user for going on 3 weeks now!

lleberg
June 2nd, 2006, 01:42 PM
Hi!
I used this guide quite a while ago, and got it working great.

But, yesterday i upgraded to Dapper, everything is fine, except for my mouse!
I couldn't get into using the setup so i used the old one..

The error says it can't find evdev. or that it's unknown.
But the package xserver-xorg-input-evdev is up to date..

Anyone else who knows this problem?

siorai
June 2nd, 2006, 02:29 PM
Hi!
I used this guide quite a while ago, and got it working great.

But, yesterday i upgraded to Dapper, everything is fine, except for my mouse!
I couldn't get into using the setup so i used the old one..

The error says it can't find evdev. or that it's unknown.
But the package xserver-xorg-input-evdev is up to date..

Anyone else who knows this problem?

The most up to date evdev is broken. Go back to page 28 in this thread. detyabozhye has posted xserver-xorg-input-evdev_1.0.0.5-0ubuntu2_i386.deb. Install that and then lock it in synaptic. Just remember that if you do a dist-upgrade, that evdev will be updated and you'll have to replace it with this older version again.

lleberg
June 2nd, 2006, 02:53 PM
Well. i found a workaround. or whatever i should call it.

Set the driver to evdev instead of mouse. and change the protocol to ImPS/2 instead of evdev.

And, this thread only has 15 pages, TOO BAD! :D

antidrugue
June 2nd, 2006, 03:20 PM
This may have been covered by one of the other million posts in this thread, but a rehash with slightly different wording can only help for the loveable lost Googlers out there! ;)

To get my Logitech MX510 working from a base Dapper Drake Flight 6 install (with some acceleration tweaks done through UI configuration tools in Gnome), I tried following several over-complicated (for my particular case) guides, then realised I could do away with all their stuff and make only a few small changes. My current /etc/X11/xorg.conf contains an InputDevice section as follows:


Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "Buttons" "10"
Option "ZAxisMapping" "4 5"
Option "ButtonMapping" "1 2 3 6 7"
# Option "Emulate3Buttons" "true"
EndSection

The important (modified) lines are:


Section "InputDevice"
Option "Buttons" "10"
Option "ZAxisMapping" "4 5"
Option "ButtonMapping" "1 2 3 6 7"
# Option "Emulate3Buttons" "true"
EndSection

...but you should be able to leave Emulate3Buttons on if you really want; it just fakes click from the third mouse button when buttons 1 and 2 are pressed together - not something that's too useful on a 10 button (including both scroll directions) mouse! :P

ZAxisMapping specifies which buttons to treat as the scroll-wheel. ButtonMapping specifies, in order of physical buttons, a list of button signals to send. So mine tells it that buttons 4 and 5 'pretend' to be 6 and 7 respectively. My other buttons are working as expected too (auto-scroll buttons are fine, window switch button just acts as another left button), so I presume they're implicitly mapped to their 'natural' signals (i.e. 8 to 8, 9 to 9, 10 to 10). (???)

This works fine for me in Firefox, but not other apps such as Nautilus. Does anyone know if this is expected (i.e. that you need to emulate keystrokes like ALT+{LEFT | RIGHT} from mouse clicks anyway)?

In Dapper, PsychoBrat's instructions work flawlessly.

phatmonkey
June 2nd, 2006, 04:39 PM
In Dapper, PsychoBrat's instructions work flawlessly.
Back/forward in firefox does not seem to be working for me with these instructions.

antidrugue
June 2nd, 2006, 04:49 PM
Back/forward in firefox does not seem to be working for me with these instructions.

Back/forward work for me in Firefox. Here is the relevant part in /etc/X11/xorg.conf:



Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "Resolution" "800"
Option "Buttons" "10"
Option "ZAxisMapping" "4 5"
Option "ButtonMapping" "1 2 3 6 7"
EndSection


Nothing else than /etc/X11/xorg.conf was changed on my install. I have a MX500 from Logitech.

xeta
June 2nd, 2006, 10:06 PM
MX518 not working. Tried countless configs listed in this thread.


Relevant info:

Xorg


Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "Resolution" "800"
Option "Buttons" "10"
Option "ZAxisMapping" "4 5"
Option "ButtonMapping" "1 2 3 6 7"
EndSection


/proc/bus/input/devices


stang@silva:~$ cat /proc/bus/input/devices
I: Bus=0003 Vendor=046d Product=c01e Version=2200
N: Name="Logitech USB-PS/2 Optical Mouse"
P: Phys=usb-0000:00:0b.0-1/input0
S: Sysfs=/class/input/input0
H: Handlers=mouse0 ts0 event0
B: EV=7
B: KEY=ff0000 0 0 0 0 0 0 0 0
B: REL=103



xev


ButtonPress event, serial 29, synthetic NO, window 0x2800001,
root 0x135, subw 0x0, time 2526076444, (170,97), root:(182,197),
state 0x10, button 8, same_screen YES

ButtonPress event, serial 29, synthetic NO, window 0x2800001,
root 0x135, subw 0x0, time 2526077132, (168,98), root:(180,198),
state 0x10, button 9, same_screen YES

xeta
June 2nd, 2006, 11:25 PM
Forgot to mention: Dapper.

detyabozhye
June 2nd, 2006, 11:53 PM
Look here: http://ubuntuforums.org/showthread.php?p=955049#post955049
and here: http://ubuntuforums.org/showpost.php?p=992685&postcount=272

Mr_J_
June 3rd, 2006, 03:39 AM
MX518 has 8 buttons not 10. The plus and minus are not going to work.
I have one. Made it work. Just installed 6.06 so lost the xorg...

opticyclic
June 3rd, 2006, 03:43 AM
This worked great with Breezy, but now I have upgraded to Dapper I have had to revert to the previous conf to stop X from crashing.
Any changes I seem to make to the mouse section seems to crash X :confused:
Its frustrating not to have the thumb buttons and the up/down buttons on my MX510 work ](*,)
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "Emulate3Buttons" "true"
Option "ZAxisMapping" "4 5"
EndSection

#Section "InputDevice"
# Identifier "Configured Mouse"
# Driver "mouse"
# Option "Protocol" "evdev"
# Option "Dev Name" "PS2++ Logitech MX Mouse"
# Option "Dev Phys" "isa0060/serio1/input0"
# Option "Device" "/dev/input/event2"
# Option "Buttons" "10"
# Option "ZAxisMapping" "4 5"
#EndSection

Cenotaph
June 3rd, 2006, 06:09 AM
hmm... does anyone managed to get the side buttons to work in nautilus with Dapper?

detyabozhye
June 3rd, 2006, 06:10 AM
I'll write a full guide for Dapper and evdev when I get a chance, for now refer to my signiture.

opticyclic
June 3rd, 2006, 12:43 PM
I have a minor improvement.
I copied and edited gelses xorg.conf (http://ubuntuforums.org/showpost.php?p=1071965&postcount=290)
I now have evdev working and my xorg.conf looks like this
Section "InputDevice"
Identifier "Configured Mouse"
Driver "evdev"
Option "Protocol" "evdev"
Option "SendCoreEvents" "true"
Option "Dev Name" "PS2++ Logitech MX Mouse"
Option "Dev Phys" "isa0060/serio1/input0"
Option "Device" "/dev/input/event2"
Option "Buttons" "11"
Option "ZAxisMapping" "4 5"
EndSectionThe thing is xev doesn't report any button presses when I press the side buttons of my MX510

LeaveNotify event, serial 29, synthetic NO, window 0x1c00001,
root 0x119, subw 0x1c00002, time 2578353718, (40,39), root:(45,85),
mode NotifyGrab, detail NotifyVirtual, same_screen YES,
focus YES, state 16

EnterNotify event, serial 29, synthetic NO, window 0x1c00001,
root 0x119, subw 0x1c00002, time 2578354041, (40,39), root:(45,85),
mode NotifyUngrab, detail NotifyVirtual, same_screen YES,
focus YES, state 16

KeymapNotify event, serial 29, synthetic NO, window 0x0,
keys: 25 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

However, when I have my ~/.xbindkeysrc set to
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[Left]""
m:0x0 + b:6
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[Right]""
m:0x0 + b:7xev reports the button presses as 8 and 9
It seems to be the ~/.xbindkeysrc that is causing a problem when I change 6 and 7 to 8 and 9
Do I need to modify anything in xorg.conf when I make changes to ~/.xbindkeysrc?

detyabozhye
June 3rd, 2006, 05:32 PM
1) Xgl works with evdev differently from regular Xorg, so if you are running Xgl, that may be part of your problem.

2) Use xmodmap to make the side buttons 6 an 7. Refer to my sig to see how.

Gtaylor
June 3rd, 2006, 11:29 PM
This works for me with a Logitech MX510 on Dapper. xmodmap seems to be quite unreliable:



Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "Buttons" "5"
Option "ButtonMapping" "1 2 3 6 7"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "false"
EndSection

The only problem is the button above the scroll wheel makes the browser go back instead of scrolling up, but I never use that silly little thing anyway. Thumb buttons work, mouse wheel scrolling works. You do -NOT- need any .xmodmap or imwheel modifications for this to work, just this edit of xorg.conf.

detyabozhye
June 4th, 2006, 02:17 AM
Two problems with that: you already mentioned that the button above the scroll wheel works funny, some people use that button (I do).

The other problem is the tilt wheel won't work with that setup.

Gtaylor
June 4th, 2006, 04:04 AM
Two problems with that: you already mentioned that the button above the scroll wheel works funny, some people use that button (I do).

The other problem is the tilt wheel won't work with that setup.
Assuming you don't use the top button, it's fine :) The original posts and replies don't work at all on my setup, this is a big step up from having nothing to having something.

And tilt wheel? What? On an MX510? I have a scroll wheel and that works fine.

detyabozhye
June 4th, 2006, 04:35 AM
I mean for the higher models, and the link in my sig works with the older version of evdev perfectly.

DancingSun
June 4th, 2006, 06:58 AM
I now have evdev working and my xorg.conf looks like this
Section "InputDevice"
Identifier "Configured Mouse"
Driver "evdev"
Option "Protocol" "evdev"
Option "SendCoreEvents" "true"
Option "Dev Name" "PS2++ Logitech MX Mouse"
Option "Dev Phys" "isa0060/serio1/input0"
Option "Device" "/dev/input/event2"
Option "Buttons" "11"
Option "ZAxisMapping" "4 5"
EndSectionThe thing is xev doesn't report any button presses when I press the side buttons of my MX510
I used yours as a template and this worked fine for me in Ubuntu 6.06. Here's mine:


Section "InputDevice"
Identifier "Mouse0"
Driver "evdev"
Option "Dev Name" "Logitech MX510"
Option "Dev Phys" "usb-0000:00:02.0-2/input0"
Option "Device" "/dev/input/event1" # (cat /proc/bus/input/devices)
Option "SendCoreEvents" "true"
Option "Buttons" "8"
Option "ZAxisMapping" "4 5"
EndSection

I don't have any mappings and the thumb buttons works fine in xev and in firefox.

opticyclic
June 4th, 2006, 05:22 PM
1) Xgl works with evdev differently from regular Xorg, so if you are running Xgl, that may be part of your problem.

2) Use xmodmap to make the side buttons 6 an 7. Refer to my sig to see how.I don't think I am running Xgl. How can I tell?
I don't fully understand how xmodmap works.
Your guide doesnt explain how to modify it for myself.
If I follow your guide X returns NULL for the Configured mouse.

All the buttons, inc. cruise control work perfectly with the basic conf
(I don't need to install click)
Its just the side buttons that are getting to me

DancingSun: You say you don't have any mappings.
Do you have your ~/.xbindkeysrc set?

opticyclic
June 4th, 2006, 05:56 PM
Praise Be! [-o<
The side buttons now work on my MX510! \\:D/
I followed this guide here
http://www.linux-gamers.net/modules/wiwimod/index.php?page=HOWTO+Mouse+Buttons

xorg.conf now looks like this
Section "InputDevice"
Identifier "Configured Mouse"
Driver "evdev"
Option "Device" "/dev/input/event2" # (cat /proc/bus/input/devices)
Option "Name" "Logitech MX510"
EndSection~/.xbindkeysrc looks like this
"xvkbd -xsendevent -text "\[Alt_L]\[Left]""
m:0x10 + b:8
"xvkbd -xsendevent -text "\[Alt_L]\[Right]""
m:0x10 + b:9and ~/.Xmodmap looks like this
pointer = 1 3 2 4 5 8 9 6 7 10

detyabozhye
June 5th, 2006, 10:27 PM
I set up a full guide here for evdev in Dapper.
http://ubuntuforums.org/showthread.php?t=188302
I might change the HOWTO though, once I experiment with the new evdev driver which didn't work the last time I tried.

Gtaylor
June 6th, 2006, 03:34 AM
Hrmm, apparently that button that I said was broken is only funky in Firefox. It appears to work just fine in everything else I've tried it with, must be a strange Firefox binding or something.

For MX510 users on Dapper, just set your mouse up in xorg.conf and don't bother with all this other stuff. Requires no real hacking and won't make your box act funky through later upgrades.

detyabozhye
June 6th, 2006, 06:35 AM
Well, I'd say both methods are good. Those who don't have tilt wheel and don't mind a button working weird and want a simple solution, they can use your method.

But if people want their tilt wheel working and all the buttons too and they don't mind doing some work, my guide is for them.

Gtaylor
June 6th, 2006, 02:46 PM
As mentioned, the MX510 doesn't have a tilt wheel and the button works fine, Firefox has a weird binding that can be easily fixed. Hence, anyone with an MX510 requires no special configuration. I can't speak for others models, but for the MX510, this is fine. No tilt wheel, buttons are fine, etc.

It really is best to avoid installing and pinning outside packages and modifying a lot of config files if you can. Hence my recommendation for any MX510 users to use the simple method. I'm going to do some more research and see if the other more advanced Logitech mice can be made to work within xorg.conf too.

GarethMB
June 6th, 2006, 04:23 PM
i have x700 and i'm using aiglx and compiz the method described on the first page doesn't work for me. Does anyone know where i can find info on this?

Ie. i can't start x with new settings in xorg.conf

detyabozhye
June 6th, 2006, 08:39 PM
As mentioned, the MX510 doesn't have a tilt wheel and the button works fine, Firefox has a weird binding that can be easily fixed. Hence, anyone with an MX510 requires no special configuration. I can't speak for others models, but for the MX510, this is fine. No tilt wheel, buttons are fine, etc.

It really is best to avoid installing and pinning outside packages and modifying a lot of config files if you can. Hence my recommendation for any MX510 users to use the simple method. I'm going to do some more research and see if the other more advanced Logitech mice can be made to work within xorg.conf too.
I know, I'm talking about mice like the Logitech MX1000 and Microsoft Intellimouse Explorer 4.0 (Wireless version is 2.0, I believe). They have tilt wheels, which won't work unless you use evdev. BTW, that's not exactly a Firefox problem, it's the driver, it's sending extra button signals, which it shouldn't. Both Firefox and Opera accept button signals higher than 7 as button 1 while the rest of the applications ignore higher numbers.

Currently, the evdev driver in Dapper is somewhat messed up, that's why it takes so many steps, like in my guide. Ideally, all it should take is editing xorg.conf, and if you want back/forward working in Nautilus, Konqueror, Epiphany, etc. you would also use xbindkeys, same as you would with your configuration.

detyabozhye
June 6th, 2006, 08:43 PM
i have x700 and i'm using aiglx and compiz the method described on the first page doesn't work for me. Does anyone know where i can find info on this?

Ie. i can't start x with new settings in xorg.conf
This guide won't work in Ubuntu 6.06, use this one: http://ubuntuforums.org/showthread.php?t=188302
Or if you want am easier method, and don't mind one button acting a little weird, use Gtaylor's method.

px79
June 13th, 2006, 04:06 PM
Thanks for this great tutorial!

I am another Laptop user struggling with a Synaptics touchpad and a Logitech MX510 USB mouse. Up to now I discovered the following facts:

1. If you have your mouse NOT plugged in and start X it might crash, if your mouse is set as "CorePointer". A better way is to set the MX510 to "SendCoreEvents" and make the touchpad the "CorePointer", since this will always be "plugged in".

2. If you make your MX510 "SendCoreEvents", xmodmap won't be abel to rearrange the mouse buttons. Since xmodmap affects ONLY the "CorePointer". But you can use xinput (I guess you have to download it first). In my case the following line does the job:

xinput set-button-map MX510 1 2 3 6 7 8 4 5
"MX510" is the device name as defined in xorg.conf:

Section "ServerLayout"
[...]
InputDevice "TouchPad" "CorePointer"
InputDevice "MX510" "SendCoreEvents"
EndSection

Section "InputDevice"
Identifier "TouchPad"
Driver "synaptics"
Option "Device" "/dev/input/mice"
Option "Protocol" "auto-dev"
Option "LeftEdge" "1700"
Option "RightEdge" "5300"
Option "TopEdge" "1700"
Option "BottomEdge" "4200"
Option "FingerLow" "25"
Option "FingerHigh" "30"
Option "MaxTapTime" "180"
Option "MaxTapMove" "220"
Option "VertScrollDelta" "100"
Option "MinSpeed" "0.09"
Option "MaxSpeed" "0.25"
Option "AccelFactor" "0.0015"
Option "SHMConfig" "on"
EndSection

Section "InputDevice"
Identifier "MX510"
Driver "mouse"
Option "Protocol" "evdev"
Option "Dev Name" "Logitech USB-PS/2 Optical Mouse"
Option "Dev Phys" "usb-*/input0"
Option "Device" "/dev/input/mice"
Option "Buttons" "8"
Option "ZAxisMapping" "7 8" # scroll wheel events
EndSection

3. What I didn't manage up to now: To enable full hotplug support. Which means, the MX510 will be recognized and enabled everytime I plug it in. But according to this information I guess it is not possible at the moment:

Currently (as of release 6.7), the XOrg server does not support any form of hotplug for input devices. The server knows about those devices that were present and configured at the time it was started, but it is not possible to add or remove devices during the lifetime of the server.http://wiki.x.org/wiki/XInputHotplug#head-ee046c3b0e1c1c1a9568779cc6a10159f2b7f063

There is a "hack" especially for this problem, but I didn't get it working: You may want to google for "X11_USBMICE_HACK".

4. What I discovered: If you start the X server with your mouse plugged in, you can remove it and plug it back in another USB port: You only have to switch away from the X server (e.g. ALT + CTRL + F1) and back to the X server (ALT + F7). But if you started X with your mouse unplugged I haven't found a way to tell X that the mouse is there now. :-(

5. If you do not need the cruise control buttons, there IS a way to "enable full hotplug support". Since the touchpad will always be plugged in, X will always be aware of this device. So all you have to do is use the same "data stream" for your touchpad and your mouse:
In your xorg.conf set Option "Device" to "/dev/input/mice" and Option "Protocol" to "auto" for both devices (maybe the last part may be skipped for the touchpad).
If you have set the settings that way, you can plug your MX510 in whenever you want and it will work (at least on my laptop). But since you no longer use the "evdev" protocol your cruise-control-up-button will send a false back-button-event additionally.

That's what I know by now. If someone has any additional information, I would be happy to take note of those. :)

Poka64
June 24th, 2006, 09:09 PM
I followed the guide on the first page and I can't get this working, getting some io104 errror when I try to startx :(

this is my configs/cat on device etc..


I: Bus=0003 Vendor=046d Product=c01d Version=2100
N: Name="Logitech USB-PS/2 Optical Mouse"
P: Phys=usb-0000:00:13.1-1/input0
S: Sysfs=/class/input/input1
H: Handlers=mouse0 ts0 event1
B: EV=7
B: KEY=ff0000 0 0 0 0 0 0 0 0
B: REL=103


My xorg.


Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "Protocol" "evdev"
Option "Dev Name" "Logitech USB-PS/2 Optical Mouse"
Option "Dev Phys" "usb-*/input0"
Option "Device" "/dev/input/event1"
Option "Buttons" "10"
Option "ZAxisMapping" "4 5"
EndSection

Anything that I can do to solve this ? :neutral:

Edit: Found the solution for Dapper: http://www.ubuntuforums.org/showthread.php?t=188302

sinaen
July 4th, 2006, 07:53 AM
Hello here. for about a second I thougt I was about to get crazy. you just babbled about buttons...
as john crichton says... "I don't care about the buttons" its a later problem.
finally at page 33 I saw that some others also had the same inclination to the same problem as I had had.;)

What I discoverd with my laptop is that you cannot uncomment the standard mouse. "Configured Mouse" and I tried to set my logitech lx700 on an independent identifier. as you all know you should have wacom support (anyway I have it and i may have had it installed before and forgotten about it) in your files too. :-s
And that doesn't screw up your X so why not I thought, if that can be there. And you don't have any wacom but have the support. Why cannot it be another identifier? :rolleyes: (that sounded something like yoda might have reasoned out 8-[ )

Said and done it worked like a charm. now I have 8 buttons.
But I currently only use the scroll-wheel (buttons is a later problem) maybe ill install Counter-strike again.. it was a long time ago I had a mouse to play with.

This is my code. You should all be xorg.conf gurus by now. so you should manage it pretty easily.



Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
EndSection

Section "InputDevice"
Identifier "logitech"
Driver "mouse"
Option "Protocol" "evdev"
Option "Dev Name" "Logitech USB-PS/2 Optical Mouse"
Option "Dev Phys" "usb-0000:00:1d.0-2/input0"
Option "Device" "/dev/input/event2"
Option "Buttons" "8"
Option "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
Identifier "Synaptics Touchpad"
Driver "synaptics"
Option "SendCoreEvents" "true"
Option "Device" "/dev/psaux"
Option "Protocol" "auto-dev"
Option "HorizScrollDelta" "0"
EndSection


second code:

Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
InputDevice "stylus" "SendCoreEvents"
InputDevice "cursor" "SendCoreEvents"
InputDevice "eraser" "SendCoreEvents"
InputDevice "Synaptics Touchpad"
InputDevice "logitech"
EndSection


So when I set up this and rebooted. (yes that was neccesary and I don't know why.) it worked and it scrolled :p \\:D/

Znero
July 6th, 2006, 09:53 PM
Hello.
I now have an MX 518 Mouse. After i Started with it, it worked great, and i was able to use the Side buttons to go trough Sites in Firefox. But i didnt work in Nautilus. Now i followed the Tutorial, and the Buttons now even dont work in Firefox.

Heres my xorg.conf:


Section "InputDevice"
Identifier "Configured Mouse"
Driver "evdev"
Option "CorePointer"
Option "Device" "/dev/input/event2"
Option "Name" "Logitech USB-PS/2 Optical Mouse"
Option "Protocol" "evdev"
Option "ZAxisMapping" "4 5"
Option "Buttons" "10"
Option "Resolution" "1600"
Option "Dev Phys" "usb-0000:00:03.0-1/input0"
EndSection

I didnt edit the xmodmap File, because it was said it is not necessary.

My xbindkeysrc is

"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[left]""
m:0x0 + b:6
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[right]""
m:0x0 + b:7
but with Capitols at Left/Right.

I didnt install the Logitech Applet, because it seems to only affect the DPI, not the Keys. And it also looks a bit out of date... (last changed 1 jear 9 months ago)

Can someone help me?

detyabozhye
July 6th, 2006, 10:34 PM
1) This tutorial was meant for Breezy, see my signiture for Dapper.

2) Logitech Applet still works even though it's not the newest thing around. (Yes, it's only used for the DPI here)

3) Use xev to find out which button numbers are fired when you press buttons . (Talked about in the tut)

4) The new xvkbd packages have a different path for xvkbd, please see my sig for details.

Jorenko
July 8th, 2006, 09:50 PM
This actually worked for me in Dapper with my MX700 with no additional packages installed; I just had to switch from Driver "mouse" and Option "Protocol" "evdev" to Driver "evdev":


Section "InputDevice"
Identifier "Configured Mouse"
Driver "evdev"
Option "CorePointer"
Option "Dev Name" "Logitech USB Receiver"
Option "Dev Phys" "usb-*/input0"
Option "Device" "/dev/input/event1"
Option "Buttons" "8"
Option "ZAxisMapping" "4 5"
EndSection

Thanks, guys!

ensiferum
July 14th, 2006, 08:31 PM
I have mx500.

I found its very simple to get all buttons working using imwheel.

xorg.conf:

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "Buttons" "7"
Option "ZAxisMapping" "4 5"
EndSection

start imwheel with
"imwheel -b "0089"

and its all set.

and yeah in imwheel.rc i only have

".*"
None,Up,Alt_L|Left
None,Down,Alt_L|Right

and thats that.

mandark
July 15th, 2006, 08:52 AM
I have an old logitech mouse attached to a serial port<not usb or ps/2> on my comp.....it works fine with windows98/xp ,but isnt getting detected in ubuntu...ie i cant move the pointer around!!......is there anywhere i can find the drivers for the mouse..or is it just plain incompatible??

nickless
July 15th, 2006, 01:53 PM
Error opening /dev/wacon : No such file or directory
(EE) xf86OpenSerial: Cannot open device /dev/wacom
No such file or directory
Error opening /dev/wacon : No such file or directory
No core pointer
I am pretty shure, that I've done everything right. Here's my xorg.conf:

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "Protocol" "evdev"
Option "Dev Name" "Logitech USB-PS/2 Optical Mouse"
Option "Dev Phys" "usb-*/input0"
Option "Device" "/dev/input/event2"
Option "Buttons" "8"
Option "ZAxisMapping" "4 5"
EndSection

#Section "InputDevice"
# Identifier "Configured Mouse"
# Driver "mouse"
# Option "CorePointer"
# Option "Device" "/dev/input/mice"
# Option "Protocol" "ExplorerPS/2"
# Option "ZAxisMapping" "4 5"
# Option "Emulate3Buttons" "true"
#EndSection

Section "InputDevice"

# /dev/input/event
# for USB
Identifier "stylus"
Driver "wacom"
Option "Device" "/dev/wacom" # Change to
Option "Type" "stylus"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "InputDevice"

# /dev/input/event
# for USB
Identifier "eraser"
Driver "wacom"
Option "Device" "/dev/wacom" # Change to
Option "Type" "eraser"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "InputDevice"

# /dev/input/event
# for USB
Identifier "cursor"
Driver "wacom"
Option "Device" "/dev/wacom" # Change to
Option "Type" "cursor"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection
But I am not shure what those wacom-devices are. I use no fancy stuff, just keyboard and mouse :D When I comment them out, it can't find my monitor... funny, hum? Confirmed "Dev Name", "Dev Phys" and "Device" everything like cat said

mect
July 19th, 2006, 06:36 AM
So I've tried lots of things to get my logitech mediaplay mouse working, including the driver by David Oliveira, with no luck. I then tried following the steps introduced in this thread, but couldn't ever get xserver to work. Finally, I found something that I will be content with for now as it appears that I have most of the buttons working. Volume works, as do the play next and previous buttons. While I can't get them to do anything yet, the back forward buttons give a button number in xev, so hopefully I can get those working. All I did was assign a multimedia keyboard layout under regional settings. Maybe someone has posted this before, but I've never seen it and thought I'd share just incase this is useful to someone else. For me personally, the BTC 5090 works quite well for both my keyboard (generic multimedia) and my mouse. Anyways, if you can't get anything else to work, you can try this.

StackError
July 31st, 2006, 07:05 PM
Hello:

the url for the logitech_applet is 404! :<
i googled it but all links lead back to frogmouth.net

Ne one have a live link????

Thx

S

Malta Soron
August 9th, 2006, 05:00 PM
I've got an MX518. I got the side buttons working in Firefox, but I wasn't succesfull in Nautilus. Although xev indicated that I should use button 6 and 7, it didn't work, so after trying for 45 minutes (and reconfiguring X.org like 7 times) I left it out.
There is a problem with the logitech applet:


jos@jos:~$ wget http://freshmeat.net/redir/logitech_applet/53319/url_tgz/logitech_applet-0.4test1.tar.gz
--17:54:58-- http://freshmeat.net/redir/logitech_applet/53319/url_tgz/logitech_applet-0.4test1.tar.gz
=> `logitech_applet-0.4test1.tar.gz'
Resolving freshmeat.net... 66.35.250.168
Connecting to freshmeat.net|66.35.250.168|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://www.frogmouth.net/logitech_applet-0.4test1.tar.gz [following]
--17:54:59-- http://www.frogmouth.net/logitech_applet-0.4test1.tar.gz
=> `logitech_applet-0.4test1.tar.gz'
Resolving www.frogmouth.net... 125.62.93.225
Connecting to www.frogmouth.net|125.62.93.225|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
17:55:00 ERROR 404: Not Found.

spacepirates
August 12th, 2006, 11:43 PM
I've got a mx310 (mx 310) and cannot get it to work. i've been working on this for three days now, and am to the point where i am randomly assigning numbers hoping it might work.

the buttons have changed numbers now (scroll up/down was 4/5, now the side buttons scroll and are 4/5)

xev gives me no button number for (originally) the side buttons (now it gives no numbers for the scroll wheel)

i fear i have ruined the mouse configuration beyond repair...


#normal mouse settings
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
EndSection

#logitech - side buttons for mouse
#Section "InputDevice"
# Identifier "Configured Mouse"
# Driver "mouse"
# Option "Protocol" "evdev"
# Option "Dev Name" "Logitech USB-PS/2 Optical Mouse"
# Option "Dev Phys" "usb-0000:00:02.0-6/input0"
# Option "Device" "/dev/input/event2"
# Option "Buttons" "8"
# Option "ZAxisMapping" "4 5"
#EndSection

is my xorg.conf for the moment (the logitech mouse settings are off of ticklemonster's), everytime i try to alter the file X crashes on reboot.

can someone please help me (a) restore the orignal mouse settings and then (b) get these side buttons to work and then maybe (c) figure out the code to have them switch workspaces?

thanks in advance!

dids22
August 22nd, 2006, 03:32 PM
hey
i didnt read the all thread.
i got a problem, after i edited xorg file and restart xserver
i got message that thier is problem with xserver (i dont remmber its exactly)
i give you detail for what i did

first this is the output of cat /proc/bus/input/devices

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=4 2000000 3802078 f840d001 f2ffffdf ffefffff ffffffff fffffffe
B: MSC=10
B: LED=7

I: Bus=0003 Vendor=046d Product=c025 Version=1800
N: Name="Logitech USB-PS/2 Optical Mouse"
P: Phys=usb-0000:00:02.0-4/input0
S: Sysfs=/class/input/input1
H: Handlers=mouse0 event1 ts0
B: EV=7
B: KEY=ff0000 0 0 0 0 0 0 0 0
B: REL=103

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



and the output of xorg after i edited him

# /etc/X11/xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the /etc/X11/xorg.conf manual page.
# (Type "man /etc/X11/xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section "Files"
FontPath "/usr/share/X11/fonts/misc"
FontPath "/usr/share/X11/fonts/cyrillic"
FontPath "/usr/share/X11/fonts/100dpi/:unscaled"
FontPath "/usr/share/X11/fonts/75dpi/:unscaled"
FontPath "/usr/share/X11/fonts/Type1"
FontPath "/usr/share/X11/fonts/100dpi"
FontPath "/usr/share/X11/fonts/75dpi"
# path to defoma fonts
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
EndSection

Section "Module"
Load "bitmap"
Load "ddc"
Load "dri"
Load "extmod"
Load "freetype"
Load "glx"
Load "int10"
Load "type1"
Load "vbe"
EndSection

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc104"
Option "XkbLayout" "us"
EndSection

#Section "InputDevice"
# Identifier "Configured Mouse"
# Driver "mouse"
# Option "CorePointer"
# Option "Device" "/dev/input/mice"
# Option "Protocol" "ExplorerPS/2"
# Option "ZAxisMapping" "4 5"
# Option "Emulate3Buttons" "true"
#EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "Protocol" "evdev"
Option "Dev Name" "Logitech USB-PS/2 Optical Mouse"
Option "Dev Phys" "usb-0000:00:02.0-4/input0"
Option "Device" "/dev/input/event1"
Option "Buttons" "10"
Option "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "stylus"
Option "Device" "/dev/wacom" # Change to
# /dev/input/event
# for USB
Option "Type" "stylus"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "eraser"
Option "Device" "/dev/wacom" # Change to
# /dev/input/event
# for USB
Option "Type" "eraser"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "cursor"
Option "Device" "/dev/wacom" # Change to
# /dev/input/event
# for USB
Option "Type" "cursor"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "Device"
Identifier "NVIDIA Corporation NV43 [GeForce 6600/GeForce 6600 GT]"
Driver "nvidia"
BusID "PCI:1:0:0"
EndSection

Section "Monitor"
Identifier "Generic Monitor"
Option "DPMS"
HorizSync 28-51
VertRefresh 43-60
EndSection

Section "Screen"
Identifier "Default Screen"
Device "NVIDIA Corporation NV43 [GeForce 6600/GeForce 6600 GT]"
Monitor "Generic Monitor"
DefaultDepth 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 "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
InputDevice "stylus" "SendCoreEvents"
InputDevice "cursor" "SendCoreEvents"
InputDevice "eraser" "SendCoreEvents"
EndSection

Section "DRI"
Mode 0666
EndSection

dids22
August 22nd, 2006, 03:33 PM
i do all right?
ho i forget- my mouse is mx500

and now for the last output (xorg.0.log)


X Window System Version 7.0.0
Release Date: 21 December 2005
X Protocol Version 11, Revision 0, Release 7.0
Build Operating System:Linux 2.6.12 i686
Current Operating System: Linux chch-desktop 2.6.15-25-386 #1 PREEMPT Wed Jun 14 11:25:49 UTC 2006 i686
Build Date: 16 March 2006
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Aug 22 15:00:20 2006
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Default Layout"
(**) |-->Screen "Default Screen" (0)
(**) | |-->Monitor "Generic Monitor"
(**) | |-->Device "NVIDIA Corporation NV43 [GeForce 6600/GeForce 6600 GT]"
(**) |-->Input Device "Generic Keyboard"
(**) |-->Input Device "Configured Mouse"
(**) |-->Input Device "stylus"
(**) |-->Input Device "cursor"
(**) |-->Input Device "eraser"
(==) |-->Input Device "Configured Mouse"
(WW) The core pointer device wasn't specified explicitly in the layout.
Using the first mouse device.
(WW) The directory "/usr/share/X11/fonts/cyrillic" does not exist.
Entry deleted from font path.
(**) FontPath set to "/usr/share/X11/fonts/misc,/usr/share/X11/fonts/100dpi/:unscaled,/usr/share/X11/fonts/75dpi/:unscaled,/usr/share/X11/fonts/Type1,/usr/share/X11/fonts/100dpi,/usr/share/X11/fonts/75dpi,/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
(==) RgbPath set to "/etc/X11/rgb"
(==) ModulePath set to "/usr/lib/xorg/modules"
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.2
X.Org Video Driver: 0.8
X.Org XInput driver : 0.5
X.Org Server Extension : 0.2
X.Org Font Renderer : 0.4
(II) Loader running on linux
(II) LoadModule: "bitmap"
(II) Loading /usr/lib/xorg/modules/fonts/libbitmap.so
(II) Module bitmap: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 1.0.0
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.4
(II) Loading font Bitmap
(II) LoadModule: "pcidata"
(II) Loading /usr/lib/xorg/modules/libpcidata.so
(II) Module pcidata: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 1.0.0
ABI class: X.Org Video Driver, version 0.8
(++) using VT number 7

(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 10de,00e1 card 0000,0000 rev a1 class 06,00,00 hdr 00
(II) PCI: 00:01:0: chip 10de,00e0 card 1458,0c11 rev a2 class 06,01,00 hdr 80
(II) PCI: 00:01:1: chip 10de,00e4 card 1458,0c11 rev a1 class 0c,05,00 hdr 80
(II) PCI: 00:02:0: chip 10de,00e7 card 1458,5004 rev a1 class 0c,03,10 hdr 80
(II) PCI: 00:02:1: chip 10de,00e7 card 1458,5004 rev a1 class 0c,03,10 hdr 80
(II) PCI: 00:02:2: chip 10de,00e8 card 1458,5004 rev a2 class 0c,03,20 hdr 80
(II) PCI: 00:05:0: chip 10de,00df card 1458,e000 rev a2 class 06,80,00 hdr 00
(II) PCI: 00:06:0: chip 10de,00ea card 1458,a002 rev a1 class 04,01,00 hdr 00
(II) PCI: 00:08:0: chip 10de,00e5 card 1458,5002 rev a2 class 01,01,8a hdr 00
(II) PCI: 00:0a:0: chip 10de,00e3 card 1458,b002 rev a2 class 01,01,85 hdr 00
(II) PCI: 00:0b:0: chip 10de,00e2 card 0000,0000 rev a2 class 06,04,00 hdr 01
(II) PCI: 00:0e:0: chip 10de,00ed card 0000,0000 rev a2 class 06,04,00 hdr 01
(II) PCI: 00:18:0: chip 1022,1100 card 0000,0000 rev 00 class 06,00,00 hdr 80
(II) PCI: 00:18:1: chip 1022,1101 card 0000,0000 rev 00 class 06,00,00 hdr 80
(II) PCI: 00:18:2: chip 1022,1102 card 0000,0000 rev 00 class 06,00,00 hdr 80
(II) PCI: 00:18:3: chip 1022,1103 card 0000,0000 rev 00 class 06,00,00 hdr 80
(II) PCI: 01:00:0: chip 10de,00f1 card 1682,2119 rev a2 class 03,00,00 hdr 00
(II) PCI: 02:0b:0: chip 11ab,4320 card 1458,e000 rev 13 class 02,00,00 hdr 00
(II) PCI: 02:0d:0: chip 1095,3512 card 1095,6512 rev 01 class 01,04,00 hdr 00
(II) PCI: 02:0e:0: chip 104c,8025 card 1458,1000 rev 01 class 0c,00,10 hdr 00
(II) PCI: End of PCI scan
(II) Host-to-PCI bridge:
(II) Bus 0: bridge is at (0:0:0), (0,0,2), BCTRL: 0x0008 (VGA_EN is set)
(II) Bus 0 I/O range:
[0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) Bus 0 non-prefetchable memory range:
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B]
(II) Bus 0 prefetchable memory range:
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B]
(II) PCI-to-ISA bridge:
(II) Bus -1: bridge is at (0:1:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set)
(II) PCI-to-PCI bridge:
(II) Bus 1: bridge is at (0:11:0), (0,1,1), BCTRL: 0x000c (VGA_EN is set)
(II) Bus 1 non-prefetchable memory range:
[0] -1 0 0xf8000000 - 0xfaffffff (0x3000000) MX[B]
(II) Bus 1 prefetchable memory range:
[0] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B]
(II) PCI-to-PCI bridge:
(II) Bus 2: bridge is at (0:14:0), (0,2,2), BCTRL: 0x0004 (VGA_EN is cleared)
(II) Bus 2 I/O range:
[0] -1 0 0x00009000 - 0x000090ff (0x100) IX[B]
[1] -1 0 0x00009400 - 0x000094ff (0x100) IX[B]
[2] -1 0 0x00009800 - 0x000098ff (0x100) IX[B]
[3] -1 0 0x00009c00 - 0x00009cff (0x100) IX[B]
[4] -1 0 0x0000a000 - 0x0000a0ff (0x100) IX[B]
[5] -1 0 0x0000a400 - 0x0000a4ff (0x100) IX[B]
[6] -1 0 0x0000a800 - 0x0000a8ff (0x100) IX[B]
[7] -1 0 0x0000ac00 - 0x0000acff (0x100) IX[B]
(II) Bus 2 non-prefetchable memory range:
[0] -1 0 0xfb000000 - 0xfcffffff (0x2000000) MX[B]
(II) Bus 2 prefetchable memory range:
[0] -1 0 0x50000000 - 0x500fffff (0x100000) MX[B]
(--) PCI:*(1:0:0) nVidia Corporation NV43 [GeForce 6600/GeForce 6600 GT] rev 162, Mem @ 0xf8000000/24, 0xe0000000/28, 0xf9000000/24
(II) Addressable bus resource ranges are
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B]
[1] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) OS-reported resource ranges:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[5] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
(II) PCI Memory resource overlap reduced 0xf0000000 from 0xf7ffffff to 0xefffffff
(II) Active PCI resource ranges:
[0] -1 0 0xfc004000 - 0xfc007fff (0x4000) MX[B]
[1] -1 0 0xfc008000 - 0xfc0087ff (0x800) MX[B]
[2] -1 0 0xfc009000 - 0xfc0091ff (0x200) MX[B]
[3] -1 0 0xfc000000 - 0xfc003fff (0x4000) MX[B]
[4] -1 0 0xfd001000 - 0xfd001fff (0x1000) MX[B]
[5] -1 0 0xfd000000 - 0xfd000fff (0x1000) MX[B]
[6] -1 0 0xfd005000 - 0xfd0050ff (0x100) MX[B]
[7] -1 0 0xfd004000 - 0xfd004fff (0x1000) MX[B]
[8] -1 0 0xfd003000 - 0xfd003fff (0x1000) MX[B]
[9] -1 0 0xf0000000 - 0xefffffff (0x0) MX[B]O
[10] -1 0 0xf9000000 - 0xf9ffffff (0x1000000) MX[B](B)
[11] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B)
[12] -1 0 0xf8000000 - 0xf8ffffff (0x1000000) MX[B](B)
[13] -1 0 0x0000a400 - 0x0000a40f (0x10) IX[B]
[14] -1 0 0x0000a000 - 0x0000a003 (0x4) IX[B]
[15] -1 0 0x00009c00 - 0x00009c07 (0x8) IX[B]
[16] -1 0 0x00009800 - 0x00009803 (0x4) IX[B]
[17] -1 0 0x00009400 - 0x00009407 (0x8) IX[B]
[18] -1 0 0x00009000 - 0x000090ff (0x100) IX[B]
[19] -1 0 0x0000e000 - 0x0000e07f (0x80) IX[B]
[20] -1 0 0x0000dc00 - 0x0000dc0f (0x10) IX[B]
[21] -1 0 0x00000b70 - 0x00000b73 (0x4) IX[B]
[22] -1 0 0x00000970 - 0x00000977 (0x8) IX[B]
[23] -1 0 0x00000bf0 - 0x00000bf3 (0x4) IX[B]
[24] -1 0 0x000009f0 - 0x000009f7 (0x8) IX[B]
[25] -1 0 0x0000f000 - 0x0000f00f (0x10) IX[B]
[26] -1 0 0x0000c000 - 0x0000c07f (0x80) IX[B]
[27] -1 0 0x0000bc00 - 0x0000bcff (0x100) IX[B]
[28] -1 0 0x0000b800 - 0x0000b807 (0x8) IX[B]
[29] -1 0 0x00002000 - 0x0000203f (0x40) IX[B]
[30] -1 0 0x00001c00 - 0x00001c3f (0x40) IX[B]
[31] -1 0 0x0000e400 - 0x0000e41f (0x20) IX[B]
(II) Active PCI resource ranges after removing overlaps:
[0] -1 0 0xfc004000 - 0xfc007fff (0x4000) MX[B]
[1] -1 0 0xfc008000 - 0xfc0087ff (0x800) MX[B]
[2] -1 0 0xfc009000 - 0xfc0091ff (0x200) MX[B]
[3] -1 0 0xfc000000 - 0xfc003fff (0x4000) MX[B]
[4] -1 0 0xfd001000 - 0xfd001fff (0x1000) MX[B]
[5] -1 0 0xfd000000 - 0xfd000fff (0x1000) MX[B]
[6] -1 0 0xfd005000 - 0xfd0050ff (0x100) MX[B]
[7] -1 0 0xfd004000 - 0xfd004fff (0x1000) MX[B]
[8] -1 0 0xfd003000 - 0xfd003fff (0x1000) MX[B]
[9] -1 0 0xf0000000 - 0xefffffff (0x0) MX[B]O
[10] -1 0 0xf9000000 - 0xf9ffffff (0x1000000) MX[B](B)
[11] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B)
[12] -1 0 0xf8000000 - 0xf8ffffff (0x1000000) MX[B](B)
[13] -1 0 0x0000a400 - 0x0000a40f (0x10) IX[B]
[14] -1 0 0x0000a000 - 0x0000a003 (0x4) IX[B]
[15] -1 0 0x00009c00 - 0x00009c07 (0x8) IX[B]
[16] -1 0 0x00009800 - 0x00009803 (0x4) IX[B]
[17] -1 0 0x00009400 - 0x00009407 (0x8) IX[B]
[18] -1 0 0x00009000 - 0x000090ff (0x100) IX[B]
[19] -1 0 0x0000e000 - 0x0000e07f (0x80) IX[B]
[20] -1 0 0x0000dc00 - 0x0000dc0f (0x10) IX[B]
[21] -1 0 0x00000b70 - 0x00000b73 (0x4) IX[B]
[22] -1 0 0x00000970 - 0x00000977 (0x8) IX[B]
[23] -1 0 0x00000bf0 - 0x00000bf3 (0x4) IX[B]
[24] -1 0 0x000009f0 - 0x000009f7 (0x8) IX[B]
[25] -1 0 0x0000f000 - 0x0000f00f (0x10) IX[B]
[26] -1 0 0x0000c000 - 0x0000c07f (0x80) IX[B]
[27] -1 0 0x0000bc00 - 0x0000bcff (0x100) IX[B]
[28] -1 0 0x0000b800 - 0x0000b807 (0x8) IX[B]
[29] -1 0 0x00002000 - 0x0000203f (0x40) IX[B]
[30] -1 0 0x00001c00 - 0x00001c3f (0x40) IX[B]
[31] -1 0 0x0000e400 - 0x0000e41f (0x20) IX[B]
(II) OS-reported resource ranges after removing overlaps with PCI:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[5] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
(II) All system resource ranges:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0xfc004000 - 0xfc007fff (0x4000) MX[B]
[5] -1 0 0xfc008000 - 0xfc0087ff (0x800) MX[B]
[6] -1 0 0xfc009000 - 0xfc0091ff (0x200) MX[B]
[7] -1 0 0xfc000000 - 0xfc003fff (0x4000) MX[B]
[8] -1 0 0xfd001000 - 0xfd001fff (0x1000) MX[B]
[9] -1 0 0xfd000000 - 0xfd000fff (0x1000) MX[B]
[10] -1 0 0xfd005000 - 0xfd0050ff (0x100) MX[B]
[11] -1 0 0xfd004000 - 0xfd004fff (0x1000) MX[B]
[12] -1 0 0xfd003000 - 0xfd003fff (0x1000) MX[B]
[13] -1 0 0xf0000000 - 0xefffffff (0x0) MX[B]O
[14] -1 0 0xf9000000 - 0xf9ffffff (0x1000000) MX[B](B)
[15] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B)
[16] -1 0 0xf8000000 - 0xf8ffffff (0x1000000) MX[B](B)
[17] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[18] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[19] -1 0 0x0000a400 - 0x0000a40f (0x10) IX[B]
[20] -1 0 0x0000a000 - 0x0000a003 (0x4) IX[B]
[21] -1 0 0x00009c00 - 0x00009c07 (0x8) IX[B]
[22] -1 0 0x00009800 - 0x00009803 (0x4) IX[B]
[23] -1 0 0x00009400 - 0x00009407 (0x8) IX[B]
[24] -1 0 0x00009000 - 0x000090ff (0x100) IX[B]
[25] -1 0 0x0000e000 - 0x0000e07f (0x80) IX[B]
[26] -1 0 0x0000dc00 - 0x0000dc0f (0x10) IX[B]
[27] -1 0 0x00000b70 - 0x00000b73 (0x4) IX[B]
[28] -1 0 0x00000970 - 0x00000977 (0x8) IX[B]
[29] -1 0 0x00000bf0 - 0x00000bf3 (0x4) IX[B]
[30] -1 0 0x000009f0 - 0x000009f7 (0x8) IX[B]
[31] -1 0 0x0000f000 - 0x0000f00f (0x10) IX[B]
[32] -1 0 0x0000c000 - 0x0000c07f (0x80) IX[B]
[33] -1 0 0x0000bc00 - 0x0000bcff (0x100) IX[B]
[34] -1 0 0x0000b800 - 0x0000b807 (0x8) IX[B]
[35] -1 0 0x00002000 - 0x0000203f (0x40) IX[B]
[36] -1 0 0x00001c00 - 0x00001c3f (0x40) IX[B]
[37] -1 0 0x0000e400 - 0x0000e41f (0x20) IX[B]
(II) LoadModule: "bitmap"
(II) Reloading /usr/lib/xorg/modules/fonts/libbitmap.so
(II) Loading font Bitmap
(II) LoadModule: "ddc"
(II) Loading /usr/lib/xorg/modules/libddc.so
(II) Module ddc: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 1.0.0
ABI class: X.Org Video Driver, version 0.8
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions/libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.2
(II) Loading sub module "drm"
(II) LoadModule: "drm"
(II) Loading /usr/lib/xorg/modules/linux/libdrm.so
(II) Module drm: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.2
(II) Loading extension XFree86-DRI
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.2
(II) Loading extension SHAPE
(II) Loading extension MIT-SUNDRY-NONSTANDARD
(II) Loading extension BIG-REQUESTS
(II) Loading extension SYNC
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XC-MISC
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-Misc
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension TOG-CUP
(II) Loading extension Extended-Visual-Information
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "freetype"
(II) Loading /usr/lib/xorg/modules/fonts/libfreetype.so
(II) Module freetype: vendor="X.Org Foundation & the After X-TT Project"
compiled for 7.0.0, module version = 2.1.0
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.4
(II) Loading font FreeType
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/libglx.so
(II) Module glx: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.8762
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.1
(II) Loading extension GLX
(II) LoadModule: "int10"
(II) Loading /usr/lib/xorg/modules/libint10.so
(II) Module int10: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 1.0.0
ABI class: X.Org Video Driver, version 0.8
(II) LoadModule: "type1"
(II) Loading /usr/lib/xorg/modules/fonts/libtype1.so
(II) Module type1: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 1.0.2
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.4
(II) Loading font Type1
(II) LoadModule: "vbe"
(II) Loading /usr/lib/xorg/modules/libvbe.so
(II) Module vbe: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 1.1.0
ABI class: X.Org Video Driver, version 0.8
(II) LoadModule: "nvidia"
(II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.o
(II) Module nvidia: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.8762
Module class: X.Org Video Driver
(II) LoadModule: "kbd"
(II) Loading /usr/lib/xorg/modules/input/kbd_drv.so
(II) Module kbd: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 1.0.1
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 0.5
(II) LoadModule: "mouse"
(II) Loading /usr/lib/xorg/modules/input/mouse_drv.so
(II) Module mouse: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 1.0.3
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 0.5
(II) LoadModule: "wacom"
(II) Loading /usr/lib/xorg/modules/input/wacom_drv.so
(II) Module wacom: vendor="X.Org Foundation"
compiled for 4.3.99.902, module version = 1.0.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 0.5
(II) Wacom driver level: 47-0.7.2 $
(II) NVIDIA X Driver 1.0-8762 Mon May 15 13:09:21 PDT 2006
(II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
(II) Primary Device is: PCI 01:00:0
(--) Chipset NVIDIA GPU found
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules/libfb.so
(II) Module fb: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.2
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Loading /usr/lib/xorg/modules/libramdac.so
(II) Module ramdac: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 0.1.0
ABI class: X.Org Video Driver, version 0.8
(II) resource ranges after xf86ClaimFixedResources() call:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0xfc004000 - 0xfc007fff (0x4000) MX[B]
[5] -1 0 0xfc008000 - 0xfc0087ff (0x800) MX[B]
[6] -1 0 0xfc009000 - 0xfc0091ff (0x200) MX[B]
[7] -1 0 0xfc000000 - 0xfc003fff (0x4000) MX[B]
[8] -1 0 0xfd001000 - 0xfd001fff (0x1000) MX[B]
[9] -1 0 0xfd000000 - 0xfd000fff (0x1000) MX[B]
[10] -1 0 0xfd005000 - 0xfd0050ff (0x100) MX[B]
[11] -1 0 0xfd004000 - 0xfd004fff (0x1000) MX[B]
[12] -1 0 0xfd003000 - 0xfd003fff (0x1000) MX[B]
[13] -1 0 0xf0000000 - 0xefffffff (0x0) MX[B]O
[14] -1 0 0xf9000000 - 0xf9ffffff (0x1000000) MX[B](B)
[15] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B)
[16] -1 0 0xf8000000 - 0xf8ffffff (0x1000000) MX[B](B)
[17] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[18] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[19] -1 0 0x0000a400 - 0x0000a40f (0x10) IX[B]
[20] -1 0 0x0000a000 - 0x0000a003 (0x4) IX[B]
[21] -1 0 0x00009c00 - 0x00009c07 (0x8) IX[B]
[22] -1 0 0x00009800 - 0x00009803 (0x4) IX[B]
[23] -1 0 0x00009400 - 0x00009407 (0x8) IX[B]
[24] -1 0 0x00009000 - 0x000090ff (0x100) IX[B]
[25] -1 0 0x0000e000 - 0x0000e07f (0x80) IX[B]
[26] -1 0 0x0000dc00 - 0x0000dc0f (0x10) IX[B]
[27] -1 0 0x00000b70 - 0x00000b73 (0x4) IX[B]
[28] -1 0 0x00000970 - 0x00000977 (0x8) IX[B]
[29] -1 0 0x00000bf0 - 0x00000bf3 (0x4) IX[B]
[30] -1 0 0x000009f0 - 0x000009f7 (0x8) IX[B]
[31] -1 0 0x0000f000 - 0x0000f00f (0x10) IX[B]
[32] -1 0 0x0000c000 - 0x0000c07f (0x80) IX[B]
[33] -1 0 0x0000bc00 - 0x0000bcff (0x100) IX[B]
[34] -1 0 0x0000b800 - 0x0000b807 (0x8) IX[B]
[35] -1 0 0x00002000 - 0x0000203f (0x40) IX[B]
[36] -1 0 0x00001c00 - 0x00001c3f (0x40) IX[B]
[37] -1 0 0x0000e400 - 0x0000e41f (0x20) IX[B]
(II) resource ranges after probing:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0xfc004000 - 0xfc007fff (0x4000) MX[B]
[5] -1 0 0xfc008000 - 0xfc0087ff (0x800) MX[B]
[6] -1 0 0xfc009000 - 0xfc0091ff (0x200) MX[B]
[7] -1 0 0xfc000000 - 0xfc003fff (0x4000) MX[B]
[8] -1 0 0xfd001000 - 0xfd001fff (0x1000) MX[B]
[9] -1 0 0xfd000000 - 0xfd000fff (0x1000) MX[B]
[10] -1 0 0xfd005000 - 0xfd0050ff (0x100) MX[B]
[11] -1 0 0xfd004000 - 0xfd004fff (0x1000) MX[B]
[12] -1 0 0xfd003000 - 0xfd003fff (0x1000) MX[B]
[13] -1 0 0xf0000000 - 0xefffffff (0x0) MX[B]O
[14] -1 0 0xf9000000 - 0xf9ffffff (0x1000000) MX[B](B)
[15] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B)
[16] -1 0 0xf8000000 - 0xf8ffffff (0x1000000) MX[B](B)
[17] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B]
[18] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B]
[19] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B]
[20] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[21] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[22] -1 0 0x0000a400 - 0x0000a40f (0x10) IX[B]
[23] -1 0 0x0000a000 - 0x0000a003 (0x4) IX[B]
[24] -1 0 0x00009c00 - 0x00009c07 (0x8) IX[B]
[25] -1 0 0x00009800 - 0x00009803 (0x4) IX[B]
[26] -1 0 0x00009400 - 0x00009407 (0x8) IX[B]
[27] -1 0 0x00009000 - 0x000090ff (0x100) IX[B]
[28] -1 0 0x0000e000 - 0x0000e07f (0x80) IX[B]
[29] -1 0 0x0000dc00 - 0x0000dc0f (0x10) IX[B]
[30] -1 0 0x00000b70 - 0x00000b73 (0x4) IX[B]
[31] -1 0 0x00000970 - 0x00000977 (0x8) IX[B]
[32] -1 0 0x00000bf0 - 0x00000bf3 (0x4) IX[B]
[33] -1 0 0x000009f0 - 0x000009f7 (0x8) IX[B]
[34] -1 0 0x0000f000 - 0x0000f00f (0x10) IX[B]
[35] -1 0 0x0000c000 - 0x0000c07f (0x80) IX[B]
[36] -1 0 0x0000bc00 - 0x0000bcff (0x100) IX[B]
[37] -1 0 0x0000b800 - 0x0000b807 (0x8) IX[B]
[38] -1 0 0x00002000 - 0x0000203f (0x40) IX[B]
[39] -1 0 0x00001c00 - 0x00001c3f (0x40) IX[B]
[40] -1 0 0x0000e400 - 0x0000e41f (0x20) IX[B]
[41] 0 0 0xfa0003b0 - 0xfa0003bb (0xc) IS[B]
[42] 0 0 0xfa0003c0 - 0xfa0003df (0x20) IS[B]
(II) Setting vga for screen 0.
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(0): Enabling RENDER acceleration
(II) NVIDIA(0): NVIDIA GPU GeForce 6600 GT at PCI:1:0:0
(--) NVIDIA(0): VideoRAM: 131072 kBytes
(--) NVIDIA(0): VideoBIOS: 05.43.02.57.00
(II) NVIDIA(0): Detected AGP rate: 8X
(--) NVIDIA(0): Interlaced video modes are supported on this GPU
(--) NVIDIA(0): Connected display device(s) on GeForce 6600 GT at PCI:1:0:0:
(--) NVIDIA(0): Samsung SyncMaster (CRT-1)
(--) NVIDIA(0): Samsung SyncMaster (CRT-1): 400.0 MHz maximum pixel clock
(II) NVIDIA(0): Assigned Display Device: CRT-1
(II) NVIDIA(0): Validated modes:
(II) NVIDIA(0): "1024x768"
(II) NVIDIA(0): "800x600"
(II) NVIDIA(0): "640x480"
(II) NVIDIA(0): Virtual screen size determined to be 1024 x 768
(--) NVIDIA(0): DPI set to (83, 84); computed from "UseEdidDpi" X config option
(--) Depth 24 pixmap format is 32 bpp
(II) do I need RAC? No, I don't.
(II) resource ranges after preInit:
[0] 0 0 0xf9000000 - 0xf9ffffff (0x1000000) MX[B]
[1] 0 0 0xe0000000 - 0xefffffff (0x10000000) MX[B]
[2] 0 0 0xf8000000 - 0xf8ffffff (0x1000000) MX[B]
[3] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[4] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[5] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[6] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[7] -1 0 0xfc004000 - 0xfc007fff (0x4000) MX[B]
[8] -1 0 0xfc008000 - 0xfc0087ff (0x800) MX[B]
[9] -1 0 0xfc009000 - 0xfc0091ff (0x200) MX[B]
[10] -1 0 0xfc000000 - 0xfc003fff (0x4000) MX[B]
[11] -1 0 0xfd001000 - 0xfd001fff (0x1000) MX[B]
[12] -1 0 0xfd000000 - 0xfd000fff (0x1000) MX[B]
[13] -1 0 0xfd005000 - 0xfd0050ff (0x100) MX[B]
[14] -1 0 0xfd004000 - 0xfd004fff (0x1000) MX[B]
[15] -1 0 0xfd003000 - 0xfd003fff (0x1000) MX[B]
[16] -1 0 0xf0000000 - 0xefffffff (0x0) MX[B]O
[17] -1 0 0xf9000000 - 0xf9ffffff (0x1000000) MX[B](B)
[18] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B)
[19] -1 0 0xf8000000 - 0xf8ffffff (0x1000000) MX[B](B)
[20] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B](OprD)
[21] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B](OprD)
[22] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B](OprD)
[23] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[24] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[25] -1 0 0x0000a400 - 0x0000a40f (0x10) IX[B]
[26] -1 0 0x0000a000 - 0x0000a003 (0x4) IX[B]
[27] -1 0 0x00009c00 - 0x00009c07 (0x8) IX[B]
[28] -1 0 0x00009800 - 0x00009803 (0x4) IX[B]
[29] -1 0 0x00009400 - 0x00009407 (0x8) IX[B]
[30] -1 0 0x00009000 - 0x000090ff (0x100) IX[B]
[31] -1 0 0x0000e000 - 0x0000e07f (0x80) IX[B]
[32] -1 0 0x0000dc00 - 0x0000dc0f (0x10) IX[B]
[33] -1 0 0x00000b70 - 0x00000b73 (0x4) IX[B]
[34] -1 0 0x00000970 - 0x00000977 (0x8) IX[B]
[35] -1 0 0x00000bf0 - 0x00000bf3 (0x4) IX[B]
[36] -1 0 0x000009f0 - 0x000009f7 (0x8) IX[B]
[37] -1 0 0x0000f000 - 0x0000f00f (0x10) IX[B]
[38] -1 0 0x0000c000 - 0x0000c07f (0x80) IX[B]
[39] -1 0 0x0000bc00 - 0x0000bcff (0x100) IX[B]
[40] -1 0 0x0000b800 - 0x0000b807 (0x8) IX[B]
[41] -1 0 0x00002000 - 0x0000203f (0x40) IX[B]
[42] -1 0 0x00001c00 - 0x00001c3f (0x40) IX[B]
[43] -1 0 0x0000e400 - 0x0000e41f (0x20) IX[B]
[44] 0 0 0xfa0003b0 - 0xfa0003bb (0xc) IS[B]
[45] 0 0 0xfa0003c0 - 0xfa0003df (0x20) IS[B]
(II) NVIDIA(0): Setting mode "1024x768"
(II) Loading extension NV-GLX
(II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
(II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
(==) NVIDIA(0): Backing store disabled
(==) NVIDIA(0): Silken mouse enabled
(**) Option "dpms"
(**) NVIDIA(0): DPMS enabled
(II) Loading extension NV-CONTROL
(==) RandR enabled
(II) Setting vga for screen 0.
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
(II) Initializing extension GLX
error opening security policy file /etc/X11/xserver/SecurityPolicy
(**) Option "CoreKeyboard"
(**) Generic Keyboard: Core Keyboard
(**) Option "Protocol" "standard"
(**) Generic Keyboard: Protocol: standard
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xorg"
(**) Generic Keyboard: XkbRules: "xorg"
(**) Option "XkbModel" "pc104"
(**) Generic Keyboard: XkbModel: "pc104"
(**) Option "XkbLayout" "us"
(**) Generic Keyboard: XkbLayout: "us"
(**) Option "CustomKeycodes" "off"
(**) Generic Keyboard: CustomKeycodes disabled
(**) Option "Protocol" "evdev"
(EE) Configured Mouse: Unknown protocol "evdev"
(EE) PreInit failed for input device "Configured Mouse"
(II) UnloadModule: "mouse"
(**) Option "SendCoreEvents"
(**) stylus: always reports core events
(**) stylus device is /dev/wacom
(**) stylus is in absolute mode
(**) stylus: forcing TabletPC ISD V4 protocol
(**) WACOM: suppress value is 2
(**) Option "BaudRate" "9600"
(**) stylus: serial speed 9600
(**) Option "SendCoreEvents"
(**) cursor: always reports core events
(**) cursor device is /dev/wacom
(**) cursor is in relative mode
(**) cursor: forcing TabletPC ISD V4 protocol
(**) WACOM: suppress value is 2
(**) Option "BaudRate" "9600"
(**) cursor: serial speed 9600
(**) Option "SendCoreEvents"
(**) eraser: always reports core events
(**) eraser device is /dev/wacom
(**) eraser is in absolute mode
(**) eraser: forcing TabletPC ISD V4 protocol
(**) WACOM: suppress value is 2
(**) Option "BaudRate" "9600"
(**) eraser: serial speed 9600
(EE) Configured Mouse: Unknown protocol "evdev"
(EE) PreInit failed for input device "Configured Mouse"
(II) UnloadModule: "mouse"
(WW) No core pointer registered
(II) XINPUT: Adding extended input device "eraser" (type: Wacom Eraser)
(II) XINPUT: Adding extended input device "cursor" (type: Wacom Cursor)
(II) XINPUT: Adding extended input device "stylus" (type: Wacom Stylus)
(II) XINPUT: Adding extended input device "Generic Keyboard" (type: KEYBOARD)
(II) XINPUT: Adding extended input device "NVIDIA Event Handler" (type: Other)
(**) Option "Device" "/dev/wacom"
(EE) xf86OpenSerial: Cannot open device /dev/wacom
No such file or directory.
Error opening /dev/wacom : No such file or directory
(EE) xf86OpenSerial: Cannot open device /dev/wacom
No such file or directory.
Error opening /dev/wacom : No such file or directory
(**) Option "Device" "/dev/wacom"
(EE) xf86OpenSerial: Cannot open device /dev/wacom
No such file or directory.
Error opening /dev/wacom : No such file or directory
(EE) xf86OpenSerial: Cannot open device /dev/wacom
No such file or directory.
Error opening /dev/wacom : No such file or directory
(**) Option "Device" "/dev/wacom"
(EE) xf86OpenSerial: Cannot open device /dev/wacom
No such file or directory.
Error opening /dev/wacom : No such file or directory
(EE) xf86OpenSerial: Cannot open device /dev/wacom
No such file or directory.
Error opening /dev/wacom : No such file or directory
No core pointer

Fatal server error:
failed to initialize core devices


do you know what the problem and how to fix it?
thnks

detyabozhye
August 22nd, 2006, 08:17 PM
If you're using Dapper, check the guide linked in my sig.

dids22
August 23rd, 2006, 12:05 PM
i got the same probleam

Fatal server error:
failed to initialize core devices

pwner4once
August 26th, 2006, 12:19 AM
i followed through the guide but i just can't get throug the xorg.conf part. it always gives me some kind of error. and say it's trying to find /sbin/wacom? O_O how is that even related to anything?

BLTicklemonster
September 2nd, 2006, 03:22 AM
(the logitech mouse settings are off of ticklemonster's), everytime i try to alter the file X crashes on reboot.

can someone please help me (a) restore the orignal mouse settings and then (b) get these side buttons to work and then maybe (c) figure out the code to have them switch workspaces?

thanks in advance!

Hey, definitely follow the guide here:

http://ubuntuforums.org/showthread.php?t=219894

I just came back to Ubuntu after being away for a while (things to do I could only do in Windows, and I didn't need the distraction of Ubuntu being around, lol) and it worked first time.

Thank you detyabozhye for that great guide!!!

geezerone
October 4th, 2006, 10:05 PM
Hi

Tried configuring my MX510 and added the xbind code but the 'side' buttons don't show a button ID using 'xev' but just the following. The scroll buttons were working by default ok and these numbers are 8 and 9:

a FocusIn event, serial 29, synthetic NO, window 0x3000001,
mode NotifyNormal, detail NotifyNonlinear

KeymapNotify event, serial 29, synthetic NO, window 0x0,
keys: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

EnterNotify event, serial 29, synthetic NO, window 0x3000001,
root 0x4c, subw 0x0, time 354632351, (155,165), root:(850,291),
mode NotifyNormal, detail NotifyAncestor, same_screen YES,
focus YES, state 16

KeymapNotify event, serial 29, synthetic NO, window 0x0,
keys: 76 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

hockeysk8
December 27th, 2006, 10:56 AM
I have posted complete instructions that are specific to the Logitech MX Revolution mouse at http://rootsmith.ca/mxrev-linux.html.

Simon80
January 13th, 2007, 07:45 AM
I don't think I found similar info in this thread, so here's a link (http://ubuntuforums.org/showthread.php?t=65062) to my posting in a different thread, with instructions for how to get logitech_applet to run whenever a Logitech mouse is plugged in, rather than on boot. Also, rather than adding a script in /etc/init.d, it would have been easier to run

sudo crontab -e

and then add a line into the crontab like so:

@reboot <command>

I got that from the Ubuntu Guide at some point. However, it's not necessary now that you have a udev rule running the command.

Bryan Larsen
January 26th, 2007, 05:19 PM
If it doesn’t work, try plugging it into a different USB port. I had everything configured correctly, and my Xorg.0.log output had lots of stuff about finding the mouse, detecting the buttons, et cetera, but then it had the lines:

(II) LogitechVX-usb-0000:00:1d.1-2/input0: On
(II) LogitechVX-usb-0000:00:1d.1-2/input0: Off

and my mouse wasn’t working. Removing the dongle from my powered USB hub and plugging it into my mainboard made everything work.

Jeeks
February 1st, 2007, 08:10 PM
Ok, I fixed m Revolution VX but I would really like to know what is the syntax for the Fn key.

Another thing would be appreciated, the thumb buttons I assigned to Pgup and Pgdn but I would like it if I click and hold it will keep executing the key and not execute it only once. Is there a way to do that?

geezerone
February 25th, 2007, 10:16 PM
Still can't get side buttons on my MX510 working (6 and 7) which in firefox move page down/up.

I have tried xmodmap to no avail. Here is my latest xorg info:


Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "Buttons" "7"
Option "ZAxisMapping" "4 5"
Option "ButtonMapping" "1 2 3 6 7"
Option "Emulate3Buttons" "true"
#Option "Resolution" "800

geezerone
March 5th, 2007, 05:42 PM
<bump> Anyone??

DancingSun
March 5th, 2007, 06:27 PM
<bump> Anyone??

Make sure you follow Section 1 of the first post. I see that your xorg.conf entry is not correct.

The Section 1 of the first post should at least get the side buttons working in Firefox as backward/forward. To make it work in Nautilus, you'll need to do the key bindings.

It may be best to disable all your key binding for your mouse when following the instructions in the first post.

geezerone
March 7th, 2007, 06:38 PM
Thanks for answering. Would the guide apply to using the mouse on PS/2 port also?

DancingSun
March 7th, 2007, 09:21 PM
Thanks for answering. Would the guide apply to using the mouse on PS/2 port also?

It should. You can always disable your current mouse configuration in xorg.conf by commenting it out. If the new configuration doesn't work, just delete the new configuration and enable the old one.

freakavoid
March 9th, 2007, 01:48 PM
In case someone encounters the same problem:

Evdev doesn't support AllowMouseOpenFail, so if you want to use this driver on a computer which doesn't have the mouse plugged in all the time (e.g. a laptop) you might want to make your touchpad your primary input device i.e. corepointer and set the SendCoreEvents option in the configured mouse section to true.

So, no more

No core pointer

Fatal server error:
failed to initialize core devices
(Actually this was for the searchers among us)

geezerone
March 11th, 2007, 11:33 PM
Well, my cat /proc/bus/input/devices is as follows:


I: Bus=0011 Vendor=0002 Product=0002 Version=0064
N: Name="PS2++ Logitech MX Mouse"
P: Phys=isa0060/serio1/input0
S: Sysfs=/class/input/input2
H: Handlers=mouse0 event2 ts0
B: EV=7
B: KEY=ff0000 0 0 0 0 0 0 0 0
B: REL=103


I inserted the following:


Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "Protocol" "evdev"
Option "Dev Name" "PS2++ Logitech MX Mouse"
Option "Dev Phys" "isa0060/serio1/input0"
Option "Device" "/dev/input/event2"
Option "Buttons" "10"
Option "ZAxisMapping" "4 5"
EndSection

I restarted X but wouldn't start with "atomic" error :confused:

I am using MX510 PS/2.

AnRkey
March 12th, 2007, 02:08 AM
The more people who make a fuss about this spec the better. We need something like this for Ubuntu.

https://blueprints.launchpad.net/ubuntu/+spec/gui-mouse-configuration

Take a look at the spec and subscribe to it to follow progress.

geezerone
March 17th, 2007, 04:01 PM
Any ideas?

Rhombuss
March 18th, 2007, 01:10 AM
I've tried this out using Ubuntu 6.10 with an MX500.

I followed the instructions but it won't reinitialize X. I keep having to recover the initial parameters to get back into X. I'm not sure if I'm doing something incorrectly, as it doesn't appear that many others have had problems reinitializing X, just getting the thumb buttons to work, etc.

Does it matter if I have my mouse plugged into my USB keyboard? I was wondering if that would affect how the xorg.conf addresses are assigned for the USB devices.

Any help is appreciated!

geezerone
March 18th, 2007, 09:39 PM
Try posting your xorg.conf here so it can be studied.

(still no thumb action here :( )

Rhombuss
March 18th, 2007, 11:23 PM
This is my xorg.conf:


Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
EndSection

#Section "InputDevice"
# Identifier "Configured Mouse"
# Driver "mouse"
# Option "Protocol" "evdev"
# Option "Dev Name" "B16_b_02 USB-PS/2 Optical Mouse"
# Option "Dev Phys" "usb-0000:00:1d.0-2.1/input0"
# Option "Device" "/dev/input/event1"
# Option "Buttons" "10"
# Option "ZAxisMapping" "4 5"
#EndSection

And this is my device listing (I included the mouse and keyboard hub listings):


I: Bus=0003 Vendor=046d Product=c025 Version=9802
N: Name="B16_b_02 USB-PS/2 Optical Mouse"
P: Phys=usb-0000:00:1d.0-2.1/input0
S: Sysfs=/class/input/input0
H: Handlers=mouse0 event0 ts0
B: EV=7
B: KEY=ff0000 0 0 0 0 0 0 0 0
B: REL=103

I: Bus=0003 Vendor=099a Product=800a Version=0102
N: Name=" Keyboard Hub"
P: Phys=usb-0000:00:1d.0-2.3/input0
S: Sysfs=/class/input/input1
H: Handlers=kbd event1
B: EV=120003
B: KEY=10000 7 ff87207a c14057ff febeffdf ffefffff ffffffff fffffffe
B: LED=7

I: Bus=0003 Vendor=099a Product=800a Version=0102
N: Name=" Keyboard Hub"
P: Phys=usb-0000:00:1d.0-2.3/input1
S: Sysfs=/class/input/input2
H: Handlers=kbd event2
B: EV=f
B: KEY=c0002 400 0 0 1 c00 78000 2639fa d841d7ad 9e0000 0 0 0
B: REL=40
B: ABS=1 0


Thanks.

Hmm, I just noticed now that it's displaying my mouse as event0 and my keyboard hubs as event1 and event2. Originally when I did the modifications, my keyboard hubs were event0 and event2, while my mouse was event1 (hence the event1 entry in the xorg.conf). Perhaps I should take the mouse off my keyboard and plug it straight into my motherboard USB ports?

richdurhm
March 23rd, 2007, 06:04 PM
hey guys i have an mx 600 i tried this and now my mouse doens't work at all neither on windows i have to use my old mouse now any suggestions????? im me on aim at richdurhm

geezerone
March 23rd, 2007, 09:16 PM
It would make no diff to windows.

Skidpad
March 24th, 2007, 01:29 AM
Just for reference, here's my X11 file. I'm using an MX610 mouse. The only thing that doesn't work is my cruise control; fwd/back/volume/scroll all work. Cruise control (auto-scrolling when clicking the wheel and moving the mouse) is my next project.


Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "ZAxisMapping" "4 5"
Option "ButtonMapping" "1 2 3 6 7"
Option "Emulate3Buttons" "true"
EndSection

bryonak
April 1st, 2007, 09:09 PM
Having only read the beginning of the thread I don't know if it's already been mentioned, but I'll post it anyways...
The solution with Xmodmap & xbindkeys has worked for me, with following exception to the .xbindkeysrc:



"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[Left]""
m:0x0 + b:6
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[Right]""
m:0x0 + b:7
*

instead of (as described on the first page):



"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[left]""
m:0x0 + b:6
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[right]""
m:0x0 + b:7


The difference being only the capitalization of "left" and "right"


Here's my xorg.conf:



Section "InputDevice"
Identifier "Configured Mouse"
Driver "evdev"
Option "CorePointer"
Option "Dev Name" "Logitech USB-PS/2 Optical Mouse"
Option "Dev Phys" "usb-*/input0"
Option "Device" "/dev/input/event1"
Option "Protocol" "evdev"
Option "Buttons" "10"
Option "ZAxisMapping" "4 5"
Option "ButtonMapping" "1 2 3 4 5 6 7 8 9 10"
EndSection


and my .Xmodmap



pointer = 1 2 3 4 5 6 7 8 9 10 11 12



* After previewing my post, it seems like the forum script converts "Left" and "Right" to "left" and "right", no matter whether I capitalize them in the reply text area... probably because of the brackets. Point is, "left" & "right" didn't work for me, "Left" & "Right" does.

Jump
April 4th, 2007, 02:24 AM
Just for reference, here's my X11 file. I'm using an MX610 mouse. The only thing that doesn't work is my cruise control; fwd/back/volume/scroll all work. Cruise control (auto-scrolling when clicking the wheel and moving the mouse) is my next project.


Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "ZAxisMapping" "4 5"
Option "ButtonMapping" "1 2 3 6 7"
Option "Emulate3Buttons" "true"
EndSection


THANK YOU!!!!

The original post did not work for me, but your recommendation worked perfectly on my MX518 w/ Edgy 6.10.

Thanks again!!!!!

:guitar:

sandman55
April 4th, 2007, 03:48 PM
I have a logitec MX500 and I havent been able to get it to work after the first bit
sudo gedit /etc/X11/xorg.conf
but before I continue (and I'm going to try a few things) I want to know is this thread for Dapper? or only edgy because I'm working with Dapper. Thanks

sandman55
April 5th, 2007, 03:19 PM
Can anyone answer are the instructions in this thread for Dapper or Edgy

detyabozhye
April 6th, 2007, 06:33 AM
They're for Breezy as far as I remember. I have the ones for Dapper in my signiture which work for some in Edgy as well.

sandman55
April 6th, 2007, 06:48 AM
Thanks for that detyabozhye I was just about to install Edgy but I will try your site first, Im using Dapper to practice on first

Angry penguin
April 29th, 2007, 04:18 AM
I am having difficulty getting this to work with my logitech mx500. I get the error:
unknown protocol "evdev"
and "failed to initialize core devices"

and something about wacom not initializing or something.

xorg:


#Section "InputDevice"
# Identifier "Configured Mouse"
# Driver "mouse"
# Option "Device" "/dev/input/event9"
# Option "Protocol" "evdev"
# Option "ZAxisMapping" "4 5"
# Option "Dev Name" "Logitech USB-PS/2 Optical Mouse"
# Option "Dev Phys" "usb-0000:00:02.0-1/input0"
# Option "Buttons" "9"
# Option "CorePointer"
#EndSection




I: Bus=0003 Vendor=046d Product=c025 Version=0110
N: Name="Logitech USB-PS/2 Optical Mouse"
P: Phys=usb-0000:00:02.0-1/input0
S: Sysfs=/class/input/input1
H: Handlers=mouse1 ts1 event1
B: EV=20007
B: KEY=ff0000 0 0 0 0 0 0 0 0
B: REL=103
B: LED=ff00


any ideas? I have been try to get this mouse to work since warty...

AnRkey
April 29th, 2007, 05:35 AM
I am having difficulty getting this to work with my logitech mx500. I get the error:
unknown protocol "evdev"
and "failed to initialize core devices"

and something about wacom not initializing or something.

xorg:


#Section "InputDevice"
# Identifier "Configured Mouse"
# Driver "mouse"
# Option "Device" "/dev/input/event9"
# Option "Protocol" "evdev"
# Option "ZAxisMapping" "4 5"
# Option "Dev Name" "Logitech USB-PS/2 Optical Mouse"
# Option "Dev Phys" "usb-0000:00:02.0-1/input0"
# Option "Buttons" "9"
# Option "CorePointer"
#EndSection




I: Bus=0003 Vendor=046d Product=c025 Version=0110
N: Name="Logitech USB-PS/2 Optical Mouse"
P: Phys=usb-0000:00:02.0-1/input0
S: Sysfs=/class/input/input1
H: Handlers=mouse1 ts1 event1
B: EV=20007
B: KEY=ff0000 0 0 0 0 0 0 0 0
B: REL=103
B: LED=ff00


any ideas? I have been try to get this mouse to work since warty...
Thist post works for Feisty >> http://ubuntuforums.org/showthread.php?t=219894

It's pretty good and easy to do. It shows how to install evdev in the firt step or two.

Let us know if it works.

AnRkey

Angry penguin
April 29th, 2007, 06:34 PM
Thist post works for Feisty >> http://ubuntuforums.org/showthread.php?t=219894

It's pretty good and easy to do. It shows how to install evdev in the firt step or two.

Let us know if it works.

AnRkey

Unfortunately, I have already tried that tutorial as well. I believe evdev is installed by default in feisty because when I tried installing it, apt told me it was already. Despite the fact that evdev is installed, It still tells me unknown protocol, which makes no sense. Unless there is something that needs to point to it, or its looking in the wrong place. :confused:

EDIT: I think I have it figured out, I just had to pretty much use the default config for my mouse and add xbindkeys to get side buttons working in nautilus and firefox. Thanks!

DancingSun
April 29th, 2007, 07:07 PM
I am having difficulty getting this to work with my logitech mx500. I get the error:
unknown protocol "evdev"
and "failed to initialize core devices"

and something about wacom not initializing or something.

xorg:


#Section "InputDevice"
# Identifier "Configured Mouse"
# Driver "mouse"
# Option "Device" "/dev/input/event9"
# Option "Protocol" "evdev"
# Option "ZAxisMapping" "4 5"
# Option "Dev Name" "Logitech USB-PS/2 Optical Mouse"
# Option "Dev Phys" "usb-0000:00:02.0-1/input0"
# Option "Buttons" "9"
# Option "CorePointer"
#EndSection




I: Bus=0003 Vendor=046d Product=c025 Version=0110
N: Name="Logitech USB-PS/2 Optical Mouse"
P: Phys=usb-0000:00:02.0-1/input0
S: Sysfs=/class/input/input1
H: Handlers=mouse1 ts1 event1
B: EV=20007
B: KEY=ff0000 0 0 0 0 0 0 0 0
B: REL=103
B: LED=ff00


any ideas? I have been try to get this mouse to work since warty...

I noticed that, at a glance, your "Device" line in xorg.conf indicates "event9" while your cat output indicates "event1".

For what it's worth, I've fiddled around with my mouse configuration on and off, and I don't remember when did I last change it, but it seems like I can get by with just 3 lines of configuration code:

Section "InputDevice"
Identifier "Mouse1"
Driver "evdev"
Option "Device" "/dev/input/event9"
EndSection

AnRkey
April 29th, 2007, 07:36 PM
Angry penguin: Glad to know it's working :)

AnRkey

measekite
September 28th, 2007, 04:42 AM
I have a MX700 and this worked fine although here is what I have in my xorg.conf:


Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Protocol" "evdev"
Option "Dev Name" "Logitech USB Receiver"
Option "Dev Phys" "usb-*/input1"
Option "Device" "/dev/input/ts0"
Option "Buttons" "10"
Option "ZAxisMapping" "9 10"
EndSectionMy mouse is connected through the Ps/2 port of the computer while keyboard is connected through USB. I have the Logitech MX Duo

Could you post your /proc/bus/input/devices FILE

measekite
September 28th, 2007, 04:47 AM
Originally Posted by Angry penguin http://ubuntuforums.org/images/uf/buttons/viewpost.gif (http://ubuntuforums.org/showthread.php?p=2556614#post2556614)
I am having difficulty getting this to work with my logitech mx500. I get the error:
unknown protocol "evdev"
and "failed to initialize core devices"

and something about wacom not initializing or something.
Option "Device" "/dev/input/event9"
EndSection[/code][/quote]


I get exactly the same thing. I do not know what to do next. If you solve this one please post. If anybody else has some ideas I sure would like to here them.

measekite
September 28th, 2007, 05:50 PM
I am having difficulty getting this to work with my logitech mx500. I get the error:
unknown protocol "evdev"
and "failed to initialize core devices"

and something about wacom not initializing or something.

xorg:


#Section "InputDevice"
# Identifier "Configured Mouse"
# Driver "mouse"
# Option "Device" "/dev/input/event9"
# Option "Protocol" "evdev"
# Option "ZAxisMapping" "4 5"
# Option "Dev Name" "Logitech USB-PS/2 Optical Mouse"
# Option "Dev Phys" "usb-0000:00:02.0-1/input0"
# Option "Buttons" "9"
# Option "CorePointer"
#EndSection


I: Bus=0003 Vendor=046d Product=c025 Version=0110
N: Name="Logitech USB-PS/2 Optical Mouse"
P: Phys=usb-0000:00:02.0-1/input0
S: Sysfs=/class/input/input1
H: Handlers=mouse1 ts1 event1
B: EV=20007
B: KEY=ff0000 0 0 0 0 0 0 0 0
B: REL=103
B: LED=ff00
any ideas? I have been try to get this mouse to work since warty...

I had the same thing. I solved this by changing
Driver "mouse" to
Driver "evdev"

All of the errors go away and the computer will boot X find. The initial problem remains: side button does not work.

Lord C
October 20th, 2007, 03:01 AM
I have a MX1000 and I have spent hours trying to get the drivers to work as in this (and other very similar tutorials).

Here's my xorg.conf

Section "InputDevice"
Identifier "Logitech MX1000"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
EndSection

#Section "InputDevice"
# Identifier ""Logitech MX1000"
# Driver "mouse"
# Option "Protocol" "evdev"
# Option "Dev Name" "Logitech USB RECEIVER"
# Option "Dev Phys" "usb-*/input0"
# Option "Device" "/dev/input/event2"
# Option "Buttons" "12"
# Option "ZAxisMapping" "4 5"

#Section "InputDevice"
#Identifier "Logitech MX1000"
#Driver "evdev"
#Option "CorePointer"
#Option "Protocol" "evdev"
#Option "Name" "Logitech USB RECEIVER"
#Option "Dev Phys" "usb-0000:00:10.0-2/input0"
#Option "Device" "/dev/input/mx1000"
#Option "Buttons" "12"
#Option "ZAxisMapping" "11 12 10 9"
#Option "Resolution" "800"
#Option "Emulate3Buttons" "false"
#EndSection

First block works obviously, default rubbish.
Second block gives error "Unknown protocol: evdev" even though of course evdev is installed.
With the third block, I tried editing udev, everything. Was getting NULL, it wasn't finding the device.

Lord C
October 20th, 2007, 03:07 AM
Turns out I was giving far too much information to xorg.conf, all it needed was the device name.

For a more up to date tutorial, follow https://help.ubuntu.com/community/MX1000Mouse

XavierGr
October 21st, 2007, 05:30 AM
Following the tutorials I finally managed to get Kubuntu to recognize nearly all the keys on my G7 mouse. Though, despite all the reading I've never read about how to enable the resolution buttons.

In my case the default resolution of 800 dpi is identical for my habits, so I want to utilize those two buttons with page up/down events (for fast scrolling). Any ideas on how to make those buttons configurable?

Thanks in advance.

XavierGr
October 21st, 2007, 11:55 PM
To answer my own post:
Searching the net I encountered this guide (http://wiki.archlinux.org/index.php/Get_All_Mouse_Buttons_Working).
Using the tool near the botom of the page (g5hack), it should be able to remap the resolution (+,-) buttons too.
Unfortunately it doesn't work for me, I hope that I am doing something wrong and I will be able to correct the problem.

MilitantPotato
November 26th, 2007, 10:56 PM
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "ZAxisMapping" "4 5"
Option "ButtonMapping" "1 2 3 6 7"
Option "Emulate3Buttons" "true"
EndSection

Worked for a MX518 on Kubuntu Gutsy 7.10 in firefox. Resolution changes also work.

superteodj
November 29th, 2007, 12:46 PM
hi everyone!
my first post... my first question :) :
i configured the xbindkeysrc file as


"/usr/bin/xvkbd -xsendevent -text "\[Alt_L]\[Left]""
m:0x0 + b:6
"/usr/bin/xvkbd -xtest -text "\[Alt_L]\[F4]""
m:0x0 + b:8

for a mx518. but, the alt+F4 combo doesnt work -.-... if leave te standard config ( alt_l+right) it works properly, but not with alt+F4 to close windows...
what's wrong?

thanks everyone ^^
ciao!

AbtZ
December 15th, 2007, 03:32 AM
Great guide, now I can finally go back and forward with the mouse in Nautilus (something I think should be enabled by default, really).

Thanks!

Shakey_Jake33
January 8th, 2008, 12:35 PM
Awesome guide, works a charm :)

Exar Kun
January 11th, 2008, 12:34 AM
I cant make my MX510 works with compiz-fusion it works fine when I disable it (compiz). I also try edved but when GDM starts half of the screen freeze this is how i configure xorg.conf. I don´t mind the extra buttons I just want to scroll up to work


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

harold4
January 11th, 2008, 02:17 AM
The following allows for all buttons, aside from the back/forward to work on my mx518.



Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "Resolution" "800"
Option "Buttons" "10"
Option "ZAxisMapping" "4 5"
Option "ButtonMapping" "1 2 3 6 7"
EndSection


xev sees back/forward as button 6/7, but it is ignored by firefox and konqueror.

geezerone
January 13th, 2008, 01:32 AM
My MX510 works apart from back/forward too - acts as scroll up.

Wonder if the latest Ubuntu has fixed this mouse button problem?

highstead
January 20th, 2008, 01:33 AM
Hopefully someone still trolls here. I've followed the guide but every time i've implemented it i get a graphical problem. Now I've had this problem before when tweaking Xorg and its been with regards to the dual monitors but this would suggest that i'm not closing something? My mouse section looks like this.

xorg.conf

Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "evdev"
Option "Dev Name" "Logitech USB-PS/2 Optical Mouse"
Option "Dev Phys" "usb-0000:00:0a.0-1/input0"
Option "Device" "/dev/input/event1"
Option "Buttons" "10"
Option "ZAxisMapping" "4 5"
# Identifier "Mouse0"
# Driver "mouse"
# Option "Protocol" "auto"
# Option "Device" "/dev/psaux"
# Option "Emulate3Buttons" "no"
# Option "ZAxisMapping" "4 5"
EndSection

Devices:

I: Bus=0003 Vendor=046d Product=c01e Version=0110
N: Name="Logitech USB-PS/2 Optical Mouse"
P: Phys=usb-0000:00:0a.0-1/input0
S: Sysfs=/class/input/input1
U: Uniq=
H: Handlers=mouse1 event1
B: EV=7
B: KEY=ff0000 0 0 0 0
B: REL=103


Kept Mouse0 because they section 'ServerLayout' Seems to refer to it.

Cheers

Microtome
January 24th, 2008, 10:26 AM
Hopefully someone still trolls here. I've followed the guide but every time i've implemented it i get a graphical problem. Now I've had this problem before when tweaking Xorg and its been with regards to the dual monitors but this would suggest that i'm not closing something? My mouse section looks like this.

xorg.conf

Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "evdev"
Option "Dev Name" "Logitech USB-PS/2 Optical Mouse"
Option "Dev Phys" "usb-0000:00:0a.0-1/input0"
Option "Device" "/dev/input/event1"
Option "Buttons" "10"
Option "ZAxisMapping" "4 5"
# Identifier "Mouse0"
# Driver "mouse"
# Option "Protocol" "auto"
# Option "Device" "/dev/psaux"
# Option "Emulate3Buttons" "no"
# Option "ZAxisMapping" "4 5"
EndSection

Devices:

I: Bus=0003 Vendor=046d Product=c01e Version=0110
N: Name="Logitech USB-PS/2 Optical Mouse"
P: Phys=usb-0000:00:0a.0-1/input0
S: Sysfs=/class/input/input1
U: Uniq=
H: Handlers=mouse1 event1
B: EV=7
B: KEY=ff0000 0 0 0 0
B: REL=103


Kept Mouse0 because they section 'ServerLayout' Seems to refer to it.

Cheers

Try checking out this page

https://help.ubuntu.com/community/MX1000Mouse

This worked for me even though I am using a Logitech G5 and Gutsy. Plus it was much easier than the previous method. Which I too have spent hours trying to make work on my set-up. Of course you mileage may vary. Check out what changes I made to the directions on the page I listed above.




cat /proc/bus/input/devices



I: Bus=0003 Vendor=046d Product=c049 Version=0111
N: Name="Logitech USB Gaming Mouse"
P: Phys=usb-0000:00:10.2-2/input0
S: Sysfs=/class/input/input4
U: Uniq=
H: Handlers=mouse1 event1
B: EV=7
B: KEY=ffff0000 0 0 0 0 0 0 0 0
B: REL=143

xorg.config


#Section "InputDevice"
# Identifier "Configured Mouse"
# Driver "mouse"
# Option "CorePointer"
# Option "Device" "/dev/input/mice"
# Option "Protocol" "ImPS/2"
# Option "ZAxisMapping" "4 5"
# Option "Emulate3Buttons" "true"
#EndSection

Section "InputDevice"
Identifier "Logitech G5"
Driver "evdev"
Option "Name" "Logitech USB Gaming Mouse"
Option "HWHEELRelativeAxisButtons" "7 6"
EndSection

Notice I only commented out the original mouse set up as I had to go back to that a couple of times to finally get it straightened out. You must also do the same to the Section "ServerLayout" seen here:


Section "ServerLayout"
Identifier "Default Layout"
screen 0 "Default Screen" 0 0
Inputdevice "Generic Keyboard"
# Inputdevice "Configured Mouse"
InputDevice "Logitech G5" "CorePointer"
EndSection

The important part for this is to just comment out the "Configured Mouse" line and add the next line using the same Identifier, in my case "Logitech G5"
Hope this helps.

Check me out, my first post is actually a contribution. :shock:

-Micro

ccdee
February 16th, 2008, 09:40 AM
hmmmm


well my 518 works in every Linux except this one... tried Ubuntu, XUbuntu... but after 1 click the mouse is Stuck... no movement or click possible anymore.... so i can't even get a terminal up :S

skunkbad
February 16th, 2008, 11:59 AM
I have a Logitech LX7, and running Ubuntu 7.10, and can't get the back/forward buttons working. I've looked at many of the guides here in the forum, and haven't been successful.

This is the mouse section of my xorg.conf:



Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
EndSection

#Section "InputDevice"
# Identifier "Configured Mouse"
# Driver "mouse"
# Option "Protocol" "evdev"
# Option "Dev Name" "Logitech USB RECEIVER"
# Option "Dev Phys" "usb-*/input0"
# Option "Device" "/dev/input/event2"
# Option "Buttons" "10"
# Option "ZAxisMapping" "4 5"
#EndSection


I of course had it commented the other way, but it wasn't working.

Any help is appreciated.

orrie
March 1st, 2008, 10:06 PM
I have now runned:

cat /proc/bus/input/devices

.. and that didn't do the thing.
I see the NVIDIA-splash and then X restarts and I see the Nvidia-splash again and then it restarts, and this keeps going on..



orrie ~ ;) cat /proc/bus/input/devices
...
...
I: Bus=0003 Vendor=046d Product=c01e Version=0110
N: Name="Logitech USB-PS/2 Optical Mouse"
P: Phys=usb-0000:00:0a.0-2/input0
S: Sysfs=/class/input/input2
U: Uniq=
H: Handlers=mouse1 event2
B: EV=7
B: KEY=ff0000 0 0 0 0
B: REL=103
...
...


orrie ~ ;) cat /etc/X11/xorg.conf
Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "Screen0" 0 0
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
EndSection

Section "Files"
EndSection

Section "ServerFlags"
Option "Xinerama" "0"
EndSection

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "no"
Option "XkbOptions" "lv3:ralt_switch"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "Protocol" "evdev"
Option "Dev Name" "Logitech USB-PS/2 Optical Mouse"
Option "Dev Phys" "usb-*/input0"
Option "Device" "/dev/input/event2"
Option "Buttons" "10"
Option "ZAxisMapping" "4 5"
EndSection


#Section "InputDevice"
# Identifier "Configured Mouse"
# Driver "mouse"
# Option "CorePointer"
# Option "Device" "/dev/input/mice"
# Option "Protocol" "ImPS/2"
# Option "ZAxisMapping" "4 5"
# Option "Emulate3Buttons" "true"
#EndSection

Section "Monitor"
Identifier "Standard skjerm"
HorizSync 28.0 - 64.0
VertRefresh 43.0 - 60.0
Option "DPMS"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Samsung SyncMaster"
HorizSync 30.0 - 81.0
VertRefresh 56.0 - 75.0
EndSection

Section "Device"
Identifier "nVidia Corporation G80 [GeForce 8800 Ultra]"
Driver "nvidia"
EndSection

Section "Device"
Identifier "Videocard0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 8800 Ultra"
EndSection

Section "Screen"
Identifier "Default Screen"
Device "nVidia Corporation G80 [GeForce 8800 Ultra]"
Monitor "Standard skjerm"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1280x800" "1280x768" "1024x768"
EndSubSection
EndSection

Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 24
Option "TwinView" "1"
Option "TwinViewXineramaInfoOrder" "DFP-0"
Option "metamodes" "DFP-0: nvidia-auto-select +0+0, DFP-1: 1440x900 +1440+0; DFP-0: nvidia-auto-select +0+0, DFP-1: 1280x768 +1440+0; DFP-0: nvidia-auto-select +0+0, DFP-1: 1024x768 +1440+0"
EndSection

orrie ~ ;) cat /var/log/Xorg.0.log

X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: Linux Ubuntu (xorg-server 2:1.3.0.0.dfsg-12ubuntu8.3)
Current Operating System: Linux ubuntu 2.6.22-14-generic #1 SMP Tue Feb 12 02:46:46 UTC 2008 x86_64
Build Date: 18 January 2008
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sat Mar 1 22:03:53 2008
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Default Layout"
(**) |-->Screen "Screen0" (0)
(**) | |-->Monitor "Monitor0"
(**) | |-->Device "Videocard0"
(**) |-->Input Device "Generic Keyboard"
(**) |-->Input Device "Configured Mouse"
(==) |-->Input Device "Configured Mouse"
(WW) The core pointer device wasn't specified explicitly in the layout.
Using the first mouse device.
(**) Option "Xinerama" "0"
(WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
Entry deleted from font path.
(==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType
(==) RgbPath set to "/etc/X11/rgb"
(==) ModulePath set to "/usr/lib/xorg/modules"
(II) Open ACPI successful (/var/run/acpid.socket)
(II) Loader magic: 0x7cdb20
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.3
X.Org Video Driver: 1.2
X.Org XInput driver : 0.7
X.Org Server Extension : 0.3
X.Org Font Renderer : 0.5
(II) Loader running on linux
(II) LoadModule: "pcidata"
(II) Loading /usr/lib/xorg/modules//libpcidata.so
(II) Module pcidata: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.0.0
ABI class: X.Org Video Driver, version 1.2
(--) using VT number 7

(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 10de,02f4 card 10de,02f4 rev a2 class 05,00,00 hdr 80
(II) PCI: 00:00:1: chip 10de,02fa card 10de,02fa rev a2 class 05,00,00 hdr 80
(II) PCI: 00:00:2: chip 10de,02fe card 10de,02fe rev a2 class 05,00,00 hdr 80
(II) PCI: 00:00:3: chip 10de,02f8 card 10de,02f8 rev a2 class 05,00,00 hdr 80
(II) PCI: 00:00:4: chip 10de,02f9 card 10de,02f9 rev a2 class 05,00,00 hdr 00
(II) PCI: 00:00:5: chip 10de,02ff card 10de,02ff rev a2 class 05,00,00 hdr 80
(II) PCI: 00:00:6: chip 10de,027f card 10de,027f rev a2 class 05,00,00 hdr 80
(II) PCI: 00:00:7: chip 10de,027e card 10de,027e rev a2 class 05,00,00 hdr 80
(II) PCI: 00:04:0: chip 10de,02fb card 0000,0000 rev a1 class 06,04,00 hdr 01
(II) PCI: 00:08:0: chip 10de,0369 card 1043,cb84 rev a1 class 05,00,00 hdr 00
(II) PCI: 00:09:0: chip 10de,0360 card 1043,cb84 rev a2 class 06,01,00 hdr 80
(II) PCI: 00:09:1: chip 10de,0368 card 1043,cb84 rev a2 class 0c,05,00 hdr 80
(II) PCI: 00:09:2: chip 10de,036a card 1043,cb84 rev a2 class 05,00,00 hdr 80
(II) PCI: 00:0a:0: chip 10de,036c card 1043,cb84 rev a1 class 0c,03,10 hdr 80
(II) PCI: 00:0a:1: chip 10de,036d card 1043,cb84 rev a2 class 0c,03,20 hdr 80
(II) PCI: 00:0c:0: chip 10de,036e card 1043,cb84 rev a1 class 01,01,8a hdr 00
(II) PCI: 00:0d:0: chip 10de,037f card 1043,cb84 rev a2 class 01,01,85 hdr 80
(II) PCI: 00:0d:1: chip 10de,037f card 1043,cb84 rev a2 class 01,01,85 hdr 80
(II) PCI: 00:0d:2: chip 10de,037f card 1043,cb84 rev a2 class 01,01,85 hdr 80
(II) PCI: 00:0e:0: chip 10de,0370 card 0000,0000 rev a2 class 06,04,01 hdr 81
(II) PCI: 00:0e:1: chip 10de,0371 card 1043,81f6 rev a2 class 04,03,00 hdr 80
(II) PCI: 00:10:0: chip 10de,0373 card 1043,cb84 rev a2 class 06,80,00 hdr 00
(II) PCI: 00:11:0: chip 10de,0373 card 1043,cb84 rev a2 class 06,80,00 hdr 00
(II) PCI: 00:16:0: chip 10de,0375 card 0000,0000 rev a2 class 06,04,00 hdr 01
(II) PCI: 00:18:0: chip 1022,1100 card 0000,0000 rev 00 class 06,00,00 hdr 80
(II) PCI: 00:18:1: chip 1022,1101 card 0000,0000 rev 00 class 06,00,00 hdr 80
(II) PCI: 00:18:2: chip 1022,1102 card 0000,0000 rev 00 class 06,00,00 hdr 80
(II) PCI: 00:18:3: chip 1022,1103 card 0000,0000 rev 00 class 06,00,00 hdr 80
(II) PCI: 01:00:0: chip 10de,0194 card 1682,2253 rev a2 class 03,00,00 hdr 00
(II) PCI: 02:0b:0: chip 104c,8023 card 1043,815b rev 00 class 0c,00,10 hdr 00
(II) PCI: 03:00:0: chip 1095,3132 card 1043,819f rev 01 class 01,80,00 hdr 00
(II) PCI: End of PCI scan
(II) PCI-to-PCI bridge:
(II) Bus 1: bridge is at (0:4:0), (0,1,1), BCTRL: 0x001c (VGA_EN is set)
(II) Bus 1 I/O range:
[0] -1 0 0x0000a000 - 0x0000a0ff (0x100) IX[B]
[1] -1 0 0x0000a400 - 0x0000a4ff (0x100) IX[B]
[2] -1 0 0x0000a800 - 0x0000a8ff (0x100) IX[B]
[3] -1 0 0x0000ac00 - 0x0000acff (0x100) IX[B]
(II) Bus 1 non-prefetchable memory range:
[0] -1 0 0xf8000000 - 0xfbffffff (0x4000000) MX[B]
(II) Bus 1 prefetchable memory range:
[0] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B]
(II) PCI-to-ISA bridge:
(II) Bus -1: bridge is at (0:9:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set)
(II) Subtractive PCI-to-PCI bridge:
(II) Bus 2: bridge is at (0:14:0), (0,2,2), BCTRL: 0x0a04 (VGA_EN is cleared)
(II) Bus 2 non-prefetchable memory range:
[0] -1 0 0xfdf00000 - 0xfdffffff (0x100000) MX[B]
(II) PCI-to-PCI bridge:
(II) Bus 3: bridge is at (0:22:0), (0,3,3), BCTRL: 0x0004 (VGA_EN is cleared)
(II) Bus 3 I/O range:
[0] -1 0 0x00009000 - 0x000090ff (0x100) IX[B]
[1] -1 0 0x00009400 - 0x000094ff (0x100) IX[B]
[2] -1 0 0x00009800 - 0x000098ff (0x100) IX[B]
[3] -1 0 0x00009c00 - 0x00009cff (0x100) IX[B]
(II) Bus 3 non-prefetchable memory range:
[0] -1 0 0xfde00000 - 0xfdefffff (0x100000) MX[B]
(II) Host-to-PCI bridge:
(II) Bus 0: bridge is at (0:24:0), (0,0,3), BCTRL: 0x0008 (VGA_EN is set)
(II) Bus 0 I/O range:
[0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) Bus 0 non-prefetchable memory range:
[0] -1 0 0x00000000 - 0xffffffff (0x100000000) MX[B]
(II) Bus 0 prefetchable memory range:
[0] -1 0 0x00000000 - 0xffffffff (0x100000000) MX[B]
(--) PCI:*(1:0:0) nVidia Corporation unknown chipset (0x0194) rev 162, Mem @ 0xfa000000/24, 0xe0000000/28, 0xf8000000/25, I/O @ 0xac00/7, BIOS @ 0xfbfe0000/17
(II) Addressable bus resource ranges are
[0] -1 0 0x00000000 - 0xffffffff (0x100000000) MX[B]
[1] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) OS-reported resource ranges:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[5] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
(II) Active PCI resource ranges:
[0] -1 0 0xfdef8000 - 0xfdefbfff (0x4000) MX[B]
[1] -1 0 0xfdeff000 - 0xfdeff07f (0x80) MX[B]
[2] -1 0 0xfdff8000 - 0xfdffbfff (0x4000) MX[B]
[3] -1 0 0xfdfff000 - 0xfdfff7ff (0x800) MX[B]
[4] -1 0 0xfe025000 - 0xfe02500f (0x10) MX[B]
[5] -1 0 0xfe026000 - 0xfe0260ff (0x100) MX[B]
[6] -1 0 0xfe027000 - 0xfe027fff (0x1000) MX[B]
[7] -1 0 0xfe028000 - 0xfe02800f (0x10) MX[B]
[8] -1 0 0xfe029000 - 0xfe0290ff (0x100) MX[B]
[9] -1 0 0xfe02a000 - 0xfe02afff (0x1000) MX[B]
[10] -1 0 0xfe020000 - 0xfe023fff (0x4000) MX[B]
[11] -1 0 0xfe02b000 - 0xfe02bfff (0x1000) MX[B]
[12] -1 0 0xfe02c000 - 0xfe02cfff (0x1000) MX[B]
[13] -1 0 0xfe02d000 - 0xfe02dfff (0x1000) MX[B]
[14] -1 0 0xfe02e000 - 0xfe02e0ff (0x100) MX[B]
[15] -1 0 0xfe02f000 - 0xfe02ffff (0x1000) MX[B]
[16] -1 0 0xfbfe0000 - 0xfbffffff (0x20000) MX[B](B)
[17] -1 0 0xf8000000 - 0xf9ffffff (0x2000000) MX[B](B)
[18] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B)
[19] -1 0 0xfa000000 - 0xfaffffff (0x1000000) MX[B](B)
[20] -1 0 0x00009c00 - 0x00009c7f (0x80) IX[B]
[21] -1 0 0x0000b000 - 0x0000b007 (0x8) IX[B]
[22] -1 0 0x0000b400 - 0x0000b407 (0x8) IX[B]
[23] -1 0 0x0000b800 - 0x0000b80f (0x10) IX[B]
[24] -1 0 0x0000bc00 - 0x0000bc03 (0x4) IX[B]
[25] -1 0 0x0000c000 - 0x0000c007 (0x8) IX[B]
[26] -1 0 0x0000c400 - 0x0000c403 (0x4) IX[B]
[27] -1 0 0x0000c800 - 0x0000c807 (0x8) IX[B]
[28] -1 0 0x0000cc00 - 0x0000cc0f (0x10) IX[B]
[29] -1 0 0x00000b60 - 0x00000b63 (0x4) IX[B]
[30] -1 0 0x00000960 - 0x00000967 (0x8) IX[B]
[31] -1 0 0x00000be0 - 0x00000be3 (0x4) IX[B]
[32] -1 0 0x000009e0 - 0x000009e7 (0x8) IX[B]
[33] -1 0 0x0000e000 - 0x0000e00f (0x10) IX[B]
[34] -1 0 0x00000b70 - 0x00000b73 (0x4) IX[B]
[35] -1 0 0x00000970 - 0x00000977 (0x8) IX[B]
[36] -1 0 0x00000bf0 - 0x00000bf3 (0x4) IX[B]
[37] -1 0 0x000009f0 - 0x000009f7 (0x8) IX[B]
[38] -1 0 0x0000f400 - 0x0000f40f (0x10) IX[B]
[39] -1 0 0x00001c40 - 0x00001c7f (0x40) IX[B]
[40] -1 0 0x00001c00 - 0x00001c3f (0x40) IX[B]
[41] -1 0 0x0000ac00 - 0x0000ac7f (0x80) IX[B](B)
(II) Active PCI resource ranges after removing overlaps:
[0] -1 0 0xfdef8000 - 0xfdefbfff (0x4000) MX[B]
[1] -1 0 0xfdeff000 - 0xfdeff07f (0x80) MX[B]
[2] -1 0 0xfdff8000 - 0xfdffbfff (0x4000) MX[B]
[3] -1 0 0xfdfff000 - 0xfdfff7ff (0x800) MX[B]
[4] -1 0 0xfe025000 - 0xfe02500f (0x10) MX[B]
[5] -1 0 0xfe026000 - 0xfe0260ff (0x100) MX[B]
[6] -1 0 0xfe027000 - 0xfe027fff (0x1000) MX[B]
[7] -1 0 0xfe028000 - 0xfe02800f (0x10) MX[B]
[8] -1 0 0xfe029000 - 0xfe0290ff (0x100) MX[B]
[9] -1 0 0xfe02a000 - 0xfe02afff (0x1000) MX[B]
[10] -1 0 0xfe020000 - 0xfe023fff (0x4000) MX[B]
[11] -1 0 0xfe02b000 - 0xfe02bfff (0x1000) MX[B]
[12] -1 0 0xfe02c000 - 0xfe02cfff (0x1000) MX[B]
[13] -1 0 0xfe02d000 - 0xfe02dfff (0x1000) MX[B]
[14] -1 0 0xfe02e000 - 0xfe02e0ff (0x100) MX[B]
[15] -1 0 0xfe02f000 - 0xfe02ffff (0x1000) MX[B]
[16] -1 0 0xfbfe0000 - 0xfbffffff (0x20000) MX[B](B)
[17] -1 0 0xf8000000 - 0xf9ffffff (0x2000000) MX[B](B)
[18] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B)
[19] -1 0 0xfa000000 - 0xfaffffff (0x1000000) MX[B](B)
[20] -1 0 0x00009c00 - 0x00009c7f (0x80) IX[B]
[21] -1 0 0x0000b000 - 0x0000b007 (0x8) IX[B]
[22] -1 0 0x0000b400 - 0x0000b407 (0x8) IX[B]
[23] -1 0 0x0000b800 - 0x0000b80f (0x10) IX[B]
[24] -1 0 0x0000bc00 - 0x0000bc03 (0x4) IX[B]
[25] -1 0 0x0000c000 - 0x0000c007 (0x8) IX[B]
[26] -1 0 0x0000c400 - 0x0000c403 (0x4) IX[B]
[27] -1 0 0x0000c800 - 0x0000c807 (0x8) IX[B]
[28] -1 0 0x0000cc00 - 0x0000cc0f (0x10) IX[B]
[29] -1 0 0x00000b60 - 0x00000b63 (0x4) IX[B]
[30] -1 0 0x00000960 - 0x00000967 (0x8) IX[B]
[31] -1 0 0x00000be0 - 0x00000be3 (0x4) IX[B]
[32] -1 0 0x000009e0 - 0x000009e7 (0x8) IX[B]
[33] -1 0 0x0000e000 - 0x0000e00f (0x10) IX[B]
[34] -1 0 0x00000b70 - 0x00000b73 (0x4) IX[B]
[35] -1 0 0x00000970 - 0x00000977 (0x8) IX[B]
[36] -1 0 0x00000bf0 - 0x00000bf3 (0x4) IX[B]
[37] -1 0 0x000009f0 - 0x000009f7 (0x8) IX[B]
[38] -1 0 0x0000f400 - 0x0000f40f (0x10) IX[B]
[39] -1 0 0x00001c40 - 0x00001c7f (0x40) IX[B]
[40] -1 0 0x00001c00 - 0x00001c3f (0x40) IX[B]
[41] -1 0 0x0000ac00 - 0x0000ac7f (0x80) IX[B](B)
(II) OS-reported resource ranges after removing overlaps with PCI:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[5] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
(II) All system resource ranges:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0xfdef8000 - 0xfdefbfff (0x4000) MX[B]
[5] -1 0 0xfdeff000 - 0xfdeff07f (0x80) MX[B]
[6] -1 0 0xfdff8000 - 0xfdffbfff (0x4000) MX[B]
[7] -1 0 0xfdfff000 - 0xfdfff7ff (0x800) MX[B]
[8] -1 0 0xfe025000 - 0xfe02500f (0x10) MX[B]
[9] -1 0 0xfe026000 - 0xfe0260ff (0x100) MX[B]
[10] -1 0 0xfe027000 - 0xfe027fff (0x1000) MX[B]
[11] -1 0 0xfe028000 - 0xfe02800f (0x10) MX[B]
[12] -1 0 0xfe029000 - 0xfe0290ff (0x100) MX[B]
[13] -1 0 0xfe02a000 - 0xfe02afff (0x1000) MX[B]
[14] -1 0 0xfe020000 - 0xfe023fff (0x4000) MX[B]
[15] -1 0 0xfe02b000 - 0xfe02bfff (0x1000) MX[B]
[16] -1 0 0xfe02c000 - 0xfe02cfff (0x1000) MX[B]
[17] -1 0 0xfe02d000 - 0xfe02dfff (0x1000) MX[B]
[18] -1 0 0xfe02e000 - 0xfe02e0ff (0x100) MX[B]
[19] -1 0 0xfe02f000 - 0xfe02ffff (0x1000) MX[B]
[20] -1 0 0xfbfe0000 - 0xfbffffff (0x20000) MX[B](B)
[21] -1 0 0xf8000000 - 0xf9ffffff (0x2000000) MX[B](B)
[22] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B)
[23] -1 0 0xfa000000 - 0xfaffffff (0x1000000) MX[B](B)
[24] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[25] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[26] -1 0 0x00009c00 - 0x00009c7f (0x80) IX[B]
[27] -1 0 0x0000b000 - 0x0000b007 (0x8) IX[B]
[28] -1 0 0x0000b400 - 0x0000b407 (0x8) IX[B]
[29] -1 0 0x0000b800 - 0x0000b80f (0x10) IX[B]
[30] -1 0 0x0000bc00 - 0x0000bc03 (0x4) IX[B]
[31] -1 0 0x0000c000 - 0x0000c007 (0x8) IX[B]
[32] -1 0 0x0000c400 - 0x0000c403 (0x4) IX[B]
[33] -1 0 0x0000c800 - 0x0000c807 (0x8) IX[B]
[34] -1 0 0x0000cc00 - 0x0000cc0f (0x10) IX[B]
[35] -1 0 0x00000b60 - 0x00000b63 (0x4) IX[B]
[36] -1 0 0x00000960 - 0x00000967 (0x8) IX[B]
[37] -1 0 0x00000be0 - 0x00000be3 (0x4) IX[B]
[38] -1 0 0x000009e0 - 0x000009e7 (0x8) IX[B]
[39] -1 0 0x0000e000 - 0x0000e00f (0x10) IX[B]
[40] -1 0 0x00000b70 - 0x00000b73 (0x4) IX[B]
[41] -1 0 0x00000970 - 0x00000977 (0x8) IX[B]
[42] -1 0 0x00000bf0 - 0x00000bf3 (0x4) IX[B]
[43] -1 0 0x000009f0 - 0x000009f7 (0x8) IX[B]
[44] -1 0 0x0000f400 - 0x0000f40f (0x10) IX[B]
[45] -1 0 0x00001c40 - 0x00001c7f (0x40) IX[B]
[46] -1 0 0x00001c00 - 0x00001c3f (0x40) IX[B]
[47] -1 0 0x0000ac00 - 0x0000ac7f (0x80) IX[B](B)
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.3
(II) Loading extension SHAPE
(II) Loading extension MIT-SUNDRY-NONSTANDARD
(II) Loading extension BIG-REQUESTS
(II) Loading extension SYNC
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XC-MISC
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-Misc
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension TOG-CUP
(II) Loading extension Extended-Visual-Information
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.3
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.1
(II) NVIDIA GLX Module 169.12 Thu Feb 14 18:34:02 PST 2008
(II) Loading extension GLX
(II) LoadModule: "freetype"
(II) Loading /usr/lib/xorg/modules//fonts/libfreetype.so
(II) Module freetype: vendor="X.Org Foundation & the After X-TT Project"
compiled for 1.3.0, module version = 2.1.0
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.5
(II) Loading font FreeType
(II) LoadModule: "record"
(II) Loading /usr/lib/xorg/modules/extensions//librecord.so
(II) Module record: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.13.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.3
(II) Loading extension RECORD
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.3
(II) Loading extension XFree86-DRI
(II) LoadModule: "nvidia"
(II) Loading /usr/lib/xorg/modules/drivers//nvidia_drv.so
(II) Module nvidia: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Video Driver
(II) LoadModule: "kbd"
(II) Loading /usr/lib/xorg/modules/input//kbd_drv.so
(II) Module kbd: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.2.1
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 0.7
(II) LoadModule: "mouse"
(II) Loading /usr/lib/xorg/modules/input//mouse_drv.so
(II) Module mouse: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.2.1
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 0.7
(II) NVIDIA dlloader X Driver 169.12 Thu Feb 14 17:53:48 PST 2008
(II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
(II) Primary Device is: PCI 01:00:0
(--) Assigning device section with no busID to primary device
(--) Chipset NVIDIA GPU found
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules//libfb.so
(II) Module fb: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.3
(II) Loading sub module "wfb"
(II) LoadModule: "wfb"
(II) Loading /usr/lib/xorg/modules//libwfb.so
(II) Module wfb: vendor="NVIDIA Corporation"
compiled for 7.1.99.2, module version = 1.0.0
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"(II) Module already built-in
(II) resource ranges after xf86ClaimFixedResources() call:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0xfdef8000 - 0xfdefbfff (0x4000) MX[B]
[5] -1 0 0xfdeff000 - 0xfdeff07f (0x80) MX[B]
[6] -1 0 0xfdff8000 - 0xfdffbfff (0x4000) MX[B]
[7] -1 0 0xfdfff000 - 0xfdfff7ff (0x800) MX[B]
[8] -1 0 0xfe025000 - 0xfe02500f (0x10) MX[B]
[9] -1 0 0xfe026000 - 0xfe0260ff (0x100) MX[B]
[10] -1 0 0xfe027000 - 0xfe027fff (0x1000) MX[B]
[11] -1 0 0xfe028000 - 0xfe02800f (0x10) MX[B]
[12] -1 0 0xfe029000 - 0xfe0290ff (0x100) MX[B]
[13] -1 0 0xfe02a000 - 0xfe02afff (0x1000) MX[B]
[14] -1 0 0xfe020000 - 0xfe023fff (0x4000) MX[B]
[15] -1 0 0xfe02b000 - 0xfe02bfff (0x1000) MX[B]
[16] -1 0 0xfe02c000 - 0xfe02cfff (0x1000) MX[B]
[17] -1 0 0xfe02d000 - 0xfe02dfff (0x1000) MX[B]
[18] -1 0 0xfe02e000 - 0xfe02e0ff (0x100) MX[B]
[19] -1 0 0xfe02f000 - 0xfe02ffff (0x1000) MX[B]
[20] -1 0 0xfbfe0000 - 0xfbffffff (0x20000) MX[B](B)
[21] -1 0 0xf8000000 - 0xf9ffffff (0x2000000) MX[B](B)
[22] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B)
[23] -1 0 0xfa000000 - 0xfaffffff (0x1000000) MX[B](B)
[24] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[25] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[26] -1 0 0x00009c00 - 0x00009c7f (0x80) IX[B]
[27] -1 0 0x0000b000 - 0x0000b007 (0x8) IX[B]
[28] -1 0 0x0000b400 - 0x0000b407 (0x8) IX[B]
[29] -1 0 0x0000b800 - 0x0000b80f (0x10) IX[B]
[30] -1 0 0x0000bc00 - 0x0000bc03 (0x4) IX[B]
[31] -1 0 0x0000c000 - 0x0000c007 (0x8) IX[B]
[32] -1 0 0x0000c400 - 0x0000c403 (0x4) IX[B]
[33] -1 0 0x0000c800 - 0x0000c807 (0x8) IX[B]
[34] -1 0 0x0000cc00 - 0x0000cc0f (0x10) IX[B]
[35] -1 0 0x00000b60 - 0x00000b63 (0x4) IX[B]
[36] -1 0 0x00000960 - 0x00000967 (0x8) IX[B]
[37] -1 0 0x00000be0 - 0x00000be3 (0x4) IX[B]
[38] -1 0 0x000009e0 - 0x000009e7 (0x8) IX[B]
[39] -1 0 0x0000e000 - 0x0000e00f (0x10) IX[B]
[40] -1 0 0x00000b70 - 0x00000b73 (0x4) IX[B]
[41] -1 0 0x00000970 - 0x00000977 (0x8) IX[B]
[42] -1 0 0x00000bf0 - 0x00000bf3 (0x4) IX[B]
[43] -1 0 0x000009f0 - 0x000009f7 (0x8) IX[B]
[44] -1 0 0x0000f400 - 0x0000f40f (0x10) IX[B]
[45] -1 0 0x00001c40 - 0x00001c7f (0x40) IX[B]
[46] -1 0 0x00001c00 - 0x00001c3f (0x40) IX[B]
[47] -1 0 0x0000ac00 - 0x0000ac7f (0x80) IX[B](B)
(II) resource ranges after probing:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0xfdef8000 - 0xfdefbfff (0x4000) MX[B]
[5] -1 0 0xfdeff000 - 0xfdeff07f (0x80) MX[B]
[6] -1 0 0xfdff8000 - 0xfdffbfff (0x4000) MX[B]
[7] -1 0 0xfdfff000 - 0xfdfff7ff (0x800) MX[B]
[8] -1 0 0xfe025000 - 0xfe02500f (0x10) MX[B]
[9] -1 0 0xfe026000 - 0xfe0260ff (0x100) MX[B]
[10] -1 0 0xfe027000 - 0xfe027fff (0x1000) MX[B]
[11] -1 0 0xfe028000 - 0xfe02800f (0x10) MX[B]
[12] -1 0 0xfe029000 - 0xfe0290ff (0x100) MX[B]
[13] -1 0 0xfe02a000 - 0xfe02afff (0x1000) MX[B]
[14] -1 0 0xfe020000 - 0xfe023fff (0x4000) MX[B]
[15] -1 0 0xfe02b000 - 0xfe02bfff (0x1000) MX[B]
[16] -1 0 0xfe02c000 - 0xfe02cfff (0x1000) MX[B]
[17] -1 0 0xfe02d000 - 0xfe02dfff (0x1000) MX[B]
[18] -1 0 0xfe02e000 - 0xfe02e0ff (0x100) MX[B]
[19] -1 0 0xfe02f000 - 0xfe02ffff (0x1000) MX[B]
[20] -1 0 0xfbfe0000 - 0xfbffffff (0x20000) MX[B](B)
[21] -1 0 0xf8000000 - 0xf9ffffff (0x2000000) MX[B](B)
[22] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B)
[23] -1 0 0xfa000000 - 0xfaffffff (0x1000000) MX[B](B)
[24] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B]
[25] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B]
[26] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B]
[27] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[28] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[29] -1 0 0x00009c00 - 0x00009c7f (0x80) IX[B]
[30] -1 0 0x0000b000 - 0x0000b007 (0x8) IX[B]
[31] -1 0 0x0000b400 - 0x0000b407 (0x8) IX[B]
[32] -1 0 0x0000b800 - 0x0000b80f (0x10) IX[B]
[33] -1 0 0x0000bc00 - 0x0000bc03 (0x4) IX[B]
[34] -1 0 0x0000c000 - 0x0000c007 (0x8) IX[B]
[35] -1 0 0x0000c400 - 0x0000c403 (0x4) IX[B]
[36] -1 0 0x0000c800 - 0x0000c807 (0x8) IX[B]
[37] -1 0 0x0000cc00 - 0x0000cc0f (0x10) IX[B]
[38] -1 0 0x00000b60 - 0x00000b63 (0x4) IX[B]
[39] -1 0 0x00000960 - 0x00000967 (0x8) IX[B]
[40] -1 0 0x00000be0 - 0x00000be3 (0x4) IX[B]
[41] -1 0 0x000009e0 - 0x000009e7 (0x8) IX[B]
[42] -1 0 0x0000e000 - 0x0000e00f (0x10) IX[B]
[43] -1 0 0x00000b70 - 0x00000b73 (0x4) IX[B]
[44] -1 0 0x00000970 - 0x00000977 (0x8) IX[B]
[45] -1 0 0x00000bf0 - 0x00000bf3 (0x4) IX[B]
[46] -1 0 0x000009f0 - 0x000009f7 (0x8) IX[B]
[47] -1 0 0x0000f400 - 0x0000f40f (0x10) IX[B]
[48] -1 0 0x00001c40 - 0x00001c7f (0x40) IX[B]
[49] -1 0 0x00001c00 - 0x00001c3f (0x40) IX[B]
[50] -1 0 0x0000ac00 - 0x0000ac7f (0x80) IX[B](B)
[51] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B]
[52] 0 0 0x000003c0 - 0x000003df (0x20) IS[B]
(II) Setting vga for screen 0.
(II) NVIDIA(0): Creating default Display subsection in Screen section
"Screen0" for depth/fbbpp 24/32
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(0): Option "TwinView" "1"
(**) NVIDIA(0): Option "MetaModes" "DFP-0: nvidia-auto-select +0+0, DFP-1: 1440x900 +1440+0; DFP-0: nvidia-auto-select +0+0, DFP-1: 1280x768 +1440+0; DFP-0: nvidia-auto-select +0+0, DFP-1: 1024x768 +1440+0"
(**) NVIDIA(0): Option "TwinViewXineramaInfoOrder" "DFP-0"
(**) NVIDIA(0): Enabling RENDER acceleration
(**) NVIDIA(0): TwinView enabled
(II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
(II) NVIDIA(0): enabled.
(II) NVIDIA(0): NVIDIA GPU GeForce 8800 Ultra (G80) at PCI:1:0:0 (GPU-0)
(--) NVIDIA(0): Memory: 786432 kBytes
(--) NVIDIA(0): VideoBIOS: 60.80.18.00.13
(II) NVIDIA(0): Detected PCI Express Link width: 16X
(--) NVIDIA(0): Interlaced video modes are supported on this GPU
(--) NVIDIA(0): Connected display device(s) on GeForce 8800 Ultra at
(--) NVIDIA(0): PCI:1:0:0:
(--) NVIDIA(0): Samsung SyncMaster (DFP-0)
(--) NVIDIA(0): Samsung SyncMaster (DFP-1)
(--) NVIDIA(0): Samsung SyncMaster (DFP-0): 330.0 MHz maximum pixel clock
(--) NVIDIA(0): Samsung SyncMaster (DFP-0): Internal Dual Link TMDS
(--) NVIDIA(0): Samsung SyncMaster (DFP-1): 330.0 MHz maximum pixel clock
(--) NVIDIA(0): Samsung SyncMaster (DFP-1): Internal Dual Link TMDS
(II) NVIDIA(0): Display Devices found referenced in MetaMode: DFP-0, DFP-1
(II) NVIDIA(0): Assigned Display Devices: DFP-0, DFP-1
(II) NVIDIA(0): Validated modes:
(II) NVIDIA(0): "DFP-0:nvidia-auto-select+0+0,DFP-1:1440x900+1440+0"
(II) NVIDIA(0): "DFP-0:nvidia-auto-select+0+0,DFP-1:1280x768+1440+0"
(II) NVIDIA(0): "DFP-0:nvidia-auto-select+0+0,DFP-1:1024x768+1440+0"
(II) NVIDIA(0): Virtual screen size determined to be 2880 x 900
(++) NVIDIA(0): DPI set to (100, 100); computed from -dpi X commandline option
(==) NVIDIA(0): Enabling 32-bit ARGB GLX visuals.
(--) Depth 24 pixmap format is 32 bpp
(II) do I need RAC? No, I don't.
(II) resource ranges after preInit:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0xfdef8000 - 0xfdefbfff (0x4000) MX[B]
[5] -1 0 0xfdeff000 - 0xfdeff07f (0x80) MX[B]
[6] -1 0 0xfdff8000 - 0xfdffbfff (0x4000) MX[B]
[7] -1 0 0xfdfff000 - 0xfdfff7ff (0x800) MX[B]
[8] -1 0 0xfe025000 - 0xfe02500f (0x10) MX[B]
[9] -1 0 0xfe026000 - 0xfe0260ff (0x100) MX[B]
[10] -1 0 0xfe027000 - 0xfe027fff (0x1000) MX[B]
[11] -1 0 0xfe028000 - 0xfe02800f (0x10) MX[B]
[12] -1 0 0xfe029000 - 0xfe0290ff (0x100) MX[B]
[13] -1 0 0xfe02a000 - 0xfe02afff (0x1000) MX[B]
[14] -1 0 0xfe020000 - 0xfe023fff (0x4000) MX[B]
[15] -1 0 0xfe02b000 - 0xfe02bfff (0x1000) MX[B]
[16] -1 0 0xfe02c000 - 0xfe02cfff (0x1000) MX[B]
[17] -1 0 0xfe02d000 - 0xfe02dfff (0x1000) MX[B]
[18] -1 0 0xfe02e000 - 0xfe02e0ff (0x100) MX[B]
[19] -1 0 0xfe02f000 - 0xfe02ffff (0x1000) MX[B]
[20] -1 0 0xfbfe0000 - 0xfbffffff (0x20000) MX[B](B)
[21] -1 0 0xf8000000 - 0xf9ffffff (0x2000000) MX[B](B)
[22] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B)
[23] -1 0 0xfa000000 - 0xfaffffff (0x1000000) MX[B](B)
[24] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B]
[25] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B]
[26] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B]
[27] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[28] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[29] -1 0 0x00009c00 - 0x00009c7f (0x80) IX[B]
[30] -1 0 0x0000b000 - 0x0000b007 (0x8) IX[B]
[31] -1 0 0x0000b400 - 0x0000b407 (0x8) IX[B]
[32] -1 0 0x0000b800 - 0x0000b80f (0x10) IX[B]
[33] -1 0 0x0000bc00 - 0x0000bc03 (0x4) IX[B]
[34] -1 0 0x0000c000 - 0x0000c007 (0x8) IX[B]
[35] -1 0 0x0000c400 - 0x0000c403 (0x4) IX[B]
[36] -1 0 0x0000c800 - 0x0000c807 (0x8) IX[B]
[37] -1 0 0x0000cc00 - 0x0000cc0f (0x10) IX[B]
[38] -1 0 0x00000b60 - 0x00000b63 (0x4) IX[B]
[39] -1 0 0x00000960 - 0x00000967 (0x8) IX[B]
[40] -1 0 0x00000be0 - 0x00000be3 (0x4) IX[B]
[41] -1 0 0x000009e0 - 0x000009e7 (0x8) IX[B]
[42] -1 0 0x0000e000 - 0x0000e00f (0x10) IX[B]
[43] -1 0 0x00000b70 - 0x00000b73 (0x4) IX[B]
[44] -1 0 0x00000970 - 0x00000977 (0x8) IX[B]
[45] -1 0 0x00000bf0 - 0x00000bf3 (0x4) IX[B]
[46] -1 0 0x000009f0 - 0x000009f7 (0x8) IX[B]
[47] -1 0 0x0000f400 - 0x0000f40f (0x10) IX[B]
[48] -1 0 0x00001c40 - 0x00001c7f (0x40) IX[B]
[49] -1 0 0x00001c00 - 0x00001c3f (0x40) IX[B]
[50] -1 0 0x0000ac00 - 0x0000ac7f (0x80) IX[B](B)
[51] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B]
[52] 0 0 0x000003c0 - 0x000003df (0x20) IS[B]
(II) NVIDIA(0): Initialized GPU GART.
(II) NVIDIA(0): Setting mode
(II) NVIDIA(0): "DFP-0:nvidia-auto-select+0+0,DFP-1:1440x900+1440+0"
(II) Loading extension NV-GLX
(II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
(II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
(==) NVIDIA(0): Backing store disabled
(==) NVIDIA(0): Silken mouse enabled
(II) Loading extension NV-CONTROL
(II) Loading extension XINERAMA
(==) RandR enabled
(II) Setting vga for screen 0.
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension XAccessControlExtension
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
(II) Initializing extension GLX
(**) Option "CoreKeyboard"
(**) Generic Keyboard: Core Keyboard
(**) Option "Protocol" "standard"
(**) Generic Keyboard: Protocol: standard
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xorg"
(**) Generic Keyboard: XkbRules: "xorg"
(**) Option "XkbModel" "pc105"
(**) Generic Keyboard: XkbModel: "pc105"
(**) Option "XkbLayout" "no"
(**) Generic Keyboard: XkbLayout: "no"
(**) Option "XkbOptions" "lv3:ralt_switch"
(**) Generic Keyboard: XkbOptions: "lv3:ralt_switch"
(**) Option "CustomKeycodes" "off"
(**) Generic Keyboard: CustomKeycodes disabled
(**) Option "Protocol" "evdev"
(EE) Configured Mouse: Unknown protocol "evdev"
(EE) PreInit failed for input device "Configured Mouse"
(II) UnloadModule: "mouse"
(EE) Configured Mouse: Unknown protocol "evdev"
(EE) PreInit failed for input device "Configured Mouse"
(II) UnloadModule: "mouse"
(WW) No core pointer registered
(II) XINPUT: Adding extended input device "Generic Keyboard" (type: KEYBOARD)
No core pointer

Fatal server error:
failed to initialize core devices



How to fix it?
I've done it before, but doesn't remember much except fixing /etc/X11/xorg.conf.

AnRkey
March 2nd, 2008, 11:38 AM
Hi everyone

I am sure by now that this mouse button issue is driving everyone nuts. Vote here http://brainstorm.ubuntu.com/idea/120/ for a mouse gui tool that already exists to be integrated into one of the next releases of Ubuntu.

And here is the launchpad listing for it >> https://bugs.launchpad.net/ubuntu/+bug/146160

AnRkey

Teura
March 8th, 2008, 11:49 PM
Ok, I have a problem with setting my MX900 mouse properly with this. Everytime I do this, my monitors gets messed up totally.

Normally, after Grub I get some blank screen and then login, but after I've done this change, first comes some text lines about boot, then Nvidia splash on both monitors, then same text, then again splash, and again text. It does this for a while, until it gives me the window about ubuntu running on low graphics mode on main monitor, second is not receiving image and is on standby
And imagelink to how I see it: http://koti.mbnet.fi/samikorh/Linux/low.jpg.


Then, using keyboard, as seeing the mouse is kinda hard when you need to press the buttons, I can get to desktop, which looks the same, http://koti.mbnet.fi/samikorh/Linux/desk.jpg.
Top half is totally messed up, and bottom left shows top right picture when bottom left shows top right.

So, is there any easy fix for this, or have I missed something?
The link to MX1000 configuring a few posts above didn't work even though the poster also said about graphics problems after this, it gives the same result. I've tried searching around forums, with no avail.

And some specs / files that might be of importance in solving.
C2D E6600, 2bg ddr2 800mhz, Geforce 8800 GTS 512 (169.09 drivers, installed with Envy), Sony G500 21" CRT (main) and LG 99G 19" CRT(2nd, configured as separate X-screens with Xinerama), MX900 mouse (the same as MX500, only with Bluetooth), Logitech cordless elite for Bluetooth keyboard and 7.10 Gutsy 64-bit version of Ubuntu

The result of cat /proc/bus/input/devices, with only mouse revelant data (first is keyboard as far as I know, I left it there in case I have indeed had them wrong)

I: Bus=0003 Vendor=046d Product=c703 Version=0110
N: Name="Logitech USB Receiver"
P: Phys=usb-0000:00:1d.0-2.1/input0
S: Sysfs=/class/input/input7
U: Uniq=14F65B
H: Handlers=kbd event2
B: EV=120003
B: KEY=1000000000007 ff800000000007ff febeffdfffefffff fffffffffffffffe
B: LED=1f

I: Bus=0003 Vendor=046d Product=c703 Version=0110
N: Name="Logitech USB Receiver"
P: Phys=usb-0000:00:1d.0-2.1/input1
S: Sysfs=/class/input/input8
U: Uniq=14F65B
H: Handlers=kbd mouse1 event3
B: EV=f
B: KEY=7fff002c3027 bf00444000000000 ff0001 f808837c000 667bfad941dfed 9e000000000000 0
B: REL=143
B: ABS=100000000

And what I have changed to the xorg.conf mouse section.

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "Protocol" "evdev"
Option "Dev Name" "Logitech USB Receiver"
Option "Dev Phys" "usb-0000:00:1d.0-2.1/input1"
Option "Device" "/dev/input/event3"
Option "Buttons" "10"
Option "ZAxisMapping" "4 5"
EndSection

If more details are needed, I'll happily post them.

geezerone
March 31st, 2008, 08:31 PM
The following gets nearly all buttons working on my MX510 with the exception of the glide (press wheel down into mouse) which is shown on xev as button 2. The configurable button doesn't do anything either but doesn't show up under xev.

Anyone got the glide (various speed up/down scroll) to work?

TIA :-k


Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "Resolution" "800"
Option "Buttons" "10"
Option "ZAxisMapping" "4 5"
Option "ButtonMapping" "1 2 3 6 7"
EndSection

geezerone
March 31st, 2008, 08:34 PM
Also the up arrow performs 'go back' function:confused:

orrie
March 31st, 2008, 08:51 PM
Adding the line below in bold font, does work excellent for me with MX518.



Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "ZAxisMapping" "4 5"
Option "ButtonMapping" "1 2 3 6 7"
Option "Emulate3Buttons" "true"
EndSection

AnRkey
April 1st, 2008, 06:54 AM
Hi every1

Just a reminder that all these problems can be fixed if we all vote for this idea on http://brainstorm.ubuntu.com

http://brainstorm.ubuntu.com/idea/120

Hopefully someone will pick it up and start working on it soon.

Thanks,

R

m1garand
July 9th, 2008, 06:46 AM
Why does my mouse in Hardy LiveCD work fine(scroll, back, forward)? And after installing Hardy, we have to go through all of this?

kiev
August 13th, 2008, 07:15 AM
If I add Option "Protocol" "evdev"
my usb mouse not work!

heelp!!!

Armaron
September 12th, 2008, 04:44 PM
If I add Option "Protocol" "evdev"
my usb mouse not work!

heelp!!!

Try:

Driver "evdev"

instead of the Option thing. Don't forget to put a # infront of the

Driver "mouse"

line.

EDIT -

On the mouse is a button that in windows is like Alt+Tab. How can I get that functionality back?

detyabozhye
September 14th, 2008, 06:01 AM
On the mouse is a button that in windows is like Alt+Tab. How can I get that functionality back?

You'll need a program with a window list and bind the button to the command for that. Xfce has one built in, it's xfdesktop -windowlist. Other DE's need a seperate program for that.

Armaron
September 15th, 2008, 08:30 AM
Ok, I seem to have a bit of an annoying problem on my hands.

Each time I restart, I need to go into the console and give the xorg.conf file the right event handler for my mouse. I haven't gotten it to work automatically so that the X server knows which event is my mouse. Any idea's on how to do it?

P.S. detya, do you know a program to do that for ubuntu with the gnome desktop? I'd rather not switch to the Xfce desktop. :)

detyabozhye
September 17th, 2008, 07:32 PM
Ok, I seem to have a bit of an annoying problem on my hands.

Each time I restart, I need to go into the console and give the xorg.conf file the right event handler for my mouse. I haven't gotten it to work automatically so that the X server knows which event is my mouse. Any idea's on how to do it?

P.S. detya, do you know a program to do that for ubuntu with the gnome desktop? I'd rather not switch to the Xfce desktop. :)

You can use udev, but this thread is very old and the method of setting up the mouse has long since changed. If you click to see the thread in my signiture, somewhere towards the end of it people talk about the new way of configuring it. For example, my current set up is:


Section "InputDevice"
Identifier "Configured Mouse"
Driver "evdev"
Option "Device" "/dev/input/by-id/usb-Logitech_USB-PS.2_Optical_Mouse-event-mouse"
EndSection

reg4c
October 8th, 2008, 06:53 AM
Excellent

I used the xbindkeys with --keys thing to make the nautilus for forward and backwards with SHIFT MOUSE DOWN and SHIFT MOUSE UP

Thanks a lot

BassKozz
November 5th, 2008, 05:09 AM
I am having a hellava time getting my Mx500 working in Intrepid, this seems like the right place to post, but I feel this information is a bit dated since Input Devices aren't handled by Xorg.conf anymore but instead by HAL...
I've already posted a whole novel on my research thus far in another thread, so rather then repost it all here, I hope you don't mind me linking to it: Mouse Wheel Broken in Intrepid (http://ubuntuforums.org/showthread.php?t=970711)

If anyone can help PLEASE [-o<

http://brainstorm.ubuntu.com/idea/120/image/1/ (http://brainstorm.ubuntu.com/idea/120/)

jimgeroul
November 10th, 2008, 11:43 AM
I have the "Trust MI7700R wireless laser" mouse witch has 8 buttons.
4 wheel buttons (up, down, left, right) - WORKING
2 side buttons (thumb1, thumb2) - WORKING
2 media buttons (for zoom in-out) - NOT WORKING

why i can't have these 2 buttons enabled??
Button Mapping for them should be "button 10" and "button 11" but they are not even recognized from xev. everything else works perfectly by default (ubuntu 8.10 intrepid).

What can i do?? can i enable them?

detyabozhye
November 11th, 2008, 06:41 AM
@BassKozz: @jimgeroul: What do you get in xev for all the buttons?

jimgeroul
November 11th, 2008, 01:02 PM
this is what i get when i press all mouse buttons. As you will see all button except buttons 10,11 have an "entry". When i press button 10 or 11 nothing happens, nothing is changing :(


KeymapNotify event, serial 34, synthetic NO, window 0x0,
keys: 62 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

ButtonRelease event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x3400002, time 5006722, (33,25), root:(584,427),
state 0x110, button 1, same_screen YES

LeaveNotify event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x0, time 5006722, (33,25), root:(584,427),
mode NotifyUngrab, detail NotifyInferior, same_screen YES,
focus YES, state 16

ButtonPress event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x3400002, time 5007428, (33,25), root:(584,427),
state 0x10, button 3, same_screen YES

EnterNotify event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x0, time 5007428, (33,25), root:(584,427),
mode NotifyGrab, detail NotifyInferior, same_screen YES,
focus YES, state 1040

KeymapNotify event, serial 34, synthetic NO, window 0x0,
keys: 4294967206 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

ButtonRelease event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x3400002, time 5007474, (33,25), root:(584,427),
state 0x410, button 3, same_screen YES

LeaveNotify event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x0, time 5007474, (33,25), root:(584,427),
mode NotifyUngrab, detail NotifyInferior, same_screen YES,
focus YES, state 16

MotionNotify event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x3400002, time 5008554, (31,26), root:(582,428),
state 0x10, is_hint 0, same_screen YES

MotionNotify event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x3400002, time 5008562, (30,27), root:(581,429),
state 0x10, is_hint 0, same_screen YES

MotionNotify event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x3400002, time 5008570, (29,27), root:(580,429),
state 0x10, is_hint 0, same_screen YES

MotionNotify event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x3400002, time 5008578, (28,27), root:(579,429),
state 0x10, is_hint 0, same_screen YES

MotionNotify event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x3400002, time 5008586, (28,28), root:(579,430),
state 0x10, is_hint 0, same_screen YES

ButtonPress event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x3400002, time 5010394, (28,28), root:(579,430),
state 0x10, button 2, same_screen YES

EnterNotify event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x0, time 5010394, (28,28), root:(579,430),
mode NotifyGrab, detail NotifyInferior, same_screen YES,
focus YES, state 528

KeymapNotify event, serial 34, synthetic NO, window 0x0,
keys: 4294967206 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

ButtonRelease event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x3400002, time 5010578, (28,28), root:(579,430),
state 0x210, button 2, same_screen YES

LeaveNotify event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x0, time 5010578, (28,28), root:(579,430),
mode NotifyUngrab, detail NotifyInferior, same_screen YES,
focus YES, state 16

LeaveNotify event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x3400002, time 5012466, (28,28), root:(579,430),
mode NotifyGrab, detail NotifyVirtual, same_screen YES,
focus YES, state 2064

EnterNotify event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x3400002, time 5012466, (28,28), root:(579,430),
mode NotifyUngrab, detail NotifyVirtual, same_screen YES,
focus YES, state 16

KeymapNotify event, serial 34, synthetic NO, window 0x0,
keys: 4294967206 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

ButtonPress event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x3400002, time 5012467, (28,28), root:(579,430),
state 0x10, button 4, same_screen YES

EnterNotify event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x0, time 5012467, (28,28), root:(579,430),
mode NotifyGrab, detail NotifyInferior, same_screen YES,
focus YES, state 2064

KeymapNotify event, serial 34, synthetic NO, window 0x0,
keys: 4294967206 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

ButtonRelease event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x3400002, time 5012467, (28,28), root:(579,430),
state 0x810, button 4, same_screen YES

LeaveNotify event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x0, time 5012467, (28,28), root:(579,430),
mode NotifyUngrab, detail NotifyInferior, same_screen YES,
focus YES, state 16

LeaveNotify event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x3400002, time 5013114, (28,28), root:(579,430),
mode NotifyGrab, detail NotifyVirtual, same_screen YES,
focus YES, state 4112

EnterNotify event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x3400002, time 5013114, (28,28), root:(579,430),
mode NotifyUngrab, detail NotifyVirtual, same_screen YES,
focus YES, state 16

KeymapNotify event, serial 34, synthetic NO, window 0x0,
keys: 4294967206 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

ButtonPress event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x3400002, time 5013115, (28,28), root:(579,430),
state 0x10, button 5, same_screen YES

EnterNotify event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x0, time 5013115, (28,28), root:(579,430),
mode NotifyGrab, detail NotifyInferior, same_screen YES,
focus YES, state 4112

KeymapNotify event, serial 34, synthetic NO, window 0x0,
keys: 4294967206 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

ButtonRelease event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x3400002, time 5013115, (28,28), root:(579,430),
state 0x1010, button 5, same_screen YES

LeaveNotify event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x0, time 5013115, (28,28), root:(579,430),
mode NotifyUngrab, detail NotifyInferior, same_screen YES,
focus YES, state 16

LeaveNotify event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x3400002, time 5013850, (28,28), root:(579,430),
mode NotifyGrab, detail NotifyVirtual, same_screen YES,
focus YES, state 16

EnterNotify event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x3400002, time 5013850, (28,28), root:(579,430),
mode NotifyUngrab, detail NotifyVirtual, same_screen YES,
focus YES, state 16

KeymapNotify event, serial 34, synthetic NO, window 0x0,
keys: 4294967206 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

ButtonPress event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x3400002, time 5013851, (28,28), root:(579,430),
state 0x10, button 6, same_screen YES

EnterNotify event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x0, time 5013851, (28,28), root:(579,430),
mode NotifyGrab, detail NotifyInferior, same_screen YES,
focus YES, state 16

KeymapNotify event, serial 34, synthetic NO, window 0x0,
keys: 4294967206 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

ButtonRelease event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x3400002, time 5013851, (28,28), root:(579,430),
state 0x10, button 6, same_screen YES

LeaveNotify event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x0, time 5013851, (28,28), root:(579,430),
mode NotifyUngrab, detail NotifyInferior, same_screen YES,
focus YES, state 16

LeaveNotify event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x3400002, time 5014578, (28,28), root:(579,430),
mode NotifyGrab, detail NotifyVirtual, same_screen YES,
focus YES, state 16

EnterNotify event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x3400002, time 5014578, (28,28), root:(579,430),
mode NotifyUngrab, detail NotifyVirtual, same_screen YES,
focus YES, state 16

KeymapNotify event, serial 34, synthetic NO, window 0x0,
keys: 4294967206 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

ButtonPress event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x3400002, time 5014579, (28,28), root:(579,430),
state 0x10, button 7, same_screen YES

EnterNotify event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x0, time 5014579, (28,28), root:(579,430),
mode NotifyGrab, detail NotifyInferior, same_screen YES,
focus YES, state 16

KeymapNotify event, serial 34, synthetic NO, window 0x0,
keys: 4294967206 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

ButtonRelease event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x3400002, time 5014579, (28,28), root:(579,430),
state 0x10, button 7, same_screen YES

LeaveNotify event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x0, time 5014579, (28,28), root:(579,430),
mode NotifyUngrab, detail NotifyInferior, same_screen YES,
focus YES, state 16

MotionNotify event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x3400002, time 5014762, (27,28), root:(578,430),
state 0x10, is_hint 0, same_screen YES

LeaveNotify event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x3400002, time 5014794, (27,28), root:(578,430),
mode NotifyGrab, detail NotifyVirtual, same_screen YES,
focus YES, state 16

EnterNotify event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x3400002, time 5014794, (27,28), root:(578,430),
mode NotifyUngrab, detail NotifyVirtual, same_screen YES,
focus YES, state 16

KeymapNotify event, serial 34, synthetic NO, window 0x0,
keys: 4294967206 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

ButtonPress event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x3400002, time 5014802, (27,28), root:(578,430),
state 0x10, button 7, same_screen YES

EnterNotify event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x0, time 5014802, (27,28), root:(578,430),
mode NotifyGrab, detail NotifyInferior, same_screen YES,
focus YES, state 16

KeymapNotify event, serial 34, synthetic NO, window 0x0,
keys: 4294967206 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

ButtonRelease event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x3400002, time 5014803, (27,28), root:(578,430),
state 0x10, button 7, same_screen YES

LeaveNotify event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x0, time 5014803, (27,28), root:(578,430),
mode NotifyUngrab, detail NotifyInferior, same_screen YES,
focus YES, state 16

LeaveNotify event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x3400002, time 5016634, (27,28), root:(578,430),
mode NotifyGrab, detail NotifyVirtual, same_screen YES,
focus YES, state 16

EnterNotify event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x3400002, time 5016635, (27,28), root:(578,430),
mode NotifyUngrab, detail NotifyVirtual, same_screen YES,
focus YES, state 16

KeymapNotify event, serial 34, synthetic NO, window 0x0,
keys: 4294967206 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

ButtonPress event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x3400002, time 5016636, (27,28), root:(578,430),
state 0x10, button 8, same_screen YES

EnterNotify event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x0, time 5016636, (27,28), root:(578,430),
mode NotifyGrab, detail NotifyInferior, same_screen YES,
focus YES, state 16

KeymapNotify event, serial 34, synthetic NO, window 0x0,
keys: 4294967206 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

ButtonRelease event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x3400002, time 5016637, (27,28), root:(578,430),
state 0x10, button 8, same_screen YES

LeaveNotify event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x0, time 5016637, (27,28), root:(578,430),
mode NotifyUngrab, detail NotifyInferior, same_screen YES,
focus YES, state 16

ButtonRelease event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x3400002, time 5016810, (27,28), root:(578,430),
state 0x10, button 8, same_screen YES

LeaveNotify event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x3400002, time 5017322, (27,28), root:(578,430),
mode NotifyGrab, detail NotifyVirtual, same_screen YES,
focus YES, state 16

EnterNotify event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x3400002, time 5017323, (27,28), root:(578,430),
mode NotifyUngrab, detail NotifyVirtual, same_screen YES,
focus YES, state 16

KeymapNotify event, serial 34, synthetic NO, window 0x0,
keys: 4294967206 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

ButtonPress event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x3400002, time 5017324, (27,28), root:(578,430),
state 0x10, button 9, same_screen YES

EnterNotify event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x0, time 5017324, (27,28), root:(578,430),
mode NotifyGrab, detail NotifyInferior, same_screen YES,
focus YES, state 16

KeymapNotify event, serial 34, synthetic NO, window 0x0,
keys: 4294967206 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

ButtonRelease event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x3400002, time 5017324, (27,28), root:(578,430),
state 0x10, button 9, same_screen YES

LeaveNotify event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x0, time 5017324, (27,28), root:(578,430),
mode NotifyUngrab, detail NotifyInferior, same_screen YES,
focus YES, state 16

ButtonRelease event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x3400002, time 5017514, (27,28), root:(578,430),
state 0x10, button 9, same_screen YES

detyabozhye
November 11th, 2008, 08:36 PM
@jimgeroul: try installing lomoco and try turning on/off the cruise control: http://manpages.ubuntu.com/manpages/gutsy/man1/lomoco.html That might have some effect on the media buttons.

Edit: Then again, it might not work since that's not a Logitech mouse.

jimgeroul
November 13th, 2008, 01:23 PM
I installed lomoco and made the changes you said but nothing... maybe my Trust mouse is not 100% supported and there is nothing i can do.
Thanks for you help though!

carthage
January 2nd, 2009, 10:37 PM
thank u so much it worked for me http://ubuntuforums.org/images/smilies/icon_biggrin.gif

Dirtneck
March 20th, 2009, 06:15 AM
Specific requirement: assign a modifier to a thumb button

I'm trying to configure the thumb/side buttons of a Logitech MX620 to work as I need. I play WoW and want to assign a modifier only to those buttons (pressing the backward thumb button should work the same as holding shift on the keyboard)

The reason this poses a problem:

The thumb buttons do not perform the same as other buttons like Mouse button 1.

Using xev:

Example using Mouse Button 1:
1) I press mouse button 1
2) the keydown event is triggered
3) I release mouse button 1
4) the keyup event is triggered



Example using a thumb button:
1) I press a thumb button
2) the keydown event is triggered AND immediately the keyup event also triggers
3) I release mouse button 1
4) n/a

So in my attempt to emulate a shift modifier, if I assigned 'Shift_L' to the thumb button I would expect to press the thumb button and then press a letter on the keyboard and I should get an uppercase letter printed. However, what actually happens with those actions is Shift_L gets pressed and depressed and then the letter is printed without the modifier.

I know this is not a mechanical limitation of the buttons as it those buttons can indeed work the way I need in windows using logitech product software.

Note: I haven't tried to get the mentioned app working with wine yet but really dont want to resort to that anyways.

I don't know if xmodmap would resolve my issue but hopefully someone with a full understanding of it could reply. As of right now, modmap is the blind direction I'll be taking.



Here's my Xbindkeysrc which I'm pretty sure has no bearing but might help:



# Logitech Custom Mouse buttons [MX620]:
# ================================================== =============================================
# 1) Left Click
# 2) Middle Mouse Button
# 3) Right Click
# 4) Scroll Up
# 5) Scroll Down
# 6) Wheel L-Tilt
# 7) Wheel R-Tilt
# 8) Side-Backward
# 9) Side-Forward
# 10) Search Button ???


# ================================================== ============================================
# ----------------------------------------------------------------- Left-Side Buttons ----------
# --> Logitech Fwd
"/usr/bin/xte 'key Alt_R' &"
m:0x0 + b:9 # Forward

# --> Logitech Bck
"/usr/bin/xte 'key Shift_R' &"
m:0x0 + b:8 # Backward
# ================================================== ============================================


# ================================================== ============================================
# --------------------------------------------------------------- Mouse Wheel Tilting ----------
# --> Logitech L-Tilt
"/usr/bin/xte 'keydown Alt_R' 'keydown Shift_R' 'key K' 'keyup Shift_R' 'keyup Alt_R' &"
m:0x0 + b:6 # Left Tilt = Shift+Alt+R

# --> Logitech R-Tilt
"/usr/bin/xte 'keydown Alt_R' 'keydown Shift_R' 'key L' 'keyup Shift_R' 'keyup Alt_R' &"
m:0x0 + b:7 # Right Tilt = Shift+Alt+L
# ================================================== ============================================


# ================================================== =============================================
# Zboard Custom Keys:
# ================================================== =============================================

# --> Zboard Pause Key
"/usr/bin/xte 'keydown Alt_R' 'keydown Shift_R' 'key P' 'keyup Shift_R' 'keyup Alt_R' &"
m:0x10 + c:127
Mod2 + Pause # Gaming pad; Pause key
# --> Zboard Cons Key
"/usr/bin/xte 'keydown Alt_R' 'keydown Shift_R' 'key O' 'keyup Shift_R' 'keyup Alt_R' &"
m:0x10 + c:49
Mod2 + grave # Gaming pad; Cons key
# ================================================== ============================================

Dirtneck
March 20th, 2009, 06:23 AM
BTW: I've noticed in this thread that people have problems getting any event to work in xbindkeys.

Check that xbindkeys is successfully running


1) Make sure xbindkeys process is stopped or you wont be able to save the xbindkeysrc file.
2) attempting to start xbindkeys may fail on syntax errors in the xbindkeysrc file.
3) check to see if there's any other listener processes running that inhibit xbindkeys from starting: run xbindkeys -v to see if it starts ok... It will complain if xbindkeys is already started or if there's another event listener causing trouble.

dnquark
July 22nd, 2009, 04:05 AM
I am having trouble remapping the one-touch search button on Logitech MX Revolution (apparently it generates keycode 225). I tried to edit xmodmap to remove the XF86Search binding from keycode 225, and it's no longer there; then I tried to use xbindkeys with xmacro to issue some alternative keypresses for keycode 225, but nothing seems to work - the search button still brings up the search dialog! Does anyone have a fix?..

expxe
November 26th, 2009, 05:15 AM
OMG, is there a simple install program to do all of this? lets keep it simple people!

detyabozhye
November 26th, 2009, 06:26 PM
Most of it actually works out of the box now. This tutorial is a few years old and shouldn't keep getting bumped anymore.

expxe
November 29th, 2009, 04:29 AM
Most of it actually works out of the box now. This tutorial is a few years old and shouldn't keep getting bumped anymore.

my logitech mx rev doesn't exactly "work out of the box", ubuntu needs proper mouse drivers from logitech really