run into another issue: when i change settings (language, continues) in the atomiswave-servicemenu and push "save & exit"
I mean, yeah. You've just made the nvram read-only, and now you're trying to save changes to it. That ain't gonna work. You'd have to do all that before you locked the file, while it was still writable.
Oops! Missed the part where you said it even happens without changing the permissions.
I changed it because I found emulation station running first was affecting the performance of the pi when doing normal desktop processes and it would quickly get annoying to have to exit emulation station and type startx to get to the desktop(for me let alone my son).
will go back to searching and see if i can figure something else out.
That might set your whole system as 'read-only' (i.e. any modifications are discarded on reboot). I'd appreciate if you wouldn't use any fowl language, we're trying to - ironically ! - keep the forum an all ages place.
alright, sorry about that, new to retropie and it's forum.
also, about what you said about the "whole system", it said boot partition when i enabled it, but at this point i give up.
it's gonna suck to have to format my pi but whatever, i reinstalled raspbian 6 times on tuesday trying to get retropie to run on a raspbian installation, before realizing that it wouldn't launch any emulators.
(maybe it not launching anything was related to the screen issue..?)
@norbit911 Why do it backwards ? You can start the Desktop from EmulationStation, so leave EmulationStation running by default. If you wish to run the desktop also when exiting EmulationStation, modify the autostart.sh file and run the desktop startup command after the emulationstation line.
I'm not sure why you'd want to downgrade to 4.6 is you already have a 4.7 system (even if on Stretch) ? If the upgrade that broke your install is from the Raspbian updates, then I don't see why the RetroPie version would make a difference.
The reasons are complex, as the upgrade to 4.7 both introduced and removed some bug symptoms I was trying to debug on something else I am working on, and others report on RPi3 B+ stretch and RetroPie 4.6. And now I’m back to v4.4 from backup on the same SD card. I’d like to get back to the v4.6 state everything was in... ;-)
I don’t know for certain if the OS upgrade that broke other things came from “apt-get -y dist-upgrade” in the RetroPie upgrade script, or if I ran an upgrade my self.
Anyways, I guess I have to accept my losses, and let this be yet another life lesson on taking an image backup before making bigger changes. Think I got a little carried away in debugging mode... ;-)
This is not guaranteed to work, since some of the emulators have been updated and - as a consequence - some of the scripts in RetroPie have been updated to support it.
Ok now I think I understand better. The complete v4.6 “state” was lost with the removal of the binaries, and is not maintained with information about commit history for external and other source files to compile from the 4.6 install script?
I guess I will use this opportunity to upgrade to buster and RetroPie 4.7 on this RPi3 B+.
This day would’ve come eventually, anyways, and it worked like a charm on my RPi4.