All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arend van Spriel <arend@broadcom.com>
To: "Jürgen Bausa" <juergen.Bausa@online.de>
Cc: <linux-wireless@vger.kernel.org>
Subject: Re: Broadcom 43340
Date: Tue, 17 Mar 2015 23:20:33 +0100	[thread overview]
Message-ID: <5508A8B1.9050604@broadcom.com> (raw)
In-Reply-To: <loom.20150317T214603-379@post.gmane.org>

On 03/17/15 22:01, Jürgen Bausa wrote:
> Arend van Spriel<arend@...>  writes:
>
>>
>> On 03/15/15 21:38, Jürgen Bausa wrote:
>>>
>>> would be nice, if you could make it clear.
>>>
>>
>> Maybe you need to mount it. This is what I found [1]:
>>
>> $ sudo mount -t efivarfs none /sys/firmware/efi/efivars
>>
>
> Thanks, that worked. Now I have firmware and nvram-file and the driver seems
> to load ok. At least I have an interface wlan0.
>
> However, I am not able to connect.Network-manager just says "interface is
> being set up ..." forever. I have no idea howto debug this. In the other
> post you said that the nl80211 driver should be used instead of wext. I
> found that nl80211 is the default for network-manager. So, whats going wrong
> here?

Could you provide output of these:

$ iw dev
$ iw list
$ ifconfig -a

Regards,
Arend

  reply	other threads:[~2015-03-17 22:20 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <550482A2.3080803@gmail.com>
     [not found] ` <55048833.90408@broadcom.com>
     [not found]   ` <55048BB1.9080906@gmail.com>
2015-03-14 19:54     ` Broadcom 43340 Arend van Spriel
2015-03-14 20:07       ` Ochal Christophe
2015-03-14 20:39         ` Stefan Lippers-Hollmann
2015-03-14 22:13           ` Ochal Christophe
2015-03-15 11:37             ` Arend van Spriel
2015-03-15 20:38               ` Jürgen Bausa
2015-03-15 21:14                 ` Arend van Spriel
2015-03-17 21:01                   ` Jürgen Bausa
2015-03-17 22:20                     ` Arend van Spriel [this message]
2015-03-18 21:12                       ` Jürgen Bausa
2015-03-17 23:20                     ` Dan Williams
2015-03-18 21:24                       ` Jürgen Bausa
2015-03-18 21:29                         ` Dan Williams
2015-03-18 21:40                           ` Arend van Spriel
2015-03-19 21:00                             ` Jürgen Bausa
2015-03-19 21:40                               ` Arend van Spriel
2015-03-21 20:38                                 ` Jürgen Bausa
2015-03-22 13:11                                   ` Arend van Spriel
2015-03-22 20:14                                     ` Jürgen Bausa
2015-03-23  9:52                                       ` Arend van Spriel
2015-03-23 20:09                                         ` Jürgen Bausa
2015-03-23 20:50                                           ` Arend van Spriel
2015-03-15 21:20                 ` Stefan Lippers-Hollmann
2015-03-15  2:03       ` Koen Bulcke
2015-03-15 11:39         ` 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=5508A8B1.9050604@broadcom.com \
    --to=arend@broadcom.com \
    --cc=juergen.Bausa@online.de \
    --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.