New Installtion on 5Big - Trouble adding disks

[Jocko]

Hi

@fvdw

Code: Select all

lrwxrwxrwx  1 root root 22 2020-09-08 23:40 /usr/sbin/buttonsd -> /bin_cab/buttons-nwsp2

So it seems the 5big1 button is not yet compiled or we forgot to include it in the last fw version :scratch
See:https://plugout.net/viewtopic.php?f=30&t=3369&p=27586#p27529

[fvdw]

The buttons-nwsp2 daemon should also work with 5big1 as the key defintion is the same for front push button as the back push button in nwsp2. We need to check if an event is detected when pressing the front button. I will post a test program later today.

[fvdw]

attached a program evtest (unpack the zip archive).

Put this file in the fvdw shared folder, connect via ssh and make the file executable and run the program

Code: Select all

cd /direct-usb/fvdw
chmod 755 evtest
./evtest


It will ask you to select device event number, enter 0
Now it will wait for input
Press and release the front button and see if you get output.
Post the output here

I would expect output like this (example)

Code: Select all

root@fvdwsl-5big2:/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)
  Event type 5 (EV_SW)
    Event code 1 (SW_TABLET_MODE) state 0
    Event code 2 (SW_HEADPHONE_INSERT) state 1
Properties:
Testing ... (interrupt to exit)
Event: time 1599673193.325871, type 1 (EV_KEY), code 116 (KEY_POWER), value 1
Event: time 1599673193.325871, -------------- SYN_REPORT ------------
Event: time 1599673193.463494, type 1 (EV_KEY), code 116 (KEY_POWER), value 0
Event: time 1599673193.463494, -------------- SYN_REPORT ------------



to exit the program press CTRL+C

[mattenwright]

Tried this a few times, and kept getting the following:

Code: Select all

root@LaCie5Big1-fvdw:/share/1100/fvdw # ./evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
Select the device event number [0-0]: 0
evtest: No such device or address
root@LaCie5Big1-fvdw:/share/1100/fvdw #


It doesn't seem to find the front button. I restarted the NAS and I get the same results.
As a note (I don't think it will have any impact), I do have 1 drive listed as failing at the moment.

[fvdw]

Mmm....seems driver gpio-keys is not loaded. I have to check the kernel setup and if this driver is not included, recompile the kernel

[fvdw]

Attached a new kernel with gpio_keys driver enabled.
You can test it using fvdw-sl console and choose option load external kernel. To be able to select the new kernel unpack the zip archive and put the file in the tftp folder of the fvdw-sl console on your PC.

Note 1.
The external kernel load works only for one boot. This is for testing if the kernel works ok we can copy it to the HDD to have it loaded at each boot without need to use fvdw-sl console. The advantage of this procedure is if the kernel fails to run you just have to reboot your 5big1 to bring up the previous kernel.

Note 2.
If this kernel runs oke we need to replace the kernel modules for the kernel as well.
If this new kernel loads and runs some modules of the previous kernel may not work or load as changes are made in the kernel code however to test gpio-keys drives it should not be a problem.

So after new kernel is running do following
a. check if we are running the new kernel

Code: Select all

uname -a

Post output

b. kill the buttons-nwsp2 daemon

Code: Select all

killall -9 buttonsd

required to be able to run evtest and see if buttons activity is detected. With a running buttons daemon and a working gpio driver the nas will reboot ;)

c. start evtest program as described in earlier post and post output

d. after fishing evtest, run dmesg command

Code: Select all

dmesg

and post output this to see if the new kernel has reported any error during loading

[Jocko]

Hi mattenwright,

Are you having trouble performing what fvdw requested?

[mattenwright]

I attempted to load the kernel via the fvdw-sl console (v 6.0), using the "External Kernel, load and start" option on the action menu.

It appears to load onto the NAS correctly, tftp shows the upload progress, and I get an OK at the end on the command window. After the "OK" in the command window, and the closure, the lights on the NAS behave as if everything has loaded. However I am unable to get the NAS to respond to anything on the network, no SSH, no ping, nothing at all.

I am using the same machine that I initially loaded the firmware on, and I have verified there are no firewall issues on the machine.

Let me know if I'm doing anything wrong or I should go about things differently.

[Jocko]

So wait fvdw for next step but an additional information maybe useful:
After a regular boot, go to the setup menu (other settings), and select the option LED off at boot.
Then stop the nas, and try again to load the new kernel version. If the LED are off after the booting sequence that means the init script is loaded and not on the other case.

[fvdw]

This might be a kernel size issue. On 5big1 a kernel of max size of 2064384 should be used, if bigger then the bootloader will fail to load the kernel because it will overwrite the bootloader.
Now the new kernel is 2044704 bytes, therefor I expected that it could be loaded. :scratch
The standard kernel is 2031616 bytes, so slightly smaller. To eliminate doubt on size I will adapt kernel a bit to reduce size below the standard kernel and you can try again.

PS did you try when the new kernel #12 was loaded boot finished if the nas reacts on the front push button ?