Nothing attached..... but here's some suggestions for you.
1). Do a 'lsusb -vv' to get a full listing of how the kernel sees the wheel.
In Linux wheels are seen as joysticks, a device with axis and buttons, whether they support FF or not. Most of these devices are HID devices and give a descriptor block which explains how the computer how many axis there are and how to extract the values for the axis/buttons. It is possible that the descriptor is 'wrong' and not parsed correctly.
2). Dump the descriptor and check for 'glitches'.
IIRC you can get this directly from '/proc/bus/usb/device/0000.0000/' directory, but I don't have a linux box to hand to check. There are some tools for decoding the data here:
3). You can 'decode' the data coming from the device, once you know how long the report it. For example the following command with dump the stream from a PS3 DualShock, and I can see which bits change when the axis/buttons are moved.
--
# hexdump -v -e '48/1 "%02x " "\n"' < /dev/hidraw1 # For kernels < 2.6.26
# hexdump -v -e '49/1 "%02x " "\n"' < /dev/hidraw1 # For kernels >= 2.6.26
00 00 00 00 00 74 7b 7c 7c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 02 ee 10 00 00 00 00 02 b2 77 01 81 02 05 01 ed 01 a4 00 02
--
The above should give you a good idea how the device sends it's data. I'm guessing that its primary function (the turn the wheel) is really derived from accelometers. The userland Xbox driver has a technique for generating a 'fake' joystick....
It's likely that the advanced functions of the wheel are going to be propriatory, so likely it would need a custom kernel driver.
Simon
PS. wow... I must be really geeky...