mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Stephan Raue <mailinglists@openelec.tv>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-3.0-rc4, wlan0 device is not showing with ifconfig
Date: Mon, 27 Jun 2011 19:29:07 +0200	[thread overview]
Message-ID: <1309195747.2532.81.camel@edumazet-laptop> (raw)
In-Reply-To: <4E08A4C9.60709@openelec.tv>

Le lundi 27 juin 2011 à 17:42 +0200, Stephan Raue a écrit :
> Hi,
> 
> running linux-3.0-rc4 my wlan0 device is not showing with ifconfig, even 
> if the driver (r8712u) loads successfull.
> 
> strace ifconfig shows:
> 
> ioctl(3, SIOCGIFFLAGS, {ifr_name="wlan0", 
> ifr_flags=IFF_BROADCAST|IFF_MULTICAST}) = 0
> ioctl(3, SIOCGIFHWADDR, {ifr_name="wlan0", 
> ifr_hwaddr=80:1f:02:0b:5d:9a}) = 0
> ioctl(3, SIOCGIFMETRIC, {ifr_name="wlan0", ifr_metric=0}) = 0
> ioctl(3, SIOCGIFMTU, {ifr_name="wlan0", ifr_mtu=1500}) = 0
> ioctl(3, SIOCGIFMAP, {ifr_name="wlan0", ifr_map={mem_start=0, mem_end=0, 
> base_addr=0, irq=0, dma=0, port=0}}) = 0
> ioctl(3, SIOCGIFTXQLEN, {ifr_name="wlan0", ifr_qlen=1000}) = 0
> ioctl(3, SIOCGIFADDR, {ifr_name="wlan0", ???}) = -1 EADDRNOTAVAIL 
> (Cannot assign requested address)
> close(3)                                = 0
> 
> the interface will be shown after i setup a ipadress manually:
> 
> ifconfig wlan0 192.68.0.13
> strace ifconfig
> 
> ioctl(3, SIOCGIFFLAGS, {ifr_name="wlan0", 
> ifr_flags=IFF_UP|IFF_BROADCAST|IFF_MULTICAST}) = 0
> ioctl(3, SIOCGIFHWADDR, {ifr_name="wlan0", 
> ifr_hwaddr=80:1f:02:0b:5d:9a}) = 0
> ioctl(3, SIOCGIFMETRIC, {ifr_name="wlan0", ifr_metric=0}) = 0
> ioctl(3, SIOCGIFMTU, {ifr_name="wlan0", ifr_mtu=1500}) = 0
> ioctl(3, SIOCGIFMAP, {ifr_name="wlan0", ifr_map={mem_start=0, mem_end=0, 
> base_addr=0, irq=0, dma=0, port=0}}) = 0
> ioctl(3, SIOCGIFTXQLEN, {ifr_name="wlan0", ifr_qlen=1000}) = 0
> ioctl(3, SIOCGIFADDR, {ifr_name="wlan0", ifr_addr={AF_INET, 
> inet_addr("168.0.0.13")}}) = 0
> ioctl(3, SIOCGIFDSTADDR, {ifr_name="wlan0", ifr_dstaddr={AF_INET, 
> inet_addr("168.0.0.13")}}) = 0
> ioctl(3, SIOCGIFBRDADDR, {ifr_name="wlan0", ifr_broadaddr={AF_INET, 
> inet_addr("168.0.255.255")}}) = 0
> ioctl(3, SIOCGIFNETMASK, {ifr_name="wlan0", ifr_netmask={AF_INET, 
> inet_addr("255.255.0.0")}}) = 0
> 
> is this problem known and is there a fix for this?

Pretty normal behavior, if your device is not "UP"

To see all devices, even DOWN ones, use "ifconfig -a"



      reply	other threads:[~2011-06-27 17:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-27 15:42 Stephan Raue
2011-06-27 17:29 ` Eric Dumazet [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1309195747.2532.81.camel@edumazet-laptop \
    --to=eric.dumazet@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mailinglists@openelec.tv \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®