Created attachment 217927 [details] boot dmesg I have an Intel 9560 on my ThinkPad X1 Carbon Gen7 and in dmesg the init fails here: iwm0: <Intel(R) Dual Band Wireless AC 9560> mem 0xea238000-0xea23bfff at device 20.3 on pci0 iwm0: fw chunk addr 0x404000 len 712 failed to load iwm0: iwm_pcie_load_section: Could not load the [0] uCode section iwm0: iwm_start_fw: failed 60 iwm0: Failed to start INIT ucode: 60 I see that some work was done in FreeBSD for the 9560 since 12.1-RELEASE, and I appreciate the efforts! I just want it to be known that while the device is actually detected this time, the firmware fails to load, so that possibly this problem can be rectified in time for the full release. I have attached a full dmesg here: https://dmesgd.nycbug.org/index.cgi?do=view&id=5669 Thanks!
None of your dmesg parts seems to be from a boot verbose. Can you please share the output of pciconf -lBbcevV iwm0
Created attachment 217935 [details] Verbose boot dmesg
I guess a verbose dmesg would be more helpful, so I've attached it here. Here's the `pciconf -lBbcevV iwm0` output: iwm0@pci0:0:20:3: class=0x028000 card=0x00308086 chip=0x9df08086 rev=0x11 hdr=0x00 vendor = 'Intel Corporation' device = 'Cannon Point-LP CNVi [Wireless-AC]' class = network bar [10] = type Memory, range 64, base rxea238000, size 16384, enabled cap 01[c8] = powerspec 3 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit cap 10[40] = PCI-Express 2 root endpoint max data 128(128) FLR RO NS cap 11[80] = MSI-X supports 16 messages, enabled Table in map 0x10[0x2000], PBA in map 0x10[0x3000] ecap 0000[100] = unknown 0 ecap 0018[14c] = LTR 1 ecap 000b[164] = Vendor 1 ID 16
Update: I booted 12.2-BETA2 today, and I noticed something VERY interesting with the wifi problem. It seems the firmware ucode load only fails if you reboot from Linux straight to FreeBSD. If I fully shut down the laptop and then boot the 12.2-BETA2 installer image, iwm0 starts up with no issues and I can even connect to wifi networks. So it seems there's only some kind of bug after a reboot from linux to freebsd now, it may be worth looking into.
Once you've power cycled and got it working in FreeBSD, does it still work after a quick reboot?
(In reply to Kyle Evans from comment #5) Yes, I forgot to mention but once I got wifi working on FreeBSD and I rebooted back to FreeBSD, everything worked just fine once again.
I've installed 12.2-BETA2 on another USB and I've noticed that while connected to wifi my speeds are barely 2 Mbit/s download and 0.21 Mbit/s upload using https://github.com/sivel/speedtest-cli, but the same tool reports 88.24 Mbit/s and 55.14 Mbit/s on the same machine running void linux, so it isn't just my internet speed. I hope I'm not coming off as complaining too much, I'd just like to help polish this stuff out through testing. I imagine certain logs/files may be helpful, but I just don't know what those would be.
(In reply to Sreehari S from comment #8) iwm(4) currently only does abg and no 11n or 11ac. We hope to rectify this with the iwlwifi port over which will also support the newer hardware from Intel before the end of the year. I'd prefer not to conflate two issues in the bug report, so let's keep this one focused on the startup issues (for whoever is going to look into that).
While also still only limited to a/b/g if you want you can give the 2nd iwlwifi snapshot a try: More here: https://lists.freebsd.org/archives/freebsd-wireless/2021-September/000068.html
Any further comments? Is my understanding that iwm(4) works on this chipset as intended and supported by iwm(4)? Did you ever try iwlwifi(4) -- also not faster yet but a possible way forward?
In case you give iwlwifi another try please let us know.