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.