@tripplies we don't support third party installs, but to get the original games off you would need to transfer them off. see: https://retropie.org.uk/docs/Transferring-Roms/#transferring-roms. essentially you're doing the same process, but in the other direction. samba, SFTP or the manual copy would work. after that, install your new system on your new SD, and transfer them back in the same manner. i would be reticent to transfer configs and the emulationstation setup as those settings are likely incompatible with current retropie and could cause issues/break it.

@mitu Ok, thanks for all the fast help!

@quicksilver I ended up installing a fresh image and it worked thanks for the replies or I’d still be stuck

@Evert said in FB Alpha 0.2.97.43 Pre-Compiled Version: I understand that you can just opt to not update your system, but what if you are building a new system? back up your lr-fbalpha.so binary i guess.

@mitu I don't know why that error occurs, I don't think RetroArch uses directly this env var - may be a Wayland/screensaver warning. So I fixed that error regarding XDG_RUNTIME_DIR, maybe RetroArch does use it after all. I was mistaken when I said it flashed up when launching, it actually flashes up when exiting! Same for the CD-ROM warning. To solve it, I did the following: run: sudo sudo -V scrolled up a bit to see which environment variables are preserved. XDG_RUNTIME_DIR is not one of them. I then had to edit the sudoers file (sudo visudo) and add the following in: Defaults env_keep += "XDG_RUNTIME_DIR" Save and exit, you can then run 'sudo sudo -V' again and you'll see XDG_RUNTIME_DIR is in the list of environment variables to preserve. Reboot the system and the error should go away when quitting Retroarch. For whatever reason, sudo does not preserve this environment variable, and i'm guessing because Retroarch launches from the Retropie menu with root privileges, it cannot see or have access to this environment variable. Adding the above in preserves it, suppressing the error (after a reboot). The CD error still pops up though, but not much that can be done about that at this time it seems. FYI, this error only pops up when you quit Retroarch after launching it on its own from the Retropie menu - it doesn't come up when quitting out of a game. I guess this is because games are launched as the 'pi' user, rather than with root privileges. My question would be, is there a reason Retroarch needs to be launched with root privileges from the Retropie menu? Maybe I am misunderstanding how it launches, but that is what it looks like to me. Cheers!

@mitu There is no modification needed at all you can use multi-switch --generic command to offer an easy setup. @MaMikee Please install raspi-gpio at first with sudo apt install raspi-gpio command. There are tons of other possibilities available ;)

*about audio

@retrotinkerer Wii games will not run on a pi. You'll need much more powerful hardware for that.

@mitu Thanks so much for the help. I'll let you know how I make out.

@rbaker I checked it and nothing helped , I used brand new Kingston microSD card so it must not be reason . Anywan I will buy new one during black friday I just want to know now , can I use Pi 3 Model B heatsinks with Pi 3 Model B + if so I ahve some of them

@cmac said in Kernel Panic issue, want to preserve data: I'll give that a shot. In the case that I can back up the filesys, is copying + pasting the root of the filesys into a fresh retropie installation's filesys root work, or is there any more to it? No, that's not the way to do it. Just back up the ROMs + BIOS folders and the emulationstation's configuration folder in /home/pi/.emulationstation to save your arkwork and ROMs. You can also back-up your configurations' folder (/opt/retropie/configs/all), but I wouldn't overwrite it on a new installation unless you're sure you have the same version of RetroPie as before.

@randall8686 Use the Docs, there is a section for each emulator (system) including the file extension understood for earch one. By now, ROMs have standardized the format and extension, most of them can be zipped and the emulator will read them.

It's okay, it was from my config file...It works now ! thanks !

@chuckyp most adapters have a headphone jack on them for audio which is far better quality than the jack on the pi.

This is a forum for RetroPie, not a general Raspberry Pi forum. You might want to ask about Kodi problems on a Kodi dedicated forum/mailing list.

@bizous The email address you registered on the forum no longer exists - please update it or I will have to remove your account (as you have subscribed to some categories and emails are bouncing).

I just received my new pi and all is working now. Time to start the rebuild and customization. I tried backing my old build on my pc before i started having issues, 64gb card, but it would always fail at 39gb when writing the image to my 2tb hard drive. Even with multiple readers.

@alturis I think @johnny5126 means a power strip with one "master" socket and a number of "slave" sockets. If the device connected to the master socket draws power, the slave sockets will be powered by the strip automatically.

Well, I've half-answered my question. I somehow suspected CEC to be an issue, and lo, when I changed hdmi_ignore_cec_init to hdmi_ignore_cec, ES stalls on launch, spits out "lvl0: CECInput::mAdapter->Open failed", runs, and then works perfectly, so it's probably an issue with the libcec I'm using.