Forums

Skip to content

Advanced search
  • Quick links
    • Unanswered topics
    • Active topics
    • Search
  • FAQ
  • Login
  • Register
  • Board index Assistance Kernel & Hardware
  • Search

AX101 Kernel 6.3 mainlined, still doesn't support my iwlwifi

Kernel not recognizing your hardware? Problems with power management or PCMCIA? What hardware is compatible with Gentoo? See here. (Only for kernels supported by Gentoo.)
Post Reply
Advanced search
20 posts • Page 1 of 1
Author
Message
n1ese
Tux's lil' helper
Tux's lil' helper
Posts: 87
Joined: Sun Sep 29, 2019 3:25 pm

AX101 Kernel 6.3 mainlined, still doesn't support my iwlwifi

  • Quote

Post by n1ese » Mon Apr 24, 2023 9:04 pm

Very disappointed. Kernel 6.3 has finally been mainlined but my AX101 WiFi adapters still are not supported.

Code: Select all

[    0.422490] Intel(R) Wireless WiFi driver for Linux
[    0.422560] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
[    0.424862] iwlwifi: No config found for PCI dev 54f0/0244, rev=0x370, rfid=0x10c000
[    0.424873] iwlwifi: probe of 0000:00:14.3 failed with error -22
Bluetooth wants to work but Intel hasn't released the firmware for it yet either.

Code: Select all

[    3.024210] Bluetooth: hci0: Device revision is 2
[    3.024214] Bluetooth: hci0: Secure boot is enabled
[    3.024215] Bluetooth: hci0: OTP lock is enabled
[    3.024216] Bluetooth: hci0: API lock is enabled
[    3.024217] Bluetooth: hci0: Debug lock is disabled
[    3.024218] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[    3.024219] Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 38
[    3.024223] Loading firmware: intel/ibt-0040-1050.sfi
[    3.024702] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-0040-1050.sfi (-2)
Last edited by n1ese on Mon May 15, 2023 4:25 pm, edited 1 time in total.
Top
Hu
Administrator
Administrator
Posts: 24401
Joined: Tue Mar 06, 2007 5:38 am

  • Quote

Post by Hu » Mon Apr 24, 2023 9:21 pm

Where had you seen a prediction that kernel 6.3 would support this wireless device?

Firmware blobs are only blobs because the vendors consistently fail to provide proper tooling and source to let the community maintain the firmware. Therefore, if you cannot get proprietary firmware for your device, the issue lies with the manufacturer that failed to release both the firmware and any means for the community to help you.
Top
n1ese
Tux's lil' helper
Tux's lil' helper
Posts: 87
Joined: Sun Sep 29, 2019 3:25 pm

  • Quote

Post by n1ese » Mon Apr 24, 2023 9:59 pm

Hu wrote:Where had you seen a prediction that kernel 6.3 would support this wireless device?
There's been a patch floating around for 6.2 that some of us had hoped would make it into 6.3 to offer at least some limited connectivity. It works to some extent but doesn't work for my networks.

Edit: also, the Intel spec sheet says it is supported by Linux but clearly it is not.
Top
Josef.95
Advocate
Advocate
Posts: 4857
Joined: Mon Sep 03, 2007 9:46 am
Location: Germany

  • Quote

Post by Josef.95 » Mon Apr 24, 2023 11:05 pm

Hm, not sure, but from https://community.intel.com/t5/Wireless ... -p/1464353
it sounds Intel is with Wi-Fi 6 AX101 driver and firmware blobs not ready yet.
Top
Goverp
Advocate
Advocate
User avatar
Posts: 2403
Joined: Wed Mar 07, 2007 6:41 pm

  • Quote

Post by Goverp » Tue Apr 25, 2023 9:31 am

n1ese wrote:...
Edit: also, the Intel spec sheet says it is supported by Linux but clearly it is not.
I had this problem with the Realtek WiFi card in my laptop. The cure was an out-of-kernel semi-official driver; Realtek fed code and support to a guy running a git repository somewhere - this persisted until the driver was tidy enough to be accepted into the kernel, about two years later. Gentoo picked up the out-of-kernel driver after a while, so it was then a case of emergeing it like any other kernel driver, though I just stayed with manually pulling updates from git and recompile/reinstalling myself.
Of course, if there's no driver anywhere, you're stuck. I don't have this hardware, so I can't say.
This thread on the Intel community forums suggests you want the "backport-iwlwifi" package, which is here on GitHub.
Greybeard
Top
Suicidal
l33t
l33t
User avatar
Posts: 959
Joined: Wed Jul 30, 2003 4:55 am
Location: /dev/null

  • Quote

