June 2024 - openSUSE Kernel - openSUSE Mailing Lists

tumbleweed upstream kernel
by S Kosner 15 Oct '24

15 Oct '24

Hi, It seems tumbleweed does not (normally) use a pure upstream kernel, as kernel-default includes patches. Although, is kernel-vanilla pure upstream like it sounds (albeit maybe compiled with custom options)? Thanks

4 8

[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

How to maintain kernel-source packages on OBS?
by Shung-Hsi Yu 27 Jun '24

27 Jun '24

Hi, I'm looking into maintaining a kernel based on out-of-tree patchset[1] on the openSUSE's build service (OBS) with Fredrik. While I work with kernel-source regularly, I have no idea on the process or publish/release the kernel. From the openSUSE:Kernel git[2] documentation and my understanding it goes down to: git clone https://github.com/openSUSE/kernel-source/ cd kernel-source git checkout $BRANCH # stable or master # Do some work here ... # Create source package scripts/tar-up.sh # Upload to OBS, need --enable-debug here otherwise BTF won't be # available scripts/osc_wrapper upload --enable-debug $PROJECT Once built, user should be able add the OBS repo, and install the kernel package I suppose? Or is there any additional that has to be done on the OBS project? Also there's two kernel branch I'd be working with: scx-kernel-releases[3] which is based on the latest stable, and sched_ext[4] which is based on bpf-next[5]. And it would be great to have suggestion on how to maintain them in practice within kernel-source. Since scx-kernel-releases is based on stable, it seems rather straight forward to maintain. I'd fork from the kernel-source's stable branch, add another directory (patches.sched-ext perhaps), add the patches there, modify series.conf to include the sched-ext patches so they are applied, and update the kernel configuration in config/ accordingly. After that it should be mostly just merging from kernel-source's stable as it changes, I hope. On the other hand sched_ext being based on the development branch bpf-next seems a bit more daunting. I could base off of kernel-source's master, but then I had to take all the patches in bpf-next[5] (which includes netdev/net-next[6]) in addition to sched-ext ones, and bpf-next could change rather often. Is there a better way to do this? Could I simply grab a tarball from the sched_ext GitHub repository[4] and use it instead? Or maybe it's just not worth the effort? Feedbacks, suggestions, and pros & cons are all welcome. Thanks, Shung-Hsi Yu 1: https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/message… 2: https://en.opensuse.org/openSUSE:Kernel_git#Using_the_kernel-source_reposit… 3: https://github.com/sched-ext/scx-kernel-releases 4: https://github.com/sched-ext/sched_ext 5: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git/log/?h=for… 6: https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net-next/

7 10