November 2023 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1217499] New: Steam Deck usb drd driver isn't loaded
by bugzilla_noreply＠suse.com 27 Nov '23

27 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1217499 Bug ID: 1217499 Summary: Steam Deck usb drd driver isn't loaded Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: monkeyboyted(a)yahoo.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 870985 --> https://bugzilla.suse.com/attachment.cgi?id=870985&action=edit lspci -vnn Hi, I just realize the usb drd driver for the steam deck isn't loaded. My deck has drd enabled in the kernel but the driver isn't in lsmod. lsb_release -a LSB Version: n/a Distributor ID: openSUSE Description: openSUSE Tumbleweed Release: 20231122 Codename: n/a Linux steamdeck.lan 6.6.2-1-default #1 SMP PREEMPT_DYNAMIC Mon Nov 20 11:22:36 UTC 2023 (263a855) x86_64 x86_64 x86_64 GNU/Linux 04:00.4 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] VanGogh USB1 [1022:163b] (prog-if 30 [XHCI]) Subsystem: Valve Software Device [1e44:1776] Flags: bus master, fast devsel, latency 0, IRQ 56, IOMMU group 4 Memory at 80100000 (64-bit, non-prefetchable) [size=1M] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [64] Express Endpoint, MSI 00 Capabilities: [a0] MSI: Enable- Count=1/8 Maskable- 64bit+ Capabilities: [c0] MSI-X: Enable+ Count=8 Masked- Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Kernel driver in use: xhci_hcd Kernel modules: xhci_pci https://gitlab.freedesktop.org/drm/amd/-/issues/2984 doof@steamdeck:~> sudo modprobe dw3 modprobe: FATAL: Module dw3 not found in directory /usr/lib/modules/6.6.2-1-default doof@steamdeck:~> sudo modprobe dw3_pci modprobe: FATAL: Module dw3_pci not found in directory /usr/lib/modules/6.6.2-1-default -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1217315] New: [LenovoX13s] Screen remains black with live images and JeOS images
by bugzilla_noreply＠suse.com 27 Nov '23

27 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1217315 Bug ID: 1217315 Summary: [LenovoX13s] Screen remains black with live images and JeOS images Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de CC: chester.lin(a)suse.com Target Milestone: --- Found By: --- Blocker: --- On the Lenovo X13s laptop, we are able to boot DVD ISO from USB just fine, but Live images [0] and JeOS images [1] are not able to display anything on the screen. I suspect the initrd is missing some kernel drivers, but failed to find which ones so far. [0]: https://build.opensuse.org/project/show/openSUSE:Factory:ARM:Live [1]: https://build.opensuse.org/package/show/openSUSE:Factory:ARM/JeOS -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1217467] Application Windows Flickering, black surrounding windows, or blank (black) app window
by bugzilla_noreply＠suse.com 27 Nov '23

27 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1217467 https://bugzilla.suse.com/show_bug.cgi?id=1217467#c2 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- FWIW, a similar report in bug 1217484 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217467] Application Windows Flickering, black surrounding windows, or blank (black) app window
by bugzilla_noreply＠suse.com 27 Nov '23

27 Nov '23

1 0

[Bug 1217291] Kernel 6.6 regression: Wacom tablet detected as USB hub
by bugzilla_noreply＠suse.com 27 Nov '23

27 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1217291 https://bugzilla.suse.com/show_bug.cgi?id=1217291#c6 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-bugs(a)opensuse.org |oneukum(a)suse.com --- Comment #6 from Takashi Iwai <tiwai(a)suse.com> --- Thanks, so it looks like a typical issue via Thunderbolt port. Tossed to Oliver, who has a better clue. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217282] kernel-default-6.6.1 fails to boot
by bugzilla_noreply＠suse.com 27 Nov '23

27 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1217282 https://bugzilla.suse.com/show_bug.cgi?id=1217282#c10 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #10 from Takashi Iwai <tiwai(a)suse.com> --- The patch was merged to stable tree for TW. I close the bug for now. Feel free to reopen if the kernel still shows the very same problem. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217512] [RPi4] kernel: vc4_hdmi fef00700.hdmi: Could not register PCM component: -517
by bugzilla_noreply＠suse.com 27 Nov '23

27 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1217512 https://bugzilla.suse.com/show_bug.cgi?id=1217512#c4 Ivan Ivanov <ivan.ivanov(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED --- Comment #4 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- (In reply to Takashi Iwai from comment #2) > -517 is -EPROBE_DEFER, and this itself isn't wrong. (The driver can use > dev_err_probe() for hiding the EPROBE_DEFER error, though.) > > Doesn't the device work afterward at all? I'm afraid not, the HDMI output doesn't work. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217512] [RPi4] kernel: vc4_hdmi fef00700.hdmi: Could not register PCM component: -517
by bugzilla_noreply＠suse.com 27 Nov '23

27 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1217512 https://bugzilla.suse.com/show_bug.cgi?id=1217512#c3 --- Comment #3 from Guillaume GARDET <guillaume.gardet(a)arm.com> --- (In reply to Takashi Iwai from comment #2) > -517 is -EPROBE_DEFER, and this itself isn't wrong. (The driver can use > dev_err_probe() for hiding the EPROBE_DEFER error, though.) > > Doesn't the device work afterward at all? It has been detected on openQA headless RPi4 and my hdmi cable is broken, so I cannot test on my 2nd RPi4. @Ivan, would you be able to test? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217512] [RPi4] kernel: vc4_hdmi fef00700.hdmi: Could not register PCM component: -517
by bugzilla_noreply＠suse.com 27 Nov '23

27 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1217512 https://bugzilla.suse.com/show_bug.cgi?id=1217512#c2 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- -517 is -EPROBE_DEFER, and this itself isn't wrong. (The driver can use dev_err_probe() for hiding the EPROBE_DEFER error, though.) Doesn't the device work afterward at all? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217512] [RPi4] kernel: vc4_hdmi fef00700.hdmi: Could not register PCM component: -517
by bugzilla_noreply＠suse.com 27 Nov '23

27 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1217512 https://bugzilla.suse.com/show_bug.cgi?id=1217512#c1 Ivan Ivanov <ivan.ivanov(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mbrugger(a)suse.com, | |patrik.jakobsson(a)suse.com, | |tzimmermann(a)suse.com --- Comment #1 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- Adding DRM experts. -- You are receiving this mail because: You are the assignee for the bug.

1 0