Some USB modem devices require to be switched from mass-storage
to serial, since they contain multiple devices and the mass-storage
has e.g. the windows drivers on them. Ths -data package contains
a list of these devices that can safely be switched. For many
modem devices, this is needed to make the device work.
bundles/NetworkManager-extras | 13 ++++++++-----
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/bundles/NetworkManager-extras b/bundles/NetworkManager-extras
index ce1def50..ed9b3f8b 100644
@@ -7,12 +7,15 @@
On Data Analytic Reference Stack (DARS) the big-data-basic bundle is
used with openblas or MKL.
Use openblas as "also-add" to be removed on MKL docker image.
bundles/big-data-basic | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/bundles/big-data-basic b/bundles/big-data-basic
index 766789af..aa6c83a8 100644
@@ -7,7 +7,7 @@
i love clear linux and have been using it without any issues for a few
years on a lenovo thinkpad x1 carbon 3rd gen. however, yesterday i rebooted
and was faced with a non-working laptop keyboard, network, etc.
fortunately i was able to connect a USB keyboard and login. i discovered
that my EFI system partition was not mounted on /boot automatically. and it
had a newer kernel and loader entries -- not the kernel i was actually
AFAICT, the issue was that the clear linux updater put new kernels and
loader entries on my *root* partition (i.e. without the EFI /boot being
mounted). how did that happen?
digging deeper, i found this:
i was able to "fix" the problem as follows:
* the 'boot.mount' file was completely missing from my system ("systemctl
list-units *.mount" showed it as missing/disabled. i used "find" to try and
it find it, but it was nowhere)
* i modified the partition table to set partition types and labels as
specified in the link above. the GPT partition type was not set, and there
was no label either. so I set the type to EFI system partition and the name
to "boot" with gdisk.
* then i created an /etc/systemd/system/boot.mount with the following
* then i did a "systemctl daemon-reload" and "systemctl enable boot.mount"
* before actually mounting the real /boot i created a tarball of the latest
kernel files from /boot/EFI and /boot/loader directories on rootfs.
* i then started the boot.mount, and extracted the latest kernel stuff in
the *real* EFI system partition.
* I am writing this from a now-working system version 31230.
* what went wrong here? i know i have done a "hack" here to make /boot
mount properly., how is this *supposed* to work?
* i'm happy to provide any additional details.
I have a new laptop with Intel Optane (16GB) + 1TB HDD.
I tried installing Ubuntu 18.04 but it has been unable to detect an
Does anyone have any experience installing ClearLinux to such a
Asking before trying because ClearLinux install image is a pretty huge