Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Help] Driver Crash : ALFA AWUS036AXML #533

Open
2 tasks done
KaliAssistant opened this issue Nov 7, 2024 · 16 comments
Open
2 tasks done

[Help] Driver Crash : ALFA AWUS036AXML #533

KaliAssistant opened this issue Nov 7, 2024 · 16 comments

Comments

@KaliAssistant
Copy link

KaliAssistant commented Nov 7, 2024

Checklist

  • I acknowledge that support is provided on a best-effort basis.
  • I acknowledge that the authors and contributors to this repository cannot be held responsible for the results of my use of any information contained in or linked from this repository.

uname

Linux KALIworkNB1 6.11.2-amd64 #1 SMP PREEMPT_DYNAMIC Kali 6.11.2-1kali1 (2024-10-15) x86_64 GNU/Linux

lsusb

Bus 001 Device 002: ID 0408:4033 Quanta Computer, Inc. ACER HD User Facing 
Bus 001 Device 003: ID 04ca:3802 Lite-On Technology Corp. Wireless_Device 
^C (endless)

rfkill

0: acer-wireless: Wireless LAN
	Soft blocked: no
	Hard blocked: no
1: acer-bluetooth: Bluetooth
	Soft blocked: no
	Hard blocked: no
2: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no
3: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no

dkms

8812au/5.6.4.2_35491.20191025, 6.10.11-amd64, x86_64: installed
8812au/5.6.4.2_35491.20191025, 6.11.2-amd64, x86_64: installed
acpi_ec/v1.0.4, 6.10.11-amd64, x86_64: installed
acpi_ec/v1.0.4, 6.11.2-amd64, x86_64: installed
acpi_ec/v1.0.4, 6.6.9-amd64, x86_64: installed

iw

phy#0
	Interface wlan0 <-----(not this, it is my pcie nic)
		ifindex 3
		wdev 0x1
		addr 9c:2f:9d:79:4c:ab
		type managed
		channel 161 (5805 MHz), width: 80 MHz, center1: 5775 MHz
		txpower 3.00 dBm
		multicast TXQ:
			qsz-byt	qsz-pkt	flows	drops	marks	overlmt	hashcol	tx-bytes	tx-packets
			0	0	0	0	0	0	0	0		0

What happened?

I have a ALFA AWUS036AXML, but when i plug in to my laptop (kali linux 6.11.2) USB3.0, driver crashed:

[ 3289.963601] usb 1-5: new high-speed USB device number 4 using xhci_hcd
[ 3290.113355] usb 1-5: New USB device found, idVendor=0e8d, idProduct=7961, bcdDevice= 1.00
[ 3290.113360] usb 1-5: New USB device strings: Mfr=6, Product=7, SerialNumber=8
[ 3290.113361] usb 1-5: Product: Wireless_Device
[ 3290.113362] usb 1-5: Manufacturer: MediaTek Inc.
[ 3290.113363] usb 1-5: SerialNumber: 000000000
[ 3290.196559] Bluetooth: hci1: HW/SW Version: 0x008a008a, Build Time: 20240219111427
[ 3317.419927] Bluetooth: hci1: command 0xfd98 tx timeout
[ 3317.419939] Bluetooth: hci1: failed to reset (-19)
[ 3317.419987] Bluetooth: hci1: Failed to apply iso setting (-110)
[ 3317.419991] Bluetooth: hci1: Device setup in 26651826 usecs
[ 3317.419992] Bluetooth: hci1: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
[ 3319.435952] Bluetooth: hci1: Opcode 0x0c03 failed: -110
[ 3319.436229] list_del corruption, ffff8f73d475a000->next is LIST_POISON1 (dead000000000100)
[ 3319.436242] ------------[ cut here ]------------
[ 3319.436243] kernel BUG at lib/list_debug.c:56!
[ 3319.436248] Oops: invalid opcode: 0000 [#1] PREEMPT SMP NOPTI
[ 3319.436252] CPU: 8 UID: 0 PID: 685 Comm: kworker/8:2 Tainted: G           OE      6.11.2-amd64 #1  Kali 6.11.2-1kali1
[ 3319.436255] Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
[ 3319.436260] Hardware name: Acer Aspire A515-57/Ganymede_ADU, BIOS V1.16 08/16/2022
[ 3319.436262] Workqueue: usb_hub_wq hub_event [usbcore]
[ 3319.436294] RIP: 0010:__list_del_entry_valid_or_report.cold+0x5c/0x6f
[ 3319.436298] Code: e8 68 60 fe ff 0f 0b 48 89 fe 48 89 ca 48 c7 c7 40 34 54 8d e8 54 60 fe ff 0f 0b 48 89 fe 48 c7 c7 08 34 54 8d e8 43 60 fe ff <0f> 0b 48 89 fe 48 c7 c7 d8 33 54 8d e8 32 60 fe ff 0f 0b 4d 8b 4c
[ 3319.436300] RSP: 0000:ffffadcbc0a67778 EFLAGS: 00010246
[ 3319.436302] RAX: 000000000000004e RBX: ffff8f73d475a000 RCX: 0000000000000000
[ 3319.436303] RDX: 0000000000000000 RSI: ffff8f78d7621780 RDI: ffff8f78d7621780
[ 3319.436304] RBP: ffff8f73d475a4d0 R08: 0000000000000000 R09: ffffadcbc0a67608
[ 3319.436305] R10: ffffffff8dcb41e8 R11: 0000000000000003 R12: ffff8f73d475a000
[ 3319.436306] R13: ffffffffc15e5278 R14: ffffffffc15e5278 R15: ffff8f7350ff3c50
[ 3319.436308] FS:  0000000000000000(0000) GS:ffff8f78d7600000(0000) knlGS:0000000000000000
[ 3319.436309] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 3319.436310] CR2: 00007f2d59e173e8 CR3: 000000010c44c000 CR4: 0000000000f50ef0
[ 3319.436312] PKRU: 55555554
[ 3319.436313] Call Trace:
[ 3319.436315]  <TASK>
[ 3319.436317]  ? __die_body.cold+0x19/0x27
[ 3319.436319]  ? die+0x2e/0x50
[ 3319.436322]  ? do_trap+0xca/0x110
[ 3319.436325]  ? do_error_trap+0x6a/0x90
[ 3319.436326]  ? __list_del_entry_valid_or_report.cold+0x5c/0x6f
[ 3319.436328]  ? exc_invalid_op+0x50/0x70
[ 3319.436331]  ? __list_del_entry_valid_or_report.cold+0x5c/0x6f
[ 3319.436332]  ? asm_exc_invalid_op+0x1a/0x20
[ 3319.436339]  ? __list_del_entry_valid_or_report.cold+0x5c/0x6f
[ 3319.436340]  ? __list_del_entry_valid_or_report.cold+0x5c/0x6f
[ 3319.436342]  hci_unregister_dev+0x46/0x1f0 [bluetooth]
[ 3319.436377]  btusb_disconnect+0x67/0x170 [btusb]
[ 3319.436381]  usb_unbind_interface+0x90/0x290 [usbcore]
[ 3319.436397]  device_release_driver_internal+0x19c/0x200
[ 3319.436401]  usb_forced_unbind_intf+0x75/0xb0 [usbcore]
[ 3319.436415]  usb_reset_device+0xe8/0x290 [usbcore]
[ 3319.436430]  mt7921u_probe+0xab/0x230 [mt7921u]
[ 3319.436433]  usb_probe_interface+0xe5/0x2b0 [usbcore]
[ 3319.436447]  ? __pfx___device_attach_driver+0x10/0x10
[ 3319.436449]  really_probe+0xdb/0x340
[ 3319.436452]  ? pm_runtime_barrier+0x54/0x90
[ 3319.436455]  __driver_probe_device+0x78/0x110
[ 3319.436457]  driver_probe_device+0x1f/0xa0
[ 3319.436459]  __device_attach_driver+0x89/0x110
[ 3319.436462]  bus_for_each_drv+0x95/0xf0
[ 3319.436465]  __device_attach+0xb0/0x1b0
[ 3319.436467]  bus_probe_device+0x8d/0xa0
[ 3319.436469]  device_add+0x664/0x870
[ 3319.436471]  usb_set_configuration+0x5c9/0x860 [usbcore]
[ 3319.436487]  ? __pfx___device_attach_driver+0x10/0x10
[ 3319.436489]  usb_generic_driver_probe+0x42/0x60 [usbcore]
[ 3319.436503]  usb_probe_device+0x3e/0x120 [usbcore]
[ 3319.436517]  really_probe+0xdb/0x340
[ 3319.436519]  ? pm_runtime_barrier+0x54/0x90
[ 3319.436521]  __driver_probe_device+0x78/0x110
[ 3319.436524]  driver_probe_device+0x1f/0xa0
[ 3319.436526]  __device_attach_driver+0x89/0x110
[ 3319.436528]  bus_for_each_drv+0x95/0xf0
[ 3319.436530]  __device_attach+0xb0/0x1b0
[ 3319.436533]  bus_probe_device+0x8d/0xa0
[ 3319.436534]  device_add+0x664/0x870
[ 3319.436536]  usb_new_device.cold+0x141/0x38f [usbcore]
[ 3319.436552]  hub_event+0x11ae/0x19d0 [usbcore]
[ 3319.436565]  ? __schedule+0x3df/0xaf0
[ 3319.436567]  process_one_work+0x174/0x330
[ 3319.436570]  worker_thread+0x252/0x390
[ 3319.436573]  ? __pfx_worker_thread+0x10/0x10
[ 3319.436575]  kthread+0xcf/0x100
[ 3319.436578]  ? __pfx_kthread+0x10/0x10
[ 3319.436580]  ret_from_fork+0x31/0x50
[ 3319.436582]  ? __pfx_kthread+0x10/0x10
[ 3319.436585]  ret_from_fork_asm+0x1a/0x30
[ 3319.436588]  </TASK>
[ 3319.436589] Modules linked in: mt7921u mt792x_usb mt76_usb xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat nf_tables libcrc32c br_netfilter bridge stp llc ppdev vmnet(OE) parport_pc parport vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) ccm rfcomm cmac algif_hash algif_skcipher af_alg overlay qrtr bnep sunrpc binfmt_misc nls_ascii nls_cp437 vfat fat snd_ctl_led snd_soc_skl_hda_dsp snd_soc_hdac_hdmi snd_sof_probes snd_soc_intel_hda_dsp_common snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_hda_scodec_component snd_soc_dmic snd_sof_pci_intel_tgl snd_sof_pci_intel_cnl snd_sof_intel_hda_generic soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda_common snd_sof_intel_hda_mlink snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus intel_uncore_frequency intel_uncore_frequency_common
[ 3319.436633]  mt7921e x86_pkg_temp_thermal snd_soc_avs intel_powerclamp mt7921_common kvm_intel mt792x_lib mt76_connac_lib snd_soc_hda_codec snd_hda_ext_core snd_soc_core mt76 btusb kvm btrtl snd_compress btintel snd_pcm_dmaengine mac80211 btbcm snd_hda_intel btmtk snd_intel_dspcfg snd_intel_sdw_acpi videobuf2_vmalloc uvc bluetooth snd_hda_codec videobuf2_memops libarc4 videobuf2_v4l2 videodev mei_pxp mei_hdcp intel_rapl_msr snd_hda_core rapl snd_hwdep cfg80211 processor_thermal_device_pci intel_cstate videobuf2_common snd_pcm processor_thermal_device iTCO_wdt mc acer_wmi processor_thermal_wt_hint intel_pmc_bxt intel_uncore platform_profile wmi_bmof snd_timer processor_thermal_rfim iTCO_vendor_support ee1004 mei_me pcspkr processor_thermal_rapl watchdog snd rfkill intel_rapl_common ucsi_acpi soundcore mei typec_ucsi processor_thermal_wt_req processor_thermal_power_floor typec igen6_edac processor_thermal_mbox roles int3403_thermal intel_pmc_core int340x_thermal_zone intel_vsec pmt_telemetry int3400_thermal intel_hid
[ 3319.436672]  joydev ac pmt_class acpi_thermal_rel acpi_pad sparse_keymap acer_wireless serio_raw evdev vmwgfx drm_ttm_helper coretemp acpi_ec(OE) configfs efi_pstore nfnetlink efivarfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic ahci libahci libata scsi_mod nvme hid_multitouch hid_generic nvme_core scsi_common i915 drm_buddy i2c_algo_bit drm_display_helper crct10dif_pclmul cec crc32_pclmul rc_core crc32c_intel ttm i2c_hid_acpi i2c_hid drm_kms_helper hid xhci_pci r8169 xhci_hcd realtek ghash_clmulni_intel mdio_devres sha512_ssse3 drm usbcore libphy thunderbolt sha256_ssse3 intel_lpss_pci i2c_i801 sha1_ssse3 i2c_smbus intel_lpss idma64 vmd usb_common fan video battery button wmi aesni_intel gf128mul crypto_simd cryptd [last unloaded: uvcvideo]
[ 3319.436723] ---[ end trace 0000000000000000 ]---
[ 3319.878109] RIP: 0010:__list_del_entry_valid_or_report.cold+0x5c/0x6f
[ 3319.878116] Code: e8 68 60 fe ff 0f 0b 48 89 fe 48 89 ca 48 c7 c7 40 34 54 8d e8 54 60 fe ff 0f 0b 48 89 fe 48 c7 c7 08 34 54 8d e8 43 60 fe ff <0f> 0b 48 89 fe 48 c7 c7 d8 33 54 8d e8 32 60 fe ff 0f 0b 4d 8b 4c
[ 3319.878118] RSP: 0000:ffffadcbc0a67778 EFLAGS: 00010246
[ 3319.878120] RAX: 000000000000004e RBX: ffff8f73d475a000 RCX: 0000000000000000
[ 3319.878121] RDX: 0000000000000000 RSI: ffff8f78d7621780 RDI: ffff8f78d7621780
[ 3319.878122] RBP: ffff8f73d475a4d0 R08: 0000000000000000 R09: ffffadcbc0a67608
[ 3319.878123] R10: ffffffff8dcb41e8 R11: 0000000000000003 R12: ffff8f73d475a000
[ 3319.878124] R13: ffffffffc15e5278 R14: ffffffffc15e5278 R15: ffff8f7350ff3c50
[ 3319.878125] FS:  0000000000000000(0000) GS:ffff8f78d7600000(0000) knlGS:0000000000000000
[ 3319.878127] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 3319.878128] CR2: 00007f2d59e173e8 CR3: 000000010c44c000 CR4: 0000000000f50ef0
[ 3319.878129] PKRU: 55555554
[ 3319.878131] note: kworker/8:2[685] exited with preempt_count 1
@KaliAssistant KaliAssistant changed the title [Help]: Driver Crash : ALFA AWUS036AXML Nov 7, 2024
@KaliAssistant KaliAssistant changed the title Driver Crash : ALFA AWUS036AXML [Help] Driver Crash : ALFA AWUS036AXML Nov 7, 2024
@morrownr
Copy link
Owner

morrownr commented Nov 7, 2024

Hi @KaliAssistant

Several individuals with this adapter have experienced this. It appears that this is a problem caused by a change in bluetooth support which should have nothing to do with this adapter but it does for some reason. You can try deleting the bluetooth firmware:

$ sudo rm /lib/firmware/mediatek/BT_RAM_CODE_MT7961_1_2_hdr.bin

Let me know if this helps.

@KaliAssistant
Copy link
Author

KaliAssistant commented Nov 8, 2024

@morrownr
My laptop pcie wifi is mt7921"e" , wifi and bt(pcie) are working good.
I tried:
mv rm /lib/firmware/mediatek/BT_RAM_CODE_MT7961_1_2_hdr.bin rm /lib/firmware/mediatek/BT_RAM_CODE_MT7961_1_2_hdr.bin.bak

and it still crash.

then i tried:
echo "blacklist btmtk \n blacklist btusb" >> /etc/modprobe.d/blacklist.conf and reboot
its wroking... but my laptop pcie mt7921e will no bt

[    2.470499] usb 4-1: new SuperSpeed USB device number 2 using xhci_hcd
[    2.496392] usb 4-1: New USB device found, idVendor=0e8d, idProduct=7961, bcdDevice= 1.00
[    2.496398] usb 4-1: New USB device strings: Mfr=6, Product=7, SerialNumber=8
[    2.496400] usb 4-1: Product: Wireless_Device
[    2.496401] usb 4-1: Manufacturer: MediaTek Inc.
[    2.496402] usb 4-1: SerialNumber: 000000000
lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0408:4033 Quanta Computer, Inc. ACER HD User Facing
Bus 001 Device 003: ID 04ca:3802 Lite-On Technology Corp. Wireless_Device
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 002: ID 0e8d:7961 MediaTek Inc. Wireless_Device
nmcli dev     
DEVICE         TYPE      STATE                   CONNECTION   
wlan1          wifi      connected               KALIXXXXX
iw phy1 info       
Wiphy phy1
	wiphy index: 1
	max # scan SSIDs: 4
	max scan IEs length: 482 bytes
	max # sched scan SSIDs: 10
	max # match sets: 16
	Retry short limit: 7
	Retry long limit: 4
	Coverage class: 0 (up to 0m)
	Device supports AP-side u-APSD.
	Device supports T-DLS.
	Supported Ciphers:
		* WEP40 (00-0f-ac:1)
		* WEP104 (00-0f-ac:5)
		* TKIP (00-0f-ac:2)
		* CCMP-128 (00-0f-ac:4)
		* CCMP-256 (00-0f-ac:10)
		* GCMP-128 (00-0f-ac:8)
		* GCMP-256 (00-0f-ac:9)
		* CMAC (00-0f-ac:6)
		* CMAC-256 (00-0f-ac:13)
		* GMAC-128 (00-0f-ac:11)
		* GMAC-256 (00-0f-ac:12)
	Available Antennas: TX 0x3 RX 0x3
	Configured Antennas: TX 0x3 RX 0x3
	Supported interface modes:
		* managed
		* AP
		* AP/VLAN
		* monitor
		* P2P-client
		* P2P-GO
	Band 1:
		Capabilities: 0x9ff
			RX LDPC
			HT20/HT40
			SM Power Save disabled
			RX Greenfield
			RX HT20 SGI
			RX HT40 SGI
			TX STBC
			RX STBC 1-stream
			Max AMSDU length: 7935 bytes
			No DSSS/CCK HT40
		Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
		Minimum RX AMPDU time spacing: No restriction (0x00)
		HT TX/RX MCS rate indexes supported: 0-15
		HE Iftypes: managed
			HE MAC Capabilities (0x08011a000040):
				+HTC HE Supported
				Trigger Frame MAC Padding Duration: 2
				OM Control
				Maximum A-MPDU Length Exponent: 3
				A-MSDU in A-MPDU
			HE PHY Capabilities: (0x2270ce120dc0b306423f00):
				HE40/2.4GHz
				242 tone RUs/2.4GHz
				Device Class: 1
				LDPC Coding in Payload
				HE SU PPDU with 1x HE-LTF and 0.8us GI
				NDP with 4x HE-LTF and 3.2us GI
				STBC Tx <= 80MHz
				STBC Rx <= 80MHz
				Full Bandwidth UL MU-MIMO
				Partial Bandwidth UL MU-MIMO
				DCM Max Constellation: 2
				DCM Max Constellation Rx: 2
				SU Beamformee
				Beamformee STS <= 80Mhz: 3
				Ng = 16 SU Feedback
				Ng = 16 MU Feedback
				Codebook Size SU Feedback
				Codebook Size MU Feedback
				Triggered CQI Feedback
				Partial Bandwidth Extended Range
				PPE Threshold Present
				Power Boost Factor ar
				HE SU PPDU & HE PPDU 4x HE-LTF 0.8us GI
				20MHz in 40MHz HE PPDU 2.4GHz
				DCM Max BW: 1
				Longer Than 16HE SIG-B OFDM Symbols
				Non-Triggered CQI Feedback
				TX 1024-QAM
				RX 1024-QAM
				RX Full BW SU Using HE MU PPDU with Compression SIGB
				RX Full BW SU Using HE MU PPDU with Non-Compression SIGB
			HE RX MCS and NSS set <= 80 MHz
				1 streams: MCS 0-11
				2 streams: MCS 0-11
				3 streams: not supported
				4 streams: not supported
				5 streams: not supported
				6 streams: not supported
				7 streams: not supported
				8 streams: not supported
			HE TX MCS and NSS set <= 80 MHz
				1 streams: MCS 0-11
				2 streams: MCS 0-11
				3 streams: not supported
				4 streams: not supported
				5 streams: not supported
				6 streams: not supported
				7 streams: not supported
				8 streams: not supported
			PPE Threshold 0x39 0x1c 0xc7 0x71 0x1c 0x07 
		HE Iftypes: AP
			HE MAC Capabilities (0x00011a081044):
				+HTC HE Supported
				BSR
				OM Control
				Maximum A-MPDU Length Exponent: 3
				BQR
				A-MSDU in A-MPDU
				OM Control UL MU Data Disable RX
			HE PHY Capabilities: (0x0220ce120000a000000c00):
				HE40/2.4GHz
				LDPC Coding in Payload
				NDP with 4x HE-LTF and 3.2us GI
				STBC Tx <= 80MHz
				STBC Rx <= 80MHz
				Full Bandwidth UL MU-MIMO
				Partial Bandwidth UL MU-MIMO
				DCM Max Constellation: 2
				DCM Max Constellation Rx: 2
				Partial Bandwidth Extended Range
				PPE Threshold Present
				TX 1024-QAM
				RX 1024-QAM
			HE RX MCS and NSS set <= 80 MHz
				1 streams: MCS 0-11
				2 streams: MCS 0-11
				3 streams: not supported
				4 streams: not supported
				5 streams: not supported
				6 streams: not supported
				7 streams: not supported
				8 streams: not supported
			HE TX MCS and NSS set <= 80 MHz
				1 streams: MCS 0-11
				2 streams: MCS 0-11
				3 streams: not supported
				4 streams: not supported
				5 streams: not supported
				6 streams: not supported
				7 streams: not supported
				8 streams: not supported
			PPE Threshold 0x39 0x1c 0xc7 0x71 0x1c 0x07 
		Bitrates (non-HT):
			* 1.0 Mbps (short preamble supported)
			* 2.0 Mbps (short preamble supported)
			* 5.5 Mbps (short preamble supported)
			* 11.0 Mbps (short preamble supported)
			* 6.0 Mbps
			* 9.0 Mbps
			* 12.0 Mbps
			* 18.0 Mbps
			* 24.0 Mbps
			* 36.0 Mbps
			* 48.0 Mbps
			* 54.0 Mbps
		Frequencies:
			* 2412.0 MHz [1] (20.0 dBm)
			* 2417.0 MHz [2] (20.0 dBm)
			* 2422.0 MHz [3] (20.0 dBm)
			* 2427.0 MHz [4] (20.0 dBm)
			* 2432.0 MHz [5] (20.0 dBm)
			* 2437.0 MHz [6] (20.0 dBm)
			* 2442.0 MHz [7] (20.0 dBm)
			* 2447.0 MHz [8] (20.0 dBm)
			* 2452.0 MHz [9] (20.0 dBm)
			* 2457.0 MHz [10] (20.0 dBm)
			* 2462.0 MHz [11] (20.0 dBm)
			* 2467.0 MHz [12] (20.0 dBm) (no IR)
			* 2472.0 MHz [13] (20.0 dBm) (no IR)
			* 2484.0 MHz [14] (20.0 dBm)
	Band 2:
		Capabilities: 0x9ff
			RX LDPC
			HT20/HT40
			SM Power Save disabled
			RX Greenfield
			RX HT20 SGI
			RX HT40 SGI
			TX STBC
			RX STBC 1-stream
			Max AMSDU length: 7935 bytes
			No DSSS/CCK HT40
		Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
		Minimum RX AMPDU time spacing: No restriction (0x00)
		HT TX/RX MCS rate indexes supported: 0-15
		VHT Capabilities (0x339071b2):
			Max MPDU length: 11454
			Supported Channel Width: neither 160 nor 80+80
			RX LDPC
			short GI (80 MHz)
			TX STBC
			SU Beamformee
			MU Beamformee
			RX antenna pattern consistency
			TX antenna pattern consistency
		VHT RX MCS set:
			1 streams: MCS 0-9
			2 streams: MCS 0-9
			3 streams: not supported
			4 streams: not supported
			5 streams: not supported
			6 streams: not supported
			7 streams: not supported
			8 streams: not supported
		VHT RX highest supported: 0 Mbps
		VHT TX MCS set:
			1 streams: MCS 0-9
			2 streams: MCS 0-9
			3 streams: not supported
			4 streams: not supported
			5 streams: not supported
			6 streams: not supported
			7 streams: not supported
			8 streams: not supported
		VHT TX highest supported: 0 Mbps
		VHT extended NSS: supported
		HE Iftypes: managed
			HE MAC Capabilities (0x08011a000040):
				+HTC HE Supported
				Trigger Frame MAC Padding Duration: 2
				OM Control
				Maximum A-MPDU Length Exponent: 3
				A-MSDU in A-MPDU
			HE PHY Capabilities: (0x4470ce120dc0b306423f00):
				HE40/HE80/5GHz
				242 tone RUs/5GHz
				Device Class: 1
				LDPC Coding in Payload
				HE SU PPDU with 1x HE-LTF and 0.8us GI
				NDP with 4x HE-LTF and 3.2us GI
				STBC Tx <= 80MHz
				STBC Rx <= 80MHz
				Full Bandwidth UL MU-MIMO
				Partial Bandwidth UL MU-MIMO
				DCM Max Constellation: 2
				DCM Max Constellation Rx: 2
				SU Beamformee
				Beamformee STS <= 80Mhz: 3
				Ng = 16 SU Feedback
				Ng = 16 MU Feedback
				Codebook Size SU Feedback
				Codebook Size MU Feedback
				Triggered CQI Feedback
				Partial Bandwidth Extended Range
				PPE Threshold Present
				Power Boost Factor ar
				HE SU PPDU & HE PPDU 4x HE-LTF 0.8us GI
				20MHz in 40MHz HE PPDU 2.4GHz
				DCM Max BW: 1
				Longer Than 16HE SIG-B OFDM Symbols
				Non-Triggered CQI Feedback
				TX 1024-QAM
				RX 1024-QAM
				RX Full BW SU Using HE MU PPDU with Compression SIGB
				RX Full BW SU Using HE MU PPDU with Non-Compression SIGB
			HE RX MCS and NSS set <= 80 MHz
				1 streams: MCS 0-11
				2 streams: MCS 0-11
				3 streams: not supported
				4 streams: not supported
				5 streams: not supported
				6 streams: not supported
				7 streams: not supported
				8 streams: not supported
			HE TX MCS and NSS set <= 80 MHz
				1 streams: MCS 0-11
				2 streams: MCS 0-11
				3 streams: not supported
				4 streams: not supported
				5 streams: not supported
				6 streams: not supported
				7 streams: not supported
				8 streams: not supported
			PPE Threshold 0x39 0x1c 0xc7 0x71 0x1c 0x07 
		HE Iftypes: AP
			HE MAC Capabilities (0x00011a081044):
				+HTC HE Supported
				BSR
				OM Control
				Maximum A-MPDU Length Exponent: 3
				BQR
				A-MSDU in A-MPDU
				OM Control UL MU Data Disable RX
			HE PHY Capabilities: (0x0420ce120000a000000c00):
				HE40/HE80/5GHz
				LDPC Coding in Payload
				NDP with 4x HE-LTF and 3.2us GI
				STBC Tx <= 80MHz
				STBC Rx <= 80MHz
				Full Bandwidth UL MU-MIMO
				Partial Bandwidth UL MU-MIMO
				DCM Max Constellation: 2
				DCM Max Constellation Rx: 2
				Partial Bandwidth Extended Range
				PPE Threshold Present
				TX 1024-QAM
				RX 1024-QAM
			HE RX MCS and NSS set <= 80 MHz
				1 streams: MCS 0-11
				2 streams: MCS 0-11
				3 streams: not supported
				4 streams: not supported
				5 streams: not supported
				6 streams: not supported
				7 streams: not supported
				8 streams: not supported
			HE TX MCS and NSS set <= 80 MHz
				1 streams: MCS 0-11
				2 streams: MCS 0-11
				3 streams: not supported
				4 streams: not supported
				5 streams: not supported
				6 streams: not supported
				7 streams: not supported
				8 streams: not supported
			PPE Threshold 0x39 0x1c 0xc7 0x71 0x1c 0x07 
		Bitrates (non-HT):
			* 6.0 Mbps
			* 9.0 Mbps
			* 12.0 Mbps
			* 18.0 Mbps
			* 24.0 Mbps
			* 36.0 Mbps
			* 48.0 Mbps
			* 54.0 Mbps
		Frequencies:
			* 5180.0 MHz [36] (20.0 dBm)
			* 5200.0 MHz [40] (20.0 dBm)
			* 5220.0 MHz [44] (20.0 dBm)
			* 5240.0 MHz [48] (20.0 dBm)
			* 5260.0 MHz [52] (20.0 dBm) (no IR, radar detection)
			* 5280.0 MHz [56] (20.0 dBm) (no IR, radar detection)
			* 5300.0 MHz [60] (20.0 dBm) (no IR, radar detection)
			* 5320.0 MHz [64] (20.0 dBm) (no IR, radar detection)
			* 5500.0 MHz [100] (20.0 dBm) (no IR, radar detection)
			* 5520.0 MHz [104] (20.0 dBm) (no IR, radar detection)
			* 5540.0 MHz [108] (20.0 dBm) (no IR, radar detection)
			* 5560.0 MHz [112] (20.0 dBm) (no IR, radar detection)
			* 5580.0 MHz [116] (20.0 dBm) (no IR, radar detection)
			* 5600.0 MHz [120] (20.0 dBm) (no IR, radar detection)
			* 5620.0 MHz [124] (20.0 dBm) (no IR, radar detection)
			* 5640.0 MHz [128] (20.0 dBm) (no IR, radar detection)
			* 5660.0 MHz [132] (20.0 dBm) (no IR, radar detection)
			* 5680.0 MHz [136] (20.0 dBm) (no IR, radar detection)
			* 5700.0 MHz [140] (20.0 dBm) (no IR, radar detection)
			* 5720.0 MHz [144] (20.0 dBm) (no IR, radar detection)
			* 5745.0 MHz [149] (20.0 dBm)
			* 5765.0 MHz [153] (20.0 dBm)
			* 5785.0 MHz [157] (20.0 dBm)
			* 5805.0 MHz [161] (20.0 dBm)
			* 5825.0 MHz [165] (20.0 dBm) (no IR)
			* 5845.0 MHz [169] (disabled)
			* 5865.0 MHz [173] (disabled)
			* 5885.0 MHz [177] (disabled)
	Band 4:
		HE Iftypes: managed
			HE MAC Capabilities (0x08011a000040):
				+HTC HE Supported
				Trigger Frame MAC Padding Duration: 2
				OM Control
				Maximum A-MPDU Length Exponent: 3
				A-MSDU in A-MPDU
			HE PHY Capabilities: (0x4470ce120dc0b306423f00):
				HE40/HE80/5GHz
				242 tone RUs/5GHz
				Device Class: 1
				LDPC Coding in Payload
				HE SU PPDU with 1x HE-LTF and 0.8us GI
				NDP with 4x HE-LTF and 3.2us GI
				STBC Tx <= 80MHz
				STBC Rx <= 80MHz
				Full Bandwidth UL MU-MIMO
				Partial Bandwidth UL MU-MIMO
				DCM Max Constellation: 2
				DCM Max Constellation Rx: 2
				SU Beamformee
				Beamformee STS <= 80Mhz: 3
				Ng = 16 SU Feedback
				Ng = 16 MU Feedback
				Codebook Size SU Feedback
				Codebook Size MU Feedback
				Triggered CQI Feedback
				Partial Bandwidth Extended Range
				PPE Threshold Present
				Power Boost Factor ar
				HE SU PPDU & HE PPDU 4x HE-LTF 0.8us GI
				20MHz in 40MHz HE PPDU 2.4GHz
				DCM Max BW: 1
				Longer Than 16HE SIG-B OFDM Symbols
				Non-Triggered CQI Feedback
				TX 1024-QAM
				RX 1024-QAM
				RX Full BW SU Using HE MU PPDU with Compression SIGB
				RX Full BW SU Using HE MU PPDU with Non-Compression SIGB
			HE RX MCS and NSS set <= 80 MHz
				1 streams: MCS 0-11
				2 streams: MCS 0-11
				3 streams: not supported
				4 streams: not supported
				5 streams: not supported
				6 streams: not supported
				7 streams: not supported
				8 streams: not supported
			HE TX MCS and NSS set <= 80 MHz
				1 streams: MCS 0-11
				2 streams: MCS 0-11
				3 streams: not supported
				4 streams: not supported
				5 streams: not supported
				6 streams: not supported
				7 streams: not supported
				8 streams: not supported
			PPE Threshold 0x39 0x1c 0xc7 0x71 0x1c 0x07 
		HE Iftypes: AP
			HE MAC Capabilities (0x00011a081044):
				+HTC HE Supported
				BSR
				OM Control
				Maximum A-MPDU Length Exponent: 3
				BQR
				A-MSDU in A-MPDU
				OM Control UL MU Data Disable RX
			HE PHY Capabilities: (0x0420ce120000a000000c00):
				HE40/HE80/5GHz
				LDPC Coding in Payload
				NDP with 4x HE-LTF and 3.2us GI
				STBC Tx <= 80MHz
				STBC Rx <= 80MHz
				Full Bandwidth UL MU-MIMO
				Partial Bandwidth UL MU-MIMO
				DCM Max Constellation: 2
				DCM Max Constellation Rx: 2
				Partial Bandwidth Extended Range
				PPE Threshold Present
				TX 1024-QAM
				RX 1024-QAM
			HE RX MCS and NSS set <= 80 MHz
				1 streams: MCS 0-11
				2 streams: MCS 0-11
				3 streams: not supported
				4 streams: not supported
				5 streams: not supported
				6 streams: not supported
				7 streams: not supported
				8 streams: not supported
			HE TX MCS and NSS set <= 80 MHz
				1 streams: MCS 0-11
				2 streams: MCS 0-11
				3 streams: not supported
				4 streams: not supported
				5 streams: not supported
				6 streams: not supported
				7 streams: not supported
				8 streams: not supported
			PPE Threshold 0x39 0x1c 0xc7 0x71 0x1c 0x07 
		Bitrates (non-HT):
			* 6.0 Mbps
			* 9.0 Mbps
			* 12.0 Mbps
			* 18.0 Mbps
			* 24.0 Mbps
			* 36.0 Mbps
			* 48.0 Mbps
			* 54.0 Mbps
		Frequencies:
			* 5955.0 MHz [1] (disabled)
			* 5975.0 MHz [5] (disabled)
			* 5995.0 MHz [9] (disabled)
			* 6015.0 MHz [13] (disabled)
			* 6035.0 MHz [17] (disabled)
			* 6055.0 MHz [21] (disabled)
			* 6075.0 MHz [25] (disabled)
			* 6095.0 MHz [29] (disabled)
			* 6115.0 MHz [33] (disabled)
			* 6135.0 MHz [37] (disabled)
			* 6155.0 MHz [41] (disabled)
			* 6175.0 MHz [45] (disabled)
			* 6195.0 MHz [49] (disabled)
			* 6215.0 MHz [53] (disabled)
			* 6235.0 MHz [57] (disabled)
			* 6255.0 MHz [61] (disabled)
			* 6275.0 MHz [65] (disabled)
			* 6295.0 MHz [69] (disabled)
			* 6315.0 MHz [73] (disabled)
			* 6335.0 MHz [77] (disabled)
			* 6355.0 MHz [81] (disabled)
			* 6375.0 MHz [85] (disabled)
			* 6395.0 MHz [89] (disabled)
			* 6415.0 MHz [93] (disabled)
			* 6435.0 MHz [97] (disabled)
			* 6455.0 MHz [101] (disabled)
			* 6475.0 MHz [105] (disabled)
			* 6495.0 MHz [109] (disabled)
			* 6515.0 MHz [113] (disabled)
			* 6535.0 MHz [117] (disabled)
			* 6555.0 MHz [121] (disabled)
			* 6575.0 MHz [125] (disabled)
			* 6595.0 MHz [129] (disabled)
			* 6615.0 MHz [133] (disabled)
			* 6635.0 MHz [137] (disabled)
			* 6655.0 MHz [141] (disabled)
			* 6675.0 MHz [145] (disabled)
			* 6695.0 MHz [149] (disabled)
			* 6715.0 MHz [153] (disabled)
			* 6735.0 MHz [157] (disabled)
			* 6755.0 MHz [161] (disabled)
			* 6775.0 MHz [165] (disabled)
			* 6795.0 MHz [169] (disabled)
			* 6815.0 MHz [173] (disabled)
			* 6835.0 MHz [177] (disabled)
			* 6855.0 MHz [181] (disabled)
			* 6875.0 MHz [185] (disabled)
			* 6895.0 MHz [189] (disabled)
			* 6915.0 MHz [193] (disabled)
			* 6935.0 MHz [197] (disabled)
			* 6955.0 MHz [201] (disabled)
			* 6975.0 MHz [205] (disabled)
			* 6995.0 MHz [209] (disabled)
			* 7015.0 MHz [213] (disabled)
			* 7035.0 MHz [217] (disabled)
			* 7055.0 MHz [221] (disabled)
			* 7075.0 MHz [225] (disabled)
			* 7095.0 MHz [229] (disabled)
			* 7115.0 MHz [233] (disabled)
	Supported commands:
		* new_interface
		* set_interface
		* new_key
		* start_ap
		* new_station
		* new_mpath
		* set_mesh_config
		* set_bss
		* authenticate
		* associate
		* deauthenticate
		* disassociate
		* join_ibss
		* join_mesh
		* remain_on_channel
		* set_tx_bitrate_mask
		* frame
		* frame_wait_cancel
		* set_wiphy_netns
		* set_channel
		* tdls_mgmt
		* tdls_oper
		* start_sched_scan
		* probe_client
		* set_noack_map
		* register_beacons
		* start_p2p_device
		* set_mcast_rate
		* connect
		* disconnect
		* channel_switch
		* set_qos_map
		* set_multicast_to_unicast
		* set_sar_specs
	WoWLAN support:
		* wake up on disconnect
		* wake up on magic packet
		* wake up on pattern match, up to 1 patterns of 1-128 bytes,
		  maximum packet offset 0 bytes
		* can do GTK rekeying
		* wake up on network detection, up to 10 match sets
	software interface modes (can always be added):
		* AP/VLAN
		* monitor
	valid interface combinations:
		* #{ managed, P2P-client } <= 2, #{ AP, P2P-GO } <= 1,
		  total <= 2, #channels <= 2
	HT Capability overrides:
		* MCS: ff ff ff ff ff ff ff ff ff ff
		* maximum A-MSDU length
		* supported channel width
		* short GI for 40 MHz
		* max A-MPDU length exponent
		* min MPDU start spacing
	Device supports TX status socket option.
	Device supports HT-IBSS.
	Device supports SAE with AUTHENTICATE command
	Device supports scan flush.
	Device supports per-vif TX power setting
	Driver supports full state transitions for AP/GO clients
	Driver supports a userspace MPM
	Device supports active monitor (which will ACK incoming frames)
	Driver/device bandwidth changes during BSS lifetime (AP/GO mode)
	Device supports configuring vdev MAC-addr on create.
	Device supports randomizing MAC-addr in scans.
	Device supports randomizing MAC-addr in sched scans.
	max # scan plans: 1
	max scan plan interval: 65535
	max scan plan iterations: 0
	Supported TX frame types:
		* IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		* managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		* AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		* AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		* mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		* P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		* P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		* P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
	Supported RX frame types:
		* IBSS: 0x40 0xb0 0xc0 0xd0
		* managed: 0x40 0xb0 0xd0
		* AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
		* AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
		* mesh point: 0xb0 0xc0 0xd0
		* P2P-client: 0x40 0xd0
		* P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
		* P2P-device: 0x40 0xd0
	Supported extended features:
		* [ RRM ]: RRM
		* [ SET_SCAN_DWELL ]: scan dwell setting
		* [ BEACON_RATE_LEGACY ]: legacy beacon rate setting
		* [ BEACON_RATE_HT ]: HT beacon rate setting
		* [ BEACON_RATE_VHT ]: VHT beacon rate setting
		* [ FILS_STA ]: STA FILS (Fast Initial Link Setup)
		* [ CQM_RSSI_LIST ]: multiple CQM_RSSI_THOLD records
		* [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211
		* [ ACK_SIGNAL_SUPPORT ]: ack signal level support
		* [ TXQS ]: FQ-CoDel-enabled intermediate TXQs
		* [ CAN_REPLACE_PTK0 ]: can safely replace PTK 0 when rekeying
		* [ AIRTIME_FAIRNESS ]: airtime fairness scheduling
		* [ AQL ]: Airtime Queue Limits (AQL)
		* [ CONTROL_PORT_NO_PREAUTH ]: disable pre-auth over nl80211 control port support
		* [ SCAN_FREQ_KHZ ]: scan on kHz frequency support
		* [ CONTROL_PORT_OVER_NL80211_TX_STATUS ]: tx status for nl80211 control port support
		* [ BEACON_RATE_HE ]: HE beacon rate support (AP/mesh)
		* [ POWERED_ADDR_CHANGE ]: can change MAC address while up
                                                                           
iperf3 -c 10.10.10.3                                                                                   ─╯
Connecting to host 10.10.10.3, port 5201
[  5] local 10.10.10.152 port 60728 connected to 10.10.10.3 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  66.5 MBytes   557 Mbits/sec    0   1.83 MBytes       
[  5]   1.00-2.00   sec  70.1 MBytes   589 Mbits/sec    0   1.83 MBytes       
[  5]   2.00-3.00   sec  67.5 MBytes   566 Mbits/sec    0   2.19 MBytes       
[  5]   3.00-4.00   sec  66.5 MBytes   558 Mbits/sec    0   2.60 MBytes       
[  5]   4.00-5.00   sec  67.2 MBytes   564 Mbits/sec    0   2.75 MBytes       
[  5]   5.00-6.00   sec  69.6 MBytes   584 Mbits/sec    0   2.75 MBytes       
[  5]   6.00-7.00   sec  69.2 MBytes   581 Mbits/sec    0   2.75 MBytes       
[  5]   7.00-8.00   sec  70.1 MBytes   589 Mbits/sec    0   2.75 MBytes       
[  5]   8.00-9.00   sec  68.5 MBytes   574 Mbits/sec    0   2.75 MBytes       
[  5]   9.00-10.00  sec  69.2 MBytes   581 Mbits/sec    0   2.92 MBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec   685 MBytes   574 Mbits/sec    0             sender
[  5]   0.00-10.01  sec   682 MBytes   571 Mbits/sec                  receiver

iperf Done.

@morrownr
Copy link
Owner

morrownr commented Nov 8, 2024

I have almost exactly the same laptop that you have and it has an M.2 card with the mt7921 chip. I also have an AXML adapter so I will test here. I have seen a long thread where it appeared Mediatek devs were working on this and they were working on the bluetooth subsystem. I am not sure if the patch has gone in yet.

I'm pretty sure or at least it seems that the AXML and one of the early Comfast adapters with the same chipset are the only adapters that show this problem. Yes, blacklisting bluetooth fixes the crash but kills all bluetooth which is not what we want so hopefully this is solved soon.

@KaliAssistant
Copy link
Author

ok, thanks

@wellitsmez
Copy link

@KaliAssistant have you tried monitor mode at this kernel? is it stable or crashing just as mine? how many networks did you get when you use air monitor because for me i made stand alone installation not using vm here for this kernel and getting about 20 percentage of what i am getting with kernel 6.8 at vm am trying to figure out what makes the performance that bad in my end

@KaliAssistant
Copy link
Author

KaliAssistant commented Nov 15, 2024

@wellitsmez i tried hcxdumptool,and its good for me, no crash ,no errors

@luckylinux
Copy link

luckylinux commented Nov 24, 2024

@morrownr: I am also getting crazy with this Issue 😢.

I originally purchased the Fenvi Adapter which more-or-less works OK. But then, sometimes, out of the blue, the Rock 5B SBC where this is installed completely crashes / disappears from the Network. Sometimes it works for like 1 Month or so. Sometimes it crashes after 10 Minutes. Last Night I managed to get it back running (apparently it was "just" the Mediatek Driver, without a Kernel Panic/Hang) simply by doing systemctl restart hostapd@wlan0. But this Morning it stopped working again 😞.

Now I was trying to get this fixed on a Raspberry Pi 2, since I don't want such critical piece of Network to go down because of a weird Driver / Firmware Issue.

But also on the Raspberry Pi 2 with Raspbian it seems all Hell is breaking loose.
The Raspberry Pi 2 reboots every 45 Seconds or so.

I tried removing the Bluetooth Firmware as you recommended:

sudo rm /lib/firmware/mediatek/BT_RAM_CODE_MT7961_1_2_hdr.bin

I blacklisted (all ?) the Relevant Drivers:
Contents of /etc/modprobe.d/blacklist-bluetooth.conf:

# Blacklist the Bluetooth Part of mt7921u
blacklist btmtk
blacklist btusb
blacklist btrtl

I forced the Raspberry Pi to Kernel 6.12 (since it would NOT let me update to anything else basically and I thought that the Issue was linked to poor Kernel 6.6 Support):

sudo rpi-update next

I also tried to installing the firmware-mediatek from bookworm-backports Repository as the Version in Raspbian / Raspberry Pi OS is VERY Old.

Nothing seems to Help.

Is there some other troubleshooting Steps that I missed ?

EDIT 1: On the Rock 5B it might also/sometimes be something related to USB Disconnection happening randomly. But once a crash/panic occurred, even if rebooting (by e.g. unpligging & replugging the Power Supply Cable), it will still crash within Seconds. The only Way to let it start is to unplug the Fenvi / mt7921u Adapter 😢.

@morrownr
Copy link
Owner

@luckylinux

I am also getting crazy with this Issue

It happens.

I originally purchased the Fenvi Adapter

Can you be specific about which Fenvi adapter you have?

Now I was trying to get this fixed on a Raspberry Pi 2, since I don't want such critical piece of Network to go down because of a weird Driver / Firmware Issue.

Okay, let's concentrate on the RasPi2. We can come back to the Rock5B.

Can you provide a link to the hardware specifics of the RasPi2 that you have?

Can you also provide me with a link to the exact RasPiOS distro you are using?

But also on the Raspberry Pi 2 with Raspbian it seems all Hell is breaking loose.
The Raspberry Pi 2 reboots every 45 Seconds or so.

I need to know what you are doing. Is this an AP mode setup? If so, what are the basics of your setup? hostapd? where is the internet connection coming from?

I tried removing the Bluetooth Firmware as you recommended:

That solution is for a different problem that only happens on 3 adapters. I am not aware of it being an issue on the Fenvi adapters.

I thought that the Issue was linked to poor Kernel 6.6 Support):

