USB device connecting and disconnecting repeatedly











up vote
2
down vote

favorite
2












I was having some problems booting into Ubuntu. After trying to reboot for sometime, I eventually opened the 4.4.0-31 recovery mode. while it was booting into recovery mode, it said that /dev/ubuntu-gnome-vg needs to fsck manually.



While this was going on the touchscreen for the computer was connecting and disconnecting repeatedly.



The screen was showing this:



usb 2-7: new full-speed USB device number 42 using using xchi_hcd
usb 2-7: New USB device found, idVendor=04f3, idproduct=016f
usb 2-7: New USB device strings: Mfr=4, Product =14, SerialNumber=0
usb 2-7: Product: Touchscreen
usb 2-7: Manufacturer: ELAN
usb 2-7: ep 0x2 - rounding interval to 64 microframes, ep desc
says 80 microframes
usb 2-7: USB disconnect, device number 42.


and then this repeats with the device being 43.



How do I stop this so that I can actually try and fix the problem on the disk. Also if you guys have some advice regarding /dev/ubuntu-gnome-vg needing to be fsck'd that be great.










share|improve this question
























  • I am having the exact same issue, did you manage to solve this issue?
    – theAlse
    Sep 6 '17 at 8:00















up vote
2
down vote

favorite
2












I was having some problems booting into Ubuntu. After trying to reboot for sometime, I eventually opened the 4.4.0-31 recovery mode. while it was booting into recovery mode, it said that /dev/ubuntu-gnome-vg needs to fsck manually.



While this was going on the touchscreen for the computer was connecting and disconnecting repeatedly.



The screen was showing this:



usb 2-7: new full-speed USB device number 42 using using xchi_hcd
usb 2-7: New USB device found, idVendor=04f3, idproduct=016f
usb 2-7: New USB device strings: Mfr=4, Product =14, SerialNumber=0
usb 2-7: Product: Touchscreen
usb 2-7: Manufacturer: ELAN
usb 2-7: ep 0x2 - rounding interval to 64 microframes, ep desc
says 80 microframes
usb 2-7: USB disconnect, device number 42.


and then this repeats with the device being 43.



How do I stop this so that I can actually try and fix the problem on the disk. Also if you guys have some advice regarding /dev/ubuntu-gnome-vg needing to be fsck'd that be great.










share|improve this question
























  • I am having the exact same issue, did you manage to solve this issue?
    – theAlse
    Sep 6 '17 at 8:00













up vote
2
down vote

favorite
2









up vote
2
down vote

favorite
2






2





I was having some problems booting into Ubuntu. After trying to reboot for sometime, I eventually opened the 4.4.0-31 recovery mode. while it was booting into recovery mode, it said that /dev/ubuntu-gnome-vg needs to fsck manually.



While this was going on the touchscreen for the computer was connecting and disconnecting repeatedly.



The screen was showing this:



usb 2-7: new full-speed USB device number 42 using using xchi_hcd
usb 2-7: New USB device found, idVendor=04f3, idproduct=016f
usb 2-7: New USB device strings: Mfr=4, Product =14, SerialNumber=0
usb 2-7: Product: Touchscreen
usb 2-7: Manufacturer: ELAN
usb 2-7: ep 0x2 - rounding interval to 64 microframes, ep desc
says 80 microframes
usb 2-7: USB disconnect, device number 42.


and then this repeats with the device being 43.



How do I stop this so that I can actually try and fix the problem on the disk. Also if you guys have some advice regarding /dev/ubuntu-gnome-vg needing to be fsck'd that be great.










share|improve this question















I was having some problems booting into Ubuntu. After trying to reboot for sometime, I eventually opened the 4.4.0-31 recovery mode. while it was booting into recovery mode, it said that /dev/ubuntu-gnome-vg needs to fsck manually.



While this was going on the touchscreen for the computer was connecting and disconnecting repeatedly.



The screen was showing this:



usb 2-7: new full-speed USB device number 42 using using xchi_hcd
usb 2-7: New USB device found, idVendor=04f3, idproduct=016f
usb 2-7: New USB device strings: Mfr=4, Product =14, SerialNumber=0
usb 2-7: Product: Touchscreen
usb 2-7: Manufacturer: ELAN
usb 2-7: ep 0x2 - rounding interval to 64 microframes, ep desc
says 80 microframes
usb 2-7: USB disconnect, device number 42.


and then this repeats with the device being 43.



