Heya,
recently I installed my NSA326 from scratch, but unfortunately with kernel 6.8.7 I do not see any mtd devices.
So I found out that I have to modprobe mtdblock, but there are still no mtd devices. If using the same rootfs but with kernel 4.9.0 fw_print shows alls the uboot variables, with 6.8.7 I get "Configuration file wrong or corrupted).
I am stuck now since I would expect the mtd device to appear after modprobe.
How could I get mtd running again under kernel 6.8.7?
TIA
Peter
recently I installed my NSA326 from scratch, but unfortunately with kernel 6.8.7 I do not see any mtd devices.
So I found out that I have to modprobe mtdblock, but there are still no mtd devices. If using the same rootfs but with kernel 4.9.0 fw_print shows alls the uboot variables, with 6.8.7 I get "Configuration file wrong or corrupted).
root@nas326:~# dmesg | grep -i nand [ 0.000000] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=pxa3xx_nand-0:2m(u-boot),2m(env),2m(config),15m(kernel1),110m(rootfs1),15m(kernel2),-(rootfs2) earlyprintk=serial [ 2.612649] marvell-nfc f10d0000.flash: too many NAND chips: 7 (max = 4 CS) root@nas326:~# modprobe mtdblock root@nas326:~# fw_printenv Configuration file wrong or corrupted root@nas326:~# ls -la /dev/m* crw-r----- 1 root kmem 1, 1 May 18 05:04 /dev/mem /dev/mapper: total 0 drwxr-xr-x 2 root root 60 May 18 05:03 . drwxr-xr-x 13 root root 12880 May 18 05:04 .. crw------- 1 root root 10, 236 May 18 05:04 control root@nas326:~#
I am stuck now since I would expect the mtd device to appear after modprobe.
How could I get mtd running again under kernel 6.8.7?
TIA
Peter