If I recall correctly, I had this same problem with madwifi on my machines, and it's not a bug in dkms at all, it's cargo-culting a broken dkms.conf (which I did as well). Fixing your dkms.conf like so will make it actually build for the version you requested, rather than the running version:
If I recall correctly, I had this same problem with madwifi on my machines, and it's not a bug in dkms at all, it's cargo-culting a broken dkms.conf (which I did as well). Fixing your dkms.conf like so will make it actually build for the version you requested, rather than the running version:
--- dkms_source_ tree/dkms. conf 2012-02-07 02:56:37.000000000 +0000 0.9.4/dkms. conf 2010-12-04 22:33:11.000000000 +0000 MODULE_ NAME[13] ="ath_rate_ onoe" MODULE_ LOCATION[ 13]="ath_ rate/onoe" LOCATION[ 13]="/kernel/ drivers/ net/wireless" /lib/modules/ $kernelver" /lib/modules/ $kernelver/ build"
+++ madwifi-
@@ -43,5 +43,5 @@
BUILT_
BUILT_
DEST_MODULE_
-MAKE[0]="make modules KERNDIR=
+MAKE[0]="make modules KERNELPATH=
AUTOINSTALL="yes"