dkms + megaraid_sas and kernel update

[Rainer Traut]

I'm afraid dkms-2.0.19 does not solve the problem.

Rainer Traut schrieb:
> Matt Domsch schrieb:
>> On Thu, May 15, 2008 at 02:15:39PM +0200, Rainer Traut wrote:
>>> After a kernel update from 2.6.18-53.1.14.el5 to 2.6.18-53.1.19.el5
>>> I see that none of my dkms installed drivers are used by the new kernel:
> 
>> Would you mind installing
>> http://linux.dell.com/dkms/dkms-2.0.19-1.noarch.rpm, and manually
>> fixing up dkms's database the way you want (e.g. dkms
>> install/uninstall commands)?  On next kernel upgrade it
>> should work as expected...
> 
> Ok, thank you.
> I go trying the rpmforge 2.0.19-2.el5.rf because I have good experience 
> with this repo. Hope this is fine.

I uninstalled completely for testing dkms V2.0.19:
bnx2, megaraid_sas, tg3, dkms2017, kernel-2.6.18-53.1.19.el5 + headers + 
devel

I reverted back to kernel 2.6.18-53.1.14.el5 + headers + devel.

Then I did:

# yum -y install bnx2 megaraid_sas tg3
...
Dependencies Resolved

Installing:
  bnx2                    noarch     1.7.1c-3.3dkms   dell-hardware-auto 
  2.5 M
  megaraid_sas            noarch     v00.00.03.16-1   dell-hardware-auto 
  3.7 M
  tg3                     noarch     3.81c-1.3dkms    dell-hardware-auto 
  1.0 M
Installing for dependencies:
  dkms                    noarch     2.0.19-2.el5.rf  xxx               58 k

Which all build fine and after reboot all is fine:

# 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.14.el5, x86_64: installed (original_module exists)
tg3, 3.81c, 2.6.18-53.1.14.el5, x86_64: installed (original_module exists)

I then yum updated the kernel to 2.6.18-53.1.19.el5 incl headers and 
devel packet and ended up with the same problems:

# 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.14.el5, x86_64: installed (original_module exists)
tg3, 3.81c, 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-weak from 
2.6.18-53.1.14.el5
bnx2, 1.7.1c, 2.6.18-53.1.19.el5, x86_64: installed-weak from 
2.6.18-53.1.14.el5
megaraid_sas, v00.00.03.16, 2.6.18-53.1.19.el5, x86_64: installed-weak 
from 2.6.18-53.1.14.el5

  # dmesg |grep mega
megasas: 00.00.03.10 Wed Mar 28 10:25:52 PST 2007
megasas: 0x1000:0x0060:0x1028:0x1f0c: bus 1:slot 0:func 0
megasas: FW now in Ready state
# dmesg |grep bnx
Broadcom NetXtreme II Gigabit Ethernet Driver bnx2 v1.5.11-rh (June 4, 2007)
bnx2: eth0: using MSI
bnx2: eth0 NIC Link is Up, 100 Mbps full duplex, receive & transmit flow 
control ON
bnx2: eth1: using MSI
bnx2: eth1 NIC Link is Up, 1000 Mbps full duplex, receive & transmit 
flow control ON

# find /lib/modules/ -name bnx2*
/lib/modules/2.6.18-53.1.19.el5/weak-updates/bnx2.ko
/lib/modules/2.6.18-53.1.19.el5/kernel/drivers/net/bnx2.ko
/lib/modules/2.6.18-53.1.14.el5/extra/bnx2.ko

# ll /lib/modules/2.6.18-53.1.19.el5/weak-updates/
insgesamt 0
lrwxrwxrwx 1 root root 45 16. Mai 10:03 bnx2.ko -> 
/lib/modules/2.6.18-53.1.14.el5/extra/bnx2.ko
lrwxrwxrwx 1 root root 45 16. Mai 10:03 cnic.ko -> 
/lib/modules/2.6.18-53.1.14.el5/extra/cnic.ko
lrwxrwxrwx 1 root root 53 16. Mai 10:03 megaraid_sas.ko -> 
/lib/modules/2.6.18-53.1.14.el5/extra/megaraid_sas.ko
lrwxrwxrwx 1 root root 44 16. Mai 10:03 tg3.ko -> 
/lib/modules/2.6.18-53.1.14.el5/extra/tg3.ko

So what is the weak-updates stuff if it is not used?
And what happens if it is used and a later kernel update removes the 
/lib/modules/2.6.18-53.1.14.el5/ directory?
And why is it not working? :)

Thx
Rainer