How do I stop this so that I can actually try and fix the problem on the disk. Also if you guys have some advice regarding /dev/ubuntu-gnome-vg needing to be fsck'd that be great.







boot usb fsck recovery-mode disconnect






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Aug 20 '16 at 16:40









Hizqeel

1,72751221




1,72751221










asked Aug 20 '16 at 13:18









Gautam Raghuvanshi

1112




1112












  • I am having the exact same issue, did you manage to solve this issue?
    – theAlse
    Sep 6 '17 at 8:00


















  • I am having the exact same issue, did you manage to solve this issue?
    – theAlse
    Sep 6 '17 at 8:00
















I am having the exact same issue, did you manage to solve this issue?
– theAlse
Sep 6 '17 at 8:00




I am having the exact same issue, did you manage to solve this issue?
– theAlse
Sep 6 '17 at 8:00










2 Answers
2






active

oldest

votes

















up vote
0
down vote













This looks suspiciously similar like a broken USB cable or port. I can say that for sure because I'm using such: every time I'm touching a cable of my USB hub, I see in /var/log/syslog a wall of those messages about (dis) connection, and increasing device number; and the connected mouse resets its sensitivity.



Just for the record, here's an example of mine log:



Aug 20 17:22:38 constantine-N61Ja kernel: [55857.366422] usb 4-1.1: USB disconnect, device number 25        
Aug 20 17:22:38 constantine-N61Ja kernel: [55857.366428] usb 4-1.1.2: USB disconnect, device number 26
Aug 20 17:22:38 constantine-N61Ja kernel: [55857.366730] usb 4-1.1.3: USB disconnect, device number 27
Aug 20 17:22:39 constantine-N61Ja kernel: [55857.690545] usb 4-1.1: new high-speed USB device number 28 using ehci-pci
Aug 20 17:22:39 constantine-N61Ja kernel: [55857.774736] hub 4-1.1:1.0: USB hub found
Aug 20 17:22:39 constantine-N61Ja kernel: [55857.774788] hub 4-1.1:1.0: 4 ports detected
Aug 20 17:22:39 constantine-N61Ja kernel: [55858.043972] usb 4-1.1.2: new low-speed USB device number 29 using ehci-pci
Aug 20 17:22:39 constantine-N61Ja kernel: [55858.142289] input: HID 192f:0716 as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1/4-1.1.2/4-1.1.2:1.0/0003:192F:0716.0019/input/input49
Aug 20 17:22:39 constantine-N61Ja kernel: [55858.142518] hid-generic 0003:192F:0716.0019: input,hidraw0: USB HID v1.11 Mouse [HID 192f:0716] on usb-0000:00:1d.0-1.1.2/input0
Aug 20 17:22:39 constantine-N61Ja kernel: [55858.207327] usb 4-1.1.3: new low-speed USB device number 30 using ehci-pci
Aug 20 17:22:39 constantine-N61Ja kernel: [55858.320867] input: USB Keyboard as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1/4-1.1.3/4-1.1.3:1.0/0003:04D9:1702.001A/input/input50
Aug 20 17:22:39 constantine-N61Ja kernel: [55858.374364] hid-generic 0003:04D9:1702.001A: input,hidraw1: USB HID v1.10 Keyboard [ USB Keyboard] on usb-0000:00:1d.0-1.1.3/input0
Aug 20 17:22:39 constantine-N61Ja kernel: [55858.391406] input: USB Keyboard as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1/4-1.1.3/4-1.1.3:1.1/0003:04D9:1702.001B/input/input51
Aug 20 17:22:39 constantine-N61Ja kernel: [55858.444140] hid-generic 0003:04D9:1702.001B: input,hidraw2: USB HID v1.10 Device [ USB Keyboard] on usb-0000:00:1d.0-1.1.3/input1





