Matt M.

This still appears to be an issue in `2.7.0`. Running into the same error that @com30n [reported above](https://github.com/hashicorp/terraform-provider-helm/issues/892#issuecomment-1167129383).

Hello! Just chiming in with another possible use case for this feature: reliably installing Azure VM extensions (`azurerm_virtual_machine_extension`). We have multiple VM extensions that we would like to install after...

I'm running into this issue as well (Viper Ultimate Wireless, OpenRazer `3.3.0`) on Arch Linux, though for whatever reason my notification says 3% when I start up instead of 1.2%....

[Here you go!](https://gist.github.com/9numbernine9/ed5fa8d0b3f20a537c8cdd1b1e5cf58f) Had to restart a few times before it happened, but it did eventually.

Added the patch, rebuilt the module, installed, rebooted, and saw these lines: ``` [ 10.738481] razermouse: Response doesn't match request. Start Marker: 02 id: ff Num Params: 07 Reserved: 04...

@z3ntu I would love a fix for workaround! With that said you're under no obligation to provide one in a timely fashion, and I suspect the fix might be non-trivial...

Sounds reasonable. Whenever the patch is ready I will do my best to help test it if you need ~~victims~~ volunteers.

I tweaked the patch slightly to add a `printk` before the value of `response_report` gets set inside the `if` statement, but I don't think the fix worked: ``` [ 3.872678]...

> Lol now we're getting a different response back. Fun! > > Does this "Response doesn't match request" error also appear in dmesg during normal usage, e.g. changing settings in...

It's a hack, but I think it works. :sweat_smile: My source now looks like this: ``` response_report = razer_send_payload(usb_dev, &report); // On Viper Ultimate Wireless we sometimes get mismatching response...