[Hardy][ath_pci madwifi] network-manager prevents atheros chip from connecting to the internet

please test if the bzr branch i just associated with this bug fixes this ath_pci issue for you.

To build:

 1. get the branch
 2. build using debuild -b

To test:

 1. install libnm-*.deb and network-manager*.deb produced by the build
 2. test to connect to wpa ... test to reboot ... and so on.

Thanks,
 - Alexander

Hi,

I don't think its wise to tell bugreporters to test branches.
I had to install bzr, fakeroot as well as build-dep network-manager – I don't think many users are willing to do that, just to confirm something. In fact most people won't even know how to to it anyway.

And still I didn't get this to work:

warning, `debian/libnm-util-dev/DEBIAN/control' contains user-defined field `Original-Maintainer'
dpkg-deb: ignoring 1 warnings about the control file(s)
dpkg-deb: building package `libnm-util-dev' in `../libnm-util-dev_0.6.6-0ubuntu2_i386.deb'.
 dpkg-genchanges -b
dpkg-genchanges: binary-only upload - not including any source code
dpkg-buildpackage (debuild emulation): binary only upload (no source included)
Now signing changes and any dsc files...
 vsignfile network-manager_0.6.6-0ubuntu2_i386.changes Alexander Sack <email address hidden>
gpg: skipped "Alexander Sack <email address hidden>": secret key not available
vgpg: [stdin]: clearsign failed: secret key not available
debsign: gpg error occurred! Aborting....
vdebuild: fatal error at line 1174:
running debsign failed

----------

I tried to install the packages anyway.
Had to install dhcdbd to make that work.

Then I installed network-manager-gnome again and this is what I get when trying to run nm-applet:

** (nm-applet:6324): WARNING **: <WARN> nma_dbus_init(): could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.50" is not allowed to own the service "org.freedesktop.NetworkManagerInfo" due to security policies in the configuration file'