Kernel 6.6 is about as solid as it gets. I run an AP on my RasPi4B with RasPiOS 64 bit and it is really support solid.

I also tried to installing the firmware-mediatek from bookworm-backports

I would not recommend that. You can install the newest firmware directly from the Linux Kernel Firmware repo:

https://github.com/morrownr/USB-WiFi/blob/main/home/How_to_Install_Firmware_for_Mediatek_based_USB_WiFi_adapters.md

Is there some other troubleshooting Steps that I missed ?

Carefully answer my questions so that I know the situation and maybe I can help.

@luckylinux
Copy link

luckylinux commented Nov 25, 2024

@morrownr

@luckylinux

I am also getting crazy with this Issue

It happens.

Far too often 🤣

I originally purchased the Fenvi Adapter

Can you be specific about which Fenvi adapter you have?

Sure. Pretty sure it was the one you reccomended in one of your Discussions/Pages/Issues a few Months ago:
https://www.aliexpress.com/item/1005005935638503.html

Note that the Driver is mt7921u and NOT mt7921 as you stated though:

dmesg Output when plugging the Adapter in (trimmed):

[   47.278735] usb 1-1.4: new high-speed USB device number 4 using dwc_otg
[   47.410572] usb 1-1.4: New USB device found, idVendor=0e8d, idProduct=7961, bcdDevice= 1.00
[   47.410616] usb 1-1.4: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[   47.410638] usb 1-1.4: Product: Wireless_Device
[   47.410656] usb 1-1.4: Manufacturer: MediaTek Inc.
[   47.410673] usb 1-1.4: SerialNumber: 000000000
[   48.028817] usb 1-1.4: reset high-speed USB device number 4 using dwc_otg
[   48.198421] usbcore: registered new interface driver mt7921u
[   48.206624] mt7921u 1-1.4:1.0: HW/SW Version: 0x8a108a10, Build Time: 20240219110958a

[   48.479505] mt7921u 1-1.4:1.0: WM Firmware Version: ____010000, Build Time: 20240219111038
[   53.741673] cryptd: max_cpu_qlen set to 1000

Output of lsusb -vvv when plugging the Adapter in:


Bus 001 Device 004: ID 0e8d:7961 MediaTek Inc. Wireless_Device
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.10
  bDeviceClass            0 
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x0e8d MediaTek Inc.
  idProduct          0x7961 
  bcdDevice            1.00
  iManufacturer           2 MediaTek Inc.
  iProduct                3 Wireless_Device
  iSerial                 4 000000000
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x0051
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          5 Config_01
    bmAttributes         0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           9
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              1 WiFi_If
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x84  EP 4 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x85  EP 5 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x08  EP 8 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x04  EP 4 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x05  EP 5 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x06  EP 6 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x07  EP 7 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x09  EP 9 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x86  EP 6 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0002  1x 2 bytes
        bInterval               1
Binary Object Store Descriptor:
  bLength                 5
  bDescriptorType        15
  wTotalLength       0x0016
  bNumDeviceCaps          2
  USB 2.0 Extension Device Capability:
    bLength                 7
    bDescriptorType        16
    bDevCapabilityType      2
    bmAttributes   0x0000f11e
      BESL Link Power Management (LPM) Supported
    BESL value      256 us 
    Deep BESL value    61440 us 
  SuperSpeed USB Device Capability:
    bLength                10
    bDescriptorType        16
    bDevCapabilityType      3
    bmAttributes         0x00
    wSpeedsSupported   0x000e
      Device can operate at Full Speed (12Mbps)
      Device can operate at High Speed (480Mbps)
      Device can operate at SuperSpeed (5Gbps)
    bFunctionalitySupport   1
      Lowest fully-functional device speed is Full Speed (12Mbps)
    bU1DevExitLat          10 micro seconds
    bU2DevExitLat         180 micro seconds
