Mouse will not work on new motherboard

English Install/Boot/Login
#1

HI, my desktop has been down for a while due to mother board failure and I got a new one, a gigabyte ATX AMD socket AM3+ 970 chipset and now my mouse will not work. I also have a PATA to USB adapter that will not work either, but a USB thumb drive does work. It’s not the USB plug because the mouse will work in knoppix 7.2. The mouse is a logiech, I’ve had no problems with it until now. It’s a wired mouse, don’t know if it makes a differenct. I looked in /var/log/warn and here’s what I come up with (all of it from the kernel):


i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042 nopnp
usb 1-2: device descriptor read/64, error -32
usb 1-2: device not accepting address 5 error -32
hub 1-0: 1.0 unable to enumerate USB device on port 2
usb 6-1: ......

The messages repeat with increasing address number and different port numbers. This is with both malfunctioning devices plugged in. I checked the system with:

rpm -q -V -a

And fixed a few broken things, nothing kernel realated, probably due to when my mother board went down, and I still have the same problem. I tried the wireless mouse from my laptop, but no go.

#2

Try to run “sudo /sbin/mkinitrd”. Maybe the initrd misses some stuff that is needed with the new motherboard.

#3

That looks familiar.

I have a Lenovo ThinkServer TS140.

At first everything was fine. Then I updated the BIOS, and started getting those messages. It was mostly annoyance. The system still worked. But, after being prompted for a LUKS partition encryption key, I had to wait for a minute or two of such USB errors, before I could type in the key. Once the system was up and running, it worked fine.

Eventually, the vendor came up with yet another BIOS update. And that fixed it. From the BIOS update summary of changes, this seems to be the important part:


<81A>
        -Fix the issue that some USB devices may not be recognized correctly during boot.

The “81A” is a BIOS version number.

I’m not at all sure what a BIOS does that affects how a USB is recognized by the kernel. But apparently, that was what was happening.

While having problems, I did experiment with some changes to what was in the “initrd”, but that didn’t change anything.

In your case, I am not clear where the “initrd” would be involved. For me, it was involved for using the keyboard to enter the LUKS key. But just about anything you do with a mouse would be from later, when the system is no longer dependent on which drivers are in the “initrd”.

#4

Can you tell us more about your usb controller hardware perhaps? Are they USB 3.0 ports we’re dealing with here?

usb-devices
#5

An addendum to my earlier reply. I did report that as Bug 879775. I closed the bug report when a BIOS update fixed the problem.

There’s some output attached to that bug report, that you could compare to what you are seeing.

#6

They have updated the bios, twice,
http://www.gigabyte.us/products/product-page.aspx?pid=4642#bios
I’ve never flashed the bios before, any links I could follow for an idea of what to do? True I probably could figure it out, but it’s the bios I’ll be dealing with.

Here’s the output of usb-devices
http://susepaste.org/57740604

Here’s the output of dmesg
http://susepaste.org/49246702

I remade the intrid, no go.

And as to weather it was the usb 2.0 or 3.0 ports, it is the 2.0 . Thanks for the hint, the mouse and everything else works well on the usb 3.0 ports. But kinda wanted more then 2 usb ports working on my system.

#7

Here’s the output of usb-devices
http://susepaste.org/57740604

T:  Bus=01 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#=  4 Spd=1.5 MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=046d ProdID=c05a Rev=63.00
S:  Manufacturer=Logitech
S:  Product=USB Optical Mouse
C:  #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=02 Driver=usbhid

Okay that looks fine.

And as to weather it was the usb 2.0 or 3.0 ports, it is the 2.0 . Thanks for the hint, the mouse and everything else works well on the usb 3.0 ports. But kinda wanted more then 2 usb ports working on my system.

Yep, understood. A bug report may be in order…

#8

Here’s the kernel messaging relating to the mouse

  257.521555] usb 1-1.1: new low-speed USB device number 4 using xhci_hcd
  257.545989] usb 1-1.1: New USB device found, idVendor=046d, idProduct=c05a
  257.546000] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
  257.546007] usb 1-1.1: Product: USB Optical Mouse
  257.546013] usb 1-1.1: Manufacturer: Logitech
  257.546258] usb 1-1.1: ep 0x81 - rounding interval to 64 microframes, ep desc says 80
microframes
  257.593657] usbcore: registered new interface driver usbhid
  257.593666] usbhid: USB HID core driver
  257.608469] input: Logitech USB Optical Mouse as
/devices/pci0000:00/0000:00:04.0/0000:02:00.0/usb1/1-1/1-1.1/1-1.1:1.0/input/input18
  257.608803] hid-generic 0003:046D:C05A.0001: input,hidraw0: USB HID v1.11 Mouse [Logitech USB
Optical Mouse] on usb-0000:02:00.0-1.1/input0

It might be useful to compare behaviour (output) when attaching to a USB 2.0 port.

It is interesting (although not the subject of this thread) to note the problems with the attached USB storage device reported for example

  240.728875] usb 1-1.2: new high-speed USB device number 3 using xhci_hcd
  240.746579] usb 1-1.2: New USB device found, idVendor=154b, idProduct=007a
  240.746590] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
  240.746597] usb 1-1.2: Product: USB 2.0 FD
  240.746603] usb 1-1.2: Manufacturer: PNY Technologies
  240.746608] usb 1-1.2: SerialNumber: ADA4HE03000000035
  240.746855] usb 1-1.2: ep 0x81 - rounding interval to 128 microframes, ep desc says 255 microframes
  240.746864] usb 1-1.2: ep 0x2 - rounding interval to 128 microframes, ep desc says 255 microframes
  240.822142] usb-storage 1-1.2:1.0: USB Mass Storage device detected
  240.822366] scsi6 : usb-storage 1-1.2:1.0
  240.822555] usbcore: registered new interface driver usb-storage
  242.324728] scsi 6:0:0:0: Direct-Access     PNY      USB 2.0 FD       1100 PQ: 0 ANSI: 4
  253.443386] usb 6-2: new full-speed USB device number 26 using ohci-pci
  253.583619] usb 6-2: device descriptor read/64, error -32
  253.827968] usb 6-2: device descriptor read/64, error -32
  254.068327] usb 6-2: new full-speed USB device number 27 using ohci-pci
  254.208524] usb 6-2: device descriptor read/64, error -32
  254.452880] usb 6-2: device descriptor read/64, error -32
  254.693219] usb 6-2: new full-speed USB device number 28 using ohci-pci
  255.101757] usb 6-2: device not accepting address 28, error -32
  255.238041] usb 6-2: new full-speed USB device number 29 using ohci-pci
  255.646569] usb 6-2: device not accepting address 29, error -32
#9

I’m not sure a BIOS update will help. They don’t mention USB problems in their description of the change.

It looks as if the BIOS updater is a Windows executable. If you have Windows, then you run that program (as administrator), and reboot after it is done.

If you don’t have Windows, I don’t know how to update.

In the case of the USB problems that I was having, it looked as if the USB controller was designed to use the “xhci” driver. My system was having problems trying the “ehci” driver. Apparently the BIOS must give some information on which driver to use, and was getting that wrong. I’m not at all sure how applicable that is to your system.

I agree with Deano, that this might be worth a bug report.

#10

And as to weather it was the usb 2.0 or 3.0 ports, it is the 2.0 . Thanks for the hint, the mouse and everything else works well on the usb 3.0 ports. But kinda wanted more then 2 usb ports working on my system.

For the moment, a pragmatic approach may be to use a USB 3.0 hub. (Research/choose carefully though!)

#11

I’ve experienced this.

New MB with USB2 and USB3 ports.

To get everything working I had to plug the HP USB printer and HP USB scanner in the USB2 ports and wireless kdb receiver and wired mouse in the USB3 ports in the back panel.

I don’t recall which right now, but either the printer or the scanner wouldn’t work with USB3 and likewise for the kbd or the mouse with USB2.

I fiddled a bit with the USB settings in BIOS but no dice, ended up juggling cables. Lousy solution, as there’s no USB3 header and only two USB3 ports in the back.

#12

Nothing works on the USB 2.0 ports, I’ve tried a USB to SATA adapter, two mice, all known good and operate properly on the USB 3.0 ports. WHere should I send the bug report? Upstream? THe kernel driver developers? The manufacturer of the motherboard? Or perhaps, considering the other output, as noted by deano_ferrai, to a combination thereof?

#13

Could be the usb2 chip is simply DOA New MB are not always perfect

#14

OK, how do I test for this?

#15

Try another OS maybe?? try another USB plug in that uses another chip for control, there are normally at least 2 on a board if some plugs support 2 and some 3?

#16

I booted up knoppix 7.2 which has the following USB related packages installed:
firmware-linux-free 3.2
firmware-linux-nonfree 0.36+wheezy.1
linux-image-3.9.6
linux-image-3.9.6-64

All ports worked, as opposed to suse with which non of the USB 2.0 ports work, I repeat non of them, meaning I tested them. I’ll try ubuntu and fedora and tell you the resalts I get from them.

#17

Now that you have seen it work in Knoppix, I recommend raising the bug report on openSUSE. Likely against the openSUSE packaged version of the kernel.

Make note in your bug report the Knoppix version where it worked, and also the Knoppix kernel version.