LED control

[taetae]

I can see sda7 after having installed only through the console. if I try I can not log in WINSscp ...

http://it.tinypic.com/r/18d8hk/8

[Jocko]

Hi taetae,

Do you refresh the winscp cache ?

If yes, that means that some times you are and other times not in the chrooted file system :scratch .

So we will try to get a clean status.

In Putty (not in winscp), do

Code: Select all

cat /etc/fvdwversion

and

Code: Select all

ls -al /etc/init.d

if sda7 is still mounted on /sda7, do

Code: Select all

ls -al /sda7/etc/init.d

[taetae]

Code: Select all

ls
0026FFF0     brightness   lacie-boot   nowhere      sda7         var
00283280     clunc        lib          opt          share
bin          dev          linuxrc      proc         sys
bin_cab      etc          lost+found   root         tmp
boot         eth0         mail         rw_fs        trigger
boot.log     fvdw-chroot  mnt          sbin         usr
~ # mkdir /sda7
mkdir: can't create directory '/sda7': File exists
~ # mount /dev/sda7 /sda7
~ # cat /etc/fvdwversion
fvdw-sl 15.0
~ # cd ..
~ # cat /etc/fvdwversion
fvdw-sl 15.0
~ # ls -al /etc/init.d
total 88
drwxr-xr-x    2 root     0             4096 Mar  1  2014 .
drwxrwxrwx   15 root     0             4096 Mar  1  2014 ..
-rwxr-xr-x    1 root     0             1893 Mar 28  2013 fuse
-rwxr-xr-x    1 root     0              504 Dec 23  2012 insert-modules
-rwxr-xr-x    1 root     0             3779 Jul 13  2011 rc.banner
-rwxr-xr-x    1 root     0             3779 Jul 13  2011 rc.banner.copy
-rwxr-xr-x    1 root     0             5435 Sep 21  2013 rc.bootup1
-rwxr-xr-x    1 root     0             5435 Sep 21  2013 rc.bootup1.copy
-rwxr-xr-x    1 root     0              316 Aug 12  2013 rc.bootup2
-rwxr-xr-x    1 root     0              316 Aug 12  2013 rc.bootup2.copy
-rwxr-xr-x    1 root     0             3160 Aug 13  2013 rc.bootup3
-rwxr-xr-x    1 root     0             3160 Aug 13  2013 rc.bootup3.copy
-rwxr-xr-x    1 root     0            15252 Sep 27  2013 rcS
-rwxr-xr-x    1 root     0            15252 Sep 27  2013 rcS.copy
~ # cd sda7/
/sda7 # ls -al /sda7/etc/init.d
total 88
drwxr-xr-x    2 root     0             4096 Mar  1  2014 .
drwxrwxrwx   15 root     0             4096 Mar  1  2014 ..
-rwxr-xr-x    1 root     0             1893 Mar 28  2013 fuse
-rwxr-xr-x    1 root     0              504 Dec 23  2012 insert-modules
-rwxr-xr-x    1 root     0             3779 Jul 13  2011 rc.banner
-rwxr-xr-x    1 root     0             3779 Jul 13  2011 rc.banner.copy
-rwxr-xr-x    1 root     0             5435 Sep 21  2013 rc.bootup1
-rwxr-xr-x    1 root     0             5435 Sep 21  2013 rc.bootup1.copy
-rwxr-xr-x    1 root     0              316 Aug 12  2013 rc.bootup2
-rwxr-xr-x    1 root     0              316 Aug 12  2013 rc.bootup2.copy
-rwxr-xr-x    1 root     0             3160 Aug 13  2013 rc.bootup3
-rwxr-xr-x    1 root     0             3160 Aug 13  2013 rc.bootup3.copy
-rwxr-xr-x    1 root     0            15252 Sep 27  2013 rcS
-rwxr-xr-x    1 root     0            15252 Sep 27  2013 rcS.copy
/sda7 #


ps : fvdw-sl firmware version 15-3 in web

[Jocko]

Hi taetae,

Just a question how do you get your shell terminal (what do you use to get it ?)

[fvdw]

Jocko means do you use your serial console ? or do you use a shell client like Putty ?

[taetae]

Using a jtag connects to putty

[fvdw]

so then you use the serial console.
That runs outside the chrooted environment.
If you want to give linux commands while the fvdw-sl firmware is running you should use Putty to coonect to the ssh server and not use the serial console. Or use WinScp which is in fact also a ssh client.

--edit
the serial console is good for montoring boot process and loading of the kernel as it will run even if there is no ethernet driver loaded

[taetae]

ok ;-) WinSCP and console WinSCP

Code: Select all

/sda7/etc/init.d

rcs sda7

[Jocko]

Hi taetae,

Seems that you have an error with tmp folder...

So there is no chroot issue and also no error with the patch install :pound

1/
- in others settings menu, select the option 'LED On at next boot'
- in putty terminal

Code: Select all

/etc/leds_bootup

if all is right, the front LED should be blue and not blinking and sata leds should be blue and blinking on R/W disk events (if a disk is missing then its led is red)

2/ - in others settings menu, select the option 'LED Off at next boot'
- in putty terminal

Code: Select all

/etc/leds_bootup

I made an error about, just do in a Putty terminal

Code: Select all

/etc/leds_switch off

if all is right, the front LED should be off but not the sata LEDS because we find no command to switch off them

3/ in LED off/on menu, what is it the behavior when you try to switch on/off the LEDs

You can now make these tests without your serial console.

[taetae]

Code: Select all

/etc/leds_bootup

Front LED blue blinking and all Sata LED blue on ( blinking on R/W disk events)

Code: Select all

/etc/leds_switch off

Front LED blue blinking