[Bug 1193648] New: mt7921e network card not initializing correctly
http://bugzilla.opensuse.org/show_bug.cgi?id=1193648 Bug ID: 1193648 Summary: mt7921e network card not initializing correctly Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: otni.ledelay@gmail.com QA Contact: qa-bugs@suse.de Found By: Community User Blocker: --- Created attachment 854506 --> http://bugzilla.opensuse.org/attachment.cgi?id=854506&action=edit output of 'journalctl --system --dmesg --boot 0' I am dual booting win10 and TW on a new laptop, trying to slowly migrate to Linux. I haven't however been able to get my WiFi working on Linux. ## I have tried: - Disabling fast boot and Windows hibernation - Several boot parameters: * pcie_aspm=force This did result in my wifi card almost working the first time I ran with it. See journal2.txt for the results of that, what happened seems similar to what's described here: https://www.spinics.net/lists/linux-wireless/msg218339.html It didn't work the second time I tried it. * pcie_aspm=off Didn't solve the problem, again identical results to journal.txt (but without the "can't disable ASPM" warning) * acpi_osi='Windows 2021' Didn't solve the problem. * acpi=off Broke a bunch of other things but didn't solve the problem. There was one time after a long time of not using my laptop that my wifi did seem to work, journal attached as journal3.txt ## System information: 212:~ # tumbleweed installed 20211206 212:~ # uname -svrio Linux 5.15.6-1-default #1 SMP Wed Dec 1 08:32:12 UTC 2021 (c2ce213) x86_64 GNU/Linux 212:~ # lspci -s 0000:02:00.0 -v 02:00.0 Network controller: MEDIATEK Corp. Device 7961 Subsystem: AzureWave Device 4680 Physical Slot: 0-1 Flags: fast devsel, IRQ 89, IOMMU group 9 Memory at ff20300000 (64-bit, prefetchable) [size=1M] Memory at ff20400000 (64-bit, prefetchable) [size=16K] Memory at ff20404000 (64-bit, prefetchable) [size=4K] Capabilities: [80] Express Endpoint, MSI 00 Capabilities: [e0] MSI: Enable- Count=1/32 Maskable+ 64bit+ Capabilities: [f8] Power Management version 3 Capabilities: [100] Vendor Specific Information: ID=1556 Rev=1 Len=008 <?> Capabilities: [108] Latency Tolerance Reporting Capabilities: [110] L1 PM Substates Capabilities: [200] Advanced Error Reporting Kernel modules: mt7921e 212:~ # lshw -C network *-network UNCLAIMED description: Network controller product: MEDIATEK Corp. vendor: MEDIATEK Corp. physical id: 0 bus info: pci@0000:02:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm cap_list configuration: latency=0 resources: iomemory:ff0-fef iomemory:ff0-fef iomemory:ff0-fef memory:ff20300000-ff203fffff memory:ff20400000-ff20403fff memory:ff20404000-ff20404fff *-network description: Ethernet interface physical id: 9 bus info: usb@1:1 logical name: enp4s0f3u1 serial: 3e:06:0b:1a:15:ec capabilities: ethernet physical configuration: autonegotiation=off broadcast=yes driver=rndis_host driverversion=5.15.6-1-default duplex=half firmware=RNDIS device ip=192.168.248.106 link=yes multicast=yes port=twisted pair (The second one is my phone using USB tethering to provide my laptop with internet, the problem is also present when my phone is not connected.) 212:~ # rfkill list all 0: asus-wlan: Wireless LAN Soft blocked: no Hard blocked: no 1: asus-bluetooth: Bluetooth Soft blocked: no Hard blocked: no 2: hci0: Bluetooth Soft blocked: no Hard blocked: no 212:~ # dmesg -l err [ 2.446661] sp5100-tco sp5100-tco: Watchdog hardware is disabled [ 4.927198] mt7921e 0000:02:00.0: ASIC revision: 79610010 [ 18.152314] Bluetooth: hci0: Failed to read MSFT supported features (-110) 212:~ # dmesg | grep mt7921e [ 4.926736] mt7921e 0000:02:00.0: enabling device (0000 -> 0002) [ 4.927096] mt7921e 0000:02:00.0: disabling ASPM L1 [ 4.927099] mt7921e 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control [ 4.927198] mt7921e 0000:02:00.0: ASIC revision: 79610010 [ 6.020425] mt7921e: probe of 0000:02:00.0 failed with error -110 212:~ # journalctl --system --dmesg --boot 0 > journal.txt 212:~ # journalctl --system --dmesg --boot -8 > journal2.txt 212:~ # journalctl --system --dmesg --boot -18 > journal3.txt -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193648 http://bugzilla.opensuse.org/show_bug.cgi?id=1193648#c1 --- Comment #1 from Ledelay <otni.ledelay@gmail.com> --- Created attachment 854507 --> http://bugzilla.opensuse.org/attachment.cgi?id=854507&action=edit output of 'journalctl --system --dmesg --boot -8', firmware loaded, but keeps resetting -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193648 Ledelay <otni.ledelay@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Alias|OLedelay | -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193648 http://bugzilla.opensuse.org/show_bug.cgi?id=1193648#c2 --- Comment #2 from Ledelay <otni.ledelay@gmail.com> --- Created attachment 854508 --> http://bugzilla.opensuse.org/attachment.cgi?id=854508&action=edit output of 'journalctl --system --dmesg --boot -18', I think it worked that time -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193648 http://bugzilla.opensuse.org/show_bug.cgi?id=1193648#c3 --- Comment #3 from Ledelay <otni.ledelay@gmail.com> --- (In reply to Ledelay from comment #1)
Created attachment 854507 [details] output of 'journalctl --system --dmesg --boot -8', firmware loaded, but keeps resetting
(In reply to Ledelay from comment #2)
Created attachment 854508 [details] output of 'journalctl --system --dmesg --boot -18', I think it worked that time
In both of these cases, nearby networks were displayed and could be connected to from the NetworkManager widget in my taskbar. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193648 http://bugzilla.opensuse.org/show_bug.cgi?id=1193648#c4 Luciano Santos <luc14n0@linuxmail.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |luc14n0@linuxmail.org --- Comment #4 from Luciano Santos <luc14n0@linuxmail.org> --- We have this upstream bug report: https://bugzilla.kernel.org/show_bug.cgi?id=214557 But it's still fresh and there isn't much progress going on. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193648 http://bugzilla.opensuse.org/show_bug.cgi?id=1193648#c5 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |otni.ledelay@gmail.com, | |tiwai@suse.com Flags| |needinfo?(otni.ledelay@gmai | |l.com) --- Comment #5 from Takashi Iwai <tiwai@suse.com> --- Just to be sure, could you check the kernel in OBS Kernel:stable repo? Note that it's an unofficial build, hence it won't boot with Secure Boot. If that kernel still shows the problem, please try the 5.16-rc kernel in OBS Kernel:HEAD repo, too. In anyway, please give the hwinfo output from the latest TW kernel, too. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193648 http://bugzilla.opensuse.org/show_bug.cgi?id=1193648#c6 Ledelay <otni.ledelay@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(otni.ledelay@gmai |needinfo? |l.com) | --- Comment #6 from Ledelay <otni.ledelay@gmail.com> --- (In reply to Takashi Iwai from comment #5)
Just to be sure, could you check the kernel in OBS Kernel:stable repo? Note that it's an unofficial build, hence it won't boot with Secure Boot.
If that kernel still shows the problem, please try the 5.16-rc kernel in OBS Kernel:HEAD repo, too.
In anyway, please give the hwinfo output from the latest TW kernel, too.
I don't know how to switch kernels, and I don't know whether/how I can safely disable secure boot. I'm a linux newb. 212:/sys/module # hwinfo --network --wlan --netcard 13: PCI 200.0: 0280 Network controller [Created at pci.386] Unique ID: [redacted] Parent ID: [redacted] SysFS ID: /devices/pci0000:00/0000:00:02.2/0000:02:00.0 SysFS BusID: 0000:02:00.0 Hardware Class: network Model: "MEDIATEK Network controller" Vendor: pci 0x14c3 "MEDIATEK Corp." Device: pci 0x7961 SubVendor: pci 0x1a3b "AzureWave" SubDevice: pci 0x4680 Memory Range: 0xff20300000-0xff203fffff (ro,non-prefetchable) Memory Range: 0xff20400000-0xff20403fff (ro,non-prefetchable) Memory Range: 0xff20404000-0xff20404fff (ro,non-prefetchable) IRQ: 89 (no events) Module Alias: "pci:v000014C3d00007961sv00001A3Bsd00004680bc02sc80i00" Driver Info #0: Driver Status: mt7921e is active Driver Activation Cmd: "modprobe mt7921e" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #32 (PCI bridge) 55: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: [redacted] SysFS ID: /class/net/enp4s0f3u1 SysFS Device Link: /devices/pci0000:00/0000:00:08.1/0000:04:00.3/usb1/1-1/1-1:1.0 Hardware Class: network interface Model: "Ethernet network interface" Driver: "rndis_host" Driver Modules: "rndis_host" Device File: enp4s0f3u1 HW Address: 3e:06:0b:1a:15:ec Link detected: yes Config Status: cfg=new, avail=yes, need=no, active=unknown 56: None 00.0: 10700 Loopback [Created at net.126] Unique ID: [redacted] SysFS ID: /class/net/lo Hardware Class: network interface Model: "Loopback network interface" Device File: lo Link detected: yes Config Status: cfg=new, avail=yes, need=no, active=unknown -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193648 http://bugzilla.opensuse.org/show_bug.cgi?id=1193648#c7 Ledelay <otni.ledelay@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo? | --- Comment #7 from Ledelay <otni.ledelay@gmail.com> --- (In reply to Takashi Iwai from comment #5)
Just to be sure, could you check the kernel in OBS Kernel:stable repo? Note that it's an unofficial build, hence it won't boot with Secure Boot.
If that kernel still shows the problem, please try the 5.16-rc kernel in OBS Kernel:HEAD repo, too.
In anyway, please give the hwinfo output from the latest TW kernel, too.
Turns out the warranty warning that I'd have to get my motherboard replaced if the TPM keys are lost don't apply to disabling secure boot. I remembered how to setup multiple kernels using YaST, and tried both Kernel:stable/standard and Kernel:HEAD/standard kernels. Neither resolved the issue. I will attach the journals. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193648 http://bugzilla.opensuse.org/show_bug.cgi?id=1193648#c8 --- Comment #8 from Ledelay <otni.ledelay@gmail.com> --- Created attachment 854549 --> http://bugzilla.opensuse.org/attachment.cgi?id=854549&action=edit output of 'journalctl --system --dmesg --boot -2', with /Kernel:/stable/standard/ -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193648 http://bugzilla.opensuse.org/show_bug.cgi?id=1193648#c9 --- Comment #9 from Ledelay <otni.ledelay@gmail.com> --- Created attachment 854550 --> http://bugzilla.opensuse.org/attachment.cgi?id=854550&action=edit output of 'journalctl --system --dmesg --boot 0', with /Kernel:/HEAD/standard/ -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193648 http://bugzilla.opensuse.org/show_bug.cgi?id=1193648#c10 --- Comment #10 from Takashi Iwai <tiwai@suse.com> --- Thanks. Does the problem happen no matter whether you do cold-boot (from power-off) or reset? I have seen some post on the net mentioning that WiFi works with 5.15 kernel after the cold boot. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193648 http://bugzilla.opensuse.org/show_bug.cgi?id=1193648#c11 --- Comment #11 from Ledelay <otni.ledelay@gmail.com> --- (In reply to Takashi Iwai from comment #10)
Thanks.
Does the problem happen no matter whether you do cold-boot (from power-off) or reset? I have seen some post on the net mentioning that WiFi works with 5.15 kernel after the cold boot.
It seems to work on cold boot, but only if my power is unplugged at the same time. This moves Linux from impossible to use to impractical to use for me. Discovered that that is a possible temporary workaround thanks to this comment from the upstream bug report: https://bugzilla.kernel.org/show_bug.cgi?id=214557#c7 I have also done zypper dup to move to version 20220107. Not resolved yet, but at least now I have a workaround. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193648 http://bugzilla.opensuse.org/show_bug.cgi?id=1193648#c13 Andreas Stieger <Andreas.Stieger@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |opensuse@wolli.com --- Comment #13 from Andreas Stieger <Andreas.Stieger@gmx.de> --- *** Bug 1195601 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193648 http://bugzilla.opensuse.org/show_bug.cgi?id=1193648#c14 Ledelay <otni.ledelay@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #14 from Ledelay <otni.ledelay@gmail.com> --- As of kernel version 5.17.4-1-default on openSUSE Tumbleweed version 20220426, this seems to be resolved. Restarting my device no longer reproduces the error. This might have been resolved in an earlier version without me noticing, but I just restarted to test it and did not get the error again. I'd like to thank anyone who has spent their valuable time to help resolve this issue. :) oled@OL:~> dmesg | grep -i mt79 [ 4.629134] mt7921e 0000:02:00.0: enabling device (0000 -> 0002) [ 4.649090] mt7921e 0000:02:00.0: ASIC revision: 79610010 [ 4.735739] mt7921e 0000:02:00.0: HW/SW Version: 0x8a108a10, Build Time: 20220311230842a [ 4.763563] mt7921e 0000:02:00.0: WM Firmware Version: ____010000, Build Time: 20220311230931 -- You are receiving this mail because: You are the assignee for the bug.
participants (1)
-
bugzilla_noreply＠suse.com