4.0-rc2 images are available for testing.
-
This is related to the issue. It's a compatibility problem with the current kernel. I've not looked into it yet, but it's likely something that needs fixing in the upstream kernel or in xboxdrv
-
@Riverstorm Please can you try this for me in case it's related to a change in the fork of xboxdrv we are using. Please first update retropie-setup then install the raspbian xboxdrv
sudo apt-get install xboxdrv
then edit
/etc/rc.local
and change the xboxdrv line from/opt/retropie/supplementary/xboxdrv/bin/xboxdrv
to/usr/bin/xboxdrv
-
@Riverstorm also please try adding
rmmod xpad; sleep 2
to a line before it in/etc/rc.local
-
@BuZz said in 4.0-beta2 images are available for testing.:
you could try the latest xpad driver instead of the xboxdrv - https://github.com/RetroPie/RetroPie-Setup/issues/1277#issuecomment-233139295
Ok so I did this and it worked. At first I had the XBOX driver enabled and they all connected as controller one but none worked. After disabling the driver it worked perfect. Minor issue is the flashing circle on all the controllers, a small pile, no idea who's player 1, 2, etc. except to pickup the controller and try it. ;)
On the other suggested testing I need to reimage back to the original 4.0-beta 2 first before update and loading the driver?
-
LED support is in the raspberry pi kernel but not yet packaged. Next kernel update will have it and no more flashing.
I would still be interested if you can test the xboxdrv changes I mentioned, as it may help me workaround the issue for those that want to use xboxdrv. Cheers
-
Just an minor detail, but if you mind putting the pre-release tag on the 4.0-beta2 image release and when the 4.0-beta3 image release comes out, this would be greatly appreciated. Thanks!
-
Strange as I had the pre-release tag set before - at least I remember setting it. Maybe it got edited/removed at some point. Set again. Thanks for the heads up.
-
Sorry if I was nit-picking...
-
Not at all - in fact it was incorrectly showing in the downloads on the main site which I didn't want.
4.0 may come out soon after beta3 as most of the issues relating to the recent retropie-setup changes have been sorted now I think.
-
Thanks! :)
-
@me
when installing lxde, you are now given the option to fix the permissions so startx can be launched from ESI also fixed up the dxx-rebirth launch links - please update retropie-setup and reinstall it from binary.
-
@Riverstorm said in 4.0-beta2 images are available for testing.:
On the other suggested testing I need to reimage back to the original 4.0-beta 2 first before update and loading the driver?
no. can just do it from your updated image. I just need to see if forcing removal of the xpad driver helps before launching xboxdrv, and also if the packaged raspbian xboxdrv behaves differently from our updated one.
This testing would be very helpful - thanks.
-
@BuZz said in 4.0-beta2 images are available for testing.:
@Riverstorm said in 4.0-beta2 images are available for testing.:
On the other suggested testing I need to reimage back to the original 4.0-beta 2 first before update and loading the driver?
no. can just do it from your updated image. I just need to see if forcing removal of the xpad driver helps before launching xboxdrv, and also if the packaged raspbian xboxdrv behaves differently from our updated one.
This testing would be very helpful - thanks.
Ok, I actually did a fresh image already and updated it. I do have a quick question. I will need to install and configure the xboxdrv first so the correct lines are part of the rc.local so I can modify them?
-
@Riverstorm yes
-
@BuZz said in 4.0-beta2 images are available for testing.:
@Riverstorm yes
Thanks Buzz, it seemed logical after looking at the rc.local but I wanted to verify it just in case.
-
@BuZz said in 4.0-beta2 images are available for testing.:
@Riverstorm said in 4.0-beta2 images are available for testing.:
On the other suggested testing I need to reimage back to the original 4.0-beta 2 first before update and loading the driver?
no. can just do it from your updated image. I just need to see if forcing removal of the xpad driver helps before launching xboxdrv, and also if the packaged raspbian xboxdrv behaves differently from our updated one.
This testing would be very helpful - thanks.
I am not sure on the intended results but this setup seems even worse. I can get them connected as 1, 3 & 4 but not 2 it flashes the green ring. I can power them off and on and they will reconnect (green quadrant light for proper controller connection) but the issue is none of them work. I can't even configure them for input let alone use them.
Here's slightly different errors when exiting ES with Ctrl-F4:
[ERROR] USBController::on_read_data(): USB read failure: 32: LIBUSB_TRANSFER_ERROR
[ERROR] USBController::on_write_data(): USB write failure: 12: LIBUSB_TRANSFER_ERROREDIT: Here's my /etc/rc.local modifications after installing the xboxdrv.
rmmod xpad; sleep 2
"/usr/bin/xboxdrv" --daemon --detach --dbus disabled --detach-kernel-driver --id 0 --led 2 --deadzone 4000 --silent --trigger-as-button --next-controller --id 1 --led 3 --deadzone 4000 --silent --trigger-as-button --next-controller --id 2 --led 4 --deadzone 4000 --silent --trigger-as-button --next-controller --id 3 --led 5 --deadzone 4000 --silent --trigger-as-button
-
thanks - and with the
rmmod xpad; sleep 2
but the original xboxdrv line also ? Any difference ?also please can you post the output of
lsmod
after putting the xboxdrv line back as it was (but keeping the rmmod) -
@BuZz said in 4.0-beta2 images are available for testing.:
thanks - and with the
rmmod xpad; sleep 2
but the original xboxdrv line also ? Any difference ?also please can you post the output of
lsmod
after putting the xboxdrv line back as it was (but keeping the rmmod)Modified lines in /etc/rc.local:
rmmod xpad; sleep 2
"/opt/retropie/supplementary/xboxdrv/bin/xboxdrv" --daemon --detach --dbus disabled --detach-kernel-driver --id 0 --led 2 --deadzone 4000 --silent --trigger-as-button --next-controller --id 1 --led 3 --deadzone 4000 --silent --trigger-as-button --next-controller --id 2 --led 4 --deadzone 4000 --silent --trigger-as-button --next-controller --id 3 --led 5 --deadzone 4000 --silent --trigger-as-button
It's different but not good. I was able to get a stick configured via Configure Input but they all just have the flashing green circles. I could navigate with controller one. Entering a game controllers 2-4 didn't work. After a disconnect and reconnect of controller one I lost connection to all of them.
lsmod output:
pi@retropie:~ $ lsmod Module Size Used by bnep 10340 2 hci_uart 17943 1 btbcm 5929 1 hci_uart bluetooth 326105 22 bnep,btbcm,hci_uart brcmfmac 186343 0 brcmutil 5661 1 brcmfmac cfg80211 427855 1 brcmfmac rfkill 16037 4 cfg80211,bluetooth snd_bcm2835 20511 0 evdev 11396 5 snd_pcm 75698 1 snd_bcm2835 joydev 9024 0 snd_timer 19160 1 snd_pcm snd 51844 3 snd_bcm2835,snd_timer,snd_pcm bcm2835_gpiomem 3040 0 bcm2835_wdt 3225 0 ff_memless 4750 0 uio_pdrv_genirq 3164 0 uio 8000 1 uio_pdrv_genirq uinput 7454 4 fuse 83461 1 ipv6 347530 34
-
@Buzz I need to go back and recheck this testing (xboxdrv with rmmod xpad). I need about an hour to finish something and will post back for sure on this.
-
I just wanted to verify I was in lr-mame2003 as it has joysticks pre-configured (Gauntlet is my 4 player test). With this configuration arrangement all the joysticks flash even the working one when connected so to test them I play a game. That is unless the other sticks should all be able to scroll through the options in ES. Joystick one works and I was able to fully use it to select & play. Joysticks 2-4 flash green with no response.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.