RetroPie 4.3.17 Stretch images
-
@fluffypillow @psyke83 gave an easy to understand answer here.
-
-
To allow emulationstation to launch Xorg you must edit the file /etc/X11/Xwrapper.config
and replace allowed_users=console
by allowed_users=anybody
-
I use retropie with a rpi3 and a xin-mo controller.
Adding usbhid.quirks=0x16c0:0x05e1:0x040 in the cmdline.txt file does not seem to work anymore.forget this post, this tip is working perfectly !
-
@bb2k dpkg reconfigure didn't seem to work like it used to, probably changes with systemd.
The following command is the former equivalent
sudo dpkg-reconfigure xserver-xorg-legacy
-
Hello,
Another bug.
Compiling lr-mame or lr-mame-2016 will result of a compil error.
(I managed to compile mame 2016 in retropie in jessie)here is the error i got for lr-mame :
Archiving libatari.a... Compiling src/mame/drivers/mpu4union.cpp... Compiling src/mame/drivers/mpu4vid.cpp... Compiling src/mame/drivers/bfcobra.cpp... Compiling src/mame/drivers/bfm_ad5.cpp... Compiling src/mame/drivers/bfm_sc1.cpp... Compiling src/mame/drivers/bfm_sc2.cpp... Compiling src/mame/drivers/bfm_sc4.cpp... {standard input}: Assembler messages: {standard input}:76226: Warning: end of file not at end of a line; newline inserted {standard input}:77479: Error: bad instruction `_znulr8device_te3644_' g++: internal compiler error: Killed (program cc1plus) Please submit a full bug report, with preprocessed source if appropriate. See <file:///usr/share/doc/gcc-6/README.Bugs> for instructions. barcrest.make:802: recipe for target '../../../../libretro/obj/libretro/src/mame/drivers/mpu4sw.o' failed make[2]: *** [../../../../libretro/obj/libretro/src/mame/drivers/mpu4sw.o] Error 4 Makefile:124: recipe for target 'barcrest' failed make[1]: *** [barcrest] Error 2 make[1]: *** Waiting for unfinished jobs.... Compiling src/mame/drivers/bfm_sc5.cpp... g++: internal compiler error: Killed (program cc1plus) Please submit a full bug report, with preprocessed source if appropriate. See <file:///usr/share/doc/gcc-6/README.Bugs> for instructions. bfm.make:739: recipe for target '../../../../libretro/obj/libretro/src/mame/drivers/bfm_sc4.o' failed make[2]: *** [../../../../libretro/obj/libretro/src/mame/drivers/bfm_sc4.o] Error 4 make[2]: *** Waiting for unfinished jobs.... Makefile:127: recipe for target 'bfm' failed make[1]: *** [bfm] Error 2 makefile:1273: recipe for target 'linux' failed make: *** [linux] Error 2 Removing additional swap /home/pi Could not successfully build lr-mame - MAME emulator - MAME (current) port for libretro (/home/pi/RetroPie-Setup/tmp/build/lr-mame/mamearcade_libretro.so not found). Log ended at: Sat 17 Feb 00:58:24 CET 2018 Total running time: 4 hours, 57 mins, 17 secs
-
@bb2k you ran out of memory. Some may need more swap added, but note that experimental emulators are not all yet tested on stretch. I'm currently working through them. Exiting ES may help.
-
@buzz ok managed to compile lrmame-2016 with 1G of swap
I'll try to compile lr-mame as well
-
@BuZz Some questions :
- do you prefer us to use this image lie we do with our regular setup, or do you have particular things you want to be tested ? (like compilation as @bb2k does) ?
- will this image be updated through regular retropie update script, or do we'll have to re-image our SD for new test versions ? AKA basically can I use this image as a base for my main setup (knowing that bugs are likely to occur), or is it better to use it for testing purpose only, without transferring all roms, saves, ... ?
-
Just updated Pegasus, it's linked to the brcm* libs now.
-
@fluffypillow can confirm this is now running on stetch, there are a few controller things to sort out but they are specific to pegasus and not stretch. thanks!
-
Minecraft fails with the same user x server error when launching from ES, will be fixed with the same fix as pixel
List of tested working experimental packages
oricutron
minivmac
ti99sim
sdltrs
lr-dinothawr
cdogs-sdl
cgenius
srb2 -
This post is deleted! -
Minecraft seems to launch and play fine for me without having to change any configuration. The mouse cursor acts odd in the initial menu, but selecting via keyboard, it works.
-
This is the failed compilation log for openblok on raspbian stretch:
-
I understand is probably not even a bug but wanted to share.
Bluetooth Audio - bluealsa is not included on Stretch Lite (which is why I assume it isn't in Retropie either, and probably isn't needed by default for retropie). It is easy to install now just use "sudo apt-get install bluealsa". The other step that is needed is to also set a default PCM to point toward bluealsa with your mac address for the bluetooth device. I can provide / link to details on setting up. I don't know the retropie packaging system and if this could or should be put as experimental or if people should just run apt-get themselves anyway. There is issues with lag anyway.
The issue is with audio lag over bluetooth. I am not sure if / how to configure, but it is basically a 1 second delay which probably means bluetooth audio is only good for playing music. Video / Games would be super annoying with that lag. Googling didn't help me find a solution. Some say to disable wifi as they both run on 2.4ghz, but that had no effect. I think that is only for quality issues anyway, not the lag due to what I think is just buffering.
Every once in a while people ask about bluetooth audio on reddit, so I will watch and or proactive put out a post when this is released. I was super hopeful with stretch since bluealsa makes it way easier than before, but the lag makes me sad.
Again there is probably nothing for retropie to do, but since questions could come up I wanted to share.
-
@maz Thanks for following this, as this is the one feature that I personally am looking for the most out of stretch.
-
@herb_fargus Fixed OpenBlok, thanks.
I've also tried Super Mario War, and while your fork builds successfully, it segfaults on launch, apparently caused by an
SDL_DisplayFormat
error. The SDL2 version works fine. -
@fluffypillow I tested the binary and compiling from source on my pi 3 on stretch and it seems to work fine. My fork is split out just for use on the pi but I wonder if it would merit any benefit to build off your latest fork despite the netplay instability as I trust your code over mine.
-
@herb_fargus Ah you're right, it does work from binary. Unfortunately other than the netplay and the SDL2 port, most of the time was spent trying to make the code maintainable, so there aren't too many visible features :( The SDL2 port might be useful though.
PS. It seems to work fine from source too now.
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.