We're getting somewhere!
The trigger file in the /sys/class/leds/power:blue directory had several items in it.
Default was: [none] nand-disk timer ide-disk heartbeat gpio default-on
I searched the web how to change this file and found:
- Code: Select all
echo ide-disk > trigger
This did the trick and changed the file to: none nand-disk timer [ide-disk] heartbeat gpio default-on
The led is now flashing to the disk activity. The original Lacie firmware had this light on, always on, and flash with disk activity. I'm not sure, nor do I know how, if more 'actions' can be combined to be the trigger for the led. Or make the led-action reverse (so always on and disk activity = off)
I think that:
default-on = led always on (power)
ide-disk = disk activity
heartbeat = server load?
nand-disk = ...
timer = ... (shutdown timer for instance? The lacie firmware blinked the led when in shutdown procedure).
gpio = ...
Thanks for the new kernel. Wow,I thought you said you didn't have time to do all this! It is GREATLY appreciated :thumbup .
I have (i'm pretty sure) followed the instructions and issued a reboot. And i'm not sure, but i think it is stuck somewhere very early in the boot process <- read: "it won't boot". Upon powering it up, the fan stays on and the led is lit, exactly as it does right before it used to load the old kernel (and immediately dimmed the led). So I guess that means the firmware can't boot the kernel and is still somewhere waiting for some user interaction (serial console I guess? Now where is my logic level converter to hook it up to my serial port?). So this weekend I will reinstall the old kernel and have another go (to check if I made a mistake somewhere). You'll be hearing from me. And again: so far, your support has been amazing. Thanks.