Intel 7260

n2linux · 03-29-2024, 06:03 PM

Unable to get Intel 7260 wireless to work in linux. Dual booting with Windows 11. Card works fine in Windows. dmesg shows "Failed to send DQA enabling command: -5". Fiddled with it a week now. Scoured a number of forums. I read where the (rev bb) could be problematic. But also got hints that some had it working. Any help here would be appreciated.

Code:

┌─[root@alienware-m15-R5]-[/]
└──╼ #inxi -SEMN
System:
  Host: alienware-m15-R5 Kernel: 6.5.0-26-generic x86_64 bits: 64
    Desktop: Cinnamon 6.0.4 Distro: Linux Mint 21.3 Virginia
Machine:
  Type: Laptop System: Alienware product: Alienware m15 Ryzen Ed. R5
    v: 1.17.0 serial: 6YL08F3
  Mobo: Alienware model: 0F8CRX v: A00 serial: .6YL08F3.CNCMC0015D01D4.
    UEFI: Alienware v: 1.17.0 date: 01/09/2024
Network:
  Device-1: Realtek RTL8125 2.5GbE driver: r8169
  Device-2: Intel Wireless 7260 driver: iwlwifi
  Device-3: MediaTek WiFi type: USB driver: mt76x0u
Bluetooth:
  Device-1: Intel Bluetooth wireless interface type: USB driver: btusb
  Report: hciconfig ID: hci0 state: up address: 58:91:CF:71:F5:97 bt-v: 2.1

Code:

┌─[root@alienware-m15-R5]-[/]
└──╼ #lspci | grep 7260
03:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)

Code:

┌─[root@alienware-m15-R5]-[/]
└──╼ #iwconfig wlp3s0
wlp3s0    IEEE 802.11  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:on

Code:

┌─[root@alienware-m15-R5]-[/]
└──╼ #mokutil --sb-state
SecureBoot enabled

Code:

┌─[root@alienware-m15-R5]-[/]
└──╼ #rfkill list all
0: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no
1: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no
2: phy1: Wireless LAN
	Soft blocked: no
	Hard blocked: no

Code:

