May 2023 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1211761] New: vtty[1-6] nouveau framebuffers produce vast snow/raster on right and bottom border areas on the larger resolution of two displays, in the absence of both plymouth and video= on linu lines
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1211761 Bug ID: 1211761 Summary: vtty[1-6] nouveau framebuffers produce vast snow/raster on right and bottom border areas on the larger resolution of two displays, in the absence of both plymouth and video= on linu lines Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 URL: https://bugzilla.kernel.org/show_bug.cgi?id=217479 ; https://gitlab.freedesktop.org/drm/nouveau/-/issues/21 4 OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: mrmazda(a)earthlink.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Original Summary: vtty[1-6] nouveau framebuffers produce vast snow/raster on right and bottom border areas on the larger resolution of two displays, in the absence of both plymouth and video= on linu lines FTR: Upstream bugs: https://bugzilla.kernel.org/show_bug.cgi?id=217479 (includes most detail, w/ dmesg) https://gitlab.freedesktop.org/drm/nouveau/-/issues/214 To reproduce: 1-connect two unequal native resolution displays to a Tesla or Firmi GPU 2-don't have plymouth in use (I don't ever have it installed, so don't know whether it impacts) 3-don't include e.g. video=1440x900@60 directive on Grub's linu lines 4-boot TW 5-switch to a vtty, e.g. Ctrl-Alt-F3 Actual behavior: 1-Both displays utilize the resolution (same pixel grid) of the lower resolution display 2-Lower resolution display behaves as expected (light text on black background) 3-Higher resolution display uses same pixels as lower resolution display, with light text on black background, leaving right side and bottom raster instead of black Expected behavior: 1-Both displays utilize the resolution (same pixel grid) of the lower resolution display 2-Lower resolution display behaves as expected 3-Entire higher resolution display's background is black instead of portions in raster Workaround: add e.g. video=1440x900@60 to Grub's linu lines, which causes both displays to use the same nominal mode on the full display space. Occurs with TW 6.3.2, 6.2.12 & 6.2.4 kernel-default, and with 6.2.15 on Fedora 38 and Mageia 9. Does not occur with TW 6.1.12 kernel-default on NVidia, or with AMD Caicos (Terascale2) GPU, or with Intel Eaglelake GPU. Tested only on legacy booting (no UEFI support). Others might describe what I call "raster" as multicolored snow. nosimplefb=1 doesn't change anything. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[kernel-bugs] Account verification
by noreply＠suse.de 18 Nov '24

18 Nov '24

Dear user opensuse-kernelbugs, we have received your email verification request. To verify your email address, please follow this link: https://idp-portal.suse.com/univention/self-service/#page=verifyaccount&tok… If the link does not work, you can go to https://idp-portal.suse.com/univention/self-service/#page=verifyaccount and enter the following token manually: vNjCDHqnMwqYa48z3RokLQTpZdp3sYBxddU7iGJR9UhboG8guN3hssVvHHxVARWo -- To unsubscribe, e-mail: kernel-bugs+unsubscribe(a)opensuse.org To contact the owner, e-mail: kernel-bugs+owner(a)opensuse.org

2 1

[kernel-bugs] [Bug 1172181] test bug for assignee change
by bugzilla_noreply＠suse.com 18 Nov '24

18 Nov '24

http://bugzilla.suse.com/show_bug.cgi?id=1172181 Jeff Mahoney <jeffm(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|jeffm(a)suse.com |kernel-bugs(a)opensuse.org -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

2 1

[Bug 1211380] New: Keyboard not working on laptop ASUS TUF FA507NU
by bugzilla_noreply＠suse.com 15 Nov '24

