TravelMate P214-55-55BS: Is microcode for WiFi only broken on Linux? Does newer microcode exist?

Species8472
Species8472 Member Posts: 20 Troubleshooter

I expect that there is shared microcode between the Windows and Linux drivers, but perhaps I am wrong. Regardless, expect that the microcode is broken on Linux for the WiFi.

[95106.477017] iwlwifi 0000:00:14.3: missed beacons exceeds threshold, but receiving data. Stay connected, Expect bugs.
[95106.477021] iwlwifi 0000:00:14.3: missed_beacons:19, missed_beacons_since_rx:1
[96478.051953] iwlwifi 0000:00:14.3: Microcode SW error detected. Restarting 0x0.
[96478.052057] iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
[96478.052058] iwlwifi 0000:00:14.3: Transport status: 0x0000004A, valid: 6
[96478.052059] iwlwifi 0000:00:14.3: Loaded firmware version: 89.6b44fa0b.0 so-a0-gf-a0-89.ucode
[96478.052060] iwlwifi 0000:00:14.3: 0x000010BA | ADVANCED_SYSASSERT           
[96478.052061] iwlwifi 0000:00:14.3: 0x00A002F0 | trm_hw_status0
[96478.052062] iwlwifi 0000:00:14.3: 0x00000000 | trm_hw_status1
[96478.052063] iwlwifi 0000:00:14.3: 0x004D9CBC | branchlink2
[96478.052063] iwlwifi 0000:00:14.3: 0x004CF826 | interruptlink1
[96478.052064] iwlwifi 0000:00:14.3: 0x004CF826 | interruptlink2
[96478.052065] iwlwifi 0000:00:14.3: 0x000005D4 | data1
[96478.052065] iwlwifi 0000:00:14.3: 0x000005D4 | data2
[96478.052066] iwlwifi 0000:00:14.3: 0xDEADBEEF | data3
[96478.052066] iwlwifi 0000:00:14.3: 0x2200932C | beacon time
[96478.052067] iwlwifi 0000:00:14.3: 0x2561B547 | tsf low
[96478.052067] iwlwifi 0000:00:14.3: 0x00000001 | tsf hi
[96478.052068] iwlwifi 0000:00:14.3: 0x00000000 | time gp1
[96478.052069] iwlwifi 0000:00:14.3: 0x6D0C200D | time gp2
[96478.052069] iwlwifi 0000:00:14.3: 0x00000001 | uCode revision type
[96478.052070] iwlwifi 0000:00:14.3: 0x00000059 | uCode version major
[96478.052070] iwlwifi 0000:00:14.3: 0x6B44FA0B | uCode version minor
[96478.052071] iwlwifi 0000:00:14.3: 0x00000370 | hw version
[96478.052072] iwlwifi 0000:00:14.3: 0x40C80002 | board version
[96478.052072] iwlwifi 0000:00:14.3: 0x02C3001C | hcmd
[96478.052073] iwlwifi 0000:00:14.3: 0x02220000 | isr0
[96478.052073] iwlwifi 0000:00:14.3: 0x00400000 | isr1
[96478.052074] iwlwifi 0000:00:14.3: 0x48F00002 | isr2
[96478.052074] iwlwifi 0000:00:14.3: 0x04C3029E | isr3
[96478.052075] iwlwifi 0000:00:14.3: 0x00200000 | isr4
[96478.052080] iwlwifi 0000:00:14.3: 0x02C2001C | last cmd Id
[96478.052081] iwlwifi 0000:00:14.3: 0x00013E68 | wait_event
[96478.052081] iwlwifi 0000:00:14.3: 0x000000D4 | l2p_control
[96478.052082] iwlwifi 0000:00:14.3: 0x00000020 | l2p_duration
[96478.052082] iwlwifi 0000:00:14.3: 0x00000007 | l2p_mhvalid
[96478.052083] iwlwifi 0000:00:14.3: 0x00810048 | l2p_addr_match
[96478.052084] iwlwifi 0000:00:14.3: 0x00000009 | lmpm_pmg_sel
[96478.052084] iwlwifi 0000:00:14.3: 0x00000000 | timestamp
[96478.052085] iwlwifi 0000:00:14.3: 0x0000B880 | flow_handler
[96478.052132] iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
[96478.052133] iwlwifi 0000:00:14.3: Transport status: 0x0000004A, valid: 7
[96478.052133] iwlwifi 0000:00:14.3: 0x20000070 | NMI_INTERRUPT_LMAC_FATAL
[96478.052134] iwlwifi 0000:00:14.3: 0x00000000 | umac branchlink1
[96478.052135] iwlwifi 0000:00:14.3: 0x8048829A | umac branchlink2
[96478.052135] iwlwifi 0000:00:14.3: 0x804AC43A | umac interruptlink1
[96478.052136] iwlwifi 0000:00:14.3: 0x804AC43A | umac interruptlink2
[96478.052137] iwlwifi 0000:00:14.3: 0x00000002 | umac data1
[96478.052137] iwlwifi 0000:00:14.3: 0x804AC43A | umac data2
[96478.052138] iwlwifi 0000:00:14.3: 0x00000000 | umac data3
[96478.052138] iwlwifi 0000:00:14.3: 0x00000059 | umac major
[96478.052139] iwlwifi 0000:00:14.3: 0x6B44FA0B | umac minor
[96478.052139] iwlwifi 0000:00:14.3: 0x6D0C203F | frame pointer
[96478.052140] iwlwifi 0000:00:14.3: 0xC0886258 | stack pointer
[96478.052141] iwlwifi 0000:00:14.3: 0x005C010D | last host cmd
[96478.052141] iwlwifi 0000:00:14.3: 0x00000000 | isr status reg
[96478.052183] iwlwifi 0000:00:14.3: IML/ROM dump:
[96478.052184] iwlwifi 0000:00:14.3: 0x00000B03 | IML/ROM error/state
[96478.052192] iwlwifi 0000:00:14.3: 0x00008720 | IML/ROM data1
[96478.052200] iwlwifi 0000:00:14.3: 0x00000090 | IML/ROM WFPM_AUTH_KEY_0
[96478.052205] iwlwifi 0000:00:14.3: Fseq Registers:
[96478.052207] iwlwifi 0000:00:14.3: 0x60000000 | FSEQ_ERROR_CODE
[96478.052210] iwlwifi 0000:00:14.3: 0x803E0003 | FSEQ_TOP_INIT_VERSION
[96478.052212] iwlwifi 0000:00:14.3: 0x00190004 | FSEQ_CNVIO_INIT_VERSION
[96478.052215] iwlwifi 0000:00:14.3: 0x0000A652 | FSEQ_OTP_VERSION
[96478.052217] iwlwifi 0000:00:14.3: 0x00000003 | FSEQ_TOP_CONTENT_VERSION
[96478.052220] iwlwifi 0000:00:14.3: 0x4552414E | FSEQ_ALIVE_TOKEN
[96478.052222] iwlwifi 0000:00:14.3: 0x00080400 | FSEQ_CNVI_ID
[96478.052225] iwlwifi 0000:00:14.3: 0x00400410 | FSEQ_CNVR_ID
[96478.052227] iwlwifi 0000:00:14.3: 0x00080400 | CNVI_AUX_MISC_CHIP
[96478.052231] iwlwifi 0000:00:14.3: 0x00400410 | CNVR_AUX_MISC_CHIP
[96478.052236] iwlwifi 0000:00:14.3: 0x00009061 | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[96478.052241] iwlwifi 0000:00:14.3: 0x00000061 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[96478.052243] iwlwifi 0000:00:14.3: 0x00190004 | FSEQ_PREV_CNVIO_INIT_VERSION
[96478.052246] iwlwifi 0000:00:14.3: 0x003E0003 | FSEQ_WIFI_FSEQ_VERSION
[96478.052248] iwlwifi 0000:00:14.3: 0x003E0003 | FSEQ_BT_FSEQ_VERSION
[96478.052250] iwlwifi 0000:00:14.3: 0x000000DC | FSEQ_CLASS_TP_VERSION
[96478.052258] iwlwifi 0000:00:14.3: UMAC CURRENT PC: 0x804abef8
[96478.052261] iwlwifi 0000:00:14.3: LMAC1 CURRENT PC: 0xd0
[96478.052490] iwlwifi 0000:00:14.3: WRT: Collecting data: ini trigger 4 fired (delay=0ms).
[96478.052492] ieee80211 phy0: Hardware restart was requested
[96478.709348] iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x20
[96478.709359] iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[96478.709367] iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90
[96478.709375] iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x0
[96478.710596] iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 4

Answers

  • AnhEZ28
    AnhEZ28 ACE, Member Posts: 4,464 Pathfinder

    @Species8472

    You can try to check the model name of the Wi-Fi card in Windows to see if it is supported by Linux.

    Please remember to include @AnhEZ28 when you want to reply back to my comment so that I can check your response.
    Thank you and have a nice day!
  • billsey
    billsey ACE Posts: 34,645 Trailblazer

    I believe the WLAN card on those models are the AX211 WiFi 6E types. They use the CNVio2 protocol over the M.2 slot, so use different drivers than the AX210 equivalents. They should be well supported in Linux, since they have been out for quite a while. You may need a specific kernel though.

    Click on "Like" if you find my answer useful or click on "Yes" if it answers your question.
  • Species8472
    Species8472 Member Posts: 20 Troubleshooter

    I think the intention is that they are well supported, but I think there is just a bug. No doubt Intel crawls the web for bug reports (and if they don't they should start doing that).

    The card sort of works (I am using it to send this message), but clearly the error states that there is a bug in its microcode.

  • billsey
    billsey ACE Posts: 34,645 Trailblazer

    I doubt if Intel crawls the web looking for bug reports. They work directly with the system manufacturers that use the cards and with their own reporting system. I expect they have a generic driver for Linux and the various flavors have to modify that for their releases. Go to the developers of the Linux flavor you are using and ask them to see if they have seen this…

    Click on "Like" if you find my answer useful or click on "Yes" if it answers your question.
  • Species8472
    Species8472 Member Posts: 20 Troubleshooter

    The only place this will be resolved is at Intel. I doubt the microcode is open-source.

    People at kernel.org might know a few things, but ultimately it's proprietary knowledge as to why it doesn't always work.

    Linux distribution developers know approximately nothing.