┌─[root@alienware-m15-R5]-[/]
└──╼ #dmesg | grep iwlwifi
[   82.374287] iwlwifi 0000:03:00.0: Microcode SW error detected.  Restarting 0x2000000.
[   82.374399] iwlwifi 0000:03:00.0: Start IWL Error Log Dump:
[   82.374402] iwlwifi 0000:03:00.0: Transport status: 0x0000004B, valid: 6
[   82.374405] iwlwifi 0000:03:00.0: Loaded firmware version: 17.3216344376.0 7260-17.ucode
[   82.374408] iwlwifi 0000:03:00.0: 0x00000038 | BAD_COMMAND                 
[   82.374411] iwlwifi 0000:03:00.0: 0x000002F0 | trm_hw_status0
[   82.374413] iwlwifi 0000:03:00.0: 0x00000000 | trm_hw_status1
[   82.374416] iwlwifi 0000:03:00.0: 0x00000B30 | branchlink2
[   82.374418] iwlwifi 0000:03:00.0: 0x000164C0 | interruptlink1
[   82.374420] iwlwifi 0000:03:00.0: 0x00000000 | interruptlink2
[   82.374423] iwlwifi 0000:03:00.0: 0xDEADBEEF | data1
[   82.374425] iwlwifi 0000:03:00.0: 0xDEADBEEF | data2
[   82.374427] iwlwifi 0000:03:00.0: 0xDEADBEEF | data3
[   82.374429] iwlwifi 0000:03:00.0: 0x003FECAF | beacon time
[   82.374431] iwlwifi 0000:03:00.0: 0x0000134F | tsf low
[   82.374434] iwlwifi 0000:03:00.0: 0x00000000 | tsf hi
[   82.374436] iwlwifi 0000:03:00.0: 0x00000000 | time gp1
[   82.374438] iwlwifi 0000:03:00.0: 0x00001350 | time gp2
[   82.374440] iwlwifi 0000:03:00.0: 0x00000000 | uCode revision type
[   82.374442] iwlwifi 0000:03:00.0: 0x00000011 | uCode version major
[   82.374445] iwlwifi 0000:03:00.0: 0xBFB58538 | uCode version minor
[   82.374447] iwlwifi 0000:03:00.0: 0x00000144 | hw version
[   82.374449] iwlwifi 0000:03:00.0: 0x40489204 | board version
[   82.374451] iwlwifi 0000:03:00.0: 0x00130C01 | hcmd
[   82.374454] iwlwifi 0000:03:00.0: 0x00022080 | isr0
[   82.374456] iwlwifi 0000:03:00.0: 0x00000000 | isr1
[   82.374458] iwlwifi 0000:03:00.0: 0x00000002 | isr2
[   82.374460] iwlwifi 0000:03:00.0: 0x00400000 | isr3
[   82.374462] iwlwifi 0000:03:00.0: 0x00000000 | isr4
[   82.374464] iwlwifi 0000:03:00.0: 0x01000002 | last cmd Id
[   82.374467] iwlwifi 0000:03:00.0: 0x00000000 | wait_event
[   82.374469] iwlwifi 0000:03:00.0: 0x0000453F | l2p_control
[   82.374471] iwlwifi 0000:03:00.0: 0x00000000 | l2p_duration
[   82.374473] iwlwifi 0000:03:00.0: 0x00000000 | l2p_mhvalid
[   82.374476] iwlwifi 0000:03:00.0: 0x00000000 | l2p_addr_match
[   82.374478] iwlwifi 0000:03:00.0: 0x00000007 | lmpm_pmg_sel
[   82.374480] iwlwifi 0000:03:00.0: 0x15041745 | timestamp
[   82.374482] iwlwifi 0000:03:00.0: 0x00001020 | flow_handler
[   82.374485] iwlwifi 0000:03:00.0: Fseq Registers:
[   82.374508] iwlwifi 0000:03:00.0: 0x00000000 | FSEQ_ERROR_CODE
[   82.374535] iwlwifi 0000:03:00.0: 0x00000000 | FSEQ_TOP_INIT_VERSION
[   82.374562] iwlwifi 0000:03:00.0: 0x00000000 | FSEQ_CNVIO_INIT_VERSION
[   82.374589] iwlwifi 0000:03:00.0: 0x00000000 | FSEQ_OTP_VERSION
[   82.374617] iwlwifi 0000:03:00.0: 0x00000000 | FSEQ_TOP_CONTENT_VERSION
[   82.374644] iwlwifi 0000:03:00.0: 0x00000000 | FSEQ_ALIVE_TOKEN
[   82.374671] iwlwifi 0000:03:00.0: 0x00000000 | FSEQ_CNVI_ID
[   82.374698] iwlwifi 0000:03:00.0: 0x00000000 | FSEQ_CNVR_ID
[   82.374725] iwlwifi 0000:03:00.0: 0x00000000 | CNVI_AUX_MISC_CHIP
[   82.374752] iwlwifi 0000:03:00.0: 0x00000000 | CNVR_AUX_MISC_CHIP
[   82.374780] iwlwifi 0000:03:00.0: 0x00000000 | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[   82.374807] iwlwifi 0000:03:00.0: 0x00000000 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[   82.374834] iwlwifi 0000:03:00.0: 0x00000000 | FSEQ_PREV_CNVIO_INIT_VERSION
[   82.374861] iwlwifi 0000:03:00.0: 0x00000000 | FSEQ_WIFI_FSEQ_VERSION
[   82.374888] iwlwifi 0000:03:00.0: 0x00000000 | FSEQ_BT_FSEQ_VERSION
[   82.374915] iwlwifi 0000:03:00.0: 0x00000000 | FSEQ_CLASS_TP_VERSION
[   82.374919] iwlwifi 0000:03:00.0: Starting mac, retry will be triggered anyway
[   82.374926] iwlwifi 0000:03:00.0: FW error in SYNC CMD UNKNOWN
[   82.374950]  iwl_trans_txq_send_hcmd_sync+0x1d5/0x370 [iwlwifi]
[   82.374977]  iwl_trans_txq_send_hcmd+0xb8/0x170 [iwlwifi]
[   82.374995]  iwl_trans_send_cmd+0x81/0x110 [iwlwifi]
[   82.375083]  ? __iwl_err+0x18a/0x1a0 [iwlwifi]
[   82.375392] iwlwifi 0000:03:00.0: Failed to send DQA enabling command: -5
[   82.392602] iwlwifi 0000:03:00.0: mac start retry 2