Post by Suicidal » Tue Apr 25, 2023 9:44 am

Maybe try running the live ebuild of linux-firmware? The latest non live ebuild is from 4/4 which predates the 6.3 general release by almost 3 weeks.
Top
n1ese
Tux's lil' helper
Tux's lil' helper
Posts: 87
Joined: Sun Sep 29, 2019 3:25 pm

  • Quote

Post by n1ese » Fri May 12, 2023 2:28 pm

Well, some progress is being made in the 6.4 kernel source. As of 6.4.0-rc1, the kernel is now detecting my AX101 properly and I've been able to get it to load the firmware although the latest version of the firmware is not available (78 ) in the live ebuild of linux-firmware. However, I can't get it to work properly, I'm getting an i/o error when bringing up the interface.

Code: Select all

# ifconfig -v wlo1 up
SIOCSIFFLAGS: Input/output error
WARNING: at least one error occured. (-1)

Code: Select all

[    0.909623] Intel(R) Wireless WiFi driver for Linux
[    0.909692] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
[    0.911841] iwlwifi 0000:00:14.3: Detected crf-id 0x501, cnv-id 0x80400 wfpm id 0x80000030
[    0.911882] iwlwifi 0000:00:14.3: PCI dev 54f0/0244, rev=0x370, rfid=0x10c000
[    0.911908] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-hr-b0-78.ucode failed with error -2
[    0.911914] iwlwifi 0000:00:14.3: api flags index 2 larger than supported by driver
[    0.911923] iwlwifi 0000:00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.36
[    0.912100] iwlwifi 0000:00:14.3: loaded firmware version 77.f92b5fed.0 so-a0-hr-b0-77.ucode op_mode iwlmvm
[    0.918950] iwlwifi 0000:00:14.3: Detected Intel(R) Wi-Fi 6 AX101, REV=0x370
[    0.924970] iwlwifi 0000:00:14.3: WRT: Invalid buffer destination
[    1.027216] iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x1f
[    1.027265] iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[    1.027316] iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90
[    1.027364] iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x10
[    1.027416] iwlwifi 0000:00:14.3: Detected RF HR1 B3, rfid=0x10c000
[    1.028515] iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 4
[    1.068626] iwlwifi 0000:00:14.3: base HW address: f4:c8:8a:48:7c:8b
[    4.230946] iwlwifi 0000:00:14.3 wlo1: renamed from wlan0
Top
rab0171610
l33t
l33t
Posts: 721
Joined: Sat Dec 24, 2022 1:41 am

  • Quote

Post by rab0171610 » Fri May 12, 2023 9:26 pm

https://git.kernel.org/pub/scm/linux/ke ... .git/tree/
The latest version of so-a0-hr-b0-77.ucode in the linux-firmware git tree is 77. There are some iwlwifi firmwares released with version 78, but the firmware version in your output is not one of them -- so-a0-hr-b0-77.ucode is the latest version installed with the live ebuild as it it the latest in the tree. My guess is that it is a work in progress and you will just have to monitor the situation.
You are not alone . . .

https://community.intel.com/t5/Wireless ... -p/1468063
Top
CooSee
Veteran
Veteran
User avatar
Posts: 1617
Joined: Sat Nov 20, 2004 10:38 pm
Location: right here !

  • Quote

Post by CooSee » Fri May 12, 2023 9:30 pm

do you have both (Bluetooth & WiFi) enabled at the same time ?

try with Bluetooth disabled.

found this https://askubuntu.com/questions/1459856 ... oth-issues and https://aur.archlinux.org/packages/iwlwifi-ax101-dkms

8)
" Die Realität ist eine Illusion, die durch Mangel an ehrlicher Kommunikation entsteht "
---
" Der Mensch ist von Natur aus neugierig, was am Ende übrig bleibt ist die Gier "
Top
rab0171610
l33t
l33t
Posts: 721
Joined: Sat Dec 24, 2022 1:41 am

  • Quote

