Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #90374 > unrolled thread
| Started by | Uwe Kleine-König <u.kleine-koenig@baylibre.com> |
|---|---|
| First post | 2025-12-06 13:00 +0100 |
| Last post | 2025-12-06 13:00 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.debian.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Bug#1109268: ath11k_pci may trigger prompt for nonexistent firmware file during installation Uwe Kleine-König <u.kleine-koenig@baylibre.com> - 2025-12-06 13:00 +0100
| From | Uwe Kleine-König <u.kleine-koenig@baylibre.com> |
|---|---|
| Date | 2025-12-06 13:00 +0100 |
| Subject | Bug#1109268: ath11k_pci may trigger prompt for nonexistent firmware file during installation |
| Message-ID | <LYZ7b-MBx-5@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
Hello Stefano, On Sat, Nov 29, 2025 at 07:12:21PM +0100, Stefano Corti wrote: > I can confirm this bug too, it occurred upgrading from bookworm to trixie. > > Failure in loading the proper firmware leads to several limitiations in the > use of the wifi chip in access points mode. > All 5GHZ band channels have the "no initiate radiation" (NO-IR) flag set > despite the correct country regulatory settings and so preventing the use of > this band in AP mode, and you cannot set more than one SSID in AP mode. > > I suspect the bug occurred after this commit in vanilla kernel: > https://github.com/torvalds/linux/commit/7db88b962f06a52af5e9a32971012e8f3427cec0 > > On Trixie, manually installing the latest bookworm kernel (6.1.40) fixes > the problem. > > 'dmesg' and 'iw list' extracts following. I the symptoms you describe are a different problem. In my understanding the original bug is that the ath11k driver supports two different firmwares and after it tries (and fails loudly) to load the first option it falls back to the second and everything is fine, just that error messages appear in dmesg. The only thing in common here is that you see those wrong error messages, too. So can you please open a separate bug for your problem? Best regards Uwe
Back to top | Article view | linux.debian.kernel
csiph-web