[edgy] Does not detect ipw2200

Bug #60679 reported by Khashayar Naderehvandi
4
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: network-manager

lsmod | grep ipw:

ipw2200 114852 0
ieee80211 34952 1 ipw2200

sudo /usr/sbin/NetworkManager --no-daemon:

NetworkManager: <information> starting...
NetworkManager: <information> eth1: Device is fully-supported using driver '8139too'.
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 wired Ethernet (802.3) device 'eth1'.
NetworkManager: <information> Deactivating device eth1.

There's nothing about eth0 which is my wireless. The wireless works fine though, manually, with good old command line 'iwconfig'. It just doesn't show up in nm-applet. I'm pretty clueless as of what other information to give. So pray tell.

EDIT: sorry, I forget: This is in Edgy.

description: updated
Revision history for this message
Jones D. Le (joneslee85) wrote :

I have experienced the same problem on Edgy Knot-3. And you are right about this bug when it runs with ipw2200. I have downloaded latest cvs NetworkManager and run it but still experienced the same bug, it seems to me more like bugs of NetworkManager rather than bug of Ubuntu.

$sudo /usr/sbin/NetworkManager --no-daemon
NetworkManager: <information> starting...
NetworkManager: <WARNING> nm_dbus_init (): nm_dbus_init() could not acquire the NetworkManager service as it is already taken (ret=3). Is the daemon already running?
NetworkManager: <ERROR> [1158570946.044629] main (): nm_dbus_init() failed, exiting. Either dbus is not running, or the NetworkManager dbus security policy was not loaded.
NetworkManager: traceback:
NetworkManager: /usr/sbin/NetworkManager(main+0x779) [0x8069569]
NetworkManager: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xdc) [0xb7c5d8cc]
NetworkManager: /usr/sbin/NetworkManager [0x8053ce1]
Trace/breakpoint trap (core dumped)

This is the result when i ran with gdb

$sudo gdb /usr/sbin/NetworkManager
GNU gdb 6.4.90-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".

(gdb) r --no-daemon
Starting program: /usr/sbin/NetworkManager --no-daemon
[Thread debugging using libthread_db enabled]
[New Thread -1211774672 (LWP 8055)]
NetworkManager: <information> starting...
NetworkManager: <WARNING> nm_dbus_init (): nm_dbus_init() could not acquire the NetworkManager service as it is already taken (ret=3). Is the daemon already running?
NetworkManager: <ERROR> [1158571329.050569] main (): nm_dbus_init() failed, exiting. Either dbus is not running, or the NetworkManager dbus security policy was not loaded.
NetworkManager: traceback:
NetworkManager: /usr/sbin/NetworkManager(main+0x779) [0x8069569]
NetworkManager: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xdc) [0xb7cd38cc]
NetworkManager: /usr/sbin/NetworkManager [0x8053ce1]

Program received signal SIGTRAP, Trace/breakpoint trap.
[Switching to Thread -1211774672 (LWP 8055)]
main (argc=Cannot access memory at address 0x3
) at NetworkManager.c:765
765 exit (EXIT_FAILURE);

Revision history for this message
Scott Robinson (scott-ubuntu) wrote :

Can you take a look at bug 59981 and let me know if that helps?

Revision history for this message
Khashayar Naderehvandi (khashayar) wrote :

Didn't help here. NM still finds only wired connection. I should probably do a clean install and try again...

Revision history for this message
Scott Robinson (scott-ubuntu) wrote :

Ok, the standard set of questions:

1. Did you remove the interface lines from /etc/network/interfaces? If not, do so and give it a try.
2. Can you attach the results of a "lshal" to your follow-up response after trying #1?

Revision history for this message
Khashayar Naderehvandi (khashayar) wrote :

Removing the lines from /etc/network/interfaces makes it work fine now. (Using the patched hal-package). Thanks :)

Revision history for this message
Scott Robinson (scott-ubuntu) wrote :

The hal patch is released, an the /e/n/i fix solved the issue. Closing.

Changed in network-manager:
status: Unconfirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.