intrepid 64 bit usb issue

[orkinoks]

Hi;
I have installed Intrepid 64 bit final release on a Asus M3N78 mainboard.When I connect my Fuji Finepix5800 camera to USB, it looks like all my USB devices are locked, such as my usb mouse.Also I can't browse the camera with FSPOT or via Nautilus.All I can do is restart the computer, I had the same issues in Beta version, but I thought these problems would be over with the final release, but even a clean install did not solve my issue.

Any helps or ideas will be apreciated.

[Dan Trevino (dantrevino)]

 Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

[Javier Bolaños (oretachi)]

Hi everyone,

I think I have the same issue with the last version of Ubuntu (8.10 Intrepid, up to date). My problem appear when I connect any usb flash memory or card reader (and when I'm printing).

I have an Asus M3N78 pro, an AMD Phenom 9550 Quad-Core, 4Gb and graphic (nvidia 8300), sound and lan on-board; mouse and keyboard are connected via usb and a wacom graphire tablet too. The printer model is HP PSC1310 and the usb flash memories are generic. Now my system information is Ubuntu 8.10 Intrepid Ibex x86-64, Linux Kernel 2.6.27-11-generic (but I try with 2.6.27-7 and 2.6.27-9, generic and server, and x86 version too, with the same issue)

When I connect the usb flash memories or when I'm printing, the usbs crashes and the usb mouse freezes (however I can move the pointer with the wacom tablet :| and the usb keyboard are still running) I try tapping 'lsusb' in a terminal, but it doesn't responds (if I don't connect any extra usb 'lsusb' responds normally)

I hope this information is useful and someone find a solution; I love this distribution.

Thanks in advance (and sorry about my bad english :P)

[Javier Bolaños (oretachi)]

Hi,

I have more information about this bug. I tried to modify the boot command adding nosplash and noapic instructions; Then I can see this information on boot:

[16.244360] /build/buildd/linux-2.6.27/drivers/hid/usbhid/hid-core.c: usb_submit_urb(ctrl) failed

However, when I login into the system the bug is over; I can connect any usb flash memory and card reader, usb bluetooth (I haven't tried to print yet) and my usb mouse doesn't freeze and the usbs remains ok.

It can be a temporally solution for whom have this problem.

I hope you find a solution soon. See you, and thanks.

[Dan Huber (djhuber82)]

I'm seeing similar USB problems with 64-bit Intrepid (8.10) running on an Asus M3N78-EM motherboard. The mouse pointer on my wireless keyboard/trackball combo freezes a few seconds after booting. It only freezes when I move it; if I don't touch the mouse then I can go for hours, but move it for a few seconds and it freezes up every time. The keyboard (same wireless receiver) keeps working. There is nothing in dmesg when the freeze happens. Only a reboot will restore it; repluging the receiver or restarting X doesn't work. Adding "noapic" to the boot options lets me use the mouse for a few minutes instead of a few seconds, but it still freezes.

This seems very similar to the USB problems reported with Dell E521, which is also an nvidia USB controller:
https://bugs.launchpad.net/linux/+bug/67734
That bug was fixed by a BIOS update.

I tried disabling all power management features, upgrading to NVIDIA driver 180.51, flashing the latest BIOS, screwing with BIOS settings. Nothing has worked. Finally got fed up an bought a PCI-E USB hub, and the mouse has worked flawlessly ever since. But this is far from an ideal solution, as the card is not recognized by the BIOS or grub.

I would really like to find a better way to fix this.

[José Ernesto Dávila Pantoja (josernestodavila)]

 We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!