share|improve this answer




























    up vote
    0
    down vote













    Temporarily disconnect your touchscreen device from its USB port. Then boot the computer into RECOVERY mode from the GRUB menu, choose ROOT, then type sudo fsck -f /dev/ubuntu-gnome-vg. Let us know how that works. Cheers, Al






    share|improve this answer





















      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%2f814569%2fusb-device-connecting-and-disconnecting-repeatedly%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes








      up vote
      0
      down vote













      This looks suspiciously similar like a broken USB cable or port. I can say that for sure because I'm using such: every time I'm touching a cable of my USB hub, I see in /var/log/syslog a wall of those messages about (dis) connection, and increasing device number; and the connected mouse resets its sensitivity.



      Just for the record, here's an example of mine log:



      Aug 20 17:22:38 constantine-N61Ja kernel: [55857.366422] usb 4-1.1: USB disconnect, device number 25        
      Aug 20 17:22:38 constantine-N61Ja kernel: [55857.366428] usb 4-1.1.2: USB disconnect, device number 26
      Aug 20 17:22:38 constantine-N61Ja kernel: [55857.366730] usb 4-1.1.3: USB disconnect, device number 27
      Aug 20 17:22:39 constantine-N61Ja kernel: [55857.690545] usb 4-1.1: new high-speed USB device number 28 using ehci-pci
      Aug 20 17:22:39 constantine-N61Ja kernel: [55857.774736] hub 4-1.1:1.0: USB hub found
      Aug 20 17:22:39 constantine-N61Ja kernel: [55857.774788] hub 4-1.1:1.0: 4 ports detected
      Aug 20 17:22:39 constantine-N61Ja kernel: [55858.043972] usb 4-1.1.2: new low-speed USB device number 29 using ehci-pci
      Aug 20 17:22:39 constantine-N61Ja kernel: [55858.142289] input: HID 192f:0716 as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1/4-1.1.2/4-1.1.2:1.0/0003:192F:0716.0019/input/input49
      Aug 20 17:22:39 constantine-N61Ja kernel: [55858.142518] hid-generic 0003:192F:0716.0019: input,hidraw0: USB HID v1.11 Mouse [HID 192f:0716] on usb-0000:00:1d.0-1.1.2/input0
      Aug 20 17:22:39 constantine-N61Ja kernel: [55858.207327] usb 4-1.1.3: new low-speed USB device number 30 using ehci-pci
      Aug 20 17:22:39 constantine-N61Ja kernel: [55858.320867] input: USB Keyboard as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1/4-1.1.3/4-1.1.3:1.0/0003:04D9:1702.001A/input/input50
      Aug 20 17:22:39 constantine-N61Ja kernel: [55858.374364] hid-generic 0003:04D9:1702.001A: input,hidraw1: USB HID v1.10 Keyboard [ USB Keyboard] on usb-0000:00:1d.0-1.1.3/input0
      Aug 20 17:22:39 constantine-N61Ja kernel: [55858.391406] input: USB Keyboard as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1/4-1.1.3/4-1.1.3:1.1/0003:04D9:1702.001B/input/input51
      Aug 20 17:22:39 constantine-N61Ja kernel: [55858.444140] hid-generic 0003:04D9:1702.001B: input,hidraw2: USB HID v1.10 Device [ USB Keyboard] on usb-0000:00:1d.0-1.1.3/input1





      share|improve this answer

























        up vote
        0
        down vote













        This looks suspiciously similar like a broken USB cable or port. I can say that for sure because I'm using such: every time I'm touching a cable of my USB hub, I see in /var/log/syslog a wall of those messages about (dis) connection, and increasing device number; and the connected mouse resets its sensitivity.



        Just for the record, here's an example of mine log:



        Aug 20 17:22:38 constantine-N61Ja kernel: [55857.366422] usb 4-1.1: USB disconnect, device number 25        
        Aug 20 17:22:38 constantine-N61Ja kernel: [55857.366428] usb 4-1.1.2: USB disconnect, device number 26
        Aug 20 17:22:38 constantine-N61Ja kernel: [55857.366730] usb 4-1.1.3: USB disconnect, device number 27
        Aug 20 17:22:39 constantine-N61Ja kernel: [55857.690545] usb 4-1.1: new high-speed USB device number 28 using ehci-pci
        Aug 20 17:22:39 constantine-N61Ja kernel: [55857.774736] hub 4-1.1:1.0: USB hub found
        Aug 20 17:22:39 constantine-N61Ja kernel: [55857.774788] hub 4-1.1:1.0: 4 ports detected
        Aug 20 17:22:39 constantine-N61Ja kernel: [55858.043972] usb 4-1.1.2: new low-speed USB device number 29 using ehci-pci
        Aug 20 17:22:39 constantine-N61Ja kernel: [55858.142289] input: HID 192f:0716 as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1/4-1.1.2/4-1.1.2:1.0/0003:192F:0716.0019/input/input49
        Aug 20 17:22:39 constantine-N61Ja kernel: [55858.142518] hid-generic 0003:192F:0716.0019: input,hidraw0: USB HID v1.11 Mouse [HID 192f:0716] on usb-0000:00:1d.0-1.1.2/input0
        Aug 20 17:22:39 constantine-N61Ja kernel: [55858.207327] usb 4-1.1.3: new low-speed USB device number 30 using ehci-pci
        Aug 20 17:22:39 constantine-N61Ja kernel: [55858.320867] input: USB Keyboard as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1/4-1.1.3/4-1.1.3:1.0/0003:04D9:1702.001A/input/input50
        Aug 20 17:22:39 constantine-N61Ja kernel: [55858.374364] hid-generic 0003:04D9:1702.001A: input,hidraw1: USB HID v1.10 Keyboard [ USB Keyboard] on usb-0000:00:1d.0-1.1.3/input0
        Aug 20 17:22:39 constantine-N61Ja kernel: [55858.391406] input: USB Keyboard as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1/4-1.1.3/4-1.1.3:1.1/0003:04D9:1702.001B/input/input51
        Aug 20 17:22:39 constantine-N61Ja kernel: [55858.444140] hid-generic 0003:04D9:1702.001B: input,hidraw2: USB HID v1.10 Device [ USB Keyboard] on usb-0000:00:1d.0-1.1.3/input1





        share|improve this answer























          up vote
          0
          down vote










          up vote
          0
          down vote









          This looks suspiciously similar like a broken USB cable or port. I can say that for sure because I'm using such: every time I'm touching a cable of my USB hub, I see in /var/log/syslog a wall of those messages about (dis) connection, and increasing device number; and the connected mouse resets its sensitivity.



          Just for the record, here's an example of mine log:



          Aug 20 17:22:38 constantine-N61Ja kernel: [55857.366422] usb 4-1.1: USB disconnect, device number 25        
          Aug 20 17:22:38 constantine-N61Ja kernel: [55857.366428] usb 4-1.1.2: USB disconnect, device number 26
          Aug 20 17:22:38 constantine-N61Ja kernel: [55857.366730] usb 4-1.1.3: USB disconnect, device number 27
          Aug 20 17:22:39 constantine-N61Ja kernel: [55857.690545] usb 4-1.1: new high-speed USB device number 28 using ehci-pci
          Aug 20 17:22:39 constantine-N61Ja kernel: [55857.774736] hub 4-1.1:1.0: USB hub found
          Aug 20 17:22:39 constantine-N61Ja kernel: [55857.774788] hub 4-1.1:1.0: 4 ports detected
          Aug 20 17:22:39 constantine-N61Ja kernel: [55858.043972] usb 4-1.1.2: new low-speed USB device number 29 using ehci-pci
          Aug 20 17:22:39 constantine-N61Ja kernel: [55858.142289] input: HID 192f:0716 as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1/4-1.1.2/4-1.1.2:1.0/0003:192F:0716.0019/input/input49
          Aug 20 17:22:39 constantine-N61Ja kernel: [55858.142518] hid-generic 0003:192F:0716.0019: input,hidraw0: USB HID v1.11 Mouse [HID 192f:0716] on usb-0000:00:1d.0-1.1.2/input0
          Aug 20 17:22:39 constantine-N61Ja kernel: [55858.207327] usb 4-1.1.3: new low-speed USB device number 30 using ehci-pci
          Aug 20 17:22:39 constantine-N61Ja kernel: [55858.320867] input: USB Keyboard as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1/4-1.1.3/4-1.1.3:1.0/0003:04D9:1702.001A/input/input50
          Aug 20 17:22:39 constantine-N61Ja kernel: [55858.374364] hid-generic 0003:04D9:1702.001A: input,hidraw1: USB HID v1.10 Keyboard [ USB Keyboard] on usb-0000:00:1d.0-1.1.3/input0
          Aug 20 17:22:39 constantine-N61Ja kernel: [55858.391406] input: USB Keyboard as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1/4-1.1.3/4-1.1.3:1.1/0003:04D9:1702.001B/input/input51
          Aug 20 17:22:39 constantine-N61Ja kernel: [55858.444140] hid-generic 0003:04D9:1702.001B: input,hidraw2: USB HID v1.10 Device [ USB Keyboard] on usb-0000:00:1d.0-1.1.3/input1





          share|improve this answer












          This looks suspiciously similar like a broken USB cable or port. I can say that for sure because I'm using such: every time I'm touching a cable of my USB hub, I see in /var/log/syslog a wall of those messages about (dis) connection, and increasing device number; and the connected mouse resets its sensitivity.



          Just for the record, here's an example of mine log:



          Aug 20 17:22:38 constantine-N61Ja kernel: [55857.366422] usb 4-1.1: USB disconnect, device number 25        
          Aug 20 17:22:38 constantine-N61Ja kernel: [55857.366428] usb 4-1.1.2: USB disconnect, device number 26
          Aug 20 17:22:38 constantine-N61Ja kernel: [55857.366730] usb 4-1.1.3: USB disconnect, device number 27
          Aug 20 17:22:39 constantine-N61Ja kernel: [55857.690545] usb 4-1.1: new high-speed USB device number 28 using ehci-pci
          Aug 20 17:22:39 constantine-N61Ja kernel: [55857.774736] hub 4-1.1:1.0: USB hub found
          Aug 20 17:22:39 constantine-N61Ja kernel: [55857.774788] hub 4-1.1:1.0: 4 ports detected
          Aug 20 17:22:39 constantine-N61Ja kernel: [55858.043972] usb 4-1.1.2: new low-speed USB device number 29 using ehci-pci
          Aug 20 17:22:39 constantine-N61Ja kernel: [55858.142289] input: HID 192f:0716 as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1/4-1.1.2/4-1.1.2:1.0/0003:192F:0716.0019/input/input49
          Aug 20 17:22:39 constantine-N61Ja kernel: [55858.142518] hid-generic 0003:192F:0716.0019: input,hidraw0: USB HID v1.11 Mouse [HID 192f:0716] on usb-0000:00:1d.0-1.1.2/input0
          Aug 20 17:22:39 constantine-N61Ja kernel: [55858.207327] usb 4-1.1.3: new low-speed USB device number 30 using ehci-pci
          Aug 20 17:22:39 constantine-N61Ja kernel: [55858.320867] input: USB Keyboard as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1/4-1.1.3/4-1.1.3:1.0/0003:04D9:1702.001A/input/input50
          Aug 20 17:22:39 constantine-N61Ja kernel: [55858.374364] hid-generic 0003:04D9:1702.001A: input,hidraw1: USB HID v1.10 Keyboard [ USB Keyboard] on usb-0000:00:1d.0-1.1.3/input0
          Aug 20 17:22:39 constantine-N61Ja kernel: [55858.391406] input: USB Keyboard as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1/4-1.1.3/4-1.1.3:1.1/0003:04D9:1702.001B/input/input51
          Aug 20 17:22:39 constantine-N61Ja kernel: [55858.444140] hid-generic 0003:04D9:1702.001B: input,hidraw2: USB HID v1.10 Device [ USB Keyboard] on usb-0000:00:1d.0-1.1.3/input1






          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Aug 20 '16 at 14:20









          Hi-Angel

          2,17211625




          2,17211625
























              up vote
              0
              down vote













              Temporarily disconnect your touchscreen device from its USB port. Then boot the computer into RECOVERY mode from the GRUB menu, choose ROOT, then type sudo fsck -f /dev/ubuntu-gnome-vg. Let us know how that works. Cheers, Al






              share|improve this answer

























                up vote
                0
                down vote













                Temporarily disconnect your touchscreen device from its USB port. Then boot the computer into RECOVERY mode from the GRUB menu, choose ROOT, then type sudo fsck -f /dev/ubuntu-gnome-vg. Let us know how that works. Cheers, Al






                share|improve this answer























                  up vote
                  0
                  down vote










                  up vote
                  0
                  down vote









                  Temporarily disconnect your touchscreen device from its USB port. Then boot the computer into RECOVERY mode from the GRUB menu, choose ROOT, then type sudo fsck -f /dev/ubuntu-gnome-vg. Let us know how that works. Cheers, Al






                  share|improve this answer












                  Temporarily disconnect your touchscreen device from its USB port. Then boot the computer into RECOVERY mode from the GRUB menu, choose ROOT, then type sudo fsck -f /dev/ubuntu-gnome-vg. Let us know how that works. Cheers, Al







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Aug 20 '16 at 18:01









                  heynnema

                  17.7k22053




                  17.7k22053






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Ask Ubuntu!


                      • 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.





                      Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                      Please pay close attention to the following guidance:


                      • 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%2faskubuntu.com%2fquestions%2f814569%2fusb-device-connecting-and-disconnecting-repeatedly%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á

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