Alex,

> 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?!

Perhaps. Use hexedit to look at its content.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Alex,

> 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,

Emdebian is no longer supported for quite many years, so should not be used.

If you want a rescue system on NAND, look into OpenWrt. In the Rescue sub-forum:

https://forum.doozan.com/read.php?4,86219
https://forum.doozan.com/read.php?4,42279

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

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!)
Therefore, what do you think would be the closest quess
for openwrt image for that box?

Regards, alex

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, alex

Alex,

Please create a new thread "OpenWrt on TBS MOI+" in the Rescue System sub-forum.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Alex,

Please see this post for release candidate kernel linux-6.13.0-kirkwood-tld-1.

https://forum.doozan.com/read.php?2,12096,138968#msg-138968

I've configured in more wifi adapters, which should support the one on this MOI+.

If during boot, you don't see the Wifi adapter brought up, then modprobe the driver.

modprobe rtl8xxxu

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi,

installed, apt upgrade, reinstalled   firmware-realtek - but
no other ifs except already known ones.

i have to remount manually at boot, as you see 
interesting, the same type of  bootcmd and  fstab,
if booting usb - it's still 6.5.7 - no need to manually remount as contrary to sata.

What about uboot-env, i have to manually hardcode 3d partition in your scan_disk variable, in order it finds 3d partition of sata disk.

Regards,
alex

Alex,

> installed, apt upgrade, reinstalled
> firmware-realtek - but
> no other ifs except already known ones.

This probably related to the way you are booting now. It's a wrong way to boot with new u-boot.

>
> i have to remount manually at boot, as you see
> interesting, the same type of bootcmd and
> fstab,

> if booting usb - it's still 6.5.7 - no need to
> manually remount as contrary to sata.
>
> What about uboot-env, i have to manually hardcode
> 3d partition in your scan_disk variable, in order
> it finds 3d partition of sata disk.

You did not post the envs, but I can tell the envs are all messed up.

========

Don't change any envs, use the default envs that come with the new u-boot

Quote

Update 13 Nov 2024

Download at Dropbox

I have not uploaded the tarball to Dropbox yet. For now, please download the tarball attached to this post.

uboot.2024.10-tld-1.moi_plus.bodhi.tar
sha256:
bb1b7ad85d2282b48e4d8199bb9b882b135dc550670f4f338d34b237c305cf1b uboot.2024.10-tld-1.moi_plus.bodhi.tar

This tarball contains 3 files:
uboot.2024.10-tld-1.moi_plus.kwb
uboot.2024.10-tld-1.moi_plus.environment
uboot.2024.10-tld-1.moi_plus.environment.img

Boot with only SATA rootfs attached.

printenv
boot

And post the entire serial console log.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi,

default envs don't support for 3d sata partitition,
therefore i had to hardcode  to "disknum:3" in scan_disk

 if load $dev $disknum:1 $load_uimage_addr /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:1; 

and 
setenv device=0:3

which results in panic(attached)

my fstab  on sda3 is:

Sat Jan 1 01:59:32 CET 2000 up 0 minutes
root@debian:~# mount /dev/sda3 /mnt/hd
[   56.552226][ T1088] EXT4-fs (sda3): mounting ext3 file system using the ext4 subsystem
[   56.946316][ T1088] EXT4-fs (sda3): mounted filesystem 0dab553c-2087-4866-8318-a06a2829035e r/w with ordered data mode. Quota mode: none.
root@debian:~# cat /mnt/hd/etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
LABEL=rootfs    /               ext3    noatime,errors=remount-ro 0 1
#/dev/sda3    /               ext3    noatime,errors=remount-ro 0 1
tmpfs          /tmp            tmpfs   defaults          0       0
root@debian:~#

root@debian:~# e2label /dev/sda3
rootfs

Regards,
alex

Alex,

The scan_disk is ok to change to 0:3.

It does not look like you are using the default envs in this boot 'devnum_3_device_0_3_panic.txt'.

Defaut envs: uboot.2024.10-tld-1.moi_plus.environment

