[Karmic] USB problems and no USB mouse after upgrade from Jaunty

[Swâmi Petaramesh]

Hi,

On a system with an ASUS M2NPV_VM motherboard, where USB worked perfectly in Gutsy, Hardy, Intrepid and Jaunty, USB doesn't work properly anymore in Karmic.

I notice the following :

- If booting the system from an USB stick with the Kunbuntu 9.10 Karmic AMD 64 "live" image (made from the CD ISO Image with Karmic's "USB startup disk creator") :
- System boots and Ubuntu loads from USB stick (so USB more or less works, at least enough for an USB stick...).
- But USB mouse doesn't work at all - and even the optical mouse LED doesn't light showing that's no X11 problem.
- Actually the USB mouse LED is lit during system POST and BIOS boot, but turns off as soon as Linux kernel starts.
- Pluging / unpluging the mouse produces absolutely no output to syslog, just as if no mouse existed at all.
- Same behaviour on any USB port of the machine.

- If booting the system from an USB stick with Kubuntu 9.10 Karmic AMD "Alternate installer" (made from the CD ISO Image with Karmic's "USB startup disk creator"), the mouse LED stays lit all the time, so the "alternate" kernel behaviour is obviously different and probably better (but I didn't check it any further, being in the "text installer", I just noticed that with this one the mouse was lit).

- Anyway once Karmic is installed (fresh install from scratch on the system), the optical USB mouse won't work and won't light its LED.

[Swâmi Petaramesh (swami-petaramesh)]

Happens with Kernels 2.6.31-14 and 2.6.31-16.

With both kernels, booting with the "nosplash" option very temporarily corrects the problem : The mouse lights up and cursor moves, but very soon this causes the mouse and keyboard to lock completely.

Pluging the same mouse to the PS/2 port (with a Logitech USB=>PS/2 mouse adapter) allows the mouse and system to work normally, but there's definitely some very weird USB issue there - same mouse was working perfectly in USB with all Ubuntu versions priori to Karmic...

[Leann Ogasawara (leannogasawara)]

Hi,

Can you boot with the USB mouse plugged in. Then capture and attach the following:

1) dmesg > dmesg.out
2) sudo lsusb -v > lsusb

Thanks.

[Swâmi Petaramesh (swami-petaramesh)]

Hi Leann,

After having booted with the USB mouse plugged, "lsusb" completely hangs with no output an cannot even be "kill -KILL" -ed ; it causes the kernel to spit ugly messages in syslog.

I will attach the dmesg including those ugly messages ;-)

[Swâmi Petaramesh (swami-petaramesh)]

I have found a solution that makes the mouse and USB work properly again in Karmic, by disabling "USB Legacy support" in the machine's BIOS setup...

  *-core
       description: Motherboard
       product: M2NPV-VM
       vendor: ASUSTek Computer INC.
     *-firmware
          description: BIOS
          vendor: Phoenix Technologies, LTD
          physical id: 0
          version: ASUS M2NPV-VM ACPI BIOS Revision 1401 (08/07/2008)

[Dale Larson (dlarson42)]

"On a system with an ASUS M2NPV_VM motherboard, where USB worked perfectly in Gutsy, Hardy, Intrepid and Jaunty, USB doesn't work properly anymore in Karmic."

I'm having the same problem with the exact same motherboard. I've installed Karmic and whenever my USB Interlink (VP6410R) wireless keyboard and mouse is plugged in the hub processing seems to hang. It's a lowspeed device. I've never had a problem with this keyboard under Ubuntu until I installed Karmic.

uname -a yields:

Linux mythtv 2.6.31-16-generic #53-Ubuntu SMP Tue Dec 8 04:01:29 UTC 2009 i686 GNU/Linux

I've attached "lspci" and "dmesg" logs. "lsusb" just hangs indefinitely (I let it run over night).

[Dale Larson (dlarson42)]

"I have found a solution that makes the mouse and USB work properly again in Karmic, by disabling "USB Legacy support" in the machine's BIOS setup..."

This workaround worked for me as well. Thank you!

Unfortunately there appears to be an issue with the USB Host subsystem.

[Brad Figg (brad-figg)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.