-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kobo libra crash and reboot after launch on kfmon #13
Comments
Hi, thanks for creating an issue. I'm afraid I can't do that much with those messages alone. Sorry to hear your e-reader had to hard reset, that should never happen.
|
Hello,
That's why I had to hard reset my e-reader and loose all the crash reports (unfortunatly I didn't try to get them using telnet...) As you said, I don't have enough information to help you track this issue and I don't think I will try to modify my kobo again. Even if it perfectly works now after the hard-reset. Maybe it could have been worse idk. Sorry to not be able to help you more |
As of right now, you shouldn't expect the KFMon script to run properly on current FW versions (c.f., #12). I'm not quite sure how bad it behaved without the fixes, but at worst a hard-reboot would have fixed it. There's a near-zero chance for anything to have any lasting impact on either Nickel itself or the actual hardware. |
Hello,
First of all, thank you for your amazing tool.
I have an issue when I try to start inkvt from kfmon it totally reboot my ereader.
Sometimes it writes "enabling wifi" when I run it just after the boot. The other times it doesn't have the time to write it.
This are the logs from KFMon:
Spawned process 9861 (/mnt/onboard/inkvt.png -> /mnt/onboard/.adds/inkvt/inkvt.sh @ watch idx 3) ... Reaped process 9861 (from watch idx 3): It exited with status 1. [PID: 9931] KFMon is already running (PID: 191)!
And then my kobo libra H2O reboot.
I was trying to search the crash.log of your program but unfortunately my ereader had to be hard reset.
sorry for my poor english, I'm french
The text was updated successfully, but these errors were encountered: