kernel 2.6.35-24-generic breaks many devices

Last one. And I forgot to mention this is on Maverick Meerkat.

The USB/HAL System is defect such that some devices brake the future use of others.

E.g.,
- the Realtek RTL8191S if present at boot prevents many other usb devices to function.
- the Huawei E182E if present at boot prevents my mouse, WiFi Link 5100, and Toshiba Corp. F3507g Mobile Broadband Module to function.

If booting into the older kernel 2.6.35-23 (otherwise identical installation), everything works.

This kernel also breaks Ralink 2870 USB wireless network adapters.

http://ubuntuforums.org/showthread.php?t=1656252

This kernel also breaks Ralink RT2680-based wireless network adapters.

http://ubuntuforums.org/showthread.php?t=1661498

It appears that this kernel also breaks the Lite-On 82c168 (using the tulip driver). I upgraded over the New Year and then started to experience an unresponsive ethernet interface after a short period of network activity. Interestingly, downing the interface, bringing it back up, and re-adding the default route (ifconfig eth0 down; ifconfig eth0 up; route add default gw ...) makes it work again and then the cycle repeats; after a short period of network activity, it becomes unresponsive again.

This also affects my machine with the Realtek 8111 Ethernet card and the Intel WiFi 5100 AGN.

Patches, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 10, 2012.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in a supported release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. As well, please comment on which kernel version specifically you tested.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream', and comment as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]