July 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1165273] New: zathura-plugin-pdf-mupdf not loaded due to error.
by bugzilla_noreply＠novell.com 31 Jan '23

31 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1165273 Bug ID: 1165273 Summary: zathura-plugin-pdf-mupdf not loaded due to error. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: dracaphallus(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.100 Safari/537.36 Build Identifier: Running zathura after the installation of zathura-plugin-pdf-mupdf the following error output is produced: ``` error: Could not load plugin '/usr/lib64/zathura/libpdf-mupdf.so' (/usr/lib64/zathura/libpdf-mupdf.so: undefined symbol: jpeg_resync_to_restart). ``` >From the error output I'd deduced that the package was packaged wrong and therefore produced the error mentioned above. It has the plugin from working as intended by making zathura incapable of opening the supported document formats (PDF, ePub, and OpenXPS). This issue was reported 14 days ago using the comment section of openSUSE:Factory, while it was reported 8 days ago in the comment section of `X11:Utilities` with no response. This has lead me to file a bug report in OpenSUSE Bugzilla with the hope of getting this issue resolved. Reproducible: Always Steps to Reproduce: 1. Installing zathura-plugin-pdf-mupdf using zypper. 2. Running zathura through terminal. Actual Results: The following error was produced: ``` error: Could not load plugin '/usr/lib64/zathura/libpdf-mupdf.so' (/usr/lib64/zathura/libpdf-mupdf.so: undefined symbol: jpeg_resync_to_restart). ``` Expected Results: Zathura being able to open the supported document formats (PDF, ePub, and OpenXPS). -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1200564] New: io_uring instability on ppc64
by bugzilla_noreply＠suse.com 30 Jan '23

30 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1200564 Bug ID: 1200564 Summary: io_uring instability on ppc64 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: PowerPC-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dmueller(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- when using aio=io_uring in qemu for KVM virtual machine guests on a SLE15SP4 or a opensuse tumbleweed host kernel on power8 or power9 machine, we have very rapid I/O corruption (within milliseconds-seconds) in the guest. on all other architectures things work perfectly fine. -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1195291] New: initrd is being rebuilt when kernel is being removed after kernel update
by bugzilla_noreply＠suse.com 28 Jan '23

28 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1195291 Bug ID: 1195291 Summary: initrd is being rebuilt when kernel is being removed after kernel update Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Despite of the problem that initrds are needlessy rebuilt when installing kernel modules (bug 1100885, bug 1191322), there are also needless rebuilds when removing obsolete kernels: Still on the next boot when older kernels are removed, their initrds are being rebuilt before the kernels are removed (it seems at least). Example (combining extracts from journal and /var/log/zypp/history): Jan 27 21:36:03 i7.site [RPM][7347]: install kernel-default-5.3.18-150300.59.43.1.x86_64: success Jan 27 21:36:04 i7.site [RPM][17173]: erase kernel-macros-5.3.18-59.40.1.noarch: success Jan 27 21:36:05 i7.site [RPM][17173]: install kernel-macros-5.3.18-150300.59.43.1.noarch: success Jan 27 21:36:06 i7.site [RPM][17173]: erase kernel-macros-5.3.18-59.40.1.noarch: success Jan 27 21:36:06 i7.site [RPM][17173]: install kernel-macros-5.3.18-150300.59.43.1.noarch: success Jan 27 21:37:32 i7.site [RPM][17175]: install kernel-preempt-5.3.18-150300.59.43.1.x86_64: success Jan 27 21:37:47 i7.site [RPM][27390]: install kernel-default-extra-5.3.18-150300.59.43.1.x86_64: success Jan 27 21:37:55 i7.site [RPM][27492]: install kernel-devel-5.3.18-150300.59.43.1.noarch: success Jan 27 21:37:55 i7.site [RPM][27492]: install kernel-devel-5.3.18-150300.59.43.1.noarch: success Jan 27 21:38:03 i7.site [RPM][27497]: install kernel-preempt-extra-5.3.18-150300.59.43.1.x86_64: success Jan 27 21:38:25 i7.site [RPM][27675]: install kernel-default-optional-5.3.18-150300.59.43.1.x86_64: success Jan 27 21:38:28 i7.site [RPM][27776]: install kernel-preempt-devel-5.3.18-150300.59.43.1.x86_64: success Jan 27 21:38:28 i7.site [RPM][27776]: install kernel-preempt-devel-5.3.18-150300.59.43.1.x86_64: success Jan 27 21:38:31 i7.site [RPM][27782]: install kernel-default-devel-5.3.18-150300.59.43.1.x86_64: success Jan 27 21:38:31 i7.site [RPM][27782]: install kernel-default-devel-5.3.18-150300.59.43.1.x86_64: success Jan 27 21:38:37 i7.site [RPM][27788]: install kernel-preempt-optional-5.3.18-150300.59.43.1.x86_64: success # 2022-01-27 21:43:41 Output of kernel-default-extra-5.3.18-150300.59.43.1.x86_64.rpm %posttrans script: # Creating initrd: /boot/initrd-5.3.18-150300.59.43-default # Creating initrd: /boot/initrd-5.3.18-150300.59.43-preempt # Creating initrd: /boot/initrd-5.3.18-59.40-default # Creating initrd: /boot/initrd-5.3.18-59.40-preempt ### Reboot ### Jan 28 20:24:49 i7 zypper[1916]: The following 9 packages are going to be REMOVED: Jan 28 20:24:49 i7 zypper[1916]: kernel-default-5.3.18-59.37.2 kernel-default-devel-5.3.18-59.37.2 kernel-default-extra-5.3.18-59.37.2 kernel-default-optional-5.3.18-59.37.2 kernel-devel-5.3.18-59.37.2 kernel-preempt-5.3.18-59.37.2 kernel-preempt-devel-5.3.18-59.37.2 kernel-preempt-extra-5.3.18-59.37.2 kernel-preempt-optional-5.3.18-59.37.2 Jan 28 20:24:49 i7 zypper[1916]: 9 packages to remove. Jan 28 20:27:04 i7.site [RPM][2887]: erase kernel-default-devel-5.3.18-59.37.2.x86_64: success Jan 28 20:27:07 i7.site [RPM][2887]: erase kernel-default-devel-5.3.18-59.37.2.x86_64: success Jan 28 20:27:07 i7.site zypper[1916]: (1/9) Removing kernel-default-devel-5.3.18-59.37.2.x86_64 [.....done] Jan 28 20:27:08 i7.site [RPM][4137]: erase kernel-default-optional-5.3.18-59.37.2.x86_64: success Jan 28 20:31:10 i7.site [RPM][4137]: erase kernel-default-optional-5.3.18-59.37.2.x86_64: success Jan 28 20:31:10 i7.site zypper[1916]: (2/9) Removing kernel-default-optional-5.3.18-59.37.2.x86_64 [.....done] Jan 28 20:31:11 i7.site [RPM][11952]: erase kernel-preempt-devel-5.3.18-59.37.2.x86_64: success Jan 28 20:31:20 i7.site [RPM][11952]: erase kernel-preempt-devel-5.3.18-59.37.2.x86_64: success Jan 28 20:31:20 i7.site zypper[1916]: (3/9) Removing kernel-preempt-devel-5.3.18-59.37.2.x86_64 [.....done] Jan 28 20:31:20 i7.site [RPM][11958]: erase kernel-preempt-optional-5.3.18-59.37.2.x86_64: success Jan 28 20:32:24 i7.site [RPM][11958]: erase kernel-preempt-optional-5.3.18-59.37.2.x86_64: success Jan 28 20:32:24 i7.site zypper[1916]: (4/9) Removing kernel-preempt-optional-5.3.18-59.37.2.x86_64 [.....done] Jan 28 20:32:25 i7.site [RPM][19401]: erase kernel-default-extra-5.3.18-59.37.2.x86_64: success Jan 28 20:33:13 i7.site [RPM][19401]: erase kernel-default-extra-5.3.18-59.37.2.x86_64: success Jan 28 20:33:13 i7.site zypper[1916]: (5/9) Removing kernel-default-extra-5.3.18-59.37.2.x86_64 [.....done] Jan 28 20:33:13 i7.site zypper[1916]: Creating initrd: /boot/initrd-5.3.18-59.37-default # Creating initrd: /boot/initrd-5.3.18-59.37-default Jan 28 20:33:17 i7.site [RPM][26818]: erase kernel-devel-5.3.18-59.37.2.noarch: success Jan 28 20:33:24 i7.site [RPM][26818]: erase kernel-devel-5.3.18-59.37.2.noarch: success Jan 28 20:33:24 i7.site zypper[1916]: (6/9) Removing kernel-devel-5.3.18-59.37.2.noarch [.....done] Jan 28 20:33:24 i7.site [RPM][26819]: erase kernel-preempt-extra-5.3.18-59.37.2.x86_64: success Jan 28 20:34:11 i7.site [RPM][26819]: erase kernel-preempt-extra-5.3.18-59.37.2.x86_64: success Jan 28 20:34:11 i7.site zypper[1916]: (7/9) Removing kernel-preempt-extra-5.3.18-59.37.2.x86_64 [.....done] Jan 28 20:34:11 i7.site zypper[1916]: Creating initrd: /boot/initrd-5.3.18-59.37-preempt # Creating initrd: /boot/initrd-5.3.18-59.37-preempt Jan 28 20:34:12 i7.site [RPM][1784]: erase kernel-default-5.3.18-59.37.2.x86_64: success Jan 28 20:34:43 i7.site [RPM][1784]: erase kernel-default-5.3.18-59.37.2.x86_64: success Jan 28 20:34:43 i7.site zypper[1916]: (8/9) Removing kernel-default-5.3.18-59.37.2.x86_64 [.....done] Jan 28 20:34:44 i7.site [RPM][4725]: erase kernel-preempt-5.3.18-59.37.2.x86_64: success Jan 28 20:35:15 i7.site [RPM][4725]: erase kernel-preempt-5.3.18-59.37.2.x86_64: success Jan 28 20:35:15 i7.site zypper[1916]: (9/9) Removing kernel-preempt-5.3.18-59.37.2.x86_64 [.....done] Jan 28 20:35:15 i7.site systemd[1]: purge-kernels.service: Succeeded. In addition to rebuiling the initrds, the bootloader was reinstalled (including the os-prober), so the removal of the old kernels took 10 minutes alltogether! # grep run_command.*grub2 /var/log/pbl.log 2022-01-27 21:35:35 <1> update-bootloader-7882 run_command.294: '/usr/lib/bootloader/grub2/config' = 0, output: 2022-01-27 21:36:03 <1> bootloader_entry-1449 run_command.294: '/usr/lib/bootloader/grub2/config' = 0, output: 2022-01-27 21:37:03 <1> update-bootloader-9958 run_command.294: '/usr/lib/bootloader/grub2/config' = 0, output: 2022-01-27 21:37:32 <1> bootloader_entry-8996 run_command.294: '/usr/lib/bootloader/grub2/config' = 0, output: 2022-01-27 21:41:39 <1> update-bootloader-8968 run_command.294: '/usr/lib/bootloader/grub2/config' = 0, output: 2022-01-27 21:42:20 <1> update-bootloader-0547 run_command.294: '/usr/lib/bootloader/grub2/config' = 0, output: 2022-01-27 21:43:00 <1> update-bootloader-6949 run_command.294: '/usr/lib/bootloader/grub2/config' = 0, output: 2022-01-27 21:43:41 <1> update-bootloader-7629 run_command.294: '/usr/lib/bootloader/grub2/config' = 0, output: 2022-01-28 20:31:09 <1> update-bootloader-0043 run_command.294: '/usr/lib/bootloader/grub2/config' = 0, output: 2022-01-28 20:32:23 <1> update-bootloader-4882 run_command.294: '/usr/lib/bootloader/grub2/config' = 0, output: 2022-01-28 20:33:12 <1> update-bootloader-4790 run_command.294: '/usr/lib/bootloader/grub2/config' = 0, output: 2022-01-28 20:34:11 <1> update-bootloader-4190 run_command.294: '/usr/lib/bootloader/grub2/config' = 0, output: 2022-01-28 20:34:43 <1> bootloader_entry-0829 run_command.294: '/usr/lib/bootloader/grub2/config' = 0, output: 2022-01-28 20:35:14 <1> bootloader_entry-7074 run_command.294: '/usr/lib/bootloader/grub2/config' = 0, output: Reinstalling the boot loader 15 times when updating two kernels!? -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1199195] New: pinebook hibernation
by bugzilla_noreply＠suse.com 28 Jan '23

28 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1199195 Bug ID: 1199195 Summary: pinebook hibernation Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: werwolf131313(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- > [werwolf@pbp] ~ > �� cat /proc/cmdline > BOOT_IMAGE=/boot/Image-5.17.4-1-default root=UUID=88f4ab19-f7b4-4d30-9322-096925da5034 resume=UUID=842067e2-7348-4ecc-82fa-89eb049dd35f loglevel=3 splash=silent systemd.show_status=1 delayacct mitigations=off security=apparmor > [werwolf@pbp] ~ > �� cat /etc/default/grub| grep -i cmdline > GRUB_CMDLINE_LINUX_DEFAULT="resume=UUID=842067e2-7348-4ecc-82fa-89eb049dd35f loglevel=3 splash=silent systemd.show_status=1 delayacct mitigations=off security=apparmor" > GRUB_CMDLINE_LINUX="" > [werwolf@pbp] ~ > �� cat /etc/dracut.conf.d/resume.conf > add_dracutmodules+=" resume " > [werwolf@pbp] ~ > �� sudo lsinitrd /boot/initrd-5.17.4-1-default| grep resume > resume > -rw-r--r-- 1 root root 50 May 3 23:21 etc/cmdline.d/95resume.conf > -rwxr-xr-x 1 root root 67656 Apr 29 11:55 usr/lib/systemd/systemd-hibernate-resume > -rwxr-xr-x 1 root root 67808 Apr 29 11:55 usr/lib/systemd/system-generators/systemd-hibernate-resume-generator > -rw-r--r-- 1 root root 680 Apr 29 11:50 usr/lib/systemd/system/systemd-hibernate-resume@.service The PBP hibernation does not work. a laptop goes into sleep normally, but cannot wake up. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1188352] New: Can't enter LUKS password since kernel 5.13 on Pinebook Pro
by bugzilla_noreply＠suse.com 28 Jan '23

28 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1188352 Bug ID: 1188352 Summary: Can't enter LUKS password since kernel 5.13 on Pinebook Pro Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: jonasdcdm(a)mailbox.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 851029 --> http://bugzilla.opensuse.org/attachment.cgi?id=851029&action=edit dmesg Since the upgrade to kernel 5.13 it's no longer possible to enter the LUKS password on boot. The physical keyboard works fine in GRUB, but the LUKS prompt won't see it, it doesn't register any key press. Entering the password via serial console works, and the Pinebook Pro boots to the desktop, where the physical keyboard works again. Kernel 5.12.13-1 is still working fine. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1201121] New: kernel: spi-nor spi0.0: BFPT parsing failed. Please consider using SPI_NOR_SKIP_SFDP when declaring the flash
by bugzilla_noreply＠suse.com 28 Jan '23

