RetroPie forum home
    • Recent
    • Tags
    • Popular
    • Home
    • Docs
    • Register
    • Login

    RetroPie 4.3.17 Stretch images

    Scheduled Pinned Locked Moved Ideas and Development
    stretchtestingbeta
    205 Posts 59 Posters 164.1k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A
      AlexJ
      last edited by

      Hello,
      Did someone tried to compile daphne-pi on stretch ?
      While it was working fine on jessie, with the same romset, it played blinded and muted on stretch.
      I tried to compile with gcc 4.9 and gcc 6.3, same result.
      Bye

      G 1 Reply Last reply Reply Quote 0
      • herb_fargusH
        herb_fargus administrators
        last edited by

        I reflashed the image for more testing but after doing so am finding it troublesome to connect my 8bitdo sf30 pro controller. It is recognised in the menu but fails to authenticate.

        (Creating device failed: org.bluez.Error.AuthentificationFailed: Authentification Failed)

        I don't know if the 8bitdo is still thinking it's connected to the old image or if I mixed something up so I'll keep digging. I imagine a reflashing of the 8bitdo firmware will probably fix it and it's probably just user error on my part but it's something to be aware of if it's persistent for other users going forward

        If you read the documentation it will answer 99% of your questions: https://retropie.org.uk/docs/

        Also if you want a solution to your problems read this first: https://retropie.org.uk/forum/topic/3/read-this-first

        1 Reply Last reply Reply Quote 0
        • G
          grant2258 Banned @AlexJ
          last edited by grant2258

          @alexj

          I know hypseus (sdl2 daphne port) is having problems on the on the pi on stretch as well the video just freezes. It also doesnt work on debian 9 x64. I wonder if its the new kernels with meltdown fixes that are effect mutex locks. I dont know if thats the same kind of problems you where having. Ill download the image and try compiling forked version of daphne and see if it works or not.

          1 Reply Last reply Reply Quote 0
          • SanoS
            Sano
            last edited by Sano

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

            Example for NES, with Dualshock3 selected for player 1 with "by name" method :

            pi@retropie:~ $ cat  /opt/retropie/configs/nes/joystick-selection.cfg 
input_player1_joypad_index = "Sony PLAYSTATION(R)3 Controller #1"

            pi@retropie:~ $ cat  /opt/retropie/configs/nes/retroarch.cfg 
# Settings made here will only override settings in the global retroarch.cfg if placed above the #include line

input_remapping_directory = "/opt/retropie/configs/nes/"

input_player1_joypad_index = "0"
# input_player2_joypad_index = "1"
# input_player3_joypad_index = "2"
# input_player4_joypad_index = "3"
#include "/opt/retropie/configs/all/retroarch.cfg"

            pi@retropie:~ $ cat  /dev/shm/runcommand.log 
--- start of joystick-selection log
joystick selection by name is ON!
joystick indexes for "nes" was configured
joystick indexes for "all" was configured
--- end of joystick-selection log
Parameters: 
Executing: /opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-fceumm/fceumm_libretro.so --config /opt/retropie/configs/nes/retroarch.cfg "/home/pi/RetroPie/roms/nes/Dr. Mario (Europe).zip" --appendconfig /dev/shm/retroarch.cfg

            Still the controller for player 1 is the other one (Hori Fighting stick mini)...

            Edit : tried with other systems : same behaviour
            I also tried to configure 2 PS3 controllers as player 1 and 2, same. Player 1 stay with the Hori stick, Player 2 is mapped with the first PS3 controller.

            Edit again : After some tests I checked the jslist files :

            pi@retropie:~ $ cat /tmp/jslist.
jslist.2Nyz  jslist.3XSC  jslist.hfJr  jslist.Tbq2  jslist.tmyw  jslist.UUnk  
pi@retropie:~ $ cat /tmp/jslist.*
0:Sony PLAYSTATION(R)3 Controller #1
1:HORI CO.,LTD. Fighting Stick mini 4 #1
0:Sony PLAYSTATION(R)3 Controller #1
1:HORI CO.,LTD. Fighting Stick mini 4 #1
0:Sony PLAYSTATION(R)3 Controller #1
1:Sony PLAYSTATION(R)3 Controller #2
2:HORI CO.,LTD. Fighting Stick mini 4 #1
0:Sony PLAYSTATION(R)3 Controller #1
1:Sony PLAYSTATION(R)3 Controller #2
2:HORI CO.,LTD. Fighting Stick mini 4 #1
0:Sony PLAYSTATION(R)3 Controller #1
1:Sony PLAYSTATION(R)3 Controller #2
2:HORI CO.,LTD. Fighting Stick mini 4 #1
0:Sony PLAYSTATION(R)3 Controller #1
1:HORI CO.,LTD. Fighting Stick mini 4 #1

            The strange thing is The Hori Controller is USB connected (and never disconnected), so it should always be index 0 (what seems to be retroarch view)...
            But his index in your script changes according to the PS3 controllers connected.

            @psyke83 Could it be that your sixaxis module somewhat forces the index of the PS3 controllers to the first ones, regardless of the already connected controllers ?
            (That would explain the active led 1 on the controller, before upgrading when I connected a DS3, the led 2 was on, because of the arcade stick being the first)

            meleuM 1 Reply Last reply Reply Quote 0
            • meleuM
              meleu @Sano
              last edited by

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

              • Useful topics
              • joystick-selection tool
              • rpie-art tool
              • achievements I made
              1 Reply Last reply Reply Quote 2
              • SanoS
                Sano
                last edited by 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

                1 Reply Last reply Reply Quote 0
                • P
                  psyke83 Global Moderator
                  last edited by 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.

                  SanoS 1 Reply Last reply Reply Quote 0
                  • SanoS
                    Sano
                    last edited by 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.

                    BuZzB 2 Replies Last reply Reply Quote 0
                    • BuZzB
                      BuZz administrators @Sano
                      last edited by

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

                      To help us help you - please make sure you read the sticky topics before posting - https://retropie.org.uk/forum/topic/3/read-this-first

                      1 Reply Last reply Reply Quote 1
                      • BuZzB
                        BuZz administrators @Sano
                        last edited by 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.

                        To help us help you - please make sure you read the sticky topics before posting - https://retropie.org.uk/forum/topic/3/read-this-first

                        BuZzB 1 Reply Last reply Reply Quote 1
                        • BuZzB
                          BuZz administrators @BuZz
                          last edited by BuZz

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

                          To help us help you - please make sure you read the sticky topics before posting - https://retropie.org.uk/forum/topic/3/read-this-first

                          1 Reply Last reply Reply Quote 0
                          • BuZzB
                            BuZz administrators
                            last edited by 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.

                            To help us help you - please make sure you read the sticky topics before posting - https://retropie.org.uk/forum/topic/3/read-this-first

                            SanoS 1 Reply Last reply Reply Quote 2
                            • SanoS
                              Sano @BuZz
                              last edited by 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).

                              1 Reply Last reply Reply Quote 1
                              • BuZzB
                                BuZz administrators
                                last edited by 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.

                                To help us help you - please make sure you read the sticky topics before posting - https://retropie.org.uk/forum/topic/3/read-this-first

                                ohmycommodoreO 1 Reply Last reply Reply Quote 1
                                • ohmycommodoreO
                                  ohmycommodore @BuZz
                                  last edited by

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

                                  1 Reply Last reply Reply Quote 0
                                  • BuZzB
                                    BuZz administrators
                                    last edited by

                                    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.

                                    To help us help you - please make sure you read the sticky topics before posting - https://retropie.org.uk/forum/topic/3/read-this-first

                                    1 Reply Last reply Reply Quote 1
                                    • BuZzB
                                      BuZz administrators
                                      last edited by

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

                                      To help us help you - please make sure you read the sticky topics before posting - https://retropie.org.uk/forum/topic/3/read-this-first

                                      MikOzzZM 1 Reply Last reply Reply Quote 4
                                      • MikOzzZM
                                        MikOzzZ @BuZz
                                        last edited by

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

                                        BuZzB 1 Reply Last reply Reply Quote 0
                                        • BuZzB
                                          BuZz administrators @MikOzzZ
                                          last edited by 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.

                                          To help us help you - please make sure you read the sticky topics before posting - https://retropie.org.uk/forum/topic/3/read-this-first

                                          MikOzzZM 1 Reply Last reply Reply Quote 0
                                          • MikOzzZM
                                            MikOzzZ @BuZz
                                            last edited by MikOzzZ

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

                                            BuZzB 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            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.