+- 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 (/showthread.php?tid=140518)
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
RE: OpenELEC Testbuilds for RaspberryPi - sraue - 2012-11-24
(2012-11-24, 22:03)SFX Group Wrote: DHCP works, however the DNS address is 127.0.0.1 with no secondary, my DHCP server gives out 2 DNS addresses, this is a bug.
this is not a bug:
OpenELEC's connection manager acts as a DNS proxy, (which for sure is locally installed). XBMC dont knows about this and shows the local system as a DNS server - which is right in this case. Our Connection manager handles the DNS stuff then byself.
RE: OpenELEC Testbuilds for RaspberryPi - Milhouse - 2012-11-24
(2012-11-24, 22:03)SFX Group Wrote: DHCP works, however the DNS address is 127.0.0.1 with no secondary, my DHCP server gives out 2 DNS addresses, this is a bug.
OpenELEC (on Pi or otherwise) has always behaved like this.
RE: OpenELEC Testbuilds for RaspberryPi - SFX Group - 2012-11-25
(2012-11-24, 22:20)sraue Wrote: OpenELEC's connection manager acts as a DNS proxy, (which for sure is locally installed). XBMC dont knows about this and shows the local system as a DNS server - which is right in this case. Our Connection manager handles the DNS stuff then byself.
Thanks for the clarification, is there a way of showing the real DNS addresses that openELEC has for administration purposes?
RE: OpenELEC Testbuilds for RaspberryPi - tuxen - 2012-11-25
I can't seem to get the new ram function to work with r12577 it's a total vanilla install on a 512 MB board ofcause.
There is enough ram but nothing is loaded at boot.
RE: OpenELEC Testbuilds for RaspberryPi - sraue - 2012-11-25
(2012-11-25, 02:02)tuxen Wrote: I can't seem to get the new ram function to work with r12577 it's a total vanilla install on a 512 MB board ofcause.
There is enough ram but nothing is loaded at boot.
can you explain what you mean with "but nothing is loaded at boot" ?
RE: OpenELEC Testbuilds for RaspberryPi - tuxen - 2012-11-25
Quote "by default OpenELEC now copys the SYSTEM file to a ramdisk very early and before the SYSTEM file is mounted, if at least 356MB "Total Memory" sorry this is what I mean and does not seem to happen. My gpu split is the default 128MB (default config.txt) but when XBMC is loaded I have 314MB free if I reboot it just hard reboots.
RE: OpenELEC Testbuilds for RaspberryPi - sraue - 2012-11-25
(2012-11-25, 04:06)tuxen Wrote: Quote "by default OpenELEC now copys the SYSTEM file to a ramdisk very early and before the SYSTEM file is mounted, if at least 356MB "Total Memory" sorry this is what I mean and does not seem to happen. My gpu split is the default 128mb (default config.txt) but when XBMC is loaded I have 314MB free if I reboot it just hard reboots.
but you have /dev/SYSTEM (check with "ls /dev"), have fewer diskaccess (check the LEDs) and a faster boot compared with a boot with the "noram" option?
RE: OpenELEC Testbuilds for RaspberryPi - tuxen - 2012-11-25
Ups I'm sorry it works now.. It was me misunderstanding how everything would play out in the end. (and being blind) Everything is good. So sorry for making anyone jump lol. Won't happen again.
Thanks a lot for the release btw.
RE: OpenELEC Testbuilds for RaspberryPi - kraades - 2012-11-25
(2012-11-24, 16:01)sraue Wrote: OpenELEC Development build (r12577):
[*] added a new "boot from RAM" function (please read the notes below)
This build primary added a function to boot from RAM instead accessing the SDCard to much on boot (512MB RPi only):
So the primary purpose is not making the boot faster?
Because compared to r12350 the time from OpenELEC to XBMC is still ~ 35 seconds.
(Yes, I do have a /dev/SYSTEM file)
RE: OpenELEC Testbuilds for RaspberryPi - Milhouse - 2012-11-25
@sraue: I must admit I'm not seeing any performance improvement with the boot from RAM function (I normally boot from a Class 10 card). I confirm I do have a /dev/SYSTEM present.
In fact, booting from RAM is actually slower.
Time from power on for main menu to appear on an overclocked (1000/500/600, force_turbo=1) 512MB Pi with Class 10 Transcend card and metadata stored in a MySQL database:
noram: 32 seconds
ram: 37 seconds
So, five seconds longer and a big chunk of RAM missing.
As you say, the boot from RAM feature may be of benefit to those network booting, but it probably shouldn't be the default for the Pi.
RE: OpenELEC Testbuilds for RaspberryPi - Ned Scott - 2012-11-25
Booting might be slower, but things should be faster when things are running. So it's a speed up as you use XBMC, rather than a speed up for starting up.
RE: OpenELEC Testbuilds for RaspberryPi - xbs08 - 2012-11-25
Is it very noticeable?
RE: OpenELEC Testbuilds for RaspberryPi - Trixster - 2012-11-25
Seems a little nippier to me, when scrolling through the list of videos. Artwork seems to appear faster.
RE: OpenELEC Testbuilds for RaspberryPi - Wanderlei - 2012-11-25
Reports only 10% RAM used after boot, but here is screen cap I think it has loaded to RAM http://img443.imageshack.us/img443/848/capturebo.jpg
Will this mostly improve XBMC performance? Does it have any impact of video playback or is overclocking the way to get better performance there?
RE: OpenELEC Testbuilds for RaspberryPi - Trixster - 2012-11-25
I can't imagine it will have any affect on video playback.