On Apr 11 2023, at 3:07 am, Greenman, Gregory <gregory.greenman@xxxxxxxxx> wrote: > On Mon, 2023-04-10 at 15:45 -0600, Aaron Dewell wrote: >> To summarize up to now and reboot the discussion: >> >> I have installed firmware-git. This is the file that was extracted >> into /lib/firmware: >> -rw-r--r-- 1 root root 429469981 Apr 2 10:47 linux-firmware-iwlwifi-fw-2023-03-30.tar.gz >> >> The card is not successfully initialized by the stock (6.1.20) kernel: >> [ 2.284183] Intel(R) Wireless WiFi driver for Linux >> [ 2.284221] cryptd: max_cpu_qlen set to 1000 >> [ 2.284223] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002) >> [ 2.286133] iwlwifi: No config found for PCI dev 7af0/1692, >> rev=0x430, rfid=0x3010d000 >> [ 2.286155] iwlwifi: probe of 0000:00:14.3 failed with error -22 >> >> The distribution is Debian Bookworm (testing), which has kernel: >> Linux shrub 6.1.0-7-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.20-1 >> (2023-03-19) x86_64 GNU/Linux >> >> The card identifies as 0x7AF0, 0x1692: >> 00:14.3 Network controller [0280]: Intel Corporation Alder Lake-S PCH >> CNVi WiFi [8086:7af0] (rev 11) >> Subsystem: Rivet Networks Alder Lake-S PCH CNVi WiFi [1a56:1692] >> Flags: fast devsel, IRQ 18, IOMMU group 6 >> Memory at 604c124000 (64-bit, non-prefetchable) [size=16K] >> Capabilities: [c8] Power Management version 3 >> Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+ >> Capabilities: [40] Express Root Complex Integrated Endpoint, >> MSI 00 >> Capabilities: [80] MSI-X: Enable- Count=16 Masked- >> Capabilities: [100] Latency Tolerance Reporting >> Capabilities: [164] Vendor Specific Information: ID=0010 Rev=0 >> Len=014 <?> >> Kernel modules: iwlwifi >> >> Granted that I am no expert on this, but I know enough to get myself >> into trouble, which is what I proceeded to do. I believe (but could >> well be mistaken) that what is needed is a configuration line for that >> PCI ID in iwlwifi/pcie/drv.c, something like this one: >> >> IWL_DEV_INFO(0x7F70, 0x1692, iwlax411_2ax_cfg_so_gf4_a0, iwl_ax411_killer_1690i_name), >> >> My attempt was to duplicate then change the new line from 7F70 to 7AF0, >> but that was also not successful, with such errors as (clipping because >> it's rather long): >> >> [...] >> [ 3.960164] iwlwifi 0000:00:14.3: Microcode SW error detected. >> Restarting 0x0. >> [...] >> [ 3.960551] iwlwifi 0000:00:14.3: Starting mac, retry will be >> triggered anyway >> [ 3.960594] iwlwifi 0000:00:14.3: FW error in SYNC CMD ADD_STA >> [ 3.960600] Call Trace: >> [ 3.960602] <TASK> >> [ 3.960602] dump_stack_lvl+0x36/0x50 >> [ 3.960606] iwl_trans_txq_send_hcmd+0x338/0x450 [iwlwifi] >> [...] >> >> It does produce an interface but it is unusable. >> >> I assume (but I am definitely out of my depth at this point) that it is >> due to the wrong firmware being referenced by that line of code (i.e. >> it's a different firmware for 7F70 vs. 7AF0) but I also don't know what >> the correct one is, thus I'm asking here. If I'm totally on the wrong >> track, I'm fine with that too, I just want to get it working. >> >> Thanks! >> >> > Hi Aaron, > > Could you please provide the whole dmesg log? Actually, the best is to open > a bugzilla ticket (as described in [1]) and attach the log there. It's strange > that the card identifies as CNVi (meaning it's SoC - integrated), but killer > NICs should be discrete. Maybe you could also attach to the bugzilla ticket > a photo of the NIC itself with all the IDs etc that it has on it? > > [1] https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging Hi Gregory, I'll open the ticket. Thanks! It is definitely not discrete, it's integrated onto the board. Aaron