baudrate=115200
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; reset
bootcmd_exec=if run load_uimage; then; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run load_dtb; then bootm $load_uimage_addr - $load_dtb_addr; else bootm $load_uimage_addr; fi; fi; fi
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootdelay=10
bootdev=usb
console=ttyS0,115200
device=0:1
devices=usb sata
disks=0 1 2 3
dtb_file=/boot/dts/kirkwood-moi-plus.dtb
if_netconsole=ping $serverip
load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file
load_dtb_addr=0x1c00000
load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd
load_initrd_addr=0x2100000
load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage
load_uimage_addr=0x800000
mtdparts=mtdparts=orion_nand:1m(uboot),-(data)
preboot_nc=setenv nc_ready 0; for pingstat in 1 2 3; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then run start_netconsole; fi
scan_disk=echo running scan_disk ...; scan_done=0; setenv scan_usb "usb reset; sleep 1; usb reset";  setenv scan_sata "sata init";  setenv scan_mmc "mmc rescan"; for dev in $devices; do if test $scan_done -eq 0; then echo Scan device $dev; run scan_$dev; for disknum in $disks; do if test $scan_done -eq 0; then echo device $dev $disknum:1; if load $dev $disknum:1 $load_uimage_addr /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:1; setenv bootdev $dev; fi; fi; done; fi; done
set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin serial,nc; setenv stdout serial,nc; setenv stderr serial,nc; version;
stderr=serial
stdin=serial
stdout=serial
uenv_addr=0x810000
uenv_import=echo importing envs ...; env import -t $uenv_addr $filesize
uenv_init_devices=echo Initializing devices...; setenv init_usb "usb reset; sleep 1; usb reset"; setenv init_sata sata init;  setenv init_mmc mmc rescan; for devtype in $devices; do run init_$devtype; done;
uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices; do for disknum in $disks; do if test $uenv_loaded -eq 0; then setenv device_type $devtype; setenv disk_number $disknum; run uenv_read; fi; done; done;
uenv_read=echo Loading envs from $device_type $disk_number...; if load $device_type  $disk_number:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; echo ... envs loaded; fi

Repeat this boot 'devnum_3_device_0_3_panic.txt'.

Interrupt serial console, and

printenv
boot

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Aah, stop,
i understand - i had to
update-initramfs -u

after changing /etc/fstab

- but, nevertheless, if i change in fstab to

/dev/sda3 /

panic again, with the difference, than kernel hints
that there are sda1 sda2 sda2 sda4 partitions there.


Regards, alex

MOI+> printenv
baudrate=115200
bootargs_linux_usb=console=ttyS0,115200 rootdelay=3 loglevel=7 root=/dev/sdb2 rw
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; reset
bootcmd_exec=if run load_uimage; then; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $lobootm $load_uimage_addr - $load_dtb_addr; else bootm $load_uimage_addr; fi; fi; fi
bootcmd_linux_usb=setenv bootargs $bootargs_linux_usb;mw.l f1010100 0020c000; usb reset; ext2load usb 0:2 $load_uimage_addr /boot/uImage;bootm $load_uimage_addr;bootm;reset
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootdelay=10
bootdev=usb
console=ttyS0,115200
device=0:3
devices=usb sata
disks=0 1 2 3
dtb_file=/boot/dts/kirkwood-moi-plus.dtb
ethact=ethernet-controller@72000
ethaddr=00:22:ab:80:05:2d
fdtcontroladdr=1fb54440
gatewayip=10.0.1.138
if_netconsole=ping $serverip
ipaddr=10.0.1.222
load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file
load_dtb_addr=0x1c00000
load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd
load_initrd_addr=0x2100000
load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage
load_uimage_addr=0x800000
mtdparts=orion_nand:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@0x200000(uImage),0x1400000@0x600000(uInitrd),-@0x1400000(ubi)
ntpserverip=156.106.214.48
preboot_nc=setenv nc_ready 0; for pingstat in 1 2 3; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then run start_netconsole; fi
scan_disk==echo running scan_disk ...; scan_done=0; setenv scan_usb "usb reset; sleep 1; usb reset";  setenv scan_sata "sata init";  setenv scan_mmc "mmc rescan"; for dev in $dScan device $dev; run scan_$dev; for disknum in $disks; do if test $scan_done -eq 0; then echo device $dev $disknum:3; if load $dev $disknum:3 $load_uimage_addr /boot/uImage 1; $dev $disknum; setenv device $disknum:3; setenv bootdev $dev; fi; fi; done; fi; done
serverip=10.0.1.211
set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin serial,nc; setenv stdout serial,nc; setenv stderr serial,nc; version;
stderr=serial
stdin=serial
stdout=serial
uenv_addr=0x810000
uenv_import=echo importing envs ...; env import -t $uenv_addr $filesize
uenv_init_devices=echo Initializing devices...; setenv init_usb "usb reset; sleep 1; usb reset"; setenv init_sata sata init;  setenv init_mmc mmc rescan; for devtype in $device
uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices; do for disknum in $disks; do if test $uenv_loaded -eq 0; then setenv device_type $devtype; seten; done;
uenv_read=echo Loading envs from $device_type $disk_number...; if load $device_type  $disk_number:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; echo ... envs loaded; 
ver=U-Boot 2024.10-tld-1 (Nov 11 2024 - 14:39:35 -0800)\
TBS2903 MOI Plus DVB to IP Gateway Box

Environment size: 3358/131068 bytes

now, if i have update-initramfs with LABEL=rootfs in fstab, an change it to /dev/sda3 and reboot,

i have it this way in KP

[    5.310634][    T1] md: autorun ...
[    5.314138][    T1] md: ... autorun DONE.
[    5.346174][    T1] /dev/root: Can't open blockdev
[    5.351044][    T1] VFS: Cannot open root device "" or unknown-block(0,0): error -6
[    5.385676][    T1] Please append a correct "root=" boot option; here are the available partitions:
[    5.395654][    T8] usb 1-1: New USB device found, idVendor=05e3, idProduct=0610, bcdDevice=32.98
[    5.404597][    T8] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    5.435637][    T1] 0800       976762584 sda 
[    5.435651][    T1]  driver: sd
[    5.443178][    T1]   0801          256000 sda1 cb6f8465-9ae8-4ead-bf1f-77e526776fbb
[    5.443189][    T1] 
[    5.453189][    T8] usb 1-1: Product: USB2.0 Hub
[    5.476737][    T8] hub 1-1:1.0: USB hub found
[    5.485645][    T8] hub 1-1:1.0: 4 ports detected
[    5.490411][    T1]   0802          512000 sda2 95f67525-f797-488f-a67d-68c04b98806f
[    5.490424][    T1] 
[    5.515782][    T1]   0803        41943040 sda3 169fc700-47f8-4d09-a61c-838e6be82ba4
[    5.515797][    T1] 
[    5.545653][    T1]   0804        31457280 sda4 6d15910d-044d-473f-abb2-232654acbe1b
[    5.545668][    T1] 
[    5.585629][    T1] List of all bdev filesystems:
[    5.590362][    T1]  ext3
[    5.590368][    T1]  ext4
[    5.593013][    T1]  fuseblk
[    5.615621][    T1] 
[    5.620718][    T1] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[    5.629727][    T1] CPU: 0 UID: 0 PID: 1 Comm: swapper Not tainted 6.13.0-kirkwood-tld-1 #1 fdec5bfc1c2f018899bfe0a6ba0472906ef0245b
[    5.641704][    T1] Hardware name: Marvell Kirkwood (Flattened Device Tree)
[    5.648698][    T1] Call trace: 
[    5.648711][    T1]  unwind_backtrace from show_stack+0x10/0x14
[    5.657926][    T1]  show_stack from panic+0xf0/0x340
[    5.663018][    T1]  panic from mount_root_generic+0x1d0/0x2a8
[    5.668896][    T1]  mount_root_generic from prepare_namespace+0x1b8/0x244
[    5.675819][    T1]  prepare_namespace from kernel_init_freeable+0x1bc/0x20c
[    5.682916][    T1]  kernel_init_freeable from kernel_init+0x10/0x138
[    5.689405][    T1]  kernel_init from ret_from_fork+0x14/0x28
[    5.695184][    T1] Exception stack(0xa0819fb0 to 0xa0819ff8)
[    5.700961][    T1] 9fa0:                                     00000000 00000000 00000000 00000000
[    5.709883][    T1] 9fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[    5.718802][    T1] 9fe0: 00000000 00000000 00000000 00000000 00000013 00000000
[    5.726159][    T1] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---

if i NOT change it, leaving to LABEL=rootfs,
i have KP the old way, without listing those partitions,
s. below:

root@debian:/# cat /etc/fstab 
# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
LABEL=rootfs    /               ext3    noatime,errors=remount-ro 0 1
#/dev/sda3    /               ext3    noatime,errors=remount-ro 0 1
tmpfs          /tmp            tmpfs   defaults          0       0
root@debian:/#

now, KP with this fstab( its original state at update-initramfs -u execution)

 VFS: Cannot open root device "" or unknown-block(0,0): error -6
