01-04-2020, 03:36 PM
(01-04-2020, 04:04 AM)sigmaris Wrote:Just wnted to let you know that I tried with the new u-boot images. I no longer got the UnrecognizedFilesystem message, but got a scanning message, then got returned to the u-boot prompt. I changed the armbian build to use ext4 for the nvme, and did reach the kernel starting message, but then hung. I believe this is because the armbian bootscript specifies the partition for u-boot, and seems to specify that it use the same partition from which the spl-tpl image ran. I am going to try to get the armbian images to work, but am now going to try with a manjaro build (which has a much simpler boot script. :-). I'm reasonably good with "c" "bash" not so much...(01-03-2020, 07:52 PM)belfastraven Wrote: ...
=> run bootcmd_nvme0
Device 0: Vendor: 0x144d Rev: EXD7101Q Prod: S444NE0K603440
Type: Hard Disk
Capacity: 244198.3 MB = 238.4 GB (500118192 x 512)
... is now current device
** Unrecognized filesystem type **
JI'm just including the log this time so that you can see that I did use the proper images....
Once again, thanks.
@belfastraven thanks for testing, and pasting the full log here. Looks like your NVMe device is detected OK, I suspect the "Unrecognized filesystem type" problem is just because there is no BTRFS support in this build (it's not enabled in U-Boot by default).
I enabled BTRFS in the config and re-built U-Boot, I haven't tested this yet but you could try using the resulting build, attached:
Edit: if you need the SPI binaries from this build, they can be downloaded from this build artifacts page.