likewise's questions

根据我的问答，我得到了一张在 Debian 上运行的 Wifi7 卡，该卡基于英特尔的 BE200NGW 芯片。

尽管在 Wifi7 路由器上启用了多链路操作，但运行内核 6.12.12 的 Debian 计算机仅在一个频段（2.4 或 5GHz）上连接到路由器。相比之下，Windows 11 在 Wifi7 模式下使用此卡。

已加载模块：

$ lsmod | grep iwlwifi
iwlwifi               581632  1 iwlmvm
cfg80211             1392640  6 ath9k_common,iwlmvm,ath9k,ath,iwlwifi,mac80211

我查看了iw设置，但尚未完全理解。不过，我也查看了NetworkManager 802.11 无线规格。我没有发现任何内容可以确认 NetworkManager 已准备好支持 Wifi7，即它支持同时连接到不同频段的同一 SSID。

我是否应该等到 Wifi 7 功能在整个网络堆栈中得到完全支持，或者我可以在设置或加载的模块中更改任何内容？

更新 2025-02-23

受到grawity评论的启发，我：

• 检查wpa_supplicant版本-它是 2.10（我在 Debian 上测试）
• 检查了使用的身份验证协议NetworkManager：它是 WPA2。回想一下 6GHz 需要 WPA3，我已将此设置更改为 WPA3 Personal。结果：该卡现在使用 6GHz 频段，链路速率约为 1.4Gbps，这已经比我家的千兆以太网有所改进。我想知道为什么 NM 需要手动干预才能使用 WPA3。
• 为了实现 MLO，我修改了wpa_supplicant.service设备，增加了-Dnl80211启动选项。原始设置没有使用任何-D指令。我想确保不使用无线扩展驱动程序，因为它不支持 Wifi7。然而，这并没有启用 MLO，所以我肯定nl80211之前已经打开了。

安装了由 Glotrends 生产的 Wifi 7 卡。日志显示已检测到，但尽管尝试了几次，固件仍无法加载。

uname -a
Linux compName 6.12.6-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.6-1 (2024-12-21) x86_64 GNU/Linux
（在内核 6.11.10 上结果相同）

sudo journalctl -xb | grep iwlwifi

Jan 14 08:00:54 compName kernel: iwlwifi 0000:02:00.0: Detected crf-id 0x2001910, cnv-id 0x2001910 wfpm id 0x80000000
Jan 14 08:00:54 compName kernel: iwlwifi 0000:02:00.0: PCI dev 272b/00f4, rev=0x472, rfid=0x112200
Jan 14 08:00:54 compName kernel: iwlwifi 0000:02:00.0: Detected Intel(R) Wi-Fi 7 BE200 320MHz
Jan 14 08:00:54 compName kernel: iwlwifi 0000:02:00.0: firmware: failed to load iwlwifi-gl-c0-fm-c0-93.ucode (-2)
Jan 14 08:00:54 compName kernel: iwlwifi 0000:02:00.0: firmware: failed to load iwlwifi-gl-c0-fm-c0-93.ucode (-2)
Jan 14 08:00:54 compName kernel: iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-gl-c0-fm-c0-93.ucode failed with error -2
Jan 14 08:00:54 compName kernel: iwlwifi 0000:02:00.0: firmware: failed to load iwlwifi-gl-c0-fm-c0-92.ucode (-2)
Jan 14 08:00:54 compName kernel: iwlwifi 0000:02:00.0: firmware: failed to load iwlwifi-gl-c0-fm-c0-92.ucode (-2)
Jan 14 08:00:54 compName kernel: iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-gl-c0-fm-c0-92.ucode failed with error -2
Jan 14 08:00:54 compName kernel: iwlwifi 0000:02:00.0: firmware: failed to load iwlwifi-gl-c0-fm-c0-91.ucode (-2)
Jan 14 08:00:54 compName kernel: iwlwifi 0000:02:00.0: firmware: failed to load iwlwifi-gl-c0-fm-c0-91.ucode (-2)
Jan 14 08:00:54 compName kernel: iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-gl-c0-fm-c0-91.ucode failed with error -2
Jan 14 08:00:54 compName kernel: iwlwifi 0000:02:00.0: firmware: failed to load iwlwifi-gl-c0-fm-c0-90.ucode (-2)
Jan 14 08:00:54 compName kernel: iwlwifi 0000:02:00.0: firmware: failed to load iwlwifi-gl-c0-fm-c0-90.ucode (-2)
Jan 14 08:00:54 compName kernel: iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-gl-c0-fm-c0-90.ucode failed with error -2
Jan 14 08:00:54 compName kernel: iwlwifi 0000:02:00.0: no suitable firmware found!
Jan 14 08:00:54 compName kernel: iwlwifi 0000:02:00.0: minimum version required: iwlwifi-gl-c0-fm-c0-90
Jan 14 08:00:54 compName kernel: iwlwifi 0000:02:00.0: maximum version supported: iwlwifi-gl-c0-fm-c0-93
Jan 14 08:00:54 compName kernel: iwlwifi 0000:02:00.0: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git

