•   
  • 1
  • 311
  • 312
  • 313(current)
  • 314
  • 315
  • 355
  •   
  Thread Closed
v18 LibreELEC Testbuilds for x86_64 (Kodi 18.0)
Hi,

i use the latest version with emby. I have problems with my bookmark preview. This problem has been around for some time and has nothing to do with the latest version, but maybe someone has a tip to help there? Is this an Emby or a kodi problem?

https://pastebin.com/MVJ94PeD

Image
(2018-11-08, 04:45)jmerrilljr Wrote: Whew!!!!

Can you try a different swtich, maybe a Gig-ethernet capable switch? From your log, and your LE8.2.5 iperf results, you're connecting at 100Mbp/s. I wonder if you still have problems with 4.19 when using a different switch?
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.
@jmerrilljr can you also post your kernel log from #1016 as I need to be sure there are no kernel errors being logged with 4.18.14 before pointing the finger at the errors being logged in 4.19-rc1.

Boot into #1016, then run dmesg | pastebinit. Then boot into #1016x and run dmesg | pastebinit. Post both urls. If you log in soon after booting you may avoid log truncation, otherwise add the log_buf_len=16M parameter.
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.
(2018-11-08, 12:00)Milhouse Wrote:
(2018-11-08, 04:45)jmerrilljr Wrote: Whew!!!!

Can you try a different swtich, maybe a Gig-ethernet capable switch? From your log, and your LE8.2.5 iperf results, you're connecting at 100Mbp/s. I wonder if you still have problems with 4.19 when using a different switch? 
That is a gig-ethernet switch. I guess the first thing is to get a new cable. Any other suggestions?
(2018-11-08, 15:39)jmerrilljr Wrote:
(2018-11-08, 12:00)Milhouse Wrote:
(2018-11-08, 04:45)jmerrilljr Wrote: Whew!!!!

Can you try a different swtich, maybe a Gig-ethernet capable switch? From your log, and your LE8.2.5 iperf results, you're connecting at 100Mbp/s. I wonder if you still have problems with 4.19 when using a different switch? 
That is a gig-ethernet switch. I guess the first thing is to get a new cable. Any other suggestions?

Nope, just a decent CAT5e cable to start with. If you still have problems with a new cable then we'll need the #1016/#1016x kernel logs to take things forward. If the new cable resolves the issue then it might still be worth having the logs - my plan is to ping them to a kernel developer familiar with the r8169, based on the assumption that the 4.19-rc1 kernel introduces some sort of regressive behaviour.
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.
(2018-11-08, 15:39)jmerrilljr Wrote:
(2018-11-08, 12:00)Milhouse Wrote:
(2018-11-08, 04:45)jmerrilljr Wrote: Whew!!!!

Can you try a different swtich, maybe a Gig-ethernet capable switch? From your log, and your LE8.2.5 iperf results, you're connecting at 100Mbp/s. I wonder if you still have problems with 4.19 when using a different switch?    
That is a gig-ethernet switch. I guess the first thing is to get a new cable. Any other suggestions?   
FYI; I'm also having the same issue in the recent builds, on a Asus Chromebox CN60, so the issue isn't isolate to @jmerrilljr or his network switch.  The following keeps repeating:
Code:
[ 67.003045] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
[ 67.003057] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
[ 67.003063] pcieport 0000:00:1c.0: device [8086:9c14] error status/mask=00003000/00002000
[ 67.003068] pcieport 0000:00:1c.0: [12] Timeout

I went back to LibreELEC-Generic.x86_64-9.0-Milhouse-20181001210358-%231001-gbf09c1f.tar and the issue didn't occur, then I tried LibreELEC-Generic.x86_64-9.0-Milhouse-20181022210409-%231022-g86e23ee.tar whcih was also fine. Then I tried LibreELEC-Generic.x86_64-9.0-Milhouse-20181027210356-%231027-g75688f2.tar which did exhibit the issue.
(2018-11-08, 19:03)Milhouse Wrote:
(2018-11-08, 15:39)jmerrilljr Wrote:
(2018-11-08, 12:00)Milhouse Wrote: Can you try a different swtich, maybe a Gig-ethernet capable switch? From your log, and your LE8.2.5 iperf results, you're connecting at 100Mbp/s. I wonder if you still have problems with 4.19 when using a different switch? 
That is a gig-ethernet switch. I guess the first thing is to get a new cable. Any other suggestions?  

Nope, just a decent CAT5e cable to start with. If you still have problems with a new cable then we'll need the #1016/#1016x kernel logs to take things forward. If the new cable resolves the issue then it might still be worth having the logs - my plan is to ping them to a kernel developer familiar with the r8169, based on the assumption that the 4.19-rc1 kernel introduces some sort of regressive behaviour.  
I bypassed the switch and went directly from my computer into libreelec. I ran iperf:

Last login: Thu Nov  8 11:53:24 on ttys000
Johns-iMac-2:~ johnmerrill$ ssh [email protected]
[email protected]'s password: 
##############################################
#                  LibreELEC                 #
#            https://libreelec.tv            #
##############################################

LibreELEC (official): 8.2.5 (Generic.x86_64)
LibreELEC:~ # iperf -c 10.0.1.62 -t 60 -i10
Connecting to host 10.0.1.62, port 5201
[  4] local 169.254.59.221 port 46516 connected to 10.0.1.62 port 5201
[ ID] Interval           Transfer     Bandwidth       Retr  Cwnd
[  4]   0.00-10.00  sec  1.10 GBytes   941 Mbits/sec    0    257 KBytes       
[  4]  10.00-20.00  sec  1.10 GBytes   941 Mbits/sec    0    257 KBytes       
[  4]  20.00-30.00  sec  1.10 GBytes   941 Mbits/sec    0    257 KBytes       
[  4]  30.00-40.00  sec  1.10 GBytes   941 Mbits/sec    0    257 KBytes       
[  4]  40.00-50.00  sec  1.10 GBytes   941 Mbits/sec    0    257 KBytes       
[  4]  50.00-60.00  sec  1.10 GBytes   941 Mbits/sec    0    257 KBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-60.00  sec  6.57 GBytes   941 Mbits/sec    0             sender
[  4]   0.00-60.00  sec  6.57 GBytes   941 Mbits/sec                  receiver

iperf Done.
LibreELEC:~ # 

I then installed 1016 followed by 1016x and got this:

#10016
http://ix.io/1rla
#10016x
http://ix.io/1rlc

Just to make things interesting I ran #1107 which works fine, now. I'm going to try to figure out the problem with the switch. I have a Time Warner modem that connects via ethernet to an Apple base station. The ethernet runs from the Apple basestation as does the wireless. I will refigure that setup.
(2018-11-08, 23:03)jmerrilljr Wrote: I then installed 1016 followed by 1016x and got this:

#10016
http://ix.io/1rla
#10016x
http://ix.io/1rlc

Just to make things interesting I ran #1107 which works fine, now. I'm going to try to figure out the problem with the switch. I have a Time Warner modem that connects via ethernet to an Apple base station. The ethernet runs from the Apple basestation as does the wireless. I will refigure that setup.

Yes, I'm not seeing any errors in your #1016x kernel log when connecting at 1Gbps, so this may be an issue triggered when connecting at 100Mbps.

@jwegman It's most likely the same issue, you can confirm by testing #1016 and #1016x, but without kernel logs from #1016/#1016x it's not possible to determine what you have in common with @jmerrilljr. For instance, do you also have an r8169, are you connecting at 100Mbps etc.?
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.
New LibreELEC.tv Leia build #1108: Generic
(Supercedes previous build)

SHA256 Checksum: fb1a8572244ba60e42fe63667872cb824c78a4b26c028ae25705145d3cb9015a (Generic)

