-
-
Notifications
You must be signed in to change notification settings - Fork 40.7k
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
AT90USB646 keyboard crashes when pc off #6726
Comments
5585 is a completely different issue, as it's an ARM chip, not an AVR. Also, just to make sure, are you on the most recent version of QMK Firmware? We recently updated the LUFA code, and that may be part of the issue. Also, do you know what revision of the PCB that you have? And just to see, could you true adding:
to your config.h and see if that helps? |
Yes, did a full re-clone yesterday just to be sure.
#define NO_USB_STARTUP_CHECK This prevents the crashing issue, but causes some RGB / audio oddities when the PC is both turned on and off. |
Yeah, I figured it might, unfortunately. The Planck Light is also set this way, and probably for the same reason. Specifically, I think there is a bug in the handling for the at90usb chips, right now. |
This seems to have been somewhat fixed in recent versions - the LED's and the Speaker go haywire during boot but the keyboard works when Windows starts. |
I have a similar problem with my atmega32u4 board, kbdfans mkII v2. I think it's related to https://docs.qmk.fm/#/faq_debug?id=problem-on-bios-uefiresume-sleep-amp-wakepower-cycles but even disabling all the mentioned options doesn't fix the issue. Will try NO_USB_STARTUP_CHECK |
This issue has been automatically closed because it has not had any recent activity. |
If I leave my keyboard plugged in when the PC is turned off, the rgb backlight stops animating yet remains on, and the attached speaker constantly beeps until power is removed. This occurs whenever the keyboard is plugged in whenever the PC is turned off. If PC is turned on whilst the keyboard is in this state, the keyboard remains unresponsive, and no keycodes are sent. Defining RGBLIGHT_SLEEP in the config seems to have no effect, and this seems related to bug #5585
System Information
The text was updated successfully, but these errors were encountered: