Bug#355785: network-manager: Does not discover wireless interface at all

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#355785: network-manager: Does not discover wireless interface at all

Mikael Nilsson
Package: network-manager
Version: 0.5.1-3
Severity: important


For some reason, nm does not seem to notice that I plug in a wireless
network card.

I have a Farallon PCMCIA card (orinoco driver), that is recognized and
initialized by udev, and the network is configured automatically.

However, NM does not seem to even sense that it is there. I get no trace of
NM in the logs, and nm-applet does not show the interface in the list.

I want NM to recognize the interface, as I want to be able to choose which
network I'm on, etc. This is a major PITA using wireless-tools and ifupdown.

Excerpt from log:

Mar  6 11:30:10 yossarian kernel: pccard: PCMCIA card inserted into slot 1
Mar  6 11:30:10 yossarian kernel: cs: memory probe 0xf4000000-0xfbffffff: excluding 0xf4000000-0xf8ffffff
Mar  6 11:30:10 yossarian kernel: pcmcia: registering new device pcmcia1.0
Mar  6 11:30:10 yossarian kernel: orinoco 0.15rc3 (David Gibson <[hidden email]>, Pavel Roskin <[hidden email]>, et al)
Mar  6 11:30:10 yossarian kernel: orinoco_cs 0.15rc3 (David Gibson <[hidden email]>, Pavel Roskin <[hidden email]>, et al)
Mar  6 11:30:10 yossarian kernel: eth2: Hardware identity 8008:0001:0001:0000
Mar  6 11:30:10 yossarian kernel: eth2: Station identity 001f:0000:0000:0008
Mar  6 11:30:10 yossarian kernel: eth2: Firmware determined as Intersil 0.8.0
Mar  6 11:30:10 yossarian kernel: eth2: Ad-hoc demo mode supported
Mar  6 11:30:10 yossarian kernel: eth2: IEEE standard IBSS ad-hoc mode supported
Mar  6 11:30:10 yossarian kernel: eth2: WEP supported, 104-bit key
Mar  6 11:30:10 yossarian kernel: eth2: MAC address 00:00:C5:09:36:13
Mar  6 11:30:10 yossarian kernel: eth2: Station name "Prism  I"
Mar  6 11:30:10 yossarian kernel: eth2: ready
Mar  6 11:30:10 yossarian kernel: eth2: index 0x01: Vcc 3.3, irq 3, io 0xe100-0xe13f
Mar  6 11:30:11 yossarian kernel: ieee80211_crypt: registered algorithm 'NULL'
Mar  6 11:30:11 yossarian kernel: hostap_cs: 0.4.4-kernel (Jouni Malinen <[hidden email]>)
Mar  6 11:30:11 yossarian dhclient: Internet Systems Consortium DHCP Client V3.0.3
Mar  6 11:30:11 yossarian dhclient: Copyright 2004-2005 Internet Systems Consortium.
Mar  6 11:30:11 yossarian dhclient: All rights reserved.
Mar  6 11:30:11 yossarian dhclient: For info, please visit http://www.isc.org/products/DHCP
Mar  6 11:30:11 yossarian dhclient:
Mar  6 11:30:11 yossarian kernel: ADDRCONF(NETDEV_UP): eth2: link is not ready
Mar  6 11:30:11 yossarian kernel: eth2: New link status: Connected (0001)
Mar  6 11:30:11 yossarian kernel: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready
Mar  6 11:30:12 yossarian dhclient: Listening on LPF/eth2/00:00:c5:09:36:13
Mar  6 11:30:12 yossarian dhclient: Sending on   LPF/eth2/00:00:c5:09:36:13
Mar  6 11:30:12 yossarian dhclient: Sending on   Socket/fallback
Mar  6 11:30:16 yossarian dhclient: DHCPDISCOVER on eth2 to 255.255.255.255 port 67 interval 6
Mar  6 11:30:16 yossarian dhclient: DHCPOFFER from 1.1.1.1
Mar  6 11:30:16 yossarian dhclient: DHCPREQUEST on eth2 to 255.255.255.255 port 67
Mar  6 11:30:17 yossarian dhclient: DHCPACK from 1.1.1.1
Mar  6 11:30:17 yossarian avahi-daemon[6020]: New relevant interface eth2.IPv4 for mDNS.
Mar  6 11:30:17 yossarian avahi-daemon[6020]: Joining mDNS multicast group on interface eth2.IPv4 with address 130.243.132.169.
Mar  6 11:30:17 yossarian avahi-daemon[6020]: Registering new address record for 130.243.132.169 on eth2.
Mar  6 11:30:17 yossarian avahi-daemon[6020]: Withdrawing address record for 130.243.132.169 on eth2.
Mar  6 11:30:17 yossarian avahi-daemon[6020]: Leaving mDNS multicast group on interface eth2.IPv4 with address 130.243.132.169.
Mar  6 11:30:17 yossarian avahi-daemon[6020]: iface.c: interface_mdns_mcast_join() called but no local address available.
Mar  6 11:30:17 yossarian avahi-daemon[6020]: Interface eth2.IPv4 no longer relevant for mDNS.
Mar  6 11:30:17 yossarian avahi-daemon[6020]: New relevant interface eth2.IPv4 for mDNS.
Mar  6 11:30:17 yossarian avahi-daemon[6020]: Joining mDNS multicast group on interface eth2.IPv4 with address 130.243.132.169.
Mar  6 11:30:17 yossarian avahi-daemon[6020]: Registering new address record for 130.243.132.169 on eth2.
Mar  6 11:30:17 yossarian dhclient: bound to 130.243.132.169 -- renewal in 350 seconds.
Mar  6 11:30:22 yossarian kernel: eth2: no IPv6 routers present


/Mikael


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-686
Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8)

Versions of packages network-manager depends on:
ii  dhcdbd                      1.12-1       dbus interface to the ISC DHCP cli
ii  iproute                     20051007-3   Professional tools to control the
ii  iputils-arping              3:20020927-3 Tool to send ICMP echo requests to
ii  libc6                       2.3.6-3      GNU C Library: Shared libraries an
ii  libdbus-1-2                 0.61-3       simple interprocess messaging syst
ii  libdbus-glib-1-2            0.61-3       simple interprocess messaging syst
ii  libgcrypt11                 1.2.2-1      LGPL Crypto library - runtime libr
ii  libglib2.0-0                2.8.6-1      The GLib library of C routines
ii  libgpg-error0               1.2-1        library for common error values an
ii  libhal1                     0.5.6-4      Hardware Abstraction Layer - share
ii  lsb-base                    3.0-15       Linux Standard Base 3.0 init scrip

network-manager recommends no packages.

-- no debconf information


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]

Reply | Threaded
Open this post in threaded view
|

Bug#355785: network-manager: Does not discover wireless interface at all

rsetti
Il giorno lun, 06/03/2006 alle 11.40 +0100, Mikael Nilsson ha scritto:

> Package: network-manager
> Version: 0.5.1-3
> Severity: important
>
>
> For some reason, nm does not seem to notice that I plug in a wireless
> network card.
>
> I have a Farallon PCMCIA card (orinoco driver), that is recognized and
> initialized by udev, and the network is configured automatically.

> However, NM does not seem to even sense that it is there. I get no trace of
> NM in the logs, and nm-applet does not show the interface in the list.

nm doesn't show interface, only networks.  If nm-applet shows network,
NM is working fine :)

Afaik orinoco device are almost supported, what i can suggest to you is
*use the last cvs orinico module*
--
ciao, giskard

D: marty! non stai pensando quadrimensionalmente!
M: lo so.. e' che mi rimane difficile..
       



signature.asc (196 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Bug#355785: network-manager: Does not discover wireless interface at all

Mikael Nilsson
tis 2006-03-07 klockan 22:54 +0100 skrev giskard:
>
> > However, NM does not seem to even sense that it is there. I get no trace of
> > NM in the logs, and nm-applet does not show the interface in the list.
>
> nm doesn't show interface, only networks.  If nm-applet shows network,
> NM is working fine :)


Well, it only shows the "wired" network... no wireless at all. I didn't
try unplugging the wired, but I can try that too. (They are not the same
subnet at all, BTW)

So, no, I don't think it's working ...


> Afaik orinoco device are almost supported, what i can suggest to you is
> *use the last cvs orinico module*

So the 2.6.15 in-kernel version is not supported?

/Mikael
--
Plus ça change, plus c'est la même chose


Reply | Threaded
Open this post in threaded view
|

Bug#355785: network-manager: Does not discover wireless interface at all

rsetti
Il giorno mar, 07/03/2006 alle 23.28 +0100, Mikael Nilsson ha scritto:
> tis 2006-03-07 klockan 22:54 +0100 skrev giskard:
> >

> Well, it only shows the "wired" network... no wireless at all. I didn't
> try unplugging the wired, but I can try that too. (They are not the same
> subnet at all, BTW)

by default wireless network is enabled, anyway could you check if it'
enabled in your case (right click on the applet).

> > Afaik orinoco device are almost supported, what i can suggest to you is
> > *use the last cvs orinico module*
>
> So the 2.6.15 in-kernel version is not supported?

i don't know if the orinoco kernel module is the latest.
take a look on:

http://savannah.nongnu.org/projects/orinoco/
and
http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Orinoco.html

for the latest one.


--
ciao, giskard

D: marty! non stai pensando quadrimensionalmente!
M: lo so.. e' che mi rimane difficile..
       



signature.asc (196 bytes) Download Attachment