Network-Manager not working with madwifi

[Guille]

Binary package hint: linux-restricted-modules-2.6.20-14-generic

I updated Fesity today, linux-restricted-modules was updated, after that Network-Manager doesn't work with madwifi drivers and my atheros wifi, he device stills works.
I tried with ndiswrapper and Network-Manager works as usual, so I think the last build of the madwifi may be the problem with Network-Manager.

My system is Festy, Network-Manager 0.6.4

[Jordan Reese (jordanmreese)]

I am experienceing the same issue, my card is a netgear wg511t (atheros chipset)

[damagedspline (icpazi)]

I have this issue aswell...

Please try to run the attached script and see if it works, this script should be run before each connection attempt - I've commented out 2 lines that activate/deactivate the wireless led (needed for my Fujitsu).

My wireless card is:
                description: Wireless interface
                product: AR5005G 802.11abg NIC
                vendor: Atheros Communications, Inc.
                physical id: 5
                bus info: pci@02:05.0
                logical name: wifi0
                version: 01
                serial: 00:c0:a8:af:21:9b
                width: 32 bits
                clock: 33MHz
                capabilities: bus_master cap_list logical ethernet physical wireless
                configuration: broadcast=yes driver=ath_pci ip=192.168.1.216 latency=168 maxlatency=28 mingnt=10 multicast=yes wireless=IEEE 802.11g
                resources: iomemory:d0200000-d020ffff irq:16

[Javier Jardón (jjardon)]

Any already configured devices that you want to be available in Network Manager will need to de-configured, as otherwise they will be ignored.

The easiest way to do this is by going to System -> Administration -> Networking and then going to "Properties" of each connection. In Properties, just untick the "Enable this connection" checkbox. Logout then log back in again. These connections should now be available in Network Manager.

OR, the harder way, is to backup and then edit the /etc/network/interfaces file to remove the configuration of these devices (except for lo which is needed for the loopback interface). You will have to save the file and reboot for the changes to take effect (or don't reboot and run /etc/init.d/networking restart instead). For example, if you wanted Network Manager to be able to control all of your devices, your /etc/network/interfaces file would look somewhat like the following:

auto lo
iface lo inet loopback

[Javier Jardón (jjardon)]

Do you still have problems?

[dawn (dawnmslack)]

No, sorry, I was able to get it working. Thank you for the assistance.

----- Original Message ----
From: Javier Jardón <email address hidden>
To: <email address hidden>
Sent: Monday, May 7, 2007 12:58:55 PM
Subject: [Bug 105637] Re: Network-Manager not working with madwifi

Do you still have problems?

--
Network-Manager not working with madwifi
https://bugs.launchpad.net/bugs/105637
You received this bug notification because you are a direct subscriber
of a duplicate bug.

[Javier Jardón (jjardon)]

Thanks dawn,

and damagedspline, Guille, Jordan Reese; Do you still have problems?

[Jordan Reese (jordanmreese)]

i havent use the laptop with that card, although i may update to that card so i will check soon.

[damagedspline (icpazi)]

I'm still having issues, but it might be linked to the acerhk kernel module (which is the wireless led controller).

I need to activate the led, deactivate it, rmmod ath_pci, kill networkmanager, modprobe ath_pci, restart network manager, reactivate the led and only then it works. btw, it networkmanager doesn't show nearby routers unless manual connection attempt was commenced...

It might be a hardware design issue other then bug in networkmanager (beside the non-scanning part).
(I use Fujistu-Seimens laptop branded Amilo A1650G)

[Phurter (johnmckinzie)]

You say that the attached script (wireless.sh) should be ran before every connection attempt. Where would you place this script for that to happen? Would "/etc/network/if-pre-up.d" be the right place?

[Phurter (johnmckinzie)]

By the way, I have a WG311T. Can't for the life of me get it working.

[damagedspline (icpazi)]

Well, I'm not sure in which script it should be...
AFAIK, If you put it "/etc/network/if-pre-up.d" you'll still need to run "ifdown ath0" and "ifup ath0", so that the script will run...

I would suggest to run it manually. (you should've checked if its working)
It's weird... I've started using Mandriva Spring, they don't use NetworkManager, and the wireless works... Maybe madwifi just have problem with some wireless chipsets when using NetworkManager.

On final note, NetworkManager should have ifup/ifdown scripts of it's own -but thats should be on a wishlist (then the script should change aswell, since no point in killing NetworkManager).

[Javier Jardón (jjardon)]

 We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

[damagedspline (icpazi)]

Actually there is a possible quickaround I found a couple of weeks ago, however it may not be battery friendly since the wireless will remain always on.

For all of you that have issues with NetworkManager and their madwifi wireless card, try load the ath_pci with rfkill=0 and see if it works for you.
meaning:
sudo rmmod ath_pci #to unload the ath_pci
sudo modprobe ath_pci rfkill=0 #load the ath_pci module

[Chris Rowson (christopherrowson)]

This bug looks like a combination of both madwifi and network-manager with neither being fully at fault!

Network manager scans for new networks whilst the card is associated with an access point.

It looks like madwifi doesn't support 'background scanning'

When a scan is performed on the instruction of network manager, the card disconnects from the access point.

See here for more info https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/37821

Fixes look to either prevent network manager from running scans whilst connected to an access point (after all, why would you want to?). Another fix would be to implement background scanning into the driver...

[Chris Rowson (christopherrowson)]

Although if linux-restricted-modules-2.6.20 ships with madwifi 0.9.1 - Current WEXT compliance should have been added to this release as requested here http://madwifi.org/ticket/462