network space 2 fvdw-sl firmware is running !

[fvdw]

Good news

yesterday evening I prepared a disk for the network space 2 (yes the new version with 256 MB RAM and 800 Mhz processor)
First I compiled a new kernel for it as we can not use the one for the newsp1 as the hardware is different
I used Linux 2.6.33.1 with some modifications in the configuration but basically same settings as the kernel for the nwsp1 and spd8020 regarding induced device and modules. This to have max compatibility between the firmware.
I needed to make a few changes in the main boot script as there are some dedicated settings there for the hardware of the spd8020 and nwsp1. For the rest the firmware is untouched.
The setup method for the disk is the same as for the nwsp1 (same partition structure with 8 partitons and what to store in each partition) I only made the swap partition bigger as the nwsp2 has 256 MB of ram so I gave it 512 MB of swap.

I needed to boot twice to get the share partition mounted (same issue as with nwsp1) but after that everything seems to work also the USB port (front). Samba came up as it should ssh is working alos FTP server, the twonky and firefly server started without a problem.

Writing to the internal disk that is formatted in ext3 using the samba server goes at speeds of 30 MB/s (gigabit) network :shock: now thats an improvement.
Also the ntfs r/w driver seems to work (for use with usb ntfs disks), unfortunate it is the ntfs-3G freeware driver that we have in the firmware so write speeds will be not be high
Jocko, the loading of the web pages is much faster (of course) the view system information screen is there within 2 seconds

The firmware only takes 33 MB of the memory so we have 220 MB free for application software without need to use the swap

:mrgreen: :mrgreen: think we have a killer NAS now with a firmware we can adapt as we like

Knowing it runs on the nwsp2 indicates that running it on other lacie device will be possible as well


partition structure (500 MB disk)

Code: Select all

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sda1               1          32      257008+ 83 Linux
/dev/sda2              33          64      257040  83 Linux
/dev/sda3              65         128      514080  82 Linux swap
/dev/sda4             129       60801   487355872+  5 Extended
/dev/sda5             129         176      385528+ 83 Linux
/dev/sda6             177         177        8001  83 Linux
/dev/sda7             178         210      265041  83 Linux
/dev/sda8             211       60801   486697176  83 Linux



demesg log after boot

Code: Select all

/ # dmesg
Linux version 2.6.33.1 (root@linux-fw1) (gcc version 4.2.0 20070413 (prerelease)                                              (CodeSourcery Sourcery G++ Lite 2007q1-21)) #49 PREEMPT Sat Jul 9 01:34:38 CEST 2011
CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: LaCie Network Space v2
Ignoring unrecognised tag 0x41000403
Memory policy: ECC disabled, Data cache writeback
On node 0 totalpages: 65536
free_area_init_node: node 0, pgdat c03b1368, node_mem_map c03ca000
  Normal zone: 512 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 65024 pages, LIFO batch:15
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
Kernel command line: console=ttyS0,115200 root=/dev/sda7 ro reset=0 productType= ASTON_KW
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 256MB = 256MB total
Memory: 255872KB available (3528K code, 196K data, 112K init, 0K highmem)
SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:114
Calibrating delay loop... 797.90 BogoMIPS (lpj=3989504)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
Kirkwood: MV88F6281-A1, TCLK=166666667.
Feroceon L2: Enabling L2
Feroceon L2: Cache support initialised.
initial MPP regs: 01112222 00003311 00551100 00000000 00000000 00000000 00000000
  final MPP regs: 01112222 00003311 00551100 00000000 00000000 00000000 00000000
