From toracat at elrepo.org Wed Jun 4 11:54:18 2025 From: toracat at elrepo.org (Akemi Yagi) Date: Wed, 4 Jun 2025 08:54:18 -0700 Subject: [elrepo] Announcement: EL10 Updated kernel-ml Package Set [6.14.9-1] Message-ID: Announcing the release of the kernel-ml-6.14.9-1.el10.elrepo package set into the EL10 elrepo-kernel repository: https://elrepo.org/wiki/doku.php?id=kernel-ml The upstream changelog: https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.14.9 The following files are currently synchronising to our mirror sites: x86_64 kernel-ml-6.14.9-1.el10.elrepo.x86_64.rpm kernel-ml-core-6.14.9-1.el10.elrepo.x86_64.rpm kernel-ml-cross-headers-6.14.9-1.el10.elrepo.x86_64.rpm kernel-ml-devel-6.14.9-1.el10.elrepo.x86_64.rpm kernel-ml-devel-matched-6.14.9-1.el10.elrepo.x86_64.rpm kernel-ml-headers-6.14.9-1.el10.elrepo.x86_64.rpm kernel-ml-modules-6.14.9-1.el10.elrepo.x86_64.rpm kernel-ml-modules-extra-6.14.9-1.el10.elrepo.x86_64.rpm kernel-ml-tools-6.14.9-1.el10.elrepo.x86_64.rpm kernel-ml-tools-libs-6.14.9-1.el10.elrepo.x86_64.rpm kernel-ml-tools-libs-devel-6.14.9-1.el10.elrepo.x86_64.rpm libperf-6.14.9-1.el10.elrepo.x86_64.rpm libperf-devel-6.14.9-1.el10.elrepo.x86_64.rpm perf-6.14.9-1.el10.elrepo.x86_64.rpm python3-perf-6.14.9-1.el10.elrepo.x86_64.rpm rtla-6.14.9-1.el10.elrepo.x86_64.rpm rv-6.14.9-1.el10.elrepo.x86_64.rpm nosrc kernel-ml-6.14.9-1.el10.elrepo.nosrc.rpm We provide these kernels for hardware testing in an effort to identify new/updated drivers which can then be targeted for backporting as kmod packages. Meanwhile, these kernels may provide interim relief to people with non-functional hardware. We stress that we consider such kernels as a last resort for those who are unable to get their hardware working using the RHEL-9 kernel with supplementary kmod packages. These packages are provided "As-Is" with no implied warranty or support. Using the kernel-ml may expose your system to security, performance and/or data corruption issues. Since timely updates may not be available from the ELRepo Project, the end user has the ultimate responsibility for deciding whether to continue using the kernel-ml packages in regular service. The packages are intentionally named kernel-ml so as not to conflict with the RHEL-9 kernels and, as such, they may be installed and updated alongside the regular kernel. The kernel configuration is based upon a default RHEL-9 configuration with added functionality enabled as appropriate. If a bug is found when using these kernels, the end user is encouraged to report it upstream to the Linux Kernel Bug Tracker [1] and, for our reference, to the ELRepo bug tracker [2]. By taking such action, the reporter will be assisting the kernel developers, Red Hat and the Open Source Community as a whole. Thank you, The ELRepo Team. [1] https://bugzilla.kernel.org/ [2] https://elrepo.org/bugs/ From toracat at elrepo.org Thu Jun 5 18:20:40 2025 From: toracat at elrepo.org (Akemi Yagi) Date: Thu, 5 Jun 2025 15:20:40 -0700 Subject: [elrepo] Announcement: EL9 Updated kernel-ml Package Set [6.15.1-1] Message-ID: Announcing the release of the kernel-ml-6.15.1-1.el9.elrepo package set into the EL9 elrepo-kernel repository: https://elrepo.org/wiki/doku.php?id=kernel-ml The upstream changelog: https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.15.1 The following files are currently synchronising to our mirror sites: aarch64 [1] bpftool-6.15.1-1.el9.elrepo.aarch64.rpm kernel-ml-6.15.1-1.el9.elrepo.aarch64.rpm kernel-ml-core-6.15.1-1.el9.elrepo.aarch64.rpm kernel-ml-devel-6.15.1-1.el9.elrepo.aarch64.rpm kernel-ml-devel-matched-6.15.1-1.el9.elrepo.aarch64.rpm kernel-ml-doc-6.15.1-1.el9.elrepo.noarch.rpm kernel-ml-headers-6.15.1-1.el9.elrepo.aarch64.rpm kernel-ml-modules-6.15.1-1.el9.elrepo.aarch64.rpm kernel-ml-modules-extra-6.15.1-1.el9.elrepo.aarch64.rpm kernel-ml-tools-6.15.1-1.el9.elrepo.aarch64.rpm kernel-ml-tools-libs-6.15.1-1.el9.elrepo.aarch64.rpm kernel-ml-tools-libs-devel-6.15.1-1.el9.elrepo.aarch64.rpm perf-6.15.1-1.el9.elrepo.aarch64.rpm python3-perf-6.15.1-1.el9.elrepo.aarch64.rpm x86_64 bpftool-6.15.1-1.el9.elrepo.x86_64.rpm kernel-ml-6.15.1-1.el9.elrepo.x86_64.rpm kernel-ml-core-6.15.1-1.el9.elrepo.x86_64.rpm kernel-ml-devel-6.15.1-1.el9.elrepo.x86_64.rpm kernel-ml-devel-matched-6.15.1-1.el9.elrepo.x86_64.rpm kernel-ml-doc-6.15.1-1.el9.elrepo.noarch.rpm kernel-ml-headers-6.15.1-1.el9.elrepo.x86_64.rpm kernel-ml-modules-6.15.1-1.el9.elrepo.x86_64.rpm kernel-ml-modules-extra-6.15.1-1.el9.elrepo.x86_64.rpm kernel-ml-tools-6.15.1-1.el9.elrepo.x86_64.rpm kernel-ml-tools-libs-6.15.1-1.el9.elrepo.x86_64.rpm kernel-ml-tools-libs-devel-6.15.1-1.el9.elrepo.x86_64.rpm perf-6.15.1-1.el9.elrepo.x86_64.rpm python3-perf-6.15.1-1.el9.elrepo.x86_64.rpm nosrc kernel-ml-6.15.1-1.el9.elrepo.nosrc.rpm We provide these kernels for hardware testing in an effort to identify new/updated drivers which can then be targeted for backporting as kmod packages. Meanwhile, these kernels may provide interim relief to people with non-functional hardware. We stress that we consider such kernels as a last resort for those who are unable to get their hardware working using the RHEL-9 kernel with supplementary kmod packages. These packages are provided "As-Is" with no implied warranty or support. Using the kernel-ml may expose your system to security, performance and/or data corruption issues. Since timely updates may not be available from the ELRepo Project, the end user has the ultimate responsibility for deciding whether to continue using the kernel-ml packages in regular service. The packages are intentionally named kernel-ml so as not to conflict with the RHEL-9 kernels and, as such, they may be installed and updated alongside the regular kernel. The kernel configuration is based upon a default RHEL-9 configuration with added functionality enabled as appropriate. If a bug is found when using these kernels, the end user is encouraged to report it upstream to the Linux Kernel Bug Tracker [2] and, for our reference, to the ELRepo bug tracker [3]. By taking such action, the reporter will be assisting the kernel developers, Red Hat and the Open Source Community as a whole. Thank you, The ELRepo Team. [1] The ELRepo Project would like to thank the OSU Open Source Lab for their support with the aarch64 platform. [2] https://bugzilla.kernel.org/ [3] https://elrepo.org/bugs/ From toracat at elrepo.org Thu Jun 5 18:22:21 2025 From: toracat at elrepo.org (Akemi Yagi) Date: Thu, 5 Jun 2025 15:22:21 -0700 Subject: [elrepo] Announcement: EL8 Updated kernel-ml Package Set [6.15.1-1] Message-ID: Announcing the release of the kernel-ml-6.15.1-1.el8.elrepo package set into the EL8 elrepo-kernel repository: https://elrepo.org/wiki/doku.php?id=kernel-ml The upstream changelog: https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.15.1 The following files are currently synchronising to our mirror sites: x86_64 kernel-ml-6.15.1-1.el8.elrepo.x86_64.rpm kernel-ml-core-6.15.1-1.el8.elrepo.x86_64.rpm kernel-ml-devel-6.15.1-1.el8.elrepo.x86_64.rpm kernel-ml-doc-6.15.1-1.el8.elrepo.noarch.rpm kernel-ml-headers-6.15.1-1.el8.elrepo.x86_64.rpm kernel-ml-modules-6.15.1-1.el8.elrepo.x86_64.rpm kernel-ml-modules-extra-6.15.1-1.el8.elrepo.x86_64.rpm kernel-ml-tools-6.15.1-1.el8.elrepo.x86_64.rpm kernel-ml-tools-libs-6.15.1-1.el8.elrepo.x86_64.rpm kernel-ml-tools-libs-devel-6.15.1-1.el8.elrepo.x86_64.rpm perf-6.15.1-1.el8.elrepo.x86_64.rpm python3-perf-6.15.1-1.el8.elrepo.x86_64.rpm nosrc kernel-ml-6.15.1-1.el8.elrepo.nosrc.rpm Please note that as of kernel-ml version 6.5.4 we are unable to continue providing the bpftool package. We provide these kernels for hardware testing in an effort to identify new/updated drivers which can then be targeted for backporting as kmod packages. Meanwhile, these kernels may provide interim relief to people with non-functional hardware. We stress that we consider such kernels as a last resort for those who are unable to get their hardware working using the RHEL-8 kernel with supplementary kmod packages. These packages are provided "As-Is" with no implied warranty or support. Using the kernel-ml may expose your system to security, performance and/or data corruption issues. Since timely updates may not be available from the ELRepo Project, the end user has the ultimate responsibility for deciding whether to continue using the kernel-ml packages in regular service. The packages are intentionally named kernel-ml so as not to conflict with the RHEL-8 kernels and, as such, they may be installed and updated alongside the regular kernel. The kernel configuration is based upon a default RHEL-8 configuration with added functionality enabled as appropriate. If a bug is found when using these kernels, the end user is encouraged to report it upstream to the Linux Kernel Bug Tracker [1] and, for our reference, to the ELRepo bug tracker [2]. By taking such action, the reporter will be assisting the kernel developers, Red Hat and the Open Source Community as a whole. Thank you, The ELRepo Team. [1] https://bugzilla.kernel.org/ [2] https://elrepo.org/bugs/ From toracat at elrepo.org Fri Jun 6 12:03:49 2025 From: toracat at elrepo.org (Akemi Yagi) Date: Fri, 6 Jun 2025 09:03:49 -0700 Subject: [elrepo] Announcement: EL10 Updated kernel-ml Package Set [6.15.1-1] Message-ID: Announcing the release of the kernel-ml-6.15.1-1.el10.elrepo package set into the EL10 elrepo-kernel repository: https://elrepo.org/wiki/doku.php?id=kernel-ml The upstream changelog: https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.15.1 The following files are currently synchronising to our mirror sites: x86_64 kernel-ml-6.15.1-1.el10.elrepo.x86_64.rpm kernel-ml-core-6.15.1-1.el10.elrepo.x86_64.rpm kernel-ml-cross-headers-6.15.1-1.el10.elrepo.x86_64.rpm kernel-ml-devel-6.15.1-1.el10.elrepo.x86_64.rpm kernel-ml-devel-matched-6.15.1-1.el10.elrepo.x86_64.rpm kernel-ml-headers-6.15.1-1.el10.elrepo.x86_64.rpm kernel-ml-modules-6.15.1-1.el10.elrepo.x86_64.rpm kernel-ml-modules-extra-6.15.1-1.el10.elrepo.x86_64.rpm kernel-ml-tools-6.15.1-1.el10.elrepo.x86_64.rpm kernel-ml-tools-libs-6.15.1-1.el10.elrepo.x86_64.rpm kernel-ml-tools-libs-devel-6.15.1-1.el10.elrepo.x86_64.rpm libperf-6.15.1-1.el10.elrepo.x86_64.rpm libperf-devel-6.15.1-1.el10.elrepo.x86_64.rpm perf-6.15.1-1.el10.elrepo.x86_64.rpm python3-perf-6.15.1-1.el10.elrepo.x86_64.rpm rtla-6.15.1-1.el10.elrepo.x86_64.rpm rv-6.15.1-1.el10.elrepo.x86_64.rpm nosrc kernel-ml-6.15.1-1.el10.elrepo.nosrc.rpm We provide these kernels for hardware testing in an effort to identify new/updated drivers which can then be targeted for backporting as kmod packages. Meanwhile, these kernels may provide interim relief to people with non-functional hardware. We stress that we consider such kernels as a last resort for those who are unable to get their hardware working using the RHEL-9 kernel with supplementary kmod packages. These packages are provided "As-Is" with no implied warranty or support. Using the kernel-ml may expose your system to security, performance and/or data corruption issues. Since timely updates may not be available from the ELRepo Project, the end user has the ultimate responsibility for deciding whether to continue using the kernel-ml packages in regular service. The packages are intentionally named kernel-ml so as not to conflict with the RHEL-9 kernels and, as such, they may be installed and updated alongside the regular kernel. The kernel configuration is based upon a default RHEL-9 configuration with added functionality enabled as appropriate. If a bug is found when using these kernels, the end user is encouraged to report it upstream to the Linux Kernel Bug Tracker [1] and, for our reference, to the ELRepo bug tracker [2]. By taking such action, the reporter will be assisting the kernel developers, Red Hat and the Open Source Community as a whole. Thank you, The ELRepo Team. [1] https://bugzilla.kernel.org/ [2] https://elrepo.org/bugs/ From jcsible at cert.org Mon Jun 9 11:14:57 2025 From: jcsible at cert.org (Joseph Christopher Sible) Date: Mon, 9 Jun 2025 15:14:57 +0000 Subject: [elrepo] Remove old GPG key from EL10 elrepo-release package Message-ID: Hello, Since the old GPG key doesn't work on RHEL 10, can it be removed from the /etc/yum.repos.d/elrepo.repo file that elrepo-release-10.el10 installs there? Its presence in that file causes GPG errors preventing automatic import of the new key. Thanks, Joseph C. Sible From toracat at elrepo.org Mon Jun 9 12:10:34 2025 From: toracat at elrepo.org (Akemi Yagi) Date: Mon, 9 Jun 2025 09:10:34 -0700 Subject: [elrepo] Remove old GPG key from EL10 elrepo-release package In-Reply-To: References: Message-ID: On Mon, Jun 9, 2025 at 8:15?AM Joseph Christopher Sible wrote: > > Hello, > > Since the old GPG key doesn't work on RHEL 10, can it be removed from the /etc/yum.repos.d/elrepo.repo file that elrepo-release-10.el10 installs there? Its presence in that file causes GPG errors preventing automatic import of the new key. > > Thanks, > > Joseph C. Sible The elrepo-release-10.0-1.el10.elrepo.noarch package does not contain the old GPG key: $ rpm -ql elrepo-release /etc/pki/elrepo /etc/pki/elrepo/SECURE-BOOT-KEY-elrepo.org.der /etc/pki/rpm-gpg/RPM-GPG-KEY-v2-elrepo.org /etc/yum.repos.d/elrepo.repo Could you check to see if your elrepo.repo file is from the el10 rpm? Akemi From jcsible at cert.org Mon Jun 9 12:24:42 2025 From: jcsible at cert.org (Joseph Christopher Sible) Date: Mon, 9 Jun 2025 16:24:42 +0000 Subject: [elrepo] Remove old GPG key from EL10 elrepo-release package In-Reply-To: References: Message-ID: That doesn't match what I'm seeing. After doing "yum install https://www.elrepo.org/elrepo-release-10.el10.elrepo.noarch.rpm" (per the https://elrepo.org/wiki/doku.php?id=start instructions) in a fresh almalinux:10 Docker container, I see the following: [root at e487a2e63bed /]# rpm -ql elrepo-release /etc/pki/elrepo /etc/pki/elrepo/SECURE-BOOT-KEY-elrepo.org.der /etc/pki/rpm-gpg/RPM-GPG-KEY-elrepo.org /etc/pki/rpm-gpg/RPM-GPG-KEY-v2-elrepo.org /etc/yum.repos.d/elrepo.repo [root at e487a2e63bed /]# rpm -qa elrepo-release elrepo-release-10.0-1.el10.elrepo.noarch [root at e487a2e63bed /]# Regards, Joseph C. Sible ________________________________________ From:?elrepo-bounces at lists.elrepo.org on behalf of Akemi Yagi Sent:?Monday, June 9, 2025 12:10 To:?EL Repo General Mailing List Subject:?Re: [elrepo] Remove old GPG key from EL10 elrepo-release package ? Warning: External Sender - do not click links or open attachments unless you recognize the sender and know the content is safe. On Mon, Jun 9, 2025 at 8:15?AM Joseph Christopher Sible wrote: > > Hello, > > Since the old GPG key doesn't work on RHEL 10, can it be removed from the /etc/yum.repos.d/elrepo.repo file that elrepo-release-10.el10 installs there? Its presence in that file causes GPG errors preventing automatic import of the new key. > > Thanks, > > Joseph C. Sible The elrepo-release-10.0-1.el10.elrepo.noarch package does not contain the old GPG key: $ rpm -ql elrepo-release /etc/pki/elrepo /etc/pki/elrepo/SECURE-BOOT-KEY-elrepo.org.der /etc/pki/rpm-gpg/RPM-GPG-KEY-v2-elrepo.org /etc/yum.repos.d/elrepo.repo Could you check to see if your elrepo.repo file is from the el10 rpm? Akemi _______________________________________________ elrepo mailing list elrepo at lists.elrepo.org http://lists.elrepo.org/mailman/listinfo/elrepo From jcsible at cert.org Mon Jun 9 12:33:59 2025 From: jcsible at cert.org (Joseph Christopher Sible) Date: Mon, 9 Jun 2025 16:33:59 +0000 Subject: [elrepo] Remove old GPG key from EL10 elrepo-release package In-Reply-To: References: Message-ID: After looking around a bit more, I found something: there are two different RPMs that both claim to be elrepo-release-10.0-1.el10.elrepo.noarch, even?though they have different contents. https://elrepo.org/linux/elrepo/el10/x86_64/RPMS/elrepo-release-10.0-1.el10.elrepo.noarch.rpm is a working one that matches what you saw, and https://www.elrepo.org/elrepo-release-10.0-1.el10.elrepo.noarch.rpm is a broken one that matches what I saw. Joseph C. Sible ________________________________________ From:?elrepo-bounces at lists.elrepo.org on behalf of Joseph Christopher Sible Sent:?Monday, June 9, 2025 12:24 To:?EL Repo General Mailing List Subject:?Re: [elrepo] Remove old GPG key from EL10 elrepo-release package ? Warning: External Sender - do not click links or open attachments unless you recognize the sender and know the content is safe. That doesn't match what I'm seeing. After doing "yum install https://www.elrepo.org/elrepo-release-10.el10.elrepo.noarch.rpm"?(per the https://elrepo.org/wiki/doku.php?id=start?instructions) in a fresh almalinux:10 Docker container, I see the following: [root at e487a2e63bed /]# rpm -ql elrepo-release /etc/pki/elrepo /etc/pki/elrepo/SECURE-BOOT-KEY-elrepo.org.der /etc/pki/rpm-gpg/RPM-GPG-KEY-elrepo.org /etc/pki/rpm-gpg/RPM-GPG-KEY-v2-elrepo.org /etc/yum.repos.d/elrepo.repo [root at e487a2e63bed /]# rpm -qa elrepo-release elrepo-release-10.0-1.el10.elrepo.noarch [root at e487a2e63bed /]# Regards, Joseph C. Sible ________________________________________ From: elrepo-bounces at lists.elrepo.org on behalf of Akemi Yagi Sent: Monday, June 9, 2025 12:10 To: EL Repo General Mailing List Subject: Re: [elrepo] Remove old GPG key from EL10 elrepo-release package Warning: External Sender - do not click links or open attachments unless you recognize the sender and know the content is safe. On Mon, Jun 9, 2025 at 8:15?AM Joseph Christopher Sible wrote: > > Hello, > > Since the old GPG key doesn't work on RHEL 10, can it be removed from the /etc/yum.repos.d/elrepo.repo file that elrepo-release-10.el10 installs there? Its presence in that file causes GPG errors preventing automatic import of the new key. > > Thanks, > > Joseph C. Sible The elrepo-release-10.0-1.el10.elrepo.noarch package does not contain the old GPG key: $ rpm -ql elrepo-release /etc/pki/elrepo /etc/pki/elrepo/SECURE-BOOT-KEY-elrepo.org.der /etc/pki/rpm-gpg/RPM-GPG-KEY-v2-elrepo.org /etc/yum.repos.d/elrepo.repo Could you check to see if your elrepo.repo file is from the el10 rpm? Akemi _______________________________________________ elrepo mailing list elrepo at lists.elrepo.org http://lists.elrepo.org/mailman/listinfo/elrepo _______________________________________________ elrepo mailing list elrepo at lists.elrepo.org http://lists.elrepo.org/mailman/listinfo/elrepo From toracat at elrepo.org Mon Jun 9 12:39:34 2025 From: toracat at elrepo.org (Akemi Yagi) Date: Mon, 9 Jun 2025 09:39:34 -0700 Subject: [elrepo] Remove old GPG key from EL10 elrepo-release package In-Reply-To: References: Message-ID: Thank you for letting us know of the source of the incorrect elrepo-release package. We will correct it shortly. Akemi On Mon, Jun 9, 2025 at 9:34?AM Joseph Christopher Sible wrote: > > After looking around a bit more, I found something: there are two different RPMs that both claim to be elrepo-release-10.0-1.el10.elrepo.noarch, even though they have different contents. https://elrepo.org/linux/elrepo/el10/x86_64/RPMS/elrepo-release-10.0-1.el10.elrepo.noarch.rpm is a working one that matches what you saw, and https://www.elrepo.org/elrepo-release-10.0-1.el10.elrepo.noarch.rpm is a broken one that matches what I saw. > > Joseph C. Sible > > ________________________________________ > From: elrepo-bounces at lists.elrepo.org on behalf of Joseph Christopher Sible > Sent: Monday, June 9, 2025 12:24 > To: EL Repo General Mailing List > Subject: Re: [elrepo] Remove old GPG key from EL10 elrepo-release package > > Warning: External Sender - do not click links or open attachments unless you recognize the sender and know the content is safe. > > > That doesn't match what I'm seeing. After doing "yum install https://www.elrepo.org/elrepo-release-10.el10.elrepo.noarch.rpm" (per the https://elrepo.org/wiki/doku.php?id=start instructions) in a fresh almalinux:10 Docker container, I see the following: > > [root at e487a2e63bed /]# rpm -ql elrepo-release > /etc/pki/elrepo > /etc/pki/elrepo/SECURE-BOOT-KEY-elrepo.org.der > /etc/pki/rpm-gpg/RPM-GPG-KEY-elrepo.org > /etc/pki/rpm-gpg/RPM-GPG-KEY-v2-elrepo.org > /etc/yum.repos.d/elrepo.repo > [root at e487a2e63bed /]# rpm -qa elrepo-release > elrepo-release-10.0-1.el10.elrepo.noarch > [root at e487a2e63bed /]# > > Regards, > > Joseph C. Sible > > ________________________________________ > From: elrepo-bounces at lists.elrepo.org on behalf of Akemi Yagi > Sent: Monday, June 9, 2025 12:10 > To: EL Repo General Mailing List > Subject: Re: [elrepo] Remove old GPG key from EL10 elrepo-release package > > Warning: External Sender - do not click links or open attachments unless you recognize the sender and know the content is safe. > > > On Mon, Jun 9, 2025 at 8:15?AM Joseph Christopher Sible > wrote: > > > > Hello, > > > > Since the old GPG key doesn't work on RHEL 10, can it be removed from the /etc/yum.repos.d/elrepo.repo file that elrepo-release-10.el10 installs there? Its presence in that file causes GPG errors preventing automatic import of the new key. > > > > Thanks, > > > > Joseph C. Sible > > The elrepo-release-10.0-1.el10.elrepo.noarch package does not contain > the old GPG key: > > $ rpm -ql elrepo-release > /etc/pki/elrepo > /etc/pki/elrepo/SECURE-BOOT-KEY-elrepo.org.der > /etc/pki/rpm-gpg/RPM-GPG-KEY-v2-elrepo.org > /etc/yum.repos.d/elrepo.repo > > Could you check to see if your elrepo.repo file is from the el10 rpm? > > Akemi > _______________________________________________ > elrepo mailing list > elrepo at lists.elrepo.org > http://lists.elrepo.org/mailman/listinfo/elrepo > _______________________________________________ > elrepo mailing list > elrepo at lists.elrepo.org > http://lists.elrepo.org/mailman/listinfo/elrepo > _______________________________________________ > elrepo mailing list > elrepo at lists.elrepo.org > http://lists.elrepo.org/mailman/listinfo/elrepo From toracat at elrepo.org Mon Jun 9 12:46:10 2025 From: toracat at elrepo.org (Akemi Yagi) Date: Mon, 9 Jun 2025 09:46:10 -0700 Subject: [elrepo] Remove old GPG key from EL10 elrepo-release package In-Reply-To: References: Message-ID: Please uninstall and reinstall the package. Is should work now. Akemi On Mon, Jun 9, 2025 at 9:39?AM Akemi Yagi wrote: > > Thank you for letting us know of the source of the incorrect > elrepo-release package. We will correct it shortly. > > Akemi > > On Mon, Jun 9, 2025 at 9:34?AM Joseph Christopher Sible > wrote: > > > > After looking around a bit more, I found something: there are two different RPMs that both claim to be elrepo-release-10.0-1.el10.elrepo.noarch, even though they have different contents. https://elrepo.org/linux/elrepo/el10/x86_64/RPMS/elrepo-release-10.0-1.el10.elrepo.noarch.rpm is a working one that matches what you saw, and https://www.elrepo.org/elrepo-release-10.0-1.el10.elrepo.noarch.rpm is a broken one that matches what I saw. > > > > Joseph C. Sible > > > > ________________________________________ > > From: elrepo-bounces at lists.elrepo.org on behalf of Joseph Christopher Sible > > Sent: Monday, June 9, 2025 12:24 > > To: EL Repo General Mailing List > > Subject: Re: [elrepo] Remove old GPG key from EL10 elrepo-release package > > > > Warning: External Sender - do not click links or open attachments unless you recognize the sender and know the content is safe. > > > > > > That doesn't match what I'm seeing. After doing "yum install https://www.elrepo.org/elrepo-release-10.el10.elrepo.noarch.rpm" (per the https://elrepo.org/wiki/doku.php?id=start instructions) in a fresh almalinux:10 Docker container, I see the following: > > > > [root at e487a2e63bed /]# rpm -ql elrepo-release > > /etc/pki/elrepo > > /etc/pki/elrepo/SECURE-BOOT-KEY-elrepo.org.der > > /etc/pki/rpm-gpg/RPM-GPG-KEY-elrepo.org > > /etc/pki/rpm-gpg/RPM-GPG-KEY-v2-elrepo.org > > /etc/yum.repos.d/elrepo.repo > > [root at e487a2e63bed /]# rpm -qa elrepo-release > > elrepo-release-10.0-1.el10.elrepo.noarch > > [root at e487a2e63bed /]# > > > > Regards, > > > > Joseph C. Sible > > > > ________________________________________ > > From: elrepo-bounces at lists.elrepo.org on behalf of Akemi Yagi > > Sent: Monday, June 9, 2025 12:10 > > To: EL Repo General Mailing List > > Subject: Re: [elrepo] Remove old GPG key from EL10 elrepo-release package > > > > Warning: External Sender - do not click links or open attachments unless you recognize the sender and know the content is safe. > > > > > > On Mon, Jun 9, 2025 at 8:15?AM Joseph Christopher Sible > > wrote: > > > > > > Hello, > > > > > > Since the old GPG key doesn't work on RHEL 10, can it be removed from the /etc/yum.repos.d/elrepo.repo file that elrepo-release-10.el10 installs there? Its presence in that file causes GPG errors preventing automatic import of the new key. > > > > > > Thanks, > > > > > > Joseph C. Sible > > > > The elrepo-release-10.0-1.el10.elrepo.noarch package does not contain > > the old GPG key: > > > > $ rpm -ql elrepo-release > > /etc/pki/elrepo > > /etc/pki/elrepo/SECURE-BOOT-KEY-elrepo.org.der > > /etc/pki/rpm-gpg/RPM-GPG-KEY-v2-elrepo.org > > /etc/yum.repos.d/elrepo.repo > > > > Could you check to see if your elrepo.repo file is from the el10 rpm? > > > > Akemi > > _______________________________________________ > > elrepo mailing list > > elrepo at lists.elrepo.org > > http://lists.elrepo.org/mailman/listinfo/elrepo > > _______________________________________________ > > elrepo mailing list > > elrepo at lists.elrepo.org > > http://lists.elrepo.org/mailman/listinfo/elrepo > > _______________________________________________ > > elrepo mailing list > > elrepo at lists.elrepo.org > > http://lists.elrepo.org/mailman/listinfo/elrepo From toracat at elrepo.org Tue Jun 10 20:28:17 2025 From: toracat at elrepo.org (Akemi Yagi) Date: Tue, 10 Jun 2025 17:28:17 -0700 Subject: [elrepo] Announcement: EL9 Updated kernel-ml Package Set [6.15.2-1] Message-ID: Announcing the release of the kernel-ml-6.15.2-1.el9.elrepo package set into the EL9 elrepo-kernel repository: https://elrepo.org/wiki/doku.php?id=kernel-ml The upstream changelog: https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.15.2 The following files are currently synchronising to our mirror sites: aarch64 [1] bpftool-6.15.2-1.el9.elrepo.aarch64.rpm kernel-ml-6.15.2-1.el9.elrepo.aarch64.rpm kernel-ml-core-6.15.2-1.el9.elrepo.aarch64.rpm kernel-ml-devel-6.15.2-1.el9.elrepo.aarch64.rpm kernel-ml-devel-matched-6.15.2-1.el9.elrepo.aarch64.rpm kernel-ml-doc-6.15.2-1.el9.elrepo.noarch.rpm kernel-ml-headers-6.15.2-1.el9.elrepo.aarch64.rpm kernel-ml-modules-6.15.2-1.el9.elrepo.aarch64.rpm kernel-ml-modules-extra-6.15.2-1.el9.elrepo.aarch64.rpm kernel-ml-tools-6.15.2-1.el9.elrepo.aarch64.rpm kernel-ml-tools-libs-6.15.2-1.el9.elrepo.aarch64.rpm kernel-ml-tools-libs-devel-6.15.2-1.el9.elrepo.aarch64.rpm perf-6.15.2-1.el9.elrepo.aarch64.rpm python3-perf-6.15.2-1.el9.elrepo.aarch64.rpm x86_64 bpftool-6.15.2-1.el9.elrepo.x86_64.rpm kernel-ml-6.15.2-1.el9.elrepo.x86_64.rpm kernel-ml-core-6.15.2-1.el9.elrepo.x86_64.rpm kernel-ml-devel-6.15.2-1.el9.elrepo.x86_64.rpm kernel-ml-devel-matched-6.15.2-1.el9.elrepo.x86_64.rpm kernel-ml-doc-6.15.2-1.el9.elrepo.noarch.rpm kernel-ml-headers-6.15.2-1.el9.elrepo.x86_64.rpm kernel-ml-modules-6.15.2-1.el9.elrepo.x86_64.rpm kernel-ml-modules-extra-6.15.2-1.el9.elrepo.x86_64.rpm kernel-ml-tools-6.15.2-1.el9.elrepo.x86_64.rpm kernel-ml-tools-libs-6.15.2-1.el9.elrepo.x86_64.rpm kernel-ml-tools-libs-devel-6.15.2-1.el9.elrepo.x86_64.rpm perf-6.15.2-1.el9.elrepo.x86_64.rpm python3-perf-6.15.2-1.el9.elrepo.x86_64.rpm nosrc kernel-ml-6.15.2-1.el9.elrepo.nosrc.rpm We provide these kernels for hardware testing in an effort to identify new/updated drivers which can then be targeted for backporting as kmod packages. Meanwhile, these kernels may provide interim relief to people with non-functional hardware. We stress that we consider such kernels as a last resort for those who are unable to get their hardware working using the RHEL-9 kernel with supplementary kmod packages. These packages are provided "As-Is" with no implied warranty or support. Using the kernel-ml may expose your system to security, performance and/or data corruption issues. Since timely updates may not be available from the ELRepo Project, the end user has the ultimate responsibility for deciding whether to continue using the kernel-ml packages in regular service. The packages are intentionally named kernel-ml so as not to conflict with the RHEL-9 kernels and, as such, they may be installed and updated alongside the regular kernel. The kernel configuration is based upon a default RHEL-9 configuration with added functionality enabled as appropriate. If a bug is found when using these kernels, the end user is encouraged to report it upstream to the Linux Kernel Bug Tracker [2] and, for our reference, to the ELRepo bug tracker [3]. By taking such action, the reporter will be assisting the kernel developers, Red Hat and the Open Source Community as a whole. Thank you, The ELRepo Team. [1] The ELRepo Project would like to thank the OSU Open Source Lab for their support with the aarch64 platform. [2] https://bugzilla.kernel.org/ [3] https://elrepo.org/bugs/ From toracat at elrepo.org Tue Jun 10 20:29:49 2025 From: toracat at elrepo.org (Akemi Yagi) Date: Tue, 10 Jun 2025 17:29:49 -0700 Subject: [elrepo] Announcement: EL8 Updated kernel-ml Package Set [6.15.2-1] Message-ID: Announcing the release of the kernel-ml-6.15.2-1.el8.elrepo package set into the EL8 elrepo-kernel repository: https://elrepo.org/wiki/doku.php?id=kernel-ml The upstream changelog: https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.15.2 The following files are currently synchronising to our mirror sites: x86_64 kernel-ml-6.15.2-1.el8.elrepo.x86_64.rpm kernel-ml-core-6.15.2-1.el8.elrepo.x86_64.rpm kernel-ml-devel-6.15.2-1.el8.elrepo.x86_64.rpm kernel-ml-doc-6.15.2-1.el8.elrepo.noarch.rpm kernel-ml-headers-6.15.2-1.el8.elrepo.x86_64.rpm kernel-ml-modules-6.15.2-1.el8.elrepo.x86_64.rpm kernel-ml-modules-extra-6.15.2-1.el8.elrepo.x86_64.rpm kernel-ml-tools-6.15.2-1.el8.elrepo.x86_64.rpm kernel-ml-tools-libs-6.15.2-1.el8.elrepo.x86_64.rpm kernel-ml-tools-libs-devel-6.15.2-1.el8.elrepo.x86_64.rpm perf-6.15.2-1.el8.elrepo.x86_64.rpm python3-perf-6.15.2-1.el8.elrepo.x86_64.rpm nosrc kernel-ml-6.15.2-1.el8.elrepo.nosrc.rpm Please note that as of kernel-ml version 6.5.4 we are unable to continue providing the bpftool package. We provide these kernels for hardware testing in an effort to identify new/updated drivers which can then be targeted for backporting as kmod packages. Meanwhile, these kernels may provide interim relief to people with non-functional hardware. We stress that we consider such kernels as a last resort for those who are unable to get their hardware working using the RHEL-8 kernel with supplementary kmod packages. These packages are provided "As-Is" with no implied warranty or support. Using the kernel-ml may expose your system to security, performance and/or data corruption issues. Since timely updates may not be available from the ELRepo Project, the end user has the ultimate responsibility for deciding whether to continue using the kernel-ml packages in regular service. The packages are intentionally named kernel-ml so as not to conflict with the RHEL-8 kernels and, as such, they may be installed and updated alongside the regular kernel. The kernel configuration is based upon a default RHEL-8 configuration with added functionality enabled as appropriate. If a bug is found when using these kernels, the end user is encouraged to report it upstream to the Linux Kernel Bug Tracker [1] and, for our reference, to the ELRepo bug tracker [2]. By taking such action, the reporter will be assisting the kernel developers, Red Hat and the Open Source Community as a whole. Thank you, The ELRepo Team. [1] https://bugzilla.kernel.org/ [2] https://elrepo.org/bugs/ From toracat at elrepo.org Tue Jun 10 20:26:44 2025 From: toracat at elrepo.org (Akemi Yagi) Date: Tue, 10 Jun 2025 17:26:44 -0700 Subject: [elrepo] Announcement: EL10 Updated kernel-ml Package Set [6.15.2-1] Message-ID: Announcing the release of the kernel-ml-6.15.2-1.el10.elrepo package set into the EL10 elrepo-kernel repository: https://elrepo.org/wiki/doku.php?id=kernel-ml The upstream changelog: https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.15.2 The following files are currently synchronising to our mirror sites: x86_64 kernel-ml-6.15.2-1.el10.elrepo.x86_64.rpm kernel-ml-core-6.15.2-1.el10.elrepo.x86_64.rpm kernel-ml-cross-headers-6.15.2-1.el10.elrepo.x86_64.rpm kernel-ml-devel-6.15.2-1.el10.elrepo.x86_64.rpm kernel-ml-devel-matched-6.15.2-1.el10.elrepo.x86_64.rpm kernel-ml-headers-6.15.2-1.el10.elrepo.x86_64.rpm kernel-ml-modules-6.15.2-1.el10.elrepo.x86_64.rpm kernel-ml-modules-extra-6.15.2-1.el10.elrepo.x86_64.rpm kernel-ml-tools-6.15.2-1.el10.elrepo.x86_64.rpm kernel-ml-tools-libs-6.15.2-1.el10.elrepo.x86_64.rpm kernel-ml-tools-libs-devel-6.15.2-1.el10.elrepo.x86_64.rpm libperf-6.15.2-1.el10.elrepo.x86_64.rpm libperf-devel-6.15.2-1.el10.elrepo.x86_64.rpm perf-6.15.2-1.el10.elrepo.x86_64.rpm python3-perf-6.15.2-1.el10.elrepo.x86_64.rpm rtla-6.15.2-1.el10.elrepo.x86_64.rpm rv-6.15.2-1.el10.elrepo.x86_64.rpm nosrc kernel-ml-6.15.2-1.el10.elrepo.nosrc.rpm We provide these kernels for hardware testing in an effort to identify new/updated drivers which can then be targeted for backporting as kmod packages. Meanwhile, these kernels may provide interim relief to people with non-functional hardware. We stress that we consider such kernels as a last resort for those who are unable to get their hardware working using the RHEL-9 kernel with supplementary kmod packages. These packages are provided "As-Is" with no implied warranty or support. Using the kernel-ml may expose your system to security, performance and/or data corruption issues. Since timely updates may not be available from the ELRepo Project, the end user has the ultimate responsibility for deciding whether to continue using the kernel-ml packages in regular service. The packages are intentionally named kernel-ml so as not to conflict with the RHEL-9 kernels and, as such, they may be installed and updated alongside the regular kernel. The kernel configuration is based upon a default RHEL-9 configuration with added functionality enabled as appropriate. If a bug is found when using these kernels, the end user is encouraged to report it upstream to the Linux Kernel Bug Tracker [1] and, for our reference, to the ELRepo bug tracker [2]. By taking such action, the reporter will be assisting the kernel developers, Red Hat and the Open Source Community as a whole. Thank you, The ELRepo Team. [1] https://bugzilla.kernel.org/ [2] https://elrepo.org/bugs/ From mstuff at read.org.nz Thu Jun 12 13:14:47 2025 From: mstuff at read.org.nz (Morgan Read) Date: Thu, 12 Jun 2025 18:14:47 +0100 Subject: [elrepo] kmod-hspa? Message-ID: Hi List, I've been getting these: `Warning: Unmaintained driver is detected: hpsa` From rhel9 for some time now - since rhel9 - and just noticed kmod-hspa in elrepo. So, there is still a driver from rhel, but it's 'unmaintained'. Is the elrepo kmod-hspa 'maintained' and is it safe to install over the top of the rhel in-kernel module? Thanks -- Morgan Read Grande Bretagne -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From tqhoang at elrepo.org Thu Jun 12 14:17:57 2025 From: tqhoang at elrepo.org (Tuan Hoang) Date: Thu, 12 Jun 2025 18:17:57 +0000 (UTC) Subject: [elrepo] kmod-hspa? In-Reply-To: References: Message-ID: <399336133.2936769.1749752277358@mail.yahoo.com> Hi Morgan, Here is the Red Hat docs explaining what they mean by ?unmaintained?.?What does it mean when hardware is classified as unmaintained in Red Hat Enterprise Linux 8.6+, 9.0 and newer? - Red Hat Customer Portal? | | | | | | | | | | | What does it mean when hardware is classified as unmaintained in Red Hat Enterprise Linux 8.6+, 9.0 and newer? - Red Hat Customer Portal I recently noticed a classification of hardware in the Considerations in Adopting RHEL 9 guide called unmaintained. What does this classification mean for me in terms of hardware enablement and technical support? After installing 8.6 I get the follow | | | | Our ELRepo kmod?drivers exist to:?- restore support for drivers with?disabled?device ID?s- add support for disabled?drivers- add an out-of-kernel?OEM driver (ex: Realtek) Most kmods are just rebuilds from the RHEL kernel source and others are backported from upstream kernels. ?We?also look to backport upstream fixes based upon end-user feedback.? In?essence we try to?provide some level of support to our end-users. ?Please note that this is a volunteer project, but we do spend numerous hours to maintain everything.? Thanks,Tuan Sent from Yahoo Mail for iPhone On Thursday, June 12, 2025, 1:15 PM, Morgan Read via elrepo wrote: Hi List, I've been getting these: `Warning: Unmaintained driver is detected: hpsa` From rhel9 for some time now - since rhel9 - and just noticed kmod-hspa in elrepo.? So, there is still a driver from rhel, but it's 'unmaintained'. Is the elrepo kmod-hspa 'maintained' and is it safe to install over the top of the rhel in-kernel module? Thanks -- Morgan Read Grande Bretagne _______________________________________________ elrepo mailing list elrepo at lists.elrepo.org http://lists.elrepo.org/mailman/listinfo/elrepo -------------- next part -------------- An HTML attachment was scrubbed... URL: From mstuff at read.org.nz Thu Jun 12 18:10:58 2025 From: mstuff at read.org.nz (Morgan Read) Date: Thu, 12 Jun 2025 23:10:58 +0100 (GMT+01:00) Subject: [elrepo] kmod-hspa? In-Reply-To: <399336133.2936769.1749752277358@mail.yahoo.com> References: <399336133.2936769.1749752277358@mail.yahoo.com> Message-ID: <4ac1da6f-cce2-4c3d-8d61-66f8b246c97d@read.org.nz> Thanks Tuan for getting back. I should have been clearer in my question, what I was trying to ask after are the implications of installing the elrepo package - I assume it overwrites `/usr/lib/modules/[uname -r]/kernel/drivers/scsi/hpsa.ko.xz' so do I have to be mindful to reinstall after kernel updates? Thanks Morgan. 12 Jun 2025 19:18:09 Tuan Hoang : > Hi Morgan, > > Here is the Red Hat docs explaining what they mean by ?unmaintained?.? > What does it mean when hardware is classified as unmaintained in Red Hat Enterprise Linux 8.6+, 9.0 and newer? - Red Hat Customer Portal[https://access.redhat.com/solutions/6663421]? > > > > > > *What does it mean when hardware is classified as unmaintained in Red Hat Enterprise Linux 8.6+, 9.0 and newer? - Red Hat Customer Portal* > > I recently noticed a classification of hardware in the Considerations in Adopting RHEL 9 guide called unmaintained. What does this classification mean for me in terms of hardware enablement and technical support? After installing 8.6 I get the follow > > > > [https://access.redhat.com/solutions/6663421] > > Our ELRepo kmod?drivers exist to:? > - restore support for drivers with?disabled?device ID?s > - add support for disabled?drivers > - add an out-of-kernel?OEM driver (ex: Realtek) > > Most kmods are just rebuilds from the RHEL kernel source and others are backported from upstream kernels. ?We?also look to backport upstream fixes based upon end-user feedback.? > > In?essence we try to?provide some level of support to our end-users. ?Please note that this is a volunteer project, but we do spend numerous hours to maintain everything.? > > Thanks, > Tuan > > > Sent from Yahoo Mail for iPhone[https://mail.onelink.me/107872968?pid=nativeplacement&c=Global_Acquisition_YMktg_315_Internal_EmailSignature&af_sub1=Acquisition&af_sub2=Global_YMktg&af_sub3=&af_sub4=100000604&af_sub5=EmailSignature__Static_&af_ios_store_cpp=9d3a686e-218d-4849-8298-b480188dc8ac&af_android_url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.yahoo.mobile.client.android.mail%26listing%3Demail_signature] > > On Thursday, June 12, 2025, 1:15 PM, Morgan Read via elrepo wrote: > > Hi List, > > I've been getting these: > `Warning: Unmaintained driver is detected: hpsa` > From rhel9 for some time now - since rhel9 - and just noticed kmod-hspa > in elrepo.? So, there is still a driver from rhel, but it's 'unmaintained'. > > Is the elrepo kmod-hspa 'maintained' and is it safe to install over the > top of the rhel in-kernel module? > > Thanks > -- > Morgan Read > Grande Bretagne > > _______________________________________________ > elrepo mailing list > elrepo at lists.elrepo.org > http://lists.elrepo.org/mailman/listinfo/elrepo > -- Morgan Read Grande Bretagne From toracat at elrepo.org Fri Jun 13 19:29:15 2025 From: toracat at elrepo.org (Akemi Yagi) Date: Fri, 13 Jun 2025 16:29:15 -0700 Subject: [elrepo] kmod-hspa? In-Reply-To: <4ac1da6f-cce2-4c3d-8d61-66f8b246c97d@read.org.nz> References: <399336133.2936769.1749752277358@mail.yahoo.com> <4ac1da6f-cce2-4c3d-8d61-66f8b246c97d@read.org.nz> Message-ID: Hi Morgan, No, our kernel modules do not overwrite the in-kernel ones. Here, I use the hpsa module and the current kernel version as an example. The distro kernel's driver is found here: /lib/modules/5.14.0-570.21.1.el9_6.x86_64/kernel/drivers/scsi/hpsa.ko.xz while the kmod-hpsa package installs the module as: /lib/modules/5.14.0-570.12.1.el9_6.x86_64/extra/hpsa/hpsa.ko /lib/modules/5.14.0-570.21.1.el9_6.x86_64/weak-updates/hpsa/hpsa.ko -> /lib/modules/5.14.0-570.12.1.el9_6.x86_64/extra/hpsa/hpsa.ko It is installed into the extra/ directory of the 9.6 GA kernel. The symlink above indicates that the module works for the current kernel-5.14.0-570.21.1.el9_6. In general, modules in the "extra" directory are prioritized over the built-in kernel modules. Our configuration file also ensures that the "weak-updates" gets a higher priority. Thus, the hpsa module in the distro kernel will not be used. When the kernel is updated to a newer version, you do not need to update the kmod package as seen in the symlink above (thanks to the kABI compatibility). This is generally true within a point release (e.g. 9.5, 9.6, etc). However a kABI breakage could happen even withing a point release. Therefore you want to install the elrepo repository so the kmod gets updated when it is required. Akemi On Thu, Jun 12, 2025 at 3:11?PM Morgan Read via elrepo wrote: > > Thanks Tuan for getting back. > > I should have been clearer in my question, what I was trying to ask after are the implications of installing the elrepo package - I assume it overwrites `/usr/lib/modules/[uname -r]/kernel/drivers/scsi/hpsa.ko.xz' so do I have to be mindful to reinstall after kernel updates? > > Thanks > Morgan. > > 12 Jun 2025 19:18:09 Tuan Hoang : > > > Hi Morgan, > > > > Here is the Red Hat docs explaining what they mean by ?unmaintained?. > > What does it mean when hardware is classified as unmaintained in Red Hat Enterprise Linux 8.6+, 9.0 and newer? - Red Hat Customer Portal[https://access.redhat.com/solutions/6663421] > > > > > > > > > > > > *What does it mean when hardware is classified as unmaintained in Red Hat Enterprise Linux 8.6+, 9.0 and newer? - Red Hat Customer Portal* > > > > I recently noticed a classification of hardware in the Considerations in Adopting RHEL 9 guide called unmaintained. What does this classification mean for me in terms of hardware enablement and technical support? After installing 8.6 I get the follow > > > > > > > > [https://access.redhat.com/solutions/6663421] > > > > Our ELRepo kmod drivers exist to: > > - restore support for drivers with disabled device ID?s > > - add support for disabled drivers > > - add an out-of-kernel OEM driver (ex: Realtek) > > > > Most kmods are just rebuilds from the RHEL kernel source and others are backported from upstream kernels. We also look to backport upstream fixes based upon end-user feedback. > > > > In essence we try to provide some level of support to our end-users. Please note that this is a volunteer project, but we do spend numerous hours to maintain everything. > > > > Thanks, > > Tuan > > > > > > Sent from Yahoo Mail for iPhone[https://mail.onelink.me/107872968?pid=nativeplacement&c=Global_Acquisition_YMktg_315_Internal_EmailSignature&af_sub1=Acquisition&af_sub2=Global_YMktg&af_sub3=&af_sub4=100000604&af_sub5=EmailSignature__Static_&af_ios_store_cpp=9d3a686e-218d-4849-8298-b480188dc8ac&af_android_url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.yahoo.mobile.client.android.mail%26listing%3Demail_signature] > > > > On Thursday, June 12, 2025, 1:15 PM, Morgan Read via elrepo wrote: > > > > Hi List, > > > > I've been getting these: > > `Warning: Unmaintained driver is detected: hpsa` > > From rhel9 for some time now - since rhel9 - and just noticed kmod-hspa > > in elrepo. So, there is still a driver from rhel, but it's 'unmaintained'. > > > > Is the elrepo kmod-hspa 'maintained' and is it safe to install over the > > top of the rhel in-kernel module? > > > > Thanks > > -- > > Morgan Read > > Grande Bretagne > > > > _______________________________________________ > > elrepo mailing list > > elrepo at lists.elrepo.org > > http://lists.elrepo.org/mailman/listinfo/elrepo > > > > -- > Morgan Read > Grande Bretagne > _______________________________________________ > elrepo mailing list > elrepo at lists.elrepo.org > http://lists.elrepo.org/mailman/listinfo/elrepo From mstuff at read.org.nz Sat Jun 14 17:05:15 2025 From: mstuff at read.org.nz (Morgan Read) Date: Sat, 14 Jun 2025 22:05:15 +0100 Subject: [elrepo] kmod-hspa? In-Reply-To: References: <399336133.2936769.1749752277358@mail.yahoo.com> <4ac1da6f-cce2-4c3d-8d61-66f8b246c97d@read.org.nz> Message-ID: Thank you very much for the indepth explanation, Akemi. Regards M On 14/06/2025 12:29 am, Akemi Yagi wrote: > Hi Morgan, > > No, our kernel modules do not overwrite the in-kernel ones. Here, I > use the hpsa module and the current kernel version as an example. > > The distro kernel's driver is found here: > > /lib/modules/5.14.0-570.21.1.el9_6.x86_64/kernel/drivers/scsi/hpsa.ko.xz > > while the kmod-hpsa package installs the module as: > > /lib/modules/5.14.0-570.12.1.el9_6.x86_64/extra/hpsa/hpsa.ko > /lib/modules/5.14.0-570.21.1.el9_6.x86_64/weak-updates/hpsa/hpsa.ko -> > /lib/modules/5.14.0-570.12.1.el9_6.x86_64/extra/hpsa/hpsa.ko > > It is installed into the extra/ directory of the 9.6 GA kernel. The > symlink above indicates that the module works for the current > kernel-5.14.0-570.21.1.el9_6. > > In general, modules in the "extra" directory are prioritized over the > built-in kernel modules. Our configuration file also ensures that the > "weak-updates" gets a higher priority. Thus, the hpsa module in the > distro kernel will not be used. > > When the kernel is updated to a newer version, you do not need to > update the kmod package as seen in the symlink above (thanks to the > kABI compatibility). This is generally true within a point release > (e.g. 9.5, 9.6, etc). However a kABI breakage could happen even > withing a point release. Therefore you want to install the elrepo > repository so the kmod gets updated when it is required. > > Akemi > > > > > > On Thu, Jun 12, 2025 at 3:11?PM Morgan Read via elrepo > wrote: >> >> Thanks Tuan for getting back. >> >> I should have been clearer in my question, what I was trying to ask after are the implications of installing the elrepo package - I assume it overwrites `/usr/lib/modules/[uname -r]/kernel/drivers/scsi/hpsa.ko.xz' so do I have to be mindful to reinstall after kernel updates? >> >> Thanks >> Morgan. >> >> 12 Jun 2025 19:18:09 Tuan Hoang : >> >>> Hi Morgan, >>> >>> Here is the Red Hat docs explaining what they mean by ?unmaintained?. >>> What does it mean when hardware is classified as unmaintained in Red Hat Enterprise Linux 8.6+, 9.0 and newer? - Red Hat Customer Portal[https://access.redhat.com/solutions/6663421] >>> >>> >>> >>> >>> >>> *What does it mean when hardware is classified as unmaintained in Red Hat Enterprise Linux 8.6+, 9.0 and newer? - Red Hat Customer Portal* >>> >>> I recently noticed a classification of hardware in the Considerations in Adopting RHEL 9 guide called unmaintained. What does this classification mean for me in terms of hardware enablement and technical support? After installing 8.6 I get the follow >>> >>> >>> >>> [https://access.redhat.com/solutions/6663421] >>> >>> Our ELRepo kmod drivers exist to: >>> - restore support for drivers with disabled device ID?s >>> - add support for disabled drivers >>> - add an out-of-kernel OEM driver (ex: Realtek) >>> >>> Most kmods are just rebuilds from the RHEL kernel source and others are backported from upstream kernels. We also look to backport upstream fixes based upon end-user feedback. >>> >>> In essence we try to provide some level of support to our end-users. Please note that this is a volunteer project, but we do spend numerous hours to maintain everything. >>> >>> Thanks, >>> Tuan >>> >>> >>> Sent from Yahoo Mail for iPhone[https://mail.onelink.me/107872968?pid=nativeplacement&c=Global_Acquisition_YMktg_315_Internal_EmailSignature&af_sub1=Acquisition&af_sub2=Global_YMktg&af_sub3=&af_sub4=100000604&af_sub5=EmailSignature__Static_&af_ios_store_cpp=9d3a686e-218d-4849-8298-b480188dc8ac&af_android_url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.yahoo.mobile.client.android.mail%26listing%3Demail_signature] >>> >>> On Thursday, June 12, 2025, 1:15 PM, Morgan Read via elrepo wrote: >>> >>> Hi List, >>> >>> I've been getting these: >>> `Warning: Unmaintained driver is detected: hpsa` >>> From rhel9 for some time now - since rhel9 - and just noticed kmod-hspa >>> in elrepo. So, there is still a driver from rhel, but it's 'unmaintained'. >>> >>> Is the elrepo kmod-hspa 'maintained' and is it safe to install over the >>> top of the rhel in-kernel module? >>> >>> Thanks >>> -- >>> Morgan Read >>> Grande Bretagne >>> >>> _______________________________________________ >>> elrepo mailing list >>> elrepo at lists.elrepo.org >>> http://lists.elrepo.org/mailman/listinfo/elrepo >>> >> >> -- >> Morgan Read >> Grande Bretagne >> _______________________________________________ >> elrepo mailing list >> elrepo at lists.elrepo.org >> http://lists.elrepo.org/mailman/listinfo/elrepo -- Morgan Read Grande Bretagne -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From toracat at elrepo.org Thu Jun 19 19:02:22 2025 From: toracat at elrepo.org (Akemi Yagi) Date: Thu, 19 Jun 2025 16:02:22 -0700 Subject: [elrepo] Announcement: EL9 Updated kernel-ml Package Set [6.15.3-1] Message-ID: Announcing the release of the kernel-ml-6.15.3-1.el9.elrepo package set into the EL9 elrepo-kernel repository: https://elrepo.org/wiki/doku.php?id=kernel-ml The upstream changelog: https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.15.3 ## Please note that the aarch64 packages could not be provided here ## because of build error. They may be released at a later time. The following files are currently synchronising to our mirror sites: x86_64 bpftool-6.15.3-1.el9.elrepo.x86_64.rpm kernel-ml-6.15.3-1.el9.elrepo.x86_64.rpm kernel-ml-core-6.15.3-1.el9.elrepo.x86_64.rpm kernel-ml-devel-6.15.3-1.el9.elrepo.x86_64.rpm kernel-ml-devel-matched-6.15.3-1.el9.elrepo.x86_64.rpm kernel-ml-doc-6.15.3-1.el9.elrepo.noarch.rpm kernel-ml-headers-6.15.3-1.el9.elrepo.x86_64.rpm kernel-ml-modules-6.15.3-1.el9.elrepo.x86_64.rpm kernel-ml-modules-extra-6.15.3-1.el9.elrepo.x86_64.rpm kernel-ml-tools-6.15.3-1.el9.elrepo.x86_64.rpm kernel-ml-tools-libs-6.15.3-1.el9.elrepo.x86_64.rpm kernel-ml-tools-libs-devel-6.15.3-1.el9.elrepo.x86_64.rpm perf-6.15.3-1.el9.elrepo.x86_64.rpm python3-perf-6.15.3-1.el9.elrepo.x86_64.rpm nosrc kernel-ml-6.15.3-1.el9.elrepo.nosrc.rpm We provide these kernels for hardware testing in an effort to identify new/updated drivers which can then be targeted for backporting as kmod packages. Meanwhile, these kernels may provide interim relief to people with non-functional hardware. We stress that we consider such kernels as a last resort for those who are unable to get their hardware working using the RHEL-9 kernel with supplementary kmod packages. These packages are provided "As-Is" with no implied warranty or support. Using the kernel-ml may expose your system to security, performance and/or data corruption issues. Since timely updates may not be available from the ELRepo Project, the end user has the ultimate responsibility for deciding whether to continue using the kernel-ml packages in regular service. The packages are intentionally named kernel-ml so as not to conflict with the RHEL-9 kernels and, as such, they may be installed and updated alongside the regular kernel. The kernel configuration is based upon a default RHEL-9 configuration with added functionality enabled as appropriate. If a bug is found when using these kernels, the end user is encouraged to report it upstream to the Linux Kernel Bug Tracker [1] and, for our reference, to the ELRepo bug tracker [2]. By taking such action, the reporter will be assisting the kernel developers, Red Hat and the Open Source Community as a whole. Thank you, The ELRepo Team. [1] https://bugzilla.kernel.org/ [2] https://elrepo.org/bugs/ From toracat at elrepo.org Thu Jun 19 19:04:02 2025 From: toracat at elrepo.org (Akemi Yagi) Date: Thu, 19 Jun 2025 16:04:02 -0700 Subject: [elrepo] Announcement: EL8 Updated kernel-ml Package Set [6.15.3-1] Message-ID: Announcing the release of the kernel-ml-6.15.3-1.el8.elrepo package set into the EL8 elrepo-kernel repository: https://elrepo.org/wiki/doku.php?id=kernel-ml The upstream changelog: https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.15.3 The following files are currently synchronising to our mirror sites: x86_64 kernel-ml-6.15.3-1.el8.elrepo.x86_64.rpm kernel-ml-core-6.15.3-1.el8.elrepo.x86_64.rpm kernel-ml-devel-6.15.3-1.el8.elrepo.x86_64.rpm kernel-ml-doc-6.15.3-1.el8.elrepo.noarch.rpm kernel-ml-headers-6.15.3-1.el8.elrepo.x86_64.rpm kernel-ml-modules-6.15.3-1.el8.elrepo.x86_64.rpm kernel-ml-modules-extra-6.15.3-1.el8.elrepo.x86_64.rpm kernel-ml-tools-6.15.3-1.el8.elrepo.x86_64.rpm kernel-ml-tools-libs-6.15.3-1.el8.elrepo.x86_64.rpm kernel-ml-tools-libs-devel-6.15.3-1.el8.elrepo.x86_64.rpm perf-6.15.3-1.el8.elrepo.x86_64.rpm python3-perf-6.15.3-1.el8.elrepo.x86_64.rpm nosrc kernel-ml-6.15.3-1.el8.elrepo.nosrc.rpm Please note that as of kernel-ml version 6.5.4 we are unable to continue providing the bpftool package. We provide these kernels for hardware testing in an effort to identify new/updated drivers which can then be targeted for backporting as kmod packages. Meanwhile, these kernels may provide interim relief to people with non-functional hardware. We stress that we consider such kernels as a last resort for those who are unable to get their hardware working using the RHEL-8 kernel with supplementary kmod packages. These packages are provided "As-Is" with no implied warranty or support. Using the kernel-ml may expose your system to security, performance and/or data corruption issues. Since timely updates may not be available from the ELRepo Project, the end user has the ultimate responsibility for deciding whether to continue using the kernel-ml packages in regular service. The packages are intentionally named kernel-ml so as not to conflict with the RHEL-8 kernels and, as such, they may be installed and updated alongside the regular kernel. The kernel configuration is based upon a default RHEL-8 configuration with added functionality enabled as appropriate. If a bug is found when using these kernels, the end user is encouraged to report it upstream to the Linux Kernel Bug Tracker [1] and, for our reference, to the ELRepo bug tracker [2]. By taking such action, the reporter will be assisting the kernel developers, Red Hat and the Open Source Community as a whole. Thank you, The ELRepo Team. [1] https://bugzilla.kernel.org/ [2] https://elrepo.org/bugs/ From toracat at elrepo.org Thu Jun 19 19:00:22 2025 From: toracat at elrepo.org (Akemi Yagi) Date: Thu, 19 Jun 2025 16:00:22 -0700 Subject: [elrepo] Announcement: EL10 Updated kernel-ml Package Set [6.15.3-1] Message-ID: Announcing the release of the kernel-ml-6.15.3-1.el10.elrepo package set into the EL10 elrepo-kernel repository: https://elrepo.org/wiki/doku.php?id=kernel-ml The upstream changelog: https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.15.3 The following files are currently synchronising to our mirror sites: x86_64 kernel-ml-6.15.3-1.el10.elrepo.x86_64.rpm kernel-ml-core-6.15.3-1.el10.elrepo.x86_64.rpm kernel-ml-cross-headers-6.15.3-1.el10.elrepo.x86_64.rpm kernel-ml-devel-6.15.3-1.el10.elrepo.x86_64.rpm kernel-ml-devel-matched-6.15.3-1.el10.elrepo.x86_64.rpm kernel-ml-headers-6.15.3-1.el10.elrepo.x86_64.rpm kernel-ml-modules-6.15.3-1.el10.elrepo.x86_64.rpm kernel-ml-modules-extra-6.15.3-1.el10.elrepo.x86_64.rpm kernel-ml-tools-6.15.3-1.el10.elrepo.x86_64.rpm kernel-ml-tools-libs-6.15.3-1.el10.elrepo.x86_64.rpm kernel-ml-tools-libs-devel-6.15.3-1.el10.elrepo.x86_64.rpm libperf-6.15.3-1.el10.elrepo.x86_64.rpm libperf-devel-6.15.3-1.el10.elrepo.x86_64.rpm perf-6.15.3-1.el10.elrepo.x86_64.rpm python3-perf-6.15.3-1.el10.elrepo.x86_64.rpm rtla-6.15.3-1.el10.elrepo.x86_64.rpm rv-6.15.3-1.el10.elrepo.x86_64.rpm nosrc kernel-ml-6.15.3-1.el10.elrepo.nosrc.rpm We provide these kernels for hardware testing in an effort to identify new/updated drivers which can then be targeted for backporting as kmod packages. Meanwhile, these kernels may provide interim relief to people with non-functional hardware. We stress that we consider such kernels as a last resort for those who are unable to get their hardware working using the RHEL-9 kernel with supplementary kmod packages. These packages are provided "As-Is" with no implied warranty or support. Using the kernel-ml may expose your system to security, performance and/or data corruption issues. Since timely updates may not be available from the ELRepo Project, the end user has the ultimate responsibility for deciding whether to continue using the kernel-ml packages in regular service. The packages are intentionally named kernel-ml so as not to conflict with the RHEL-9 kernels and, as such, they may be installed and updated alongside the regular kernel. The kernel configuration is based upon a default RHEL-9 configuration with added functionality enabled as appropriate. If a bug is found when using these kernels, the end user is encouraged to report it upstream to the Linux Kernel Bug Tracker [1] and, for our reference, to the ELRepo bug tracker [2]. By taking such action, the reporter will be assisting the kernel developers, Red Hat and the Open Source Community as a whole. Thank you, The ELRepo Team. [1] https://bugzilla.kernel.org/ [2] https://elrepo.org/bugs/ From toracat at elrepo.org Fri Jun 20 12:40:55 2025 From: toracat at elrepo.org (Akemi Yagi) Date: Fri, 20 Jun 2025 09:40:55 -0700 Subject: [elrepo] Announcement: EL9 Updated kernel-ml Package Set [6.15.3-1] (aarch64) Message-ID: ## Please note that the x86_64 packages were released earlier. Announcing the release of the kernel-ml-6.15.3-1.el9.elrepo package set into the EL9 elrepo-kernel repository: https://elrepo.org/wiki/doku.php?id=kernel-ml The upstream changelog: https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.15.3 The following files are currently synchronising to our mirror sites: aarch64 [1] bpftool-6.15.3-1.el9.elrepo.aarch64.rpm kernel-ml-6.15.3-1.el9.elrepo.aarch64.rpm kernel-ml-core-6.15.3-1.el9.elrepo.aarch64.rpm kernel-ml-devel-6.15.3-1.el9.elrepo.aarch64.rpm kernel-ml-devel-matched-6.15.3-1.el9.elrepo.aarch64.rpm kernel-ml-doc-6.15.3-1.el9.elrepo.noarch.rpm kernel-ml-headers-6.15.3-1.el9.elrepo.aarch64.rpm kernel-ml-modules-6.15.3-1.el9.elrepo.aarch64.rpm kernel-ml-modules-extra-6.15.3-1.el9.elrepo.aarch64.rpm kernel-ml-tools-6.15.3-1.el9.elrepo.aarch64.rpm kernel-ml-tools-libs-6.15.3-1.el9.elrepo.aarch64.rpm kernel-ml-tools-libs-devel-6.15.3-1.el9.elrepo.aarch64.rpm perf-6.15.3-1.el9.elrepo.aarch64.rpm python3-perf-6.15.3-1.el9.elrepo.aarch64.rpm nosrc kernel-ml-6.15.3-1.el9.elrepo.nosrc.rpm We provide these kernels for hardware testing in an effort to identify new/updated drivers which can then be targeted for backporting as kmod packages. Meanwhile, these kernels may provide interim relief to people with non-functional hardware. We stress that we consider such kernels as a last resort for those who are unable to get their hardware working using the RHEL-9 kernel with supplementary kmod packages. These packages are provided "As-Is" with no implied warranty or support. Using the kernel-ml may expose your system to security, performance and/or data corruption issues. Since timely updates may not be available from the ELRepo Project, the end user has the ultimate responsibility for deciding whether to continue using the kernel-ml packages in regular service. The packages are intentionally named kernel-ml so as not to conflict with the RHEL-9 kernels and, as such, they may be installed and updated alongside the regular kernel. The kernel configuration is based upon a default RHEL-9 configuration with added functionality enabled as appropriate. If a bug is found when using these kernels, the end user is encouraged to report it upstream to the Linux Kernel Bug Tracker [2] and, for our reference, to the ELRepo bug tracker [3]. By taking such action, the reporter will be assisting the kernel developers, Red Hat and the Open Source Community as a whole. Thank you, The ELRepo Team. [1] The ELRepo Project would like to thank the OSU Open Source Lab for their support with the aarch64 platform. [2] https://bugzilla.kernel.org/ [3] https://elrepo.org/bugs/ From toracat at elrepo.org Fri Jun 27 21:12:07 2025 From: toracat at elrepo.org (Akemi Yagi) Date: Fri, 27 Jun 2025 18:12:07 -0700 Subject: [elrepo] Announcement: EL8 Updated kernel-ml Package Set [6.15.4-1] Message-ID: Announcing the release of the kernel-ml-6.15.4-1.el8.elrepo package set into the EL8 elrepo-kernel repository: https://elrepo.org/wiki/doku.php?id=kernel-ml The upstream changelog: https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.15.4 The following files are currently synchronising to our mirror sites: x86_64 kernel-ml-6.15.4-1.el8.elrepo.x86_64.rpm kernel-ml-core-6.15.4-1.el8.elrepo.x86_64.rpm kernel-ml-devel-6.15.4-1.el8.elrepo.x86_64.rpm kernel-ml-doc-6.15.4-1.el8.elrepo.noarch.rpm kernel-ml-headers-6.15.4-1.el8.elrepo.x86_64.rpm kernel-ml-modules-6.15.4-1.el8.elrepo.x86_64.rpm kernel-ml-modules-extra-6.15.4-1.el8.elrepo.x86_64.rpm kernel-ml-tools-6.15.4-1.el8.elrepo.x86_64.rpm kernel-ml-tools-libs-6.15.4-1.el8.elrepo.x86_64.rpm kernel-ml-tools-libs-devel-6.15.4-1.el8.elrepo.x86_64.rpm perf-6.15.4-1.el8.elrepo.x86_64.rpm python3-perf-6.15.4-1.el8.elrepo.x86_64.rpm nosrc kernel-ml-6.15.4-1.el8.elrepo.nosrc.rpm Please note that as of kernel-ml version 6.5.4 we are unable to continue providing the bpftool package. We provide these kernels for hardware testing in an effort to identify new/updated drivers which can then be targeted for backporting as kmod packages. Meanwhile, these kernels may provide interim relief to people with non-functional hardware. We stress that we consider such kernels as a last resort for those who are unable to get their hardware working using the RHEL-8 kernel with supplementary kmod packages. These packages are provided "As-Is" with no implied warranty or support. Using the kernel-ml may expose your system to security, performance and/or data corruption issues. Since timely updates may not be available from the ELRepo Project, the end user has the ultimate responsibility for deciding whether to continue using the kernel-ml packages in regular service. The packages are intentionally named kernel-ml so as not to conflict with the RHEL-8 kernels and, as such, they may be installed and updated alongside the regular kernel. The kernel configuration is based upon a default RHEL-8 configuration with added functionality enabled as appropriate. If a bug is found when using these kernels, the end user is encouraged to report it upstream to the Linux Kernel Bug Tracker [1] and, for our reference, to the ELRepo bug tracker [2]. By taking such action, the reporter will be assisting the kernel developers, Red Hat and the Open Source Community as a whole. Thank you, The ELRepo Team. [1] https://bugzilla.kernel.org/ [2] https://elrepo.org/bugs/ From toracat at elrepo.org Fri Jun 27 21:13:19 2025 From: toracat at elrepo.org (Akemi Yagi) Date: Fri, 27 Jun 2025 18:13:19 -0700 Subject: [elrepo] Announcement: EL9 Updated kernel-lt Package Set [6.1.142-1] Message-ID: Announcing the release of the kernel-lt-6.1.142-1.el9.elrepo package set into the EL9 elrepo-kernel repository: https://elrepo.org/wiki/doku.php?id=kernel-lt The upstream changelog: https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.142 The following files are currently synchronising to our mirror sites: aarch64 [1] bpftool-6.1.142-1.el9.elrepo.aarch64.rpm kernel-lt-6.1.142-1.el9.elrepo.aarch64.rpm kernel-lt-core-6.1.142-1.el9.elrepo.aarch64.rpm kernel-lt-devel-6.1.142-1.el9.elrepo.aarch64.rpm kernel-lt-devel-matched-6.1.142-1.el9.elrepo.aarch64.rpm kernel-lt-doc-6.1.142-1.el9.elrepo.noarch.rpm kernel-lt-headers-6.1.142-1.el9.elrepo.aarch64.rpm kernel-lt-modules-6.1.142-1.el9.elrepo.aarch64.rpm kernel-lt-modules-extra-6.1.142-1.el9.elrepo.aarch64.rpm kernel-lt-tools-6.1.142-1.el9.elrepo.aarch64.rpm kernel-lt-tools-libs-6.1.142-1.el9.elrepo.aarch64.rpm kernel-lt-tools-libs-devel-6.1.142-1.el9.elrepo.aarch64.rpm perf-6.1.142-1.el9.elrepo.aarch64.rpm python3-perf-6.1.142-1.el9.elrepo.aarch64.rpm x86_64 bpftool-6.1.142-1.el9.elrepo.x86_64.rpm kernel-lt-6.1.142-1.el9.elrepo.x86_64.rpm kernel-lt-core-6.1.142-1.el9.elrepo.x86_64.rpm kernel-lt-devel-6.1.142-1.el9.elrepo.x86_64.rpm kernel-lt-devel-matched-6.1.142-1.el9.elrepo.x86_64.rpm kernel-lt-doc-6.1.142-1.el9.elrepo.noarch.rpm kernel-lt-headers-6.1.142-1.el9.elrepo.x86_64.rpm kernel-lt-modules-6.1.142-1.el9.elrepo.x86_64.rpm kernel-lt-modules-extra-6.1.142-1.el9.elrepo.x86_64.rpm kernel-lt-tools-6.1.142-1.el9.elrepo.x86_64.rpm kernel-lt-tools-libs-6.1.142-1.el9.elrepo.x86_64.rpm kernel-lt-tools-libs-devel-6.1.142-1.el9.elrepo.x86_64.rpm perf-6.1.142-1.el9.elrepo.x86_64.rpm python3-perf-6.1.142-1.el9.elrepo.x86_64.rpm nosrc kernel-lt-6.1.142-1.el9.elrepo.nosrc.rpm We provide these kernels for hardware testing in an effort to identify new/updated drivers which can then be targeted for backporting as kmod packages. Meanwhile, these kernels may provide interim relief to people with non-functional hardware. We stress that we consider such kernels as a last resort for those who are unable to get their hardware working using the RHEL-9 kernel with supplementary kmod packages. These packages are provided "As-Is" with no implied warranty or support. Using the kernel-lt may expose your system to security, performance and/or data corruption issues. Since timely updates may not be available from the ELRepo Project, the end user has the ultimate responsibility for deciding whether to continue using the kernel-lt packages in regular service. The packages are intentionally named kernel-lt so as not to conflict with the RHEL-9 kernels and, as such, they may be installed and updated alongside the regular kernel. The kernel configuration is based upon a default RHEL-9 configuration with added functionality enabled as appropriate. If a bug is found when using these kernels, the end user is encouraged to report it upstream to the Linux Kernel Bug Tracker [2] and, for our reference, to the ELRepo bug tracker [3]. By taking such action, the reporter will be assisting the kernel developers, Red Hat and the Open Source Community as a whole. Thank you, The ELRepo Team. [1] The ELRepo Project would like to thank the OSU Open Source Lab for their support with the aarch64 platform. [2] https://bugzilla.kernel.org/ [3] https://elrepo.org/bugs/ From toracat at elrepo.org Fri Jun 27 21:14:53 2025 From: toracat at elrepo.org (Akemi Yagi) Date: Fri, 27 Jun 2025 18:14:53 -0700 Subject: [elrepo] Announcement: EL8 Updated kernel-lt Package Set [5.4.295-1] Message-ID: Announcing the release of the kernel-lt-5.4.295-1.el8.elrepo package set into the EL8 elrepo-kernel repository: https://elrepo.org/wiki/doku.php?id=kernel-lt The upstream changelog: https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.295 The following files are currently synchronising to our mirror sites: x86_64 bpftool-5.4.295-1.el8.elrepo.x86_64.rpm kernel-lt-5.4.295-1.el8.elrepo.x86_64.rpm kernel-lt-core-5.4.295-1.el8.elrepo.x86_64.rpm kernel-lt-devel-5.4.295-1.el8.elrepo.x86_64.rpm kernel-lt-doc-5.4.295-1.el8.elrepo.noarch.rpm kernel-lt-headers-5.4.295-1.el8.elrepo.x86_64.rpm kernel-lt-modules-5.4.295-1.el8.elrepo.x86_64.rpm kernel-lt-modules-extra-5.4.295-1.el8.elrepo.x86_64.rpm kernel-lt-tools-5.4.295-1.el8.elrepo.x86_64.rpm kernel-lt-tools-libs-5.4.295-1.el8.elrepo.x86_64.rpm kernel-lt-tools-libs-devel-5.4.295-1.el8.elrepo.x86_64.rpm perf-5.4.295-1.el8.elrepo.x86_64.rpm python3-perf-5.4.295-1.el8.elrepo.x86_64.rpm nosrc kernel-lt-5.4.295-1.el8.elrepo.nosrc.rpm We provide these kernels for hardware testing in an effort to identify new/updated drivers which can then be targeted for backporting as kmod packages. Meanwhile, these kernels may provide interim relief to people with non-functional hardware. We stress that we consider such kernels as a last resort for those who are unable to get their hardware working using the RHEL-8 kernel with supplementary kmod packages. These packages are provided "As-Is" with no implied warranty or support. Using the kernel-lt may expose your system to security, performance and/or data corruption issues. Since timely updates may not be available from the ELRepo Project, the end user has the ultimate responsibility for deciding whether to continue using the kernel-lt packages in regular service. The packages are intentionally named kernel-lt so as not to conflict with the RHEL-8 kernels and, as such, they may be installed and updated alongside the regular kernel. The kernel configuration is based upon a default RHEL-8 configuration with added functionality enabled as appropriate. If a bug is found when using these kernels, the end user is encouraged to report it upstream to the Linux Kernel Bug Tracker [1] and, for our reference, to the ELRepo bug tracker [2]. By taking such action, the reporter will be assisting the kernel developers, Red Hat and the Open Source Community as a whole. Thank you, The ELRepo Team. [1] https://bugzilla.kernel.org/ [2] https://elrepo.org/bugs/ From toracat at elrepo.org Fri Jun 27 21:09:36 2025 From: toracat at elrepo.org (Akemi Yagi) Date: Fri, 27 Jun 2025 18:09:36 -0700 Subject: [elrepo] Announcement: EL9 Updated kernel-ml Package Set [6.15.4-1] Message-ID: Announcing the release of the kernel-ml-6.15.4-1.el9.elrepo package set into the EL9 elrepo-kernel repository: https://elrepo.org/wiki/doku.php?id=kernel-ml The upstream changelog: https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.15.4 The following files are currently synchronising to our mirror sites: aarch64 [1] bpftool-6.15.4-1.el9.elrepo.aarch64.rpm kernel-ml-6.15.4-1.el9.elrepo.aarch64.rpm kernel-ml-core-6.15.4-1.el9.elrepo.aarch64.rpm kernel-ml-devel-6.15.4-1.el9.elrepo.aarch64.rpm kernel-ml-devel-matched-6.15.4-1.el9.elrepo.aarch64.rpm kernel-ml-doc-6.15.4-1.el9.elrepo.noarch.rpm kernel-ml-headers-6.15.4-1.el9.elrepo.aarch64.rpm kernel-ml-modules-6.15.4-1.el9.elrepo.aarch64.rpm kernel-ml-modules-extra-6.15.4-1.el9.elrepo.aarch64.rpm kernel-ml-tools-6.15.4-1.el9.elrepo.aarch64.rpm kernel-ml-tools-libs-6.15.4-1.el9.elrepo.aarch64.rpm kernel-ml-tools-libs-devel-6.15.4-1.el9.elrepo.aarch64.rpm perf-6.15.4-1.el9.elrepo.aarch64.rpm python3-perf-6.15.4-1.el9.elrepo.aarch64.rpm x86_64 bpftool-6.15.4-1.el9.elrepo.x86_64.rpm kernel-ml-6.15.4-1.el9.elrepo.x86_64.rpm kernel-ml-core-6.15.4-1.el9.elrepo.x86_64.rpm kernel-ml-devel-6.15.4-1.el9.elrepo.x86_64.rpm kernel-ml-devel-matched-6.15.4-1.el9.elrepo.x86_64.rpm kernel-ml-doc-6.15.4-1.el9.elrepo.noarch.rpm kernel-ml-headers-6.15.4-1.el9.elrepo.x86_64.rpm kernel-ml-modules-6.15.4-1.el9.elrepo.x86_64.rpm kernel-ml-modules-extra-6.15.4-1.el9.elrepo.x86_64.rpm kernel-ml-tools-6.15.4-1.el9.elrepo.x86_64.rpm kernel-ml-tools-libs-6.15.4-1.el9.elrepo.x86_64.rpm kernel-ml-tools-libs-devel-6.15.4-1.el9.elrepo.x86_64.rpm perf-6.15.4-1.el9.elrepo.x86_64.rpm python3-perf-6.15.4-1.el9.elrepo.x86_64.rpm nosrc kernel-ml-6.15.4-1.el9.elrepo.nosrc.rpm We provide these kernels for hardware testing in an effort to identify new/updated drivers which can then be targeted for backporting as kmod packages. Meanwhile, these kernels may provide interim relief to people with non-functional hardware. We stress that we consider such kernels as a last resort for those who are unable to get their hardware working using the RHEL-9 kernel with supplementary kmod packages. These packages are provided "As-Is" with no implied warranty or support. Using the kernel-ml may expose your system to security, performance and/or data corruption issues. Since timely updates may not be available from the ELRepo Project, the end user has the ultimate responsibility for deciding whether to continue using the kernel-ml packages in regular service. The packages are intentionally named kernel-ml so as not to conflict with the RHEL-9 kernels and, as such, they may be installed and updated alongside the regular kernel. The kernel configuration is based upon a default RHEL-9 configuration with added functionality enabled as appropriate. If a bug is found when using these kernels, the end user is encouraged to report it upstream to the Linux Kernel Bug Tracker [2] and, for our reference, to the ELRepo bug tracker [3]. By taking such action, the reporter will be assisting the kernel developers, Red Hat and the Open Source Community as a whole. Thank you, The ELRepo Team. [1] The ELRepo Project would like to thank the OSU Open Source Lab for their support with the aarch64 platform. [2] https://bugzilla.kernel.org/ [3] https://elrepo.org/bugs/ From toracat at elrepo.org Fri Jun 27 21:11:17 2025 From: toracat at elrepo.org (Akemi Yagi) Date: Fri, 27 Jun 2025 18:11:17 -0700 Subject: [elrepo] Announcement: EL10 Updated kernel-ml Package Set [6.15.4-1] Message-ID: Announcing the release of the kernel-ml-6.15.4-1.el10.elrepo package set into the EL10 elrepo-kernel repository: https://elrepo.org/wiki/doku.php?id=kernel-ml The upstream changelog: https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.15.4 The following files are currently synchronising to our mirror sites: x86_64 kernel-ml-6.15.4-1.el10.elrepo.x86_64.rpm kernel-ml-core-6.15.4-1.el10.elrepo.x86_64.rpm kernel-ml-cross-headers-6.15.4-1.el10.elrepo.x86_64.rpm kernel-ml-devel-6.15.4-1.el10.elrepo.x86_64.rpm kernel-ml-devel-matched-6.15.4-1.el10.elrepo.x86_64.rpm kernel-ml-headers-6.15.4-1.el10.elrepo.x86_64.rpm kernel-ml-modules-6.15.4-1.el10.elrepo.x86_64.rpm kernel-ml-modules-extra-6.15.4-1.el10.elrepo.x86_64.rpm kernel-ml-tools-6.15.4-1.el10.elrepo.x86_64.rpm kernel-ml-tools-libs-6.15.4-1.el10.elrepo.x86_64.rpm kernel-ml-tools-libs-devel-6.15.4-1.el10.elrepo.x86_64.rpm libperf-6.15.4-1.el10.elrepo.x86_64.rpm libperf-devel-6.15.4-1.el10.elrepo.x86_64.rpm perf-6.15.4-1.el10.elrepo.x86_64.rpm python3-perf-6.15.4-1.el10.elrepo.x86_64.rpm rtla-6.15.4-1.el10.elrepo.x86_64.rpm rv-6.15.4-1.el10.elrepo.x86_64.rpm nosrc kernel-ml-6.15.4-1.el10.elrepo.nosrc.rpm We provide these kernels for hardware testing in an effort to identify new/updated drivers which can then be targeted for backporting as kmod packages. Meanwhile, these kernels may provide interim relief to people with non-functional hardware. We stress that we consider such kernels as a last resort for those who are unable to get their hardware working using the RHEL-9 kernel with supplementary kmod packages. These packages are provided "As-Is" with no implied warranty or support. Using the kernel-ml may expose your system to security, performance and/or data corruption issues. Since timely updates may not be available from the ELRepo Project, the end user has the ultimate responsibility for deciding whether to continue using the kernel-ml packages in regular service. The packages are intentionally named kernel-ml so as not to conflict with the RHEL-9 kernels and, as such, they may be installed and updated alongside the regular kernel. The kernel configuration is based upon a default RHEL-9 configuration with added functionality enabled as appropriate. If a bug is found when using these kernels, the end user is encouraged to report it upstream to the Linux Kernel Bug Tracker [1] and, for our reference, to the ELRepo bug tracker [2]. By taking such action, the reporter will be assisting the kernel developers, Red Hat and the Open Source Community as a whole. Thank you, The ELRepo Team. [1] https://bugzilla.kernel.org/ [2] https://elrepo.org/bugs/