Retropie on Raspbian Buster

mitu

@geekinchief Using the manual installation instructions from the Docs.

geekinchief

@mitu I had tried that a few days ago and it failed. I'll try again.

hhromic

@geekinchief just to clarify, @mitu refers to the newly released (yesterday!) official Raspbian Buster from the foundation, not any of the experimental images. Get it from the RPI website.

mitu

@geekinchief Without any logs, it's hard to diagnose what's the problem. As @hhromic said, use the newly released image when trying to install RetroPie. Please provide any error messages/logs if you want assistance, just saying 'it failed' it's not going to help.

quicksilver

@mitu were you able to build lr-mupen64plus-next? Slightly off topic but I supposed with the release of the pi 4, the mupen64plus.sh file will need to be re-examined and modified. Im not sure that the resolution will still need to be locked to 320x240 anymore for gliden64 (hopefully) and the blacklist will need to be re-examined as well. Though I think its primarily Gizmo that maintains it, if hes still around.

mitu

@quicksilver No, I only have tried the basic install (which installs only the main and optional sections). Since it took a while, I just left it overnight on a 3B+ system and checked in the morning for errors.
I'll give lr-mupen64plus-next a try later this evening, I just want to see if a quick fix is available for mupen64plus.

EDIT: heh, it looks like the error is already reported ~~upstream~~ - https://github.com/ricrpi/mupen64plus-video-gles2n64/issues/25.

geekinchief

I am getting this error message upon completion of the install:

mitu

@geekinchief Yes, I think I got the same messages, but since the building of packages (except one) was successful, I just treated them as warnings.

libavdevice-dev has a hard dependency on libsdl-2.0.9 (required by retroarch) and it fails installation.
libusb-1.0-0-dev is installable, we'll have to see why it's not installed (required by retroarch, dolphin and xboxdrv
libxkbcommon-dev is installable, similar like before (required by retroarch).

EDIT: I see now that retroarch is not installed because of this, somehow I missed it in the log. Excluding libavdevice-dev from the dependencies makes the compilation work, probably with disabled recording capabilities.

mitu

@quicksilver lr-mupen64plus-next builds fine, I just loaded 007 to test (ran horribly) and it loaded ok.

quicksilver

@mitu Yea, that game doesnt run well using lr-mupen64plus-next on my overclocked 3b+ either. Im hopefully getting a pi 4 this friday, if my microcenter near me gets some in stock and will try to test then on the new hardware.

geekinchief

@mitu How do I exclude libavdevice-dev?

mitu

@geekinchief Update your RetroPie-Setup script and try again to build RetroArch.

geekinchief

@mitu said in Retropie on Raspbian Buster:

rc

Maybe I'm dense, but I can't find any reference to libavdevice-dev in my setup script.

mitu

@geekinchief Please re-read my previous reply.

geekinchief

@mitu So it seems that with the latest Buster everything installed but muplus64. However, emulationstation shows a black screen. Any idea if there's a workaround?

mitu

@geekinchief I didn't experience the black screen. What display/system do you have ?

BuZz

@geekinchief are you using a rpi4 ? Buster is not yet supported anyway yet, so I'm not sure how useful this thread is - unless you are able to code/debug and work on the support yourself.

geekinchief

@BuZz I am using a Pi 4, yes, so was hoping to find a way to at least try some of the emulators on it.

psyke83

This post is deleted!

mikem

I updated my RPI2 running raspbian/retropie to buster. I needed to make some adaptions to mupen64plus-video-gles2n64 [1] for mupen64plus (which i personally do not use) to build. And emulationstation does not autostart because the pi user does not login automatically anymore (need to check why), but after logging in with pi on tty1 ES starts and at least the SNES-Emulator runs fine.

[1] https://github.com/ricrpi/mupen64plus-video-gles2n64/pull/26