1 of 1 people found this helpful
Just to be clear, BIOS 35 for the SC Compute Stick is NOT the same as BIOS 35 for the FC Compute Stick. These BIOSs are completely independent of each other; there was a full year's difference in the BIOS origins. They just happen to be the 35th BIOS version built for each of these Compute Sticks.
Can you clarify what you mean by "Funny the unsupported model is running more solid than the supported one" as it seems somewhat contradictory given the device model numbers you quote and your description of the issue?
Our fleet of STCK1A8LFC's which are EOL and no longer supported seem to boot reliably.
Our fleet of STK1A32SC's which are a current supported model do not boot reliably.
The STCK1A8LFC originally came with Ubuntu 14.04 with a v3.16 kernel so is it still running the same release and kernel version? Obviously the STK1A32SC didn't come with any OS so what release/kernel combo are you running on those devices? A link to a 'dmesg' from (one of) each device and posted via 'pastebinit' would be useful.
The 'dmesg' logs need to be captured immediately after booting.
Unfortunately these logs are incomplete. Maybe it is better to use the 'pastebinit' command (see https://help.ubuntu.com/community/Pastebinit). First install the command by entering 'sudo apt-get install -y pastebinit' and then reboot the device. After booting login and enter 'dmesg | pastebinit'. This will paste a copy of the output from 'dmesg' to Ubuntu's Pastebin. Then post the URL it returns here and repeat this for the other device.
That's a great tool I'd never used before! That'll be very useful for me in the future.
Thank you for your patience.
FYI one stick has been updated to the SCCHTAX5.86A.0037 firmware. Its paste is here: http://paste.ubuntu.com/25728551/
Are you interested/willing to perform a re-installation or do you want to keep the current installation? Also for each model (i.e. STCK1A8LFC and STK1A32SC), what is the Ubuntu release? Probably best to run the command 'cat /etc/lsb-release' on a device of each model like you did for the 'dmesg' and post the results.
While operationally not ideal, a re-install would be okay if it solves the issue we're having.
DISTRIB_DESCRIPTION="Ubuntu 14.04.5 LTS"
DISTRIB_DESCRIPTION="Ubuntu 16.04.2 LTS"
I'm looking into this and as a result have another question. Given you are using the devices in a digital signage capacity is sound or audio over HDMI required?
Thanks for looking into it. We currently do not use sound with our signage systems.
The kernels you are running on both devices are old and unsupported. Even though 14.04 is an LTS you should really be on a v4.4 kernel so that you are supported. You are probably being held back by DKMS dependencies to provide HDMI audio which you have confirmed is not required. Equally for 16.04 you should not be using one of my earlier kernels but one that is fully supported. You are already a point release behind as the current is 16.04.3. It would probably be simpler to reinstall but I'd recommend getting all devices to 16.04.3 and to get the best official kernel for your devices I'd recommend installing the package 'linux-generic-hwe-16.04-edge' which currently would take you to the v4.11.0-14.22 kernel. This kernel includes a lot of the patches for both Bay Trail and Cherry Trail devices and if you keep this updated you soon pick up the latest power management patches that provide the best functionality. By moving to the v4.11.0-14.22 kernel you should find the "Purple Screen of Death" is no longer an issue as at least I'm not experiencing them in testing.