Hi everybody
I'm running Kodi on Raspberry Pi and after a normal restart, I started getting a dark screen on TV after the Kodi logo. That's the log I'm getting, I got it vi ssh. I tried restarting several times but it's always the same. I even tried to format the sd card and load an image I got a couple of months ago. Same result.
Any ideas?
@Karellen- Log removed
Thank you
Quote:Starting Kodi (15.2 Git:02e7013)
Running on OpenELEC (official) - Version: 6.0.3
That's a pretty old setup. Since the very short log is not telling me very much, other than maybe an audio engine initialisation problem, I'm gonna go with SD card corruption for the time being.
Also, please use the internal pastebinit command in OpenELEC to upload your log files to an external website such as pastebin.com .
Hello alexandros
We do not allow logs to be pasted in the forum. Please use a Pastebin type site. Also you need to enable debugging. Use the Advanced method. Instructions are in my signature below.
Last line of that log you posted seemed to indicate Audio issues. Might want to check your audio drivers and settings first.
Thank you both for the feedback.
I've enabled (I think) the advanced log for normal debugging.
This is the log I got:
Log
A couple of things, I didn't change anything, it was working fine so how can it be an audio driver thing? Also, if there was an SD corruption, would I be able to restore from the image?
Quote:it was working fine so how can it be an audio driver thing
I don't know much about the RPi, all I see is this...
PHP Code:
02:00:45 25.224104 T:1957688384 NOTICE: Thread ActiveAE start, auto delete: false
02:00:45 25.225044 T:1947202624 NOTICE: Thread AESink start, auto delete: false
02:00:45 25.226044 T:1947202624 INFO: CActiveAESink::OpenSink - initialize sink
02:00:45 25.226395 T:1947202624 DEBUG: CActiveAESink::OpenSink - trying to open device PI:HDMI
02:00:45 25.226807 T:1947202624 DEBUG: DllBcm: Using omx system library
02:00:50 30.226139 T:1957688384 ERROR: ActiveAE::InitSink - failed to init
The last line is repeated as the last line of the log, indicating that is the likely issue.
@
Klojum is the one that can assist.
I restored from an older image and now it's working.
Thanks