Linux wireless drivers development
 help / color / mirror / Atom feed
From: Mourad De Clerck <bugs-kernel@aquazul.com>
To: Michael Ayers <anothergrump@runbox.com>,
	Larry Finger <Larry.Finger@lwfinger.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Kernel 6.2.4 and WiFi with BCM4345
Date: Thu, 23 Mar 2023 22:24:33 +0100	[thread overview]
Message-ID: <a9fc7a06-c13e-36ed-c112-e3eddd2aa8a0@aquazul.com> (raw)
In-Reply-To: <a1953a58-9bdb-384a-42ca-503389aed8e5@runbox.com>

On 3/20/23 02:41, Michael Ayers wrote:
> On 20/03/23 13:12, Larry Finger wrote:
>> 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,
> 
> I'm using NetworkManager but I also tried Wicked with the same results.
> 
> NetworkManager tries to connect but fails.


Hi,

I think I may be hitting the same bug. I have this device:

02:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries 
BCM4350 802.11ac Wireless Network Adapter [14e4:43a3] (rev 05)

This is a 2017 MacBookPro14,1.

NetworkManager fails to connect when booting Linux v6.2.5, but seems to 
have no problems with v6.2.1.

Let me know if you need more information.

-- Mourad


      parent reply	other threads:[~2023-03-23 21:33 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
2023-03-20  2:11           ` Larry Finger
2023-03-23 21:24           ` Mourad De Clerck [this message]

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=a9fc7a06-c13e-36ed-c112-e3eddd2aa8a0@aquazul.com \
    --to=bugs-kernel@aquazul.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=anothergrump@runbox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox