[regression] wireless card does not work in gutsy, ma311

I'm having troubles with the hostap driver, too. I have a Thinkpad T30 whose wireless support seems to break in different ways with each new release :-(

I've found that if I blacklist hostap_pci in /etc/modprobe.d/blacklist, reboot, then _manually_ load hostap_pci (sudo modprobe hostap_pci), I can connect using the network administrative applet.

Still missing orinoco_pci, though...

Thank you for taking the time to report this bug and helping to make Ubuntu better. Could you both of you please add the full output of 'sudo lspci -vvn' as attachments to your bug report so we can identify the specific cards that are problematic? Thanks in advance.

The bug represents a regression in hardware support. More than that, this bug can cause computers with the card in question to hang. For less experienced users, this might as well be the destruction of their entire computer, since they wouldn't know how to recover from it. If this bug isn't resolved before gutsy is released, any owners of this card will find themselves with a broken system.

Therefore I think this bug's importance should be set to critical.

At the very least orinoco_pci should be reinstated as it was in edgy/feisty. It didn't work out of the box, but at least the system shipped with the correct driver. This way, whilst we won't have made any progress, at least we won't have made things potentially much worse.

Seems to be a dupe/similar to #125832. (https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/125832)

It is very similar to it, yes, since the same family of kernel modules were taken out in the same kernel upload (orinoco_*). That bug report is specifically about the orinoco_cs component, whilst this one is about orinoco_pci.

Perhaps this bug should be considered a dupe, then, since these modules were disabled simultaneously? But then again, the solution involves manually changing PCI IDs in the respective modules, so perhaps these bugs should stay separate!

Either way, the effects of these bugs are important. I'd hate to see gutsy released with regressed support for wireless cards.

Why oronoco have been disabled ... My Pcimcia wifi card doesn't because of that ... and on the french Forum a lot of people want it come back ...

This driver is much used in france because of an internet access company that give it freely ...

I have an MA311 myself and it sort of works with hostap_pci (Gutsy and now Hardy) but there are issues like Bug #89464 .

By the way if you have a pure prism PCMCIA card you can still use orinoco_cs . It seems to be the plx and pci drivers that have been removed.

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

This bug report is being closed because we received no response to the previous inquiry for information. Please reopen if this is still an issue in the current Ubuntu release, Jaunty Jackalope 9.04 - http://www.ubuntu.com/getubuntu/download. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

-Bryan