Re: iwx fatal firmware error on Intel Wi-Fi 6 AX200
You are welcome! Giacomo El jue., 23 abr. 2020 a las 17:00, Stefan Sperling () escribió: > On Thu, Apr 23, 2020 at 02:02:46PM +0200, Giacomo wrote: > > Hello again Stefan. > > Some good news: I set a fixed channel on the 2.4GHz Access Point (to 6) > and > > now I get a stable connection, although not constantly fast. Let's say > > average around 10mbps. > > I think those messages are related to channel settings. Every time I > select > > a different channel, I get one fatal firmware error on dmesg. But then, > no > > more. > > Thanks! > > So it seems to be related to the AP moving channels. This is indeed > something I have not yet specifically tested. I will try to reproduce it. > > Cheers, > Stefan > -- Giacomo S. http://www.giacomos.it Sincrotrone Trieste S.C.p.A. di interesse nazionale Strada Statale 14 - km 163,5 in AREA Science Park 34149 Basovizza, Trieste ITALY - 040 3758073 328 3237959
Re: iwx fatal firmware error on Intel Wi-Fi 6 AX200
On Thu, Apr 23, 2020 at 02:02:46PM +0200, Giacomo wrote: > Hello again Stefan. > Some good news: I set a fixed channel on the 2.4GHz Access Point (to 6) and > now I get a stable connection, although not constantly fast. Let's say > average around 10mbps. > I think those messages are related to channel settings. Every time I select > a different channel, I get one fatal firmware error on dmesg. But then, no > more. Thanks! So it seems to be related to the AP moving channels. This is indeed something I have not yet specifically tested. I will try to reproduce it. Cheers, Stefan
Re: iwx fatal firmware error on Intel Wi-Fi 6 AX200
Hello again Stefan. Some good news: I set a fixed channel on the 2.4GHz Access Point (to 6) and now I get a stable connection, although not constantly fast. Let's say average around 10mbps. I think those messages are related to channel settings. Every time I select a different channel, I get one fatal firmware error on dmesg. But then, no more. Additionally, this brought to my mind that I had to do the same on the 5GHz channel because on Linux I got continuous disconnections if the channel was "Auto". That's good, and I'm glad to share this piece of news. Now I'll spend some time tweaking gnome desktop to see if it can get a little bit close to what I'm used to on Linux, because it seems rather slow in comparison. If you are aware of some optimization guidelines, that would be great. Kind regards and thanks again G El jue., 23 abr. 2020 a las 12:52, Giacomo () escribió: > One more thing: what about trying tweaking the settings for the 2.4G on > the Access point? Don't know, fixed channel or something... > Are there any parameters in the driver that can be set? > > Regards > G. > > El jue., 23 abr. 2020 a las 12:50, Giacomo () > escribió: > >> Hello again >> >> >> El jue., 23 abr. 2020 a las 12:31, Stefan Sperling () >> escribió: >> >>> On Thu, Apr 23, 2020 at 12:13:09PM +0200, Giacomo wrote: >>> > Hi Stefan. Thanks for Your prompt response! >>> > Since I seem to understand firmware is taken from linux iwlwifi, my >>> idea >>> > was to understand which one(s) you picked up and how you built the >>> > package iwx-firmware-20191022p0. >>> > Maybe worth trying with some other .ucode in there.. don't know, just >>> > guessing. >>> > I am not an expert >>> >>> Just dropping in another firmware won't magically fix anything. >>> Firmware and driver need to be in sync for things to work. >>> >>> >> I understand >> >> >>> I picked the lowest FW version (46) the device supports because >>> this means the least amount of changes had to be made relative >>> to iwm(4) code (the iwx driver code was derived from iwm). >>> >>> > What do you mean by specific environment? >>> > It is a PCI-E card installed on my desktop. Yesterday I did a fresh >>> > snapshot of 6.7 installation and configured the card with WPA2. >>> > Even before configuring it and being able to connect to the network >>> > (stuttering) dmesg frequently printed that message related to "SCAN". >>> >>> Sounds like you have 'ifconfig iwx0 debug' enabled? >>> >> >> Not that I am aware of :-) >> Never typed any debug on the command line, nor in /etc/hostname.iwx0 >> If in case, how to check it is enabled? >> >> >>> I don't see why SCAN messages would appear otherwise. >>> >> >> Actually, my mistake. SOME OF the dmesg messages ended with a reference >> to SCAN, probably prior to connect to the wpa. >> AS you can see from my initial message, in the attached dmesg there is no >> reference to SCAN. >> >> >>> >>> Frequent printing to dmesg can interfere with regular operation. >>> Please only enable 'debug' if really needed. >>> >>> > I tried to measure the speed as soon as I got a desktop working, and it >>> > goes from some hundred to 800/900 Kbits per second. >>> > Probably this very slow rate has to do with unlucky firmware and >>> continuous >>> > connection resets. >>> > Gmail is not able to load, for example. >>> > >>> > What is the speed you get? Is it stable? >>> >>> It is working OK for me up with up to somewhere around 20 Mbps. >>> Linux can of course drive the device to be a lot faster than that but >>> we don't support full 11n, let alone 11ac, yet. >>> >> >> Yes, I've read it in man page. 20Mbps would be good indeed, and expected >> for 802.11g. >> And yes, with linux I reach 60Mbps in 11n, or ac, don't know exactly.. >> >> Let me know if I can help somehow >> >> Kind regards, Giacomo >> >> >> >> -- >> Giacomo S. >> http://www.giacomos.it >> >> Sincrotrone Trieste S.C.p.A. di interesse nazionale >> Strada Statale 14 - km 163,5 in AREA Science Park >> 34149 Basovizza, Trieste ITALY >> - >> 040 3758073 >> 328 3237959 >> >> > > -- > Giacomo S. > http://www.giacomos.it > > Sincrotrone Trieste S.C.p.A. di interesse nazionale > Strada Statale 14 - km 163,5 in AREA Science Park > 34149 Basovizza, Trieste ITALY > - > 040 3758073 > 328 3237959 > > -- Giacomo S. http://www.giacomos.it Sincrotrone Trieste S.C.p.A. di interesse nazionale Strada Statale 14 - km 163,5 in AREA Science Park 34149 Basovizza, Trieste ITALY - 040 3758073 328 3237959
Re: iwx fatal firmware error on Intel Wi-Fi 6 AX200
One more thing: what about trying tweaking the settings for the 2.4G on the Access point? Don't know, fixed channel or something... Are there any parameters in the driver that can be set? Regards G. El jue., 23 abr. 2020 a las 12:50, Giacomo () escribió: > Hello again > > > El jue., 23 abr. 2020 a las 12:31, Stefan Sperling () > escribió: > >> On Thu, Apr 23, 2020 at 12:13:09PM +0200, Giacomo wrote: >> > Hi Stefan. Thanks for Your prompt response! >> > Since I seem to understand firmware is taken from linux iwlwifi, my idea >> > was to understand which one(s) you picked up and how you built the >> > package iwx-firmware-20191022p0. >> > Maybe worth trying with some other .ucode in there.. don't know, just >> > guessing. >> > I am not an expert >> >> Just dropping in another firmware won't magically fix anything. >> Firmware and driver need to be in sync for things to work. >> >> > I understand > > >> I picked the lowest FW version (46) the device supports because >> this means the least amount of changes had to be made relative >> to iwm(4) code (the iwx driver code was derived from iwm). >> >> > What do you mean by specific environment? >> > It is a PCI-E card installed on my desktop. Yesterday I did a fresh >> > snapshot of 6.7 installation and configured the card with WPA2. >> > Even before configuring it and being able to connect to the network >> > (stuttering) dmesg frequently printed that message related to "SCAN". >> >> Sounds like you have 'ifconfig iwx0 debug' enabled? >> > > Not that I am aware of :-) > Never typed any debug on the command line, nor in /etc/hostname.iwx0 > If in case, how to check it is enabled? > > >> I don't see why SCAN messages would appear otherwise. >> > > Actually, my mistake. SOME OF the dmesg messages ended with a reference to > SCAN, probably prior to connect to the wpa. > AS you can see from my initial message, in the attached dmesg there is no > reference to SCAN. > > >> >> Frequent printing to dmesg can interfere with regular operation. >> Please only enable 'debug' if really needed. >> >> > I tried to measure the speed as soon as I got a desktop working, and it >> > goes from some hundred to 800/900 Kbits per second. >> > Probably this very slow rate has to do with unlucky firmware and >> continuous >> > connection resets. >> > Gmail is not able to load, for example. >> > >> > What is the speed you get? Is it stable? >> >> It is working OK for me up with up to somewhere around 20 Mbps. >> Linux can of course drive the device to be a lot faster than that but >> we don't support full 11n, let alone 11ac, yet. >> > > Yes, I've read it in man page. 20Mbps would be good indeed, and expected > for 802.11g. > And yes, with linux I reach 60Mbps in 11n, or ac, don't know exactly.. > > Let me know if I can help somehow > > Kind regards, Giacomo > > > > -- > Giacomo S. > http://www.giacomos.it > > Sincrotrone Trieste S.C.p.A. di interesse nazionale > Strada Statale 14 - km 163,5 in AREA Science Park > 34149 Basovizza, Trieste ITALY > - > 040 3758073 > 328 3237959 > > -- Giacomo S. http://www.giacomos.it Sincrotrone Trieste S.C.p.A. di interesse nazionale Strada Statale 14 - km 163,5 in AREA Science Park 34149 Basovizza, Trieste ITALY - 040 3758073 328 3237959
Re: iwx fatal firmware error on Intel Wi-Fi 6 AX200
Hello again El jue., 23 abr. 2020 a las 12:31, Stefan Sperling () escribió: > On Thu, Apr 23, 2020 at 12:13:09PM +0200, Giacomo wrote: > > Hi Stefan. Thanks for Your prompt response! > > Since I seem to understand firmware is taken from linux iwlwifi, my idea > > was to understand which one(s) you picked up and how you built the > > package iwx-firmware-20191022p0. > > Maybe worth trying with some other .ucode in there.. don't know, just > > guessing. > > I am not an expert > > Just dropping in another firmware won't magically fix anything. > Firmware and driver need to be in sync for things to work. > > I understand > I picked the lowest FW version (46) the device supports because > this means the least amount of changes had to be made relative > to iwm(4) code (the iwx driver code was derived from iwm). > > > What do you mean by specific environment? > > It is a PCI-E card installed on my desktop. Yesterday I did a fresh > > snapshot of 6.7 installation and configured the card with WPA2. > > Even before configuring it and being able to connect to the network > > (stuttering) dmesg frequently printed that message related to "SCAN". > > Sounds like you have 'ifconfig iwx0 debug' enabled? > Not that I am aware of :-) Never typed any debug on the command line, nor in /etc/hostname.iwx0 If in case, how to check it is enabled? > I don't see why SCAN messages would appear otherwise. > Actually, my mistake. SOME OF the dmesg messages ended with a reference to SCAN, probably prior to connect to the wpa. AS you can see from my initial message, in the attached dmesg there is no reference to SCAN. > > Frequent printing to dmesg can interfere with regular operation. > Please only enable 'debug' if really needed. > > > I tried to measure the speed as soon as I got a desktop working, and it > > goes from some hundred to 800/900 Kbits per second. > > Probably this very slow rate has to do with unlucky firmware and > continuous > > connection resets. > > Gmail is not able to load, for example. > > > > What is the speed you get? Is it stable? > > It is working OK for me up with up to somewhere around 20 Mbps. > Linux can of course drive the device to be a lot faster than that but > we don't support full 11n, let alone 11ac, yet. > Yes, I've read it in man page. 20Mbps would be good indeed, and expected for 802.11g. And yes, with linux I reach 60Mbps in 11n, or ac, don't know exactly.. Let me know if I can help somehow Kind regards, Giacomo -- Giacomo S. http://www.giacomos.it Sincrotrone Trieste S.C.p.A. di interesse nazionale Strada Statale 14 - km 163,5 in AREA Science Park 34149 Basovizza, Trieste ITALY - 040 3758073 328 3237959
Re: iwx fatal firmware error on Intel Wi-Fi 6 AX200
On Thu, Apr 23, 2020 at 12:13:09PM +0200, Giacomo wrote: > Hi Stefan. Thanks for Your prompt response! > Since I seem to understand firmware is taken from linux iwlwifi, my idea > was to understand which one(s) you picked up and how you built the > package iwx-firmware-20191022p0. > Maybe worth trying with some other .ucode in there.. don't know, just > guessing. > I am not an expert Just dropping in another firmware won't magically fix anything. Firmware and driver need to be in sync for things to work. I picked the lowest FW version (46) the device supports because this means the least amount of changes had to be made relative to iwm(4) code (the iwx driver code was derived from iwm). > What do you mean by specific environment? > It is a PCI-E card installed on my desktop. Yesterday I did a fresh > snapshot of 6.7 installation and configured the card with WPA2. > Even before configuring it and being able to connect to the network > (stuttering) dmesg frequently printed that message related to "SCAN". Sounds like you have 'ifconfig iwx0 debug' enabled? I don't see why SCAN messages would appear otherwise. Frequent printing to dmesg can interfere with regular operation. Please only enable 'debug' if really needed. > I tried to measure the speed as soon as I got a desktop working, and it > goes from some hundred to 800/900 Kbits per second. > Probably this very slow rate has to do with unlucky firmware and continuous > connection resets. > Gmail is not able to load, for example. > > What is the speed you get? Is it stable? It is working OK for me up with up to somewhere around 20 Mbps. Linux can of course drive the device to be a lot faster than that but we don't support full 11n, let alone 11ac, yet.
Re: iwx fatal firmware error on Intel Wi-Fi 6 AX200
Hi Stefan. Thanks for Your prompt response! Since I seem to understand firmware is taken from linux iwlwifi, my idea was to understand which one(s) you picked up and how you built the package iwx-firmware-20191022p0. Maybe worth trying with some other .ucode in there.. don't know, just guessing. I am not an expert What do you mean by specific environment? It is a PCI-E card installed on my desktop. Yesterday I did a fresh snapshot of 6.7 installation and configured the card with WPA2. Even before configuring it and being able to connect to the network (stuttering) dmesg frequently printed that message related to "SCAN". I tried to measure the speed as soon as I got a desktop working, and it goes from some hundred to 800/900 Kbits per second. Probably this very slow rate has to do with unlucky firmware and continuous connection resets. Gmail is not able to load, for example. What is the speed you get? Is it stable? I wish I could help You more. Giacomo. El jue., 23 abr. 2020 a las 11:58, Stefan Sperling () escribió: > On Thu, Apr 23, 2020 at 11:05:51AM +0200, Giacomo wrote: > > Hello everyone. > > > > pcidump -v: > > > > 2:0:0: Intel Wi-Fi 6 AX200 > > 0x: Vendor ID: 8086, Product ID: 2723 > > 0x0004: Command: 0006, Status: 0010 > > 0x0008: Class: 02 Network, Subclass: 80 Miscellaneous, > > Interface: 00, Revision: 1a > > 0x000c: BIST: 00, Header Type: 00, Latency Timer: 00, > > Cache Line Size: 10 > > 0x0010: BAR mem 64bit addr: 0xf7c0/0x4000 > > 0x0018: BAR empty () > > 0x001c: BAR empty () > > 0x0020: BAR empty () > > 0x0024: BAR empty () > > 0x0028: Cardbus CIS: > > 0x002c: Subsystem Vendor ID: 8086 Product ID: 0084 > > 0x0030: Expansion ROM Base Address: > > 0x0038: > > 0x003c: Interrupt Pin: 01 Line: 0a Min Gnt: 00 Max Lat: 00 > > 0x00c8: Capability 0x01: Power Management > > State: D0 > > 0x00d0: Capability 0x05: Message Signalled Interrupts (MSI) > > Enabled: no > > 0x0040: Capability 0x10: PCI Express > > Link Speed: 5.0 / 5.0 GT/s, Link Width: x1 / x1 > > 0x0100: Enhanced Capability 0x01: Advanced Error Reporting > > 0x014c: Enhanced Capability 0x18: Latency Tolerance Reporting > > 0x0154: Enhanced Capability 0x1e: L1 PM > > 0x0080: Capability 0x11: Extended Message Signalled Interrupts (MSI-X) > > Enabled: yes; table size 16 (BAR 0:8192) > > This is a new driver and the hardware isn't very widespread yet. > So problems like this are unfortunate but somewhat expected. > > The device iwx(4) was developed with is the one shown below. > Note that the Subsystem Product ID differs (0080 vs 0084). > Whether or not this difference matters is something we cannot know without > doing tedious research since Intel provides no documentation. > > My device sees only very occasional firmware errors which don't prevent > regular usage. It's still unclear why these occur. > > Unless there is a way for me to reproduce frequent error conditions > locally there is nothing I could do to help. > Are these errors happening in a specific environment or everywhere? > > 4:0:0: Intel Wi-Fi 6 AX200 > 0x: Vendor ID: 8086, Product ID: 2723 > 0x0004: Command: 0006, Status: 0010 > 0x0008: Class: 02 Network, Subclass: 80 Miscellaneous, > Interface: 00, Revision: 1a > 0x000c: BIST: 00, Header Type: 00, Latency Timer: 00, > Cache Line Size: 10 > 0x0010: BAR mem 64bit addr: 0xf7c0/0x4000 > 0x0018: BAR empty () > 0x001c: BAR empty () > 0x0020: BAR empty () > 0x0024: BAR empty () > 0x0028: Cardbus CIS: > 0x002c: Subsystem Vendor ID: 8086 Product ID: 0080 > 0x0030: Expansion ROM Base Address: > 0x0038: > 0x003c: Interrupt Pin: 01 Line: 03 Min Gnt: 00 Max Lat: 00 > 0x00c8: Capability 0x01: Power Management > State: D0 > 0x00d0: Capability 0x05: Message Signalled Interrupts (MSI) > Enabled: no > 0x0040: Capability 0x10: PCI Express > Link Speed: 5.0 / 5.0 GT/s, Link Width: x1 / x1 > 0x0100: Enhanced Capability 0x01: Advanced Error Reporting > 0x014c: Enhanced Capability 0x18: Latency Tolerance Reporting > 0x0154: Enhanced Capability 0x1e: L1 PM > 0x0080: Capability 0x11: Extended Message Signalled Interrupts > (MSI-X) > Enabled: yes; table size 16 (BAR 0:8192) > -- Giacomo S. http://www.giacomos.it Sincrotrone Trieste S.C.p.A. di interesse nazionale Strada Statale 14 - km 163,5 in AREA Science Park 34149 Basovizza, Trieste ITALY - 040 3758073 328 3237959
Re: iwx fatal firmware error on Intel Wi-Fi 6 AX200
On Thu, Apr 23, 2020 at 11:05:51AM +0200, Giacomo wrote: > Hello everyone. > > pcidump -v: > > 2:0:0: Intel Wi-Fi 6 AX200 > 0x: Vendor ID: 8086, Product ID: 2723 > 0x0004: Command: 0006, Status: 0010 > 0x0008: Class: 02 Network, Subclass: 80 Miscellaneous, > Interface: 00, Revision: 1a > 0x000c: BIST: 00, Header Type: 00, Latency Timer: 00, > Cache Line Size: 10 > 0x0010: BAR mem 64bit addr: 0xf7c0/0x4000 > 0x0018: BAR empty () > 0x001c: BAR empty () > 0x0020: BAR empty () > 0x0024: BAR empty () > 0x0028: Cardbus CIS: > 0x002c: Subsystem Vendor ID: 8086 Product ID: 0084 > 0x0030: Expansion ROM Base Address: > 0x0038: > 0x003c: Interrupt Pin: 01 Line: 0a Min Gnt: 00 Max Lat: 00 > 0x00c8: Capability 0x01: Power Management > State: D0 > 0x00d0: Capability 0x05: Message Signalled Interrupts (MSI) > Enabled: no > 0x0040: Capability 0x10: PCI Express > Link Speed: 5.0 / 5.0 GT/s, Link Width: x1 / x1 > 0x0100: Enhanced Capability 0x01: Advanced Error Reporting > 0x014c: Enhanced Capability 0x18: Latency Tolerance Reporting > 0x0154: Enhanced Capability 0x1e: L1 PM > 0x0080: Capability 0x11: Extended Message Signalled Interrupts (MSI-X) > Enabled: yes; table size 16 (BAR 0:8192) This is a new driver and the hardware isn't very widespread yet. So problems like this are unfortunate but somewhat expected. The device iwx(4) was developed with is the one shown below. Note that the Subsystem Product ID differs (0080 vs 0084). Whether or not this difference matters is something we cannot know without doing tedious research since Intel provides no documentation. My device sees only very occasional firmware errors which don't prevent regular usage. It's still unclear why these occur. Unless there is a way for me to reproduce frequent error conditions locally there is nothing I could do to help. Are these errors happening in a specific environment or everywhere? 4:0:0: Intel Wi-Fi 6 AX200 0x: Vendor ID: 8086, Product ID: 2723 0x0004: Command: 0006, Status: 0010 0x0008: Class: 02 Network, Subclass: 80 Miscellaneous, Interface: 00, Revision: 1a 0x000c: BIST: 00, Header Type: 00, Latency Timer: 00, Cache Line Size: 10 0x0010: BAR mem 64bit addr: 0xf7c0/0x4000 0x0018: BAR empty () 0x001c: BAR empty () 0x0020: BAR empty () 0x0024: BAR empty () 0x0028: Cardbus CIS: 0x002c: Subsystem Vendor ID: 8086 Product ID: 0080 0x0030: Expansion ROM Base Address: 0x0038: 0x003c: Interrupt Pin: 01 Line: 03 Min Gnt: 00 Max Lat: 00 0x00c8: Capability 0x01: Power Management State: D0 0x00d0: Capability 0x05: Message Signalled Interrupts (MSI) Enabled: no 0x0040: Capability 0x10: PCI Express Link Speed: 5.0 / 5.0 GT/s, Link Width: x1 / x1 0x0100: Enhanced Capability 0x01: Advanced Error Reporting 0x014c: Enhanced Capability 0x18: Latency Tolerance Reporting 0x0154: Enhanced Capability 0x1e: L1 PM 0x0080: Capability 0x11: Extended Message Signalled Interrupts (MSI-X) Enabled: yes; table size 16 (BAR 0:8192)
iwx fatal firmware error on Intel Wi-Fi 6 AX200
Hello everyone. pcidump -v: 2:0:0: Intel Wi-Fi 6 AX200 0x: Vendor ID: 8086, Product ID: 2723 0x0004: Command: 0006, Status: 0010 0x0008: Class: 02 Network, Subclass: 80 Miscellaneous, Interface: 00, Revision: 1a 0x000c: BIST: 00, Header Type: 00, Latency Timer: 00, Cache Line Size: 10 0x0010: BAR mem 64bit addr: 0xf7c0/0x4000 0x0018: BAR empty () 0x001c: BAR empty () 0x0020: BAR empty () 0x0024: BAR empty () 0x0028: Cardbus CIS: 0x002c: Subsystem Vendor ID: 8086 Product ID: 0084 0x0030: Expansion ROM Base Address: 0x0038: 0x003c: Interrupt Pin: 01 Line: 0a Min Gnt: 00 Max Lat: 00 0x00c8: Capability 0x01: Power Management State: D0 0x00d0: Capability 0x05: Message Signalled Interrupts (MSI) Enabled: no 0x0040: Capability 0x10: PCI Express Link Speed: 5.0 / 5.0 GT/s, Link Width: x1 / x1 0x0100: Enhanced Capability 0x01: Advanced Error Reporting 0x014c: Enhanced Capability 0x18: Latency Tolerance Reporting 0x0154: Enhanced Capability 0x1e: L1 PM 0x0080: Capability 0x11: Extended Message Signalled Interrupts (MSI-X) Enabled: yes; table size 16 (BAR 0:8192) FIRMWARE fw_update -i Installed: inteldrm-firmware-20181218 vmm-firmware-1.11.0p2 iwx-firmware-20191022p0 intel-firmware-20191115p0v0 DMESG iwx0: dumping device error log iwx0: Start Error Log Dump: iwx0: Status: 0x1, count: 6 iwx0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL iwx0: 002022F0 | trm_hw_status0 iwx0: | trm_hw_status1 iwx0: 004FC308 | branchlink2 iwx0: 00016E5A | interruptlink1 iwx0: 00016E5A | interruptlink2 iwx0: 004F9F62 | data1 iwx0: 1000 | data2 iwx0: F008 | data3 iwx0: | beacon time iwx0: 00010996 | tsf low iwx0: | tsf hi iwx0: | time gp1 iwx0: 00010997 | time gp2 iwx0: 0001 | uCode revision type iwx0: 002E | uCode version major iwx0: 177B3E46 | uCode version minor iwx0: 0340 | hw version iwx0: 18889000 | board version iwx0: 800AFD0C | hcmd iwx0: 0002 | isr0 iwx0: | isr1 iwx0: 18F2 | isr2 iwx0: 00CC | isr3 iwx0: | isr4 iwx0: | last cmd Id iwx0: 004F9F62 | wait_event iwx0: | l2p_control iwx0: 0020 | l2p_duration iwx0: | l2p_mhvalid iwx0: | l2p_addr_match iwx0: 0009 | lmpm_pmg_sel iwx0: 19071335 | timestamp iwx0: 0828 | flow_handler iwx0: Start UMAC Error Log Dump: iwx0: Status: 0x1, count: 7 iwx0: 0x201010A3 | ADVANCED_SYSASSERT iwx0: 0x | umac branchlink1 iwx0: 0xC008B1C0 | umac branchlink2 iwx0: 0xC0084E04 | umac interruptlink1 iwx0: 0x | umac interruptlink2 iwx0: 0x0002 | umac data1 iwx0: 0x0001 | umac data2 iwx0: 0xDEADBEEF | umac data3 iwx0: 0x002E | umac major iwx0: 0x177B3E46 | umac minor iwx0: 0x00010987 | frame pointer iwx0: 0xC0886C6C | stack pointer iwx0: 0x00050C00 | last host cmd iwx0: 0x | isr status reg driver status: tx ring 0: qid=0 cur=6 queued=0 tx ring 1: qid=1 cur=0 queued=0 tx ring 2: qid=2 cur=0 queued=0 tx ring 3: qid=3 cur=0 queued=0 tx ring 4: qid=4 cur=0 queued=0 tx ring 5: qid=5 cur=0 queued=0 tx ring 6: qid=6 cur=0 queued=0 tx ring 7: qid=7 cur=0 queued=0 tx ring 8: qid=8 cur=0 queued=0 tx ring 9: qid=9 cur=0 queued=0 tx ring 10: qid=10 cur=0 queued=0 tx ring 11: qid=11 cur=0 queued=0 tx ring 12: qid=12 cur=0 queued=0 tx ring 13: qid=13 cur=0 queued=0 tx ring 14: qid=14 cur=0 queued=0 tx ring 15: qid=15 cur=0 queued=0 tx ring 16: qid=16 cur=0 queued=0 tx ring 17: qid=17 cur=0 queued=0 tx ring 18: qid=18 cur=0 queued=0 tx ring 19: qid=19 cur=0 queued=0 tx ring 20: qid=20 cur=0 queued=0 tx ring 21: qid=21 cur=0 queued=0 tx ring 22: qid=22 cur=0 queued=0 tx ring 23: qid=23 cur=0 queued=0 tx ring 24: qid=24 cur=0 queued=0 tx ring 25: qid=25 cur=0 queued=0 tx ring 26: qid=26 cur=0 queued=0 tx ring 27: qid=27 cur=0 queued=0 tx ring 28: qid=28 cur=0 queued=0 tx ring 29: qid=29 cur=0 queued=0 tx ring 30: qid=30 cur=0 queued=0 rx ring: cur=265 802.11 state INIT iwx0: fatal firmware error iwx0: hw rev 0x340, fw ver 46.393952838.0, address 84:c5:a6:00:10:ef This error appears continuously making the network unusable openbsd# uname -ar OpenBSD openbsd.home 6.7 GENERIC.MP#149 amd64 cat /etc/hostname.iwx0 nwid SetTheControls wpakey mykey dhcp openbsd# ifconfig iwx0 iwx0: flags=808843 mtu 1500 lladdr 84:c5:a6:00:10:ef index 2 priority 4 llprio 3 groups: wlan egress media: IEEE802.11 autoselect (HT-MCS5 mode 11n) status: active ieee80211: nwid SetTheControls chan 1 bssid 5c:e2:8c:7d:cd:28 56% wpakey wpaprotos wpa2 wpaakms psk wpaciphers ccmp wpagroupcipher ccmp inet 192.168.1.159 netmask 0xff00 broadcast 192.168.1.255 I have checked whether on http://firmware.openbsd.org/firmware/ there are other available versions but could not find any. If this can help, on Linux the device works properly with iwlwifi firmware versi
