January 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1180543] kernel 5.10.4: Displays never wake up, though on one system it does... network is also dead
by bugzilla_noreply＠suse.com 12 Jan '21

12 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180543 https://bugzilla.suse.com/show_bug.cgi?id=1180543#c28 --- Comment #28 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Bit Juggler from comment #27) > Now and then i roam the forums and occasionally get asked to file a bug > report. Replies like comment #5 or #22 are of no avail and really > discouraging and have stopped me from doing so a long time ago. > > If openSUSE developers want to use bugzilla to improve their software then > that sort of replies does not look very promising to me. On the other hand, only adding me-too comments (like your comment #4), without actually trying what was already suggested (comment #3) only makes our lives harder. Not speaking about trying what was _not_ suggested and is obviously different from what was suggested. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180543] kernel 5.10.4: Displays never wake up, though on one system it does... network is also dead
by bugzilla_noreply＠suse.com 12 Jan '21

12 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180543 https://bugzilla.suse.com/show_bug.cgi?id=1180543#c27 --- Comment #27 from Bit Juggler <suse.junky(a)t-online.de> --- (In reply to Takashi Iwai from comment #25) > Please don't play pingpong. > Thank you very much for your elaborate and helpful statement! Sorry! I do not want to cause any disturbance. Now and then i roam the forums and occasionally get asked to file a bug report. Replies like comment #5 or #22 are of no avail and really discouraging and have stopped me from doing so a long time ago. If openSUSE developers want to use bugzilla to improve their software then that sort of replies does not look very promising to me. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1179367] Driver brcmfmac for Broadcom 43430 or firmware does not use channel 12 and 13 on WiFi 2.4GHz
by bugzilla_noreply＠suse.com 12 Jan '21

12 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1179367 Bug 1179367 depends on bug 1179308, which changed state. Bug 1179308 Summary: Image X11 for Raspberry Pi 3B is missing packages for WLAN for 2.4GHz channel 12 and 13 http://bugzilla.opensuse.org/show_bug.cgi?id=1179308 What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1179367] Driver brcmfmac for Broadcom 43430 or firmware does not use channel 12 and 13 on WiFi 2.4GHz
by bugzilla_noreply＠suse.com 12 Jan '21

12 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1179367 http://bugzilla.opensuse.org/show_bug.cgi?id=1179367#c5 --- Comment #5 from Dr. Werner Fink <werner(a)suse.com> --- (In reply to Takashi Iwai from comment #4) > (In reply to Dr. Werner Fink from comment #3) > > Is there a reason why this > > > > https://patchwork.kernel.org/project/linux-wireless/patch/20171006135532. > > 29550-2-johannes(a)sipsolutions.net/ > > > > does not work with as least the brcmfmac driver kerne module? > > The patch was merged in 4.17, so it must be effective in Leap 15.2 kernel. > The feature is in cfg80211, and it should be independent from brcmfmac... Without hacking the firmware config /lib/firmware/brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.txt it does not work for brcmfmac ... btw. on an intel laptop cfg80211 does its job well and the command ``iw reg get`` lists the global as well as the phy#0 configuration ... on the raspberry only the global one is shown: bash> iw reg get global country DE: DFS-ETSI (2400 - 2483 @ 40), (N/A, 20), (N/A) (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW (5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS (5725 - 5875 @ 80), (N/A, 13), (N/A) (57000 - 66000 @ 2160), (N/A, 40), (N/A) ... here with the hacked firmware config as otherwise I do not have network at all. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180799] No keyboard input available in installer or during boot on RPi4
by bugzilla_noreply＠suse.com 12 Jan '21

12 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180799 https://bugzilla.suse.com/show_bug.cgi?id=1180799#c2 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fvogt(a)suse.com --- Comment #2 from Fabian Vogt <fvogt(a)suse.com> --- Related to bug 1180336? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180442] New: amdgpu not detected on boot with eDP connector
by bugzilla_noreply＠suse.com 12 Jan '21

