Either lib1.4.77
or lib1.4.193
packages are the OK ones but you are connected with something called libuuu_1.4.193-0-ge56424c
, probably all right but still output that I’m unfamiliar with. Please take a look at this package more closely, please install and use compatible one (lib1.4.77
or lib1.4.193
but not libuuu
) within your Linux distribution.
Another still, related to this post of mine, as of this brand new day (please just bear with me as solution itself, actual flashing one, is not in my hands anyway) is based on that you are currently having on your Librem 5 (that doesn’t boot/react, for some unknown reason, any more) installed Kernel: 5.16.0-1-librem5
(and uuu
package for arm64
in version: 1.4.77-1
).
Now (reproducing steps made by myself), after getting steady red LED light (showing that Librem 5 is physically connected) output of: uuu -lsusb
is already present (as shown in @librem5 posts above) yet sudo fdisk -l
doesn’t see eMMC drive from my/your Librem 5.
My current step two: successful execution of ./boot-purism-librem5.sh
from JumpDrive folder auto-mounts both L5 eMMC partitions but lsusb | grep 8M
and uuu -lsusb
commands doesn’t show any output any more (both outputs are empty). sudo umount /dev/sdb1
and sudo umount /dev/sdb2
changes nothing (as expected) either.
Please provide adequate help to @librem5 on how to establish uuu
connection again, get both: visible Librem eMMC and uuu
working (both connections established at the same time, as perhaps needed for flashing, I think while not moved, as not intend to execute: ./scripts/librem5r4-flash-image
, not now)?
And if relevant, central (and helpful for real) workaround here is probably based around this fact:
That I might briefly (and unofficially) translate into (for the purpose of this thread solution only): current Librem 5 Jumpdrive package is disabling uuu
when 5.16.0-1-librem5
image “on board”. Discussion is open now , all kindly invited (myself already out, I guess, as cannot help any further).
EDIT:
Please ignore my above advice (as probably not helping anyway) here and tell us which Linux distribution you are using? Also, why not to simply extract (unpack) JumpDrive 0.8 archive (as already recommended elsewhere): https://github.com/dreemurrs-embedded/Jumpdrive/releases/download/0.8/purism-librem5.tar.xz
and run ./boot-purism-librem5.sh
from there (related extract folder)?