• 1
  • 198
  • 199
  • 200(current)
  • 201
  • 202
  • 260
Intel NUC - Haswell (4th Generation CPU)
Another one: @trsqr: You can contact me in #xbmc-xvba or #xbmc and I can show you how to git bisect between those revisions and exactly find that commit. as those are only approx 15 commits, we are finished after max 4 compilations.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
Got an i3 Haswell coming over the weekend to use with openelec. Does anyone have a link or advice on what settings are recommended for video and audio configuration?
Reply
(2014-05-02, 17:36)Nellgrove Wrote: Got an i3 Haswell coming over the weekend to use with openelec. Does anyone have a link or advice on what settings are recommended for video and audio configuration?

The most important thing is to forget about using the stable Frodo Openelec, nothing much works! Use the latest Gotham beta or r17733 nightly if you want live TV to work with a USB tuner stick (see long recent discussion about kernel regression). Apart from that, I changed very few of the default settings. I think all I did was set deinterlace to "auto" for all sources, and "enable SW filter for VAAPI". Fritsch has some more detailed suggestions here

http://forum.xbmc.org/showthread.php?tid=165707

that you might want to experiment with.
Reply
http://forum.xbmc.org/showthread.php?tid=165707
Reply
We will find the culprit tonight, tsqr has started bisecting and 4 steps are left. Stay tuned.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
Thank you both Smile
Reply
Has anyone had either of the two following problems on the Haswell NUCs?

1.)After installing XBMCBuntu, the keyboard no longer works on startup to get into the BIOS. Using a K400.

2.)Shutting down causes an immediate restart every time.
Reply
(2014-05-02, 19:49)ratzofftoya Wrote: Has anyone had either of the two following problems on the Haswell NUCs?

1.)After installing XBMCBuntu, the keyboard no longer works on startup to get into the BIOS. Using a K400.

2.)Shutting down causes an immediate restart every time.

1. yes i had this issue. Pulling the power cable and re plug it should help in this situation.

2. Either disable Wake on Lan in the Bios or install the latest BETA Bios. The Issue should be fixed then. https://downloadcenter.intel.com/Detail_...ldID=23826
Reply
hi guys,

Got Abel H2 case and mounted in it recently my I5 NUC.
I'm little scared though about the temperatures.

Idle is ~40C
Watching movies ~55C with 10% cpu load.
Watching Netflix over silverlight pushes temps to ~75C with HDD temps reaching almost 60C

max when pushing temp with Prime95 was 85!

Is this normal ?

when watching netflix whole case is barley touchable, so hot it is :O

I used first time paste given with case but Nuc shutdown twice on me with temp around 50, so i repasted with best artic silver I could get and it started to work without hickups but the temps are scary.
I'm afraid it will start fire on my TV closet.

Anyone with abel H2 case wants to post experience ?
Reply
(2014-05-02, 17:51)fritsch Wrote: We will find the culprit tonight, tsqr has started bisecting and 4 steps are left. Stay tuned.

Ok, I've compiled 7 kernels now with some serious git+kernel compilation guidance from fritsch. As a result it seems that this commit is the one causing the issue. It seems that this same commit breaks multiple PCTV 290e tuners in one NUC as well.

Code:
47f467ac740ebf0475a5176ddb1741acba6aad4e is the first bad commit
commit 47f467ac740ebf0475a5176ddb1741acba6aad4e
Author: Sarah Sharp <[email protected]>
Date:   Fri Jan 31 11:45:02 2014 -0800

    Revert "xhci: Set scatter-gather limit to avoid failed block writes."

    commit 1386ff75797a187df324062fb4e929152392da88 upstream.

    This reverts commit f2d9b991c549f159dc9ae81f77d8206c790cbfee.

    We are ripping out commit 35773dac5f862cb1c82ea151eba3e2f6de51ec3e "usb:
    xhci: Link TRB must not occur within a USB payload burst" because it's a
    hack that caused regressions in the usb-storage and userspace USB
    drivers that use usbfs and libusb.  This commit attempted to fix the
    issues with that patch.

    Signed-off-by: Sarah Sharp <[email protected]>
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

:040000 040000 632634f31130502e87cd3e5fd0e300d5a8249ffd 8f1de710a99ac9b721bb77dc0dd2ab9de9597029 M       drivers

The good ones were very stable. I recorded 2 HD channels, watched 1 other HD channel in XBMC with EPG overlaid on it and used another tuner to record SD channel while compiling the next kernel, and not a single continuity error was seen during the compilation.

This was an eye-opening experience. Nice that we masterminds like fritsch who are able to come up with such a test setup, that a lesser Linux mortal like myself could actually make the tests and contribute in some way. Now I would need suggestions on how to proceed with the bug reporting.

Edit: The way I tested was: started with a single tuner connected. Started to record a HDTV channel and watch another one in XBMC. Then tried to watch the EPG and move around in the menus. In some of the versions this caused continuity counter errors in the logs. Then I enabled the second tuner. For the softwares that I saw continuity counter errors, there was also an XHCI crash when the second tuner was used. So it seems that the root cause for both problems is the same.
Reply
Which RAM do you suggest I use in the Haswell NUC? I want it to be as fast as it can, but I don't want to waste money on overkill.

Also, can someone suggest the benefits/disadvantages of either openelec or XBMCBuntu? (I have not used either of them yet).

Thank you.
Reply
(2014-05-02, 21:29)trsqr Wrote:
(2014-05-02, 17:51)fritsch Wrote: We will find the culprit tonight, tsqr has started bisecting and 4 steps are left. Stay tuned.

Ok, I've compiled 7 kernels now with some serious git+kernel compilation guidance from fritsch. As a result it seems that this commit is the one causing the issue. It seems that this same commit breaks multiple PCTV 290e tuners in one NUC as well.

Code:
47f467ac740ebf0475a5176ddb1741acba6aad4e is the first bad commit
commit 47f467ac740ebf0475a5176ddb1741acba6aad4e
Author: Sarah Sharp <[email protected]>
Date:   Fri Jan 31 11:45:02 2014 -0800

    Revert "xhci: Set scatter-gather limit to avoid failed block writes."

    commit 1386ff75797a187df324062fb4e929152392da88 upstream.


    This reverts commit f2d9b991c549f159dc9ae81f77d8206c790cbfee.

    We are ripping out commit 35773dac5f862cb1c82ea151eba3e2f6de51ec3e "usb:
    xhci: Link TRB must not occur within a USB payload burst" because it's a
    hack that caused regressions in the usb-storage and userspace USB
    drivers that use usbfs and libusb.  This commit attempted to fix the
    issues with that patch.

    Signed-off-by: Sarah Sharp <[email protected]>
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

:040000 040000 632634f31130502e87cd3e5fd0e300d5a8249ffd 8f1de710a99ac9b721bb77dc0dd2ab9de9597029 M       drivers

The good ones were very stable. I recorded 2 HD channels, watched 1 other HD channel in XBMC with EPG overlaid on it and used another tuner to record SD channel while compiling the next kernel, and not a single continuity error was seen during the compilation.

This was an eye-opening experience. Nice that we masterminds like fritsch who are able to come up with such a test setup, that a lesser Linux mortal like myself could actually make the tests and contribute in some way. Now I would need suggestions on how to proceed with the bug reporting.

Edit: The way I tested was: started with a single tuner connected. Started to record a HDTV channel and watch another one in XBMC. Then tried to watch the EPG and move around in the menus. In some of the versions this caused continuity counter errors in the logs. Then I enabled the second tuner. For the softwares that I saw continuity counter errors, there was also an XHCI crash when the second tuner was used. So it seems that the root cause for both problems is the same.


Ok nice work to both of you ! Any chance of a new Openelec test build ? Big Grin
Reply
(2014-05-02, 21:29)trsqr Wrote:
(2014-05-02, 17:51)fritsch Wrote: We will find the culprit tonight, tsqr has started bisecting and 4 steps are left. Stay tuned.

Thanks so much to trsqr and fritsch for their fantastic work. The usb kernel people have already had to revert an adjacent commit that caused a regression for mass storage devices

https://lkml.org/lkml/2014/3/6/284

seems they were having a bad commit day ...
Reply
(2014-05-02, 21:32)mystik Wrote: Also, can someone suggest the benefits/disadvantages of either openelec or XBMCBuntu? (I have not used either of them yet).

Try it yourself, it's free Nod
XBMCbuntu is a minimal Ubuntu with XBMC + Desktop (Lubuntu)
OpenElec is XBMC only on a very small Linux Kernel
Benefit from XBMCbuntu is, you have a Desktop and you can use Tools/Drivers for Ubuntu.
Benefit from OpenElec (if you have the right Hardware), you can set it um in 2 min and just use it.
You can also use ubuntu minimal + XBMC, when you don't want a Desktop: http://forum.xbmc.org/showthread.php?tid=165707
| myHTPC |
Reply
https://github.com/OpenELEC/OpenELEC.tv/pull/3165 <- no "me too" comments please :-)

I have pinged sarahsharp, let's see if she has time to comment.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
  • 1
  • 198
  • 199
  • 200(current)
  • 201
  • 202
  • 260

Logout Mark Read Team Forum Stats Members Help
Intel NUC - Haswell (4th Generation CPU)7