public inbox for regressions@lists.linux.dev
 help / color / mirror / Atom feed
From: Jan Palus <jpalus@fastmail.com>
To: linux-rockchip@lists.infradead.org
Cc: Peter Robinson <pbrobinson@gmail.com>,
	 Heiko Stuebner <heiko@sntech.de>,
	regressions@lists.linux.dev
Subject: [REGRESSION][BISECTED] wifi broken on pinebook pro
Date: Wed, 17 Dec 2025 12:26:46 +0100	[thread overview]
Message-ID: <aUKOlj-RvTYlrpiS@rock.grzadka> (raw)

WiFi no longer works on Pinebook Pro after upgrade to kernel 6.18. It
appears firmware fails to load:

...
mmc_host mmc0: card is non-removable.
mmc_host mmc0: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0)
Bluetooth: hci0: BCM: features 0x0f
Bluetooth: hci0: BCM4345C5 Ampak_CL1 UART 37.4 MHz BT 5.0 [Version: Version: 0039.0089]
Bluetooth: hci0: BCM4345C5 (003.006.006) build 0089
mmc_host mmc0: Bus speed (slot 0) = 148500000Hz (slot req 150000000Hz, actual 148500000HZ div = 0)
dwmmc_rockchip fe310000.mmc: Successfully tuned phase to 55
mmc0: new UHS-I speed SDR104 SDIO card at address 0001
brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43456-sdio for chip BCM4345/9
usbcore: registered new interface driver brcmfmac
brcmfmac mmc0:0001:1: Direct firmware load for brcm/brcmfmac43456-sdio.pine64,pinebook-pro.bin failed with error -2
brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
ieee80211 phy0: brcmf_bus_started: failed: -110
ieee80211 phy0: brcmf_attach: dongle is not responding: err=-110
brcmfmac: brcmf_sdio_firmware_callback: brcmf_attach failed

compared to 6.17 instead of last 4 lines with errors there's single one
with info about loaded firmware:

brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/9 wl0: May 14 2020 17:26:08 version 7.84.17.1 (r871554) FWID 01-3d9e1d87

Bisected to:

6d54d935062e2d4a7d3f779ceb9eeff108d0535d is the first new commit
commit 6d54d935062e2d4a7d3f779ceb9eeff108d0535d (HEAD)
Author: Peter Robinson <pbrobinson@gmail.com>
Date:   Wed Aug 27 16:30:37 2025

    arm64: dts: rockchip: Further describe the WiFi for the Pinebook Pro
    
    Update the wake-up pin and associated interupt details for the
    Pinebook Pro WiFi module.
    
    Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
    Link: https://lore.kernel.org/r/20250827143040.1644867-1-pbrobinson@gmail.com
    Signed-off-by: Heiko Stuebner <heiko@sntech.de>

 arch/arm64/boot/dts/rockchip/rk3399-pinebook-pro.dts | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)


With this commit reverted on top of 6.18.1 wireless connection works
fine.

Not sure what could be relevant but:
- it's an early model, I think second batch, delivered end of 2019
- mainline uboot 2025.10 is used


#regzbot introduced: 6d54d93506

             reply	other threads:[~2025-12-17 11:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-17 11:26 Jan Palus [this message]
2025-12-29  6:23 ` [REGRESSION][BISECTED] wifi broken on pinebook pro Peter Robinson
2025-12-29 12:18   ` Jan Palus
2026-01-02 12:17     ` FUKAUMI Naoki
2026-01-23 13:39       ` Robin Murphy
2026-01-14 13:03   ` Thorsten Leemhuis
2026-02-03 10:42     ` Thorsten Leemhuis
2026-02-05 10:34       ` Jan Palus

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=aUKOlj-RvTYlrpiS@rock.grzadka \
    --to=jpalus@fastmail.com \
    --cc=heiko@sntech.de \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=pbrobinson@gmail.com \
    --cc=regressions@lists.linux.dev \
    /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