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.