Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Hardware: simple utility for send hex commands to usb device
03-17-2008, 02:36 PM
Post: #16
 
I don't think it's a 64-bit problem, as it works under Ubuntu Gutsy 64 for me. I think the problems are coming from your system's usb.h conflicting with the usb.h in the directory with the usbtool.
Visit this user's website Find all posts by this user
Quote this message in a reply
03-17-2008, 03:15 PM
Post: #17
 
Okay it works now. I was running either "python ./usbtool" or just "./usbtool". It turns out, I had to use "python2.5 ./usbtool", as Python 2.4 is the default version of Python in Debian.

Another problem... Sad

Code:
$ sudo python2.5 ./usbtool -d 044f:b202:0 f78e
Traceback (most recent call last):
  File "./usbtool", line 158, in <module>
    dev=usb.OpenDevice(device[0],device[1], device[2])
  File "/r/hdd/s/src/usbtool/usb.py", line 292, in OpenDevice
    return iface.openbulk()
  File "/r/hdd/s/src/usbtool/usb.py", line 148, in openbulk
    assert epout is not None
AssertionError
--
edit: Made a workaround for that by adding a line to usb.py to use "IN" endpoint as "out" (there are no any "OUT" endpoint, so it was failing). Dunno if this is correct at all. Anything I try to send to the device just causes it to unregister itself now.
Find all posts by this user
Quote this message in a reply
03-17-2008, 06:10 PM
Post: #18
 
You might also find it useful to use usbmon to log usb traffic while you play around with it. Use google to find a site detailing how to use usbmon, I don't remember well enough the steps to replicate it, but it was pretty easy.
Visit this user's website Find all posts by this user
Quote this message in a reply
04-21-2008, 12:29 PM
Post: #19
/dev/js0 disappeared
Hello, I can successfully use your usbtool .

after each use, the /dev/jsX device file disappear, but we can just enter the following commands to make it appear again :

sudo rmmod joydev
sudo rmmod usbhid
sudo modprobe usbhid


at least, it works on my gentoo distrib.

Hope this helps !
Find all posts by this user
Quote this message in a reply
05-12-2008, 12:49 PM
Post: #20
Full G25 wheel support under Linux (except force feedback)
Hi, all.

For the happy owners of a Logitech G25 wheel that did not manage yet
to enjoy the full features of the beast under Linux, this is a small
summary of what I found on the net and my own humble experience about it
on a 2.6.22.9 Kernel (Mandriva 2008.0 x86_64) :

Note: This is only my own understanding and summarizing of what people cleverer
than me discovered by themselves. My work only consisted to put
all the stuff together in an as clear, simple and explict as possible
sum-up. See at the bottom for references and real authors.

1) when plugged in, the G25 identies itself as a Logitech Formula Force EX
USB device (046d:c294) ; you only get 4 axes and 12 buttons, that is
neither clutch pedal nor any of the 3trd to 6th gear on the grid shifter
2) to get the lacking native features of the beast, it must be sent a command
to switch to its native mode, that makes it disconnect and reconnect
as itself this time (USB device ids 046d:c299)
Note: Another similar command can also switch it to the Logitech Driving
Force Pro mode.
3) to send the command, you need a userland tool that basically writes
the associated bytes on the USB device, and the one I am using is
usbtool <ftp>
(the package includes pre-built binaries for python 2.5,
and sources if you need to build it yourself) ;

to switch the G25 to its native mode, after plugging it in, I simply use :
./usbtool -v g25-set-extended-mode

Note: you can also send other pre-configured commands with the usbtool
(run ./usbtool --list-commands to see which)
like g25-set-range-wheel-900 (teasing ;-)
BUT: I never succeeded to send 2 successive commands to the device :
the first one is generally OK (sometimes, though, you may need to repeat
it), but the second (and following ones) seems to be completely ignored.

4) but this makes disappear the /dev/jsX and /dev/input/eventY devices !
to get them back and be able to play with the G25, I use :
sudo rmmod joydev
sudo rmmod usbhid
sudo modprobe usbhid
(man sudo and sudoers to be able to run these root commands)

