Spectrum SBE1V1K (IPQ9574) OpenWrt Support

Can someone tell me how to get wifi working on this thing ? I have created all the board files and i put them in the hw 2.0 folder, but i still have no wifi tab in openwrt ?

Take the BDF from https://github.com/openwrt/firmware_qca-wireless/pull/123/commits/0d2b3c0c42b5cae549e59f1a3f003216ed4d6c4b and put it in package/firmware/ipq-wifi/src

Yeah, i managed to get it working. I didn’t include that mac80211 patch that you made in my build folder. All is good right now. Thanks for your work on this device. :slightly_smiling_face:

Could you kindly let me know if one or more reboots breaks your wireless config? I have an issue open https://github.com/openwrt/openwrt/issues/22157.

Basically, the PCIe ports are brought up in random order, which causes wifi-detect to add a new radio path into /etc/config/wireless.

You can run dmesg | grep -i "pcieportā€ and ls -la /sys/class/ieee80211/phy0/ and share the results here.

I’ll try to post tomorrow, today i spend all day installing OpenWRT on this device, assembling it, dissasembling it, and i’m exhausted.

1 Like

So i took a quick look, and i have a problem with my wifi. 2.4G turns on and works, but 5G and 6G are not enabling themselves. In log i have this:


[23 lut 2026, 15:56:05 CET] kern.info: [  600.286514] br-lan: port 5(phy0.1-ap0) entered blocking state
[23 lut 2026, 15:56:05 CET] kern.info: [  600.286551] br-lan: port 5(phy0.1-ap0) entered disabled state
[23 lut 2026, 15:56:05 CET] kern.info: [  600.291284] ath12k_pci 0001:01:00.0 phy0.1-ap0: entered allmulticast mode
[23 lut 2026, 15:56:05 CET] kern.info: [  600.297181] ath12k_pci 0001:01:00.0 phy0.1-ap0: entered promiscuous mode
[23 lut 2026, 15:56:05 CET] kern.info: [  600.304037] br-lan: port 5(phy0.1-ap0) entered blocking state
[23 lut 2026, 15:56:05 CET] kern.info: [  600.310513] br-lan: port 5(phy0.1-ap0) entered forwarding state
[23 lut 2026, 15:56:05 CET] daemon.notice: hostapd: phy0.1-ap0: interface state UNINITIALIZED->COUNTRY_UPDATE
[23 lut 2026, 15:56:05 CET] kern.info: [  600.316567] br-lan: port 5(phy0.1-ap0) entered disabled state
[23 lut 2026, 15:56:05 CET] daemon.notice: hostapd: phy0.1-ap0: interface state COUNTRY_UPDATE->HT_SCAN
[23 lut 2026, 15:56:05 CET] kern.info: [  600.404075] br-lan: port 5(phy0.1-ap0) entered disabled state
[23 lut 2026, 15:56:05 CET] kern.info: [  600.404366] ath12k_pci 0001:01:00.0 phy0.1-ap0: left allmulticast mode
[23 lut 2026, 15:56:05 CET] kern.info: [  600.408802] ath12k_pci 0001:01:00.0 phy0.1-ap0: left promiscuous mode
[23 lut 2026, 15:56:05 CET] daemon.notice: hostapd: nl80211: Failed to remove interface phy0.1-ap0 from bridge br-lan: Invalid argument
[23 lut 2026, 15:56:05 CET] kern.info: [  600.415294] br-lan: port 5(phy0.1-ap0) entered disabled state
[23 lut 2026, 15:56:05 CET] kern.info: [  600.655189] br-lan: port 5(phy0.1-ap0) entered blocking state
[23 lut 2026, 15:56:05 CET] kern.info: [  600.655220] br-lan: port 5(phy0.1-ap0) entered disabled state
[23 lut 2026, 15:56:05 CET] kern.info: [  600.659932] ath12k_pci 0001:01:00.0 phy0.1-ap0: entered allmulticast mode
[23 lut 2026, 15:56:05 CET] daemon.err: hostapd: Failed to request a scan of neighboring BSSes ret=-22 (Invalid argument)
[23 lut 2026, 15:56:05 CET] daemon.notice: hostapd: phy0.1-ap0: interface state HT_SCAN->DISABLED
[23 lut 2026, 15:56:05 CET] daemon.notice: hostapd: phy0.1-ap0: AP-DISABLED
[23 lut 2026, 15:56:05 CET] daemon.err: hostapd: phy0.1-ap0: Unable to setup interface.
[23 lut 2026, 15:56:05 CET] kern.info: [  600.665819] ath12k_pci 0001:01:00.0 phy0.1-ap0: entered promiscuous mode
[23 lut 2026, 15:56:05 CET] kern.info: [  600.672761] ath12k_pci 0001:01:00.0 phy0.1-ap0: left allmulticast mode
[23 lut 2026, 15:56:05 CET] kern.info: [  600.679206] ath12k_pci 0001:01:00.0 phy0.1-ap0: left promiscuous mode
[23 lut 2026, 15:56:05 CET] kern.info: [  600.685573] br-lan: port 5(phy0.1-ap0) entered disabled state
[23 lut 2026, 15:56:06 CET] daemon.err: hostapd: rmdir[ctrl_interface=/var/run/hostapd]: Permission denied
[23 lut 2026, 15:56:06 CET] daemon.notice: hostapd: phy0.1-ap0: CTRL-EVENT-TERMINATING
[23 lut 2026, 15:56:06 CET] daemon.err: hostapd: hostapd_free_hapd_data: Interface phy0.1-ap0 wasn't started
[23 lut 2026, 15:56:06 CET] daemon.notice: hostapd: hostapd.add_iface failed for phy phy0.1 ifname=phy0.1-ap0

The dmesg command doesn’t give me anything, i’ll try to post more tommorow.

Here’s where this device stands:

If you manage to make a successful build, everything should work well and the only annoyance will be the fan ticking. If anyone is so invested in this device, I’d advise you to investigate PWM and/or the WSI issues. Good luck!

3 Likes

Thank you for the work! May I ask if hardware offloading of IPQ9574 (PPE?) is working?

AFAIK Qualcomm only sent the code to get Ethernet packets to flow through without offloading for Linux similar to how NSS is enabled in IPQ807x, https://lore.kernel.org/all/20250818-qcom_ipq_ppe-v8-0-1d4ff641fce9@quicinc.com/.

The driver can also be extended later for adding support for L2/L3
network offload features that the PPE can support.

I’m not sure if OpenWrt includes any hardware acceleration patches

1 Like