can't get debug descriptor: Resource temporarily unavailable
Device Status:     0x0002
  (Bus Powered)
  Remote Wakeup Enabled

Bus 001 Device 003: ID 0424:ec00 Microchip Technology, Inc. (formerly SMSC) SMSC9512/9514 Fast Ethernet Adapter
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass          255 Vendor Specific Class
  bDeviceSubClass         0 
  bDeviceProtocol         1 
  bMaxPacketSize0        64
  idVendor           0x0424 Microchip Technology, Inc. (formerly SMSC)
  idProduct          0xec00 SMSC9512/9514 Fast Ethernet Adapter
  bcdDevice            2.00
  iManufacturer           0 
  iProduct                0 
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x0027
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xe0
      Self Powered
      Remote Wakeup
    MaxPower                2mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass      0 
      bInterfaceProtocol    255 
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0010  1x 16 bytes
        bInterval               4
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass          255 Vendor Specific Class
  bDeviceSubClass         0 
  bDeviceProtocol         1 
  bMaxPacketSize0        64
  bNumConfigurations      1
can't get debug descriptor: Resource temporarily unavailable
Device Status:     0x0001
  Self Powered

Bus 001 Device 002: ID 0424:9514 Microchip Technology, Inc. (formerly SMSC) SMC9514 Hub
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            9 Hub
  bDeviceSubClass         0 
  bDeviceProtocol         2 TT per port
  bMaxPacketSize0        64
  idVendor           0x0424 Microchip Technology, Inc. (formerly SMSC)
  idProduct          0x9514 SMC9514 Hub
  bcdDevice            2.00
  iManufacturer           0 
  iProduct                0 
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x0029
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xe0
      Self Powered
      Remote Wakeup
    MaxPower                2mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         9 Hub
      bInterfaceSubClass      0 
      bInterfaceProtocol      1 Single TT
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0001  1x 1 bytes
        bInterval              12
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       1
      bNumEndpoints           1
      bInterfaceClass         9 Hub
      bInterfaceSubClass      0 
      bInterfaceProtocol      2 TT per port
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0001  1x 1 bytes
        bInterval              12
