OK, to answer comments like:
… and so on
The NVME drive is BRAND NEW and bought from a local seller. Given Australia’s excellent consumer protection, I am completely certain that this seller has supplied the genuine item, so please don’t allow paranoia and bad online experiences to muddy the waters of this issue.
I can say that I’ve tried with an empty disklabel, and also formatted a primary partition as ext4 and/or vfat (with matching filesystem ID in MBR). One utility in Android (DiskInfo) reported that the nvme drive was “INTERNAL” and others declared “BLKEXT”, but under no circumstances does Android itself allow me to setup the drive, as you would normally see when you plug in an external drive. I went as far as comparing the NVME drive to TWO BRAND NEW drives (SATA with USB adapter, and a USB flash drive), but still no dice. I can mount both ext4 and vfat (*snigger … WHY?) filesystems manually, but I’ve not found a way of winning with a modified vendor fstab (system fails to boot) or a script forked late from init.rc (logcat suggests insufficient permissions).
I should also mention that reading from the drive seems fine, but writing corrupts the (1080P) display BADLY, and the ‘q’ key isn’t recognised on a hardware keyboard REAL HANDY OOTB. That’s probably fine for my (current) purpose, in that I’m happy to mount the filesystem as read-only during video playback, but could be a real showstopper if I were to be adding TVHeadend and an old DVB network tuner to the mix. I assume that this is some sort of design fault?
At this point I have to repeat that I’d really prefer to have this working with CoreElec … a REAL Linux by comparison. Checking /proc/config.gz it would seem that NVME block support simply isn’t enabled in 220.127.116.11, even though it seems that the 4.9 kernel used would be suitable for this purpose. This would mean avoiding attempts to circumvent the “security” in Android, and having to deal with a far-from-optimal image.
If the Khadas team is unable or unwilling to enable this kernel module support in CoreElec QUICKLY (given that this is another in a list of capabilities advertised prior to sale, but not realised), then perhaps one of the team members could link the kernel source and CURRENT default.config for CoreElec 18.104.22.168 in this thread? I’m fast running out of time and patience for this particular project to be completed, and I’m more than happy to compile a kernel, if that’s the only problem preventing me from moving on to other issues.
The same request applies to a properly working OpenWRT image, assuming it’s possible to “simply” revert to kernel 4.9 in order to produce a working image, rather than spend months(?) waiting for hyphop to find time to debug the NVME issues with 5.7, and maybe even get around to fixing RSDB WiFi support (also advertised prior to sale, but not yet working).