28 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1201121 Bug ID: 1201121 Summary: kernel: spi-nor spi0.0: BFPT parsing failed. Please consider using SPI_NOR_SKIP_SFDP when declaring the flash 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: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Starting with the Tumbleweed snapshot installed on June 7th I get kernel: spi-nor spi0.0: BFPT parsing failed. Please consider using SPI_NOR_SKIP_SFDP when declaring the flash in my journal on every boot. Running fwupdmgr I get fwupd[6102]: 12:26:06:0015 FuPluginDfu truncated DFU interface data, no bcdDFUVersion The daemon nevertheless is starting. Because there is no newer firmware for any of my devices I am not able to test, if an update would work despite these error messages. This is a XPS 13 9310 2-in-1/0NVVG0, BIOS 2.8.1 02/25/2022. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1185174] New: [i815] kernel 5.11: Xorg fails to run: open /dev/dri/card0: No such file or directory; (EE) GARTInit: Unable to open /dev/agpgart (No such file or directory)
by bugzilla_noreply＠suse.com 27 Jan '23

27 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1185174 Bug ID: 1185174 Summary: [i815] kernel 5.11: Xorg fails to run: open /dev/dri/card0: No such file or directory; (EE) GARTInit: Unable to open /dev/agpgart (No such file or directory) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: i686 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: mrmazda(a)earthlink.net QA Contact: gfx-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 848660 --> http://bugzilla.opensuse.org/attachment.cgi?id=848660&action=edit dmesg tail; journal tail; Xorg.0.log; drm.debug=0x06 log_buf_len=1M Original Summary: [i815] kernel 5.11: Xorg fails to run: open /dev/dri/card0: No such file or directory; (EE) GARTInit: Unable to open /dev/agpgart (No such file or directory) Xorg is running on TW20210420 on this ancient i815 Dell using xf86-video-intel DDX and kernel 5.10, but fails as indicated in summary with 5.11.15. https://www.linuxquestions.org/questions/linux-hardware-18/intel-corporatio… has a short record of TW Xorg on this same PC's IGP working 13 months ago. # inxi -CGSxxy System: Host: gx150 Kernel: 5.10.16-1-default i686 bits: 32 compiler: gcc v: 10.2.1 Desktop: KDE 3 wm: kwin dm: N/A Distro: openSUSE Tumbleweed 20210420 CPU: Info: Single Core model: Intel Pentium III bits: 32 type: MCP arch: P6 III Tualitin rev: 1 cache: L1: 32 KiB L2: 256 KiB flags: pae sse bogomips: 2259 Speed: 1130 MHz min/max: N/A Core speed (MHz): 1: 1130Graphics: Device-1: Intel 82815 Graphics vendor: Dell driver: N/A bus-ID: 00:02.0 chip-ID: 8086:1132 Display: x11 server: X.Org 1.20.10 driver: loaded: intel unloaded: fbdev,modesetting,vesa resolution: 1680x1050~60Hz s-dpi: 90 OpenGL: renderer: llvmpipe (LLVM 11.0.1 128 bits) v: 4.5 Mesa 21.0.2 compat-v: 3.1 direct render: Yes # zypper se -si intel ... i | intel-vaapi-driver | package | 2.4.1-2.4 | i586 | OSS i+ | kernel-firmware-intel | package | 20210315-1.1 | noarch | OSS i | libdrm_intel1 | package | 2.4.105-1.1 | i586 | OSS i+ | xf86-video-intel | package | 2.99.917+git8674.25c9a2fcc-5.7 | i586 | OSS # rpm -qa | grep nel-def kernel-default-5.4.14-2.1.i586 OK kernel-default-5.5.13-1.1.i586 OK kernel-default-5.7.11-1.1.i586 OK kernel-default-5.8.15-1.2.i586 OK kernel-default-5.9.14-1.2.i586 OK kernel-default-5.10.16-1.3.i586 OK kernel-default-5.11.2-1.2.i586 FAIL kernel-default-5.11.15-1.2.i586 FAIL -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1198722] New: initialize useful compiled in LSMs by default
by bugzilla_noreply＠suse.com 27 Jan '23

