You are not logged in.
mmm yes but the horizontal scroll on a seveninchesdisplay is a smart tool
and, i bougth vx yesterday, i cannot accept to have an half mouse at a duble price ![]()
Offline
I'm totally with you, but my previous attempt at editing xorg.conf ended up in tears. I'm no longer young enough to be happy with something that breaks so easily (oh, the misspent youth...). :-(
As I said, I'll try running xev in the hope of catching as many buttons as possible, then using kbindkeys to enable them. Sounds much less risky...
BTW, I successfully rationalised the purchase by using the VX on all three of my laptops, some of which run XP. ;-)
Offline
I have been seriously considering getting an EEE for some time now and have been skimming the forums on everything from grafting a 1.8" to the mobo to SDHC problems to different OS installations and now this. This info is fascinating to me guys, thanks for all of it. Sorry the off topic babble.
I would like to use this mouse(i have researched it before:) with linux but if this thing can't be mastered thats a problem, something so simple that would make web surfing much more efficient. I guess just booting from XP on an external hard drive would be OK. But man am I sick of Windows.
Offline
I have just tried xev and it seems the only buttons not visible out of the box are left and right tilt of the scroll wheel. These I don't really care about as I think they are too fiddly (I struggle to make that finger move, but YMMV).
Now it's only a matter of binding the buttons to actions in KDE, so I'm happy...
Offline
yes the modify to xorg.conf make the tilt buttons availables
Offline
if it works then can someone add the steps to the wiki?
Offline
Compared to everything else I see here, this is kind of a dumb question. My VX Nano works fine (no hacks, no editing of config files, no attempt to side scroll yet, etc.), except that when I unplug the USB dongle, the touchpad no longer functions. I have rebooted without VX dongle and I have used a paperclip to reset (not sure when to do the reset - while on, off, or what?). Although I will be using the Eee with VX most of the time, there are times when I won't have the VX with me.
Anyone know what to do to reactivate the touchscreen?
Thanks,
Bob
Offline
The main reason I wanted to program the extra buttons on the VX Nano was for sideways scrolling. That may be easier than I thought:
HOWTO: Logitech MX Revolution in Dapper - Ubuntu Forums
ubuntuforums.org/showthread.php?t=277388
Note created December 4, 2007
12/4/07
Mouse wheel tilt for horizontal scrolling
This tip is used to switch the mouse wheel tilt function to horizontal scroll in Firefox. Thanks to knn for suggesting this tip.
1. Go to about:config by typing "about:config" in the URL field of Firefox.
2. Set mousewheel.horizscroll.withnokey.action "Value" field to 0. NOTE: If you've swapped the wheel tilt buttons as described in the "Switch mouse wheel tilt functions" tip above, the direction will be reversed. In this case, change mousewheel.horizscroll.withnokey.numlines "Value" to 1.
___
got this info from a link tek43 provided. thanks tek43!
Offline
But you can configure firefox only if the horizontal buttons work
I have found some new problems unplugging the wi receiver with opzion "CorePointer" ,
this problem go away with "SendCoreEvents" but the mouse has the horizontal buttons inverted and xmodmap do nothing in this case...
Offline
First of all :Sorry for the bad english!
If you watch you can see a long text but it isn't a long work..if works ![]()
Please someone of you try/test this and confirm that it works.
This is what i have done to have a vx working (untill i don't find new problem
(maybe not) )
First :
ctrl+alt+t
sudo apt-get update sudo apt-get install xserver-xorg-input-evdev cd /etc/X11/ cp xorg.conf xorgb.conf cat /proc/bus/input/devices
I search for this :
I: Bus=0003 Vendor=046d Product=c521 Version=0111 N: Name="Logitech USB Receiver" P: Phys=usb-0000:00:1d.0-2/input0 S: Sysfs=/class/input/input6 H: Handlers=mouse1 event6 B: EV=7 B: KEY=ffff0000 0 0 0 0 0 0 0 0 B: REL=143
and wrote on a piceofpaper event6 (H: Handlers=mouse1 event6)
Then :
ctrl+alt+t
cd /etc/X11/
sudo nano xorg.confhere i change :
Section "ServerLayout"
Identifier "Xandros"
Screen 0 "Screen1"
InputDevice "keyboard"
InputDevice "mouse"
InputDevice "synaptics"
EndSectionTO :
Section "ServerLayout"
Identifier "Xandros"
Screen 0 "Screen1"
InputDevice "keyboard"
InputDevice "mouse"
InputDevice "synaptics" "CorePointer"
EndSectionThe mouse section from :
Section "InputDevice"
Identifier "mouse"
Driver "mouse"
Option "Device" "/dev/input/mice"
Option "Protocol" "IMPS/2"
Option "Emulate3Buttons" "yes"
Option "ZAxisMapping" "4 5"
Option "CorePointer"
EndSectionTO :
Section "InputDevice"
Identifier "mouse"
Driver "evdev"
Option "Device" "/dev/input/event6"
Option "Protocol" "evdev"
Option "Buttons" "9"
Option "SendCoreEvents"
Option "HWHEELRelativeAxisButtons" "7 6"
EndSectionI put a # in front of
Option "SendCoreEvents" "yes"
under the input device synaptic
Now all my buttons works and if i unplug the receiver all work fine.
Then i set the left 2 buttons using xbindkeys:
sudo apt-get install xbindkeys
and i put :
"xvkbd -xsendevent -text "\[Alt_L]\[Left]"" m:0x10 + b:9 "xvkbd -xsendevent -text "\[Alt_L]\[Right]"" m:0x10 + b:10
into .xbindkeysrc file created in /home/user/
I don-t know if it still works for you, i hope so.
PS: if some problem occurs and the SO don't want to restart do this:
on booting(on the first screen) press f9, in the new screen select normal boot , and press "e"
on the next screen select line starting with "kernel" and press "e"
at the end of the line write XANDROSBOOTDEBUG=y, press enter
press "b"
Here type :
mount /dev/sda2 /mnt-user cd /mnt-user/etc/X11 rm xorg.conf cp xorgb.conf xorg.conf exit
enter
And you are at the start point...
Last edited by tek43 (2007-12-06 1:39:31 pm)
Offline
tek43 wrote:
But you can configure firefox only if the horizontal buttons work
I have found some new problems unplugging the wi receiver with opzion "CorePointer" ,
this problem go away with "SendCoreEvents" but the mouse has the horizontal buttons inverted and xmodmap do nothing in this case...
Hey, tek43,
Can you tell us the easy way to just get the tilt wheel to work?
Thanks for all your great work on this challenge!!
Offline
RobF228 wrote:
My VX Nano works fine (no hacks, no editing of config files, no attempt to side scroll yet, etc.), except that when I unplug the USB dongle, the touchpad no longer functions.
That's strange. I just received my vx nano and haven't changed xorg.conf yet either. My eee's touchpad keeps working properly even after unplugging the dongle.
Sorry I don't have any good advice. ![]()
Offline
mrmot wrote:
imabuddha wrote:
C.J. wrote:
I just broke my Eee PC adding the above to my xorg.conf file.
...I'm not a linux expert, but I'm pretty sure that editing xorg.conf cannot cause that error.
...Well, exact same thing happened to me when I added this section to my xorg.conf, and I'm quite sure that was the only difference between "worked before" and "killed after" states. Had to recover to factory settings with F9.
Having just today received my VX nano, I see what you mean. However, this is another example of the bs in the eee's xandros linux. Normally if there's a problem with the xorg.conf, X will fail to start but you'll end up at the command line.
I'm guessing that fastinit wants to keep trying to start X thus causing the endless loop. I messed around with the xorg.conf file a lot this evening getting my settings just right, and encountered this problem near the end of my many changes.
For anyone doing more than just using the "easy mode", I highly advise following this wiki page to setup a rescue console, which will make recovering from a situation like this trivial: http://wiki.eeeuser.com/howto:installre … escue_mode
Last edited by imabuddha (2007-12-07 6:55:46 pm)
Offline
A big Thank You to tek43 for posting all the info on getting the VX nano fully operational!!!
I did find a few omitted steps and a couple of things needed to be changed to get it working properly for me. I also determined that a couple of the changes weren't necessary.
I'll be posting a how-to page on the wiki soon, but for those who can't wait, follow tek43's advice in post #36 above, but:
- the evdev package is already installed (no need to apt-get it)
- you don't need to know the event # from /proc/bus/input/devices, but you do need the name, which for this mouse should never change
- the synaptics line in the ServerLayout section doesn't need CorePointer
- it's a good idea to add another InputDevice line in that section specifically for the vx nano
- if you do that, you'll need to add a new InputDevice section for the vx nano instead of altering the existing mouse section
- in the InputDevice section for the vx nano, instead of the option device line, use an option name line with the name reported in /proc/bus/input devices: "Logitech USB Receiver". this way even if you have different usb devices plugged in at boot (or other times) the new vx nano settings will still work.
- don't comment out the SendCoreEvents line in the synaptics section (doing so caused the touchpad to not work, even if CorePointer is added to the synaptics line in the ServerLayout section)
- to get the 2 small left buttons to work, three things must be done differently:
1. you do need to apt-get install xbindkeys, but you'll also need xvkbd !
2. in the code for the .xbindkeysrc file, change m:0x10 to m:0x00 in both places, and change b:10 to b:8 (there's no button 10)
3. finally, you need to run xbindkeys when X starts. I did it by adding a symbolic link to xbindkeys in ~/.kde/Autostart
OK, so that's a lot of "stuff" in addition to tek43's instructions, which is why a wiki how-to is forthcoming.
Offline
i'm learning a lot of thing in this days about linux ![]()
I supposed to have done a lot of not necessary changes ![]()
Some question to better undestand:
I didn't use name "usbl rceiver etc" because there was 2 of them , i'll try
i have synaptic sendcoreevents with # and it still works, there are no problem leaving sendcor and adding core pointer together?
the "xbindkeys section" is really footmade
i wrote incomplete info, good corrections ![]()
Last edited by tek43 (2007-12-07 7:56:07 pm)
Offline
imabuddha wrote:
A big Thank You to tek43 for posting all the info on getting the VX nano fully operational!!!
I did find a few omitted steps and a couple of things needed to be changed to get it working properly for me. I also determined that a couple of the changes weren't necessary.
I'll be posting a how-to page on the wiki soon, but for those who can't wait, follow tek43's advice in post #36 above, but:
- the evdev package is already installed (no need to apt-get it)
- you don't need to know the event # from /proc/bus/input/devices, but you do need the name, which for this mouse should never change
- the synaptics line in the ServerLayout section doesn't need CorePointer
- it's a good idea to add another InputDevice line in that section specifically for the vx nano
- if you do that, you'll need to add a new InputDevice section for the vx nano instead of altering the existing mouse section
- in the InputDevice section for the vx nano, instead of the option device line, use an option name line with the name reported in /proc/bus/input devices: "Logitech USB Receiver". this way even if you have different usb devices plugged in at boot (or other times) the new vx nano settings will still work.
- don't comment out the SendCoreEvents line in the synaptics section (doing so caused the touchpad to not work, even if CorePointer is added to the synaptics line in the ServerLayout section)
- to get the 2 small left buttons to work, three things must be done differently:
1. you do need to apt-get install xbindkeys, but you'll also need xvkbd !
2. in the code for the .xbindkeysrc file, change m:0x10 to m:0x00 in both places, and change b:10 to b:8 (there's no button 10)
3. finally, you need to run xbindkeys when X starts. I did it by adding a symbolic link to xbindkeys in ~/.kde/Autostart
OK, so that's a lot of "stuff" in addition to tek43's instructions, which is why a wiki how-to is forthcoming.
A zillion thanks for that pending wiki how-to! If you have Paypal I'll donate in thanks!
Offline
tek43 wrote:
i'm learning a lot of thing in this days about linux
Me too! ![]()
I didn't use name "usbl rceiver etc" because there was 2 of them , i'll try
i have synaptic sendcoreevents with # and it still works, there are no problem leaving sendcor and adding core pointer together?
I first tried doing it exactly the way you wrote it, and it mostly worked. However, I read on the ubuntu forum a bit more about how this works, and my testing showed that plugging different things into the usb ports at boot can change the event #. Using the name avoids this problem. Yep, this mouse makes 2 usb events, but the other is mapped to a keyboard and doesn't interfere.
My touch pad didn't work without SendCoreEvents, even with CorePointer in the ServerLayout section. I added it back in and removed CorePointer, basically undo-ing those two changes, and it works perfectly.
I'm creating the wiki page now. It's time consuming, but when it's done I'll post a link here, and then you can see my xorg.conf, etc. ![]()
Offline
ohyes wrote:
A zillion thanks for that pending wiki how-to! If you have Paypal I'll donate in thanks!
I hope it helps you! (and everyone else) I have paypal, and while I can always use more $, consider it an early holiday gift. ![]()
I've learned a lot from others on this forum/wiki, and I'm just trying to give a little back.
Offline
imabuddha wrote:
ohyes wrote:
A zillion thanks for that pending wiki how-to! If you have Paypal I'll donate in thanks!
I hope it helps you! (and everyone else) I have paypal, and while I can always use more $, consider it an early holiday gift.
I've learned a lot from others on this forum/wiki, and I'm just trying to give a little back.
Great spirit! Please let us know when you put it on the wiki. If you have a favorite charity that takes online donations, please provide a link and I'll make a donation in thanks. My holiday gift back to you!
Offline
As promised, here's the wiki: http://wiki.eeeuser.com/configure_logitech_vx_nano
Let me know if it doesn't work, or even better update the wiki if you know how to improve it! ![]()
Offline
imabuddha wrote:
As promised, here's the wiki: http://wiki.eeeuser.com/configure_logitech_vx_nano
Let me know if it doesn't work, or even better update the wiki if you know how to improve it!
Nice job on the instructions, very clear. As soon as I get my VX for Christmas, I'll try it out! Thanks!!!
Offline
When I use the instructions in the Wiki, and put in
sudo apt-get install xbindkeys xvkbd
I get back:
E: Couldn't find package xbindkeys
Can anyone help me with this?
thanks
Offline
imabuddha wrote:
As promised, here's the wiki: http://wiki.eeeuser.com/configure_logitech_vx_nano
Let me know if it doesn't work, or even better update the wiki if you know how to improve it!
I am working to try to have the horizontal scroll and back/forward buttons work in Easy Mode and will report when I make progress. In the meantime, if anyone has made both items work in Easy Mode, please let me know.
Offline
silent e wrote:
imabuddha wrote:
As promised, here's the wiki: http://wiki.eeeuser.com/configure_logitech_vx_nano
Let me know if it doesn't work, or even better update the wiki if you know how to improve it!I am working to try to have the horizontal scroll and back/forward buttons work in Easy Mode and will report when I make progress. In the meantime, if anyone has made both items work in Easy Mode, please let me know.
I got both the horizontal scroll and the back/forward buttons of my VX Nano working in Firefox in Easy Mode!
To get the buttons to work, above and beyond the steps listed in the VX Nano Wiki Entry, do the following steps:
1) Add an entry for xbindkeys to an .icewm startup file using the "Easy Mode" instructions listed in the Running a script at startup Wiki Entry. Note: I had success by making my entry xbindkeys (it didn't work using /etc/bin/xbindkeys)
My .icewm/startup file has 2 lines and looks like this:
#!/bin/sh
xbindkeys
then
2) Make sure to change the about:config file in Firefox using the steps outlined in post #34 of this thread. In addition to setting the mousewheel.horizscroll.withnokey.action "Value" field to 0 and the mousewheel.horizscroll.withnokey.numlines "Value" to 1, I find the horizontal scrolling action to be more precise if I also change the mousewheel.horizscroll.withmetakey.numlines "Value" to 1.
Offline