Kobo libra crash and reboot after launch on kfmon

llandsmeer / inkvt

Experimental VT100 terminal emulator for Kobo e-readers

GNU General Public License v3.0

39 stars 5 forks source link

Kobo libra crash and reboot after launch on kfmon #13

Open Onion2222 opened 3 years ago

Onion2222 commented 3 years ago

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

llandsmeer commented 3 years ago

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.

Do you known which firmware version you have (7?)
Did you have other mods installed that might have interfered?
As I understand it, you just clicked the icon in Nickel and then it crashed?

Onion2222 commented 3 years ago

Hello, Sorry for my late answer:

About the firmware, I have mark 7. It recently updated to 4.24.15676, I had the version just before when I had the problem
No
When I clicked on the icon in Nickel, sometimes it wrote an error message and then it always rebooted. However, when it rebooted I had some troubles using the touchscreen and the display.

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. I think that the problem come from the installation kfmon I certainly did something wrong during it or maybe I modified something I shouldn't in the linux embedded system.

Sorry to not be able to help you more

NiLuJe commented 3 years ago

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.