根据制造商的技术规格，我预计该卡开箱即可使用。该网站提供了英特尔网站的链接，那里也提供 Linux 驱动程序。该网站称驱动程序已包含在内核 6.11 中，但该卡需要固件才能工作。日志中说了同样的话，但我已经iwlwifi安装了模块。

升级apt到版本 >= 2.9.19 后，SHA1 和 RSA1024 签名被拒绝。

它的变更日志中有一个部分内容如下：

apt (2.9.19) 不稳定；紧急程度=中等

• 用 OpenSSL 替换 GnuTLS 和 gcrypt
• 在支持的 Debian 平台上用 Sequoia 替换 GnuPG
  • 方法：添加新的 sqv 方法
  • debian：添加默认策略以允许 SHA-1 自签名直至 2026 年
  • debian：将 sqv 插入到软件包构建中

所以我认为这将使策略能够接受 SHA1 签名，但也许我误解了。

在 Linux 6.12.6-amd64 上使用 SDDM 的 X11 上的 KDE plasma 6 #1 SMP PREEMPT_DYNAMIC Debian 6.12.6-1 (2024-12-21) x86_64 GNU/Linux

KDE 系统托盘上的两个蓝牙控制图标均未显示 BT 适配器。单击启用蓝牙会将小部件的 GUI 切换为启用 BT 的模式，但配对设备列表为空，扫描不起作用，并且没有适配器。

蓝牙曾经在这台机器上工作过，但我已经有一段时间没有使用蓝牙了，而更喜欢 KDE Con​​nect。这是自迁移到内核 6.12 和 KDE Plasma 6 以来第一次尝试使用蓝牙。

sudo journalctl -xb | grep tooth