business_kid · 03-30-2024, 07:24 AM

Hello, n2linux & welcome to LQ.

You appear to have two wifi cards. Does the other one work? Why not use that? Do you use networkmanager or init scripts to setup your network stuff?

Please post the output of iwconfig. This 'solve your problem' trick only works if you explain your setup well and do what's asked of you.

n2linux · 03-30-2024, 08:01 AM

Yes, I do have a second wireless. When I couldn't get the internal wireless card to work, I bought a Panda Wireless USB nub as an interim solution. It works, but I'd really like to get the internal card working on Linux and free up the USB port. I also have other Linux projects that the Panda Wireless nub could be useful on.

Here is the full iwconfig results...

Code:

┌─[root@alienware-m15-R5]-[/]
└──╼ #iwconfig
lo        no wireless extensions.

enp2s0    no wireless extensions.

wlp3s0    IEEE 802.11  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:on
          
wlx9cefd5fb2d60  IEEE 802.11  ESSID:"##########_5G"  
          Mode:Managed  Frequency:5.745 GHz  Access Point: E0:22:03:95:17:62   
          Bit Rate=130 Mb/s   Tx-Power=16 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=39/70  Signal level=-71 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:1  Invalid misc:53   Missed beacon:0

virbr0    no wireless extensions.

I'm using NetworkManager...I have wifi.powersave = 2 set there to stabilize my connection.

Code:

┌─[root@alienware-m15-R5]-[/]
└──╼ #systemctl status NetworkManager
● NetworkManager.service - Network Manager
     Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
     Active: active (running) since Fri 2024-03-29 19:36:52 CDT; 12h ago
       Docs: man:NetworkManager(8)
   Main PID: 1180 (NetworkManager)
      Tasks: 3 (limit: 38044)
     Memory: 10.0M
        CPU: 8.846s
     CGroup: /system.slice/NetworkManager.service
             └─1180 /usr/sbin/NetworkManager --no-daemon

Mar 30 07:28:58 alienware-m15-R5 NetworkManager[1180]: <error> [1711801738.8154] device (wlp3s0): Couldn't initialize s>
Mar 30 07:29:09 alienware-m15-R5 NetworkManager[1180]: <warn>  [1711801749.3978] device (wlp3s0): re-acquiring supplica>

I've also disabled Fast Startup on Windows 11.

business_kid · 03-30-2024, 01:15 PM

It finally dawned on me your problem is the intel part. Mediatek have the bad reputation, but they have cleaned up their act on linux. They even bought Ralink, and cleaned up their act.

There should be linux drivers(source) and firmware on Intel's site if they are needed. There might be module options required for iwlwifi.ko to try. If firmware is online, and it's later than the firmware in /lib/firmware, try it. And do a decent web search. You won't be the only one with this problem. Intel are usually a good buy in wifi cards. Anyone is, EXCEPT REALTEK.

You can also try connecting yourself.

Install wpa_supplicant if you haven't got it in /usr/sbin.
Type this command in a terminal: "wpa_passphrase Your_ESSID Your_Password"
It will give you back a formatted entry for /etc/wpa_supplicant.conf (or /etc/wpa_supplicant/wpa_supplicant.conf)
Edit wpa_supplicant.conf and put in the chunk as is. There's man pages for wpa_supplicant.conf & wpa_passphrase

