> And indeed, getting data off the NAS improved > quite a bit, effectively doubled! > TSO OFF > 1073741824 bytes received in 00:32 (31.82 MiB/s) > 1073741824 bytes sent in 00:51 (19.92 MiB/s) > > TSO ON > 1073741824 bytes received in 00:16 (63.26 MiB/s) > 1073741824 bytes sent in 00:51 (20.05 MiB/s) Cool! > I would have never guessed, that with TSO ON,by bodhi - Debian
spiderdijon, > root@debian:~# cat /proc/mtd > dev: size erasesize name > mtd0: 00180000 00020000 "u-boot" > mtd1: 00020000 00020000 "u-boot-env" > mtd2: 00600000 00020000 "uImage" > mtd3: 00400000 00020000 "minirootfs" > mtd4: 07400000 00020000 "ubifs" Looks good. > root@debian:~# fw_printenv Looks gby bodhi - Debian
> Edit: I think I found it: > https://source.denx.de/u-boot/u-boot/ (?) but now > having difficulty in producing a kwboot binary. It > doesn't seem to build it with the "make > tools-only"? > You need to pick a board first, any ARM board is OK. For example, on rPi: make rpi_3_defconfig make tools And thanks for reporting the problem running on rPi.by bodhi - Debian
> Hi out of curryosity if testet an SMB transfer > with an > USB Network adapter and there i get about 10mb/s > witch is about USB2.0 speed > with the same file on the internal adapter i get > about 30-100kb/s > > so its the internal Network adapter with the > problem > is it possible that my env´s are the problem ? > or an linux problem ? Not u-bby bodhi - uBoot
Set up MTD partitions and u-boot envs for Debian Recap. The current setenvs to boot Debian Marvell>> setenv bootdev usb Marvell>> setenv device 0:1 Marvell>> setenv load_image_addr 0x02000000 Marvell>> setenv load_initrd_addr 0x3000000 Marvell>> setenv load_image 'echo loading uImage ...; ext2load $bootdev $device $load_image_addr /boot/uImage'by bodhi - Debian
spiderdijon, I've uploaded the latest kwboot in this post: https://forum.doozan.com/read.php?3,27280,27280#msg-27280by bodhi - Debian
Peter, > "Marvell never designed this SoC to do what we're > doing to it" > That is 100% true, but the genius is not always in > the design, sometimes it is in the application. :) Yes it is :) > > For me the plus is giving these things some more > life, while doing something useful. Totally. > power when not being actively used, installby bodhi - Debian
Hi Trond, > The system clock is still lagging, but a bit less > than before. It used to be lagging 6 to 7 seconds > per minute. Now it's lagging just above 5 seconds > per minute. That's cool! an indicator that perhaps your theory is correct. > > Btw, the title of this thread has a spelling > error: RN120/RN104 should read RN102/RN104. Thanks!by bodhi - Debian
@sudos, I agreed with most of what you said. Except for: > such, transfers requiring encryption (such as > SSH/SFTP) are going to eat at the CPU usage, > moreso if the speed is slow. > I've already come to > terms that the most I'll ever get out file > transfer-wise is going to be 7-8MB/s maximum on > any kirkwood device, That might be true for otherby bodhi - Debian
QuoteI have tried setting the -a flag for amarda XP timings but then it never seems to even start. Do you have any pointers on what to set -q -s -o to if anything? That option -a was tested extensively, so -q -s probably will not be much help. And yes, option -a should be used. QuoteI've read a few threads relating to kwboot. Possibly I might be having a issue because I'm startingby bodhi - Debian
Hi Trond, It seems there was no DTB embedded in uImage. The zImage size is the same as your uImage in the boot log. The uImage size should be a bit larger with the DTB in it. -rwxr-xr-x 1 root root 5099248 Feb 21 15:13 zImage-6.7.5-mvebu-370xp-tld-2 ## Booting kernel from Legacy Image at 02000000 ... Image Name: Linux-6.7.5-mvebu-370xp-tld-2 Created: 2024-02-28 21:by bodhi - Debian
> > 1183.731484][ T7311] __nand_correct_data: > uncorrectable ECC error > [ 1183.753539][ T7311] __nand_correct_data: > uncorrectable ECC error > [ 1183.759599][ T7311] print_req_error: I/O error, > dev mtdblock8, sector 0 flags 0 > [ 1183.783533][ T7311] Buffer I/O error on dev > mtdblock8, logical block 0, async page read > > This problem typicallby bodhi - uBoot
Hi Peter, > End of last year, I tried to revive a NSA310 NAS > by debianizing it. Thanks to bodhi, and the howtos > on this forum, I managed to get it funcionally > working with > "Debian-6.5.7-kirkwood-tld-1-rootfs-bodhi.tar.bz2". Glad to hear another piece of old hardware running the latest Linux kernel! > The only thing that seems a little off, is theby bodhi - Debian
> only thing now is the extremly slow transfer speed > of only 20kb/s on an gigabite connection > is there anything i can do about ? Definitely something is wrong there. This box could get up to 800-900mb/s if the other end is capable. First thing you'd do is to run pure network benchmark while connect to another host that is Gbs capable. See the Wiki thread: QuotePerfornby bodhi - uBoot
spiderdijon , Please try kwboot with the attached u-boot image: uboot.2024.04-rc3-tld-1.ds414.kwbby bodhi - Debian
spiderdijon, > OK great. Thank you for the instructions, they > were very clear. I have successfully booted into > debian and updated the rootfs and kernel. Here is > the log: Cool! It sounds like you've used option number 2 (boot new kernel temporarily)? > It is interesting to note that the RN2120 has a > dual core CPU but seemingly only one core is beingby bodhi - Debian
Th3l0lb0y, Filesystem Size Used Avail Use% Mounted on udev 241M 0 241M 0% /dev tmpfs 49M 1.3M 48M 3% /run /dev/sdc1 11G 1.6G 8.1G 17% / tmpfs 244M 0 244M 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 244M 0 244M 0% /tmp total 0 I don't see any HDD mounted. You must mount theby bodhi - uBoot
CyberPK, > blue led, solid on = disk presence, solid off = > disk absence, blink disk activity. > > I'm struggling to make this behavior work, but I > probably need to edit your patch because I'm still > not able to connect both the behaviour (disk > presence + disk activity) to the same led. The > ide-disk1/2 trigger seems to override the gpio > iby bodhi - Debian
All, Please try this kernel. See if it helps with the kernel panic. linux-6.7.5-mvebu-tld-2-bodhi.tar.bz2 md5: 8a84e9d35625d3fc5ddd07b52ab271f2 sha256: cb96edad9c0b47ed13bef090d661d2c81fb7650f40269068ad3d461fa72d3a26 This tarball contains 5 files linux-image-6.7.5-mvebu-tld-2_2_armhf.deb linux-headers-6.7.5-mvebu-tld-2_2_armhf.deb zImage-6.7.5-mvebu-tld-2 config-6.7.5-mvebu-tlby bodhi - Debian
Please post output of uname -a mount df -h ls -l /sys/class/leds/ cat /sys/class/leds/nsa320:green:hdd1/trigger cat /sys/class/leds/nsa320:green:hdd2/triggerby bodhi - uBoot
spiderdijon, 1. Recreate the bootable usb drive but with the different kernel Yes. On another Linux host, you can chroot into the USB rootfs (you already created) to install new full kernel linux-6.5.7-mvebu-370xp-tld-1. And then use the same setenv commands above, boot the usb drive. Or use the alternative where you don't use chroot to install: 2. You can also boot kernel linux-by bodhi - Debian
Hi Trond, Sorry, was being sidetracked and forgot! it is uploaded now in the post above.by bodhi - Debian
@spiderdijon, Ah OK. I did not notice that this box has a much older u-boot for Armada XP and Armada 370. Are you familiar with chroot? you need to install the other kernel on top of the current basic rootfs Debian-6.6.2-mvebu-tld-1-rootfs-bodhi.tar.bz2. This is the kernel that should be used for this box. GTI Mirabox and Netgear RN120/RN104 (Armada 370) Installation & Kernel Upgby bodhi - Debian
Please use this new DTB with kernel 6.7.5-mvebu-370xp-tld-2. I've removed audio controller nodes.by bodhi - Debian
> I've just noticed a rewrite of ledtrig-gpio > driver: > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/leds/trigger/ledtrig-gpio.c?id=4a11dbf04f31c71eb458c062129e95b7aa308464 > If I'm not wrong, this patch should enable the > trigger source, eliminating the need to set the > leds in rc.local Not sure I get the idea of this patby bodhi - Debian
> one more question is it normal that in my current > env´s were is 2x arcNumber= with two different > numbers behind ? No, it is not normal. Probably one of the two has some hidden char in the name that we cannot see. Also, these 2 are not needed. boot_sata1=mw 0x800000 0 1; setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10 $mtdparts; ide reset; ext2load ideby bodhi - uBoot
bodhi Wrote: ------------------------------------------------------- > @ksuszka, > > Thanks. So let me upload a new DTB later to see if > we can get around this problem. UPDATE1: looks like I need to investigate further. My initial thought about tweaking the DTS is probably not good. UPDATE2: looks like I need to build a new kernel to test this kernel panic issue.by bodhi - Debian
Th3l0lb0y, Quotei have another question is it possible to get the buttons to work for like (power off ) We have a Wiki thread. QuoteKey daemon (button control) Multimedia keyboard daemon for Linux How to use set up button to reboot or shutdown with Key Daemon (esekeyd) Shutdown with Power button with regret option by esekeyd Read the "Multimedia keyboard daemon for Linux&quby bodhi - uBoot
Hi Trond, > > I notice that there are no > > changes to 'dts/armada-370-netgear-rn102.dtb' > > since version 6.5.7 except for it's time stamp. > Is > > this intentionally? > > Yes, I did not change the DTS, so the DTB is the > same. Perhaps I should remove those sound specific nodes in the DTS too.by bodhi - Debian