From: Michael Ayers <anothergrump@runbox.com>
To: arm@lists.opensuse.org
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Kernel 6.2.4 and WiFi with BCM4345
Date: Mon, 20 Mar 2023 14:41:25 +1300 [thread overview]
Message-ID: <a1953a58-9bdb-384a-42ca-503389aed8e5@runbox.com> (raw)
In-Reply-To: <1db6b607-faff-9ae2-0cf3-567d9c86e4ba@lwfinger.net>
On 20/03/23 13:12, Larry Finger wrote:
> On 3/19/23 14:35, Michael Ayers wrote:
>>
>> On 20/03/2023 08:24, Michael Ayers wrote:
>>>
>>> On 20/03/2023 07:58, Larry Finger wrote:
>>>> On 3/19/23 13:20, Michael Ayers wrote:
>>>>> Kernel 6.2.4-1-default has broken wifi on the Pinebook pro, kernel
>>>>> 6.2.1-1-default works fine.
>>>>>
>>>>> Logs give me so much information that I am not sure where to begin.
>>>>
>>>> The first piece of information would be to tell us what what device
>>>> you have. The Pinebrook Pro web site says that you have an 802.11ac
>>>> (Wifi 5) device, but not who made it. The output of 'lspci -nn' or
>>>> 'lsusb' would be useful.
>>>>
>>>> You should also run the command 'sudo dmesg > dmesg.txt', and post
>>>> dmesg.txt at pastebin.com, or some similar site. Report the URL
>>>> back with the ouput of the two commands above. Do not attach
>>>> dmesg.txt to your reply. There are thousands of readers of this
>>>> list that do not care, thus they should not be forced to download
>>>> such stuff.
>>>>
>>>> Larry
>>>>
>>>>
>>> The wifi device would seem to be a Broadcom 4345 and if I've done
>>> this right this: https://pastebin.com/rz2wnuVt should be the link to
>>> dmesg.txt.
>>>
>>> MIke
>>
>>
>> Sorry that is the wrong dmesg link it should be:
>> https://pastebin.com/SE0DV7XP
>
> Mike,
>
> I just noticed that the linux-wireless list was not in the Cc list - I
> added it. I also changed the subject to help catch the attention of
> the Broadcom maintainers. I am definitely not one of them.
>
> Your device is a BCM4345, which uses the brcmfmac driver. The dmesg
> output that you posted shows the firmware loading, but nothing happens
> beyond that. This is the point where I would expect the user-space
> code such as NetworkManager to take over. What code do you use to
> control wifi? Did that change when your kernel was updated?
>
> Larry
>
>
Larry,
I'm using NetworkManager but I also tried Wicked with the same results.
NetworkManager tries to connect but fails.
Mike
next prev parent reply other threads:[~2023-03-20 2:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e26eeebb-4fb0-5506-afbc-e9b56b849211@runbox.com>
[not found] ` <c09e012e-7abd-7304-3721-799758a7f0e3@lwfinger.net>
[not found] ` <cc6e8c12-33b7-7c42-345b-c3212b13bc77@runbox.com>
[not found] ` <fa88eb52-7194-ecb2-0590-f554a12485ec@runbox.com>
2023-03-20 0:12 ` Kernel 6.2.4 and WiFi with BCM4345 Larry Finger
2023-03-20 1:41 ` Michael Ayers [this message]
2023-03-20 2:11 ` Larry Finger
2023-03-23 21:24 ` Mourad De Clerck
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=a1953a58-9bdb-384a-42ca-503389aed8e5@runbox.com \
--to=anothergrump@runbox.com \
--cc=arm@lists.opensuse.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