** (nm-applet:6324): CRITICAL **: nma_dbus_enable_networking: assertion `applet->connection != NULL' failed

** (nm-applet:6324): WARNING **: <WARN> nma_dbus_init(): could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.50" is not allowed to own the service "org.freedesktop.NetworkManagerInfo" due to security policies in the configuration file'

(last message gets repeated indefinitely)

OK, after a reboot nm-applet got started automatically (via its entry in the Startup Programs) and it works.

I'm still worried about the aforementioned error messages but I had a look at the daemon.log and things seem to be fine.
I attached the part of the last login (current one).

I haven't rebooted yet, but this seems to have fixed the problem. When I updated to 0.6.6, networking broke, and when i updated to this bzr branch, it was fixed

Is there a binary build of this so-called bzr branch?

I am will to test/confirm a fix, but don't have the time resources to build it.

@tippettm:

It's really easy to build, you just need to have the dependencies installed, so

sudo apt-get build-dep network-manager
bzr branch http://bazaar.launchpad.net/~ubuntu-core-dev/network-manager/ubuntu.0.6.x
cd ubuntu.0.6.x
debuild -b
cd ..
sudo dpkg -i libnm*.deb
sudo dpkg -i network-manager*.deb

That's all you should need to get all the packages built. Although, I hacked the debian/changelog file to change the version to 0.6.6-0ubuntu2~hardy1 so that the final 0ubuntu2 package would override it. The build only took a few minutes on my laptop, which doesn't usually compile very fast.

Also, be sure you have bzr installed.

Thanks,

The comment (as others have mentioned in the thread) wasn't that the building is an issue (network-manager is a small application), it is the understanding about what to do to get the bzr stuff built. You probably saved an hour of anyone's time who is interested in confirming. Most users who haven't dealt with building deb packages, or bzr, or other parts of the Ubuntu development process have to hunt and chug through trying to understand what to do. What takes an experienced dev a few minutes, may take an experienced user (but not experienced dev) a number of hours full for confusion and dead ends to assist in confirming a good fix.

I will follow the commands blindly from above, but first up bzr took 35 minutes to get about 15% of the sidebar, so I am starting again...

Once I have something down, I will report back success or failure.

I can confirm that the bzr branch works.

I've since rebooted, and can confirm that the bzr branch works as well.

I've been able to connect to my school and home networks, which are both WPA-secured

thanks to all for testing this. lets hope that we get a wext capable driver for ath_pci at some point.

@tippettm, your comments are valid. i prefer to post bzr branches instead of packages if i only want testing from a considerably narrow community (e.g. those that see this bug), but i agree that more detailed instructions are helpful (and as its just three steps it should be totally feasible for me to do so) and i will do this in future.

This bug was fixed in the package network-manager - 0.6.6-0ubuntu2

---------------
network-manager (0.6.6-0ubuntu2) hardy; urgency=low

  * resurrect and adapt driver tweaks to new code base for ath_pci cards
    (LP: #202453).
    - add debian/patches/42a_ath_pci_supplicant_tweaks.patch
    - update debian/patches/series
  * add Replaces: network-manager-gnome (<< 0.6.5) as network-manager started
    to ship vpn files in after the source package split introduced by 0.6.5.
    this fixes the file overwrite problem on dapper->hardy upgrades.
    (LP: #203707)
    - update debian/control

 -- Alexander Sack <email address hidden> Tue, 18 Mar 2008 22:19:03 +0100

This last update prevents network manager from working at least with my setup...

I'm using x86_64 ubuntu hardy and the hardware consists of an iwl3945 wireless card.

I get the following in syslog:
=====================================================================
Mar 21 20:12:47 luis-lpt NetworkManager: <info> Activation (wlan0) started...
Mar 21 20:12:47 luis-lpt NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Mar 21 20:12:47 luis-lpt NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Mar 21 20:12:47 luis-lpt NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Mar 21 20:12:47 luis-lpt NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Mar 21 20:12:47 luis-lpt NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Mar 21 20:12:47 luis-lpt NetworkManager: <info> Activation (wlan0/wireless): access point 'kamikazeII' is encrypted, but NO valid key exists. New key needed.
Mar 21 20:12:47 luis-lpt NetworkManager: <info> Activation (wlan0) New wireless user key requested for network 'kamikazeII'.
Mar 21 20:12:47 luis-lpt NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Mar 21 20:12:47 luis-lpt NetworkManager: <info> Activation (wlan0) New wireless user key for network 'kamikazeII' received.
Mar 21 20:12:47 luis-lpt NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Mar 21 20:12:47 luis-lpt NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Mar 21 20:12:47 luis-lpt NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Mar 21 20:12:47 luis-lpt NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Mar 21 20:12:47 luis-lpt NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Mar 21 20:12:47 luis-lpt NetworkManager: <info> Activation (wlan0/wireless): access point 'kamikazeII' is encrypted, and a key exists. No new key needed.
Mar 21 20:12:48 luis-lpt NetworkManager: <WARN> nm_signal_handler(): Caught signal 11. Generating backtrace...
Mar 21 20:12:48 luis-lpt NetworkManager: ******************* START **********************************
Mar 21 20:12:48 luis-lpt NetworkManager: (no debugging symbols found)
Mar 21 20:12:48 luis-lpt NetworkManager: Using host libthread_db library "/lib/libthread_db.so.1".
Mar 21 20:12:48 luis-lpt NetworkManager: (no debugging symbols found)
Mar 21 20:12:48 luis-lpt last message repeated 10 times
Mar 21 20:12:49 luis-lpt NetworkManager: [Thread debugging using libthread_db enabled]
Mar 21 20:12:49 luis-lpt NetworkManager: [New Thread 0x7ff3bb29a780 (LWP 11813)]
Mar 21 20:12:49 luis-lpt NetworkManager: [New Thread 0x40a06950 (LWP 11820)]
Mar 21 20:12:49 luis-lpt NetworkManager: [New Thread 0x41fba950 (LWP 11816)]
Mar 21 20:12:49 luis-lpt NetworkManager: (no debugging symbols found)
Mar 21 20:12:49 luis-lpt last message repeated 9 times
Mar 21 20:12:49 luis-lpt NetworkManager: 0x00007ff3b9611cc6 in poll () from /lib/libc.so.6
Mar ...

debian/patches/42a_ath_pci_supplicant_tweaks.patch causes the above Segmentation Fault for almost (if not all) wireless users. wired networks are unaffected.

I did some testing on my system that has an Atheros card and wext works fine when I configure WPA_Supplicant by hand. I don't think it is necessary to use -D madwifi anymore but maybe we still need to use AP_SCAN=2?

The latest update (although it could be a couple of days back, TBH) has fixed this for me.