5) Then, if you find that the "dead zone" at the center of the wheel
is too large (the centered angle where nothing happens when you steer into),
it is only beacause you need to calibrate your device.
I use jscal (ff-utils @ In order to view links, you must have to reply to this thread.
to do that :
a) plug-in the device
b) send the native mode-switch command if you like (see above 3)
c) jscal -c /dev/jsX (X being 0, 1, ... look which in /dev after plugging-in)
d) jstest /dev/jsX (to test if everything fits your desire)
e) jscal -p /dev/jsX (to get the jscal command to put in your .bashrc
or any script you would run before your favorite games ...)

Note: All this stuff should also work for a Driving Force Pro, and some says
that it's also true for the Momo Racing wheels ... but don't tested.

Now, as far as force feedback is concerned, I have no such good news
for the moment : fftest and ffcstress don't work for me for the moment.

References:

Thanks to avl, eckzow, anrp, thelusiv, tof8pool, synapse247 and cuckoo,
on In order to view links, you must have to reply to this thread. forum :
In order to view links, you must have to reply to this thread.
In order to view links, you must have to reply to this thread.
In order to view links, you must have to reply to this thread.
In order to view links, you must have to reply to this thread.

Thanks to Jiri Kosina, Chris Guirl,
from the Linux input dev team
In order to view links, you must have to reply to this thread.
In order to view links, you must have to reply to this thread.
(search "g25" on each list)

Hoping this helps ...

Pouillot.
Find all posts by this user
Quote this message in a reply
09-27-2008, 01:22 PM
Post: #21
G25 all axes / buttons AND force feedback
Here is my experience and some little tricks.

First of all, I had to modify my kernel source code. I'm not a kernel developper, so I don't know If all the modification were needed.

All those modifications shouldn't break anything as they are only new declarations, no logic has been modified.
My kernel is a 2.6.25

In your /usr/src/linux/drivers/hid/hid-ff.c, add this line near line 60 :
{ 0x46d, 0xc299, hid_lgff_init }, /* Logitech G25 */
the file should look like this :
Quote:#ifdef CONFIG_LOGITECH_FF
{ 0x46d, 0xc211, hid_lgff_init }, /* Logitech Cordless rumble pad */
{ 0x46d, 0xc219, hid_lgff_init }, /* Logitech Cordless rumble pad 2 */
{ 0x46d, 0xc283, hid_lgff_init }, /* Logitech Wingman Force 3d */
{ 0x46d, 0xc286, hid_lgff_init }, /* Logitech Force 3D Pro Joystick */
{ 0x46d, 0xc294, hid_lgff_init }, /* Logitech Formula Force EX */
{ 0x46d, 0xc295, hid_lgff_init }, /* Logitech MOMO force wheel */
{ 0x46d, 0xc299, hid_lgff_init }, /* Logitech G25 */
{ 0x46d, 0xca03, hid_lgff_init }, /* Logitech MOMO force wheel */
#endif


In your /usr/src/linux/drivers/hid/hid-lgff.c, add this near line 58 :
{ 0x046d, 0xc299, ff_joystick },
the file should look like this :
Quote:static const struct dev_type devices[] = {
{ 0x046d, 0xc211, ff_rumble },
{ 0x046d, 0xc219, ff_rumble },
{ 0x046d, 0xc283, ff_joystick },
{ 0x046d, 0xc286, ff_joystick },
{ 0x046d, 0xc294, ff_joystick },
{ 0x046d, 0xc295, ff_joystick },
{ 0x046d, 0xc299, ff_joystick },
{ 0x046d, 0xca03, ff_joystick },
};