Hub Descriptor:
  bLength               9
  bDescriptorType      41
  nNbrPorts             5
  wHubCharacteristic 0x000d
    Per-port power switching
    Compound device
    Per-port overcurrent protection
    TT think time 8 FS bits
  bPwrOn2PwrGood       50 * 2 milli seconds
  bHubContrCurrent      1 milli Ampere
  DeviceRemovable    0x02
  PortPwrCtrlMask    0xff
 Hub Port Status:
   Port 1: 0000.0503 highspeed power enable connect
   Port 2: 0000.0100 power
   Port 3: 0000.0100 power
   Port 4: 0000.0503 highspeed power enable connect
   Port 5: 0000.0100 power
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass            9 Hub
  bDeviceSubClass         0 
  bDeviceProtocol         0 Full speed (or root) hub
  bMaxPacketSize0        64
  bNumConfigurations      1
can't get debug descriptor: Resource temporarily unavailable
Device Status:     0x0001
  Self Powered

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            9 Hub
  bDeviceSubClass         0 
  bDeviceProtocol         1 Single TT
  bMaxPacketSize0        64
  idVendor           0x1d6b Linux Foundation
  idProduct          0x0002 2.0 root hub
  bcdDevice            6.06
  iManufacturer           3 Linux 6.6.51-v7+ dwc_otg_hcd
  iProduct                2 DWC OTG Controller
  iSerial                 1 3f980000.usb
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x0019
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xe0
      Self Powered
      Remote Wakeup
    MaxPower                0mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         9 Hub
      bInterfaceSubClass      0 
      bInterfaceProtocol      0 Full speed (or root) hub
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0004  1x 4 bytes
        bInterval              12
Hub Descriptor:
  bLength               9
  bDescriptorType      41
  nNbrPorts             1
  wHubCharacteristic 0x0008
    Ganged power switching
    Per-port overcurrent protection
    TT think time 8 FS bits
  bPwrOn2PwrGood        1 * 2 milli seconds
  bHubContrCurrent      0 milli Ampere
  DeviceRemovable    0x00
  PortPwrCtrlMask    0xff
 Hub Port Status:
   Port 1: 0000.0503 highspeed power enable connect
can't get device qualifier: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable
Device Status:     0x0001
  Self Powered