[    5.395655][    T1] Please append a correct "root=" boot option; here are the available partitions:
[    5.404766][    T1] 0800       976762584 sda 
[    5.404777][    T1]  driver: sd
[    5.435666][    T1]   0801          256000 sda1 cb6f8465-9ae8-4ead-bf1f-77e526776fbb
[    5.435680][    T1] 
[    5.465645][    T8] usb 1-1: New USB device found, idVendor=05e3, idProduct=0610, bcdDevice=32.98
[    5.474573][    T8] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    5.482486][    T1]   0802          512000 sda2 95f67525-f797-488f-a67d-68c04b98806f
[    5.482498][    T1] 
[    5.495641][    T8] usb 1-1: Product: USB2.0 Hub
[    5.525853][    T8] hub 1-1:1.0: USB hub found
[    5.530394][    T1]   0803        41943040 sda3 169fc700-47f8-4d09-a61c-838e6be82ba4
[    5.530408][    T1] 
[    5.540459][    T8] hub 1-1:1.0: 4 ports detected
[    5.555637][    T1]   0804        31457280 sda4 6d15910d-044d-473f-abb2-232654acbe1b
[    5.555650][    T1] 
[    5.586102][    T1] List of all bdev filesystems:
[    5.595663][    T1]  ext3
[    5.595673][    T1]  ext4
[    5.615634][    T1]  fuseblk
[    5.618277][    T1] 
[    5.623373][    T1] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[    5.632379][    T1] CPU: 0 UID: 0 PID: 1 Comm: swapper Not tainted 6.13.0-kirkwood-tld-1 #1 fdec5bfc1c2f018899bfe0a6ba0472906ef0245b
[    5.644358][    T1] Hardware name: Marvell Kirkwood (Flattened Device Tree)
[    5.651352][    T1] Call trace: 
[    5.651364][    T1]  unwind_backtrace from show_stack+0x10/0x14
[    5.660579][    T1]  show_stack from panic+0xf0/0x340
[    5.665671][    T1]  panic from mount_root_generic+0x1d0/0x2a8
[    5.671549][    T1]  mount_root_generic from prepare_namespace+0x1b8/0x244
[    5.678472][    T1]  prepare_namespace from kernel_init_freeable+0x1bc/0x20c
[    5.685570][    T1]  kernel_init_freeable from kernel_init+0x10/0x138
[    5.692050][    T1]  kernel_init from ret_from_fork+0x14/0x28
[    5.697829][    T1] Exception stack(0xa0819fb0 to 0xa0819ff8)
[    5.703605][    T1] 9fa0:                                     00000000 00000000 00000000 00000000
[    5.712527][    T1] 9fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[    5.721446][    T1] 9fe0: 00000000 00000000 00000000 00000000 00000013 00000000
[    5.728804][    T1] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---

(no difference)

the same, as
If i chage fstab to /dev/sda3 /
and then update-initramfs -u
and booting with that fstab or
changing it to LABEL=rootfs

Regards, alex



Edited 1 time(s). Last edit at 02/21/2025 05:57AM by ri8.

Alex,

fstab is irrelevant when you have root device in bootargs

set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params

If you have the root device in fstab, it must be

LABEL=rootfs    /               ext3    noatime,errors=remount-ro 0 1

With the envs defined as above, especially these envs must be so:

load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file
load_dtb_addr=0x1c00000
load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd
load_initrd_addr=0x2100000
load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage
load_uimage_addr=0x800000

Go ahead and boot

setenv devices 'sata usb'
setenv bootdev sata
boot

And then post the entire serial console log (don't post excerpts).

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi,

did as you said;
- but the real solution was to delete uImage,
generate a new one - !without dtb attached,
setenv dtb_file to where_dtb_lives, en voilas,
correct booting with boot. - Sorry for misleading you
all the time, i forgot about that NOT attaching dtb in uImage.
I'll post you dmesg

i'm using 100bit switch , so that i can ssh to the box
more conveniently , 1Gb works, i've tested.

still no wifi iface after
modprobe rtl8xuuu.

Regards. alex



Edited 1 time(s). Last edit at 02/22/2025 04:04AM by ri8.

> still no wifi iface after
> modprobe rtl8xuuu.

OK. So we know this Wifi chip is USB based, and the module rtl8xxxu already has support for this chip. But we don't know how it is connected internally.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Alex,

Have you installed firmware-realtek?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi,

having in mind, that in the stock rootfs
there was only 8192se in firmware directory,
i tried to load all 8192* modules from
/lib/modules/6.13.0-kirkwood-tld-1/kernel/drivers/net/wireless/realtek/rtlwifi
, with no results.

alex.

bodhi,

>Have you installed firmware-realtek?

yes, i have


Now, as i don't hear from you anything more,

is it actually, it with this chip issue?

Because, i'd tried to insert a rtl8168 mini-pci
ethernet card, and, as contrary to the x64 bookworm
installation, it doesn't work on this box, either.
likewise, rtl8168 source, installed with apt-get, do not compile.
Can i expect some comments on this?

Regards
Alex



Edited 2 time(s). Last edit at 02/28/2025 02:39AM by ri8.