** Changed in: linux-oem-7.0 (Ubuntu Stonking)
Status: New => Invalid
** Description changed:
- TBD.
- ---
+ [SRU Justification]
+
+ [Impact]
+
+ While we are to support Intel Wilcat Lake in oem projects, the PV driver
+ release depends on firmware release of core102 API. In Ubuntu, core102
+ API is currently only supported through backport-iwlwifi-dkms >= 0~102
+ version, or linux-unstable based kernel v7.1-rcX. The support plan is:
+
+ 1. to enable linux-oem-6.17 supportness using backport-iwlwifi-dkms,
+ 2. when migrated to linux-hwe-7.0 and/or generic linux-7.0, expect
+ native support of iwlwifi core102 API in them.
+
+ Without 2., the Intel Wildcat Lake platforms shipped with
+ linux-oem-6.17 kernel will be blocked until a latter point release in
+ around early 2027, a hwe kernel based on Stonking generic kernel 7.3 or
+ so.
+
+ While the PV driver is only upstreamed until v7.1-rc, it's impossible to
+ integrate this before Resolute linux-7.0 release.
+
+ [Fix]
+
+ The backport is made of 57 patches from mainline kernel. A few patches
+ proposed by Intel but appears irrelevant to the core function have been
+ removed because they lead to either build failures to other components,
+ or external dkms packages due to API changes.
+
+ Most of the patches touch only iwlwifi driver itself. For those walk
+ across the border:
+
+ 1. from wireless-next-2026-03-19:
+
+ - f10ebd136dfef wifi: nl80211: use int for band coming from netlink
+ - eb092b188fcf9 wifi: mac80211: fix STA link removal during link removal
+ - 6fb86f7b696e8 wifi: nl80211: reject S1G/60G with HT chantype
+ - 7218d8e9d8485 wifi: cfg80211: check non-S1G width with S1G chandef
+ - 92d77e06e73ca wifi: cfg80211: restrict cfg80211_chandef_create() to only
HT-based bands
+ - a6d4291eae040 wifi: mac80211: don't use cfg80211_chandef_create() for
default chandef
+ - 84674b03d8bf3 wifi: mac80211: Remove deleted sta links in
ieee80211_ml_reconf_work()
+ - fd2905157d692 wifi: cfg80211: split control freq check from chandef check
+ - f932856649b07 wifi: mac80211: always use full chanctx compatible check
+ - ba9d121f85771 wifi: mac80211: refactor chandef tracing macros
+ - f2514ff78855c wifi: mac80211: validate HE 6 GHz operation when EHT is
used
+
+ Above commits are internal to nl80211/mac80211/cfg80211 and did not
+ touch API/ABI.
+
+ - e4b993f2bca78 wifi: nl80211: split out UHR operation information
+
+ This is to define a new nl80211 attribute for userspace program use.
+ For hostap/wpa_supplicant, it's in the main branch starting from
+ commit b6bdf8581 ("UHR: Protocol definitions from IEEE
+ P802.11bn/D1.4") and is not yet released ever. hostap, actually libnl
+ already handles unknown attribute by passing maximum accepted
+ attribute id NL80211_ATTR_MAX to nla_parse() or so.
+
+ - 35de87bf598ca wifi: Add SPDX ids to some files in the wireless subsystem
+ - a140826caa2c1 wifi: nl80211: fix UHR capability validation
+ - 9f39e2cc2b012 wifi: mac80211: remove AID bit stripping for print
+ - 2f211be112e64 wifi: mac80211: remove stale TODO item
+
+ Another few commit irrelevant to API/ABI changes.
+
+ 2. from wireless-next-2026-03-04:
+
+ - 5d048bbed1bb2 wifi: mac80211: give the AP more time for EPPKE as well
+ - b8a57b979a7c2 wifi: mac80211: update outdated comment
+
+ Internal fixes only.
+
+ - 6a584e336cefb wifi: cfg80211: add support to handle incumbent
+ signal detected event from mac80211/driver
+
+ This is to notify upper layers about the signal interference event.
+ mac80211 simulator (MAC80211_HWSIM), uses it. hostap implemented this
+ process since commit bfc3fe08a ("nl80211: Incumbent signal
+ interference event") in main branch; before that, it's simply dropped
+ with a debug message indicating an unsupported event.
+
+ - f3f52e6f20ac8 wifi: mac80211: Set link ID for NULL packets sent to probe
stations
+ - 73e7df69edb6f wifi: mac80211: set band information only for non-MLD when
probing stations using NULL frame
+
+ [Test Plan]
+
+ 1. Install the new patched kernel from -proposed.
+
+ 2. On an Intel Wildcat Lake platform, with BE211/BE213 wireless modules,
+ check the dmesg gives something like:
+ ```
+ $ sudo dmesg | grep iwlwifi
+ kernel: iwlwifi 0000:00:14.3: Detected Intel(R) Wi-Fi 7 BE211 320MHz
+ kernel: iwlwifi 0000:00:14.3: loaded firmware version 102.07fca168.0
bz-b0-wh-b0-c102.ucode op_mode iwlmld
+ ```
+
+ 3. Install checkbox:
+ ```
+ $ sudo apt-add-repository ppa:checkbox-dev/stable
+ $ sudo apt install canonical-certification-client
+ ```
+ Run wireless automated test plan:
+ ```
+ $ sudo checkbox-cli run-plan
+ # Pick "Automated tests for wireless and follow further menus
+ ```
+
+ 4. Replace the module with other models even with a different vendor if
+ possible. Retry with step 2. and 3.
+
+ 5. Tested dkms packages:
+ ```
+ $ dkms status
+ backport-iwlwifi/0~103.14434-gitdf6b5bf4, 7.0.0-3015-generic, x86_64:
installed
+ broadcom-sta/6.30.223.271, 7.0.0-3015-generic, x86_64: installed
+ ezurio-qcacld-2.0/0.0~git20240408.aa96a9f+dfsg, 7.0.0-3015-generic, x86_64:
installed
+ ipt-netflow/2.6, 7.0.0-3015-generic, x86_64: installed
+ jool/4.1.15, 7.0.0-3015-generic, x86_64: installed
+ osmocom-dahdi/0.0~git20250226.6dada77, 7.0.0-3015-generic, x86_64: installed
+ ovpn-dco/0.0+git20251017, 7.0.0-3015-generic, x86_64: installed
+ r8125/9.016.01, 7.0.0-3015-generic, x86_64: installed
+ r8168/8.055.00, 7.0.0-3015-generic, x86_64: installed
+ rtpengine/13.5.1.4, 7.0.0-3015-generic, x86_64: installed
+ sl-modem/2.9.11~20110321, 7.0.0-3015-generic, x86_64: installed
+ west-chamber/20100405+svn20111107.r124, 7.0.0-3015-generic, x86_64: installed
+ xtables-addons/3.30, 7.0.0-3015-generic, x86_64: installed
+ ```
+
+ [Where problems could occur]
+
+ By lifting iwlwifi firmware API from core101 which linux-7.0 supports to
+ core102, it follows a few firmware may become active while they were not
+ although released in linux-firmware/resolute. These files are:
+
+ * intel/iwlwifi/iwlwifi-bz-b0-fm-c0-c102.ucode (BE201)
+ * intel/iwlwifi/iwlwifi-bz-b0-wh-b0-c102.ucode (BE211/BE213)
+ * intel/iwlwifi/iwlwifi-gl-c0-fm-c0-c102.ucode (BE201)
+ * intel/iwlwifi/iwlwifi-sc-a0-fm-c0-c102.ucode (BE201)
+ * intel/iwlwifi/iwlwifi-sc-a0-wh-b0-c102.ucode (BE211/BE213)
+
+ While these models are expected to be supported in Intel Wildcat Lake, it
+ follows they must become active to meet device enablement plan. The blobs
+ are PV ones, they are supposed to be working fine.
+
+ In addition, when Intel AX211 module is installed, there is a known
+ issue LP #2152688 that iwlwifi gives "failed to send
+ MCC_ALLOWED_AP_TYPE_CMD (-22)" error at initializing. This happens to
+ backport-iwlwifi-dkms core105, too.
+
+ [Other Info]
+
+ While these patches are backported from v7.1-rcX, nominate for Resolute
+ and oem-6.17 only.
+
+ ---
ProblemType: Bug
ApportVersion: 2.34.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
- USER PID ACCESS COMMAND
- /dev/snd/seq: gdm-greeter 1545 F.... pipewire
+ USER PID ACCESS COMMAND
+ /dev/snd/seq: gdm-greeter 1545 F.... pipewire
CasperMD5CheckResult: pass
DistroRelease: Ubuntu 26.04
InstallationDate: Installed on 2025-12-23 (157 days ago)
InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64
(20250215)
Lsusb:
- Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
- Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
- Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
- Bus 003 Device 002: ID 2a7a:8a5b CASUE USB KB
- Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+ Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+ Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ Bus 003 Device 002: ID 2a7a:8a5b CASUE USB KB
+ Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
MachineType: Intel Corporation Wildcat Lake Client Platform
Package: linux (not installed)
ProcFB: 0 xedrmfb
ProcKernelCmdLine: BOOT_IMAGE=/rootfs/resolute/boot/vmlinuz-7.0.0-19-generic
root=UUID=e9935351-eaa0-4e67-9f5a-5910f8e4786e ro
rootflags=subvol=rootfs/resolute quiet splash
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
ProcVersionSignature: Ubuntu 7.0.0-19.19-generic 7.0.9
Tags: resolute
Uname: Linux 7.0.0-19-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 08/07/2025
dmi.bios.vendor: Intel Corporation
dmi.bios.version: WCLPFWI1.R00.3323.D05.2508071747
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: WCL LP5x MD T3 RVP2
dmi.board.vendor: Intel Corporation
dmi.board.version: 2
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 0.1
dmi.ec.firmware.release: 2.40
dmi.modalias:
dmi:bvnIntelCorporation:bvrWCLPFWI1.R00.3323.D05.2508071747:bd08/07/2025:efr2.40:svnIntelCorporation:pnWildcatLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnWCLLP5xMDT3RVP2:rvr2:cvnIntelCorporation:ct9:cvr0.1:sku0100000000210100:pfaWildcatLakeClientSystem:
dmi.product.family: Wildcat Lake Client System
dmi.product.name: Wildcat Lake Client Platform
dmi.product.sku: 0100000000210100
dmi.product.version: 0.1
dmi.sys.vendor: Intel Corporation
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2148636
Title:
backport Intel iwlwifi core102 support from linux-next to
linux/resolute 7.0.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2148636/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
