linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arend van Spriel <arend@broadcom.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: linux-wireless Mailing List <linux-wireless@vger.kernel.org>,
	<frankyl@broadcom.com>, Samuel Ortiz <sameo@linux.intel.com>
Subject: Re: brcmfmac not working on ECS LIVA
Date: Sun, 9 Nov 2014 11:46:41 +0100	[thread overview]
Message-ID: <545F4611.3010207@broadcom.com> (raw)
In-Reply-To: <CAMP44s2XAmaiK2=BJA3TCW48Uo=5qyT5WsASDsZnOiSNgK6b0A@mail.gmail.com>

On 11/08/14 21:39, Felipe Contreras wrote:
> Hi,
>
> I just got an ECS LIVA and I haven't been able to get the wireless
> working. First I got the error that the brcmfmac43241b4-sdio.txt file
> was missing. I got the file from the ECS's beta drivers [1], but it's
> still not working.
>
> brcmfmac: brcmf_sdio_drivestrengthinit: No SDIO Drive strength init
> done for chip 4324 rev 5 pmurev 17
> brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Jul 17 2013
> 07:36:07 version 6.10.197.71 (r412987) FWID 01-882d2634
> brcmfmac: brcmf_add_if: ERROR: netdev:wlan0 already exists
> brcmfmac: brcmf_add_if: ignore IF event
>
> WPA association/authentication failed for interface 'wlan0'
>
> I also tried a nvram file that is stored in EFI variables, but it
> didn't work either.
>
> Some things seem to work some times, but not the whole association.
>
> This is a 3.17.2 kernel.
>
> Any ideas?

Hi Felipe,

The ideas may come to us with a bit more trace information. The logging 
above is the usual stuff so no problem indication there.

I looked at the nvram file from [1]. At the end there are some entries 
about OOB wakeup, ie. starting with 'sd_'. You may remove those, but 
giving the logging it would not be the first thing to do.

Could you share the nvram obtained from EFI? Also please create a kernel 
log with debug=0xd416.

Regards,
Arend

> [1] http://www.ecs.com.tw/LIVA/support.html
>


  reply	other threads:[~2014-11-09 10:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-08 20:39 brcmfmac not working on ECS LIVA Felipe Contreras
2014-11-09 10:46 ` Arend van Spriel [this message]
2014-11-10 20:48   ` Felipe Contreras
2014-11-11 11:08     ` Arend van Spriel
2014-11-11 18:32       ` Felipe Contreras
2014-11-11 18:35         ` Arend van Spriel
2014-11-11 18:49           ` Felipe Contreras
2014-11-11 19:10             ` Arend van Spriel
2014-11-11 19:13               ` Felipe Contreras
2014-11-11 22:32   ` Felipe Contreras
2014-11-12 10:40     ` Arend van Spriel
2014-11-12 15:23       ` Felipe Contreras
2014-11-13 10:47         ` Arend van Spriel
2014-11-14 17:03           ` Felipe Contreras
2014-11-14 19:30             ` Arend van Spriel

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=545F4611.3010207@broadcom.com \
    --to=arend@broadcom.com \
    --cc=felipe.contreras@gmail.com \
    --cc=frankyl@broadcom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sameo@linux.intel.com \
    /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;
as well as URLs for NNTP newsgroup(s).