27 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1198722 Bug ID: 1198722 Summary: initialize useful compiled in LSMs by default 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: dmueller(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Currently CONFIG_LSM is very minimal, not even listing the LSMs that we compile into the kernel, which requires manual fixing on kernel boot cmdline using the "lsm=" parameter. we can enable these * landlock: optional ability for user land applications to sandbox themselves * yama: optional restrict of use of ptrace for nonprivileged users * bpf: create eBPF based LSMs dynamically bpf was enabled earlier already, but reverted due to bsc#1197746 -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1196632] New: Raspberry Pi 3: kernel errors in journal
by bugzilla_noreply＠suse.com 27 Jan '23

27 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1196632 Bug ID: 1196632 Summary: Raspberry Pi 3: kernel errors in journal Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 URL: https://openqa.opensuse.org/tests/2220373/modules/jour nal_check/steps/10 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: afaerber(a)suse.com, dmueller(a)suse.com, mbrugger(a)suse.com Found By: openQA Blocker: Yes Raspberry Pi 3 shows kernel errors in journal in openQA: Feb 24 00:00:59.640173 localhost kernel: of_clk_hw_onecell_get: invalid index 15 Feb 24 00:00:59.640443 localhost kernel: [drm:vc4_vec_bind [vc4]] *ERROR* Failed to get clock: -2 Feb 24 00:00:59.640588 localhost kernel: vc4-drm soc:gpu: failed to bind 3f806000.vec (ops vc4_vec_ops [vc4]): -2 Feb 24 00:01:03.628986 localhost kernel: lan78xx 1-1.1.1:1.0 eth0: kevent 4 may have been dropped Feb 24 00:01:03.630784 localhost kernel: lan78xx 1-1.1.1:1.0 eth0: kevent 4 may have been dropped See: https://openqa.opensuse.org/tests/2220373/modules/journal_check/steps/10 RPi 2 has similar traces: Feb 24 00:01:05.797966 localhost kernel: of_clk_hw_onecell_get: invalid index 15 Feb 24 00:01:05.798406 localhost kernel: [drm:vc4_vec_bind [vc4]] *ERROR* Failed to get clock: -2 Feb 24 00:01:05.798737 localhost kernel: vc4-drm soc:gpu: failed to bind 3f806000.vec (ops vc4_vec_ops [vc4]): -2 Feb 24 00:01:05.852969 localhost systemd-udevd[1029]: controlC1: /usr/lib/udev/rules.d/78-sound-card.rules:5 Failed to write ATTR{/sys/devices/platform/soc/3f902000.hdmi/sound/card1/controlC1/../uevent}, ignoring: No such file or directory See: https://openqa.opensuse.org/tests/2220373#step/journal_check/10 -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1195297] New: fbtft spi screens no longer functions properly.
by bugzilla_noreply＠suse.com 27 Jan '23

27 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1195297 Bug ID: 1195297 Summary: fbtft spi screens no longer functions properly. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: simonf.lees(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Connected to the raspberry pi on my Robot I have a small 3.2" display [1] (or a clone / older version) it connects via SPI on the raspberry pi's GPIO header. In the past i've had it working with the overlay at [2] and the fbtft driver. This kinda setup is pretty common in the embedded / hobbyist world, I don't use a desktop or anything just simple status apps using the framebuffer directly on the other hand it wouldn't be the end of the world if I moved to Qt. Today I finally got a chance to update and as of now I no longer have an /dev/fb1 (/dev/fb0 is hdmi) is that expected with my current setup? I had other issues with the update and had to grab a fresh image and re add my overlay and raspbery pi config so there is also a chance I missed something setting it up again. I've put some dmesg output from the older system the new system shows nothing and below that is an fbi command I use for testing. Log from previously working system: [ 59.468595] fbtft: module is from the staging directory, the quality is unknown, you have been warned. [ 59.714749] fb_ili9340: module is from the staging directory, the quality is unknown, you have been warned. [ 59.716023] fb_ili9340 spi0.0: fbtft_property_value: buswidth = 8 [ 59.716049] fb_ili9340 spi0.0: fbtft_property_value: debug = 0 [ 59.716063] fb_ili9340 spi0.0: fbtft_property_value: rotate = 270 [ 59.716079] fb_ili9340 spi0.0: fbtft_property_value: fps = 25 [ 59.716093] fb_ili9340 spi0.0: fbtft_property_value: txbuflen = 32768 [ 61.352903] graphics fb1: fb_ili9340 frame buffer, 320x240, 150 KiB video memory, 32 KiB buffer memory, fps=25, spi0.0 at 16 MHz Test command: sudo fbi -T 13 -d /dev/fb1 --noverbose 1-110313112A3.jpg 1. https://www.waveshare.com/wiki/3.2inch_RPi_LCD_(B) 2. https://github.com/swkim01/waveshare-dtoverlays -- You are receiving this mail because: You are on the CC list for the bug.

1 4