Hello William,

Not sure if my case is related but today I rebooted laptop and wireless
connected at 2.4ghz instead of 5ghz.
I did noticed it was connected in 'ng' mode instead of 'ac'. A quick
`service netif restart` did the job and put it at 'ac'/5ghz again.

Now I'm looking for the best way to "force" connection to 'ac' and 5ghz.

Thanks,

William D Pool <rotaechoj...@gmail.com> escreveu (sábado, 15/03/2025 à(s)
18:40):

> Apologies for the late response, medical issues have been occupying my
> time.
>
>
> I went back to revisit my findings, and I think it was an error on my
> setup.
>
>
> In my /etc/rc.conf I had the 2.4ghz SSID listed, once I removed the 5G
> SSID started to be detected in the wpa_supplicant.conf. My guess is that
> the rc.conf supersedes entries in wpa_supplicant.conf
>
>
> The other settings in my rc.conf for wifi settings are:
>
> ifconfig_wlan0="mode 11n WPA SYNCDHCP"
>
> I have been trying to keep my SSID information in the wpa_supplicant.conf
> file from now on than in the rc.conf to avoid future confusion.
>
>
> That's been the main way I've been switching between the 2.4 and 5ghz
> networks. Updating the SSID in wpa_supplicant.conf and then issuing a
> /etc/rc.d/netif restart
>
>
> Thanks!
>
>
> -William
>
>
> On 3/11/25 03:06, Bjoern A. Zeeb wrote:
>
> On Sun, 9 Mar 2025, William D Pool wrote:
>
> Howdy, I finally got to testing the following URLs against my Framework 16
> laptop with Intel AX210 wifi card. Thanks for the hard work!
>
> ...
>
> The first link change works with 2.4ghz, but not on 5ghz; I just changed
> the SSID to my 5Ghz network and it failed, should I require more than
> picking the SSID for 5Ghz?
>
>
> Can you describe me a sequence of commands how you did/do that?
> This is the 2nd report related to that topic.
> If I can get hold of a way to reproduce it it'll make debugging a lot
> easier.
>
>
>
> compat.linuxkpi.80211.hw_crypto=1
>
> The second link change neither 2.4ghz or 5ghz work with the changes to
> /boot/loader.conf
>
> compat.linuxkpi.iwlwifi_11n_disable=0
> compat.linuxkpi.iwlwifi_disable_11ac=0
>
>
> Once you are in the state that the FW crashed you would need manual
> recovery currently still as we want to sort these issues.  So let's sort
> that first and then see again about HT/VHT.  Hope that's okay!
>
> Lots of health,
> Bjoern
>
>
> iwlwifi0@pci0:1:0:0:    class=0x028000 rev=0x1a hdr=0x00 vendor=0x8086
> device=0x2725 subvendor=0x8086 subdevi
> ce=0x0024
>   vendor     = 'Intel Corporation'
>   device     = 'Wi-Fi 6E(802.11ax) AX210/AX1675* 2x2 [Typhoon Peak]'
>   class      = network
>
> ***** messages ******
>
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: <iwlwifi> mem
> 0x90b00000-0x90b03fff at device 0.0 on pci1
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: Detected crf-id 0x400410,
> cnv-id 0x400410 wfpm id 0x80000000
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: PCI dev 2725/0024, rev=0x420,
> rfid=0x10d000
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: Detected Intel(R) Wi-Fi 6 AX210
> 160MHz
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: successfully loaded firmware
> image 'iwlwifi-ty-a0-gf-a0-89.ucode'
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: TLV_FW_FSEQ_VERSION: FSEQ
> Version: 0.0.2.42
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: loaded firmware version
> 89.6b44fa0b.0 ty-a0-gf-a0-89.ucode op_mode
> iwlmvm
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: WFPM_UMAC_PD_NOTIFICATION: 0x20
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: WFPM_LMAC2_PD_NOTIFICATION:
> 0x1f
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: WFPM_AUTH_KEY_0: 0x90
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: CNVI_SCU_SEQ_DATA_DW9: 0x0
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: successfully loaded firmware
> image 'iwlwifi-ty-a0-gf-a0.pnvm'
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: loaded PNVM version 181407b3
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: Detected RF GF, rfid=0x10d000
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: base HW address:
> 5c:b2:6d:8c:3b:ce
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: WFPM_UMAC_PD_NOTIFICATION: 0x20
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: WFPM_LMAC2_PD_NOTIFICATION:
> 0x1f
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: WFPM_AUTH_KEY_0: 0x90
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: CNVI_SCU_SEQ_DATA_DW9: 0x0
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: Microcode SW error detected.
> Restarting 0x0.
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: Start IWL Error Log Dump:
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: Transport status: 0x0000004B,
> valid: 6
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: Loaded firmware version:
> 89.6b44fa0b.0 ty-a0-gf-a0-89.ucode
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x00000071 |
> NMI_INTERRUPT_UMAC_FATAL
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x000002F0 | trm_hw_status0
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x00000000 | trm_hw_status1
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x004DACF8 | branchlink2
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x004D091A | interruptlink1
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x004D091A | interruptlink2
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x000144A8 | data1
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x00000010 | data2
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x00000000 | data3
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x0000FA72 | beacon time
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x2CA60723 | tsf low
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x000000CC | tsf hi
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x00000000 | time gp1
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x00388D02 | time gp2
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x00000001 | uCode revision
> type
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x00000059 | uCode version
> major
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x6B44FA0B | uCode version
> minor
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x00000420 | hw version
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x00C80002 | board version
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x80E9FF00 | hcmd
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x00020000 | isr0
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x60000000 | isr1
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x48F00002 | isr2
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x00C3001C | isr3
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x00200000 | isr4
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x00330103 | last cmd Id
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x000144A8 | wait_event
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x00000583 | l2p_control
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x00000020 | l2p_duration
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x00000003 | l2p_mhvalid
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x00001800 | l2p_addr_match
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x00000009 | lmpm_pmg_sel
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x00000000 | timestamp
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x00007898 | flow_handler
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: Start IWL Error Log Dump:
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: Transport status: 0x0000004B,
> valid: 7
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x20101A27 | ADVANCED_SYSASSERT
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x00000000 | umac branchlink1
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x804838BE | umac branchlink2
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x0106B1B4 | umac
> interruptlink1
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x00000000 | umac
> interruptlink2
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x00010000 | umac data1
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x00000000 | umac data2
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0xDEADBEEF | umac data3
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x00000059 | umac major
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x6B44FA0B | umac minor
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x00388CFC | frame pointer
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0xC0886BAC | stack pointer
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x0037050F | last host cmd
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x00000000 | isr status reg
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: IML/ROM dump:
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x00000B03 | IML/ROM
> error/state
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x00008DF6 | IML/ROM data1
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x00000090 | IML/ROM
> WFPM_AUTH_KEY_0
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: Fseq Registers:
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x60000000 | FSEQ_ERROR_CODE
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x80440007 |
> FSEQ_TOP_INIT_VERSION
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x00080009 |
> FSEQ_CNVIO_INIT_VERSION
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x0000A652 | FSEQ_OTP_VERSION
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x00000002 |
> FSEQ_TOP_CONTENT_VERSION
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x4552414E | FSEQ_ALIVE_TOKEN
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x00400410 | FSEQ_CNVI_ID
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x00400410 | FSEQ_CNVR_ID
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x00400410 | CNVI_AUX_MISC_CHIP
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x00400410 | CNVR_AUX_MISC_CHIP
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x00009061 |
> CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x00000061 |
> CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x00080009 |
> FSEQ_PREV_CNVIO_INIT_VERSION
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x00440007 |
> FSEQ_WIFI_FSEQ_VERSION
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x9205542C |
> FSEQ_BT_FSEQ_VERSION
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: 0x000000F0 |
> FSEQ_CLASS_TP_VERSION
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: UMAC CURRENT PC: 0x804a578c
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: LMAC1 CURRENT PC: 0xd0
> Mar  9 20:09:13 Bullfrog kernel: iwlwifi0: WRT: Collecting data: ini
> trigger 4 fired (delay=0ms).
>
>
> --
> -William Pool (www.tdivanagons.com)
> Framework 16 / Intel AX210 / Sennheiser BTD-600 - STABLE/14
>
>

-- 
Nuno Teixeira
FreeBSD UNIX:  <edua...@freebsd.org>   Web:  https://FreeBSD.org

Reply via email to