ComputeStick CS125 notes
Posted: 28 May 2019, 06:11
Scarfed up another stick, this time the Intel CS125 Computestick. Model STK1AW32SC.
Still your basic 2gb ram, 32gb emmc, but this time with Windows 10(32bit), and an additional usb port (3.0) Has dual-band wireless AC, and uses the intel wireless driver, so Porteus 4.0-64bit picked that up immediately.
Not interested in bluetooth or sound, so didn't test for that.
Bios notes:
Disabled Secure boot.
Enabled 3rd party UEFI signatures.
OS defined in bios is Windows 32 bit, but Porteus boot fine when set to either Windows 64 bit, or Android. So if you want to dual-boot this thing between oem windows 10 and Porteus, you have to go into bios and toggle and restart. Or build your own custom bootloader.
But, like all Intel Atom cpu driven boxes I've tested, the bootcode of
intel_idle.max_cstate=1
seems to be called for. And even then, once in a blue moon, it will lock upon booting. I just powercycle and it usually boots. Added the fsck bootcode even though no major corruption seems to ever occur.
Windows 10, although not to my taste, comes in handy for burning porteus iso's using their own simple method described in the iso file itself.
This unit has been out for a few years, and although mine was fairly recent manufactured within the last 6 months, I still did the bios update from the Intel site (easy to perform!).
Still your basic 2gb ram, 32gb emmc, but this time with Windows 10(32bit), and an additional usb port (3.0) Has dual-band wireless AC, and uses the intel wireless driver, so Porteus 4.0-64bit picked that up immediately.
Not interested in bluetooth or sound, so didn't test for that.
Bios notes:
Disabled Secure boot.
Enabled 3rd party UEFI signatures.
OS defined in bios is Windows 32 bit, but Porteus boot fine when set to either Windows 64 bit, or Android. So if you want to dual-boot this thing between oem windows 10 and Porteus, you have to go into bios and toggle and restart. Or build your own custom bootloader.
But, like all Intel Atom cpu driven boxes I've tested, the bootcode of
intel_idle.max_cstate=1
seems to be called for. And even then, once in a blue moon, it will lock upon booting. I just powercycle and it usually boots. Added the fsck bootcode even though no major corruption seems to ever occur.
Windows 10, although not to my taste, comes in handy for burning porteus iso's using their own simple method described in the iso file itself.
This unit has been out for a few years, and although mine was fairly recent manufactured within the last 6 months, I still did the bios update from the Intel site (easy to perform!).