dkms + megaraid_sas and kernel update

Rainer Traut tr.ml at gmx.de
Fri May 16 09:12:10 CDT 2008


Matt Domsch schrieb:
>> And why is it not working? :)
> 
> What's not working about this now?  Your initrd-2.6.18-53.1.19.el5.img
> should have the v00.00.03.16 driver in it now.  No?

No.
All of my dkms built modules are not used with the new kernel.

Correct me if I'm wrong but because of this file:

/etc/depmod.d/depmod.conf.dist

-
# override default search ordering for kmod packaging
search updates extra built-in weak-updates
-

No module from weak-updates which has a redhat counterpart is used 
because built-in modules have precendence.

And more fun:
After deleting the symlinks from weak-updates the dkms-autoinstaller 
builds the drivers and places them to the extras dir. Good.
But it omits megaraid_sas. :(

# dkms status
megaraid_sas, v00.00.03.16, 2.6.18-53.1.14.el5, x86_64: installed 
(original_module exists)
bnx2, 1.7.1c, 2.6.18-53.1.19.el5, x86_64: installed (original_module exists)
bnx2, 1.7.1c, 2.6.18-53.1.14.el5, x86_64: installed (original_module exists)
tg3, 3.81c, 2.6.18-53.1.19.el5, x86_64: installed (original_module exists)
tg3, 3.81c, 2.6.18-53.1.14.el5, x86_64: installed (original_module exists)

Not until dkms build and install it appeared.
Kinda hard to do this after every kernel update? :)

Thx
Rainer



More information about the Linux-PowerEdge mailing list