Announcement

Collapse
No announcement yet.

DYNEX Wireless mouse Causes hangup after GRUP menu

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    DYNEX Wireless mouse Causes hangup after GRUP menu

    Interesting issue I have been having for the last week or two. Sometimes when I booted up, my machine would hang after the GRUB menu. When I restarted the machine by power cycling it, the machine would boot successfully, but with what looks lime a recovery spash screen. One day for troubleshooting, I removed the DYNEX wireless mouse from the USB port and the machine would boot successfully every time. Since I am kind of curious, I put the USB back and tried it with the mouse switched on and the mouse switched off. As long as the mose is off, the system would boot successfully. I was wondering if there is a log entry somewhere I could look at to really nail down the issue from a theoretical standpoint rather than just a practical standpoint.

    Output of lsusb:


    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 001 Device 002: ID 064e:f209 Suyin Corp.
    Bus 005 Device 002: ID 19ff:0225 Dynex
    Bus 006 Device 002: ID 138a:0005 Validity Sensors, Inc. VFS301 Fingerprint Reader
    Tags: None
    • Top
    • Bottom
    #2
    Compare the syslog of a failed boot to that of a successful boot. Can you identify the failure point, and possibly determine a cause from whatever might be in the log?
    • Top
    • Bottom

    Comment

      #3
      SteveRiley,

      Here is what I gat, but all it tells me is that the system cannot enumerate the USB device, which I kind of already knew. :-)


      Aug 14 20:38:40 kubuntu-64 kernel: [ 102.916370] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:38:40 kubuntu-64 kernel: [ 103.364325] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:38:41 kubuntu-64 kernel: [ 103.812324] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:38:41 kubuntu-64 kernel: [ 104.260326] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:38:41 kubuntu-64 kernel: [ 104.708304] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:38:42 kubuntu-64 kernel: [ 105.156338] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:38:42 kubuntu-64 kernel: [ 105.604266] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:38:43 kubuntu-64 kernel: [ 106.052337] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:38:43 kubuntu-64 kernel: [ 106.500322] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:38:44 kubuntu-64 kernel: [ 106.948309] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:38:44 kubuntu-64 kernel: [ 107.396336] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:38:45 kubuntu-64 kernel: [ 107.844322] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:38:45 kubuntu-64 kernel: [ 108.292326] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:38:45 kubuntu-64 kernel: [ 108.740374] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:38:46 kubuntu-64 kernel: [ 109.188361] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:38:46 kubuntu-64 kernel: [ 109.636375] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:38:47 kubuntu-64 kernel: [ 110.084354] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:38:47 kubuntu-64 kernel: [ 110.532358] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:38:48 kubuntu-64 kernel: [ 110.980171] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:38:48 kubuntu-64 kernel: [ 111.428360] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:38:49 kubuntu-64 kernel: [ 111.876324] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:38:49 kubuntu-64 kernel: [ 112.324305] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:38:49 kubuntu-64 kernel: [ 112.772316] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:38:50 kubuntu-64 kernel: [ 113.220327] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:38:50 kubuntu-64 kernel: [ 113.668355] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:38:51 kubuntu-64 kernel: [ 114.116325] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:38:51 kubuntu-64 kernel: [ 114.564191] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:38:52 kubuntu-64 kernel: [ 115.012313] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:38:52 kubuntu-64 kernel: [ 115.460318] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:38:53 kubuntu-64 kernel: [ 115.908306] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:38:53 kubuntu-64 kernel: [ 116.356311] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:38:54 kubuntu-64 kernel: [ 116.804348] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:38:54 kubuntu-64 kernel: [ 117.252340] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:38:54 kubuntu-64 kernel: [ 117.700328] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:38:55 kubuntu-64 kernel: [ 118.148325] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:38:55 kubuntu-64 kernel: [ 118.596332] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:38:56 kubuntu-64 kernel: [ 119.044309] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:38:56 kubuntu-64 kernel: [ 119.492309] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:38:57 kubuntu-64 kernel: [ 119.940339] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:38:57 kubuntu-64 kernel: [ 120.388328] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:38:58 kubuntu-64 kernel: [ 120.836329] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:38:58 kubuntu-64 kernel: [ 121.284328] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:38:58 kubuntu-64 kernel: [ 121.732340] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:38:59 kubuntu-64 kernel: [ 122.180372] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:38:59 kubuntu-64 kernel: [ 122.628344] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:39:00 kubuntu-64 kernel: [ 123.076288] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:39:00 kubuntu-64 kernel: [ 123.524309] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:39:01 kubuntu-64 kernel: [ 123.972322] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:39:01 kubuntu-64 kernel: [ 124.420312] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:39:02 kubuntu-64 kernel: [ 124.868288] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:39:02 kubuntu-64 kernel: [ 125.316331] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:39:02 kubuntu-64 kernel: [ 125.764317] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:39:03 kubuntu-64 kernel: [ 126.212307] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:39:03 kubuntu-64 kernel: [ 126.660308] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:39:04 kubuntu-64 kernel: [ 127.108144] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:39:04 kubuntu-64 kernel: [ 127.556392] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:39:05 kubuntu-64 kernel: [ 128.004322] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:39:05 kubuntu-64 kernel: [ 128.452256] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:39:06 kubuntu-64 kernel: [ 128.900323] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:39:06 kubuntu-64 kernel: [ 129.348308] hub 5-0:1.0: unable to enumerate USB device on port 5
      Aug 14 20:39:07 kubuntu-64 kernel: [ 129.796168] hub 5-0:1.0: unable to enumerate USB device on port 5
      • Top
      • Bottom

      Comment

        #4
        Does that line simply keep reappearing in the syslog file until you power off the machine?

        Also, let's ensure I understand your original problem:

        * Power up from cold, mouse receiver attached, mouse on -> hang.
        * Cycle power, receiver attached, mouse on -> success (but with "lime a recovery splash screen" -- what's that?)
        * Power up from cold, mouse receiver attached, mouse off -> success.

        Have you tried moving the receiver to some other USB port? It might be worth trying to figure out which ports are attached to bus 001, 002, or 003. These are USB 2.0 ports on your machine. Could be that your mouse is having problems on the USB 1.1 port.

        lsusb -t lists your USB hierarchy in a tree. Move the receiver to another port and run that command. Keep trying until you see the device listed under Bus 001, 002, or 003. Then see if you can boot cold with the mouse switched on.

        BTW, on my machine, lsusb -t enumerates the bus in reverse order:
        Code:
        steve@x1:~$ [B]sudo lsusb -t[/B]
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 5000M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/3p, 480M
    |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/8p, 480M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/3p, 480M
    |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/6p, 480M
        |__ Port 6: Dev 3, If 0, Class='bInterfaceClass 0x0e not yet handled', Driver=uvcvideo, 480M
        |__ Port 6: Dev 3, If 1, Class='bInterfaceClass 0x0e not yet handled', Driver=uvcvideo, 480M
        See, it's 04, 03, 02, then 01. I honestly don't know whether that's normal or just a quirk of my hardware.
        • Top
        • Bottom

        Comment

          #5
          SteveRiley,

          I have tried to move the mouse to another port, to no avail.

          Here is my lsusb -t output:

          Code:
          6-1:1.0: No such file or directory
/:  Bus 07.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/4p, 12M
/:  Bus 06.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/2p, 12M
    |__ Port 1: Dev 2, If 0, Class=vend., Driver=, 12M
/:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/5p, 12M
    |__ Port 2: Dev 2, If 0, Class=HID, Driver=usbhid, 12M
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/5p, 12M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/4p, 480M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/5p, 480M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/5p, 480M
    |__ Port 3: Dev 2, If 0, Class='bInterfaceClass 0x0e not yet handled', Driver=uvcvideo, 480M
    |__ Port 3: Dev 2, If 1, Class='bInterfaceClass 0x0e not yet handled', Driver=uvcvideo, 480M
          ISTM that the mouse is not detected as a mouse if the mouse is on, and the system hangs, FWIW.
          • Top
          • Bottom

          Comment

            #6
            Originally posted by Thiudans View Post
            ISTM that the mouse is not detected as a mouse if the mouse is on, and the system hangs, FWIW.
            That appears to be the only obvious explanation. But it certainly is unsatisfactory.
            • Top
            • Bottom

            Comment

              #7
              Agreed. Should I create a bug report?
              • Top
              • Bottom

              Comment

                #8
                Probably... the driver module is usbhid, which is part of the linux-image-version package.
                • Top
                • Bottom

                Comment

                Previous template Next
                Working...
                X