1081
Users / Re: USB gamepad - anyone have one, happy to test alternative detection?
« on: February 06, 2013, 10:32:50 pm »I really want to beat whomever did the udev rules for these devices to a fucking pulp...
-Thom
Agreed.
J.
Rule #1 - Be Patient - Rule #2 - Don't ask when, if you don't contribute - Rule #3 - You have coding skills - LinuxMCE's small brother is available: http://www.agocontrol.com
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
I really want to beat whomever did the udev rules for these devices to a fucking pulp...
-Thom
Sure, here it is on the accelerometer machine (hp6710b):
Thanks for having a look at this. I will try to apply and test your patches on my false positives (hp6710b notebooks accelerometer) and let you know. Will be great if this is addressed.
udevadm info --query property --name /dev/input/js0
for your accelerometer device. (Accelerometer in my laptop doesn't present at /dev/input/js?) I know it will not mis-detect a mouse device now but I'm not sure what the accelerometer presents as.awesome. patch it
-Thom
# udevadm info --query property --name /dev/input/js0
UDEV_LOG=3
DEVPATH=/devices/pci0000:00/0000:00:06.0/usb2/2-1/2-1:1.0/input/input4/js0
MAJOR=13
MINOR=0
DEVNAME=/dev/input/js0
SUBSYSTEM=input
ID_INPUT=1
ID_INPUT_MOUSE=1
ID_VENDOR=VirtualBox
ID_VENDOR_ENC=VirtualBox
ID_VENDOR_ID=80ee
ID_MODEL=USB_Tablet
ID_MODEL_ENC=USB\x20Tablet
ID_MODEL_ID=0021
ID_REVISION=0100
ID_SERIAL=VirtualBox_USB_Tablet
ID_TYPE=hid
ID_BUS=usb
ID_USB_INTERFACES=:030000:
ID_USB_INTERFACE_NUM=00
ID_USB_DRIVER=usbhid
ID_PATH=pci-0000:00:06.0-usb-0:1:1.0
DEVLINKS=/dev/char/13:0 /dev/input/by-id/usb-VirtualBox_USB_Tablet-mouse /dev/input/by-path/pci-0000:00:06.0-usb-0:1:1.0-mouse
OK, so the package is installed if required, but I can't see why the GamepadCmd variable is set because I can't figure out where/if it's ever used?
...
snag is... that "GamepadCmd" bit... what is that used for and where does it come in. Is it a necessary step I'm missing out?
I know the embedded transmitter (usb uirt embedded transmitter) is a child device, sort of a dummy device as referred to by Tshak, but should it still have a log file? Only the parent has a log file in my case (the parent being the receiver, which is working).
I do get the "some devices failed to start" message when I start up my MD. How do I track down which devices? Is it possible that the embedded transmitter is the one failing? Is it supposed to start (being a dummy/child device and all)?
Haven't had a chance to look into this further yet, still fiddling with the remote mapping for the receiver, but I wanted to ask if anyone has one (USBUIRT) working as a transmitter in 10.04? If so, when you transmit a code (say in "Test" mode when you are entering codes and you press the test button), can you see a flash from the unit? I've tried using my mobile phone camera to watch the unit and I don't see anything so I'm presuming it isn't happening.
I see there was a bug in 07.10 and there are a few references in the wiki to transmission problems and I haven't tried any of those fixes, assuming they are no longer an issue in 10.04?
Anyone care to comment?
wiki.linuxmce.org/index.php/RaspberryPi has some attempts to get LinuxMCE running on RPi.
Can someone elaborate on why it is not possible to run LinuxMCE on RPi?
Seems like it should.
Jason, do you not see this if you open the log and search back to the point where you first opened the grid? you have to go back quite a bit...