bio: create slab <bio-0> at 0
SCSI subsystem initialized
libata version 3.00 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Switching to clocksource orion_clocksource
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 32
NetWinder Floating Point Emulator V0.97 (double precision)
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
msgmni has been set to 500
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
console [ttyS0] enabled
loop: module loaded
Uniform Multi-Platform E-IDE driver
ide-gd driver 1.18
sata_mv sata_mv.0: version 1.28
sata_mv sata_mv.0: slots 32 ports 2
scsi0 : sata_mv
scsi1 : sata_mv
ata1: SATA max UDMA/133 irq 21
ata2: SATA max UDMA/133 irq 21
MV-643xx 10/100/1000 ethernet driver version 1.4
mv643xx_eth smi: probed
net eth0: port 0 with MAC address 00:d0:4b:8d:a9:74
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
orion-ehci orion-ehci.0: Marvell Orion EHCI
orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver ums-datafab
usbcore: registered new interface driver ums-freecom
usbcore: registered new interface driver ums-jumpshot
usbcore: registered new interface driver ums-sddr09
usbcore: registered new interface driver ums-sddr55
input: gpio-keys as /class/input/input0
i2c /dev entries driver
at24 0-0050: 512 byte 24c04 EEPROM (writable)
Registered led device: ns_v2:red:fail
mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver
mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver
mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy )
mv_xor mv_xor.2: Marvell XOR: ( xor cpy )
mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy )
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
TCP cubic registered
NET: Registered protocol family 17
Gating clock of unused units
before: 0x00c7c1dd
 after: 0x00c7c1c9
VFP support v0.3: not present
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
ata1.00: ATA-8: Hitachi HDP725050GLA360, GM4OA52A, max UDMA/133
ata1.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata1.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access     ATA      Hitachi HDP72505 GM4O PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/465 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO                                              or FUA
 sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 >
