Showing 1 of 2440 conversations about:
Foreman
38
May 11, 2016
bookmark_border
Is anyone having any issues regarding their Rev 1.1d keyboards not working after you place your computer to sleep? After I sleep my computer I need to disconnect and then reconnect my keyboard in order for it to be recognized by my pc. Does anyone have a fix for this?
May 11, 2016
moazzamk
74
May 11, 2016
bookmark_border
I think someone else had asked the same question. Have you tried this :
- Put computer to sleep - Wake the computer up using your mouse - Type on Infinity Ergodox
Does that work for you?
Original Ergodox doesn't wake the computer up from sleep. I am guessing Infinity one doesn't either (unless you re-plug it like you have been doing). However, if the computer is already up then there is no issue.
In some instances I have been able to wakeup my Macbook from sleep using Ergodox if the computer JUST went to sleep but not after some time. I don't think this was ever fixed
May 11, 2016
Foreman
38
May 11, 2016
bookmark_border
No, it doesnt. The ergodox needs to be replugged in entirely in order to be recognized by my computer at all.
May 11, 2016
moazzamk
74
May 11, 2016
bookmark_border
Oh, then I don't know what's wrong. I keep Ergodox hooked to my Macbook and I never have to re-plug it. Very rarely, it does lose connection and I replug it. You should contact Massdrop support and for a replacement.
On another note: The previous Ergodox I had ordered doesnt work at all, so I have to contact Massdrop support too, lol. I started building it recently even though I had ordered it a long time ago. The drop was a while ago though so not sure if they will replace it.
May 11, 2016
sieroaoj
4
May 11, 2016
bookmark_border
In my ergodox from (last shipment) if I sleep my mac-mini and wake it with the mouse it works, but if I reboot or shutdown and power-on, the ergodox blocks it-self after a little (it works for 1 ou 2 seconds and blocks), after a while my mac-mini starts looking for bluetooth keyboards, showing the Bluetooth Setup Assistant screent. While blocked If I disconnect and reconnect the ergodox usb cable it starts working again. No other issues found, already loaded a new configuration and other than that works great (without the stabilizers)
May 11, 2016
domesdkg
9
May 12, 2016
bookmark_border
I'm having similar issues. The keyboard will often not be recognized at the BIOS password or bitlocker screens, and if I leave it untouched with the screen locked for longer periods of time it will also require a re-plug. I only noticed the issue recently so I'm wondering if it's related to more recent firmware... but it could be a coincidence.
May 12, 2016
Madam
23
May 12, 2016
bookmark_border
Out of curiosity, is USB selective suspending enabled in your computers power settings settings?
May 12, 2016
domesdkg
9
May 13, 2016
bookmark_border
Woooooow. I'm impressed. Mine was indeed enabled, have disabled and will see if it helps things. Great suggestion.
May 13, 2016
Foreman
38
May 13, 2016
bookmark_border
As a matter of fact it was, however after adjusting the settings just now I've found that there is no difference and that the bug still persists. I'm going to go through my BIOS settings and see what I can find.
May 13, 2016
Foreman
38
May 13, 2016
bookmark_border
So, it looks like I was able to fix my issue by enabling xHCI and EHCI legacy compatibility in my BIOS. While it wont wake the computer from sleep it will work as normal once the computer is up!
Now I just need to figure out how to power off the LCD when it sleeps and I'll be golden.
May 13, 2016
deletarus
23
May 13, 2016
bookmark_border
I had this issue with the stock firmware that came on the keyboard, the initial fix for me was to re-flash with a more recent firmware and the issue was resolved. However, yesterday I decided to update my key layout and flashed with the most recent firmware downloaded from the configurator and it seems the issue has returned (at least when I came back into work this morning the keyboard was in an unrecognized state after waking my computer and I had to re-plug for it work.
@HaaTa has something changed recently in the newest revisions of the firmware that may have re-introduced this bug? The working version of the firmware was downloaded on 4/26 or 4/27 (I have 2 on my desktop and I'm not sure which it was) and the one that seems to have re-introduced it for me was download on 5/12.
May 13, 2016
Foreman
38
May 13, 2016
bookmark_border
I actually had the issue return for me even after the BIOS fiddling, and reflashed both sides of my dox independently, which seems to have fixed the issue.
May 13, 2016
phoible
123
May 14, 2016
bookmark_border
I'm having this issue with firmware I built from the github repo (I believe I downloaded it late last week).
May 14, 2016
deletarus
23
May 16, 2016
bookmark_border
I flashed both halves of my dox independently as well and with the new firmware, the issue is there. Last time I had this happen @HaaTa was quick to respond. Maybe he's busy? But I use this at work and I can't have it mess up every time I let my computer go to sleep or have to restart. I also noticed that with this same version of the firmware from the configurator, the LED support seems to be... different... from the last. When I plug in the keyboard in, one side will light up, then a couple of seconds later the other half will light. With the previous firmware I had they would both light nearly instantly. Also, the LED off, + and - seem not to be recognized at times (like most of the time...). It seems some bugs have certainly worked their way in...
May 16, 2016
HaaTa
558
Input Club
May 16, 2016
bookmark_border
Sorry, I get busy sometimes....
Yes, I've updated the USB firmware module recently to better respond to power saving requests from the OS. Turns out that using the full power right away...is, well bad. You have to let the OS tell you that it's ok. Then, then interconnect has to initialize before allowing full power usage mode (there is an added bonus that you know that everything is all working and ready to go when the slave side leds start working.. :P). Unfortunately, there may be some corner case bugs, so I hope to add a KLL option (and perhaps to the configurator as well) to disable USB low power mode requests from the OS.
As for the restart, not working thing. I've been getting more reports, but more importantly, I think I may have a reproducible setup now. In theory, once I can capture the request on my USB analyzer I can write/fix the code that deals with this somewhat obscure USB request.
Also, please, please, please check/file bugs here -> https://github.com/kiibohd/controller/issues MD discussions are way to annoying to search, respond, and remember all the details. You can also subscribe to the bug to get notifications when stuff happens :D
May 16, 2016
View Full Discussion