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) - doveman2 - 2015-12-10 (2015-12-10, 14:42)Milhouse Wrote: There should be no space between ! and / I'm using Notepad++. I'm pretty sure I copied this exactly from gendo's post but I've removed the space between ! and / now and still get the same output when I run autostart.sh. I even tried opening it with nano and saving it, both with and without pressing return to go to a newline after the last command and now when I run it I get : not foundostart.sh: line 6: EDIT: OK, if I create a file from scratch with nano it works and gives rmmod: ERROR: Module dvb_usb_af9035 is in use modprobe so it seems I can't even use Notepad++ to create these files. After rebooting "journalctl --no-pager | grep autostart" still doesn't produce any output but "systemctl status kodi-autostart" now gives me รข kodi-autostart.service - Kodi user autostart script Loaded: loaded (/usr/lib/systemd/system/kodi-autostart.service; disabled; vendor preset: enabled) Active: active (exited) since Thu 1970-01-01 01:00:04 BST; 45 years 11 months ago Process: 332 ExecStart=/bin/sh -c . /etc/profile; exec /bin/sh /storage/.config/autostart.sh (code=exited, status=0/SUCCESS) Main PID: 332 (code=exited, status=0/SUCCESS) CGroup: /system.slice/kodi-autostart.service Dec 10 13:12:07 OpenELEC sh[332]: rmmod Dec 10 13:12:07 OpenELEC sh[332]: rmmod: ERROR: Module dvb_usb_af9035 is in use Dec 10 13:12:07 OpenELEC sh[332]: modprobe Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable. Hint: Some lines were ellipsized, use -l to show in full. so it seems to be running properly now. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - doveman2 - 2015-12-11 Still having problems with scanning/updating and playback. I'm on #1204 currently and using the same Hanewin NFS server that I've always used without any problem until recently. Scan was started at 23:29:12 and got stuck on "Preparing" for ages but eventually worked. Then I played a bit of Marvels Episode 10, stopped it and played Ep.9, then went to play Ep.10 again at 00:03:13 and just got the spinner for a while before "Playback failed" at 00:04:35. Log (8MB): https://drive.google.com/file/d/0B1fDI89phEESSUVFOEp5WVJkc2M/view?usp=sharing RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - jeffjoker - 2015-12-13 No new build (since 04/12) ? RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - nalor - 2015-12-13 You have to change to the kodi 17 test build thread. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - gendo - 2015-12-13 looks like mine... shoudl work.. (2015-12-10, 14:59)doveman2 Wrote:(2015-12-10, 14:17)gendo Wrote: doveman output of lsmod please.. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - doveman2 - 2015-12-13 (2015-12-13, 12:17)gendo Wrote: looks like mine... shoudl work.. Thanks. I had time to set the autostart.sh up on my brother's Pi yesterday and when I ran it there was no "ERROR: Module dvb_usb_af9035 is in use" message, which confirms it wasn't working. After I'd run it, the tuner was properly detected in TVh, so hopefully your advice has solved the problem RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - doveman2 - 2015-12-14 (2015-12-11, 02:28)doveman2 Wrote: Still having problems with scanning/updating and playback. I'm on #1204 currently and using the same Hanewin NFS server that I've always used without any problem until recently. I've dropped back to #1128 to try and work out when this problem started and it's happening with that too (at least the long Preparing bit is). I also found that CEC wasn't working, which seems to happen if the Pi input on the TV doesn't have focus when booting. This is the non-working CEC log. I zipped it down to 830KB from 16MB! It's possible the CEC was working at boot and stopped later as I hadn't touched it after updating and rebooting until now but it seems more likely that it wasn't working due to the lack of focus when booting https://drive.google.com/file/d/0B1fDI89phEESalJVdkVvYnBNZmM/view?usp=sharing This is the preparing bug log. Only 328KB this one, as I'd just rebooted. https://drive.google.com/file/d/0B1fDI89phEESbVVyUmJTR2FJY28/view?usp=sharing RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Milhouse - 2015-12-14 In your #1128 and #1204 logs: Code: 23:29:12 37038.968750 T:1625289632 NOTICE: VideoInfoScanner: Starting scan .. So it looks like a WakeOnAccess issue. Can you try with a build which doesn't include PR7030, ie. #1202b (or with build #1204, disable WakeOnAccess support, turn on the server 192.168.1.64 and perform another scan - do you still have the delay?) Finally, test with the latest build #1213 as PR7030 has been updated since build #1204, with updated WOL support. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - jeffjoker - 2015-12-14 (2015-12-13, 11:52)nalor Wrote: You have to change to the kodi 17 test build thread. Yeah I saw that thanks I'm already using the Kodi 17 Was just wondering since Kodi is still not final and Kodi 17 is in early alpha RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Brok3n - 2015-12-14 (2015-12-09, 23:36)slymobi Wrote: Hi, I think I'm in the right place ! Just installed the latest version via Leopold dev add-on and all is good on the system, the GUI is so smooth and responsive its like coming from pi to pi2 all over again I have no playback issues or anything but what I am having issues with and unable to find any reports on is CEC. All versions upto Jarvis have worked perfect with my Samsung remote via CEC but after initial install of Jarvis it just won't work.This keeps happening but I have found a solution.... If I switch off the pi via shutdown and the switch off my TV from the mains, turn TV on and then pi its resolved and CEC is back to normal. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - popcornmix - 2015-12-14 (2015-12-14, 17:35)slymobi Wrote: This keeps happening but I have found a solution.... If I switch off the pi via shutdown and the switch off my TV from the mains, turn TV on and then pi its resolved and CEC is back to normal. The Pi reads the TV's EDID on boot. This includes the CEC physical address. Some TVs allow the EDID to be read when powered off (this is possible as the Pi provides 5V through HDMI cable for this purpose). Some TVs only allow EDID to be read when powered on (and some only if on the correct AV input). For TVs that don't allow reading the EDID you can capture the EDID to a file: http://kodi.wiki/view/Raspberry_Pi_FAQ#TV_is_not_detected_unless_powered_on_first This may help your issue. Make sure you remove or update the setting if you want to use the Pi with a different TV (or you change HDMI input on TV). RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - doveman2 - 2015-12-14 (2015-12-14, 08:44)Milhouse Wrote: So it looks like a WakeOnAccess issue. Can you try with a build which doesn't include PR7030, ie. #1202b (or with build #1204, disable WakeOnAccess support, turn on the server 192.168.1.64 and perform another scan - do you still have the delay?) I tested with #1115, #1202b and #1213 and it's fine with all three. Thanks for your assistance. Note the server (actually my PC) has always been on when testing, so it seems like there was a bug introduced into the WOL support somewhere. On the CEC issue, I've been using the forced edid.dat for some time now and still have issues with the remote not working occasionally. It's not often enough to be bothersome though. I'll try recreating the file anyway, as I guess it might have got corrupted. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - HomerJayS - 2015-12-18 (2015-12-05, 19:06)niwa2 Wrote:Hello!(2015-12-05, 18:37)popcornmix Wrote:Quote:I tried this as well on #1204 with the same result. But #1204 does not play anything in 3D. With #1203 3D is working fine.I don't see anything 3D related in changes for #1204. Can you double check? If still a problem, Can confirm these findings. Just updated to #1204 because I wanted to try MVC Support -no succes (would only play as 2D). After I read the above, I downgraded to #1203 and it works like a charm. I just wanted to let you know, that a maybe new occured bug can be recognized as early as possible! Cheers and thanks a lot for your great work!! RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - popcornmix - 2015-12-18 (2015-12-18, 15:31)HomerJayS Wrote: Can confirm these findings. Just updated to #1204 because I wanted to try MVC Support -no succes (would only play as 2D). After I read the above, I downgraded to #1203 and it works like a charm. These builds are superceded by Kodi 17 builds. Thy the latest build there and report (on that thread) if there is still a problem. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - steve1977 - 2016-01-01 I am using mysql. If I were to keep my OSX / Win builts on Kodi 16 Beta 4 / RC / stable, what would be the ideal version for OE keeping mysql working. Would this be #1204 above? |