12 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1180442 Bug ID: 1180442 Summary: amdgpu not detected on boot with eDP connector Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: jshand2013(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 844743 --> http://bugzilla.opensuse.org/attachment.cgi?id=844743&action=edit Hardware Profile Hi there, just tried kernel version 5.10.3 and unfortunately I still need to specify nomodeset in the grub command line, not graphics driver listed. must be llvmpipe instead. -- You are receiving this mail because: You are the assignee for the bug.

1 24

[Bug 1180543] kernel 5.10.4: Displays never wake up, though on one system it does... network is also dead
by bugzilla_noreply＠suse.com 12 Jan '21

12 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180543 https://bugzilla.suse.com/show_bug.cgi?id=1180543#c26 --- Comment #26 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Bit Juggler from comment #24) > However it would have been of much more help to explain why there is > supposed to be a difference between supplying an option to a module via > kernel command line or supplying it via a file in /etc/modprobe.d There is none if done right, of course. But noone here suggested this. If someone wants to do it differently, they are free to, but don't complain when it doesn't work. The workaround suggested here apparently works for others. The kernel was fixed too, so why would one to reopen this already fixed bug in the first place? That is, if someone still has an issue (where the _suggested_ workaround doesn't work), open a new bug. P.S. The problem is elsewhere: the parameter is wrong (look at it, it's _obvious_, so the comment was aimed that way). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180543] kernel 5.10.4: Displays never wake up, though on one system it does... network is also dead
by bugzilla_noreply＠suse.com 12 Jan '21

12 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180543 https://bugzilla.suse.com/show_bug.cgi?id=1180543#c25 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED --- Comment #25 from Takashi Iwai <tiwai(a)suse.com> --- Please don't play pingpong. There are two ways to pass the module options. One is to pass via boot option, and in this case, the format is MODULENAME.OPTION=VALUE So you'd need to pass snd_hda_codec_hdmi.enable_silent_stream=0 there. OTOH, alternative is to pass via a module config file in /etc/modprobe.d/*.conf file, and in this case, the format is options MODULENAME OPTION=VALUE So you'd need to create a file /etc/modprobe.d/hda.conf containing options snd_hda_codec_hdmi enable_silent_stream=0 instead. In anyway, the fix appears in 5.10.5 kernel package. Please test with it, then you need no workaround any longer. Reopen the entry only if the issue is still seen with the new package. Thanks. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180543] kernel 5.10.4: Displays never wake up, though on one system it does... network is also dead
by bugzilla_noreply＠suse.com 12 Jan '21

12 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180543 https://bugzilla.suse.com/show_bug.cgi?id=1180543#c24 Bit Juggler <suse.junky(a)t-online.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #24 from Bit Juggler <suse.junky(a)t-online.de> --- (In reply to Jiri Slaby from comment #22) > (In reply to filippos Filippos from comment #21) > > Tried: > > sudo vi /etc/modprobe.d/snd_hda.conf > > options snd_hda_codec_hdmi.enable_silent_stream=N > > > > but it doesn't fix > > Obviously. What a witty remark! However it would have been of much more help to explain why there is supposed to be a difference between supplying an option to a module via kernel command line or supplying it via a file in /etc/modprobe.d -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180543] kernel 5.10.4: Displays never wake up, though on one system it does... network is also dead
by bugzilla_noreply＠suse.com 12 Jan '21

12 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180543 https://bugzilla.suse.com/show_bug.cgi?id=1180543#c23 --- Comment #23 from Petr Vorel <petr.vorel(a)suse.com> --- (In reply to filippos Filippos from comment #21) > Same error here: screen frozen, net frozen, usb, mice & keyboards frozen. > > Tried: > sudo vi /etc/modprobe.d/snd_hda.conf > options snd_hda_codec_hdmi.enable_silent_stream=N > > but it doesn't fix > @Filippos You need to add it to GRUB_CMDLINE_LINUX or GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub and update grub (grub2-mkconfig -o /boot/grub2/grub.cfg). -- You are receiving this mail because: You are the assignee for the bug.

1 0