Post by rab0171610 » Fri May 12, 2023 9:51 pm

In my experiences with newer hardware, bluetooth/wifi co-existence is usually one of the last parts of a kernel module that gets improved upon. So as you are trying to get newer wifi kernel modules and firmware loaded and working, I agree with CooSee that you should ideally test the wifi with bluetooth disabled.
Top
n1ese
Tux's lil' helper
Tux's lil' helper
Posts: 87
Joined: Sun Sep 29, 2019 3:25 pm

  • Quote

Post by n1ese » Fri May 12, 2023 11:47 pm

CooSee wrote:do you have both (Bluetooth & WiFi) enabled at the same time ?

try with Bluetooth disabled.

found this https://askubuntu.com/questions/1459856 ... oth-issues and https://aur.archlinux.org/packages/iwlwifi-ax101-dkms

8)
I'll give it a try. One goofy thing, it's an AX101 adapter but the kernel is detecting the bluetooth portion of the adapter as an AX201.
Top
logrusx
Advocate
Advocate
User avatar
Posts: 3534
Joined: Thu Feb 22, 2018 2:29 pm

  • Quote

Post by logrusx » Sat May 13, 2023 5:49 am

The *01 chips are not complete WiFi modules, they are missing a chip because they "outsource" part of the computation to the main system and work only on Intel systems. Is your system Intel based?

Best Regards,
Georgi
Top
n1ese
Tux's lil' helper
Tux's lil' helper
Posts: 87
Joined: Sun Sep 29, 2019 3:25 pm

  • Quote

Post by n1ese » Sat May 13, 2023 1:04 pm

logrusx wrote:The *01 chips are not complete WiFi modules, they are missing a chip because they "outsource" part of the computation to the main system and work only on Intel systems. Is your system Intel basedi
Yes, of course, it's an N305 CPU and AX101 WiFi 6 adapter.. both are very new to the market, part of the problem.
Top
n1ese
Tux's lil' helper
Tux's lil' helper
Posts: 87
Joined: Sun Sep 29, 2019 3:25 pm

  • Quote

Post by n1ese » Mon May 15, 2023 4:24 pm

Bluetooth disabled, still having issues. Here is the latest dmesg with IWL error log dump. Any chance I am missing something simple?

Code: Select all

