Setting 4.0.2 again and Kodi won´t launch

josete2k

It's simple, I'm trying to set the 4.0.2 again because the psx and n64 emulators and I cannot launch Kodi.

Fresh 4.0.2 install.
Install Kodi from optional packages.

It appears on the PORTS section, but when launched it goes back to the main menu.

I placed a snes rom for testing and it works, so I assume that the SD is OK.

Is there any issue with binary installation in 4.0.2?

Do I need to update core packages?

Thanks in advance.

AlexMurphy

@josete2k I would advise you to install the latest image from the RetroPie site. The image is 4.1, then when up and running update the setup script and then all packages including the os when prompted. The latest version is 4.1.14. A lot has changed since 4.0.2 including Kodi which is Krypton 17 since the start of the month.

josete2k

@AlexMurphy Thanks... I asume so, that kodi 17 is not compatible with 4.0.2

The reason for 4.0.2 is that I have better performance in psx and N64 emulation instead 4.1.

Rascas

Kodi 17 should work on older versions of RetroPie, but you should update the RetroPie-Setup scripts and update/install Kodi again. You don't need to update the emulators.
And please provide more info and the logs, like explained here:
https://retropie.org.uk/forum/topic/3/read-this-first

BuZz

@josete2k I am not aware of any n64 performance changes - probably the default gpu plugin changed for one that was more compatible, but nothing has got slower that I am aware of.

There was a bug in lr-pcsx-rearmed when the 4.1 image was generated but it's easily fixed by updated that emulator.

josete2k

@Rascas thanks, I tried to update RetroPie script and all cores from sources, reinstalled kodi and it doesn't launch :(

I'm not sure if I can make a log from it... I'll take a look next time I power on my raspberry.

@BuZz I had some issues in lr-pcsx even in 4.0.3 (with EA intros) and some slowdown (in R-Type Delta) those issues aren't in the emulator that comes with the premade img of 4.0.2.

N64 is more compatible in 4.0.2 with glide-HiRes (Mario KART) and in 4.1 I have some glitches in many games (Mario 64).

I'll try with 4.1.5 and updating the emulators.

BuZz

@josete2k the 4.0.3 issue may have been something else - or you may have updated to the buggy version.

Re n64 The glitches are already fixed.

josete2k

@BuZz thanks again... I've tested with a 4.1 image.

I've updated script, cores, mupenplus64, lr-pcsx and kodi.

Reboot...

And EmulationStation don't boot

segmentation fault

:(

BuZz

@josete2k Please provide more information about your system. Also how you updated. and the contents of /opt/retropie/configs/all/emulationstation/es_log.txt

eg the information here - https://retropie.org.uk/forum/topic/3/read-this-first

You should just do "Update all packages" btw - rather than updating individually - it's possible you missed something doing it manually etc.

josete2k

@BuZz I'm flashing the SD and I'll try again in a few minutes.

If doesn't work, can I read the es_log.txt from ssh, I assume.

Thanks.

BuZz

@josete2k or from sftp / windows networking.

josete2k

Ok, as ES doesn't launch I was thinking that sftp maybe doesn't work.

Perfect.
Tanks again.

josete2k

Ok, new tests.

4.1.15 is still buggy (slowdown in R-Type DELTA and fail to launch FIFA98 SPANISH is I don't skip the EA intro). Kodi updated to 17 Krypton without any issue.

So, I wanted to test 4.0.2 again...

I got an SD 4.0.2 image with Kodi 16 100% working, updated ONLY Kodi to 17 Krypton and... same result: no launching. So there is something wrong with the Krypton+4.0.2 combination.

Maybe I'd let it in 4.0.2 and Kodi 16.

BuZz

@josete2k rtype delta has no slowdowns here - I play that game a fair amount. How did you update ?

josete2k

Update RetroPie Script
Reboot
Update all installed packages

BuZz

@josete2k BTW it's enough to just do update all installed packages. Maybe you have some wrong settings - but I cannot advise without more information - you should start a new topic for specific emulator issues providing details about setup / emulator in use and so on .

That is the way to go forward - I cannot help on an older unsupported version.