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
How about picocom like you did above? sudo picocom -c --b 115200 --f n --p n --d 8 /dev/ttyUSB0by bodhi - uBoot
Backup NAND mtds and also use mtd0 for kwboot Change to a directory where these backup files will be save. nanddump --noecc --omitoob -f mtd0.rn2120 /dev/mtd0 nanddump --noecc --omitoob -f mtd1.rn2120 /dev/mtd1 nanddump --noecc --omitoob -f mtd2.rn2120 /dev/mtd2 nanddump --noecc --omitoob -f mtd3.rn2120 /dev/mtd3 nanddump --noecc --omitoob -f mtd4.rn2120 /dev/mtd4 And then compress thby bodhi - Debian
spiderdijon, Let's be productive and do other tasks first. Here is the new SMP kernel. Please install and verify that it works for 2 cores. https://forum.doozan.com/read.php?2,92514,136942#msg-136942by bodhi - Debian
Here is kernel linux-6.7.5-mvebu-370xp-tld-3. The objective is to: - Configured as SMP kernel, to add support for Netgear RN2120 (Armada XP 2-cores) - I2S and SPDIF still configured in the kernel (these were removed in linux-6.7.5-mvebu-370xp-tld-2). - The DTB for Netgear RN120 has Audio Controller nodes removed. This is for testing the time lag issue in RN102 (see if it will help or hurt).by bodhi - Debian
Apparently the Windows side is the problem. Not sure what was. I would suggest running the server side on another Linux box. Or on a Linux VM. Use VMWare Player or Virtual Box, you can run Ubuntu or Mint on the VM for free. It is quite convenient to run Linux VM so you can learn more about Linux and do time consuming task such as backup/restore a USB rootfs,... (speed up anything that wouldby bodhi - uBoot
> Would the swap space be the same as the swap file > mentioned here? > https://forum.doozan.com/read.php?2,133753 Yes it is.by bodhi - uBoot
metodi, Don't run kwboot. Run only picocom only.by bodhi - uBoot
dhargens, It must be that something is running in the system, and cpufrequtils decided to raise it to 800 Mhz. I've recalled it works on this Pogo V4. Try this to prove that there is no problem particular to the Pogo V4. cpufreq-set -g powersave And then cpufreq-info That should bring it down to 200 MHz.by bodhi - Debian
> Any idea on what can affect the performances on > kernel 6.7.y even if patched to remove the new > flag CRYPTO_ALG_ALLOCATES_MEMORY? Perhaps it might be that the whole patch must be reversed, not just the part about CRYPTO_ALG_ALLOCATES_MEMORY.by bodhi - Debian
Metodi, > A couple of days ago my ZyXEL NSA325 v1 died. Only > the POWER and the HDD2 LEDs are lit and the box > gets in the reboot loop - restarting every 30-40 > sec. This is not exactly "died". You must be running stock FW? and that's the behaviour of the watchdog. If you are stuck and can not boot into Linux for about 30 seconds, this box's watchdog wby bodhi - uBoot
spiderdijon, Use this static kwboot: kwboot_static_2024.04-rc3by bodhi - Debian
Hi Trond, > Perhpas "dep" did not work before. I'll try a test > to see if can recreate your observation. I've verified that "MODULES=dep" works in Debian 11.by bodhi - Debian
Hi Trond, > most likely because 'mkimage' on the 2nd box do > not support 'MODULES=dep': > So it seems 'mkimage' got a face lift in Debian > Bookworm? Probably not that reason. Because 'MODULES=dep" was in Debian 11.x This is one of my home media NAS boxes, still running Debian 11. root@HomeMedia1:~# cat /etc/debian_version 1by bodhi - Debian