Here is the DTB, with its DTS also attached.by bodhi - Debian
MM, > Hi, try DTB from this topic > https://forum.doozan.com/read.php?2,133204,133272,quote=1 > > for two or more usb sticks hub with external power > requerd Thanks! I forgot all about it. Probably because @gt suddenly stop posting. So that DTB might work only partially.by bodhi - Debian
cmp18, Power up, interrupt serial console and bdinfo mii infoby bodhi - Debian
QuoteI tried to extract dtb/dts from my running system/kernel with various utilities (binwalk, extract-dtb, etc) + I tried extract dts/dtb from working system (from /sys, /proc, etc) - but I couldn't find dts/dtb anywhere (maybe my kernel uses an older mechanism than dts/dtb?) Old kernels don't have FDT. So you have to use an existing DTB for another box to boot it first. And then I cby bodhi - Debian
cmp18, Here for how to boot this box with stock u-boot: https://forum.doozan.com/read.php?2,102054,105374#msg-105374 The DTB is needed to be appended to uImage, though. Let me take sometime to read that old thread again.by bodhi - Debian
Ivan, How did you format this 12TB drive? did you format it as ext3 or ext4? Could you - Use command line parted to wipe the disk - Create a brand new partition - Format it as ext3. - Populate it with the rootfs (or some files in the root folder and /boot). The purpose is to see if you can see the files listed. And boot with this drive inserted in the upper bay. setenv deviceby bodhi - uBoot
Hi Ivan, > The upper_sata1_12TBHDD.txt test actually looks > good. > > Please try that test again. > > > dm tree > sata init > dm tree > > sata info > sata part > ext2ls sata 0:1 /boot > setenv devices sata > run scan_disk > I meant only the 12TB HDD is plugged in the slot where the 1TB was seen working. That's the upperby bodhi - uBoot
Ivan, The upper_sata1_12TBHDD.txt test actually looks good. Please try that test again. dm tree sata init dm tree sata info sata part ext2ls sata 0:1 /boot setenv devices sata run scan_diskby bodhi - uBoot
Alan, If you don't get reponse from the u-boot ML, try sending again to both the ML and the maintainer (reply to your email and add the maintainer email address to TO: list). Find the email address here. board/mediatek/mt7621/MAINTAINERS You don't need to mention this forum.by bodhi - uBoot
Ivan, Here is the Nov 27 build. uboot.2024.10-tld-1.ds211.bodhi.tar.nov_27 sha256: 0c4a5153e3a6e153fca7e81cfc26b9c945a86f17fe4b3e6884d051328e56412f uboot.2024.10-tld-1.ds211.bodhi.tar.nov_27 This tarball contains 3 files. Ony the uboot.2024.10-tld-1.ds211.kwb is different from previous build. uboot.2024.10-tld-1.ds211.kwb uboot.2024.10-tld-1.ds211.environment.img uboot.2024.10-by bodhi - uBoot
Alex, > so, something like than > over mtd0 > or it is a fdt file , binary , in /sys/firmware That's a good find. I decompiled this FDT # dtc -I dtb -O dts -o fdt.dts fdt and attached the DTS here. It confirmed what we already done for this box regarding Ethernet. As usual, Wifi is not needed in the DTS.by bodhi - Debian
Alex, > 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. Yeah :) sometime you see the specific info how the owner built the entry (see below). > So, i discovered, there is a the > directory in /lib/firmware/RTL8192by bodhi - Debian
Alex, > 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 Nice work! > would it be possible to > boot the board with your dtb and u-boot loader? Not possible. The stock kernel is very old. I think it is 2.6.35 or something like that, so DTby bodhi - Debian
Jungle, > I found the folder /usr/lib/modules contains old > kernel modules and tried to remove them using apt > after finding this: > stackexchange > > But when I rebooted, my external usb drive (not > rootfs flash drive but another) was no longer > recognized. > is there a safe way to clean these up? Don't remove the /usr/lib/modules like that. Soby bodhi - Debian
Ivan, > There are still issues with sata 0 and 12TB HDD. Looks like the upper slot is working with the 1TB drive. So for now, you should put the rootfs in that slot and boot with it. The lower slot is apparently not working at all. The bad news about the 12TB drive is it exhibits the old problem with large Seagate drives in u-boot. [ 649.929053] scsi 1:0:0:0: Direct-Accessby bodhi - uBoot
Ivan, Here is the new Nov 22 build. uboot.2024.10-tld-1.ds211.bodhi.tar sha256: e671953db45bfb2693f877fbb4da09eaa1c963213074aabb7d42b85905356d6a This taball contains 3 files uboot.2024.10-tld-1.ds211.kwb uboot.2024.10-tld-1.ds211.environment uboot.2024.10-tld-1.ds211.environment.img Only the uboot.2024.10-tld-1.ds211.kwb is different from previous version. Please test it thisby bodhi - uBoot
Alan, You mispelled MT7621A? MediaTek is mt7621, not tm7621. I think.by bodhi - uBoot
Alansbor, It does not sound like you're doing anything wrong. This board is actively maintained in U-Boot, so you should send this report to: U-Boot Mailing List <u-boot@lists.denx.de>by bodhi - uBoot
Ivan, > Tried to boot with lower SATA slot, but it wasn't > recognized at all, even after running "bootdev > hunt". > > With upper SATA slot, still doesn't boot with 12GB > HDD. After running "bootdev hunt" and "bootdev > list", it does list the boot device, but fails to > boot. > When you do testing SATA, donby bodhi - uBoot
Alex, Perhaps you need to apt-get update If it does not work, back up your USB rootfs, and upgrade to the latest Debian release. apt-get upgradeby bodhi - Debian
Flo, Looks like you missed step 3 in the rootfs creation. https://forum.doozan.com/read.php?2,32146 Quote3. Create uImage with DTB appended. I am using the Zyxel NAS326 as an example here. Please replace armada-380-zyxel-nas326.dtb below with the appropriate DTB name for your box. cd /media/sdb1/boot cp -a uImage uImage.orig cp -a zImage-6.6.2-mvebu-tld-1 zImage.fdt cat dts/armadby bodhi - Debian
The information is somewhere in the forum, but it's hard to find. Here is 3 different ways to do that. 1. Simplest strings /dev/mtd0 | grep U-Boot\ 2 Output could be like this U-Boot 2022.10-rc2-00031-gd765364759-dirty (Aug 10 2022 - 14:36:13 -0700) 2. Dump the mtd0 to a file and grep it dd if=/dev/mtd0 of=/tmp/mtd0.bin conv=sync && grep -a --null-data U-Boot /tby bodhi - Debian
compiled with dkms 8188eu driver , version 5.13.5 depmod modprobe ok -> no complains lsmod -> listed ip link -> not listed Did you try to bring up all network? ifup -a Is wlan0 in /etc/network/interfaces?by bodhi - Debian
Alex, > 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? Actually u-boot has nothing to do with helping the Ethernet or Wifi network connection in Linux. It only seems that way because the way I was troubleshooting the pby bodhi - Debian
> That patch never got to mainline. I wonder why. > Perhaps it was rejected? I can see why it was not going to be accepted in mainline. It is too invasive and could potetially breaks other MVEBU boards.by bodhi - Debian
New u-boot was uploaded: https://forum.doozan.com/read.php?3,138456,138496#msg-138496by bodhi - Debian
Ivanj, Please test this Nov 20 version for SATAs spinup in u-boot. uboot.2024.10-tld-1.ds211.bodhi.tar sha256: 819af95eb73cfbf67f683d2423c52086cfa1568b4c781619384f4da9e91a8753 This tarball contains 3 files uboot.2024.10-tld-1.ds211.kwb uboot.2024.10-tld-1.ds211.environment uboot.2024.10-tld-1.ds211.environment.img Only the uboot kwb file is different from previous version.by bodhi - uBoot
adrien60, > Someone indicated a patch made by Netgear on the > kernel, about orion-mdio (related to the 1318 phy) > here : > https://forum.doozan.com/read.php?2,92514,136627#msg-136627 > > I don't see something equivalent in the mainline > linux kernel, so I wonder if this is still > relevant. That was from pczerepaniak. That patch never got to mainliby bodhi - Debian
adrien60, > I wonder if Netgear did some patches to the kernel > to keep powering the NIC/PHY in standby. They might have. But that is supposed to be in Linux mainline by now. We need to see a working WOL example from someone runing an Armada 37x/38x based NAS with the 1318 chip. The driver is mvneta. The Kirkwood SoC driver is mv643xx_eth. I have tested this successfully with theby bodhi - Debian
Ivanj, > With the new dtb file both SATA slots are working > and recognize the drives! > > [ 638.325500] ata2: link is slow to respond, > please be patient (ready=0) > [ 642.385518] ata2: SRST failed (errno=-16) > [ 648.365503] ata2: link is slow to respond, > please be patient (ready=0) > [ 649.835513] ata2: SATA link up 3.0 Gbps > (SStatus 123 SConby bodhi - Debian