I have just picked up a Clear Linux image (version 23510)  that I installed on a NUC. The installation ran smoothly and I went straight to the login prompt after reboot the machine. The first thing I did after logging in was to disable the autoupdate feature ('swupd autoupdate --disable'). I was surprised however to notice that the image running is at version 23610. Does the installer perform an update to the latest version automatically when doing a bare-metal installation?
I have an older PC which I am currently running Linux Mint 19 which boots up in UEFI mode and for which your clear-linux-check-config.sh script claims is compatible with ClearLinux as seen below.
However, after an apparent successful install of ClearLinux it is unable to boot. No errors, just a simple blinking cursor and a blank screen; Even after 15 minutes of waiting.
I followed the procedure outlined here: https://clearlinux.org/documentation/clear-linux/get-started/bare-metal-i...
Any ideas what needs to be done to get your ClearLinux installed on this machine?
---------- Cut and Paste output mentioned above below here --------
✔ root@puget> ./clear-linux-check-config.sh host
Checking if host is capable of running Clear Linux* OS for Intel® Architecture
SUCCESS: 64-bit CPU (lm)
SUCCESS: Supplemental Streaming SIMD Extensions 3 (ssse3)
SUCCESS: Streaming SIMD Extensions v4.1 (sse4_1)
SUCCESS: Streaming SIMD Extensions v4.2 (sse4_2)
SUCCESS: Advanced Encryption Standard instruction set (aes)
SUCCESS: Carry-less Multiplication extensions (pclmulqdq)
SUCCESS: EFI firmware
✔ root@puget> efibootmgr -v
Timeout: 1 seconds
Boot0000* ubuntu HD(1,GPT,93e8bda6-2f4d-4f59-a9af-43b46ca09acd,0x800,0x3d0000)/File(\EFI\ubuntu\shimx64.efi)
Boot0002* CD/DVD Drive BBS(CDROM,,0x0)..GO..NO........O.A.S.U.S. . . . .D.R.W.-.2.4.F.1.S.T. . . .b.................>..Gd-.;.A..MQ..L.9.E.0.D.L.C.18.104.22.168.4.5. . . . . . . . ........BO
Boot0003* Hard Drive BBS(HD,,0x0)..GO..NO........O.S.a.m.s.u.n.g. .S.S.D. .8.5.0. .E.V.O. .2.5.0.G.B.................>..Gd-.;.A..MQ..L.2.S.N.1.S.N.G.A.22.214.171.124.8.5. .M. . . . ........BO..NO........O.S.a.m.s.u.n.g. .S.S.D. .8.5.0. .E.V.O. .2.5.0.G.B.................>..Gd-.;.A..MQ..L.2.S.N.1.S.N.G.A.126.96.36.199.8.0. .M. . . . ........BO
Boot0004* ubuntu HD(1,GPT,93e8bda6-2f4d-4f59-a9af-43b46ca09acd,0x800,0x3d0000)/File(EFI\Ubuntu\grubx64.efi)
✔ root@puget> lsb_release -a
No LSB modules are available.
Distributor ID: LinuxMint
Description: Linux Mint 19 Tara
as of release 23550 we have now migrated to Python 3.7, with (almost) all python components
rebuilt for this python release.
The only remaining open item is Tensorflow which will be landing this weekend (TF is always
a bit more complicated) and turning byte compile back on more broadly.
(we hit a bug that the upstream python folks fixed very quickly but it missed the 23550 release)
A full overview of what is new in Python 3.7 can be found at
One of the interesting new features is more advanced debugger support, and we'll be looking
at adding improved debugging options to the distribution in the next week now that the base
From a distribution perspective, the "hashed pyc files" feature is awesome; it means we can
stop mucking around with fragile timestamps of .py files and get all the pyc caching based
on proper hashes. In the 23550 release this feature is not yet turned on; we hit a "fun" bug
( https://bugs.python.org/issue34056 ) with the feature that upstream promptly fixed for us,
but the fixes and pyc files will be in 23570 and later builds.
The release notes also mention improved performance; we'll learn more of that in the next
days as our longer performance runs run over the weekend.