bodhi, thanks for you answer. I found a way to flash the new uboot (see my updated previous post). Can you please help me to restore the original rootfs in the flash using hipserv2_seagateplug-20160314.ubi from http://support.goflexhome.hipserv.com/en/reflash/? I have one bad block: Device 0 bad blocks: 07940000. Regards. shvby shv - uBoot
bodhi, the serial console is working. Nevertheless UART booting doesn't work because it is not supported form the processor. I could load something from USB or IDE ext2 filesystem. Now I tried to flash the uboot from IDE: ide reset ext2load ide 0:1 0x6400000 /uboot.2016.05-tld-1.goflexnet.mtd0.kwb nand erase 0x0 0x80000 nand write.e 0x6400000 0x0 0x80000 nand read.e 0x6500000 0xby shv - uBoot
@bodhi, I saw somewhere a post that flashing uboot and/or uboot env is also possible in the boot console (stop bootup at the beginning) using files from a connected usb stick. I have Goflex Net device where rootfs in flash is partly bricked. The original uboot is still on this device. Can you please tell me how to flash new uboot and uboot env with the boot console. This device does not supportby shv - uBoot
I uploaded the source packages which I got from Zyxel: ftp://45.43.194.173/by shv - Debian
The download links I got from Zyxel don't work anymore. I requested new download links but didn't get them yet. I have the packages on my harddisk and will upload them next weekend. It is about 2,5GB and seams to be almost complete with tools and instructions how to build it. The following packages are available: build_NSA325.tar.gz 1,2GB nsa325v2_470aals0c0.tar.gz 800MB sdk3.3-by shv - Debian
@bodhi, I am running NSA 325-v2 stock OS v4.80 with stock kernel version "Linux NSA325-v2 2.6.31.8 #2 Fri May 15 12:20:01 CST 2015 armv5tel GNU/Linux". I prefere a patch for the stock xhci module to prevent any possible drawback due to kernel exchange. If we find a solution it might be regarded by Zyxel for the next FW update of the "old" hardware generation. It would be niby shv - Debian
Hello, I connected a USB3.0 HUB to the NSA325-v2 USB3.0 connector in the front. USB3.0 devices which are connected to the USB3.0 HUB, e.g. harddisks, are no recognized by the firmware. USB2.0 devices connected to the USB3.0 HUB are working. demesg messages after connection of USB3.0 HUB to NSA325-v2: usb 2-3: new high speed USB device using xhci_hcd and address 0 In hub_port_init, and numby shv - Debian
This line is wrong: setenv ide_set_bootargs setenv bootargs 'root=/dev/sda1 rootfstype=ext4 console=ttyS0,115200 mem=128M' I think you didn't change ide_set_bootargs. -shvby shv - uBoot
Because you have a P24 device you should check if you have ox820-pogoplug-classic.dtb in the dts folder. Then you should change your boot env to use this file instead the file for the Pro device. shvby shv - uBoot
@Robert, SATA booting seams to work now. With your current setting you are booting an old kernel uImage_2.6.31.14_OX820_1.2_shv.Pro where you don't have the module path. You only need to change you boot settings by changing one line to: dt_ide_bootcmd=run ide_set_bootargs; run dt_ide_boot setenv dt_ide_bootcmd 'run ide_set_bootargs; run dt_ide_boot' With this change you wiby shv - uBoot
Robert, Can you please upload the script which you used for step3? The latest rootfs is Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2 but this is not your problem because at least one of two prerequisites for SATA booting seams to be not met. You don't need mkenvimage because you can use the serial console to adapt the boot env. -shvby shv - uBoot
Please post the output of the following commands: fdisk -lc blkid Please stop the bootloader at the countdown and post the output of: printenv -shvby shv - uBoot
@Robert, your boot environment looks OK for the old WarheadsSE booting procedure. It looks that you don't have the right rootfs on partition sda2 (ext3/partition name rootfs). Nevertheless I want to recommend you to use new uboot. Bodhi already pointed you to my post: http://forum.doozan.com/read.php?3,16017,17297#msg-17297. The device must support 512 Byte sector size either nativelyby shv - uBoot
Usually it is 700 MHz. You can try running at 850 MHz which is stable using the file from the following post: http://forum.doozan.com/read.php?3,16017,17548#msg-17548. -shvby shv - uBoot
anto Wrote: ------------------------------------------------------- > I have it running as a DLNA audio renderer using > mpd and > umpmd > cli. > > I had to compile upmpdcli from the source version > 0.8.1 (0.8.5 doesn't work) I am using upmpdcli-0.8.6 and is works very well. Can you recommend me a better audio dongle? I am using a dongle like this: http:by shv - Debian
@denexo, if you just need a kernel which supports uvcvideo I could offer you the 2.6.31.14 kernel which I use. Mjpeg streamer is working well. If you want to use this kernel for Pogoplug Pro only I could upload it for you. If it shall be used for Wheezy two small configuration changes must be done which are not necessary for Squeeze. -shvby shv - Debian
@all: I've got the information from the author of the performance values that they are not for Zyxel NSA 325-v2 even they were posted in the OMV for Zyxel NSA thread. This means they are completely useless with regard to Debian on Zyxel device. Nevertheless I will open a new thread to discuss NFS/Samba performance of Kirkwood devices to see if there are differences with different operaby shv - Debian
@Pacemaker, I will do a performance comparision of Debian vs. Archlinux with my Goflex Net device. I didn't find an installation guideline for Freenas on Kirkwood devices yet. -shvby shv - Debian
In the linked post http://pogoplug.square7.de/forum/viewtopic.php?f=4&t=13#p75 I measured the top Samba speed using Totalcommander on a Windows 7 PC to copy one bigger file in both direction. This means that the last post is Samba network speed. If you have a look on the two posts before you will see that I used dd to measure the local drive speed and netio to measure the network performanceby shv - Debian
If you look at my comparision of device performance at http://pogoplug.square7.de/forum/viewtopic.php?f=4&t=13#p75 you will see that you don't reach the highest possible speed with your Pogoplug E02. Moreover you can see that the Goflex Net device can read data from harddrive with 100MB/s from a 2.5" harddisk but reaches just 32MB/s Samba troughput and that this speed limitation doeby shv - Debian
On your PogoPlug E02 you have USB2.0 which is limiting the speed. It might be completely different with Zyxel NAS if it can reach 120MB/s. In this case the kernel and system configuration could limit the reachable speed. -shvby shv - Debian
@Almaz: which is you NFS and Samba troughput? -shvby shv - Debian
bodhi, I didn't use any alternative OS on my Zyxel NAS because I expect less performance compared to the original OS. I think I read here in the forum about the performance if Debian is running on the device. -shvby shv - Debian
You can find some performance figures for different OS für Zyxel NSA325v2:http://www.zyxelforum.de/openmediavault-1-0-ist-da%C7%83-anleitung-zum-installieren--t7787s27.html. It seams to depend on the OS or optimization of its kernel which throughput can be reached. Archlinux and Freenas seam to deliver very good speed but Openmediavault is less than half of this speed. What throughput can be reaby shv - Debian
Also with envs set exactly to the same as stock env the kernel didn't boot. I will not continue trying to find a solution to boot the old kernel/rootfs anymore. In the meantime I made some pictures of the JTAG interface: http://pogoplug.cwsurf.de/jlink.jpg http://pogoplug.cwsurf.de/customadapter.jpg http://pogoplug.cwsurf.de/goflexnetjlink.jpg -shvby shv - uBoot
I just recovered to the original uboot to find out the definition of stock mtd parts. -sh-3.2# cat /proc/mtd dev: size erasesize name mtd0: 00100000 00020000 "u-boot" mtd1: 00400000 00020000 "uImage" mtd2: 02000000 00020000 "root" mtd3: 0db00000 00020000 "data" It is the same as the new definition. But it seams that the original environment vaby shv - uBoot
bodhi, I found a backup of Goflex Net Stock uboot envs: baudrate=115200 loads_echo=0 ipaddr=169.254.254.253 serverip=169.254.254.254 rootpath=/mnt/ARM_FS/ netmask=255.255.0.0 run_diag=yes console=console=ttyS0,115200 CASset=min MALLOC_len=1 ethprime=egiga0 bootargs_root=root=/dev/mtdblock2 ro ethmtu=1500 usb0Mode=host nandEcc=1bit ethact=egiga0 stdin=serial stdout=serial sby shv - uBoot
Seams to be not possible to boot the old original kernel: GoFlexNet> nboot 0x800000 0 0x100000; bootm 0x800000 Loading from nand0, offset 0x100000 Image Name: Linux-2.6.22.18 Created: 2010-10-19 23:05:02 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1979140 Bytes = 1.9 MiB Load Address: 00008000 Entry Point: 00008000 ## Booting keby shv - uBoot
bodhi Wrote: ------------------------------------------------------- > shv, > > ubifs_bootcmd=run ubifs_set_bootargs; if ubi > part data && ubifsmount rootfs && ubifsload > 0x800000 /boot/uImage && ubifsload 0x1100000 > /boot/uInitrd; then bootm 0x800000 0x1100000; > fi > bodhi, I don't think that this will work because there isby shv - uBoot
It didn't work to load the original uboot which shall load and start uImage from Nand with Goflex Net. Therefore I ask if it is posible to load and start uImage directly with your uboot which should normally be possible. -shvby shv - uBoot