15 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1211380 Bug ID: 1211380 Summary: Keyboard not working on laptop ASUS TUF FA507NU 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: julien.colinet(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 867003 --> https://bugzilla.suse.com/attachment.cgi?id=867003&action=edit lsmod output Hello, I have an issue with my laptop keyboard. The keyboard is not working, only a few keys are working, the mic mute, keyboard backlight and screen brightness. I have to use an USB keyboard for the moment. ASUS TUF A15 FA507NU AMD 7735HS nVidia RTX 4050 Keyboard vas working on Xubuntu with kernel 5.19. With kernel 6.2 it doesn't work with Xubuntu, Endeavour and Leap/Tumbleweed. I installed a newer snapshot of Tumbleweed with 6.3 kernel but it doesn't change anything. The bug is similar to this one: https://bugzilla.kernel.org/show_bug.cgi?id=217336 The keyboard is working fine under Windows 11, so for now I use my laptop on Windows but it would be great if this bug can be solved so I can use Tumbleweed -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 1211352] New: ThinkPad T14s Gen 2a hangs up on s2ram resume
by bugzilla_noreply＠suse.com 15 Nov '24

15 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1211352 Bug ID: 1211352 Summary: ThinkPad T14s Gen 2a hangs up on s2ram resume Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dheidler(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 866978 --> https://bugzilla.suse.com/attachment.cgi?id=866978&action=edit hwinfo.txt The suspend mode selector that can be set to windows or linux is set to linux via UEFI/BIOS setup. The suspend seems to work fine. The system suspends and the power led begins to flash. On resume the screen stays dark - the backlight does light up, though. It it not possible to switch to a tty. ``` cat /etc/systemd/logind.conf | grep -v '^#' [Login] HandlePowerKey=suspend HandleLidSwitch=ignore ``` -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 1211428] New: Steam deck speaker is quiet.
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1211428 Bug ID: 1211428 Summary: Steam deck speaker is quiet. 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: --- Hi everyone, Steam deck speakers finally works in both speakers. Speaker-test works. However, I also notice the sound is quiet compared to SteamOS. Can you fix it? speaker-test -Dplughw:1,1 -c2 Linux steamdeck.lan 6.4.0-rc2-1.g679133f-default #1 SMP PREEMPT_DYNAMIC Sun May 14 21:09:47 UTC 2023 (679133f) x86_64 x86_64 x86_64 GNU/Linux LSB Version: n/a Distributor ID: openSUSE Description: openSUSE Tumbleweed Release: 20230514 Codename: n/a -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 1211796] New: kernel modules not usrmerged
by bugzilla_noreply＠suse.com 27 Feb '24

27 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1211796 Bug ID: 1211796 Summary: kernel modules not usrmerged 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: msuchanek(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Currently kernel modules are installed through compatibility symlink, and te assumed location is in /lib. Patch kmod and kernel-binary.spec.in to not rely on this symlink. -- You are receiving this mail because: You are the assignee for the bug.

1 22

[Bug 1210791] New: KMP builds fails with ld: cannot find arch/s390/lib/expoline/expoline.o
by bugzilla_noreply＠suse.com 27 Feb '24

27 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1210791 Bug ID: 1210791 Summary: KMP builds fails with ld: cannot find arch/s390/lib/expoline/expoline.o Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: S/390-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ptesarik(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Out-of-tree kernel modules can no longer be built for openSUSE:Factory:zSystems. See See https://build.opensuse.org/build/Kernel:kdump/openSUSE_Factory_zSystems/s39… [ 783s] + make -C /usr/src/linux-obj/s390x/default modules M=/home/abuild/rpmbuild/BUILD/crash-8.0.2/kbuild/default [ 783s] CC [M] /home/abuild/rpmbuild/BUILD/crash-8.0.2/kbuild/default/crash.o [ 784s] MODPOST /home/abuild/rpmbuild/BUILD/crash-8.0.2/kbuild/default/Module.symvers [ 784s] CC [M] /home/abuild/rpmbuild/BUILD/crash-8.0.2/kbuild/default/crash.mod.o [ 784s] LD [M] /home/abuild/rpmbuild/BUILD/crash-8.0.2/kbuild/default/crash.ko [ 784s] ld: cannot find arch/s390/lib/expoline/expoline.o: No such file or directory [ 784s] make[1]: *** [/usr/src/linux-6.2.12-1/scripts/Makefile.modfinal:61: /home/abuild/rpmbuild/BUILD/crash-8.0.2/kbuild/default/crash.ko] Error 1 [ 784s] make: *** [../../../linux-6.2.12-1/Makefile:1953: modules] Error 2 [ 784s] error: Bad exit status from /var/tmp/rpm-tmp.6wzRBp (%build) -- You are receiving this mail because: You are the assignee for the bug.

1 17

[Bug 1211117] New: 50-check-kernel-build-id fails to extract vmlinux
by bugzilla_noreply＠suse.com 27 Nov '23

27 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1211117 Bug ID: 1211117 Summary: 50-check-kernel-build-id fails to extract vmlinux Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: S/390-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: msuchanek(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When looking at build log from random stable kernel build I get this: [17308s] ... running 50-check-kernel-build-id [17309s] ... Verifying kernel build-ids for kernel-default 6.3.1-1.gdd8cfff s390x [17309s] ... Processing kernel rpms in '//home/abuild/rpmbuild/RPMS/s390x' [17909s] ... Unable to extract ./usr/lib/modules/6.3.1-1.gdd8cfff-default/vmlinux.xz from //home/abuild/rpmbuild/RPMS/s390x/kernel-default-debuginfo-6.3.1-1.1.gdd8cfff.s390x.rpm [17910s] Giving up vmlinux.xz is in kernel-default, not kernel-default-debuginfo. Either the message is misleading or the script is looking in the wrong place. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1211224] New: How does Nvidia KMP work with dracut uefi_secureboot_cert solution when no MOK?
by bugzilla_noreply＠suse.com 24 Jul '23

24 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1211224 Bug ID: 1211224 Summary: How does Nvidia KMP work with dracut uefi_secureboot_cert solution when no MOK? 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: jlee(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- This issue is derived from boo#1211166. The openSUSE tumbleweed kernel can work with MOK for Nvidia KMP now. But in the dracut uefi_secureboot_cert case, it doesn't use shim, which means that MOK is not available. How does Nvidia RPM works with dracut solution for modsign? Even when lockdown be enabled in kernel? Does dracut uefi_secureboot_cert solution support dynamic local generated one time key? Nvidia KMP needs the solution. -- You are receiving this mail because: You are the assignee for the bug.

1 6