In a terminal, run this command:

Code:

sudo /usr/sbin/wpa_supplicant -D 80211 -i wlp3s0 -c /path/to/wpa_supplicant.conf

You'll get the output in the terminal and it will stay there. Post the interesting stuff ONLY. In the unlikely event that it stops writing, it has crashed or connected. If connected, grab another terminal and type

Code:

sudo /sbin/dhcpcd wlp3s0 or sudo /sbin/dhclient wlp3s0

You might have one or the other of those programs. If you don't, install one. Post anything you think is odd with a bit of context.

n2linux · 03-30-2024, 09:38 PM

I checked the Intel website earlier and only found iwlwifi-7260-14.ucode available for download. But my laptop has a higher version already installed and in use, iwlwifi-7260-17.ucode.

I also tried wpa-supplicant as suggested and received the following...

Code:

┌─[macos@alienware-m15-R5]-[/lib/firmware]
└──╼ $sudo /usr/sbin/wpa_supplicant -D nl80211 -i wlp3s0 -c /etc/wpa_supplicant/wpa_supplicant.conf
Successfully initialized wpa_supplicant
Could not set interface wlp3s0 flags (UP): Input/output error
nl80211: Could not set interface 'wlp3s0' UP
nl80211: deinit ifname=wlp3s0 disabled_11b_rates=0
wlp3s0: Failed to initialize driver interface
wlp3s0: CTRL-EVENT-DSCP-POLICY clear_all

I'm still digging into the source code references regarding iwlwifi and iwlmvm about DQA (dynamic queue allocation). Even found some current patch activity. Hopefully something will bubble up to the top and give me a clue as to circumventing the failure.

n2linux · 03-30-2024, 11:01 PM

The plot thickens. I downloaded an old Ubuntu 14.04 ISO. It used the iwlwifi-7260-13.ucode firmware. Lo and behold, the Intel 7260 worked. This is not a viable solution, but it does appear to indicate that something in the current kernel or firmware is not playing nice with the Intel 7260 (rev bb) I have.

business_kid · 03-31-2024, 12:00 PM

Quote:

Originally Posted by n2linux

I checked the Intel website earlier and only found iwlwifi-7260-14.ucode available for download. But my laptop has a higher version already installed and in use, iwlwifi-7260-17.ucode.

I also tried wpa-supplicant as suggested and received the following...

Code:

┌─[macos@alienware-m15-R5]-[/lib/firmware]
└──╼ $sudo /usr/sbin/wpa_supplicant -D nl80211 -i wlp3s0 -c /etc/wpa_supplicant/wpa_supplicant.conf
Successfully initialized wpa_supplicant
Could not set interface wlp3s0 flags (UP): Input/output error
nl80211: Could not set interface 'wlp3s0' UP
nl80211: deinit ifname=wlp3s0 disabled_11b_rates=0
wlp3s0: Failed to initialize driver interface
wlp3s0: CTRL-EVENT-DSCP-POLICY clear_all

I'm still digging into the source code references regarding iwlwifi and iwlmvm about DQA (dynamic queue allocation). Even found some current patch activity. Hopefully something will bubble up to the top and give me a clue as to circumventing the failure.

Looking at the wpa_supplicant output above, the nl80211 driver can't configure the wifi [bold type above]. The good news is that there may be an alternative. Try the same wpa_supplicant line, except use '-D wext' and see if that provokes a difference.

Odd that the Intel website doesn't have the latest driver, but they gave it to the Linux community. I wonder is it some linux-specific thing? Have you tried the firmware from the website?

The 'input/output error' is pretty catastrophic, btw. It's often a sign of bad hardware, but not in this case of course. But it's puking on the equivalent of 'ifconfig wlp3s0 up' afaict.

n2linux · 03-31-2024, 12:41 PM

No luck using wext either...

Code:

