public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel <damage@rooties.de>
To: linux-kernel@vger.kernel.org
Subject: debug prism wlan
Date: Sat, 12 Aug 2006 21:40:44 +0000	[thread overview]
Message-ID: <200608122140.44365.damage@rooties.de> (raw)

Hi,
my wlan gives up working somewhere between upgrading to gcc-4.1, changing some 
kernel options and upgrading to linux-2.8.16-r4.

Now I get following from iwconfig:

eth2      NOT READY!  ESSID:off/any
          Mode:Master  Channel:0  Access Point: Not-Associated
          Tx-Power=31 dBm   Sensitivity=0/200
          Retry min limit:0   RTS thr=-1 B   Fragment thr=-1 B
          Encryption key:off
          Link Quality:27  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

But I'm not able to get infromation why this device isn't ready.
dmesg is not reporting an error.

So, has someone an idea of how to get some informations to solve this problem?

regards
Daniel

             reply	other threads:[~2006-08-12 19:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-12 21:40 Daniel [this message]
2006-08-12 20:15 ` debug prism wlan Alistair John Strachan
2006-08-12 22:26   ` Daniel
2006-08-12 20:43     ` Alistair John Strachan
2006-08-12 22:56       ` Daniel
2006-08-12 21:07         ` Alistair John Strachan
2006-08-12 22:49     ` Daniel
2006-08-12 21:06       ` Alistair John Strachan
  -- strict thread matches above, loose matches on Subject: below --
2006-08-13  5:20 Roger While
2006-08-13 11:31 ` Daniel
2006-08-13 10:37 Roger While

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=200608122140.44365.damage@rooties.de \
    --to=damage@rooties.de \
    --cc=linux-kernel@vger.kernel.org \
    /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