Lacie EdMini V2 - noob review - speed question

[fvdw]

Yesit measn the compiler on my nwsp2 is ok for for this kernel. That makes it much easier to do experiments as cross compiling has its limitations

Good to hear that the now at least the power led is on, so that change made was right.
To get disk activity blinking you could try the trigger setting again. If thats ok then a simple line in the boot scripts will enable that.

For the poweroff via gpio pin 24.
This can only by done by compiling new kernels.
first one to define the gpio 24 pin without setting a value and trying if a value can be set with exporting the it.
If that not works define gpio pin 24 and set it to value 0 (value 1 we already tried and that made the edmini_v2 not booting anymore)

I will compile those.
But I lost some files during the weekend due to a bug in the firmware and need to set up the kernel files again. But maybe I can send them this evening.

[fvdw]

pm sent with two more kernels to try
kernel 5 with only as extra defining gpio pin 24 in the kernel (to test if we can now export it when the nas is running)
kernel 6 with gpio pin 24 defined and value set to 0 (to test if with kernel 5 we still can not export the pin if this makes export possibe, the setting of ) is different from firts trial were we used 1 and that made the edmini_v2 stop booting, so the setting 0 may prevent this)

[swamswam_h]

Kernel 5: The echo commands you suggested in the earlier post gave the same error as before. I have listed the contents of the /sys/class/gpio directories (if that is any help at all). Shutdown and restart behavior remain the same.

root@LACIE_NAS:/sys/class/gpio/gpiochip0 # echo 24 > /sys/class/gpio/export
root@LACIE_NAS:/sys/class/gpio/gpiochip0 # echo out > /sys/class/gpio/gpio24/direction
-sh: can't create /sys/class/gpio/gpio24/direction: nonexistent directory
root@LACIE_NAS:/sys/class/gpio/gpiochip0 # cd /sys/class/gpio
root@LACIE_NAS:/sys/class/gpio # ls -l
total 0
--w------- 1 root root 4096 2012-09-18 09:31 export
drwxr-xr-x 3 root root 0 2012-09-18 10:27 gpiochip0
--w------- 1 root root 4096 2012-09-18 10:27 unexport
root@LACIE_NAS:/sys/class/gpio # cd gpiochip0
root@LACIE_NAS:/sys/class/gpio/gpiochip0 # ls -l
total 0
-r--r--r-- 1 root root 4096 2012-09-18 09:30 base
-r--r--r-- 1 root root 4096 2012-09-18 09:30 label
-r--r--r-- 1 root root 4096 2012-09-18 09:30 ngpio
drwxr-xr-x 2 root root 0 2012-09-18 09:30 power
lrwxrwxrwx 1 root root 0 2012-09-18 09:30 subsystem -> ../../gpio
-rw-r--r-- 1 root root 4096 2012-09-18 09:30 uevent
root@LACIE_NAS:/sys/class/gpio/gpiochip0 # cd power
root@LACIE_NAS:/sys/class/gpio/gpiochip0/power # ls -l
total 0
-rw-r--r-- 1 root root 4096 2012-09-18 09:30 wakeup
root@LACIE_NAS:/sys/class/gpio/gpiochip0/power #

[swamswam_h]

Kernel 6: System boots normally. Everything seems ok.

I'm reading this page now: http://www.rigacci.org/wiki/doku.php/do ... d2_network
The board in the D2_network is different from the one in the EdMiniV2. Although there are many, many similarities.
I just remembered something else: the original lacie firmware had a blue powerled with blue (off=disk-read activity?) and a red led for disk-write activity. Is the 'patch' that is proposed on this page also possible on the plugout software to enable the red led? (perhaps blue = power, red = disk activity of any kind)?

So both kernels you sent me are bootable. How do I proceed now? Are there any other things I can test, any patches possible?

[swamswam_h]

Oh and for some strange reason the samba server isn't accessible from my main computer (all others work fine, so the problem lies in this one computer and not with the plugout firmware). Probably a temporary glitch. But to circumvent this I had enabled the FTP server but I couldn't get anywhere when logged on. The problem: again, a leading space in the user account management ftp home share field. Strange huh? But I'm aware of the spaces now so whenever I enter something somewhere... check for spaces first! :-D

[Jocko]

Hi swamswam_h,

the samba server isn't accessible from my main computer

You must set the workgroup in the lan setup menu : Put in the same workgroup than your main computer.

I had enabled the FTP server but I couldn't get anywhere when logged on

You must enable the FTP access for each share in the share menu. You must set also access for the user account used as login.
I advice you to read the FTP Help page

[fvdw]

Kernel 6: System boots normally. Everything seems ok.

I'm reading this page now: http://www.rigacci.org/wiki/doku.php/do ... d2_network
The board in the D2_network is different from the one in the EdMiniV2. Although there are many, many similarities.
I just remembered something else: the original lacie firmware had a blue powerled with blue (off=disk-read activity?) and a red led for disk-write activity. Is the 'patch' that is proposed on this page also possible on the plugout software to enable the red led? (perhaps blue = power, red = disk activity of any kind)?

So both kernels you sent me are bootable. How do I proceed now? Are there any other things I can test, any patches possible?

and with this kernel can you set gpio 24 or not ?
If not then I have run out of options for the time being regarding power down

ps when you set the trigger to ide-disk, does the ble power led now flicker with disk activity and is it on when there is no disk activity ?

[swamswam_h]

Jocko: The SMB server and users were configured and running for days without problems. Today it rebooted four times - with different kernels - and I could not connect anymore to upload a different kernel. A reboot of the computer might work, but it cannot be rebooted now (a huge que is running).

[swamswam_h]

Nope... this kernel has exactly the same output as the others. GPIO 24 cannot be set.
root@LACIE_NAS:/sys/class/gpio # echo 24 > /sys/class/gpio/export
root@LACIE_NAS:/sys/class/gpio # echo out > /sys/class/gpio/gpio24/direction
-sh: can't create /sys/class/gpio/gpio24/direction: nonexistent directory

LED is working perfectly (one color only). Lit when power is on and flashing with disk activity (enabled through 'echo ide-disk > trigger' in /sys/class/leds/power:blue)!!! :applause
Thank you very much Fvdw!

Any ideas on how to enable the red led?

[swamswam_h]

I was wondering about this:
The system software (original lacie) sets the eeprom status bit to enable a reboot or halt. After that is resets the unit and Uboot boots up again, checks the status in the eeprom and turns off power or reboots. Right? Or did I get it all wrong... But if this is so, shouldn't the 'magic bullet' to our problem be incorporated in the lacie uboot source (which is free, available and heavily modified by lacie)??