March 2024 - openSUSE Kernel - openSUSE Mailing Lists

Disabling /dev/fb0 on TW
by Thomas Zimmermann 22 Oct '24

22 Oct '24

tl;dr: Disable fbdev userspace interfaces on TW Hi, the upcoming Linux kernel v6.6 will contain the option to disable fbdev userspace interfaces in the kernel configuration. [1] I intent to enable this and thereby switch off /dev/fb0 et al. The tracker bug is boo#1212947. [2] * Why? The old fbdev subsystem is an endless source of bugs. For example, we recently had an out-of-bounds access in the fbdev emulation, where userspace could write beyond the end of the framebuffer memory. [3] Fbdev is under-maintained. I've been doing improvements in recent kernel releases, but only where it benefits the DRM subsystem. Disabling fbdev userspace interfaces will also help weeding out any programs that still contain hard dependencies on them. * What changes? Enabling the new kernel option disables all fbdev userspace interfaces. These are * the device files, such as /dev/fb0 * the sys files under /sys/class/graphics/fb[0-9]+ * /proc/fb * What are the effects on userspace programs? Userspace applications run on the desktop via Wayland or X. There will be no change to them. Xorg and Wayland compositors run on DRM interfaces. A few programs run on SDL, which has no dependency on fbdev either. Any fbdev support in these mid-layer components should be disabled as well. There's one known affected program: TW's text-mode installer can use the tool fbiterm to display CJK symbols during installation. This comes from a time when some low-end systems where not able to boot graphics installation. fbiterm has been unmaintained for >15 years and is ready for retirement. But there's no good drop-in replacement. I propose to simply remove fbiterm and let the graphics installer handle CJK. * What about the framebuffer console? The kernel-provided framebuffer console does not change. The kernel will still show the regular console. Userspace interfaces in /sys/class/graphics/fbcon are still available. For questions and discussion, please comment here or in boo#1212947. Best regards Thomas [1] https://elixir.bootlin.com/linux/v6.6-rc1/source/drivers/video/fbdev/core/K… [2] https://bugzilla.opensuse.org/show_bug.cgi?id=1212947 [3] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?… -- Thomas Zimmermann Graphics Driver Developer SUSE Software Solutions Germany GmbH Frankenstrasse 146, 90461 Nuernberg, Germany GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman HRB 36809 (AG Nuernberg)

1 1

[opensuse-kernel] kernel-default-base-2.6.29-5.2.x86_64 rpm errors
by Dave Plater 18 Jul '24

18 Jul '24

Hi, I'm busy updating to the latest factory kernel and have received the following errors from kernel-default-base installation (I did insert a blank dvd during the installation of the rpm by zypper):- WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sd_mod.ko needs unknown symbol crc_t10dif WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sr_mod.ko needs unknown symbol register_cdrom WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sr_mod.ko needs unknown symbol cdrom_ioctl WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sr_mod.ko needs unknown symbol cdrom_media_changed WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sr_mod.ko needs unknown symbol cdrom_get_media_event WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sr_mod.ko needs unknown symbol cdrom_release WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sr_mod.ko needs unknown symbol cdrom_open WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sr_mod.ko needs unknown symbol unregister_cdrom WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sr_mod.ko needs unknown symbol cdrom_number_of_slots And then these errors which I think IIRC happened before when the kernel was first split into three:- Kernel image: /boot/vmlinuz-2.6.29-rc8-5-default Initrd image: /boot/initrd-2.6.29-rc8-5-default Root device: /dev/disk/by-id/ata-WDC_WD800JB-00JJC0_WD-WMAM9RA78067-part3 (/dev/sda3) (mounted on / as xfs) Resume device: /dev/disk/by-id/ata-WDC_WD800JB-00JJC0_WD-WMAM9RA78067-part2 (/dev/sda2) FATAL: Module processor not found. WARNING: no dependencies for kernel module 'processor' found. FATAL: Module thermal not found. WARNING: no dependencies for kernel module 'thermal' found. FATAL: Module ata_generic not found. WARNING: no dependencies for kernel module 'ata_generic' found. FATAL: Module piix not found. WARNING: no dependencies for kernel module 'piix' found. FATAL: Module ide_pci_generic not found. WARNING: no dependencies for kernel module 'ide_pci_generic' found. FATAL: Module fan not found. WARNING: no dependencies for kernel module 'fan' found. FATAL: Module xfs not found. WARNING: no dependencies for kernel module 'xfs' found. FATAL: Module usbhid not found. WARNING: no dependencies for kernel module 'usbhid' found. Kernel Modules: scsi_mod libata ata_piix edd ahci sd_mod usbcore ohci-hcd ehci-hcd uhci-hcd WARNING: /dev/shm/mkinitramfs.0drQsZ/mnt/lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sd_mod.ko needs unknown symbol crc_t10dif Features: block usb resume.userspace resume.kernel Bootsplash: openSUSE (1280x1024) 22669 blocks Should I open a bug report about the errors which are possibly from inserting a dvd while the kernel rpm was installing? Regards Dave P -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

