FVDW-SL on a Seagate Personal Cloud - additional steps

[fvdw]

I looked to the pictures you have posted, so the kernels are uploaded and you choose the right command

Why did you set nas ip to 192.168.221.6 ?
The ping answer you receive at some moments is that when u-boot is active or after the kernel has been started ?? or does the ping dies after the kernel is loaded ?
After loading the nas gets an IP assigned by your dhcp server so necessary the same one as you use in fvdw-sl-console.
Did you try the fvdw-sl-assistant to find the nas ?

And it seems I made a mistake when making kernel 7. (It is same as 6)

Can you try this updated version #7-2
--edit oops another error I think, this should be the right one

UIMAGE-466-SGARMADA370-7-2.zip

and this one #x

$matches[2]

[fvdw]

I update kernel #7-2 in the post above

[m1m1sm1t1c0]

Why did you set nas ip to 192.168.221.6 ?

This is my NAS IP. Manually assign IP setting.

The ping answer you receive at some moments is that when u-boot is active or after the kernel has been started ?? or does the ping dies after the kernel is loaded ?

u-boot is active. Die after.

After loading the nas gets an IP assigned by your dhcp server so necessary the same one as you use in fvdw-sl-console.

I do not have DHCP in my network. Manually assign IP setting.

Did you try the fvdw-sl-assistant to find the nas ?

If you look closely at the image, I have Wireshark running to find an ip change, but nothing.

[fvdw]

But is the white led working then with sata activity ?

Yes, only color white. It never changes to red. But it flashes.

To avoid misunderstanding
It flashes with disk activity and not with fixed interval like turn signal on a car?

[m1m1sm1t1c0]

It flashes with disk activity and not with fixed interval like turn signal on a car?

It flashes with disk activity.

[fvdw]

Thks so everything is ok, or is the problem that the led cannot be disabled?

[m1m1sm1t1c0]

Thks so everything is ok, or is the problem that the led cannot be disabled?

You are right, the led can not be disabled. Neither button "Power LED Off" nor "LED On/Off at boot".

[Jocko]

You are right, the led can not be disabled. Neither button "Power LED Off" nor "LED On/Off at boot".

Be careful, as some settings are missing, these commands from the web-interface fail in all cases.

Only your direct attempts

Code: Select all

grep '' /sys/class/leds/cumulus:red:sata0/*

Code: Select all

login as: root
root@10.113.1.4's password:
root@ftp:/ # grep '' /sys/class/leds/cumulus:red:sata0/*
/sys/class/leds/cumulus:red:sata0/brightness:0
/sys/class/leds/cumulus:red:sata0/max_brightness:255
/sys/class/leds/cumulus:red:sata0/trigger:[none] kbd-scrollock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock nand-disk timer heartbeat cpu0 default-on
root@ftp:/ #


Was On and White

Code: Select all

echo 255 > /sys/class/leds/cumulus:red:sata0/brightness

on ? red or white ?

Go not total Red

Code: Select all

echo 50 > /sys/class/leds/cumulus:red:sata0/brightness

brightness changes ?

Nop

Code: Select all

echo 0 > /sys/class/leds/cumulus:red:sata0/brightness

led off? or white on ?

White On

Code: Select all

echo hearbeat >/sys/class/leds/cumulus:red:sata0/trigger

do you get a hearbeat blinking ?

Nop

are valid and there it seems there is no way to switch on/off the white LED.
Currently only red colour may be set on/off (not total red because white color is still on)

Go not total Red

[m1m1sm1t1c0]

Can you try this updated version #7-2
--edit oops another error I think, this should be the right one
and this one #x

With UIMAGE-466-SGARMADA370-7-2 neither. NAS does not start. Led one second ON, one second (maybe two) OFF.

With UIMAGE-466-SGARMADA370-X neither. NAS does not start. Led stays ON.

[fvdw]

Then something is wrong with using this method to load a kernel because kernel #x is the actual kernel used in the firmware so it should load. This can only be if the console is not supplying the right boot line commands when loading the kernel.

To find out which parameters to be used you could activate the uboot console of the fvdw-sl console and give at the command line the command

Code: Select all

printenv

and post ouput. I will have look at dmesg output also the boot parameters could be visible.

I assume that the standalone kernel loading works, please confirm