From: Arend Van Spriel <arend.vanspriel@broadcom.com>
To: message <letter@openmailbox.org>,
brcm80211-dev-list.pdl@broadcom.com, arch-general@archlinux.org,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: linux driver bcm4311 failure
Date: Sat, 14 Jan 2017 12:53:18 +0100 [thread overview]
Message-ID: <da82a20d-fad4-69e4-c2bc-6cee1374253d@broadcom.com> (raw)
In-Reply-To: <851aa49795494ec407c4783f8579437e@openmailbox.org>
On 14-1-2017 11:15, message wrote:
> On 2017-01-02 20:04, Arend van Spriel wrote:
>> On 02-01-17 15:33, message wrote:
>>> On 2016-12-30 19:46, message wrote:
>>>> On 2016-09-17 08:11, message wrote:
>>>>> On 2016-09-09 07:57, Arend Van Spriel wrote:
>>>>>>
>>>>>> The device is claimed by b43-pci-bridge so I would suggest:
>>>>>>
>>>>>> blacklist b43-pci-bridge
>>>>>>
>>>
>>> The wifi card indicator now appears to start after computer switch on
>>> (twice in a row now!)
>>>
>>> Neither networkmanager or wicd are accepting the password.
>>>
>>> Even:
>>>
>>> wicd-cli --wireless -c [wifihotspotname]
>>> done!
>>>
>>> is false and internet access not found.
>>>
>>> wpa_supplicant continues to report 'conn_failed' error.
>>>
>>> Connection to same network is successful using debian on chromebook
>>> (crouton)
>>
>> I am confused by all your messages. In the previous one you did a
>> 'modprobe b43'. So what driver do you intend to use here. b43 is not a
>> driver maintained by broadcom. You should ask for help on the b43
>> mailing list [1] if you want to use that driver.
>>
>> Regards,
>> Arend
>>
>> [1] http://lists.infradead.org/mailman/listinfo/b43-dev
>
> After system upgrade, wifi card fails to be recognised.
>
> For the benefit of other users: save your time and avoid broadcom
> products; they are terrible.
Why sending these types of messages hiding in anonymity without
responding to any of the questions in my email responses. Again what
driver are you using. If it is b43 you want you should not blacklist
b43-pci-bridge. Whether or not b43 supports your device can be found
here [2]. Supposedly it is. If not you might try your luck at the b43
mailing list I gave you in earlier email.
Regards,
Arend
[2] https://wireless.wiki.kernel.org/en/users/drivers/b43#list_of_hardware
parent reply other threads:[~2017-01-14 11:53 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <851aa49795494ec407c4783f8579437e@openmailbox.org>]
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=da82a20d-fad4-69e4-c2bc-6cee1374253d@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=arch-general@archlinux.org \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=letter@openmailbox.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox