New Installtion on 5Big - Trouble adding disks

[fvdw]

attached kernel #32 and the fvdw versios of gpio_keys module (v12)

Please load the kernel and insert this module (the module goes into /lib/modules/3.14.2
Before loading it give the command

Code: Select all

depmod

and after that

Code: Select all

modprobe gpio-keys

If it installs correctly perform the test with the evtest program and press and release the front button

[mattenwright]

All installed correctly, and I ran the evtest program with the following results:

Code: Select all

root@LaCie5Big1-fvdw:/direct-usb/fvdw # ./evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:      gpio-keys
Select the device event number [0-0]: 0
Input driver version is 1.0.1
Input device ID: bus 0x19 vendor 0x1 product 0x1 version 0x100
Input device name: "gpio-keys"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 116 (KEY_POWER)
Properties:
Testing ... (interrupt to exit)
Event: time 1604520230.819246, type 1 (EV_KEY), code 116 (KEY_POWER), value 1
Event: time 1604520230.819246, -------------- SYN_REPORT ------------
Event: time 1604520230.932210, type 1 (EV_KEY), code 116 (KEY_POWER), value 0
Event: time 1604520230.932210, -------------- SYN_REPORT ------------
Event: time 1604520250.004400, type 1 (EV_KEY), code 116 (KEY_POWER), value 1
Event: time 1604520250.004400, -------------- SYN_REPORT ------------
Event: time 1604520250.117373, type 1 (EV_KEY), code 116 (KEY_POWER), value 0
Event: time 1604520250.117373, -------------- SYN_REPORT ------------
Event: time 1604520251.153155, type 1 (EV_KEY), code 116 (KEY_POWER), value 1
Event: time 1604520251.153155, -------------- SYN_REPORT ------------
Event: time 1604520252.463803, type 1 (EV_KEY), code 116 (KEY_POWER), value 0
Event: time 1604520252.463803, -------------- SYN_REPORT ------------
^Croot@LaCie5Big1-fvdw:/direct-usb/fvdw #



The front button now appears to work correctly!! YAY Wonderful news

Do you know if the power switch also is on the GPIO or is that somewhere else?

[fvdw]

Oke thank you for testing, next step will be integrating the driver in the kernel instead as module and adapting the button daemon.
About power switch, yes there are gpio pins availble but integrating them in the kernel is useless to my opinion. As the same can be accomplished with the push button, switching off and rebooting. Also I expect when nas is running the switch is in on position. When moving it to off what happens now? Can you test that. If nothing happens and nas keeps running the off position could be integrated in the firmware to switch off the nas.
Switchting on with power switch will always be controlled by the bootloader. As no kernel is running on that moment

[mattenwright]

Also I expect when nas is running the switch is in on position. When moving it to off what happens now? Can you test that.

The NAS is running with the switch in the ON position, and from my testing, if I switch it off during the countdown to auto boot, it will power off the NAS.
As the NAS is booting, there is no effect from the power switch at all.
After the NAS has been booted and the gpiokeys module has been loaded, there is also no effect on the NAS, and nothing shows on the serial output.

I would concur that there's really no specific reason to integrate the power switch into kernel if the tasks can be performed from the front button. I just wasn't sure if there was something there previously, or it was just something that had to be phased out from an older revision.

[fvdw]

Oke.
We wiil test with adapted buttons daemon to see what happens if the nas is shuttdown using front push button and if it can be powered on again by pushing front button

Ps I am busy with some other things so it can tske a few days before I have time for this

[mattenwright]

As long as it can be shutdown or restarted using the front button, that's fine, it does not have to be powered on using the front button.

No worries at all on the delay, I've also been dealing with quite a bit as well :-)

[fvdw]

attached an adapted buttons daemon specific for 5big1 that should work with this gpio-keys driver
Put in the root folder of the system (like evtest)

load the kernel en gpio-keys module and after that the daemon

Code: Select all

/buttons-5big1

If it is loaded press - hold -release the front button
press+holding less then 5 seconds initiate a reboot,
press+holding more then 5 seconds a poweroff.

[mattenwright]

The buttons executable worked exactly as described.
The reboot behavior was exactly that, it ran perfectly.
The shutdown behavior was quick, all the disks stopped as they should and everything was unreachable after a few seconds.
The system did remain powered on and did not respond to the power switch, but as we discussed, that's totally fine as I know the system is off after all the disks click, and a few moments.

Well done and thank you again!

[fvdw]

oke thank you for testing.
I Have question about this remark you made

...The system did remain powered on and did not respond to the power switch, but as we discussed, that's totally fine as I know the system is off after all the disks click, and a few moments.

Do you mean with "remain powered on" that the front led is still on after the shutdown ? And that it can be booted again after pressing the front button shortly ?
Or does the front led goes out as well and system can be brought back to live with pressing front button shortly ?

[fvdw]

attached kernel #33
This one has the modified gpio_keys driver included so no need anymore to load the module
Also some clean up is done to remove not required print statements for normal operation.

Please test if it loads and that the buttons daemon works with this kernel

Note you might have to kill the buttons-nwsp2 daemon firts as it will be loaded during boot now that the gpio-diver is active.
We will change the boot scripts later

Code: Select all

killall -9 buttonsd

After that load the buttons-5big1 driver