Update to 5.19 series, security and bugfixes... SRPMS: kernel-5.19.3-1.mga8.src.rpm kmod-virtualbox-6.1.36-2.4.mga8.src.rpm kmod-xtables-addons-3.21-2.2.mga8.src.rpm i586: bpftool-5.19.3-1.mga8.i586.rpm cpupower-5.19.3-1.mga8.i586.rpm cpupower-devel-5.19.3-1.mga8.i586.rpm dkms-xtables-addons-3.21-1.mga8.i586.rpm kernel-desktop-5.19.3-1.mga8-1-1.mga8.i586.rpm kernel-desktop586-5.19.3-1.mga8-1-1.mga8.i586.rpm kernel-desktop586-devel-5.19.3-1.mga8-1-1.mga8.i586.rpm kernel-desktop586-devel-latest-5.19.3-1.mga8.i586.rpm kernel-desktop586-latest-5.19.3-1.mga8.i586.rpm kernel-desktop-devel-5.19.3-1.mga8-1-1.mga8.i586.rpm kernel-desktop-devel-latest-5.19.3-1.mga8.i586.rpm kernel-desktop-latest-5.19.3-1.mga8.i586.rpm kernel-doc-5.19.3-1.mga8.noarch.rpm kernel-server-5.19.3-1.mga8-1-1.mga8.i586.rpm kernel-server-devel-5.19.3-1.mga8-1-1.mga8.i586.rpm kernel-server-devel-latest-5.19.3-1.mga8.i586.rpm kernel-server-latest-5.19.3-1.mga8.i586.rpm kernel-source-5.19.3-1.mga8-1-1.mga8.noarch.rpm kernel-source-latest-5.19.3-1.mga8.noarch.rpm kernel-userspace-headers-5.19.3-1.mga8.i586.rpm libbpf1-5.19.3-1.mga8.i586.rpm libbpf-devel-5.19.3-1.mga8.i586.rpm perf-5.19.3-1.mga8.i586.rpm xtables-addons-kernel-5.19.3-desktop-1.mga8-3.21-2.2.mga8.i586.rpm xtables-addons-kernel-5.19.3-desktop586-1.mga8-3.21-2.2.mga8.i586.rpm xtables-addons-kernel-5.19.3-server-1.mga8-3.21-2.2.mga8.i586.rpm xtables-addons-kernel-desktop586-latest-3.21-2.2.mga8.i586.rpm xtables-addons-kernel-desktop-latest-3.21-2.2.mga8.i586.rpm xtables-addons-kernel-server-latest-3.21-2.2.mga8.i586.rpm x86_64: bpftool-5.19.3-1.mga8.x86_64.rpm cpupower-5.19.3-1.mga8.x86_64.rpm cpupower-devel-5.19.3-1.mga8.x86_64.rpm dkms-xtables-addons-3.21-1.mga8.x86_64.rpm kernel-desktop-5.19.3-1.mga8-1-1.mga8.x86_64.rpm kernel-desktop-devel-5.19.3-1.mga8-1-1.mga8.x86_64.rpm kernel-desktop-devel-latest-5.19.3-1.mga8.x86_64.rpm kernel-desktop-latest-5.19.3-1.mga8.x86_64.rpm kernel-doc-5.19.3-1.mga8.noarch.rpm kernel-server-5.19.3-1.mga8-1-1.mga8.x86_64.rpm kernel-server-devel-5.19.3-1.mga8-1-1.mga8.x86_64.rpm kernel-server-devel-latest-5.19.3-1.mga8.x86_64.rpm kernel-server-latest-5.19.3-1.mga8.x86_64.rpm kernel-source-5.19.3-1.mga8-1-1.mga8.noarch.rpm kernel-source-latest-5.19.3-1.mga8.noarch.rpm kernel-userspace-headers-5.19.3-1.mga8.x86_64.rpm lib64bpf1-5.19.3-1.mga8.x86_64.rpm lib64bpf-devel-5.19.3-1.mga8.x86_64.rpm perf-5.19.3-1.mga8.x86_64.rpm virtualbox-kernel-5.19.3-desktop-1.mga8-6.1.36-2.4.mga8.x86_64.rpm virtualbox-kernel-5.19.3-server-1.mga8-6.1.36-2.4.mga8.x86_64.rpm virtualbox-kernel-desktop-latest-6.1.36-2.4.mga8.x86_64.rpm virtualbox-kernel-server-latest-6.1.36-2.4.mga8.x86_64.rpm xtables-addons-kernel-5.19.3-desktop-1.mga8-3.21-2.2.mga8.x86_64.rpm xtables-addons-kernel-5.19.3-server-1.mga8-3.21-2.2.mga8.x86_64.rpm xtables-addons-kernel-desktop-latest-3.21-2.2.mga8.x86_64.rpm xtables-addons-kernel-server-latest-3.21-2.2.mga8.x86_64.rpm
Checking: lib64bpf1 ? use to be lib64bpf0
Keywords: (none) => feedbackCC: (none) => fri
Feeling adventurous, I in drakrpm manually selected lib64bpf1 for install, like all other relevant updates for this kernel on this system. $ rpm -qa |grep lib64bpf lib64bpf0-5.15.62-1.mga8 lib64bpf1-5.19.3-1.mga8 And drakrpm list lib64bpf0 with the icon of non-uninstallable system packages, but lib64bpf1 like a normal uninstallable package. Hardware: My workstation "svarten": Mainboard: Sabertooth P67, CPU: i7-3770, RAM 16G, GM107 [GeForce GTX 750] using nvidia-current; GeForce 635 series and later, 4k display. Disk&Filesystem: SSD with /boot/EFI and ext4 /boot, LUKS{LVM {swap, ext4 /home & / } and a spinner at /mnt/spinner $ rpm -qa | grep 5.19.3 | sort cpupower-5.19.3-1.mga8 kernel-desktop-5.19.3-1.mga8-1-1.mga8 kernel-desktop-devel-5.19.3-1.mga8-1-1.mga8 kernel-desktop-devel-latest-5.19.3-1.mga8 kernel-desktop-latest-5.19.3-1.mga8 kernel-userspace-headers-5.19.3-1.mga8 lib64bpf1-5.19.3-1.mga8 virtualbox-kernel-5.19.3-desktop-1.mga8-6.1.36-2.4.mga8 $ uname -a Linux svarten.tribun 5.19.3-desktop-1.mga8 #1 SMP PREEMPT_DYNAMIC Sun Aug 21 19:58:34 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ dkms status | grep 5.19.3 | sort nvidia-current, 515.65.01-1.mga8.nonfree, 5.19.3-desktop-1.mga8, x86_64: installed virtualbox, 6.1.36-1.mga8, 5.19.3-desktop-1.mga8, x86_64: installed virtualbox, 6.1.36-1.mga8, 5.19.3-desktop-1.mga8, x86_64: installed-binary from 5.19.3-desktop-1.mga8 BOINC detects CUDA and OpenCL. But no such work unit to try. Tested: Plasma desktop; using Thunderbird, LibreOffice, Ktorrent, Nextcloud client, Syncthing, Firefox ESR (video ok) java program FriBOK, Flatpak program KiCad... Tests OK as VirtualBox Host: Guest 1: my usual MSW7pro-64, tests OK: dynamic guest window resizing, bidirectional clipboard, host shared folders write protected and not, USB2 memory stick read&write (using upstream extension pack), video playing OK in Firefox when restricting BOINC to only use 70%CPU, all cores. Guest 2: OK: 2x BOINC LHC@home ATLAS simulation virtual machine 3CPU.
(In reply to Morgan Leijström from comment #1) > Checking: lib64bpf1 ? use to be lib64bpf0 Yes, lib(64)bpf major has been bumped upstream from 0 to 1 with the 5.19 series kernels. this is not a problem ...
Keywords: feedback => (none)
(In reply to Morgan Leijström from comment #2) > Feeling adventurous, I in drakrpm manually selected lib64bpf1 for install, > like all other relevant updates for this kernel on this system. > $ rpm -qa |grep lib64bpf > lib64bpf0-5.15.62-1.mga8 > lib64bpf1-5.19.3-1.mga8 > And drakrpm list lib64bpf0 with the icon of non-uninstallable system > packages, but lib64bpf1 like a normal uninstallable package. I also had to select lib64bpf1 manually; it has not been offered as an update of lib64bpf0. For lambda users who will simply update to kernel 5.19.3 once it has been validated by QA, isn't there a risk that most of them will miss lib64bpf1? Could this cause problems for machines which have kernel 5.19.3 + lib64bpf0 only?
(In reply to Frédéric "LpSolit" Buclin from comment #4) > I also had to select lib64bpf1 manually; it has not been offered as an > update of lib64bpf0. For lambda users who will simply update to kernel > 5.19.3 once it has been validated by QA, isn't there a risk that most of > them will miss lib64bpf1? Could this cause problems for machines which have > kernel 5.19.3 + lib64bpf0 only? nope, there is nothing built against lib(64)bpf1 in Mga8, which is why nothing pulls it in. and the whole purpose of our libification with libmajor in the name is so there is no package conflict, and a package with a new libmajor should never obsolete an old lib package as that would force a rebuild of a lot of packages in a stable release... of course if something that depends on lib(64)bpf would be pushed to backports, that would pick up the new dep...
MGA8-64, on Xfce, Toshiba Laptop AMD A6-3420M APU Radeon HD 6520G RTL8188CE 802.11b/g/n WiFi Adapter The following 5 packages are going to be installed: usual 4 with lib64bpf1 --- rebooted $ uname -a Linux localhost 5.19.3-desktop-1.mga8 #1 SMP PREEMPT_DYNAMIC Sun Aug 21 19:58:34 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux - wifi works - sound works - firefox works - libreoffice looks ok - nextcloud client working System is working as expected.
CC: (none) => brtians1
Whiteboard: (none) => MGA8-64-OKKeywords: (none) => validated_backport
Moved.
Status: NEW => RESOLVEDResolution: (none) => FIXED
This kernel seems to be OK on Foolishness, my 32-bit Dell Inspiron 5100. (P4, Radeon RV200 graphics, Xfce) Adding a 32-bit OK, just because...
Whiteboard: MGA8-64-OK => MGA8-32-OK MGA8-64-OKCC: (none) => andrewsfarm