# uname -a
Linux NUC 4.19.1 #1 SMP Thu Nov 8 21:04:25 GMT 2018 x86_64 GNU/Linux

# lsb_release
LibreELEC (Milhouse): devel-20181108210234-#1108-ge8e2816 [Build #1108]

# Kodi version
(18.0-RC1 Git:c674db0). Platform: Linux x86 64-bit

Based on tip of LibreELEC.tv master (e8e2816, changelog) and tip of XBMC master (c674db0, changelog) with the following modifications: Build Highlights:
  1. samba: update to samba-4.9.2
  2. libcec 4.0.3
  3. [Settings] Implement FindIntInList in CSettingList
Build Details:
  1. LibreELEC.tv:
    • lcdd: build with optimization (PR:3094, 1 commit, 2 files changed)
  2. XBMC:
    • windowing/gbm: fallback to non-alpha visual id (PR:14785, 3 commits, 7 files changed)
    • [Settings] Implement FindIntInList in CSettingList (PR:14815, 1 commit, 3 files changed)
    • [macos] [filemanager] Removable storage fixes/improvements (PR:14818, 2 commits, 6 files changed)
    • [osx/windowing] - fix "blank other displays" (PR:14822, 1 commit, 1 file changed)
    • [macos] CDarwinStorageProvider::Eject: Fix crash due to double release of DADiskRef instance. (PR:14827, 2 commits, 1 file changed)
  3. libcec:
    • changed/fixed: install cec-client by default. correct vs redist (6c76f5f)
    • changed: build with vs 2015 (d8bd948)
    • bump to 4.0.3 (d57d3ac)
  4. pvr.mythtv:
  5. Additional commits/pull requests/changes not yet merged upstream:
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.
(2018-11-09, 03:44)Milhouse Wrote:
(2018-11-08, 23:03)jmerrilljr Wrote: I then installed 1016 followed by 1016x and got this:

#10016
http://ix.io/1rla
#10016x
http://ix.io/1rlc

Just to make things interesting I ran #1107 which works fine, now. I'm going to try to figure out the problem with the switch. I have a Time Warner modem that connects via ethernet to an Apple base station. The ethernet runs from the Apple basestation as does the wireless. I will refigure that setup.

Yes, I'm not seeing any errors in your #1016x kernel log when connecting at 1Gbps, so this may be an issue triggered when connecting at 100Mbps.

@jwegman It's most likely the same issue, you can confirm by testing #1016 and #1016x, but without kernel logs from #1016/#1016x it's not possible to determine what you have in common with @jmerrilljr. For instance, do you also have an r8169, are you connecting at 100Mbps etc.? 
I went back to my original networking setup because Libreelec does not play nice with the non-switched setup. Lots of ip address changes, etc. so I'm back to the slow connection. However, #1107 still plays well. Go figure? I think I need to contact Time Warner/Spectrum and get some info re: their modem.
(2018-11-09, 04:21)jmerrilljr Wrote:
(2018-11-09, 03:44)Milhouse Wrote:
(2018-11-08, 23:03)jmerrilljr Wrote: I then installed 1016 followed by 1016x and got this:

#10016
http://ix.io/1rla
#10016x
http://ix.io/1rlc

Just to make things interesting I ran #1107 which works fine, now. I'm going to try to figure out the problem with the switch. I have a Time Warner modem that connects via ethernet to an Apple base station. The ethernet runs from the Apple basestation as does the wireless. I will refigure that setup.

Yes, I'm not seeing any errors in your #1016x kernel log when connecting at 1Gbps, so this may be an issue triggered when connecting at 100Mbps.

