adapting fvdw-sl firmware for isp1 trials

[johan72]

Ok, thats very nice indeed.

the lsmod gives the following result

Code: Select all

/ # lsmod
fuse 53621 0 - Live 0xbf0d0000
ntfs 209080 0 - Live 0xbf093000
libcrc32c 660 0 - Live 0xbf08d000
isofs 22882 0 - Live 0xbf081000
crc_ccitt 993 0 - Live 0xbf07b000
crc32c 2384 1 - Live 0xbf075000
crypto_hash 10529 2 libcrc32c,crc32c, Live 0xbf06c000
crypto_algapi 11145 1 crypto_hash, Live 0xbf062000
cifs 218827 0 - Live 0xbf021000
nls_cp865 4567 0 - Live 0xbf01a000
nls_cp863 4567 0 - Live 0xbf013000
nls_cp860 4311 0 - Live 0xbf00c000
nls_utf8 918 0 - Live 0xbf006000
nls_iso8859_3 3551 0 - Live 0xbf000000


[fvdw]

That proves that all modules are loaded, than all features of the fvdw-sl firmware should work....including the ntfs-3G driver enabling write access to ntfs formatted usb disks :D

[johan72]

:) Yes, the NTFS support works!
Will upgrade the other IS with this linux kernel. :P

[2011-09-04] update
This is the correct picture.

[fvdw]

that good news..your picture shows a vfat formated usb disk however..??

ps I will prepare a ISP1 package for the download section of the forum

[fvdw]

Johan, another request..can you also update the how-to guide for first install, and add the writing of the new kernel

ps the first time install package will contain:

a kernel with name: uImage-26331-2-isp1

an archive for sda5 with name : sda5-lacie-isp.tar.gz

a disk image with the fvw-sl firmware: fvdw-sl-9-0-isp1-ddmmmyyyy.img

a file MD5 containing MD5 checksum of the firmware image file, can be used to verify if the firmware file.

a file with name PLATFORM containing information on platform for which files are intended

a file with name NAME containing name of the firmware file, this is for future use

a file with name release_notes.htm conatining the release notes form the firmware

[johan72]

Ah a new package for the IS..great...
Will it contain the fix for reboot aswell?

Below you will find an updated first time install manual for IS devices :)
Please review it.

-edit fvdw
file removed as it is outdated

[fvdw]

I will review it Johan

did you test changing the symlinks for reboot and poweroff ? and if so, did they work ?
Alternatively you could also give the following commands in putty to test if the standard linux commands work on this device (better not use the command window in winSCP for it)

Code: Select all

sync
busybox poweroff


Code: Select all

sync
busybox reboot


[johan72]

No did not change the symlinks yet.
Tested with Putty, reboot is OK, poweroff is NOT.
Poweroff makes the IS inaccessible. Disconnects all connections but power stays on.

[fvdw]

mmm..at least reboot is working.

At poweroff maybe only the led is still working as you mention that it becomes inaccessible, is the HDD still spinning ?
Does the pushing the power switch on the back let it boot again. If so then a solution could be to find a way to switch of the led at poweroff.

PS I did some googling on edmini_v2 as it is that kernel we use and found that the poweroff is known issue with the vanilla kernel and is not (yet) supported properly in the vanilla kernel. Seems some specific bits must be set in the I2C device on the mainboard. The reason why it is not included in the kernel setup is unclear.

[johan72]

Tried the poweroff again by using Putty.
HDD is not spinning, LAN LED's are flashing, Blue LED on front panel is lit up.
The IS does not respond on any PowerSwitch action.
Only way to power it up again is by dis- and reconnecting the powercable.