wlan card not detected

[Carlos Kassab]

My wireless network card is not being detected when booting from cd rom, maybe some drivers not loaded?

My computer is a hp pavilion ze5400
the network card has an intersil corporation prism 2.5 wavelan chipset

[amiga_os (peterdanielmyers)]

Neither my wlan nor my ethernet card are detected by feisty.

Both are registered on the new "Ubuntu devices" list, and both show up in lspci.

Gnome "networking" applet (in the System->Configure menu) shows nothing (not even my modem), and the network-manager in the notification bar just says "No network devices detected"

This problem happened during Edgy development also. And gnome-network-manager never detected my wireless card when I used it in Dapper or Edgy.

I remember having a discussion as to the importance of this bug - it was triaged quite low in Edgy development. Can I suggest it be triaged quite high? There is no way I can update anything in Feisty (which is an upgrade from an Edgy installation)... this makes the problem a real killer as there is no way to solve it, unless I download and install a newer version later.

Apart from the obvious frustration this brings, it yet again means I can't help with bug-fixing the next Ubuntu...

I've attached my lspci output from within Feisty.

[Brian Murray (brian-murray)]

Thanks for your bug report. Could you please add the output of 'lspci -vv' and 'dmesg' to it? Thanks in advance.

[amiga_os (peterdanielmyers)]

sorry but I no longer have feisty installd. This is lspci -vv from within edgy

[amiga_os (peterdanielmyers)]

this is dmesg from within edgy

[Kyle McMartin (kyle)]

The problem is Realtek use the same PCI Ids for multiple revisions of the cards, and we don't support your revision yet.

[Kyle McMartin (kyle)]

Can you attach "lsmod" from edgy? Thanks.
 Kyle

[Carlos Kassab (carlos-kassab)]

This is lsmod from my actual edgy instalation where my network card is working now.

[Launchpad Janitor (janitor)]

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!

[Leann Ogasawara (leannogasawara)]

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.

[Markus Korn (thekorn)]

Unfortunately this bug report is being closed because we received no response to the last inquiry for information. However, the Intrepid Ibex 8.10 Beta release was most recently announced - http://www.ubuntu.com/testing/intrepid/beta . If you are able to confirm this is still an issue with this most recent release please feel free to reopen this report. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New".

Thanks,
Markus

[Launchpad Janitor (janitor)]

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.