4.0-rc2 images are available for testing.

Riverstorm

@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.

Riverstorm

@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_ERROR

EDIT: 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

BuZz

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)

Riverstorm

@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

Riverstorm

@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.

Riverstorm

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.

BuZz

4.0-rc1 is released - see first post in thread.

BuZz

@Riverstorm thanks for the feedback.

cooky069

Not sure if this is a bug or not but I tried 4.0-rc1 last nite and noticed that when I tried setting up overlys none were available . The only option was unset . I looked in to the file system and it appears the entire overlays directory is missing. Decided to try beta2 and the same thing happened but 3.8.1 is fine

BuZz

@cooky069 you need to install them from packages -core - retroarch - configure or setup/tools - retroarch. You can now keep them updated separately from retroarch

cooky069

Thanks I'll have a look when I get chance . I was in configuration then all retroarch cfg , was able to set overlays on but when I clicked on the next option down to select an overly is when I encountered the problem . But if they need installing first then I must have missed something, so hopefully that's it

Riverstorm

@BuZz said in 4.0-rc1 images are available for testing.:

4.0-rc1 is released - see first post in thread.

Is there any additional tweaks to the xboxdrv that need testing or will we need to use the xpad driver steps for the coming GA?

BuZz

@Riverstorm you may well need to use the xpad driver if xboxdrv isn't working. the built in kernel xpad driver should work with 360 controllers, although the led flashes (upstream kernel config change fixes it in the next raspberry pi kernel update)

Riverstorm

@BuZz said in 4.0-rc1 images are available for testing.:

@Riverstorm you may well need to use the xpad driver if xboxdrv isn't working. the built in kernel xpad driver should work with 360 controllers, although the led flashes (upstream kernel config change fixes it in the next raspberry pi kernel update)

Ok that sounds good. Would the kernel update be announced here on the forums anywhere or is there a good link to watch for that enhancement?

What I really liked about the xboxdrv is the values are consistent on both wired and wireless. If I remember correctly switching back to the xpad driver several inputs in MAME need tweaked as the values are all different and most of the emulators weren't setup to support joysticks out of the box. Except lr-mame2003 I think Dank added joystick support by default.

BuZz

https://github.com/raspberrypi/firmware
https://github.com/raspberrypi/linux

updates hit the firmware repo first, and gets packaged later.

Riverstorm

@BuZz said in 4.0-rc1 images are available for testing.:

https://github.com/raspberrypi/firmware
https://github.com/raspberrypi/linux

updates hit the firmware repo first, and gets packaged later.

Thanks Buzz, I will keep an eye out. Sorry one last question will the xboxdrv be phased out in favor of the xpad driver on future releases?

BuZz

I don't know - depends on xboxdrv development vs kernel xpad features

Riverstorm

@BuZz said in 4.0-rc1 images are available for testing.:

I don't know - depends on xboxdrv development vs kernel xpad features

Ok, that sounds good. If you need a tester for any additional changes to the xboxdrv just let me know as I do use them regularly and willing to troubleshoot whatever I can. :)

BennyProfane

@BuZz thanks for all your hard work - just tried 4.0-rc1, really happy with this version and just have 1 note/1 minor issue (which I don't think should stop the release of 4.0 in any way):

1- I'm trying to get all 3 ES+ kodi + lxde/desktop running. When the RetroPie script has installed lxde, even after rebooting, many commands fail to run. This is because the startx command needs to be called for the desktop to finish setting up its thing -- and this took me a while to figure out: could this be documented clearly within the script (e.g. popup asking you to make the call), or just get the script to force the command after the installation process?

2- The new ability to autostart kodi is something I've wanted for a while, so thanks for that, however the exit option fails to return to emulationstation (just kills kodi and turns my tv off!). I've seen this thread but it looks like the autostart does call kodi rather than kodi-standalone, so am stuck on this one...

I'm also using a PS3 bluetooth controller and that all worked fine.

BuZz

1 - LXDE - when you install lxde it installs an entry in Ports for launching it (Did you install it from the raspbian tools menu?).startx is mentioned on the wiki in the FAQ.

2 - are you using CEC ? that may be set to turn off screen on exit - you can change that in Kodi. I launch Kodi before ES on my setups and they exit fine to ES.