RetroPie 4.3.17 Stretch images

meleu

@sano said in RetroPie 4.3.11 Stretch images for testing:

Joystick selection doesn't seem to work anymore on this image.

:(

Thanks for the heads-up. Will try to check it when I find some free time.

Sano

Thanks a lot @meleu ;)
And try to enjoy your free time, this is not so critical :)

I think I narrowed it down to the jslist executable.

Here are 2 results before and after powering on a DS3 :

pi@retropie:~ $ /opt/retropie/supplementary/joystick-selection/jslist 
0:HORI CO.,LTD. Fighting Stick mini 4
pi@retropie:~ $ 
pi@retropie:~ $ /opt/retropie/supplementary/joystick-selection/jslist 
0:Sony PLAYSTATION(R)3 Controller
1:HORI CO.,LTD. Fighting Stick mini 4

Whatever, Retroarch still sees Hori as the 1st controller and DS3 as the 2nd, hence the issue...
If it can help, from the OS point of view, Hori is /dev/input/js0 and DS3 is /dev/input/js1

psyke83

I'm not too familiar with the controller order stuff, but isn't the HORI controller a PS3-compatible controller? That means it'll use the hid-sony driver.

That's a relevant detail, because the old ps3controllerdriver works differently. The sony_hid driver (with or without my module) would use the name Sony PLAYSTATION(R)3 Controller, but ps3controller (assuming you use the DS3 via bluetooth) selects the name PLAYSTATION(R)3 Controller, and it's enumerated through a uinput virtual input device.

If this is a sixaxis bug (or if not a bug, different behaviour from the driver), then it's off-topic regarding the stretch image and I would suggest continuing the discussion in my thread to keep this one on track.

FWIW, I have two official DS3 pads, and they seem to select the correct led corresponding to the controller number.

Sano

For information, I updated today, including OS packages, and the console autologin option reverted back to false, resulting in a console login prompt at boot.
I had to reconfigure it through raspi-config in order to boot to ES.
If someone could try to reproduce this... It could be an upstream bug.

BuZz

@sano I've seen this also. It is an upstream bug (unless they somehow wanted this by design, which I doubt).

BuZz

@sano It's caused by the systemd package update - from the upgrade log

Setting up systemd (232-25+deb9u2) ...
addgroup: The group `systemd-journal' already exists as a system group. Exiting.
Removed /etc/systemd/system/getty.target.wants/getty@tty1.service.
Created symlink /etc/systemd/system/getty.target.wants/getty@tty1.service → /lib/systemd/system/getty@.service.

I will report this upstream.

BuZz

Issue opened here - https://bugs.launchpad.net/raspbian/+bug/1755811

BuZz

4.3.14 stretch images are now available in the first post.

I will be testing them out on my Raspberry Pi 3 B+ when it arrives. But the packages are up to date, so they should work.

Sano

@buzz Nice, I was wondering if you saw my post about this.
Tagging interested people from other threads : @ganondork @pjft @tashman
Thanks for them, I didn't buy a Pi 3B+ (not yet).

BuZz

Looks like there may be a problem with the images - as I can't boot them here from a quick test. Possibly due to upstream Raspbian changes that are incompatible with the build script. Will update with more information soon.

[edit] Actually it could be my desktop/build system, as I updated it recently.

[edit] It was: They are missing the fat partition :-)

mkfs.vfat: command not found

Have fixed up the image builder dependencies. Currently building 4.3.15 images.

ohmycommodore

@buzz Got a 3B+ already. I'm not super-advanced, but happy to use my extra card with the new Pi to see if and how things work. Ping me when you have what you think is a working image and I'll grab it.

BuZz

4.3.15 stretch images are now available in the first post. They should work on the Raspberry Pi 3 B+ but I have not yet tested. They boot on my Raspberry Pi 3 Model B.

The images are based on the latest Raspbian Stretch Lite.

BuZz

I can confirm the 2/3/3+ image works correctly on the new Raspberry Pi 3 Model B+

MikOzzZ

@buzz you happen to have the wifi or the network with pi 3b + and 4.3.15?

BuZz

@mikozzz Just tested LAN - for Wifi on the new Raspberry Pi 3 Model B+ you need to set the country (same as with Raspbian Stretch)

WiFi is disabled until wireless regulatory domain is set (Pi 3 B+ only)
- The domain can be done through 'Raspberry Pi Configuration' (rc_gui),
'raspi-config' or by setting 'country=' to an appropriate ISO 3166
alpha2 country code in /etc/wpa_supplicant/wpa_supplicant.conf.

MikOzzZ

@buzz I can not find the network with the network too , i use winscp

BuZz

@mikozzz that's not enough information for me to go on. Can you see the internet from the RPI ? Did you enable SSH ? How is your RPI connected?

MikOzzZ

@buzz ^^ not much slept sorry obviously

ohmycommodore

The .15 image boots up fine for me.

No, i can't see my wifi networks straight away (i have both 2.4 and 5.0).

Found the setting to set Wifi Country (Canada for me). Pi asked for reboot, which i did. Now i can see both 2.4 and 5.0 networks. That got me an IP so i assume all is well.

edit:

I also set Pi name and password before looking at the wifi stuff.
Wifi indeed works as it can find RPie Setup Script and a couple of themes.

edit:

Based on a quick test with N64 Rogue Squadron, the music is still pretty scratchy and the game sluggish as usual. However, N64 Mario Kart seems better on both counts than I recall.

Finally, I can't seem to get my Mac Transmit app to connect. I can browse it in the Finder just fine, though I always found Transmit gets me to a higher (root?) starting point. I can still connect via Finder or Transmit with my old Pi fine. Yes I've enabled SSH. Transmit settings are identical for the two devices, except for the IP address, which I've set aside for each device in my router.

Oh well, enough for now :)

ohmycommodore

No real -need- for me to update, and I'd normally be in that camp... though having the opportunity to grab one on release day, not at all going more than 5 mins out of my way, was just too easy to pass up :)