Posts by jmooremcc

Quote from jmooremcc

I've just installed LE 9.0 Kodi Leah V18 on my Raspberry Pi 2. I'm using NextPVR for my Live TV functionality. I can playback recordings OK, however, I've encountered numerous problems watching live TV including stuttering video and large audio offsets. The screen also goes black when I click any buttons on my remote.

Has anyone else experienced similar problems? If so, how did you resolve them?

Any advice will be greatly appreciated.

Kodi.Log

Display More

I re-imaged my sdcard and the stuttering during playback has gone away. However, while watching live TV, anytime I click a button on my remote the screen goes black and the audio stops playing. The screen also goes black when I remotely change the channel using JSONPRC.

Anyone have any idea why this is happening and what can be done to fix it?

I don't have this problem with LE v8.25.

LE9 Kodi.Log

I've just installed LE 9.0 Kodi Leah V18 on my Raspberry Pi 2. I'm using NextPVR for my Live TV functionality. I can playback recordings OK, however, I've encountered numerous problems watching live TV including stuttering video and large audio offsets. The screen also goes black when I click any buttons on my remote.

Has anyone else experienced similar problems? If so, how did you resolve them?

Any advice will be greatly appreciated.

Kodi.Log

I'm attempting to build Version 8.2.5 on a Ubuntu 18.04.1 LTS (GNU/Linux 4.15.0-43-generic i686) system.

I've followed the instructions to compile the code found on this website but I get the following errors:

Quote

configure: WARNING: unrecognized options: --disable-static, --enable-shared

/home/john/LibreELEC.tv/build.LibreELEC-RPi2.arm-8.2.5/make-4.2.1/configure: lin

e 9807: /home/john/LibreELEC.tv/build.LibreELEC-RPi2.arm-8.2.5/toolchain/bin/pkg

-config: No such file or directory

configure: WARNING: unrecognized options: --disable-static, --enable-shared

glob/libglob.a(glob.o): In function `glob_in_dir':

glob.c:(.text+0x2f6): undefined reference to `__alloca'

glob.c:(.text+0x477): undefined reference to `__alloca'

glob.c:(.text+0x636): undefined reference to `__alloca'

glob.c:(.text+0x69b): undefined reference to `__alloca'

glob/libglob.a(glob.o): In function `glob64':

glob.c:(.text+0xa21): undefined reference to `__alloca'

glob/libglob.a(glob.o):glob.c:(.text+0x113e): more undefined references to `__al

loca' follow

collect2: error: ld returned 1 exit status

make[3]: *** [make] Error 1

make[2]: *** [all-recursive] Error 1

make[1]: *** [all] Error 2

make: *** [image] Error 2

Display More

From the research I've done, it appears that the problem may be related to the following comment I found in the glob.c file:

Quote

/* Comment out all this code if we are using the GNU C Library, and are not

actually compiling the library itself. This code is part of the GNU C

Library, but also included in many other GNU distributions. Compiling

and linking in this code is a waste when using the GNU C library

(especially if it is a shared library). Rather than having every GNU

program understand `configure --with-gnu-libc' and omit the object files,

it is simpler to just do this in the source for each such file. */

Display More

If I should be using the glob function from the GNU C Library instead of compiling glob.c, how would I make that happen?

Or if I have to compile the glob.c file, how would I reconcile the reference to the __alloca function?

The command I used to compile was:

Quote

PROJECT=RPi2 ARCH=arm CUSTOM_VERSION="JM_8.2.5" make image

I've also attached my logs for your inspection:

rpi.log

rpiError.log

Thank you in advance for your assistance.

I too have a similar problem compiling 8.2.5. I'm getting the following errors:

Quote

configure: WARNING: unrecognized options: --disable-static, --enable-shared

/home/john/LibreELEC.tv/build.LibreELEC-RPi2.arm-8.2.5/make-4.2.1/configure: lin

e 9807: /home/john/LibreELEC.tv/build.LibreELEC-RPi2.arm-8.2.5/toolchain/bin/pkg

-config: No such file or directory

configure: WARNING: unrecognized options: --disable-static, --enable-shared

glob/libglob.a(glob.o): In function `glob_in_dir':

glob.c:(.text+0x2f6): undefined reference to `__alloca'

glob.c:(.text+0x477): undefined reference to `__alloca'

glob.c:(.text+0x636): undefined reference to `__alloca'

glob.c:(.text+0x69b): undefined reference to `__alloca'

glob/libglob.a(glob.o): In function `glob64':

glob.c:(.text+0xa21): undefined reference to `__alloca'

glob/libglob.a(glob.o):glob.c:(.text+0x113e): more undefined references to `__al

loca' follow

collect2: error: ld returned 1 exit status

make[3]: *** [make] Error 1

make[2]: *** [all-recursive] Error 1

make[1]: *** [all] Error 2

make: *** [image] Error 2

Display More

If anyone has any suggestions on how to resolve these issues, I would appreciate it.

I'd like to get the latest version of the NextPVR addon (v.2.4.7) for a RPi2.

Anyone know how I can get this version, even if it means compiling it myself.

Thank you in advance

I've loaded this release on my RPi2. Whenever I try to restore my backup from 8.2.5, it appears to go OK but when it reboots, the restore has not taken place and the initial setup screen appears.

Also when it does run, the audio is out of sync with the video.

Anyone know what's happening and can anyone suggest any work arounds for this problem?

I have two RPi2s and both exhibit the same problem when watching live TV. I'm using the NextPVR addon to connect to a backend NPVR server running on a Windows 10 desktop computer.

In the first case, after watching live TV for up to 6 hours, the stream will suddenly freeze.

Attached is the Kodi Log for this problem: kodiLog_20181218.zip

Please note the following in the log file:

In the 2nd case, I've been using JSON RPC to remotely change the Live TV channels and periodically after a channel change, Kodi will freeze.

Attached is the Kodi Log for this problem: kodiLog.zip

Please note the following in the log file:

In both cases, the RPi2 is still running and I'm able to log in to it using SSH.

I've not been able to figure out why this is happening and would appreciate any help anyone can offer.

Thank you in advance.

Quote from Iridium

Also output from.

dmesg|paste

journalctl|paste

done

Display More

The PSU is a CanaKit 5V 2.5A Raspberry Pi 3 B+ Power Supply / Adapter (UL Listed)

I've attached the kodi log that was generated after the reboot.

I have 4 crash logs that were generated on 11/9/18. I will attach 2 more for your review.

If there are any settings that you could recommend that would improve the information in the log files, please let me know.

My RPi crashes randomly and reboots. I saved a crash log that recently occurred while the RPi was essentially idle.

The log indicated the following:

"

Using host libthread_db library "/usr/lib/libthread_db.so.1".

Core was generated by `/usr/lib/kodi/kodi.bin --standalone -fs --lircdev /run/lirc/lircd'.

Program terminated with signal SIGSEGV, Segmentation fault.

#0 0x76f31b64 in memcmp () from /usr/lib/libarmmem.so

"

Is this a problem with /usr/lib/libarmmem.so? If so, what can be done to fix it?

I'm attaching the entire crash log for reference.

Quote from chewitt

The LE staff have a generally low opinion on Realtek wireless devices. The hardware is probably reasonable, and performance on Windows is probably great because that's where they invest all the Engineering time. Their Linux drivers are an afterthought, and we're fed up with they way they breed chipsets and new drivers that rehash the same greatest-hits compilation of hacks over and over.

Find something that uses the ath9k driver, which is in-kernel and much higher quality code.

I've been unable to find a USB WiFI dongle that utilizes the ath9k driver and works with the 802.11ac standard. Everything I've found so far only meets the 802.11n standard and is not compatible with the 802.11ac standard.

For those of us who are using a Raspberry Pi and want to use the 5G band because there's less interference with other WiFI devices, it appears that Realtec devices are our only choice.

So chewitt , are you saying that the Edimax EW-7811UTC wifi dongle isn't any good?

Amazon users give it 3.7 stars out of 5 and New Egg users gives it 4 eggs out of 5.

So what do you recommend that will provide superior performance and can co-exist in an environment that has multiple channels with the same SSID?

I thought I would share my experience with everyone about using an ac600 wifi dongle with a raspberry Pi. I have multiple Raspberry Pi systems ranging from the PI1 to a PI2 running version 8.2.5. I have to confess that I got very frustrated dealing with the problems I was experiencing. I even bought a new router, a tri-band EA9300 by Linksys, capable of handling 4k streaming data and my RPi2 was still having great difficulty connecting.

Whenever I would try to connect to one of 5G channels, the PI2 would refuse to connect. So in frustration I decided to try the 2.4G channel. I put in the passphrase and everything was working just fine. But 10 minutes later, Kodi indicated that the connection had dropped and when I tried to re-establish the connection, the passphrase field was blank and required me to re-enter the passphrase once again. I tried over and over again to enter the passphrase only to have to repeat the process 10 minutes later.

As it turns out, the drivers used by LE on the RPi aren't sophisticated enough to deal with a network with identical SSIDs and I have more than one router with the same SSID. I changed the SSID of the 2.4G channel on the new router and was then able to connect successfully without the connection dropping.

With that success, I decided to try the 5G channel again. Unfortunately, the same problems surfaced again. I then realized that the EA9300, a tri-band router, gave both of its 5G channels the same SSID. So once again, the drivers in LE had problems connecting. I turned off the fancy "5GHz steering mode" on the router which allowed me to name each of the 5G channels individually. I was then able to connect to any of the available 5G channels with no problem.

So the moral of the story is that if you use multiple SSIDs with Kodi boxes powered by a Raspberry Pi, make sure that the SSIDs are uniquely named so that you can avoid the conflicts I ran into.

Quote from chewitt

Nope. Our default config is wide open. It will change in LE9 so iptables restricts inbound connections to RFC1918 networks, but that still wouldn't explain why you cannot connect from a local network.

Hi chewitt,

I finally figured out what was going on. The Python interpreter in LE does not recognize the hostname 'localhost'. In my test script, changing host='localhost' to host='' fixes the problem.

My Windows version of Python 2.7 does not suffer from this problem. Yes, I can successfully ping 'localhost' from the command line but binding a socket with 'localhost' causes the connection refused error problem I reported.

Hi chewitt I've tried to connect from a Windows 10 PC as well as from othe RPis on the same network and got the same result.

Is there some other mechanism installed that is only allowing Kodi related ports to be open?

So I did some research and discovered the iptables command that is suppose to control the firewall.

iptables -S shows no rules so I don't know why the RPi is rejecting the tcp connection.

Anyway, I issued the following command to add a rule:

iptables -A INPUT -p tcp -m tcp --dport 51000 -j ACCEPT

It appears that the rule is being ignored because it did not allow me to connect to the server code running on the RPi from my Windows PC that was running the client.

I ran the same test on my Ubuntu PC and it worked with no problem.

Any suggestions for resolving this issue will be greatly appreciated.

I'm developing a Python Kodi addon that utilizes a client/server model. The addon works under Windows but when I install it on my Raspberry Pi (LE 8.2.1), I get the following error:"tcp connection refused Error 10061". I ran netstat and could see that my socket was Listening on the port I assigned.

To eliminate anything with Kodi, I wrote a set of simple client/server scripts in Python clientServerTest.zip. I got the same error when I ran the server code from the command line on the RPi and tried to connect to it using the client script on an external computer. Again, netstat showed the port I used being listened to.

My question is how can I enable the tcp port I have chosen so that I can access my server? Any help or suggestions will be greatly appreciated.

Problem Solved:

I compared my 2 RPi systems and found that the problem child had an LE setting the good system didn't have: a timeserver setting. I've removed the timeserver setting and have rebooted the problem child 6 times and each time, the EPG time was correct.

Background:

RPi systems do not have a clock so when the internet is down, an RPi shows the time it was the LE software was compiled. My solution to this problem was to turn my back end NextPVR server, a Windows 10 desktop PC, into a time server for the RPi since it has a clock. The solution appeared to work well until Daylight Savings Time ended. I don't know if the problem would exist if I had specified an external time server. What I do know is that specifying the windows PC as a time server is problematic.