network-manager in feisty is broken

Thank you for your report please try the following.

open a terminal and type the following.

sudo cp /etc/network/interfaces /etc/network/interfaces.bak

now do the following.

sudo gedit /etc/network/interface

scroll down the list until you find your wireless connection and delete the two lines. Save the file, then reboot your machine.

If that fails you can reset to the default with the following.

sudo rm /etc/network/interfaces

sudo mv /etc/network/interfaces.bak /etc/network/interfaces

If this solves your problem please report back many thanks.

There is no ath0 in the /etc/network/interfaces

My problem at first is with the wire. It claim that I have NO network device when the wireless driver is not loaded. eth0 is there and working (on board, using the tg3 driver).

Try following the examples here https://launchpad.net/bugs/78037

and here http://ubuntuforums.org/showthread.php?p=2092813

Someone else had a similar sounding problem on two different cards and these links fixed them.

Please let me know how you get on.

does not help at all. The problem is that Network manager think I have NO network device. And then programs like Gaim think I have no network because of Network Manager.

The only proof that my network cards work is because it let the IP packet go through so I can file that bug.

Okay can you try the following please.

In a terminal type

NetworkManager --no-daemon

and log the results. Also could you check /var/log/syslog and see if Network Manager is very verbose there.

$ sudo NetworkManager --no-daemon
NetworkManager: <information> starting...
NetworkManager: <information> Updating allowed wireless network lists.

That's all. then it hangs. (wifi driver is NOT loaded atm, as I don't care)

If I modprobe the wifi driver, I get this:

NetworkManager: <debug info> [1170363249.391205] nm_hal_device_added (): New device added (hal udi is '/org/freedesktop/Hal/devices/net_00_14_a4_61_ac_29').
NetworkManager: <information> ath0: Device is fully-supported using driver 'ath_pci'.
NetworkManager: <information> nm_device_init(): waiting for device's worker thread to start
NetworkManager: <information> nm_device_init(): device's worker thread started, continuing.
NetworkManager: <information> Now managing wireless (802.11) device 'ath0'.
NetworkManager: <information> Deactivating device ath0.
NetworkManager: <debug info> [1170363249.553024] nm_hal_device_added (): New device added (hal udi is '/org/freedesktop/Hal/devices/net_00_14_a4_61_ac_29_0').
NetworkManager: <WARNING> nm_signal_handler (): Caught signal 2, shutting down normally.
NetworkManager: <information> Caught terminiation signal
NetworkManager: <debug info> [1170364775.436088] nm_print_open_socks (): Open Sockets List:
NetworkManager: <debug info> [1170364775.436151] nm_print_open_socks (): Open Sockets List Done.
NetworkManager: <information> Deactivating device ath0.

In short it does not pickup eth0 but does ath0.

Will attach lshal --long and lspci -vvn

Please note that Hubert is running a pre-Dapper kernel.

On Thu, Feb 01, 2007 at 09:30:03PM -0000, Simon Law wrote:
> Please note that Hubert is running a pre-Dapper kernel.

Right. I'm guessing that's due to https://launchpad.net/bugs/76294 ? If
not, could you try upgrading to a newer kernel, Hubert?

--
| Soren Hansen | Linux2Go | http://Linux2Go.dk/ |
| Seniorkonsulent | Lindholmsvej 42, 2. TH | +45 46 90 26 42 |
| <email address hidden> | 9400 Norresundby, Denmark | GPG key: E8BDA4E3 |

I've the same problem.
I've solved it (gaim now work) deconfiguring the eth interface, in fact networkmanager manage my wired connection. The problem is that doing this way i cannot assign a static ip to my machine

Soren, same problem with Feisty official kernel.

Bug 76294 has nothing to do because my problem involve Ethernet without any ath_pci loaded.

On Fri, Feb 02, 2007 at 01:22:47PM -0000, Hubert Figuiere wrote:
> Soren, same problem with Feisty official kernel.

Ok. I'll take a look at it over the weekend.

> Bug 76294 has nothing to do because my problem involve Ethernet
> without any ath_pci loaded.

Yes, I know, but that particular bug makes many madwifi users unable to
boot the official feisty kernels and since you're a madwifi user, I
guessed that you could not boot using that kernel.

Cheers.

Soren Hansen wrote:

> Yes, I know, but that particular bug makes many madwifi users unable to
> boot the official feisty kernels and since you're a madwifi user, I
> guessed that you could not boot using that kernel.

Neither. I don't have linux-restricted.... The madwifi driver has been
compiled by myself from -ng, because the official one from ubuntu never
worked anyway.

#include <binary_blob_rant.h>

Hub

My network connection manager says "eth2:avahi", and it refuses to say that I am connected to the internet. However, with an "ifdown eth2" and then an "ifup eth2", I am able to connect to the internet. I have both a broadcom internal chipset, at eth1, which I never use, and an Aironet external card, which is on eth2 and wifi0. Also, network-manager sees my wireless network, but will not connect to it when I click on it.

as of today, newer kernel (from Feisty), I installed linux-restricted that now works with my Atheros card, and NetworkManager finds it.

Still no luck with the wired connection. I'll try something else.

The wired connection is now recognized.

I don't know exactly what caused that, but as off today in Feisty, it works.

I also have broken network manager. I have two generic Ethernet cards that have always worked before, and which are guaranteed Linux-supported by manufacturers (from Hoary till Dapper have always worked).

I installed Herd 5 yesterday and updated to latest packages. At first both network interfaces worked: Other one is assigned static IP for LAN (eth0), other is assigned IP by DHCP.

A little while later I noticed that either one of the interfaces gets dropped, defaults to no IP assigned. If i go to network manager and reconfigure them, other one starts to work. Say I reconfigure eth1 with dhcp, it gets the IP and starts working, but AT THE SAME MOMENT, the other interface loses its IP. Happens every time, I can have only one interface active and with an IP. Repeated this process several times, always just one interface working at a time. I dont think this can be a hardware issue, since both interfaces DO work, just not at the same time.

This is as of today (25.3.) still broken in the way I described above, using two wired interfaces. Im running Feisty Herd 5 updated to all latest packages. Still am unable to configure 2 interfaces using the network manager, can only have one active interface at a time.

actually it work now. various *kernel* issues that got solved.

Nope :( still broken with latest updates. As described above.

Works for the original reporter. The rest of you can run to bug #82335.