> > But the best out there does not mean it's > > good enough. DSM usually runs an old kernel, > and > > so for internet facing server it's not worth > > keeping because it will be insecure at some > point > > after. > > This is not true, if you check the links of my > first post, Synology released this year (2024) a > new DSM vby bodhi - Debian
barroshelder, > What I would like to do is install DSM on NAND > (overwriting the old ZyXEL OS from NAS), like it > was done on the Western Digital NAS (see link on > my first post) I see. >. On the WD instructions, the user > must flash a BIN file (I suppose it is a new > bootloader that will make the WD behave like a > Synology NAS: > https://wd.hides.by bodhi - Debian
barroshelder, > Thanks for the link, do I need Debian running > before installing DSM software from Synology? The link above describes how to install new u-boot and Debian. And skip DSM altogether. And this will not allow to boot back to DSM. ==== If you still want to use DSM and also run Debian then you need to keep stock U-Boot. And install Debian on a USB drive. And thatby bodhi - Debian
Peter, > I dont remember, if there was an option during > uboot install to customize the MAC, but I skipped > it for sure. The device could not tell its MAC > when it arrived to me. > Warning: eth_rtl8169 MAC addresses don't match: > Address in ROM is 00:00:00:00:00:30 > Address in environment is 52:3b:20:9c:11:51 That's OK. The MACby bodhi - Debian
> > NSA310> pci enum > pcie0.0: Link up > > > > > NSA310> dm tree > Class Index Probed Driver > Name > ----------------------------------------------------------- > root 0 [ + ] root_driver > root_driver > simple_bus 0 [ + ] simple_bus > |-- mbus@f1000000 > miscby bodhi - Debian
spiderdijon, > Image has invalid data checksum > uboot.rn2120.rescue.img: Invalid image. Strange, I would expect to see this with a much older kwboot. I'll double check. In the meantime, please kwboot with the ds4141 u-boot that I uploaded before. As long as it starts running, then we're almost done.by bodhi - Debian
barroshelder, NSA325v2 is fully supported here. Basic steps to install Debian and new u-boot (or stock u-boot) on a Kirkwood box: https://forum.doozan.com/read.php?2,136462 Read it over and post question if you are not sure.by bodhi - Debian
scraamble, The persistent MAC address problem is common to most of these NAS. Most of the Marvell Armada SoC boxes, regardless from which vendor, use the same u-boot code base from Marvell. I have a similar work around in my released rootfs. Quotehttps://forum.doozan.com/read.php?2,32146 Note 6. Persistent MAC address (Optional)by bodhi - Debian
1000001101000 Wrote: ------------------------------------------------------- > I spent some time looking at the clock speed of > some armada-370 devices a while back. It appeared > in the datasheet that the relevant values had to > be set right when the CPU came up either by pull > up/down resistors on certain pins or via the > bootrom. I got the impression this all happeby bodhi - Debian
spiderdijon , bodhi Wrote: ------------------------------------------------------- > Netgear RN2120 Rescue u-boot > > This u-boot image uboot.rn2120.rescue.img can be > used in kwboot the box. As spiderdijon has found > in > the > above post, the power button must be pushed > and hold at the start of kwboot to make it > successful. > > Warning: thby bodhi - Debian
Hi Peter, Here is the new NSA310 u-boot (attached to this post). uboot.2023.04-tld-1.nsa310.kwb md5: cf4a7959fd2d7e5f8ec72b95ce5702f8 sha256: 707e43e6b6284c7484668a9eb2c8d9e6516e07279117e6cd59500190b8cf4ba2 Run kwboot with it, interrupt the u-boot countdown, and dm tree ping <the router IP address> if the ping is successful dm tree if the ping is not successful pciby bodhi - Debian
Netgear RN2120 Rescue u-boot The Synology DS414 u-boot can be used as a rescue u-boot. Please see this thread to download uboot.2024.04-rc3-tld-1.ds414.kwb: https://forum.doozan.com/read.php?2,136786,136855#msg-136855by bodhi - Debian
spiderdijon, > Ah! Success on the kwboot. I found another thread > : https://forum.doozan.com/read.php?3,95249 and it > seems the power button needs to be pressed and > held down during the first stage (bootloader?) > upload. I was able to successfully boot using > mtd0.rn2120 backup file. Interestingly it worked > fine without the -a flag. I also managed to build &by bodhi - Debian
Hi Mark, > Hi All! I am thinking it may be time to put a > newer kernel on my old Seagate Business Storage > NAS but I've pretty much forgotten all I learned > about it the first time! So have I :) In the past, I found some info about this Cavium SoC problem, so I'm no longer interested in it. > Is this box's meager 512 MB of RAM enough to > reliablyby bodhi - Debian
Thanks Peter! That's the driver name I am looking for [ 25.199172] r8169 0000:01:00.0: vgaarb: pci_notify [ 25.199366] r8169 0000:01:00.0: assign IRQ: got 36 [ 25.199478] pci 0000:00:01.0: enabling bus mastering [ 25.199503] r8169 0000:01:00.0: enabling device (0140 -> 0143) [ 25.298043] r8169 0000:01:00.0: enabling Mem-Wr-Inval [ 25.314896] orion_wdt: Initial timby bodhi - Debian
How to create a u-boot boot script on USB rootfs Often time, when booting with stock u-boot, or during testing, we'd want to have a way to excute several commands at the prompt. The script can be run at the u-boot prompt interactively, or saved to an existing env so that it always run during boot (be extra careful with saving envs, some stock u-boot will corrupt the envs when you do that)by bodhi - Debian
scraamble, > With the system fully booted, I can do > 'fw_printenv' but 'fw_setenv' does not work even > after trying 'flash_unlock /dev/mtd1' and > 'flash_unlock /dev/mtd2'. It might be because of > old uboot or broken setenv command. I intend to > use the box to build new versions later when I get > time. There are 2 reasoby bodhi - Debian
> is it possible that i somehow messed up my env´s > to a point that result in this ? The envs don't have anything that could cause a slow down. > because it should be possible to alter thise > setting´s with ethtool you say´s ? ethtool is a Ethernet tool. One thing I have not asked you to do is after running the test, you also want to post the kernel log hereby bodhi - uBoot
Your rootfs is quite old. It's Debian buster (10.x). I guess because you want to run OMV on that. But I have no idea how to help you further. I don't have anybox running Debian buster anymore. I usually keep 1 version older on at least one or two boxes, and that's bullsyes (11.x) . Create a new rootfs on another USB drive using the bookwork rootfs Debian-6.5.7-kirkwood-tld-1-by bodhi - uBoot
OK , so you can see how to peel an onion! We've separated the test so it is very clear that when the NSA320 is a client, all is well with 647 Mbits/sec transfer rate. But when it is a server, the speed is real bad. Based on the output of ethtool, root@Vault-111:~# ethtool -k eth0 | grep tcp-segment tcp-segmentation-offload: off tx-tcp-segmentation: off You need to tby bodhi - uBoot
> Hope its ok :-) Ok! It looks good. Before we do the next step tuning it with ethtool, do the reverse test. On the NSA320 ( 192.168.178.137) iperf -s On the Debian VM (192.168.178.140) iperf -c 192.168.178.137by bodhi - uBoot
Peter, Please post output of dmesgby bodhi - Debian
On the NSA320 ifconfig -a ethtool eth0 ethtool -k eth0 | grep tcp-segment And then, On the Debian VM (192.168.178.140) iperf -s And then, On the NSA320 ( 192.168.178.137) iperf -c 192.168.178.140by bodhi - uBoot
Since we can't kwboot this box yet, I will write the instruction to create and run a boot script. This will save time executing these setenvs commands. I'm sure by now it has become too tedious to mannual copy/paste these commands to the prompt :)by bodhi - Debian
Peter, > I could give it a try, if you make a version. I am > guessing I would only need to just kwboot is over > UART, and see if the network interface is > recognized? Yes, that's the idea. Hopefully it won't be too time consuming. Basically, whenever I build a new version, you then try kwboot and ping the router, and then post the log.by bodhi - Debian
> 1. That the baud rate does not change when setting > the -B option. It always stays at 115200 It is OK. The baudrate is whatever the Marvell BootROM uses, and it is 115200. > 2. The transfer appears to be going fine. Lots of > ACKs from the RN2120 for the first ~100 blocks > then the RN2120 pulls its TX pin low mid byte (and > mid block) and doesn't respond aftby bodhi - Debian
spiderdijon, > Looks good! cpuinfo reports two processors now. Nice! > However what ever is causing > > > pci 0000:00:01.0: not ready after 65535ms; giving > up > > > Is still present. I'm not sure what's going on with this yet. Usually the PCIe bus in these NAS are used for the 2nd and 3rd SATA. Have you tried booting with any SATA dby bodhi - Debian
I can see this problem a bit better now. This might be the issue with cpuidle is broken for this SoC during early booting. But unfortunately we don't have coherency fabric defined in the MMP3 DTS (so we can mark cpuidle as broken).by bodhi - Debian
Hi Trond, 6.7.5-mvebu-370xp-tld-3 > So the rn102's system clock lagged 25 seconds in 5 > minutes. That's 5 seconds per minute. 6.7.5-mvebu-370xp-tld-2 > It used to be lagging 6 to 7 seconds > per minute. Now it's lagging just above 5 seconds > per minute. So it proved that the kernel configs for I2S and SPIF can remain, we just need to remove theby bodhi - Debian