Show all posts by user
Discuss all things Debian on your device
TC7200U_broadcom - 3 months ago
bodhi, BCM3384 would it make for a type of device, worthy of attention on this forum? it is 4 port eth switch with usb and mini pci-e WIFI card with 2 processors and enough memory and nand; in place of uboot they are using aeolus as bootloader and eCos to initialize the hardware more on the box i 've found : https://github.com/jclehner/linux-technicolor-tc7200 https:/by ri8 - Debian
Re: r8168_kirkwood - 3 months ago
bodhi, i did't know about it, but now, i came a little bit further: root@debian:~# lscpu|grep arm Architecture: armv5tel root@debian:~# so, with a swtich ARCH=armv5tel and CROSS_COMPILE=arch-linux-noneabi- compilation stops whith this log: Consult /var/lib/dkms/r8168/8.051.02/build/make.log for more information. root@debian:/usr/src# less /var/lib/dkmsby ri8 - Debian
Re: r8168_kirkwood - 3 months ago
bodhi, alas, my question should have also this modprobe r8168 (ok) modprobe r8169 (ok) root@debian:/usr/src# dmesg|tail -2 [ 40.193638] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 100 Mb/s, full duplex, flow control disabled [ 456.085811] r8168: loading out-of-tree module taints kernel. after which i installed deb package r8168-dkms, and as it failed to compile, downloaby ri8 - Debian
r8168_kirkwood - 3 months ago
Hi bodhi, i try to make work a rtl8168 pci-e card working on moiplus, yet deb package for in do not get compiled, with output : root@debian:/usr/src# dkms build -m r8168/8.051.02 Sign command: /lib/modules/6.12.6-kirkwood-tld-1/build/scripts/sign-file Binary /lib/modules/6.12.6-kirkwood-tld-1/build/scripts/sign-file not found,ules won't be signed Building module: Cleaning builby ri8 - Debian
moi+_kirkwood_RTL8188EUS - 3 months ago
hi folks i have a running 6.12.6 debian on a TBS moi+ tv streaming box upgrade to 6.13 works too, but i've downgraded to 6.12.6. the original u-boot get lost, so (thanks bodhi!) i'm using latest one from this forum. the box was issued with a 2.6.35.14 linux, supporting on-board RTL8188EUS chip on the stock rootfs the file structure for its driver looks as following: ~ # fby ri8 - Debian
Re: Debian on TBS2921 MOI+ - 4 months ago
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 compiby ri8 - Debian
Re: Debian on TBS2921 MOI+ - 4 months ago
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.by ri8 - Debian
Re: Debian on TBS2921 MOI+ - 4 months ago
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 , 1by ri8 - Debian
Re: Debian on TBS2921 MOI+ - 4 months ago
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_by ri8 - Debian
Re: Debian on TBS2921 MOI+ - 4 months ago
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, alexby ri8 - Debian
Re: Debian on TBS2921 MOI+ - 4 months ago
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 Cby ri8 - Debian
Re: Debian on TBS2921 MOI+ - 4 months ago
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 variablby ri8 - Debian
Re: OpenWrt on TBS MOI+ - 6 months ago
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
Re: OpenWrt on TBS MOI+ - 6 months ago
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
Re: OpenWrt on TBS MOI+ - 6 months ago
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
Re: OpenWrt on TBS MOI+ - 6 months ago
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
Re: OpenWrt on TBS MOI+ - 6 months ago
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
Re: OpenWrt on TBS MOI+ - 6 months ago
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
Re: OpenWrt on TBS MOI+ - 6 months ago
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
Re: OpenWrt on TBS MOI+ - 6 months ago
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
Re: OpenWrt on TBS MOI+ - 6 months ago
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
Re: OpenWrt on TBS MOI+ - 6 months ago
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
OpenWrt on TBS MOI+ - 6 months ago
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
Re: Debian on TBS2921 MOI+ - 6 months ago
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
Re: Debian on TBS2921 MOI+ - 6 months ago
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
Re: Debian on TBS2921 MOI+ - 6 months ago
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
Re: Debian on TBS2921 MOI+ - 6 months ago
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
Re: Debian on TBS2921 MOI+ - 6 months ago
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
Re: Debian on TBS2921 MOI+ - 6 months ago
bodhi, now, i see the light! thank your very match, it's a great having you, Regards, alexby ri8 - Debian
Re: Debian on TBS2921 MOI+ - 7 months ago
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