RetropPie 3.7 - CEC (Kodi) and GBA (freezing)

herb_fargus

@ShootHere please use pastebin or equivalent for posting logs.

https://retropie.org.uk/forum/topic/3/read-this-first

ShootHere

Sir yes sir! I was looking for such an option (a lot of forums have a code option) but couldn't find it.

Fix'd

herb_fargus

@ShootHere for simple code blocks you can use markdown:

http://commonmark.org/help/

Rascas

@ShootHere Try disabling internal RPi 3 BT by adding dtoverlay=pi3-disable-bt in config.txt. Than see if it fixes the problem.

ShootHere

@Rascas I am afraid that is a no go. Both crash still.

Rascas

@ShootHere Please post everything (including the PSU amperes) that you have connected to the Raspberry Pi. I still cannot reproduce any error, it works just fine for me, so it must be a hardware / setup problem of yours. Also post your /var/log/syslog file to pastebin.

ShootHere

Pi Model: RPi3
RetroPie Version Used: 3.7
Built From: SD Image
USB Devices connected: Wired USB Sony PS3 Controller, not set up for BT (BT disabled in config.txt), SanDisk 32GB USB Stick, Kodi resides on the SD Card
Controller used: Sony PS3 Controller
PSU: Official Raspberry Pi Foundation 2.5A

/var/log/syslog exceeds 512kb so I need the pro version of Pastebin.

Can I manually attach the file to this post?

The other seemingly related files are already posted above.

I have disable the BT in config.txt as per your instructions.

Rascas

@ShootHere The hardware that you are using should be no problem.
I think it is not possible to post files here, post the dmesg output to pastebin instead, after Kodi crashes, and the /tmp/runcommand.log file again.
Did you installed anything else besides Kodi ?

ShootHere

Well perhaps one thing springs to mind is I installed both Kodi and Kodi-Extra (wanted to compare). Could that be the problem? Perhaps this will save us a LOT of searching.

Addison

Hey all.

I'm using a Raspberry Pie 2 with a fresh version of 3.7 and Kodi 16.0.

I get these errors as well on screen:

fbi: no process found
Failed to start cec.service: Unit cec.service failed to load: No such file or directory.
Failed to stop cec.service: Unit cec.service not loaded.

I've never had them before but I haven't cared too much about this since I don't know what it means.

Everything works great on my end.

I'm curious though, what is CEC?

Rascas

@Addison The fbi is the program that loads the splashscreen in RetroPie, it has to be closed before Kodi starts otherwise it will have a bug ( you will see the terminal while a video is playing).

CEC is the tecnology that permits you to control Kodi (and other things) with with your TV remote, if your TV supports that.
https://en.wikipedia.org/wiki/HDMI#CEC

The cec service is a PiPplware specific service (does not exist in RetroPie) that permits you to control other programs with your TV remote, like Emulation Station, etc. It also has to be closed before Kodi starts, if not, there can be problems.

Thats only warnings, just ignore that. I will hide that warnings in the next Kodi version.

Addison

@Rascas

Okay.

I guess I'm getting those errors now because I use an iBuffalo controller with Kodi.

So you're the one who manages Kodi?

I think you just became my new, personal hero. ♥

ShootHere

Would disabling CEC somehow remove the error/crash? I use my smartphone to control it, so would that be an option?

Rascas

@Addison No, that warnings have nothing to do with your iBuffalo controller, just forget/ignore it.

Yes, I am the guy who compile the Kodi packages currently on RetroPie.

@ShootHere CEC also has nothing to do with your crash, at least that warning. That CEC service is independent of Kodi, and it does not even exist in RetroPie. And Kodi's CEC works just fine. Your problem is something else.
Yes, controlling Kodi with a smartphone is an option, you can use any method supported by Kodi to control it, you just have to configure it.

Abs

@Rascas

Just to provide an update to the original post. After I started using 3.7 from a fresh install, GBA stopped freezing.

With regards to the CEC, I think something has gone wrong with my TV. So its not related to the Raspberry Pi 3.