sd 0:0:0:0: [sda] Attached SCSI disk
ata2: SATA link down (SStatus 0 SControl F300)
EXT3-fs (sda7): orphan cleanup on readonly fs
kjournald starting.  Commit interval 5 seconds
ext3_orphan_cleanup: deleting unreferenced inode 975
EXT3-fs (sda7): 1 orphan inode deleted
EXT3-fs (sda7): recovery complete
EXT3-fs (sda7): mounted filesystem with ordered data mode
VFS: Mounted root (ext3 filesystem) readonly on device 8:7.
Freeing init memory: 112K
EXT3-fs (sda7): warning: maximal mount count reached, running e2fsck is recommen                                             ded
EXT3-fs (sda7): using internal journal
kjournald starting.  Commit interval 5 seconds
EXT3-fs (sda5): using internal journal
EXT3-fs (sda5): recovery complete
EXT3-fs (sda5): mounted filesystem with ordered data mode
Adding 514072k swap on /dev/sda3.  Priority:-1 extents:1 across:514072k
Slow work thread pool: Starting up
Slow work thread pool: Ready
NTFS driver 2.1.29 [Flags: R/W MODULE].
fuse init (API version 7.13)
kjournald starting.  Commit interval 5 seconds
EXT3-fs (sda8): using internal journal
EXT3-fs (sda8): mounted filesystem with ordered data mode
eth0: link up, 1000 Mb/s, full duplex, flow control disabled
warning: `proftpd' uses 32-bit capabilities (legacy support in use)


Look at the memory usage...lots of free memory...= lots of possibilities

Code: Select all

/ # free
              total         used         free       shared      buffers
  Mem:       256136        33656       222480            0         1188
 Swap:       514072            0       514072
Total:       770208        33656       736552

loot at the transfer rates... :shock: :D

transfer speed.JPG

[langerak]

Possible this will run on the EDMini etc as well. The EDMini with it's slow processor would be nice to have this on :).

The NS2 gives better performance indeed (altho mine died). But there is a substantial difference in your screenshot, is this reading or writing? I suppose it's reading? On writing my tinkered NS2 never got above 20 MB/s and reading around 30/35 Mb. With FTP transfer, you can add a +10 Mb/sec for reading / writing.

Argh fvdw, now I have to continue scripting on this :P.

[fvdw]

:mrgreen: it was writing (read the screen shot van windows PC-->naar public folder on nswsp2)

It does not always get this speed typically more around 25 MB/s but that is still very good

Think the firmware will run as well on the EDmini although I don't have kernel for that, if I remember it is supported in the orion-git so that should be not a big problem (only V2 of EDmini seems to be supported).
Does the EDmini have the same boot sequence as the networkspace 1 and 2 ? Loading the kernel from sda6 and root filesystem in sda7 ?

Maybe I should compile a kernel that supports mutiple device which is possible if the mach numbers are different used by the bootloaders of the devices
edit--- a quick check indicates that this is a no go as the spd8020 and EDmini use the same mach number (526) in the boot loader.
Can you confirm that langerak ? That means the mach-types files need to be changed otherwise the EDmini bootloader will not laod the kernel. Unfortunate it uses the same number as the spd8020/Lacie nwsp1

Disadvantage is also that the kernel will become bigger for device like nwsp 1 and spd8020 this is a disavantage giving their tiny system memory

[fvdw]

same file as above but now reading from nwsp2 public folder :D :shock: :shock:

transfer speed reading.JPG

[fvdw]

a somewhat bigger file, but you can see the transfer is quite stable see task mangers windows (I did it three times)

transfer speed reading2.JPG

[fvdw]

writing same file, odd is that network traffic is higher when writing then during reading...

transfer speed wrting2.JPG

[fvdw]

on the spd8020 speeds are for this file reading 10 MB/s and writing 6-7 MB/s with same behavior that network traffic during writing is higher.

[Jocko]

fvdw, great job! :P

The work to improve the firmware is even more justified and this motivates to continue ;)

[langerak]

There is only one major difference as far as I know within the LaCie nas range. That is the "Orion" branch, those would consist of the non-black brick design of LaCie, with InternetSpace as only brick device using the same CPU as the older devices, but newer partitioning scheme.
It is possible to build a "universal" kernel, but only for the "Kirkwood" devices, to which NS2 belongs as well, only not supported in stock kernel. The currently supported Kirkwood devices are:

Code: Select all

Marvell DB-88F6281-BP Development Board
Marvell RD-88F6192-NAS Reference Board
Marvell RD-88F6281 Reference Board
Marvell 88F6281 GTW GE Board
Marvell SheevaPlug Reference Board
Marvell eSATA SheevaPlug Reference Board
Marvell GuruPlug Reference Board
QNAP TS-110, TS-119, TS-119P+, TS-210, TS-219, TS-219P and TS-219P+ Turbo NAS
QNAP TS-410, TS-410U, TS-419P, TS-419P+ and TS-419U Turbo NAS
Seagate FreeAgent DockStar
Marvell OpenRD Base Board
Marvell OpenRD Client Board
Marvell OpenRD Ultimate Board
LaCie Network Space v2 NAS Board
LaCie Internet Space v2 NAS Board
LaCie Network Space Max v2 NAS Board
LaCie d2 Network v2 NAS Board
LaCie 2Big Network v2 NAS Board
LaCie 5Big Network v2 NAS Board
HP t5325 Thin Client

So on supporting those devices, there would be a broader approach of firmware use, but should for now only be limited to LaCie devices because of their partitioning scheme. I also own that thin client, but it sucks deeply due to the graphics card with no opensource drivers...

The kernel should not get any bigger. Only compile in the needed drivers and let the rest be modules, therefore placing them on the disk filesystem. I've done that with my EDMini V2 and others, just compile in the most needed drivers, and the rest, let them be modules. In this case they only use space on disk during the time they are not used :).
For Orion, as long as you make sure you selected the units you want to support, there should be no hassle with mach ID's.

The transfer speeds are nice, altho a small file is used. Try a good full DVD size file, I would like to see some graphs of that, because with such files, I also get better speeds, but at the end it drops like hell.

About the network traffic, maybe the NAS is receiving more than it can handle at that time? With 256 Mb, it can store more information into buffers in RAM.

[fvdw]

.......
The transfer speeds are nice, altho a small file is used. Try a good full DVD size file, I would like to see some graphs of that, because with such files, I also get better speeds, but at the end it drops like hell.

About the network traffic, maybe the NAS is receiving more than it can handle at that time? With 256 Mb, it can store more information into buffers in RAM.

well it was a 1.41 GByte file, pretty big and the graphs shows that speed is rather constant

why more network transfer is there with writing although transfer speed is lower has i think nothing to do with RAM but more with the way the dta is stored on disk using ext3 format