[    0.000000] Linux version 6.4.0-rc2 (root@ganymede) (gcc (Gentoo 13.1.0-r1 p1) 13.1.0, GNU ld (Gentoo 2.40 p5) 2.40.0) #1 SMP PREEMPT_DYNAMIC Sun May 14 19:38:07 CDT 2023
[    0.619679] Intel(R) Wireless WiFi driver for Linux
[    0.619751] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
[    0.621969] iwlwifi 0000:00:14.3: Detected crf-id 0x501, cnv-id 0x80400 wfpm id 0x80000030
[    0.622010] iwlwifi 0000:00:14.3: PCI dev 54f0/0244, rev=0x370, rfid=0x10c000
[    0.622085] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-hr-b0-78.ucode failed with error -2
[    0.622091] iwlwifi 0000:00:14.3: api flags index 2 larger than supported by driver
[    0.622101] iwlwifi 0000:00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.36
[    0.622270] iwlwifi 0000:00:14.3: loaded firmware version 77.f92b5fed.0 so-a0-hr-b0-77.ucode op_mode iwlmvm
[    0.629241] iwlwifi 0000:00:14.3: Detected Intel(R) Wi-Fi 6 AX101, REV=0x370
[    0.635988] iwlwifi 0000:00:14.3: WRT: Invalid buffer destination
[    0.733175] iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x1f
[    0.733221] iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[    0.733270] iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90
[    0.733321] iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x10
[    0.733371] iwlwifi 0000:00:14.3: Detected RF HR1 B3, rfid=0x10c000
[    0.734489] iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 4
[    3.911892] iwlwifi 0000:00:14.3 wlo1: renamed from wlan0
[    5.675433] iwlwifi 0000:00:14.3: WRT: Invalid buffer destination
[    5.772382] iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x1f
[    5.772431] iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[    5.772439] iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90
[    5.772447] iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x10
[    5.773493] iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 4
[    5.821003] iwlwifi 0000:00:14.3: Registered PHC clock: iwlwifi-PTP, with index: 2
[    5.821965] iwlwifi 0000:00:14.3: Microcode SW error detected. Restarting 0x0.
[    5.822119] iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
[    5.822121] iwlwifi 0000:00:14.3: Transport status: 0x0000004B, valid: 6
[    5.822123] iwlwifi 0000:00:14.3: Loaded firmware version: 77.f92b5fed.0 so-a0-hr-b0-77.ucode
[    5.822125] iwlwifi 0000:00:14.3: 0x00000071 | NMI_INTERRUPT_UMAC_FATAL
[    5.822126] iwlwifi 0000:00:14.3: 0x000002F0 | trm_hw_status0
[    5.822127] iwlwifi 0000:00:14.3: 0x00000000 | trm_hw_status1
[    5.822128] iwlwifi 0000:00:14.3: 0x004D930E | branchlink2
[    5.822129] iwlwifi 0000:00:14.3: 0x004CF3DA | interruptlink1
[    5.822130] iwlwifi 0000:00:14.3: 0x004CF3DA | interruptlink2
[    5.822131] iwlwifi 0000:00:14.3: 0x0001556A | data1
[    5.822132] iwlwifi 0000:00:14.3: 0x00000010 | data2
[    5.822132] iwlwifi 0000:00:14.3: 0x00000000 | data3
[    5.822133] iwlwifi 0000:00:14.3: 0x00000000 | beacon time
[    5.822134] iwlwifi 0000:00:14.3: 0x0001838C | tsf low
[    5.822135] iwlwifi 0000:00:14.3: 0x00000000 | tsf hi
[    5.822135] iwlwifi 0000:00:14.3: 0x00000000 | time gp1
[    5.822136] iwlwifi 0000:00:14.3: 0x00023B24 | time gp2
[    5.822137] iwlwifi 0000:00:14.3: 0x00000001 | uCode revision type
[    5.822138] iwlwifi 0000:00:14.3: 0x0000004D | uCode version major
[    5.822139] iwlwifi 0000:00:14.3: 0xF92B5FED | uCode version minor
[    5.822140] iwlwifi 0000:00:14.3: 0x00000370 | hw version
[    5.822140] iwlwifi 0000:00:14.3: 0x00C80002 | board version
[    5.822141] iwlwifi 0000:00:14.3: 0x8057FF00 | hcmd
[    5.822142] iwlwifi 0000:00:14.3: 0x00020000 | isr0
[    5.822143] iwlwifi 0000:00:14.3: 0x00000000 | isr1
[    5.822143] iwlwifi 0000:00:14.3: 0x48F00002 | isr2
[    5.822144] iwlwifi 0000:00:14.3: 0x00C3000C | isr3
[    5.822145] iwlwifi 0000:00:14.3: 0x00000000 | isr4
[    5.822146] iwlwifi 0000:00:14.3: 0x00000000 | last cmd Id
[    5.822147] iwlwifi 0000:00:14.3: 0x0001556A | wait_event
[    5.822147] iwlwifi 0000:00:14.3: 0x00000000 | l2p_control
[    5.822148] iwlwifi 0000:00:14.3: 0x00000000 | l2p_duration
[    5.822149] iwlwifi 0000:00:14.3: 0x00000000 | l2p_mhvalid
[    5.822149] iwlwifi 0000:00:14.3: 0x00000000 | l2p_addr_match
[    5.822150] iwlwifi 0000:00:14.3: 0x00000018 | lmpm_pmg_sel
[    5.822151] iwlwifi 0000:00:14.3: 0x00000000 | timestamp
[    5.822152] iwlwifi 0000:00:14.3: 0x00001034 | flow_handler
[    5.822200] iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
[    5.822201] iwlwifi 0000:00:14.3: Transport status: 0x0000004B, valid: 7
[    5.822202] iwlwifi 0000:00:14.3: 0x201002FD | ADVANCED_SYSASSERT
[    5.822203] iwlwifi 0000:00:14.3: 0x00000000 | umac branchlink1
[    5.822204] iwlwifi 0000:00:14.3: 0x8046CE44 | umac branchlink2
[    5.822204] iwlwifi 0000:00:14.3: 0xC00814B0 | umac interruptlink1
[    5.822205] iwlwifi 0000:00:14.3: 0x00000000 | umac interruptlink2
[    5.822206] iwlwifi 0000:00:14.3: 0x0014020B | umac data1
[    5.822206] iwlwifi 0000:00:14.3: 0x00000308 | umac data2
[    5.822207] iwlwifi 0000:00:14.3: 0x00000304 | umac data3
[    5.822208] iwlwifi 0000:00:14.3: 0x0000004D | umac major
[    5.822208] iwlwifi 0000:00:14.3: 0xF92B5FED | umac minor
[    5.822209] iwlwifi 0000:00:14.3: 0x00023B1E | frame pointer
[    5.822210] iwlwifi 0000:00:14.3: 0xC0886C24 | stack pointer
[    5.822210] iwlwifi 0000:00:14.3: 0x0014020B | last host cmd
[    5.822211] iwlwifi 0000:00:14.3: 0x00000000 | isr status reg
[    5.822250] iwlwifi 0000:00:14.3: IML/ROM dump:
[    5.822251] iwlwifi 0000:00:14.3: 0x00000B03 | IML/ROM error/state
[    5.822259] iwlwifi 0000:00:14.3: 0x000050AE | IML/ROM data1
[    5.822268] iwlwifi 0000:00:14.3: 0x00000090 | IML/ROM WFPM_AUTH_KEY_0
[    5.822273] iwlwifi 0000:00:14.3: Fseq Registers:
[    5.822275] iwlwifi 0000:00:14.3: 0x60000000 | FSEQ_ERROR_CODE
[    5.822278] iwlwifi 0000:00:14.3: 0x80350002 | FSEQ_TOP_INIT_VERSION
[    5.822281] iwlwifi 0000:00:14.3: 0x00150000 | FSEQ_CNVIO_INIT_VERSION
[    5.822283] iwlwifi 0000:00:14.3: 0x0000A482 | FSEQ_OTP_VERSION
[    5.822286] iwlwifi 0000:00:14.3: 0x00000003 | FSEQ_TOP_CONTENT_VERSION
[    5.822289] iwlwifi 0000:00:14.3: 0x4552414E | FSEQ_ALIVE_TOKEN
[    5.822291] iwlwifi 0000:00:14.3: 0x00080400 | FSEQ_CNVI_ID
[    5.822294] iwlwifi 0000:00:14.3: 0x00000501 | FSEQ_CNVR_ID
[    5.822296] iwlwifi 0000:00:14.3: 0x00080400 | CNVI_AUX_MISC_CHIP
[    5.822301] iwlwifi 0000:00:14.3: 0x00000501 | CNVR_AUX_MISC_CHIP
[    5.822306] iwlwifi 0000:00:14.3: 0x05B0905B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[    5.822311] iwlwifi 0000:00:14.3: 0x0000025B | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[    5.822313] iwlwifi 0000:00:14.3: UMAC CURRENT PC: 0xd05c18
[    5.822314] iwlwifi 0000:00:14.3: LMAC1 CURRENT PC: 0xd05c1c
[    5.822316] iwlwifi 0000:00:14.3: Starting mac, retry will be triggered anyway
[    5.822346] iwlwifi 0000:00:14.3: FW error in SYNC CMD RFI_CONFIG_CMD
[    5.822349] CPU: 0 PID: 1960 Comm: dhcpcd Not tainted 6.4.0-rc2 #1
[    5.822351] Hardware name: AZW EQ/EQ, BIOS N95V104 03/17/2023
[    5.822353] Call Trace:
[    5.822355]  <TASK>
[    5.822356]  dump_stack_lvl+0x36/0x50
[    5.822360]  iwl_trans_txq_send_hcmd+0x338/0x450
[    5.822364]  ? __pfx_autoremove_wake_function+0x10/0x10
[    5.822367]  iwl_trans_send_cmd+0x61/0xf0
[    5.822369]  iwl_mvm_send_cmd+0x11/0x40
[    5.822371]  iwl_rfi_send_config_cmd+0xf0/0x190
[    5.822373]  ? acpi_os_release_object+0x9/0x10
[    5.822377]  iwl_mvm_up+0xbff/0xc50
[    5.822380]  ? __iwl_mvm_mac_start+0x5a/0x200
[    5.822382]  __iwl_mvm_mac_start+0x5a/0x200
[    5.822384]  iwl_mvm_mac_start+0x74/0x130
[    5.822385]  drv_start+0x3a/0x100
[    5.822387]  ieee80211_do_open+0x315/0x780
[    5.822390]  ieee80211_open+0x65/0x80
[    5.822392]  __dev_open+0xec/0x1a0
[    5.822394]  __dev_change_flags+0x1aa/0x220
[    5.822396]  dev_change_flags+0x21/0x60
[    5.822397]  devinet_ioctl+0x30e/0x7c0
[    5.822399]  inet_ioctl+0x1c7/0x1e0
[    5.822401]  sock_ioctl+0x2f3/0x3d0
[    5.822405]  ? security_file_ioctl+0x38/0x60
[    5.822407]  __x64_sys_ioctl+0x505/0xa10
[    5.822410]  do_syscall_64+0x3c/0x90
[    5.822412]  entry_SYSCALL_64_after_hwframe+0x72/0xdc
[    5.822414] RIP: 0033:0x7fb18c29ac2b
[    5.822417] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <3d> 00 f0 ff ff 89 c2 77 1c 48 8b 44 24 18 64 48 2b 04 25 28 00>
[    5.822418] RSP: 002b:00007ffd85ac1ac0 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
[    5.822420] RAX: ffffffffffffffda RBX: 0000000000001043 RCX: 00007fb18c29ac2b
[    5.822421] RDX: 00007ffd85ac1b20 RSI: 0000000000008914 RDI: 000000000000000c
[    5.822422] RBP: 000055fb1151eba0 R08: 000000000417ce4b R09: 000000003782fbb5
[    5.822423] R10: 00007ffd85bf8080 R11: 0000000000000246 R12: 00007ffd85ac1b20
[    5.822424] R13: 0000000000000000 R14: 00007ffd85ac1c18 R15: 0000000000000000
[    5.822425]  </TASK>
[    5.822426] iwlwifi 0000:00:14.3: Failed to send RFI config cmd -5
[    5.822431] iwlwifi 0000:00:14.3: Failed to send MAC_CONFIG_CMD (action:1): -5
Top
CooSee
Veteran
Veteran
User avatar
Posts: 1617
Joined: Sat Nov 20, 2004 10:38 pm
Location: right here !

  • Quote

