search

qmk / qmk_firmware

Open-source keyboard firmware for Atmel AVR and Arm USB families
https://qmk.fm
GNU General Public License v2.0
18k stars 38.69k forks source link

[Bug] Waking up computer from sleep results in keyboard not working anymore #19192

Open kev31w opened 1 year ago

kev31w commented 1 year ago

Describe the Bug

Sometimes, when waking up w10 computer from sleep, my Nascent Keyboard does not register. Unplugging the keyboard, via host or device does not fix this issue. This is inconsistent for me and does not happen every time. I have tried 3 different cables that have worked with other keyboards without exhibiting this behavior.

However, I'm able to reproduce this behavior fairly consistently by doing the following steps.

1) connect keyboard and ensure it's working 2) set computer to sleep 3) wake up computer 4) try to login // if it works proceed to step 5 5) unplug device connection. re plug again. The keyboard no longer sends proper input. No windows sound chime indicating device is connected.

Left in a "stuck state" where i have to do a combination of restart, unplug host/device, switch cables, to get keyboard working again.

In general, unplugging device usbc connection seems to lead to keyboard not being registered afterwards. Sometimes reconnecting fixes it

Possibly separate but related issue:

Sometimes when I unplug, change cables (using a cable that was connected to a different board), re plug my keyboard, it also scrambles my entire keyboard's key mapping. Verified this in VIA and https://config.qmk.fm/#/test/

Keyboard Used

Nascent

Link to product page (if applicable)

No response

Operating System

windows 10

qmk doctor Output

Ψ QMK Doctor is checking your environment.
Ψ CLI version: 1.1.1
Ψ QMK home: C:/Users/kchow/qmk_firmware
Ψ Detected Windows 10 (10.0.19045).
Ψ Git branch: master
Ψ Repo version: 0.19.0
Ψ - Latest master: 2022-11-28 00:46:40 -0500 (d27b852fcc) -- new keyboard rb1 (#18164)
Ψ - Latest upstream/master: 2022-11-28 00:46:40 -0500 (d27b852fcc) -- new keyboard rb1 (#18164)
Ψ - Latest upstream/develop: None
Ψ - Common ancestor with upstream/master: 2022-11-28 00:46:40 -0500 (d27b852fcc) -- new keyboard rb1 (#18164)
Ψ - Common ancestor with upstream/develop: None
Ψ All dependencies are installed.
Ψ Found arm-none-eabi-gcc version 10.1.0
Ψ Found avr-gcc version 8.5.0
Ψ Found avrdude version 7.0
Ψ Found dfu-util version 0.11
Ψ Found dfu-programmer version 0.7.2
Ψ Submodules are up to date.
Ψ Submodule status:
Ψ - lib/chibios: 2022-09-18 10:01:17 +0000 --  (0e9d558b5)
Ψ - lib/chibios-contrib: 2022-10-03 18:09:41 +0200 --  (bb8356fb)
Ψ - lib/googletest: 2021-06-11 06:37:43 -0700 --  (e2239ee6)
Ψ - lib/lufa: 2022-08-26 12:09:55 +1000 --  (549b97320)
Ψ - lib/pico-sdk: 2022-09-19 18:02:44 +0200 --  (8d56ea3)
Ψ - lib/printf: 2022-06-29 23:59:58 +0300 --  (c2e3b4e)
Ψ - lib/vusb: 2022-06-13 09:18:17 +1000 --  (819dbc1)
Ψ QMK is ready to go

Is AutoHotKey / Karabiner installed

Other keyboard-related software installed

No response

Additional Context

No response

drashna commented 1 year ago

Disable console and command and see if that helps.