just bought a rpi 2 in need of help
#1
I installed the suggested rasbian os, then installed kodi. When I try to watch a video on kodi it freezes. The play screen always says it is 13 seconds in to the video. if i try to click stop it will freeze the rpi all together and I cant do anything after that. More information I installed genisis using the tvaddon configure.
Reply
#2
Get rid of all the addons from tvaddons, try using a "clean" system. TVAddons installs way too much cr*p. Upload a debug log (wiki).
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Reply
#3
(2015-05-15, 07:37)amazinggreg Wrote: I installed the suggested rasbian os, then installed kodi. When I try to watch a video on kodi it freezes. The play screen always says it is 13 seconds in to the video. if i try to click stop it will freeze the rpi all together and I cant do anything after that. More information I installed genisis using the tvaddon configure.

I have exactly the same behavior, however I did not install any genisis nor tvaddon thingies...

Additionally, I bought the MPG2 and WVC1 license codecs from the raspberry store.

Any clues?
Reply
#4
Debug log.
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Reply
#5
(2015-05-15, 12:29)Milhouse Wrote: Debug log.

Ok, I'll try to generate the log as stated in http://kodi.wiki/view/Log_file/Advanced when I have access to the system
Reply
#6
(2015-05-15, 12:29)Milhouse Wrote: Debug log.

Hi,

I generated the debug log as Milhouse requested. You can find it in

http://pastebin.com/LqGFsY11

I noticed multiple entries regarding some OMXVideo decoding timeouts & rendering not started properly. May this explain the situation?

20:09:58 T:1747784720 ERROR: OMXVideo:Big Grinecode timeout
20:09:58 T:1747784720 INFO: Output - renderer not started

Thank you very much!
Reply
#7
I cant help you with your current problem but I installed Openelec / Kodi on my Raspberry Pi 2 and it worked perfectly and is stable. Instructions http://wiki.openelec.tv/index.php/Raspberry_Pi
I downloaded the [Stable] OpenELEC 5.0.8 (arm) Diskimage loacated here http://releases.openelec.tv/OpenELEC-RPi...0.8.img.gz

The Raspberry Pi is a wonderful toy I suggest you get a extra memory card and install every build you can find for the Raspberry Pi and see what works best for you. I had problems with the rasbian os too my problems started on the first boot screen then someone suggested the Openelec. This was last fall they might have the bugs worked out of the rasbian os by now.

Once you get one working good you like pull the memory card out and make a backup so if you ever have problems you can just restore back to the backup you made I use this tool to back up and restore it http://hddguru.com/software/HDD-Raw-Copy-Tool/

The backups you make inside the program might not be any good if your memory card dies....
Reply
#8
(2015-05-16, 22:55)Lisa_ Wrote: I cant help you with your current problem but I installed Openelec / Kodi on my Raspberry Pi 2 and it worked perfectly and is stable. Instructions http://wiki.openelec.tv/index.php/Raspberry_Pi
I downloaded the [Stable] OpenELEC 5.0.8 (arm) Diskimage loacated here http://releases.openelec.tv/OpenELEC-RPi...0.8.img.gz

The Raspberry Pi is a wonderful toy I suggest you get a extra memory card and install every build you can find for the Raspberry Pi and see what works best for you. I had problems with the rasbian os too my problems started on the first boot screen then someone suggested the Openelec. This was last fall they might have the bugs worked out of the rasbian os by now.

Once you get one working good you like pull the memory card out and make a backup so if you ever have problems you can just restore back to the backup you made I use this tool to back up and restore it http://hddguru.com/software/HDD-Raw-Copy-Tool/

The backups you make inside the program might not be any good if your memory card dies....

Thank you for the pointers Lisa. Since others seem to have the same issue, I think it's great to (or at least, try to) fix the issue and help Kodi developers locating and reporting these problems in order to get a better releases.
Reply
#9
Dear all,

it looks like the following Forum entry seems to have found and solved the issue I pointed out regarding the OMXVideo issues.

I'll give it a try and if I'm able to fix it, I'll change the status of this thread to solved.

Regards.

