The change was made so that other devices would work. In effect it seems to have broken others. The devices that were broken were a regression from breezy, so in essence we have a dual problem where we had to have this fix to keep things from breaking between breezy and dapper, but in doing so we broke machines that were once working in dapper.
The workaround is likely to remove the ehci_hcd module by performing this command:
sudo modprobe -r ehci_hcd
If you would like to make this permanent, then do:
Sorry, this bug kind of slipped through my bug mbox. I am aware of this problem.
The problem was introduced in 2.6.15-24.41, with this change:
* usb: Enable CONFIG_ USB_EHCI_ SPLIT_ISO and CONFIG_ USB_EHCI_ ROOT_HUB_ TT
- Malone #28840
- Malone #49367
The change was made so that other devices would work. In effect it seems to have broken others. The devices that were broken were a regression from breezy, so in essence we have a dual problem where we had to have this fix to keep things from breaking between breezy and dapper, but in doing so we broke machines that were once working in dapper.
The workaround is likely to remove the ehci_hcd module by performing this command:
sudo modprobe -r ehci_hcd
If you would like to make this permanent, then do:
sudo sh -c 'echo blacklist ehci_hcd > /etc/modprobe. d/blacklist- ehci'
sudo update-initramfs -u -k `uname -r`
This process can be reversed by removing the /etc/modprobe. d/blacklist- ehci file and rerunning the update-initramfs command.
Hope this helps in the interim until this is resolved.