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) - ascl_ - 2013-12-17 Ah yeah, of course. How frustrating! RE: Intel NUC - HTPC (Haswell Late 2013 edition) - Settepotet - 2013-12-17 (2013-12-17, 12:08)ascl_ Wrote: Ah yeah, of course. How frustrating! Yeah... Well, will try to check out some possible solutions tonight. If not solved, I will ask for a replacement. Seems like this christmas will be without a sexy HTPC... RE: Intel NUC - HTPC (Haswell Late 2013 edition) - d_hero - 2013-12-17 (2013-12-16, 21:12)millercentral Wrote: Just a heads up that I ran into an issue with the r16530 nightly. I use the "Wait for network to start before booting" setting in OE, and with this nightly applied it never gets past that OE splashscreen waiting for the network (keeps showing the "will wait a maximum of 10 seconds" message over and over again). Strange, I need to use this setting too as without it, my SQL library has not connected when Openelec/xbmc boots up, so I set a 5 sec wait for network and had this running on 16519 and now 16559 and no problems at all. It pauses for 5 seconds or less at the Openelec splash and then continues to boot and works flawlessly. RE: Intel NUC - HTPC (Haswell Late 2013 edition) - Camlann - 2013-12-17 I just had a phone Call with an Intel Support Agent; he said to me that the Box is within 30days of Purchase and I shall have it replaced from the Vendor. Called the Vendor, they told me I get my Money back; they expect the next bunch of NUCs mid January :-( Now i'm disappointed, but i'll give the NUC another try in Jan. RE: Intel NUC - HTPC (Haswell Late 2013 edition) - micoba - 2013-12-17 Windows shows me sometimes a message that I don't have sufficient RAM available. I just can't believe that this is true. I've never seen this message on Win 7 on my Desktop PC. Though I set that the HD5000 may use 512MB of the RAM. Is this too much? RE: Intel NUC - HTPC (Haswell Late 2013 edition) - Camlann - 2013-12-17 Check within TaskManager on the Performance Tab. What does Memory look like? How much is "available"? RE: Intel NUC - HTPC (Haswell Late 2013 edition) - arokh - 2013-12-17 (2013-12-17, 09:28)Settepotet Wrote: I'm at work now, so have not tried it. Never got mine to work with mini hdmi cable either. It works with a mini dp to hdmi cable but there is no picture until X starts. After X starts and I get a picture, I can reboot and see the entire boot sequence. Might be because I have hdmi as preferred output, but trying to change that in bios causes a crash. Haven't tried with the latest "22" bios. RE: Intel NUC - HTPC (Haswell Late 2013 edition) - gamble - 2013-12-17 My Nuc works since the beginning with an Hdmi - Mini-Hdmi Cable (No Adapter) without issues..only sometimes if i start up the Nuc without being on my XBMC Input on my AVR i get no picture...then i need to reboot the NUC..guess that are Handshake problems so no bis deal.. RE: Intel NUC - HTPC (Haswell Late 2013 edition) - andreig1978 - 2013-12-17 Hi all, First of all thank you for all the information you took the time to share with the others - although it is a little challenging to go through all the posts Secondly I'm looking into the instant wake up issue and by running: Code: cat /proc/acpi/wakeup and: Code: lspci I see that the following devices are capable to wake up the system: Code: GLAN S4 *enabled pci:0000:00:19.0 00:19.0 Ethernet controller: Intel Corporation Device 1559 (rev 04) Another thing that I noticed is that Code: dmesg Code: [64538.809321] e1000e 0000:00:19.0 eth0: PHY Wakeup cause - Magic Packet Although I don't know of any device that did WoL. I will investigate further but I thought I should share the little that I have found in hope that it sparks an ideea in someone else RE: Intel NUC - HTPC (Haswell Late 2013 edition) - dreamfield - 2013-12-17 I noticed a few comments recently that the ALSA/Linux libraries could cause intermittent audio. Anyone on OE 3.2.4 gotten the new i5 NUC to work with retroarch? I've followed the OE thread on fixes and when you chose the correct HDMI output hardware, it seems to crash and just restart XBMC. Also, when using SSH, and testing with speaker-test for 8 channels, it only seems to play the left and right channels. Curious to know if anyone else has this issue or a recommended solution. RE: Intel NUC - HTPC (Haswell Late 2013 edition) - Settepotet - 2013-12-18 First of all, the NUC now works!! Second, I'm a dumbass... Turns out the problem wasn't with the NUC, but with the user. I bought the mini DP to HDMI adapter yesterday, and that didn't work either of course. So I took out the SSD, RAM and Wifi and was getting ready to send the darn thing back to the shop where I bought it. But then an euraka moment. I booted up my desktop computer, and connected the monitor with the mini HDMI to HDMI cable. No signal. Then I connected it the normal way, via DVI. Signal. Hmm, I entered the menu on my BenQ monitor and there it was. Input was set to DVI only...... So I changed it to HDMI, reassembled the NUC, connected it and booted - voila! The two words "Intel NUC" on my screen was the best letters I've seen in a long time. Windows 7 is now installed, and now my NUC HTPC journey finally begins! RE: Intel NUC - HTPC (Haswell Late 2013 edition) - ascl_ - 2013-12-18 hahah, PEBKAC foils the best laid plans sometimes. At least you have it sorted now! RE: Intel NUC - HTPC (Haswell Late 2013 edition) - Settepotet - 2013-12-18 (2013-12-18, 08:27)ascl_ Wrote: hahah, PEBKAC foils the best laid plans sometimes. At least you have it sorted now! If I just had connected it to my home theater setup in the first place, and not in my home office, all this would have not happened! You live and learn. RE: Intel NUC - HTPC (Haswell Late 2013 edition) - dave_beer_uk - 2013-12-18 I've given up on the remote for the time being as I'm getting nowhere. Sorry if this is too far off topic but I am also having sound problems. Sound works fine in XBMC, browser, and Spotify however in Netflix, ZSNES and Steam I have no sound. Not sure if I should have a asound.rc file and or asound.conf to get it working in other applications? (using Ubuntu) Dave EDIT: All working now by uninstalling and reinstalling Pulseaudio RE: Intel NUC - HTPC (Haswell Late 2013 edition) - millercentral - 2013-12-19 (2013-12-17, 12:36)d_hero Wrote: Strange, I need to use this setting too as without it, my SQL library has not connected when Openelec/xbmc boots up, so I set a 5 sec wait for network and had this running on 16519 and now 16559 and no problems at all. It pauses for 5 seconds or less at the Openelec splash and then continues to boot and works flawlessly. Yeah, looks like it was just that one build as I'm up on the latest now and everything is back to normal. One other note: I noticed the "HD Audio issue with Match Refresh Rate" occurs also on Windows with XBMC 12.3 -- and with Plex too for that matter, so that makes me wonder if it is really just a ALSA linux issue, or if it is something bigger. |