| View previous topic :: View next topic |
| Author |
Message |
asdasd1dsadsa
n00b
Joined: 18 Jan 2022
Posts: 6
|
 Posted: Sun Nov 19, 2023 11:49 am Post subject: Intel AX200NGW, Built-in kernel iwlwifi error |
 |
|
Background
Half a year ago, I got my new laptop(with an Intel AX200NGW wireless card) and was installing gentoo on it. However the situation was that, neither the system in LIVECD nor sys-kernel/gentoo-kernel-bin-6.1.31 has internet. Days later, I found a workaround(I also tried many other things):
| Code: | | /lib/firmware/iwlwifi-cc-a0-46.ucode |
from https://www.intel.com/content/www/us/en/support/articles/000005511/wireless.html
From this website we know that it's recommended by Intel, however it's not included in new sys-kernel/linux-firmware package.
2. Build this ucode file into kernel(also move the higher versions in /lib/firmware directory):
| Code: | # /usr/src/linux/.config
CONFIG_IWLWIFI=y
CONFIG_IWLDVM=y
CONFIG_IWLMVM=y
CONFIG_EXTRA_FIRMWARE="... regulatory.db regulatory.db.p7s iwlwifi-cc-a0-46.ucode intel/ibt-20-1-3.ddc intel/ibt-20-1-3.sfi"
CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware/" |
| Code: | # /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="... iwlmvm.power_scheme=1"
|
You may question me: how do I install gentoo without any network? I could tell that there's a manual workaround to get network. That is removing the pci device and rescanning mannually, I show it here as a bash script:
| Code: | ls -d /sys/bus/pci/drivers/iwlwifi/*/ | while read dev; do
echo 1 > "${dev}remove" && echo 1 > /sys/bus/pci/rescan;
done;
|
Each time I reload it, the interface number in wlan0 increases, hours later I may get a interface named as wlan4.
Two months later
To enable some kernel feature, I updated my kernel to 6.3.7, my workaround is still working.
Today
I've emerge @world, and then try the new kernel 6.3.7, both sys-kernel/gentoo-kernel-bin and sys-kernel/gentoo-sources. I found them loading the new ucode (as I also emerge linux-firmware and didn't remove them yet) iwlwifi-cc-a0-77.ucode. The situation is better than the one with 6.1.31 kernel, as I have wireless network working, but still buggy: iwlwifi encounters error sometimes(can be seen in dmesg), and then was reloaded (and I could observe the interface renamed to wlan1 from wlan0).
When I retry my workaround, that is to make the kernel load 46 version ucode, it tells me that it's below the minimum supported version! dmesg says
| Code: | [ 2.979365] iwlwifi 0000:02:00.0: no suitable firmware found!
[ 2.979367] iwlwifi 0000:02:00.0: minimum version required: iwlwifi-cc-a0-50
[ 2.979369] iwlwifi 0000:02:00.0: maximum version supported: iwlwifi-cc-a0-77
[ 2.979371] iwlwifi 0000:02:00.0: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
|
However, it's the only one I've found that work normally. When I was installing the 6.1.31 kernel, I tried 46, 48, 50, 72, 77. With 6.6.1 kernel, I tried 46, 50, 72, 77.
I do not plan to instantly put a bunch of my dmesg etc. here, as they has many versions and I had to restart my laptop for many times and wait things occasionally happen. Before that I just want to ask a basic question that, is it worth to trace these messages and report them to kernel developers?
Or there is already some other way to make it work, I just don't do it in a right way?
Must I keep myself in 6.3.7 version, as newer version no longer support the version-46-ucode?
Must I use modules instead of built-in-kernel iwlwifi?
I don't find a newer ucode that works better (at least, not worse) than 46 version, why the new kernel stopped supporting it? |
|
| Back to top |
|
 |
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54578
Location: 56N 3W
|
| Posted: Sun Nov 19, 2023 11:59 am Post subject: |
|
|
asdasd1dsadsa,
Welcome to Gentoo
Modules will 'just work' as iwlwi will help itself to firmware from /lib/firmware when it loads.
If you use modules, dmesg will list the firmware that it tried to load and the version in use.
Its not an error to build more that more version of the firmware into the kernel. I have
| Code: | $ ls /lib/firmware/iwlwifi-cc-a0-
iwlwifi-cc-a0-50.ucode iwlwifi-cc-a0-72.ucode iwlwifi-cc-a0-77.ucode
iwlwifi-cc-a0-59.ucode iwlwifi-cc-a0-73.ucode
iwlwifi-cc-a0-66.ucode iwlwifi-cc-a0-74.ucode |
in /lib/firmware.
The driver will choose the latest version it can use, jast as if it was a module.
If you don't have internet, there is always sneakernet.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
logrusx
Advocate
Joined: 22 Feb 2018
Posts: 2437
|
| Posted: Mon Nov 20, 2023 7:14 am Post subject: |
|
|
You've embedded 46 and the minimum is 50.
Best Regards,
Georgi |
|
| Back to top |
|
|
asdasd1dsadsa
n00b
Joined: 18 Jan 2022
Posts: 6
|
| Posted: Mon Nov 20, 2023 12:10 pm Post subject: Reply to |
|
|
Higher versions are buggy, the one only work is 46, which is going out of the range of kernel support. If I use ver 77, it occasionally crash, with various error log. Here's an example(I've said yes to CONFIG_IWLWIFI_DEBUG and set iwlwifi.debug=1):
| Code: | [ 593.948804] iwlwifi 0000:02:00.0: regular scan timed out
[ 593.949095] iwlwifi 0000:02:00.0: Microcode SW error detected. Restarting 0x0.
[ 593.949314] iwlwifi 0000:02:00.0: Start IWL Error Log Dump:
[ 593.949316] iwlwifi 0000:02:00.0: Transport status: 0x0000004A, valid: 6
[ 593.949319] iwlwifi 0000:02:00.0: Loaded firmware version: 77.bd067429.0 cc-a0-77.ucode
[ 593.949322] iwlwifi 0000:02:00.0: 0x00000084 | NMI_INTERRUPT_UNKNOWN
[ 593.949324] iwlwifi 0000:02:00.0: 0x000022F0 | trm_hw_status0
[ 593.949325] iwlwifi 0000:02:00.0: 0x00000000 | trm_hw_status1
[ 593.949327] iwlwifi 0000:02:00.0: 0x004F8B7A | branchlink2
[ 593.949329] iwlwifi 0000:02:00.0: 0x004EEC2A | interruptlink1
[ 593.949330] iwlwifi 0000:02:00.0: 0x004EEC2A | interruptlink2
[ 593.949331] iwlwifi 0000:02:00.0: 0x000152DA | data1
[ 593.949332] iwlwifi 0000:02:00.0: 0x01000000 | data2
[ 593.949333] iwlwifi 0000:02:00.0: 0x00000000 | data3
[ 593.949334] iwlwifi 0000:02:00.0: 0x00000000 | beacon time
[ 593.949335] iwlwifi 0000:02:00.0: 0x01D89722 | tsf low
[ 593.949336] iwlwifi 0000:02:00.0: 0x00000000 | tsf hi
[ 593.949337] iwlwifi 0000:02:00.0: 0x00000000 | time gp1
[ 593.949338] iwlwifi 0000:02:00.0: 0x01D8F4F6 | time gp2
[ 593.949339] iwlwifi 0000:02:00.0: 0x00000001 | uCode revision type
[ 593.949340] iwlwifi 0000:02:00.0: 0x0000004D | uCode version major
[ 593.949341] iwlwifi 0000:02:00.0: 0xBD067429 | uCode version minor
[ 593.949342] iwlwifi 0000:02:00.0: 0x00000340 | hw version
[ 593.949343] iwlwifi 0000:02:00.0: 0x18C89000 | board version
[ 593.949344] iwlwifi 0000:02:00.0: 0x80FFFD26 | hcmd
[ 593.949345] iwlwifi 0000:02:00.0: 0x00020000 | isr0
[ 593.949346] iwlwifi 0000:02:00.0: 0x00000000 | isr1
[ 593.949347] iwlwifi 0000:02:00.0: 0x08F00002 | isr2
[ 593.949348] iwlwifi 0000:02:00.0: 0x00C3001C | isr3
[ 593.949349] iwlwifi 0000:02:00.0: 0x00000000 | isr4
[ 593.949350] iwlwifi 0000:02:00.0: 0x00290103 | last cmd Id
[ 593.949351] iwlwifi 0000:02:00.0: 0x000152DA | wait_event
[ 593.949352] iwlwifi 0000:02:00.0: 0x00000080 | l2p_control
[ 593.949353] iwlwifi 0000:02:00.0: 0x00000000 | l2p_duration
[ 593.949354] iwlwifi 0000:02:00.0: 0x0000003F | l2p_mhvalid
[ 593.949355] iwlwifi 0000:02:00.0: 0x00000000 | l2p_addr_match
[ 593.949356] iwlwifi 0000:02:00.0: 0x00000009 | lmpm_pmg_sel
[ 593.949357] iwlwifi 0000:02:00.0: 0x00000000 | timestamp
[ 593.949358] iwlwifi 0000:02:00.0: 0x0000488C | flow_handler
[ 593.949474] iwlwifi 0000:02:00.0: Start IWL Error Log Dump:
[ 593.949475] iwlwifi 0000:02:00.0: Transport status: 0x0000004A, valid: 7
[ 593.949477] iwlwifi 0000:02:00.0: 0x20000066 | NMI_INTERRUPT_HOST
[ 593.949478] iwlwifi 0000:02:00.0: 0x00000000 | umac branchlink1
[ 593.949479] iwlwifi 0000:02:00.0: 0x80455D2E | umac branchlink2
[ 593.949480] iwlwifi 0000:02:00.0: 0x80472C66 | umac interruptlink1
[ 593.949481] iwlwifi 0000:02:00.0: 0x80472C66 | umac interruptlink2
[ 593.949482] iwlwifi 0000:02:00.0: 0x01000000 | umac data1
[ 593.949483] iwlwifi 0000:02:00.0: 0x80472C66 | umac data2
[ 593.949484] iwlwifi 0000:02:00.0: 0x00000000 | umac data3
[ 593.949485] iwlwifi 0000:02:00.0: 0x0000004D | umac major
[ 593.949486] iwlwifi 0000:02:00.0: 0xBD067429 | umac minor
[ 593.949487] iwlwifi 0000:02:00.0: 0x01D8F4F3 | frame pointer
[ 593.949488] iwlwifi 0000:02:00.0: 0xC0886260 | stack pointer
[ 593.949489] iwlwifi 0000:02:00.0: 0x00290103 | last host cmd
[ 593.949490] iwlwifi 0000:02:00.0: 0x00000000 | isr status reg
[ 593.949564] iwlwifi 0000:02:00.0: IML/ROM dump:
[ 593.949565] iwlwifi 0000:02:00.0: 0x00000003 | IML/ROM error/state
[ 593.949610] iwlwifi 0000:02:00.0: 0x00005C83 | IML/ROM data1
[ 593.949655] iwlwifi 0000:02:00.0: 0x00000080 | IML/ROM WFPM_AUTH_KEY_0
[ 593.949694] iwlwifi 0000:02:00.0: Fseq Registers:
[ 593.949699] iwlwifi 0000:02:00.0: 0x60000000 | FSEQ_ERROR_CODE
[ 593.949703] iwlwifi 0000:02:00.0: 0x80290021 | FSEQ_TOP_INIT_VERSION
[ 593.949708] iwlwifi 0000:02:00.0: 0x00050008 | FSEQ_CNVIO_INIT_VERSION
[ 593.949744] iwlwifi 0000:02:00.0: 0x0000A503 | FSEQ_OTP_VERSION
[ 593.949748] iwlwifi 0000:02:00.0: 0x80000003 | FSEQ_TOP_CONTENT_VERSION
[ 593.949782] iwlwifi 0000:02:00.0: 0x4552414E | FSEQ_ALIVE_TOKEN
[ 593.949786] iwlwifi 0000:02:00.0: 0x00100530 | FSEQ_CNVI_ID
[ 593.949791] iwlwifi 0000:02:00.0: 0x00000532 | FSEQ_CNVR_ID
[ 593.949796] iwlwifi 0000:02:00.0: 0x00100530 | CNVI_AUX_MISC_CHIP
[ 593.949803] iwlwifi 0000:02:00.0: 0x00000532 | CNVR_AUX_MISC_CHIP
[ 593.949810] iwlwifi 0000:02:00.0: 0x05B0905B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[ 593.949853] iwlwifi 0000:02:00.0: 0x0000025B | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[ 593.949886] iwlwifi 0000:02:00.0: 0x00050008 | FSEQ_PREV_CNVIO_INIT_VERSION
[ 593.949891] iwlwifi 0000:02:00.0: 0x00290021 | FSEQ_WIFI_FSEQ_VERSION
[ 593.949895] iwlwifi 0000:02:00.0: 0x00290021 | FSEQ_BT_FSEQ_VERSION
[ 593.949930] iwlwifi 0000:02:00.0: 0x00000104 | FSEQ_CLASS_TP_VERSION
[ 593.949976] iwlwifi 0000:02:00.0: UMAC CURRENT PC: 0x8047277c
[ 593.949981] iwlwifi 0000:02:00.0: LMAC1 CURRENT PC: 0xd0
[ 593.950204] iwlwifi 0000:02:00.0: WRT: Collecting data: ini trigger 4 fired (delay=0ms).
[ 593.950207] iwlwifi 0000:02:00.0: iwl_mvm_nic_restart FW restart requested after debug collection
[ 593.950209] ieee80211 phy4: Hardware restart was requested
[ 593.950214] iwlwifi 0000:02:00.0: iwl_fw_dbg_collect_sync WRT: Data collection start
[ 594.836628] iwlwifi 0000:02:00.0: iwl_fw_dbg_collect_sync WRT: Data collection done
[ 594.836649] iwlwifi 0000:02:00.0: _iwl_trans_pcie_gen2_stop_device DEVICE_ENABLED bit was set and is now cleared
[ 594.836791] iwlwifi 0000:02:00.0: iwl_pcie_gen2_apm_stop Stop card, put in low power state
[ 594.836870] iwlwifi 0000:02:00.0: iwl_pcie_apm_stop_master stop master
[ 594.849129] iwlwifi 0000:02:00.0: iwl_pcie_prepare_card_hw iwl_trans_prepare_card_hw enter
[ 594.849183] iwlwifi 0000:02:00.0: iwl_pcie_set_hw_ready hardware ready
[ 594.849309] iwlwifi 0000:02:00.0: iwl_pcie_prepare_card_hw iwl_trans_prepare_card_hw enter
[ 594.849348] iwlwifi 0000:02:00.0: iwl_pcie_set_hw_ready hardware ready
[ 594.855398] iwlwifi 0000:02:00.0: iwl_pcie_prepare_card_hw iwl_trans_prepare_card_hw enter
[ 594.855448] iwlwifi 0000:02:00.0: iwl_pcie_set_hw_ready hardware ready
[ 594.855452] iwlwifi 0000:02:00.0: iwl_pcie_apm_init Init card's basic functions
[ 594.858342] iwlwifi 0000:02:00.0: iwl_pcie_prepare_card_hw iwl_trans_prepare_card_hw enter
[ 594.858385] iwlwifi 0000:02:00.0: iwl_pcie_set_hw_ready hardware ready
[ 594.858434] iwlwifi 0000:02:00.0: iwl_pcie_gen2_apm_init Init card's basic functions
[ 594.860702] iwlwifi 0000:02:00.0: iwl_mvm_nic_config Radio type=0x0-0x2-0x1
[ 594.862586] iwlwifi 0000:02:00.0: iwl_pcie_gen2_nic_init Enabling shadow registers in device
[ 594.980465] iwlwifi 0000:02:00.0: iwl_mvm_rx_mfuart_notif MFUART: installed ver: 0x1400000c, external ver: 0x1400000c, status: 0x00350000, duration: 0x000013ab
[ 594.980471] iwlwifi 0000:02:00.0: iwl_mvm_rx_mfuart_notif MFUART: image size: 0x00006094
[ 594.980573] iwlwifi 0000:02:00.0: iwl_trans_txq_send_hcmd_sync Attempting to send sync command INIT_EXTENDED_CFG_CMD
[ 594.980577] iwlwifi 0000:02:00.0: iwl_trans_txq_send_hcmd_sync Setting HCMD_ACTIVE for command INIT_EXTENDED_CFG_CMD
[ 594.983063] iwlwifi 0000:02:00.0: iwl_pcie_hcmd_complete Clearing HCMD_ACTIVE for command INIT_EXTENDED_CFG_CMD
[ 594.983124] iwlwifi 0000:02:00.0: iwl_trans_txq_send_hcmd_sync Attempting to send sync command NVM_ACCESS_COMPLETE
[ 594.983137] iwlwifi 0000:02:00.0: iwl_trans_txq_send_hcmd_sync Setting HCMD_ACTIVE for command NVM_ACCESS_COMPLETE
[ 594.983449] iwlwifi 0000:02:00.0: iwl_pcie_hcmd_complete Clearing HCMD_ACTIVE for command NVM_ACCESS_COMPLETE
[ 595.048610] iwlwifi 0000:02:00.0: iwl_trans_txq_send_hcmd_sync Attempting to send sync command SHARED_MEM_CFG_CMD
[ 595.048620] iwlwifi 0000:02:00.0: iwl_trans_txq_send_hcmd_sync Setting HCMD_ACTIVE for command SHARED_MEM_CFG_CMD
[ 595.049508] iwlwifi 0000:02:00.0: iwl_pcie_hcmd_complete Clearing HCMD_ACTIVE for command SHARED_MEM_CFG_CMD
[ 595.049574] iwlwifi 0000:02:00.0: iwl_get_shared_mem_conf SHARED MEM CFG: got memory offsets/sizes
[ 595.049586] iwlwifi 0000:02:00.0: iwl_trans_txq_send_hcmd_sync Attempting to send sync command TX_ANT_CONFIGURATION_CMD
[ 595.049591] iwlwifi 0000:02:00.0: iwl_trans_txq_send_hcmd_sync Setting HCMD_ACTIVE for command TX_ANT_CONFIGURATION_CMD
[ 595.050306] iwlwifi 0000:02:00.0: iwl_pcie_hcmd_complete Clearing HCMD_ACTIVE for command TX_ANT_CONFIGURATION_CMD
[ 595.050370] iwlwifi 0000:02:00.0: iwl_trans_txq_send_hcmd_sync Attempting to send sync command BT_CONFIG
[ 595.050378] iwlwifi 0000:02:00.0: iwl_trans_txq_send_hcmd_sync Setting HCMD_ACTIVE for command BT_CONFIG
[ 595.050950] iwlwifi 0000:02:00.0: iwl_pcie_hcmd_complete Clearing HCMD_ACTIVE for command BT_CONFIG
[ 595.051014] iwlwifi 0000:02:00.0: iwl_trans_txq_send_hcmd_sync Attempting to send sync command UNKNOWN
[ 595.051022] iwlwifi 0000:02:00.0: iwl_trans_txq_send_hcmd_sync Setting HCMD_ACTIVE for command UNKNOWN
[ 595.051645] iwlwifi 0000:02:00.0: iwl_pcie_hcmd_complete Clearing HCMD_ACTIVE for command UNKNOWN
[ 595.051694] iwlwifi 0000:02:00.0: iwl_trans_txq_send_hcmd_sync Attempting to send sync command RFH_QUEUE_CONFIG_CMD
[ 595.051698] iwlwifi 0000:02:00.0: iwl_trans_txq_send_hcmd_sync Setting HCMD_ACTIVE for command RFH_QUEUE_CONFIG_CMD
[ 595.051862] iwlwifi 0000:02:00.0: iwl_pcie_hcmd_complete Clearing HCMD_ACTIVE for command RFH_QUEUE_CONFIG_CMD
[ 595.051896] iwlwifi 0000:02:00.0: iwl_trans_txq_send_hcmd_sync Attempting to send sync command RSS_CONFIG_CMD
[ 595.051903] iwlwifi 0000:02:00.0: iwl_trans_txq_send_hcmd_sync Setting HCMD_ACTIVE for command RSS_CONFIG_CMD
[ 595.052045] iwlwifi 0000:02:00.0: iwl_pcie_hcmd_complete Clearing HCMD_ACTIVE for command RSS_CONFIG_CMD
[ 595.052082] iwlwifi 0000:02:00.0: iwl_trans_txq_send_hcmd_sync Attempting to send sync command PHY_CONTEXT_CMD
[ 595.052086] iwlwifi 0000:02:00.0: iwl_trans_txq_send_hcmd_sync Setting HCMD_ACTIVE for command PHY_CONTEXT_CMD |
|
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54578
Location: 56N 3W
|
| Posted: Mon Nov 20, 2023 12:48 pm Post subject: |
|
|
asdasd1dsadsa,
Be aware that CONFIG_*_DEBUG kernel options are permitted to interfere with normal operation to gather information for debugging the kernel driver.
Firmware is not a part of the kernel driver. Its loaded (by the kernel driver) into the device to allow the device to operate. It saves vendors a few shillings on the permanent storage in the device.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
logrusx
Advocate
Joined: 22 Feb 2018
Posts: 2437
|
| Posted: Mon Nov 20, 2023 4:14 pm Post subject: Re: Reply to |
|
|
| asdasd1dsadsa wrote: | Higher versions are buggy, the one only work is 46, which is going out of the range of kernel support. If I use ver 77, it occasionally crash, with various error log. Here's an example(I've said yes to CONFIG_IWLWIFI_DEBUG and set iwlwifi.debug=1):
|
That doesn't make sense. I've had no problems whatsoever with iwlwifi, using mostly latest versions of stable kernels. If you insist on using 46, try with one of the long term support kernels.
p.s. many of those are diagnostic messages. You can't judge by them if the driver crashed. Did you experience any crash or you're finding them in the logs?
Best Regards,
Georgi |
|
| Back to top |
|
|
asdasd1dsadsa
n00b
Joined: 18 Jan 2022
Posts: 6
|
| Posted: Tue Nov 21, 2023 4:18 am Post subject: |
|
|
| NeddySeagoon wrote: | Be aware that CONFIG_*_DEBUG kernel options are permitted to interfere with normal operation to gather information for debugging the kernel driver.
|
However, the crash would still occur when I didn't turn on that debug option: I even don't know that kernel option before the crash and my searching on websites. |
|
| Back to top |
|
|
asdasd1dsadsa
n00b
Joined: 18 Jan 2022
Posts: 6
|
| Posted: Tue Nov 21, 2023 4:31 am Post subject: Re: Reply to |
|
|
| logrusx wrote: | | You can't judge by them if the driver crashed. Did you experience any crash or you're finding them in the logs? |
My NetworkManager(under KDE) is losing the wireless connection, and I believe it's related to firmware restart after errors, as:
1. I can find such log descriptions in dmesg: | Code: | [ 204.574419] iwlwifi 0000:02:00.0: iwl_mvm_nic_restart FW restart requested after debug collection
[ 204.574421] ieee80211 phy0: Hardware restart was requested |
2. In early time (that time I was still in 6.1.31 or LIVECD), the crash never heals itself, but requires my manual restart (pasted in my main post).
3. In later time, the missing network comes back on its own after several seconds(sometimes half a minute). However, the interface name changes from wlan0 to wlan1, wlan2, etc..
4. dmesg messages showed that there are some "UNKOWN" commands, I think they relate to some version compatibility issues. And, the "UNKNOWN" log occurs much more times(e.g. 129 times) in ver-77 firmware, while the ver-46 one has always only 3 lines of such logs. There's an example:
| Code: | [ 5.411304] iwlwifi 0000:02:00.0: iwl_trans_txq_send_hcmd_sync Attempting to send sync command UNKNOWN
[ 5.411313] iwlwifi 0000:02:00.0: iwl_trans_txq_send_hcmd_sync Setting HCMD_ACTIVE for command UNKNOWN
[ 5.411438] iwlwifi 0000:02:00.0: iwl_pcie_hcmd_complete Clearing HCMD_ACTIVE for command UNKNOWN |
|
|
| Back to top |
|
|
logrusx
Advocate
Joined: 22 Feb 2018
Posts: 2437
|
| Posted: Tue Nov 21, 2023 11:18 am Post subject: |
|
|
I'm sorry to tell you that looks like a hardware failure.
Did you try with a 5.15 kernel?
If you can't find a kernel that works with it, you might consider replacing the adapter. I had AX200 for a year maybe, but it was defective and the connectors for the antennas ripped off very easily, so I had to replace it. I've never noticed such issues with it. Now I have AX210 and I see I've had crashes with 6.5.0, not like yours though, mine are with big dumps. But I don't have logs for too far back to check with which kernel the AX200 worked.
I think I used 6.0.x for a long time, so I guess it was with it.
Best Regards,
Georgi |
|
| Back to top |
|
|
asdasd1dsadsa
n00b
Joined: 18 Jan 2022
Posts: 6
|
| Posted: Tue Nov 21, 2023 2:50 pm Post subject: |
|
|
| logrusx wrote: | I'm sorry to tell you that looks like a hardware failure.
Did you try with a 5.15 kernel?
If you can't find a kernel that works with it, you might consider replacing the adapter. I had AX200 for a year maybe, but it was defective and the connectors for the antennas ripped off very easily, so I had to replace it. I've never noticed such issues with it. Now I have AX210 and I see I've had crashes with 6.5.0, not like yours though, mine are with big dumps. But I don't have logs for too far back to check with which kernel the AX200 worked.
I think I used 6.0.x for a long time, so I guess it was with it.
Best Regards,
Georgi |
Thanks for the help. I may leave myself at 6.3.7, until buying a new network card. Should I report this to kernel developers? |
|
| Back to top |
|
|
logrusx
Advocate
Joined: 22 Feb 2018
Posts: 2437
|
| Posted: Thu Nov 23, 2023 11:08 am Post subject: |
|
|
| asdasd1dsadsa wrote: |
Thanks for the help. I may leave myself at 6.3.7, until buying a new network card. Should I report this to kernel developers? |
I don't know. I don't want to mess with the antenna connectors on my current card, otherwise I would install the old one just to see if it works. It had one connector left, so it could be used for test.
I don't believe this is an issue with the drivers as there would be plenty of threads around by now. You didn't say anything about trying with 5.15. You can use the gentoo-kernel-bin to make it quick.
Best Regards,
Georgi |
|
| Back to top |
|
|
asdasd1dsadsa
n00b
Joined: 18 Jan 2022
Posts: 6
|
| Posted: Tue Nov 19, 2024 2:14 pm Post subject: New progress |
|
|
| I bought a new AX210 card half a year ago, it works well with iwlwifi-ty-a0-gf-a0-59.ucode and gentoo-sources-6.6.38, linux-firmware-20240709 |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
