I just got a fenvi FV-AX3000 card, which at its core uses an Intel AX200. I was getting the same log from the kernel as above with RT ucode: -110, until I did some more snooping around.
I originally plugged in the card to one of the x16 slots on my motherboard (Gigabyte Z77X-UD5H motherboard, CPU is an Intel i7-3770k), which according to the user manual for the motherboard, due to my current configuration, should now be operating with x4 lanes (8x lanes for my GPU, x4 lanes for a 1x sound card, and x4 lanes for the 1x AX200). These lanes are managed directly by the CPU as far as I can tell, per CPU and motherboard documentation. It was in this configuration that I got the RT ucode errors, and the card refused to work on Windows as well. As per comment 7, I happened to have one poorly placed 1x PCI-E slot available (right under the GPU..., blocking some airflow to it). I switched the AX200 card to this 1x slot, which is managed by the motherboard's chipset instead of the CPU, and... the card loaded: [ 33.632318] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 33.633710] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 33.637366] Intel(R) Wireless WiFi driver for Linux [ 33.637367] Copyright(c) 2003- 2015 Intel Corporation [ 33.637397] iwlwifi 0000:06:00.0: enabling device (0100 -> 0102) [ 33.643015] iwlwifi 0000:06:00.0: api flags index 2 larger than supported by driver [ 33.643021] iwlwifi 0000:06:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 68.3.35.22 [ 33.643024] iwlwifi 0000:06:00.0: Found debug destination: EXTERNAL_DRAM [ 33.643024] iwlwifi 0000:06:00.0: Found debug configuration: 0 [ 33.643197] iwlwifi 0000:06:00.0: loaded firmware version 53.c31ac674.0 cc-a0-53.ucode op_mode iwlmvm [ 33.643211] iwlwifi 0000:06:00.0: Direct firmware load for iwl-debug-yoyo.bin failed with error -2 [ 33.654918] iwlwifi 0000:06:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340 [ 33.845091] iwlwifi 0000:06:00.0: base HW address: f8:e4:e3:00:a8:8e [ 33.857641] thermal thermal_zone3: failed to read out thermal zone (-61) [ 33.857974] systemd-udevd[2525]: Using default interface naming scheme 'v245'. [ 33.858295] systemd-udevd[2525]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable. [ 33.858372] iwlwifi 0000:06:00.0 wlp6s0: renamed from wlan0 [ 33.877736] systemd-udevd[2525]: wlan0: Process 'net.sh wlp6s0 start' failed with exit code 1. [ 37.895263] wlp6s0: authenticate with c2:56:27:6e:77:44 [ 37.897414] wlp6s0: send auth to c2:56:27:6e:77:44 (try 1/3) [ 37.922976] wlp6s0: authenticated [ 37.926295] wlp6s0: associate with c2:56:27:6e:77:44 (try 1/3) [ 37.946948] wlp6s0: RX AssocResp from c2:56:27:6e:77:44 (capab=0x431 status=0 aid=2) [ 37.951616] wlp6s0: associated [ 37.964058] IPv6: ADDRCONF(NETDEV_CHANGE): wlp6s0: link becomes ready [ 76.920106] elogind-daemon[1845]: Removed session 2. [ 76.978916] elogind-daemon[1845]: Removed session 3. [ 77.529926] elogind-daemon[1845]: New session 3 of user root. [ 90.962303] elogind-daemon[1845]: Removed session 3. [ 90.971156] elogind-daemon[1845]: New session 4 of user gabriel. [ 92.317347] Bluetooth: RFCOMM TTY layer initialized [ 92.317351] Bluetooth: RFCOMM socket layer initialized [ 92.317352] Bluetooth: RFCOMM ver 1.11 [ 92.626219] usb 1-1.3: reset high-speed USB device number 5 using ehci-pci PCI-E is one of the parts of modern systems I'm less familiar with, but to me it sounds like the problem could be one of the following (or more, these are the ones I can think of): 1. Somehow either the AX200 or the surrounding electronics on the wifi card (I don't think there's much there, so I think it's just the AX200) fails to negotiate the number of lanes it needs properly. (I have another 1x card, an Asus sound card, and that negotiates fine). 2. There's a bug or a hardware defect on the AX200 preventing it from communicating properly with the CPU PCI-E controller. Like I mentioned earlier, I have another 1x PCI-E card connected to one of the ports that connects to the CPU PCI-E controller, and that one works wonderfully. 3. Maybe my CPU is old enough that there's some incompatibility between it and the AX200. Still, the motherboard x1 port works just fine (in fact, I'm submitting this over wifi using the AX200). Because I can reproduce this reliably, and can work around it, let me know what information you would need from me to debug this, if anything. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848831 Title: Intel WiFi AX200 [8086:08b1] subsystem [8086:4070] firmware loading error resulting in no wifi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntux/+bug/1848831/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