In your /usr/src/linux/drivers/hid/hid-quirks.c add this line near line 316 :
#define USB_DEVICE_ID_LOGITECH_WHEELG25 0xc299
and this line near line 608 :
{ USB_VENDOR_ID_LOGITECH, USB_DEVICE_ID_LOGITECH_WHEELG25, HID_QUIRK_NOGET },
the file should look like this:
Quote:#define USB_DEVICE_ID_LOGITECH_HARMONY_64 0xc14f
#define USB_DEVICE_ID_LOGITECH_EXTREME_3D 0xc215
#define USB_DEVICE_ID_LOGITECH_WHEEL 0xc294
#define USB_DEVICE_ID_LOGITECH_WHEELG25 0xc299
#define USB_DEVICE_ID_LOGITECH_ELITE_KBD 0xc30a
#define USB_DEVICE_ID_LOGITECH_KBD 0xc311
#define USB_DEVICE_ID_S510_RECEIVER 0xc50c
#define USB_DEVICE_ID_S510_RECEIVER_2 0xc517
#define USB_DEVICE_ID_LOGITECH_CORDLESS_DESKTOP_LX500 0xc512
and this :
Quote: { USB_VENDOR_ID_ATEN, USB_DEVICE_ID_ATEN_4PORTKVMC, HID_QUIRK_NOGET },
{ USB_VENDOR_ID_ELO, USB_DEVICE_ID_ELO_TS2700, HID_QUIRK_NOGET },
{ USB_VENDOR_ID_LOGITECH, USB_DEVICE_ID_LOGITECH_EXTREME_3D, HID_QUIRK_NOGET },
{ USB_VENDOR_ID_LOGITECH, USB_DEVICE_ID_LOGITECH_WHEEL, HID_QUIRK_NOGET },
{ USB_VENDOR_ID_LOGITECH, USB_DEVICE_ID_LOGITECH_WHEELG25, HID_QUIRK_NOGET },
{ USB_VENDOR_ID_MICROSOFT, USB_DEVICE_ID_WIRELESS_OPTICAL_DESKTOP_3_0, HID_QUIRK_NOGET },
{ USB_VENDOR_ID_PETALYNX, USB_DEVICE_ID_PETALYNX_MAXTER_REMOTE, HID_QUIRK_NOGET },
{ USB_VENDOR_ID_SUN, USB_DEVICE_ID_RARITAN_KVM_DONGLE, HID_QUIRK_NOGET },
{ USB_VENDOR_ID_TURBOX, USB_DEVICE_ID_TURBOX_KEYBOARD, HID_QUIRK_NOGET },
{ USB_VENDOR_ID_WISEGROUP, USB_DEVICE_ID_DUAL_USB_JOYPAD, HID_QUIRK_NOGET | HID_QUIRK_MULTI_INPUT },

Once your new kernel has been compiled and booted, we can play a little bit with udev to make it run the commands needed to have /dev/jsX recreated when using usbtool.

Create a file named /etc/udev/rules.d/99-G25.rules which content is :
Quote:KERNEL=="event*", MODE="660", GROUP="games"
BUS=="usb", SYSFS{product}=="G25 Racing Wheel", SYSFS{idVendor}=="046d", ACTION=="remove", RUN+="/etc/init.d/usbhid restart"
BUS=="usb", SYSFS{product}=="G25 Racing Wheel", SYSFS{idVendor}=="046d", ACTION=="add", RUN+="/etc/init.d/usbhid start"

then create a file named /etc/init.d/usbhid which content is :
Quote:#!/bin/sh
#

start() {
/sbin/modprobe usbhid
}

stop() {
/sbin/modprobe -r joydev usbhid
}

case "$1" in
start)
start
;;
stop)
stop
;;
restart)
stop
start
;;
*)
echo "Usage: /etc/init.d/usbhid {start|stop|restart}"
exit 1
esac
At least run udevadm control --reload_rules

Now when U use usbtool to toggle your G25 wheel to extended mode, you should still have force feedback working and your /dev/jsX file should already have been recreated.

With those tips I'm able to drive in vdrift with all axes and force feedback.

Sorry, if some of my sentences are not very easy to understand, english is not my native language.
Hope this helps
Find all posts by this user
Quote this message in a reply
09-28-2008, 08:02 PM
Post: #22
 
How does the force feedback feel? I haven't tried it yet.
Find all posts by this user
Quote this message in a reply
10-11-2008, 07:08 PM
Post: #23
 
i applied that patch to 2.6.25-gentoo-r8 and i still can't get fftest / ffcstress to acknowledge that the wheel has force feedback. were there any other modifications you had to make?

thanks
Find all posts by this user
Quote this message in a reply
10-12-2008, 05:47 AM
Post: #24
 
bunder, I do not run 2.6.25-r8 yet because I can't compile the nvidia-driver with it.

I did not modify anything else than already said.

Can you give a little bit more details on how you're using fftest and ffcfstress ( are you getting error messages ?).
Do you have any foce feedback before using usbtool ?

For me fftest works only with effect number 1 ( constant force ).

To run it, I have to use /dev/input/event2 like this :
fftest /dev/input/event2
ffcfstress -d /dev/input/event2

joevenzon, the force feedback in the game is not very good compared to games like Rfactor or Live For Speed, but at least it does exist and to my knowledge, it is the first linux game trying to use force feedback.
So because Vdrift is the first one, we need to be patient. No doubt they will succeed.
Find all posts by this user
Quote this message in a reply
10-12-2008, 08:20 AM
Post: #25
 
i unplugged my wheel, and plugged it in and ran fftest. it said it could only run effect 1 like yours did, but i couldn't tell any difference while it was running. on the other hand, ffcstress did work. now to find out why its still not working after i run usbtool and "rmmod joydev && rmmod usbhid && modprobe usbhid" :?

i'll keep trying.

thanks

update: i got working. now to find out why wine/LFS (is that a bad word around here? heh) isn't using it... thanks a bunch guys Big Grin
Find all posts by this user
Quote this message in a reply
10-18-2008, 10:41 PM
Post: #26
 
Thanks for the so called "fix", Ive tried recompiling a custom 2.6.27 kernel and just the module itself but have had no luck with force feedback.

I can get it into 900 degrees and extended mode but thats as far as I get. No force feedback. Its the only thing stopping me from getting rid of windows for good as wine has vastly improved. I'm a avid driving game enthusiast.

I use Ubuntu, I need someone to get this working on ubuntu!
I have been frustrated with this problem since I bought the wheel about a year ago. I really badly want it to work fully and I am willing to write a python gui frontend for this once done (similar to the logitech tools on windows)!

I can upload the .deb kernel image for ubuntu, it is 266MB though. Reply if you want it.

Theres a ubuntu intrepid beta out, it comes with 2.6.27.
Find all posts by this user
Quote this message in a reply
10-19-2008, 06:01 AM
Post: #27
 
Rich43 Wrote:I can get it into 900 degrees and extended mode but thats as far as I get. No force feedback.

can you run ffcstress against the /dev/input/event# device? also, you'll need to modify the permissions on the device, making it owned by the games group should be all you need. that way users can use the wheel with the ffb enabled.

my script, in case you're not using the udev rule above:

Code:
# cat dowheel
#!/bin/bash

cd usbtool-0.1
python2.4 usbtool -l | grep G25

echo turning on wheel functions
python2.4 usbtool g25-set-extended-mode
sleep 3

python2.4 usbtool -l | grep G25

echo turning on 900 degrees
python2.4 usbtool g25-set-range-wheel-900
sleep 3

python2.4 usbtool -l | grep g25

echo redetecting js0
ls -l /dev/input/js0
rmmod joydev && rmmod usbhid && modprobe usbhid
sleep 1
ls -l /dev/input/js0
sleep 2

echo fixing event6 permissions
ls -l /dev/input/event6
chgrp games /dev/input/event6
chmod g+rw /dev/input/event6
ls -l /dev/input/event6

echo done

output looks like this:

Code:
# ./dowheel
046d:c299:0 Device G25 (normal mode) found!

turning on wheel functions
alt setting 0
046d:c299:0 Device G25 (extended mode) found!

turning on 900 degrees
alt setting 0

redetecting js0
ls: cannot access /dev/input/js0: No such file or directory
crw-r--r-- 1 root root 13, 0 Oct 19 05:59 /dev/input/js0

fixing event6 permissions
crw-r----- 1 root root 13, 70 Oct 19 05:59 /dev/input/event6
crw-rw---- 1 root games 13, 70 Oct 19 05:59 /dev/input/event6

done
Find all posts by this user
Quote this message in a reply
10-19-2008, 03:32 PM
Post: #28
 
Ok, I had another bash at it, found a small typo in my patch (missing comma) and reinstalled my custom kernel.

It seems to put the g25 on event3.

richie@richie-desktop:~/ff-utils$ sudo ./ffcfstress -d /dev/input/event3
ERROR: device (or driver) has no force feedback support [ffcfstress.c:165]


Debug info:
Code:
custom g25 kernel:
richie@richie-desktop:~/ff-utils$ uname -a
Linux richie-desktop 2.6.27-g25 #2 SMP Sun Oct 19 14:56:05 BST 2008 i686 GNU/Linux
richie@richie-desktop:~/ff-utils$
Code:
richie@richie-desktop:~/usbtool-0.1$ sudo ./dowheel
./dowheel: line 3: cd: usbtool-0.1: No such file or directory
/home/richie/usbtool-0.1/libusb.py:7: RuntimeWarning: Python C API version mismatch for module _libusb: This Python has API version 1012, module _libusb has version 1013.
  import _libusb
