k65 lux rgb Slight flicker problem

When I first used the unofficial ckb GNU/Linux driver, I noticed flicker sometimes on the RGB lighting on some buttons. I decided to plug in the damn thing into a relative's garbage Windows PC, and lo and behold- it still happens once in a while, when there is animations happening (static-only pretty much works fine). Is there any reason for this? Is it firmware? Or is it hardware? My OCD is bugging me about this. :[pouts:

EDIT: just in case anybody asks this, on the relative's PC I'm using CUE 2.7.78.

EDIT 2: I also even held the ESC key before and a little after plugging in. No dice.

EDIT 3: also using the newest firmware, 2.05.

Its due to the USB controller dropping packets. I would check for chipset, and USB controller driver updates.

Except this has happened on 2 machines (my laptop, which is the specs I listed, with exceptions, and the relative's PC). Also, my CPU drivers on my laptop should be on the newest version anyways (It's Linux on the laptop, Linux has drivers built-in it, plus the laptop has a Intel CPU, good Linux support), so I don't know if it's that. Is there any way to diagnosis this on both Windows and Linux?

EDIT: I hope you're right though, I really don't want to go through an RMA process...

EDIT 2: I guess, looking at your FAQ, that I'll have to update my BIOS?! Well, I guess I might have to... Let me see if you're right first though. I'll try looking up logs on Windows for example (CUE, as you said in your FAQ, has logs, sadly I don't know about ckb).

Except this has happened on 2 machines (my laptop, which is the specs I listed, with exceptions, and the relative's PC). Also, my CPU drivers on my laptop should be on the newest version anyways (It's Linux on the laptop, Linux has drivers built-in it, plus the laptop has a Intel CPU, good Linux support), so I don't know if it's that. Is there any way to diagnosis this on both Windows and Linux?

 

EDIT: I hope you're right though, I really don't want to go through an RMA process...

 

EDIT 2: I guess, looking at your FAQ, that I'll have to update my BIOS?! Well, I guess I might have to... Let me see if you're right first though. I'll try looking up logs on Windows for example (CUE, as you said in your FAQ, has logs, sadly I don't know about ckb).

Corsair does not support Linux or CKB, you will have to talk to MSC about that. For CUE the logs will show timeouts and dropped packets if its a USB controller issue. If it is a USB controller issue a RMA won't help.

http://pastebin.com/mwzRzFNp

Here's a log from CUE.

EDIT: In particular, this is interesting:

2016-12-19T16:37:39 I cue.dev: Buffer write failed, 1. request timed out for K65 LUX RGB

2016-12-19T16:37:43 I cue.dev: Buffer write failed, 1. request timed out for K65 LUX RGB

2016-12-19T16:37:43 I cue.dev: Buffer write failed, 1. request timed out for K65 LUX RGB

2016-12-19T16:37:44 I cue.dev: Buffer write failed, 1. request timed out for K65 LUX RGB

2016-12-19T16:37:45 I cue.dev: Buffer apply for Green failed. request timed out for K65 LUX RGB

2016-12-19T16:37:49 I cue.dev: Buffer apply for Green failed. request timed out for K65 LUX RGB

2016-12-19T16:37:51 I cue.dev: Buffer write failed, 1. request timed out for K65 LUX RGB

2016-12-19T16:37:52 I cue.dev: Buffer write failed, 1. request timed out for K65 LUX RGB

2016-12-19T16:37:52 I cue.dev: Buffer write failed, 1. request timed out for K65 LUX RGB

2016-12-19T16:37:54 I cue.dev: Buffer write failed, 1. request timed out for K65 LUX RGB

2016-12-19T16:37:55 I cue.dev: Buffer write failed, 1. request timed out for K65 LUX RGB

2016-12-19T16:37:56 I cue.dev: Buffer apply for Blue failed. request timed out for K65 LUX RGB

2016-12-19T16:37:56 I cue.dev: Buffer write failed, 1. request timed out for K65 LUX RGB

2016-12-19T16:37:57 I cue.dev: Buffer write failed, 1. request timed out for K65 LUX RGB

Yea, it looks like the controller is not correctly passing the packets between the keyboard and CUE.

If you know which USB ports are intel chipset controlled i would try those. If that still doesn't work, contact Corsair Support. They might have a solution for your issue.

Yea, it looks like the controller is not correctly passing the packets between the keyboard and CUE.

 

If you know which USB ports are intel chipset controlled i would try those. If that still doesn't work, contact Corsair Support. They might have a solution for your issue.

This PC I was using it on (for CUE/Windows) is (formerly mine) a weak-*** pre-built Gateway with an AMD E1-1200 APU. Ouch. DX

This PC I was using it on (for CUE/Windows) is (formerly mine) a weak-*** pre-built Gateway with an AMD E1-1200 APU. Ouch. DX

yea.... that might be the problem lol. AMD isnt know for great chipsets. I mean AM3+ still doesnt have PCIE 3.0 support. RPI. Try it in a modern intel computer on a intel controlled port. It should run fine.

yea.... that might be the problem lol. AMD isnt know for great chipsets. I mean AM3+ still doesnt have PCIE 3.0 support. RPI. Try it in a modern intel computer on a intel controlled port. It should run fine.

Except this isn't even their FX or high-end APUs. this is their bottom-bin, 2012 ****. 2 "Cores" @ 1.4 GHz. Basically like a mid/low end tablet. Hell, my school Chromebook has better specs. :P