Jan 06 09:36:44 compName kernel: Bluetooth: Core ver 2.22
Jan 06 09:36:44 compName kernel: Bluetooth: HCI device and connection manager initialized
Jan 06 09:36:44 compName kernel: Bluetooth: HCI socket layer initialized
Jan 06 09:36:44 compName kernel: Bluetooth: L2CAP socket layer initialized
Jan 06 09:36:44 compName kernel: Bluetooth: SCO socket layer initialized
Jan 06 09:36:44 compName kernel: Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
Jan 06 09:36:44 compName kernel: Bluetooth: hci0: Device revision is 5
Jan 06 09:36:44 compName kernel: Bluetooth: hci0: Secure boot is enabled
Jan 06 09:36:44 compName kernel: Bluetooth: hci0: OTP lock is enabled
Jan 06 09:36:44 compName kernel: Bluetooth: hci0: API lock is enabled
Jan 06 09:36:44 compName kernel: Bluetooth: hci0: Debug lock is disabled
Jan 06 09:36:44 compName kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014
Jan 06 09:36:44 compName kernel: Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
Jan 06 09:36:44 compName kernel: Bluetooth: hci0: Failed to send firmware data (-38)
Jan 06 09:36:44 compName kernel: Bluetooth: hci0: Intel reset sent to retry FW download
Jan 06 09:36:46 compName kernel: Bluetooth: hci0: command 0xfca6 tx timeout
Jan 06 09:36:46 compName kernel: Bluetooth: hci0: Reading supported features failed (-110)
Jan 06 09:36:46 compName kernel: Bluetooth: hci0: Error reading debug features
Jan 06 09:36:46 compName kernel: Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.
Jan 06 09:36:51 compName systemd[1]: Starting blueman-mechanism.service - Bluetooth management mechanism...
Jan 06 09:36:51 compName systemd[1]: Starting bluemon.service - LSB: Bluetooth monitoring daemon...
Jan 06 09:36:51 compName systemd[1]: Starting bluetooth.service - Bluetooth service...
░░ Subject: A start job for unit bluetooth.service has begun execution
░░ A start job for unit bluetooth.service has begun execution.
Jan 06 09:36:51 compName (uetoothd)[1143]: bluetooth.service: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
Jan 06 09:36:51 compName systemd[1]: Started bluemon.service - LSB: Bluetooth monitoring daemon.
Jan 06 09:36:51 compName bluetoothd[1143]: Bluetooth daemon 5.79
Jan 06 09:36:51 compName systemd[1]: Started bluetooth.service - Bluetooth service.
░░ Subject: A start job for unit bluetooth.service has finished successfully
░░ A start job for unit bluetooth.service has finished successfully.
Jan 06 09:36:51 compName systemd[1]: Reached target bluetooth.target - Bluetooth Support.
░░ Subject: A start job for unit bluetooth.target has finished successfully
░░ A start job for unit bluetooth.target has finished successfully.
Jan 06 09:36:51 compName bluetoothd[1143]: Starting SDP server
Jan 06 09:36:51 compName dbus-daemon[1145]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.6' (uid=0 pid=1143 comm="/usr/libexec/bluetooth/bluetoothd")
Jan 06 09:36:52 compName kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Jan 06 09:36:52 compName kernel: Bluetooth: BNEP filters: protocol multicast
Jan 06 09:36:52 compName kernel: Bluetooth: BNEP socket layer initialized
Jan 06 09:36:52 compName bluetoothd[1143]: src/plugin.c:init_plugin() System does not support bap plugin
Jan 06 09:36:52 compName bluetoothd[1143]: src/plugin.c:init_plugin() System does not support bass plugin
Jan 06 09:36:52 compName bluetoothd[1143]: src/plugin.c:init_plugin() System does not support mcp plugin
Jan 06 09:36:52 compName bluetoothd[1143]: src/plugin.c:init_plugin() System does not support vcp plugin
Jan 06 09:36:52 compName bluetoothd[1143]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
Jan 06 09:36:52 compName bluetoothd[1143]: src/plugin.c:init_plugin() System does not support micp plugin
Jan 06 09:36:52 compName bluetoothd[1143]: src/plugin.c:init_plugin() System does not support ccp plugin
Jan 06 09:36:52 compName bluetoothd[1143]: src/plugin.c:init_plugin() System does not support csip plugin
Jan 06 09:36:52 compName bluetoothd[1143]: src/plugin.c:init_plugin() System does not support asha plugin
Jan 06 09:36:52 compName bluetoothd[1143]: Bluetooth management interface 1.23 initialized
Jan 06 09:36:52 compName NetworkManager[1247]: <info>  [1736177812.2228] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.50.1/libnm-device-plugin-bluetooth.so)
Jan 06 09:36:52 compName systemd[1]: Started blueman-mechanism.service - Bluetooth management mechanism.
Jan 06 09:36:58 compName kernel: Modules linked in: xt_addrtype nft_compat br_netfilter bridge stp llc overlay nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables qrtr bnep binfmt_misc nvidia_drm(POE) drm_kms_helper nvidia_modeset(POE) nvidia(POE) intel_rapl_msr intel_rapl_common squashfs loop x86_pkg_temp_thermal intel_powerclamp iwlmvm kvm_intel snd_soc_avs mac80211 kvm snd_soc_hda_codec snd_hda_ext_core snd_hda_codec_realtek snd_soc_core snd_hda_codec_generic snd_hda_scodec_component snd_hda_codec_hdmi uvcvideo snd_compress snd_pcm_dmaengine crct10dif_pclmul ghash_clmulni_intel snd_hda_intel videobuf2_vmalloc libarc4 uvc sha512_ssse3 snd_intel_dspcfg videobuf2_memops snd_usb_audio snd_intel_sdw_acpi videobuf2_v4l2 sha256_ssse3 snd_hda_codec sha1_ssse3 videodev iwlwifi aesni_intel btusb snd_usbmidi_lib snd_hda_core gf128mul snd_rawmidi crypto_simd btrtl snd_hwdep snd_seq_device btintel cryptd videobuf2_common snd_pcm iTCO_wdt btbcm intel_pmc_bxt rapl btmtk intel_cstate iTCO_vendor_support cfg80211 bluetooth
Jan 06 09:37:01 compName systemd[2101]: Started mpris-proxy.service - Bluetooth mpris proxy.

sudo systemctl restart bluetooth.service没有帮助。

sudo rfkill list

0: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no
1: phy0: Wireless LAN
        Soft blocked: yes
        Hard blocked: no

bluetoothctl devices说No default controller available
sudo journalctl -xb | grep btusb没有显示错误

我已经重启了几次，似乎找到了固件，内核模块也加载了......但没有 BT。