Intel NUC - Haswell (4th Generation CPU) - Printable Version +- Kodi Community Forum (https://forum.kodi.tv) +-- Forum: Discussions (https://forum.kodi.tv/forumdisplay.php?fid=222) +--- Forum: Hardware (https://forum.kodi.tv/forumdisplay.php?fid=112) +--- Thread: Intel NUC - Haswell (4th Generation CPU) (/showthread.php?tid=176718) 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
|
RE: Intel NUC - HTPC (Haswell Late 2013 edition) - fritsch - 2014-01-02 Those with a nuc an recent kernel, could you try to add (there is a _ in there) Code: acpi_osi='!Windows 2012' to /etc/default/grub and run sudo update-grub after it? Put it behind "quiet splash acpi_osi='!Windows 2012'" Does this still need the workaround? RE: Intel NUC - HTPC (Haswell Late 2013 edition) - tutu - 2014-01-02 What is the fix for? Also my NUC now shuts down properly.. not sure what was going on before! RE: Intel NUC - HTPC (Haswell Late 2013 edition) - fritsch - 2014-01-02 That will use non Windows 8 ACPI tables - perhaps the remote shows up that way, as the problem is in the acpi bios programming. RE: Intel NUC - HTPC (Haswell Late 2013 edition) - Carcharius - 2014-01-02 fritsch - where should that be applied in an OpenElec build? /etc/default/grub doesn't appear to exist Should it be added to the end of the APPEND line in /flash/extlinux.conf after quiet? RE: Intel NUC - HTPC (Haswell Late 2013 edition) - fritsch - 2014-01-02 @Carcharius: Yes, exactly somewhere along that lines. acpi_osi='!Windows 2012' RE: Intel NUC - HTPC (Haswell Late 2013 edition) - zag - 2014-01-02 (2014-01-01, 19:00)cyrusir Wrote: are any of the fanless cases on sale in the UK or europe, probably most interested in the akasa one yes check out the tranquil pc 'abel' range RE: Intel NUC - HTPC (Haswell Late 2013 edition) - Carcharius - 2014-01-02 ok - just tried it I disabled the remote fix in my autostart and rebooted (without the acpi_osi fix in place) cat /sys/bus/acpi/devices/NTN0530:00/physical_node/resources gives just state = disabled I added the acpi_osi fix to extlinux.conf and rebooted again. cat /sys/bus/acpi/devices/NTN0530:00/physical_node/resources still gives just state = disabled Also running poweroff does seem to now cause the nuc to shutdown and stay off rather than reboot. Am testing remotely so can't test actual remote functionality or anything for now. This is on the r16765 build of OpenElec-Generic x86_64 from xbmcnightlybuilds.com RE: Intel NUC - HTPC (Haswell Late 2013 edition) - fritsch - 2014-01-02 Okay, so as a summary: acpi_osi helps with the shutdown issue, but we still need to workaround the IR problem? RE: Intel NUC - HTPC (Haswell Late 2013 edition) - Carcharius - 2014-01-02 Yes that seems to be the case. Can't confirm the shutdown until in front of the machine in a normal usage scenario - i.e. shutting down from within xbmc. But testing remotely over ssh that certainly does seem to be the case. RE: Intel NUC - HTPC (Haswell Late 2013 edition) - cyrusir - 2014-01-02 (2014-01-02, 15:21)zag Wrote:(2014-01-01, 19:00)cyrusir Wrote: are any of the fanless cases on sale in the UK or europe, probably most interested in the akasa one thank you it looks very nice, but its pricey RE: Intel NUC - HTPC (Haswell Late 2013 edition) - passingbat - 2014-01-02 (2014-01-01, 19:00)cyrusir Wrote: are any of the fanless cases on sale in the UK or europe, probably most interested in the akasa one (2014-01-02, 15:21)zag Wrote:(2014-01-01, 19:00)cyrusir Wrote: are any of the fanless cases on sale in the UK or europe, probably most interested in the akasa one (2014-01-02, 19:21)cyrusir Wrote:(2014-01-02, 15:21)zag Wrote:(2014-01-01, 19:00)cyrusir Wrote: are any of the fanless cases on sale in the UK or europe, probably most interested in the akasa one There are some here, but I can't find out much about them as a company. http://www.atlastsolutions.com/intel-next-unit-of-computing/ RE: Intel NUC - HTPC (Haswell Late 2013 edition) - gamble - 2014-01-03 (2014-01-02, 15:30)Carcharius Wrote: Yes that seems to be the case. Can't confirm the shutdown until in front of the machine in a normal usage scenario - i.e. shutting down from within xbmc. Should look like this when modified right? Doesn't work for me, Nuc still reboots on first attempt to Shut off.. FYI : The pic was taken AFTER i tried shutting off, i did execute mount -o remount,rw /flash before editing cuz of the needed permission.. VA-API doesn't work either, if i try to start a Movie while enabled XBMC freezes and i need to use the Power Button of the NUC to get it working again.. HereĀ“s a log of it http://xbmclogs.com/show.php?id=104888 Intel NUC - HTPC (Haswell Late 2013 edition) - millercentral - 2014-01-03 I've found that VA-API doesn't work if "multithreaded" is enabled (i5 Haswell NUC). With multithreaded selected the stream never really starts, and the system eventually locks up. Debug log: http://pastebin.com/ppV2vFUN With multithreading unchecked, VA-API decoding appears to work fine (with about 20% CPU utilization on my i5) using the setting suggested in the VA-API thread (software codec, HW scale at 20%, lancose3, auto deinterlace w/De-interlace). Hope that helps! I'll test more later tonight. RE: Intel NUC - HTPC (Haswell Late 2013 edition) - fritsch - 2014-01-03 @millercentral: "Multithreaded": Please read the description. This highly interfers with every HW Acceleration. HW Decoders need to get the frames single threaded or they crash hard. This setting will be moved to Expert Settings and I will put in a really fat warning. So - that is to be expected. @gamble: Don't introduce newlines. RE: Intel NUC - HTPC (Haswell Late 2013 edition) - gamble - 2014-01-03 Never tried disabling Multithreaded, will try at home, thanks ! @fritsch Also keine neue Zeile beginnen sondern einfach hinter ssh quiet dran? |