i5Js, Since you are using patched u-boot and can use USB drive, you don't need to boot that old kernel. The rootfs Debian-5.13.8-mvebu-tld-1-rootfs-bodhi.tar.bz2 should work. When booting Debian-5.13.8-mvebu-tld-1-rootfs-bodhi.tar.bz2, try these addresses: QuoteuImage 0x800000 uInitrd 0x2100000 and also setenv initrd_high 0xffffffffby bodhi - Debian
zebe, > Id ask you kindly for some additional hint - I > tried to move installation from my primary USB on > HDD: boot, rootfs, swap, Data partitions, but does > not seem to work afterwards - only orange flashing > led.. You might have changed the u-boot envs incorrectly. Or the HDD rootfs was not prepared properly. > Moreover-even when starting from USB again I canby bodhi - Debian
Radm, I think for x86_64 it is generally not needed ot have device tree. You could just boot the kernel. But I'm not familiar with the x86 kernel, so will let others chime in.by bodhi - Debian
Hi Martin, > SATA 1 regulator works correctly. Cool! > For SATA 2 even when all are configured the disk > does not spin up (previously I only tested with > one disk). That's a bumer! u-boot GPL source is quite clear about the both SATA GPIO numbers. I'll look at the DTS to see if there is any typo. > > I will have to do further tests, but it likelyby bodhi - Debian
> Would you advice: should ssh/telnet console or > other means be used to communicate with NSA325 > after disconnecting serial link? SSH. > Is there any WEB interface to be installed on > debian NAS325 ? Webmin is one of the oldest Linux simple web interfaces. Aslo see the Wiki thread: QuoteDebian Desktop XFCE desktop Pogoplug Debian LXDE / XFCE Desktop on Hby bodhi - Debian
lonestar, So I've confirmed: in the GPL, the GPIOs 42, 44 are for SATA 1 and 2. Try this attached pacth (removed the other 2 SATA ports and their associated nodes).by bodhi - Debian
mshak, QuoteStora booted to debian with usb stick and to openwrt without a stick I know you have booted into Debian before with OpenWrt u-boot. Perhaps my uboot build has some USB quirks. ========== If you have Sandisk or Kingston brand USB, try them. Or just redo the USB rootfs. Make sure you use single Ext3 partition, and do everything to create the rootfs while being root user (by bodhi - Debian
mshak, 1 bytes read in 753 ms (0 Bytes/s) Found bootable drive on usb 0 loading uImage ... 5435888 bytes read in 1056 ms (4.9 MiB/s) loading uInitrd ... EHCI timed out on TD - token=0xd8d80 EHCI timed out on TD - token=0x80008d80 ... a lot of same "EHCI timed out on TD" It could be a flaky USB drive. Which brand, model, capacity is this drive? Try these 2 envs to insby bodhi - Debian
lonestar, QuoteInteresting fact: the drive is correctly powered up after ata2 link down message. This is the same behavior as on stock image. So at least this part seems to be ok. So did any of the 2 SATA drives power up? If none of the SATA drives is up, at this point, we need to find out if 2 out of these 4 regulators can be used. IOW, is the GPIO in each one is correct? or the ds214 usby bodhi - Debian
mshak, Looks almost done. But you did not complete all the steps in flashing the env image. Especially this part is important: Quotef. Adjust the DTB name to boot with a rootfs that has FDT kernel 3.17+ (this is the normal case): Find your box DTB file in the rootfs /boot/dts directory and adjust the env to it. For example, if the box is the Dockstar fw_setenv dtb_file '/boot/dtsby bodhi - Debian
zebe, > Btw dont know why but my system boots with > ....pogo_e02.dts ?! It boots because both boxes are in the same Kirkwood SoC family. > Ps. ONly debian-security.org repo gives me error > and gets disabled. Whats the right repo for now? The release notes: Quotehttps://forum.doozan.com/read.php?2,12096 ==============================================================by bodhi - Debian
Hi Martin, > On linux the following lines are in the dmesg > output: > > Quote > [ 3.286187][ T1] scsi host0: sata_mv > [ 3.291223][ T1] scsi host1: sata_mv > [ 3.295841][ T1] ata1: SATA max UDMA/133 irq > 37 > [ 3.300665][ T1] ata2: SATA max UDMA/133 irq > 37 > [ 3.636269][ T674] ata1: SATA link down > (SStatus 0 SContby bodhi - Debian
zebe, Your envs are wrong so that's why you have no network. Power up, interrupt serial console, and setenv dtb_file '/boot/dts/kirkwood-nsa325.dtb' and then get a listing of the envs before booting. printenv bootby bodhi - Debian
Here is the revised patch. Of course the other old definition for 4 SATAs need to be removed (or 2 regulators should be kept if they are correct). But here is the internal 2-port-sata node should be added. diff -Naur armada-xp-synology-ds214.dts.orig armada-xp-synology-ds214.dts --- armada-xp-synology-ds214.dts.orig 2022-11-03 08:00:35.000000000 -0700 +++ armada-xp-synology-ds214.dts 2022-by bodhi - Debian
schnee, > I am trying to utilize the onboard FLASh on the > Pogoplug V3 board to load the kernel from it. I > tried it with the latest kernel (5.4.224) and also > with previous ones, but it seems that JFFS2 file > system support it missing. If you are loading the kernel from flash, the rootfs has nothing to do with it. It's u-boot that loads the uImage and/or uInitrdby bodhi - Debian
Sorry, I accidentally modified your post instead of replying to it :)by bodhi - Debian
Martin, > An interesting detail, that I have found so far: > In file mvBoardEnvLib.c: > Quote > ... > #elif defined(SYNO_HW_VERSION_DS414) || > defined(SYNO_HW_VERSION_DS414r1) > gBoardId = SYNO_AXP_4BAY_2BAY; > #elif defined(SYNO_HW_VERSION_DS214) > gBoardId = SYNO_AXP_2BAY; > ... > > MV_BOOL mvBoardIsPortInSgmii(MV_U32 ethPortNum) > { &by bodhi - Debian
Martin, QuoteI guess this means that the definitions in armada-xp-mv78230.dtsi might also not be sufficient? I don't think that's the case. The ds414 has been working for a long time. This box is a 2-bay version for the ds414, so I'd expect that you only need 2 internal SATA ports, and the PCIe bus is just used for USB 3.0. I'm not sure, but my guess is this box does nby bodhi - Debian
lonestar, Try this DTS patch. root@tldDebian:/usr/src/linux-6.0.7-mvebu/arch/arm/boot/dts# diff -Naur armada-xp-synology-ds214.dts.orig armada-xp-synology-ds214.dts --- armada-xp-synology-ds214.dts.orig 2022-11-03 08:00:35.000000000 -0700 +++ armada-xp-synology-ds214.dts 2022-11-19 13:18:04.974981611 -0800 @@ -25,8 +25,8 @@ #include "armada-xp-mv78230.dtsi" / { - modby bodhi - Debian
mshak, If you have not flashed my u-boot, try this. Boot into Debian on USB, and echo "/dev/mtd0 0xe0000 0x20000 0x20000" > /etc/fw_env.config fw_printenvby bodhi - Debian
It looks like the patch is not complete. I wonder where they build this? staging tree? There are files missing in the pull reqest.by bodhi - Debian
zebe, Power up, interrupt serial console, printenv ping <router IP> and then boot boot And post the entire serial console log here.by bodhi - Debian
mshak, OK the bad news: the envs are not in mtd0 or mtd1. So what we see here could be just the internal envs. And u-boot can be configured that it will use only the internal envs. Netgear Stora> printenv arcNumber=2743 baudrate=115200 bootcmd=setenv bootargs ${console} ${mtdparts} ${bootargs_root}; ubi part ubi; ubifsmount ubi:rootfs; ubi read 0x800000 kernel; bootm 0x800000 boby bodhi - Debian
mshak, That's the location of the internal envs, not ones in flash. Please do the same for nanddump --noecc --omitoob -f mtd1.owrt.uboot.2020.04.stora /dev/mtd1by bodhi - Debian
lonestar, > Note: DO NOT EVER CALL SAVEENV ON THE STOCK U-BOOT > LOADER. > It will overwrite your kernel in the SPI flash and > for some reason the stock u-boot will then no > longer boot. If this happened to you anyways: > overwrite the u-boot env checksum in flash at > address 1.000.000 (decimal). Then at least stock > u-boot itself will load again. You can thby bodhi - Debian
> A little off-top: further described procedure > tells to upgrade/amend some files, that requires > internet link of course. > Is -at that stage-any other option to make it > networked except eth cabling to some router /wifi > adapter on Zyxel's usb maybe?/ Before running apt-get, apt-get upgrade, either connect ethernet cable, or USB wifi adapter to get network ruby bodhi - Debian
zebe, > Thanks. You mean just one Ext3/labelled 'rootfs'/ > partition on USB, w/copied content onto it? You need to follow the instruction how to create the rootfs. And don't substitute any part with any thing that you think it's equivalent. For example, you must be root, one Ext3 partition, untar to extract,.... The instruction was written in a way that avoids aby bodhi - Debian
zebe, > Ive been just in process of 'debianization' on my > Zyxel NSA 325, flashed uboot w/kwboot - as per > Bodhi's instructions BUT > I have not prepared new kernel/boot files while on > default uboot... Create a new rootfs on USB using Debian-5.13.6-kirkwood-tld-1-rootfs-bodhi.tar.bz2 from the release thread: https://forum.doozan.com/read.php?2,12096by bodhi - Debian
brmiller, No, the Goflex Home and Pogo Mobile boxes are different from each other. Most likely the factory restore won't work the same way. Besides, that link I have was old and now broken. To run serial console on this box, you don't even need to solder the header. This is what I did because I was soldering-challenged: - Prepare the serial console GND,TXD,RXD wires. Attach theby bodhi - uBoot