for me dosn't work. Please help me!
Printable View
for me dosn't work. Please help me!
hello
Its don't work for me in Feisty
this udev is that really necessary in Fiesty
So, after struggling to figure out what the udev code was saying, I stumbled upon a bit of an issue. The reason the udev assignment works is that linux creates event0 through event9 no matter how many devices are plugged in. However, I have more than 10 devices, meaning event9 is occupied. The obvious fix would be to reassign the udev rule to event15, but event15 isn't by default created -- enough for each device over event9. How can I make linux create an event15 by default on boot?
hi,
this is my first nip from the ubuntu cup. And yes, i´m impressed :)
Thanks to this thread, i did figure out how to get my Revo fully featured in Feisty.
I´ve written a german howto for kubuntu 7.04 which is based on this one.
BIg thanks to daou and knn!
If somebody is interested in translating mine to help out those struggling Feisty users, who don´t know german - please feel free to do so.
My english is´nt good enough to turn it into something helpful, i think.
You can read it --> here (i´m mddn there)
coredix
Nice work. Just a small correction: In this line:
You should replace "Vendor=046d Product=c51a" with whatever your mouse's product id is. (the vendor id should remain the same, since they're all Logitech, but you could use this for other mice as well. The product id is different for the vx revo). The product id's can be found in the first post, but you can also runCode:eventname=$(cat /proc/bus/input/devices | grep "Vendor=046d Product=c51a" -A 4 | grep "Handlers=mouse" | sed "s/.*\(event.\).*/\1/")
and check there (my Revo's version was different than the version posted in the first post, so I did not include a version check)Code:cat /proc/bus/input/devices
Perhaps you could try my simlink trick (previous post), and change event9 to event15 in it. You won't need udev at all then.Quote:
So, after struggling to figure out what the udev code was saying, I stumbled upon a bit of an issue. The reason the udev assignment works is that linux creates event0 through event9 no matter how many devices are plugged in. However, I have more than 10 devices, meaning event9 is occupied. The obvious fix would be to reassign the udev rule to event15, but event15 isn't by default created -- enough for each device over event9. How can I make linux create an event15 by default on boot?
Thx for the correction, there is a completely new version of my howto online now.
Pls take look here.
I can confirm that. event15 works fine for me, no need for udev.
Some posts before there was a need for a quick taskselectionbox one can get with a mousebutton.
There is a simple way to put this function on the searchbutton. A description is in my howto near the end,
Maybe someone can translate it and post it here ;)
coredix
For me the VX Rev doesn't work in Feisty anymore.. The X won't start unless I remove the parts about the the VX in xorg.conf. Anyone else got the problem?
Hi,
Sorry for not checking up on the thread and replying for a while. I've been very busy this spring hacking away at the Linux based Nokia 770 for a uni project. Now I'm working at an embedded solutions company doing Linux and electronics work. That should be incentive enough for anyone to learn some Linux ;)!
I just started working on a program today that reroutes events from the MX Revo through uinput back to X as keyboard events (or any events for that matter). Basically this means no more pulling hairs with evdev, udev, xorg.conf, xvkbd, xbindkeys, and mousekeys. I don't know about everyone else, but I got tired of it, especially after the Feisty upgrade.
Basic functionality is already working. My free time is quite limited, but once I get the program polished up enough, I'll post about it here for anyone interested.
The first release of the program is done. I've posted instructions at the top of the how to. Let me know if there are any problems.
And I would appreciate it if a VX user could test the program. If it doesn't work, then someone with a VX needs to do some hexdumping on an event handler.
Hi Daou!
Man...someone finally comes up with this nifty program....getting your mousebuttons to
work decently is (stupidly enough) soo much work in (k)ubuntu...i couldn't believe it at first.
I own a logitech G5 mouse now, which is an excellent mouse aswell.
I've installed your program and it does well....nothing ;-)
im pretty sure this is due to the fact that my mouse sends out what you call rawcodes in
your program that i haven't configured yet.
Can you tell me how i can lookup what the rawcodes are for my mouse? (i think it's xev)
xev tells me this when i push my scrollwheel:
ButtonPress event, serial 31, synthetic NO, window 0x3e00001,
root 0x137, subw 0x0, time 7753479, (120,113), root: (123,301),
state 0x10, button 2, same_screen YES
ButtonRelease event, serial 31, synthetic NO, window 0x3e00001,
root 0x137, subw 0x0, time 7753646, (120,113), root: (123,301),
state 0x210, button 2, same_screen YES
only thing i can imagine is the 'state 0x..." code that changes but i entered that in your config file, doesn't work.
I want to bind the keyboard 'L' key to pressing my mousewheel for in game usage.
Can i use xev's output (and what part) to make it work with your program you think?
I'm willing to test anything you want and givefeeback in order to make your program more universal.
I think (k)ubuntu needs this program bad as this is one the things that is withholding me from
ditching windows all together!
(k)ubuntu rocks!