/home/richie/usbtool-0.1/libusb.py:7: RuntimeWarning: Python C API version mismatch for module swig_runtime_data3: This Python has API version 1012, module swig_runtime_data3 has version 1013.
  import _libusb
046d:c294:0 Device G25 (normal mode) found!
turning on wheel functions
/home/richie/usbtool-0.1/libusb.py:7: RuntimeWarning: Python C API version mismatch for module _libusb: This Python has API version 1012, module _libusb has version 1013.
  import _libusb
/home/richie/usbtool-0.1/libusb.py:7: RuntimeWarning: Python C API version mismatch for module swig_runtime_data3: This Python has API version 1012, module swig_runtime_data3 has version 1013.
  import _libusb
alt setting 0
/home/richie/usbtool-0.1/libusb.py:7: RuntimeWarning: Python C API version mismatch for module _libusb: This Python has API version 1012, module _libusb has version 1013.
  import _libusb
/home/richie/usbtool-0.1/libusb.py:7: RuntimeWarning: Python C API version mismatch for module swig_runtime_data3: This Python has API version 1012, module swig_runtime_data3 has version 1013.
  import _libusb
046d:c299:0 Device G25 (extended mode) found!
turning on 900 degrees
/home/richie/usbtool-0.1/libusb.py:7: RuntimeWarning: Python C API version mismatch for module _libusb: This Python has API version 1012, module _libusb has version 1013.
  import _libusb
/home/richie/usbtool-0.1/libusb.py:7: RuntimeWarning: Python C API version mismatch for module swig_runtime_data3: This Python has API version 1012, module swig_runtime_data3 has version 1013.
  import _libusb
alt setting 0
/home/richie/usbtool-0.1/libusb.py:7: RuntimeWarning: Python C API version mismatch for module _libusb: This Python has API version 1012, module _libusb has version 1013.
  import _libusb
/home/richie/usbtool-0.1/libusb.py:7: RuntimeWarning: Python C API version mismatch for module swig_runtime_data3: This Python has API version 1012, module swig_runtime_data3 has version 1013.
  import _libusb
redetecting js0
ls: cannot access /dev/input/js0: No such file or directory
crw-rw---- 1 root plugdev 13, 0 2008-10-19 20:18 /dev/input/js0
fixing event3 permissions
crw-rw---- 1 root root 13, 67 2008-10-19 20:18 /dev/input/event3
crw-rw---- 1 root games 13, 67 2008-10-19 20:18 /dev/input/event3
done
richie@richie-desktop:~/usbtool-0.1$
Code:
richie@richie-desktop:~/ff-utils$ jstest /dev/input/js0
Driver version is 2.1.0.
Joystick (G25 Racing Wheel) has 6 axes (X, Y, Z, Rz, Hat0X, Hat0Y)
and 19 buttons (Trigger, ThumbBtn, ThumbBtn2, TopBtn, TopBtn2, PinkieBtn, BaseBtn, BaseBtn2, BaseBtn3, BaseBtn4, BaseBtn5, BaseBtn6, BtnDead, BtnA, BtnB, BtnC, BtnX, BtnY, BtnZ).
Testing ... (interrupt to exit)
Axes:  0:     0  1:     0  2:     0  3:     0  4:     0  5:     0 Buttons:  0:off  1:off  2:off  3:off  4:off  5:off  6:off  7:off  8:off  9:off 10:off 11:off 1
Code:
richie@richie-desktop:~/ff-utils$ ./ffcfstress -d /dev/input/event3
ERROR: can not open /dev/input/event3 (Permission denied) [ffcfstress.c:110]
[b]richie@richie-desktop:~/ff-utils$ sudo ./ffcfstress -d /dev/input/event3
ERROR: device (or driver) has no force feedback support [ffcfstress.c:165][/b]
richie@richie-desktop:~/ff-utils$ sudo ./ffcfstress -d /dev/input/js0
ERROR: can not get key bits (Invalid argument) [ffcfstress.c:118]
richie@richie-desktop:~/ff-utils$ sudo ./ffcfstress -d /dev/input/event1
ERROR: no suitable x-axis found [ffcfstress.c:144]
richie@richie-desktop:~/ff-utils$ sudo ./ffcfstress -d /dev/input/event2
ERROR: no suitable x-axis found [ffcfstress.c:144]
richie@richie-desktop:~/ff-utils$ sudo ./ffcfstress -d /dev/input/event4
ERROR: no suitable x-axis found [ffcfstress.c:144]
richie@richie-desktop:~/ff-utils$ sudo ./ffcfstress -d /dev/input/event5
ERROR: no suitable x-axis found [ffcfstress.c:144]
richie@richie-desktop:~/ff-utils$ sudo ./ffcfstress -d /dev/input/event6
ERROR: no suitable x-axis found [ffcfstress.c:144]
richie@richie-desktop:~/ff-utils$ sudo ./ffcfstress -d /dev/input/event7
ERROR: no suitable x-axis found [ffcfstress.c:144]
richie@richie-desktop:~/ff-utils$ sudo ./ffcfstress -d /dev/input/event8
ERROR: can not open /dev/input/event8 (No such file or directory) [ffcfstress.c:110]
Code:
richie@richie-desktop:~/ff-utils$ ./fftest /dev/input/event3
Force feedback test program.
HOLD FIRMLY YOUR WHEEL OR JOYSTICK TO PREVENT DAMAGES

