Driver installation from hell
This is a discussion about Driver installation from hell in the Everything Linux category; Hello everyone. See what I mean? An nightmare if there ever was one but I am going to let it defeat me. I can't expect anyone to go through all that so I will break my questions into small steps. I've had a go but it didn't work.
Hello everyone.
http://linuxwacom.sourceforge.net/index.php/howto/all
See what I mean?
An nightmare if there ever was one but I am going to let it defeat me. I can't expect anyone to go through all that so I will break my questions into small steps.
I've had a go but it didn't work. I seem to get the general idea of what is happening. Having installed the drivers (or so I thought) I use the program wacdump to see what was happening. The lack of pressure information made me conclude the drivers were still in place.
I could not see what I was doing wrong until I tryed rebuilding the drivers. This time I found an error message stating the XFree86 build environment couldn't be found. I have a /usr/src/redhat/BUILD directory but no XFree86 folder in that.
In a nutshell I am looking to install a certain /usr/src/redhat/BUILD/XFree86-4.2.0 folder somehow.
Can anyone please help me?
Koba
http://linuxwacom.sourceforge.net/index.php/howto/all
See what I mean?
An nightmare if there ever was one but I am going to let it defeat me. I can't expect anyone to go through all that so I will break my questions into small steps.
I've had a go but it didn't work. I seem to get the general idea of what is happening. Having installed the drivers (or so I thought) I use the program wacdump to see what was happening. The lack of pressure information made me conclude the drivers were still in place.
I could not see what I was doing wrong until I tryed rebuilding the drivers. This time I found an error message stating the XFree86 build environment couldn't be found. I have a /usr/src/redhat/BUILD directory but no XFree86 folder in that.
In a nutshell I am looking to install a certain /usr/src/redhat/BUILD/XFree86-4.2.0 folder somehow.
Can anyone please help me?
Koba
Participate in our website and join the conversation
This subject has been archived. New comments and votes cannot be submitted.
Jul 25
Jul 28
0
3 minutes
Responses to this topic
OP
Hoorah!
I did it!
I realised that the XFree86 were precompiled so I didn't need to compile them myself. So I followed the documentation: compiled the object files, replaced the respective devices in /dev/input, loaded the new modules and then edited XFConf to get the drivers working through the X Windows system.
So I've submited a compatibility report for the Graphire 3: It is all working fine.
So now I'm continuing my search for gesture recognition for linux and does anyone know how to scroll by clicking-dragging with the mouse wheel in linux?
Koba
I did it!
I realised that the XFree86 were precompiled so I didn't need to compile them myself. So I followed the documentation: compiled the object files, replaced the respective devices in /dev/input, loaded the new modules and then edited XFConf to get the drivers working through the X Windows system.
So I've submited a compatibility report for the Graphire 3: It is all working fine.
So now I'm continuing my search for gesture recognition for linux and does anyone know how to scroll by clicking-dragging with the mouse wheel in linux?
Koba
Congratulations Koba! It's a great feeling when you persist and conquer such problems in Linux!
if you haven't already set up the mouse protocol to IMPS/2 with
XFConf, then that's the first step to getting the wheel working.
Next, you'll need to add (or uncomment) the 'ZAxisMapping' and
possibly reverse the order of the axis indexes if you find your
wheel spinning backwards.
Note: you need to log out of your session so that X is restarted
for your changes to take effect.
XFConf, then that's the first step to getting the wheel working.
Next, you'll need to add (or uncomment) the 'ZAxisMapping' and
possibly reverse the order of the axis indexes if you find your
wheel spinning backwards.
Note: you need to log out of your session so that X is restarted
for your changes to take effect.
OP
Hi
Thanks for the reply.
I'm not sure you understood what I am asking for: admittedly it is a rather strange request.
Seeing the pen tablet is now working, I would like to use it . The mousewheel works fine by rolling it up and down for scrolling.
There is no wheel on the pen but one solution (on windows) is to map middle click (mouse wheel click) to one of the pen's buttons. Then using "intellimouse" you can scroll rapidly by mouse wheel clicking and dragging (not rolling).
This is a rather perculiar problem so I doubt there is a solution.
Koba
Thanks for the reply.
I'm not sure you understood what I am asking for: admittedly it is a rather strange request.
Seeing the pen tablet is now working, I would like to use it . The mousewheel works fine by rolling it up and down for scrolling.
There is no wheel on the pen but one solution (on windows) is to map middle click (mouse wheel click) to one of the pen's buttons. Then using "intellimouse" you can scroll rapidly by mouse wheel clicking and dragging (not rolling).
This is a rather perculiar problem so I doubt there is a solution.
Koba
oh, ok, I understand now. You can customize your special mouse
(the stylus) as you wish, and you'll need to use 'xev' to figure
out which stylus button equals which button number X Windows receives.
In short, you're going to set up more than one "InputDevice" and
one of those InputDevices has an Option set to identify the device
as type stylus. After that, it's a matter of button mapping.
However, I realize one of the buttons serves as the stylus tip contact report
and one end of the rocker switch. You'll see this with 'xev'.
You might not have enough buttons to do exactly what you want, but
you can mess around with ZAxisMapping and ChordMiddle. You may
want to be certain to have a second non-tablet mouse connected
in case your experimental subject goes wacky.
(the stylus) as you wish, and you'll need to use 'xev' to figure
out which stylus button equals which button number X Windows receives.
In short, you're going to set up more than one "InputDevice" and
one of those InputDevices has an Option set to identify the device
as type stylus. After that, it's a matter of button mapping.
However, I realize one of the buttons serves as the stylus tip contact report
and one end of the rocker switch. You'll see this with 'xev'.
You might not have enough buttons to do exactly what you want, but
you can mess around with ZAxisMapping and ChordMiddle. You may
want to be certain to have a second non-tablet mouse connected
in case your experimental subject goes wacky.