I also tried to set the Raspberry Pi to deliver (up to) 1.2A (1200mA) of Current through the USB Power (Total Value, but I'm only using 1 USB Port anyways here).

Contents of /boot/firmware/config.txt:

# For more options and information see
# http://rptl.io/configtxt
# Some settings may impact device functionality. See link above for details

# Uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on

# Enable audio (loads snd_bcm2835)
dtparam=audio=on

# Additional overlays and parameters are documented
# /boot/firmware/overlays/README

# Automatically load overlays for detected cameras
camera_auto_detect=1

# Automatically load overlays for detected DSI displays
display_auto_detect=1

# Automatically load initramfs files, if found
auto_initramfs=1

# Enable DRM VC4 V3D driver
dtoverlay=vc4-kms-v3d
max_framebuffers=2

# Don't have the firmware create an initial video= setting in cmdline.txt.
# Use the kernel's default instead.
disable_fw_kms_setup=1

# Disable compensation for displays with overscan
disable_overscan=1

# Run as fast as firmware / board allows
arm_boost=1

# Disable USB Suspend feature
usbcore.autosuspend=-1

# Disable Bluetooth
dtoverlay=disable-bt

# Enable Watchdog
dtparam=watchdog=on

# Disable EEE
dtparam=eee=off

# Allow up to 1.2A for USB Current
max_usb_current=1

[cm4]
# Enable host mode on the 2711 built-in XHCI USB controller.
# This line should be removed if the legacy DWC2 controller is required
# (e.g. for USB device mode) or if USB support is not required.
otg_mode=1

[all]
# Use Custom Kernel and Initramfs
# kernel=vmlinuz-6.11.5+bpo-armmp-lpae
# initramfs=initrd.img-6.11.5+bpo-armmp-lpae

I also tried to use Debian Backports linux-image-armmp-lpae but it wouln't boot at all.

Now I was trying to get this fixed on a Raspberry Pi 2, since I don't want such critical piece of Network to go down because of a weird Driver / Firmware Issue.

Okay, let's concentrate on the RasPi2. We can come back to the Rock5B.

Can you provide a link to the hardware specifics of the RasPi2 that you have?

Not sure what you mean exactly. It was like 10 Years ago and the Seller removed the Article from their Website. The Email Invoice just says "Raspberry Pi 2 Model B - 1GB RAM".

It seems to be a VERY old Version. Cannot know the Revision without taking the Case apart, but here is cat /proc/cpuinfo:

root@raspberrypi2-02:~ # cat /proc/cpuinfo 
processor	: 0
model name	: ARMv7 Processor rev 5 (v7l)
BogoMIPS	: 44.80
Features	: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm 
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x0
CPU part	: 0xc07
CPU revision	: 5

processor	: 1
model name	: ARMv7 Processor rev 5 (v7l)
BogoMIPS	: 44.80
Features	: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm 
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x0
CPU part	: 0xc07
CPU revision	: 5

processor	: 2
model name	: ARMv7 Processor rev 5 (v7l)
BogoMIPS	: 44.80
Features	: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm 
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x0
CPU part	: 0xc07
CPU revision	: 5

processor	: 3
model name	: ARMv7 Processor rev 5 (v7l)
BogoMIPS	: 44.80
Features	: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm 
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x0
CPU part	: 0xc07
CPU revision	: 5

Hardware	: BCM2835
Revision	: a01041
Serial		: 00000000e7218b02
Model		: Raspberry Pi 2 Model B Rev 1.1

Ignore theBCM2835 Part, that is a BUG/Feature, according to Raspberry Pi GitHub Tracker.

From https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#new-style-revision-codes-in-use we can indeed see that Revision a01041 is indeed the Raspberry Pi 2B Revision 1.1 with 1GB of RAM.

Can you also provide me with a link to the exact RasPiOS distro you are using?

To be Honest not really. Because, when I tried to flash the most recent Version using Raspberry Pi Imager for a Raspberry Pi 2, it just would NOT boot at all.

So I basically grabbed an oldish (6 Months out of Date ?) SD Card with Rasberry Pi OS Installed on that specific Raspberry Pi 2, applied all updates, and here I am. Yes, it boots with latest Updates and it's Stable If the Fenvi Adapter is NOT plugged In.

But also on the Raspberry Pi 2 with Raspbian it seems all Hell is breaking loose.
The Raspberry Pi 2 reboots every 45 Seconds or so.

I need to know what you are doing. Is this an AP mode setup? If so, what are the basics of your setup? hostapd? where is the internet connection coming from?

It is/was an AP mode setup using hostapd + dnsmasq. Internet Connection is coming directly through the Main Ethernet port from the "Main LAN". So yeah, it's probably double/triple NAT.

I tried disabling the hostapd Service now and see if it survives longer with the Fenvi Adapter plugged in. But nope, still crashes in about 45-60 Seconds or so after I plugged it in.

I tried removing the Bluetooth Firmware as you recommended:

That solution is for a different problem that only happens on 3 adapters. I am not aware of it being an issue on the Fenvi adapters.

Uhm alright. I did NOT need Bluetooth, so it's OK to remove for me anyways.

I thought that the Issue was linked to poor Kernel 6.6 Support):

Kernel 6.6 is about as solid as it gets. I run an AP on my RasPi4B with RasPiOS 64 bit and it is really support solid.

Well that definitively is NOT my experience on the Rock 5B. It seems to work fine. Until it doesn't. And on the Raspberry Pi 2 it's consistently crashing, so totally unusable.

I'd do this on a Raspberry Pi 3/4, but since I have still a lot of Raspberry Pi 2 laying around, I'd rather use those for such low-power Tasks, than having to buy a new one ...

I also tried to installing the firmware-mediatek from bookworm-backports

I would not recommend that. You can install the newest firmware directly from the Linux Kernel Firmware repo:

https://github.com/morrownr/USB-WiFi/blob/main/home/How_to_Install_Firmware_for_Mediatek_based_USB_WiFi_adapters.md

Alright, I uninstalled firmware-realtek using APT, then I installed using your Method (that I Scripted):

#!/bin/bash

mkdir -p /lib/firmware/mediatek
cd /lib/firmware/mediatek
wget https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/mediatek/WIFI_MT7961_patch_mcu_1_2_hdr.bin -O WIFI_MT7961_patch_mcu_1_2_hdr.bin
wget https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/mediatek/WIFI_RAM_CODE_MT7961_1.bin -O WIFI_RAM_CODE_MT7961_1.bin
wget https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/mediatek/BT_RAM_CODE_MT7961_1_2_hdr.bin -O BT_RAM_CODE_MT7961_1_2_hdr.bin

Currently I'm rebuilding my Initramfs with update-initramfs -k all -u then Reboot and try again.

I'm NOT very hopeful however based on previous Experiences ...

Is there some other troubleshooting Steps that I missed ?

Carefully answer my questions so that I know the situation and maybe I can help.

Thanks for your Help. Is there other Info you need ?

Currently running Kernel:

Linux raspberrypi2-02 6.6.51-v7+ #1802 SMP Tue Oct  8 17:23:58 BST 2024 armv7l GNU/Linux

