Posts by Jester
-
-
I tried your last image LibreELEC-WeTek_Play_2.aarch64-8.0-devel-20170108131246-r25157-g9e4c5ea.img.gz and network device with 1000 Mbits still shows the frozen behaviour ...
That my workaround (tested it now many many hours) isn't a solution for 4k movies, is clear to me. But maybe it is the right step in the right direction to get rid of this bug. Does the workaround works for you with SD and HD material?
Hmm, too bad, as in that build has an updated kernel, but probably still the same eth0 driver (didnt check)...
For me its still ok...
-
-
see my post Play 2: network disconnecting (hardware failure ?) - Page 3 - WeTek Community Forum
and add
ethtool -s eth0 speed 100 autoneg off
to /storage/.config/autostart.shThanks, yeah I read that, its my thread however, creates stutter on high-bit rate 4k files, so no solution.
so far no issues with a build from master I compiled
-
Thanks, I read that (its my thread not a solution, plus an issue for highbit rate 4k files i'm afraid.
Latest build from master seems stable so far...
-
That sounds interesting Jester. Is there anything different about your build that you know of?Would it be possible for you to share your build for more of us to test it?
Still no issue, but still testing, and i've made no changes, just a compile from the current github master, Commits · LibreELEC/LibreELEC.tv · GitHub
I've put up a test build here if people want to try, it works fine on mine, but don't blame me if stuff breaks (it shouldnt, but still)
-
I've been looking at the same thing here: LibreELEC
Although I just play 4k movies stored on my NAS over SMB.
-
just linking: LibreELEC
I'm running my own build at the moment, to see if there are any improvements, runs ok so far....lets see.
-
-
-
seeing the same on NUC5i3RYK
-
If the same thing happens under Android/WeOS then it's a hardware problem and WeTek will replace the unit for you. If it only happens under LibreELEC then we need to do more investigating. I haven't been able to reproduce yet this myself yet, but that might just mean I don't have the right conditions to trigger the issue.Hi Ned,
WeOS uses weplayer (Javis 16.1) not kodi 17 beta 7, so thats a bad comparison, plus I dont want android
to reproduce, I have weOs 2.01 on the play2, I boot a fresh alpha 10 from SD card, add a bunch of movies to the library, switch to Amber skin, display is set to 4k res and play a 4k file using SMB from my NAS, normally the network crashes between 20 and 30 minutes, but sometimes it takes 50 minutes.
The issue is hard to diagnose as there are very limited indications in debug/dmesg/log files for the issue.
If a dev reads this, can somebody build a LE 10 version with kernel debug enabled so we can better diagnose what is going on ? -
-
While testing Alpha 10 on an SD card, I just ran into the same problem, while previously I had no issue, only difference is a bigger movies database and on this reboot the rpcbind failed.
Re-running the test now that rpcbind is running, although I doubt that this is the issue
(to make the network port disconnect I run the play2 at 4k resolution while playing a 4k movie, it runs fine between 25-35 minutes and then the network stops)
-
Looks like the rpcbind issue has just been addressed
rpcbind: needs to wait until /var/run is available · LibreELEC/LibreELEC.tv@72212c0 · GitHub
-
Couple of questions,
why does dmesg report IPv6 when eth0 comes up (ipv6 is off) ?
[ 11.987170@1] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 12.926600@3] libphy: stmmac-0:00 - Link is Up - 1000/Full
[ 12.927649@3] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes readyAlso rpcbind fails to start on each boot: (are we actually using it?)
[ 8.620360@2] systemd[1]: Starting RPC Bind...
[ 8.636782@2] systemd[1]: rpcbind.service: Main process exited, code=exited, status=1/FAILURE
[ 8.637396@2] systemd[1]: Failed to start RPC Bind.
[ 8.637811@2] systemd[1]: rpcbind.service: Unit entered failed state.
[ 8.637829@2] systemd[1]: rpcbind.service: Failed with result 'exit-code'. -
Right,
After being told that doing NAND installs voids the warranty (WTF?) I'm trying to get to the bottom of this issue several people are reporting (mainly on the wetek forums)
(see here Play 2: network disconnecting (hardware failure ?) - WeTek Community Forum)
LibreELEC (Krypton) v7.90.009 ALPHA - Network Crash - WeTek Community ForumIn short, with the latest alpha versions (/8/9/10) when installing it on
NANDNAND and SD and using a wired network connection, the network drops out after x amount of minutes playing a movie/file, with network drop out I mean I can't ping/ssh into the box any longer and whatever i'm playing/streaming via my NAS just freezes and stops after a few seconds.
A quick way to get the network up and running again (apart from rebooting) is using libreelec settings and switching the wired network off and on.Kodi debug log doesn't give much detail other then CVideoPlayerAudio: process - stream stalled, so my suspicion lays with the ethernet driver on the OS side of things.
dmesg and ifconfig just before a network disconnect dont say much, except a few dropped RX packets which is interesting but doesnt cause any issues like this.
Thing to add, I noticed the network port link led (green one) doesn't come up, only the orange traffic led works, and no its not the cable or switch, I have a nuc and old wt play that work fine with the same cable/switch.Any help to further diagnose (and hopefully fix) the issue is welcome
kodi debug log:
18:24:49.314 T:548304584704 NOTICE: special://profile/ is mapped to: special:// - Pastebin.com -
no clue why it doesnt work using a normal install via kodi gui, however:
manual install via ssh works
wget inputstream.rtmp-1.0.3.zip