[elrepo] Announcement: EL5 and EL6 Updated kernel-lt Release [3.0.94-1]
Announcing the release of the kernel-lt-3.0.94-1.el5.elrepo and kernel-lt-3.0.94-1.el6.elrepo packages into the respective elrepo-kernel repositories: http://elrepo.org/tiki/kernel-lt The upstream changelog: https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.0.94 The following files are currently syncing to the mirrors: EL5: x86 kernel-lt-3.0.94-1.el5.elrepo.i686.rpm kernel-lt-devel-3.0.94-1.el5.elrepo.i686.rpm kernel-lt-doc-3.0.94-1.el5.elrepo.noarch.rpm kernel-lt-headers-3.0.94-1.el5.elrepo.i386.rpm kernel-lt-PAE-3.0.94-1.el5.elrepo.i686.rpm kernel-lt-PAE-devel-3.0.94-1.el5.elrepo.i686.rpm x86_64 kernel-lt-3.0.94-1.el5.elrepo.x86_64.rpm kernel-lt-devel-3.0.94-1.el5.elrepo.x86_64.rpm kernel-lt-doc-3.0.94-1.el5.elrepo.noarch.rpm kernel-lt-headers-3.0.94-1.el5.elrepo.x86_64.rpm src kernel-lt-3.0.94-1.el5.elrepo.nosrc.rpm EL6: x86 kernel-lt-3.0.94-1.el6.elrepo.i686.rpm kernel-lt-devel-3.0.94-1.el6.elrepo.i686.rpm kernel-lt-doc-3.0.94-1.el6.elrepo.noarch.rpm kernel-lt-firmware-3.0.94-1.el6.elrepo.noarch.rpm kernel-lt-headers-3.0.94-1.el6.elrepo.i386.rpm kernel-lt-NONPAE-3.0.94-1.el6.elrepo.i686.rpm kernel-lt-NONPAE-devel-3.0.94-1.el6.elrepo.i686.rpm perf-3.0.94-1.el6.elrepo.i686.rpm x86_64 kernel-lt-3.0.94-1.el6.elrepo.x86_64.rpm kernel-lt-devel-3.0.94-1.el6.elrepo.x86_64.rpm kernel-lt-doc-3.0.94-1.el6.elrepo.noarch.rpm kernel-lt-firmware-3.0.94-1.el6.elrepo.noarch.rpm kernel-lt-headers-3.0.94-1.el6.elrepo.x86_64.rpm perf-3.0.94-1.el6.elrepo.x86_64.rpm src kernel-lt-3.0.94-1.el6.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 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 kernels and, as such, they may be installed and updated alongside the regular kernel. The kernel configuration is based upon a default RHEL 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] http://bugzilla.kernel.org/ [2] http://elrepo.org/bugs/ ___ elrepo mailing list elrepo@lists.elrepo.org http://lists.elrepo.org/mailman/listinfo/elrepo
Re: [elrepo] Questions about rebuilding kmod-nvidia RPM for new kernel
On 08/29/2013 01:56 PM, Akemi Yagi wrote: Take a look at the spec file from kmod-nvidia. Basically you want to remove any reference to kmodtool (Source10). Remove those lines, remove the lines that refer to depmod.d. If you are stuck, let us know what error(s) you get. Akemi Thanks a lot everyone, this allowed me to finally get this working! I just added a %files section to grab the nvidia.ko file and a depmod after install. Rob ___ elrepo mailing list elrepo@lists.elrepo.org http://lists.elrepo.org/mailman/listinfo/elrepo
Re: [elrepo] Questions about rebuilding kmod-nvidia RPM for new kernel
On Thu, Aug 29, 2013 at 1:23 PM, Rob Spearman wrote: > I was hoping for something more elegant than just doing a manual install and > then copying over to my own RPM. No spec files out there that are not kabi > constrained? Take a look at the spec file from kmod-nvidia. Basically you want to remove any reference to kmodtool (Source10). Remove those lines, remove the lines that refer to depmod.d. If you are stuck, let us know what error(s) you get. Akemi ___ elrepo mailing list elrepo@lists.elrepo.org http://lists.elrepo.org/mailman/listinfo/elrepo
Re: [elrepo] Questions about rebuilding kmod-nvidia RPM for new kernel
Thanks for the quick replies. I did see the mainline kernel packages, but as you say it doesn't help with packaging the nvidia module. I am not using REHL kernels at all, just need an RPM based way to distribute the nvidia drivers. I was hoping for something more elegant than just doing a manual install and then copying over to my own RPM. No spec files out there that are not kabi constrained? Thanks, Rob ___ elrepo mailing list elrepo@lists.elrepo.org http://lists.elrepo.org/mailman/listinfo/elrepo
Re: [elrepo] Questions about rebuilding kmod-nvidia RPM for new kernel
On 29/08/13 20:38, Phil Perry wrote: On 29/08/13 16:46, Rob Spearman wrote: I installed a 3.9.7-4 kernel on CentOS 6 (via the kernel's 'make rpm') and am running this kernel. When I try to rebuild the proprietary nvidia driver RPMs using the 319.32 src RPM from elrepo, I have a number of issues. BTW, have you seen Alan maintains a series of mainline kernel packages for EL6 here at elrepo: http://elrepo.org/tiki/kernel-ml I see the very latest mainline kernel (kernel-ml-3.10.9-1.el6.elrepo) is available: http://elrepo.org/linux/kernel/el6/x86_64/RPMS/ This doesn't help you with your nvidia issues (kmod-nvidia still won't work with these kernels), but they do provide a conveniently packaged and maintained solution (provided as is, without any warranty) for those in need of a newer kernel which can easily be installed and used alongside the regular RHEL kernels. Regards, Phil ___ elrepo mailing list elrepo@lists.elrepo.org http://lists.elrepo.org/mailman/listinfo/elrepo
Re: [elrepo] Questions about rebuilding kmod-nvidia RPM for new kernel
On 29/08/13 16:46, Rob Spearman wrote: I installed a 3.9.7-4 kernel on CentOS 6 (via the kernel's 'make rpm') and am running this kernel. When I try to rebuild the proprietary nvidia driver RPMs using the 319.32 src RPM from elrepo, I have a number of issues. 1. I have to specify kversion as "3.9.7-4" on the rpmbuild command line. This does not match the format in the spec file, which includes repo and arch. Why the discrepancy? Full command line is: rpmbuild -bb nvidia-kmod.spec --define "kernels $(uname -r)" --define "kversion $(uname -r)" --target $(uname -m) 2. I can build the RPM, but it will not install. It complains of what looks like kabi mismatch errors. Examples: kernel(__bitmap_weight) = 0x4cbbd171 is needed by kmod-nvidia-319.32-3.el6.x86_64 kernel(__const_udelay) = 0xeae3dfd6 is needed by kmod-nvidia-319.32-3.el6.x86_64 kernel(__get_free_pages) = 0x93fca811 is needed by kmod-nvidia-319.32-3.el6.x86_64 kernel(__init_waitqueue_head) = 0x68dfc59f is needed by kmod-nvidia-319.32-3.el6.x86_64 If I install anyway, the module will not load. So it appears to be built incorrectly but I can not determine how this could be happening. I can easily install the same nvidia driver version through the nvidia .run process, so it is not an nvidia problem. Shouldn't this process work? Any suggestions? Thanks, Rob Our 'kmod' drivers are somewhat special RPM packages that package and deliver kernel modules (kmods) that track the kABI of the RHEL kernel. They are not intended nor will they work with non-RHEL kernels. As hinted in the SPEC file, the "magic" is hidden in the kmodtool script. Hence it's rather pointless trying to rebuild our kmod packages against a non-RHEL kernel. The main advantage of a kmod package for providing a kernel module is that the module will seamlessly work against further RHEL kernel updates bacause RHEL uses a stable kABI in their kernels hence you don't need to recompile the module for each new kernel. If you are using a non-RHEL kernel then there is no escaping the fact that the module will need to be build against each kernel. If you are not likely to update your kernel often then this is not such an issue, but if you do then you might want to look at other options such as DKMS-based solutions that automatically rebuild the module against each new kernel for you. You can certainly use our packages as a base for developing your own packages if you wish. You could use the existing nvidia-x11-drv package and you would probably only need to tweak the RPM scripts; it would probably be easier to throw away kmod-nvidia and write a regular RPM package from scratch to prep, build and install the kernel module. However, unless you are an experienced packager I would suggest the nvidia installer which, although a far from perfect solution, is probably your easiest option (have a good read of the NVIDIA documentation if you go this route). One question, which could potentially complicate issues - are you planning on mixing booting of RHEL and non-RHEL kernels? Regards, Phil ___ elrepo mailing list elrepo@lists.elrepo.org http://lists.elrepo.org/mailman/listinfo/elrepo
[elrepo] Questions about rebuilding kmod-nvidia RPM for new kernel
I installed a 3.9.7-4 kernel on CentOS 6 (via the kernel's 'make rpm') and am running this kernel. When I try to rebuild the proprietary nvidia driver RPMs using the 319.32 src RPM from elrepo, I have a number of issues. 1. I have to specify kversion as "3.9.7-4" on the rpmbuild command line. This does not match the format in the spec file, which includes repo and arch. Why the discrepancy? Full command line is: rpmbuild -bb nvidia-kmod.spec --define "kernels $(uname -r)" --define "kversion $(uname -r)" --target $(uname -m) 2. I can build the RPM, but it will not install. It complains of what looks like kabi mismatch errors. Examples: kernel(__bitmap_weight) = 0x4cbbd171 is needed by kmod-nvidia-319.32-3.el6.x86_64 kernel(__const_udelay) = 0xeae3dfd6 is needed by kmod-nvidia-319.32-3.el6.x86_64 kernel(__get_free_pages) = 0x93fca811 is needed by kmod-nvidia-319.32-3.el6.x86_64 kernel(__init_waitqueue_head) = 0x68dfc59f is needed by kmod-nvidia-319.32-3.el6.x86_64 If I install anyway, the module will not load. So it appears to be built incorrectly but I can not determine how this could be happening. I can easily install the same nvidia driver version through the nvidia .run process, so it is not an nvidia problem. Shouldn't this process work? Any suggestions? Thanks, Rob ___ elrepo mailing list elrepo@lists.elrepo.org http://lists.elrepo.org/mailman/listinfo/elrepo