EDIT 1: I must emphasize, at least on the Rock 5B, that the Fenvi USB Adapter (and possible the USB Hub that I'm using) seems to be EXTREMELY finicky: one light touch on the Rock 5B is enough to trigger a USB Disconnection (whereas my main worry would be the RJ45 Cable getting "ejected", since the retaining Tab on the Cable is broken). But nope, touch lightly the Rock 5B, and you can see USB Disconnection Messages in dmesg.

EDIT 2: with the Firmware installed from Linux Kernel git Repository as per your Instruction, the dmesg Output changes to (indicating a new Firmware Version of 20241106):

[  207.287788] usb 1-1.4: new high-speed USB device number 4 using dwc_otg
[  207.419333] usb 1-1.4: New USB device found, idVendor=0e8d, idProduct=7961, bcdDevice= 1.00
[  207.419373] usb 1-1.4: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[  207.419387] usb 1-1.4: Product: Wireless_Device
[  207.419399] usb 1-1.4: Manufacturer: MediaTek Inc.
[  207.419411] usb 1-1.4: SerialNumber: 000000000
[  208.007811] usb 1-1.4: reset high-speed USB device number 4 using dwc_otg
[  208.171357] usbcore: registered new interface driver mt7921u
[  208.179956] mt7921u 1-1.4:1.0: HW/SW Version: 0x8a108a10, Build Time: 20241106151007a

[  208.455127] mt7921u 1-1.4:1.0: WM Firmware Version: ____010000, Build Time: 20241106151045
[  212.177388] cryptd: max_cpu_qlen set to 1000

And my dumb Script to detect when the Crash occurs shows that the Raspberry Pi 2 still reboots quite soon:

root@raspberrypi2-02:/tools_local # ./did_i_crash.sh 
20241125-07:28:48 - Still Alive (up since 2024-11-25 07:27:24)
20241125-07:28:49 - Still Alive (up since 2024-11-25 07:27:24)
20241125-07:28:50 - Still Alive (up since 2024-11-25 07:27:24)
20241125-07:28:51 - Still Alive (up since 2024-11-25 07:27:24)
20241125-07:28:52 - Still Alive (up since 2024-11-25 07:27:24)
20241125-07:28:53 - Still Alive (up since 2024-11-25 07:27:24)
20241125-07:28:54 - Still Alive (up since 2024-11-25 07:27:24)
20241125-07:28:55 - Still Alive (up since 2024-11-25 07:27:24)
20241125-07:28:56 - Still Alive (up since 2024-11-25 07:27:24)
20241125-07:28:57 - Still Alive (up since 2024-11-25 07:27:24)
20241125-07:28:58 - Still Alive (up since 2024-11-25 07:27:24)
20241125-07:28:59 - Still Alive (up since 2024-11-25 07:27:24)
20241125-07:29:00 - Still Alive (up since 2024-11-25 07:27:24)
20241125-07:29:01 - Still Alive (up since 2024-11-25 07:27:24)
20241125-07:29:02 - Still Alive (up since 2024-11-25 07:27:24)
20241125-07:29:03 - Still Alive (up since 2024-11-25 07:27:24)
20241125-07:29:04 - Still Alive (up since 2024-11-25 07:27:24)
20241125-07:29:05 - Still Alive (up since 2024-11-25 07:27:24)
20241125-07:29:06 - Still Alive (up since 2024-11-25 07:27:24)
20241125-07:29:07 - Still Alive (up since 2024-11-25 07:27:24)
20241125-07:29:08 - Still Alive (up since 2024-11-25 07:27:24)
Connection to 192.168.4.31 closed by remote host.
Connection to 192.168.4.31 closed.

@morrownr
Copy link
Owner

@luckylinux

Pretty sure it was the one you recomended in one of your Discussions/Pages/Issues a few Months ago

Okay, you link shows the Fenvi FU-AX1800. The Plug and Play List also has a Fenvi FU-AX1801D. I am just trying to understand the situation. Your post should have been in a new Issue as this issue is about a different adapter.

Note that the Driver is mt7921u and NOT mt7921 as you stated though...

I did a quick look around the site to see what I said but did not find where I said this. If you can point me to the problem, I can correct it.

Not sure what you mean exactly. It was like 10 Years ago and the Seller removed the Article from their Website. The Email Invoice just says "Raspberry Pi 2 Model B - 1GB RAM".

I am trying to figure out the capabilities of your RasPi2B. It appears to me that this model is using a 32 bit cpu and is USB2 only. That means you have to use the 32 bit version of RasPiOS and it appears that you are. For me to test, I have a RasPi3B that is available, it is 64 bit but I could install the 32 bit version and I'll have to lock the use of the 64 bit kernel as RasPi has made it such that the 64 bit kernel will be used, even on 32 bit installations if the hardware is capable of 64 bit operation.

It is curious why you did not have any success with a new 32 bit installation. I'll admit that I grow more skeptical of using 32 bit distros as time passes as 32 bit simply does not get the testing that it once did.

So I basically grabbed an oldish (6 Months out of Date ?) SD Card with Rasberry Pi OS Installed on that specific Raspberry Pi 2, applied all updates, and here I am. Yes, it boots with latest Updates and it's Stable If the Fenvi Adapter is NOT plugged In.

Do you have any other USB WiFi adapters available for testing? If so, please let me know what you have so we can pick out one or two for you to test.

I tried disabling the hostapd Service now and see if it survives longer with the Fenvi Adapter plugged in. But nope, still crashes in about 45-60 Seconds or so after I plugged it in.

Good information. Have you tested the Fenvi adapter on a desktop or laptop with x86_64/amd64 cpu and a recent mainstream distro such as Ubuntu 24.04 or 24.10. I'd like to rule out a manufacturing problem. Even testing on a Windows system would help eliminate a manufacturing problem.

Alright, I uninstalled firmware-realtek...

Realtek?

Thanks for your Help. Is there other Info you need ?

I think the keys right now are you testing to eliminate a manufacturing problem and me testing a 32 bit RasPiOS installation. Let me know what you find out.

I must emphasize, at least on the Rock 5B, that the Fenvi USB Adapter (and possible the USB Hub that I'm using) seems to be EXTREMELY finicky: one light touch on the Rock 5B is enough to trigger a USB Disconnection (whereas my main worry would be the RJ45 Cable getting "ejected", since the retaining Tab on the Cable is broken). But nope, touch lightly the Rock 5B, and you can see USB Disconnection Messages in dmesg.

I think that you testing the adapter on a desktop/laptop system that is known to perform well, even if you need to do it on a Windows system is very important to this investigation. The issue is whether your adapter has a manufacturing problem.

with the Firmware installed from Linux Kernel git Repository as per your Instruction, the dmesg Output changes to (indicating a new Firmware Version of 20241106):

Updating firmware is best performed with the method I outlined because the location is THE location where the new firmware is placed for distro maintainers to get the updates. Most maintainers of distros are not aggressive about getting updates of firmware.

@luckylinux
Copy link

Damn I see that this morning I forgot to post the most important Comment (I was making an Edit of the Original Comment but never pressed Save) 😞.

For some weird Reason netconsole refuses to do anything. Not sure why I cannot get remote Logging working over Netcat 😞.

Anyways, I thought I'd check the Watchdog Configuration and sure enough it was enabled and /etc/watchdog.conf (copied from a Raspberry Pi 3 which does have WiFi !) it was set to Monitor Network Interface wlan0.

Which means, as soon as I plugged the Fenvi in the USB Port, after a few 15-seconds Attempts, the Watchdog would trigger a restart of the Raspberry Pi.

Whereas if wlan0 didn't exist, then the Watchdog gets disabled automatically. Weird. I didn't see that coming 🤣.

I now changed the Watchdog Monitor Interface to eth0 instead and the Raspberry Pi survives "OK".

Still weird that, no Matter what I do, netcnosole + netcat refuse to work, so that I can get remote logging to work.

@luckylinux
Copy link

@luckylinux

Pretty sure it was the one you recomended in one of your Discussions/Pages/Issues a few Months ago

Okay, you link shows the Fenvi FU-AX1800. The Plug and Play List also has a Fenvi FU-AX1801D. I am just trying to understand the situation. Your post should have been in a new Issue as this issue is about a different adapter.

Sorry. Should I create one new Issue then ?

Note that the Driver is mt7921u and NOT mt7921 as you stated though...

I did a quick look around the site to see what I said but did not find where I said this. If you can point me to the problem, I can correct it.

Here I meant that it should be mt7921u instead of mt7921:
image

Not sure what you mean exactly. It was like 10 Years ago and the Seller removed the Article from their Website. The Email Invoice just says "Raspberry Pi 2 Model B - 1GB RAM".

I am trying to figure out the capabilities of your RasPi2B. It appears to me that this model is using a 32 bit cpu and is USB2 only. That means you have to use the 32 bit version of RasPiOS and it appears that you are. For me to test, I have a RasPi3B that is available, it is 64 bit but I could install the 32 bit version and I'll have to lock the use of the 64 bit kernel as RasPi has made it such that the 64 bit kernel will be used, even on 32 bit installations if the hardware is capable of 64 bit operation.

Yeah 32bit Raspberry Pi 2 is a bit of a Freak. But I cannot see myself just throwing it away like this 😢. Still good for a very simple AP Setup. It should also work with Mainline Debian, but also there Things are moving towards 64-bit mainly/only.

So I basically grabbed an oldish (6 Months out of Date ?) SD Card with Rasberry Pi OS Installed on that specific Raspberry Pi 2, applied all updates, and here I am. Yes, it boots with latest Updates and it's Stable If the Fenvi Adapter is NOT plugged In.

Do you have any other USB WiFi adapters available for testing? If so, please let me know what you have so we can pick out one or two for you to test.

Oh I had that VERY BAD nowadays supported RTL Adapter (8814au) but I don't think it's a good Idea to try that. You (rightly so) pointed me towards the Fenvi / Mediatek Chipset for better HW Support 😄.

I tried disabling the hostapd Service now and see if it survives longer with the Fenvi Adapter plugged in. But nope, still crashes in about 45-60 Seconds or so after I plugged it in.

Good information. Have you tested the Fenvi adapter on a desktop or laptop with x86_64/amd64 cpu and a recent mainstream distro such as Ubuntu 24.04 or 24.10. I'd like to rule out a manufacturing problem. Even testing on a Windows system would help eliminate a manufacturing problem.

No, not yet at least.

Alright, I uninstalled firmware-realtek...

Realtek?

Sorry, firmware-mediatek. I also uninstalled other Firmware that were NOT needed though including NVIDIAv Graphics etc.

Thanks for your Help. Is there other Info you need ?

I think the keys right now are you testing to eliminate a manufacturing problem and me testing a 32 bit RasPiOS installation. Let me know what you find out.

It might have been the Watchdog all along on the Raspberry Pi 2.

That still does NOT however explain the finickiness on the Rock 5B though with very sensitive USB Disconnection.

I must emphasize, at least on the Rock 5B, that the Fenvi USB Adapter (and possible the USB Hub that I'm using) seems to be EXTREMELY finicky: one light touch on the Rock 5B is enough to trigger a USB Disconnection (whereas my main worry would be the RJ45 Cable getting "ejected", since the retaining Tab on the Cable is broken). But nope, touch lightly the Rock 5B, and you can see USB Disconnection Messages in dmesg.

I think that you testing the adapter on a desktop/laptop system that is known to perform well, even if you need to do it on a Windows system is very important to this investigation. The issue is whether your adapter has a manufacturing problem.

I have several Fenvi around (4x ? 5x ? not sure). So yeah at least 1 is "free" to play around with.

with the Firmware installed from Linux Kernel git Repository as per your Instruction, the dmesg Output changes to (indicating a new Firmware Version of 20241106):

Updating firmware is best performed with the method I outlined because the location is THE location where the new firmware is placed for distro maintainers to get the updates. Most maintainers of distros are not aggressive about getting updates of firmware.

Debian even less so 🤣.

@morrownr
Copy link
Owner

morrownr commented Dec 5, 2024

@luckylinux

Should I create one new Issue then?

I think it would help.

Here I meant that it should be mt7921u instead of mt7921:

I looked at the pic you posted and still do not understand. I did not mention the driver name at all. Tell me what you think should be changed.

Yeah 32bit Raspberry Pi 2 is a bit of a Freak. But I cannot see myself just throwing it away...

I am not suggesting that you recycle it. I am trying to point out that as time passes, it may become more problematic getting some things to work on 32 bit. The mt7921au chip and it's driver came about long after we were solidly in a 64 bit world. Was the driver tested for 32 bit operation? Maybe.

@steev
Copy link

steev commented Dec 6, 2024

Hey @morrownr, steev from the kali team here. do you happen to know which unrelated bluetooth commit it is that breaks this?

@morrownr
Copy link
Owner

morrownr commented Dec 6, 2024

Hi @steev

do you happen to know which unrelated bluetooth commit it is that breaks this?

I do not. I would dissected this problem but I have been very busy. I think it was about the time that kernel 6.7 was released that I got the first message about this problem.

I have an AXML and can easily duplicate the problem here. I also have another adapter with the same chip that does not show the problem. There are 3 known adapters that show this problem: Alfa's AXML and AXM as well as the Comfast 953. None of the other adapters with the same chip show the problem.

This is a problem that may be hard to solve without a dissection. I suspect that the bad adapters may have problematic eeproms in that they are showing bluetooth support when it is actually turned off. This leads to the BAD behavior in the bluetooth stack, which also kills wifi. This did not happen until around kernel 6.7 so something changed.

Keep me posted if you find someone to dissect this problem.

@wellitsmez
Copy link

@steev hello steev the Bluetooth is not the only thing is broken here also the VIF mode under the monitor mode you can have a look at some work arounds in here #539 and also some discussion about what is broken when it comes to kernels bigger than 6.1 in here ZerBea/hcxdumptool#361 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants