All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: Luciano Coelho <coelho@ti.com>
Subject: Re: Troubles with wl12xx
Date: Wed, 14 Mar 2012 07:41:56 -0600	[thread overview]
Message-ID: <4F60A024.9060306@mlbassoc.com> (raw)
In-Reply-To: <4F6092FB.6030809@mlbassoc.com>

On 2012-03-14 06:45, Gary Thomas wrote:
> I'm having some issues getting my [newly designed] board to run
> with wl12xx (wl1271 on SDIO) My kernel is 2.6.37 and I'm using
> a compat-wireless snapshot from 2012-02-28
>
> Here's what I see when I boot - looks OK:
> Compat-wireless backport release: compat-wireless-2012-02-28
> Backport based on linux-next.git next-20120228
> cfg80211: Calling CRDA to update world regulatory domain
> wl12xx: loaded
>
> If I bring up the wlan0 interface manually, I can talk to the
> device, scan for access points, etc. All looks good.
>
> The problem comes when I try to negotiate for an address with
> WPA security.
> # ifup wlan0
> wl12xx: firmware booted (Rev 6.3.5.0.98)
> ADDRCONF(NETDEV_UP): wlan0: link is not ready
> udhcpc (v1.19.3) started
> Sending discover...
> wl12xx: down
> Sending discover...
> Sending discover...
> No lease, failing
>
> A few seconds later, everything falls apart. Sorry for the verbosity, but
> the messages changed at the end and I wanted to make sure you saw it all.

A little more information - maybe this helps:
   # ifup -v wlan0
   run-parts /etc/network/if-pre-up.d
   wl12xx: firmware booted (Rev 6.3.5.0.98)
   wl12xx: ERROR watchdog interrupt received! starting recovery.
   wl12xx: Reading FW panic log
   wl12xx: Hardware recovery in progress. FW ver: Rev 6.3.5.0.98 pc: 0x0
     wl12xx: down
   ieee80211 phy0: Hardware restart was requested
   ADDRCONF(NETDEV_UP): wlan0: link is not ready
   wl12xx: ERROR timeout waiting for the hardware to complete initialization
   wl12xx: ERROR timeout waiting for the hardware to complete initialization
   wl12xx: ERROR timeout waiting for the hardware to complete initialization
   wl12xx: ERROR firmware boot failed despite 3 retries
   ifconfig wlan0 up
   udhcpc -R -n -p /var/run/udhcpc.wlan0.pid -i wlan0
   udhcpc (v1.19.3) started
   Sending discover...
   Sending discover...
   Sending discover...
   No lease, failing

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

  reply	other threads:[~2012-03-14 13:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-14 12:45 Troubles with wl12xx Gary Thomas
2012-03-14 13:41 ` Gary Thomas [this message]
2012-03-14 18:44   ` Gary Thomas
2012-03-15 15:43     ` Gary Thomas
2012-04-02 11:04       ` Gary Thomas

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=4F60A024.9060306@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=coelho@ti.com \
    --cc=linux-wireless@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.