http://bugzilla.opensuse.org/show_bug.cgi?id=1193648 Ledelay 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#c3 --- Comment #3 from Ledelay --- (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#c5 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |otni.ledelay@gmail.com, | |tiwai@suse.com Flags| |needinfo?(otni.ledelay@gmai | |l.com) --- Comment #5 from Takashi Iwai --- 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#c7 Ledelay changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo? | --- Comment #7 from Ledelay --- (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#c9 --- Comment #9 from Ledelay --- 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#c11 --- Comment #11 from Ledelay --- (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#c14 Ledelay changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #14 from Ledelay --- 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.