yes, that's why I've mentioned it. when using other filesystems, it depends on processes and disk io, cpu performance, amount of ram they are limiting transfer speeds but you can compare it. On other boxes I've seen (with some optimisations) 50 - 60 MB/s read and 35 - 40 MB/s write (samba) one thing concerning the "r8169": samba tuning has no effect. when using thby pengu - Debian
this is the real file transfer rate (samba, large file) the more I apply some modification to /etc/smb.conf, the more it depends on the OS. shure, I could use nc or iperf but in real life ftp, samba or http is used. later I'll do some more testing atm, the situation is like this: - the r8168 driver offers high read bot slow write rates - the r8169 driver offers slow read bat nby pengu - Debian
I've noticed that on ZyXEL OS 45 MB/s read and 40 MB/s write is possible. on debian, only 20 - 25 MB/s read and 35 - 38 MB/s write is possible. the "r8169 driver is built into the kernel so I have to change this. I'm using the stock kernel 4.2 sources + patch and the r8169 driver is built as module Now, I could unload / blackist it and use the r8168 driver. http://paby pengu - Debian
sorry I'll test it later. the write problem exists on other boxes so I'll first fix this there. Edit ok ..looks like an error in the fw_env.config now writing is possible on the Stora seems that the first modification which let's the 2047 bad blocks gone awas is enough, but I can test the second one too Edit 2 the last modification is also working ;-)by pengu - Debian
thanks again bodhi ;-) when creating the stick, I wanted to keep the old U-Boot but now I decided to use the new one. as you can see her, this was the cause: (I found the "zImage.fdt" in the /boot directory ;-)) http://pastebin.com/tP76dgcX <- the "old" bootlog http://pastebin.com/hcZKi2gk <- the "new" bootlog with recreated uImage and uInitrd sby pengu - Debian
bodhi Wrote: ------------------------------------------------------- > pengu, > > - Recreate uImage for booting with separated DTB > - Reboot I'm booting with seperate (nsa310s) DTB.by pengu - Debian
got another NSA310s, flashed the new u-boot but I cannot boot debian because bootargs aren't recognized: [ 0.000000] Kernel command line: console=ttyS0,115200 no root and rootfstype were set ;-( on another box I got this fixed bot not on this one: my U-Boot env (atm) NSA3x0S> pri arcNumber=4931 baudrate=115200 bootcmd=run bootcmd_uenv; run set_bootargs_usb; runby pengu - Debian
I got another NSA320 it should running with debian but the first thing that I notice: It looks like I cannont transfer anything via TFTP (U-Boot) The stock U-Boot only noticed sime timeouts and newer U-Boot versions show dropped packages and the file (s) never get transfered NSA320> tftp 0x800000 foo Using egiga0 device TFTP from server 192.168.1.112; our IP address is 192.168.1by pengu - Debian
booted with new DTB: [ 1.884855] nand: device found, Manufacturer ID: 0xec, Chip ID: 0xda [ 1.891247] nand: Samsung NAND 256MiB 3,3V 8-bit [ 1.895926] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64 [ 1.903550] Scanning device for bad blocks [ 1.988351] Bad eraseblock 751 at 0x000005de0000 [ 2.022252] Bad eraseblock 1024 at 0x000008000000 [ 2by pengu - Debian
that's what I get when I try to read the env (fw_printenv) > > What the error message look like? Did it say "too > many bad blocks/ too few good blocks" or did it > show individual bocks? before that, it seems that all blocks on nand were bad blocks: ... [ 11.535624] Bad eraseblock 2037 at 0x00000fea0000 [ 11.540388] Bad eraseblock 2038 at 0x00000by pengu - Debian
I've made a script to do this but sometimes the U-Boot env gets hosed so I do this within U-Bootby pengu - Debian
with stock U-Boot I had some problems getting debian running on this box. so I tried to cleaning out the U-Boot env but this results in an env overflow I tested and flashend the newest U-Boot and it's running fine U-Boot 2014.07-tld-2 (Sep 20 2014 - 01:22:13) Netgear-MS2110 SoC: Kirkwood 88F6281_A1 DRAM: 128 MiB WARNING: Caches not enabled NAND: 256 MiB In: serial Oby pengu - Debian
http://pastebin.com/2PXNJuZj <- the full bootlog [ 9.655453] hwmon_vid: Unknown VRM version of your CPU as we can see here, the "lm sensors" output still doesn't make sense root@debianNSA310:~# sensors adt7476-i2c-0-2e Adapter: mv64xxx_i2c adapter in0: +0.00 V (min = +0.00 V, max = +3.31 V) Vcore: +0.00 V (min = +0.00 V, max = +2.99 V)by pengu - Debian
I see no error here, let's look again at your U-Boot env: you don't need a special bootcmd line for each USB port because they are all recognized. $(loadaddr) points to??? please use it directly as done for loading uInitrd. ext2load usb 0:1 0x800000 /uImage ext2load usb 0:1 0x1100000 /uInitrd bootm 0x800000 0x1100000by pengu - Debian
edinger Wrote: ------------------------------------------------------- > Hi bobafetthotmail, hi bodhi > > @bobafetthotmail: it didn't work. I attached log > on > your post according to your env a primary ext2 or ext3 partition but there is some other stuff there please look at the bootcmd_linux_usb commands, there is something wrong,by pengu - Debian
you can tell us about that perhaps we can confirm this till next weekend ;-)by pengu - uBoot
moved to the right thread ;-) sorry for confusing Sending boot message. Please reboot the target...| Sending boot image... 0 % [......................................................................] 2 % [......................................................................] 4 % [......................................................................] ... ... 94 % [............by pengu - uBoot
bodhi Wrote: ------------------------------------------------------- > pengu, > > > yes it is > > And there was no debug output? if there was, pls > post the log from the beginning. ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2014.07-tld-4-test-1.nsa310.mtd0.kwb -p Sending boot message. Please reboot the target.../ Sending boot image... 0 % [.............by pengu - uBoot
done, nothing changed: http://pastebin.com/htLjmNHEby pengu - Debian
bodhi Wrote: ------------------------------------------------------- > pengu, > > > > > NSA310> ping 192.168.1.112 > > No ethernet found. > > ping failed; host 192.168.1.112 is not alive > > NSA310> > > > > Is this the output from the test u-boot UART > booting? yes it isby pengu - uBoot
I'll do so but there is another interesting thing: as seen in a previous post, on ZyXEL OS the "r8168" driver is used. there, you get 40 MB/s read and 45 MB/s write. this driver is still used on debian wheezy (kernel 3.2.0) on newer kernels wie have the "r8169 with this driver you only get 22 MB/s read and 35 MB/s write with some network tuning, the following is posby pengu - uBoot
the "ZyXEL" NSA310 has arrived so let's see it has the _same_ ethernet chip as the "TDC" one. http://abload.de/img/nsa310_lan_chipapkr9.jpg <- lan chip http://abload.de/img/nsa310_pcb_2auqoo.jpg <- pcb @bobafetthotmail I never had problems with the NSA310 (ZxXEL and TDC) (Kernel 3.18.3, 4.0.0, 4.10) that one on which I tested the new U-Boot yesterdaby pengu - uBoot
both, the "ZyXEL" and the "TDC" brand has a Realtek LAN chip I haven't seen any NSA310 with Marvell Chipby pengu - uBoot
yes, the red usb is working: echo usb-host > /sys/class/leds/nsa310\:red\:usb/trigger http://abload.de/img/nsa310_red_usbgas60.jpg the pci stuff: http://pastebin.com/ZDj9F2Bh nsa310 pcb: http://abload.de/img/nsa310_pcbuwucn.jpgby pengu - uBoot
bodhi Wrote: ------------------------------------------------------- > That's not the same LAN chip, if it shows RTL8169 both is from the same box so ZyXEL OS uses a different driver for the same chip http://abload.de/img/nsa310_lanbisgx.jpg > Does it have the red USB LED? ls /sys/class/leds/nsa310:red:usb . .. brightness device max_brightness power subsysteby pengu - uBoot
bodhi Wrote: ------------------------------------------------------- > pengu Wrote: > -------------------------------------------------- > ----- > > > > MODEL_ID=A203 > > > > This shold be the TDC Homedisk. > > Ah! that makes a lot of sense. The orginal NSA310 > network should work fine. I'll see if I can find > and incorporate thby pengu - uBoot
U-Boot 2014.07-tld-4 (Aug 19 2015 - 20:51:56) ZyXEL NSA310 1-Bay Power Media Server SoC: Kirkwood 88F6281_A1 DRAM: 256 MiB WARNING: Caches not enabled NAND: 128 MiB *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: egiga0 PHY reset timed out MV88E1318 PHY initialized on egiga0 Hit any key to stop autoboot: 0 the networkiby pengu - uBoot
with stock U-Boot: Marvell>> md f1010140 f1010140: 00000000 ffffffff 00000000 00000000 ................ f1010150: 00000009 00000009 00000000 00000000 ................ f1010160: 00000000 00000000 00000000 00000000 ................ f1010170: 00000000 00000000 00000000 00000000 ................ f1010180: 00000000 00000000 00000000 00000000 ................ f1010190: 0by pengu - Debian
bodhi Wrote: ------------------------------------------------------- > pengu, > > > nothing changed ... > > Of course, I now saw that it was already set to 2 > before the poke. > > Was that true it is already before the poke it was already > > f1010140: 00000002 fffffff9 00000000 00000000 > ................ > > when you interruptby pengu - Debian
f1010140: 00000002 fffffff9 00000000 00000000 ................ f1010150: 00000009 00000009 00000000 00000000 ................ f1010160: 00000000 00000000 00000000 00000000 ................ f1010170: 00000000 00000000 00000000 00000000 ................ f1010180: 00000000 00000000 00000000 00000000 ................ f1010190: 00000000 00000000 00000000 00000000 .............by pengu - Debian