2 2

[Slowroll] Building and signing KMPs
by Manfred Hollstein 03 Apr '24

03 Apr '24

Hi there, I build the old broadcom-wl kmp for a variety of OS/kernel combinations. With Slowroll however it fails when the built rpms will be signed using a generated pesign.spec. This is from https://build.opensuse.org/public/build/home:manfred-h:KMPs/openSUSE_Slowro…: [ 33s] /etc/profile.d/suse-buildsystem.sh: line 53: test: : integer expression expected [ 33s] + exec rpmbuild -ba --define '_srcdefattr (-,root,root)' --nosignature --undefine _enable_debug_packages --define 'disturl obs://build.opensuse.org/home:manfred-h:KMPs/openSUSE_Slowroll/9aa3d5cf0236…' /home/abuild/rpmbuild/SOURCES/pesign-repackage.spec [ 33s] error: source_date_epoch_from_changelog set but %changelog is missing [ 33s] [ 33s] RPM build errors: [ 33s] source_date_epoch_from_changelog set but %changelog is missing [ 33s] ### VM INTERACTION START ### [ 34s] [ 28.473717][ T1] sysrq: Power Off [ 34s] [ 28.474748][ T8] reboot: Power down [ 34s] ### VM INTERACTION END ### [ 34s] [ 34s] i02-ch1d failed "build pesign-repackage.spec" at Wed Mar 27 08:11:09 UTC 2024. Perhaps Bernhard is reading this, is there anything special building a kmp for Slowroll? TIA, cheers. l8er manfred

5 9

Wrong dates in shared folder mounted in VirtualBox
by Larry Finger 07 Mar '24

07 Mar '24

Hi, As noted in boo#1220524 - Files in virtualbox shared folder (on the guest) show wrong timestamp, the dates are not passed from host to guest if the guest is TW. This problem began sometime in kernel 6.7.X. To try to debug this issue, I have generated a v6.7.7-1-default kernel locally. The standard openSUSE configuration was used with one change. As I do not have access to the .pem file specified in the standard configuration, I changed to the kernel source signing key with 'CONFIG_MODULE_SIG_KEY="certs/signing_key.pem"'. All other configuration variables are unchanged. The kernel generated in this manner works correctly; however, what should be the equivalent installed with zypper from the TW repos fails!!! The local kernel was generated with gcc-13.2.1 20240206. I will be happy to provide further information that will help fix this bug. Larry

2 1

Building the distribution kernel
by Larry Finger 05 Mar '24

05 Mar '24

Hi, I am trying to debug the problem shown in boo#1220524 - Files in virtualbox shared folder (on the guest) show wrong timestamp. Using the standard 6.6.5 default kernel in a TW guest (Xfce desktop) shows the problem. When I generate a 6.6.5 kernel starting with the mainline 6.5.0 and applying the patches in the kernel-source repo in the patches.kernel.org and patches.suse directories, the generated kernel works correctly! What am I missing? I am installing the kernel using 'make modules_install install', not from an rpm, but I do not expect that to cause a problem. Are there patches applied to the standard kernel that I am missing? Does installing from an rpm install other packages? Thanks, Larry

2 1