Hi there,
I am running a script to show a screensaver/wordclock on my kobo. The script is essentially a loop that displays an image on the kobo an then sends it to sleep via rtcwake. I'm connected to the kobo via telnet (Wifi) and start the script using nohup.
Structure of script:
Kill Kobo-Stuff (nickel etc.)
Shutdown Wifi to save energy
Looping the following
Do something
Send device to sleep (rtcwake -m mem -s 180)
repeat
This runs nicely for some time. But then the script unexpectedly stops. In this case (sent to sleep 180s) it breaks after about half a day. It appears that it breaks after a number of cycles rather than time (when increasing the time sent to sleep it runs much longer).
Most frequently the script stops in front of the rtcwake command but sometimes in the middle of the "do something"-part.
Any ideas what causes the script to stop and how to further debug?
Kind regards
KristianR
PS:
What I tried so far:
- I echoed some debuginformation like running processes, battery-level, date vs hwclock, free memory - nothing obvious to me.
- enabled syslog via "devmodeon" and selecting all logging options. No syslog gets written to .kobo-Directory unless I hit save log (but this is not accessible since in the case of stopped script I can't access the menu). After resetting and saving the log, this log does not contain information of the events before the reset
- dmesg also only shows information after the reset
- tried to establish access via usbnet to connect after script stops. But was not able to get it running - I'm getting following error "insmod: can't insert '/drivers/mx6sl-ntx/usb/gadget/arcotg_udc.ko': invalid module format"
I am running a script to show a screensaver/wordclock on my kobo. The script is essentially a loop that displays an image on the kobo an then sends it to sleep via rtcwake. I'm connected to the kobo via telnet (Wifi) and start the script using nohup.
Structure of script:
Kill Kobo-Stuff (nickel etc.)
Shutdown Wifi to save energy
Looping the following
Do something
Send device to sleep (rtcwake -m mem -s 180)
repeat
This runs nicely for some time. But then the script unexpectedly stops. In this case (sent to sleep 180s) it breaks after about half a day. It appears that it breaks after a number of cycles rather than time (when increasing the time sent to sleep it runs much longer).
Most frequently the script stops in front of the rtcwake command but sometimes in the middle of the "do something"-part.
Any ideas what causes the script to stop and how to further debug?
Kind regards
KristianR
PS:
What I tried so far:
- I echoed some debuginformation like running processes, battery-level, date vs hwclock, free memory - nothing obvious to me.
- enabled syslog via "devmodeon" and selecting all logging options. No syslog gets written to .kobo-Directory unless I hit save log (but this is not accessible since in the case of stopped script I can't access the menu). After resetting and saving the log, this log does not contain information of the events before the reset
- dmesg also only shows information after the reset
- tried to establish access via usbnet to connect after script stops. But was not able to get it running - I'm getting following error "insmod: can't insert '/drivers/mx6sl-ntx/usb/gadget/arcotg_udc.ko': invalid module format"