root@debian:~# ifconfig -a eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.178.136 netmask 255.255.255.0 broadcast 192.168.178.255 inet6 2a02:2454:9b9b:1600:ca6c:87ff:fe9b:2f78 prefixlen 64 scopeid 0x0<global> inet6 fe80::ca6c:87ff:fe9b:2f78 prefixlen 64 scopeid 0x20<link> ether c8:6c:87:9b:2f:78 txqueuelen 10by bodhi - uBoot
> the thing is the nsa320 is the only device in my > complete network that is acting like that > like (low downsream high upstream) > > -Th3l0lb0y > > edit: side question ; is it possible that i > messed up the Mac adress in the Env in a way that > can cause something like that ? No, the MAC address is not relevant. The IP address is. Also some bridge coby bodhi - uBoot
Are both NSA320 and Debian VM boxes plugged into the same switch or router?by bodhi - uBoot
TSO was OK now Repeat this test NSA320 iperf -s ServerVM iperf -c and then, On the NSA320 dmesg | tail -50 On the Debian VM dmesg | tail -50by bodhi - uBoot
Hi Peter, Log in to Debian and ethtool enp1s0 lspci -vvby bodhi - Debian
Loos like it did not take. Try again, ethtool -K eth0 tso on sg on ethtool -k eth0 | grep tcp-segment If TSO is still off, try again ethtool -K eth0 tso on ethtool -k eth0 | grep tcp-segmentby bodhi - uBoot
Hi barroshelder, Sounds like the DSM built for the 2 boxes you mention will run on this NSA325, but likely with limitation. Things like Ethernet and SATA might or might not work. Each manufacturer has a differrent board design so some low level setup for these devices are likely different (even they use the same SoC and LAN chip). I'm not interested in supporting any stock software herby bodhi - Debian
On the NSA320, while in Debian, do ethtool -K eth0 tso on sg on And run the tests again.by bodhi - uBoot
ahuovinen, > So gpt and usb capabilities should be there. Made > usb rootfs stick according to directions > from https://forum.doozan.com/read.php?2,12096 01 > nov 2023. When you are setting up the first time, use MBR partition and Ext3 file system. Don't use GPT, and don't use Ext4. After booting into Debian in USB, you can try GPT if u-boot supports it (lookby bodhi - Debian
spiderdijon, > Do these envs need to be saved permanently at this > point? Not much point adding them to the script on > the USB drive as the USB drive is already present! > :) Yes! now that you can run kwboot, we should go a head and make the envs permanent. And also see that it works Debian, too. Assuming you've already done the dual boot set up above and tested it.by bodhi - Debian
metodi, > I checked the serial port pins. No odd colors, no > sign of burning, no unstable pins. The only odd > thing I saw were multiple "wet spots" (I don't > know how are these called in English?!) on the > back/downside of the whole board. It is like at > some moment there were salty water drops that had > dried out, but left like tiny white spots?by bodhi - uBoot
Dual boot Debian and stock OS on Netgear RN2120 Currently the RN2120 can be booted into Debian with the following envs: setenv bootdev usb setenv device 0:1 setenv load_image_addr 0x02000000 setenv load_initrd_addr 0x3000000 setenv load_image 'echo loading uImage ...; ext2load $bootdev $device $load_image_addr /boot/uImage' setenv load_initrd 'echo loading uInitrd ...; eby bodhi - Debian
metodi, > 1 - is it possible the communication settings to > be different, like different baud rate, or data > bits, or stop bits, etc.? I searched more > information on the internet and I found a couple > of articles, stating that those 00s I am getting > are a sign for bad communication between devices. > I tried different settings, slowing down baud, > changinby bodhi - uBoot
spiderdijon, > It appears to boot the uboot but is missing > loading env variables from SPI flash. With ID > bytes of 0xFF 0xFF 0xFF it's likely it's actually > not accessing anything at all. Is this because > there is no SPI NOR Flash on this device? > It looks > like it uses NAND flash instead? Correct, there is no SPI flash. This box uses NAND flash.by bodhi - Debian
Next step: Create a new rootfs on another USB drive using the bookwork rootfs Debian-6.5.7-kirkwood-tld-1-rootfs-bodhi.tar.bz2. Don't install any extra software such as OMV, don't run systemd.... Basically a pristine Debian-6.5.7-kirkwood-tld-1 rootfs. Boot with it and the run the iperf tests.by bodhi - uBoot
Hi sudos, > For transfers over SFTP or SMB which is what I'm > doing, transfers are slow and have a lot of CPU > overhead. This is because for SFTP, it's file > transfer over SSH. > All SSH traffic is encrypted by > default (and should never not be in my opinion.) Mine too! > Was the system using NFS v2 or v3? Yes, it was NFS V3. > Thoseby bodhi - Debian
Not sure if the DS213 Ethernet and SATA are configured the same way as the NSA325, though.by bodhi - Debian
> > 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. > OK. I can see why it did not work. > 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
> > 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