network space 2 fvdw-sl firmware is running !

[langerak]

Then those speeds are really nice indeed! Good for streaming :).

[fvdw]

I compiled a new kernel as the RTC clock was not working in the previous version, logical as it has different hardware. From the dmesg output from the original lacie kernel I figured out which driver to use.. :mrgreen: hwclock is up and running as well

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)) #50 PREEMPT Thu Jul 14 23:54:04 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 c03b13b4, 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
rtc-mv rtc-mv: rtc core: registered rtc-mv as rtc0
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
rtc-mv rtc-mv: setting system clock to 2011-07-14 22:27:33 UTC (1310682453)
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): mounted filesystem with ordered data mode
VFS: Mounted root (ext3 filesystem) readonly on device 8:7.
Freeing init memory: 112K
kjournald starting.  Commit interval 5 seconds
EXT3-fs (sda7): warning: maximal mount count reached, running e2fsck is recommended
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): recovery complete
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)
/ #


furthermore everything of the fvdw firmware seems to be running

Code: Select all

 # ps -ef
UID        PID  PPID  C STIME TTY          TIME CMD
root         1     0  0 22:27 ?        00:00:00 init
root         2     0  0 22:27 ?        00:00:00 [kthreadd]
root         3     2  6 22:27 ?        00:00:35 [ksoftirqd/0]
root         4     2  0 22:27 ?        00:00:00 [events/0]
root         5     2  0 22:27 ?        00:00:00 [khelper]
root         8     2  0 22:27 ?        00:00:00 [async/mgr]
root       109     2  0 22:27 ?        00:00:00 [sync_supers]
root       111     2  0 22:27 ?        00:00:00 [bdi-default]
root       112     2  0 22:27 ?        00:00:00 [kblockd/0]
root       117     2  0 22:27 ?        00:00:00 [ata/0]
root       118     2  0 22:27 ?        00:00:00 [ata_aux]
root       122     2  0 22:27 ?        00:00:00 [ksuspend_usbd]
root       127     2  0 22:27 ?        00:00:00 [khubd]
root       146     2  0 22:27 ?        00:00:00 [rpciod/0]
root       153     2  0 22:27 ?        00:00:00 [kswapd0]
root       154     2  0 22:27 ?        00:00:00 [aio/0]
root       155     2  0 22:27 ?        00:00:00 [nfsiod]
root       221     2  0 22:27 ?        00:00:00 [scsi_eh_0]
root       223     2  0 22:27 ?        00:00:00 [scsi_eh_1]
root       229     2  0 22:27 ?        00:00:00 [mtdblockd]
root       290     2  0 22:27 ?        00:00:00 [usbhid_resumer]
root       310     2  0 22:27 ?        00:00:00 [kjournald]
root       324     2  0 22:27 ?        00:00:00 [kjournald]
root       350     2  0 22:27 ?        00:00:00 [kslowd000]
root       351     2  0 22:27 ?        00:00:00 [kslowd001]
root       440     1  0 22:27 ?        00:00:00 /sbin/syslogd
root       450     1  0 22:27 ?        00:00:00 /usr/sbin/noflushd -n 15 /dev/sda
root       457     2  0 22:27 ?        00:00:00 [kjournald]
root       488     1  0 22:27 ?        00:00:00 /sbin/udhcpc -b -i eth0 -s /etc/api/api_dhcpc.php dhcpdCbScript
root       497     1  0 22:27 ?        00:00:00 /sbin/udevd
root       502     1  0 22:27 ?        00:00:00 /usr/bin/httpd -f httpd.conf -d /etc
_ntp       517     1  0 22:27 ?        00:00:00 /usr/bin/ntpd -s -f /rw_fs/etc/ntp.conf
nobody     518   502  0 22:27 ?        00:00:00 /usr/bin/httpd -f httpd.conf -d /etc
root       519     1  0 22:27 ?        00:00:00 /usr/bin/ntpd -s -f /rw_fs/etc/ntp.conf
root       543     1  0 22:27 ?        00:00:00 /usr/sbin/syncawayd -n 3
root       554     1  0 22:28 ?        00:00:02 mrvlqosd
nobody     597     1  0 22:28 ?        00:00:00 proftpd: (accepting connections)
root       609     1  0 22:28 ?        00:00:00 dropbear
root       642     1  0 22:28 ?        00:00:00 /usr/sbin/nmbd -D -l /var/log/samba
root       644     1  0 22:28 ?        00:00:00 /usr/sbin/smbd -D -l /var/log/samba
root       647   644  0 22:28 ?        00:00:00 /usr/sbin/smbd -D -l /var/log/samba
root       648     1  0 22:28 ?        00:00:00 /bin/sh
root       649   609  0 22:28 ?        00:00:00 dropbear
root       650   649  0 22:29 ?        00:00:00 -sh
root       668   609  0 22:30 ?        00:00:00 dropbear
root       669   668  0 22:30 ttyp0    00:00:00 -sh
root       676     2  0 22:35 ?        00:00:00 [flush-8:0]
root       679   669  0 22:36 ttyp0    00:00:00 ps -ef


[fvdw]

The firmware seems to run fine on the network space vs2 , some minor adaptations to be made wrt poweroff and reboot as on the philips and nwsp1 they were hardware dependent.

I also managed to get a procedure in place to run the firmware from different partition just like on the spd8020, this makes upgrading in future much easier.
One big improvement is also the response of the webinterface, see video attached to get an impression (download it and unzip it, its a wmv file)

nwsp2-3-wmv.zip

edit---
shutdown is working, but reboot not
could use some inputs on how the reboot is implemented on the lacie nwsp2, the standard commands don't work they only shut down the device. I look at the reboot command in the lacie firmware but it is linked to ncginit, the source code is quite complicated but maybe someone can have a look to figure out how it is down.

[fvdw]

edit---
shutdown is working, but reboot not
could use some inputs on how the reboot is implemented on the lacie nwsp2, the standard commands don't work they only shut down the device. I look at the reboot command in the lacie firmware but it is linked to ncginit, the source code is quite complicated but maybe someone can have a look to figure out how it is down.

:mrgreen: solved, found a way to manipulate the power button setting, now it reboot when using the reboot command and powers off when using a (software) power off command. Also it can be set to boot when power is connected without the need to push the back button for two seconds. This is good when you have a power failure, after power is restored it will boot automatically when power is restored.

So everything is in principle available to be able to make a firmware release. That will not be in the coming weeks but probably in august, sorry to keep you waiting but summer also asks for other activities ;)

[fvdw]

19 august 2011

It is finally ready and I can release the first version of the firmware fo use on the lacie network space 2. (nwsp2) :D :mrgreen:
It is running now for some weeks without a problem on my nwsp2 so I consider it save to release it as "beta" version. For testing by others to see if there are still any bugs.

See firmware and howto guides topic of the forum, there are the files ready for download.

Please share your experiences with us when having installed it.
It will help us to improve the firmware further and it can be useful for others
thks

--edit
Remark: when you have used the shutdown or reboot command in the web interface of the fvdw-sl firmware on the nwsp2 the power up method of the nwsp2 will change. When connecting power it will directly continue with booting no need any more to press and hold the button on the back for 2 sec to enable boot. This change was necessary to make normal linux shutdown and reboot commands work. Also I think it is good that it boots automatically after a power failure as you are not always at home to fire it up again after a power failure. When using the standby command in the fvdw-sl web interface the nwsp2 will switch off with the power still connected, it can be started again by simply pressing and releasing the button on the back. No need to disconnect/reconnect power. The original behavior can be restored, that option will be included in one of the next releases

[moonshadow88]

Hi@ll

I have been using your firmware for a while on a lacie network space v2 and it works really good!

the only thing I can't find is where to config the USB Share, this is, the partition you see when you connect the nas to a PC using the back usb connector.

Can you help me?

Thnx in advance and continue like that!

[fvdw]

thks for your feedback moonshadow88, much appreciated and glad to hear that it meets your expectations

what do you want to configure on the usb share ?
read/write rights per user you can set in the shares menu of the web interface, the usb share will be listed and just click on it to edit the settings as you would do with any other share

[moonshadow88]

hi,

I think i didn't explain myself clear enough. No problem with the usb shares, what I want is use the nas as usb mass storage device (like a usb pendrive). The original firmware allows you to use 500Gb of the disk as usb mass storage device. With your firmware when I connect the NAS to the computer using a usb sable, my windows 7 didn't recognize it.

[fvdw]

aha.. now I understand, thats the usb connector on the back of the nwsp2, indeed that is still not working on our firmware, need to study the lacie firmware how they have implemented that, but it is not very high on the priority list to be honest as not many people use the NAS as USB drive ;)

[moonshadow88]

sorry to hear that because it's a critical feature to me :(

I will have to restore the original firmware until yours support that feature. Is there a guide to restore the original firmware as good as the one to install yours? I have done the backup of the partitions explained in your guide.

anyway, you're doing a great job, keep it that way!!!