madwifi no longer working in kernel 2.6.22-12 and 2.6.22-14

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information.

Please include the information requested at [WWW] https://wiki.ubuntu.com/DebuggingHardwareDetection as separate attachments.

Ok,so I booted into windows to check to make sure the hardware was working; it was.

then I booted my gutsy alpha CD (on which the wireless was working). It was working there was well
I noticed however, that it was using a slightly older version of madwifi: .9.3 instead of .9.3.2 on the
release candidate.

I then booted back into my installed system... and lo- and behold, wireless was working.
It has been a bit finicky since though, but I think its a Network manager problem. I don't know
what the problem could be, maybe bad firmware?

Hi.

I had the same problem, but a different card. Mine is a Belkin f7010, version 7 or 7000 (same thing). In Fiesty, I got it to work just by following these instructions:

"http://www.realtek.com.tw/downloads/...Downloads=true

Download the windows xp version of net8185.inf

Extract the file into a directory of your choice.

install the driver
sudo ndiswrapper -i net8185.inf
update the driver with the PCI ID
sudo ndiswrapper -a 1799:700f net8185
restart the computer.
then ndiswrapper -l should show that it exists.
net8185 : driver installed
device (1799:700F) present
then configure it through System>Admin>Networking"

So, that worked in Fiesty, and it did in Gutsy too - ndiswrapper -l reported the device present. However, ifconfig, iwconfig still would not see it, _at all_. I tried a whole bunch of commands, one of them being "sudo lshw -C network". At the bottom of the output, it said *network UNCLAIMED, and then said a bunch of things about my Belkin card (sorry, the terminal didn't save the output as I was randomly trying every command I found to get it working). The next thing that did it was doing "ifconfig wlan0 up" - tried it out of the blue, since I remember wlan0 being my wireless. That did something, as iwconfig now reported the card. After that I went to system - administration - network, my wireless was there. I manually connected to a network, had to choose the automatic DHCP configuration, then clicked "Ok", and had to enable the wireless device.

That didn't finish it though, but by that time, my Wicd was able to see the networks about me, and I connected to one just fine.

I'll attach the logs as needed. I'm really hoping this could be fixed, because it was -way- easier to get wireless working in Fiesty (I was told that the new kernel has a new wireless "stack", maybe that's it?)

i can confirm this with an acer aspire 3100. in feisty it worked, but after upgrade to gutsy ist stopped working. ndiswrapper in my opinion isn't a solution, since madwifi driver should work natively on linux.

dmesg.log

Georg,

try a "sudo /etc/init.d/dbus restart" which seems to fix it for me whenever the radio turns itself off or something wonky like that.

Why is this of low importance ? It seems like a major issue to me as it seems to affect also non amd64 computers.

Same bug with a ACER Aspire 3610 computer and this wifi card:
Atheros communications, Inc. AR2413 802.11bg NIC (rev 01)

It was working perfectly before.

"sudo /etc/init.d/dbus restart" doesn't solve the problem for me.

I have found what the problem is.
It is directly tied to the operation of the wireless switch (at least on my computer)
In order to fix it, you have to boot a liveCD (gutsy amd64 did it for me) which
I assume has something to do with resetting its HAL status.

I am assigning this bug to the 'ubuntu-kernel-team' per their bug policy. For future reference you can learn more about their bug policy at https://wiki.ubuntu.com/KernelTeamBugPolicies .

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.