Yay, guinea pigs!
.
Jokes aside, yeah, nothing jumps out from the logs, so it's indeed not crashing, which would point to the framebuffer handling code not doing things right...
So, a couple questions for those of you who have a shell access:
* Does
FBInk actually manage to print something on your screen? (And do you get an ioctl error or not when you try).
* It's strace time! Download this
strace binary, run it like this, and move around a bit in the (Kindle) UI (a bit of everything would be helpful, if you can remember the order in which you did things, that's even better: something like Homescreen, Menu, Library, moving around a bit in the Library, Opening a book, moving around in the book, opening a couple menus in a book).
Code:
./strace -fitv -e trace=ioctl -p $(pidof awesome)
(Make sure you're calling this strace binary (i.e., ./), the one bundled in USBNet and in your $PATH will probably crash on the first screen update
).
^C once you're done, and send me the output
.