How to get a Corsair gaming keyboard to act like a standard USB HID keyboard












1















I have a Corsair Strafe RGB keyboard which has caused a number of boot and suspend/resume issues on Linux due to some kind of USB error. On recent kernels, the issue has been mostly fixed, but it still hangs the boot by about ten seconds every time.



I went to install OpenBSD earlier today and encountered another eerily familiar boot hang when it was initializing USB devices. By the time it timed out, the OS printed a something along the lines of “disabling usb6” (it scrolled by too fast to read or take a picture of, though). The keyboard backlight then turned off and I could not input text into the installer.



After a bit of research that I dug back up again, I found that it can, in fact be fixed in software (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678477), but this leads me to believe that it is a hardware issue since it requires this patch.



Since the issue affects multiple Linux distros, kernels, and even OpenBSD, I think that there’s something wrong with the keyboard firmware or hardware.



Is there something I can use to solve the issue in some way? I was thinking that I could try jerry-rigging a USB-PS2-USB setup, but am unsure if it would help.










share|improve this question



























    1















    I have a Corsair Strafe RGB keyboard which has caused a number of boot and suspend/resume issues on Linux due to some kind of USB error. On recent kernels, the issue has been mostly fixed, but it still hangs the boot by about ten seconds every time.



    I went to install OpenBSD earlier today and encountered another eerily familiar boot hang when it was initializing USB devices. By the time it timed out, the OS printed a something along the lines of “disabling usb6” (it scrolled by too fast to read or take a picture of, though). The keyboard backlight then turned off and I could not input text into the installer.



    After a bit of research that I dug back up again, I found that it can, in fact be fixed in software (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678477), but this leads me to believe that it is a hardware issue since it requires this patch.



    Since the issue affects multiple Linux distros, kernels, and even OpenBSD, I think that there’s something wrong with the keyboard firmware or hardware.



    Is there something I can use to solve the issue in some way? I was thinking that I could try jerry-rigging a USB-PS2-USB setup, but am unsure if it would help.










    share|improve this question

























      1












      1








      1








      I have a Corsair Strafe RGB keyboard which has caused a number of boot and suspend/resume issues on Linux due to some kind of USB error. On recent kernels, the issue has been mostly fixed, but it still hangs the boot by about ten seconds every time.



      I went to install OpenBSD earlier today and encountered another eerily familiar boot hang when it was initializing USB devices. By the time it timed out, the OS printed a something along the lines of “disabling usb6” (it scrolled by too fast to read or take a picture of, though). The keyboard backlight then turned off and I could not input text into the installer.



      After a bit of research that I dug back up again, I found that it can, in fact be fixed in software (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678477), but this leads me to believe that it is a hardware issue since it requires this patch.



      Since the issue affects multiple Linux distros, kernels, and even OpenBSD, I think that there’s something wrong with the keyboard firmware or hardware.



      Is there something I can use to solve the issue in some way? I was thinking that I could try jerry-rigging a USB-PS2-USB setup, but am unsure if it would help.










      share|improve this question














      I have a Corsair Strafe RGB keyboard which has caused a number of boot and suspend/resume issues on Linux due to some kind of USB error. On recent kernels, the issue has been mostly fixed, but it still hangs the boot by about ten seconds every time.



      I went to install OpenBSD earlier today and encountered another eerily familiar boot hang when it was initializing USB devices. By the time it timed out, the OS printed a something along the lines of “disabling usb6” (it scrolled by too fast to read or take a picture of, though). The keyboard backlight then turned off and I could not input text into the installer.



      After a bit of research that I dug back up again, I found that it can, in fact be fixed in software (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678477), but this leads me to believe that it is a hardware issue since it requires this patch.



      Since the issue affects multiple Linux distros, kernels, and even OpenBSD, I think that there’s something wrong with the keyboard firmware or hardware.



      Is there something I can use to solve the issue in some way? I was thinking that I could try jerry-rigging a USB-PS2-USB setup, but am unsure if it would help.







      linux keyboard openbsd






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jan 11 at 22:50









      Robotic ExtremetiesRobotic Extremeties

      62




      62






















          1 Answer
          1






          active

          oldest

          votes


















          0














          It turns out that the reason that a variety of standards-complaint kernels fail to initialize the keyboard is due to how the backlight pulls more power than the USB 2.0 specification is intended to handle.



          The issue is solved when using a powered USB hub. No PS/2 adapter setup required.






          share|improve this answer























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "3"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1393371%2fhow-to-get-a-corsair-gaming-keyboard-to-act-like-a-standard-usb-hid-keyboard%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            It turns out that the reason that a variety of standards-complaint kernels fail to initialize the keyboard is due to how the backlight pulls more power than the USB 2.0 specification is intended to handle.



            The issue is solved when using a powered USB hub. No PS/2 adapter setup required.






            share|improve this answer




























              0














              It turns out that the reason that a variety of standards-complaint kernels fail to initialize the keyboard is due to how the backlight pulls more power than the USB 2.0 specification is intended to handle.



              The issue is solved when using a powered USB hub. No PS/2 adapter setup required.






              share|improve this answer


























                0












                0








                0







                It turns out that the reason that a variety of standards-complaint kernels fail to initialize the keyboard is due to how the backlight pulls more power than the USB 2.0 specification is intended to handle.



                The issue is solved when using a powered USB hub. No PS/2 adapter setup required.






                share|improve this answer













                It turns out that the reason that a variety of standards-complaint kernels fail to initialize the keyboard is due to how the backlight pulls more power than the USB 2.0 specification is intended to handle.



                The issue is solved when using a powered USB hub. No PS/2 adapter setup required.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Jan 13 at 2:14









                Robotic ExtremetiesRobotic Extremeties

                62




                62






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Super User!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1393371%2fhow-to-get-a-corsair-gaming-keyboard-to-act-like-a-standard-usb-hid-keyboard%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

                    Mangá

                     ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