Post by CooSee » Tue May 16, 2023 3:26 am

which device are you using ? - BIOS is current ?

please re-emerge sys-kernel/linux-firmware-99999999 to get sure you've current up-to-date tree.

try with https://gpo.zugaina.org/sys-kernel/clear-sources - Clear OS is from Intel anyway - i hope there'll be a difference.

i assume you already read this https://wireless.wiki.kernel.org/en/use ... rs/iwlwifi

... fingers crossed !

8)
" Die Realität ist eine Illusion, die durch Mangel an ehrlicher Kommunikation entsteht "
---
" Der Mensch ist von Natur aus neugierig, was am Ende übrig bleibt ist die Gier "
Top
n1ese
Tux's lil' helper
Tux's lil' helper
Posts: 87
Joined: Sun Sep 29, 2019 3:25 pm

  • Quote

Post by n1ese » Tue May 16, 2023 8:03 am

CooSee wrote:which device are you using ? - BIOS is current ?
It's a brand new Mini-PC from Beelink that just hit the market in March. It uses the new Intel N305 CPU.
CooSee wrote:please re-emerge sys-kernel/linux-firmware-99999999 to get sure you've current up-to-date tree.
Yes, I watch the linux-firmware github closely for chages as well.
CooSee wrote:try with https://gpo.zugaina.org/sys-kernel/clear-sources - Clear OS is from Intel anyway - i hope there'll be a difference.
I actually emailed the linux-wireless kernel mailing list since I'm now using kernel 6.4 and they replied asking me to try this patch:

https://patchwork.kernel.org/project/li ... @changeid/

I just woke up a few minutes ago, haven't tried it yet.. need some more coffee in me first.
Top
n1ese
Tux's lil' helper
Tux's lil' helper
Posts: 87
Joined: Sun Sep 29, 2019 3:25 pm

  • Quote

Post by n1ese » Tue May 16, 2023 8:39 am

Sweet, applied the patch I mentioned above to 6.4.0-rc2 and the wifi side of the AX101 is now working very nicely. Now, onward to try and fix the bluetooth side of things.
Top
n1ese
Tux's lil' helper
Tux's lil' helper
Posts: 87
Joined: Sun Sep 29, 2019 3:25 pm

  • Quote

Post by n1ese » Tue May 16, 2023 9:59 am

Ok, bluetooth is now finally working as well. It is being detected as an AX201 and wants firmware not currently in the tree, ibt-0040-1050.sfi, so I just copied one of the older AX201 firmware files, ibt-1040-4150, to the new names and it is now working fine with the bluetooth devices I need.
Top
logrusx
Advocate
Advocate
User avatar
Posts: 3534
Joined: Thu Feb 22, 2018 2:29 pm

  • Quote

Post by logrusx » Tue May 16, 2023 11:50 am

n1ese wrote:Ok, bluetooth is now finally working as well. It is being detected as an AX201 and wants firmware not currently in the tree, ibt-0040-1050.sfi, so I just copied one of the older AX201 firmware files, ibt-1040-4150, to the new names and it is now working fine with the bluetooth devices I need.
It asks for the latest version the driver supports but will work with older ones, you don't need to rename firmware files.

