v17 LibreELEC Testbuilds for RaspberryPi (Kodi 17.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: Raspberry Pi (https://forum.kodi.tv/forumdisplay.php?fid=166) +---- Thread: v17 LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) (/showthread.php?tid=269814) 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
|
RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - Milhouse - 2016-04-23 (2016-04-23, 18:10)MONSTA Wrote: Strange. Then what is this? I used the transmission addon from there It's a left over from your old OpenELEC installation. If you install OE fresh, install the OE Unofficial repo (written to /storage/.kodi/addons), then upgrade to LE you'll still have the OE Unofficial repo listed as it remains installed in your addons folder. If however you install LE fresh, you won't have any option to install the OE Unofficial repo as it doesn't exist within the LE build. RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - Milhouse - 2016-04-23 (2016-04-23, 19:17)steve1977 Wrote: Thanks. I installed the addon on LE successfully. Then used Putty to run it from command line. I just typed iperf, but got the following error message: Reboot and try again - *ELEC has to apply some magic to command line add-ons in order to make them executable. RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - ultraman - 2016-04-23 (2016-04-23, 17:35)Milhouse Wrote:Paste output only from this command. Not from other logs. RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - polo_joe - 2016-04-23 I got no output from this command in putty so I uploaded the full journalctl log. RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - Kiralina - 2016-04-23 In build #0423 my HifiBerry digi + stopped working and can't be found in the list of audio output devices. It worked fine till now. Some help would be greatly appreciated. Thanks. RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - ratson - 2016-04-23 Upgraded to 423 from 420 and my Hifiberry DAC+ soundcard is absent. Reverting back to 420 brings it back. Any ideas on how to enable it in 423? I can post any specific logs if required. RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - Kiralina - 2016-04-23 (2016-04-23, 21:17)ratson Wrote: Upgraded to 423 from 420 and my Hifiberry DAC+ soundcard is absent. Reverting back to 420 brings it back. Any ideas on how to enable it in 423? I can post any specific logs if required. Same here with the hifiberry digi + . Going back to #0420 brings it back. RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - herrmeier01 - 2016-04-23 VDR isn't starting in #0423, I reverted to #0420 RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - parcel - 2016-04-24 (2016-04-23, 15:55)Pienoet Wrote:(2016-04-23, 14:18)Pienoet Wrote:(2016-04-22, 23:35)Pienoet Wrote: Hi Milhouse thanks for the LibreELEC testbuilds. If you got huge frame drop within 9 minutes, setting "number of buffers used by graphics driver" change to 3 from 2. It's new setting and this problem start with #0415. RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - steve1977 - 2016-04-24 (2016-04-23, 19:56)Milhouse Wrote:(2016-04-23, 19:17)steve1977 Wrote: Thanks. I installed the addon on LE successfully. Then used Putty to run it from command line. I just typed iperf, but got the following error message: Unfortunately, it also didn't work after reboot. Still same error message. I installed iperf on LE and not on OE. I am currenlty using the v.7 beta 2. Maybe that's not compatible with the addon? RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - steve1977 - 2016-04-24 Installed OE now and it is working. What's the syntax to run iperf now? RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - steve1977 - 2016-04-24 While looking to get it to work, I found related thread (http://forum.kodi.tv/showthread.php?tid=213797&page=4). I guess my issue is the same. My CPU-KODI is around 20% although I have no addons installed (besides iperf). It looks like it was solved by switching from SMB to NFS shares. Any idea whether there could be another solution? It used to work with exactly this setup for many months. No clue what's different now. Btw, not sure whether facts or coincidence. LE runs a lot better than OE (both stutter/buffer/lose-audio, but LE plays visibly better). Does LE applies automatically some overclock settings, which could be responsible for that? RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - steve1977 - 2016-04-24 I tried a few more things to isolate the issue: * Changed to another RPi2 with different SD card to avoid faulty device (no improvement) * Changed the ethernet cable (no improvement) * Changed to wireless instead of wired (no improvement) RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - MONSTA - 2016-04-24 (2016-04-23, 19:50)Milhouse Wrote: It's a left over from your old OpenELEC installation.I got it. That's just the renamed OE repo. It was a clean installation. LE image 6.90.004 then your build. No matter. The transmission service doesn't works, it's important for me. Hope somebody will fix it soon. Thanks. Regards, Den. RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - popcornmix - 2016-04-24 (2016-04-24, 02:04)parcel Wrote: If you got huge frame drop within 9 minutes, setting "number of buffers used by graphics driver" change to 3 from 2. Can you confirm if the frame drop problem is with "3" or "2" (or both)? "2" is the default which is what you should have if you have never altered it manually. |