Ubuntu 18.04 USB mouse does not work after boot from a powered off state: can't read configurations, error...











up vote
0
down vote

favorite












I have a newly installed version of Ubuntu 18.04 dual booted with Windows 10. Setup went great and I've had no issues using Ubuntu. However, when I turn on my computer and boot into Linux, my mouse pointer will not move. I have a mouse that lights up when it is powered on and when it is not working I noticed the lights are off. It seems that it isn't even getting power when this happens. To fix this, I just turn the computer off and back on again then the mouse has power and everything is fine. When I boot into Windows 10, the mouse always works. It has become a common enough occurrence that I have power cycle again, after turning it on initially, on a daily basis just to get the mouse working.



I have a Razor Naga USB mouse. The keyboard (also USB) doesn't seem to be effected. The mouse is using the USB in the back of the computer (as opposed to a USB hub or additional port on the keyboard).



Has anyone had this issue? How would I even go about troubleshooting this? I'm not familiar with investigating system level failures (like USB drivers for example) in Linux.



Update: dmesg output:



[    1.792881] [drm] Finished loading DMC firmware i915/skl_dmc_ver1_26.bin (v1.26)
[ 1.797053] usb 1-8: New USB device found, idVendor=0d8c, idProduct=0012
[ 1.797054] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1.797055] usb 1-8: Product: USB Audio Device
[ 1.797056] usb 1-8: Manufacturer: C-Media Electronics Inc.
[ 1.928008] usb 1-9: new full-speed USB device number 5 using xhci_hcd
[ 2.061261] [drm] failed to retrieve link info, disabling eDP
[ 2.064752] [drm] Initialized i915 1.6.0 20171023 for 0000:00:02.0 on minor 1
[ 2.077201] usb 1-9: unable to read config index 0 descriptor/all
[ 2.077203] usb 1-9: can't read configurations, error -71
[ 2.204069] usb 1-9: new full-speed USB device number 6 using xhci_hcd
[ 2.256394] checking generic (d1000000 300000) vs hw (b0000000 10000000)
[ 2.256447] i915 0000:00:02.0: fb1: inteldrmfb frame buffer device
[ 2.354338] usb 1-9: string descriptor 0 read error: -71
[ 2.354342] usb 1-9: New USB device found, idVendor=1532, idProduct=001f
[ 2.354343] usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2.355456] usb 1-9: can't set config #1, error -71
[ 2.480295] usb 1-14: new full-speed USB device number 7 using xhci_hcd
[ 2.629969] usb 1-14: New USB device found, idVendor=1532, idProduct=021e
[ 2.629984] usb 1-14: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2.629985] usb 1-14: Product: Razer Ornata Chroma
[ 2.629986] usb 1-14: Manufacturer: Razer


After I disconnect and reconnect the mouse:



[ 1436.941950] usb 1-9: USB disconnect, device number 6
[ 1446.504530] usb 1-9: new full-speed USB device number 8 using xhci_hcd
[ 1446.654938] usb 1-9: New USB device found, idVendor=1532, idProduct=001f
[ 1446.654941] usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1446.654944] usb 1-9: Product: Razer Naga Epic
[ 1446.654946] usb 1-9: Manufacturer: Razer
[ 1446.656777] input: Razer Razer Naga Epic as /devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9:1.0/0003:1532:001F.0006/input/input28
[ 1446.657065] hid-generic 0003:1532:001F.0006: input,hidraw5: USB HID v1.11 Mouse [Razer Razer Naga Epic] on usb-0000:00:14.0-9/input0
[ 1446.657984] input: Razer Razer Naga Epic as /devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9:1.1/0003:1532:001F.0007/input/input29
[ 1446.716997] hid-generic 0003:1532:001F.0007: input,hidraw6: USB HID v1.11 Keyboard [Razer Razer Naga Epic] on usb-0000:00:14.0-9/input1


Using this command:



strings /usr/src/linux-headers-4.15.0-38-generic/include/uapi/asm-generic/errno.h


I found what error code -71 is: EPROTO 71 /* Protocol error */



But I still don't know what this really means... and how to fix it.










share|improve this question




























    up vote
    0
    down vote

    favorite












    I have a newly installed version of Ubuntu 18.04 dual booted with Windows 10. Setup went great and I've had no issues using Ubuntu. However, when I turn on my computer and boot into Linux, my mouse pointer will not move. I have a mouse that lights up when it is powered on and when it is not working I noticed the lights are off. It seems that it isn't even getting power when this happens. To fix this, I just turn the computer off and back on again then the mouse has power and everything is fine. When I boot into Windows 10, the mouse always works. It has become a common enough occurrence that I have power cycle again, after turning it on initially, on a daily basis just to get the mouse working.



    I have a Razor Naga USB mouse. The keyboard (also USB) doesn't seem to be effected. The mouse is using the USB in the back of the computer (as opposed to a USB hub or additional port on the keyboard).



    Has anyone had this issue? How would I even go about troubleshooting this? I'm not familiar with investigating system level failures (like USB drivers for example) in Linux.



    Update: dmesg output:



    [    1.792881] [drm] Finished loading DMC firmware i915/skl_dmc_ver1_26.bin (v1.26)
    [ 1.797053] usb 1-8: New USB device found, idVendor=0d8c, idProduct=0012
    [ 1.797054] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    [ 1.797055] usb 1-8: Product: USB Audio Device
    [ 1.797056] usb 1-8: Manufacturer: C-Media Electronics Inc.
    [ 1.928008] usb 1-9: new full-speed USB device number 5 using xhci_hcd
    [ 2.061261] [drm] failed to retrieve link info, disabling eDP
    [ 2.064752] [drm] Initialized i915 1.6.0 20171023 for 0000:00:02.0 on minor 1
    [ 2.077201] usb 1-9: unable to read config index 0 descriptor/all
    [ 2.077203] usb 1-9: can't read configurations, error -71
    [ 2.204069] usb 1-9: new full-speed USB device number 6 using xhci_hcd
    [ 2.256394] checking generic (d1000000 300000) vs hw (b0000000 10000000)
    [ 2.256447] i915 0000:00:02.0: fb1: inteldrmfb frame buffer device
    [ 2.354338] usb 1-9: string descriptor 0 read error: -71
    [ 2.354342] usb 1-9: New USB device found, idVendor=1532, idProduct=001f
    [ 2.354343] usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    [ 2.355456] usb 1-9: can't set config #1, error -71
    [ 2.480295] usb 1-14: new full-speed USB device number 7 using xhci_hcd
    [ 2.629969] usb 1-14: New USB device found, idVendor=1532, idProduct=021e
    [ 2.629984] usb 1-14: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    [ 2.629985] usb 1-14: Product: Razer Ornata Chroma
    [ 2.629986] usb 1-14: Manufacturer: Razer


    After I disconnect and reconnect the mouse:



    [ 1436.941950] usb 1-9: USB disconnect, device number 6
    [ 1446.504530] usb 1-9: new full-speed USB device number 8 using xhci_hcd
    [ 1446.654938] usb 1-9: New USB device found, idVendor=1532, idProduct=001f
    [ 1446.654941] usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    [ 1446.654944] usb 1-9: Product: Razer Naga Epic
    [ 1446.654946] usb 1-9: Manufacturer: Razer
    [ 1446.656777] input: Razer Razer Naga Epic as /devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9:1.0/0003:1532:001F.0006/input/input28
    [ 1446.657065] hid-generic 0003:1532:001F.0006: input,hidraw5: USB HID v1.11 Mouse [Razer Razer Naga Epic] on usb-0000:00:14.0-9/input0
    [ 1446.657984] input: Razer Razer Naga Epic as /devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9:1.1/0003:1532:001F.0007/input/input29
    [ 1446.716997] hid-generic 0003:1532:001F.0007: input,hidraw6: USB HID v1.11 Keyboard [Razer Razer Naga Epic] on usb-0000:00:14.0-9/input1


    Using this command:



    strings /usr/src/linux-headers-4.15.0-38-generic/include/uapi/asm-generic/errno.h


    I found what error code -71 is: EPROTO 71 /* Protocol error */



    But I still don't know what this really means... and how to fix it.










    share|improve this question


























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I have a newly installed version of Ubuntu 18.04 dual booted with Windows 10. Setup went great and I've had no issues using Ubuntu. However, when I turn on my computer and boot into Linux, my mouse pointer will not move. I have a mouse that lights up when it is powered on and when it is not working I noticed the lights are off. It seems that it isn't even getting power when this happens. To fix this, I just turn the computer off and back on again then the mouse has power and everything is fine. When I boot into Windows 10, the mouse always works. It has become a common enough occurrence that I have power cycle again, after turning it on initially, on a daily basis just to get the mouse working.



      I have a Razor Naga USB mouse. The keyboard (also USB) doesn't seem to be effected. The mouse is using the USB in the back of the computer (as opposed to a USB hub or additional port on the keyboard).



      Has anyone had this issue? How would I even go about troubleshooting this? I'm not familiar with investigating system level failures (like USB drivers for example) in Linux.



      Update: dmesg output:



      [    1.792881] [drm] Finished loading DMC firmware i915/skl_dmc_ver1_26.bin (v1.26)
      [ 1.797053] usb 1-8: New USB device found, idVendor=0d8c, idProduct=0012
      [ 1.797054] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=0
      [ 1.797055] usb 1-8: Product: USB Audio Device
      [ 1.797056] usb 1-8: Manufacturer: C-Media Electronics Inc.
      [ 1.928008] usb 1-9: new full-speed USB device number 5 using xhci_hcd
      [ 2.061261] [drm] failed to retrieve link info, disabling eDP
      [ 2.064752] [drm] Initialized i915 1.6.0 20171023 for 0000:00:02.0 on minor 1
      [ 2.077201] usb 1-9: unable to read config index 0 descriptor/all
      [ 2.077203] usb 1-9: can't read configurations, error -71
      [ 2.204069] usb 1-9: new full-speed USB device number 6 using xhci_hcd
      [ 2.256394] checking generic (d1000000 300000) vs hw (b0000000 10000000)
      [ 2.256447] i915 0000:00:02.0: fb1: inteldrmfb frame buffer device
      [ 2.354338] usb 1-9: string descriptor 0 read error: -71
      [ 2.354342] usb 1-9: New USB device found, idVendor=1532, idProduct=001f
      [ 2.354343] usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=0
      [ 2.355456] usb 1-9: can't set config #1, error -71
      [ 2.480295] usb 1-14: new full-speed USB device number 7 using xhci_hcd
      [ 2.629969] usb 1-14: New USB device found, idVendor=1532, idProduct=021e
      [ 2.629984] usb 1-14: New USB device strings: Mfr=1, Product=2, SerialNumber=0
      [ 2.629985] usb 1-14: Product: Razer Ornata Chroma
      [ 2.629986] usb 1-14: Manufacturer: Razer


      After I disconnect and reconnect the mouse:



      [ 1436.941950] usb 1-9: USB disconnect, device number 6
      [ 1446.504530] usb 1-9: new full-speed USB device number 8 using xhci_hcd
      [ 1446.654938] usb 1-9: New USB device found, idVendor=1532, idProduct=001f
      [ 1446.654941] usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=0
      [ 1446.654944] usb 1-9: Product: Razer Naga Epic
      [ 1446.654946] usb 1-9: Manufacturer: Razer
      [ 1446.656777] input: Razer Razer Naga Epic as /devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9:1.0/0003:1532:001F.0006/input/input28
      [ 1446.657065] hid-generic 0003:1532:001F.0006: input,hidraw5: USB HID v1.11 Mouse [Razer Razer Naga Epic] on usb-0000:00:14.0-9/input0
      [ 1446.657984] input: Razer Razer Naga Epic as /devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9:1.1/0003:1532:001F.0007/input/input29
      [ 1446.716997] hid-generic 0003:1532:001F.0007: input,hidraw6: USB HID v1.11 Keyboard [Razer Razer Naga Epic] on usb-0000:00:14.0-9/input1


      Using this command:



      strings /usr/src/linux-headers-4.15.0-38-generic/include/uapi/asm-generic/errno.h


      I found what error code -71 is: EPROTO 71 /* Protocol error */



      But I still don't know what this really means... and how to fix it.










      share|improve this question















      I have a newly installed version of Ubuntu 18.04 dual booted with Windows 10. Setup went great and I've had no issues using Ubuntu. However, when I turn on my computer and boot into Linux, my mouse pointer will not move. I have a mouse that lights up when it is powered on and when it is not working I noticed the lights are off. It seems that it isn't even getting power when this happens. To fix this, I just turn the computer off and back on again then the mouse has power and everything is fine. When I boot into Windows 10, the mouse always works. It has become a common enough occurrence that I have power cycle again, after turning it on initially, on a daily basis just to get the mouse working.



      I have a Razor Naga USB mouse. The keyboard (also USB) doesn't seem to be effected. The mouse is using the USB in the back of the computer (as opposed to a USB hub or additional port on the keyboard).



      Has anyone had this issue? How would I even go about troubleshooting this? I'm not familiar with investigating system level failures (like USB drivers for example) in Linux.



      Update: dmesg output:



      [    1.792881] [drm] Finished loading DMC firmware i915/skl_dmc_ver1_26.bin (v1.26)
      [ 1.797053] usb 1-8: New USB device found, idVendor=0d8c, idProduct=0012
      [ 1.797054] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=0
      [ 1.797055] usb 1-8: Product: USB Audio Device
      [ 1.797056] usb 1-8: Manufacturer: C-Media Electronics Inc.
      [ 1.928008] usb 1-9: new full-speed USB device number 5 using xhci_hcd
      [ 2.061261] [drm] failed to retrieve link info, disabling eDP
      [ 2.064752] [drm] Initialized i915 1.6.0 20171023 for 0000:00:02.0 on minor 1
      [ 2.077201] usb 1-9: unable to read config index 0 descriptor/all
      [ 2.077203] usb 1-9: can't read configurations, error -71
      [ 2.204069] usb 1-9: new full-speed USB device number 6 using xhci_hcd
      [ 2.256394] checking generic (d1000000 300000) vs hw (b0000000 10000000)
      [ 2.256447] i915 0000:00:02.0: fb1: inteldrmfb frame buffer device
      [ 2.354338] usb 1-9: string descriptor 0 read error: -71
      [ 2.354342] usb 1-9: New USB device found, idVendor=1532, idProduct=001f
      [ 2.354343] usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=0
      [ 2.355456] usb 1-9: can't set config #1, error -71
      [ 2.480295] usb 1-14: new full-speed USB device number 7 using xhci_hcd
      [ 2.629969] usb 1-14: New USB device found, idVendor=1532, idProduct=021e
      [ 2.629984] usb 1-14: New USB device strings: Mfr=1, Product=2, SerialNumber=0
      [ 2.629985] usb 1-14: Product: Razer Ornata Chroma
      [ 2.629986] usb 1-14: Manufacturer: Razer


      After I disconnect and reconnect the mouse:



      [ 1436.941950] usb 1-9: USB disconnect, device number 6
      [ 1446.504530] usb 1-9: new full-speed USB device number 8 using xhci_hcd
      [ 1446.654938] usb 1-9: New USB device found, idVendor=1532, idProduct=001f
      [ 1446.654941] usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=0
      [ 1446.654944] usb 1-9: Product: Razer Naga Epic
      [ 1446.654946] usb 1-9: Manufacturer: Razer
      [ 1446.656777] input: Razer Razer Naga Epic as /devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9:1.0/0003:1532:001F.0006/input/input28
      [ 1446.657065] hid-generic 0003:1532:001F.0006: input,hidraw5: USB HID v1.11 Mouse [Razer Razer Naga Epic] on usb-0000:00:14.0-9/input0
      [ 1446.657984] input: Razer Razer Naga Epic as /devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9:1.1/0003:1532:001F.0007/input/input29
      [ 1446.716997] hid-generic 0003:1532:001F.0007: input,hidraw6: USB HID v1.11 Keyboard [Razer Razer Naga Epic] on usb-0000:00:14.0-9/input1


      Using this command:



      strings /usr/src/linux-headers-4.15.0-38-generic/include/uapi/asm-generic/errno.h


      I found what error code -71 is: EPROTO 71 /* Protocol error */



      But I still don't know what this really means... and how to fix it.







      dual-boot usb 18.04 mouse






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 19 at 16:21

























      asked Aug 10 at 0:04









      Nathan Thompson

      14




      14






















          3 Answers
          3






          active

          oldest

          votes

















          up vote
          0
          down vote













          you can try this : sudo modprobe -r psmouse






          share|improve this answer





















          • How does removing the mouse module help?
            – Nathan Thompson
            Aug 19 at 23:36


















          up vote
          0
          down vote













          This removes the mouse. If you run the above command by mistake, run this: sudo modprobe -a psmouse






          share|improve this answer





















          • and what happens after running that cmd?
            – Pierre.Vriens
            Oct 28 at 13:26


















          up vote
          0
          down vote













          I had the same problem using a Razer Diamondback 2 mouse on openSUSE Tumbleweed and was able to fix it. I've included a description on how I solved the problem below, since I'm not using Ubuntu and as the problem seems to be very hardware specific.



          tl;dr: Add the line following line to /etc/modprobe.d/50-blacklist.conf:



          blacklist mt76x2u


          How to make sure the solution works for you:



          It seems to be a problem with a MediaTek's mt76x2u firmware driver. Loading the driver seems to result in a page fault if the Razer device is plugged into USB 3 (at least that's what happened to my mouse and keyboard).



          You should probably make sure first that you've got the same problem. dmesg | grep mt76x2u got me several lines, including these two:



          [   10.367973] mt76x2u 5-4.2:1.0: firmware upload timed out
          [ 15.552552] mt76x2u: probe of 5-4.2:1.0 failed with error -5


          You should also see similar errors in journalctl.



          Once you've made sure that you have the same problem, you just need to disable the driver. It was recently added to linux-firmware, and everything worked fine for me before, so I concluded that I just don't need it.

          Find your modprobe blacklist. For me it's /etc/modprobe.d/50-blacklist.conf, but appearently its /etc/modprobe.d/blacklist.conf on some other distributions. Then blacklist the kernel module by entering the line blacklist mt76x2u, save and reboot.






          share|improve this answer










          New contributor




          tumbleweed_user is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.


















          • Thanks for your suggestion. It appears I do not have the same problem that you have, but I was able to find the info in dmesg that describes what is going on. I've updated my question with the information.
            – Nathan Thompson
            Nov 19 at 16:03











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "89"
          };
          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',
          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%2faskubuntu.com%2fquestions%2f1064006%2fubuntu-18-04-usb-mouse-does-not-work-after-boot-from-a-powered-off-state-cant%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          3 Answers
          3






          active

          oldest

          votes








          3 Answers
          3






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          0
          down vote













          you can try this : sudo modprobe -r psmouse






          share|improve this answer





















          • How does removing the mouse module help?
            – Nathan Thompson
            Aug 19 at 23:36















          up vote
          0
          down vote













          you can try this : sudo modprobe -r psmouse






          share|improve this answer





















          • How does removing the mouse module help?
            – Nathan Thompson
            Aug 19 at 23:36













          up vote
          0
          down vote










          up vote
          0
          down vote









          you can try this : sudo modprobe -r psmouse






          share|improve this answer












          you can try this : sudo modprobe -r psmouse







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Aug 18 at 5:50









          HANSONS PAKISTAN

          113




          113












          • How does removing the mouse module help?
            – Nathan Thompson
            Aug 19 at 23:36


















          • How does removing the mouse module help?
            – Nathan Thompson
            Aug 19 at 23:36
















          How does removing the mouse module help?
          – Nathan Thompson
          Aug 19 at 23:36




          How does removing the mouse module help?
          – Nathan Thompson
          Aug 19 at 23:36












          up vote
          0
          down vote













          This removes the mouse. If you run the above command by mistake, run this: sudo modprobe -a psmouse






          share|improve this answer





















          • and what happens after running that cmd?
            – Pierre.Vriens
            Oct 28 at 13:26















          up vote
          0
          down vote













          This removes the mouse. If you run the above command by mistake, run this: sudo modprobe -a psmouse






          share|improve this answer





















          • and what happens after running that cmd?
            – Pierre.Vriens
            Oct 28 at 13:26













          up vote
          0
          down vote










          up vote
          0
          down vote









          This removes the mouse. If you run the above command by mistake, run this: sudo modprobe -a psmouse






          share|improve this answer












          This removes the mouse. If you run the above command by mistake, run this: sudo modprobe -a psmouse







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Oct 28 at 13:14









          Amresh Kadian

          1




          1












          • and what happens after running that cmd?
            – Pierre.Vriens
            Oct 28 at 13:26


















          • and what happens after running that cmd?
            – Pierre.Vriens
            Oct 28 at 13:26
















          and what happens after running that cmd?
          – Pierre.Vriens
          Oct 28 at 13:26




          and what happens after running that cmd?
          – Pierre.Vriens
          Oct 28 at 13:26










          up vote
          0
          down vote













          I had the same problem using a Razer Diamondback 2 mouse on openSUSE Tumbleweed and was able to fix it. I've included a description on how I solved the problem below, since I'm not using Ubuntu and as the problem seems to be very hardware specific.



          tl;dr: Add the line following line to /etc/modprobe.d/50-blacklist.conf:



          blacklist mt76x2u


          How to make sure the solution works for you:



          It seems to be a problem with a MediaTek's mt76x2u firmware driver. Loading the driver seems to result in a page fault if the Razer device is plugged into USB 3 (at least that's what happened to my mouse and keyboard).



          You should probably make sure first that you've got the same problem. dmesg | grep mt76x2u got me several lines, including these two:



          [   10.367973] mt76x2u 5-4.2:1.0: firmware upload timed out
          [ 15.552552] mt76x2u: probe of 5-4.2:1.0 failed with error -5


          You should also see similar errors in journalctl.



          Once you've made sure that you have the same problem, you just need to disable the driver. It was recently added to linux-firmware, and everything worked fine for me before, so I concluded that I just don't need it.

          Find your modprobe blacklist. For me it's /etc/modprobe.d/50-blacklist.conf, but appearently its /etc/modprobe.d/blacklist.conf on some other distributions. Then blacklist the kernel module by entering the line blacklist mt76x2u, save and reboot.






          share|improve this answer










          New contributor




          tumbleweed_user is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.


















          • Thanks for your suggestion. It appears I do not have the same problem that you have, but I was able to find the info in dmesg that describes what is going on. I've updated my question with the information.
            – Nathan Thompson
            Nov 19 at 16:03















          up vote
          0
          down vote













          I had the same problem using a Razer Diamondback 2 mouse on openSUSE Tumbleweed and was able to fix it. I've included a description on how I solved the problem below, since I'm not using Ubuntu and as the problem seems to be very hardware specific.



          tl;dr: Add the line following line to /etc/modprobe.d/50-blacklist.conf:



          blacklist mt76x2u


          How to make sure the solution works for you:



          It seems to be a problem with a MediaTek's mt76x2u firmware driver. Loading the driver seems to result in a page fault if the Razer device is plugged into USB 3 (at least that's what happened to my mouse and keyboard).



          You should probably make sure first that you've got the same problem. dmesg | grep mt76x2u got me several lines, including these two:



          [   10.367973] mt76x2u 5-4.2:1.0: firmware upload timed out
          [ 15.552552] mt76x2u: probe of 5-4.2:1.0 failed with error -5


          You should also see similar errors in journalctl.



          Once you've made sure that you have the same problem, you just need to disable the driver. It was recently added to linux-firmware, and everything worked fine for me before, so I concluded that I just don't need it.

          Find your modprobe blacklist. For me it's /etc/modprobe.d/50-blacklist.conf, but appearently its /etc/modprobe.d/blacklist.conf on some other distributions. Then blacklist the kernel module by entering the line blacklist mt76x2u, save and reboot.






          share|improve this answer










          New contributor




          tumbleweed_user is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.


















          • Thanks for your suggestion. It appears I do not have the same problem that you have, but I was able to find the info in dmesg that describes what is going on. I've updated my question with the information.
            – Nathan Thompson
            Nov 19 at 16:03













          up vote
          0
          down vote










          up vote
          0
          down vote









          I had the same problem using a Razer Diamondback 2 mouse on openSUSE Tumbleweed and was able to fix it. I've included a description on how I solved the problem below, since I'm not using Ubuntu and as the problem seems to be very hardware specific.



          tl;dr: Add the line following line to /etc/modprobe.d/50-blacklist.conf:



          blacklist mt76x2u


          How to make sure the solution works for you:



          It seems to be a problem with a MediaTek's mt76x2u firmware driver. Loading the driver seems to result in a page fault if the Razer device is plugged into USB 3 (at least that's what happened to my mouse and keyboard).



          You should probably make sure first that you've got the same problem. dmesg | grep mt76x2u got me several lines, including these two:



          [   10.367973] mt76x2u 5-4.2:1.0: firmware upload timed out
          [ 15.552552] mt76x2u: probe of 5-4.2:1.0 failed with error -5


          You should also see similar errors in journalctl.



          Once you've made sure that you have the same problem, you just need to disable the driver. It was recently added to linux-firmware, and everything worked fine for me before, so I concluded that I just don't need it.

          Find your modprobe blacklist. For me it's /etc/modprobe.d/50-blacklist.conf, but appearently its /etc/modprobe.d/blacklist.conf on some other distributions. Then blacklist the kernel module by entering the line blacklist mt76x2u, save and reboot.






          share|improve this answer










          New contributor




          tumbleweed_user is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.









          I had the same problem using a Razer Diamondback 2 mouse on openSUSE Tumbleweed and was able to fix it. I've included a description on how I solved the problem below, since I'm not using Ubuntu and as the problem seems to be very hardware specific.



          tl;dr: Add the line following line to /etc/modprobe.d/50-blacklist.conf:



          blacklist mt76x2u


          How to make sure the solution works for you:



          It seems to be a problem with a MediaTek's mt76x2u firmware driver. Loading the driver seems to result in a page fault if the Razer device is plugged into USB 3 (at least that's what happened to my mouse and keyboard).



          You should probably make sure first that you've got the same problem. dmesg | grep mt76x2u got me several lines, including these two:



          [   10.367973] mt76x2u 5-4.2:1.0: firmware upload timed out
          [ 15.552552] mt76x2u: probe of 5-4.2:1.0 failed with error -5


          You should also see similar errors in journalctl.



          Once you've made sure that you have the same problem, you just need to disable the driver. It was recently added to linux-firmware, and everything worked fine for me before, so I concluded that I just don't need it.

          Find your modprobe blacklist. For me it's /etc/modprobe.d/50-blacklist.conf, but appearently its /etc/modprobe.d/blacklist.conf on some other distributions. Then blacklist the kernel module by entering the line blacklist mt76x2u, save and reboot.







          share|improve this answer










          New contributor




          tumbleweed_user is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.









          share|improve this answer



          share|improve this answer








          edited Nov 18 at 9:45









          Thomas

          3,45081427




          3,45081427






          New contributor




          tumbleweed_user is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.









          answered Nov 18 at 9:34









          tumbleweed_user

          1




          1




          New contributor




          tumbleweed_user is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.





          New contributor





          tumbleweed_user is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.






          tumbleweed_user is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.












          • Thanks for your suggestion. It appears I do not have the same problem that you have, but I was able to find the info in dmesg that describes what is going on. I've updated my question with the information.
            – Nathan Thompson
            Nov 19 at 16:03


















          • Thanks for your suggestion. It appears I do not have the same problem that you have, but I was able to find the info in dmesg that describes what is going on. I've updated my question with the information.
            – Nathan Thompson
            Nov 19 at 16:03
















          Thanks for your suggestion. It appears I do not have the same problem that you have, but I was able to find the info in dmesg that describes what is going on. I've updated my question with the information.
          – Nathan Thompson
          Nov 19 at 16:03




          Thanks for your suggestion. It appears I do not have the same problem that you have, but I was able to find the info in dmesg that describes what is going on. I've updated my question with the information.
          – Nathan Thompson
          Nov 19 at 16:03


















           

          draft saved


          draft discarded



















































           


          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1064006%2fubuntu-18-04-usb-mouse-does-not-work-after-boot-from-a-powered-off-state-cant%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

          Quarter-circle Tiles

          build a pushdown automaton that recognizes the reverse language of a given pushdown automaton?

          Mont Emei