New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] ymdk_np21 works unreliably after update #15400
Comments
So I did some However, it's impossible to build image with Also still happens as of 0.19.10 Flashed ps2avrGB and kb doesn't do that with this firmware, which was what they had originally. |
I finally got some time to debug this, built @noroadsleft it looks like your commit and seems rather large |
I have a commitment this morning, but I should be able to investigate this in the afternoon. (It's 8:21 AM local time right now.) |
I mean, I can wait a bit more since I was able to cope with that for more than a year, lol. It's not an urgent matter at all. |
Considering that the atomic block commit may be the issue, does adding |
Yes, with this workaround I no longer see the issue but I don't think that this is a fix if users need to add this themselves for each board. This bug is rather obscure so it is kinda tricky to figure this out. |
I used some older version of QMK for probably a year or so and decided to upgrade recently.
Everything worked without issues before update but then suddenly I have multiple problems with QMK.
I didn't pay attention to which version was working because I didn't think I could get malfunctioning keyboard after update.
Describe the Bug
C(KC_F13)
,C(KC_V)
and both tapdance actions forACTION_TAP_DANCE_DOUBLE(S(KC_F16), C(S(KC_F16)))
are ones that I use often) it can sometimes be ignore.I don't see any correlation with time between keypresses in any case.
A(KC_F4)
and it could just happily wipe out all the windows I have.System Information
qmkfm/qmk_cli
containerqmkfm/qmk_cli
containerNo
Additional information
config.h diff
rules.mk diff
dmesg
I also looked to dmesg and I see messages like that:
usb 1-4.3: reset low-speed USB device number 12 using xhci_hcd
This device is indeed that keyboard:
This keyboard plugged in USB3.0 hub which is plugged into USB3.0 port. I cannot test it with 2.0 port because I don't have neither USB2.0 ports nor USB2.0 hub.
The text was updated successfully, but these errors were encountered: