Baytrail J1900 - this one has the CPU bug that when switching loads (and therefore C-States) would just freeze, hang and so on. You have two possibilities:
a) Build a kernel that has a workaround for that
b) use the intel_idle.max_cstate=1 kernel parameter to disable them by software (it will get hotter that way)
Fritsch, thanks tremendously for your efforts. Both files downloaded, installed, and a reboot confirms they're now in use:
old:
Quote:root@fender:/etc/grub.d# uname -a
Linux fender 4.4.0-104-generic #127-Ubuntu SMP Mon Dec 11 12:16:42 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Current:
Quote:fender:/home/dave $ uname -a
Linux fender 4.14.13-byt1+ #1 SMP Sat Jan 13 18:38:19 CET 2018 x86_64 x86_64 x86_64 GNU/Linux
(for those that aren't Linux-savvy, this was pretty idiot-proof and required very little effort on the user part, thanks to Fritsch's work).
Not sure if it's of any concern, but had some warnings crop up during the install:
Quote: Hmm. There is a symbolic link /lib/modules/4.14.13-byt1+/build
However, I can not read it: No such file or directory
Therefore, I am deleting /lib/modules/4.14.13-byt1+/build
Hmm. The package shipped with a symbolic link /lib/modules/4.14.13-byt1+/source
However, I can not read the target: No such file or directory
Therefore, I am deleting /lib/modules/4.14.13-byt1+/source
Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.14.13-byt1+ /boot/vmlinuz-4.14.13-byt1+
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.14.13-byt1+ /boot/vmlinuz-4.14.13-byt1+
update-initramfs: Generating /boot/initrd.img-4.14.13-byt1+
W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module i915
Nonetheless, everything seems fine; I'm currently soak-testing it with an episode downstairs that it previously crashed on.
The previous build would bomb out every 30 mins, you can see the (list) of crashlogs here:
http://paste.ubuntu.com/26385087/ - I take it the known CPU bug means none of these are of any use? If so, I'll clear them out and await new ones.
Thanks again for your speedy response; I'm hoping to transition everything over to this new silent box and I'm still getting caught out with finding some OS-level oddities, but it's reassuring to hear that some aren't just known issues but workarounds are also available.
nb: in the light of this issue, should I hold off on future kernel updates? Thinking newer Canonical-supplied kernels may lack the tweaks you've done here.
Test it for a few more days. Remove the other crashlogs so we can look into the new ones when your system crashes and burns again.
Thanks... but the regular 30-min crashlogs are reapparing again.
http://paste.ubuntu.com/26386408/ is the latest one.
Peculiarly, a few earlier crashlogs show issues with files I was playing fine. I don't recall the screen blanking nor Kodi resetting in this time, so it looks more like a dump than an actual crash and restart.
Would earlier logs help also? Appreciate you looking into this issue, Fritsch.
It's caused by this addon:
Quote:17:13:47.135 T:140468414859008 NOTICE: weather.metoffice: Fetching Hourly Observation for 'Heathrow (3772)' from the Met Office...
17:13:47.142 T:140468414859008 NOTICE: weather.metoffice: Fetching Daily Forecast for 'Great Malvern (351670)' from the Met Office...
17:13:47.147 T:140468414859008 NOTICE: weather.metoffice: Fetching 3 Hourly Forecast for 'Great Malvern (351670)' from the Met Office...
Remove it please.
Removed! Will see if I get another crashlog showing up. For a few other questions:
- Any suggestions for alternatives? Being UK-based, I picked it from the list... but it won't be any great loss if I have no weather showing up in Kodi.
- Is it possible to add/remove plugins from the command-line, or from the web interface (http://kodiserver:8000)?
- Is the location of crashlogs configurable? Was thinking of pointing it at another directory location to keep them out of the home directory.
If the answers are simply "yeah, read the Wiki" then I'll head off there. I realise it's been some time since I checked it, I ought to read up recent developments, actually...
Nope, but please ask those in another thread. No one will find those questions in here :-)
Good point! New thread forthcoming...
For what it's worth, no crashlog appearing, so it seems Met Office plugin was definitely the culprit for that - thanks!
Hi Kodi Team,
I think I have the same problem as camelreef with my intel NUC7i3BNH
(see his post: #4,567).
Unfortunately, his screenshots and the testfile are already deleted.
I don't experience this issue with ubuntu kernel 4.10.0-37-generic (4k hevc 10bit playback for hours without a problem). All kernels including 4.13 and higher give me this problem after 30-45min into perfect playback. Did somebody ever got this to fix? Apart from that, it's an awesome setup which plays everything in HW!
Here is a log of using the 4.13.16-041316-generic kernel:
Code:
dpkg -l |grep mesa | pastebinit
http://paste.ubuntu.com/26454035/
DISPLAY=:0 vainfo | pastebinit
https://paste.ubuntu.com/26454038/
cat ~/.kodi/temp/kodi.log | pastebinit
https://paste.ubuntu.com/26454055/
dmesg | pastebinit
https://paste.ubuntu.com/26454065/
id | pastebinit
uid=1000(erik) gid=1000(erik) groups=1000(erik),4(adm),20(dialout),24(cdrom),27(sudo),30(dip),46(plugdev),104(fuse),108(lpadmin),125(sambashare),126(vboxusers)
amixer | pastebinit
https://paste.ubuntu.com/26454069/
Thanks,
Erik
Wrong thread. This thread is NOT about Linux-Mint:
Quote:1:09:34.886 T:140177976863104 NOTICE: Running on Linux Mint 18.3, kernel: Linux x86 64-bit version 4.13.16-041316-generic
Please open your own thread.
(2017-06-28, 12:28)Axman Wrote: [ -> ] (2017-06-28, 12:19)soder Wrote: [ -> ]Hi. I know this is kind of a question that might not be suited for this thread, but I try it anyways.
I got a Intel NUC (nuc5cpyh) with braswell, and I kind of bought it cause I thought it was "future proof" and could do both x264 and hevc in 2160p. I've later learned from you guys in here that it doesn't play hevc in 10bits in HW, making it impossible to play 2160p hevc in 10bit on that NUC.
I wonder if there's some other great hardware to use a my HTPC, wíth about the same specs as my NUC, but also play 10bits hevc?
Thanks.
/Söder
I'll apologize in advance, because my answer will disappoint you. Unfortunately, it is based on fresh experience and as such reflects reality:
- Braswell is not future proof - you should opt for Kaby Lake now to get HW decoding of HEVC in 2160p
- You need bleeding edge Mesa (Intel) drivers and latest Kodi agile (from git), see my post for instructions: https://forum.kodi.tv/showthread.php?tid...pid2543877
- the 7th Gen NUCs have these CPUs, but unfortunately there are issues with DTS-HD bitstreaming on Linux. I had a Gen 7 i3 NUC and was unable to get passthrough of HD audio working (but hw encoding of the video worked
Short answer: Buy a desktop PC (mini ITX H270 board for example, if you want it small) and use a Kaby Lake CPU on it. Then follow step 0 of Fritsch's guide in first post, and follow my instructions from step 1.
Then you'll have a future proof system capable of HW decoding 10bit HEVC 2160p, and also full HD audio passthrough support. The result of my search for the ultimate HTPC.
For more general advice on hardware picks, I would consult wrxtasy's guide here: https://forum.kodi.tv/showthread.php?tid=252916
If I didn't thank you before, I do it now. I've returned to your post many times, and tried to look in to what I should get instead of my Braswell NUC.
I miss being able to see hevc 4k 10bits on my (for now) not HDR ready TV, and I returned once again to your post to find the url to the guild.
I think that the Vero 4K could be something for me. It's not android, and seems to be able to do a lot of stuff I want. Do you guys think it's a great device?
If not, what is it missing in your opinions?
Thanks.
/Söder
(2018-01-07, 17:53)fritsch Wrote: [ -> ]Your user is not member of video nor audio (see useradd on the first page)
Quote:uid=1000(dni) gid=1000(dni) groups=1000(dni),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),110(lxd),115(lpadmin),116(sambashare)
now dni is part of the required groups, but the problem still persists:
dni@ubi- htpc :~$ groups
dni adm dialout cdrom sudo audio dip video plugdev users input lxd lpadmin sambashare
dni@ubi-htpc:~$ groups kodi
kodi : kodi dialout cdrom audio dip video plugdev users input
But as far as is can tell kodi application is running by kodi user, not by dni. Could you please tell me what should I check next to get proper audio pass-through?
Repost all your logs .. no crystal ball here.
In the meantime, i managed to solve it. I disabled pulse audio globally, so i can use alsa instead and now it works as expected.
Thanks for your help.