#include <standard_disclaimer.h>/* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the system failed. Please * do some research if you have any concerns about features included in this Kernel/OS * before flashing it! YOU are choosing to use these modifications upon your own choice, and if * you point the finger at me for messing up your device, I'll just sit and laugh at you. */

I used AA666 NSA320 sources for build on NSA310, parts of this tutorial are taken from his topic(credits to him). We couldn't use his sources because there was no compatible ethernet driver included in his kernel image(Rtl8169 for NSA310).

------Compilation from source(CrossCompile on Ubutu)-------*Grab the linux kernel source: linux-3.2.tar.bz2*Make sure you have build-essential & gcc-arm-linux-gnueabi installed*Extract the kernel to a dir in your homedir(for example ~/build)*Cd to build/*Put the patchfile next to the linux-3.2.0 dir*Apply patch: patch -p0 < patch-3.2.0-nsa320*Copy config-arm to .config in linux-3.2.0 directory*make nconfig ARCH=arm(Optional if you want to make changes)*ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- make uImage modules*You'll now have uImage in linux-3.2.0/arch/arm/boot/uImage

------Serial Adapter------U-Boot is only available via a serial console on the board. I've used a bus-pirate to interface with the board. Make sure your cable is only outputting 3.3V.|*|-|*|*|*| --> pinout on the board: |GND|NC|RX|TX|VCC|

------Prepare usb stick------Since uboot on the NSA310 doesn't work with ethernet, it is necessary to make an usb drive with the necessary files.

*Get an usb disk with a size that supports FAT16(<4GB)*Format it to FAT16*Copy the needed files to the stick

Maybe samba issue is related to high network usage? Please write steps to reproduce your problemMy ethernet lights blinks - connected via 100Mbit/s cableI have compiled kernel with my config but i think it is very similar to yours.

My another change is booting from usb by setting bootcmd in u-boot - no pendrive ->no boot.[Edit] and i can change kernel just by replacing one on pendrive [/Edit]I'll check later if our box has cryptographic accelerator - that would be nice to have all disks encrypted

I have changed /etc/inittab to run getty on ttyS0 by commenting all lines and adding getty for ttyS0

S0:2345:respawn:/sbin/getty 115200 ttyS0 vt100....

I have also modified my /etc/inittab and now the getty part looks like this, I forgot to mention that

Code:

.....# Note that on most Debian systems tty7 is used by the X Window System,# so if you want to add more getty's go ahead but skip tty7 if you run X.##1:2345:respawn:/sbin/getty 38400 tty1#2:23:respawn:/sbin/getty 38400 tty2#3:23:respawn:/sbin/getty 38400 tty3#4:23:respawn:/sbin/getty 38400 tty4#5:23:respawn:/sbin/getty 38400 tty5#6:23:respawn:/sbin/getty 38400 tty6

# Example how to put a getty on a serial line (for a terminal)#T0:23:respawn:/sbin/getty -L ttyS0 115200 vt100......

Actually I've tried both drivers, the r8169 driver gave better performance(40MB/s vs 30MB/s). I'm on a gigabit link and haven't tried 100MBit but I'll believe you when you say the lights work at 100MBit

Server only crashes when I'm using samba, FTP works without any problems(@40MB/s). Haven't experienced any other lock-ups either. You just have to write a lot of small files to the samba share and the box will lock-up.

Next thing I'm gonna try is to upgrade to DEB7(wheezy) and see if the samba problems are gone.

Edit: Still happens on wheezy, less frequent though. But still really unstable.

Only issue i found was console terminal not responding after many hours of high load- but this can be related to my ultra cheap ttl converter or getty respawn/inittab issue.I can confirm ethernet lights problem - they do not work when working with gigabit speed

Cryptographic Engine and Security AcceleratorThe device integrates a Cryptographic Engine and Security Accelerator to support data encryption and authentication. It also contains a dedicated Direct Memory Access (DMA) controller to perform the following:„Hardware implementation of encryption and authentication engines to boost packet processing speed„Dedicated DMA to feed the hardware engines with data from the internal SRAM memory or from the DDR memory„Implements AES, DES, and 3DES encryption algorithms„Implements SHA1 and MD5 authentication algorithms

Edit: Have now build a working 3.2 kernel with custom sata led-trigger because AA666 patches on sata_mv didn't work anymore

Now we have sata-disk trigger in /sys/class/leds/nsa320:red:SATA1/triggers

Hi,I followed your guide for installing Debian on my NSA-310. Thank you for sharing your information. I managed to install and boot Debian from USB. First steps are done.

But, when i take off the usb-stick, i´m not able to boot the original zyxel-system. I think i have to change back the arcnumber and something else, but i have no idea what to do. Can you help me with this task? For testing it would be fantastic if i could change the running system, before installing debian in the nand.

You can't have a Debian install and a working stock system, Debian is on harddisk and a part of zyxel's original firmware also(probably) it at least needs disk access. I think if you format the HDD you can boot the original zyxel system again

Thank you for your fast reply. I dont want to have the old system back for long, but just for testing the performance against the debian installation. I wondered, because i haven´t used any harddisk. I followed your guide but installed debian on an usb-stick.

That´s why i thaught, that the original zyxel "Shit" - System is still in the nand. Isn´t that right? I don´t do the Nand-Installation for now. That´s why i thaught simply unplugging the USB-Stick should start the original system.

Who is online

Users browsing this forum: Google [Bot] and 71 guests

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot post attachments in this forum