ADDITION: Looks like the Raspberry PI FAQ already points out the same solution http://kodi.wiki/view/Raspberry_Pi_FAQ#Memory_Usage
Reply
#10
(2015-05-15, 12:15)redcrash Wrote:
(2015-05-15, 07:37)amazinggreg Wrote: I installed the suggested rasbian os, then installed kodi. When I try to watch a video on kodi it freezes. The play screen always says it is 13 seconds in to the video. if i try to click stop it will freeze the rpi all together and I cant do anything after that. More information I installed genisis using the tvaddon configure.

I have exactly the same behavior, however I did not install any genisis nor tvaddon thingies...

Additionally, I bought the MPG2 and WVC1 license codecs from the raspberry store.

Any clues?


When you added your files did you allow any of the scraping things? I make sure it says NONE and then check the box that says "Exclude selected folder from scans" biggest mistake I ever made was allowing it to "scrape" brought my Raspberry Pi to its knees acted like a virus and took over all the resources I could not format the card and start over fast enough.

Maybe your timeouts are because something else is hogging all your resources?
Reply
#11
Yes an rpi will take a while to scrape, just let it do it. Kodi isn't that great without the library.
If I have helped you or increased your knowledge, click the 'thumbs up' button to give thanks :) (People with less than 20 posts won't see the "thumbs up" button.)
Reply
#12
(2015-05-16, 23:04)redcrash Wrote: Dear all,

it looks like the following Forum entry seems to have found and solved the issue I pointed out regarding the OMXVideo issues.

I'll give it a try and if I'm able to fix it, I'll change the status of this thread to solved.

Regards.

ADDITION: Looks like the Raspberry PI FAQ already points out the same solution http://kodi.wiki/view/Raspberry_Pi_FAQ#Memory_Usage


Hello!

I just wanted to note that increasing the gpu_mem to 128 solved the issue!! Hope it also helps amazinggreg.

Thank you to everyone for helping on this!
Reply
#13
(2015-05-17, 14:21)redcrash Wrote: I just wanted to note that increasing the gpu_mem to 128 solved the issue!! Hope it also helps amazinggreg.

Thank you to everyone for helping on this!

You've got a Pi2 so should set gpu_mem=256 (you've got plenty of RAM on the Pi2, and the GPU needs it more than the ARM!)

I've updated the Wiki entry to add some clarification regarding Pi2 memory usage.
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Reply
#14
(2015-05-17, 00:15)nickr Wrote: Yes an rpi will take a while to scrape, just let it do it. Kodi isn't that great without the library.

Yeah your right you should see all the crap it scraped up for the more than 180 home movies haha I wish some place in the instructions it WARNED me what it could to and was going to do if allowed so we didnt waste so much of time not to mention all the other movies it attempted to rename for us.

Kodi works PERFECT with no library we simple navigate to the media we want to view no distractions with the fanart that is mostly wrong most the time, thank GOD someone had enough insite to allow scraping to be avoided, in about another week all our media players will be disconnected from the web for good anyways, life will be even better no need to rename files we already know exactly what they are all our time will be spent enjoying our media just like the old days with the WDTV that has never been connected to the web..

We love all the options what we don't like is all the bias towards the options and no mention of all the hair pulling things that can happen at the flip of a switch so to speak, our hats off to the XBMC and KODI team for all the GREAT WORK they have done to take media players to the next level! I am sure some day someone will write a guide detailing what not to do.

Thanks everybody.
Reply
#15
(2015-05-17, 14:21)redcrash Wrote:
(2015-05-16, 23:04)redcrash Wrote: Dear all,

it looks like the following Forum entry seems to have found and solved the issue I pointed out regarding the OMXVideo issues.

I'll give it a try and if I'm able to fix it, I'll change the status of this thread to solved.

Regards.

ADDITION: Looks like the Raspberry PI FAQ already points out the same solution http://kodi.wiki/view/Raspberry_Pi_FAQ#Memory_Usage


Hello!

I just wanted to note that increasing the gpu_mem to 128 solved the issue!! Hope it also helps amazinggreg.

Thank you to everyone for helping on this!

Thats great to hear, what instructions did you use to make the memory adjustments, I looked at the link to the wiki but did not see any instructions on how to adjust the memory just suggestions to change the settings.


Pay attention during boot up to your screen look for a colored square to appear on the screen briefly I just wonder if the power load on boot up increases do to the memory changes.

Thanks and good luck.
Reply

Logout Mark Read Team Forum Stats Members Help
just bought a rpi 2 in need of help0