Hi there,
using Fenix 1.0.10 Ubuntu 22.04 LTS Linux 5.4.125 with gnome on VIM4 (arrived today 
)
But I can’t get my 970evo 1TB to work with the new m2x extension.
lspci is listing the controller: 01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983
but no device under /dev/nvm* and nothing in the disk utility.
Any info or help or necessary steps to activate nvme?
Same issue on my VIM4 + 970EVO.
SSD is shown in lspci, but never found by fdisk.
I can add, that it is not dependend on m2x, also with direct attached ssd same observation can be made
Same here on Ubuntu
phison 1tb sm2801t24gkbb4s-e162 is not visible
01:00.0 Non-Volatile memory controller: Phison Electronics Corporation E12 NVMe Controller (rev 01) (prog-if 02 [NVM Express])
Subsystem: Phison Electronics Corporation E12 NVMe Controller
Flags: fast devsel, IRQ 118
Memory at f5700000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [80] Express Endpoint, MSI 00
Capabilities: [d0] MSI-X: Enable- Count=9 Masked-
Capabilities: [e0] MSI: Enable- Count=1/8 Maskable- 64bit+
Capabilities: [f8] Power Management version 3
Capabilities: [100] Latency Tolerance Reporting
Capabilities: [110] L1 PM Substates
Capabilities: [128] Alternative Routing-ID Interpretation (ARI)
Capabilities: [200] Advanced Error Reporting
Capabilities: [300] Secondary PCI Express
root@Khadas:/home/khadas# dmesg |grep nvme
[ 0.667346] nvme nvme0: pci function 0000:01:00.0
[ 0.667564] nvme 0000:01:00.0: enabling device (0000 -> 0002)
[ 62.430590] nvme nvme0: I/O 16 QID 0 timeout, disable controller
[ 62.431334] nvme nvme0: Identify Controller failed (-4)
[ 62.431343] nvme nvme0: Removing after probe failure status: -5
same here
a@Khadas:~$ dmesg | grep nvme
[ 0.660379] nvme nvme0: pci function 0000:01:00.0
[ 0.660502] nvme 0000:01:00.0: enabling device (0000 → 0002)
[ 62.431524] nvme nvme0: I/O 20 QID 0 timeout, disable controller
[ 62.431689] nvme nvme0: Identify Controller failed (-4)
[ 62.431697] nvme nvme0: Removing after probe failure status: -5
@Khadas:~$ dmesg | grep nvme
[ 0.660379] nvme nvme0: pci function 0000:01:00.0
[ 0.660502] nvme 0000:01:00.0: enabling device (0000 → 0002)
[ 62.431524] nvme nvme0: I/O 20 QID 0 timeout, disable controller
[ 62.431689] nvme nvme0: Identify Controller failed (-4)
[ 62.431697] nvme nvme0: Removing after probe failure status: -5
FYI, with the latest image build with fenix, my nvme ssd is working. So either build you own image with fenix or wait until the next official one is available.
I can share my image (ubuntu 22.04 server) if you want to try
hmm i have also latest kernel build:
Linux Khadas 5.4.125 #1.0.11 SMP PREEMPT Fri Jun 3 10:35:35 PDT 2022 aarch64 aarch64 aarch64 GNU/Linux
but now i am testing diff Nvme, let me revert old one.
ahhh my bad WD Red Sata is not supported ;D
root@Khadas:~# kvm-ok
INFO: /dev/kvm exists
KVM acceleration can be used
root@Khadas:~#
I’m running the latest available version of Ubuntu 22.04 with Gnome on my VIM4 and it doesn’t recognise my 1TB Samsung 970 EVO Plus or my 1TB Netac N930E Pro most of the time. On the rare occasion it does see one of them, it hangs as soon as I try to write to it.
They both work fine in every other device I’ve tried and I’ve tried plugging them into the onboard socket and using a USB3 caddy (which also works on every other device I’ve tried) but it doesn’t make any difference.
Maybe they need more power, what kind of power supply you have ? 25W+ ?
did you build yourself or use oowow image? last time i checked changes are not available in oowow.
I can build my config with gnome and share, but you’ll need to flash via usb burn tool.
970 evo 1tb is definitely working for me (22.04. server)
sorry, I should have said that I’m using the one from OOWOW and it is my understanding that it isn’t possible to create a customized kernel using that.
It isn’t a show stopper so can wait and see if there are any fixes coming.
that is a possibility I’ll have to investigate thanks
Hello @technodevotee
I will upload a new test image which fix the NVMe SSD issue this week then you can use OOWOW to install it.
That’s great - thanks.
It would be great if support for CIFS could be added at the same time.
maybe I should create a new post about that?
Yes, if you want to talk more about CIFS you can create a new topic, if you just want to enable CIFS config then no need to create a new topic, I will add it directly.
Its just that I tried to mount CIFS like I do on my other boxes and discovered that it isn’t supported.
Okay, could you please provide your test command to me to test?