4.0-rc2 images are available for testing.

Riverstorm

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

you should update everything including os packages for testing please.

I updated everything and did a reboot. It's still very eradicate. It seems a hit or miss on if the controller will connect or just flash (green circle).

I had two flashing controllers and did a reboot one connected as controller one and the second continued to flash.

I did a reboot and left all the controllers off. After it fully booted up I powered on two controllers about 3 seconds apart and both connected as controller one (upper left quadrant glowing green on both). The other 2 wouldn't connect at all. So I shut off the two working ones and tried reconnecting them again but neither would connect a second time.

If you get disconnected after you're connected the only thing to do is reboot it seems. You can't always get connected though. I can't find a pattern in why sometimes they connect and other times not. It's very sporadic still.

I have 4 controllers all 1403 (two older from the Modern Warfare 2 era) and two newer. It's a hit or miss on which will connect and which won't. There seems no rhyme or reason.

EDIT: I have to head out for the evening but if there's a next step or any logs I can send you just let me know and I'll get them sent first thing tomorrow.

BuZz

you could try the latest xpad driver instead of the xboxdrv - https://github.com/RetroPie/RetroPie-Setup/issues/1277#issuecomment-233139295

Riverstorm

@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 will try that. Also something new when exiting the ES menu with F4. I have two errors, both the same:

[ERROR] USBController::on_write_data(): USB write failure: 12: LIBUSB_TRANSFER_ERROR
[ERROR] USBController::on_write_data(): USB write failure: 12: LIBUSB_TRANSFER_ERROR

I have two things plugged in to the USB ports a keyboard and the Microsoft wireless receiver.

BuZz

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

BuZz

@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

BuZz

@Riverstorm also please try adding rmmod xpad; sleep 2 to a line before it in /etc/rc.local

Riverstorm

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

BuZz

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

PokeEngineer

@BuZz

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!

BuZz

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.

PokeEngineer

@BuZz

Sorry if I was nit-picking...

BuZz

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.

PokeEngineer

@BuZz

Thanks! :)

BuZz

@me
when installing lxde, you are now given the option to fix the permissions so startx can be launched from ES

I also fixed up the dxx-rebirth launch links - please update retropie-setup and reinstall it from binary.

BuZz

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

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.

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?

BuZz

@Riverstorm yes

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)