OpenELEC Testbuilds for RaspberryPi (Kodi 16.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: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) (/showthread.php?tid=231092) 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
|
RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Milhouse - 2015-10-09 @bagofcrap24 - some more kernels if you don't mind testing: Quote:c1a6ce0483bbdd9cf3489e - +149 commits Try c1a6ce0483bbdd9cf3489e if BAD then d339d03860f21b3f27a674 if GOOD then d36f8434da8c333aa3837c RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - bagofcrap24 - 2015-10-09 (2015-10-09, 05:39)Milhouse Wrote: @bagofcrap24 - some more kernels if you don't mind testing: c1a6ce0483bbdd9cf3489e = Good d36f8434da8c333aa3837c = Good RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - doveman2 - 2015-10-09 Is there anything in this log that shows why Putty/SSH isn't working on my brother's RPi v2? I checked in the OE settings addon that SSH is enabled and deleted the files in .cache/ssh to let it recreate them. I can connect with WinSCP, which I think uses the same SSH key but when I try with Putty it can't connect and I just get an empty black window until I cancel it. http://pastebin.com/479iWxbr RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - jmerrilljr - 2015-10-09 Using the Harmony Smart Hub/Remote. The Menu key does not open the context menu. (This works on all stable versions of OpenElec.) The workaround is to open the keyboard and use the c key. The keyboard is only accessible on the mobile version of the remote, not the remote hardware. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Milhouse - 2015-10-09 (2015-10-09, 14:18)doveman2 Wrote: Is there anything in this log that shows why Putty/SSH isn't working on my brother's RPi v2? I checked in the OE settings addon that SSH is enabled and deleted the files in .cache/ssh to let it recreate them. I can connect with WinSCP, which I think uses the same SSH key but when I try with Putty it can't connect and I just get an empty black window until I cancel it. No. You'll need to enable PuTTY logging to view the communication handshake between PuTTY and OpenELEC to get an idea of why it's not working. RSA keys were recently deprecated by OpenSSH, so you may need to switch to DSA or ECDSA keys (however the latter are only supported in PuTTY when using the "development" build). RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Milhouse - 2015-10-09 (2015-10-09, 16:50)jmerrilljr Wrote: Using the Harmony Smart Hub/Remote. The Menu key does not open the context menu. (This works on all stable versions of OpenElec.) The workaround is to open the keyboard and use the c key. The keyboard is only accessible on the mobile version of the remote, not the remote hardware. Does it work with 5.95.5? If not you may need to report it upstream. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - jmerrilljr - 2015-10-09 It works on the Chromebox version of 5.95.5. I have not tried the pi version. I will run that and see what happens. Thanks. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - doveman2 - 2015-10-09 (2015-10-09, 17:35)Milhouse Wrote: No. You'll need to enable PuTTY logging to view the communication handshake between PuTTY and OpenELEC to get an idea of why it's not working. RSA keys were recently deprecated by OpenSSH, so you may need to switch to DSA or ECDSA keys (however the latter are only supported in PuTTY when using the "development" build). Thanks, I never even noticed the PuTTY logging option! I'll see what the log reveals. I haven't had to change anything on my PC in PuTTY for it to work with my RPi v2 and the latest builds, whilst my brother is still on #825 and I think I checked PuTTY was working when I first sent the RPi v2 to him, to replace his RPI B+. He told me it froze recently and he had to cut the power and after he rebooted all his settings had reset (this seemed to happen to him with his B+ as well but I can't recall this happening with mine on the occasions I've had to cut the power), so it's possible something got screwed up there I guess. He said he tried using the RPi reboot shortcut I created on his desktop, which is just a batch file that uses PuTTY, before cutting the power and that didn't work but I guess that's normal if the RPi/OE had completely crashed, rather than just Kodi. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - popcornmix - 2015-10-09 (2015-10-09, 11:21)bagofcrap24 Wrote: c1a6ce0483bbdd9cf3489e = Good Thanks. From Milhouse: Quote:b21ee342590aa41e21aa0196bff5af592cc349d0 - +157 commits So, can you test b21ee3425 first. If Good then e55ffaf45 If Bad then 0c1122ae6 This should be the final test and narrow it down to a single commit. I have my suspicions which commit it will be, but would be good to run the test to be sure. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - bagofcrap24 - 2015-10-09 (2015-10-09, 18:47)popcornmix Wrote:(2015-10-09, 11:21)bagofcrap24 Wrote: c1a6ce0483bbdd9cf3489e = Good b21ee3425 = Good (Choosing Reboot on main menu doesn't actually restart, all connections stop but reboot doesnt happen) e55ffaf45 = Bad I hope these are the results you was expecting RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - popcornmix - 2015-10-09 (2015-10-09, 19:34)bagofcrap24 Wrote: b21ee3425 = Good (Choosing Reboot on main menu doesn't actually restart, all connections stop but reboot doesnt happen) Not quite. Was hoping for b21ee3425=Bad. Could you switch back to that kernel just to be sure. I found this bug fix which has gone into mainline kernel tree, but not the stable tree we use. And that fixes a bug introduced in 0c1122ae6. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - bagofcrap24 - 2015-10-09 (2015-10-09, 20:00)popcornmix Wrote:(2015-10-09, 19:34)bagofcrap24 Wrote: b21ee3425 = Good (Choosing Reboot on main menu doesn't actually restart, all connections stop but reboot doesnt happen) My apologies, b21ee3425 is in fact Bad. Must have not been waiting long enough for the lockup to occur when testing. Definetly got the exact same lockup with b21ee3425. Solid green activity light, no response to SSH Just trying 0c1122ae6 now 0c1122ae6 = Bad Last Good Kernel = d36f8434d RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - popcornmix - 2015-10-09 (2015-10-09, 20:24)bagofcrap24 Wrote: My apologies, b21ee3425 is in fact Bad. Cool. That is what I hoped for. Tonight's build will be back to 4.1.10 with a fix for the "deadlock" commit. Hopefully that will be good too. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - bagofcrap24 - 2015-10-09 Thanks to the both of you for the time looking into this one. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Milhouse - 2015-10-10 New OpenELEC Jarvis build #1009: RPi / RPi2 (Supercedes previous build) Code: # uname -a Based on tip of OpenELEC master (e2b6fefc, changelog) and tip of XBMC master (783db620, changelog) with the following modifications:
|