Open device file: Permission denied
richie@richie-desktop:~/ff-utils$ sudo ./fftest /dev/input/event3
Force feedback test program.
HOLD FIRMLY YOUR WHEEL OR JOYSTICK TO PREVENT DAMAGES

Device /dev/input/event3 opened
Axes query:
Effects:
Number of simultaneous effects: 0
Upload effects[0]: Function not implemented
Upload effects[1]: Function not implemented
Upload effects[2]: Function not implemented
Upload effects[3]: Function not implemented
Upload effects[4]: Function not implemented
Upload effects[5]: Function not implemented
Enter effect number, -1 to exit
0
Now Playing: Sine vibration
Enter effect number, -1 to exit
1
Now Playing: Constant Force
Enter effect number, -1 to exit
^C
richie@richie-desktop:~/ff-utils$
Code:
richie@richie-desktop:~/ff-utils$ ls -l /dev/input
total 0
drwxr-xr-x 2 root root       140 2008-10-19 20:18 by-id
drwxr-xr-x 2 root root       160 2008-10-19 20:18 by-path
crw-rw---- 1 root root    13, 64 2008-10-19 20:02 event0
crw-rw---- 1 root root    13, 65 2008-10-19 20:18 event1
crw-rw---- 1 root root    13, 66 2008-10-19 20:18 event2
crw-rw---- 1 root games   13, 67 2008-10-19 20:18 event3
crw-rw---- 1 root root    13, 68 2008-10-19 20:02 event4
crw-rw---- 1 root root    13, 69 2008-10-19 20:02 event5
crw-rw---- 1 root root    13, 70 2008-10-19 20:02 event6
crw-rw---- 1 root root    13, 71 2008-10-19 20:02 event7
crw-rw---- 1 root plugdev 13,  0 2008-10-19 20:18 js0
crw-rw---- 1 root root    13, 63 2008-10-19 21:02 mice
crw-rw---- 1 root root    13, 32 2008-10-19 21:02 mouse0
crw-rw---- 1 root root    13, 33 2008-10-19 20:18 mouse1
richie@richie-desktop:~/ff-utils$
Code:
richie@richie-desktop:~/ff-utils$ lsusb
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 050d:0131 Belkin Components Bluetooth Device with trace filter
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 046d:c513 Logitech, Inc. MX3000 Cordless Desktop Receiver
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 003: ID 046d:c299 Logitech, Inc.
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
richie@richie-desktop:~/ff-utils$
Find all posts by this user
Quote this message in a reply
10-20-2008, 01:58 AM
Post: #29
 
Do you get force feedback before switching your wheel to extended mode ?
Find all posts by this user
Quote this message in a reply
10-20-2008, 11:32 AM
Post: #30
 
tof8pool Wrote:Do you get force feedback before switching your wheel to extended mode ?

Nope, I think i need some way to tell if the modified driver was loaded or some ordinary driver. Perhaps some log message?

How do I program that in? Im unfamiliar with kernel dev.

Tho if you have other ideas to fix this, then that will help too.
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)