v18 LibreELEC Testbuilds for x86_64 (Kodi 18.0) - Printable Version +- Kodi Community Forum (https://forum.kodi.tv) +-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33) +--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111) +---- Forum: Linux (https://forum.kodi.tv/forumdisplay.php?fid=52) +---- Thread: v18 LibreELEC Testbuilds for x86_64 (Kodi 18.0) (/showthread.php?tid=298462) Pages:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
|
RE: LibreELEC Testbuilds for x86_64 (Kodi 18.0) - riccardo - 2018-11-18 Hi, please how to disable a message appearing when LE starts saying "Remote communication server failed to start" ? And I don't know if it's my config or a bug but audio passthrough has still some issues on NUC 6CAYH. The Dolby+ audio plays only if I play the video containng this audio as a first video (after fresh boot). If I first play a video with other audio format in it and then try to play other one with Dolby+, the audio won't play. I have to reboot LE to get Dolby+ working again. Edit: If this happens, the LE gets messed up and all the non-HD audio formats won't play either. Only DTS-HD/MA and TrueHD stay functional. RE: LibreELEC Testbuilds for x86_64 (Kodi 18.0) - Milhouse - 2018-11-18 (2018-11-18, 14:45)whocarez1 Wrote: Just tell me what else might be needed, or what else to test, and I will do it later today. You have the same kernel errors as the other users have reported - I would suggest posting information on the kernel bug https://bugzilla.kernel.org/show_bug.cgi?id=201517 RE: LibreELEC Testbuilds for x86_64 (Kodi 18.0) - Milhouse - 2018-11-18 (2018-11-18, 18:22)riccardo Wrote: Hi, please how to disable a message appearing when LE starts saying "Remote communication server failed to start" ? No log, no problem. RE: LibreELEC Testbuilds for x86_64 (Kodi 18.0) - Milhouse - 2018-11-18 New LibreELEC.tv Leia build #1118: Generic (Supercedes previous build) SHA256 Checksum: 6001aa4dde8c2d3627dba6a3381f4c8bb9509e91a49a5c22c0e66c47429c7a52 (Generic)
Based on tip of LibreELEC.tv master (d35701a, changelog) and tip of XBMC master (4b7d471, changelog) with the following modifications:
RE: LibreELEC Testbuilds for x86_64 (Kodi 18.0) - whocarez1 - 2018-11-19 I suppose we can assume that the PCIe error is the cause, and not something else. It seems to be related to the PCI bridge and the errors appear frequently when the network is in use. And yes, indeed the device connected to 00:1c.0 seems to be the ethernet controller. I guess trying a couple of kernel options might be a workaround too. But it is probably better to follow it up with a bug report. RE: LibreELEC Testbuilds for x86_64 (Kodi 18.0) - riccardo - 2018-11-19 (2018-11-18, 18:22)riccardo Wrote: Hi, please how to disable a message appearing when LE starts saying "Remote communication server failed to start" ?Here is the log: http://ix.io/1swC The Dolby+ audio issue appears at 22:14:25.803 T:140377956149376 Previous file with DTSHDMA7.1 played fine The "Remote comm. server failed to start" message issue happend as well. I just don't recognize it in the log. RE: LibreELEC Testbuilds for x86_64 (Kodi 18.0) - whysoserious - 2018-11-19 (2018-11-18, 18:22)riccardo Wrote: Hi, please how to disable a message appearing when LE starts saying "Remote communication server failed to start" ?Somewhere in your network settings (I forget where exactly, I think it's in the LibreELEC program add-on) is the option to tell LibreELEC to wait for a network connection before starting up. Set it for 10 sec. just to be sure. RE: LibreELEC Testbuilds for x86_64 (Kodi 18.0) - Milhouse - 2018-11-19 Weekly Linux 4.20-rc3 build #1118x: Generic Known issues:
RE: LibreELEC Testbuilds for x86_64 (Kodi 18.0) - Milhouse - 2018-11-19 (2018-11-19, 00:16)whocarez1 Wrote: I suppose we can assume that the PCIe error is the cause, and not something else. It seems to be related to the PCI bridge and the errors appear frequently when the network is in use. And yes, indeed the device connected to 00:1c.0 seems to be the ethernet controller. I guess trying a couple of kernel options might be a workaround too. But it is probably better to follow it up with a bug report. Please add your kernel logs to the existing bug. It may be worth pointing out on the bug that this problem started with 4.19-rc1. RE: LibreELEC Testbuilds for x86_64 (Kodi 18.0) - Milhouse - 2018-11-19 (2018-11-19, 00:33)riccardo Wrote: Here is the log: Try adding the "wait for network" setting - your WiFi network IP address is being assigned as Kodi is starting which will cause problems for Kodi when it tries to access your network. As for the audio issues, a debug log (wiki) provides more useful information and is what we mean by a "log" around here... RE: LibreELEC Testbuilds for x86_64 (Kodi 18.0) - whocarez1 - 2018-11-19 Yes, I will do that. However, there are at least two of those "AER: error corrected" bugs reported recently for kernel 4.19. I am not sure if each of those bugs are triggered by the same thing. This one is about the same PCIe port: https://bugzilla.kernel.org/show_bug.cgi?id=199695 As a small workaround I added pci=nomsi to the kernel command line. It "helps" for the time being, at least on my Chromebox. Surely just a workaround, since it only suppresses a possible driver problem.
If you do not boot through EFI, possibly just edit /flash/syslinux.cfg RE: LibreELEC Testbuilds for x86_64 (Kodi 18.0) - Milhouse - 2018-11-19 (2018-11-19, 00:54)whocarez1 Wrote: Yes, I will do that. However, there are at least two of those "AER: error corrected" bugs reported recently for kernel 4.19. I am not sure if each of those bugs are triggered by the same thing. This one is about the same PCIe port: https://bugzilla.kernel.org/show_bug.cgi?id=199695 As a small workaround I added pci=nomsi to the kernel command line. It "helps" for the time being, at least on my Chromebox. Surely just a workaround, since it only suppresses a possible driver problem. Yes, I've found bugs which mention type=Physical Layer (same as the bug you linked above), and then there are bugs with type=Data Link Layer , which matches the errors reported in this thread and also the bug I linked previously. I'm not sure if the type actually matters to be honest - they could be the same bug (or same root), or completely different bugs.Also, I'm not sure what the commonality is of this bug - it doesn't affect everyone, but seems to affect Chromebox, which is based on r8169, although I don't see this issue with my Revo 3700 which is also r8169 based. However the errors are being kicked out by the PCI Bridge, and the details in the bug I linked seem to have come from an AMD Threadripper system. All we know is that this seems to have started with 4.19-rc1. It could be a configuration issue, but PCIEAER (PCI Express Advanced Error Reporting) related configs are the same in both 4.18.14 and 4.19-rc1. I don't want to be the middle man in this bug as I can't reproduce it so can't add much value, in which case posting your logs direct to the bug is the best option right now - if there are any fixes proposed I'll be more than happy to help you all test them (I've cc'd myself on the bug). (2018-11-19, 00:54)whocarez1 Wrote:If you are booting with EFI you should only need to edit /flash/syslinux.cfg - we have done away with /flash/EFI/BOOT/syslinux.cfg (several months ago).
RE: LibreELEC Testbuilds for x86_64 (Kodi 18.0) - Matt Devo - 2018-11-19 (2018-11-19, 00:54)whocarez1 Wrote: Yes, I will do that. However, there are at least two of those "AER: error corrected" bugs reported recently for kernel 4.19. I am not sure if each of those bugs are triggered by the same thing. This one is about the same PCIe port: https://bugzilla.kernel.org/show_bug.cgi?id=199695 As a small workaround I added pci=nomsi to the kernel command line. It "helps" for the time being, at least on my Chromebox. Surely just a workaround, since it only suppresses a possible driver problem.as a corollary, the issue isn't AER or the lack of support thereof; disabling AER and rebuilding the firmware will eliminate the error messages, but not fix the performance issue. Disabling MSI via kernel parameter fixes the performance issue, so that would seem to be where the issue lies. I'll dig a little further RE: LibreELEC Testbuilds for x86_64 (Kodi 18.0) - Matt Devo - 2018-11-19 (2018-11-19, 02:14)Milhouse Wrote: Also, I'm not sure what the commonality is of this bug - it doesn't affect everyone, but seems to affect Chromebox, which is based on r8169, although I don't see this issue with my Revo 3700 which is also r8169 based. However the errors are being kicked out by the PCI Bridge, and the details in the bug I linked seem to have come from an AMD Threadripper system. I have 3 Chromeboxes here with the r8169 - a Haswell, a Broadwell, and a Kabylake. The Haswell box is completely crippled by this bug, xfer rates are <250KB/s. The Broadwell box is affected but less so - I get ~3MB/s with that. I haven't tested the Kabylake box to get precise figures, but it seems minimally affected, if at all, by kernel 4.19.x based on daily use (and the kernel log shows no AER errors). The HSW/BDW boxes get > 50MB/s transfer with either a 4.18.x kernel or pci=nomsi used with 4.19-rc1+ edit: the KBL box sees a drop from ~50MB/s (likely limited by write speed to USB boot media) to ~35MB/s on 4.19.x RE: LibreELEC Testbuilds for x86_64 (Kodi 18.0) - whocarez1 - 2018-11-20 (2018-11-19, 02:14)Milhouse Wrote: If you do not boot through EFI, possibly just edit /flash/syslinux.cfg Interesting. On my system editing /flash/syslinux.cfg had no effect But then again, I have not reinstalled Libreelec completely for many months, I just use the update function for the time being. |