┌─[macos@alienware-m15-R5]-[~]
└──╼ $sudo /usr/sbin/wpa_supplicant -D wext -i wlp3s0 -c /etc/wpa_supplicant/wpa_supplicant.conf
[sudo] password for macos:          
Successfully initialized wpa_supplicant
Could not set interface wlp3s0 flags (UP): Input/output error
WEXT: Could not set interface 'wlp3s0' UP
wlp3s0: Failed to initialize driver interface
wlp3s0: CTRL-EVENT-DSCP-POLICY clear_all

I'm open to suggestions on using the Intel website firmware. I've hacked away at it, but the driver insists on using iwlwifi-7260-17.ucode. I tried renaming the more current firmware so that the driver would drop down to iwlwifi-7260-13.ucode, but that didn't work.

Code:

[   14.862098] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-7260-17.ucode failed with error -2
[   14.862102] iwlwifi 0000:03:00.0: no suitable firmware found!
[   14.862105] iwlwifi 0000:03:00.0: iwlwifi-7260-17 is required

business_kid · 03-31-2024, 02:01 PM

The linux driver must be checking for the version 17 firmware in the software. The oldest firmware I had around was dated 20220124, and that had the iwlwifi-7260-17.ucode. That was part of the slackware64-15.0 release. That had versions 7,8,9,10,12,13,16 & 17
Your options are:

1. Grit your teeth, join the LKML, and file a bug against the intel driver. You will have to compile very latest kernel version they say, do the tests they need, apply the patches they give you, and report the results. Your pc will be testing their patch. Patience can wear thin quickly on the LKML, but your issue will be fixed. Then you'll have to update to a patched kernel.

2. Approach the same issue through the intel website. Your email will probably go to a windows programmer thence to a linux one. He might well instruct you to do option 1 anyhow.

3. Revert to some older kernel which uses the earlier firmware, with any issues involved there. That might be the original slackware64-5.15.19 kernel and see if that takes earlier firmware. The earlier versions might just be detritis in the firmware archive. I'd be hopeful for iwlwifi-7260-16.

4. Forget the whole thing and continue using the Mediatek usb wifi in linux.

n2linux · 03-31-2024, 03:08 PM

Option #4 made me laugh. But that's my likely route. I think its the (rev bb) that's the issue. There are a number of 7260 flavors out there and the (rev bb) has been problematic for others in the past. I appreciate your time and responses. If I get adventurous, I may replace the card down the road. And if it turns out I'm not alone and others are experiencing this issue, I may circle back to the other options you mention. Linux is my main driver, I enjoy using it, and on principle I'd like to see it work out of the box for others.

business_kid · 04-01-2024, 04:07 AM

How's about option

5. Revert to the older firmware without the older kernel? There isn't a direct tie, like kernel & modules?

And the new stuff going into the kernel is usually oddball stuff we don't have. Have you ever had to wait for a device to work because the firmware wasn't written yet? It's part of the hardware design process, because the device won't function without the firmware.

replica9000 · 04-01-2024, 09:47 PM

Not an ideal solution, but can you replace the 7260, assuming there's no whitelist?

The 7260 is known to be a bit buggy under both Linux and Windows. I had replaced a couple with the 8260 and the issues I was having went away. (frequent/random disconnects)

You can get a newer Intel Wi-Fi card for about $25.

n2linux · 04-02-2024, 07:15 AM

Thanks for noting a possible replacement. I was thinking I might replace the 7260 at some point. But then the question was "with what?". Glad to hear the 8260 has worked for you.

business_kid · 04-02-2024, 08:36 AM

Quote:

Originally Posted by n2linux

Thanks for noting a possible replacement. I was thinking I might replace the 7260 at some point. But then the question was "with what?". Glad to hear the 8260 has worked for you.

Here's another: Qualcomm Atheros - any one. Here's mine:

Code:

04:00.0 Network controller: Qualcomm Atheros AR9462 Wireless Network Adapter (rev 01)

My laptop has the AR9452. All the features too, like a good range of 5GHz frequencies, as the ones allowed vary a lot across the planet widely.