Closed quantentunnels closed 9 years ago
No usable log output?
And which protocol are you using? LUFA is only actively supported by me.
I used the LUFA stack and I don't know how to get log output concerning this. Maybe I need a keylogger ;)
you can find some log files under /var/log.
Did you try PJRC stack or benblazak's firmware?
same problem with win8. what even worse is the keyboard needs to be unplugged and plugged back in to work again. Is there any way I can retrieve log files from win?
What's your keyboard? Ergodox or others? And Latest firmware with LUFA?
I just confirmed suspend and resume work well on Windows 7 64bit with HHKB and the latest firmware(@4192bce) at least. I don't use this feature daily but it's worked for me since quite a bit ago.
This problem is probably specific to Ergodox port(cub-uanic/tmk_keyboard) which based on a bit old tmk. Try backport from the latest tree of tmk and check suspend code. EDIT: not old now.(cub-uanic/tmk_keyboard@8ecb3e9e442a3a5d7a79ee766af8e36d69d6c1cd)
LUFA suspend code is here, very simple loop. https://github.com/tmk/tmk_keyboard/blob/master/protocol/lufa/lufa.c#L589
I'll close this unless some later unless new info comes up.
So I found some output in kern.log. I can see the suspend but, can't make sense of it.
i merged tmk fork and cub fork in my own repo: https://github.com/lkong/tmk_keyboard The problem Ive mentioned in previous post has been solved. Still need to test the sleeping problem.
Should be fixed now in Ergodox port (cub-uanic/tmk_keyboard).
I'm using Ubuntu 14.04. and whenever I want to go to standby, the machine powers down and then right back up again. When I unplug the keyboard the machine stays in standby mode.
I'm using cubuanics fork on my ergodox (cub-uanic/tmk_keyboard@7c1ed424f1011aa214b9539a083da318050e21b7).