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
> Using 'strace', I found that the 'fw_printenv' > error message "Configuration file wrong or > corrupted" is misleading. A call to 'perror()' > just after "openat(AT_FDCWD, "/dev/mtd1", > O_RDONLY)" failes would give the far more > informative message "Permission denied". Do you > know who maintainsby bodhi - Debian
> Things have been running since my last post! Not > the quickest but it's enough as a NAS. Thank you > for all the help! Nice! watch the swapping activities when you run OMV. And follow this rule: swap space >= 4xRAM. So on this box, the swap file should be 2GB or more.by bodhi - uBoot
Hi Trond, > What does 'fdt_skip_update' do to U-Boot? Which is > the recommended setting? The recommended setting is fdt_skip_update=yes These old u-boots (on many Synology and Netgear NAS) have this customization. It updates the device tree already loaded at pre-determined location before starting kernel. We don't want u-boot to do anything extra to mess up theby bodhi - Debian
> It still doesn't seem to build kwboot. It builds > kwbimage.o but that is as far as it goes. Try building a board make nsa310s_defconfig make And then check the ./tools/ directory.by bodhi - Debian
> I realize I'm kinda cross-posting about this, Yeah, perhaps you can start a thread about cpufreq-utils and I'll discuss this in that thread. All my Kirkwood boxes run on-demand cpufreq. > AFAICT, it's set to 'ondemand', which should > throttle. Yes.by bodhi - Debian
The speed looks good. But something is not right. Server listening on TCP port 5001 TCP window size: 208 KByte (default) ------------------------------------------------------------ [ 4] local 192.168.178.70 port 5001 connected with 192.168.178.137 port 37054 [ ID] Interval Transfer Bandwidth [ 4] 0.0-10.0 sec 723 MBytes 606 Mbits/sec ---------------------------------by bodhi - uBoot
dhargens, > I've successfully followed directions (for a > change) and gotten it to boot to the SSD. I've > also attached the printenv output. Cool! I'll take a look at the envs to doublecheck. > With a minimal size of 1G for the rootfs, do I > have enough for the future, or should I bump it > some? Seems like 200M might tight it there's a >by bodhi - Debian
> i mean i know how to create and use shares from > omv but i dont know how to link 2 linux boxes > together to make your test from your link > -> > Network performance - SAMBA - NFS > (various protocols) > Pogo Pro V3 Network NFS benchmarks > Kirkwood vs OXNAS network > performance (with flow control) > Kirkwood vs OXNAS network performance (flow > cby bodhi - uBoot
> im realy lost at this point > i cant make the test´s because i dont know how i > mount the share of my other nas and so on When it comes to OMV, I will let others help you. Or you could Google whatever problems you see. To me, looks like it booted OK into OMV QuoteVault-111 login: openmediavault 5.6.26-1 (Usul) Vault-111 ttyS0 Copyright (C) 2009-2022 by Volker Theile. Aby bodhi - uBoot
whitepawn, Your best bet would be starting with Toradex u-boot and kernel. > I searched web about what people do with this SOC > and linux before and found out that toradex (some > kind of SBC manufacturer i think) made an u-boot > bootloader, toolchain and rootfs and shared source > codes and binary files and instructions for PXA320 > in here. > https://files.torby bodhi - Debian
CyberPK, I've re-uploaded linux-5.3.5-mvebu-tld-1 tarball. See Old kernel and rootfs releases. QuoteUpdated 12 Oct 2019: Kernel linux-5.3.5-mvebu-tld-1 package has been uploaded. ...... Download at Dropbox linux-5.3.5-mvebu-tld-1-bodhi.tar.bz2 (This tarball was re-uploaded on 01 Mar 2024)by bodhi - Debian
Hi Trond, > I have successfully updated my 2nd RN102 to Linux > version 6.7.5. I noticed that the size of > 'uInitrd' differs significantly between the two > boxes. Check the modules load option on both boxes: cat /etc/initramfs-tools/initramfs.conf | grep MODULES If MODULES=dep then this rootfs started from Debian-6.6.2-mvebu-tld-1-rootfs-bodhi.tar.bz2. Thatby bodhi - Debian