Best Regards,
Georgi
Top
n1ese
Tux's lil' helper
Tux's lil' helper
Posts: 87
Joined: Sun Sep 29, 2019 3:25 pm

  • Quote

Post by n1ese » Tue May 16, 2023 11:57 am

logrusx wrote:It asks for the latest version the driver supports but will work with older ones, you don't need to rename firmware
For whatever reason, not in my case, the firmware loader was asking for one, and only one, specific firmware file not in the current tree.

Code: Select all

 [    3.024210] Bluetooth: hci0: Device revision is 2 
[    3.024214] Bluetooth: hci0: Secure boot is enabled 
[    3.024215] Bluetooth: hci0: OTP lock is enabled 
[    3.024216] Bluetooth: hci0: API lock is enabled 
[    3.024217] Bluetooth: hci0: Debug lock is disabled 
[    3.024218] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 
[    3.024219] Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 38 
[    3.024223] Loading firmware: intel/ibt-0040-1050.sfi 
[    3.024702] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-0040-1050.sfi (-2)
Top
Post Reply

20 posts • Page 1 of 1

Return to “Kernel & Hardware”

Jump to
  • Assistance
  • ↳   News & Announcements
  • ↳   Frequently Asked Questions
  • ↳   Installing Gentoo
  • ↳   Multimedia
  • ↳   Desktop Environments
  • ↳   Networking & Security
  • ↳   Kernel & Hardware
  • ↳   Portage & Programming
  • ↳   Gamers & Players
  • ↳   Other Things Gentoo
  • ↳   Unsupported Software
  • Discussion & Documentation
  • ↳   Documentation, Tips & Tricks
  • ↳   Gentoo Chat
  • ↳   Gentoo Forums Feedback
  • ↳   Duplicate Threads
  • International Gentoo Users
  • ↳   中文 (Chinese)
  • ↳   Dutch
  • ↳   Finnish
  • ↳   French
  • ↳   Deutsches Forum (German)
  • ↳   Diskussionsforum
  • ↳   Deutsche Dokumentation
  • ↳   Greek
  • ↳   Forum italiano (Italian)
  • ↳   Forum di discussione italiano
  • ↳   Risorse italiane (documentazione e tools)
  • ↳   Polskie forum (Polish)
  • ↳   Instalacja i sprzęt
  • ↳   Polish OTW
  • ↳   Portuguese
  • ↳   Documentação, Ferramentas e Dicas
  • ↳   Russian
  • ↳   Scandinavian
  • ↳   Spanish
  • ↳   Other Languages
  • Architectures & Platforms
  • ↳   Gentoo on ARM
  • ↳   Gentoo on PPC
  • ↳   Gentoo on Sparc
  • ↳   Gentoo on Alternative Architectures
  • ↳   Gentoo on AMD64
  • ↳   Gentoo for Mac OS X (Portage for Mac OS X)
  • Board index
  • All times are UTC
  • Delete cookies

© 2001–2026 Gentoo Foundation, Inc.

Powered by phpBB® Forum Software © phpBB Limited

Privacy Policy

 

 

magic