* Re: ath12k: No 6GHz Wireless found [not found] <CAMb39_ngQs8=FUML5QXMh2RmEZBZ2NwUHefhGoTkGtHat+KWJA@mail.gmail.com> @ 2025-04-01 18:53 ` Jeff Johnson 2025-04-01 21:21 ` Walt Holman 0 siblings, 1 reply; 32+ messages in thread From: Jeff Johnson @ 2025-04-01 18:53 UTC (permalink / raw) To: Walt Holman, linux-wireless, ath12k@lists.infradead.org On 3/30/2025 7:28 AM, Walt Holman wrote: > Hello, > > I have a wcn7850 hw2.0 based m.2 wireless card in my laptop and am > unable to see or connect to 6Ghz networks. I have an ASUS BE30000 wifi > router setup with a separate 6ghz only network, which my phone and > other laptops can connect to. I'm unable to even see this network on > this particular laptop. Months ago (maybe September), I could see it > occasionally, but now it never shows up. I'm using firmware from > git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git > and track the kernels pretty closely. I'm currently running 6.14.0 > built from source. Any suggestions? Some HW info is below: > > 63:00.0 Network controller: Qualcomm Technologies, Inc WCN785x Wi-Fi > 7(802.11be) 320MHz 2x2 [FastConnect 7800 > ] (rev 01) > Subsystem: Quectel Wireless Solutions Co., Ltd. Device 8000 > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- > ParErr- Stepping- SERR- FastB2B- DisINTx+ > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort+ > <TAbort- <MAbort- >SERR- <PERR- INTx- > Latency: 0, Cache Line Size: 64 bytes > Interrupt: pin ? routed to IRQ 111 > IOMMU group: 19 > Region 0: Memory at dd800000 (64-bit, non-prefetchable) [size=2M] > Capabilities: [40] Power Management version 3 > Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA > PME(D0+,D1-,D2-,D3hot+,D3cold+) > Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- > Capabilities: [50] MSI: Enable+ Count=16/32 Maskable+ 64bit- > Address: fee00000 Data: 0000 > Masking: ffff8000 Pending: 00000000 > Capabilities: [70] Express (v2) Endpoint, IntMsgNum 0 > DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s > unlimited, L1 unlimited > ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- > SlotPowerLimit 75W TEE-IO- > DevCtl: CorrErr+ NonFatalErr+ FatalErr+ UnsupReq+ > RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ > MaxPayload 128 bytes, MaxReadReq 512 bytes > DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- > AuxPwr+ TransPend- > LnkCap: Port #0, Speed 8GT/s, Width x2, ASPM L0s L1, > Exit Latency L0s <1us, L1 <64us > ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+ > LnkCtl: ASPM L1 Enabled; RCB 64 bytes, LnkDisable- CommClk+ > ExtSynch+ ClockPM- AutWidDis- BWInt- AutBWInt- > LnkSta: Speed 8GT/s, Width x1 (downgraded) > TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- > DevCap2: Completion Timeout: Range ABCD, TimeoutDis+ > NROPrPrP- LTR+ > 10BitTagComp- 10BitTagReq- OBFF Not Supported, > ExtFmt- EETLPPrefix- > EmergencyPowerReduction Not Supported, > EmergencyPowerReductionInit- > FRS- TPHComp+ ExtTPHComp- > AtomicOpsCap: 32bit- 64bit- 128bitCAS- > DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- > AtomicOpsCtl: ReqEn- > IDOReq- IDOCompl- LTR+ EmergencyPowerReductionReq- > 10BitTagReq- OBFF Disabled, EETLPPrefixBlk- > LnkCap2: Supported Link Speeds: 2.5-8GT/s, Crosslink- > Retimer- 2Retimers- DRS- > LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis- > Transmit Margin: Normal Operating Range, > EnterModifiedCompliance- ComplianceSOS- > Compliance Preset/De-emphasis: -6dB > de-emphasis, 0dB preshoot > LnkSta2: Current De-emphasis Level: -3.5dB, > EqualizationComplete+ EqualizationPhase1+ > EqualizationPhase2+ EqualizationPhase3+ > LinkEqualizationRequest- > Retimer- 2Retimers- CrosslinkRes: unsupported > Capabilities: [100 v2] Advanced Error Reporting > UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- > UnxCmplt- RxOF- MalfTLP- > ECRC- UnsupReq- ACSViol- UncorrIntErr- > BlockedTLP- AtomicOpBlocked- TLPBlockedErr- > PoisonTLPBlocked- DMWrReqBlocked- IDECheck- > MisIDETLP- PCRC_CHECK- TLPXlatBlocked- > UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- > UnxCmplt- RxOF- MalfTLP- > ECRC- UnsupReq- ACSViol- UncorrIntErr+ > BlockedTLP- AtomicOpBlocked- TLPBlockedErr- > PoisonTLPBlocked- DMWrReqBlocked- IDECheck- > MisIDETLP- PCRC_CHECK- TLPXlatBlocked- > UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- > UnxCmplt- RxOF+ MalfTLP+ > ECRC- UnsupReq- ACSViol- UncorrIntErr+ > BlockedTLP- AtomicOpBlocked- TLPBlockedErr- > PoisonTLPBlocked- DMWrReqBlocked- IDECheck- > MisIDETLP- PCRC_CHECK- TLPXlatBlocked- > CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- > AdvNonFatalErr- CorrIntErr- HeaderOF- > CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- > AdvNonFatalErr+ CorrIntErr+ HeaderOF+ > AERCap: First Error Pointer: 00, ECRCGenCap+ ECRCGenEn- > ECRCChkCap+ ECRCChkEn- > MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap- > HeaderLog: 00000000 00000000 00000000 00000000 > Capabilities: [148 v1] Secondary PCI Express > LnkCtl3: LnkEquIntrruptEn- PerformEqu- > LaneErrStat: 0 > Capabilities: [158 v1] Transaction Processing Hints > No steering table available > Capabilities: [1e4 v1] Latency Tolerance Reporting > Max snoop latency: 1048576ns > Max no snoop latency: 1048576ns > Capabilities: [1ec v1] L1 PM Substates > L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ > ASPM_L1.1+ L1_PM_Substates+ > PortCommonModeRestoreTime=70us PortTPowerOnTime=0us > L1SubCtl1: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ > T_CommonMode=0us LTR1.2_Threshold=166912ns > L1SubCtl2: T_PwrOn=90us > Kernel driver in use: ath12k_pci > Kernel modules: ath12k > > root@walt-ROG-zephyrus:~# iw reg get > global > country US: DFS-FCC > (902 - 904 @ 2), (N/A, 30), (N/A) > (904 - 920 @ 16), (N/A, 30), (N/A) > (920 - 928 @ 8), (N/A, 30), (N/A) > (2400 - 2472 @ 40), (N/A, 30), (N/A) > (5150 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW > (5250 - 5350 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW > (5470 - 5730 @ 160), (N/A, 24), (0 ms), DFS > (5730 - 5850 @ 80), (N/A, 30), (N/A), AUTO-BW > (5850 - 5895 @ 40), (N/A, 27), (N/A), NO-OUTDOOR, AUTO-BW, PASSIVE-SCAN > (5925 - 7125 @ 320), (N/A, 12), (N/A), NO-OUTDOOR, PASSIVE-SCAN > (57240 - 71000 @ 2160), (N/A, 40), (N/A) > > phy#0 (self-managed) > country na: DFS-UNSET > (2402 - 2472 @ 40), (N/A, 20), (N/A) > (2457 - 2482 @ 20), (N/A, 20), (N/A), PASSIVE-SCAN > (5170 - 5330 @ 160), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN > (5490 - 5730 @ 160), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN > (5735 - 5895 @ 160), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN > (5945 - 7125 @ 320), (N/A, 30), (N/A), AUTO-BW, PASSIVE-SCAN > I added the ath12k list to make sure this has the proper attention. Since you are building from source, can you please test with the following patch: https://msgid.link/20250401020840.357-1-quic_kangyang@quicinc.com This is in my pending queue. /jeff ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ath12k: No 6GHz Wireless found 2025-04-01 18:53 ` ath12k: No 6GHz Wireless found Jeff Johnson @ 2025-04-01 21:21 ` Walt Holman 2025-04-02 2:48 ` Kang Yang 0 siblings, 1 reply; 32+ messages in thread From: Walt Holman @ 2025-04-01 21:21 UTC (permalink / raw) To: Jeff Johnson; +Cc: linux-wireless, ath12k@lists.infradead.org On Tue, Apr 1, 2025 at 1:53 PM Jeff Johnson <jeff.johnson@oss.qualcomm.com> wrote: > > On 3/30/2025 7:28 AM, Walt Holman wrote: > > Hello, > > > > I have a wcn7850 hw2.0 based m.2 wireless card in my laptop and am > > unable to see or connect to 6Ghz networks. I have an ASUS BE30000 wifi > > router setup with a separate 6ghz only network, which my phone and > > other laptops can connect to. I'm unable to even see this network on > > this particular laptop. Months ago (maybe September), I could see it > > occasionally, but now it never shows up. I'm using firmware from > > git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git > > and track the kernels pretty closely. I'm currently running 6.14.0 > > built from source. Any suggestions? Some HW info is below: > > > > 63:00.0 Network controller: Qualcomm Technologies, Inc WCN785x Wi-Fi > > 7(802.11be) 320MHz 2x2 [FastConnect 7800 > > ] (rev 01) > > Subsystem: Quectel Wireless Solutions Co., Ltd. Device 8000 > > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- > > ParErr- Stepping- SERR- FastB2B- DisINTx+ > > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort+ > > <TAbort- <MAbort- >SERR- <PERR- INTx- > > Latency: 0, Cache Line Size: 64 bytes > > Interrupt: pin ? routed to IRQ 111 > > IOMMU group: 19 > > Region 0: Memory at dd800000 (64-bit, non-prefetchable) [size=2M] > > Capabilities: [40] Power Management version 3 > > Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA > > PME(D0+,D1-,D2-,D3hot+,D3cold+) > > Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- > > Capabilities: [50] MSI: Enable+ Count=16/32 Maskable+ 64bit- > > Address: fee00000 Data: 0000 > > Masking: ffff8000 Pending: 00000000 > > Capabilities: [70] Express (v2) Endpoint, IntMsgNum 0 > > DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s > > unlimited, L1 unlimited > > ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- > > SlotPowerLimit 75W TEE-IO- > > DevCtl: CorrErr+ NonFatalErr+ FatalErr+ UnsupReq+ > > RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ > > MaxPayload 128 bytes, MaxReadReq 512 bytes > > DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- > > AuxPwr+ TransPend- > > LnkCap: Port #0, Speed 8GT/s, Width x2, ASPM L0s L1, > > Exit Latency L0s <1us, L1 <64us > > ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+ > > LnkCtl: ASPM L1 Enabled; RCB 64 bytes, LnkDisable- CommClk+ > > ExtSynch+ ClockPM- AutWidDis- BWInt- AutBWInt- > > LnkSta: Speed 8GT/s, Width x1 (downgraded) > > TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- > > DevCap2: Completion Timeout: Range ABCD, TimeoutDis+ > > NROPrPrP- LTR+ > > 10BitTagComp- 10BitTagReq- OBFF Not Supported, > > ExtFmt- EETLPPrefix- > > EmergencyPowerReduction Not Supported, > > EmergencyPowerReductionInit- > > FRS- TPHComp+ ExtTPHComp- > > AtomicOpsCap: 32bit- 64bit- 128bitCAS- > > DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- > > AtomicOpsCtl: ReqEn- > > IDOReq- IDOCompl- LTR+ EmergencyPowerReductionReq- > > 10BitTagReq- OBFF Disabled, EETLPPrefixBlk- > > LnkCap2: Supported Link Speeds: 2.5-8GT/s, Crosslink- > > Retimer- 2Retimers- DRS- > > LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis- > > Transmit Margin: Normal Operating Range, > > EnterModifiedCompliance- ComplianceSOS- > > Compliance Preset/De-emphasis: -6dB > > de-emphasis, 0dB preshoot > > LnkSta2: Current De-emphasis Level: -3.5dB, > > EqualizationComplete+ EqualizationPhase1+ > > EqualizationPhase2+ EqualizationPhase3+ > > LinkEqualizationRequest- > > Retimer- 2Retimers- CrosslinkRes: unsupported > > Capabilities: [100 v2] Advanced Error Reporting > > UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- > > UnxCmplt- RxOF- MalfTLP- > > ECRC- UnsupReq- ACSViol- UncorrIntErr- > > BlockedTLP- AtomicOpBlocked- TLPBlockedErr- > > PoisonTLPBlocked- DMWrReqBlocked- IDECheck- > > MisIDETLP- PCRC_CHECK- TLPXlatBlocked- > > UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- > > UnxCmplt- RxOF- MalfTLP- > > ECRC- UnsupReq- ACSViol- UncorrIntErr+ > > BlockedTLP- AtomicOpBlocked- TLPBlockedErr- > > PoisonTLPBlocked- DMWrReqBlocked- IDECheck- > > MisIDETLP- PCRC_CHECK- TLPXlatBlocked- > > UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- > > UnxCmplt- RxOF+ MalfTLP+ > > ECRC- UnsupReq- ACSViol- UncorrIntErr+ > > BlockedTLP- AtomicOpBlocked- TLPBlockedErr- > > PoisonTLPBlocked- DMWrReqBlocked- IDECheck- > > MisIDETLP- PCRC_CHECK- TLPXlatBlocked- > > CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- > > AdvNonFatalErr- CorrIntErr- HeaderOF- > > CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- > > AdvNonFatalErr+ CorrIntErr+ HeaderOF+ > > AERCap: First Error Pointer: 00, ECRCGenCap+ ECRCGenEn- > > ECRCChkCap+ ECRCChkEn- > > MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap- > > HeaderLog: 00000000 00000000 00000000 00000000 > > Capabilities: [148 v1] Secondary PCI Express > > LnkCtl3: LnkEquIntrruptEn- PerformEqu- > > LaneErrStat: 0 > > Capabilities: [158 v1] Transaction Processing Hints > > No steering table available > > Capabilities: [1e4 v1] Latency Tolerance Reporting > > Max snoop latency: 1048576ns > > Max no snoop latency: 1048576ns > > Capabilities: [1ec v1] L1 PM Substates > > L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ > > ASPM_L1.1+ L1_PM_Substates+ > > PortCommonModeRestoreTime=70us PortTPowerOnTime=0us > > L1SubCtl1: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ > > T_CommonMode=0us LTR1.2_Threshold=166912ns > > L1SubCtl2: T_PwrOn=90us > > Kernel driver in use: ath12k_pci > > Kernel modules: ath12k > > > > root@walt-ROG-zephyrus:~# iw reg get > > global > > country US: DFS-FCC > > (902 - 904 @ 2), (N/A, 30), (N/A) > > (904 - 920 @ 16), (N/A, 30), (N/A) > > (920 - 928 @ 8), (N/A, 30), (N/A) > > (2400 - 2472 @ 40), (N/A, 30), (N/A) > > (5150 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW > > (5250 - 5350 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW > > (5470 - 5730 @ 160), (N/A, 24), (0 ms), DFS > > (5730 - 5850 @ 80), (N/A, 30), (N/A), AUTO-BW > > (5850 - 5895 @ 40), (N/A, 27), (N/A), NO-OUTDOOR, AUTO-BW, PASSIVE-SCAN > > (5925 - 7125 @ 320), (N/A, 12), (N/A), NO-OUTDOOR, PASSIVE-SCAN > > (57240 - 71000 @ 2160), (N/A, 40), (N/A) > > > > phy#0 (self-managed) > > country na: DFS-UNSET > > (2402 - 2472 @ 40), (N/A, 20), (N/A) > > (2457 - 2482 @ 20), (N/A, 20), (N/A), PASSIVE-SCAN > > (5170 - 5330 @ 160), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN > > (5490 - 5730 @ 160), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN > > (5735 - 5895 @ 160), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN > > (5945 - 7125 @ 320), (N/A, 30), (N/A), AUTO-BW, PASSIVE-SCAN > > > > I added the ath12k list to make sure this has the proper attention. > Since you are building from source, can you please test with the following patch: > https://msgid.link/20250401020840.357-1-quic_kangyang@quicinc.com > > This is in my pending queue. > > /jeff > Hi Jeff, No dice on the 6Ghz networks. It fixed up the registration info, but I still don't see any 6Ghz networks. Even from an 'iw wlp99s0 scan' global country US: DFS-FCC (902 - 904 @ 2), (N/A, 30), (N/A) (904 - 920 @ 16), (N/A, 30), (N/A) (920 - 928 @ 8), (N/A, 30), (N/A) (2400 - 2472 @ 40), (N/A, 30), (N/A) (5150 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW (5250 - 5350 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW (5470 - 5730 @ 160), (N/A, 24), (0 ms), DFS (5730 - 5850 @ 80), (N/A, 30), (N/A), AUTO-BW (5850 - 5895 @ 40), (N/A, 27), (N/A), NO-OUTDOOR, AUTO-BW, PASSIVE-SCAN (5925 - 7125 @ 320), (N/A, 12), (N/A), NO-OUTDOOR, PASSIVE-SCAN (57240 - 71000 @ 2160), (N/A, 40), (N/A) phy#0 (self-managed) country US: DFS-FCC (2402 - 2472 @ 40), (6, 30), (N/A) (5170 - 5250 @ 80), (6, 24), (N/A), AUTO-BW (5250 - 5330 @ 80), (6, 24), (0 ms), DFS, AUTO-BW (5490 - 5730 @ 160), (6, 24), (0 ms), DFS, AUTO-BW (5735 - 5855 @ 80), (6, 30), (N/A), AUTO-BW (5855 - 5925 @ 40), (6, 30), (N/A), NO-OUTDOOR, AUTO-BW (5925 - 7125 @ 320), (N/A, 30), (N/A), NO-OUTDOOR, AUTO-BW -Walt ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ath12k: No 6GHz Wireless found 2025-04-01 21:21 ` Walt Holman @ 2025-04-02 2:48 ` Kang Yang 2025-04-02 17:48 ` Walt Holman 2025-04-02 17:50 ` Walt Holman 0 siblings, 2 replies; 32+ messages in thread From: Kang Yang @ 2025-04-02 2:48 UTC (permalink / raw) To: Walt Holman, Jeff Johnson; +Cc: linux-wireless, ath12k@lists.infradead.org On 4/2/2025 5:21 AM, Walt Holman wrote: > On Tue, Apr 1, 2025 at 1:53 PM Jeff Johnson > <jeff.johnson@oss.qualcomm.com> wrote: >> >> On 3/30/2025 7:28 AM, Walt Holman wrote: >>> Hello, >>> >>> I have a wcn7850 hw2.0 based m.2 wireless card in my laptop and am >>> unable to see or connect to 6Ghz networks. I have an ASUS BE30000 wifi >>> router setup with a separate 6ghz only network, which my phone and >>> other laptops can connect to. I'm unable to even see this network on >>> this particular laptop. Months ago (maybe September), I could see it >>> occasionally, but now it never shows up. I'm using firmware from >>> git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git >>> and track the kernels pretty closely. I'm currently running 6.14.0 >>> built from source. Any suggestions? Some HW info is below: >>> >>> 63:00.0 Network controller: Qualcomm Technologies, Inc WCN785x Wi-Fi >>> 7(802.11be) 320MHz 2x2 [FastConnect 7800 >>> ] (rev 01) >>> Subsystem: Quectel Wireless Solutions Co., Ltd. Device 8000 >>> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- >>> ParErr- Stepping- SERR- FastB2B- DisINTx+ >>> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort+ >>> <TAbort- <MAbort- >SERR- <PERR- INTx- >>> Latency: 0, Cache Line Size: 64 bytes >>> Interrupt: pin ? routed to IRQ 111 >>> IOMMU group: 19 >>> Region 0: Memory at dd800000 (64-bit, non-prefetchable) [size=2M] >>> Capabilities: [40] Power Management version 3 >>> Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA >>> PME(D0+,D1-,D2-,D3hot+,D3cold+) >>> Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- >>> Capabilities: [50] MSI: Enable+ Count=16/32 Maskable+ 64bit- >>> Address: fee00000 Data: 0000 >>> Masking: ffff8000 Pending: 00000000 >>> Capabilities: [70] Express (v2) Endpoint, IntMsgNum 0 >>> DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s >>> unlimited, L1 unlimited >>> ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- >>> SlotPowerLimit 75W TEE-IO- >>> DevCtl: CorrErr+ NonFatalErr+ FatalErr+ UnsupReq+ >>> RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ >>> MaxPayload 128 bytes, MaxReadReq 512 bytes >>> DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- >>> AuxPwr+ TransPend- >>> LnkCap: Port #0, Speed 8GT/s, Width x2, ASPM L0s L1, >>> Exit Latency L0s <1us, L1 <64us >>> ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+ >>> LnkCtl: ASPM L1 Enabled; RCB 64 bytes, LnkDisable- CommClk+ >>> ExtSynch+ ClockPM- AutWidDis- BWInt- AutBWInt- >>> LnkSta: Speed 8GT/s, Width x1 (downgraded) >>> TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- >>> DevCap2: Completion Timeout: Range ABCD, TimeoutDis+ >>> NROPrPrP- LTR+ >>> 10BitTagComp- 10BitTagReq- OBFF Not Supported, >>> ExtFmt- EETLPPrefix- >>> EmergencyPowerReduction Not Supported, >>> EmergencyPowerReductionInit- >>> FRS- TPHComp+ ExtTPHComp- >>> AtomicOpsCap: 32bit- 64bit- 128bitCAS- >>> DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- >>> AtomicOpsCtl: ReqEn- >>> IDOReq- IDOCompl- LTR+ EmergencyPowerReductionReq- >>> 10BitTagReq- OBFF Disabled, EETLPPrefixBlk- >>> LnkCap2: Supported Link Speeds: 2.5-8GT/s, Crosslink- >>> Retimer- 2Retimers- DRS- >>> LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis- >>> Transmit Margin: Normal Operating Range, >>> EnterModifiedCompliance- ComplianceSOS- >>> Compliance Preset/De-emphasis: -6dB >>> de-emphasis, 0dB preshoot >>> LnkSta2: Current De-emphasis Level: -3.5dB, >>> EqualizationComplete+ EqualizationPhase1+ >>> EqualizationPhase2+ EqualizationPhase3+ >>> LinkEqualizationRequest- >>> Retimer- 2Retimers- CrosslinkRes: unsupported >>> Capabilities: [100 v2] Advanced Error Reporting >>> UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- >>> UnxCmplt- RxOF- MalfTLP- >>> ECRC- UnsupReq- ACSViol- UncorrIntErr- >>> BlockedTLP- AtomicOpBlocked- TLPBlockedErr- >>> PoisonTLPBlocked- DMWrReqBlocked- IDECheck- >>> MisIDETLP- PCRC_CHECK- TLPXlatBlocked- >>> UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- >>> UnxCmplt- RxOF- MalfTLP- >>> ECRC- UnsupReq- ACSViol- UncorrIntErr+ >>> BlockedTLP- AtomicOpBlocked- TLPBlockedErr- >>> PoisonTLPBlocked- DMWrReqBlocked- IDECheck- >>> MisIDETLP- PCRC_CHECK- TLPXlatBlocked- >>> UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- >>> UnxCmplt- RxOF+ MalfTLP+ >>> ECRC- UnsupReq- ACSViol- UncorrIntErr+ >>> BlockedTLP- AtomicOpBlocked- TLPBlockedErr- >>> PoisonTLPBlocked- DMWrReqBlocked- IDECheck- >>> MisIDETLP- PCRC_CHECK- TLPXlatBlocked- >>> CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- >>> AdvNonFatalErr- CorrIntErr- HeaderOF- >>> CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- >>> AdvNonFatalErr+ CorrIntErr+ HeaderOF+ >>> AERCap: First Error Pointer: 00, ECRCGenCap+ ECRCGenEn- >>> ECRCChkCap+ ECRCChkEn- >>> MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap- >>> HeaderLog: 00000000 00000000 00000000 00000000 >>> Capabilities: [148 v1] Secondary PCI Express >>> LnkCtl3: LnkEquIntrruptEn- PerformEqu- >>> LaneErrStat: 0 >>> Capabilities: [158 v1] Transaction Processing Hints >>> No steering table available >>> Capabilities: [1e4 v1] Latency Tolerance Reporting >>> Max snoop latency: 1048576ns >>> Max no snoop latency: 1048576ns >>> Capabilities: [1ec v1] L1 PM Substates >>> L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ >>> ASPM_L1.1+ L1_PM_Substates+ >>> PortCommonModeRestoreTime=70us PortTPowerOnTime=0us >>> L1SubCtl1: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ >>> T_CommonMode=0us LTR1.2_Threshold=166912ns >>> L1SubCtl2: T_PwrOn=90us >>> Kernel driver in use: ath12k_pci >>> Kernel modules: ath12k >>> >>> root@walt-ROG-zephyrus:~# iw reg get >>> global >>> country US: DFS-FCC >>> (902 - 904 @ 2), (N/A, 30), (N/A) >>> (904 - 920 @ 16), (N/A, 30), (N/A) >>> (920 - 928 @ 8), (N/A, 30), (N/A) >>> (2400 - 2472 @ 40), (N/A, 30), (N/A) >>> (5150 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW >>> (5250 - 5350 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW >>> (5470 - 5730 @ 160), (N/A, 24), (0 ms), DFS >>> (5730 - 5850 @ 80), (N/A, 30), (N/A), AUTO-BW >>> (5850 - 5895 @ 40), (N/A, 27), (N/A), NO-OUTDOOR, AUTO-BW, PASSIVE-SCAN >>> (5925 - 7125 @ 320), (N/A, 12), (N/A), NO-OUTDOOR, PASSIVE-SCAN >>> (57240 - 71000 @ 2160), (N/A, 40), (N/A) >>> >>> phy#0 (self-managed) >>> country na: DFS-UNSET >>> (2402 - 2472 @ 40), (N/A, 20), (N/A) >>> (2457 - 2482 @ 20), (N/A, 20), (N/A), PASSIVE-SCAN >>> (5170 - 5330 @ 160), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN >>> (5490 - 5730 @ 160), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN >>> (5735 - 5895 @ 160), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN >>> (5945 - 7125 @ 320), (N/A, 30), (N/A), AUTO-BW, PASSIVE-SCAN >>> >> >> I added the ath12k list to make sure this has the proper attention. >> Since you are building from source, can you please test with the following patch: >> https://msgid.link/20250401020840.357-1-quic_kangyang@quicinc.com >> >> This is in my pending queue. >> >> /jeff >> > > Hi Jeff, > > No dice on the 6Ghz networks. It fixed up the registration info, but I > still don't see any 6Ghz networks. Even from an 'iw wlp99s0 scan' > > global > country US: DFS-FCC > (902 - 904 @ 2), (N/A, 30), (N/A) > (904 - 920 @ 16), (N/A, 30), (N/A) > (920 - 928 @ 8), (N/A, 30), (N/A) > (2400 - 2472 @ 40), (N/A, 30), (N/A) > (5150 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW > (5250 - 5350 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW > (5470 - 5730 @ 160), (N/A, 24), (0 ms), DFS > (5730 - 5850 @ 80), (N/A, 30), (N/A), AUTO-BW > (5850 - 5895 @ 40), (N/A, 27), (N/A), NO-OUTDOOR, AUTO-BW, PASSIVE-SCAN > (5925 - 7125 @ 320), (N/A, 12), (N/A), NO-OUTDOOR, PASSIVE-SCAN > (57240 - 71000 @ 2160), (N/A, 40), (N/A) > > phy#0 (self-managed) > country US: DFS-FCC > (2402 - 2472 @ 40), (6, 30), (N/A) > (5170 - 5250 @ 80), (6, 24), (N/A), AUTO-BW > (5250 - 5330 @ 80), (6, 24), (0 ms), DFS, AUTO-BW > (5490 - 5730 @ 160), (6, 24), (0 ms), DFS, AUTO-BW > (5735 - 5855 @ 80), (6, 30), (N/A), AUTO-BW > (5855 - 5925 @ 40), (6, 30), (N/A), NO-OUTDOOR, AUTO-BW > (5925 - 7125 @ 320), (N/A, 30), (N/A), NO-OUTDOOR, AUTO-BW > > Test on 6.14.0-rc5-wt-ath+, with the firmware you used. I can get 6 GHz AP and connect to it. ath12k_pci 0000:03:00.0: fw_version 0x100301e1 fw_build_timestamp 2023-12-06 04:05 fw_build_id QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3 yk@yk-Mayan:~$ sudo iw wls1 scan | tee iw_scan.log: BSS 62:03:7f:12:64:64(on wls1) -- associated TSF: 606308271476 usec (7d, 00:25:08) freq: 6275 beacon interval: 100 TUs capability: ESS Privacy SpectrumMgmt ShortSlotTime (0x0511) signal: -17.00 dBm last seen: 52 ms ago Information elements from Probe Response frame: SSID: MLO-KANG-6G and other 6 GHz APs: SSID: 6G-gxia SSID: NETGEAR97-6G …… kernel log: [88158.033218] wls1: Inserted STA 62:03:7f:12:64:64 [88158.033232] wls1: authenticate with 62:03:7f:12:64:64 (local address=00:03:7f:37:12:54) [88158.033242] wls1: send auth to 62:03:7f:12:64:64 (try 1/3) [88158.041895] wls1: authenticated [88158.041914] wls1: moving STA 62:03:7f:12:64:64 to state 2 [88158.044291] wls1: determined local STA to be EHT, BW limited to 320 MHz [88158.045719] wls1: associate with 62:03:7f:12:64:64 (try 1/3) [88158.067045] wls1: RX AssocResp from 62:03:7f:12:64:64 (capab=0x511 status=0 aid=4) [88158.089090] wls1: associated I can even connect to it by Ubuntu GUI. Can you update to 6.14.0-rc5-wt-ath+ and have a retry? Also please make sure that your wpa_supplicant/iw support 6 GHz(or directly update to the latest version). If you still cannot find 6 GHz AP, you can set debug_mask to 0xffffffff to get ath12k logs. Then give it to us. > -Walt > ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ath12k: No 6GHz Wireless found 2025-04-02 2:48 ` Kang Yang @ 2025-04-02 17:48 ` Walt Holman 2025-04-03 8:19 ` Kang Yang 2025-04-02 17:50 ` Walt Holman 1 sibling, 1 reply; 32+ messages in thread From: Walt Holman @ 2025-04-02 17:48 UTC (permalink / raw) To: Kang Yang; +Cc: Jeff Johnson, linux-wireless, ath12k@lists.infradead.org [-- Attachment #1: Type: text/plain, Size: 13438 bytes --] On Tue, Apr 1, 2025 at 9:48 PM Kang Yang <quic_kangyang@quicinc.com> wrote: > > > > On 4/2/2025 5:21 AM, Walt Holman wrote: > > On Tue, Apr 1, 2025 at 1:53 PM Jeff Johnson > > <jeff.johnson@oss.qualcomm.com> wrote: > >> > >> On 3/30/2025 7:28 AM, Walt Holman wrote: > >>> Hello, > >>> > >>> I have a wcn7850 hw2.0 based m.2 wireless card in my laptop and am > >>> unable to see or connect to 6Ghz networks. I have an ASUS BE30000 wifi > >>> router setup with a separate 6ghz only network, which my phone and > >>> other laptops can connect to. I'm unable to even see this network on > >>> this particular laptop. Months ago (maybe September), I could see it > >>> occasionally, but now it never shows up. I'm using firmware from > >>> git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git > >>> and track the kernels pretty closely. I'm currently running 6.14.0 > >>> built from source. Any suggestions? Some HW info is below: > >>> > >>> 63:00.0 Network controller: Qualcomm Technologies, Inc WCN785x Wi-Fi > >>> 7(802.11be) 320MHz 2x2 [FastConnect 7800 > >>> ] (rev 01) > >>> Subsystem: Quectel Wireless Solutions Co., Ltd. Device 8000 > >>> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- > >>> ParErr- Stepping- SERR- FastB2B- DisINTx+ > >>> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort+ > >>> <TAbort- <MAbort- >SERR- <PERR- INTx- > >>> Latency: 0, Cache Line Size: 64 bytes > >>> Interrupt: pin ? routed to IRQ 111 > >>> IOMMU group: 19 > >>> Region 0: Memory at dd800000 (64-bit, non-prefetchable) [size=2M] > >>> Capabilities: [40] Power Management version 3 > >>> Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA > >>> PME(D0+,D1-,D2-,D3hot+,D3cold+) > >>> Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- > >>> Capabilities: [50] MSI: Enable+ Count=16/32 Maskable+ 64bit- > >>> Address: fee00000 Data: 0000 > >>> Masking: ffff8000 Pending: 00000000 > >>> Capabilities: [70] Express (v2) Endpoint, IntMsgNum 0 > >>> DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s > >>> unlimited, L1 unlimited > >>> ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- > >>> SlotPowerLimit 75W TEE-IO- > >>> DevCtl: CorrErr+ NonFatalErr+ FatalErr+ UnsupReq+ > >>> RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ > >>> MaxPayload 128 bytes, MaxReadReq 512 bytes > >>> DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- > >>> AuxPwr+ TransPend- > >>> LnkCap: Port #0, Speed 8GT/s, Width x2, ASPM L0s L1, > >>> Exit Latency L0s <1us, L1 <64us > >>> ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+ > >>> LnkCtl: ASPM L1 Enabled; RCB 64 bytes, LnkDisable- CommClk+ > >>> ExtSynch+ ClockPM- AutWidDis- BWInt- AutBWInt- > >>> LnkSta: Speed 8GT/s, Width x1 (downgraded) > >>> TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- > >>> DevCap2: Completion Timeout: Range ABCD, TimeoutDis+ > >>> NROPrPrP- LTR+ > >>> 10BitTagComp- 10BitTagReq- OBFF Not Supported, > >>> ExtFmt- EETLPPrefix- > >>> EmergencyPowerReduction Not Supported, > >>> EmergencyPowerReductionInit- > >>> FRS- TPHComp+ ExtTPHComp- > >>> AtomicOpsCap: 32bit- 64bit- 128bitCAS- > >>> DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- > >>> AtomicOpsCtl: ReqEn- > >>> IDOReq- IDOCompl- LTR+ EmergencyPowerReductionReq- > >>> 10BitTagReq- OBFF Disabled, EETLPPrefixBlk- > >>> LnkCap2: Supported Link Speeds: 2.5-8GT/s, Crosslink- > >>> Retimer- 2Retimers- DRS- > >>> LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis- > >>> Transmit Margin: Normal Operating Range, > >>> EnterModifiedCompliance- ComplianceSOS- > >>> Compliance Preset/De-emphasis: -6dB > >>> de-emphasis, 0dB preshoot > >>> LnkSta2: Current De-emphasis Level: -3.5dB, > >>> EqualizationComplete+ EqualizationPhase1+ > >>> EqualizationPhase2+ EqualizationPhase3+ > >>> LinkEqualizationRequest- > >>> Retimer- 2Retimers- CrosslinkRes: unsupported > >>> Capabilities: [100 v2] Advanced Error Reporting > >>> UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- > >>> UnxCmplt- RxOF- MalfTLP- > >>> ECRC- UnsupReq- ACSViol- UncorrIntErr- > >>> BlockedTLP- AtomicOpBlocked- TLPBlockedErr- > >>> PoisonTLPBlocked- DMWrReqBlocked- IDECheck- > >>> MisIDETLP- PCRC_CHECK- TLPXlatBlocked- > >>> UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- > >>> UnxCmplt- RxOF- MalfTLP- > >>> ECRC- UnsupReq- ACSViol- UncorrIntErr+ > >>> BlockedTLP- AtomicOpBlocked- TLPBlockedErr- > >>> PoisonTLPBlocked- DMWrReqBlocked- IDECheck- > >>> MisIDETLP- PCRC_CHECK- TLPXlatBlocked- > >>> UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- > >>> UnxCmplt- RxOF+ MalfTLP+ > >>> ECRC- UnsupReq- ACSViol- UncorrIntErr+ > >>> BlockedTLP- AtomicOpBlocked- TLPBlockedErr- > >>> PoisonTLPBlocked- DMWrReqBlocked- IDECheck- > >>> MisIDETLP- PCRC_CHECK- TLPXlatBlocked- > >>> CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- > >>> AdvNonFatalErr- CorrIntErr- HeaderOF- > >>> CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- > >>> AdvNonFatalErr+ CorrIntErr+ HeaderOF+ > >>> AERCap: First Error Pointer: 00, ECRCGenCap+ ECRCGenEn- > >>> ECRCChkCap+ ECRCChkEn- > >>> MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap- > >>> HeaderLog: 00000000 00000000 00000000 00000000 > >>> Capabilities: [148 v1] Secondary PCI Express > >>> LnkCtl3: LnkEquIntrruptEn- PerformEqu- > >>> LaneErrStat: 0 > >>> Capabilities: [158 v1] Transaction Processing Hints > >>> No steering table available > >>> Capabilities: [1e4 v1] Latency Tolerance Reporting > >>> Max snoop latency: 1048576ns > >>> Max no snoop latency: 1048576ns > >>> Capabilities: [1ec v1] L1 PM Substates > >>> L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ > >>> ASPM_L1.1+ L1_PM_Substates+ > >>> PortCommonModeRestoreTime=70us PortTPowerOnTime=0us > >>> L1SubCtl1: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ > >>> T_CommonMode=0us LTR1.2_Threshold=166912ns > >>> L1SubCtl2: T_PwrOn=90us > >>> Kernel driver in use: ath12k_pci > >>> Kernel modules: ath12k > >>> > >>> root@walt-ROG-zephyrus:~# iw reg get > >>> global > >>> country US: DFS-FCC > >>> (902 - 904 @ 2), (N/A, 30), (N/A) > >>> (904 - 920 @ 16), (N/A, 30), (N/A) > >>> (920 - 928 @ 8), (N/A, 30), (N/A) > >>> (2400 - 2472 @ 40), (N/A, 30), (N/A) > >>> (5150 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW > >>> (5250 - 5350 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW > >>> (5470 - 5730 @ 160), (N/A, 24), (0 ms), DFS > >>> (5730 - 5850 @ 80), (N/A, 30), (N/A), AUTO-BW > >>> (5850 - 5895 @ 40), (N/A, 27), (N/A), NO-OUTDOOR, AUTO-BW, PASSIVE-SCAN > >>> (5925 - 7125 @ 320), (N/A, 12), (N/A), NO-OUTDOOR, PASSIVE-SCAN > >>> (57240 - 71000 @ 2160), (N/A, 40), (N/A) > >>> > >>> phy#0 (self-managed) > >>> country na: DFS-UNSET > >>> (2402 - 2472 @ 40), (N/A, 20), (N/A) > >>> (2457 - 2482 @ 20), (N/A, 20), (N/A), PASSIVE-SCAN > >>> (5170 - 5330 @ 160), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN > >>> (5490 - 5730 @ 160), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN > >>> (5735 - 5895 @ 160), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN > >>> (5945 - 7125 @ 320), (N/A, 30), (N/A), AUTO-BW, PASSIVE-SCAN > >>> > >> > >> I added the ath12k list to make sure this has the proper attention. > >> Since you are building from source, can you please test with the following patch: > >> https://msgid.link/20250401020840.357-1-quic_kangyang@quicinc.com > >> > >> This is in my pending queue. > >> > >> /jeff > >> > > > > Hi Jeff, > > > > No dice on the 6Ghz networks. It fixed up the registration info, but I > > still don't see any 6Ghz networks. Even from an 'iw wlp99s0 scan' > > > > global > > country US: DFS-FCC > > (902 - 904 @ 2), (N/A, 30), (N/A) > > (904 - 920 @ 16), (N/A, 30), (N/A) > > (920 - 928 @ 8), (N/A, 30), (N/A) > > (2400 - 2472 @ 40), (N/A, 30), (N/A) > > (5150 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW > > (5250 - 5350 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW > > (5470 - 5730 @ 160), (N/A, 24), (0 ms), DFS > > (5730 - 5850 @ 80), (N/A, 30), (N/A), AUTO-BW > > (5850 - 5895 @ 40), (N/A, 27), (N/A), NO-OUTDOOR, AUTO-BW, PASSIVE-SCAN > > (5925 - 7125 @ 320), (N/A, 12), (N/A), NO-OUTDOOR, PASSIVE-SCAN > > (57240 - 71000 @ 2160), (N/A, 40), (N/A) > > > > phy#0 (self-managed) > > country US: DFS-FCC > > (2402 - 2472 @ 40), (6, 30), (N/A) > > (5170 - 5250 @ 80), (6, 24), (N/A), AUTO-BW > > (5250 - 5330 @ 80), (6, 24), (0 ms), DFS, AUTO-BW > > (5490 - 5730 @ 160), (6, 24), (0 ms), DFS, AUTO-BW > > (5735 - 5855 @ 80), (6, 30), (N/A), AUTO-BW > > (5855 - 5925 @ 40), (6, 30), (N/A), NO-OUTDOOR, AUTO-BW > > (5925 - 7125 @ 320), (N/A, 30), (N/A), NO-OUTDOOR, AUTO-BW > > > > > > Test on 6.14.0-rc5-wt-ath+, with the firmware you used. > I can get 6 GHz AP and connect to it. > > ath12k_pci 0000:03:00.0: fw_version 0x100301e1 fw_build_timestamp > 2023-12-06 04:05 fw_build_id > QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3 > > yk@yk-Mayan:~$ sudo iw wls1 scan | tee iw_scan.log: > BSS 62:03:7f:12:64:64(on wls1) -- associated > TSF: 606308271476 usec (7d, 00:25:08) > freq: 6275 > beacon interval: 100 TUs > capability: ESS Privacy SpectrumMgmt ShortSlotTime (0x0511) > signal: -17.00 dBm > last seen: 52 ms ago > Information elements from Probe Response frame: > SSID: MLO-KANG-6G > and other 6 GHz APs: > SSID: 6G-gxia > SSID: NETGEAR97-6G > …… > > > kernel log: > [88158.033218] wls1: Inserted STA 62:03:7f:12:64:64 > [88158.033232] wls1: authenticate with 62:03:7f:12:64:64 (local > address=00:03:7f:37:12:54) > [88158.033242] wls1: send auth to 62:03:7f:12:64:64 (try 1/3) > [88158.041895] wls1: authenticated > [88158.041914] wls1: moving STA 62:03:7f:12:64:64 to state 2 > [88158.044291] wls1: determined local STA to be EHT, BW limited to 320 MHz > [88158.045719] wls1: associate with 62:03:7f:12:64:64 (try 1/3) > [88158.067045] wls1: RX AssocResp from 62:03:7f:12:64:64 (capab=0x511 > status=0 aid=4) > [88158.089090] wls1: associated > > I can even connect to it by Ubuntu GUI. > > Can you update to 6.14.0-rc5-wt-ath+ and have a retry? Also please make > sure that your wpa_supplicant/iw support 6 GHz(or directly update to the > latest version). > > If you still cannot find 6 GHz AP, you can set debug_mask to 0xffffffff > to get ath12k logs. Then give it to us. > > > > -Walt > > > OK, I retested with the wt-ath 033125 tagged build. This included the patch the Jeff suggested I try, but the rest of the tree was clean. Still no 6ghz Wifi. I'm attaching a log file of the boot and first few seconds with the debug mask turned on. I noticed that if I rmmod the module and then modprobe it, it complains about not finding firmware-2.bin, however, I thought that was only for the qcn based chip? The HW info from dmesg looks like this: [ 6.070282] ath12k_pci 0000:63:00.0: BAR 0 [mem 0xdd800000-0xdd9fffff 64bit]: assigned [ 6.070310] ath12k_pci 0000:63:00.0: enabling device (0000 -> 0002) [ 6.071249] ath12k_pci 0000:63:00.0: MSI vectors: 16 [ 6.071254] ath12k_pci 0000:63:00.0: Hardware name: wcn7850 hw2.0 [ 6.596331] ath12k_pci 0000:63:00.0: qmi dma allocation failed (7077888 B type 1), will try later with sma ll size [ 6.604041] ath12k_pci 0000:63:00.0: chip_id 0x2 chip_family 0x4 board_id 0xff soc_id 0x40170200 [ 6.604044] ath12k_pci 0000:63:00.0: fw_version 0x100301e1 fw_build_timestamp 2023-12-06 04:05 fw_build_id QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ- Also, I noticed when looking through the debug logs there are the occasional WARNING statements from a BUG it appears. They trace back to the mac.c file inside the ath12k code. There should be some in the debug log that's attached. Let me know if I can do anything else. Thanks, -Walt [-- Attachment #2: wt-ath-bootup.log.gz --] [-- Type: application/gzip, Size: 304896 bytes --] ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ath12k: No 6GHz Wireless found 2025-04-02 17:48 ` Walt Holman @ 2025-04-03 8:19 ` Kang Yang 2025-04-03 16:04 ` Walt Holman 0 siblings, 1 reply; 32+ messages in thread From: Kang Yang @ 2025-04-03 8:19 UTC (permalink / raw) To: Walt Holman; +Cc: Jeff Johnson, linux-wireless, ath12k@lists.infradead.org On 4/3/2025 1:48 AM, Walt Holman wrote: > On Tue, Apr 1, 2025 at 9:48 PM Kang Yang <quic_kangyang@quicinc.com> wrote: >> >> Test on 6.14.0-rc5-wt-ath+, with the firmware you used. >> I can get 6 GHz AP and connect to it. >> >> ath12k_pci 0000:03:00.0: fw_version 0x100301e1 fw_build_timestamp >> 2023-12-06 04:05 fw_build_id >> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3 >> >> yk@yk-Mayan:~$ sudo iw wls1 scan | tee iw_scan.log: >> BSS 62:03:7f:12:64:64(on wls1) -- associated >> TSF: 606308271476 usec (7d, 00:25:08) >> freq: 6275 >> beacon interval: 100 TUs >> capability: ESS Privacy SpectrumMgmt ShortSlotTime (0x0511) >> signal: -17.00 dBm >> last seen: 52 ms ago >> Information elements from Probe Response frame: >> SSID: MLO-KANG-6G >> and other 6 GHz APs: >> SSID: 6G-gxia >> SSID: NETGEAR97-6G >> …… >> >> >> kernel log: >> [88158.033218] wls1: Inserted STA 62:03:7f:12:64:64 >> [88158.033232] wls1: authenticate with 62:03:7f:12:64:64 (local >> address=00:03:7f:37:12:54) >> [88158.033242] wls1: send auth to 62:03:7f:12:64:64 (try 1/3) >> [88158.041895] wls1: authenticated >> [88158.041914] wls1: moving STA 62:03:7f:12:64:64 to state 2 >> [88158.044291] wls1: determined local STA to be EHT, BW limited to 320 MHz >> [88158.045719] wls1: associate with 62:03:7f:12:64:64 (try 1/3) >> [88158.067045] wls1: RX AssocResp from 62:03:7f:12:64:64 (capab=0x511 >> status=0 aid=4) >> [88158.089090] wls1: associated >> >> I can even connect to it by Ubuntu GUI. >> >> Can you update to 6.14.0-rc5-wt-ath+ and have a retry? Also please make >> sure that your wpa_supplicant/iw support 6 GHz(or directly update to the >> latest version). >> >> If you still cannot find 6 GHz AP, you can set debug_mask to 0xffffffff >> to get ath12k logs. Then give it to us. >> >> >>> -Walt >>> >> > > OK, I retested with the wt-ath 033125 tagged build. This included the > patch the Jeff suggested I try, but the rest of the tree was clean. > Still no 6ghz Wifi. I'm attaching a log file of the boot and first few > seconds with the debug mask turned on. I noticed that if I rmmod the > module and then modprobe it, it complains about not finding > firmware-2.bin, however, I thought that was only for the qcn based > chip? The HW info from dmesg looks like this: > I cannot find this tag... From the log, the 6 GHz channel should work. When scan is triggered, FW shall send probe req on these channels. If AP send probe resp, station shall find the AP. > [ 6.070282] ath12k_pci 0000:63:00.0: BAR 0 [mem > 0xdd800000-0xdd9fffff 64bit]: assigned > [ 6.070310] ath12k_pci 0000:63:00.0: enabling device (0000 -> 0002) > [ 6.071249] ath12k_pci 0000:63:00.0: MSI vectors: 16 > [ 6.071254] ath12k_pci 0000:63:00.0: Hardware name: wcn7850 hw2.0 > [ 6.596331] ath12k_pci 0000:63:00.0: qmi dma allocation failed > (7077888 B type 1), will try later with sma > ll size > [ 6.604041] ath12k_pci 0000:63:00.0: chip_id 0x2 chip_family 0x4 > board_id 0xff soc_id 0x40170200 > [ 6.604044] ath12k_pci 0000:63:00.0: fw_version 0x100301e1 > fw_build_timestamp 2023-12-06 04:05 fw_build_id > QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ- > > Also, I noticed when looking through the debug logs there are the > occasional WARNING statements from a BUG it appears. They trace back > to the mac.c file inside the ath12k code. There should be some in the > debug log that's attached. Let me know if I can do anything else. > Thanks, > I have never seen this warning on my upstream setup...Not sure if you have changed anything or using the correct code base. Jeff merged this patch-set into ath-202504021602. Can you try on this branch? git clone https://git.kernel.org/pub/scm/linux/kernel/git/ath/ath.git/ git pull git reset --hard ath-202504021602 compile and install... Also make sure that the firmware you used is from the same folder, don't mix with other folders: linux-firmware/ath12k/WCN7850/hw2.0 1. rmmod/insmod(debug_mask=0xffff) 2. iw reg get 3. iw reg set US 4. iw xxx scan wait and collect logs. don't do anything else. Also, can you show me your AP configuration. If you have another 6 GHz AP, you can have a try(better different brands). If you have sniffer, could please capture packets during testing? Thanks! > -Walt ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ath12k: No 6GHz Wireless found 2025-04-03 8:19 ` Kang Yang @ 2025-04-03 16:04 ` Walt Holman 2025-04-07 1:57 ` Kang Yang 0 siblings, 1 reply; 32+ messages in thread From: Walt Holman @ 2025-04-03 16:04 UTC (permalink / raw) To: Kang Yang; +Cc: Jeff Johnson, linux-wireless, ath12k@lists.infradead.org [-- Attachment #1: Type: text/plain, Size: 5493 bytes --] On Thu, Apr 3, 2025 at 3:20 AM Kang Yang <quic_kangyang@quicinc.com> wrote: > > > > On 4/3/2025 1:48 AM, Walt Holman wrote: > > On Tue, Apr 1, 2025 at 9:48 PM Kang Yang <quic_kangyang@quicinc.com> wrote: > > >> > >> Test on 6.14.0-rc5-wt-ath+, with the firmware you used. > >> I can get 6 GHz AP and connect to it. > >> > >> ath12k_pci 0000:03:00.0: fw_version 0x100301e1 fw_build_timestamp > >> 2023-12-06 04:05 fw_build_id > >> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3 > >> > >> yk@yk-Mayan:~$ sudo iw wls1 scan | tee iw_scan.log: > >> BSS 62:03:7f:12:64:64(on wls1) -- associated > >> TSF: 606308271476 usec (7d, 00:25:08) > >> freq: 6275 > >> beacon interval: 100 TUs > >> capability: ESS Privacy SpectrumMgmt ShortSlotTime (0x0511) > >> signal: -17.00 dBm > >> last seen: 52 ms ago > >> Information elements from Probe Response frame: > >> SSID: MLO-KANG-6G > >> and other 6 GHz APs: > >> SSID: 6G-gxia > >> SSID: NETGEAR97-6G > >> …… > >> > >> > >> kernel log: > >> [88158.033218] wls1: Inserted STA 62:03:7f:12:64:64 > >> [88158.033232] wls1: authenticate with 62:03:7f:12:64:64 (local > >> address=00:03:7f:37:12:54) > >> [88158.033242] wls1: send auth to 62:03:7f:12:64:64 (try 1/3) > >> [88158.041895] wls1: authenticated > >> [88158.041914] wls1: moving STA 62:03:7f:12:64:64 to state 2 > >> [88158.044291] wls1: determined local STA to be EHT, BW limited to 320 MHz > >> [88158.045719] wls1: associate with 62:03:7f:12:64:64 (try 1/3) > >> [88158.067045] wls1: RX AssocResp from 62:03:7f:12:64:64 (capab=0x511 > >> status=0 aid=4) > >> [88158.089090] wls1: associated > >> > >> I can even connect to it by Ubuntu GUI. > >> > >> Can you update to 6.14.0-rc5-wt-ath+ and have a retry? Also please make > >> sure that your wpa_supplicant/iw support 6 GHz(or directly update to the > >> latest version). > >> > >> If you still cannot find 6 GHz AP, you can set debug_mask to 0xffffffff > >> to get ath12k logs. Then give it to us. > >> > >> > >>> -Walt > >>> > >> > > > > OK, I retested with the wt-ath 033125 tagged build. This included the > > patch the Jeff suggested I try, but the rest of the tree was clean. > > Still no 6ghz Wifi. I'm attaching a log file of the boot and first few > > seconds with the debug mask turned on. I noticed that if I rmmod the > > module and then modprobe it, it complains about not finding > > firmware-2.bin, however, I thought that was only for the qcn based > > chip? The HW info from dmesg looks like this: > > > > I cannot find this tag... > > > From the log, the 6 GHz channel should work. When scan is triggered, FW > shall send probe req on these channels. If AP send probe resp, station > shall find the AP. > > > > > > [ 6.070282] ath12k_pci 0000:63:00.0: BAR 0 [mem > > 0xdd800000-0xdd9fffff 64bit]: assigned > > [ 6.070310] ath12k_pci 0000:63:00.0: enabling device (0000 -> 0002) > > [ 6.071249] ath12k_pci 0000:63:00.0: MSI vectors: 16 > > [ 6.071254] ath12k_pci 0000:63:00.0: Hardware name: wcn7850 hw2.0 > > [ 6.596331] ath12k_pci 0000:63:00.0: qmi dma allocation failed > > (7077888 B type 1), will try later with sma > > ll size > > [ 6.604041] ath12k_pci 0000:63:00.0: chip_id 0x2 chip_family 0x4 > > board_id 0xff soc_id 0x40170200 > > [ 6.604044] ath12k_pci 0000:63:00.0: fw_version 0x100301e1 > > fw_build_timestamp 2023-12-06 04:05 fw_build_id > > QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ- > > > > Also, I noticed when looking through the debug logs there are the > > occasional WARNING statements from a BUG it appears. They trace back > > to the mac.c file inside the ath12k code. There should be some in the > > debug log that's attached. Let me know if I can do anything else. > > Thanks, > > > > > I have never seen this warning on my upstream setup...Not sure if you > have changed anything or using the correct code base. > > Jeff merged this patch-set into ath-202504021602. Can you try on this > branch? > > git clone https://git.kernel.org/pub/scm/linux/kernel/git/ath/ath.git/ > git pull > git reset --hard ath-202504021602 > compile and install... > > Also make sure that the firmware you used is from the same folder, don't > mix with other folders: > linux-firmware/ath12k/WCN7850/hw2.0 > > 1. rmmod/insmod(debug_mask=0xffff) > 2. iw reg get > 3. iw reg set US > 4. iw xxx scan > wait and collect logs. > > don't do anything else. > > > Also, can you show me your AP configuration. > If you have another 6 GHz AP, you can have a try(better different brands). > > > If you have sniffer, could please capture packets during testing? > > Thanks! > > > -Walt > OK, I cloned and built the kernel based on your instructions in your last email. Originally, the result was identical to my last email, including the WARNINGS. The .config I use is configured for a fully RT PREEMPT kernel, which I wondered if that was why I was receiving the WARNING. So I configured it as a Low Latency PREEMPT Desktop without the RT_PREEMPT and that eliminated the WARNING. However, still no 6Ghz networks. The firmware I'm using is straight from kernel.org GIT and I do a 'make install; make dedup' to install it. I believe it should be good. Attached is the latest log file. -Walt [-- Attachment #2: wt-ath-bootup.log.gz --] [-- Type: application/gzip, Size: 104313 bytes --] ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ath12k: No 6GHz Wireless found 2025-04-03 16:04 ` Walt Holman @ 2025-04-07 1:57 ` Kang Yang 2025-04-07 17:49 ` Walt Holman 0 siblings, 1 reply; 32+ messages in thread From: Kang Yang @ 2025-04-07 1:57 UTC (permalink / raw) To: Walt Holman; +Cc: Jeff Johnson, linux-wireless, ath12k@lists.infradead.org On 4/4/2025 12:04 AM, Walt Holman wrote: > On Thu, Apr 3, 2025 at 3:20 AM Kang Yang <quic_kangyang@quicinc.com> wrote: >> >> >> >> On 4/3/2025 1:48 AM, Walt Holman wrote: >>> On Tue, Apr 1, 2025 at 9:48 PM Kang Yang <quic_kangyang@quicinc.com> wrote: >> >>>> >>>> Test on 6.14.0-rc5-wt-ath+, with the firmware you used. >>>> I can get 6 GHz AP and connect to it. >>>> >>>> ath12k_pci 0000:03:00.0: fw_version 0x100301e1 fw_build_timestamp >>>> 2023-12-06 04:05 fw_build_id >>>> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3 >>>> >>>> yk@yk-Mayan:~$ sudo iw wls1 scan | tee iw_scan.log: >>>> BSS 62:03:7f:12:64:64(on wls1) -- associated >>>> TSF: 606308271476 usec (7d, 00:25:08) >>>> freq: 6275 >>>> beacon interval: 100 TUs >>>> capability: ESS Privacy SpectrumMgmt ShortSlotTime (0x0511) >>>> signal: -17.00 dBm >>>> last seen: 52 ms ago >>>> Information elements from Probe Response frame: >>>> SSID: MLO-KANG-6G >>>> and other 6 GHz APs: >>>> SSID: 6G-gxia >>>> SSID: NETGEAR97-6G >>>> …… >>>> >>>> >>>> kernel log: >>>> [88158.033218] wls1: Inserted STA 62:03:7f:12:64:64 >>>> [88158.033232] wls1: authenticate with 62:03:7f:12:64:64 (local >>>> address=00:03:7f:37:12:54) >>>> [88158.033242] wls1: send auth to 62:03:7f:12:64:64 (try 1/3) >>>> [88158.041895] wls1: authenticated >>>> [88158.041914] wls1: moving STA 62:03:7f:12:64:64 to state 2 >>>> [88158.044291] wls1: determined local STA to be EHT, BW limited to 320 MHz >>>> [88158.045719] wls1: associate with 62:03:7f:12:64:64 (try 1/3) >>>> [88158.067045] wls1: RX AssocResp from 62:03:7f:12:64:64 (capab=0x511 >>>> status=0 aid=4) >>>> [88158.089090] wls1: associated >>>> >>>> I can even connect to it by Ubuntu GUI. >>>> >>>> Can you update to 6.14.0-rc5-wt-ath+ and have a retry? Also please make >>>> sure that your wpa_supplicant/iw support 6 GHz(or directly update to the >>>> latest version). >>>> >>>> If you still cannot find 6 GHz AP, you can set debug_mask to 0xffffffff >>>> to get ath12k logs. Then give it to us. >>>> >>>> >>>>> -Walt >>>>> >>>> >>> >>> OK, I retested with the wt-ath 033125 tagged build. This included the >>> patch the Jeff suggested I try, but the rest of the tree was clean. >>> Still no 6ghz Wifi. I'm attaching a log file of the boot and first few >>> seconds with the debug mask turned on. I noticed that if I rmmod the >>> module and then modprobe it, it complains about not finding >>> firmware-2.bin, however, I thought that was only for the qcn based >>> chip? The HW info from dmesg looks like this: >>> >> >> I cannot find this tag... >> >> >> From the log, the 6 GHz channel should work. When scan is triggered, FW >> shall send probe req on these channels. If AP send probe resp, station >> shall find the AP. >> >> >> >> >>> [ 6.070282] ath12k_pci 0000:63:00.0: BAR 0 [mem >>> 0xdd800000-0xdd9fffff 64bit]: assigned >>> [ 6.070310] ath12k_pci 0000:63:00.0: enabling device (0000 -> 0002) >>> [ 6.071249] ath12k_pci 0000:63:00.0: MSI vectors: 16 >>> [ 6.071254] ath12k_pci 0000:63:00.0: Hardware name: wcn7850 hw2.0 >>> [ 6.596331] ath12k_pci 0000:63:00.0: qmi dma allocation failed >>> (7077888 B type 1), will try later with sma >>> ll size >>> [ 6.604041] ath12k_pci 0000:63:00.0: chip_id 0x2 chip_family 0x4 >>> board_id 0xff soc_id 0x40170200 >>> [ 6.604044] ath12k_pci 0000:63:00.0: fw_version 0x100301e1 >>> fw_build_timestamp 2023-12-06 04:05 fw_build_id >>> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ- >>> >>> Also, I noticed when looking through the debug logs there are the >>> occasional WARNING statements from a BUG it appears. They trace back >>> to the mac.c file inside the ath12k code. There should be some in the >>> debug log that's attached. Let me know if I can do anything else. >>> Thanks, >>> >> >> >> I have never seen this warning on my upstream setup...Not sure if you >> have changed anything or using the correct code base. >> >> Jeff merged this patch-set into ath-202504021602. Can you try on this >> branch? >> >> git clone https://git.kernel.org/pub/scm/linux/kernel/git/ath/ath.git/ >> git pull >> git reset --hard ath-202504021602 >> compile and install... >> >> Also make sure that the firmware you used is from the same folder, don't >> mix with other folders: >> linux-firmware/ath12k/WCN7850/hw2.0 >> >> 1. rmmod/insmod(debug_mask=0xffff) >> 2. iw reg get >> 3. iw reg set US >> 4. iw xxx scan >> wait and collect logs. >> >> don't do anything else. >> >> >> Also, can you show me your AP configuration. >> If you have another 6 GHz AP, you can have a try(better different brands). >> Thanks for testing. Could you share your AP configuration? >> >> If you have sniffer, could please capture packets during testing? Can you capture packets during the testing? I need to check probe req and probe resp. >> >> Thanks! >> >>> -Walt >> > OK, I cloned and built the kernel based on your instructions in your > last email. Originally, the result was identical to my last email, > including the WARNINGS. The .config I use is configured for a fully RT > PREEMPT kernel, which I wondered if that was why I was receiving the > WARNING. So I configured it as a Low Latency PREEMPT Desktop without > the RT_PREEMPT and that eliminated the WARNING. However, still no 6Ghz > networks. The firmware I'm using is straight from kernel.org GIT and I > do a 'make install; make dedup' to install it. I believe it should be > good. Attached is the latest log file. > > -Walt ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ath12k: No 6GHz Wireless found 2025-04-07 1:57 ` Kang Yang @ 2025-04-07 17:49 ` Walt Holman 2025-04-08 9:16 ` Kang Yang 0 siblings, 1 reply; 32+ messages in thread From: Walt Holman @ 2025-04-07 17:49 UTC (permalink / raw) To: Kang Yang; +Cc: Jeff Johnson, linux-wireless, ath12k@lists.infradead.org [-- Attachment #1: Type: text/plain, Size: 6866 bytes --] Attached is a small packet capture where I did an 'iw wlp99s0 scan' and also deactivated and reactivated wireless while the scan was ongoing. Hopefully there's something interesting for you in there. Also, I've take 3 screenshots showing the configs of the wireless AP for the 6ghz network. The first screen is just the definition of the network. No advanced settings are used. The 2nd screen shows the channels and radio enabled. The 3rd screen has the advanced (professional) settings for the network. I believe I changed 'Agile Multiband' to enabled, but other settings are their defaults. Hope some of this helps. Let me know if you need anything else. Thanks, -Walt On Sun, Apr 6, 2025 at 8:58 PM Kang Yang <quic_kangyang@quicinc.com> wrote: > > > > On 4/4/2025 12:04 AM, Walt Holman wrote: > > On Thu, Apr 3, 2025 at 3:20 AM Kang Yang <quic_kangyang@quicinc.com> wrote: > >> > >> > >> > >> On 4/3/2025 1:48 AM, Walt Holman wrote: > >>> On Tue, Apr 1, 2025 at 9:48 PM Kang Yang <quic_kangyang@quicinc.com> wrote: > >> > >>>> > >>>> Test on 6.14.0-rc5-wt-ath+, with the firmware you used. > >>>> I can get 6 GHz AP and connect to it. > >>>> > >>>> ath12k_pci 0000:03:00.0: fw_version 0x100301e1 fw_build_timestamp > >>>> 2023-12-06 04:05 fw_build_id > >>>> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3 > >>>> > >>>> yk@yk-Mayan:~$ sudo iw wls1 scan | tee iw_scan.log: > >>>> BSS 62:03:7f:12:64:64(on wls1) -- associated > >>>> TSF: 606308271476 usec (7d, 00:25:08) > >>>> freq: 6275 > >>>> beacon interval: 100 TUs > >>>> capability: ESS Privacy SpectrumMgmt ShortSlotTime (0x0511) > >>>> signal: -17.00 dBm > >>>> last seen: 52 ms ago > >>>> Information elements from Probe Response frame: > >>>> SSID: MLO-KANG-6G > >>>> and other 6 GHz APs: > >>>> SSID: 6G-gxia > >>>> SSID: NETGEAR97-6G > >>>> …… > >>>> > >>>> > >>>> kernel log: > >>>> [88158.033218] wls1: Inserted STA 62:03:7f:12:64:64 > >>>> [88158.033232] wls1: authenticate with 62:03:7f:12:64:64 (local > >>>> address=00:03:7f:37:12:54) > >>>> [88158.033242] wls1: send auth to 62:03:7f:12:64:64 (try 1/3) > >>>> [88158.041895] wls1: authenticated > >>>> [88158.041914] wls1: moving STA 62:03:7f:12:64:64 to state 2 > >>>> [88158.044291] wls1: determined local STA to be EHT, BW limited to 320 MHz > >>>> [88158.045719] wls1: associate with 62:03:7f:12:64:64 (try 1/3) > >>>> [88158.067045] wls1: RX AssocResp from 62:03:7f:12:64:64 (capab=0x511 > >>>> status=0 aid=4) > >>>> [88158.089090] wls1: associated > >>>> > >>>> I can even connect to it by Ubuntu GUI. > >>>> > >>>> Can you update to 6.14.0-rc5-wt-ath+ and have a retry? Also please make > >>>> sure that your wpa_supplicant/iw support 6 GHz(or directly update to the > >>>> latest version). > >>>> > >>>> If you still cannot find 6 GHz AP, you can set debug_mask to 0xffffffff > >>>> to get ath12k logs. Then give it to us. > >>>> > >>>> > >>>>> -Walt > >>>>> > >>>> > >>> > >>> OK, I retested with the wt-ath 033125 tagged build. This included the > >>> patch the Jeff suggested I try, but the rest of the tree was clean. > >>> Still no 6ghz Wifi. I'm attaching a log file of the boot and first few > >>> seconds with the debug mask turned on. I noticed that if I rmmod the > >>> module and then modprobe it, it complains about not finding > >>> firmware-2.bin, however, I thought that was only for the qcn based > >>> chip? The HW info from dmesg looks like this: > >>> > >> > >> I cannot find this tag... > >> > >> > >> From the log, the 6 GHz channel should work. When scan is triggered, FW > >> shall send probe req on these channels. If AP send probe resp, station > >> shall find the AP. > >> > >> > >> > >> > >>> [ 6.070282] ath12k_pci 0000:63:00.0: BAR 0 [mem > >>> 0xdd800000-0xdd9fffff 64bit]: assigned > >>> [ 6.070310] ath12k_pci 0000:63:00.0: enabling device (0000 -> 0002) > >>> [ 6.071249] ath12k_pci 0000:63:00.0: MSI vectors: 16 > >>> [ 6.071254] ath12k_pci 0000:63:00.0: Hardware name: wcn7850 hw2.0 > >>> [ 6.596331] ath12k_pci 0000:63:00.0: qmi dma allocation failed > >>> (7077888 B type 1), will try later with sma > >>> ll size > >>> [ 6.604041] ath12k_pci 0000:63:00.0: chip_id 0x2 chip_family 0x4 > >>> board_id 0xff soc_id 0x40170200 > >>> [ 6.604044] ath12k_pci 0000:63:00.0: fw_version 0x100301e1 > >>> fw_build_timestamp 2023-12-06 04:05 fw_build_id > >>> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ- > >>> > >>> Also, I noticed when looking through the debug logs there are the > >>> occasional WARNING statements from a BUG it appears. They trace back > >>> to the mac.c file inside the ath12k code. There should be some in the > >>> debug log that's attached. Let me know if I can do anything else. > >>> Thanks, > >>> > >> > >> > >> I have never seen this warning on my upstream setup...Not sure if you > >> have changed anything or using the correct code base. > >> > >> Jeff merged this patch-set into ath-202504021602. Can you try on this > >> branch? > >> > >> git clone https://git.kernel.org/pub/scm/linux/kernel/git/ath/ath.git/ > >> git pull > >> git reset --hard ath-202504021602 > >> compile and install... > >> > >> Also make sure that the firmware you used is from the same folder, don't > >> mix with other folders: > >> linux-firmware/ath12k/WCN7850/hw2.0 > >> > >> 1. rmmod/insmod(debug_mask=0xffff) > >> 2. iw reg get > >> 3. iw reg set US > >> 4. iw xxx scan > >> wait and collect logs. > >> > >> don't do anything else. > >> > >> > >> Also, can you show me your AP configuration. > >> If you have another 6 GHz AP, you can have a try(better different brands). > >> > > Thanks for testing. > > Could you share your AP configuration? > > > >> > >> If you have sniffer, could please capture packets during testing? > > > Can you capture packets during the testing? I need to check probe req > and probe resp. > > >> > >> Thanks! > >> > >>> -Walt > >> > > OK, I cloned and built the kernel based on your instructions in your > > last email. Originally, the result was identical to my last email, > > including the WARNINGS. The .config I use is configured for a fully RT > > PREEMPT kernel, which I wondered if that was why I was receiving the > > WARNING. So I configured it as a Low Latency PREEMPT Desktop without > > the RT_PREEMPT and that eliminated the WARNING. However, still no 6Ghz > > networks. The firmware I'm using is straight from kernel.org GIT and I > > do a 'make install; make dedup' to install it. I believe it should be > > good. Attached is the latest log file. > > > > -Walt > [-- Attachment #2: packet-capture-20250407.pcapng.gz --] [-- Type: application/gzip, Size: 21626 bytes --] [-- Attachment #3: wifi-screen3.png --] [-- Type: image/png, Size: 431446 bytes --] [-- Attachment #4: wifi-screen2.png --] [-- Type: image/png, Size: 439271 bytes --] [-- Attachment #5: wifi-screen1.png --] [-- Type: image/png, Size: 421902 bytes --] ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ath12k: No 6GHz Wireless found 2025-04-07 17:49 ` Walt Holman @ 2025-04-08 9:16 ` Kang Yang 2025-04-09 19:37 ` Walt Holman 0 siblings, 1 reply; 32+ messages in thread From: Kang Yang @ 2025-04-08 9:16 UTC (permalink / raw) To: Walt Holman; +Cc: Jeff Johnson, linux-wireless, ath12k@lists.infradead.org On 4/8/2025 1:49 AM, Walt Holman wrote: > Attached is a small packet capture where I did an 'iw wlp99s0 scan' > and also deactivated and reactivated wireless while the scan was > ongoing. Hopefully there's something interesting for you in there. > Also, I've take 3 screenshots showing the configs of the wireless AP > for the 6ghz network. The first screen is just the definition of the > network. No advanced settings are used. The 2nd screen shows the > channels and radio enabled. The 3rd screen has the advanced > (professional) settings for the network. I believe I changed 'Agile > Multiband' to enabled, but other settings are their defaults. Hope > some of this helps. Let me know if you need anything else. Thanks, > Your packets are Ethernet packets. I need wireless packets. Not sure if you know how to add a seperate monitor interface to capture 6 G channels' packet on your AP(you can google for specific command). Also, please capture firmware log: 1. sudo apt install trace-cmd 2. sudo trace-cmd record -e ath12k_wmi_diag 3. run test 4. "ctrl c" to stop recording: Hit Ctrl^C to stop recording ^CCPU0 data recorded at offset=0xdf5000 2605056 bytes in size Then share the trace.dat to us. So you need to: 1. try to capture wireless packets. 2. capture firmware log(trade.data). 3. save kernel/wpa_supplicant/iw logs. > -Walt > > On Sun, Apr 6, 2025 at 8:58 PM Kang Yang <quic_kangyang@quicinc.com> wrote: >> >> >> >> On 4/4/2025 12:04 AM, Walt Holman wrote: >>> On Thu, Apr 3, 2025 at 3:20 AM Kang Yang <quic_kangyang@quicinc.com> wrote: >>>> >>>> >>>> >>>> On 4/3/2025 1:48 AM, Walt Holman wrote: >>>>> On Tue, Apr 1, 2025 at 9:48 PM Kang Yang <quic_kangyang@quicinc.com> wrote: >>>> >>>>>> >>>>>> Test on 6.14.0-rc5-wt-ath+, with the firmware you used. >>>>>> I can get 6 GHz AP and connect to it. >>>>>> >>>>>> ath12k_pci 0000:03:00.0: fw_version 0x100301e1 fw_build_timestamp >>>>>> 2023-12-06 04:05 fw_build_id >>>>>> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3 >>>>>> >>>>>> yk@yk-Mayan:~$ sudo iw wls1 scan | tee iw_scan.log: >>>>>> BSS 62:03:7f:12:64:64(on wls1) -- associated >>>>>> TSF: 606308271476 usec (7d, 00:25:08) >>>>>> freq: 6275 >>>>>> beacon interval: 100 TUs >>>>>> capability: ESS Privacy SpectrumMgmt ShortSlotTime (0x0511) >>>>>> signal: -17.00 dBm >>>>>> last seen: 52 ms ago >>>>>> Information elements from Probe Response frame: >>>>>> SSID: MLO-KANG-6G >>>>>> and other 6 GHz APs: >>>>>> SSID: 6G-gxia >>>>>> SSID: NETGEAR97-6G >>>>>> …… >>>>>> >>>>>> >>>>>> kernel log: >>>>>> [88158.033218] wls1: Inserted STA 62:03:7f:12:64:64 >>>>>> [88158.033232] wls1: authenticate with 62:03:7f:12:64:64 (local >>>>>> address=00:03:7f:37:12:54) >>>>>> [88158.033242] wls1: send auth to 62:03:7f:12:64:64 (try 1/3) >>>>>> [88158.041895] wls1: authenticated >>>>>> [88158.041914] wls1: moving STA 62:03:7f:12:64:64 to state 2 >>>>>> [88158.044291] wls1: determined local STA to be EHT, BW limited to 320 MHz >>>>>> [88158.045719] wls1: associate with 62:03:7f:12:64:64 (try 1/3) >>>>>> [88158.067045] wls1: RX AssocResp from 62:03:7f:12:64:64 (capab=0x511 >>>>>> status=0 aid=4) >>>>>> [88158.089090] wls1: associated >>>>>> >>>>>> I can even connect to it by Ubuntu GUI. >>>>>> >>>>>> Can you update to 6.14.0-rc5-wt-ath+ and have a retry? Also please make >>>>>> sure that your wpa_supplicant/iw support 6 GHz(or directly update to the >>>>>> latest version). >>>>>> >>>>>> If you still cannot find 6 GHz AP, you can set debug_mask to 0xffffffff >>>>>> to get ath12k logs. Then give it to us. >>>>>> >>>>>> >>>>>>> -Walt >>>>>>> >>>>>> >>>>> >>>>> OK, I retested with the wt-ath 033125 tagged build. This included the >>>>> patch the Jeff suggested I try, but the rest of the tree was clean. >>>>> Still no 6ghz Wifi. I'm attaching a log file of the boot and first few >>>>> seconds with the debug mask turned on. I noticed that if I rmmod the >>>>> module and then modprobe it, it complains about not finding >>>>> firmware-2.bin, however, I thought that was only for the qcn based >>>>> chip? The HW info from dmesg looks like this: >>>>> >>>> >>>> I cannot find this tag... >>>> >>>> >>>> From the log, the 6 GHz channel should work. When scan is triggered, FW >>>> shall send probe req on these channels. If AP send probe resp, station >>>> shall find the AP. >>>> >>>> >>>> >>>> >>>>> [ 6.070282] ath12k_pci 0000:63:00.0: BAR 0 [mem >>>>> 0xdd800000-0xdd9fffff 64bit]: assigned >>>>> [ 6.070310] ath12k_pci 0000:63:00.0: enabling device (0000 -> 0002) >>>>> [ 6.071249] ath12k_pci 0000:63:00.0: MSI vectors: 16 >>>>> [ 6.071254] ath12k_pci 0000:63:00.0: Hardware name: wcn7850 hw2.0 >>>>> [ 6.596331] ath12k_pci 0000:63:00.0: qmi dma allocation failed >>>>> (7077888 B type 1), will try later with sma >>>>> ll size >>>>> [ 6.604041] ath12k_pci 0000:63:00.0: chip_id 0x2 chip_family 0x4 >>>>> board_id 0xff soc_id 0x40170200 >>>>> [ 6.604044] ath12k_pci 0000:63:00.0: fw_version 0x100301e1 >>>>> fw_build_timestamp 2023-12-06 04:05 fw_build_id >>>>> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ- >>>>> >>>>> Also, I noticed when looking through the debug logs there are the >>>>> occasional WARNING statements from a BUG it appears. They trace back >>>>> to the mac.c file inside the ath12k code. There should be some in the >>>>> debug log that's attached. Let me know if I can do anything else. >>>>> Thanks, >>>>> >>>> >>>> >>>> I have never seen this warning on my upstream setup...Not sure if you >>>> have changed anything or using the correct code base. >>>> >>>> Jeff merged this patch-set into ath-202504021602. Can you try on this >>>> branch? >>>> >>>> git clone https://git.kernel.org/pub/scm/linux/kernel/git/ath/ath.git/ >>>> git pull >>>> git reset --hard ath-202504021602 >>>> compile and install... >>>> >>>> Also make sure that the firmware you used is from the same folder, don't >>>> mix with other folders: >>>> linux-firmware/ath12k/WCN7850/hw2.0 >>>> >>>> 1. rmmod/insmod(debug_mask=0xffff) >>>> 2. iw reg get >>>> 3. iw reg set US >>>> 4. iw xxx scan >>>> wait and collect logs. >>>> >>>> don't do anything else. >>>> >>>> >>>> Also, can you show me your AP configuration. >>>> If you have another 6 GHz AP, you can have a try(better different brands). >>>> >> >> Thanks for testing. >> >> Could you share your AP configuration? >> >> >>>> >>>> If you have sniffer, could please capture packets during testing? >> >> >> Can you capture packets during the testing? I need to check probe req >> and probe resp. >> >>>> >>>> Thanks! >>>> >>>>> -Walt >>>> >>> OK, I cloned and built the kernel based on your instructions in your >>> last email. Originally, the result was identical to my last email, >>> including the WARNINGS. The .config I use is configured for a fully RT >>> PREEMPT kernel, which I wondered if that was why I was receiving the >>> WARNING. So I configured it as a Low Latency PREEMPT Desktop without >>> the RT_PREEMPT and that eliminated the WARNING. However, still no 6Ghz >>> networks. The firmware I'm using is straight from kernel.org GIT and I >>> do a 'make install; make dedup' to install it. I believe it should be >>> good. Attached is the latest log file. >>> >>> -Walt >> ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ath12k: No 6GHz Wireless found 2025-04-08 9:16 ` Kang Yang @ 2025-04-09 19:37 ` Walt Holman 2025-04-10 8:26 ` Kang Yang 0 siblings, 1 reply; 32+ messages in thread From: Walt Holman @ 2025-04-09 19:37 UTC (permalink / raw) To: Kang Yang; +Cc: Jeff Johnson, linux-wireless, ath12k@lists.infradead.org [-- Attachment #1: Type: text/plain, Size: 8419 bytes --] On Tue, Apr 8, 2025 at 4:17 AM Kang Yang <quic_kangyang@quicinc.com> wrote: > > > > On 4/8/2025 1:49 AM, Walt Holman wrote: > > Attached is a small packet capture where I did an 'iw wlp99s0 scan' > > and also deactivated and reactivated wireless while the scan was > > ongoing. Hopefully there's something interesting for you in there. > > Also, I've take 3 screenshots showing the configs of the wireless AP > > for the 6ghz network. The first screen is just the definition of the > > network. No advanced settings are used. The 2nd screen shows the > > channels and radio enabled. The 3rd screen has the advanced > > (professional) settings for the network. I believe I changed 'Agile > > Multiband' to enabled, but other settings are their defaults. Hope > > some of this helps. Let me know if you need anything else. Thanks, > > > > Your packets are Ethernet packets. I need wireless packets. > > > Not sure if you know how to add a seperate monitor interface to capture > 6 G channels' packet on your AP(you can google for specific command). > > > Also, please capture firmware log: > > 1. sudo apt install trace-cmd > 2. sudo trace-cmd record -e ath12k_wmi_diag > 3. run test > 4. "ctrl c" to stop recording: > Hit Ctrl^C to stop recording > ^CCPU0 data recorded at offset=0xdf5000 > 2605056 bytes in size > Then share the trace.dat to us. > > So you need to: > 1. try to capture wireless packets. > 2. capture firmware log(trade.data). > 3. save kernel/wpa_supplicant/iw logs. > > > > > > > -Walt > > > > On Sun, Apr 6, 2025 at 8:58 PM Kang Yang <quic_kangyang@quicinc.com> wrote: > >> > >> > >> > >> On 4/4/2025 12:04 AM, Walt Holman wrote: > >>> On Thu, Apr 3, 2025 at 3:20 AM Kang Yang <quic_kangyang@quicinc.com> wrote: > >>>> > >>>> > >>>> > >>>> On 4/3/2025 1:48 AM, Walt Holman wrote: > >>>>> On Tue, Apr 1, 2025 at 9:48 PM Kang Yang <quic_kangyang@quicinc.com> wrote: > >>>> > >>>>>> > >>>>>> Test on 6.14.0-rc5-wt-ath+, with the firmware you used. > >>>>>> I can get 6 GHz AP and connect to it. > >>>>>> > >>>>>> ath12k_pci 0000:03:00.0: fw_version 0x100301e1 fw_build_timestamp > >>>>>> 2023-12-06 04:05 fw_build_id > >>>>>> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3 > >>>>>> > >>>>>> yk@yk-Mayan:~$ sudo iw wls1 scan | tee iw_scan.log: > >>>>>> BSS 62:03:7f:12:64:64(on wls1) -- associated > >>>>>> TSF: 606308271476 usec (7d, 00:25:08) > >>>>>> freq: 6275 > >>>>>> beacon interval: 100 TUs > >>>>>> capability: ESS Privacy SpectrumMgmt ShortSlotTime (0x0511) > >>>>>> signal: -17.00 dBm > >>>>>> last seen: 52 ms ago > >>>>>> Information elements from Probe Response frame: > >>>>>> SSID: MLO-KANG-6G > >>>>>> and other 6 GHz APs: > >>>>>> SSID: 6G-gxia > >>>>>> SSID: NETGEAR97-6G > >>>>>> …… > >>>>>> > >>>>>> > >>>>>> kernel log: > >>>>>> [88158.033218] wls1: Inserted STA 62:03:7f:12:64:64 > >>>>>> [88158.033232] wls1: authenticate with 62:03:7f:12:64:64 (local > >>>>>> address=00:03:7f:37:12:54) > >>>>>> [88158.033242] wls1: send auth to 62:03:7f:12:64:64 (try 1/3) > >>>>>> [88158.041895] wls1: authenticated > >>>>>> [88158.041914] wls1: moving STA 62:03:7f:12:64:64 to state 2 > >>>>>> [88158.044291] wls1: determined local STA to be EHT, BW limited to 320 MHz > >>>>>> [88158.045719] wls1: associate with 62:03:7f:12:64:64 (try 1/3) > >>>>>> [88158.067045] wls1: RX AssocResp from 62:03:7f:12:64:64 (capab=0x511 > >>>>>> status=0 aid=4) > >>>>>> [88158.089090] wls1: associated > >>>>>> > >>>>>> I can even connect to it by Ubuntu GUI. > >>>>>> > >>>>>> Can you update to 6.14.0-rc5-wt-ath+ and have a retry? Also please make > >>>>>> sure that your wpa_supplicant/iw support 6 GHz(or directly update to the > >>>>>> latest version). > >>>>>> > >>>>>> If you still cannot find 6 GHz AP, you can set debug_mask to 0xffffffff > >>>>>> to get ath12k logs. Then give it to us. > >>>>>> > >>>>>> > >>>>>>> -Walt > >>>>>>> > >>>>>> > >>>>> > >>>>> OK, I retested with the wt-ath 033125 tagged build. This included the > >>>>> patch the Jeff suggested I try, but the rest of the tree was clean. > >>>>> Still no 6ghz Wifi. I'm attaching a log file of the boot and first few > >>>>> seconds with the debug mask turned on. I noticed that if I rmmod the > >>>>> module and then modprobe it, it complains about not finding > >>>>> firmware-2.bin, however, I thought that was only for the qcn based > >>>>> chip? The HW info from dmesg looks like this: > >>>>> > >>>> > >>>> I cannot find this tag... > >>>> > >>>> > >>>> From the log, the 6 GHz channel should work. When scan is triggered, FW > >>>> shall send probe req on these channels. If AP send probe resp, station > >>>> shall find the AP. > >>>> > >>>> > >>>> > >>>> > >>>>> [ 6.070282] ath12k_pci 0000:63:00.0: BAR 0 [mem > >>>>> 0xdd800000-0xdd9fffff 64bit]: assigned > >>>>> [ 6.070310] ath12k_pci 0000:63:00.0: enabling device (0000 -> 0002) > >>>>> [ 6.071249] ath12k_pci 0000:63:00.0: MSI vectors: 16 > >>>>> [ 6.071254] ath12k_pci 0000:63:00.0: Hardware name: wcn7850 hw2.0 > >>>>> [ 6.596331] ath12k_pci 0000:63:00.0: qmi dma allocation failed > >>>>> (7077888 B type 1), will try later with sma > >>>>> ll size > >>>>> [ 6.604041] ath12k_pci 0000:63:00.0: chip_id 0x2 chip_family 0x4 > >>>>> board_id 0xff soc_id 0x40170200 > >>>>> [ 6.604044] ath12k_pci 0000:63:00.0: fw_version 0x100301e1 > >>>>> fw_build_timestamp 2023-12-06 04:05 fw_build_id > >>>>> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ- > >>>>> > >>>>> Also, I noticed when looking through the debug logs there are the > >>>>> occasional WARNING statements from a BUG it appears. They trace back > >>>>> to the mac.c file inside the ath12k code. There should be some in the > >>>>> debug log that's attached. Let me know if I can do anything else. > >>>>> Thanks, > >>>>> > >>>> > >>>> > >>>> I have never seen this warning on my upstream setup...Not sure if you > >>>> have changed anything or using the correct code base. > >>>> > >>>> Jeff merged this patch-set into ath-202504021602. Can you try on this > >>>> branch? > >>>> > >>>> git clone https://git.kernel.org/pub/scm/linux/kernel/git/ath/ath.git/ > >>>> git pull > >>>> git reset --hard ath-202504021602 > >>>> compile and install... > >>>> > >>>> Also make sure that the firmware you used is from the same folder, don't > >>>> mix with other folders: > >>>> linux-firmware/ath12k/WCN7850/hw2.0 > >>>> > >>>> 1. rmmod/insmod(debug_mask=0xffff) > >>>> 2. iw reg get > >>>> 3. iw reg set US > >>>> 4. iw xxx scan > >>>> wait and collect logs. > >>>> > >>>> don't do anything else. > >>>> > >>>> > >>>> Also, can you show me your AP configuration. > >>>> If you have another 6 GHz AP, you can have a try(better different brands). > >>>> > >> > >> Thanks for testing. > >> > >> Could you share your AP configuration? > >> > >> > >>>> > >>>> If you have sniffer, could please capture packets during testing? > >> > >> > >> Can you capture packets during the testing? I need to check probe req > >> and probe resp. > >> > >>>> > >>>> Thanks! > >>>> > >>>>> -Walt > >>>> > >>> OK, I cloned and built the kernel based on your instructions in your > >>> last email. Originally, the result was identical to my last email, > >>> including the WARNINGS. The .config I use is configured for a fully RT > >>> PREEMPT kernel, which I wondered if that was why I was receiving the > >>> WARNING. So I configured it as a Low Latency PREEMPT Desktop without > >>> the RT_PREEMPT and that eliminated the WARNING. However, still no 6Ghz > >>> networks. The firmware I'm using is straight from kernel.org GIT and I > >>> do a 'make install; make dedup' to install it. I believe it should be > >>> good. Attached is the latest log file. > >>> > >>> -Walt > >> > Sorry for the top-post earlier. I can't figure out how to capture the wireless packets as my chip/driver combo doesn't support monitor mode. I've attached a tarball that contains the trace data and additional firmware logs from the kernel.log file. Anything else you need, just ask. Thanks for your help, -Walt [-- Attachment #2: logs-20250409.tgz --] [-- Type: application/x-compressed-tar, Size: 4291322 bytes --] ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ath12k: No 6GHz Wireless found 2025-04-09 19:37 ` Walt Holman @ 2025-04-10 8:26 ` Kang Yang 2025-04-10 15:32 ` Walt Holman 0 siblings, 1 reply; 32+ messages in thread From: Kang Yang @ 2025-04-10 8:26 UTC (permalink / raw) To: Walt Holman; +Cc: Jeff Johnson, linux-wireless, ath12k@lists.infradead.org On 4/10/2025 3:37 AM, Walt Holman wrote: > On Tue, Apr 8, 2025 at 4:17 AM Kang Yang <quic_kangyang@quicinc.com> wrote: >> >> >> >> On 4/8/2025 1:49 AM, Walt Holman wrote: >>> Attached is a small packet capture where I did an 'iw wlp99s0 scan' >>> and also deactivated and reactivated wireless while the scan was >>> ongoing. Hopefully there's something interesting for you in there. >>> Also, I've take 3 screenshots showing the configs of the wireless AP >>> for the 6ghz network. The first screen is just the definition of the >>> network. No advanced settings are used. The 2nd screen shows the >>> channels and radio enabled. The 3rd screen has the advanced >>> (professional) settings for the network. I believe I changed 'Agile >>> Multiband' to enabled, but other settings are their defaults. Hope >>> some of this helps. Let me know if you need anything else. Thanks, >>> >> >> Your packets are Ethernet packets. I need wireless packets. >> >> >> Not sure if you know how to add a seperate monitor interface to capture >> 6 G channels' packet on your AP(you can google for specific command). >> >> >> Also, please capture firmware log: >> >> 1. sudo apt install trace-cmd >> 2. sudo trace-cmd record -e ath12k_wmi_diag >> 3. run test >> 4. "ctrl c" to stop recording: >> Hit Ctrl^C to stop recording >> ^CCPU0 data recorded at offset=0xdf5000 >> 2605056 bytes in size >> Then share the trace.dat to us. >> >> So you need to: >> 1. try to capture wireless packets. >> 2. capture firmware log(trade.data). >> 3. save kernel/wpa_supplicant/iw logs. >> >> >> >> >> >>> -Walt >>> >>> On Sun, Apr 6, 2025 at 8:58 PM Kang Yang <quic_kangyang@quicinc.com> wrote: >>>> >>>> >>>> >>>> On 4/4/2025 12:04 AM, Walt Holman wrote: >>>>> On Thu, Apr 3, 2025 at 3:20 AM Kang Yang <quic_kangyang@quicinc.com> wrote: >>>>>> >>>>>> >>>>>> >>>>>> On 4/3/2025 1:48 AM, Walt Holman wrote: >>>>>>> On Tue, Apr 1, 2025 at 9:48 PM Kang Yang <quic_kangyang@quicinc.com> wrote: >>>>>> >>>>>>>> >>>>>>>> Test on 6.14.0-rc5-wt-ath+, with the firmware you used. >>>>>>>> I can get 6 GHz AP and connect to it. >>>>>>>> >>>>>>>> ath12k_pci 0000:03:00.0: fw_version 0x100301e1 fw_build_timestamp >>>>>>>> 2023-12-06 04:05 fw_build_id >>>>>>>> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3 >>>>>>>> >>>>>>>> yk@yk-Mayan:~$ sudo iw wls1 scan | tee iw_scan.log: >>>>>>>> BSS 62:03:7f:12:64:64(on wls1) -- associated >>>>>>>> TSF: 606308271476 usec (7d, 00:25:08) >>>>>>>> freq: 6275 >>>>>>>> beacon interval: 100 TUs >>>>>>>> capability: ESS Privacy SpectrumMgmt ShortSlotTime (0x0511) >>>>>>>> signal: -17.00 dBm >>>>>>>> last seen: 52 ms ago >>>>>>>> Information elements from Probe Response frame: >>>>>>>> SSID: MLO-KANG-6G >>>>>>>> and other 6 GHz APs: >>>>>>>> SSID: 6G-gxia >>>>>>>> SSID: NETGEAR97-6G >>>>>>>> …… >>>>>>>> >>>>>>>> >>>>>>>> kernel log: >>>>>>>> [88158.033218] wls1: Inserted STA 62:03:7f:12:64:64 >>>>>>>> [88158.033232] wls1: authenticate with 62:03:7f:12:64:64 (local >>>>>>>> address=00:03:7f:37:12:54) >>>>>>>> [88158.033242] wls1: send auth to 62:03:7f:12:64:64 (try 1/3) >>>>>>>> [88158.041895] wls1: authenticated >>>>>>>> [88158.041914] wls1: moving STA 62:03:7f:12:64:64 to state 2 >>>>>>>> [88158.044291] wls1: determined local STA to be EHT, BW limited to 320 MHz >>>>>>>> [88158.045719] wls1: associate with 62:03:7f:12:64:64 (try 1/3) >>>>>>>> [88158.067045] wls1: RX AssocResp from 62:03:7f:12:64:64 (capab=0x511 >>>>>>>> status=0 aid=4) >>>>>>>> [88158.089090] wls1: associated >>>>>>>> >>>>>>>> I can even connect to it by Ubuntu GUI. >>>>>>>> >>>>>>>> Can you update to 6.14.0-rc5-wt-ath+ and have a retry? Also please make >>>>>>>> sure that your wpa_supplicant/iw support 6 GHz(or directly update to the >>>>>>>> latest version). >>>>>>>> >>>>>>>> If you still cannot find 6 GHz AP, you can set debug_mask to 0xffffffff >>>>>>>> to get ath12k logs. Then give it to us. >>>>>>>> >>>>>>>> >>>>>>>>> -Walt >>>>>>>>> >>>>>>>> >>>>>>> >>>>>>> OK, I retested with the wt-ath 033125 tagged build. This included the >>>>>>> patch the Jeff suggested I try, but the rest of the tree was clean. >>>>>>> Still no 6ghz Wifi. I'm attaching a log file of the boot and first few >>>>>>> seconds with the debug mask turned on. I noticed that if I rmmod the >>>>>>> module and then modprobe it, it complains about not finding >>>>>>> firmware-2.bin, however, I thought that was only for the qcn based >>>>>>> chip? The HW info from dmesg looks like this: >>>>>>> >>>>>> >>>>>> I cannot find this tag... >>>>>> >>>>>> >>>>>> From the log, the 6 GHz channel should work. When scan is triggered, FW >>>>>> shall send probe req on these channels. If AP send probe resp, station >>>>>> shall find the AP. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>> [ 6.070282] ath12k_pci 0000:63:00.0: BAR 0 [mem >>>>>>> 0xdd800000-0xdd9fffff 64bit]: assigned >>>>>>> [ 6.070310] ath12k_pci 0000:63:00.0: enabling device (0000 -> 0002) >>>>>>> [ 6.071249] ath12k_pci 0000:63:00.0: MSI vectors: 16 >>>>>>> [ 6.071254] ath12k_pci 0000:63:00.0: Hardware name: wcn7850 hw2.0 >>>>>>> [ 6.596331] ath12k_pci 0000:63:00.0: qmi dma allocation failed >>>>>>> (7077888 B type 1), will try later with sma >>>>>>> ll size >>>>>>> [ 6.604041] ath12k_pci 0000:63:00.0: chip_id 0x2 chip_family 0x4 >>>>>>> board_id 0xff soc_id 0x40170200 >>>>>>> [ 6.604044] ath12k_pci 0000:63:00.0: fw_version 0x100301e1 >>>>>>> fw_build_timestamp 2023-12-06 04:05 fw_build_id >>>>>>> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ- >>>>>>> >>>>>>> Also, I noticed when looking through the debug logs there are the >>>>>>> occasional WARNING statements from a BUG it appears. They trace back >>>>>>> to the mac.c file inside the ath12k code. There should be some in the >>>>>>> debug log that's attached. Let me know if I can do anything else. >>>>>>> Thanks, >>>>>>> >>>>>> >>>>>> >>>>>> I have never seen this warning on my upstream setup...Not sure if you >>>>>> have changed anything or using the correct code base. >>>>>> >>>>>> Jeff merged this patch-set into ath-202504021602. Can you try on this >>>>>> branch? >>>>>> >>>>>> git clone https://git.kernel.org/pub/scm/linux/kernel/git/ath/ath.git/ >>>>>> git pull >>>>>> git reset --hard ath-202504021602 >>>>>> compile and install... >>>>>> >>>>>> Also make sure that the firmware you used is from the same folder, don't >>>>>> mix with other folders: >>>>>> linux-firmware/ath12k/WCN7850/hw2.0 >>>>>> >>>>>> 1. rmmod/insmod(debug_mask=0xffff) >>>>>> 2. iw reg get >>>>>> 3. iw reg set US >>>>>> 4. iw xxx scan >>>>>> wait and collect logs. >>>>>> >>>>>> don't do anything else. >>>>>> >>>>>> >>>>>> Also, can you show me your AP configuration. >>>>>> If you have another 6 GHz AP, you can have a try(better different brands). >>>>>> >>>> >>>> Thanks for testing. >>>> >>>> Could you share your AP configuration? >>>> >>>> >>>>>> >>>>>> If you have sniffer, could please capture packets during testing? >>>> >>>> >>>> Can you capture packets during the testing? I need to check probe req >>>> and probe resp. >>>> >>>>>> >>>>>> Thanks! >>>>>> >>>>>>> -Walt >>>>>> >>>>> OK, I cloned and built the kernel based on your instructions in your >>>>> last email. Originally, the result was identical to my last email, >>>>> including the WARNINGS. The .config I use is configured for a fully RT >>>>> PREEMPT kernel, which I wondered if that was why I was receiving the >>>>> WARNING. So I configured it as a Low Latency PREEMPT Desktop without >>>>> the RT_PREEMPT and that eliminated the WARNING. However, still no 6Ghz >>>>> networks. The firmware I'm using is straight from kernel.org GIT and I >>>>> do a 'make install; make dedup' to install it. I believe it should be >>>>> good. Attached is the latest log file. >>>>> >>>>> -Walt >>>> >> > > > Sorry for the top-post earlier. I can't figure out how to capture the > wireless packets as my chip/driver combo doesn't support monitor mode. Your AP also cannot capture wireless packets? log in AP by usbserial or ssh. Try to enter command line. use iw command to create monitor interface. Then use tcpdump to capture packets. > I've attached a tarball that contains the trace data and additional > firmware logs from the kernel.log file. Anything else you need, just > ask. Thanks for your help, Your AP mac address? Need it to help check the fw log. > > -Walt ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ath12k: No 6GHz Wireless found 2025-04-10 8:26 ` Kang Yang @ 2025-04-10 15:32 ` Walt Holman 2025-04-15 21:23 ` Walt Holman 0 siblings, 1 reply; 32+ messages in thread From: Walt Holman @ 2025-04-10 15:32 UTC (permalink / raw) To: Kang Yang; +Cc: Jeff Johnson, linux-wireless, ath12k@lists.infradead.org On Thu, Apr 10, 2025 at 3:26 AM Kang Yang <kang.yang@oss.qualcomm.com> wrote: > > > > On 4/10/2025 3:37 AM, Walt Holman wrote: > > On Tue, Apr 8, 2025 at 4:17 AM Kang Yang <quic_kangyang@quicinc.com> wrote: > >> > >> > >> > >> On 4/8/2025 1:49 AM, Walt Holman wrote: > >>> Attached is a small packet capture where I did an 'iw wlp99s0 scan' > >>> and also deactivated and reactivated wireless while the scan was > >>> ongoing. Hopefully there's something interesting for you in there. > >>> Also, I've take 3 screenshots showing the configs of the wireless AP > >>> for the 6ghz network. The first screen is just the definition of the > >>> network. No advanced settings are used. The 2nd screen shows the > >>> channels and radio enabled. The 3rd screen has the advanced > >>> (professional) settings for the network. I believe I changed 'Agile > >>> Multiband' to enabled, but other settings are their defaults. Hope > >>> some of this helps. Let me know if you need anything else. Thanks, > >>> > >> > >> Your packets are Ethernet packets. I need wireless packets. > >> > >> > >> Not sure if you know how to add a seperate monitor interface to capture > >> 6 G channels' packet on your AP(you can google for specific command). > >> > >> > >> Also, please capture firmware log: > >> > >> 1. sudo apt install trace-cmd > >> 2. sudo trace-cmd record -e ath12k_wmi_diag > >> 3. run test > >> 4. "ctrl c" to stop recording: > >> Hit Ctrl^C to stop recording > >> ^CCPU0 data recorded at offset=0xdf5000 > >> 2605056 bytes in size > >> Then share the trace.dat to us. > >> > >> So you need to: > >> 1. try to capture wireless packets. > >> 2. capture firmware log(trade.data). > >> 3. save kernel/wpa_supplicant/iw logs. > >> > >> > >> > >> > >> > >>> -Walt > >>> > >>> On Sun, Apr 6, 2025 at 8:58 PM Kang Yang <quic_kangyang@quicinc.com> wrote: > >>>> > >>>> > >>>> > >>>> On 4/4/2025 12:04 AM, Walt Holman wrote: > >>>>> On Thu, Apr 3, 2025 at 3:20 AM Kang Yang <quic_kangyang@quicinc.com> wrote: > >>>>>> > >>>>>> > >>>>>> > >>>>>> On 4/3/2025 1:48 AM, Walt Holman wrote: > >>>>>>> On Tue, Apr 1, 2025 at 9:48 PM Kang Yang <quic_kangyang@quicinc.com> wrote: > >>>>>> > >>>>>>>> > >>>>>>>> Test on 6.14.0-rc5-wt-ath+, with the firmware you used. > >>>>>>>> I can get 6 GHz AP and connect to it. > >>>>>>>> > >>>>>>>> ath12k_pci 0000:03:00.0: fw_version 0x100301e1 fw_build_timestamp > >>>>>>>> 2023-12-06 04:05 fw_build_id > >>>>>>>> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3 > >>>>>>>> > >>>>>>>> yk@yk-Mayan:~$ sudo iw wls1 scan | tee iw_scan.log: > >>>>>>>> BSS 62:03:7f:12:64:64(on wls1) -- associated > >>>>>>>> TSF: 606308271476 usec (7d, 00:25:08) > >>>>>>>> freq: 6275 > >>>>>>>> beacon interval: 100 TUs > >>>>>>>> capability: ESS Privacy SpectrumMgmt ShortSlotTime (0x0511) > >>>>>>>> signal: -17.00 dBm > >>>>>>>> last seen: 52 ms ago > >>>>>>>> Information elements from Probe Response frame: > >>>>>>>> SSID: MLO-KANG-6G > >>>>>>>> and other 6 GHz APs: > >>>>>>>> SSID: 6G-gxia > >>>>>>>> SSID: NETGEAR97-6G > >>>>>>>> …… > >>>>>>>> > >>>>>>>> > >>>>>>>> kernel log: > >>>>>>>> [88158.033218] wls1: Inserted STA 62:03:7f:12:64:64 > >>>>>>>> [88158.033232] wls1: authenticate with 62:03:7f:12:64:64 (local > >>>>>>>> address=00:03:7f:37:12:54) > >>>>>>>> [88158.033242] wls1: send auth to 62:03:7f:12:64:64 (try 1/3) > >>>>>>>> [88158.041895] wls1: authenticated > >>>>>>>> [88158.041914] wls1: moving STA 62:03:7f:12:64:64 to state 2 > >>>>>>>> [88158.044291] wls1: determined local STA to be EHT, BW limited to 320 MHz > >>>>>>>> [88158.045719] wls1: associate with 62:03:7f:12:64:64 (try 1/3) > >>>>>>>> [88158.067045] wls1: RX AssocResp from 62:03:7f:12:64:64 (capab=0x511 > >>>>>>>> status=0 aid=4) > >>>>>>>> [88158.089090] wls1: associated > >>>>>>>> > >>>>>>>> I can even connect to it by Ubuntu GUI. > >>>>>>>> > >>>>>>>> Can you update to 6.14.0-rc5-wt-ath+ and have a retry? Also please make > >>>>>>>> sure that your wpa_supplicant/iw support 6 GHz(or directly update to the > >>>>>>>> latest version). > >>>>>>>> > >>>>>>>> If you still cannot find 6 GHz AP, you can set debug_mask to 0xffffffff > >>>>>>>> to get ath12k logs. Then give it to us. > >>>>>>>> > >>>>>>>> > >>>>>>>>> -Walt > >>>>>>>>> > >>>>>>>> > >>>>>>> > >>>>>>> OK, I retested with the wt-ath 033125 tagged build. This included the > >>>>>>> patch the Jeff suggested I try, but the rest of the tree was clean. > >>>>>>> Still no 6ghz Wifi. I'm attaching a log file of the boot and first few > >>>>>>> seconds with the debug mask turned on. I noticed that if I rmmod the > >>>>>>> module and then modprobe it, it complains about not finding > >>>>>>> firmware-2.bin, however, I thought that was only for the qcn based > >>>>>>> chip? The HW info from dmesg looks like this: > >>>>>>> > >>>>>> > >>>>>> I cannot find this tag... > >>>>>> > >>>>>> > >>>>>> From the log, the 6 GHz channel should work. When scan is triggered, FW > >>>>>> shall send probe req on these channels. If AP send probe resp, station > >>>>>> shall find the AP. > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>>> [ 6.070282] ath12k_pci 0000:63:00.0: BAR 0 [mem > >>>>>>> 0xdd800000-0xdd9fffff 64bit]: assigned > >>>>>>> [ 6.070310] ath12k_pci 0000:63:00.0: enabling device (0000 -> 0002) > >>>>>>> [ 6.071249] ath12k_pci 0000:63:00.0: MSI vectors: 16 > >>>>>>> [ 6.071254] ath12k_pci 0000:63:00.0: Hardware name: wcn7850 hw2.0 > >>>>>>> [ 6.596331] ath12k_pci 0000:63:00.0: qmi dma allocation failed > >>>>>>> (7077888 B type 1), will try later with sma > >>>>>>> ll size > >>>>>>> [ 6.604041] ath12k_pci 0000:63:00.0: chip_id 0x2 chip_family 0x4 > >>>>>>> board_id 0xff soc_id 0x40170200 > >>>>>>> [ 6.604044] ath12k_pci 0000:63:00.0: fw_version 0x100301e1 > >>>>>>> fw_build_timestamp 2023-12-06 04:05 fw_build_id > >>>>>>> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ- > >>>>>>> > >>>>>>> Also, I noticed when looking through the debug logs there are the > >>>>>>> occasional WARNING statements from a BUG it appears. They trace back > >>>>>>> to the mac.c file inside the ath12k code. There should be some in the > >>>>>>> debug log that's attached. Let me know if I can do anything else. > >>>>>>> Thanks, > >>>>>>> > >>>>>> > >>>>>> > >>>>>> I have never seen this warning on my upstream setup...Not sure if you > >>>>>> have changed anything or using the correct code base. > >>>>>> > >>>>>> Jeff merged this patch-set into ath-202504021602. Can you try on this > >>>>>> branch? > >>>>>> > >>>>>> git clone https://git.kernel.org/pub/scm/linux/kernel/git/ath/ath.git/ > >>>>>> git pull > >>>>>> git reset --hard ath-202504021602 > >>>>>> compile and install... > >>>>>> > >>>>>> Also make sure that the firmware you used is from the same folder, don't > >>>>>> mix with other folders: > >>>>>> linux-firmware/ath12k/WCN7850/hw2.0 > >>>>>> > >>>>>> 1. rmmod/insmod(debug_mask=0xffff) > >>>>>> 2. iw reg get > >>>>>> 3. iw reg set US > >>>>>> 4. iw xxx scan > >>>>>> wait and collect logs. > >>>>>> > >>>>>> don't do anything else. > >>>>>> > >>>>>> > >>>>>> Also, can you show me your AP configuration. > >>>>>> If you have another 6 GHz AP, you can have a try(better different brands). > >>>>>> > >>>> > >>>> Thanks for testing. > >>>> > >>>> Could you share your AP configuration? > >>>> > >>>> > >>>>>> > >>>>>> If you have sniffer, could please capture packets during testing? > >>>> > >>>> > >>>> Can you capture packets during the testing? I need to check probe req > >>>> and probe resp. > >>>> > >>>>>> > >>>>>> Thanks! > >>>>>> > >>>>>>> -Walt > >>>>>> > >>>>> OK, I cloned and built the kernel based on your instructions in your > >>>>> last email. Originally, the result was identical to my last email, > >>>>> including the WARNINGS. The .config I use is configured for a fully RT > >>>>> PREEMPT kernel, which I wondered if that was why I was receiving the > >>>>> WARNING. So I configured it as a Low Latency PREEMPT Desktop without > >>>>> the RT_PREEMPT and that eliminated the WARNING. However, still no 6Ghz > >>>>> networks. The firmware I'm using is straight from kernel.org GIT and I > >>>>> do a 'make install; make dedup' to install it. I believe it should be > >>>>> good. Attached is the latest log file. > >>>>> > >>>>> -Walt > >>>> > >> > > > > > > Sorry for the top-post earlier. I can't figure out how to capture the > > wireless packets as my chip/driver combo doesn't support monitor mode. > > Your AP also cannot capture wireless packets? > log in AP by usbserial or ssh. > Try to enter command line. use iw command to create monitor interface. > Then use tcpdump to capture packets. > > > I've attached a tarball that contains the trace data and additional > > firmware logs from the kernel.log file. Anything else you need, just > > ask. Thanks for your help, > > > Your AP mac address? > Need it to help check the fw log. > > > > > > -Walt > Sorry, the AP doesn't have tcpdump available on it. Also, this is a mesh setup with 3 nodes total. The main AP and 2 mesh nodes. I'm within 10 feet of one of the nodes and it's MAC for the wireless 6ghz network is: 10:7C:61:6F:2A:CA -Walt ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ath12k: No 6GHz Wireless found 2025-04-10 15:32 ` Walt Holman @ 2025-04-15 21:23 ` Walt Holman 2025-04-18 21:18 ` Walt Holman 0 siblings, 1 reply; 32+ messages in thread From: Walt Holman @ 2025-04-15 21:23 UTC (permalink / raw) To: Kang Yang; +Cc: Jeff Johnson, linux-wireless, ath12k@lists.infradead.org On Thu, Apr 10, 2025 at 10:32 AM Walt Holman <waltholman09@gmail.com> wrote: > > On Thu, Apr 10, 2025 at 3:26 AM Kang Yang <kang.yang@oss.qualcomm.com> wrote: > > > > > > > > On 4/10/2025 3:37 AM, Walt Holman wrote: > > > On Tue, Apr 8, 2025 at 4:17 AM Kang Yang <quic_kangyang@quicinc.com> wrote: > > >> > > >> > > >> > > >> On 4/8/2025 1:49 AM, Walt Holman wrote: > > >>> Attached is a small packet capture where I did an 'iw wlp99s0 scan' > > >>> and also deactivated and reactivated wireless while the scan was > > >>> ongoing. Hopefully there's something interesting for you in there. > > >>> Also, I've take 3 screenshots showing the configs of the wireless AP > > >>> for the 6ghz network. The first screen is just the definition of the > > >>> network. No advanced settings are used. The 2nd screen shows the > > >>> channels and radio enabled. The 3rd screen has the advanced > > >>> (professional) settings for the network. I believe I changed 'Agile > > >>> Multiband' to enabled, but other settings are their defaults. Hope > > >>> some of this helps. Let me know if you need anything else. Thanks, > > >>> > > >> > > >> Your packets are Ethernet packets. I need wireless packets. > > >> > > >> > > >> Not sure if you know how to add a seperate monitor interface to capture > > >> 6 G channels' packet on your AP(you can google for specific command). > > >> > > >> > > >> Also, please capture firmware log: > > >> > > >> 1. sudo apt install trace-cmd > > >> 2. sudo trace-cmd record -e ath12k_wmi_diag > > >> 3. run test > > >> 4. "ctrl c" to stop recording: > > >> Hit Ctrl^C to stop recording > > >> ^CCPU0 data recorded at offset=0xdf5000 > > >> 2605056 bytes in size > > >> Then share the trace.dat to us. > > >> > > >> So you need to: > > >> 1. try to capture wireless packets. > > >> 2. capture firmware log(trade.data). > > >> 3. save kernel/wpa_supplicant/iw logs. > > >> > > >> > > >> > > >> > > >> > > >>> -Walt > > >>> > > >>> On Sun, Apr 6, 2025 at 8:58 PM Kang Yang <quic_kangyang@quicinc.com> wrote: > > >>>> > > >>>> > > >>>> > > >>>> On 4/4/2025 12:04 AM, Walt Holman wrote: > > >>>>> On Thu, Apr 3, 2025 at 3:20 AM Kang Yang <quic_kangyang@quicinc.com> wrote: > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>>> On 4/3/2025 1:48 AM, Walt Holman wrote: > > >>>>>>> On Tue, Apr 1, 2025 at 9:48 PM Kang Yang <quic_kangyang@quicinc.com> wrote: > > >>>>>> > > >>>>>>>> > > >>>>>>>> Test on 6.14.0-rc5-wt-ath+, with the firmware you used. > > >>>>>>>> I can get 6 GHz AP and connect to it. > > >>>>>>>> > > >>>>>>>> ath12k_pci 0000:03:00.0: fw_version 0x100301e1 fw_build_timestamp > > >>>>>>>> 2023-12-06 04:05 fw_build_id > > >>>>>>>> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3 > > >>>>>>>> > > >>>>>>>> yk@yk-Mayan:~$ sudo iw wls1 scan | tee iw_scan.log: > > >>>>>>>> BSS 62:03:7f:12:64:64(on wls1) -- associated > > >>>>>>>> TSF: 606308271476 usec (7d, 00:25:08) > > >>>>>>>> freq: 6275 > > >>>>>>>> beacon interval: 100 TUs > > >>>>>>>> capability: ESS Privacy SpectrumMgmt ShortSlotTime (0x0511) > > >>>>>>>> signal: -17.00 dBm > > >>>>>>>> last seen: 52 ms ago > > >>>>>>>> Information elements from Probe Response frame: > > >>>>>>>> SSID: MLO-KANG-6G > > >>>>>>>> and other 6 GHz APs: > > >>>>>>>> SSID: 6G-gxia > > >>>>>>>> SSID: NETGEAR97-6G > > >>>>>>>> …… > > >>>>>>>> > > >>>>>>>> > > >>>>>>>> kernel log: > > >>>>>>>> [88158.033218] wls1: Inserted STA 62:03:7f:12:64:64 > > >>>>>>>> [88158.033232] wls1: authenticate with 62:03:7f:12:64:64 (local > > >>>>>>>> address=00:03:7f:37:12:54) > > >>>>>>>> [88158.033242] wls1: send auth to 62:03:7f:12:64:64 (try 1/3) > > >>>>>>>> [88158.041895] wls1: authenticated > > >>>>>>>> [88158.041914] wls1: moving STA 62:03:7f:12:64:64 to state 2 > > >>>>>>>> [88158.044291] wls1: determined local STA to be EHT, BW limited to 320 MHz > > >>>>>>>> [88158.045719] wls1: associate with 62:03:7f:12:64:64 (try 1/3) > > >>>>>>>> [88158.067045] wls1: RX AssocResp from 62:03:7f:12:64:64 (capab=0x511 > > >>>>>>>> status=0 aid=4) > > >>>>>>>> [88158.089090] wls1: associated > > >>>>>>>> > > >>>>>>>> I can even connect to it by Ubuntu GUI. > > >>>>>>>> > > >>>>>>>> Can you update to 6.14.0-rc5-wt-ath+ and have a retry? Also please make > > >>>>>>>> sure that your wpa_supplicant/iw support 6 GHz(or directly update to the > > >>>>>>>> latest version). > > >>>>>>>> > > >>>>>>>> If you still cannot find 6 GHz AP, you can set debug_mask to 0xffffffff > > >>>>>>>> to get ath12k logs. Then give it to us. > > >>>>>>>> > > >>>>>>>> > > >>>>>>>>> -Walt > > >>>>>>>>> > > >>>>>>>> > > >>>>>>> > > >>>>>>> OK, I retested with the wt-ath 033125 tagged build. This included the > > >>>>>>> patch the Jeff suggested I try, but the rest of the tree was clean. > > >>>>>>> Still no 6ghz Wifi. I'm attaching a log file of the boot and first few > > >>>>>>> seconds with the debug mask turned on. I noticed that if I rmmod the > > >>>>>>> module and then modprobe it, it complains about not finding > > >>>>>>> firmware-2.bin, however, I thought that was only for the qcn based > > >>>>>>> chip? The HW info from dmesg looks like this: > > >>>>>>> > > >>>>>> > > >>>>>> I cannot find this tag... > > >>>>>> > > >>>>>> > > >>>>>> From the log, the 6 GHz channel should work. When scan is triggered, FW > > >>>>>> shall send probe req on these channels. If AP send probe resp, station > > >>>>>> shall find the AP. > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>>>> [ 6.070282] ath12k_pci 0000:63:00.0: BAR 0 [mem > > >>>>>>> 0xdd800000-0xdd9fffff 64bit]: assigned > > >>>>>>> [ 6.070310] ath12k_pci 0000:63:00.0: enabling device (0000 -> 0002) > > >>>>>>> [ 6.071249] ath12k_pci 0000:63:00.0: MSI vectors: 16 > > >>>>>>> [ 6.071254] ath12k_pci 0000:63:00.0: Hardware name: wcn7850 hw2.0 > > >>>>>>> [ 6.596331] ath12k_pci 0000:63:00.0: qmi dma allocation failed > > >>>>>>> (7077888 B type 1), will try later with sma > > >>>>>>> ll size > > >>>>>>> [ 6.604041] ath12k_pci 0000:63:00.0: chip_id 0x2 chip_family 0x4 > > >>>>>>> board_id 0xff soc_id 0x40170200 > > >>>>>>> [ 6.604044] ath12k_pci 0000:63:00.0: fw_version 0x100301e1 > > >>>>>>> fw_build_timestamp 2023-12-06 04:05 fw_build_id > > >>>>>>> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ- > > >>>>>>> > > >>>>>>> Also, I noticed when looking through the debug logs there are the > > >>>>>>> occasional WARNING statements from a BUG it appears. They trace back > > >>>>>>> to the mac.c file inside the ath12k code. There should be some in the > > >>>>>>> debug log that's attached. Let me know if I can do anything else. > > >>>>>>> Thanks, > > >>>>>>> > > >>>>>> > > >>>>>> > > >>>>>> I have never seen this warning on my upstream setup...Not sure if you > > >>>>>> have changed anything or using the correct code base. > > >>>>>> > > >>>>>> Jeff merged this patch-set into ath-202504021602. Can you try on this > > >>>>>> branch? > > >>>>>> > > >>>>>> git clone https://git.kernel.org/pub/scm/linux/kernel/git/ath/ath.git/ > > >>>>>> git pull > > >>>>>> git reset --hard ath-202504021602 > > >>>>>> compile and install... > > >>>>>> > > >>>>>> Also make sure that the firmware you used is from the same folder, don't > > >>>>>> mix with other folders: > > >>>>>> linux-firmware/ath12k/WCN7850/hw2.0 > > >>>>>> > > >>>>>> 1. rmmod/insmod(debug_mask=0xffff) > > >>>>>> 2. iw reg get > > >>>>>> 3. iw reg set US > > >>>>>> 4. iw xxx scan > > >>>>>> wait and collect logs. > > >>>>>> > > >>>>>> don't do anything else. > > >>>>>> > > >>>>>> > > >>>>>> Also, can you show me your AP configuration. > > >>>>>> If you have another 6 GHz AP, you can have a try(better different brands). > > >>>>>> > > >>>> > > >>>> Thanks for testing. > > >>>> > > >>>> Could you share your AP configuration? > > >>>> > > >>>> > > >>>>>> > > >>>>>> If you have sniffer, could please capture packets during testing? > > >>>> > > >>>> > > >>>> Can you capture packets during the testing? I need to check probe req > > >>>> and probe resp. > > >>>> > > >>>>>> > > >>>>>> Thanks! > > >>>>>> > > >>>>>>> -Walt > > >>>>>> > > >>>>> OK, I cloned and built the kernel based on your instructions in your > > >>>>> last email. Originally, the result was identical to my last email, > > >>>>> including the WARNINGS. The .config I use is configured for a fully RT > > >>>>> PREEMPT kernel, which I wondered if that was why I was receiving the > > >>>>> WARNING. So I configured it as a Low Latency PREEMPT Desktop without > > >>>>> the RT_PREEMPT and that eliminated the WARNING. However, still no 6Ghz > > >>>>> networks. The firmware I'm using is straight from kernel.org GIT and I > > >>>>> do a 'make install; make dedup' to install it. I believe it should be > > >>>>> good. Attached is the latest log file. > > >>>>> > > >>>>> -Walt > > >>>> > > >> > > > > > > > > > Sorry for the top-post earlier. I can't figure out how to capture the > > > wireless packets as my chip/driver combo doesn't support monitor mode. > > > > Your AP also cannot capture wireless packets? > > log in AP by usbserial or ssh. > > Try to enter command line. use iw command to create monitor interface. > > Then use tcpdump to capture packets. > > > > > I've attached a tarball that contains the trace data and additional > > > firmware logs from the kernel.log file. Anything else you need, just > > > ask. Thanks for your help, > > > > > > Your AP mac address? > > Need it to help check the fw log. > > > > > > > > > > -Walt > > > > Sorry, the AP doesn't have tcpdump available on it. Also, this is a > mesh setup with 3 nodes total. The main AP and 2 mesh nodes. I'm > within 10 feet of one of the nodes and it's MAC for the wireless 6ghz > network is: 10:7C:61:6F:2A:CA > > -Walt The other 2 node 6ghz mac addresses are: 10:7C:61:6F:1F:11 - Router 10:7C:61:6F:32:92 - Node The first MAC address I gave you earlier was a node located approximately 5 feet from where the laptop is. -Walt ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ath12k: No 6GHz Wireless found 2025-04-15 21:23 ` Walt Holman @ 2025-04-18 21:18 ` Walt Holman 2025-04-20 15:18 ` Walt Holman 0 siblings, 1 reply; 32+ messages in thread From: Walt Holman @ 2025-04-18 21:18 UTC (permalink / raw) To: Kang Yang; +Cc: Jeff Johnson, linux-wireless, ath12k@lists.infradead.org On Tue, Apr 15, 2025 at 4:23 PM Walt Holman <waltholman09@gmail.com> wrote: > > On Thu, Apr 10, 2025 at 10:32 AM Walt Holman <waltholman09@gmail.com> wrote: > > > > On Thu, Apr 10, 2025 at 3:26 AM Kang Yang <kang.yang@oss.qualcomm.com> wrote: > > > > > > > > > > > > On 4/10/2025 3:37 AM, Walt Holman wrote: > > > > On Tue, Apr 8, 2025 at 4:17 AM Kang Yang <quic_kangyang@quicinc.com> wrote: > > > >> > > > >> > > > >> > > > >> On 4/8/2025 1:49 AM, Walt Holman wrote: > > > >>> Attached is a small packet capture where I did an 'iw wlp99s0 scan' > > > >>> and also deactivated and reactivated wireless while the scan was > > > >>> ongoing. Hopefully there's something interesting for you in there. > > > >>> Also, I've take 3 screenshots showing the configs of the wireless AP > > > >>> for the 6ghz network. The first screen is just the definition of the > > > >>> network. No advanced settings are used. The 2nd screen shows the > > > >>> channels and radio enabled. The 3rd screen has the advanced > > > >>> (professional) settings for the network. I believe I changed 'Agile > > > >>> Multiband' to enabled, but other settings are their defaults. Hope > > > >>> some of this helps. Let me know if you need anything else. Thanks, > > > >>> > > > >> > > > >> Your packets are Ethernet packets. I need wireless packets. > > > >> > > > >> > > > >> Not sure if you know how to add a seperate monitor interface to capture > > > >> 6 G channels' packet on your AP(you can google for specific command). > > > >> > > > >> > > > >> Also, please capture firmware log: > > > >> > > > >> 1. sudo apt install trace-cmd > > > >> 2. sudo trace-cmd record -e ath12k_wmi_diag > > > >> 3. run test > > > >> 4. "ctrl c" to stop recording: > > > >> Hit Ctrl^C to stop recording > > > >> ^CCPU0 data recorded at offset=0xdf5000 > > > >> 2605056 bytes in size > > > >> Then share the trace.dat to us. > > > >> > > > >> So you need to: > > > >> 1. try to capture wireless packets. > > > >> 2. capture firmware log(trade.data). > > > >> 3. save kernel/wpa_supplicant/iw logs. > > > >> > > > >> > > > >> > > > >> > > > >> > > > >>> -Walt > > > >>> > > > >>> On Sun, Apr 6, 2025 at 8:58 PM Kang Yang <quic_kangyang@quicinc.com> wrote: > > > >>>> > > > >>>> > > > >>>> > > > >>>> On 4/4/2025 12:04 AM, Walt Holman wrote: > > > >>>>> On Thu, Apr 3, 2025 at 3:20 AM Kang Yang <quic_kangyang@quicinc.com> wrote: > > > >>>>>> > > > >>>>>> > > > >>>>>> > > > >>>>>> On 4/3/2025 1:48 AM, Walt Holman wrote: > > > >>>>>>> On Tue, Apr 1, 2025 at 9:48 PM Kang Yang <quic_kangyang@quicinc.com> wrote: > > > >>>>>> > > > >>>>>>>> > > > >>>>>>>> Test on 6.14.0-rc5-wt-ath+, with the firmware you used. > > > >>>>>>>> I can get 6 GHz AP and connect to it. > > > >>>>>>>> > > > >>>>>>>> ath12k_pci 0000:03:00.0: fw_version 0x100301e1 fw_build_timestamp > > > >>>>>>>> 2023-12-06 04:05 fw_build_id > > > >>>>>>>> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3 > > > >>>>>>>> > > > >>>>>>>> yk@yk-Mayan:~$ sudo iw wls1 scan | tee iw_scan.log: > > > >>>>>>>> BSS 62:03:7f:12:64:64(on wls1) -- associated > > > >>>>>>>> TSF: 606308271476 usec (7d, 00:25:08) > > > >>>>>>>> freq: 6275 > > > >>>>>>>> beacon interval: 100 TUs > > > >>>>>>>> capability: ESS Privacy SpectrumMgmt ShortSlotTime (0x0511) > > > >>>>>>>> signal: -17.00 dBm > > > >>>>>>>> last seen: 52 ms ago > > > >>>>>>>> Information elements from Probe Response frame: > > > >>>>>>>> SSID: MLO-KANG-6G > > > >>>>>>>> and other 6 GHz APs: > > > >>>>>>>> SSID: 6G-gxia > > > >>>>>>>> SSID: NETGEAR97-6G > > > >>>>>>>> …… > > > >>>>>>>> > > > >>>>>>>> > > > >>>>>>>> kernel log: > > > >>>>>>>> [88158.033218] wls1: Inserted STA 62:03:7f:12:64:64 > > > >>>>>>>> [88158.033232] wls1: authenticate with 62:03:7f:12:64:64 (local > > > >>>>>>>> address=00:03:7f:37:12:54) > > > >>>>>>>> [88158.033242] wls1: send auth to 62:03:7f:12:64:64 (try 1/3) > > > >>>>>>>> [88158.041895] wls1: authenticated > > > >>>>>>>> [88158.041914] wls1: moving STA 62:03:7f:12:64:64 to state 2 > > > >>>>>>>> [88158.044291] wls1: determined local STA to be EHT, BW limited to 320 MHz > > > >>>>>>>> [88158.045719] wls1: associate with 62:03:7f:12:64:64 (try 1/3) > > > >>>>>>>> [88158.067045] wls1: RX AssocResp from 62:03:7f:12:64:64 (capab=0x511 > > > >>>>>>>> status=0 aid=4) > > > >>>>>>>> [88158.089090] wls1: associated > > > >>>>>>>> > > > >>>>>>>> I can even connect to it by Ubuntu GUI. > > > >>>>>>>> > > > >>>>>>>> Can you update to 6.14.0-rc5-wt-ath+ and have a retry? Also please make > > > >>>>>>>> sure that your wpa_supplicant/iw support 6 GHz(or directly update to the > > > >>>>>>>> latest version). > > > >>>>>>>> > > > >>>>>>>> If you still cannot find 6 GHz AP, you can set debug_mask to 0xffffffff > > > >>>>>>>> to get ath12k logs. Then give it to us. > > > >>>>>>>> > > > >>>>>>>> > > > >>>>>>>>> -Walt > > > >>>>>>>>> > > > >>>>>>>> > > > >>>>>>> > > > >>>>>>> OK, I retested with the wt-ath 033125 tagged build. This included the > > > >>>>>>> patch the Jeff suggested I try, but the rest of the tree was clean. > > > >>>>>>> Still no 6ghz Wifi. I'm attaching a log file of the boot and first few > > > >>>>>>> seconds with the debug mask turned on. I noticed that if I rmmod the > > > >>>>>>> module and then modprobe it, it complains about not finding > > > >>>>>>> firmware-2.bin, however, I thought that was only for the qcn based > > > >>>>>>> chip? The HW info from dmesg looks like this: > > > >>>>>>> > > > >>>>>> > > > >>>>>> I cannot find this tag... > > > >>>>>> > > > >>>>>> > > > >>>>>> From the log, the 6 GHz channel should work. When scan is triggered, FW > > > >>>>>> shall send probe req on these channels. If AP send probe resp, station > > > >>>>>> shall find the AP. > > > >>>>>> > > > >>>>>> > > > >>>>>> > > > >>>>>> > > > >>>>>>> [ 6.070282] ath12k_pci 0000:63:00.0: BAR 0 [mem > > > >>>>>>> 0xdd800000-0xdd9fffff 64bit]: assigned > > > >>>>>>> [ 6.070310] ath12k_pci 0000:63:00.0: enabling device (0000 -> 0002) > > > >>>>>>> [ 6.071249] ath12k_pci 0000:63:00.0: MSI vectors: 16 > > > >>>>>>> [ 6.071254] ath12k_pci 0000:63:00.0: Hardware name: wcn7850 hw2.0 > > > >>>>>>> [ 6.596331] ath12k_pci 0000:63:00.0: qmi dma allocation failed > > > >>>>>>> (7077888 B type 1), will try later with sma > > > >>>>>>> ll size > > > >>>>>>> [ 6.604041] ath12k_pci 0000:63:00.0: chip_id 0x2 chip_family 0x4 > > > >>>>>>> board_id 0xff soc_id 0x40170200 > > > >>>>>>> [ 6.604044] ath12k_pci 0000:63:00.0: fw_version 0x100301e1 > > > >>>>>>> fw_build_timestamp 2023-12-06 04:05 fw_build_id > > > >>>>>>> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ- > > > >>>>>>> > > > >>>>>>> Also, I noticed when looking through the debug logs there are the > > > >>>>>>> occasional WARNING statements from a BUG it appears. They trace back > > > >>>>>>> to the mac.c file inside the ath12k code. There should be some in the > > > >>>>>>> debug log that's attached. Let me know if I can do anything else. > > > >>>>>>> Thanks, > > > >>>>>>> > > > >>>>>> > > > >>>>>> > > > >>>>>> I have never seen this warning on my upstream setup...Not sure if you > > > >>>>>> have changed anything or using the correct code base. > > > >>>>>> > > > >>>>>> Jeff merged this patch-set into ath-202504021602. Can you try on this > > > >>>>>> branch? > > > >>>>>> > > > >>>>>> git clone https://git.kernel.org/pub/scm/linux/kernel/git/ath/ath.git/ > > > >>>>>> git pull > > > >>>>>> git reset --hard ath-202504021602 > > > >>>>>> compile and install... > > > >>>>>> > > > >>>>>> Also make sure that the firmware you used is from the same folder, don't > > > >>>>>> mix with other folders: > > > >>>>>> linux-firmware/ath12k/WCN7850/hw2.0 > > > >>>>>> > > > >>>>>> 1. rmmod/insmod(debug_mask=0xffff) > > > >>>>>> 2. iw reg get > > > >>>>>> 3. iw reg set US > > > >>>>>> 4. iw xxx scan > > > >>>>>> wait and collect logs. > > > >>>>>> > > > >>>>>> don't do anything else. > > > >>>>>> > > > >>>>>> > > > >>>>>> Also, can you show me your AP configuration. > > > >>>>>> If you have another 6 GHz AP, you can have a try(better different brands). > > > >>>>>> > > > >>>> > > > >>>> Thanks for testing. > > > >>>> > > > >>>> Could you share your AP configuration? > > > >>>> > > > >>>> > > > >>>>>> > > > >>>>>> If you have sniffer, could please capture packets during testing? > > > >>>> > > > >>>> > > > >>>> Can you capture packets during the testing? I need to check probe req > > > >>>> and probe resp. > > > >>>> > > > >>>>>> > > > >>>>>> Thanks! > > > >>>>>> > > > >>>>>>> -Walt > > > >>>>>> > > > >>>>> OK, I cloned and built the kernel based on your instructions in your > > > >>>>> last email. Originally, the result was identical to my last email, > > > >>>>> including the WARNINGS. The .config I use is configured for a fully RT > > > >>>>> PREEMPT kernel, which I wondered if that was why I was receiving the > > > >>>>> WARNING. So I configured it as a Low Latency PREEMPT Desktop without > > > >>>>> the RT_PREEMPT and that eliminated the WARNING. However, still no 6Ghz > > > >>>>> networks. The firmware I'm using is straight from kernel.org GIT and I > > > >>>>> do a 'make install; make dedup' to install it. I believe it should be > > > >>>>> good. Attached is the latest log file. > > > >>>>> > > > >>>>> -Walt > > > >>>> > > > >> > > > > > > > > > > > > Sorry for the top-post earlier. I can't figure out how to capture the > > > > wireless packets as my chip/driver combo doesn't support monitor mode. > > > > > > Your AP also cannot capture wireless packets? > > > log in AP by usbserial or ssh. > > > Try to enter command line. use iw command to create monitor interface. > > > Then use tcpdump to capture packets. > > > > > > > I've attached a tarball that contains the trace data and additional > > > > firmware logs from the kernel.log file. Anything else you need, just > > > > ask. Thanks for your help, > > > > > > > > > Your AP mac address? > > > Need it to help check the fw log. > > > > > > > > > > > > > > -Walt > > > > > > > Sorry, the AP doesn't have tcpdump available on it. Also, this is a > > mesh setup with 3 nodes total. The main AP and 2 mesh nodes. I'm > > within 10 feet of one of the nodes and it's MAC for the wireless 6ghz > > network is: 10:7C:61:6F:2A:CA > > > > -Walt > > The other 2 node 6ghz mac addresses are: > 10:7C:61:6F:1F:11 - Router > 10:7C:61:6F:32:92 - Node > > The first MAC address I gave you earlier was a node located > approximately 5 feet from where the laptop is. > > -Walt Well, I'm running into a brick wall it seems trying to get 6Ghz enabled on this. I tried the ath-next-20250418 tag just now and still don't see or connect to my 6Ghz network. I applied the patches in: https://lore.kernel.org/linux-wireless/20250418-ath12k-6g-lp-vlp-v1-0-c869c86cad60@quicinc.com/T/#t hoping that would help, but alas, no 6Ghz networks. I see that MLO and other nice fixes are coming in 6.16, but without 6Ghz, they'll do me no good. I'm really wondering if it's a firmware issue that excludes my chip or something. Again, anything I can do to help, let me know. Thanks, -Walt ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ath12k: No 6GHz Wireless found 2025-04-18 21:18 ` Walt Holman @ 2025-04-20 15:18 ` Walt Holman 2025-05-02 7:02 ` ath12k-firmware: Module no longer loads with current git firmware Walt Holman 2025-05-15 8:12 ` ath12k: No 6GHz Wireless found Kang Yang 0 siblings, 2 replies; 32+ messages in thread From: Walt Holman @ 2025-04-20 15:18 UTC (permalink / raw) To: Kang Yang; +Cc: Jeff Johnson, linux-wireless, ath12k@lists.infradead.org On Fri, Apr 18, 2025 at 4:18 PM Walt Holman <waltholman09@gmail.com> wrote: > > On Tue, Apr 15, 2025 at 4:23 PM Walt Holman <waltholman09@gmail.com> wrote: > > > > On Thu, Apr 10, 2025 at 10:32 AM Walt Holman <waltholman09@gmail.com> wrote: > > > > > > On Thu, Apr 10, 2025 at 3:26 AM Kang Yang <kang.yang@oss.qualcomm.com> wrote: > > > > > > > > > > > > > > > > On 4/10/2025 3:37 AM, Walt Holman wrote: > > > > > On Tue, Apr 8, 2025 at 4:17 AM Kang Yang <quic_kangyang@quicinc.com> wrote: > > > > >> > > > > >> > > > > >> > > > > >> On 4/8/2025 1:49 AM, Walt Holman wrote: > > > > >>> Attached is a small packet capture where I did an 'iw wlp99s0 scan' > > > > >>> and also deactivated and reactivated wireless while the scan was > > > > >>> ongoing. Hopefully there's something interesting for you in there. > > > > >>> Also, I've take 3 screenshots showing the configs of the wireless AP > > > > >>> for the 6ghz network. The first screen is just the definition of the > > > > >>> network. No advanced settings are used. The 2nd screen shows the > > > > >>> channels and radio enabled. The 3rd screen has the advanced > > > > >>> (professional) settings for the network. I believe I changed 'Agile > > > > >>> Multiband' to enabled, but other settings are their defaults. Hope > > > > >>> some of this helps. Let me know if you need anything else. Thanks, > > > > >>> > > > > >> > > > > >> Your packets are Ethernet packets. I need wireless packets. > > > > >> > > > > >> > > > > >> Not sure if you know how to add a seperate monitor interface to capture > > > > >> 6 G channels' packet on your AP(you can google for specific command). > > > > >> > > > > >> > > > > >> Also, please capture firmware log: > > > > >> > > > > >> 1. sudo apt install trace-cmd > > > > >> 2. sudo trace-cmd record -e ath12k_wmi_diag > > > > >> 3. run test > > > > >> 4. "ctrl c" to stop recording: > > > > >> Hit Ctrl^C to stop recording > > > > >> ^CCPU0 data recorded at offset=0xdf5000 > > > > >> 2605056 bytes in size > > > > >> Then share the trace.dat to us. > > > > >> > > > > >> So you need to: > > > > >> 1. try to capture wireless packets. > > > > >> 2. capture firmware log(trade.data). > > > > >> 3. save kernel/wpa_supplicant/iw logs. > > > > >> > > > > >> > > > > >> > > > > >> > > > > >> > > > > >>> -Walt > > > > >>> > > > > >>> On Sun, Apr 6, 2025 at 8:58 PM Kang Yang <quic_kangyang@quicinc.com> wrote: > > > > >>>> > > > > >>>> > > > > >>>> > > > > >>>> On 4/4/2025 12:04 AM, Walt Holman wrote: > > > > >>>>> On Thu, Apr 3, 2025 at 3:20 AM Kang Yang <quic_kangyang@quicinc.com> wrote: > > > > >>>>>> > > > > >>>>>> > > > > >>>>>> > > > > >>>>>> On 4/3/2025 1:48 AM, Walt Holman wrote: > > > > >>>>>>> On Tue, Apr 1, 2025 at 9:48 PM Kang Yang <quic_kangyang@quicinc.com> wrote: > > > > >>>>>> > > > > >>>>>>>> > > > > >>>>>>>> Test on 6.14.0-rc5-wt-ath+, with the firmware you used. > > > > >>>>>>>> I can get 6 GHz AP and connect to it. > > > > >>>>>>>> > > > > >>>>>>>> ath12k_pci 0000:03:00.0: fw_version 0x100301e1 fw_build_timestamp > > > > >>>>>>>> 2023-12-06 04:05 fw_build_id > > > > >>>>>>>> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3 > > > > >>>>>>>> > > > > >>>>>>>> yk@yk-Mayan:~$ sudo iw wls1 scan | tee iw_scan.log: > > > > >>>>>>>> BSS 62:03:7f:12:64:64(on wls1) -- associated > > > > >>>>>>>> TSF: 606308271476 usec (7d, 00:25:08) > > > > >>>>>>>> freq: 6275 > > > > >>>>>>>> beacon interval: 100 TUs > > > > >>>>>>>> capability: ESS Privacy SpectrumMgmt ShortSlotTime (0x0511) > > > > >>>>>>>> signal: -17.00 dBm > > > > >>>>>>>> last seen: 52 ms ago > > > > >>>>>>>> Information elements from Probe Response frame: > > > > >>>>>>>> SSID: MLO-KANG-6G > > > > >>>>>>>> and other 6 GHz APs: > > > > >>>>>>>> SSID: 6G-gxia > > > > >>>>>>>> SSID: NETGEAR97-6G > > > > >>>>>>>> …… > > > > >>>>>>>> > > > > >>>>>>>> > > > > >>>>>>>> kernel log: > > > > >>>>>>>> [88158.033218] wls1: Inserted STA 62:03:7f:12:64:64 > > > > >>>>>>>> [88158.033232] wls1: authenticate with 62:03:7f:12:64:64 (local > > > > >>>>>>>> address=00:03:7f:37:12:54) > > > > >>>>>>>> [88158.033242] wls1: send auth to 62:03:7f:12:64:64 (try 1/3) > > > > >>>>>>>> [88158.041895] wls1: authenticated > > > > >>>>>>>> [88158.041914] wls1: moving STA 62:03:7f:12:64:64 to state 2 > > > > >>>>>>>> [88158.044291] wls1: determined local STA to be EHT, BW limited to 320 MHz > > > > >>>>>>>> [88158.045719] wls1: associate with 62:03:7f:12:64:64 (try 1/3) > > > > >>>>>>>> [88158.067045] wls1: RX AssocResp from 62:03:7f:12:64:64 (capab=0x511 > > > > >>>>>>>> status=0 aid=4) > > > > >>>>>>>> [88158.089090] wls1: associated > > > > >>>>>>>> > > > > >>>>>>>> I can even connect to it by Ubuntu GUI. > > > > >>>>>>>> > > > > >>>>>>>> Can you update to 6.14.0-rc5-wt-ath+ and have a retry? Also please make > > > > >>>>>>>> sure that your wpa_supplicant/iw support 6 GHz(or directly update to the > > > > >>>>>>>> latest version). > > > > >>>>>>>> > > > > >>>>>>>> If you still cannot find 6 GHz AP, you can set debug_mask to 0xffffffff > > > > >>>>>>>> to get ath12k logs. Then give it to us. > > > > >>>>>>>> > > > > >>>>>>>> > > > > >>>>>>>>> -Walt > > > > >>>>>>>>> > > > > >>>>>>>> > > > > >>>>>>> > > > > >>>>>>> OK, I retested with the wt-ath 033125 tagged build. This included the > > > > >>>>>>> patch the Jeff suggested I try, but the rest of the tree was clean. > > > > >>>>>>> Still no 6ghz Wifi. I'm attaching a log file of the boot and first few > > > > >>>>>>> seconds with the debug mask turned on. I noticed that if I rmmod the > > > > >>>>>>> module and then modprobe it, it complains about not finding > > > > >>>>>>> firmware-2.bin, however, I thought that was only for the qcn based > > > > >>>>>>> chip? The HW info from dmesg looks like this: > > > > >>>>>>> > > > > >>>>>> > > > > >>>>>> I cannot find this tag... > > > > >>>>>> > > > > >>>>>> > > > > >>>>>> From the log, the 6 GHz channel should work. When scan is triggered, FW > > > > >>>>>> shall send probe req on these channels. If AP send probe resp, station > > > > >>>>>> shall find the AP. > > > > >>>>>> > > > > >>>>>> > > > > >>>>>> > > > > >>>>>> > > > > >>>>>>> [ 6.070282] ath12k_pci 0000:63:00.0: BAR 0 [mem > > > > >>>>>>> 0xdd800000-0xdd9fffff 64bit]: assigned > > > > >>>>>>> [ 6.070310] ath12k_pci 0000:63:00.0: enabling device (0000 -> 0002) > > > > >>>>>>> [ 6.071249] ath12k_pci 0000:63:00.0: MSI vectors: 16 > > > > >>>>>>> [ 6.071254] ath12k_pci 0000:63:00.0: Hardware name: wcn7850 hw2.0 > > > > >>>>>>> [ 6.596331] ath12k_pci 0000:63:00.0: qmi dma allocation failed > > > > >>>>>>> (7077888 B type 1), will try later with sma > > > > >>>>>>> ll size > > > > >>>>>>> [ 6.604041] ath12k_pci 0000:63:00.0: chip_id 0x2 chip_family 0x4 > > > > >>>>>>> board_id 0xff soc_id 0x40170200 > > > > >>>>>>> [ 6.604044] ath12k_pci 0000:63:00.0: fw_version 0x100301e1 > > > > >>>>>>> fw_build_timestamp 2023-12-06 04:05 fw_build_id > > > > >>>>>>> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ- > > > > >>>>>>> > > > > >>>>>>> Also, I noticed when looking through the debug logs there are the > > > > >>>>>>> occasional WARNING statements from a BUG it appears. They trace back > > > > >>>>>>> to the mac.c file inside the ath12k code. There should be some in the > > > > >>>>>>> debug log that's attached. Let me know if I can do anything else. > > > > >>>>>>> Thanks, > > > > >>>>>>> > > > > >>>>>> > > > > >>>>>> > > > > >>>>>> I have never seen this warning on my upstream setup...Not sure if you > > > > >>>>>> have changed anything or using the correct code base. > > > > >>>>>> > > > > >>>>>> Jeff merged this patch-set into ath-202504021602. Can you try on this > > > > >>>>>> branch? > > > > >>>>>> > > > > >>>>>> git clone https://git.kernel.org/pub/scm/linux/kernel/git/ath/ath.git/ > > > > >>>>>> git pull > > > > >>>>>> git reset --hard ath-202504021602 > > > > >>>>>> compile and install... > > > > >>>>>> > > > > >>>>>> Also make sure that the firmware you used is from the same folder, don't > > > > >>>>>> mix with other folders: > > > > >>>>>> linux-firmware/ath12k/WCN7850/hw2.0 > > > > >>>>>> > > > > >>>>>> 1. rmmod/insmod(debug_mask=0xffff) > > > > >>>>>> 2. iw reg get > > > > >>>>>> 3. iw reg set US > > > > >>>>>> 4. iw xxx scan > > > > >>>>>> wait and collect logs. > > > > >>>>>> > > > > >>>>>> don't do anything else. > > > > >>>>>> > > > > >>>>>> > > > > >>>>>> Also, can you show me your AP configuration. > > > > >>>>>> If you have another 6 GHz AP, you can have a try(better different brands). > > > > >>>>>> > > > > >>>> > > > > >>>> Thanks for testing. > > > > >>>> > > > > >>>> Could you share your AP configuration? > > > > >>>> > > > > >>>> > > > > >>>>>> > > > > >>>>>> If you have sniffer, could please capture packets during testing? > > > > >>>> > > > > >>>> > > > > >>>> Can you capture packets during the testing? I need to check probe req > > > > >>>> and probe resp. > > > > >>>> > > > > >>>>>> > > > > >>>>>> Thanks! > > > > >>>>>> > > > > >>>>>>> -Walt > > > > >>>>>> > > > > >>>>> OK, I cloned and built the kernel based on your instructions in your > > > > >>>>> last email. Originally, the result was identical to my last email, > > > > >>>>> including the WARNINGS. The .config I use is configured for a fully RT > > > > >>>>> PREEMPT kernel, which I wondered if that was why I was receiving the > > > > >>>>> WARNING. So I configured it as a Low Latency PREEMPT Desktop without > > > > >>>>> the RT_PREEMPT and that eliminated the WARNING. However, still no 6Ghz > > > > >>>>> networks. The firmware I'm using is straight from kernel.org GIT and I > > > > >>>>> do a 'make install; make dedup' to install it. I believe it should be > > > > >>>>> good. Attached is the latest log file. > > > > >>>>> > > > > >>>>> -Walt > > > > >>>> > > > > >> > > > > > > > > > > > > > > > Sorry for the top-post earlier. I can't figure out how to capture the > > > > > wireless packets as my chip/driver combo doesn't support monitor mode. > > > > > > > > Your AP also cannot capture wireless packets? > > > > log in AP by usbserial or ssh. > > > > Try to enter command line. use iw command to create monitor interface. > > > > Then use tcpdump to capture packets. > > > > > > > > > I've attached a tarball that contains the trace data and additional > > > > > firmware logs from the kernel.log file. Anything else you need, just > > > > > ask. Thanks for your help, > > > > > > > > > > > > Your AP mac address? > > > > Need it to help check the fw log. > > > > > > > > > > > > > > > > > > -Walt > > > > > > > > > > Sorry, the AP doesn't have tcpdump available on it. Also, this is a > > > mesh setup with 3 nodes total. The main AP and 2 mesh nodes. I'm > > > within 10 feet of one of the nodes and it's MAC for the wireless 6ghz > > > network is: 10:7C:61:6F:2A:CA > > > > > > -Walt > > > > The other 2 node 6ghz mac addresses are: > > 10:7C:61:6F:1F:11 - Router > > 10:7C:61:6F:32:92 - Node > > > > The first MAC address I gave you earlier was a node located > > approximately 5 feet from where the laptop is. > > > > -Walt > > Well, I'm running into a brick wall it seems trying to get 6Ghz > enabled on this. I tried the ath-next-20250418 tag just now and still > don't see or connect to my 6Ghz network. I applied the patches in: > https://lore.kernel.org/linux-wireless/20250418-ath12k-6g-lp-vlp-v1-0-c869c86cad60@quicinc.com/T/#t > > hoping that would help, but alas, no 6Ghz networks. I see that MLO and > other nice fixes are coming in 6.16, but without 6Ghz, they'll do me > no good. I'm really wondering if it's a firmware issue that excludes > my chip or something. Again, anything I can do to help, let me know. > Thanks, > > -Walt Well, I used the swiss army tools to look at the firmware, and my chip is listed in the firmware, so it's not excluded or anything. Really puzzlling issue as my other two laptops connect to the 6Ghz network just fine, and this laptop does in Windows, just not in Linux. I really don't use Windows at all though, so that does me no good. This laptop used to connect to the 6Ghz network around the Sep. - Oct. 2024 timeframe. Something has changed and now it doesn't. I'm going to boot off a live image of Ubuntu 24.10 and see if I can see the network. It was always hit or miss so we'll see. -Walt ^ permalink raw reply [flat|nested] 32+ messages in thread
* ath12k-firmware: Module no longer loads with current git firmware 2025-04-20 15:18 ` Walt Holman @ 2025-05-02 7:02 ` Walt Holman 2025-05-06 10:54 ` Baochen Qiang 2025-05-15 8:12 ` ath12k: No 6GHz Wireless found Kang Yang 1 sibling, 1 reply; 32+ messages in thread From: Walt Holman @ 2025-05-02 7:02 UTC (permalink / raw) To: Jeff Johnson; +Cc: linux-wireless, ath12k@lists.infradead.org [-- Attachment #1: Type: text/plain, Size: 428 bytes --] Hello, In my never ending quest for 6ghz WiFi, I saw there was updated firmware posted to the kernel.org linux-firmware GIT repository. However, my ath12k module fails to operate with the updated firmware. I've attached a debug log of the firmware loading logs to this email. I've tried loading in both 6.14.5 just now, and 6.15.0-rc. Is this firmware needing an updated driver that is not in the current stable or RC kernels? [-- Attachment #2: ath12k-firmware-load-log.txt --] [-- Type: text/plain, Size: 41999 bytes --] 2025-05-02T01:51:01.370844-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: BAR 0 [mem 0xdd800000-0xdd9fffff 64bit]: assigned 2025-05-02T01:51:01.370861-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: boot pci_mem 0x0000000058c5a548 2025-05-02T01:51:01.370863-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: pci probe 17cb:1107 1eac:8000 2025-05-02T01:51:01.370864-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: pci tcsr_soc_hw_version major 2 minor 0 2025-05-02T01:51:01.371868-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: MSI vectors: 16 2025-05-02T01:51:01.371871-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: msi base data is 0 2025-05-02T01:51:01.371872-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: Hardware name: wcn7850 hw2.0 2025-05-02T01:51:01.371872-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: failed to load firmware-2.bin: -2 2025-05-02T01:51:01.371873-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: using fw api 1 2025-05-02T01:51:01.371873-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: Assign MSI to user: MHI, num_vectors: 3, user_base_data: 0, base_vector: 0 2025-05-02T01:51:01.371874-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: Number of assigned MSI for MHI is 3, base vector is 0 2025-05-02T01:51:01.372933-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: Assign MSI to user: CE, num_vectors: 5, user_base_data: 3, base_vector: 3 2025-05-02T01:51:01.372935-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: Assign MSI to user: DP, num_vectors: 8, user_base_data: 8, base_vector: 8 2025-05-02T01:51:01.372936-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: irq:119 group:0 2025-05-02T01:51:01.373986-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: irq:120 group:1 2025-05-02T01:51:01.373991-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: irq:121 group:2 2025-05-02T01:51:01.373992-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: irq:122 group:3 2025-05-02T01:51:01.373994-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: irq:123 group:4 2025-05-02T01:51:01.373995-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: irq:124 group:5 2025-05-02T01:51:01.373996-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: irq:125 group:6 2025-05-02T01:51:01.374828-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: pci after request_irq msi_ep_base_data 0 2025-05-02T01:51:01.374831-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: unable to get wsi info from dt, grouping single device 2025-05-02T01:51:01.374831-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: wsi group-id 255 num-devices 1 index 0 2025-05-02T01:51:01.374832-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: num devices 1 num probed 1 2025-05-02T01:51:01.374832-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: pci ltssm 0x111 2025-05-02T01:51:01.374833-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: pci pcie_hot_rst 0xffffffff 2025-05-02T01:51:01.379822-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: cookie:0x0 2025-05-02T01:51:01.379827-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: WLAON_WARM_SW_ENTRY 0x14c4e54 2025-05-02T01:51:01.399829-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: WLAON_WARM_SW_ENTRY 0x14c4e54 2025-05-02T01:51:01.399834-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: soc reset cause:0 2025-05-02T01:51:01.420837-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: MHISTATUS 0xff04 2025-05-02T01:51:01.430841-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: pci link_ctl 0x00c2 L0s 0 L1 1 2025-05-02T01:51:01.430845-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: setting mhi state: INIT(0) 2025-05-02T01:51:01.430846-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: setting mhi state: POWER_ON(2) 2025-05-02T01:51:01.883840-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: mhi notify status reason MHI_CB_EE_MISSION_MODE 2025-05-02T01:51:01.889855-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi wifi fw qmi service connected 2025-05-02T01:51:01.890831-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: phy capability resp valid 1 num_phy 2 valid 0 board_id 0 valid 0 single_chip_mlo_support 0 2025-05-02T01:51:01.891834-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: trigger host cap for device id 0 2025-05-02T01:51:01.891842-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: MLO is disabled hence skip QMI MLO cap 2025-05-02T01:51:01.893839-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi firmware request memory request 2025-05-02T01:51:01.893844-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi mem seg type 1 size 7012352 2025-05-02T01:51:01.893845-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi mem seg type 4 size 8454144 2025-05-02T01:51:01.893847-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi dma allocation failed (7012352 B type 1), will try later with small size 2025-05-02T01:51:01.893848-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi delays mem_request 2 2025-05-02T01:51:01.894841-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi firmware request memory request 2025-05-02T01:51:01.894849-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi mem seg type 1 size 524288 2025-05-02T01:51:01.894855-05:00 walt-ROG-zephyrus kernel: message repeated 6 times: [ ath12k_pci 0000:63:00.0: qmi mem seg type 1 size 524288] 2025-05-02T01:51:01.894855-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi mem seg type 1 size 327680 2025-05-02T01:51:01.894862-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi mem seg type 1 size 524288 2025-05-02T01:51:01.894865-05:00 walt-ROG-zephyrus kernel: message repeated 2 times: [ ath12k_pci 0000:63:00.0: qmi mem seg type 1 size 524288] 2025-05-02T01:51:01.894866-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi mem seg type 1 size 393216 2025-05-02T01:51:01.894867-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi mem seg type 1 size 524288 2025-05-02T01:51:01.894867-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi mem seg type 4 size 524288 2025-05-02T01:51:01.894875-05:00 walt-ROG-zephyrus kernel: message repeated 15 times: [ ath12k_pci 0000:63:00.0: qmi mem seg type 4 size 524288] 2025-05-02T01:51:01.894875-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi mem seg type 4 size 65536 2025-05-02T01:51:01.894876-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi mem seg type 1 size 524288 2025-05-02T01:51:01.895847-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi req mem_seg[0] 0x000000004e980000 524288 1 2025-05-02T01:51:01.895849-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi req mem_seg[1] 0x0000000002200000 524288 1 2025-05-02T01:51:01.895850-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi req mem_seg[2] 0x0000000002280000 524288 1 2025-05-02T01:51:01.895850-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi req mem_seg[3] 0x0000000002300000 524288 1 2025-05-02T01:51:01.895851-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi req mem_seg[4] 0x0000000002380000 524288 1 2025-05-02T01:51:01.895851-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi req mem_seg[5] 0x0000000039000000 524288 1 2025-05-02T01:51:01.895851-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi req mem_seg[6] 0x0000000039080000 524288 1 2025-05-02T01:51:01.895852-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi req mem_seg[7] 0x0000000039100000 327680 1 2025-05-02T01:51:01.895853-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi req mem_seg[8] 0x0000000039180000 524288 1 2025-05-02T01:51:01.895853-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi req mem_seg[9] 0x000000004d400000 524288 1 2025-05-02T01:51:01.895854-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi req mem_seg[10] 0x000000004d480000 524288 1 2025-05-02T01:51:01.895854-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi req mem_seg[11] 0x000000004d500000 393216 1 2025-05-02T01:51:01.895855-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi req mem_seg[12] 0x000000004d580000 524288 1 2025-05-02T01:51:01.895855-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi req mem_seg[13] 0x000000004c800000 524288 4 2025-05-02T01:51:01.895856-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi req mem_seg[14] 0x000000004c880000 524288 4 2025-05-02T01:51:01.895856-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi req mem_seg[15] 0x000000004c900000 524288 4 2025-05-02T01:51:01.895856-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi req mem_seg[16] 0x000000004c980000 524288 4 2025-05-02T01:51:01.895857-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi req mem_seg[17] 0x000000004f200000 524288 4 2025-05-02T01:51:01.895858-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi req mem_seg[18] 0x000000004f280000 524288 4 2025-05-02T01:51:01.895858-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi req mem_seg[19] 0x000000004f300000 524288 4 2025-05-02T01:51:01.895858-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi req mem_seg[20] 0x000000004f380000 524288 4 2025-05-02T01:51:01.895859-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi req mem_seg[21] 0x000000004ec00000 524288 4 2025-05-02T01:51:01.895859-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi req mem_seg[22] 0x000000004ec80000 524288 4 2025-05-02T01:51:01.895860-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi req mem_seg[23] 0x000000004ed00000 524288 4 2025-05-02T01:51:01.895860-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi req mem_seg[24] 0x000000004ed80000 524288 4 2025-05-02T01:51:01.895860-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi req mem_seg[25] 0x000000004ee00000 524288 4 2025-05-02T01:51:01.895861-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi req mem_seg[26] 0x000000004ee80000 524288 4 2025-05-02T01:51:01.895861-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi req mem_seg[27] 0x000000004ef00000 524288 4 2025-05-02T01:51:01.895861-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi req mem_seg[28] 0x000000004ef80000 524288 4 2025-05-02T01:51:01.895862-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi req mem_seg[29] 0x000000004f180000 65536 4 2025-05-02T01:51:01.895862-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi req mem_seg[30] 0x000000004e400000 524288 1 2025-05-02T01:51:01.900841-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi firmware memory ready indication 2025-05-02T01:51:01.901828-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: devmem [0] start 0x113000 size 20480 2025-05-02T01:51:01.901831-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: devmem [1] start 0x0 size 0 2025-05-02T01:51:01.901831-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: devmem [2] start 0x0 size 0 2025-05-02T01:51:01.901832-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: devmem [3] start 0x0 size 0 2025-05-02T01:51:01.901832-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: chip_id 0x2 chip_family 0x4 board_id 0xff soc_id 0x40170200 2025-05-02T01:51:01.901833-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: fw_version 0x1105811c fw_build_timestamp 2025-03-11 07:08 fw_build_id QC_IMAGE_VERSION_STRING=WLAN.HMT.1.1.c5-00284-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3 2025-05-02T01:51:01.901833-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: SMBIOS bdf variant name not set. 2025-05-02T01:51:01.901834-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: boot using board name 'bus=pci,vendor=17cb,device=1107,subsystem-vendor=1eac,subsystem-device=8000,qmi-chip-id=2,qmi-board-id=255' 2025-05-02T01:51:01.904833-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: boot firmware request ath12k/WCN7850/hw2.0/board-2.bin size 1986952 2025-05-02T01:51:01.904838-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: board name 2025-05-02T01:51:01.904838-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: failed to fetch regdb data for bus=pci,vendor=17cb,device=1107,subsystem-vendor=1eac,subsystem-device=8000,qmi-chip-id=2,qmi-board-id=255 from ath12k/WCN7850/hw2.0/board-2.bin 2025-05-02T01:51:01.904839-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: boot using board name 'bus=pci' 2025-05-02T01:51:01.906828-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: boot firmware request ath12k/WCN7850/hw2.0/board-2.bin size 1986952 2025-05-02T01:51:01.906831-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: board name 2025-05-02T01:51:01.906832-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: boot found match regdb data for name 'bus=pci' 2025-05-02T01:51:01.906832-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: boot found regdb data for 'bus=pci' 2025-05-02T01:51:01.906833-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: fetched regdb 2025-05-02T01:51:01.906833-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi bdf_type 4 2025-05-02T01:51:01.906834-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi bdf download req fixed addr type 4 2025-05-02T01:51:01.907874-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi bdf download request remaining 18166 2025-05-02T01:51:01.907879-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi bdf download req fixed addr type 4 2025-05-02T01:51:01.909833-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi bdf download request remaining 12022 2025-05-02T01:51:01.909836-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi bdf download req fixed addr type 4 2025-05-02T01:51:01.910829-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi bdf download request remaining 5878 2025-05-02T01:51:01.910832-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi bdf download req fixed addr type 4 2025-05-02T01:51:01.912829-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi bdf download request remaining 0 2025-05-02T01:51:01.912833-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi BDF download sequence completed 2025-05-02T01:51:01.912833-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: boot using board name 'bus=pci,vendor=17cb,device=1107,subsystem-vendor=1eac,subsystem-device=8000,qmi-chip-id=2,qmi-board-id=255' 2025-05-02T01:51:01.914866-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: boot firmware request ath12k/WCN7850/hw2.0/board-2.bin size 1986952 2025-05-02T01:51:01.914870-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: board name 2025-05-02T01:51:01.914901-05:00 walt-ROG-zephyrus kernel: message repeated 41 times: [ ath12k_pci 0000:63:00.0: board name] 2025-05-02T01:51:01.914902-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: boot found match board data for name 'bus=pci,vendor=17cb,device=1107,subsystem-vendor=1eac,subsystem-device=8000,qmi-chip-id=2,qmi-board-id=255' 2025-05-02T01:51:01.914907-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: boot found board data for 'bus=pci,vendor=17cb,device=1107,subsystem-vendor=1eac,subsystem-device=8000,qmi-chip-id=2,qmi-board-id=255' 2025-05-02T01:51:01.914908-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: using board api 2 2025-05-02T01:51:01.914909-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi bdf_type 1 2025-05-02T01:51:01.914910-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi bdf download req fixed addr type 1 2025-05-02T01:51:01.917843-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi bdf download request remaining 82728 2025-05-02T01:51:01.917846-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi bdf download req fixed addr type 1 2025-05-02T01:51:01.918830-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi bdf download request remaining 76584 2025-05-02T01:51:01.918832-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi bdf download req fixed addr type 1 2025-05-02T01:51:01.920838-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi bdf download request remaining 70440 2025-05-02T01:51:01.920842-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi bdf download req fixed addr type 1 2025-05-02T01:51:01.921830-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi bdf download request remaining 64296 2025-05-02T01:51:01.921833-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi bdf download req fixed addr type 1 2025-05-02T01:51:01.923852-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi bdf download request remaining 58152 2025-05-02T01:51:01.923857-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi bdf download req fixed addr type 1 2025-05-02T01:51:01.924839-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi bdf download request remaining 52008 2025-05-02T01:51:01.924844-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi bdf download req fixed addr type 1 2025-05-02T01:51:01.926843-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi bdf download request remaining 45864 2025-05-02T01:51:01.926845-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi bdf download req fixed addr type 1 2025-05-02T01:51:01.927839-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi bdf download request remaining 39720 2025-05-02T01:51:01.927843-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi bdf download req fixed addr type 1 2025-05-02T01:51:01.929843-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi bdf download request remaining 33576 2025-05-02T01:51:01.929845-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi bdf download req fixed addr type 1 2025-05-02T01:51:01.930842-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi bdf download request remaining 27432 2025-05-02T01:51:01.930845-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi bdf download req fixed addr type 1 2025-05-02T01:51:01.932904-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi bdf download request remaining 21288 2025-05-02T01:51:01.932908-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi bdf download req fixed addr type 1 2025-05-02T01:51:01.933837-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi bdf download request remaining 15144 2025-05-02T01:51:01.933839-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi bdf download req fixed addr type 1 2025-05-02T01:51:01.935853-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi bdf download request remaining 9000 2025-05-02T01:51:01.935857-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi bdf download req fixed addr type 1 2025-05-02T01:51:01.936852-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi bdf download request remaining 2856 2025-05-02T01:51:01.936856-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi bdf download req fixed addr type 1 2025-05-02T01:51:01.949840-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi bdf download request remaining 0 2025-05-02T01:51:01.949846-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi BDF download sequence completed 2025-05-02T01:51:01.949847-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: boot firmware request ath12k/WCN7850/hw2.0/m3.bin size 299660 2025-05-02T01:51:01.956869-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi firmware ready 2025-05-02T01:51:01.956874-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: target_reg a3b04c, shadow reg 0x8fc shadow_idx 0x0, ring_type 0, ring num 0 2025-05-02T01:51:01.956875-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: target_reg a3b054, shadow reg 0x900 shadow_idx 0x1, ring_type 0, ring num 1 2025-05-02T01:51:01.956875-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: target_reg a3b05c, shadow reg 0x904 shadow_idx 0x2, ring_type 0, ring num 2 2025-05-02T01:51:01.956876-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: target_reg a3b064, shadow reg 0x908 shadow_idx 0x3, ring_type 0, ring num 3 2025-05-02T01:51:01.956877-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: target_reg a3b06c, shadow reg 0x90c shadow_idx 0x4, ring_type 0, ring num 4 2025-05-02T01:51:01.956878-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: target_reg a3b074, shadow reg 0x910 shadow_idx 0x5, ring_type 0, ring num 5 2025-05-02T01:51:01.956878-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: target_reg a3b07c, shadow reg 0x914 shadow_idx 0x6, ring_type 0, ring num 6 2025-05-02T01:51:01.956880-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: target_reg a3b084, shadow reg 0x918 shadow_idx 0x7, ring_type 0, ring num 7 2025-05-02T01:51:01.956881-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: target_reg a3b08c, shadow reg 0x91c shadow_idx 0x8, ring_type 1, ring num 0 2025-05-02T01:51:01.956882-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: target_reg a3b028, shadow reg 0x920 shadow_idx 0x9, ring_type 2, ring num 0 2025-05-02T01:51:01.956882-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: target_reg a3b020, shadow reg 0x924 shadow_idx 0xa, ring_type 3, ring num 0 2025-05-02T01:51:01.956883-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: target_reg a3b0ac, shadow reg 0x928 shadow_idx 0xb, ring_type 4, ring num 0 2025-05-02T01:51:01.956884-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: target_reg a46000, shadow reg 0x92c shadow_idx 0xc, ring_type 5, ring num 0 2025-05-02T01:51:01.956885-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: target_reg a46008, shadow reg 0x930 shadow_idx 0xd, ring_type 5, ring num 1 2025-05-02T01:51:01.956885-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: target_reg a46010, shadow reg 0x934 shadow_idx 0xe, ring_type 5, ring num 2 2025-05-02T01:51:01.956886-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: target_reg a46018, shadow reg 0x938 shadow_idx 0xf, ring_type 5, ring num 3 2025-05-02T01:51:01.956887-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: target_reg a46020, shadow reg 0x93c shadow_idx 0x10, ring_type 5, ring num 4 2025-05-02T01:51:01.956887-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: target_reg a46028, shadow reg 0x940 shadow_idx 0x11, ring_type 6, ring num 0 2025-05-02T01:51:01.956888-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: target_reg a4604c, shadow reg 0x944 shadow_idx 0x12, ring_type 7, ring num 0 2025-05-02T01:51:01.956889-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: target_reg a370b8, shadow reg 0x948 shadow_idx 0x13, ring_type 11, ring num 0 2025-05-02T01:51:01.956889-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: target_reg a37010, shadow reg 0x94c shadow_idx 0x14, ring_type 12, ring num 0 2025-05-02T01:51:01.956890-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: target_reg a370cc, shadow reg 0x950 shadow_idx 0x15, ring_type 13, ring num 0 2025-05-02T01:51:01.956891-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: target_reg a370d4, shadow reg 0x954 shadow_idx 0x16, ring_type 13, ring num 1 2025-05-02T01:51:01.956891-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: target_reg a370dc, shadow reg 0x958 shadow_idx 0x17, ring_type 13, ring num 2 2025-05-02T01:51:01.956892-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: target_reg a370e4, shadow reg 0x95c shadow_idx 0x18, ring_type 13, ring num 3 2025-05-02T01:51:01.956893-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: target_reg a370ec, shadow reg 0x960 shadow_idx 0x19, ring_type 13, ring num 4 2025-05-02T01:51:01.956893-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: target_reg a370f4, shadow reg 0x964 shadow_idx 0x1a, ring_type 13, ring num 5 2025-05-02T01:51:01.956894-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: target_reg a370fc, shadow reg 0x968 shadow_idx 0x1b, ring_type 13, ring num 6 2025-05-02T01:51:01.956894-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: target_reg a37104, shadow reg 0x96c shadow_idx 0x1c, ring_type 13, ring num 7 2025-05-02T01:51:01.956895-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: target_reg 1b80400, shadow reg 0x970 shadow_idx 0x1d, ring_type 8, ring num 0 2025-05-02T01:51:01.956896-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: target_reg 1b83400, shadow reg 0x974 shadow_idx 0x1e, ring_type 9, ring num 1 2025-05-02T01:51:01.956896-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: target_reg 1b8340c, shadow reg 0x978 shadow_idx 0x1f, ring_type 10, ring num 1 2025-05-02T01:51:01.956897-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: target_reg 1b85400, shadow reg 0x97c shadow_idx 0x20, ring_type 9, ring num 2 2025-05-02T01:51:01.956898-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: target_reg 1b8540c, shadow reg 0x980 shadow_idx 0x21, ring_type 10, ring num 2 2025-05-02T01:51:01.956898-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: target_reg 1b86400, shadow reg 0x984 shadow_idx 0x22, ring_type 8, ring num 3 2025-05-02T01:51:01.956910-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: target_reg 1b88400, shadow reg 0x988 shadow_idx 0x23, ring_type 8, ring num 4 2025-05-02T01:51:02.001891-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: Assign MSI to user: CE, num_vectors: 5, user_base_data: 3, base_vector: 3 2025-05-02T01:51:02.001911-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: hal type 8 ring_num 0 reg_base 0x1b80400 shadow 0x970 2025-05-02T01:51:02.001912-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: Assign MSI to user: CE, num_vectors: 5, user_base_data: 3, base_vector: 3 2025-05-02T01:51:02.001913-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: hal type 9 ring_num 1 reg_base 0x1b83400 shadow 0x974 2025-05-02T01:51:02.001914-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: Assign MSI to user: CE, num_vectors: 5, user_base_data: 3, base_vector: 3 2025-05-02T01:51:02.001914-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: type 10 ring_num 1 target_reg 0x1b8340c shadow 0x978 2025-05-02T01:51:02.001915-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: Assign MSI to user: CE, num_vectors: 5, user_base_data: 3, base_vector: 3 2025-05-02T01:51:02.001916-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: hal type 9 ring_num 2 reg_base 0x1b85400 shadow 0x97c 2025-05-02T01:51:02.001917-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: Assign MSI to user: CE, num_vectors: 5, user_base_data: 3, base_vector: 3 2025-05-02T01:51:02.001918-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: type 10 ring_num 2 target_reg 0x1b8540c shadow 0x980 2025-05-02T01:51:02.001918-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: Assign MSI to user: CE, num_vectors: 5, user_base_data: 3, base_vector: 3 2025-05-02T01:51:02.001919-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: hal type 8 ring_num 3 reg_base 0x1b86400 shadow 0x984 2025-05-02T01:51:02.001920-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: hal type 8 ring_num 4 reg_base 0x1b88400 shadow 0x988 2025-05-02T01:51:02.001921-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: Assign MSI to user: DP, num_vectors: 8, user_base_data: 8, base_vector: 8 2025-05-02T01:51:02.001922-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: ring not part of an ext_group; ring_type: 11,ring_num 0 2025-05-02T01:51:02.001922-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: hal type 11 ring_num 0 reg_base 0xa370b8 shadow 0x948 2025-05-02T01:51:02.003839-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: Assign MSI to user: DP, num_vectors: 8, user_base_data: 8, base_vector: 8 2025-05-02T01:51:02.003846-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: ring not part of an ext_group; ring_type: 12,ring_num 0 2025-05-02T01:51:02.003847-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: hal type 12 ring_num 0 reg_base 0xa37010 shadow 0x94c 2025-05-02T01:51:02.003847-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: Assign MSI to user: DP, num_vectors: 8, user_base_data: 8, base_vector: 8 2025-05-02T01:51:02.003848-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: ring not part of an ext_group; ring_type: 5,ring_num 0 2025-05-02T01:51:02.003849-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: hal type 5 ring_num 0 reg_base 0xa46000 shadow 0x92c 2025-05-02T01:51:02.003849-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: Assign MSI to user: DP, num_vectors: 8, user_base_data: 8, base_vector: 8 2025-05-02T01:51:02.003850-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: type 13 ring_num 0 target_reg 0xa370cc shadow 0x950 2025-05-02T01:51:02.003851-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: Assign MSI to user: DP, num_vectors: 8, user_base_data: 8, base_vector: 8 2025-05-02T01:51:02.003852-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: ring not part of an ext_group; ring_type: 5,ring_num 1 2025-05-02T01:51:02.003853-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: hal type 5 ring_num 1 reg_base 0xa46008 shadow 0x930 2025-05-02T01:51:02.003854-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: Assign MSI to user: DP, num_vectors: 8, user_base_data: 8, base_vector: 8 2025-05-02T01:51:02.003854-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: type 13 ring_num 2 target_reg 0xa370dc shadow 0x958 2025-05-02T01:51:02.003855-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: Assign MSI to user: DP, num_vectors: 8, user_base_data: 8, base_vector: 8 2025-05-02T01:51:02.003856-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: ring not part of an ext_group; ring_type: 5,ring_num 2 2025-05-02T01:51:02.003856-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: hal type 5 ring_num 2 reg_base 0xa46010 shadow 0x934 2025-05-02T01:51:02.003858-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: Assign MSI to user: DP, num_vectors: 8, user_base_data: 8, base_vector: 8 2025-05-02T01:51:02.003859-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: type 13 ring_num 4 target_reg 0xa370ec shadow 0x960 2025-05-02T01:51:02.003860-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: Assign MSI to user: DP, num_vectors: 8, user_base_data: 8, base_vector: 8 2025-05-02T01:51:02.003861-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: ring not part of an ext_group; ring_type: 2,ring_num 0 2025-05-02T01:51:02.003861-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: hal type 2 ring_num 0 reg_base 0xa3b028 shadow 0x920 2025-05-02T01:51:02.003862-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: Assign MSI to user: DP, num_vectors: 8, user_base_data: 8, base_vector: 8 2025-05-02T01:51:02.003864-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: type 13 ring_num 3 target_reg 0xa370e4 shadow 0x95c 2025-05-02T01:51:02.003878-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: Assign MSI to user: DP, num_vectors: 8, user_base_data: 8, base_vector: 8 2025-05-02T01:51:02.003879-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: type 1 ring_num 0 target_reg 0xa3b08c shadow 0x91c 2025-05-02T01:51:02.003880-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: Assign MSI to user: DP, num_vectors: 8, user_base_data: 8, base_vector: 8 2025-05-02T01:51:02.003881-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: ring not part of an ext_group; ring_type: 3,ring_num 0 2025-05-02T01:51:02.003882-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: hal type 3 ring_num 0 reg_base 0xa3b020 shadow 0x924 2025-05-02T01:51:02.003883-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: Assign MSI to user: DP, num_vectors: 8, user_base_data: 8, base_vector: 8 2025-05-02T01:51:02.003883-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: type 4 ring_num 0 target_reg 0xa3b0ac shadow 0x928 2025-05-02T01:51:02.004833-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: Assign MSI to user: DP, num_vectors: 8, user_base_data: 8, base_vector: 8 2025-05-02T01:51:02.004839-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: ring not part of an ext_group; ring_type: 14,ring_num 0 2025-05-02T01:51:02.004840-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: Assign MSI to user: DP, num_vectors: 8, user_base_data: 8, base_vector: 8 2025-05-02T01:51:02.004841-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: ring not part of an ext_group; ring_type: 14,ring_num 1 2025-05-02T01:51:02.004841-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: Assign MSI to user: DP, num_vectors: 8, user_base_data: 8, base_vector: 8 2025-05-02T01:51:02.004842-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: ring not part of an ext_group; ring_type: 14,ring_num 2 2025-05-02T01:51:02.004842-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: Assign MSI to user: DP, num_vectors: 8, user_base_data: 8, base_vector: 8 2025-05-02T01:51:02.004842-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: ring not part of an ext_group; ring_type: 15,ring_num 0 2025-05-02T01:51:02.009495-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: boot htc service 'Control' ul pipe 0 dl pipe 2 eid 0 ready 2025-05-02T01:51:02.009501-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: boot htc service 'Control' eid 0 TX flow control disabled 2025-05-02T01:51:02.009502-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: rx ce pipe 2 len 20 2025-05-02T01:51:02.009504-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: Target ready! transmit resources: 2 size:2176 2025-05-02T01:51:02.009504-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: boot htc service HTT Data does not allocate target credits 2025-05-02T01:51:02.009666-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: rx ce pipe 2 len 20 2025-05-02T01:51:02.009674-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: HTC Service HTT Data connect response: status: 0, assigned ep: 1 2025-05-02T01:51:02.009674-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: boot htc service 'HTT Data' ul pipe 4 dl pipe 1 eid 1 ready 2025-05-02T01:51:02.009675-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: boot htc service 'HTT Data' eid 1 TX flow control disabled 2025-05-02T01:51:02.009857-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: rx ce pipe 2 len 20 2025-05-02T01:51:02.009870-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: HTC Service WMI connect response: status: 0, assigned ep: 2 2025-05-02T01:51:02.009871-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: boot htc service 'WMI' ul pipe 3 dl pipe 2 eid 2 ready 2025-05-02T01:51:02.009872-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: HTC is using TX credit flow control 2025-05-02T01:51:02.010324-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: rx ce pipe 2 len 72 2025-05-02T01:51:02.010331-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: htc rx completion ep 2 skb 0000000003e9f059 2025-05-02T01:51:02.010332-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: wmi_ext_service_bitmap 0xdf75f488 0x2dd6902 0x7c78f15e 0x6efdf615 2025-05-02T01:51:02.010333-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: wmi_ext2_service_bitmap 0xe3f8ea2e 0x8f550403 0x52eee356 0x8c85034 2025-05-02T01:51:02.010847-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: rx ce pipe 2 len 356 2025-05-02T01:51:02.010854-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: htc rx completion ep 2 skb 00000000fe08b327 2025-05-02T01:51:02.010855-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: rx ce pipe 2 len 1588 2025-05-02T01:51:02.010856-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: htc rx completion ep 2 skb 00000000ae3a5a43 2025-05-02T01:51:02.010857-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: preferred_hw_mode:5 2025-05-02T01:51:02.011264-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: rx ce pipe 2 len 1300 2025-05-02T01:51:02.011272-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: htc rx completion ep 2 skb 000000003d17c8ed 2025-05-02T01:51:02.011846-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: Assign MSI to user: DP, num_vectors: 8, user_base_data: 8, base_vector: 8 2025-05-02T01:51:02.011858-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: type 0 ring_num 0 target_reg 0xa3b04c shadow 0x8fc 2025-05-02T01:51:02.011859-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: Assign MSI to user: DP, num_vectors: 8, user_base_data: 8, base_vector: 8 2025-05-02T01:51:02.011860-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: type 0 ring_num 1 target_reg 0xa3b054 shadow 0x900 2025-05-02T01:51:02.011861-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: Assign MSI to user: DP, num_vectors: 8, user_base_data: 8, base_vector: 8 2025-05-02T01:51:02.011862-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: type 0 ring_num 2 target_reg 0xa3b05c shadow 0x904 2025-05-02T01:51:02.011863-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: Assign MSI to user: DP, num_vectors: 8, user_base_data: 8, base_vector: 8 2025-05-02T01:51:02.011865-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: type 0 ring_num 3 target_reg 0xa3b064 shadow 0x908 2025-05-02T01:51:02.011866-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: Assign MSI to user: DP, num_vectors: 8, user_base_data: 8, base_vector: 8 2025-05-02T01:51:02.011867-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: ring not part of an ext_group; ring_type: 0,ring_num 4 2025-05-02T01:51:02.011867-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: type 0 ring_num 4 target_reg 0xa3b06c shadow 0x90c 2025-05-02T01:51:02.011868-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: Assign MSI to user: DP, num_vectors: 8, user_base_data: 8, base_vector: 8 2025-05-02T01:51:02.011869-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: ring not part of an ext_group; ring_type: 0,ring_num 5 2025-05-02T01:51:02.011870-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: type 0 ring_num 5 target_reg 0xa3b074 shadow 0x910 2025-05-02T01:51:02.011871-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: Assign MSI to user: DP, num_vectors: 8, user_base_data: 8, base_vector: 8 2025-05-02T01:51:02.011872-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: ring not part of an ext_group; ring_type: 0,ring_num 6 2025-05-02T01:51:02.011873-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: type 0 ring_num 6 target_reg 0xa3b07c shadow 0x914 2025-05-02T01:51:02.011874-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: Assign MSI to user: DP, num_vectors: 8, user_base_data: 8, base_vector: 8 2025-05-02T01:51:02.011874-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: ring not part of an ext_group; ring_type: 0,ring_num 7 2025-05-02T01:51:02.011885-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: type 0 ring_num 7 target_reg 0xa3b084 shadow 0x918 2025-05-02T01:51:02.011886-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: htc ep 2 consumed 1 credits (total 1) 2025-05-02T01:51:02.016667-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: rx ce pipe 2 len 24 2025-05-02T01:51:02.016674-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: htc rx completion ep 2 skb 00000000a0e05761 2025-05-02T01:51:02.016675-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: Unknown eventid: 0x16005 2025-05-02T01:51:02.188857-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: mhi notify status reason MHI_CB_EE_RDDM 2025-05-02T01:51:02.188872-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: ignore reset dev flags 0x200 2025-05-02T01:51:02.387859-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: mhi notify status reason MHI_CB_EE_RDDM 2025-05-02T01:51:02.387874-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: do not queue again for consecutive RDDM event 2025-05-02T01:51:07.149855-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: failed to receive wmi unified ready event: -110 2025-05-02T01:51:07.149874-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: failed to start core: -110 2025-05-02T01:51:07.151862-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi failed to send mode request, mode: 4, err = -5 2025-05-02T01:51:07.151863-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi failed to send wlan mode off 2025-05-02T01:51:53.469883-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi failed to send mode request, mode: 4, err = -5 2025-05-02T01:51:53.469886-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi failed to send wlan mode off 2025-05-02T01:51:53.474939-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: setting mhi state: POWER_OFF(3) 2025-05-02T01:51:53.474955-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: qmi wifi fw del server 2025-05-02T01:51:53.474956-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: setting mhi state: DEINIT(1) 2025-05-02T01:51:53.474957-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: cookie:0x0 2025-05-02T01:51:53.474958-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: WLAON_WARM_SW_ENTRY 0x14b6e64 2025-05-02T01:51:53.494845-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: WLAON_WARM_SW_ENTRY 0x14b6e64 2025-05-02T01:51:53.494856-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: soc reset cause:0 2025-05-02T01:51:53.514843-05:00 walt-ROG-zephyrus kernel: ath12k_pci 0000:63:00.0: MHISTATUS 0xff04 ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ath12k-firmware: Module no longer loads with current git firmware 2025-05-02 7:02 ` ath12k-firmware: Module no longer loads with current git firmware Walt Holman @ 2025-05-06 10:54 ` Baochen Qiang 0 siblings, 0 replies; 32+ messages in thread From: Baochen Qiang @ 2025-05-06 10:54 UTC (permalink / raw) To: Walt Holman, Jeff Johnson; +Cc: linux-wireless, ath12k@lists.infradead.org On 5/2/2025 3:02 PM, Walt Holman wrote: > Hello, > > In my never ending quest for 6ghz WiFi, I saw there was updated > firmware posted to the kernel.org linux-firmware GIT repository. > However, my ath12k module fails to operate with the updated firmware. > I've attached a debug log of the firmware loading logs to this email. > I've tried loading in both 6.14.5 just now, and 6.15.0-rc. Is this > firmware needing an updated driver that is not in the current stable > or RC kernels? recently we got several similar reports, we are checking into this. will update later. ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ath12k: No 6GHz Wireless found 2025-04-20 15:18 ` Walt Holman 2025-05-02 7:02 ` ath12k-firmware: Module no longer loads with current git firmware Walt Holman @ 2025-05-15 8:12 ` Kang Yang 2025-05-15 9:22 ` Kang Yang 1 sibling, 1 reply; 32+ messages in thread From: Kang Yang @ 2025-05-15 8:12 UTC (permalink / raw) To: Walt Holman; +Cc: Jeff Johnson, linux-wireless, ath12k@lists.infradead.org On 4/20/2025 11:18 PM, Walt Holman wrote: > On Fri, Apr 18, 2025 at 4:18 PM Walt Holman <waltholman09@gmail.com> wrote: >> On Tue, Apr 15, 2025 at 4:23 PM Walt Holman <waltholman09@gmail.com> wrote: >>> On Thu, Apr 10, 2025 at 10:32 AM Walt Holman <waltholman09@gmail.com> wrote: >>>> On Thu, Apr 10, 2025 at 3:26 AM Kang Yang <kang.yang@oss.qualcomm.com> wrote: >>>>> >>>>> >>>>> On 4/10/2025 3:37 AM, Walt Holman wrote: >>>>>> On Tue, Apr 8, 2025 at 4:17 AM Kang Yang <quic_kangyang@quicinc.com> wrote: >>>>>>> >>>>>>> >>>>>>> On 4/8/2025 1:49 AM, Walt Holman wrote: >>>>>>>> Attached is a small packet capture where I did an 'iw wlp99s0 scan' >>>>>>>> and also deactivated and reactivated wireless while the scan was >>>>>>>> ongoing. Hopefully there's something interesting for you in there. >>>>>>>> Also, I've take 3 screenshots showing the configs of the wireless AP >>>>>>>> for the 6ghz network. The first screen is just the definition of the >>>>>>>> network. No advanced settings are used. The 2nd screen shows the >>>>>>>> channels and radio enabled. The 3rd screen has the advanced >>>>>>>> (professional) settings for the network. I believe I changed 'Agile >>>>>>>> Multiband' to enabled, but other settings are their defaults. Hope >>>>>>>> some of this helps. Let me know if you need anything else. Thanks, >>>>>>>> >>>>>>> Your packets are Ethernet packets. I need wireless packets. >>>>>>> >>>>>>> >>>>>>> Not sure if you know how to add a seperate monitor interface to capture >>>>>>> 6 G channels' packet on your AP(you can google for specific command). >>>>>>> >>>>>>> >>>>>>> Also, please capture firmware log: >>>>>>> >>>>>>> 1. sudo apt install trace-cmd >>>>>>> 2. sudo trace-cmd record -e ath12k_wmi_diag >>>>>>> 3. run test >>>>>>> 4. "ctrl c" to stop recording: >>>>>>> Hit Ctrl^C to stop recording >>>>>>> ^CCPU0 data recorded at offset=0xdf5000 >>>>>>> 2605056 bytes in size >>>>>>> Then share the trace.dat to us. >>>>>>> >>>>>>> So you need to: >>>>>>> 1. try to capture wireless packets. >>>>>>> 2. capture firmware log(trade.data). >>>>>>> 3. save kernel/wpa_supplicant/iw logs. >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>>> -Walt >>>>>>>> >>>>>>>> On Sun, Apr 6, 2025 at 8:58 PM Kang Yang <quic_kangyang@quicinc.com> wrote: >>>>>>>>> >>>>>>>>> >>>>>>>>> On 4/4/2025 12:04 AM, Walt Holman wrote: >>>>>>>>>> On Thu, Apr 3, 2025 at 3:20 AM Kang Yang <quic_kangyang@quicinc.com> wrote: >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On 4/3/2025 1:48 AM, Walt Holman wrote: >>>>>>>>>>>> On Tue, Apr 1, 2025 at 9:48 PM Kang Yang <quic_kangyang@quicinc.com> wrote: >>>>>>>>>>>>> Test on 6.14.0-rc5-wt-ath+, with the firmware you used. >>>>>>>>>>>>> I can get 6 GHz AP and connect to it. >>>>>>>>>>>>> >>>>>>>>>>>>> ath12k_pci 0000:03:00.0: fw_version 0x100301e1 fw_build_timestamp >>>>>>>>>>>>> 2023-12-06 04:05 fw_build_id >>>>>>>>>>>>> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3 >>>>>>>>>>>>> >>>>>>>>>>>>> yk@yk-Mayan:~$ sudo iw wls1 scan | tee iw_scan.log: >>>>>>>>>>>>> BSS 62:03:7f:12:64:64(on wls1) -- associated >>>>>>>>>>>>> TSF: 606308271476 usec (7d, 00:25:08) >>>>>>>>>>>>> freq: 6275 >>>>>>>>>>>>> beacon interval: 100 TUs >>>>>>>>>>>>> capability: ESS Privacy SpectrumMgmt ShortSlotTime (0x0511) >>>>>>>>>>>>> signal: -17.00 dBm >>>>>>>>>>>>> last seen: 52 ms ago >>>>>>>>>>>>> Information elements from Probe Response frame: >>>>>>>>>>>>> SSID: MLO-KANG-6G >>>>>>>>>>>>> and other 6 GHz APs: >>>>>>>>>>>>> SSID: 6G-gxia >>>>>>>>>>>>> SSID: NETGEAR97-6G >>>>>>>>>>>>> …… >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> kernel log: >>>>>>>>>>>>> [88158.033218] wls1: Inserted STA 62:03:7f:12:64:64 >>>>>>>>>>>>> [88158.033232] wls1: authenticate with 62:03:7f:12:64:64 (local >>>>>>>>>>>>> address=00:03:7f:37:12:54) >>>>>>>>>>>>> [88158.033242] wls1: send auth to 62:03:7f:12:64:64 (try 1/3) >>>>>>>>>>>>> [88158.041895] wls1: authenticated >>>>>>>>>>>>> [88158.041914] wls1: moving STA 62:03:7f:12:64:64 to state 2 >>>>>>>>>>>>> [88158.044291] wls1: determined local STA to be EHT, BW limited to 320 MHz >>>>>>>>>>>>> [88158.045719] wls1: associate with 62:03:7f:12:64:64 (try 1/3) >>>>>>>>>>>>> [88158.067045] wls1: RX AssocResp from 62:03:7f:12:64:64 (capab=0x511 >>>>>>>>>>>>> status=0 aid=4) >>>>>>>>>>>>> [88158.089090] wls1: associated >>>>>>>>>>>>> >>>>>>>>>>>>> I can even connect to it by Ubuntu GUI. >>>>>>>>>>>>> >>>>>>>>>>>>> Can you update to 6.14.0-rc5-wt-ath+ and have a retry? Also please make >>>>>>>>>>>>> sure that your wpa_supplicant/iw support 6 GHz(or directly update to the >>>>>>>>>>>>> latest version). >>>>>>>>>>>>> >>>>>>>>>>>>> If you still cannot find 6 GHz AP, you can set debug_mask to 0xffffffff >>>>>>>>>>>>> to get ath12k logs. Then give it to us. >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>>> -Walt >>>>>>>>>>>>>> >>>>>>>>>>>> OK, I retested with the wt-ath 033125 tagged build. This included the >>>>>>>>>>>> patch the Jeff suggested I try, but the rest of the tree was clean. >>>>>>>>>>>> Still no 6ghz Wifi. I'm attaching a log file of the boot and first few >>>>>>>>>>>> seconds with the debug mask turned on. I noticed that if I rmmod the >>>>>>>>>>>> module and then modprobe it, it complains about not finding >>>>>>>>>>>> firmware-2.bin, however, I thought that was only for the qcn based >>>>>>>>>>>> chip? The HW info from dmesg looks like this: >>>>>>>>>>>> >>>>>>>>>>> I cannot find this tag... >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> From the log, the 6 GHz channel should work. When scan is triggered, FW >>>>>>>>>>> shall send probe req on these channels. If AP send probe resp, station >>>>>>>>>>> shall find the AP. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> [ 6.070282] ath12k_pci 0000:63:00.0: BAR 0 [mem >>>>>>>>>>>> 0xdd800000-0xdd9fffff 64bit]: assigned >>>>>>>>>>>> [ 6.070310] ath12k_pci 0000:63:00.0: enabling device (0000 -> 0002) >>>>>>>>>>>> [ 6.071249] ath12k_pci 0000:63:00.0: MSI vectors: 16 >>>>>>>>>>>> [ 6.071254] ath12k_pci 0000:63:00.0: Hardware name: wcn7850 hw2.0 >>>>>>>>>>>> [ 6.596331] ath12k_pci 0000:63:00.0: qmi dma allocation failed >>>>>>>>>>>> (7077888 B type 1), will try later with sma >>>>>>>>>>>> ll size >>>>>>>>>>>> [ 6.604041] ath12k_pci 0000:63:00.0: chip_id 0x2 chip_family 0x4 >>>>>>>>>>>> board_id 0xff soc_id 0x40170200 >>>>>>>>>>>> [ 6.604044] ath12k_pci 0000:63:00.0: fw_version 0x100301e1 >>>>>>>>>>>> fw_build_timestamp 2023-12-06 04:05 fw_build_id >>>>>>>>>>>> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ- >>>>>>>>>>>> >>>>>>>>>>>> Also, I noticed when looking through the debug logs there are the >>>>>>>>>>>> occasional WARNING statements from a BUG it appears. They trace back >>>>>>>>>>>> to the mac.c file inside the ath12k code. There should be some in the >>>>>>>>>>>> debug log that's attached. Let me know if I can do anything else. >>>>>>>>>>>> Thanks, >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> I have never seen this warning on my upstream setup...Not sure if you >>>>>>>>>>> have changed anything or using the correct code base. >>>>>>>>>>> >>>>>>>>>>> Jeff merged this patch-set into ath-202504021602. Can you try on this >>>>>>>>>>> branch? >>>>>>>>>>> >>>>>>>>>>> git clone https://git.kernel.org/pub/scm/linux/kernel/git/ath/ath.git/ >>>>>>>>>>> git pull >>>>>>>>>>> git reset --hard ath-202504021602 >>>>>>>>>>> compile and install... >>>>>>>>>>> >>>>>>>>>>> Also make sure that the firmware you used is from the same folder, don't >>>>>>>>>>> mix with other folders: >>>>>>>>>>> linux-firmware/ath12k/WCN7850/hw2.0 >>>>>>>>>>> >>>>>>>>>>> 1. rmmod/insmod(debug_mask=0xffff) >>>>>>>>>>> 2. iw reg get >>>>>>>>>>> 3. iw reg set US >>>>>>>>>>> 4. iw xxx scan >>>>>>>>>>> wait and collect logs. >>>>>>>>>>> >>>>>>>>>>> don't do anything else. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Also, can you show me your AP configuration. >>>>>>>>>>> If you have another 6 GHz AP, you can have a try(better different brands). >>>>>>>>>>> >>>>>>>>> Thanks for testing. >>>>>>>>> >>>>>>>>> Could you share your AP configuration? >>>>>>>>> >>>>>>>>> >>>>>>>>>>> If you have sniffer, could please capture packets during testing? >>>>>>>>> >>>>>>>>> Can you capture packets during the testing? I need to check probe req >>>>>>>>> and probe resp. >>>>>>>>> >>>>>>>>>>> Thanks! >>>>>>>>>>> >>>>>>>>>>>> -Walt >>>>>>>>>> OK, I cloned and built the kernel based on your instructions in your >>>>>>>>>> last email. Originally, the result was identical to my last email, >>>>>>>>>> including the WARNINGS. The .config I use is configured for a fully RT >>>>>>>>>> PREEMPT kernel, which I wondered if that was why I was receiving the >>>>>>>>>> WARNING. So I configured it as a Low Latency PREEMPT Desktop without >>>>>>>>>> the RT_PREEMPT and that eliminated the WARNING. However, still no 6Ghz >>>>>>>>>> networks. The firmware I'm using is straight from kernel.org GIT and I >>>>>>>>>> do a 'make install; make dedup' to install it. I believe it should be >>>>>>>>>> good. Attached is the latest log file. >>>>>>>>>> >>>>>>>>>> -Walt >>>>>> >>>>>> Sorry for the top-post earlier. I can't figure out how to capture the >>>>>> wireless packets as my chip/driver combo doesn't support monitor mode. >>>>> Your AP also cannot capture wireless packets? >>>>> log in AP by usbserial or ssh. >>>>> Try to enter command line. use iw command to create monitor interface. >>>>> Then use tcpdump to capture packets. >>>>> >>>>>> I've attached a tarball that contains the trace data and additional >>>>>> firmware logs from the kernel.log file. Anything else you need, just >>>>>> ask. Thanks for your help, >>>>> >>>>> Your AP mac address? >>>>> Need it to help check the fw log. >>>>> >>>>> >>>>>> -Walt >>>> Sorry, the AP doesn't have tcpdump available on it. Also, this is a >>>> mesh setup with 3 nodes total. The main AP and 2 mesh nodes. I'm >>>> within 10 feet of one of the nodes and it's MAC for the wireless 6ghz >>>> network is: 10:7C:61:6F:2A:CA >>>> >>>> -Walt >>> The other 2 node 6ghz mac addresses are: >>> 10:7C:61:6F:1F:11 - Router >>> 10:7C:61:6F:32:92 - Node >>> >>> The first MAC address I gave you earlier was a node located >>> approximately 5 feet from where the laptop is. >>> >>> -Walt >> Well, I'm running into a brick wall it seems trying to get 6Ghz >> enabled on this. I tried the ath-next-20250418 tag just now and still >> don't see or connect to my 6Ghz network. I applied the patches in: >> https://lore.kernel.org/linux-wireless/20250418-ath12k-6g-lp-vlp-v1-0-c869c86cad60@quicinc.com/T/#t >> >> hoping that would help, but alas, no 6Ghz networks. I see that MLO and >> other nice fixes are coming in 6.16, but without 6Ghz, they'll do me >> no good. I'm really wondering if it's a firmware issue that excludes >> my chip or something. Again, anything I can do to help, let me know. >> Thanks, >> >> -Walt > Well, I used the swiss army tools to look at the firmware, and my chip > is listed in the firmware, so it's not excluded or anything. Really > puzzlling issue as my other two laptops connect to the 6Ghz network > just fine, and this laptop does in Windows, just not in Linux. I > really don't use Windows at all though, so that does me no good. > > This laptop used to connect to the 6Ghz network around the Sep. - Oct. > 2024 timeframe. Something has changed and now it doesn't. I'm going to > boot off a live image of Ubuntu 24.10 and see if I can see the > network. It was always hit or miss so we'll see. > -Walt Can you find 6 GHz AP now? ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ath12k: No 6GHz Wireless found 2025-05-15 8:12 ` ath12k: No 6GHz Wireless found Kang Yang @ 2025-05-15 9:22 ` Kang Yang 2025-05-15 17:47 ` Walt Holman 0 siblings, 1 reply; 32+ messages in thread From: Kang Yang @ 2025-05-15 9:22 UTC (permalink / raw) To: Walt Holman; +Cc: Jeff Johnson, linux-wireless, ath12k@lists.infradead.org On 5/15/2025 4:12 PM, Kang Yang wrote: > > On 4/20/2025 11:18 PM, Walt Holman wrote: >> On Fri, Apr 18, 2025 at 4:18 PM Walt Holman <waltholman09@gmail.com> >> wrote: >>> On Tue, Apr 15, 2025 at 4:23 PM Walt Holman <waltholman09@gmail.com> >>> wrote: >>>> On Thu, Apr 10, 2025 at 10:32 AM Walt Holman >>>> <waltholman09@gmail.com> wrote: >>>>> On Thu, Apr 10, 2025 at 3:26 AM Kang Yang >>>>> <kang.yang@oss.qualcomm.com> wrote: >>>>>> >>>>>> >>>>>> On 4/10/2025 3:37 AM, Walt Holman wrote: >>>>>>> On Tue, Apr 8, 2025 at 4:17 AM Kang Yang >>>>>>> <quic_kangyang@quicinc.com> wrote: >>>>>>>> >>>>>>>> >>>>>>>> On 4/8/2025 1:49 AM, Walt Holman wrote: >>>>>>>>> Attached is a small packet capture where I did an 'iw wlp99s0 >>>>>>>>> scan' >>>>>>>>> and also deactivated and reactivated wireless while the scan was >>>>>>>>> ongoing. Hopefully there's something interesting for you in there. >>>>>>>>> Also, I've take 3 screenshots showing the configs of the >>>>>>>>> wireless AP >>>>>>>>> for the 6ghz network. The first screen is just the definition >>>>>>>>> of the >>>>>>>>> network. No advanced settings are used. The 2nd screen shows the >>>>>>>>> channels and radio enabled. The 3rd screen has the advanced >>>>>>>>> (professional) settings for the network. I believe I changed >>>>>>>>> 'Agile >>>>>>>>> Multiband' to enabled, but other settings are their defaults. Hope >>>>>>>>> some of this helps. Let me know if you need anything else. Thanks, >>>>>>>>> >>>>>>>> Your packets are Ethernet packets. I need wireless packets. >>>>>>>> >>>>>>>> >>>>>>>> Not sure if you know how to add a seperate monitor interface to >>>>>>>> capture >>>>>>>> 6 G channels' packet on your AP(you can google for specific >>>>>>>> command). >>>>>>>> >>>>>>>> >>>>>>>> Also, please capture firmware log: >>>>>>>> >>>>>>>> 1. sudo apt install trace-cmd >>>>>>>> 2. sudo trace-cmd record -e ath12k_wmi_diag >>>>>>>> 3. run test >>>>>>>> 4. "ctrl c" to stop recording: >>>>>>>> Hit Ctrl^C to stop recording >>>>>>>> ^CCPU0 data recorded at offset=0xdf5000 >>>>>>>> 2605056 bytes in size >>>>>>>> Then share the trace.dat to us. >>>>>>>> >>>>>>>> So you need to: >>>>>>>> 1. try to capture wireless packets. >>>>>>>> 2. capture firmware log(trade.data). >>>>>>>> 3. save kernel/wpa_supplicant/iw logs. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> -Walt >>>>>>>>> >>>>>>>>> On Sun, Apr 6, 2025 at 8:58 PM Kang Yang >>>>>>>>> <quic_kangyang@quicinc.com> wrote: >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On 4/4/2025 12:04 AM, Walt Holman wrote: >>>>>>>>>>> On Thu, Apr 3, 2025 at 3:20 AM Kang Yang >>>>>>>>>>> <quic_kangyang@quicinc.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On 4/3/2025 1:48 AM, Walt Holman wrote: >>>>>>>>>>>>> On Tue, Apr 1, 2025 at 9:48 PM Kang Yang >>>>>>>>>>>>> <quic_kangyang@quicinc.com> wrote: >>>>>>>>>>>>>> Test on 6.14.0-rc5-wt-ath+, with the firmware you used. >>>>>>>>>>>>>> I can get 6 GHz AP and connect to it. >>>>>>>>>>>>>> >>>>>>>>>>>>>> ath12k_pci 0000:03:00.0: fw_version 0x100301e1 >>>>>>>>>>>>>> fw_build_timestamp >>>>>>>>>>>>>> 2023-12-06 04:05 fw_build_id >>>>>>>>>>>>>> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481- >>>>>>>>>>>>>> QCAHMTSWPL_V1.0_V2.0_SILICONZ-3 >>>>>>>>>>>>>> >>>>>>>>>>>>>> yk@yk-Mayan:~$ sudo iw wls1 scan | tee iw_scan.log: >>>>>>>>>>>>>> BSS 62:03:7f:12:64:64(on wls1) -- associated >>>>>>>>>>>>>> TSF: 606308271476 usec (7d, 00:25:08) >>>>>>>>>>>>>> freq: 6275 >>>>>>>>>>>>>> beacon interval: 100 TUs >>>>>>>>>>>>>> capability: ESS Privacy SpectrumMgmt >>>>>>>>>>>>>> ShortSlotTime (0x0511) >>>>>>>>>>>>>> signal: -17.00 dBm >>>>>>>>>>>>>> last seen: 52 ms ago >>>>>>>>>>>>>> Information elements from Probe Response frame: >>>>>>>>>>>>>> SSID: MLO-KANG-6G >>>>>>>>>>>>>> and other 6 GHz APs: >>>>>>>>>>>>>> SSID: 6G-gxia >>>>>>>>>>>>>> SSID: NETGEAR97-6G >>>>>>>>>>>>>> …… >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> kernel log: >>>>>>>>>>>>>> [88158.033218] wls1: Inserted STA 62:03:7f:12:64:64 >>>>>>>>>>>>>> [88158.033232] wls1: authenticate with 62:03:7f:12:64:64 >>>>>>>>>>>>>> (local >>>>>>>>>>>>>> address=00:03:7f:37:12:54) >>>>>>>>>>>>>> [88158.033242] wls1: send auth to 62:03:7f:12:64:64 (try 1/3) >>>>>>>>>>>>>> [88158.041895] wls1: authenticated >>>>>>>>>>>>>> [88158.041914] wls1: moving STA 62:03:7f:12:64:64 to state 2 >>>>>>>>>>>>>> [88158.044291] wls1: determined local STA to be EHT, BW >>>>>>>>>>>>>> limited to 320 MHz >>>>>>>>>>>>>> [88158.045719] wls1: associate with 62:03:7f:12:64:64 (try >>>>>>>>>>>>>> 1/3) >>>>>>>>>>>>>> [88158.067045] wls1: RX AssocResp from 62:03:7f:12:64:64 >>>>>>>>>>>>>> (capab=0x511 >>>>>>>>>>>>>> status=0 aid=4) >>>>>>>>>>>>>> [88158.089090] wls1: associated >>>>>>>>>>>>>> >>>>>>>>>>>>>> I can even connect to it by Ubuntu GUI. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Can you update to 6.14.0-rc5-wt-ath+ and have a retry? >>>>>>>>>>>>>> Also please make >>>>>>>>>>>>>> sure that your wpa_supplicant/iw support 6 GHz(or directly >>>>>>>>>>>>>> update to the >>>>>>>>>>>>>> latest version). >>>>>>>>>>>>>> >>>>>>>>>>>>>> If you still cannot find 6 GHz AP, you can set debug_mask >>>>>>>>>>>>>> to 0xffffffff >>>>>>>>>>>>>> to get ath12k logs. Then give it to us. >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>>> -Walt >>>>>>>>>>>>>>> >>>>>>>>>>>>> OK, I retested with the wt-ath 033125 tagged build. This >>>>>>>>>>>>> included the >>>>>>>>>>>>> patch the Jeff suggested I try, but the rest of the tree >>>>>>>>>>>>> was clean. >>>>>>>>>>>>> Still no 6ghz Wifi. I'm attaching a log file of the boot >>>>>>>>>>>>> and first few >>>>>>>>>>>>> seconds with the debug mask turned on. I noticed that if I >>>>>>>>>>>>> rmmod the >>>>>>>>>>>>> module and then modprobe it, it complains about not finding >>>>>>>>>>>>> firmware-2.bin, however, I thought that was only for the >>>>>>>>>>>>> qcn based >>>>>>>>>>>>> chip? The HW info from dmesg looks like this: >>>>>>>>>>>>> >>>>>>>>>>>> I cannot find this tag... >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> From the log, the 6 GHz channel should work. When scan >>>>>>>>>>>> is triggered, FW >>>>>>>>>>>> shall send probe req on these channels. If AP send probe >>>>>>>>>>>> resp, station >>>>>>>>>>>> shall find the AP. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>>> [ 6.070282] ath12k_pci 0000:63:00.0: BAR 0 [mem >>>>>>>>>>>>> 0xdd800000-0xdd9fffff 64bit]: assigned >>>>>>>>>>>>> [ 6.070310] ath12k_pci 0000:63:00.0: enabling device >>>>>>>>>>>>> (0000 -> 0002) >>>>>>>>>>>>> [ 6.071249] ath12k_pci 0000:63:00.0: MSI vectors: 16 >>>>>>>>>>>>> [ 6.071254] ath12k_pci 0000:63:00.0: Hardware name: >>>>>>>>>>>>> wcn7850 hw2.0 >>>>>>>>>>>>> [ 6.596331] ath12k_pci 0000:63:00.0: qmi dma allocation >>>>>>>>>>>>> failed >>>>>>>>>>>>> (7077888 B type 1), will try later with sma >>>>>>>>>>>>> ll size >>>>>>>>>>>>> [ 6.604041] ath12k_pci 0000:63:00.0: chip_id 0x2 >>>>>>>>>>>>> chip_family 0x4 >>>>>>>>>>>>> board_id 0xff soc_id 0x40170200 >>>>>>>>>>>>> [ 6.604044] ath12k_pci 0000:63:00.0: fw_version 0x100301e1 >>>>>>>>>>>>> fw_build_timestamp 2023-12-06 04:05 fw_build_id >>>>>>>>>>>>> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481- >>>>>>>>>>>>> QCAHMTSWPL_V1.0_V2.0_SILICONZ- >>>>>>>>>>>>> >>>>>>>>>>>>> Also, I noticed when looking through the debug logs there >>>>>>>>>>>>> are the >>>>>>>>>>>>> occasional WARNING statements from a BUG it appears. They >>>>>>>>>>>>> trace back >>>>>>>>>>>>> to the mac.c file inside the ath12k code. There should be >>>>>>>>>>>>> some in the >>>>>>>>>>>>> debug log that's attached. Let me know if I can do anything >>>>>>>>>>>>> else. >>>>>>>>>>>>> Thanks, >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> I have never seen this warning on my upstream setup...Not >>>>>>>>>>>> sure if you >>>>>>>>>>>> have changed anything or using the correct code base. >>>>>>>>>>>> >>>>>>>>>>>> Jeff merged this patch-set into ath-202504021602. Can you >>>>>>>>>>>> try on this >>>>>>>>>>>> branch? >>>>>>>>>>>> >>>>>>>>>>>> git clone https://git.kernel.org/pub/scm/linux/kernel/git/ >>>>>>>>>>>> ath/ath.git/ >>>>>>>>>>>> git pull >>>>>>>>>>>> git reset --hard ath-202504021602 >>>>>>>>>>>> compile and install... >>>>>>>>>>>> >>>>>>>>>>>> Also make sure that the firmware you used is from the same >>>>>>>>>>>> folder, don't >>>>>>>>>>>> mix with other folders: >>>>>>>>>>>> linux-firmware/ath12k/WCN7850/hw2.0 >>>>>>>>>>>> >>>>>>>>>>>> 1. rmmod/insmod(debug_mask=0xffff) >>>>>>>>>>>> 2. iw reg get >>>>>>>>>>>> 3. iw reg set US >>>>>>>>>>>> 4. iw xxx scan >>>>>>>>>>>> wait and collect logs. >>>>>>>>>>>> >>>>>>>>>>>> don't do anything else. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Also, can you show me your AP configuration. >>>>>>>>>>>> If you have another 6 GHz AP, you can have a try(better >>>>>>>>>>>> different brands). >>>>>>>>>>>> >>>>>>>>>> Thanks for testing. >>>>>>>>>> >>>>>>>>>> Could you share your AP configuration? >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>> If you have sniffer, could please capture packets during >>>>>>>>>>>> testing? >>>>>>>>>> >>>>>>>>>> Can you capture packets during the testing? I need to check >>>>>>>>>> probe req >>>>>>>>>> and probe resp. >>>>>>>>>> >>>>>>>>>>>> Thanks! >>>>>>>>>>>> >>>>>>>>>>>>> -Walt >>>>>>>>>>> OK, I cloned and built the kernel based on your instructions >>>>>>>>>>> in your >>>>>>>>>>> last email. Originally, the result was identical to my last >>>>>>>>>>> email, >>>>>>>>>>> including the WARNINGS. The .config I use is configured for a >>>>>>>>>>> fully RT >>>>>>>>>>> PREEMPT kernel, which I wondered if that was why I was >>>>>>>>>>> receiving the >>>>>>>>>>> WARNING. So I configured it as a Low Latency PREEMPT Desktop >>>>>>>>>>> without >>>>>>>>>>> the RT_PREEMPT and that eliminated the WARNING. However, >>>>>>>>>>> still no 6Ghz >>>>>>>>>>> networks. The firmware I'm using is straight from kernel.org >>>>>>>>>>> GIT and I >>>>>>>>>>> do a 'make install; make dedup' to install it. I believe it >>>>>>>>>>> should be >>>>>>>>>>> good. Attached is the latest log file. >>>>>>>>>>> >>>>>>>>>>> -Walt >>>>>>> >>>>>>> Sorry for the top-post earlier. I can't figure out how to capture >>>>>>> the >>>>>>> wireless packets as my chip/driver combo doesn't support monitor >>>>>>> mode. >>>>>> Your AP also cannot capture wireless packets? >>>>>> log in AP by usbserial or ssh. >>>>>> Try to enter command line. use iw command to create monitor >>>>>> interface. >>>>>> Then use tcpdump to capture packets. >>>>>> >>>>>>> I've attached a tarball that contains the trace data and additional >>>>>>> firmware logs from the kernel.log file. Anything else you need, just >>>>>>> ask. Thanks for your help, >>>>>> >>>>>> Your AP mac address? >>>>>> Need it to help check the fw log. >>>>>> >>>>>> >>>>>>> -Walt >>>>> Sorry, the AP doesn't have tcpdump available on it. Also, this is a >>>>> mesh setup with 3 nodes total. The main AP and 2 mesh nodes. I'm >>>>> within 10 feet of one of the nodes and it's MAC for the wireless 6ghz >>>>> network is: 10:7C:61:6F:2A:CA >>>>> >>>>> -Walt >>>> The other 2 node 6ghz mac addresses are: >>>> 10:7C:61:6F:1F:11 - Router >>>> 10:7C:61:6F:32:92 - Node >>>> >>>> The first MAC address I gave you earlier was a node located >>>> approximately 5 feet from where the laptop is. >>>> >>>> -Walt >>> Well, I'm running into a brick wall it seems trying to get 6Ghz >>> enabled on this. I tried the ath-next-20250418 tag just now and still >>> don't see or connect to my 6Ghz network. I applied the patches in: >>> https://lore.kernel.org/linux-wireless/20250418-ath12k-6g-lp-vlp- >>> v1-0-c869c86cad60@quicinc.com/T/#t >>> >>> hoping that would help, but alas, no 6Ghz networks. I see that MLO and >>> other nice fixes are coming in 6.16, but without 6Ghz, they'll do me >>> no good. I'm really wondering if it's a firmware issue that excludes >>> my chip or something. Again, anything I can do to help, let me know. >>> Thanks, >>> >>> -Walt >> Well, I used the swiss army tools to look at the firmware, and my chip >> is listed in the firmware, so it's not excluded or anything. Really >> puzzlling issue as my other two laptops connect to the 6Ghz network >> just fine, and this laptop does in Windows, just not in Linux. I >> really don't use Windows at all though, so that does me no good. >> >> This laptop used to connect to the 6Ghz network around the Sep. - Oct. >> 2024 timeframe. Something has changed and now it doesn't. I'm going to >> boot off a live image of Ubuntu 24.10 and see if I can see the >> network. It was always hit or miss so we'll see. >> -Walt > > > Can you find 6 GHz AP now? > Our firmware team said you station device sent the probe request but didn't receive the probe resp or beacon. Since your current configuration is single 6 GHz AP. Could you change your AP configuration to 6 GHz + 2/5 GHz to have a retry? > > > ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ath12k: No 6GHz Wireless found 2025-05-15 9:22 ` Kang Yang @ 2025-05-15 17:47 ` Walt Holman 2025-05-15 18:20 ` Jeff Johnson 2025-05-16 3:06 ` Kang Yang 0 siblings, 2 replies; 32+ messages in thread From: Walt Holman @ 2025-05-15 17:47 UTC (permalink / raw) To: Kang Yang; +Cc: Jeff Johnson, linux-wireless, ath12k@lists.infradead.org On Thu, May 15, 2025 at 4:22 AM Kang Yang <quic_kangyang@quicinc.com> wrote: > > > > On 5/15/2025 4:12 PM, Kang Yang wrote: > > > > On 4/20/2025 11:18 PM, Walt Holman wrote: > >> On Fri, Apr 18, 2025 at 4:18 PM Walt Holman <waltholman09@gmail.com> > >> wrote: > >>> On Tue, Apr 15, 2025 at 4:23 PM Walt Holman <waltholman09@gmail.com> > >>> wrote: > >>>> On Thu, Apr 10, 2025 at 10:32 AM Walt Holman > >>>> <waltholman09@gmail.com> wrote: > >>>>> On Thu, Apr 10, 2025 at 3:26 AM Kang Yang > >>>>> <kang.yang@oss.qualcomm.com> wrote: > >>>>>> > >>>>>> > >>>>>> On 4/10/2025 3:37 AM, Walt Holman wrote: > >>>>>>> On Tue, Apr 8, 2025 at 4:17 AM Kang Yang > >>>>>>> <quic_kangyang@quicinc.com> wrote: > >>>>>>>> > >>>>>>>> > >>>>>>>> On 4/8/2025 1:49 AM, Walt Holman wrote: > >>>>>>>>> Attached is a small packet capture where I did an 'iw wlp99s0 > >>>>>>>>> scan' > >>>>>>>>> and also deactivated and reactivated wireless while the scan was > >>>>>>>>> ongoing. Hopefully there's something interesting for you in there. > >>>>>>>>> Also, I've take 3 screenshots showing the configs of the > >>>>>>>>> wireless AP > >>>>>>>>> for the 6ghz network. The first screen is just the definition > >>>>>>>>> of the > >>>>>>>>> network. No advanced settings are used. The 2nd screen shows the > >>>>>>>>> channels and radio enabled. The 3rd screen has the advanced > >>>>>>>>> (professional) settings for the network. I believe I changed > >>>>>>>>> 'Agile > >>>>>>>>> Multiband' to enabled, but other settings are their defaults. Hope > >>>>>>>>> some of this helps. Let me know if you need anything else. Thanks, > >>>>>>>>> > >>>>>>>> Your packets are Ethernet packets. I need wireless packets. > >>>>>>>> > >>>>>>>> > >>>>>>>> Not sure if you know how to add a seperate monitor interface to > >>>>>>>> capture > >>>>>>>> 6 G channels' packet on your AP(you can google for specific > >>>>>>>> command). > >>>>>>>> > >>>>>>>> > >>>>>>>> Also, please capture firmware log: > >>>>>>>> > >>>>>>>> 1. sudo apt install trace-cmd > >>>>>>>> 2. sudo trace-cmd record -e ath12k_wmi_diag > >>>>>>>> 3. run test > >>>>>>>> 4. "ctrl c" to stop recording: > >>>>>>>> Hit Ctrl^C to stop recording > >>>>>>>> ^CCPU0 data recorded at offset=0xdf5000 > >>>>>>>> 2605056 bytes in size > >>>>>>>> Then share the trace.dat to us. > >>>>>>>> > >>>>>>>> So you need to: > >>>>>>>> 1. try to capture wireless packets. > >>>>>>>> 2. capture firmware log(trade.data). > >>>>>>>> 3. save kernel/wpa_supplicant/iw logs. > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>>> -Walt > >>>>>>>>> > >>>>>>>>> On Sun, Apr 6, 2025 at 8:58 PM Kang Yang > >>>>>>>>> <quic_kangyang@quicinc.com> wrote: > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> On 4/4/2025 12:04 AM, Walt Holman wrote: > >>>>>>>>>>> On Thu, Apr 3, 2025 at 3:20 AM Kang Yang > >>>>>>>>>>> <quic_kangyang@quicinc.com> wrote: > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> On 4/3/2025 1:48 AM, Walt Holman wrote: > >>>>>>>>>>>>> On Tue, Apr 1, 2025 at 9:48 PM Kang Yang > >>>>>>>>>>>>> <quic_kangyang@quicinc.com> wrote: > >>>>>>>>>>>>>> Test on 6.14.0-rc5-wt-ath+, with the firmware you used. > >>>>>>>>>>>>>> I can get 6 GHz AP and connect to it. > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> ath12k_pci 0000:03:00.0: fw_version 0x100301e1 > >>>>>>>>>>>>>> fw_build_timestamp > >>>>>>>>>>>>>> 2023-12-06 04:05 fw_build_id > >>>>>>>>>>>>>> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481- > >>>>>>>>>>>>>> QCAHMTSWPL_V1.0_V2.0_SILICONZ-3 > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> yk@yk-Mayan:~$ sudo iw wls1 scan | tee iw_scan.log: > >>>>>>>>>>>>>> BSS 62:03:7f:12:64:64(on wls1) -- associated > >>>>>>>>>>>>>> TSF: 606308271476 usec (7d, 00:25:08) > >>>>>>>>>>>>>> freq: 6275 > >>>>>>>>>>>>>> beacon interval: 100 TUs > >>>>>>>>>>>>>> capability: ESS Privacy SpectrumMgmt > >>>>>>>>>>>>>> ShortSlotTime (0x0511) > >>>>>>>>>>>>>> signal: -17.00 dBm > >>>>>>>>>>>>>> last seen: 52 ms ago > >>>>>>>>>>>>>> Information elements from Probe Response frame: > >>>>>>>>>>>>>> SSID: MLO-KANG-6G > >>>>>>>>>>>>>> and other 6 GHz APs: > >>>>>>>>>>>>>> SSID: 6G-gxia > >>>>>>>>>>>>>> SSID: NETGEAR97-6G > >>>>>>>>>>>>>> …… > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> kernel log: > >>>>>>>>>>>>>> [88158.033218] wls1: Inserted STA 62:03:7f:12:64:64 > >>>>>>>>>>>>>> [88158.033232] wls1: authenticate with 62:03:7f:12:64:64 > >>>>>>>>>>>>>> (local > >>>>>>>>>>>>>> address=00:03:7f:37:12:54) > >>>>>>>>>>>>>> [88158.033242] wls1: send auth to 62:03:7f:12:64:64 (try 1/3) > >>>>>>>>>>>>>> [88158.041895] wls1: authenticated > >>>>>>>>>>>>>> [88158.041914] wls1: moving STA 62:03:7f:12:64:64 to state 2 > >>>>>>>>>>>>>> [88158.044291] wls1: determined local STA to be EHT, BW > >>>>>>>>>>>>>> limited to 320 MHz > >>>>>>>>>>>>>> [88158.045719] wls1: associate with 62:03:7f:12:64:64 (try > >>>>>>>>>>>>>> 1/3) > >>>>>>>>>>>>>> [88158.067045] wls1: RX AssocResp from 62:03:7f:12:64:64 > >>>>>>>>>>>>>> (capab=0x511 > >>>>>>>>>>>>>> status=0 aid=4) > >>>>>>>>>>>>>> [88158.089090] wls1: associated > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> I can even connect to it by Ubuntu GUI. > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> Can you update to 6.14.0-rc5-wt-ath+ and have a retry? > >>>>>>>>>>>>>> Also please make > >>>>>>>>>>>>>> sure that your wpa_supplicant/iw support 6 GHz(or directly > >>>>>>>>>>>>>> update to the > >>>>>>>>>>>>>> latest version). > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> If you still cannot find 6 GHz AP, you can set debug_mask > >>>>>>>>>>>>>> to 0xffffffff > >>>>>>>>>>>>>> to get ath12k logs. Then give it to us. > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>>> -Walt > >>>>>>>>>>>>>>> > >>>>>>>>>>>>> OK, I retested with the wt-ath 033125 tagged build. This > >>>>>>>>>>>>> included the > >>>>>>>>>>>>> patch the Jeff suggested I try, but the rest of the tree > >>>>>>>>>>>>> was clean. > >>>>>>>>>>>>> Still no 6ghz Wifi. I'm attaching a log file of the boot > >>>>>>>>>>>>> and first few > >>>>>>>>>>>>> seconds with the debug mask turned on. I noticed that if I > >>>>>>>>>>>>> rmmod the > >>>>>>>>>>>>> module and then modprobe it, it complains about not finding > >>>>>>>>>>>>> firmware-2.bin, however, I thought that was only for the > >>>>>>>>>>>>> qcn based > >>>>>>>>>>>>> chip? The HW info from dmesg looks like this: > >>>>>>>>>>>>> > >>>>>>>>>>>> I cannot find this tag... > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> From the log, the 6 GHz channel should work. When scan > >>>>>>>>>>>> is triggered, FW > >>>>>>>>>>>> shall send probe req on these channels. If AP send probe > >>>>>>>>>>>> resp, station > >>>>>>>>>>>> shall find the AP. > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>>> [ 6.070282] ath12k_pci 0000:63:00.0: BAR 0 [mem > >>>>>>>>>>>>> 0xdd800000-0xdd9fffff 64bit]: assigned > >>>>>>>>>>>>> [ 6.070310] ath12k_pci 0000:63:00.0: enabling device > >>>>>>>>>>>>> (0000 -> 0002) > >>>>>>>>>>>>> [ 6.071249] ath12k_pci 0000:63:00.0: MSI vectors: 16 > >>>>>>>>>>>>> [ 6.071254] ath12k_pci 0000:63:00.0: Hardware name: > >>>>>>>>>>>>> wcn7850 hw2.0 > >>>>>>>>>>>>> [ 6.596331] ath12k_pci 0000:63:00.0: qmi dma allocation > >>>>>>>>>>>>> failed > >>>>>>>>>>>>> (7077888 B type 1), will try later with sma > >>>>>>>>>>>>> ll size > >>>>>>>>>>>>> [ 6.604041] ath12k_pci 0000:63:00.0: chip_id 0x2 > >>>>>>>>>>>>> chip_family 0x4 > >>>>>>>>>>>>> board_id 0xff soc_id 0x40170200 > >>>>>>>>>>>>> [ 6.604044] ath12k_pci 0000:63:00.0: fw_version 0x100301e1 > >>>>>>>>>>>>> fw_build_timestamp 2023-12-06 04:05 fw_build_id > >>>>>>>>>>>>> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481- > >>>>>>>>>>>>> QCAHMTSWPL_V1.0_V2.0_SILICONZ- > >>>>>>>>>>>>> > >>>>>>>>>>>>> Also, I noticed when looking through the debug logs there > >>>>>>>>>>>>> are the > >>>>>>>>>>>>> occasional WARNING statements from a BUG it appears. They > >>>>>>>>>>>>> trace back > >>>>>>>>>>>>> to the mac.c file inside the ath12k code. There should be > >>>>>>>>>>>>> some in the > >>>>>>>>>>>>> debug log that's attached. Let me know if I can do anything > >>>>>>>>>>>>> else. > >>>>>>>>>>>>> Thanks, > >>>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> I have never seen this warning on my upstream setup...Not > >>>>>>>>>>>> sure if you > >>>>>>>>>>>> have changed anything or using the correct code base. > >>>>>>>>>>>> > >>>>>>>>>>>> Jeff merged this patch-set into ath-202504021602. Can you > >>>>>>>>>>>> try on this > >>>>>>>>>>>> branch? > >>>>>>>>>>>> > >>>>>>>>>>>> git clone https://git.kernel.org/pub/scm/linux/kernel/git/ > >>>>>>>>>>>> ath/ath.git/ > >>>>>>>>>>>> git pull > >>>>>>>>>>>> git reset --hard ath-202504021602 > >>>>>>>>>>>> compile and install... > >>>>>>>>>>>> > >>>>>>>>>>>> Also make sure that the firmware you used is from the same > >>>>>>>>>>>> folder, don't > >>>>>>>>>>>> mix with other folders: > >>>>>>>>>>>> linux-firmware/ath12k/WCN7850/hw2.0 > >>>>>>>>>>>> > >>>>>>>>>>>> 1. rmmod/insmod(debug_mask=0xffff) > >>>>>>>>>>>> 2. iw reg get > >>>>>>>>>>>> 3. iw reg set US > >>>>>>>>>>>> 4. iw xxx scan > >>>>>>>>>>>> wait and collect logs. > >>>>>>>>>>>> > >>>>>>>>>>>> don't do anything else. > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> Also, can you show me your AP configuration. > >>>>>>>>>>>> If you have another 6 GHz AP, you can have a try(better > >>>>>>>>>>>> different brands). > >>>>>>>>>>>> > >>>>>>>>>> Thanks for testing. > >>>>>>>>>> > >>>>>>>>>> Could you share your AP configuration? > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>>>> If you have sniffer, could please capture packets during > >>>>>>>>>>>> testing? > >>>>>>>>>> > >>>>>>>>>> Can you capture packets during the testing? I need to check > >>>>>>>>>> probe req > >>>>>>>>>> and probe resp. > >>>>>>>>>> > >>>>>>>>>>>> Thanks! > >>>>>>>>>>>> > >>>>>>>>>>>>> -Walt > >>>>>>>>>>> OK, I cloned and built the kernel based on your instructions > >>>>>>>>>>> in your > >>>>>>>>>>> last email. Originally, the result was identical to my last > >>>>>>>>>>> email, > >>>>>>>>>>> including the WARNINGS. The .config I use is configured for a > >>>>>>>>>>> fully RT > >>>>>>>>>>> PREEMPT kernel, which I wondered if that was why I was > >>>>>>>>>>> receiving the > >>>>>>>>>>> WARNING. So I configured it as a Low Latency PREEMPT Desktop > >>>>>>>>>>> without > >>>>>>>>>>> the RT_PREEMPT and that eliminated the WARNING. However, > >>>>>>>>>>> still no 6Ghz > >>>>>>>>>>> networks. The firmware I'm using is straight from kernel.org > >>>>>>>>>>> GIT and I > >>>>>>>>>>> do a 'make install; make dedup' to install it. I believe it > >>>>>>>>>>> should be > >>>>>>>>>>> good. Attached is the latest log file. > >>>>>>>>>>> > >>>>>>>>>>> -Walt > >>>>>>> > >>>>>>> Sorry for the top-post earlier. I can't figure out how to capture > >>>>>>> the > >>>>>>> wireless packets as my chip/driver combo doesn't support monitor > >>>>>>> mode. > >>>>>> Your AP also cannot capture wireless packets? > >>>>>> log in AP by usbserial or ssh. > >>>>>> Try to enter command line. use iw command to create monitor > >>>>>> interface. > >>>>>> Then use tcpdump to capture packets. > >>>>>> > >>>>>>> I've attached a tarball that contains the trace data and additional > >>>>>>> firmware logs from the kernel.log file. Anything else you need, just > >>>>>>> ask. Thanks for your help, > >>>>>> > >>>>>> Your AP mac address? > >>>>>> Need it to help check the fw log. > >>>>>> > >>>>>> > >>>>>>> -Walt > >>>>> Sorry, the AP doesn't have tcpdump available on it. Also, this is a > >>>>> mesh setup with 3 nodes total. The main AP and 2 mesh nodes. I'm > >>>>> within 10 feet of one of the nodes and it's MAC for the wireless 6ghz > >>>>> network is: 10:7C:61:6F:2A:CA > >>>>> > >>>>> -Walt > >>>> The other 2 node 6ghz mac addresses are: > >>>> 10:7C:61:6F:1F:11 - Router > >>>> 10:7C:61:6F:32:92 - Node > >>>> > >>>> The first MAC address I gave you earlier was a node located > >>>> approximately 5 feet from where the laptop is. > >>>> > >>>> -Walt > >>> Well, I'm running into a brick wall it seems trying to get 6Ghz > >>> enabled on this. I tried the ath-next-20250418 tag just now and still > >>> don't see or connect to my 6Ghz network. I applied the patches in: > >>> https://lore.kernel.org/linux-wireless/20250418-ath12k-6g-lp-vlp- > >>> v1-0-c869c86cad60@quicinc.com/T/#t > >>> > >>> hoping that would help, but alas, no 6Ghz networks. I see that MLO and > >>> other nice fixes are coming in 6.16, but without 6Ghz, they'll do me > >>> no good. I'm really wondering if it's a firmware issue that excludes > >>> my chip or something. Again, anything I can do to help, let me know. > >>> Thanks, > >>> > >>> -Walt > >> Well, I used the swiss army tools to look at the firmware, and my chip > >> is listed in the firmware, so it's not excluded or anything. Really > >> puzzlling issue as my other two laptops connect to the 6Ghz network > >> just fine, and this laptop does in Windows, just not in Linux. I > >> really don't use Windows at all though, so that does me no good. > >> > >> This laptop used to connect to the 6Ghz network around the Sep. - Oct. > >> 2024 timeframe. Something has changed and now it doesn't. I'm going to > >> boot off a live image of Ubuntu 24.10 and see if I can see the > >> network. It was always hit or miss so we'll see. > >> -Walt > > > > > > Can you find 6 GHz AP now? > > > > Our firmware team said you station device sent the probe request but > didn't receive the probe resp or beacon. > > Since your current configuration is single 6 GHz AP. Could you change > your AP configuration to 6 GHz + 2/5 GHz to have a retry? > I adedd another network with 2.4 / 5 / 6Ghz settings and still only connect to the 5Ghz network portion. This is verified through wavemon and the AP. I saw some patches recently to address 6 Ghz operatoins in various modes (https://lore.kernel.org/linux-wireless/1692f2f8-c77e-87ce-db70-00b4d9fc7c95@oss.qualcomm.com/), but the patch doesn't apply cleanly to current or ath-pending. Don't know that it would help, but it seemed interesting. When I went back to the older kernel / distro I still could not see the 6 Ghz band nor connect to it. I think something has changed on the AP as well, as this used to work intermittently. I think I have mentioned this before, but I have a dual-boot setup on this laptop and in Windows 11, it does see and connect to the 6 Ghz band and MLO works as well. Also, I have about 5 other devices (phones and laptops) that can all connect to the 6 Ghz band. I think it's a combination of the AP and the driver / firmware. -Walt ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ath12k: No 6GHz Wireless found 2025-05-15 17:47 ` Walt Holman @ 2025-05-15 18:20 ` Jeff Johnson 2025-05-15 18:57 ` Walt Holman 2025-05-16 3:06 ` Kang Yang 1 sibling, 1 reply; 32+ messages in thread From: Jeff Johnson @ 2025-05-15 18:20 UTC (permalink / raw) To: Walt Holman, Kang Yang; +Cc: linux-wireless, ath12k@lists.infradead.org On 5/15/2025 10:47 AM, Walt Holman wrote: > I adedd another network with 2.4 / 5 / 6Ghz settings and still only > connect to the 5Ghz network portion. This is verified through wavemon > and the AP. I saw some patches recently to address 6 Ghz operatoins in > various modes (https://lore.kernel.org/linux-wireless/1692f2f8-c77e-87ce-db70-00b4d9fc7c95@oss.qualcomm.com/), > but the patch doesn't apply cleanly to current or ath-pending. Don't > know that it would help, but it seemed interesting. That series is already part of the pending branch, hence why it doesn't apply cleanly. So ideally you could test with that branch, but there are some other issues in that branch that are still being resolved, see: https://msgid.link/7db2e4b5-377c-4d3b-b51f-290accc9ddd9@oss.qualcomm.com /jeff ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ath12k: No 6GHz Wireless found 2025-05-15 18:20 ` Jeff Johnson @ 2025-05-15 18:57 ` Walt Holman 0 siblings, 0 replies; 32+ messages in thread From: Walt Holman @ 2025-05-15 18:57 UTC (permalink / raw) To: Jeff Johnson; +Cc: Kang Yang, linux-wireless, ath12k@lists.infradead.org On Thu, May 15, 2025 at 1:20 PM Jeff Johnson <jeff.johnson@oss.qualcomm.com> wrote: > > On 5/15/2025 10:47 AM, Walt Holman wrote: > > I adedd another network with 2.4 / 5 / 6Ghz settings and still only > > connect to the 5Ghz network portion. This is verified through wavemon > > and the AP. I saw some patches recently to address 6 Ghz operatoins in > > various modes (https://lore.kernel.org/linux-wireless/1692f2f8-c77e-87ce-db70-00b4d9fc7c95@oss.qualcomm.com/), > > but the patch doesn't apply cleanly to current or ath-pending. Don't > > know that it would help, but it seemed interesting. > > That series is already part of the pending branch, hence why it doesn't apply > cleanly. So ideally you could test with that branch, but there are some other > issues in that branch that are still being resolved, see: > https://msgid.link/7db2e4b5-377c-4d3b-b51f-290accc9ddd9@oss.qualcomm.com > > /jeff Thanks for the info. I've found something odd out just now. If I turn on WPS it will find the 6Ghz Network. It times out before the connection can be made and WPS turns back off. Just another data point to consider I guess. -Walt ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ath12k: No 6GHz Wireless found 2025-05-15 17:47 ` Walt Holman 2025-05-15 18:20 ` Jeff Johnson @ 2025-05-16 3:06 ` Kang Yang 2025-05-16 18:09 ` Walt Holman 2025-05-21 5:05 ` Walt Holman 1 sibling, 2 replies; 32+ messages in thread From: Kang Yang @ 2025-05-16 3:06 UTC (permalink / raw) To: Walt Holman; +Cc: Jeff Johnson, linux-wireless, ath12k@lists.infradead.org On 5/16/2025 1:47 AM, Walt Holman wrote: > On Thu, May 15, 2025 at 4:22 AM Kang Yang <quic_kangyang@quicinc.com> wrote: >> >> >> >> On 5/15/2025 4:12 PM, Kang Yang wrote: >>> >>> On 4/20/2025 11:18 PM, Walt Holman wrote: >>>> On Fri, Apr 18, 2025 at 4:18 PM Walt Holman <waltholman09@gmail.com> >>>> wrote: >>>>> On Tue, Apr 15, 2025 at 4:23 PM Walt Holman <waltholman09@gmail.com> >>>>> wrote: >>>>>> On Thu, Apr 10, 2025 at 10:32 AM Walt Holman >>>>>> <waltholman09@gmail.com> wrote: >>>>>>> On Thu, Apr 10, 2025 at 3:26 AM Kang Yang >>>>>>> <kang.yang@oss.qualcomm.com> wrote: >>>>>>>> >>>>>>>> >>>>>>>> On 4/10/2025 3:37 AM, Walt Holman wrote: >>>>>>>>> On Tue, Apr 8, 2025 at 4:17 AM Kang Yang >>>>>>>>> <quic_kangyang@quicinc.com> wrote: >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On 4/8/2025 1:49 AM, Walt Holman wrote: >>>>>>>>>>> Attached is a small packet capture where I did an 'iw wlp99s0 >>>>>>>>>>> scan' >>>>>>>>>>> and also deactivated and reactivated wireless while the scan was >>>>>>>>>>> ongoing. Hopefully there's something interesting for you in there. >>>>>>>>>>> Also, I've take 3 screenshots showing the configs of the >>>>>>>>>>> wireless AP >>>>>>>>>>> for the 6ghz network. The first screen is just the definition >>>>>>>>>>> of the >>>>>>>>>>> network. No advanced settings are used. The 2nd screen shows the >>>>>>>>>>> channels and radio enabled. The 3rd screen has the advanced >>>>>>>>>>> (professional) settings for the network. I believe I changed >>>>>>>>>>> 'Agile >>>>>>>>>>> Multiband' to enabled, but other settings are their defaults. Hope >>>>>>>>>>> some of this helps. Let me know if you need anything else. Thanks, >>>>>>>>>>> >>>>>>>>>> Your packets are Ethernet packets. I need wireless packets. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Not sure if you know how to add a seperate monitor interface to >>>>>>>>>> capture >>>>>>>>>> 6 G channels' packet on your AP(you can google for specific >>>>>>>>>> command). >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Also, please capture firmware log: >>>>>>>>>> >>>>>>>>>> 1. sudo apt install trace-cmd >>>>>>>>>> 2. sudo trace-cmd record -e ath12k_wmi_diag >>>>>>>>>> 3. run test >>>>>>>>>> 4. "ctrl c" to stop recording: >>>>>>>>>> Hit Ctrl^C to stop recording >>>>>>>>>> ^CCPU0 data recorded at offset=0xdf5000 >>>>>>>>>> 2605056 bytes in size >>>>>>>>>> Then share the trace.dat to us. >>>>>>>>>> >>>>>>>>>> So you need to: >>>>>>>>>> 1. try to capture wireless packets. >>>>>>>>>> 2. capture firmware log(trade.data). >>>>>>>>>> 3. save kernel/wpa_supplicant/iw logs. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> -Walt >>>>>>>>>>> >>>>>>>>>>> On Sun, Apr 6, 2025 at 8:58 PM Kang Yang >>>>>>>>>>> <quic_kangyang@quicinc.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On 4/4/2025 12:04 AM, Walt Holman wrote: >>>>>>>>>>>>> On Thu, Apr 3, 2025 at 3:20 AM Kang Yang >>>>>>>>>>>>> <quic_kangyang@quicinc.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> On 4/3/2025 1:48 AM, Walt Holman wrote: >>>>>>>>>>>>>>> On Tue, Apr 1, 2025 at 9:48 PM Kang Yang >>>>>>>>>>>>>>> <quic_kangyang@quicinc.com> wrote: >>>>>>>>>>>>>>>> Test on 6.14.0-rc5-wt-ath+, with the firmware you used. >>>>>>>>>>>>>>>> I can get 6 GHz AP and connect to it. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> ath12k_pci 0000:03:00.0: fw_version 0x100301e1 >>>>>>>>>>>>>>>> fw_build_timestamp >>>>>>>>>>>>>>>> 2023-12-06 04:05 fw_build_id >>>>>>>>>>>>>>>> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481- >>>>>>>>>>>>>>>> QCAHMTSWPL_V1.0_V2.0_SILICONZ-3 >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> yk@yk-Mayan:~$ sudo iw wls1 scan | tee iw_scan.log: >>>>>>>>>>>>>>>> BSS 62:03:7f:12:64:64(on wls1) -- associated >>>>>>>>>>>>>>>> TSF: 606308271476 usec (7d, 00:25:08) >>>>>>>>>>>>>>>> freq: 6275 >>>>>>>>>>>>>>>> beacon interval: 100 TUs >>>>>>>>>>>>>>>> capability: ESS Privacy SpectrumMgmt >>>>>>>>>>>>>>>> ShortSlotTime (0x0511) >>>>>>>>>>>>>>>> signal: -17.00 dBm >>>>>>>>>>>>>>>> last seen: 52 ms ago >>>>>>>>>>>>>>>> Information elements from Probe Response frame: >>>>>>>>>>>>>>>> SSID: MLO-KANG-6G >>>>>>>>>>>>>>>> and other 6 GHz APs: >>>>>>>>>>>>>>>> SSID: 6G-gxia >>>>>>>>>>>>>>>> SSID: NETGEAR97-6G >>>>>>>>>>>>>>>> …… >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> kernel log: >>>>>>>>>>>>>>>> [88158.033218] wls1: Inserted STA 62:03:7f:12:64:64 >>>>>>>>>>>>>>>> [88158.033232] wls1: authenticate with 62:03:7f:12:64:64 >>>>>>>>>>>>>>>> (local >>>>>>>>>>>>>>>> address=00:03:7f:37:12:54) >>>>>>>>>>>>>>>> [88158.033242] wls1: send auth to 62:03:7f:12:64:64 (try 1/3) >>>>>>>>>>>>>>>> [88158.041895] wls1: authenticated >>>>>>>>>>>>>>>> [88158.041914] wls1: moving STA 62:03:7f:12:64:64 to state 2 >>>>>>>>>>>>>>>> [88158.044291] wls1: determined local STA to be EHT, BW >>>>>>>>>>>>>>>> limited to 320 MHz >>>>>>>>>>>>>>>> [88158.045719] wls1: associate with 62:03:7f:12:64:64 (try >>>>>>>>>>>>>>>> 1/3) >>>>>>>>>>>>>>>> [88158.067045] wls1: RX AssocResp from 62:03:7f:12:64:64 >>>>>>>>>>>>>>>> (capab=0x511 >>>>>>>>>>>>>>>> status=0 aid=4) >>>>>>>>>>>>>>>> [88158.089090] wls1: associated >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> I can even connect to it by Ubuntu GUI. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Can you update to 6.14.0-rc5-wt-ath+ and have a retry? >>>>>>>>>>>>>>>> Also please make >>>>>>>>>>>>>>>> sure that your wpa_supplicant/iw support 6 GHz(or directly >>>>>>>>>>>>>>>> update to the >>>>>>>>>>>>>>>> latest version). >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> If you still cannot find 6 GHz AP, you can set debug_mask >>>>>>>>>>>>>>>> to 0xffffffff >>>>>>>>>>>>>>>> to get ath12k logs. Then give it to us. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> -Walt >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> OK, I retested with the wt-ath 033125 tagged build. This >>>>>>>>>>>>>>> included the >>>>>>>>>>>>>>> patch the Jeff suggested I try, but the rest of the tree >>>>>>>>>>>>>>> was clean. >>>>>>>>>>>>>>> Still no 6ghz Wifi. I'm attaching a log file of the boot >>>>>>>>>>>>>>> and first few >>>>>>>>>>>>>>> seconds with the debug mask turned on. I noticed that if I >>>>>>>>>>>>>>> rmmod the >>>>>>>>>>>>>>> module and then modprobe it, it complains about not finding >>>>>>>>>>>>>>> firmware-2.bin, however, I thought that was only for the >>>>>>>>>>>>>>> qcn based >>>>>>>>>>>>>>> chip? The HW info from dmesg looks like this: >>>>>>>>>>>>>>> >>>>>>>>>>>>>> I cannot find this tag... >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> From the log, the 6 GHz channel should work. When scan >>>>>>>>>>>>>> is triggered, FW >>>>>>>>>>>>>> shall send probe req on these channels. If AP send probe >>>>>>>>>>>>>> resp, station >>>>>>>>>>>>>> shall find the AP. >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>>> [ 6.070282] ath12k_pci 0000:63:00.0: BAR 0 [mem >>>>>>>>>>>>>>> 0xdd800000-0xdd9fffff 64bit]: assigned >>>>>>>>>>>>>>> [ 6.070310] ath12k_pci 0000:63:00.0: enabling device >>>>>>>>>>>>>>> (0000 -> 0002) >>>>>>>>>>>>>>> [ 6.071249] ath12k_pci 0000:63:00.0: MSI vectors: 16 >>>>>>>>>>>>>>> [ 6.071254] ath12k_pci 0000:63:00.0: Hardware name: >>>>>>>>>>>>>>> wcn7850 hw2.0 >>>>>>>>>>>>>>> [ 6.596331] ath12k_pci 0000:63:00.0: qmi dma allocation >>>>>>>>>>>>>>> failed >>>>>>>>>>>>>>> (7077888 B type 1), will try later with sma >>>>>>>>>>>>>>> ll size >>>>>>>>>>>>>>> [ 6.604041] ath12k_pci 0000:63:00.0: chip_id 0x2 >>>>>>>>>>>>>>> chip_family 0x4 >>>>>>>>>>>>>>> board_id 0xff soc_id 0x40170200 >>>>>>>>>>>>>>> [ 6.604044] ath12k_pci 0000:63:00.0: fw_version 0x100301e1 >>>>>>>>>>>>>>> fw_build_timestamp 2023-12-06 04:05 fw_build_id >>>>>>>>>>>>>>> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481- >>>>>>>>>>>>>>> QCAHMTSWPL_V1.0_V2.0_SILICONZ- >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Also, I noticed when looking through the debug logs there >>>>>>>>>>>>>>> are the >>>>>>>>>>>>>>> occasional WARNING statements from a BUG it appears. They >>>>>>>>>>>>>>> trace back >>>>>>>>>>>>>>> to the mac.c file inside the ath12k code. There should be >>>>>>>>>>>>>>> some in the >>>>>>>>>>>>>>> debug log that's attached. Let me know if I can do anything >>>>>>>>>>>>>>> else. >>>>>>>>>>>>>>> Thanks, >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> I have never seen this warning on my upstream setup...Not >>>>>>>>>>>>>> sure if you >>>>>>>>>>>>>> have changed anything or using the correct code base. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Jeff merged this patch-set into ath-202504021602. Can you >>>>>>>>>>>>>> try on this >>>>>>>>>>>>>> branch? >>>>>>>>>>>>>> >>>>>>>>>>>>>> git clone https://git.kernel.org/pub/scm/linux/kernel/git/ >>>>>>>>>>>>>> ath/ath.git/ >>>>>>>>>>>>>> git pull >>>>>>>>>>>>>> git reset --hard ath-202504021602 >>>>>>>>>>>>>> compile and install... >>>>>>>>>>>>>> >>>>>>>>>>>>>> Also make sure that the firmware you used is from the same >>>>>>>>>>>>>> folder, don't >>>>>>>>>>>>>> mix with other folders: >>>>>>>>>>>>>> linux-firmware/ath12k/WCN7850/hw2.0 >>>>>>>>>>>>>> >>>>>>>>>>>>>> 1. rmmod/insmod(debug_mask=0xffff) >>>>>>>>>>>>>> 2. iw reg get >>>>>>>>>>>>>> 3. iw reg set US >>>>>>>>>>>>>> 4. iw xxx scan >>>>>>>>>>>>>> wait and collect logs. >>>>>>>>>>>>>> >>>>>>>>>>>>>> don't do anything else. >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Also, can you show me your AP configuration. >>>>>>>>>>>>>> If you have another 6 GHz AP, you can have a try(better >>>>>>>>>>>>>> different brands). >>>>>>>>>>>>>> >>>>>>>>>>>> Thanks for testing. >>>>>>>>>>>> >>>>>>>>>>>> Could you share your AP configuration? >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>>>> If you have sniffer, could please capture packets during >>>>>>>>>>>>>> testing? >>>>>>>>>>>> >>>>>>>>>>>> Can you capture packets during the testing? I need to check >>>>>>>>>>>> probe req >>>>>>>>>>>> and probe resp. >>>>>>>>>>>> >>>>>>>>>>>>>> Thanks! >>>>>>>>>>>>>> >>>>>>>>>>>>>>> -Walt >>>>>>>>>>>>> OK, I cloned and built the kernel based on your instructions >>>>>>>>>>>>> in your >>>>>>>>>>>>> last email. Originally, the result was identical to my last >>>>>>>>>>>>> email, >>>>>>>>>>>>> including the WARNINGS. The .config I use is configured for a >>>>>>>>>>>>> fully RT >>>>>>>>>>>>> PREEMPT kernel, which I wondered if that was why I was >>>>>>>>>>>>> receiving the >>>>>>>>>>>>> WARNING. So I configured it as a Low Latency PREEMPT Desktop >>>>>>>>>>>>> without >>>>>>>>>>>>> the RT_PREEMPT and that eliminated the WARNING. However, >>>>>>>>>>>>> still no 6Ghz >>>>>>>>>>>>> networks. The firmware I'm using is straight from kernel.org >>>>>>>>>>>>> GIT and I >>>>>>>>>>>>> do a 'make install; make dedup' to install it. I believe it >>>>>>>>>>>>> should be >>>>>>>>>>>>> good. Attached is the latest log file. >>>>>>>>>>>>> >>>>>>>>>>>>> -Walt >>>>>>>>> >>>>>>>>> Sorry for the top-post earlier. I can't figure out how to capture >>>>>>>>> the >>>>>>>>> wireless packets as my chip/driver combo doesn't support monitor >>>>>>>>> mode. >>>>>>>> Your AP also cannot capture wireless packets? >>>>>>>> log in AP by usbserial or ssh. >>>>>>>> Try to enter command line. use iw command to create monitor >>>>>>>> interface. >>>>>>>> Then use tcpdump to capture packets. >>>>>>>> >>>>>>>>> I've attached a tarball that contains the trace data and additional >>>>>>>>> firmware logs from the kernel.log file. Anything else you need, just >>>>>>>>> ask. Thanks for your help, >>>>>>>> >>>>>>>> Your AP mac address? >>>>>>>> Need it to help check the fw log. >>>>>>>> >>>>>>>> >>>>>>>>> -Walt >>>>>>> Sorry, the AP doesn't have tcpdump available on it. Also, this is a >>>>>>> mesh setup with 3 nodes total. The main AP and 2 mesh nodes. I'm >>>>>>> within 10 feet of one of the nodes and it's MAC for the wireless 6ghz >>>>>>> network is: 10:7C:61:6F:2A:CA >>>>>>> >>>>>>> -Walt >>>>>> The other 2 node 6ghz mac addresses are: >>>>>> 10:7C:61:6F:1F:11 - Router >>>>>> 10:7C:61:6F:32:92 - Node >>>>>> >>>>>> The first MAC address I gave you earlier was a node located >>>>>> approximately 5 feet from where the laptop is. >>>>>> >>>>>> -Walt >>>>> Well, I'm running into a brick wall it seems trying to get 6Ghz >>>>> enabled on this. I tried the ath-next-20250418 tag just now and still >>>>> don't see or connect to my 6Ghz network. I applied the patches in: >>>>> https://lore.kernel.org/linux-wireless/20250418-ath12k-6g-lp-vlp- >>>>> v1-0-c869c86cad60@quicinc.com/T/#t >>>>> >>>>> hoping that would help, but alas, no 6Ghz networks. I see that MLO and >>>>> other nice fixes are coming in 6.16, but without 6Ghz, they'll do me >>>>> no good. I'm really wondering if it's a firmware issue that excludes >>>>> my chip or something. Again, anything I can do to help, let me know. >>>>> Thanks, >>>>> >>>>> -Walt >>>> Well, I used the swiss army tools to look at the firmware, and my chip >>>> is listed in the firmware, so it's not excluded or anything. Really >>>> puzzlling issue as my other two laptops connect to the 6Ghz network >>>> just fine, and this laptop does in Windows, just not in Linux. I >>>> really don't use Windows at all though, so that does me no good. >>>> >>>> This laptop used to connect to the 6Ghz network around the Sep. - Oct. >>>> 2024 timeframe. Something has changed and now it doesn't. I'm going to >>>> boot off a live image of Ubuntu 24.10 and see if I can see the >>>> network. It was always hit or miss so we'll see. >>>> -Walt >>> >>> >>> Can you find 6 GHz AP now? >>> >> >> Our firmware team said you station device sent the probe request but >> didn't receive the probe resp or beacon. >> >> Since your current configuration is single 6 GHz AP. Could you change >> your AP configuration to 6 GHz + 2/5 GHz to have a retry? >> > I adedd another network with 2.4 / 5 / 6Ghz settings and still only > connect to the 5Ghz network portion. This is verified through wavemon > and the AP. I saw some patches recently to address 6 Ghz operatoins in > various modes (https://lore.kernel.org/linux-wireless/1692f2f8-c77e-87ce-db70-00b4d9fc7c95@oss.qualcomm.com/), > but the patch doesn't apply cleanly to current or ath-pending. Don't > know that it would help, but it seemed interesting. > > When I went back to the older kernel / distro I still could not see > the 6 Ghz band nor connect to it. I think something has changed on the > AP as well, as this used to work intermittently. I think I have > mentioned this before, but I have a dual-boot setup on this laptop and > in Windows 11, it does see and connect to the 6 Ghz band and MLO works > as well. Also, I have about 5 other devices (phones and laptops) that > can all connect to the 6 Ghz band. I think it's a combination of the > AP and the driver / firmware. Do you have another WCN7850? Our monitor mode is now in pending branch, and one fix is coming so that you can use WCN7850 to capture 6 GHz management packects. So that our firmware team can do further research. > > -Walt > ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ath12k: No 6GHz Wireless found 2025-05-16 3:06 ` Kang Yang @ 2025-05-16 18:09 ` Walt Holman 2025-05-21 5:05 ` Walt Holman 1 sibling, 0 replies; 32+ messages in thread From: Walt Holman @ 2025-05-16 18:09 UTC (permalink / raw) To: Kang Yang; +Cc: Jeff Johnson, linux-wireless, ath12k@lists.infradead.org On Thu, May 15, 2025 at 10:06 PM Kang Yang <quic_kangyang@quicinc.com> wrote: > > > > On 5/16/2025 1:47 AM, Walt Holman wrote: > > On Thu, May 15, 2025 at 4:22 AM Kang Yang <quic_kangyang@quicinc.com> wrote: > >> > >> > >> > >> On 5/15/2025 4:12 PM, Kang Yang wrote: > >>> > >>> On 4/20/2025 11:18 PM, Walt Holman wrote: > >>>> On Fri, Apr 18, 2025 at 4:18 PM Walt Holman <waltholman09@gmail.com> > >>>> wrote: > >>>>> On Tue, Apr 15, 2025 at 4:23 PM Walt Holman <waltholman09@gmail.com> > >>>>> wrote: > >>>>>> On Thu, Apr 10, 2025 at 10:32 AM Walt Holman > >>>>>> <waltholman09@gmail.com> wrote: > >>>>>>> On Thu, Apr 10, 2025 at 3:26 AM Kang Yang > >>>>>>> <kang.yang@oss.qualcomm.com> wrote: > >>>>>>>> > >>>>>>>> > >>>>>>>> On 4/10/2025 3:37 AM, Walt Holman wrote: > >>>>>>>>> On Tue, Apr 8, 2025 at 4:17 AM Kang Yang > >>>>>>>>> <quic_kangyang@quicinc.com> wrote: > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> On 4/8/2025 1:49 AM, Walt Holman wrote: > >>>>>>>>>>> Attached is a small packet capture where I did an 'iw wlp99s0 > >>>>>>>>>>> scan' > >>>>>>>>>>> and also deactivated and reactivated wireless while the scan was > >>>>>>>>>>> ongoing. Hopefully there's something interesting for you in there. > >>>>>>>>>>> Also, I've take 3 screenshots showing the configs of the > >>>>>>>>>>> wireless AP > >>>>>>>>>>> for the 6ghz network. The first screen is just the definition > >>>>>>>>>>> of the > >>>>>>>>>>> network. No advanced settings are used. The 2nd screen shows the > >>>>>>>>>>> channels and radio enabled. The 3rd screen has the advanced > >>>>>>>>>>> (professional) settings for the network. I believe I changed > >>>>>>>>>>> 'Agile > >>>>>>>>>>> Multiband' to enabled, but other settings are their defaults. Hope > >>>>>>>>>>> some of this helps. Let me know if you need anything else. Thanks, > >>>>>>>>>>> > >>>>>>>>>> Your packets are Ethernet packets. I need wireless packets. > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> Not sure if you know how to add a seperate monitor interface to > >>>>>>>>>> capture > >>>>>>>>>> 6 G channels' packet on your AP(you can google for specific > >>>>>>>>>> command). > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> Also, please capture firmware log: > >>>>>>>>>> > >>>>>>>>>> 1. sudo apt install trace-cmd > >>>>>>>>>> 2. sudo trace-cmd record -e ath12k_wmi_diag > >>>>>>>>>> 3. run test > >>>>>>>>>> 4. "ctrl c" to stop recording: > >>>>>>>>>> Hit Ctrl^C to stop recording > >>>>>>>>>> ^CCPU0 data recorded at offset=0xdf5000 > >>>>>>>>>> 2605056 bytes in size > >>>>>>>>>> Then share the trace.dat to us. > >>>>>>>>>> > >>>>>>>>>> So you need to: > >>>>>>>>>> 1. try to capture wireless packets. > >>>>>>>>>> 2. capture firmware log(trade.data). > >>>>>>>>>> 3. save kernel/wpa_supplicant/iw logs. > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>>> -Walt > >>>>>>>>>>> > >>>>>>>>>>> On Sun, Apr 6, 2025 at 8:58 PM Kang Yang > >>>>>>>>>>> <quic_kangyang@quicinc.com> wrote: > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> On 4/4/2025 12:04 AM, Walt Holman wrote: > >>>>>>>>>>>>> On Thu, Apr 3, 2025 at 3:20 AM Kang Yang > >>>>>>>>>>>>> <quic_kangyang@quicinc.com> wrote: > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> On 4/3/2025 1:48 AM, Walt Holman wrote: > >>>>>>>>>>>>>>> On Tue, Apr 1, 2025 at 9:48 PM Kang Yang > >>>>>>>>>>>>>>> <quic_kangyang@quicinc.com> wrote: > >>>>>>>>>>>>>>>> Test on 6.14.0-rc5-wt-ath+, with the firmware you used. > >>>>>>>>>>>>>>>> I can get 6 GHz AP and connect to it. > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> ath12k_pci 0000:03:00.0: fw_version 0x100301e1 > >>>>>>>>>>>>>>>> fw_build_timestamp > >>>>>>>>>>>>>>>> 2023-12-06 04:05 fw_build_id > >>>>>>>>>>>>>>>> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481- > >>>>>>>>>>>>>>>> QCAHMTSWPL_V1.0_V2.0_SILICONZ-3 > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> yk@yk-Mayan:~$ sudo iw wls1 scan | tee iw_scan.log: > >>>>>>>>>>>>>>>> BSS 62:03:7f:12:64:64(on wls1) -- associated > >>>>>>>>>>>>>>>> TSF: 606308271476 usec (7d, 00:25:08) > >>>>>>>>>>>>>>>> freq: 6275 > >>>>>>>>>>>>>>>> beacon interval: 100 TUs > >>>>>>>>>>>>>>>> capability: ESS Privacy SpectrumMgmt > >>>>>>>>>>>>>>>> ShortSlotTime (0x0511) > >>>>>>>>>>>>>>>> signal: -17.00 dBm > >>>>>>>>>>>>>>>> last seen: 52 ms ago > >>>>>>>>>>>>>>>> Information elements from Probe Response frame: > >>>>>>>>>>>>>>>> SSID: MLO-KANG-6G > >>>>>>>>>>>>>>>> and other 6 GHz APs: > >>>>>>>>>>>>>>>> SSID: 6G-gxia > >>>>>>>>>>>>>>>> SSID: NETGEAR97-6G > >>>>>>>>>>>>>>>> …… > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> kernel log: > >>>>>>>>>>>>>>>> [88158.033218] wls1: Inserted STA 62:03:7f:12:64:64 > >>>>>>>>>>>>>>>> [88158.033232] wls1: authenticate with 62:03:7f:12:64:64 > >>>>>>>>>>>>>>>> (local > >>>>>>>>>>>>>>>> address=00:03:7f:37:12:54) > >>>>>>>>>>>>>>>> [88158.033242] wls1: send auth to 62:03:7f:12:64:64 (try 1/3) > >>>>>>>>>>>>>>>> [88158.041895] wls1: authenticated > >>>>>>>>>>>>>>>> [88158.041914] wls1: moving STA 62:03:7f:12:64:64 to state 2 > >>>>>>>>>>>>>>>> [88158.044291] wls1: determined local STA to be EHT, BW > >>>>>>>>>>>>>>>> limited to 320 MHz > >>>>>>>>>>>>>>>> [88158.045719] wls1: associate with 62:03:7f:12:64:64 (try > >>>>>>>>>>>>>>>> 1/3) > >>>>>>>>>>>>>>>> [88158.067045] wls1: RX AssocResp from 62:03:7f:12:64:64 > >>>>>>>>>>>>>>>> (capab=0x511 > >>>>>>>>>>>>>>>> status=0 aid=4) > >>>>>>>>>>>>>>>> [88158.089090] wls1: associated > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> I can even connect to it by Ubuntu GUI. > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> Can you update to 6.14.0-rc5-wt-ath+ and have a retry? > >>>>>>>>>>>>>>>> Also please make > >>>>>>>>>>>>>>>> sure that your wpa_supplicant/iw support 6 GHz(or directly > >>>>>>>>>>>>>>>> update to the > >>>>>>>>>>>>>>>> latest version). > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> If you still cannot find 6 GHz AP, you can set debug_mask > >>>>>>>>>>>>>>>> to 0xffffffff > >>>>>>>>>>>>>>>> to get ath12k logs. Then give it to us. > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> -Walt > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> OK, I retested with the wt-ath 033125 tagged build. This > >>>>>>>>>>>>>>> included the > >>>>>>>>>>>>>>> patch the Jeff suggested I try, but the rest of the tree > >>>>>>>>>>>>>>> was clean. > >>>>>>>>>>>>>>> Still no 6ghz Wifi. I'm attaching a log file of the boot > >>>>>>>>>>>>>>> and first few > >>>>>>>>>>>>>>> seconds with the debug mask turned on. I noticed that if I > >>>>>>>>>>>>>>> rmmod the > >>>>>>>>>>>>>>> module and then modprobe it, it complains about not finding > >>>>>>>>>>>>>>> firmware-2.bin, however, I thought that was only for the > >>>>>>>>>>>>>>> qcn based > >>>>>>>>>>>>>>> chip? The HW info from dmesg looks like this: > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>> I cannot find this tag... > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> From the log, the 6 GHz channel should work. When scan > >>>>>>>>>>>>>> is triggered, FW > >>>>>>>>>>>>>> shall send probe req on these channels. If AP send probe > >>>>>>>>>>>>>> resp, station > >>>>>>>>>>>>>> shall find the AP. > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>>> [ 6.070282] ath12k_pci 0000:63:00.0: BAR 0 [mem > >>>>>>>>>>>>>>> 0xdd800000-0xdd9fffff 64bit]: assigned > >>>>>>>>>>>>>>> [ 6.070310] ath12k_pci 0000:63:00.0: enabling device > >>>>>>>>>>>>>>> (0000 -> 0002) > >>>>>>>>>>>>>>> [ 6.071249] ath12k_pci 0000:63:00.0: MSI vectors: 16 > >>>>>>>>>>>>>>> [ 6.071254] ath12k_pci 0000:63:00.0: Hardware name: > >>>>>>>>>>>>>>> wcn7850 hw2.0 > >>>>>>>>>>>>>>> [ 6.596331] ath12k_pci 0000:63:00.0: qmi dma allocation > >>>>>>>>>>>>>>> failed > >>>>>>>>>>>>>>> (7077888 B type 1), will try later with sma > >>>>>>>>>>>>>>> ll size > >>>>>>>>>>>>>>> [ 6.604041] ath12k_pci 0000:63:00.0: chip_id 0x2 > >>>>>>>>>>>>>>> chip_family 0x4 > >>>>>>>>>>>>>>> board_id 0xff soc_id 0x40170200 > >>>>>>>>>>>>>>> [ 6.604044] ath12k_pci 0000:63:00.0: fw_version 0x100301e1 > >>>>>>>>>>>>>>> fw_build_timestamp 2023-12-06 04:05 fw_build_id > >>>>>>>>>>>>>>> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481- > >>>>>>>>>>>>>>> QCAHMTSWPL_V1.0_V2.0_SILICONZ- > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> Also, I noticed when looking through the debug logs there > >>>>>>>>>>>>>>> are the > >>>>>>>>>>>>>>> occasional WARNING statements from a BUG it appears. They > >>>>>>>>>>>>>>> trace back > >>>>>>>>>>>>>>> to the mac.c file inside the ath12k code. There should be > >>>>>>>>>>>>>>> some in the > >>>>>>>>>>>>>>> debug log that's attached. Let me know if I can do anything > >>>>>>>>>>>>>>> else. > >>>>>>>>>>>>>>> Thanks, > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> I have never seen this warning on my upstream setup...Not > >>>>>>>>>>>>>> sure if you > >>>>>>>>>>>>>> have changed anything or using the correct code base. > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> Jeff merged this patch-set into ath-202504021602. Can you > >>>>>>>>>>>>>> try on this > >>>>>>>>>>>>>> branch? > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> git clone https://git.kernel.org/pub/scm/linux/kernel/git/ > >>>>>>>>>>>>>> ath/ath.git/ > >>>>>>>>>>>>>> git pull > >>>>>>>>>>>>>> git reset --hard ath-202504021602 > >>>>>>>>>>>>>> compile and install... > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> Also make sure that the firmware you used is from the same > >>>>>>>>>>>>>> folder, don't > >>>>>>>>>>>>>> mix with other folders: > >>>>>>>>>>>>>> linux-firmware/ath12k/WCN7850/hw2.0 > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> 1. rmmod/insmod(debug_mask=0xffff) > >>>>>>>>>>>>>> 2. iw reg get > >>>>>>>>>>>>>> 3. iw reg set US > >>>>>>>>>>>>>> 4. iw xxx scan > >>>>>>>>>>>>>> wait and collect logs. > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> don't do anything else. > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> Also, can you show me your AP configuration. > >>>>>>>>>>>>>> If you have another 6 GHz AP, you can have a try(better > >>>>>>>>>>>>>> different brands). > >>>>>>>>>>>>>> > >>>>>>>>>>>> Thanks for testing. > >>>>>>>>>>>> > >>>>>>>>>>>> Could you share your AP configuration? > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>>>> If you have sniffer, could please capture packets during > >>>>>>>>>>>>>> testing? > >>>>>>>>>>>> > >>>>>>>>>>>> Can you capture packets during the testing? I need to check > >>>>>>>>>>>> probe req > >>>>>>>>>>>> and probe resp. > >>>>>>>>>>>> > >>>>>>>>>>>>>> Thanks! > >>>>>>>>>>>>>> > >>>>>>>>>>>>>>> -Walt > >>>>>>>>>>>>> OK, I cloned and built the kernel based on your instructions > >>>>>>>>>>>>> in your > >>>>>>>>>>>>> last email. Originally, the result was identical to my last > >>>>>>>>>>>>> email, > >>>>>>>>>>>>> including the WARNINGS. The .config I use is configured for a > >>>>>>>>>>>>> fully RT > >>>>>>>>>>>>> PREEMPT kernel, which I wondered if that was why I was > >>>>>>>>>>>>> receiving the > >>>>>>>>>>>>> WARNING. So I configured it as a Low Latency PREEMPT Desktop > >>>>>>>>>>>>> without > >>>>>>>>>>>>> the RT_PREEMPT and that eliminated the WARNING. However, > >>>>>>>>>>>>> still no 6Ghz > >>>>>>>>>>>>> networks. The firmware I'm using is straight from kernel.org > >>>>>>>>>>>>> GIT and I > >>>>>>>>>>>>> do a 'make install; make dedup' to install it. I believe it > >>>>>>>>>>>>> should be > >>>>>>>>>>>>> good. Attached is the latest log file. > >>>>>>>>>>>>> > >>>>>>>>>>>>> -Walt > >>>>>>>>> > >>>>>>>>> Sorry for the top-post earlier. I can't figure out how to capture > >>>>>>>>> the > >>>>>>>>> wireless packets as my chip/driver combo doesn't support monitor > >>>>>>>>> mode. > >>>>>>>> Your AP also cannot capture wireless packets? > >>>>>>>> log in AP by usbserial or ssh. > >>>>>>>> Try to enter command line. use iw command to create monitor > >>>>>>>> interface. > >>>>>>>> Then use tcpdump to capture packets. > >>>>>>>> > >>>>>>>>> I've attached a tarball that contains the trace data and additional > >>>>>>>>> firmware logs from the kernel.log file. Anything else you need, just > >>>>>>>>> ask. Thanks for your help, > >>>>>>>> > >>>>>>>> Your AP mac address? > >>>>>>>> Need it to help check the fw log. > >>>>>>>> > >>>>>>>> > >>>>>>>>> -Walt > >>>>>>> Sorry, the AP doesn't have tcpdump available on it. Also, this is a > >>>>>>> mesh setup with 3 nodes total. The main AP and 2 mesh nodes. I'm > >>>>>>> within 10 feet of one of the nodes and it's MAC for the wireless 6ghz > >>>>>>> network is: 10:7C:61:6F:2A:CA > >>>>>>> > >>>>>>> -Walt > >>>>>> The other 2 node 6ghz mac addresses are: > >>>>>> 10:7C:61:6F:1F:11 - Router > >>>>>> 10:7C:61:6F:32:92 - Node > >>>>>> > >>>>>> The first MAC address I gave you earlier was a node located > >>>>>> approximately 5 feet from where the laptop is. > >>>>>> > >>>>>> -Walt > >>>>> Well, I'm running into a brick wall it seems trying to get 6Ghz > >>>>> enabled on this. I tried the ath-next-20250418 tag just now and still > >>>>> don't see or connect to my 6Ghz network. I applied the patches in: > >>>>> https://lore.kernel.org/linux-wireless/20250418-ath12k-6g-lp-vlp- > >>>>> v1-0-c869c86cad60@quicinc.com/T/#t > >>>>> > >>>>> hoping that would help, but alas, no 6Ghz networks. I see that MLO and > >>>>> other nice fixes are coming in 6.16, but without 6Ghz, they'll do me > >>>>> no good. I'm really wondering if it's a firmware issue that excludes > >>>>> my chip or something. Again, anything I can do to help, let me know. > >>>>> Thanks, > >>>>> > >>>>> -Walt > >>>> Well, I used the swiss army tools to look at the firmware, and my chip > >>>> is listed in the firmware, so it's not excluded or anything. Really > >>>> puzzlling issue as my other two laptops connect to the 6Ghz network > >>>> just fine, and this laptop does in Windows, just not in Linux. I > >>>> really don't use Windows at all though, so that does me no good. > >>>> > >>>> This laptop used to connect to the 6Ghz network around the Sep. - Oct. > >>>> 2024 timeframe. Something has changed and now it doesn't. I'm going to > >>>> boot off a live image of Ubuntu 24.10 and see if I can see the > >>>> network. It was always hit or miss so we'll see. > >>>> -Walt > >>> > >>> > >>> Can you find 6 GHz AP now? > >>> > >> > >> Our firmware team said you station device sent the probe request but > >> didn't receive the probe resp or beacon. > >> > >> Since your current configuration is single 6 GHz AP. Could you change > >> your AP configuration to 6 GHz + 2/5 GHz to have a retry? > >> > > I adedd another network with 2.4 / 5 / 6Ghz settings and still only > > connect to the 5Ghz network portion. This is verified through wavemon > > and the AP. I saw some patches recently to address 6 Ghz operatoins in > > various modes (https://lore.kernel.org/linux-wireless/1692f2f8-c77e-87ce-db70-00b4d9fc7c95@oss.qualcomm.com/), > > but the patch doesn't apply cleanly to current or ath-pending. Don't > > know that it would help, but it seemed interesting. > > > > When I went back to the older kernel / distro I still could not see > > the 6 Ghz band nor connect to it. I think something has changed on the > > AP as well, as this used to work intermittently. I think I have > > mentioned this before, but I have a dual-boot setup on this laptop and > > in Windows 11, it does see and connect to the 6 Ghz band and MLO works > > as well. Also, I have about 5 other devices (phones and laptops) that > > can all connect to the 6 Ghz band. I think it's a combination of the > > AP and the driver / firmware. > > > > > Do you have another WCN7850? > Our monitor mode is now in pending branch, and one fix is coming so that > you can use WCN7850 to capture 6 GHz management packects. So that our > firmware team can do further research. I do have another m.2 card, however, I purchased the one I've got installed due to the original card having the same issues. Think I'll sit tight for a couple days and see how the fix goes in for the pending tree and try that with monitor mode as well to get a better look. Thank you for your help, -Walt ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ath12k: No 6GHz Wireless found 2025-05-16 3:06 ` Kang Yang 2025-05-16 18:09 ` Walt Holman @ 2025-05-21 5:05 ` Walt Holman 2025-05-21 6:06 ` Kang Yang 1 sibling, 1 reply; 32+ messages in thread From: Walt Holman @ 2025-05-21 5:05 UTC (permalink / raw) To: Kang Yang; +Cc: Jeff Johnson, linux-wireless, ath12k@lists.infradead.org [-- Attachment #1: Type: text/plain, Size: 16631 bytes --] On Thu, May 15, 2025 at 10:06 PM Kang Yang <quic_kangyang@quicinc.com> wrote: > > > > On 5/16/2025 1:47 AM, Walt Holman wrote: > > On Thu, May 15, 2025 at 4:22 AM Kang Yang <quic_kangyang@quicinc.com> wrote: > >> > >> > >> > >> On 5/15/2025 4:12 PM, Kang Yang wrote: > >>> > >>> On 4/20/2025 11:18 PM, Walt Holman wrote: > >>>> On Fri, Apr 18, 2025 at 4:18 PM Walt Holman <waltholman09@gmail.com> > >>>> wrote: > >>>>> On Tue, Apr 15, 2025 at 4:23 PM Walt Holman <waltholman09@gmail.com> > >>>>> wrote: > >>>>>> On Thu, Apr 10, 2025 at 10:32 AM Walt Holman > >>>>>> <waltholman09@gmail.com> wrote: > >>>>>>> On Thu, Apr 10, 2025 at 3:26 AM Kang Yang > >>>>>>> <kang.yang@oss.qualcomm.com> wrote: > >>>>>>>> > >>>>>>>> > >>>>>>>> On 4/10/2025 3:37 AM, Walt Holman wrote: > >>>>>>>>> On Tue, Apr 8, 2025 at 4:17 AM Kang Yang > >>>>>>>>> <quic_kangyang@quicinc.com> wrote: > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> On 4/8/2025 1:49 AM, Walt Holman wrote: > >>>>>>>>>>> Attached is a small packet capture where I did an 'iw wlp99s0 > >>>>>>>>>>> scan' > >>>>>>>>>>> and also deactivated and reactivated wireless while the scan was > >>>>>>>>>>> ongoing. Hopefully there's something interesting for you in there. > >>>>>>>>>>> Also, I've take 3 screenshots showing the configs of the > >>>>>>>>>>> wireless AP > >>>>>>>>>>> for the 6ghz network. The first screen is just the definition > >>>>>>>>>>> of the > >>>>>>>>>>> network. No advanced settings are used. The 2nd screen shows the > >>>>>>>>>>> channels and radio enabled. The 3rd screen has the advanced > >>>>>>>>>>> (professional) settings for the network. I believe I changed > >>>>>>>>>>> 'Agile > >>>>>>>>>>> Multiband' to enabled, but other settings are their defaults. Hope > >>>>>>>>>>> some of this helps. Let me know if you need anything else. Thanks, > >>>>>>>>>>> > >>>>>>>>>> Your packets are Ethernet packets. I need wireless packets. > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> Not sure if you know how to add a seperate monitor interface to > >>>>>>>>>> capture > >>>>>>>>>> 6 G channels' packet on your AP(you can google for specific > >>>>>>>>>> command). > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> Also, please capture firmware log: > >>>>>>>>>> > >>>>>>>>>> 1. sudo apt install trace-cmd > >>>>>>>>>> 2. sudo trace-cmd record -e ath12k_wmi_diag > >>>>>>>>>> 3. run test > >>>>>>>>>> 4. "ctrl c" to stop recording: > >>>>>>>>>> Hit Ctrl^C to stop recording > >>>>>>>>>> ^CCPU0 data recorded at offset=0xdf5000 > >>>>>>>>>> 2605056 bytes in size > >>>>>>>>>> Then share the trace.dat to us. > >>>>>>>>>> > >>>>>>>>>> So you need to: > >>>>>>>>>> 1. try to capture wireless packets. > >>>>>>>>>> 2. capture firmware log(trade.data). > >>>>>>>>>> 3. save kernel/wpa_supplicant/iw logs. > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>>> -Walt > >>>>>>>>>>> > >>>>>>>>>>> On Sun, Apr 6, 2025 at 8:58 PM Kang Yang > >>>>>>>>>>> <quic_kangyang@quicinc.com> wrote: > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> On 4/4/2025 12:04 AM, Walt Holman wrote: > >>>>>>>>>>>>> On Thu, Apr 3, 2025 at 3:20 AM Kang Yang > >>>>>>>>>>>>> <quic_kangyang@quicinc.com> wrote: > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> On 4/3/2025 1:48 AM, Walt Holman wrote: > >>>>>>>>>>>>>>> On Tue, Apr 1, 2025 at 9:48 PM Kang Yang > >>>>>>>>>>>>>>> <quic_kangyang@quicinc.com> wrote: > >>>>>>>>>>>>>>>> Test on 6.14.0-rc5-wt-ath+, with the firmware you used. > >>>>>>>>>>>>>>>> I can get 6 GHz AP and connect to it. > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> ath12k_pci 0000:03:00.0: fw_version 0x100301e1 > >>>>>>>>>>>>>>>> fw_build_timestamp > >>>>>>>>>>>>>>>> 2023-12-06 04:05 fw_build_id > >>>>>>>>>>>>>>>> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481- > >>>>>>>>>>>>>>>> QCAHMTSWPL_V1.0_V2.0_SILICONZ-3 > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> yk@yk-Mayan:~$ sudo iw wls1 scan | tee iw_scan.log: > >>>>>>>>>>>>>>>> BSS 62:03:7f:12:64:64(on wls1) -- associated > >>>>>>>>>>>>>>>> TSF: 606308271476 usec (7d, 00:25:08) > >>>>>>>>>>>>>>>> freq: 6275 > >>>>>>>>>>>>>>>> beacon interval: 100 TUs > >>>>>>>>>>>>>>>> capability: ESS Privacy SpectrumMgmt > >>>>>>>>>>>>>>>> ShortSlotTime (0x0511) > >>>>>>>>>>>>>>>> signal: -17.00 dBm > >>>>>>>>>>>>>>>> last seen: 52 ms ago > >>>>>>>>>>>>>>>> Information elements from Probe Response frame: > >>>>>>>>>>>>>>>> SSID: MLO-KANG-6G > >>>>>>>>>>>>>>>> and other 6 GHz APs: > >>>>>>>>>>>>>>>> SSID: 6G-gxia > >>>>>>>>>>>>>>>> SSID: NETGEAR97-6G > >>>>>>>>>>>>>>>> …… > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> kernel log: > >>>>>>>>>>>>>>>> [88158.033218] wls1: Inserted STA 62:03:7f:12:64:64 > >>>>>>>>>>>>>>>> [88158.033232] wls1: authenticate with 62:03:7f:12:64:64 > >>>>>>>>>>>>>>>> (local > >>>>>>>>>>>>>>>> address=00:03:7f:37:12:54) > >>>>>>>>>>>>>>>> [88158.033242] wls1: send auth to 62:03:7f:12:64:64 (try 1/3) > >>>>>>>>>>>>>>>> [88158.041895] wls1: authenticated > >>>>>>>>>>>>>>>> [88158.041914] wls1: moving STA 62:03:7f:12:64:64 to state 2 > >>>>>>>>>>>>>>>> [88158.044291] wls1: determined local STA to be EHT, BW > >>>>>>>>>>>>>>>> limited to 320 MHz > >>>>>>>>>>>>>>>> [88158.045719] wls1: associate with 62:03:7f:12:64:64 (try > >>>>>>>>>>>>>>>> 1/3) > >>>>>>>>>>>>>>>> [88158.067045] wls1: RX AssocResp from 62:03:7f:12:64:64 > >>>>>>>>>>>>>>>> (capab=0x511 > >>>>>>>>>>>>>>>> status=0 aid=4) > >>>>>>>>>>>>>>>> [88158.089090] wls1: associated > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> I can even connect to it by Ubuntu GUI. > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> Can you update to 6.14.0-rc5-wt-ath+ and have a retry? > >>>>>>>>>>>>>>>> Also please make > >>>>>>>>>>>>>>>> sure that your wpa_supplicant/iw support 6 GHz(or directly > >>>>>>>>>>>>>>>> update to the > >>>>>>>>>>>>>>>> latest version). > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> If you still cannot find 6 GHz AP, you can set debug_mask > >>>>>>>>>>>>>>>> to 0xffffffff > >>>>>>>>>>>>>>>> to get ath12k logs. Then give it to us. > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> -Walt > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> OK, I retested with the wt-ath 033125 tagged build. This > >>>>>>>>>>>>>>> included the > >>>>>>>>>>>>>>> patch the Jeff suggested I try, but the rest of the tree > >>>>>>>>>>>>>>> was clean. > >>>>>>>>>>>>>>> Still no 6ghz Wifi. I'm attaching a log file of the boot > >>>>>>>>>>>>>>> and first few > >>>>>>>>>>>>>>> seconds with the debug mask turned on. I noticed that if I > >>>>>>>>>>>>>>> rmmod the > >>>>>>>>>>>>>>> module and then modprobe it, it complains about not finding > >>>>>>>>>>>>>>> firmware-2.bin, however, I thought that was only for the > >>>>>>>>>>>>>>> qcn based > >>>>>>>>>>>>>>> chip? The HW info from dmesg looks like this: > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>> I cannot find this tag... > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> From the log, the 6 GHz channel should work. When scan > >>>>>>>>>>>>>> is triggered, FW > >>>>>>>>>>>>>> shall send probe req on these channels. If AP send probe > >>>>>>>>>>>>>> resp, station > >>>>>>>>>>>>>> shall find the AP. > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>>> [ 6.070282] ath12k_pci 0000:63:00.0: BAR 0 [mem > >>>>>>>>>>>>>>> 0xdd800000-0xdd9fffff 64bit]: assigned > >>>>>>>>>>>>>>> [ 6.070310] ath12k_pci 0000:63:00.0: enabling device > >>>>>>>>>>>>>>> (0000 -> 0002) > >>>>>>>>>>>>>>> [ 6.071249] ath12k_pci 0000:63:00.0: MSI vectors: 16 > >>>>>>>>>>>>>>> [ 6.071254] ath12k_pci 0000:63:00.0: Hardware name: > >>>>>>>>>>>>>>> wcn7850 hw2.0 > >>>>>>>>>>>>>>> [ 6.596331] ath12k_pci 0000:63:00.0: qmi dma allocation > >>>>>>>>>>>>>>> failed > >>>>>>>>>>>>>>> (7077888 B type 1), will try later with sma > >>>>>>>>>>>>>>> ll size > >>>>>>>>>>>>>>> [ 6.604041] ath12k_pci 0000:63:00.0: chip_id 0x2 > >>>>>>>>>>>>>>> chip_family 0x4 > >>>>>>>>>>>>>>> board_id 0xff soc_id 0x40170200 > >>>>>>>>>>>>>>> [ 6.604044] ath12k_pci 0000:63:00.0: fw_version 0x100301e1 > >>>>>>>>>>>>>>> fw_build_timestamp 2023-12-06 04:05 fw_build_id > >>>>>>>>>>>>>>> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481- > >>>>>>>>>>>>>>> QCAHMTSWPL_V1.0_V2.0_SILICONZ- > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> Also, I noticed when looking through the debug logs there > >>>>>>>>>>>>>>> are the > >>>>>>>>>>>>>>> occasional WARNING statements from a BUG it appears. They > >>>>>>>>>>>>>>> trace back > >>>>>>>>>>>>>>> to the mac.c file inside the ath12k code. There should be > >>>>>>>>>>>>>>> some in the > >>>>>>>>>>>>>>> debug log that's attached. Let me know if I can do anything > >>>>>>>>>>>>>>> else. > >>>>>>>>>>>>>>> Thanks, > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> I have never seen this warning on my upstream setup...Not > >>>>>>>>>>>>>> sure if you > >>>>>>>>>>>>>> have changed anything or using the correct code base. > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> Jeff merged this patch-set into ath-202504021602. Can you > >>>>>>>>>>>>>> try on this > >>>>>>>>>>>>>> branch? > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> git clone https://git.kernel.org/pub/scm/linux/kernel/git/ > >>>>>>>>>>>>>> ath/ath.git/ > >>>>>>>>>>>>>> git pull > >>>>>>>>>>>>>> git reset --hard ath-202504021602 > >>>>>>>>>>>>>> compile and install... > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> Also make sure that the firmware you used is from the same > >>>>>>>>>>>>>> folder, don't > >>>>>>>>>>>>>> mix with other folders: > >>>>>>>>>>>>>> linux-firmware/ath12k/WCN7850/hw2.0 > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> 1. rmmod/insmod(debug_mask=0xffff) > >>>>>>>>>>>>>> 2. iw reg get > >>>>>>>>>>>>>> 3. iw reg set US > >>>>>>>>>>>>>> 4. iw xxx scan > >>>>>>>>>>>>>> wait and collect logs. > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> don't do anything else. > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> Also, can you show me your AP configuration. > >>>>>>>>>>>>>> If you have another 6 GHz AP, you can have a try(better > >>>>>>>>>>>>>> different brands). > >>>>>>>>>>>>>> > >>>>>>>>>>>> Thanks for testing. > >>>>>>>>>>>> > >>>>>>>>>>>> Could you share your AP configuration? > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>>>> If you have sniffer, could please capture packets during > >>>>>>>>>>>>>> testing? > >>>>>>>>>>>> > >>>>>>>>>>>> Can you capture packets during the testing? I need to check > >>>>>>>>>>>> probe req > >>>>>>>>>>>> and probe resp. > >>>>>>>>>>>> > >>>>>>>>>>>>>> Thanks! > >>>>>>>>>>>>>> > >>>>>>>>>>>>>>> -Walt > >>>>>>>>>>>>> OK, I cloned and built the kernel based on your instructions > >>>>>>>>>>>>> in your > >>>>>>>>>>>>> last email. Originally, the result was identical to my last > >>>>>>>>>>>>> email, > >>>>>>>>>>>>> including the WARNINGS. The .config I use is configured for a > >>>>>>>>>>>>> fully RT > >>>>>>>>>>>>> PREEMPT kernel, which I wondered if that was why I was > >>>>>>>>>>>>> receiving the > >>>>>>>>>>>>> WARNING. So I configured it as a Low Latency PREEMPT Desktop > >>>>>>>>>>>>> without > >>>>>>>>>>>>> the RT_PREEMPT and that eliminated the WARNING. However, > >>>>>>>>>>>>> still no 6Ghz > >>>>>>>>>>>>> networks. The firmware I'm using is straight from kernel.org > >>>>>>>>>>>>> GIT and I > >>>>>>>>>>>>> do a 'make install; make dedup' to install it. I believe it > >>>>>>>>>>>>> should be > >>>>>>>>>>>>> good. Attached is the latest log file. > >>>>>>>>>>>>> > >>>>>>>>>>>>> -Walt > >>>>>>>>> > >>>>>>>>> Sorry for the top-post earlier. I can't figure out how to capture > >>>>>>>>> the > >>>>>>>>> wireless packets as my chip/driver combo doesn't support monitor > >>>>>>>>> mode. > >>>>>>>> Your AP also cannot capture wireless packets? > >>>>>>>> log in AP by usbserial or ssh. > >>>>>>>> Try to enter command line. use iw command to create monitor > >>>>>>>> interface. > >>>>>>>> Then use tcpdump to capture packets. > >>>>>>>> > >>>>>>>>> I've attached a tarball that contains the trace data and additional > >>>>>>>>> firmware logs from the kernel.log file. Anything else you need, just > >>>>>>>>> ask. Thanks for your help, > >>>>>>>> > >>>>>>>> Your AP mac address? > >>>>>>>> Need it to help check the fw log. > >>>>>>>> > >>>>>>>> > >>>>>>>>> -Walt > >>>>>>> Sorry, the AP doesn't have tcpdump available on it. Also, this is a > >>>>>>> mesh setup with 3 nodes total. The main AP and 2 mesh nodes. I'm > >>>>>>> within 10 feet of one of the nodes and it's MAC for the wireless 6ghz > >>>>>>> network is: 10:7C:61:6F:2A:CA > >>>>>>> > >>>>>>> -Walt > >>>>>> The other 2 node 6ghz mac addresses are: > >>>>>> 10:7C:61:6F:1F:11 - Router > >>>>>> 10:7C:61:6F:32:92 - Node > >>>>>> > >>>>>> The first MAC address I gave you earlier was a node located > >>>>>> approximately 5 feet from where the laptop is. > >>>>>> > >>>>>> -Walt > >>>>> Well, I'm running into a brick wall it seems trying to get 6Ghz > >>>>> enabled on this. I tried the ath-next-20250418 tag just now and still > >>>>> don't see or connect to my 6Ghz network. I applied the patches in: > >>>>> https://lore.kernel.org/linux-wireless/20250418-ath12k-6g-lp-vlp- > >>>>> v1-0-c869c86cad60@quicinc.com/T/#t > >>>>> > >>>>> hoping that would help, but alas, no 6Ghz networks. I see that MLO and > >>>>> other nice fixes are coming in 6.16, but without 6Ghz, they'll do me > >>>>> no good. I'm really wondering if it's a firmware issue that excludes > >>>>> my chip or something. Again, anything I can do to help, let me know. > >>>>> Thanks, > >>>>> > >>>>> -Walt > >>>> Well, I used the swiss army tools to look at the firmware, and my chip > >>>> is listed in the firmware, so it's not excluded or anything. Really > >>>> puzzlling issue as my other two laptops connect to the 6Ghz network > >>>> just fine, and this laptop does in Windows, just not in Linux. I > >>>> really don't use Windows at all though, so that does me no good. > >>>> > >>>> This laptop used to connect to the 6Ghz network around the Sep. - Oct. > >>>> 2024 timeframe. Something has changed and now it doesn't. I'm going to > >>>> boot off a live image of Ubuntu 24.10 and see if I can see the > >>>> network. It was always hit or miss so we'll see. > >>>> -Walt > >>> > >>> > >>> Can you find 6 GHz AP now? > >>> > >> > >> Our firmware team said you station device sent the probe request but > >> didn't receive the probe resp or beacon. > >> > >> Since your current configuration is single 6 GHz AP. Could you change > >> your AP configuration to 6 GHz + 2/5 GHz to have a retry? > >> > > I adedd another network with 2.4 / 5 / 6Ghz settings and still only > > connect to the 5Ghz network portion. This is verified through wavemon > > and the AP. I saw some patches recently to address 6 Ghz operatoins in > > various modes (https://lore.kernel.org/linux-wireless/1692f2f8-c77e-87ce-db70-00b4d9fc7c95@oss.qualcomm.com/), > > but the patch doesn't apply cleanly to current or ath-pending. Don't > > know that it would help, but it seemed interesting. > > > > When I went back to the older kernel / distro I still could not see > > the 6 Ghz band nor connect to it. I think something has changed on the > > AP as well, as this used to work intermittently. I think I have > > mentioned this before, but I have a dual-boot setup on this laptop and > > in Windows 11, it does see and connect to the 6 Ghz band and MLO works > > as well. Also, I have about 5 other devices (phones and laptops) that > > can all connect to the 6 Ghz band. I think it's a combination of the > > AP and the driver / firmware. > > > > > Do you have another WCN7850? > Our monitor mode is now in pending branch, and one fix is coming so that > you can use WCN7850 to capture 6 GHz management packects. So that our > firmware team can do further research. I've successfully put the wifi into monitor mode and captured some traffic. I used freq. 6615, which is the frequency my Holman-6G runs at with a width of 320Mhz. I can see beacons and other wifi related traffic, however, I did not have an encryption key set, so any traffic should still be encrypted. Hopefully the beacons and other things help. I took a chance that the patches were ready and used the most recent tag: ath-pending-202505201841 and it appeared to work OK. Let me know if this helps and if you need anything else. Thanks, -Walt [-- Attachment #2: wifi-packet-capture-20250520.pcapng.gz --] [-- Type: application/gzip, Size: 70410 bytes --] ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ath12k: No 6GHz Wireless found 2025-05-21 5:05 ` Walt Holman @ 2025-05-21 6:06 ` Kang Yang 2025-05-22 17:48 ` Walt Holman 0 siblings, 1 reply; 32+ messages in thread From: Kang Yang @ 2025-05-21 6:06 UTC (permalink / raw) To: Walt Holman; +Cc: Jeff Johnson, linux-wireless, ath12k@lists.infradead.org On 5/21/2025 1:05 PM, Walt Holman wrote: > On Thu, May 15, 2025 at 10:06 PM Kang Yang <quic_kangyang@quicinc.com> wrote: >> >> >> >> On 5/16/2025 1:47 AM, Walt Holman wrote: >>> On Thu, May 15, 2025 at 4:22 AM Kang Yang <quic_kangyang@quicinc.com> wrote: >>>> >>>> >>>> >>>> On 5/15/2025 4:12 PM, Kang Yang wrote: >>>>> >>>>> On 4/20/2025 11:18 PM, Walt Holman wrote: >>>>>> On Fri, Apr 18, 2025 at 4:18 PM Walt Holman <waltholman09@gmail.com> >>>>>> wrote: >>>>>>> On Tue, Apr 15, 2025 at 4:23 PM Walt Holman <waltholman09@gmail.com> >>>>>>> wrote: >>>>>>>> On Thu, Apr 10, 2025 at 10:32 AM Walt Holman >>>>>>>> <waltholman09@gmail.com> wrote: >>>>>>>>> On Thu, Apr 10, 2025 at 3:26 AM Kang Yang >>>>>>>>> <kang.yang@oss.qualcomm.com> wrote: >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On 4/10/2025 3:37 AM, Walt Holman wrote: >>>>>>>>>>> On Tue, Apr 8, 2025 at 4:17 AM Kang Yang >>>>>>>>>>> <quic_kangyang@quicinc.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On 4/8/2025 1:49 AM, Walt Holman wrote: >>>>>>>>>>>>> Attached is a small packet capture where I did an 'iw wlp99s0 >>>>>>>>>>>>> scan' >>>>>>>>>>>>> and also deactivated and reactivated wireless while the scan was >>>>>>>>>>>>> ongoing. Hopefully there's something interesting for you in there. >>>>>>>>>>>>> Also, I've take 3 screenshots showing the configs of the >>>>>>>>>>>>> wireless AP >>>>>>>>>>>>> for the 6ghz network. The first screen is just the definition >>>>>>>>>>>>> of the >>>>>>>>>>>>> network. No advanced settings are used. The 2nd screen shows the >>>>>>>>>>>>> channels and radio enabled. The 3rd screen has the advanced >>>>>>>>>>>>> (professional) settings for the network. I believe I changed >>>>>>>>>>>>> 'Agile >>>>>>>>>>>>> Multiband' to enabled, but other settings are their defaults. Hope >>>>>>>>>>>>> some of this helps. Let me know if you need anything else. Thanks, >>>>>>>>>>>>> >>>>>>>>>>>> Your packets are Ethernet packets. I need wireless packets. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Not sure if you know how to add a seperate monitor interface to >>>>>>>>>>>> capture >>>>>>>>>>>> 6 G channels' packet on your AP(you can google for specific >>>>>>>>>>>> command). >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Also, please capture firmware log: >>>>>>>>>>>> >>>>>>>>>>>> 1. sudo apt install trace-cmd >>>>>>>>>>>> 2. sudo trace-cmd record -e ath12k_wmi_diag >>>>>>>>>>>> 3. run test >>>>>>>>>>>> 4. "ctrl c" to stop recording: >>>>>>>>>>>> Hit Ctrl^C to stop recording >>>>>>>>>>>> ^CCPU0 data recorded at offset=0xdf5000 >>>>>>>>>>>> 2605056 bytes in size >>>>>>>>>>>> Then share the trace.dat to us. >>>>>>>>>>>> >>>>>>>>>>>> So you need to: >>>>>>>>>>>> 1. try to capture wireless packets. >>>>>>>>>>>> 2. capture firmware log(trade.data). >>>>>>>>>>>> 3. save kernel/wpa_supplicant/iw logs. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>>> -Walt >>>>>>>>>>>>> >>>>>>>>>>>>> On Sun, Apr 6, 2025 at 8:58 PM Kang Yang >>>>>>>>>>>>> <quic_kangyang@quicinc.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> On 4/4/2025 12:04 AM, Walt Holman wrote: >>>>>>>>>>>>>>> On Thu, Apr 3, 2025 at 3:20 AM Kang Yang >>>>>>>>>>>>>>> <quic_kangyang@quicinc.com> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On 4/3/2025 1:48 AM, Walt Holman wrote: >>>>>>>>>>>>>>>>> On Tue, Apr 1, 2025 at 9:48 PM Kang Yang >>>>>>>>>>>>>>>>> <quic_kangyang@quicinc.com> wrote: >>>>>>>>>>>>>>>>>> Test on 6.14.0-rc5-wt-ath+, with the firmware you used. >>>>>>>>>>>>>>>>>> I can get 6 GHz AP and connect to it. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> ath12k_pci 0000:03:00.0: fw_version 0x100301e1 >>>>>>>>>>>>>>>>>> fw_build_timestamp >>>>>>>>>>>>>>>>>> 2023-12-06 04:05 fw_build_id >>>>>>>>>>>>>>>>>> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481- >>>>>>>>>>>>>>>>>> QCAHMTSWPL_V1.0_V2.0_SILICONZ-3 >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> yk@yk-Mayan:~$ sudo iw wls1 scan | tee iw_scan.log: >>>>>>>>>>>>>>>>>> BSS 62:03:7f:12:64:64(on wls1) -- associated >>>>>>>>>>>>>>>>>> TSF: 606308271476 usec (7d, 00:25:08) >>>>>>>>>>>>>>>>>> freq: 6275 >>>>>>>>>>>>>>>>>> beacon interval: 100 TUs >>>>>>>>>>>>>>>>>> capability: ESS Privacy SpectrumMgmt >>>>>>>>>>>>>>>>>> ShortSlotTime (0x0511) >>>>>>>>>>>>>>>>>> signal: -17.00 dBm >>>>>>>>>>>>>>>>>> last seen: 52 ms ago >>>>>>>>>>>>>>>>>> Information elements from Probe Response frame: >>>>>>>>>>>>>>>>>> SSID: MLO-KANG-6G >>>>>>>>>>>>>>>>>> and other 6 GHz APs: >>>>>>>>>>>>>>>>>> SSID: 6G-gxia >>>>>>>>>>>>>>>>>> SSID: NETGEAR97-6G >>>>>>>>>>>>>>>>>> …… >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> kernel log: >>>>>>>>>>>>>>>>>> [88158.033218] wls1: Inserted STA 62:03:7f:12:64:64 >>>>>>>>>>>>>>>>>> [88158.033232] wls1: authenticate with 62:03:7f:12:64:64 >>>>>>>>>>>>>>>>>> (local >>>>>>>>>>>>>>>>>> address=00:03:7f:37:12:54) >>>>>>>>>>>>>>>>>> [88158.033242] wls1: send auth to 62:03:7f:12:64:64 (try 1/3) >>>>>>>>>>>>>>>>>> [88158.041895] wls1: authenticated >>>>>>>>>>>>>>>>>> [88158.041914] wls1: moving STA 62:03:7f:12:64:64 to state 2 >>>>>>>>>>>>>>>>>> [88158.044291] wls1: determined local STA to be EHT, BW >>>>>>>>>>>>>>>>>> limited to 320 MHz >>>>>>>>>>>>>>>>>> [88158.045719] wls1: associate with 62:03:7f:12:64:64 (try >>>>>>>>>>>>>>>>>> 1/3) >>>>>>>>>>>>>>>>>> [88158.067045] wls1: RX AssocResp from 62:03:7f:12:64:64 >>>>>>>>>>>>>>>>>> (capab=0x511 >>>>>>>>>>>>>>>>>> status=0 aid=4) >>>>>>>>>>>>>>>>>> [88158.089090] wls1: associated >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> I can even connect to it by Ubuntu GUI. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Can you update to 6.14.0-rc5-wt-ath+ and have a retry? >>>>>>>>>>>>>>>>>> Also please make >>>>>>>>>>>>>>>>>> sure that your wpa_supplicant/iw support 6 GHz(or directly >>>>>>>>>>>>>>>>>> update to the >>>>>>>>>>>>>>>>>> latest version). >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> If you still cannot find 6 GHz AP, you can set debug_mask >>>>>>>>>>>>>>>>>> to 0xffffffff >>>>>>>>>>>>>>>>>> to get ath12k logs. Then give it to us. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> -Walt >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> OK, I retested with the wt-ath 033125 tagged build. This >>>>>>>>>>>>>>>>> included the >>>>>>>>>>>>>>>>> patch the Jeff suggested I try, but the rest of the tree >>>>>>>>>>>>>>>>> was clean. >>>>>>>>>>>>>>>>> Still no 6ghz Wifi. I'm attaching a log file of the boot >>>>>>>>>>>>>>>>> and first few >>>>>>>>>>>>>>>>> seconds with the debug mask turned on. I noticed that if I >>>>>>>>>>>>>>>>> rmmod the >>>>>>>>>>>>>>>>> module and then modprobe it, it complains about not finding >>>>>>>>>>>>>>>>> firmware-2.bin, however, I thought that was only for the >>>>>>>>>>>>>>>>> qcn based >>>>>>>>>>>>>>>>> chip? The HW info from dmesg looks like this: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> I cannot find this tag... >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> From the log, the 6 GHz channel should work. When scan >>>>>>>>>>>>>>>> is triggered, FW >>>>>>>>>>>>>>>> shall send probe req on these channels. If AP send probe >>>>>>>>>>>>>>>> resp, station >>>>>>>>>>>>>>>> shall find the AP. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> [ 6.070282] ath12k_pci 0000:63:00.0: BAR 0 [mem >>>>>>>>>>>>>>>>> 0xdd800000-0xdd9fffff 64bit]: assigned >>>>>>>>>>>>>>>>> [ 6.070310] ath12k_pci 0000:63:00.0: enabling device >>>>>>>>>>>>>>>>> (0000 -> 0002) >>>>>>>>>>>>>>>>> [ 6.071249] ath12k_pci 0000:63:00.0: MSI vectors: 16 >>>>>>>>>>>>>>>>> [ 6.071254] ath12k_pci 0000:63:00.0: Hardware name: >>>>>>>>>>>>>>>>> wcn7850 hw2.0 >>>>>>>>>>>>>>>>> [ 6.596331] ath12k_pci 0000:63:00.0: qmi dma allocation >>>>>>>>>>>>>>>>> failed >>>>>>>>>>>>>>>>> (7077888 B type 1), will try later with sma >>>>>>>>>>>>>>>>> ll size >>>>>>>>>>>>>>>>> [ 6.604041] ath12k_pci 0000:63:00.0: chip_id 0x2 >>>>>>>>>>>>>>>>> chip_family 0x4 >>>>>>>>>>>>>>>>> board_id 0xff soc_id 0x40170200 >>>>>>>>>>>>>>>>> [ 6.604044] ath12k_pci 0000:63:00.0: fw_version 0x100301e1 >>>>>>>>>>>>>>>>> fw_build_timestamp 2023-12-06 04:05 fw_build_id >>>>>>>>>>>>>>>>> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481- >>>>>>>>>>>>>>>>> QCAHMTSWPL_V1.0_V2.0_SILICONZ- >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Also, I noticed when looking through the debug logs there >>>>>>>>>>>>>>>>> are the >>>>>>>>>>>>>>>>> occasional WARNING statements from a BUG it appears. They >>>>>>>>>>>>>>>>> trace back >>>>>>>>>>>>>>>>> to the mac.c file inside the ath12k code. There should be >>>>>>>>>>>>>>>>> some in the >>>>>>>>>>>>>>>>> debug log that's attached. Let me know if I can do anything >>>>>>>>>>>>>>>>> else. >>>>>>>>>>>>>>>>> Thanks, >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> I have never seen this warning on my upstream setup...Not >>>>>>>>>>>>>>>> sure if you >>>>>>>>>>>>>>>> have changed anything or using the correct code base. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Jeff merged this patch-set into ath-202504021602. Can you >>>>>>>>>>>>>>>> try on this >>>>>>>>>>>>>>>> branch? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> git clone https://git.kernel.org/pub/scm/linux/kernel/git/ >>>>>>>>>>>>>>>> ath/ath.git/ >>>>>>>>>>>>>>>> git pull >>>>>>>>>>>>>>>> git reset --hard ath-202504021602 >>>>>>>>>>>>>>>> compile and install... >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Also make sure that the firmware you used is from the same >>>>>>>>>>>>>>>> folder, don't >>>>>>>>>>>>>>>> mix with other folders: >>>>>>>>>>>>>>>> linux-firmware/ath12k/WCN7850/hw2.0 >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> 1. rmmod/insmod(debug_mask=0xffff) >>>>>>>>>>>>>>>> 2. iw reg get >>>>>>>>>>>>>>>> 3. iw reg set US >>>>>>>>>>>>>>>> 4. iw xxx scan >>>>>>>>>>>>>>>> wait and collect logs. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> don't do anything else. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Also, can you show me your AP configuration. >>>>>>>>>>>>>>>> If you have another 6 GHz AP, you can have a try(better >>>>>>>>>>>>>>>> different brands). >>>>>>>>>>>>>>>> >>>>>>>>>>>>>> Thanks for testing. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Could you share your AP configuration? >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>>>> If you have sniffer, could please capture packets during >>>>>>>>>>>>>>>> testing? >>>>>>>>>>>>>> >>>>>>>>>>>>>> Can you capture packets during the testing? I need to check >>>>>>>>>>>>>> probe req >>>>>>>>>>>>>> and probe resp. >>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Thanks! >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> -Walt >>>>>>>>>>>>>>> OK, I cloned and built the kernel based on your instructions >>>>>>>>>>>>>>> in your >>>>>>>>>>>>>>> last email. Originally, the result was identical to my last >>>>>>>>>>>>>>> email, >>>>>>>>>>>>>>> including the WARNINGS. The .config I use is configured for a >>>>>>>>>>>>>>> fully RT >>>>>>>>>>>>>>> PREEMPT kernel, which I wondered if that was why I was >>>>>>>>>>>>>>> receiving the >>>>>>>>>>>>>>> WARNING. So I configured it as a Low Latency PREEMPT Desktop >>>>>>>>>>>>>>> without >>>>>>>>>>>>>>> the RT_PREEMPT and that eliminated the WARNING. However, >>>>>>>>>>>>>>> still no 6Ghz >>>>>>>>>>>>>>> networks. The firmware I'm using is straight from kernel.org >>>>>>>>>>>>>>> GIT and I >>>>>>>>>>>>>>> do a 'make install; make dedup' to install it. I believe it >>>>>>>>>>>>>>> should be >>>>>>>>>>>>>>> good. Attached is the latest log file. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> -Walt >>>>>>>>>>> >>>>>>>>>>> Sorry for the top-post earlier. I can't figure out how to capture >>>>>>>>>>> the >>>>>>>>>>> wireless packets as my chip/driver combo doesn't support monitor >>>>>>>>>>> mode. >>>>>>>>>> Your AP also cannot capture wireless packets? >>>>>>>>>> log in AP by usbserial or ssh. >>>>>>>>>> Try to enter command line. use iw command to create monitor >>>>>>>>>> interface. >>>>>>>>>> Then use tcpdump to capture packets. >>>>>>>>>> >>>>>>>>>>> I've attached a tarball that contains the trace data and additional >>>>>>>>>>> firmware logs from the kernel.log file. Anything else you need, just >>>>>>>>>>> ask. Thanks for your help, >>>>>>>>>> >>>>>>>>>> Your AP mac address? >>>>>>>>>> Need it to help check the fw log. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> -Walt >>>>>>>>> Sorry, the AP doesn't have tcpdump available on it. Also, this is a >>>>>>>>> mesh setup with 3 nodes total. The main AP and 2 mesh nodes. I'm >>>>>>>>> within 10 feet of one of the nodes and it's MAC for the wireless 6ghz >>>>>>>>> network is: 10:7C:61:6F:2A:CA >>>>>>>>> >>>>>>>>> -Walt >>>>>>>> The other 2 node 6ghz mac addresses are: >>>>>>>> 10:7C:61:6F:1F:11 - Router >>>>>>>> 10:7C:61:6F:32:92 - Node >>>>>>>> >>>>>>>> The first MAC address I gave you earlier was a node located >>>>>>>> approximately 5 feet from where the laptop is. >>>>>>>> >>>>>>>> -Walt >>>>>>> Well, I'm running into a brick wall it seems trying to get 6Ghz >>>>>>> enabled on this. I tried the ath-next-20250418 tag just now and still >>>>>>> don't see or connect to my 6Ghz network. I applied the patches in: >>>>>>> https://lore.kernel.org/linux-wireless/20250418-ath12k-6g-lp-vlp- >>>>>>> v1-0-c869c86cad60@quicinc.com/T/#t >>>>>>> >>>>>>> hoping that would help, but alas, no 6Ghz networks. I see that MLO and >>>>>>> other nice fixes are coming in 6.16, but without 6Ghz, they'll do me >>>>>>> no good. I'm really wondering if it's a firmware issue that excludes >>>>>>> my chip or something. Again, anything I can do to help, let me know. >>>>>>> Thanks, >>>>>>> >>>>>>> -Walt >>>>>> Well, I used the swiss army tools to look at the firmware, and my chip >>>>>> is listed in the firmware, so it's not excluded or anything. Really >>>>>> puzzlling issue as my other two laptops connect to the 6Ghz network >>>>>> just fine, and this laptop does in Windows, just not in Linux. I >>>>>> really don't use Windows at all though, so that does me no good. >>>>>> >>>>>> This laptop used to connect to the 6Ghz network around the Sep. - Oct. >>>>>> 2024 timeframe. Something has changed and now it doesn't. I'm going to >>>>>> boot off a live image of Ubuntu 24.10 and see if I can see the >>>>>> network. It was always hit or miss so we'll see. >>>>>> -Walt >>>>> >>>>> >>>>> Can you find 6 GHz AP now? >>>>> >>>> >>>> Our firmware team said you station device sent the probe request but >>>> didn't receive the probe resp or beacon. >>>> >>>> Since your current configuration is single 6 GHz AP. Could you change >>>> your AP configuration to 6 GHz + 2/5 GHz to have a retry? >>>> >>> I adedd another network with 2.4 / 5 / 6Ghz settings and still only >>> connect to the 5Ghz network portion. This is verified through wavemon >>> and the AP. I saw some patches recently to address 6 Ghz operatoins in >>> various modes (https://lore.kernel.org/linux-wireless/1692f2f8-c77e-87ce-db70-00b4d9fc7c95@oss.qualcomm.com/), >>> but the patch doesn't apply cleanly to current or ath-pending. Don't >>> know that it would help, but it seemed interesting. >>> >>> When I went back to the older kernel / distro I still could not see >>> the 6 Ghz band nor connect to it. I think something has changed on the >>> AP as well, as this used to work intermittently. I think I have >>> mentioned this before, but I have a dual-boot setup on this laptop and >>> in Windows 11, it does see and connect to the 6 Ghz band and MLO works >>> as well. Also, I have about 5 other devices (phones and laptops) that >>> can all connect to the 6 Ghz band. I think it's a combination of the >>> AP and the driver / firmware. >> >> >> >> >> Do you have another WCN7850? >> Our monitor mode is now in pending branch, and one fix is coming so that >> you can use WCN7850 to capture 6 GHz management packects. So that our >> firmware team can do further research. > > I've successfully put the wifi into monitor mode and captured some > traffic. I used freq. 6615, which is the frequency my Holman-6G runs > at with a width of 320Mhz. I can see beacons and other wifi related > traffic, however, I did not have an encryption key set, so any traffic > should still be encrypted. Hopefully the beacons and other things > help. > I took a chance that the patches were ready and used the most recent > tag: ath-pending-202505201841 and it appeared to work OK. Let me know > if this helps and if you need anything else. Thanks, This is what we needed. But i didn't see probe req in this file. Not sure if you didn't run the test? Can you put this monitor mode device between your test station device and AP device(Try to ensure that it is on the connection line between the two device), then start the full test? Remember run "iw reg set US" before connecting step. Also, please provide us the host/firmware log and the packets. All logs/packets come from the same test, will make it easier for our firmware team to debug. 🙂 > > -Walt ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ath12k: No 6GHz Wireless found 2025-05-21 6:06 ` Kang Yang @ 2025-05-22 17:48 ` Walt Holman 2025-05-23 2:12 ` Kang Yang 0 siblings, 1 reply; 32+ messages in thread From: Walt Holman @ 2025-05-22 17:48 UTC (permalink / raw) To: Kang Yang; +Cc: Jeff Johnson, linux-wireless, ath12k@lists.infradead.org [-- Attachment #1: Type: text/plain, Size: 18628 bytes --] On Wed, May 21, 2025 at 1:07 AM Kang Yang <quic_kangyang@quicinc.com> wrote: > > > > On 5/21/2025 1:05 PM, Walt Holman wrote: > > On Thu, May 15, 2025 at 10:06 PM Kang Yang <quic_kangyang@quicinc.com> wrote: > >> > >> > >> > >> On 5/16/2025 1:47 AM, Walt Holman wrote: > >>> On Thu, May 15, 2025 at 4:22 AM Kang Yang <quic_kangyang@quicinc.com> wrote: > >>>> > >>>> > >>>> > >>>> On 5/15/2025 4:12 PM, Kang Yang wrote: > >>>>> > >>>>> On 4/20/2025 11:18 PM, Walt Holman wrote: > >>>>>> On Fri, Apr 18, 2025 at 4:18 PM Walt Holman <waltholman09@gmail.com> > >>>>>> wrote: > >>>>>>> On Tue, Apr 15, 2025 at 4:23 PM Walt Holman <waltholman09@gmail.com> > >>>>>>> wrote: > >>>>>>>> On Thu, Apr 10, 2025 at 10:32 AM Walt Holman > >>>>>>>> <waltholman09@gmail.com> wrote: > >>>>>>>>> On Thu, Apr 10, 2025 at 3:26 AM Kang Yang > >>>>>>>>> <kang.yang@oss.qualcomm.com> wrote: > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> On 4/10/2025 3:37 AM, Walt Holman wrote: > >>>>>>>>>>> On Tue, Apr 8, 2025 at 4:17 AM Kang Yang > >>>>>>>>>>> <quic_kangyang@quicinc.com> wrote: > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> On 4/8/2025 1:49 AM, Walt Holman wrote: > >>>>>>>>>>>>> Attached is a small packet capture where I did an 'iw wlp99s0 > >>>>>>>>>>>>> scan' > >>>>>>>>>>>>> and also deactivated and reactivated wireless while the scan was > >>>>>>>>>>>>> ongoing. Hopefully there's something interesting for you in there. > >>>>>>>>>>>>> Also, I've take 3 screenshots showing the configs of the > >>>>>>>>>>>>> wireless AP > >>>>>>>>>>>>> for the 6ghz network. The first screen is just the definition > >>>>>>>>>>>>> of the > >>>>>>>>>>>>> network. No advanced settings are used. The 2nd screen shows the > >>>>>>>>>>>>> channels and radio enabled. The 3rd screen has the advanced > >>>>>>>>>>>>> (professional) settings for the network. I believe I changed > >>>>>>>>>>>>> 'Agile > >>>>>>>>>>>>> Multiband' to enabled, but other settings are their defaults. Hope > >>>>>>>>>>>>> some of this helps. Let me know if you need anything else. Thanks, > >>>>>>>>>>>>> > >>>>>>>>>>>> Your packets are Ethernet packets. I need wireless packets. > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> Not sure if you know how to add a seperate monitor interface to > >>>>>>>>>>>> capture > >>>>>>>>>>>> 6 G channels' packet on your AP(you can google for specific > >>>>>>>>>>>> command). > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> Also, please capture firmware log: > >>>>>>>>>>>> > >>>>>>>>>>>> 1. sudo apt install trace-cmd > >>>>>>>>>>>> 2. sudo trace-cmd record -e ath12k_wmi_diag > >>>>>>>>>>>> 3. run test > >>>>>>>>>>>> 4. "ctrl c" to stop recording: > >>>>>>>>>>>> Hit Ctrl^C to stop recording > >>>>>>>>>>>> ^CCPU0 data recorded at offset=0xdf5000 > >>>>>>>>>>>> 2605056 bytes in size > >>>>>>>>>>>> Then share the trace.dat to us. > >>>>>>>>>>>> > >>>>>>>>>>>> So you need to: > >>>>>>>>>>>> 1. try to capture wireless packets. > >>>>>>>>>>>> 2. capture firmware log(trade.data). > >>>>>>>>>>>> 3. save kernel/wpa_supplicant/iw logs. > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>>> -Walt > >>>>>>>>>>>>> > >>>>>>>>>>>>> On Sun, Apr 6, 2025 at 8:58 PM Kang Yang > >>>>>>>>>>>>> <quic_kangyang@quicinc.com> wrote: > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> On 4/4/2025 12:04 AM, Walt Holman wrote: > >>>>>>>>>>>>>>> On Thu, Apr 3, 2025 at 3:20 AM Kang Yang > >>>>>>>>>>>>>>> <quic_kangyang@quicinc.com> wrote: > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> On 4/3/2025 1:48 AM, Walt Holman wrote: > >>>>>>>>>>>>>>>>> On Tue, Apr 1, 2025 at 9:48 PM Kang Yang > >>>>>>>>>>>>>>>>> <quic_kangyang@quicinc.com> wrote: > >>>>>>>>>>>>>>>>>> Test on 6.14.0-rc5-wt-ath+, with the firmware you used. > >>>>>>>>>>>>>>>>>> I can get 6 GHz AP and connect to it. > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> ath12k_pci 0000:03:00.0: fw_version 0x100301e1 > >>>>>>>>>>>>>>>>>> fw_build_timestamp > >>>>>>>>>>>>>>>>>> 2023-12-06 04:05 fw_build_id > >>>>>>>>>>>>>>>>>> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481- > >>>>>>>>>>>>>>>>>> QCAHMTSWPL_V1.0_V2.0_SILICONZ-3 > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> yk@yk-Mayan:~$ sudo iw wls1 scan | tee iw_scan.log: > >>>>>>>>>>>>>>>>>> BSS 62:03:7f:12:64:64(on wls1) -- associated > >>>>>>>>>>>>>>>>>> TSF: 606308271476 usec (7d, 00:25:08) > >>>>>>>>>>>>>>>>>> freq: 6275 > >>>>>>>>>>>>>>>>>> beacon interval: 100 TUs > >>>>>>>>>>>>>>>>>> capability: ESS Privacy SpectrumMgmt > >>>>>>>>>>>>>>>>>> ShortSlotTime (0x0511) > >>>>>>>>>>>>>>>>>> signal: -17.00 dBm > >>>>>>>>>>>>>>>>>> last seen: 52 ms ago > >>>>>>>>>>>>>>>>>> Information elements from Probe Response frame: > >>>>>>>>>>>>>>>>>> SSID: MLO-KANG-6G > >>>>>>>>>>>>>>>>>> and other 6 GHz APs: > >>>>>>>>>>>>>>>>>> SSID: 6G-gxia > >>>>>>>>>>>>>>>>>> SSID: NETGEAR97-6G > >>>>>>>>>>>>>>>>>> …… > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> kernel log: > >>>>>>>>>>>>>>>>>> [88158.033218] wls1: Inserted STA 62:03:7f:12:64:64 > >>>>>>>>>>>>>>>>>> [88158.033232] wls1: authenticate with 62:03:7f:12:64:64 > >>>>>>>>>>>>>>>>>> (local > >>>>>>>>>>>>>>>>>> address=00:03:7f:37:12:54) > >>>>>>>>>>>>>>>>>> [88158.033242] wls1: send auth to 62:03:7f:12:64:64 (try 1/3) > >>>>>>>>>>>>>>>>>> [88158.041895] wls1: authenticated > >>>>>>>>>>>>>>>>>> [88158.041914] wls1: moving STA 62:03:7f:12:64:64 to state 2 > >>>>>>>>>>>>>>>>>> [88158.044291] wls1: determined local STA to be EHT, BW > >>>>>>>>>>>>>>>>>> limited to 320 MHz > >>>>>>>>>>>>>>>>>> [88158.045719] wls1: associate with 62:03:7f:12:64:64 (try > >>>>>>>>>>>>>>>>>> 1/3) > >>>>>>>>>>>>>>>>>> [88158.067045] wls1: RX AssocResp from 62:03:7f:12:64:64 > >>>>>>>>>>>>>>>>>> (capab=0x511 > >>>>>>>>>>>>>>>>>> status=0 aid=4) > >>>>>>>>>>>>>>>>>> [88158.089090] wls1: associated > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> I can even connect to it by Ubuntu GUI. > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> Can you update to 6.14.0-rc5-wt-ath+ and have a retry? > >>>>>>>>>>>>>>>>>> Also please make > >>>>>>>>>>>>>>>>>> sure that your wpa_supplicant/iw support 6 GHz(or directly > >>>>>>>>>>>>>>>>>> update to the > >>>>>>>>>>>>>>>>>> latest version). > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> If you still cannot find 6 GHz AP, you can set debug_mask > >>>>>>>>>>>>>>>>>> to 0xffffffff > >>>>>>>>>>>>>>>>>> to get ath12k logs. Then give it to us. > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>> -Walt > >>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> OK, I retested with the wt-ath 033125 tagged build. This > >>>>>>>>>>>>>>>>> included the > >>>>>>>>>>>>>>>>> patch the Jeff suggested I try, but the rest of the tree > >>>>>>>>>>>>>>>>> was clean. > >>>>>>>>>>>>>>>>> Still no 6ghz Wifi. I'm attaching a log file of the boot > >>>>>>>>>>>>>>>>> and first few > >>>>>>>>>>>>>>>>> seconds with the debug mask turned on. I noticed that if I > >>>>>>>>>>>>>>>>> rmmod the > >>>>>>>>>>>>>>>>> module and then modprobe it, it complains about not finding > >>>>>>>>>>>>>>>>> firmware-2.bin, however, I thought that was only for the > >>>>>>>>>>>>>>>>> qcn based > >>>>>>>>>>>>>>>>> chip? The HW info from dmesg looks like this: > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> I cannot find this tag... > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> From the log, the 6 GHz channel should work. When scan > >>>>>>>>>>>>>>>> is triggered, FW > >>>>>>>>>>>>>>>> shall send probe req on these channels. If AP send probe > >>>>>>>>>>>>>>>> resp, station > >>>>>>>>>>>>>>>> shall find the AP. > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> [ 6.070282] ath12k_pci 0000:63:00.0: BAR 0 [mem > >>>>>>>>>>>>>>>>> 0xdd800000-0xdd9fffff 64bit]: assigned > >>>>>>>>>>>>>>>>> [ 6.070310] ath12k_pci 0000:63:00.0: enabling device > >>>>>>>>>>>>>>>>> (0000 -> 0002) > >>>>>>>>>>>>>>>>> [ 6.071249] ath12k_pci 0000:63:00.0: MSI vectors: 16 > >>>>>>>>>>>>>>>>> [ 6.071254] ath12k_pci 0000:63:00.0: Hardware name: > >>>>>>>>>>>>>>>>> wcn7850 hw2.0 > >>>>>>>>>>>>>>>>> [ 6.596331] ath12k_pci 0000:63:00.0: qmi dma allocation > >>>>>>>>>>>>>>>>> failed > >>>>>>>>>>>>>>>>> (7077888 B type 1), will try later with sma > >>>>>>>>>>>>>>>>> ll size > >>>>>>>>>>>>>>>>> [ 6.604041] ath12k_pci 0000:63:00.0: chip_id 0x2 > >>>>>>>>>>>>>>>>> chip_family 0x4 > >>>>>>>>>>>>>>>>> board_id 0xff soc_id 0x40170200 > >>>>>>>>>>>>>>>>> [ 6.604044] ath12k_pci 0000:63:00.0: fw_version 0x100301e1 > >>>>>>>>>>>>>>>>> fw_build_timestamp 2023-12-06 04:05 fw_build_id > >>>>>>>>>>>>>>>>> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481- > >>>>>>>>>>>>>>>>> QCAHMTSWPL_V1.0_V2.0_SILICONZ- > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> Also, I noticed when looking through the debug logs there > >>>>>>>>>>>>>>>>> are the > >>>>>>>>>>>>>>>>> occasional WARNING statements from a BUG it appears. They > >>>>>>>>>>>>>>>>> trace back > >>>>>>>>>>>>>>>>> to the mac.c file inside the ath12k code. There should be > >>>>>>>>>>>>>>>>> some in the > >>>>>>>>>>>>>>>>> debug log that's attached. Let me know if I can do anything > >>>>>>>>>>>>>>>>> else. > >>>>>>>>>>>>>>>>> Thanks, > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> I have never seen this warning on my upstream setup...Not > >>>>>>>>>>>>>>>> sure if you > >>>>>>>>>>>>>>>> have changed anything or using the correct code base. > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> Jeff merged this patch-set into ath-202504021602. Can you > >>>>>>>>>>>>>>>> try on this > >>>>>>>>>>>>>>>> branch? > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> git clone https://git.kernel.org/pub/scm/linux/kernel/git/ > >>>>>>>>>>>>>>>> ath/ath.git/ > >>>>>>>>>>>>>>>> git pull > >>>>>>>>>>>>>>>> git reset --hard ath-202504021602 > >>>>>>>>>>>>>>>> compile and install... > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> Also make sure that the firmware you used is from the same > >>>>>>>>>>>>>>>> folder, don't > >>>>>>>>>>>>>>>> mix with other folders: > >>>>>>>>>>>>>>>> linux-firmware/ath12k/WCN7850/hw2.0 > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> 1. rmmod/insmod(debug_mask=0xffff) > >>>>>>>>>>>>>>>> 2. iw reg get > >>>>>>>>>>>>>>>> 3. iw reg set US > >>>>>>>>>>>>>>>> 4. iw xxx scan > >>>>>>>>>>>>>>>> wait and collect logs. > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> don't do anything else. > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> Also, can you show me your AP configuration. > >>>>>>>>>>>>>>>> If you have another 6 GHz AP, you can have a try(better > >>>>>>>>>>>>>>>> different brands). > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>> Thanks for testing. > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> Could you share your AP configuration? > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> If you have sniffer, could please capture packets during > >>>>>>>>>>>>>>>> testing? > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> Can you capture packets during the testing? I need to check > >>>>>>>>>>>>>> probe req > >>>>>>>>>>>>>> and probe resp. > >>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> Thanks! > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> -Walt > >>>>>>>>>>>>>>> OK, I cloned and built the kernel based on your instructions > >>>>>>>>>>>>>>> in your > >>>>>>>>>>>>>>> last email. Originally, the result was identical to my last > >>>>>>>>>>>>>>> email, > >>>>>>>>>>>>>>> including the WARNINGS. The .config I use is configured for a > >>>>>>>>>>>>>>> fully RT > >>>>>>>>>>>>>>> PREEMPT kernel, which I wondered if that was why I was > >>>>>>>>>>>>>>> receiving the > >>>>>>>>>>>>>>> WARNING. So I configured it as a Low Latency PREEMPT Desktop > >>>>>>>>>>>>>>> without > >>>>>>>>>>>>>>> the RT_PREEMPT and that eliminated the WARNING. However, > >>>>>>>>>>>>>>> still no 6Ghz > >>>>>>>>>>>>>>> networks. The firmware I'm using is straight from kernel.org > >>>>>>>>>>>>>>> GIT and I > >>>>>>>>>>>>>>> do a 'make install; make dedup' to install it. I believe it > >>>>>>>>>>>>>>> should be > >>>>>>>>>>>>>>> good. Attached is the latest log file. > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> -Walt > >>>>>>>>>>> > >>>>>>>>>>> Sorry for the top-post earlier. I can't figure out how to capture > >>>>>>>>>>> the > >>>>>>>>>>> wireless packets as my chip/driver combo doesn't support monitor > >>>>>>>>>>> mode. > >>>>>>>>>> Your AP also cannot capture wireless packets? > >>>>>>>>>> log in AP by usbserial or ssh. > >>>>>>>>>> Try to enter command line. use iw command to create monitor > >>>>>>>>>> interface. > >>>>>>>>>> Then use tcpdump to capture packets. > >>>>>>>>>> > >>>>>>>>>>> I've attached a tarball that contains the trace data and additional > >>>>>>>>>>> firmware logs from the kernel.log file. Anything else you need, just > >>>>>>>>>>> ask. Thanks for your help, > >>>>>>>>>> > >>>>>>>>>> Your AP mac address? > >>>>>>>>>> Need it to help check the fw log. > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>>> -Walt > >>>>>>>>> Sorry, the AP doesn't have tcpdump available on it. Also, this is a > >>>>>>>>> mesh setup with 3 nodes total. The main AP and 2 mesh nodes. I'm > >>>>>>>>> within 10 feet of one of the nodes and it's MAC for the wireless 6ghz > >>>>>>>>> network is: 10:7C:61:6F:2A:CA > >>>>>>>>> > >>>>>>>>> -Walt > >>>>>>>> The other 2 node 6ghz mac addresses are: > >>>>>>>> 10:7C:61:6F:1F:11 - Router > >>>>>>>> 10:7C:61:6F:32:92 - Node > >>>>>>>> > >>>>>>>> The first MAC address I gave you earlier was a node located > >>>>>>>> approximately 5 feet from where the laptop is. > >>>>>>>> > >>>>>>>> -Walt > >>>>>>> Well, I'm running into a brick wall it seems trying to get 6Ghz > >>>>>>> enabled on this. I tried the ath-next-20250418 tag just now and still > >>>>>>> don't see or connect to my 6Ghz network. I applied the patches in: > >>>>>>> https://lore.kernel.org/linux-wireless/20250418-ath12k-6g-lp-vlp- > >>>>>>> v1-0-c869c86cad60@quicinc.com/T/#t > >>>>>>> > >>>>>>> hoping that would help, but alas, no 6Ghz networks. I see that MLO and > >>>>>>> other nice fixes are coming in 6.16, but without 6Ghz, they'll do me > >>>>>>> no good. I'm really wondering if it's a firmware issue that excludes > >>>>>>> my chip or something. Again, anything I can do to help, let me know. > >>>>>>> Thanks, > >>>>>>> > >>>>>>> -Walt > >>>>>> Well, I used the swiss army tools to look at the firmware, and my chip > >>>>>> is listed in the firmware, so it's not excluded or anything. Really > >>>>>> puzzlling issue as my other two laptops connect to the 6Ghz network > >>>>>> just fine, and this laptop does in Windows, just not in Linux. I > >>>>>> really don't use Windows at all though, so that does me no good. > >>>>>> > >>>>>> This laptop used to connect to the 6Ghz network around the Sep. - Oct. > >>>>>> 2024 timeframe. Something has changed and now it doesn't. I'm going to > >>>>>> boot off a live image of Ubuntu 24.10 and see if I can see the > >>>>>> network. It was always hit or miss so we'll see. > >>>>>> -Walt > >>>>> > >>>>> > >>>>> Can you find 6 GHz AP now? > >>>>> > >>>> > >>>> Our firmware team said you station device sent the probe request but > >>>> didn't receive the probe resp or beacon. > >>>> > >>>> Since your current configuration is single 6 GHz AP. Could you change > >>>> your AP configuration to 6 GHz + 2/5 GHz to have a retry? > >>>> > >>> I adedd another network with 2.4 / 5 / 6Ghz settings and still only > >>> connect to the 5Ghz network portion. This is verified through wavemon > >>> and the AP. I saw some patches recently to address 6 Ghz operatoins in > >>> various modes (https://lore.kernel.org/linux-wireless/1692f2f8-c77e-87ce-db70-00b4d9fc7c95@oss.qualcomm.com/), > >>> but the patch doesn't apply cleanly to current or ath-pending. Don't > >>> know that it would help, but it seemed interesting. > >>> > >>> When I went back to the older kernel / distro I still could not see > >>> the 6 Ghz band nor connect to it. I think something has changed on the > >>> AP as well, as this used to work intermittently. I think I have > >>> mentioned this before, but I have a dual-boot setup on this laptop and > >>> in Windows 11, it does see and connect to the 6 Ghz band and MLO works > >>> as well. Also, I have about 5 other devices (phones and laptops) that > >>> can all connect to the 6 Ghz band. I think it's a combination of the > >>> AP and the driver / firmware. > >> > >> > >> > >> > >> Do you have another WCN7850? > >> Our monitor mode is now in pending branch, and one fix is coming so that > >> you can use WCN7850 to capture 6 GHz management packects. So that our > >> firmware team can do further research. > > > > I've successfully put the wifi into monitor mode and captured some > > traffic. I used freq. 6615, which is the frequency my Holman-6G runs > > at with a width of 320Mhz. I can see beacons and other wifi related > > traffic, however, I did not have an encryption key set, so any traffic > > should still be encrypted. Hopefully the beacons and other things > > help. > > I took a chance that the patches were ready and used the most recent > > tag: ath-pending-202505201841 and it appeared to work OK. Let me know > > if this helps and if you need anything else. Thanks, > > > This is what we needed. > > But i didn't see probe req in this file. > Not sure if you didn't run the test? > > Can you put this monitor mode device between your test station device > and AP device(Try to ensure that it is on the connection line between > the two device), then start the full test? > Remember run "iw reg set US" before connecting step. > > > Also, please provide us the host/firmware log and the packets. > All logs/packets come from the same test, will make it easier for our > firmware team to debug. > 🙂 OK, I think I've got something here and I hope it's useful. I did a packet capture of the wifi traffic on Freq. 6615 @ 160Mhz from another host and then loaded the ath12k module on the problem host and logged it all. The wifi adapter for the ath12k is a Quectel model. Also, I shut off both mesh nodes so that only the AP was running to ensure we were on the same node. Please let me know if you need anything else. I did see some packets from the ath12k module in the source field of the capture so hopefully this helps. -Walt [-- Attachment #2: wifi-capture-20250522.pcapng.gz --] [-- Type: application/gzip, Size: 95912 bytes --] [-- Attachment #3: firmware-log-20250522.txt.gz --] [-- Type: application/gzip, Size: 177631 bytes --] ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ath12k: No 6GHz Wireless found 2025-05-22 17:48 ` Walt Holman @ 2025-05-23 2:12 ` Kang Yang 2025-05-27 21:03 ` Walt Holman 0 siblings, 1 reply; 32+ messages in thread From: Kang Yang @ 2025-05-23 2:12 UTC (permalink / raw) To: Walt Holman; +Cc: Jeff Johnson, linux-wireless, ath12k@lists.infradead.org On 5/23/2025 1:48 AM, Walt Holman wrote: > On Wed, May 21, 2025 at 1:07 AM Kang Yang <quic_kangyang@quicinc.com> wrote: >> >> >> >> On 5/21/2025 1:05 PM, Walt Holman wrote: >>> On Thu, May 15, 2025 at 10:06 PM Kang Yang <quic_kangyang@quicinc.com> wrote: >>>> >>>> >>>> >>>> On 5/16/2025 1:47 AM, Walt Holman wrote: >>>>> On Thu, May 15, 2025 at 4:22 AM Kang Yang <quic_kangyang@quicinc.com> wrote: >>>>>> >>>>>> >>>>>> >>>>>> On 5/15/2025 4:12 PM, Kang Yang wrote: >>>>>>> >>>>>>> On 4/20/2025 11:18 PM, Walt Holman wrote: >>>>>>>> On Fri, Apr 18, 2025 at 4:18 PM Walt Holman <waltholman09@gmail.com> >>>>>>>> wrote: >>>>>>>>> On Tue, Apr 15, 2025 at 4:23 PM Walt Holman <waltholman09@gmail.com> >>>>>>>>> wrote: >>>>>>>>>> On Thu, Apr 10, 2025 at 10:32 AM Walt Holman >>>>>>>>>> <waltholman09@gmail.com> wrote: >>>>>>>>>>> On Thu, Apr 10, 2025 at 3:26 AM Kang Yang >>>>>>>>>>> <kang.yang@oss.qualcomm.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On 4/10/2025 3:37 AM, Walt Holman wrote: >>>>>>>>>>>>> On Tue, Apr 8, 2025 at 4:17 AM Kang Yang >>>>>>>>>>>>> <quic_kangyang@quicinc.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> On 4/8/2025 1:49 AM, Walt Holman wrote: >>>>>>>>>>>>>>> Attached is a small packet capture where I did an 'iw wlp99s0 >>>>>>>>>>>>>>> scan' >>>>>>>>>>>>>>> and also deactivated and reactivated wireless while the scan was >>>>>>>>>>>>>>> ongoing. Hopefully there's something interesting for you in there. >>>>>>>>>>>>>>> Also, I've take 3 screenshots showing the configs of the >>>>>>>>>>>>>>> wireless AP >>>>>>>>>>>>>>> for the 6ghz network. The first screen is just the definition >>>>>>>>>>>>>>> of the >>>>>>>>>>>>>>> network. No advanced settings are used. The 2nd screen shows the >>>>>>>>>>>>>>> channels and radio enabled. The 3rd screen has the advanced >>>>>>>>>>>>>>> (professional) settings for the network. I believe I changed >>>>>>>>>>>>>>> 'Agile >>>>>>>>>>>>>>> Multiband' to enabled, but other settings are their defaults. Hope >>>>>>>>>>>>>>> some of this helps. Let me know if you need anything else. Thanks, >>>>>>>>>>>>>>> >>>>>>>>>>>>>> Your packets are Ethernet packets. I need wireless packets. >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Not sure if you know how to add a seperate monitor interface to >>>>>>>>>>>>>> capture >>>>>>>>>>>>>> 6 G channels' packet on your AP(you can google for specific >>>>>>>>>>>>>> command). >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Also, please capture firmware log: >>>>>>>>>>>>>> >>>>>>>>>>>>>> 1. sudo apt install trace-cmd >>>>>>>>>>>>>> 2. sudo trace-cmd record -e ath12k_wmi_diag >>>>>>>>>>>>>> 3. run test >>>>>>>>>>>>>> 4. "ctrl c" to stop recording: >>>>>>>>>>>>>> Hit Ctrl^C to stop recording >>>>>>>>>>>>>> ^CCPU0 data recorded at offset=0xdf5000 >>>>>>>>>>>>>> 2605056 bytes in size >>>>>>>>>>>>>> Then share the trace.dat to us. >>>>>>>>>>>>>> >>>>>>>>>>>>>> So you need to: >>>>>>>>>>>>>> 1. try to capture wireless packets. >>>>>>>>>>>>>> 2. capture firmware log(trade.data). >>>>>>>>>>>>>> 3. save kernel/wpa_supplicant/iw logs. >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>>> -Walt >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Sun, Apr 6, 2025 at 8:58 PM Kang Yang >>>>>>>>>>>>>>> <quic_kangyang@quicinc.com> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On 4/4/2025 12:04 AM, Walt Holman wrote: >>>>>>>>>>>>>>>>> On Thu, Apr 3, 2025 at 3:20 AM Kang Yang >>>>>>>>>>>>>>>>> <quic_kangyang@quicinc.com> wrote: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On 4/3/2025 1:48 AM, Walt Holman wrote: >>>>>>>>>>>>>>>>>>> On Tue, Apr 1, 2025 at 9:48 PM Kang Yang >>>>>>>>>>>>>>>>>>> <quic_kangyang@quicinc.com> wrote: >>>>>>>>>>>>>>>>>>>> Test on 6.14.0-rc5-wt-ath+, with the firmware you used. >>>>>>>>>>>>>>>>>>>> I can get 6 GHz AP and connect to it. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> ath12k_pci 0000:03:00.0: fw_version 0x100301e1 >>>>>>>>>>>>>>>>>>>> fw_build_timestamp >>>>>>>>>>>>>>>>>>>> 2023-12-06 04:05 fw_build_id >>>>>>>>>>>>>>>>>>>> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481- >>>>>>>>>>>>>>>>>>>> QCAHMTSWPL_V1.0_V2.0_SILICONZ-3 >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> yk@yk-Mayan:~$ sudo iw wls1 scan | tee iw_scan.log: >>>>>>>>>>>>>>>>>>>> BSS 62:03:7f:12:64:64(on wls1) -- associated >>>>>>>>>>>>>>>>>>>> TSF: 606308271476 usec (7d, 00:25:08) >>>>>>>>>>>>>>>>>>>> freq: 6275 >>>>>>>>>>>>>>>>>>>> beacon interval: 100 TUs >>>>>>>>>>>>>>>>>>>> capability: ESS Privacy SpectrumMgmt >>>>>>>>>>>>>>>>>>>> ShortSlotTime (0x0511) >>>>>>>>>>>>>>>>>>>> signal: -17.00 dBm >>>>>>>>>>>>>>>>>>>> last seen: 52 ms ago >>>>>>>>>>>>>>>>>>>> Information elements from Probe Response frame: >>>>>>>>>>>>>>>>>>>> SSID: MLO-KANG-6G >>>>>>>>>>>>>>>>>>>> and other 6 GHz APs: >>>>>>>>>>>>>>>>>>>> SSID: 6G-gxia >>>>>>>>>>>>>>>>>>>> SSID: NETGEAR97-6G >>>>>>>>>>>>>>>>>>>> …… >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> kernel log: >>>>>>>>>>>>>>>>>>>> [88158.033218] wls1: Inserted STA 62:03:7f:12:64:64 >>>>>>>>>>>>>>>>>>>> [88158.033232] wls1: authenticate with 62:03:7f:12:64:64 >>>>>>>>>>>>>>>>>>>> (local >>>>>>>>>>>>>>>>>>>> address=00:03:7f:37:12:54) >>>>>>>>>>>>>>>>>>>> [88158.033242] wls1: send auth to 62:03:7f:12:64:64 (try 1/3) >>>>>>>>>>>>>>>>>>>> [88158.041895] wls1: authenticated >>>>>>>>>>>>>>>>>>>> [88158.041914] wls1: moving STA 62:03:7f:12:64:64 to state 2 >>>>>>>>>>>>>>>>>>>> [88158.044291] wls1: determined local STA to be EHT, BW >>>>>>>>>>>>>>>>>>>> limited to 320 MHz >>>>>>>>>>>>>>>>>>>> [88158.045719] wls1: associate with 62:03:7f:12:64:64 (try >>>>>>>>>>>>>>>>>>>> 1/3) >>>>>>>>>>>>>>>>>>>> [88158.067045] wls1: RX AssocResp from 62:03:7f:12:64:64 >>>>>>>>>>>>>>>>>>>> (capab=0x511 >>>>>>>>>>>>>>>>>>>> status=0 aid=4) >>>>>>>>>>>>>>>>>>>> [88158.089090] wls1: associated >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> I can even connect to it by Ubuntu GUI. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Can you update to 6.14.0-rc5-wt-ath+ and have a retry? >>>>>>>>>>>>>>>>>>>> Also please make >>>>>>>>>>>>>>>>>>>> sure that your wpa_supplicant/iw support 6 GHz(or directly >>>>>>>>>>>>>>>>>>>> update to the >>>>>>>>>>>>>>>>>>>> latest version). >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> If you still cannot find 6 GHz AP, you can set debug_mask >>>>>>>>>>>>>>>>>>>> to 0xffffffff >>>>>>>>>>>>>>>>>>>> to get ath12k logs. Then give it to us. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> -Walt >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> OK, I retested with the wt-ath 033125 tagged build. This >>>>>>>>>>>>>>>>>>> included the >>>>>>>>>>>>>>>>>>> patch the Jeff suggested I try, but the rest of the tree >>>>>>>>>>>>>>>>>>> was clean. >>>>>>>>>>>>>>>>>>> Still no 6ghz Wifi. I'm attaching a log file of the boot >>>>>>>>>>>>>>>>>>> and first few >>>>>>>>>>>>>>>>>>> seconds with the debug mask turned on. I noticed that if I >>>>>>>>>>>>>>>>>>> rmmod the >>>>>>>>>>>>>>>>>>> module and then modprobe it, it complains about not finding >>>>>>>>>>>>>>>>>>> firmware-2.bin, however, I thought that was only for the >>>>>>>>>>>>>>>>>>> qcn based >>>>>>>>>>>>>>>>>>> chip? The HW info from dmesg looks like this: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> I cannot find this tag... >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> From the log, the 6 GHz channel should work. When scan >>>>>>>>>>>>>>>>>> is triggered, FW >>>>>>>>>>>>>>>>>> shall send probe req on these channels. If AP send probe >>>>>>>>>>>>>>>>>> resp, station >>>>>>>>>>>>>>>>>> shall find the AP. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> [ 6.070282] ath12k_pci 0000:63:00.0: BAR 0 [mem >>>>>>>>>>>>>>>>>>> 0xdd800000-0xdd9fffff 64bit]: assigned >>>>>>>>>>>>>>>>>>> [ 6.070310] ath12k_pci 0000:63:00.0: enabling device >>>>>>>>>>>>>>>>>>> (0000 -> 0002) >>>>>>>>>>>>>>>>>>> [ 6.071249] ath12k_pci 0000:63:00.0: MSI vectors: 16 >>>>>>>>>>>>>>>>>>> [ 6.071254] ath12k_pci 0000:63:00.0: Hardware name: >>>>>>>>>>>>>>>>>>> wcn7850 hw2.0 >>>>>>>>>>>>>>>>>>> [ 6.596331] ath12k_pci 0000:63:00.0: qmi dma allocation >>>>>>>>>>>>>>>>>>> failed >>>>>>>>>>>>>>>>>>> (7077888 B type 1), will try later with sma >>>>>>>>>>>>>>>>>>> ll size >>>>>>>>>>>>>>>>>>> [ 6.604041] ath12k_pci 0000:63:00.0: chip_id 0x2 >>>>>>>>>>>>>>>>>>> chip_family 0x4 >>>>>>>>>>>>>>>>>>> board_id 0xff soc_id 0x40170200 >>>>>>>>>>>>>>>>>>> [ 6.604044] ath12k_pci 0000:63:00.0: fw_version 0x100301e1 >>>>>>>>>>>>>>>>>>> fw_build_timestamp 2023-12-06 04:05 fw_build_id >>>>>>>>>>>>>>>>>>> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481- >>>>>>>>>>>>>>>>>>> QCAHMTSWPL_V1.0_V2.0_SILICONZ- >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Also, I noticed when looking through the debug logs there >>>>>>>>>>>>>>>>>>> are the >>>>>>>>>>>>>>>>>>> occasional WARNING statements from a BUG it appears. They >>>>>>>>>>>>>>>>>>> trace back >>>>>>>>>>>>>>>>>>> to the mac.c file inside the ath12k code. There should be >>>>>>>>>>>>>>>>>>> some in the >>>>>>>>>>>>>>>>>>> debug log that's attached. Let me know if I can do anything >>>>>>>>>>>>>>>>>>> else. >>>>>>>>>>>>>>>>>>> Thanks, >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> I have never seen this warning on my upstream setup...Not >>>>>>>>>>>>>>>>>> sure if you >>>>>>>>>>>>>>>>>> have changed anything or using the correct code base. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Jeff merged this patch-set into ath-202504021602. Can you >>>>>>>>>>>>>>>>>> try on this >>>>>>>>>>>>>>>>>> branch? >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> git clone https://git.kernel.org/pub/scm/linux/kernel/git/ >>>>>>>>>>>>>>>>>> ath/ath.git/ >>>>>>>>>>>>>>>>>> git pull >>>>>>>>>>>>>>>>>> git reset --hard ath-202504021602 >>>>>>>>>>>>>>>>>> compile and install... >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Also make sure that the firmware you used is from the same >>>>>>>>>>>>>>>>>> folder, don't >>>>>>>>>>>>>>>>>> mix with other folders: >>>>>>>>>>>>>>>>>> linux-firmware/ath12k/WCN7850/hw2.0 >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> 1. rmmod/insmod(debug_mask=0xffff) >>>>>>>>>>>>>>>>>> 2. iw reg get >>>>>>>>>>>>>>>>>> 3. iw reg set US >>>>>>>>>>>>>>>>>> 4. iw xxx scan >>>>>>>>>>>>>>>>>> wait and collect logs. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> don't do anything else. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Also, can you show me your AP configuration. >>>>>>>>>>>>>>>>>> If you have another 6 GHz AP, you can have a try(better >>>>>>>>>>>>>>>>>> different brands). >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Thanks for testing. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Could you share your AP configuration? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> If you have sniffer, could please capture packets during >>>>>>>>>>>>>>>>>> testing? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Can you capture packets during the testing? I need to check >>>>>>>>>>>>>>>> probe req >>>>>>>>>>>>>>>> and probe resp. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Thanks! >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> -Walt >>>>>>>>>>>>>>>>> OK, I cloned and built the kernel based on your instructions >>>>>>>>>>>>>>>>> in your >>>>>>>>>>>>>>>>> last email. Originally, the result was identical to my last >>>>>>>>>>>>>>>>> email, >>>>>>>>>>>>>>>>> including the WARNINGS. The .config I use is configured for a >>>>>>>>>>>>>>>>> fully RT >>>>>>>>>>>>>>>>> PREEMPT kernel, which I wondered if that was why I was >>>>>>>>>>>>>>>>> receiving the >>>>>>>>>>>>>>>>> WARNING. So I configured it as a Low Latency PREEMPT Desktop >>>>>>>>>>>>>>>>> without >>>>>>>>>>>>>>>>> the RT_PREEMPT and that eliminated the WARNING. However, >>>>>>>>>>>>>>>>> still no 6Ghz >>>>>>>>>>>>>>>>> networks. The firmware I'm using is straight from kernel.org >>>>>>>>>>>>>>>>> GIT and I >>>>>>>>>>>>>>>>> do a 'make install; make dedup' to install it. I believe it >>>>>>>>>>>>>>>>> should be >>>>>>>>>>>>>>>>> good. Attached is the latest log file. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> -Walt >>>>>>>>>>>>> >>>>>>>>>>>>> Sorry for the top-post earlier. I can't figure out how to capture >>>>>>>>>>>>> the >>>>>>>>>>>>> wireless packets as my chip/driver combo doesn't support monitor >>>>>>>>>>>>> mode. >>>>>>>>>>>> Your AP also cannot capture wireless packets? >>>>>>>>>>>> log in AP by usbserial or ssh. >>>>>>>>>>>> Try to enter command line. use iw command to create monitor >>>>>>>>>>>> interface. >>>>>>>>>>>> Then use tcpdump to capture packets. >>>>>>>>>>>> >>>>>>>>>>>>> I've attached a tarball that contains the trace data and additional >>>>>>>>>>>>> firmware logs from the kernel.log file. Anything else you need, just >>>>>>>>>>>>> ask. Thanks for your help, >>>>>>>>>>>> >>>>>>>>>>>> Your AP mac address? >>>>>>>>>>>> Need it to help check the fw log. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>>> -Walt >>>>>>>>>>> Sorry, the AP doesn't have tcpdump available on it. Also, this is a >>>>>>>>>>> mesh setup with 3 nodes total. The main AP and 2 mesh nodes. I'm >>>>>>>>>>> within 10 feet of one of the nodes and it's MAC for the wireless 6ghz >>>>>>>>>>> network is: 10:7C:61:6F:2A:CA >>>>>>>>>>> >>>>>>>>>>> -Walt >>>>>>>>>> The other 2 node 6ghz mac addresses are: >>>>>>>>>> 10:7C:61:6F:1F:11 - Router >>>>>>>>>> 10:7C:61:6F:32:92 - Node >>>>>>>>>> >>>>>>>>>> The first MAC address I gave you earlier was a node located >>>>>>>>>> approximately 5 feet from where the laptop is. >>>>>>>>>> >>>>>>>>>> -Walt >>>>>>>>> Well, I'm running into a brick wall it seems trying to get 6Ghz >>>>>>>>> enabled on this. I tried the ath-next-20250418 tag just now and still >>>>>>>>> don't see or connect to my 6Ghz network. I applied the patches in: >>>>>>>>> https://lore.kernel.org/linux-wireless/20250418-ath12k-6g-lp-vlp- >>>>>>>>> v1-0-c869c86cad60@quicinc.com/T/#t >>>>>>>>> >>>>>>>>> hoping that would help, but alas, no 6Ghz networks. I see that MLO and >>>>>>>>> other nice fixes are coming in 6.16, but without 6Ghz, they'll do me >>>>>>>>> no good. I'm really wondering if it's a firmware issue that excludes >>>>>>>>> my chip or something. Again, anything I can do to help, let me know. >>>>>>>>> Thanks, >>>>>>>>> >>>>>>>>> -Walt >>>>>>>> Well, I used the swiss army tools to look at the firmware, and my chip >>>>>>>> is listed in the firmware, so it's not excluded or anything. Really >>>>>>>> puzzlling issue as my other two laptops connect to the 6Ghz network >>>>>>>> just fine, and this laptop does in Windows, just not in Linux. I >>>>>>>> really don't use Windows at all though, so that does me no good. >>>>>>>> >>>>>>>> This laptop used to connect to the 6Ghz network around the Sep. - Oct. >>>>>>>> 2024 timeframe. Something has changed and now it doesn't. I'm going to >>>>>>>> boot off a live image of Ubuntu 24.10 and see if I can see the >>>>>>>> network. It was always hit or miss so we'll see. >>>>>>>> -Walt >>>>>>> >>>>>>> >>>>>>> Can you find 6 GHz AP now? >>>>>>> >>>>>> >>>>>> Our firmware team said you station device sent the probe request but >>>>>> didn't receive the probe resp or beacon. >>>>>> >>>>>> Since your current configuration is single 6 GHz AP. Could you change >>>>>> your AP configuration to 6 GHz + 2/5 GHz to have a retry? >>>>>> >>>>> I adedd another network with 2.4 / 5 / 6Ghz settings and still only >>>>> connect to the 5Ghz network portion. This is verified through wavemon >>>>> and the AP. I saw some patches recently to address 6 Ghz operatoins in >>>>> various modes (https://lore.kernel.org/linux-wireless/1692f2f8-c77e-87ce-db70-00b4d9fc7c95@oss.qualcomm.com/), >>>>> but the patch doesn't apply cleanly to current or ath-pending. Don't >>>>> know that it would help, but it seemed interesting. >>>>> >>>>> When I went back to the older kernel / distro I still could not see >>>>> the 6 Ghz band nor connect to it. I think something has changed on the >>>>> AP as well, as this used to work intermittently. I think I have >>>>> mentioned this before, but I have a dual-boot setup on this laptop and >>>>> in Windows 11, it does see and connect to the 6 Ghz band and MLO works >>>>> as well. Also, I have about 5 other devices (phones and laptops) that >>>>> can all connect to the 6 Ghz band. I think it's a combination of the >>>>> AP and the driver / firmware. >>>> >>>> >>>> >>>> >>>> Do you have another WCN7850? >>>> Our monitor mode is now in pending branch, and one fix is coming so that >>>> you can use WCN7850 to capture 6 GHz management packects. So that our >>>> firmware team can do further research. >>> >>> I've successfully put the wifi into monitor mode and captured some >>> traffic. I used freq. 6615, which is the frequency my Holman-6G runs >>> at with a width of 320Mhz. I can see beacons and other wifi related >>> traffic, however, I did not have an encryption key set, so any traffic >>> should still be encrypted. Hopefully the beacons and other things >>> help. >>> I took a chance that the patches were ready and used the most recent >>> tag: ath-pending-202505201841 and it appeared to work OK. Let me know >>> if this helps and if you need anything else. Thanks, >> >> >> This is what we needed. >> >> But i didn't see probe req in this file. >> Not sure if you didn't run the test? >> >> Can you put this monitor mode device between your test station device >> and AP device(Try to ensure that it is on the connection line between >> the two device), then start the full test? >> Remember run "iw reg set US" before connecting step. >> >> >> Also, please provide us the host/firmware log and the packets. >> All logs/packets come from the same test, will make it easier for our >> firmware team to debug. >> 🙂 > > OK, I think I've got something here and I hope it's useful. I did a > packet capture of the wifi traffic on Freq. 6615 @ 160Mhz from another > host and then loaded the ath12k module on the problem host and logged > it all. The wifi adapter for the ath12k is a Quectel model. Also, I > shut off both mesh nodes so that only the AP was running to ensure we > were on the same node. This is great, thanks. > Please let me know if you need anything else. I > did see some packets from the ath12k module in the source field of the > capture so hopefully this helps. Oh... you missed the firmware log. 1. sudo apt install trace-cmd 2. sudo trace-cmd record -e ath12k_wmi_diag 3. run test 4. "ctrl c" to stop recording: Hit Ctrl^C to stop recording ^CCPU0 data recorded at offset=0xdf5000 2605056 bytes in size Then share the trace.dat to us. So you need to: 1. try to capture wireless packets. 2. capture firmware log(trade.data). Total three files: trace.dat, kernel.log, wifi-capture.pcapng 🙂It's a little complicated, but they are necessary, thanks. > > -Walt ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ath12k: No 6GHz Wireless found 2025-05-23 2:12 ` Kang Yang @ 2025-05-27 21:03 ` Walt Holman 2025-05-29 8:24 ` Kang Yang 0 siblings, 1 reply; 32+ messages in thread From: Walt Holman @ 2025-05-27 21:03 UTC (permalink / raw) To: Kang Yang; +Cc: Jeff Johnson, linux-wireless, ath12k@lists.infradead.org [-- Attachment #1: Type: text/plain, Size: 20298 bytes --] On Thu, May 22, 2025 at 9:12 PM Kang Yang <quic_kangyang@quicinc.com> wrote: > > > > On 5/23/2025 1:48 AM, Walt Holman wrote: > > On Wed, May 21, 2025 at 1:07 AM Kang Yang <quic_kangyang@quicinc.com> wrote: > >> > >> > >> > >> On 5/21/2025 1:05 PM, Walt Holman wrote: > >>> On Thu, May 15, 2025 at 10:06 PM Kang Yang <quic_kangyang@quicinc.com> wrote: > >>>> > >>>> > >>>> > >>>> On 5/16/2025 1:47 AM, Walt Holman wrote: > >>>>> On Thu, May 15, 2025 at 4:22 AM Kang Yang <quic_kangyang@quicinc.com> wrote: > >>>>>> > >>>>>> > >>>>>> > >>>>>> On 5/15/2025 4:12 PM, Kang Yang wrote: > >>>>>>> > >>>>>>> On 4/20/2025 11:18 PM, Walt Holman wrote: > >>>>>>>> On Fri, Apr 18, 2025 at 4:18 PM Walt Holman <waltholman09@gmail.com> > >>>>>>>> wrote: > >>>>>>>>> On Tue, Apr 15, 2025 at 4:23 PM Walt Holman <waltholman09@gmail.com> > >>>>>>>>> wrote: > >>>>>>>>>> On Thu, Apr 10, 2025 at 10:32 AM Walt Holman > >>>>>>>>>> <waltholman09@gmail.com> wrote: > >>>>>>>>>>> On Thu, Apr 10, 2025 at 3:26 AM Kang Yang > >>>>>>>>>>> <kang.yang@oss.qualcomm.com> wrote: > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> On 4/10/2025 3:37 AM, Walt Holman wrote: > >>>>>>>>>>>>> On Tue, Apr 8, 2025 at 4:17 AM Kang Yang > >>>>>>>>>>>>> <quic_kangyang@quicinc.com> wrote: > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> On 4/8/2025 1:49 AM, Walt Holman wrote: > >>>>>>>>>>>>>>> Attached is a small packet capture where I did an 'iw wlp99s0 > >>>>>>>>>>>>>>> scan' > >>>>>>>>>>>>>>> and also deactivated and reactivated wireless while the scan was > >>>>>>>>>>>>>>> ongoing. Hopefully there's something interesting for you in there. > >>>>>>>>>>>>>>> Also, I've take 3 screenshots showing the configs of the > >>>>>>>>>>>>>>> wireless AP > >>>>>>>>>>>>>>> for the 6ghz network. The first screen is just the definition > >>>>>>>>>>>>>>> of the > >>>>>>>>>>>>>>> network. No advanced settings are used. The 2nd screen shows the > >>>>>>>>>>>>>>> channels and radio enabled. The 3rd screen has the advanced > >>>>>>>>>>>>>>> (professional) settings for the network. I believe I changed > >>>>>>>>>>>>>>> 'Agile > >>>>>>>>>>>>>>> Multiband' to enabled, but other settings are their defaults. Hope > >>>>>>>>>>>>>>> some of this helps. Let me know if you need anything else. Thanks, > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>> Your packets are Ethernet packets. I need wireless packets. > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> Not sure if you know how to add a seperate monitor interface to > >>>>>>>>>>>>>> capture > >>>>>>>>>>>>>> 6 G channels' packet on your AP(you can google for specific > >>>>>>>>>>>>>> command). > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> Also, please capture firmware log: > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> 1. sudo apt install trace-cmd > >>>>>>>>>>>>>> 2. sudo trace-cmd record -e ath12k_wmi_diag > >>>>>>>>>>>>>> 3. run test > >>>>>>>>>>>>>> 4. "ctrl c" to stop recording: > >>>>>>>>>>>>>> Hit Ctrl^C to stop recording > >>>>>>>>>>>>>> ^CCPU0 data recorded at offset=0xdf5000 > >>>>>>>>>>>>>> 2605056 bytes in size > >>>>>>>>>>>>>> Then share the trace.dat to us. > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> So you need to: > >>>>>>>>>>>>>> 1. try to capture wireless packets. > >>>>>>>>>>>>>> 2. capture firmware log(trade.data). > >>>>>>>>>>>>>> 3. save kernel/wpa_supplicant/iw logs. > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>>> -Walt > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> On Sun, Apr 6, 2025 at 8:58 PM Kang Yang > >>>>>>>>>>>>>>> <quic_kangyang@quicinc.com> wrote: > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> On 4/4/2025 12:04 AM, Walt Holman wrote: > >>>>>>>>>>>>>>>>> On Thu, Apr 3, 2025 at 3:20 AM Kang Yang > >>>>>>>>>>>>>>>>> <quic_kangyang@quicinc.com> wrote: > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> On 4/3/2025 1:48 AM, Walt Holman wrote: > >>>>>>>>>>>>>>>>>>> On Tue, Apr 1, 2025 at 9:48 PM Kang Yang > >>>>>>>>>>>>>>>>>>> <quic_kangyang@quicinc.com> wrote: > >>>>>>>>>>>>>>>>>>>> Test on 6.14.0-rc5-wt-ath+, with the firmware you used. > >>>>>>>>>>>>>>>>>>>> I can get 6 GHz AP and connect to it. > >>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>> ath12k_pci 0000:03:00.0: fw_version 0x100301e1 > >>>>>>>>>>>>>>>>>>>> fw_build_timestamp > >>>>>>>>>>>>>>>>>>>> 2023-12-06 04:05 fw_build_id > >>>>>>>>>>>>>>>>>>>> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481- > >>>>>>>>>>>>>>>>>>>> QCAHMTSWPL_V1.0_V2.0_SILICONZ-3 > >>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>> yk@yk-Mayan:~$ sudo iw wls1 scan | tee iw_scan.log: > >>>>>>>>>>>>>>>>>>>> BSS 62:03:7f:12:64:64(on wls1) -- associated > >>>>>>>>>>>>>>>>>>>> TSF: 606308271476 usec (7d, 00:25:08) > >>>>>>>>>>>>>>>>>>>> freq: 6275 > >>>>>>>>>>>>>>>>>>>> beacon interval: 100 TUs > >>>>>>>>>>>>>>>>>>>> capability: ESS Privacy SpectrumMgmt > >>>>>>>>>>>>>>>>>>>> ShortSlotTime (0x0511) > >>>>>>>>>>>>>>>>>>>> signal: -17.00 dBm > >>>>>>>>>>>>>>>>>>>> last seen: 52 ms ago > >>>>>>>>>>>>>>>>>>>> Information elements from Probe Response frame: > >>>>>>>>>>>>>>>>>>>> SSID: MLO-KANG-6G > >>>>>>>>>>>>>>>>>>>> and other 6 GHz APs: > >>>>>>>>>>>>>>>>>>>> SSID: 6G-gxia > >>>>>>>>>>>>>>>>>>>> SSID: NETGEAR97-6G > >>>>>>>>>>>>>>>>>>>> …… > >>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>> kernel log: > >>>>>>>>>>>>>>>>>>>> [88158.033218] wls1: Inserted STA 62:03:7f:12:64:64 > >>>>>>>>>>>>>>>>>>>> [88158.033232] wls1: authenticate with 62:03:7f:12:64:64 > >>>>>>>>>>>>>>>>>>>> (local > >>>>>>>>>>>>>>>>>>>> address=00:03:7f:37:12:54) > >>>>>>>>>>>>>>>>>>>> [88158.033242] wls1: send auth to 62:03:7f:12:64:64 (try 1/3) > >>>>>>>>>>>>>>>>>>>> [88158.041895] wls1: authenticated > >>>>>>>>>>>>>>>>>>>> [88158.041914] wls1: moving STA 62:03:7f:12:64:64 to state 2 > >>>>>>>>>>>>>>>>>>>> [88158.044291] wls1: determined local STA to be EHT, BW > >>>>>>>>>>>>>>>>>>>> limited to 320 MHz > >>>>>>>>>>>>>>>>>>>> [88158.045719] wls1: associate with 62:03:7f:12:64:64 (try > >>>>>>>>>>>>>>>>>>>> 1/3) > >>>>>>>>>>>>>>>>>>>> [88158.067045] wls1: RX AssocResp from 62:03:7f:12:64:64 > >>>>>>>>>>>>>>>>>>>> (capab=0x511 > >>>>>>>>>>>>>>>>>>>> status=0 aid=4) > >>>>>>>>>>>>>>>>>>>> [88158.089090] wls1: associated > >>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>> I can even connect to it by Ubuntu GUI. > >>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>> Can you update to 6.14.0-rc5-wt-ath+ and have a retry? > >>>>>>>>>>>>>>>>>>>> Also please make > >>>>>>>>>>>>>>>>>>>> sure that your wpa_supplicant/iw support 6 GHz(or directly > >>>>>>>>>>>>>>>>>>>> update to the > >>>>>>>>>>>>>>>>>>>> latest version). > >>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>> If you still cannot find 6 GHz AP, you can set debug_mask > >>>>>>>>>>>>>>>>>>>> to 0xffffffff > >>>>>>>>>>>>>>>>>>>> to get ath12k logs. Then give it to us. > >>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>> -Walt > >>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>> OK, I retested with the wt-ath 033125 tagged build. This > >>>>>>>>>>>>>>>>>>> included the > >>>>>>>>>>>>>>>>>>> patch the Jeff suggested I try, but the rest of the tree > >>>>>>>>>>>>>>>>>>> was clean. > >>>>>>>>>>>>>>>>>>> Still no 6ghz Wifi. I'm attaching a log file of the boot > >>>>>>>>>>>>>>>>>>> and first few > >>>>>>>>>>>>>>>>>>> seconds with the debug mask turned on. I noticed that if I > >>>>>>>>>>>>>>>>>>> rmmod the > >>>>>>>>>>>>>>>>>>> module and then modprobe it, it complains about not finding > >>>>>>>>>>>>>>>>>>> firmware-2.bin, however, I thought that was only for the > >>>>>>>>>>>>>>>>>>> qcn based > >>>>>>>>>>>>>>>>>>> chip? The HW info from dmesg looks like this: > >>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> I cannot find this tag... > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> From the log, the 6 GHz channel should work. When scan > >>>>>>>>>>>>>>>>>> is triggered, FW > >>>>>>>>>>>>>>>>>> shall send probe req on these channels. If AP send probe > >>>>>>>>>>>>>>>>>> resp, station > >>>>>>>>>>>>>>>>>> shall find the AP. > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>> [ 6.070282] ath12k_pci 0000:63:00.0: BAR 0 [mem > >>>>>>>>>>>>>>>>>>> 0xdd800000-0xdd9fffff 64bit]: assigned > >>>>>>>>>>>>>>>>>>> [ 6.070310] ath12k_pci 0000:63:00.0: enabling device > >>>>>>>>>>>>>>>>>>> (0000 -> 0002) > >>>>>>>>>>>>>>>>>>> [ 6.071249] ath12k_pci 0000:63:00.0: MSI vectors: 16 > >>>>>>>>>>>>>>>>>>> [ 6.071254] ath12k_pci 0000:63:00.0: Hardware name: > >>>>>>>>>>>>>>>>>>> wcn7850 hw2.0 > >>>>>>>>>>>>>>>>>>> [ 6.596331] ath12k_pci 0000:63:00.0: qmi dma allocation > >>>>>>>>>>>>>>>>>>> failed > >>>>>>>>>>>>>>>>>>> (7077888 B type 1), will try later with sma > >>>>>>>>>>>>>>>>>>> ll size > >>>>>>>>>>>>>>>>>>> [ 6.604041] ath12k_pci 0000:63:00.0: chip_id 0x2 > >>>>>>>>>>>>>>>>>>> chip_family 0x4 > >>>>>>>>>>>>>>>>>>> board_id 0xff soc_id 0x40170200 > >>>>>>>>>>>>>>>>>>> [ 6.604044] ath12k_pci 0000:63:00.0: fw_version 0x100301e1 > >>>>>>>>>>>>>>>>>>> fw_build_timestamp 2023-12-06 04:05 fw_build_id > >>>>>>>>>>>>>>>>>>> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481- > >>>>>>>>>>>>>>>>>>> QCAHMTSWPL_V1.0_V2.0_SILICONZ- > >>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>> Also, I noticed when looking through the debug logs there > >>>>>>>>>>>>>>>>>>> are the > >>>>>>>>>>>>>>>>>>> occasional WARNING statements from a BUG it appears. They > >>>>>>>>>>>>>>>>>>> trace back > >>>>>>>>>>>>>>>>>>> to the mac.c file inside the ath12k code. There should be > >>>>>>>>>>>>>>>>>>> some in the > >>>>>>>>>>>>>>>>>>> debug log that's attached. Let me know if I can do anything > >>>>>>>>>>>>>>>>>>> else. > >>>>>>>>>>>>>>>>>>> Thanks, > >>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> I have never seen this warning on my upstream setup...Not > >>>>>>>>>>>>>>>>>> sure if you > >>>>>>>>>>>>>>>>>> have changed anything or using the correct code base. > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> Jeff merged this patch-set into ath-202504021602. Can you > >>>>>>>>>>>>>>>>>> try on this > >>>>>>>>>>>>>>>>>> branch? > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> git clone https://git.kernel.org/pub/scm/linux/kernel/git/ > >>>>>>>>>>>>>>>>>> ath/ath.git/ > >>>>>>>>>>>>>>>>>> git pull > >>>>>>>>>>>>>>>>>> git reset --hard ath-202504021602 > >>>>>>>>>>>>>>>>>> compile and install... > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> Also make sure that the firmware you used is from the same > >>>>>>>>>>>>>>>>>> folder, don't > >>>>>>>>>>>>>>>>>> mix with other folders: > >>>>>>>>>>>>>>>>>> linux-firmware/ath12k/WCN7850/hw2.0 > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> 1. rmmod/insmod(debug_mask=0xffff) > >>>>>>>>>>>>>>>>>> 2. iw reg get > >>>>>>>>>>>>>>>>>> 3. iw reg set US > >>>>>>>>>>>>>>>>>> 4. iw xxx scan > >>>>>>>>>>>>>>>>>> wait and collect logs. > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> don't do anything else. > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> Also, can you show me your AP configuration. > >>>>>>>>>>>>>>>>>> If you have another 6 GHz AP, you can have a try(better > >>>>>>>>>>>>>>>>>> different brands). > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> Thanks for testing. > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> Could you share your AP configuration? > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> If you have sniffer, could please capture packets during > >>>>>>>>>>>>>>>>>> testing? > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> Can you capture packets during the testing? I need to check > >>>>>>>>>>>>>>>> probe req > >>>>>>>>>>>>>>>> and probe resp. > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> Thanks! > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>> -Walt > >>>>>>>>>>>>>>>>> OK, I cloned and built the kernel based on your instructions > >>>>>>>>>>>>>>>>> in your > >>>>>>>>>>>>>>>>> last email. Originally, the result was identical to my last > >>>>>>>>>>>>>>>>> email, > >>>>>>>>>>>>>>>>> including the WARNINGS. The .config I use is configured for a > >>>>>>>>>>>>>>>>> fully RT > >>>>>>>>>>>>>>>>> PREEMPT kernel, which I wondered if that was why I was > >>>>>>>>>>>>>>>>> receiving the > >>>>>>>>>>>>>>>>> WARNING. So I configured it as a Low Latency PREEMPT Desktop > >>>>>>>>>>>>>>>>> without > >>>>>>>>>>>>>>>>> the RT_PREEMPT and that eliminated the WARNING. However, > >>>>>>>>>>>>>>>>> still no 6Ghz > >>>>>>>>>>>>>>>>> networks. The firmware I'm using is straight from kernel.org > >>>>>>>>>>>>>>>>> GIT and I > >>>>>>>>>>>>>>>>> do a 'make install; make dedup' to install it. I believe it > >>>>>>>>>>>>>>>>> should be > >>>>>>>>>>>>>>>>> good. Attached is the latest log file. > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> -Walt > >>>>>>>>>>>>> > >>>>>>>>>>>>> Sorry for the top-post earlier. I can't figure out how to capture > >>>>>>>>>>>>> the > >>>>>>>>>>>>> wireless packets as my chip/driver combo doesn't support monitor > >>>>>>>>>>>>> mode. > >>>>>>>>>>>> Your AP also cannot capture wireless packets? > >>>>>>>>>>>> log in AP by usbserial or ssh. > >>>>>>>>>>>> Try to enter command line. use iw command to create monitor > >>>>>>>>>>>> interface. > >>>>>>>>>>>> Then use tcpdump to capture packets. > >>>>>>>>>>>> > >>>>>>>>>>>>> I've attached a tarball that contains the trace data and additional > >>>>>>>>>>>>> firmware logs from the kernel.log file. Anything else you need, just > >>>>>>>>>>>>> ask. Thanks for your help, > >>>>>>>>>>>> > >>>>>>>>>>>> Your AP mac address? > >>>>>>>>>>>> Need it to help check the fw log. > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>>> -Walt > >>>>>>>>>>> Sorry, the AP doesn't have tcpdump available on it. Also, this is a > >>>>>>>>>>> mesh setup with 3 nodes total. The main AP and 2 mesh nodes. I'm > >>>>>>>>>>> within 10 feet of one of the nodes and it's MAC for the wireless 6ghz > >>>>>>>>>>> network is: 10:7C:61:6F:2A:CA > >>>>>>>>>>> > >>>>>>>>>>> -Walt > >>>>>>>>>> The other 2 node 6ghz mac addresses are: > >>>>>>>>>> 10:7C:61:6F:1F:11 - Router > >>>>>>>>>> 10:7C:61:6F:32:92 - Node > >>>>>>>>>> > >>>>>>>>>> The first MAC address I gave you earlier was a node located > >>>>>>>>>> approximately 5 feet from where the laptop is. > >>>>>>>>>> > >>>>>>>>>> -Walt > >>>>>>>>> Well, I'm running into a brick wall it seems trying to get 6Ghz > >>>>>>>>> enabled on this. I tried the ath-next-20250418 tag just now and still > >>>>>>>>> don't see or connect to my 6Ghz network. I applied the patches in: > >>>>>>>>> https://lore.kernel.org/linux-wireless/20250418-ath12k-6g-lp-vlp- > >>>>>>>>> v1-0-c869c86cad60@quicinc.com/T/#t > >>>>>>>>> > >>>>>>>>> hoping that would help, but alas, no 6Ghz networks. I see that MLO and > >>>>>>>>> other nice fixes are coming in 6.16, but without 6Ghz, they'll do me > >>>>>>>>> no good. I'm really wondering if it's a firmware issue that excludes > >>>>>>>>> my chip or something. Again, anything I can do to help, let me know. > >>>>>>>>> Thanks, > >>>>>>>>> > >>>>>>>>> -Walt > >>>>>>>> Well, I used the swiss army tools to look at the firmware, and my chip > >>>>>>>> is listed in the firmware, so it's not excluded or anything. Really > >>>>>>>> puzzlling issue as my other two laptops connect to the 6Ghz network > >>>>>>>> just fine, and this laptop does in Windows, just not in Linux. I > >>>>>>>> really don't use Windows at all though, so that does me no good. > >>>>>>>> > >>>>>>>> This laptop used to connect to the 6Ghz network around the Sep. - Oct. > >>>>>>>> 2024 timeframe. Something has changed and now it doesn't. I'm going to > >>>>>>>> boot off a live image of Ubuntu 24.10 and see if I can see the > >>>>>>>> network. It was always hit or miss so we'll see. > >>>>>>>> -Walt > >>>>>>> > >>>>>>> > >>>>>>> Can you find 6 GHz AP now? > >>>>>>> > >>>>>> > >>>>>> Our firmware team said you station device sent the probe request but > >>>>>> didn't receive the probe resp or beacon. > >>>>>> > >>>>>> Since your current configuration is single 6 GHz AP. Could you change > >>>>>> your AP configuration to 6 GHz + 2/5 GHz to have a retry? > >>>>>> > >>>>> I adedd another network with 2.4 / 5 / 6Ghz settings and still only > >>>>> connect to the 5Ghz network portion. This is verified through wavemon > >>>>> and the AP. I saw some patches recently to address 6 Ghz operatoins in > >>>>> various modes (https://lore.kernel.org/linux-wireless/1692f2f8-c77e-87ce-db70-00b4d9fc7c95@oss.qualcomm.com/), > >>>>> but the patch doesn't apply cleanly to current or ath-pending. Don't > >>>>> know that it would help, but it seemed interesting. > >>>>> > >>>>> When I went back to the older kernel / distro I still could not see > >>>>> the 6 Ghz band nor connect to it. I think something has changed on the > >>>>> AP as well, as this used to work intermittently. I think I have > >>>>> mentioned this before, but I have a dual-boot setup on this laptop and > >>>>> in Windows 11, it does see and connect to the 6 Ghz band and MLO works > >>>>> as well. Also, I have about 5 other devices (phones and laptops) that > >>>>> can all connect to the 6 Ghz band. I think it's a combination of the > >>>>> AP and the driver / firmware. > >>>> > >>>> > >>>> > >>>> > >>>> Do you have another WCN7850? > >>>> Our monitor mode is now in pending branch, and one fix is coming so that > >>>> you can use WCN7850 to capture 6 GHz management packects. So that our > >>>> firmware team can do further research. > >>> > >>> I've successfully put the wifi into monitor mode and captured some > >>> traffic. I used freq. 6615, which is the frequency my Holman-6G runs > >>> at with a width of 320Mhz. I can see beacons and other wifi related > >>> traffic, however, I did not have an encryption key set, so any traffic > >>> should still be encrypted. Hopefully the beacons and other things > >>> help. > >>> I took a chance that the patches were ready and used the most recent > >>> tag: ath-pending-202505201841 and it appeared to work OK. Let me know > >>> if this helps and if you need anything else. Thanks, > >> > >> > >> This is what we needed. > >> > >> But i didn't see probe req in this file. > >> Not sure if you didn't run the test? > >> > >> Can you put this monitor mode device between your test station device > >> and AP device(Try to ensure that it is on the connection line between > >> the two device), then start the full test? > >> Remember run "iw reg set US" before connecting step. > >> > >> > >> Also, please provide us the host/firmware log and the packets. > >> All logs/packets come from the same test, will make it easier for our > >> firmware team to debug. > >> 🙂 > > > > OK, I think I've got something here and I hope it's useful. I did a > > packet capture of the wifi traffic on Freq. 6615 @ 160Mhz from another > > host and then loaded the ath12k module on the problem host and logged > > it all. The wifi adapter for the ath12k is a Quectel model. Also, I > > shut off both mesh nodes so that only the AP was running to ensure we > > were on the same node. > > This is great, thanks. > > > > Please let me know if you need anything else. I > > did see some packets from the ath12k module in the source field of the > > capture so hopefully this helps. > > Oh... you missed the firmware log. > > 1. sudo apt install trace-cmd > 2. sudo trace-cmd record -e ath12k_wmi_diag > 3. run test > 4. "ctrl c" to stop recording: > Hit Ctrl^C to stop recording > ^CCPU0 data recorded at offset=0xdf5000 > 2605056 bytes in size > Then share the trace.dat to us. > > So you need to: > 1. try to capture wireless packets. > 2. capture firmware log(trade.data). > > > Total three files: > trace.dat, kernel.log, wifi-capture.pcapng > 🙂It's a little complicated, but they are necessary, thanks. Sorry about that, was in a hurry for the holiday and forgot about it. Here's the 3 files. -Walt [-- Attachment #2: firmware-log-20250527.txt.gz --] [-- Type: application/gzip, Size: 119244 bytes --] [-- Attachment #3: trace.dat.gz --] [-- Type: application/gzip, Size: 4345054 bytes --] [-- Attachment #4: wifi-capture-20250527.pcapng.gz --] [-- Type: application/gzip, Size: 64940 bytes --] ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ath12k: No 6GHz Wireless found 2025-05-27 21:03 ` Walt Holman @ 2025-05-29 8:24 ` Kang Yang 2025-05-30 21:34 ` Walt Holman 0 siblings, 1 reply; 32+ messages in thread From: Kang Yang @ 2025-05-29 8:24 UTC (permalink / raw) To: Walt Holman, Kang Yang Cc: Jeff Johnson, linux-wireless, ath12k@lists.infradead.org On 5/28/2025 5:03 AM, Walt Holman wrote: > On Thu, May 22, 2025 at 9:12 PM Kang Yang <quic_kangyang@quicinc.com> wrote: >> >> >> On 5/23/2025 1:48 AM, Walt Holman wrote: >>> On Wed, May 21, 2025 at 1:07 AM Kang Yang <quic_kangyang@quicinc.com> wrote: >>>> >>>> >>>> On 5/21/2025 1:05 PM, Walt Holman wrote: >>>>> On Thu, May 15, 2025 at 10:06 PM Kang Yang <quic_kangyang@quicinc.com> wrote: >>>>>> >>>>>> >>>>>> On 5/16/2025 1:47 AM, Walt Holman wrote: >>>>>>> On Thu, May 15, 2025 at 4:22 AM Kang Yang <quic_kangyang@quicinc.com> wrote: >>>>>>>> >>>>>>>> >>>>>>>> On 5/15/2025 4:12 PM, Kang Yang wrote: >>>>>>>>> On 4/20/2025 11:18 PM, Walt Holman wrote: >>>>>>>>>> On Fri, Apr 18, 2025 at 4:18 PM Walt Holman <waltholman09@gmail.com> >>>>>>>>>> wrote: >>>>>>>>>>> On Tue, Apr 15, 2025 at 4:23 PM Walt Holman <waltholman09@gmail.com> >>>>>>>>>>> wrote: >>>>>>>>>>>> On Thu, Apr 10, 2025 at 10:32 AM Walt Holman >>>>>>>>>>>> <waltholman09@gmail.com> wrote: >>>>>>>>>>>>> On Thu, Apr 10, 2025 at 3:26 AM Kang Yang >>>>>>>>>>>>> <kang.yang@oss.qualcomm.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>> On 4/10/2025 3:37 AM, Walt Holman wrote: >>>>>>>>>>>>>>> On Tue, Apr 8, 2025 at 4:17 AM Kang Yang >>>>>>>>>>>>>>> <quic_kangyang@quicinc.com> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On 4/8/2025 1:49 AM, Walt Holman wrote: >>>>>>>>>>>>>>>>> Attached is a small packet capture where I did an 'iw wlp99s0 >>>>>>>>>>>>>>>>> scan' >>>>>>>>>>>>>>>>> and also deactivated and reactivated wireless while the scan was >>>>>>>>>>>>>>>>> ongoing. Hopefully there's something interesting for you in there. >>>>>>>>>>>>>>>>> Also, I've take 3 screenshots showing the configs of the >>>>>>>>>>>>>>>>> wireless AP >>>>>>>>>>>>>>>>> for the 6ghz network. The first screen is just the definition >>>>>>>>>>>>>>>>> of the >>>>>>>>>>>>>>>>> network. No advanced settings are used. The 2nd screen shows the >>>>>>>>>>>>>>>>> channels and radio enabled. The 3rd screen has the advanced >>>>>>>>>>>>>>>>> (professional) settings for the network. I believe I changed >>>>>>>>>>>>>>>>> 'Agile >>>>>>>>>>>>>>>>> Multiband' to enabled, but other settings are their defaults. Hope >>>>>>>>>>>>>>>>> some of this helps. Let me know if you need anything else. Thanks, >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Your packets are Ethernet packets. I need wireless packets. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Not sure if you know how to add a seperate monitor interface to >>>>>>>>>>>>>>>> capture >>>>>>>>>>>>>>>> 6 G channels' packet on your AP(you can google for specific >>>>>>>>>>>>>>>> command). >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Also, please capture firmware log: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> 1. sudo apt install trace-cmd >>>>>>>>>>>>>>>> 2. sudo trace-cmd record -e ath12k_wmi_diag >>>>>>>>>>>>>>>> 3. run test >>>>>>>>>>>>>>>> 4. "ctrl c" to stop recording: >>>>>>>>>>>>>>>> Hit Ctrl^C to stop recording >>>>>>>>>>>>>>>> ^CCPU0 data recorded at offset=0xdf5000 >>>>>>>>>>>>>>>> 2605056 bytes in size >>>>>>>>>>>>>>>> Then share the trace.dat to us. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> So you need to: >>>>>>>>>>>>>>>> 1. try to capture wireless packets. >>>>>>>>>>>>>>>> 2. capture firmware log(trade.data). >>>>>>>>>>>>>>>> 3. save kernel/wpa_supplicant/iw logs. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> -Walt >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Sun, Apr 6, 2025 at 8:58 PM Kang Yang >>>>>>>>>>>>>>>>> <quic_kangyang@quicinc.com> wrote: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On 4/4/2025 12:04 AM, Walt Holman wrote: >>>>>>>>>>>>>>>>>>> On Thu, Apr 3, 2025 at 3:20 AM Kang Yang >>>>>>>>>>>>>>>>>>> <quic_kangyang@quicinc.com> wrote: >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> On 4/3/2025 1:48 AM, Walt Holman wrote: >>>>>>>>>>>>>>>>>>>>> On Tue, Apr 1, 2025 at 9:48 PM Kang Yang >>>>>>>>>>>>>>>>>>>>> <quic_kangyang@quicinc.com> wrote: >>>>>>>>>>>>>>>>>>>>>> Test on 6.14.0-rc5-wt-ath+, with the firmware you used. >>>>>>>>>>>>>>>>>>>>>> I can get 6 GHz AP and connect to it. >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> ath12k_pci 0000:03:00.0: fw_version 0x100301e1 >>>>>>>>>>>>>>>>>>>>>> fw_build_timestamp >>>>>>>>>>>>>>>>>>>>>> 2023-12-06 04:05 fw_build_id >>>>>>>>>>>>>>>>>>>>>> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481- >>>>>>>>>>>>>>>>>>>>>> QCAHMTSWPL_V1.0_V2.0_SILICONZ-3 >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> yk@yk-Mayan:~$ sudo iw wls1 scan | tee iw_scan.log: >>>>>>>>>>>>>>>>>>>>>> BSS 62:03:7f:12:64:64(on wls1) -- associated >>>>>>>>>>>>>>>>>>>>>> TSF: 606308271476 usec (7d, 00:25:08) >>>>>>>>>>>>>>>>>>>>>> freq: 6275 >>>>>>>>>>>>>>>>>>>>>> beacon interval: 100 TUs >>>>>>>>>>>>>>>>>>>>>> capability: ESS Privacy SpectrumMgmt >>>>>>>>>>>>>>>>>>>>>> ShortSlotTime (0x0511) >>>>>>>>>>>>>>>>>>>>>> signal: -17.00 dBm >>>>>>>>>>>>>>>>>>>>>> last seen: 52 ms ago >>>>>>>>>>>>>>>>>>>>>> Information elements from Probe Response frame: >>>>>>>>>>>>>>>>>>>>>> SSID: MLO-KANG-6G >>>>>>>>>>>>>>>>>>>>>> and other 6 GHz APs: >>>>>>>>>>>>>>>>>>>>>> SSID: 6G-gxia >>>>>>>>>>>>>>>>>>>>>> SSID: NETGEAR97-6G >>>>>>>>>>>>>>>>>>>>>> …… >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> kernel log: >>>>>>>>>>>>>>>>>>>>>> [88158.033218] wls1: Inserted STA 62:03:7f:12:64:64 >>>>>>>>>>>>>>>>>>>>>> [88158.033232] wls1: authenticate with 62:03:7f:12:64:64 >>>>>>>>>>>>>>>>>>>>>> (local >>>>>>>>>>>>>>>>>>>>>> address=00:03:7f:37:12:54) >>>>>>>>>>>>>>>>>>>>>> [88158.033242] wls1: send auth to 62:03:7f:12:64:64 (try 1/3) >>>>>>>>>>>>>>>>>>>>>> [88158.041895] wls1: authenticated >>>>>>>>>>>>>>>>>>>>>> [88158.041914] wls1: moving STA 62:03:7f:12:64:64 to state 2 >>>>>>>>>>>>>>>>>>>>>> [88158.044291] wls1: determined local STA to be EHT, BW >>>>>>>>>>>>>>>>>>>>>> limited to 320 MHz >>>>>>>>>>>>>>>>>>>>>> [88158.045719] wls1: associate with 62:03:7f:12:64:64 (try >>>>>>>>>>>>>>>>>>>>>> 1/3) >>>>>>>>>>>>>>>>>>>>>> [88158.067045] wls1: RX AssocResp from 62:03:7f:12:64:64 >>>>>>>>>>>>>>>>>>>>>> (capab=0x511 >>>>>>>>>>>>>>>>>>>>>> status=0 aid=4) >>>>>>>>>>>>>>>>>>>>>> [88158.089090] wls1: associated >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> I can even connect to it by Ubuntu GUI. >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> Can you update to 6.14.0-rc5-wt-ath+ and have a retry? >>>>>>>>>>>>>>>>>>>>>> Also please make >>>>>>>>>>>>>>>>>>>>>> sure that your wpa_supplicant/iw support 6 GHz(or directly >>>>>>>>>>>>>>>>>>>>>> update to the >>>>>>>>>>>>>>>>>>>>>> latest version). >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> If you still cannot find 6 GHz AP, you can set debug_mask >>>>>>>>>>>>>>>>>>>>>> to 0xffffffff >>>>>>>>>>>>>>>>>>>>>> to get ath12k logs. Then give it to us. >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> -Walt >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> OK, I retested with the wt-ath 033125 tagged build. This >>>>>>>>>>>>>>>>>>>>> included the >>>>>>>>>>>>>>>>>>>>> patch the Jeff suggested I try, but the rest of the tree >>>>>>>>>>>>>>>>>>>>> was clean. >>>>>>>>>>>>>>>>>>>>> Still no 6ghz Wifi. I'm attaching a log file of the boot >>>>>>>>>>>>>>>>>>>>> and first few >>>>>>>>>>>>>>>>>>>>> seconds with the debug mask turned on. I noticed that if I >>>>>>>>>>>>>>>>>>>>> rmmod the >>>>>>>>>>>>>>>>>>>>> module and then modprobe it, it complains about not finding >>>>>>>>>>>>>>>>>>>>> firmware-2.bin, however, I thought that was only for the >>>>>>>>>>>>>>>>>>>>> qcn based >>>>>>>>>>>>>>>>>>>>> chip? The HW info from dmesg looks like this: >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> I cannot find this tag... >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> From the log, the 6 GHz channel should work. When scan >>>>>>>>>>>>>>>>>>>> is triggered, FW >>>>>>>>>>>>>>>>>>>> shall send probe req on these channels. If AP send probe >>>>>>>>>>>>>>>>>>>> resp, station >>>>>>>>>>>>>>>>>>>> shall find the AP. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> [ 6.070282] ath12k_pci 0000:63:00.0: BAR 0 [mem >>>>>>>>>>>>>>>>>>>>> 0xdd800000-0xdd9fffff 64bit]: assigned >>>>>>>>>>>>>>>>>>>>> [ 6.070310] ath12k_pci 0000:63:00.0: enabling device >>>>>>>>>>>>>>>>>>>>> (0000 -> 0002) >>>>>>>>>>>>>>>>>>>>> [ 6.071249] ath12k_pci 0000:63:00.0: MSI vectors: 16 >>>>>>>>>>>>>>>>>>>>> [ 6.071254] ath12k_pci 0000:63:00.0: Hardware name: >>>>>>>>>>>>>>>>>>>>> wcn7850 hw2.0 >>>>>>>>>>>>>>>>>>>>> [ 6.596331] ath12k_pci 0000:63:00.0: qmi dma allocation >>>>>>>>>>>>>>>>>>>>> failed >>>>>>>>>>>>>>>>>>>>> (7077888 B type 1), will try later with sma >>>>>>>>>>>>>>>>>>>>> ll size >>>>>>>>>>>>>>>>>>>>> [ 6.604041] ath12k_pci 0000:63:00.0: chip_id 0x2 >>>>>>>>>>>>>>>>>>>>> chip_family 0x4 >>>>>>>>>>>>>>>>>>>>> board_id 0xff soc_id 0x40170200 >>>>>>>>>>>>>>>>>>>>> [ 6.604044] ath12k_pci 0000:63:00.0: fw_version 0x100301e1 >>>>>>>>>>>>>>>>>>>>> fw_build_timestamp 2023-12-06 04:05 fw_build_id >>>>>>>>>>>>>>>>>>>>> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481- >>>>>>>>>>>>>>>>>>>>> QCAHMTSWPL_V1.0_V2.0_SILICONZ- >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> Also, I noticed when looking through the debug logs there >>>>>>>>>>>>>>>>>>>>> are the >>>>>>>>>>>>>>>>>>>>> occasional WARNING statements from a BUG it appears. They >>>>>>>>>>>>>>>>>>>>> trace back >>>>>>>>>>>>>>>>>>>>> to the mac.c file inside the ath12k code. There should be >>>>>>>>>>>>>>>>>>>>> some in the >>>>>>>>>>>>>>>>>>>>> debug log that's attached. Let me know if I can do anything >>>>>>>>>>>>>>>>>>>>> else. >>>>>>>>>>>>>>>>>>>>> Thanks, >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> I have never seen this warning on my upstream setup...Not >>>>>>>>>>>>>>>>>>>> sure if you >>>>>>>>>>>>>>>>>>>> have changed anything or using the correct code base. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Jeff merged this patch-set into ath-202504021602. Can you >>>>>>>>>>>>>>>>>>>> try on this >>>>>>>>>>>>>>>>>>>> branch? >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> git clone https://git.kernel.org/pub/scm/linux/kernel/git/ >>>>>>>>>>>>>>>>>>>> ath/ath.git/ >>>>>>>>>>>>>>>>>>>> git pull >>>>>>>>>>>>>>>>>>>> git reset --hard ath-202504021602 >>>>>>>>>>>>>>>>>>>> compile and install... >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Also make sure that the firmware you used is from the same >>>>>>>>>>>>>>>>>>>> folder, don't >>>>>>>>>>>>>>>>>>>> mix with other folders: >>>>>>>>>>>>>>>>>>>> linux-firmware/ath12k/WCN7850/hw2.0 >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> 1. rmmod/insmod(debug_mask=0xffff) >>>>>>>>>>>>>>>>>>>> 2. iw reg get >>>>>>>>>>>>>>>>>>>> 3. iw reg set US >>>>>>>>>>>>>>>>>>>> 4. iw xxx scan >>>>>>>>>>>>>>>>>>>> wait and collect logs. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> don't do anything else. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Also, can you show me your AP configuration. >>>>>>>>>>>>>>>>>>>> If you have another 6 GHz AP, you can have a try(better >>>>>>>>>>>>>>>>>>>> different brands). >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Thanks for testing. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Could you share your AP configuration? >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> If you have sniffer, could please capture packets during >>>>>>>>>>>>>>>>>>>> testing? >>>>>>>>>>>>>>>>>> Can you capture packets during the testing? I need to check >>>>>>>>>>>>>>>>>> probe req >>>>>>>>>>>>>>>>>> and probe resp. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Thanks! >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> -Walt >>>>>>>>>>>>>>>>>>> OK, I cloned and built the kernel based on your instructions >>>>>>>>>>>>>>>>>>> in your >>>>>>>>>>>>>>>>>>> last email. Originally, the result was identical to my last >>>>>>>>>>>>>>>>>>> email, >>>>>>>>>>>>>>>>>>> including the WARNINGS. The .config I use is configured for a >>>>>>>>>>>>>>>>>>> fully RT >>>>>>>>>>>>>>>>>>> PREEMPT kernel, which I wondered if that was why I was >>>>>>>>>>>>>>>>>>> receiving the >>>>>>>>>>>>>>>>>>> WARNING. So I configured it as a Low Latency PREEMPT Desktop >>>>>>>>>>>>>>>>>>> without >>>>>>>>>>>>>>>>>>> the RT_PREEMPT and that eliminated the WARNING. However, >>>>>>>>>>>>>>>>>>> still no 6Ghz >>>>>>>>>>>>>>>>>>> networks. The firmware I'm using is straight from kernel.org >>>>>>>>>>>>>>>>>>> GIT and I >>>>>>>>>>>>>>>>>>> do a 'make install; make dedup' to install it. I believe it >>>>>>>>>>>>>>>>>>> should be >>>>>>>>>>>>>>>>>>> good. Attached is the latest log file. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> -Walt >>>>>>>>>>>>>>> Sorry for the top-post earlier. I can't figure out how to capture >>>>>>>>>>>>>>> the >>>>>>>>>>>>>>> wireless packets as my chip/driver combo doesn't support monitor >>>>>>>>>>>>>>> mode. >>>>>>>>>>>>>> Your AP also cannot capture wireless packets? >>>>>>>>>>>>>> log in AP by usbserial or ssh. >>>>>>>>>>>>>> Try to enter command line. use iw command to create monitor >>>>>>>>>>>>>> interface. >>>>>>>>>>>>>> Then use tcpdump to capture packets. >>>>>>>>>>>>>> >>>>>>>>>>>>>>> I've attached a tarball that contains the trace data and additional >>>>>>>>>>>>>>> firmware logs from the kernel.log file. Anything else you need, just >>>>>>>>>>>>>>> ask. Thanks for your help, >>>>>>>>>>>>>> Your AP mac address? >>>>>>>>>>>>>> Need it to help check the fw log. >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>>> -Walt >>>>>>>>>>>>> Sorry, the AP doesn't have tcpdump available on it. Also, this is a >>>>>>>>>>>>> mesh setup with 3 nodes total. The main AP and 2 mesh nodes. I'm >>>>>>>>>>>>> within 10 feet of one of the nodes and it's MAC for the wireless 6ghz >>>>>>>>>>>>> network is: 10:7C:61:6F:2A:CA >>>>>>>>>>>>> >>>>>>>>>>>>> -Walt >>>>>>>>>>>> The other 2 node 6ghz mac addresses are: >>>>>>>>>>>> 10:7C:61:6F:1F:11 - Router >>>>>>>>>>>> 10:7C:61:6F:32:92 - Node >>>>>>>>>>>> >>>>>>>>>>>> The first MAC address I gave you earlier was a node located >>>>>>>>>>>> approximately 5 feet from where the laptop is. >>>>>>>>>>>> >>>>>>>>>>>> -Walt >>>>>>>>>>> Well, I'm running into a brick wall it seems trying to get 6Ghz >>>>>>>>>>> enabled on this. I tried the ath-next-20250418 tag just now and still >>>>>>>>>>> don't see or connect to my 6Ghz network. I applied the patches in: >>>>>>>>>>> https://lore.kernel.org/linux-wireless/20250418-ath12k-6g-lp-vlp- >>>>>>>>>>> v1-0-c869c86cad60@quicinc.com/T/#t >>>>>>>>>>> >>>>>>>>>>> hoping that would help, but alas, no 6Ghz networks. I see that MLO and >>>>>>>>>>> other nice fixes are coming in 6.16, but without 6Ghz, they'll do me >>>>>>>>>>> no good. I'm really wondering if it's a firmware issue that excludes >>>>>>>>>>> my chip or something. Again, anything I can do to help, let me know. >>>>>>>>>>> Thanks, >>>>>>>>>>> >>>>>>>>>>> -Walt >>>>>>>>>> Well, I used the swiss army tools to look at the firmware, and my chip >>>>>>>>>> is listed in the firmware, so it's not excluded or anything. Really >>>>>>>>>> puzzlling issue as my other two laptops connect to the 6Ghz network >>>>>>>>>> just fine, and this laptop does in Windows, just not in Linux. I >>>>>>>>>> really don't use Windows at all though, so that does me no good. >>>>>>>>>> >>>>>>>>>> This laptop used to connect to the 6Ghz network around the Sep. - Oct. >>>>>>>>>> 2024 timeframe. Something has changed and now it doesn't. I'm going to >>>>>>>>>> boot off a live image of Ubuntu 24.10 and see if I can see the >>>>>>>>>> network. It was always hit or miss so we'll see. >>>>>>>>>> -Walt >>>>>>>>> >>>>>>>>> Can you find 6 GHz AP now? >>>>>>>>> >>>>>>>> Our firmware team said you station device sent the probe request but >>>>>>>> didn't receive the probe resp or beacon. >>>>>>>> >>>>>>>> Since your current configuration is single 6 GHz AP. Could you change >>>>>>>> your AP configuration to 6 GHz + 2/5 GHz to have a retry? >>>>>>>> >>>>>>> I adedd another network with 2.4 / 5 / 6Ghz settings and still only >>>>>>> connect to the 5Ghz network portion. This is verified through wavemon >>>>>>> and the AP. I saw some patches recently to address 6 Ghz operatoins in >>>>>>> various modes (https://lore.kernel.org/linux-wireless/1692f2f8-c77e-87ce-db70-00b4d9fc7c95@oss.qualcomm.com/), >>>>>>> but the patch doesn't apply cleanly to current or ath-pending. Don't >>>>>>> know that it would help, but it seemed interesting. >>>>>>> >>>>>>> When I went back to the older kernel / distro I still could not see >>>>>>> the 6 Ghz band nor connect to it. I think something has changed on the >>>>>>> AP as well, as this used to work intermittently. I think I have >>>>>>> mentioned this before, but I have a dual-boot setup on this laptop and >>>>>>> in Windows 11, it does see and connect to the 6 Ghz band and MLO works >>>>>>> as well. Also, I have about 5 other devices (phones and laptops) that >>>>>>> can all connect to the 6 Ghz band. I think it's a combination of the >>>>>>> AP and the driver / firmware. >>>>>> >>>>>> >>>>>> >>>>>> Do you have another WCN7850? >>>>>> Our monitor mode is now in pending branch, and one fix is coming so that >>>>>> you can use WCN7850 to capture 6 GHz management packects. So that our >>>>>> firmware team can do further research. >>>>> I've successfully put the wifi into monitor mode and captured some >>>>> traffic. I used freq. 6615, which is the frequency my Holman-6G runs >>>>> at with a width of 320Mhz. I can see beacons and other wifi related >>>>> traffic, however, I did not have an encryption key set, so any traffic >>>>> should still be encrypted. Hopefully the beacons and other things >>>>> help. >>>>> I took a chance that the patches were ready and used the most recent >>>>> tag: ath-pending-202505201841 and it appeared to work OK. Let me know >>>>> if this helps and if you need anything else. Thanks, >>>> >>>> This is what we needed. >>>> >>>> But i didn't see probe req in this file. >>>> Not sure if you didn't run the test? >>>> >>>> Can you put this monitor mode device between your test station device >>>> and AP device(Try to ensure that it is on the connection line between >>>> the two device), then start the full test? >>>> Remember run "iw reg set US" before connecting step. >>>> >>>> >>>> Also, please provide us the host/firmware log and the packets. >>>> All logs/packets come from the same test, will make it easier for our >>>> firmware team to debug. >>>> 🙂 >>> OK, I think I've got something here and I hope it's useful. I did a >>> packet capture of the wifi traffic on Freq. 6615 @ 160Mhz from another >>> host and then loaded the ath12k module on the problem host and logged >>> it all. The wifi adapter for the ath12k is a Quectel model. Also, I >>> shut off both mesh nodes so that only the AP was running to ensure we >>> were on the same node. >> This is great, thanks. >> >> >>> Please let me know if you need anything else. I >>> did see some packets from the ath12k module in the source field of the >>> capture so hopefully this helps. >> Oh... you missed the firmware log. >> >> 1. sudo apt install trace-cmd >> 2. sudo trace-cmd record -e ath12k_wmi_diag >> 3. run test >> 4. "ctrl c" to stop recording: >> Hit Ctrl^C to stop recording >> ^CCPU0 data recorded at offset=0xdf5000 >> 2605056 bytes in size >> Then share the trace.dat to us. >> >> So you need to: >> 1. try to capture wireless packets. >> 2. capture firmware log(trade.data). >> >> >> Total three files: >> trace.dat, kernel.log, wifi-capture.pcapng >> 🙂It's a little complicated, but they are necessary, thanks. > Sorry about that, was in a hurry for the holiday and forgot about it. > Here's the 3 files. Thanks! According to your logs, it is 6G non_transmitted MBSSID and with wildcard ssid. Offiline sync with firmware team. For this kind of AP, station shuold add SSID in scan so that we can receive probe resp from this AP. So can you test again and collect the wpa_supplicant log? Also, remember to collect the trace.dat/capture packets. 1.Please add some logs in ath12k_wmi_send_scan_start_cmd(). if (arg->num_ssids) { ssid = ptr; for (i = 0; i < arg->num_ssids; ++i) { ssid->ssid_len = cpu_to_le32(arg->ssid[i].ssid_len); memcpy(ssid->ssid, arg->ssid[i].ssid, arg->ssid[i].ssid_len); ssid++; } } Firmware team needs to check the "ssid->ssid"🙂 thanks! 2. add network config in wpa_supplicant.conf like: network={ ssid="Holman-6G" psk="1234567890" scan_ssid=1 key_mgmt=SAE disabled=0 } ideally, you will see wpa_supplicant logs like: wls1: nl80211: New scan results available nl80211: Scan probed for SSID 'Holman-6G' nl80211: Scan probed for SSID '' Step 2 is necessary because we won't send probe req to these hidden AP unless it is configured in wpa_supplicant. There may be slight differences in the wpa_supplicant configuration, please make changes according to your AP's configuration. > > -Walt ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ath12k: No 6GHz Wireless found 2025-05-29 8:24 ` Kang Yang @ 2025-05-30 21:34 ` Walt Holman 0 siblings, 0 replies; 32+ messages in thread From: Walt Holman @ 2025-05-30 21:34 UTC (permalink / raw) To: Kang Yang Cc: Kang Yang, Jeff Johnson, linux-wireless, ath12k@lists.infradead.org On Thu, May 29, 2025 at 3:24 AM Kang Yang <kang.yang@oss.qualcomm.com> wrote: > > > On 5/28/2025 5:03 AM, Walt Holman wrote: > > On Thu, May 22, 2025 at 9:12 PM Kang Yang <quic_kangyang@quicinc.com> wrote: > >> > >> > >> On 5/23/2025 1:48 AM, Walt Holman wrote: > >>> On Wed, May 21, 2025 at 1:07 AM Kang Yang <quic_kangyang@quicinc.com> wrote: > >>>> > >>>> > >>>> On 5/21/2025 1:05 PM, Walt Holman wrote: > >>>>> On Thu, May 15, 2025 at 10:06 PM Kang Yang <quic_kangyang@quicinc.com> wrote: > >>>>>> > >>>>>> > >>>>>> On 5/16/2025 1:47 AM, Walt Holman wrote: > >>>>>>> On Thu, May 15, 2025 at 4:22 AM Kang Yang <quic_kangyang@quicinc.com> wrote: > >>>>>>>> > >>>>>>>> > >>>>>>>> On 5/15/2025 4:12 PM, Kang Yang wrote: > >>>>>>>>> On 4/20/2025 11:18 PM, Walt Holman wrote: > >>>>>>>>>> On Fri, Apr 18, 2025 at 4:18 PM Walt Holman <waltholman09@gmail.com> > >>>>>>>>>> wrote: > >>>>>>>>>>> On Tue, Apr 15, 2025 at 4:23 PM Walt Holman <waltholman09@gmail.com> > >>>>>>>>>>> wrote: > >>>>>>>>>>>> On Thu, Apr 10, 2025 at 10:32 AM Walt Holman > >>>>>>>>>>>> <waltholman09@gmail.com> wrote: > >>>>>>>>>>>>> On Thu, Apr 10, 2025 at 3:26 AM Kang Yang > >>>>>>>>>>>>> <kang.yang@oss.qualcomm.com> wrote: > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> On 4/10/2025 3:37 AM, Walt Holman wrote: > >>>>>>>>>>>>>>> On Tue, Apr 8, 2025 at 4:17 AM Kang Yang > >>>>>>>>>>>>>>> <quic_kangyang@quicinc.com> wrote: > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> On 4/8/2025 1:49 AM, Walt Holman wrote: > >>>>>>>>>>>>>>>>> Attached is a small packet capture where I did an 'iw wlp99s0 > >>>>>>>>>>>>>>>>> scan' > >>>>>>>>>>>>>>>>> and also deactivated and reactivated wireless while the scan was > >>>>>>>>>>>>>>>>> ongoing. Hopefully there's something interesting for you in there. > >>>>>>>>>>>>>>>>> Also, I've take 3 screenshots showing the configs of the > >>>>>>>>>>>>>>>>> wireless AP > >>>>>>>>>>>>>>>>> for the 6ghz network. The first screen is just the definition > >>>>>>>>>>>>>>>>> of the > >>>>>>>>>>>>>>>>> network. No advanced settings are used. The 2nd screen shows the > >>>>>>>>>>>>>>>>> channels and radio enabled. The 3rd screen has the advanced > >>>>>>>>>>>>>>>>> (professional) settings for the network. I believe I changed > >>>>>>>>>>>>>>>>> 'Agile > >>>>>>>>>>>>>>>>> Multiband' to enabled, but other settings are their defaults. Hope > >>>>>>>>>>>>>>>>> some of this helps. Let me know if you need anything else. Thanks, > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> Your packets are Ethernet packets. I need wireless packets. > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> Not sure if you know how to add a seperate monitor interface to > >>>>>>>>>>>>>>>> capture > >>>>>>>>>>>>>>>> 6 G channels' packet on your AP(you can google for specific > >>>>>>>>>>>>>>>> command). > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> Also, please capture firmware log: > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> 1. sudo apt install trace-cmd > >>>>>>>>>>>>>>>> 2. sudo trace-cmd record -e ath12k_wmi_diag > >>>>>>>>>>>>>>>> 3. run test > >>>>>>>>>>>>>>>> 4. "ctrl c" to stop recording: > >>>>>>>>>>>>>>>> Hit Ctrl^C to stop recording > >>>>>>>>>>>>>>>> ^CCPU0 data recorded at offset=0xdf5000 > >>>>>>>>>>>>>>>> 2605056 bytes in size > >>>>>>>>>>>>>>>> Then share the trace.dat to us. > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> So you need to: > >>>>>>>>>>>>>>>> 1. try to capture wireless packets. > >>>>>>>>>>>>>>>> 2. capture firmware log(trade.data). > >>>>>>>>>>>>>>>> 3. save kernel/wpa_supplicant/iw logs. > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> -Walt > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> On Sun, Apr 6, 2025 at 8:58 PM Kang Yang > >>>>>>>>>>>>>>>>> <quic_kangyang@quicinc.com> wrote: > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> On 4/4/2025 12:04 AM, Walt Holman wrote: > >>>>>>>>>>>>>>>>>>> On Thu, Apr 3, 2025 at 3:20 AM Kang Yang > >>>>>>>>>>>>>>>>>>> <quic_kangyang@quicinc.com> wrote: > >>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>> On 4/3/2025 1:48 AM, Walt Holman wrote: > >>>>>>>>>>>>>>>>>>>>> On Tue, Apr 1, 2025 at 9:48 PM Kang Yang > >>>>>>>>>>>>>>>>>>>>> <quic_kangyang@quicinc.com> wrote: > >>>>>>>>>>>>>>>>>>>>>> Test on 6.14.0-rc5-wt-ath+, with the firmware you used. > >>>>>>>>>>>>>>>>>>>>>> I can get 6 GHz AP and connect to it. > >>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>> ath12k_pci 0000:03:00.0: fw_version 0x100301e1 > >>>>>>>>>>>>>>>>>>>>>> fw_build_timestamp > >>>>>>>>>>>>>>>>>>>>>> 2023-12-06 04:05 fw_build_id > >>>>>>>>>>>>>>>>>>>>>> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481- > >>>>>>>>>>>>>>>>>>>>>> QCAHMTSWPL_V1.0_V2.0_SILICONZ-3 > >>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>> yk@yk-Mayan:~$ sudo iw wls1 scan | tee iw_scan.log: > >>>>>>>>>>>>>>>>>>>>>> BSS 62:03:7f:12:64:64(on wls1) -- associated > >>>>>>>>>>>>>>>>>>>>>> TSF: 606308271476 usec (7d, 00:25:08) > >>>>>>>>>>>>>>>>>>>>>> freq: 6275 > >>>>>>>>>>>>>>>>>>>>>> beacon interval: 100 TUs > >>>>>>>>>>>>>>>>>>>>>> capability: ESS Privacy SpectrumMgmt > >>>>>>>>>>>>>>>>>>>>>> ShortSlotTime (0x0511) > >>>>>>>>>>>>>>>>>>>>>> signal: -17.00 dBm > >>>>>>>>>>>>>>>>>>>>>> last seen: 52 ms ago > >>>>>>>>>>>>>>>>>>>>>> Information elements from Probe Response frame: > >>>>>>>>>>>>>>>>>>>>>> SSID: MLO-KANG-6G > >>>>>>>>>>>>>>>>>>>>>> and other 6 GHz APs: > >>>>>>>>>>>>>>>>>>>>>> SSID: 6G-gxia > >>>>>>>>>>>>>>>>>>>>>> SSID: NETGEAR97-6G > >>>>>>>>>>>>>>>>>>>>>> …… > >>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>> kernel log: > >>>>>>>>>>>>>>>>>>>>>> [88158.033218] wls1: Inserted STA 62:03:7f:12:64:64 > >>>>>>>>>>>>>>>>>>>>>> [88158.033232] wls1: authenticate with 62:03:7f:12:64:64 > >>>>>>>>>>>>>>>>>>>>>> (local > >>>>>>>>>>>>>>>>>>>>>> address=00:03:7f:37:12:54) > >>>>>>>>>>>>>>>>>>>>>> [88158.033242] wls1: send auth to 62:03:7f:12:64:64 (try 1/3) > >>>>>>>>>>>>>>>>>>>>>> [88158.041895] wls1: authenticated > >>>>>>>>>>>>>>>>>>>>>> [88158.041914] wls1: moving STA 62:03:7f:12:64:64 to state 2 > >>>>>>>>>>>>>>>>>>>>>> [88158.044291] wls1: determined local STA to be EHT, BW > >>>>>>>>>>>>>>>>>>>>>> limited to 320 MHz > >>>>>>>>>>>>>>>>>>>>>> [88158.045719] wls1: associate with 62:03:7f:12:64:64 (try > >>>>>>>>>>>>>>>>>>>>>> 1/3) > >>>>>>>>>>>>>>>>>>>>>> [88158.067045] wls1: RX AssocResp from 62:03:7f:12:64:64 > >>>>>>>>>>>>>>>>>>>>>> (capab=0x511 > >>>>>>>>>>>>>>>>>>>>>> status=0 aid=4) > >>>>>>>>>>>>>>>>>>>>>> [88158.089090] wls1: associated > >>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>> I can even connect to it by Ubuntu GUI. > >>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>> Can you update to 6.14.0-rc5-wt-ath+ and have a retry? > >>>>>>>>>>>>>>>>>>>>>> Also please make > >>>>>>>>>>>>>>>>>>>>>> sure that your wpa_supplicant/iw support 6 GHz(or directly > >>>>>>>>>>>>>>>>>>>>>> update to the > >>>>>>>>>>>>>>>>>>>>>> latest version). > >>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>> If you still cannot find 6 GHz AP, you can set debug_mask > >>>>>>>>>>>>>>>>>>>>>> to 0xffffffff > >>>>>>>>>>>>>>>>>>>>>> to get ath12k logs. Then give it to us. > >>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>> -Walt > >>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>> OK, I retested with the wt-ath 033125 tagged build. This > >>>>>>>>>>>>>>>>>>>>> included the > >>>>>>>>>>>>>>>>>>>>> patch the Jeff suggested I try, but the rest of the tree > >>>>>>>>>>>>>>>>>>>>> was clean. > >>>>>>>>>>>>>>>>>>>>> Still no 6ghz Wifi. I'm attaching a log file of the boot > >>>>>>>>>>>>>>>>>>>>> and first few > >>>>>>>>>>>>>>>>>>>>> seconds with the debug mask turned on. I noticed that if I > >>>>>>>>>>>>>>>>>>>>> rmmod the > >>>>>>>>>>>>>>>>>>>>> module and then modprobe it, it complains about not finding > >>>>>>>>>>>>>>>>>>>>> firmware-2.bin, however, I thought that was only for the > >>>>>>>>>>>>>>>>>>>>> qcn based > >>>>>>>>>>>>>>>>>>>>> chip? The HW info from dmesg looks like this: > >>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>> I cannot find this tag... > >>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>> From the log, the 6 GHz channel should work. When scan > >>>>>>>>>>>>>>>>>>>> is triggered, FW > >>>>>>>>>>>>>>>>>>>> shall send probe req on these channels. If AP send probe > >>>>>>>>>>>>>>>>>>>> resp, station > >>>>>>>>>>>>>>>>>>>> shall find the AP. > >>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>> [ 6.070282] ath12k_pci 0000:63:00.0: BAR 0 [mem > >>>>>>>>>>>>>>>>>>>>> 0xdd800000-0xdd9fffff 64bit]: assigned > >>>>>>>>>>>>>>>>>>>>> [ 6.070310] ath12k_pci 0000:63:00.0: enabling device > >>>>>>>>>>>>>>>>>>>>> (0000 -> 0002) > >>>>>>>>>>>>>>>>>>>>> [ 6.071249] ath12k_pci 0000:63:00.0: MSI vectors: 16 > >>>>>>>>>>>>>>>>>>>>> [ 6.071254] ath12k_pci 0000:63:00.0: Hardware name: > >>>>>>>>>>>>>>>>>>>>> wcn7850 hw2.0 > >>>>>>>>>>>>>>>>>>>>> [ 6.596331] ath12k_pci 0000:63:00.0: qmi dma allocation > >>>>>>>>>>>>>>>>>>>>> failed > >>>>>>>>>>>>>>>>>>>>> (7077888 B type 1), will try later with sma > >>>>>>>>>>>>>>>>>>>>> ll size > >>>>>>>>>>>>>>>>>>>>> [ 6.604041] ath12k_pci 0000:63:00.0: chip_id 0x2 > >>>>>>>>>>>>>>>>>>>>> chip_family 0x4 > >>>>>>>>>>>>>>>>>>>>> board_id 0xff soc_id 0x40170200 > >>>>>>>>>>>>>>>>>>>>> [ 6.604044] ath12k_pci 0000:63:00.0: fw_version 0x100301e1 > >>>>>>>>>>>>>>>>>>>>> fw_build_timestamp 2023-12-06 04:05 fw_build_id > >>>>>>>>>>>>>>>>>>>>> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481- > >>>>>>>>>>>>>>>>>>>>> QCAHMTSWPL_V1.0_V2.0_SILICONZ- > >>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>> Also, I noticed when looking through the debug logs there > >>>>>>>>>>>>>>>>>>>>> are the > >>>>>>>>>>>>>>>>>>>>> occasional WARNING statements from a BUG it appears. They > >>>>>>>>>>>>>>>>>>>>> trace back > >>>>>>>>>>>>>>>>>>>>> to the mac.c file inside the ath12k code. There should be > >>>>>>>>>>>>>>>>>>>>> some in the > >>>>>>>>>>>>>>>>>>>>> debug log that's attached. Let me know if I can do anything > >>>>>>>>>>>>>>>>>>>>> else. > >>>>>>>>>>>>>>>>>>>>> Thanks, > >>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>> I have never seen this warning on my upstream setup...Not > >>>>>>>>>>>>>>>>>>>> sure if you > >>>>>>>>>>>>>>>>>>>> have changed anything or using the correct code base. > >>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>> Jeff merged this patch-set into ath-202504021602. Can you > >>>>>>>>>>>>>>>>>>>> try on this > >>>>>>>>>>>>>>>>>>>> branch? > >>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>> git clone https://git.kernel.org/pub/scm/linux/kernel/git/ > >>>>>>>>>>>>>>>>>>>> ath/ath.git/ > >>>>>>>>>>>>>>>>>>>> git pull > >>>>>>>>>>>>>>>>>>>> git reset --hard ath-202504021602 > >>>>>>>>>>>>>>>>>>>> compile and install... > >>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>> Also make sure that the firmware you used is from the same > >>>>>>>>>>>>>>>>>>>> folder, don't > >>>>>>>>>>>>>>>>>>>> mix with other folders: > >>>>>>>>>>>>>>>>>>>> linux-firmware/ath12k/WCN7850/hw2.0 > >>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>> 1. rmmod/insmod(debug_mask=0xffff) > >>>>>>>>>>>>>>>>>>>> 2. iw reg get > >>>>>>>>>>>>>>>>>>>> 3. iw reg set US > >>>>>>>>>>>>>>>>>>>> 4. iw xxx scan > >>>>>>>>>>>>>>>>>>>> wait and collect logs. > >>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>> don't do anything else. > >>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>> Also, can you show me your AP configuration. > >>>>>>>>>>>>>>>>>>>> If you have another 6 GHz AP, you can have a try(better > >>>>>>>>>>>>>>>>>>>> different brands). > >>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> Thanks for testing. > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> Could you share your AP configuration? > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>> If you have sniffer, could please capture packets during > >>>>>>>>>>>>>>>>>>>> testing? > >>>>>>>>>>>>>>>>>> Can you capture packets during the testing? I need to check > >>>>>>>>>>>>>>>>>> probe req > >>>>>>>>>>>>>>>>>> and probe resp. > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>> Thanks! > >>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>> -Walt > >>>>>>>>>>>>>>>>>>> OK, I cloned and built the kernel based on your instructions > >>>>>>>>>>>>>>>>>>> in your > >>>>>>>>>>>>>>>>>>> last email. Originally, the result was identical to my last > >>>>>>>>>>>>>>>>>>> email, > >>>>>>>>>>>>>>>>>>> including the WARNINGS. The .config I use is configured for a > >>>>>>>>>>>>>>>>>>> fully RT > >>>>>>>>>>>>>>>>>>> PREEMPT kernel, which I wondered if that was why I was > >>>>>>>>>>>>>>>>>>> receiving the > >>>>>>>>>>>>>>>>>>> WARNING. So I configured it as a Low Latency PREEMPT Desktop > >>>>>>>>>>>>>>>>>>> without > >>>>>>>>>>>>>>>>>>> the RT_PREEMPT and that eliminated the WARNING. However, > >>>>>>>>>>>>>>>>>>> still no 6Ghz > >>>>>>>>>>>>>>>>>>> networks. The firmware I'm using is straight from kernel.org > >>>>>>>>>>>>>>>>>>> GIT and I > >>>>>>>>>>>>>>>>>>> do a 'make install; make dedup' to install it. I believe it > >>>>>>>>>>>>>>>>>>> should be > >>>>>>>>>>>>>>>>>>> good. Attached is the latest log file. > >>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>> -Walt > >>>>>>>>>>>>>>> Sorry for the top-post earlier. I can't figure out how to capture > >>>>>>>>>>>>>>> the > >>>>>>>>>>>>>>> wireless packets as my chip/driver combo doesn't support monitor > >>>>>>>>>>>>>>> mode. > >>>>>>>>>>>>>> Your AP also cannot capture wireless packets? > >>>>>>>>>>>>>> log in AP by usbserial or ssh. > >>>>>>>>>>>>>> Try to enter command line. use iw command to create monitor > >>>>>>>>>>>>>> interface. > >>>>>>>>>>>>>> Then use tcpdump to capture packets. > >>>>>>>>>>>>>> > >>>>>>>>>>>>>>> I've attached a tarball that contains the trace data and additional > >>>>>>>>>>>>>>> firmware logs from the kernel.log file. Anything else you need, just > >>>>>>>>>>>>>>> ask. Thanks for your help, > >>>>>>>>>>>>>> Your AP mac address? > >>>>>>>>>>>>>> Need it to help check the fw log. > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>>> -Walt > >>>>>>>>>>>>> Sorry, the AP doesn't have tcpdump available on it. Also, this is a > >>>>>>>>>>>>> mesh setup with 3 nodes total. The main AP and 2 mesh nodes. I'm > >>>>>>>>>>>>> within 10 feet of one of the nodes and it's MAC for the wireless 6ghz > >>>>>>>>>>>>> network is: 10:7C:61:6F:2A:CA > >>>>>>>>>>>>> > >>>>>>>>>>>>> -Walt > >>>>>>>>>>>> The other 2 node 6ghz mac addresses are: > >>>>>>>>>>>> 10:7C:61:6F:1F:11 - Router > >>>>>>>>>>>> 10:7C:61:6F:32:92 - Node > >>>>>>>>>>>> > >>>>>>>>>>>> The first MAC address I gave you earlier was a node located > >>>>>>>>>>>> approximately 5 feet from where the laptop is. > >>>>>>>>>>>> > >>>>>>>>>>>> -Walt > >>>>>>>>>>> Well, I'm running into a brick wall it seems trying to get 6Ghz > >>>>>>>>>>> enabled on this. I tried the ath-next-20250418 tag just now and still > >>>>>>>>>>> don't see or connect to my 6Ghz network. I applied the patches in: > >>>>>>>>>>> https://lore.kernel.org/linux-wireless/20250418-ath12k-6g-lp-vlp- > >>>>>>>>>>> v1-0-c869c86cad60@quicinc.com/T/#t > >>>>>>>>>>> > >>>>>>>>>>> hoping that would help, but alas, no 6Ghz networks. I see that MLO and > >>>>>>>>>>> other nice fixes are coming in 6.16, but without 6Ghz, they'll do me > >>>>>>>>>>> no good. I'm really wondering if it's a firmware issue that excludes > >>>>>>>>>>> my chip or something. Again, anything I can do to help, let me know. > >>>>>>>>>>> Thanks, > >>>>>>>>>>> > >>>>>>>>>>> -Walt > >>>>>>>>>> Well, I used the swiss army tools to look at the firmware, and my chip > >>>>>>>>>> is listed in the firmware, so it's not excluded or anything. Really > >>>>>>>>>> puzzlling issue as my other two laptops connect to the 6Ghz network > >>>>>>>>>> just fine, and this laptop does in Windows, just not in Linux. I > >>>>>>>>>> really don't use Windows at all though, so that does me no good. > >>>>>>>>>> > >>>>>>>>>> This laptop used to connect to the 6Ghz network around the Sep. - Oct. > >>>>>>>>>> 2024 timeframe. Something has changed and now it doesn't. I'm going to > >>>>>>>>>> boot off a live image of Ubuntu 24.10 and see if I can see the > >>>>>>>>>> network. It was always hit or miss so we'll see. > >>>>>>>>>> -Walt > >>>>>>>>> > >>>>>>>>> Can you find 6 GHz AP now? > >>>>>>>>> > >>>>>>>> Our firmware team said you station device sent the probe request but > >>>>>>>> didn't receive the probe resp or beacon. > >>>>>>>> > >>>>>>>> Since your current configuration is single 6 GHz AP. Could you change > >>>>>>>> your AP configuration to 6 GHz + 2/5 GHz to have a retry? > >>>>>>>> > >>>>>>> I adedd another network with 2.4 / 5 / 6Ghz settings and still only > >>>>>>> connect to the 5Ghz network portion. This is verified through wavemon > >>>>>>> and the AP. I saw some patches recently to address 6 Ghz operatoins in > >>>>>>> various modes (https://lore.kernel.org/linux-wireless/1692f2f8-c77e-87ce-db70-00b4d9fc7c95@oss.qualcomm.com/), > >>>>>>> but the patch doesn't apply cleanly to current or ath-pending. Don't > >>>>>>> know that it would help, but it seemed interesting. > >>>>>>> > >>>>>>> When I went back to the older kernel / distro I still could not see > >>>>>>> the 6 Ghz band nor connect to it. I think something has changed on the > >>>>>>> AP as well, as this used to work intermittently. I think I have > >>>>>>> mentioned this before, but I have a dual-boot setup on this laptop and > >>>>>>> in Windows 11, it does see and connect to the 6 Ghz band and MLO works > >>>>>>> as well. Also, I have about 5 other devices (phones and laptops) that > >>>>>>> can all connect to the 6 Ghz band. I think it's a combination of the > >>>>>>> AP and the driver / firmware. > >>>>>> > >>>>>> > >>>>>> > >>>>>> Do you have another WCN7850? > >>>>>> Our monitor mode is now in pending branch, and one fix is coming so that > >>>>>> you can use WCN7850 to capture 6 GHz management packects. So that our > >>>>>> firmware team can do further research. > >>>>> I've successfully put the wifi into monitor mode and captured some > >>>>> traffic. I used freq. 6615, which is the frequency my Holman-6G runs > >>>>> at with a width of 320Mhz. I can see beacons and other wifi related > >>>>> traffic, however, I did not have an encryption key set, so any traffic > >>>>> should still be encrypted. Hopefully the beacons and other things > >>>>> help. > >>>>> I took a chance that the patches were ready and used the most recent > >>>>> tag: ath-pending-202505201841 and it appeared to work OK. Let me know > >>>>> if this helps and if you need anything else. Thanks, > >>>> > >>>> This is what we needed. > >>>> > >>>> But i didn't see probe req in this file. > >>>> Not sure if you didn't run the test? > >>>> > >>>> Can you put this monitor mode device between your test station device > >>>> and AP device(Try to ensure that it is on the connection line between > >>>> the two device), then start the full test? > >>>> Remember run "iw reg set US" before connecting step. > >>>> > >>>> > >>>> Also, please provide us the host/firmware log and the packets. > >>>> All logs/packets come from the same test, will make it easier for our > >>>> firmware team to debug. > >>>> 🙂 > >>> OK, I think I've got something here and I hope it's useful. I did a > >>> packet capture of the wifi traffic on Freq. 6615 @ 160Mhz from another > >>> host and then loaded the ath12k module on the problem host and logged > >>> it all. The wifi adapter for the ath12k is a Quectel model. Also, I > >>> shut off both mesh nodes so that only the AP was running to ensure we > >>> were on the same node. > >> This is great, thanks. > >> > >> > >>> Please let me know if you need anything else. I > >>> did see some packets from the ath12k module in the source field of the > >>> capture so hopefully this helps. > >> Oh... you missed the firmware log. > >> > >> 1. sudo apt install trace-cmd > >> 2. sudo trace-cmd record -e ath12k_wmi_diag > >> 3. run test > >> 4. "ctrl c" to stop recording: > >> Hit Ctrl^C to stop recording > >> ^CCPU0 data recorded at offset=0xdf5000 > >> 2605056 bytes in size > >> Then share the trace.dat to us. > >> > >> So you need to: > >> 1. try to capture wireless packets. > >> 2. capture firmware log(trade.data). > >> > >> > >> Total three files: > >> trace.dat, kernel.log, wifi-capture.pcapng > >> 🙂It's a little complicated, but they are necessary, thanks. > > Sorry about that, was in a hurry for the holiday and forgot about it. > > Here's the 3 files. > > > Thanks! > > > According to your logs, it is 6G non_transmitted MBSSID and with > wildcard ssid. Offiline sync with firmware team. > > For this kind of AP, station shuold add SSID in scan so that we can > receive probe resp from this AP. > > So can you test again and collect the wpa_supplicant log? Also, remember > to collect the trace.dat/capture packets. > > > 1.Please add some logs in ath12k_wmi_send_scan_start_cmd(). > > if (arg->num_ssids) { > ssid = ptr; > for (i = 0; i < arg->num_ssids; ++i) { > ssid->ssid_len = cpu_to_le32(arg->ssid[i].ssid_len); > memcpy(ssid->ssid, arg->ssid[i].ssid, > arg->ssid[i].ssid_len); > ssid++; > } > } > > > Firmware team needs to check the "ssid->ssid"🙂 thanks! > > 2. add network config in wpa_supplicant.conf like: > > network={ > ssid="Holman-6G" > psk="1234567890" > scan_ssid=1 > key_mgmt=SAE > disabled=0 > } > > ideally, you will see wpa_supplicant logs like: > wls1: nl80211: New scan results available > nl80211: Scan probed for SSID 'Holman-6G' > nl80211: Scan probed for SSID '' > > Step 2 is necessary because we won't send probe req to these hidden AP > unless it is configured in wpa_supplicant. > > There may be slight differences in the wpa_supplicant configuration, > please make changes according to your AP's configuration. Well, I've got some good news to report! The patch series listed at: https://lore.kernel.org/linux-wireless/20250530035615.3178480-1-rameshkumar.sundaram@oss.qualcomm.com/T/#t Fixes my issue. I can see the single 6 Ghz network as well as connect to the 6 Ghz network that is part of the multi-band "Holman" network. I didn't get an MLO connection using the ath-pending tag from 5/21, but this is really good progress. Now if we could only get that series back-ported to stable. -Walt ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ath12k: No 6GHz Wireless found 2025-04-02 2:48 ` Kang Yang 2025-04-02 17:48 ` Walt Holman @ 2025-04-02 17:50 ` Walt Holman 1 sibling, 0 replies; 32+ messages in thread From: Walt Holman @ 2025-04-02 17:50 UTC (permalink / raw) To: Kang Yang; +Cc: Jeff Johnson, linux-wireless, ath12k@lists.infradead.org Almost forgot. I've been running Kubuntu 24.10 until recently and am now running the Beta of Kubuntu 25.04, which is the most recent version available. My wpa_supplicant is built with 6Ghz support as I'm running this OS on my other machines and both of them can connect to my 6Ghz network. They are using different chipsets of course. -Walt On Tue, Apr 1, 2025 at 9:48 PM Kang Yang <quic_kangyang@quicinc.com> wrote: > > > > On 4/2/2025 5:21 AM, Walt Holman wrote: > > On Tue, Apr 1, 2025 at 1:53 PM Jeff Johnson > > <jeff.johnson@oss.qualcomm.com> wrote: > >> > >> On 3/30/2025 7:28 AM, Walt Holman wrote: > >>> Hello, > >>> > >>> I have a wcn7850 hw2.0 based m.2 wireless card in my laptop and am > >>> unable to see or connect to 6Ghz networks. I have an ASUS BE30000 wifi > >>> router setup with a separate 6ghz only network, which my phone and > >>> other laptops can connect to. I'm unable to even see this network on > >>> this particular laptop. Months ago (maybe September), I could see it > >>> occasionally, but now it never shows up. I'm using firmware from > >>> git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git > >>> and track the kernels pretty closely. I'm currently running 6.14.0 > >>> built from source. Any suggestions? Some HW info is below: > >>> > >>> 63:00.0 Network controller: Qualcomm Technologies, Inc WCN785x Wi-Fi > >>> 7(802.11be) 320MHz 2x2 [FastConnect 7800 > >>> ] (rev 01) > >>> Subsystem: Quectel Wireless Solutions Co., Ltd. Device 8000 > >>> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- > >>> ParErr- Stepping- SERR- FastB2B- DisINTx+ > >>> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort+ > >>> <TAbort- <MAbort- >SERR- <PERR- INTx- > >>> Latency: 0, Cache Line Size: 64 bytes > >>> Interrupt: pin ? routed to IRQ 111 > >>> IOMMU group: 19 > >>> Region 0: Memory at dd800000 (64-bit, non-prefetchable) [size=2M] > >>> Capabilities: [40] Power Management version 3 > >>> Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA > >>> PME(D0+,D1-,D2-,D3hot+,D3cold+) > >>> Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- > >>> Capabilities: [50] MSI: Enable+ Count=16/32 Maskable+ 64bit- > >>> Address: fee00000 Data: 0000 > >>> Masking: ffff8000 Pending: 00000000 > >>> Capabilities: [70] Express (v2) Endpoint, IntMsgNum 0 > >>> DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s > >>> unlimited, L1 unlimited > >>> ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- > >>> SlotPowerLimit 75W TEE-IO- > >>> DevCtl: CorrErr+ NonFatalErr+ FatalErr+ UnsupReq+ > >>> RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ > >>> MaxPayload 128 bytes, MaxReadReq 512 bytes > >>> DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- > >>> AuxPwr+ TransPend- > >>> LnkCap: Port #0, Speed 8GT/s, Width x2, ASPM L0s L1, > >>> Exit Latency L0s <1us, L1 <64us > >>> ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+ > >>> LnkCtl: ASPM L1 Enabled; RCB 64 bytes, LnkDisable- CommClk+ > >>> ExtSynch+ ClockPM- AutWidDis- BWInt- AutBWInt- > >>> LnkSta: Speed 8GT/s, Width x1 (downgraded) > >>> TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- > >>> DevCap2: Completion Timeout: Range ABCD, TimeoutDis+ > >>> NROPrPrP- LTR+ > >>> 10BitTagComp- 10BitTagReq- OBFF Not Supported, > >>> ExtFmt- EETLPPrefix- > >>> EmergencyPowerReduction Not Supported, > >>> EmergencyPowerReductionInit- > >>> FRS- TPHComp+ ExtTPHComp- > >>> AtomicOpsCap: 32bit- 64bit- 128bitCAS- > >>> DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- > >>> AtomicOpsCtl: ReqEn- > >>> IDOReq- IDOCompl- LTR+ EmergencyPowerReductionReq- > >>> 10BitTagReq- OBFF Disabled, EETLPPrefixBlk- > >>> LnkCap2: Supported Link Speeds: 2.5-8GT/s, Crosslink- > >>> Retimer- 2Retimers- DRS- > >>> LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis- > >>> Transmit Margin: Normal Operating Range, > >>> EnterModifiedCompliance- ComplianceSOS- > >>> Compliance Preset/De-emphasis: -6dB > >>> de-emphasis, 0dB preshoot > >>> LnkSta2: Current De-emphasis Level: -3.5dB, > >>> EqualizationComplete+ EqualizationPhase1+ > >>> EqualizationPhase2+ EqualizationPhase3+ > >>> LinkEqualizationRequest- > >>> Retimer- 2Retimers- CrosslinkRes: unsupported > >>> Capabilities: [100 v2] Advanced Error Reporting > >>> UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- > >>> UnxCmplt- RxOF- MalfTLP- > >>> ECRC- UnsupReq- ACSViol- UncorrIntErr- > >>> BlockedTLP- AtomicOpBlocked- TLPBlockedErr- > >>> PoisonTLPBlocked- DMWrReqBlocked- IDECheck- > >>> MisIDETLP- PCRC_CHECK- TLPXlatBlocked- > >>> UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- > >>> UnxCmplt- RxOF- MalfTLP- > >>> ECRC- UnsupReq- ACSViol- UncorrIntErr+ > >>> BlockedTLP- AtomicOpBlocked- TLPBlockedErr- > >>> PoisonTLPBlocked- DMWrReqBlocked- IDECheck- > >>> MisIDETLP- PCRC_CHECK- TLPXlatBlocked- > >>> UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- > >>> UnxCmplt- RxOF+ MalfTLP+ > >>> ECRC- UnsupReq- ACSViol- UncorrIntErr+ > >>> BlockedTLP- AtomicOpBlocked- TLPBlockedErr- > >>> PoisonTLPBlocked- DMWrReqBlocked- IDECheck- > >>> MisIDETLP- PCRC_CHECK- TLPXlatBlocked- > >>> CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- > >>> AdvNonFatalErr- CorrIntErr- HeaderOF- > >>> CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- > >>> AdvNonFatalErr+ CorrIntErr+ HeaderOF+ > >>> AERCap: First Error Pointer: 00, ECRCGenCap+ ECRCGenEn- > >>> ECRCChkCap+ ECRCChkEn- > >>> MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap- > >>> HeaderLog: 00000000 00000000 00000000 00000000 > >>> Capabilities: [148 v1] Secondary PCI Express > >>> LnkCtl3: LnkEquIntrruptEn- PerformEqu- > >>> LaneErrStat: 0 > >>> Capabilities: [158 v1] Transaction Processing Hints > >>> No steering table available > >>> Capabilities: [1e4 v1] Latency Tolerance Reporting > >>> Max snoop latency: 1048576ns > >>> Max no snoop latency: 1048576ns > >>> Capabilities: [1ec v1] L1 PM Substates > >>> L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ > >>> ASPM_L1.1+ L1_PM_Substates+ > >>> PortCommonModeRestoreTime=70us PortTPowerOnTime=0us > >>> L1SubCtl1: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ > >>> T_CommonMode=0us LTR1.2_Threshold=166912ns > >>> L1SubCtl2: T_PwrOn=90us > >>> Kernel driver in use: ath12k_pci > >>> Kernel modules: ath12k > >>> > >>> root@walt-ROG-zephyrus:~# iw reg get > >>> global > >>> country US: DFS-FCC > >>> (902 - 904 @ 2), (N/A, 30), (N/A) > >>> (904 - 920 @ 16), (N/A, 30), (N/A) > >>> (920 - 928 @ 8), (N/A, 30), (N/A) > >>> (2400 - 2472 @ 40), (N/A, 30), (N/A) > >>> (5150 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW > >>> (5250 - 5350 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW > >>> (5470 - 5730 @ 160), (N/A, 24), (0 ms), DFS > >>> (5730 - 5850 @ 80), (N/A, 30), (N/A), AUTO-BW > >>> (5850 - 5895 @ 40), (N/A, 27), (N/A), NO-OUTDOOR, AUTO-BW, PASSIVE-SCAN > >>> (5925 - 7125 @ 320), (N/A, 12), (N/A), NO-OUTDOOR, PASSIVE-SCAN > >>> (57240 - 71000 @ 2160), (N/A, 40), (N/A) > >>> > >>> phy#0 (self-managed) > >>> country na: DFS-UNSET > >>> (2402 - 2472 @ 40), (N/A, 20), (N/A) > >>> (2457 - 2482 @ 20), (N/A, 20), (N/A), PASSIVE-SCAN > >>> (5170 - 5330 @ 160), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN > >>> (5490 - 5730 @ 160), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN > >>> (5735 - 5895 @ 160), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN > >>> (5945 - 7125 @ 320), (N/A, 30), (N/A), AUTO-BW, PASSIVE-SCAN > >>> > >> > >> I added the ath12k list to make sure this has the proper attention. > >> Since you are building from source, can you please test with the following patch: > >> https://msgid.link/20250401020840.357-1-quic_kangyang@quicinc.com > >> > >> This is in my pending queue. > >> > >> /jeff > >> > > > > Hi Jeff, > > > > No dice on the 6Ghz networks. It fixed up the registration info, but I > > still don't see any 6Ghz networks. Even from an 'iw wlp99s0 scan' > > > > global > > country US: DFS-FCC > > (902 - 904 @ 2), (N/A, 30), (N/A) > > (904 - 920 @ 16), (N/A, 30), (N/A) > > (920 - 928 @ 8), (N/A, 30), (N/A) > > (2400 - 2472 @ 40), (N/A, 30), (N/A) > > (5150 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW > > (5250 - 5350 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW > > (5470 - 5730 @ 160), (N/A, 24), (0 ms), DFS > > (5730 - 5850 @ 80), (N/A, 30), (N/A), AUTO-BW > > (5850 - 5895 @ 40), (N/A, 27), (N/A), NO-OUTDOOR, AUTO-BW, PASSIVE-SCAN > > (5925 - 7125 @ 320), (N/A, 12), (N/A), NO-OUTDOOR, PASSIVE-SCAN > > (57240 - 71000 @ 2160), (N/A, 40), (N/A) > > > > phy#0 (self-managed) > > country US: DFS-FCC > > (2402 - 2472 @ 40), (6, 30), (N/A) > > (5170 - 5250 @ 80), (6, 24), (N/A), AUTO-BW > > (5250 - 5330 @ 80), (6, 24), (0 ms), DFS, AUTO-BW > > (5490 - 5730 @ 160), (6, 24), (0 ms), DFS, AUTO-BW > > (5735 - 5855 @ 80), (6, 30), (N/A), AUTO-BW > > (5855 - 5925 @ 40), (6, 30), (N/A), NO-OUTDOOR, AUTO-BW > > (5925 - 7125 @ 320), (N/A, 30), (N/A), NO-OUTDOOR, AUTO-BW > > > > > > Test on 6.14.0-rc5-wt-ath+, with the firmware you used. > I can get 6 GHz AP and connect to it. > > ath12k_pci 0000:03:00.0: fw_version 0x100301e1 fw_build_timestamp > 2023-12-06 04:05 fw_build_id > QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3 > > yk@yk-Mayan:~$ sudo iw wls1 scan | tee iw_scan.log: > BSS 62:03:7f:12:64:64(on wls1) -- associated > TSF: 606308271476 usec (7d, 00:25:08) > freq: 6275 > beacon interval: 100 TUs > capability: ESS Privacy SpectrumMgmt ShortSlotTime (0x0511) > signal: -17.00 dBm > last seen: 52 ms ago > Information elements from Probe Response frame: > SSID: MLO-KANG-6G > and other 6 GHz APs: > SSID: 6G-gxia > SSID: NETGEAR97-6G > …… > > > kernel log: > [88158.033218] wls1: Inserted STA 62:03:7f:12:64:64 > [88158.033232] wls1: authenticate with 62:03:7f:12:64:64 (local > address=00:03:7f:37:12:54) > [88158.033242] wls1: send auth to 62:03:7f:12:64:64 (try 1/3) > [88158.041895] wls1: authenticated > [88158.041914] wls1: moving STA 62:03:7f:12:64:64 to state 2 > [88158.044291] wls1: determined local STA to be EHT, BW limited to 320 MHz > [88158.045719] wls1: associate with 62:03:7f:12:64:64 (try 1/3) > [88158.067045] wls1: RX AssocResp from 62:03:7f:12:64:64 (capab=0x511 > status=0 aid=4) > [88158.089090] wls1: associated > > I can even connect to it by Ubuntu GUI. > > Can you update to 6.14.0-rc5-wt-ath+ and have a retry? Also please make > sure that your wpa_supplicant/iw support 6 GHz(or directly update to the > latest version). > > If you still cannot find 6 GHz AP, you can set debug_mask to 0xffffffff > to get ath12k logs. Then give it to us. > > > > -Walt > > > ^ permalink raw reply [flat|nested] 32+ messages in thread
![[-- Attachment #3: wifi-screen3.png --] [-- Type: image/png, Size: 431446 bytes --]](../../CAMb39_=G_TEL1pbeF_PAZLQh-JOFcncSfqZChPmEj63NjsEOLA@mail.gmail.com/3-wifi-screen3.png){kind=link}
![[-- Attachment #4: wifi-screen2.png --] [-- Type: image/png, Size: 439271 bytes --]](../../CAMb39_=G_TEL1pbeF_PAZLQh-JOFcncSfqZChPmEj63NjsEOLA@mail.gmail.com/4-wifi-screen2.png){kind=link}
![[-- Attachment #5: wifi-screen1.png --] [-- Type: image/png, Size: 421902 bytes --]](../../CAMb39_=G_TEL1pbeF_PAZLQh-JOFcncSfqZChPmEj63NjsEOLA@mail.gmail.com/5-wifi-screen1.png){kind=link}
end of thread, other threads:[~2025-05-30 21:37 UTC | newest]
Thread overview: 32+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <CAMb39_ngQs8=FUML5QXMh2RmEZBZ2NwUHefhGoTkGtHat+KWJA@mail.gmail.com>
2025-04-01 18:53 ` ath12k: No 6GHz Wireless found Jeff Johnson
2025-04-01 21:21 ` Walt Holman
2025-04-02 2:48 ` Kang Yang
2025-04-02 17:48 ` Walt Holman
2025-04-03 8:19 ` Kang Yang
2025-04-03 16:04 ` Walt Holman
2025-04-07 1:57 ` Kang Yang
2025-04-07 17:49 ` Walt Holman
2025-04-08 9:16 ` Kang Yang
2025-04-09 19:37 ` Walt Holman
2025-04-10 8:26 ` Kang Yang
2025-04-10 15:32 ` Walt Holman
2025-04-15 21:23 ` Walt Holman
2025-04-18 21:18 ` Walt Holman
2025-04-20 15:18 ` Walt Holman
2025-05-02 7:02 ` ath12k-firmware: Module no longer loads with current git firmware Walt Holman
2025-05-06 10:54 ` Baochen Qiang
2025-05-15 8:12 ` ath12k: No 6GHz Wireless found Kang Yang
2025-05-15 9:22 ` Kang Yang
2025-05-15 17:47 ` Walt Holman
2025-05-15 18:20 ` Jeff Johnson
2025-05-15 18:57 ` Walt Holman
2025-05-16 3:06 ` Kang Yang
2025-05-16 18:09 ` Walt Holman
2025-05-21 5:05 ` Walt Holman
2025-05-21 6:06 ` Kang Yang
2025-05-22 17:48 ` Walt Holman
2025-05-23 2:12 ` Kang Yang
2025-05-27 21:03 ` Walt Holman
2025-05-29 8:24 ` Kang Yang
2025-05-30 21:34 ` Walt Holman
2025-04-02 17:50 ` Walt Holman
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox