bodhi, >Perhaps the module source code you are using is not a right one. >I'll revisit this issue in the next kernel release. Great. while i don't have any experience in kernel development, nevertheless, may be you can give me some starting point, where i can start to look at it; say, for this specific wifi device, to begin with. Just for the sake of completby ri8 - Rescue System
bodhi Quotebodhi This is the old scheme in Openwrt. Due to the small size of the NAND for ReadyNAS Duo V2, they use squashfs for the volume rootfs. It is not mountable because u-boot does not support squashfs. So even though you can see rootfs and rootfs_data volume in u-boot, they are not accessible. Quotebodhi > 2 mkfs.ubifs -o rootfs.ubifs rootfs/ > 3. ubinized rootfs.ubifs >by ri8 - Rescue System
bohdi, why nobody says? because the only way to KNOW it is to find in one your OWN;-) pretty simple, if you now, HOWTO root@debian:~# cat /proc/mtd dev: size erasesize name mtd0: 00180000 00020000 "u-boot" mtd1: 00020000 00020000 "u-boot-env" mtd2: 00600000 00020000 "uImage" mtd3: 01400000 00020000 "uInitrd" mtd4: 1ec00000 00020000 &quby ri8 - Rescue System
bodhi, to reiterate; if i were about to make my own rootfs and kernel, the steps are following: 1. ubinize uImage -> kernel.ubi 2. mkfs.ubifs rootfs/ 3. ubinize rootfs.ubifs -> rootfs.ubi 4 ubiformat /dev/mtd2 kernel.ubi 5- ubiformat /dev/mtd3 rootf.ubi Right? Regards, alexby ri8 - Rescue System
bodhi, good round-up. One topic remains though, if speaking about moi+ native; thats the RTL8188EUS WIFI chip on the board still not being used, openwrt or debian the same thing. Is it a pci or usb thing? It doesn't help, if any rtl firmware packages or rtl wifi kmod are installed, wlan device will not appear. the site https://wikidevi.wi-cat.ru/Realtek says, it's USBby ri8 - Rescue System
bodhi, they have the openwrt-build or something like that ant it is downloadble, i cat give it a go; so, it's a openwrt imagebuilder compiles(in seconds with make PROFILE=$device) an openwrt-$version-$device-systemupdate.bin to bin/$arch after imagebuilder untarring there are in bash-5.1$ ls build_dir/target-arm_xscale_musl_eabi/linux-kirkwood_generic/ checkpoint_l-50-uImageby ri8 - Rescue System
bodhi, i'm sorry, it was not doable to mount another volumes, besides what was mounted automatically; it is no top level boot directory in root of any mounted(able) volumes; as i flashed systemupdate, there were some errors; i've posted in previous message: may be, it could give some hints? root@OpenWrt:/tmp# sysupgrade -n openwrt-24.10.0-rc2-kirkwood-generic-netgear_re aby ri8 - Rescue System
bodhi, mtdparts, exactly. thanks for your insights. the /proc/cmdline was empty of mtdparts definition, and openwrt 's set it to his default of 4 partitions. i've changed it as you suggested: after systemupdate root@OpenWrt:/tmp# sysupgrade -n openwrt-24.10.0-rc2-kirkwood-generic-netgear_re adynas-duo-v2-squashfs-sysupgrade.bin Wed Dec 18 14:06:09 UTC 2024 upgrade: Commby ri8 - Rescue System
bodhi, OI+> ubi part ubi ubi0: attaching mtd2 ubi0: scanning is finished ubi0: attached mtd2 (name "ubi", size 511 MiB) ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 512 ubi0: VID header offset: 512 (aligned 512), data offset: 2048 ubi0: good PEBs: 4088, bad PEBs: 0, corrupted PEBs: 0 ubi0: user voby ri8 - Rescue System
bodhi, following a thread https://forum.doozan.com/read.php?4,42279 made the stuff they're suggesting while in uboot, inclusive nand erase.ubi booted into Openwrt kernel, opkg-update, opkg install ... opkg install ethtool (suppressed echo ont eth0 with it, thank an you:-) uploaded and installed systemupgrade (openwrt-24.10.0-rc2-kirkwood-generic-netgear_readynas-duo-v2-squashfs-sby ri8 - Rescue System
bodhi, having SoC: Kirkwood 88F6282_A1 Model: TBS MOI+ DRAM: 512 MiB Core: 19 devices, 14 uclasses, devicetree: separate NAND: 512 MiB Loading Environment from NAND... OK In: serial Out: serial Err: serial pcie0.0: Link up Net: eth0: ethernet-controller@72000 Hit any key to stop autoboot: 0 MOI+> mtd mtd mtdparts MOI+> mtdparts device nand0 &by ri8 - Rescue System
bodhi, have i folow the path for zyxels, as you suggested for those devices, and change mtdparts like: fw_setenv mtdparts 'mtdparts=orion_nand:0x100000@0x0(u-boot),-@0x100000(ubi)' current mtdparts looks similarly: mtdparts=mtdparts=orion_nand:1m(uboot),-(data) Regards, alexby ri8 - Debian
bodhi, good, that i've asked you before; i've tried already a lot of openwrt images in the past with an old NSA325 uboot, but now i've forgotten, which of them worked best (eth0). what i well can remember, it was only one of them, where eth0 were working- but unusable, because of a unsupressable echo on it. (had i knew about a trick with ethtool at that time!) Theby ri8 - Debian
bodhi, root@debian:~# nanddump -nf mtd1.dupm /dev/mtd1 Block size 131072, page size 2048, OOB size 64 Dumping data starting at 0x00000000 and ending at 0x1ff00000... root@debian:~# ls -lh mtd1.dupm -rw-r--r-- 1 root root 511M Dec 13 01:25 mtd1.dupm It's quite something there, or not?! Regards, alexby ri8 - Debian
bodhi, thank for your patience with me. I found another thread on this site, that on embeddian, startted from jeff: - booting debian from NAND I could write to this thread, but since the thread is rather old, and one of the latest posts on it is from you, so i go to you once again: i have on moi+ box this: root@debian:~# cat /proc/cmdline console=ttyS0,115200 root=LABEL=rootby ri8 - Debian
bodhi, you 've managed to compile a kernel, which is bootable , as it seems, with all kirkwood devices; if i wanted (i definitely do wont ;-) to compile a kernel myself, which would boot on this box, could i expect any hints from this forum on how to actually make it? Regards, alexby ri8 - Debian
bodhi, now, i see the light! thank your very match, it's a great having you, Regards, alexby ri8 - Debian
bodhi, it should be possible to bring the box up with a stock uImage. but boptomg stops after kernel being loaded . Regards, alexby ri8 - Debian
Sorry, i ment nandwrite /dev/mtd0 mtd0.dump , and, - most important!- unfortunately, i misled you, the stock rootfs tree i've talked about was not original one, but one i created from rootfs which i already booted into with debian uImage; forget about those fdt and mtd0.dump posts. So, only question 1. remaining Regards. alexby ri8 - Debian
bodhi, >I'm not clear yet what you want to do here. I need to see if I can understand! simply put, to make uImage, able to bring up the stock rootfs. it works with: debian uImage , debian and stock uInitrd, with stock and new dtb, but doesn't work with the stock uImage; there is no progress after loading that uImage. If cross-compiled in the tbs-sources tree, configurby ri8 - Debian
bodhi, i found also this file is it poss. to get a mtd layout from? Regards, alexby ri8 - Debian
bodhi, with that dts compiled, i'm able to bring the box up into stock rootfs with all possible combination of debian and stock uInitrd and uEnv.txt (where i have the different paths for stock and your dtb), - but stock uImage; i have no output after stock uImage loads, and there is no network activity on an address i put in etc-network- interfaces obviously, i have to recompileby ri8 - Debian
so, something like than over mtd0 or it is a fdt file , binary , in /sys/firmware Regards, alexby ri8 - Debian
bodhi, thanks for encouraging me:-) You now, its in fact, kinda fascinating to chroot ash on it, and looking around, what 's have been made- like to break occasionally in a old house, where someone for ages leaved. So, i discovered, there is a the directory in /lib/firmware/RTL8192SU with firmware binary within; i recall now, by very first compilation for RTL8188EUS, which isby ri8 - Debian
bodh, the old compile tree from tbs compiles smoothly on x86_64 with 4.9 gcc i've managed to extract also a rootfs tree for the box from their update archive would it be possible to boot the board with your dtb and u-boot loader? there is uImage generated on compile, as well as zImage, and initramfs. is also generated (for mtd, i suppose;-) Regards alexby ri8 - Debian
bodhi, besides, direct after reboot manually modprobe with this output in dmesg: as it seems, can't find the right firmware Regards, alex oot@debian:~# dmesg|tail -10 [ 42.645631] mv643xx_eth_port mv643xx_eth_port.0 eth0: link down [ 42.653111] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled [ 43.598589] mv643xx_eth_port mvby ri8 - Debian
bodhi, (uboot has nothing to do with...) strange: it were not before you posted uboot for moi_plus, that eth0 showed up in it; exactly , that was the reason, i've posted for the first time to this forum; but, as to 8188 - some output there and, 8188eu don't load at boot Regards, alex root@debian:~# lsmod Module Size Used by 8188euby ri8 - Debian
bodhi, compiled with dkms 8188eu driver , version 5.13.5 depmod modprobe ok -> no complains lsmod -> listed ip link -> not listed Now, a silly question;-) Before you 've made that beautiful u-boot, eth0 was also not listed with ip link isn't is the same way with wireless chip, and something have to be activated throu the u-boot first? Regards. alexby ri8 - Debian
bodhi, another: root@debian:/usr/src/linux-headers-6.11.6-kirkwood-tld-1# make scripts SYNC include/config/auto.conf.cmd can't find file Kconfig make[3]: *** Error 1 make[2]: *** Error 2 make[1]: *** Error 2 make: *** Error 2 root@debian:/usr/src/linux-headers-6.11.6-kirkwood-tld-1# r.alexby ri8 - Debian
bodhi, reinstal rootfs, 6.11.6 etc boots normally apt-get update -> OK and then apt-get install xyz complaining about glibc 2.38 the same after reboot, now without network r. alexby ri8 - Debian