[alexpigment]

Anyone else noticing that after a suspend/resume the controller stops working ?

when turning on the controller the position lights keeps flashing.

Running rc.local again just gives:



any ideas ?

I personally run my machine 24/7, so I have no experience with suspend/resume. Perhaps others may have experienced the same thing. Sorry I can't help.

[awef]

That's odd. The first command in the sh script is to rmmod xpad, so that shouldn't be necessary. Are you sure you followed step 6b correctly, or did you replace *all* of the existing lines with what I pasted?

I think you are right. Tried rebooting just now and it's not working. Do you have to do anything special like have the controller 'on' and searching while the PC boots and loads the driver?

[alexpigment]

I think you are right. Tried rebooting just now and it's not working. Do you have to do anything special like have the controller 'on' and searching while the PC boots and loads the driver?

Nope. I've definitely tried both ways though. Make sure your rc.local file is correct, I'd say. That's necessary for making it work, in my experience.

If that doesn't work, I'd say try my steps again, but ignore step 6.

http://forum.xbmc.org/showpost.php?p=609...stcount=92

[awef]

alexpigment, you could modify your guide to simply use the repository to get xboxdrv (which gets the latest version also).

I just tested this method on a fresh xbmc live install and it was quite simple (only for one controller but you get the idea):

First install xboxdrv:

Code:

sudo add-apt-repository ppa:grumbel/ppa
sudo apt-get update
sudo apt-get install xboxdrv

Then, make a new bash script called ~xbmc/xboxdrv.sh containing:

Code:

#!/bin/bash
rmmod xpad
modprobe uinput
modprobe joydev
xboxdrv --wid 0 -s -l 2 --dpad-as-button --deadzone 12000 --trigger-as-zaxis

(and make it executable)

Then, add this line to /etc/rc.local

Code:

/home/xbmc/xboxdrv.sh

Lastly, copy the keymap same way you described.

That's it.

I have discovered that the wireless dongle sometimes can't be detected if it hasn't been shutdown/initialised properly.. through my various experiments I managed to run into this a few times. Properly turning off my PC seems to reset it, or you can unplug/replug the device. Worth noting.

[alexpigment]

alexpigment, you could modify your guide to simply use the repository to get xboxdrv (which gets the latest version also).

I just tested this method on a fresh xbmc live install and it was quite simple (only for one controller but you get the idea):

First install xboxdrv:

Code:

sudo add-apt-repository ppa:grumbel/ppa
sudo apt-get update
sudo apt-get install xboxdrv

Then, make a new bash script called ~xbmc/xboxdrv.sh containing:

Code:

#!/bin/bash
rmmod xpad
modprobe uinput
modprobe joydev
xboxdrv --wid 0 -s -l 2 --dpad-as-button --deadzone 12000 --trigger-as-zaxis

(and make it executable)

Then, add this line to /etc/rc.local

Code:

/home/xbmc/xboxdrv.sh

Lastly, copy the keymap same way you described.

That's it.

I have discovered that the wireless dongle sometimes can't be detected if it hasn't been shutdown/initialised properly.. through my various experiments I managed to run into this a few times. Properly turning off my PC seems to reset it, or you can unplug/replug the device. Worth noting.

While this is indeed useful, I think it still doesn't get around the fact that you have to download a special file (in this case, the keymap). grumbel (xboxdrv creator) is working with others right now to create a driver which includes wireless chatpad support. At that point, I will redo my tutorial steps and hopefully get it down to 3-4 steps or less.

Thanks for the input either way. I'll take this into consideration when I rewrite it.

[grumbel]

While this is indeed useful, I think it still doesn't get around the fact that you have to download a special file (in this case, the keymap).

Is the special keymap needed because of differences between xpad and xboxdrv? If so, xboxdrv has an option for that:

xboxdrv --mimic-xpad

Also xboxdrv can be configured to mimic basically any input device with the --ui-axismap/--ui-buttonmap options, might be easier then doing a keymap for XBMC.

