Cool. Thanks I'll hold of putting me new build together for now then and keep using the current one until buster/retropie release. At least Debian only release new major releases every 2 years unlike some other distros

@tribunal88 said in Upgrade to 4.4 without wiping disk: Is there a way to do a "fresh" install without formatting the SD card? Yes, but it's not recommended. If you'd like to try an in-place upgrade, follow the link above and create a backup of your card beforehand.

@mitu Thank you! I can't believe I didn't stumble upon those in my search.

@Dwarfboysim said in Upgrading from 3B to 3B +: What are OC’s? Overclocking.

No worries

@bobharris Hi, I am upgrading because I figured there will have been performance improvements that would perhaps help with various emulators. Have decided to make a full img backup, then will try doing the upgrade within Retropie and see how I get on - if it messes up for any reason I will just write my original image back and use that version, spending ages trying to get it all up and running again seems like a lot of work. I also have to build a zero from scratch for a handheld project so I have plenty to do at the moment - thanks for the replies guys!

Sorry, I thought I did. But that was in another post. That said, compiling on a threadripper 2990WX with -J80 is almost hilarious. :-)

@mitu said in 4.3 to 4.4: @weirdocollector If you followed the docs, then your bios folder will not be on the USB drive, only your ROMs, so you need to save it also. /etc/emulationstation doesn't need to be copied, unless you modified the es_systems.cfg manually in that location. That should be it. Make a backup of the sd-card also (https://retropie.org.uk/docs/Updating-RetroPie/#making-a-backup-option-1) just in case. @mitu Hi ! I've finally found the time to try to update my Retropie to 4.4, but re-reading the docs, if I've understood correctly, also the BIOS folder should be on the USB HDD, and as such should not be copied on the new 4.4 SD Card. From the docs: Now that the USB drive is mounted directly to home/pi/RetroPie, every time this directory is accessed, you're actually accessing the USB drive. As the BIOS directory is under home/pi/Retropie it seems it shouldn't be copied as it is already safely on the USB HDD. If this is true, the only directories to be copied are: /etc/emulationstation /opt/retropie/configs Once done that, the home/pi/Retropie directory have to be again mounted on the USB HDD using the procedure described in the docs. Is the above correct ? Thanks a lot for any help.

@retrogamer78 Kodi is installed from a Debian-type repository, so you can set the package status to hold to prevent automatic updates. echo kodi hold | dpkg --set-selections

@bobharris My image is "Stretch" already and I ordered this PSU now: https://www.amazon.de/gp/product/B01E75SB2C/ref=oh_aui_detailpage_o00_s00?ie=UTF8&psc=1 The user reviews of this product are great. I'm excited :) Thanks for the overclocking tip. I'll try that.

Great, thank you for the quick response I appreciate it!

@dankcushions sweet, that's great to know! Thanks!

Hi, I actually followed a guide to upgrade to stretch and deploy 4.4 over my existing setup. All looks to be running well.

@usarmyvet That depends on the emulator in question. Most emulators of Retropie are so called "cores" of RetroArch. See here how to smoothen their graphics in RetroArch and even "upgrade" them to some extend, i.e. making them look more like the vintage monitors the games were originally run on. https://retropie.org.uk/docs/Shaders-and-Smoothing/

@Lodan-Zark Worked perfect man. Now I play my raspberry b+. Thank you so much

@wizardling Shucks, I'm blushing here. But seriously no problem at all, just browsing the forum and saw your post and noticed you were using apt and was aware it sometimes can cause issues like this. The "problem" is that Linux will do exactly what you tell it to do and if you aren't fully versed in exactly how things work it can cause problems. I honestly couldn't tell you why it works, other than it handles installation of packages and dependencies differently.

@buzz Thanks - I finally got it figured out. I had been overlooking the files in sources.list.d/ and noticed that both collabora.list and raspi.list had wheezy listed. Changed them to jessie, re-ran the update/upgrade process and things started working - except sound. I also had to add dtparam=audio=on to my config.txt file for some reason, even though that had been fine previously without it. Anyway, thanks again for the help working through this problem. <3 RetroPie.

@rsn8887 it was a non fatal error in this case. I prefer that over a force pull.

Related - see my reply, here: https://retropie.org.uk/forum/topic/8091/noninteractive-installation-upgrades/7