Alex, > it should be possible to bring > the box up with a stock uImage. Yes, in theory only. > but boptomg stops after > kernel being loaded That's normal. In order to boot stock kernel, most of the time you'll need to run stock u-boot. So kwboot the back up mtd0, and if it is successul, printenv and then post the serial console log.by bodhi - Debian
cmp18, > thank you so much! your dts/dtb are working fine > for my device (network and usb are working, iperf > ~700 Mbits/sec), but the device is working only > with kernel 6.6.3-kirkwood-tld-1 and older. With > newer kernels - the trouble that I wrote about > above: the device boot once out of ten times (and > works fine). in the other nine times - there is a >by bodhi - Debian
Ivan, > BTW, I am getting a new device, that I might need > your help with: DLink ShareCenter D-320 2 Bay > NAS. > It has a Marvell Kirkwood 88F6702 @ 1 > GHz according to > https://www.smallnetbuilder.com/nas/nas-reviews/d-link-dns-320l-sharecenter-2-bay-cloud-storage-2000-reviewed/ > > I will start a new thread for it once I obtain it. Perhaps continue withby bodhi - uBoot
Ivan, Quote> 12TB works just fine when rootfs is booted from > the USB, which makes me think that uboot driver is > not working well. Yes. It is indeed broken somewhere in mainline u-boot. So your plan to use USB rootfs is a good plan. I don't know when I will be able to revisit this and trouble shoot. I will try to debug using my 4TB HDD on another Kirkwood box.by bodhi - uBoot
Ivan, That's actually a very good test. The ID words have nothing DS211> sata init S/N: Firmware version: Product model number: Capablity: 0 sectors id[49]: capabilities = 0x0000 id[53]: field valid = 0x0000 id[63]: mwdma = 0x0000 id[64]: pio = 0x0000 id[75]: queue depth = 0x0000 id[76]: sata capablity = 0x0000 id[78]: sata features supported = 0x0000 id[79]: sataby bodhi - uBoot
Ivan, I've just posted the Dec 02 version above. > My plan was to use 2 x 12TB HDDs, and have the > rootfs installed on both, in case one fails it > will be still able to boot on the second one (I > assume this would work, wanted to give it a try > anyhow). I used 1TB HDD just for testing > purposes. > Since I can't boot from HDDs, I'll just use Uby bodhi - uBoot
Ivan, Here is the Dec 02 build. uboot.2024.10-tld-1.ds211.bodhi.tar.dec_02 sha256: 3d39a2be0fad1fc6a0aa4b709072819c69a67a5e30ed73a66da7810fd3d6199b 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-tld-1.ds211.environment The ATA ID wordsby bodhi - uBoot
Alex, > So, only question 1. remaining I don't see question 1. Can you repeat it?by bodhi - Debian
phivo, Please try the latest kernel: Latest released kernel: linux-6.11.6-mvebu-370xp-tld-1-bodhi.tar.bz2 (13 Nov 2024)by bodhi - Debian
Ivan > The power supply is original with 12V 6A. > I did run the old Synology OS with two 12TB HDD > drives, and it worked just fine, with OS installed > on the HHDs. > This makes me doubt that there is an issue with > the power, unless there are some boot time power > fluctuations. Power has 2 parts. Hardware and software. So the fact that you can run stock FW anby bodhi - uBoot
> Use hexedit to load the file and then search for > mtdparts. bootcmd=ubi part ubi; ubi read 0x800000 kernel; bootm 0x800000 bootdelay=3 baudrate=115200 console=console=ttyS0,115200 mtdparts=mtdparts=orion_nand:0x0c0000(uboot),0x80000(uboot_env),0x7ec0000(ubi)by bodhi - Debian
Alex, > is it poss. to get a mtd layout from? Use hexedit to load the file and then search for mtdparts.by bodhi - Debian
Alex, > 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-networkby bodhi - Debian
Ivan, I'm convinced that there is a problem in u-boot regarding the large disk. It has nothing to do with SATA Identify. I've dumped the Identity words on my 4TB HDD and it looks fine. It seems flaky. Like there is not enough power. Large HDDs need 12V. For now, you should flash the Nov 22 version, which is OK with the normal HDD (i.e. 1TB) rootfs. And use it with the 12TB inby bodhi - uBoot
Ivan, Try a gain but this time insert a wait period. setenv devices sata dm tree sata init dm tree sleep 1 # if 1 second does not work, try a longer sleep up to 10 seconds in the next tests sata info sata part ext2ls sata 0:1 / ext2ls sata 0:1 /boot Each test should be from a cold start. The reason is we want to power it up in Standby mode. For the large capacity Seagateby bodhi - uBoot
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