Also shouldn't xpad be stable enough by now or does that still have issues?

[Raphael Barros]

EDIT:

I installed o joystick, tested with jstest and jscal:

jstest --event /dev/input/js0

jscal -c /dev/input/js0

and made it work in zsnes.

To make it wok in mame, I added this in the /etc/xmame/xmamerc:

### Input device options ###
joytype 1
analogstick 0
joydevname /dev/input/js
ugcicoin 0
# lircrc <NULL> (not set)
lirc 1
steadykey 0
a2d_deadzone 0.300000
# ctrlr <NULL> (not set)
digital none
usbpspad 1
rapidfire 0

I think it's better to configure the xmamerc because it saves time in launcher.

Thanks for the positive energy!

===========================================================================================


Guys, I bought a adaptor to use my 4 old xbox joysticks in xbmc and emulators. Could you plese show me how to configure them to xbmc and emulators recognize them?

These is my condition right now:

Code:

root@raphael:/usr/lib# 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 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 007: ID 045e:0289 Microsoft Corp. Xbox Controller S
Bus 003 Device 006: ID 045e:0288 Microsoft Corp. Xbox Controller S Hub
Bus 003 Device 005: ID 05e3:0604 Genesys Logic, Inc. USB 1.1 Hub
Bus 003 Device 004: ID 04fc:05d8 Sunplus Technology Co., Ltd
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 058f:6377 Alcor Micro Corp. Multimedia Card Reader
Bus 001 Device 003: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Code:

root@raphael:/usr/lib# lsmod
Module * * * * * * * * *Size *Used by
xpad * * * * * * * * * 10711 *0
ff_memless * * * * * * *5109 *1 xpad
nls_utf8 * * * * * * * *1421 *0
isofs * * * * * * * * *33399 *0
cryptd * * * * * * * * *8116 *0
aes_x86_64 * * * * * * *7912 *3
aes_generic * * * * * *27607 *1 aes_x86_64
binfmt_misc * * * * * * 7960 *1
reiserfs * * * * * * *243856 *2
snd_hda_codec_analog * *78702 *1
arc4 * * * * * * * * * *1473 *2
snd_hda_intel * * * * *25741 *4
snd_hda_codec * * * * *85759 *2 snd_hda_codec_analog,snd_hda_intel
snd_hwdep * * * * * * * 6924 *1 snd_hda_codec
snd_pcm_oss * * * * * *41394 *0
snd_mixer_oss * * * * *16299 *1 snd_pcm_oss
snd_pcm * * * * * * * *87946 *4 snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_seq_dummy * * * * * 1782 *0
snd_seq_oss * * * * * *31191 *0
snd_seq_midi * * * * * *5829 *0
snd_rawmidi * * * * * *23420 *1 snd_seq_midi
snd_seq_midi_event * * *7267 *2 snd_seq_oss,snd_seq_midi
snd_seq * * * * * * * *57481 *6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
snd_timer * * * * * * *23649 *2 snd_pcm,snd_seq
snd_seq_device * * * * *6888 *5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
rtl8187 * * * * * * * *53204 *0
mac80211 * * * * * * *238896 *1 rtl8187
fbcon * * * * * * * * *39270 *72
led_class * * * * * * * 3764 *2 xpad,rtl8187
tileblit * * * * * * * *2487 *1 fbcon
snd * * * * * * * * * *71251 *19 snd_hda_codec_analog,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
cfg80211 * * * * * * *148725 *2 rtl8187,mac80211
font * * * * * * * * * *8053 *1 fbcon
bitblit * * * * * * * * 5811 *1 fbcon
eeprom_93cx6 * * * * * *1765 *1 rtl8187
softcursor * * * * * * *1565 *1 bitblit
soundcore * * * * * * * 8052 *1 snd
joydev * * * * * * * * 11104 *0
serio_raw * * * * * * * 4918 *0
snd_page_alloc * * * * *8500 *2 snd_hda_intel,snd_pcm
asus_atk0110 * * * * * 10033 *0
nvidia * * * * * * * 8096262 *34
vga16fb * * * * * * * *12757 *1
vgastate * * * * * * * *9857 *1 vga16fb
intel_agp * * * * * * *29319 *0
lp * * * * * * * * * * *9336 *0
parport * * * * * * * *37160 *1 lp
hid_sunplus * * * * * * 1691 *0
ohci1394 * * * * * * * 30260 *0
r8169 * * * * * * * * *39714 *0
usbhid * * * * * * * * 41116 *0
usb_storage * * * * * *49961 *0
mii * * * * * * * * * * 5237 *1 r8169
hid * * * * * * * * * *83472 *2 hid_sunplus,usbhid
ieee1394 * * * * * * * 94771 *1 ohci1394
pata_jmicron * * * * * *2747 *0
ahci * * * * * * * * * 37870 *0
sky2 * * * * * * * * * 48835 *0

