Description of problem: As there are no kernel-devel RPMs for the PAE kernels, one gets dangling symlinks in the module directories. Version-Release number of selected component (if applicable): Seems to affect all PAE kernel RPMs. How to reproduce: # symlinks /lib/modules/*PAE*/ dangling: /lib/modules/2.6.18-128.1.10.el5PAE/build -> ../../../usr/src/kernels/2.6.18-128.1.10.el5-PAE-i686 dangling: /lib/modules/2.6.18-128.1.10.el5PAE/source -> build dangling: /lib/modules/2.6.18-128.1.6.el5PAE/build -> ../../../usr/src/kernels/2.6.18-128.1.6.el5-PAE-i686 dangling: /lib/modules/2.6.18-128.1.6.el5PAE/source -> build dangling: /lib/modules/2.6.18-128.el5PAE/build -> ../../../usr/src/kernels/2.6.18-128.el5-PAE-i686 dangling: /lib/modules/2.6.18-128.el5PAE/source -> build This (correctly) breaks the installation of the AMD driver for my Radeon based gfx card (running 2.6.18-128.1.6.el5PAE at that moment): # rpm -Uvh /usr/src/redhat/RPMS/i386/fglrx_7_1_0-8.593-1.i386.rpm Vorbereiten... ########################################### [100%] 1:fglrx_7_1_0 ########################################### [100%] Error! Your kernel source for kernel 2.6.18-128.1.6.el5PAE cannot be found at /lib/modules/2.6.18-128.1.6.el5PAE/build or /lib/modules/2.6.18-128.1.6.el5PAE/source. Error! Invalid number of parameters passed. Usage: remove -m <module> -v <module-version> --all or: remove -m <module> -v <module-version> -k <kernel-version> DKMS part of installation failed. Please refer to /usr/share/ati/fglrx-install.log for details # cat /usr/share/ati/fglrx-install.log Creating symlink /var/lib/dkms/fglrx/8.593/source -> /usr/src/fglrx-8.593 DKMS: add Completed. You can use the --kernelsourcedir option to tell DKMS where it's located. [Error] Kernel Module : Failed to build fglrx-8.593 with DKMS [Error] Kernel Module : Removing fglrx-8.593 from DKMS [Message] Driver : End of installation
There should be kernel-PAE-devel rpms. Where did you get your kernel rpm? RHN? The devel rpm is installed separately from the normal rpm and as a side effect there are dangling symlinks until the devel rpm is installed.
Also, are you sure you're installing the "kernel-PAE-devel" RPM, and not "kernel-devel-PAE"? P.
I upgraded the system from 4.7 to 5.3 using bootable media. On 4.7 I had kernel, kernel-devel, kernel-smp, and kernel-smp-devel installed. After the upgrade there were kernel, kernel-devel and kernel-pae. But you're right Prarit, I should have looked better for the right name! Feel free to close the bug. Tnx. Concerning the dangling link, I vote for moving this symlink in the kernel-devel-PAE, so one doesn't have any dangling links after installing a proper kernel RPM.
Regarding the dangling link, the other side of the argument is that it is also ok to install a -devel package _without_ the corresponding kernel package. And so the debate has gone back and forth whether to create a dangling link or create complicated spec file logic to determine if the link should be created by the -devel package at install time if the corresponding kernel packages exists or by the kernel package if the corresponding -devel package is installed first. The simpler approach was taken; the dangling symlink.
(In reply to comment #3) > But you're right Prarit, I should have looked better for the right name! Feel > free to close the bug. Tnx. > :) I've done that myself :) Closing as NOTABUG. P.