970evo 1tb on VIM4 (new m2x)

for testing I use

mount.cifs //192.168.101.100/sharename /mnt/mountname -o username=shareuser,password=sharepassword,domain=domainname

but for use in scripts, I create a credentials file and reference that in an fstab entry like this

//192.168.101.100/sharename/ /mnt/mountname cifs noauto,uid=0,credentials=/home/username/.smb,iocharset=utf8,vers=3.0,noperm 0 0

Sorry for getting off topic here

Hi,

cifs kernel module was not build in by default. I had build it in my build as well:

server image is tested, gnome was just build. Did not run it. again you’ll need to flash with usb burn tool
@numbqq is it possible to generate images with fenix to flash via oowow? (as this thread is already off topic)

@technodevotee

Checked work on my side with cifs enabled.

$ sudo modprobe cifs
$ sudo modprobe md4
$ sudo mount.cifs //192.168.101.100/sharename /mnt/mountname -o username=shareuser,password=sharepassword,domain=domainname

I will upload tomorrow.

@numbqq @aXe_111 thanks, I’ll give it a try

yes, just need create raw compressed images (with .xz file extension) by fenix, and store it to removable storage or write it directly by network via oowow remote API

in my case i have a VM ubuntu then after compilation simple scp to VIm4 and thats all.

i can share my Kernel with is working on my ubuntu VIM4

sure same possible just replace kernel + modules

Uploaded new image, please use OOWOW to install.

That seems to be working thanks.

My 1TB Netac NVME SSD is seen when plugged into the board and I have read and written to it.

I had to install cifs-utils and append lines in /etc/modules to load cifs and md4 at startup.

I can now mount SMB shares on my NAS using an entry in fstab.

One thing though: I still had to remove and reinstall Firefox as it wouldn’t start.

No need to reinstall, just use snap to install firefox.

$ sudo snap install firefox

it said firefox was installed so I used Synaptic Package Manager to reinstall it

To get back onto the original topic.

Is anyone else that got it working experiencing dropouts of the SSD? I’m using the latest (June 7th) 22.04 image installed via OOWOW with a 970 evo 250gb. I’m trying to run a build from the SSD and partway through I start to get I/O errors and the drive disappears and is no longer seen in GParted.

I don’t have a dmesg log, but I can grab one later.

1 Like

I had only ever tried to use the ssd once, where I have compiled opencv from source on the ssd. After 15 min it dropped out and was mounted in read only mode. Didn’t do much troubleshooting and assumed it was due to temperature of the ssd (no cooling what so ever on the ssd while I was testing)

As you mention it I will try again, and I am currently also experiencing similar problems with the onboard sd card slot. Only emmc and usb attached storage is working flawless for me currently.

1 Like

Thank you for confirming I’m not entirely out to lunch.

I also made some assumptions on temp the first time, but while quite warm I was still able to hold the SSD so it was for sure less than 60 C. I can try slapping a very large heatsink on the SSD and try again.

I can also try the onboard SD slot to confirm your observations, out of curiosity what SD card are you using?

1 Like

See here (64G SanDisk Extreme A2): https://forum.khadas.com/t/sd-card-not-working-properly
But i’ve tried severall ones, all with some sort of error as result

1 Like

Testing with 970evo 1TB (+fan on ssd) and the same script as in the sd thread (and the same server image). It also shows errors in f3read, see:

kernel throws erros on blk_update_requests

[   50.342147]  nvme0n1:
[   50.483522]  nvme0n1: p1
[   50.568223] EXT4-fs (nvme0n1p1): mounted filesystem with ordered data mode. Opts: (null)
[   51.544077] blk_update_request: I/O error, dev nvme0n1, sector 12512 op 0x1:(WRITE) flags 0x4000 phys_seg 127 prio class 0
[   51.544835] blk_update_request: I/O error, dev nvme0n1, sector 11496 op 0x1:(WRITE) flags 0x4000 phys_seg 127 prio class 0
[   51.546226] blk_update_request: I/O error, dev nvme0n1, sector 14560 op 0x1:(WRITE) flags 0x800 phys_seg 122 prio class 0
[   51.547622] blk_update_request: I/O error, dev nvme0n1, sector 13544 op 0x1:(WRITE) flags 0x4800 phys_seg 127 prio class 0
[   51.549027] blk_update_request: I/O error, dev nvme0n1, sector 13528 op 0x1:(WRITE) flags 0x0 phys_seg 2 prio class 0
[  516.562187] Now can use cma, free:6203, wm:6595

@numbqq might be related with the sd issues on my board

I get the same errors in my dmsg. Samsung 970. I also can’t use cifs or nfs for that matter. Just reflashed to the may 16 oowow, and June 7th ubuntu-gnome image.

Looks like identical issues here, with a Sabrent Rocket 4.0 NVME:

~$ lspci
00:00.0 PCI bridge: Synopsys, Inc. DWC_usb3 / PCIe bridge (rev 01)
01:00.0 Non-Volatile memory controller: Phison Electronics Corporation E16 PCIe4 NVMe Controller (rev 01)
khadas@Khadas:~$ lsblk
NAME         MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
mmcblk0      179:0    0 29.1G  0 disk 
mmcblk0boot0 179:32   0    4M  0 disk 
mmcblk0boot1 179:64   0    4M  0 disk 
zram0        253:0    0    0B  0 disk 
zram1        253:1    0  256M  0 disk [SWAP]
zram2        253:2    0  256M  0 disk [SWAP]
zram3        253:3    0  256M  0 disk [SWAP]
zram4        253:4    0  256M  0 disk [SWAP]
zram5        253:5    0    0B  0 disk 
khadas@Khadas:~$ dmesg | grep nvme
[    0.667044] nvme nvme0: pci function 0000:01:00.0
[    0.667098] nvme 0000:01:00.0: enabling device (0000 -> 0002)
[   62.430582] nvme nvme0: I/O 24 QID 0 timeout, disable controller
[   62.430742] nvme nvme0: Identify Controller failed (-4)
[   62.430751] nvme nvme0: Removing after probe failure status: -5
khadas@Khadas:~$ uname -a
Linux Khadas 5.4.125 #1.0.10 SMP PREEMPT Mon Apr 25 13:56:56 CST 2022 aarch64 aarch64 aarch64 GNU/Linux

I’ve flashed the OOWOW to the latest version, but I have not re-imaged the eMMC using the latest version of the Ubuntu image (the Fenix version is higher on the latest image than the one I have).

Should I try that?

EDIT: I just used OOWOW to re-flash the eMMC.

NVME is recognized now. I guess there’s something in the image that’s not included in various updates via apt-get.

1 Like

apt-get is not ready for current image you install via OOWOW, so you can’t upgrade system via apt-get , we will release image with OTA upgrade next month,