dmesg:

Code:

[37606.671876] usb 3-1.3.1: new full speed USB device using uhci_hcd and address 7
[37606.798990] usb 3-1.3.1: configuration #1 chosen from 1 choice
[37606.857456] input: Microsoft X-Box pad v2 (US) as /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.3/3-1.3.1/3-1.3.1:1.0/input/input8
[37606.857652] usbcore: registered new interface driver xpad
[37606.857821] xpad: X-Box pad driver

[ral67]

I personally run my machine 24/7, so I have no experience with suspend/resume. Perhaps others may have experienced the same thing. Sorry I can't help.

thanks - too bad

I've tried awef's instructions and got the latest xboxdrv from the repository but still no go after wakeup

I've noticed that I also cant wake the Asrock up using the xbox wireless controller instead of the IR remote - dont know if thats even supposed to work

[ral67]

You can generally turn the system off by clicking the right thumbstick and going to "shut down" in that menu.

Turning a system on or coming out of suspend (or, indeed, xboxdrv working after resume from suspend at all!) does not currently work.

I'd love to figure out the suspend issue, but the issue does not seem to be something that is obvious to myself or grumbel and I haven't had too much time to hack at it lately.

=darwin

any progress getting xboxdrv to work after a resume ?

I've tried the obvious - like killing the old xboxdrv and starting a new one via /etc/pm/sleep.d but that doesnt help

thanks

[awef]

any progress getting xboxdrv to work after a resume ?

I've tried the obvious - like killing the old xboxdrv and starting a new one via /etc/pm/sleep.d but that doesnt help

thanks

My experience has been that the USB dongle is very temperamental, and if it isn't shut down cleanly it won't be available on the next boot, etc. It may be an issue not with xboxdrv at all, but with the dongle. Are you definitely cleanly 'unmounting' the dongle on sleep? not just killing xboxdrv but actually cleanly shutting down the dongle?

[ral67]

can you tell me how to cleanly shutdown the dongle?

I had to kill xboxdrv with -9 since it wont exit on the normal -15

[awef]

can you tell me how to cleanly shutdown the dongle?

I had to kill xboxdrv with -9 since it wont exit on the normal -15

I've no idea, sorry.. just suggesting a line of investigation.

[darwin]

any progress getting xboxdrv to work after a resume ?

I've tried the obvious - like killing the old xboxdrv and starting a new one via /etc/pm/sleep.d but that doesnt help

I believe this doesn't work for the same reason there is a race condition at startup time : XBMC doesn't appear to dynamically detect the driver being started. This is kinda weird, because I'm pretty sure it used to.

I'm pretty confident the /etc/pm/sleep.d method would work if XBMC could see the "new" xboxdrv..

=darwin

[ral67]

I'm not so sure its XBMC related - when I manually start xboxdrv it doesnt even create the ev devices input7 and js0

[lightshow12]

I tired following the directions for Ubuntu 8.04 and it wouldn't compile correctly. I'm using the Crystalbuntu OS (which is just Ubuntu 8.04 put on a patchstick for the AppleTv XBMC).

Has anyone had success with Ubuntu 8.04?