OpenELEC Testbuilds for RaspberryPi Part 2 - 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: OpenELEC Testbuilds for RaspberryPi Part 2 (/showthread.php?tid=184866) 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
|
RE: OpenELEC Testbuilds for RaspberryPi Part 2 - RichG - 2014-02-16 Just the TVHeadend issue. I'll repeat the dmesg if the remote fails after a reboot ... (will try now). Re: RE: OpenELEC Testbuilds for RaspberryPi Part 2 - f1vefour - 2014-02-16 (2014-02-16, 22:21)RichG Wrote: Just the TVHeadend issue. Thanks, I'm not at home but I can post the messages when I get there. It happens regularly, and my experience mirrors yours. Sometimes it doesn't work at all and other times it is intermittent. RE: OpenELEC Testbuilds for RaspberryPi Part 2 - RichG - 2014-02-16 OK - just did a cold start and remote wasn't working. dmesg shows: Code: OpenELEC:~ # dmesg | grep lirc Which looks the same as before (when the remote did work). I think this rules out kernel problem (but I have little knowledge on these things). RE: OpenELEC Testbuilds for RaspberryPi Part 2 - bonzinip - 2014-02-16 (2014-02-16, 22:18)RichG Wrote: It's not an OE issue it's the lirc_rpi kernel module, check dmesg when it happens and you should see some debugging messages about lirc_rpi. I believe the lirc_rpi module code needs some messaging to make it more compatible with newer kernel revisions. I'm not using these builds, I'm using Raspbmc, but I also have IR problems and I don't think it's lirc_rpi. I only see problems with the numeric keys (but not just in live TV mode), and it works in an XBMC build from one month ago (same kernel, same firmware), so it's unlikely to be a kernel problem. RE: OpenELEC Testbuilds for RaspberryPi Part 2 - RichG - 2014-02-16 (2014-02-16, 22:42)bonzinip Wrote:(2014-02-16, 22:18)RichG Wrote: It's not an OE issue it's the lirc_rpi kernel module, check dmesg when it happens and you should see some debugging messages about lirc_rpi. I believe the lirc_rpi module code needs some messaging to make it more compatible with newer kernel revisions. Yeah, I checked a week or so ago using current firmware and an old version of OE (I think a December Gotham build) and that worked fine. That is interesting that you have issues in Rasbmc too, although they may not necessarily be related. It does show that something has become a little broken somewhere, most probably with XBMC itself. Re: RE: OpenELEC Testbuilds for RaspberryPi Part 2 - f1vefour - 2014-02-16 (2014-02-16, 22:31)RichG Wrote: OK - just did a cold start and remote wasn't working. It's strange that our issue is identical yet you don't show the debugging. It certainly isn't an XBMC issue, perhaps a lircd problem. RE: OpenELEC Testbuilds for RaspberryPi Part 2 - RichG - 2014-02-16 (2014-02-16, 22:51)f1vefour Wrote: It's strange that our issue is identical yet you don't show the debugging. It certainly isn't an XBMC issue, perhaps a lircd problem. It's all very strange... lircd is part of the kernel / firmware is it not? So using latest kernel with old XBMC you would expect to see that same problem, but this is not the case (at least for me). I am wondering if it might be a timing issue. As in, if XBMC starts before lircd is ready it will fail. Perhaps this is why I see overclocking having an impact? Is there possibly a way to delay the start of XBMC on reboot to give lircd more time? Re: OpenELEC Testbuilds for RaspberryPi Part 2 - f1vefour - 2014-02-16 lircd is a binary, the daemon that translates the key presses to actions (2014-02-16, 22:59)RichG Wrote: I am wondering if it might be a timing issue. As in, if XBMC starts before lircd is ready it will fail. Perhaps this is why I see overclocking having an impact? To test this boot up and if the remote isn't functional kill xbmc and let it restart itself, if the remote then functions it is a timing issue. RE: OpenELEC Testbuilds for RaspberryPi Part 2 - RichG - 2014-02-16 (2014-02-16, 23:00)f1vefour Wrote: lircd is a binary, the daemon that translates the key presses to actions Yes - but does it get updated with the kernel? ie If I keep a recent kernel but go back to older system is lircd recent or older? Re: RE: OpenELEC Testbuilds for RaspberryPi Part 2 - f1vefour - 2014-02-16 (2014-02-16, 23:04)RichG Wrote:(2014-02-16, 23:00)f1vefour Wrote: lircd is a binary, the daemon that translates the key presses to actions It doesn't get updated with the kernel. RE: OpenELEC Testbuilds for RaspberryPi Part 2 - RichG - 2014-02-16 (2014-02-16, 23:00)f1vefour Wrote: To test this boot up and if the remote isn't functional kill xbmc and let it restart itself, if the remote then functions it is a timing issue. Ah yes - good point. This has been just as intermittent for me. Sometime it works, other times not. (2014-02-16, 23:04)f1vefour Wrote:(2014-02-16, 23:04)RichG Wrote:(2014-02-16, 23:00)f1vefour Wrote: lircd is a binary, the daemon that translates the key presses to actions So, as I said, it works with new kernel / lircd and old system / XBMC, but is problematic with newer system / XBMC. Suggests it's not related to any update that has occurred to lircd / kernel. RE: OpenELEC Testbuilds for RaspberryPi Part 2 - tfouto - 2014-02-16 to me, gpio didn't work either with latest gotham nightlies. Only worked after installed this addon: http://openelec.tv/forum/124-raspberry-pi/51887-raspberry-pi-gpio-ir-receiver-with-openelec-compilation-patches-and-snapshot?start=270#97620 Thanks for your hard work... RE: OpenELEC Testbuilds for RaspberryPi Part 2 - RichG - 2014-02-16 (2014-02-16, 23:25)tfouto Wrote: to me, gpio didn't work either with latest gotham nightlies. Only worked after installed this addon: I was using the add-on and it worked well for a while, but at some point it stopped working (and actually made matters worse) so I disabled it. Looking at the python script it appears to do something similar to what I have in my autostart.sh script, but not quite the same: Code: OpenELEC:~ # cat /storage/.config/autostart.sh Code: OpenELEC:~ # cat /storage/.xbmc/addons/script.service.lirc_rpi_launcher/addon.py RE: OpenELEC Testbuilds for RaspberryPi Part 2 - corb06 - 2014-02-17 (2014-02-16, 18:52)popcornmix Wrote:(2014-02-16, 18:37)mcarni Wrote: If in playback video setting I enable "sync video to display" (with any of the sub-options) crackling is still audible, as soon as i disable this option crakling goes away. Thanks! Now the crackleing sound distortion is gone, so unticking Sync Video did the trick. RE: OpenELEC Testbuilds for RaspberryPi Part 2 - bonzinip - 2014-02-17 (2014-02-16, 22:51)f1vefour Wrote: It's strange that our issue is identical yet you don't show the debugging. It certainly isn't an XBMC issue, perhaps a lircd problem. For me the problem was simply that XBMC stopped recognizing KEY_0 to KEY_9 (as opposed to KEY_NUMERIC_0 to KEY_NUMERIC_9). Caused by pull request #4001. Pull request #4000 should fix it. |