@jwegman It's most likely the same issue, you can confirm by testing #1016 and #1016x, but without kernel logs from #1016/#1016x it's not possible to determine what you have in common with @jmerrilljr. For instance, do you also have an r8169, are you connecting at 100Mbps etc.?  
I went back to my original networking setup because Libreelec does not play nice with the non-switched setup. Lots of ip address changes, etc. so I'm back to the slow connection. However, #1107 still plays well. Go figure? I think I need to contact Time Warner/Spectrum and get some info re: their modem. 
 I will retest #1016 and #1016x tomorrow at 100Mbps  and will get kernel logs for you.
(2018-11-09, 04:37)jmerrilljr Wrote:
(2018-11-09, 04:21)jmerrilljr Wrote:
(2018-11-09, 03:44)Milhouse Wrote: Yes, I'm not seeing any errors in your #1016x kernel log when connecting at 1Gbps, so this may be an issue triggered when connecting at 100Mbps.

@jwegman It's most likely the same issue, you can confirm by testing #1016 and #1016x, but without kernel logs from #1016/#1016x it's not possible to determine what you have in common with @jmerrilljr. For instance, do you also have an r8169, are you connecting at 100Mbps etc.?  
I went back to my original networking setup because Libreelec does not play nice with the non-switched setup. Lots of ip address changes, etc. so I'm back to the slow connection. However, #1107 still plays well. Go figure? I think I need to contact Time Warner/Spectrum and get some info re: their modem.  
 I will retest #1016 and #1016x tomorrow at 100Mbps  and will get kernel logs for you. 
I'm getting a new switch. I will do the above retests before I use it.
(2018-11-08, 19:10)jwegman Wrote:
(2018-11-08, 15:39)jmerrilljr Wrote:
(2018-11-08, 12:00)Milhouse Wrote: Can you try a different swtich, maybe a Gig-ethernet capable switch? From your log, and your LE8.2.5 iperf results, you're connecting at 100Mbp/s. I wonder if you still have problems with 4.19 when using a different switch?    
That is a gig-ethernet switch. I guess the first thing is to get a new cable. Any other suggestions?     
FYI; I'm also having the same issue in the recent builds, on a Asus Chromebox CN60, so the issue isn't isolate to @jmerrilljr or his network switch.  The following keeps repeating: 
I have the same "buffering" problems with a Asus Chromebox M004U with the latest builds.
(2018-11-09, 17:14)supergroover Wrote:
(2018-11-08, 19:10)jwegman Wrote:
(2018-11-08, 15:39)jmerrilljr Wrote: That is a gig-ethernet switch. I guess the first thing is to get a new cable. Any other suggestions?     
FYI; I'm also having the same issue in the recent builds, on a Asus Chromebox CN60, so the issue isn't isolate to @jmerrilljr or his network switch.  The following keeps repeating: 
I have the same "buffering" problems with a Asus Chromebox M004U with the latest builds.

No log no problem. In this case I'll need a kernel log. Compare #1016/#1016x. Logs from both please.
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.
(2018-11-09, 17:16)Milhouse Wrote:
(2018-11-09, 17:14)supergroover Wrote:
(2018-11-08, 19:10)jwegman Wrote: FYI; I'm also having the same issue in the recent builds, on a Asus Chromebox CN60, so the issue isn't isolate to @jmerrilljr or his network switch.  The following keeps repeating: 
I have the same "buffering" problems with a Asus Chromebox M004U with the latest builds.

No log no problem. In this case I'll need a kernel log. Compare #1016/#1016x. Logs from both please.

#1016
http://ix.io/1rpR

#1016x
http://ix.io/1rpV

#1016 with dmesg log_buf_len=16M | pastebinit
http://ix.io/1rq6

#1016x with dmesg log_buf_len=16M | pastebinit
http://ix.io/1rq3
  •   
  • 1
  • 311
  • 312
  • 313(current)
  • 314
  • 315
  • 355
  •   
  Thread Closed
 
Thread Rating:
  • 24 Vote(s) - 4.5 Average



Logout Mark Read Team Forum Stats Members Help
LibreELEC Testbuilds for x86_64 (Kodi 18.0)4.524