Description of problem: When attepting to rebuild the kernel RPM (from the .src.rpm) the dmi_broken symbol exported from arch/i386/kernel/dmi_scan.c is not versioned, leading to unresolved symbols in the powernow-k7 module (cpufreq). Version-Release number of selected component (if applicable): 2.4.22-1.2140 (but also previous releases) How reproducible: Always Additional info: I tracked the problem to the fact that the lm_sensors patch adds another file named dmi_scan.c in drivers/i2c/. Since both dmi_scan.c files export symbols the modversioning stuff picks only one, and that happens to be the i2c one (at least on my machine). I solved the problem by renaming the i2c dmi_scan.{c,h} files to i2c-dmi_scan.{c,h}. Although there is maybe a saner approach? Patch next.
Created attachment 96858 [details] Proposed patch: rename i2c dmi_scan.{c,h} to i2c-dmi_scan.{c,h} The patch is really simple, but has the drawback on renaming the module.
On a second thought, maybe it's better to upgrade the lm_sensors kernel patch? Currently is a 2.6.5, which is really old. Or is it too much work?
Later lm_sensors/i2c have the same behaviour. By coincidence I posted on the same day about this on the lm_sensors list: http://archives.andrew.net.au/lm-sensors/msg06061.html I just verified the same for FC1 2174 kernel and lm_sensors/i2c 2.8.4. BTW patched FC1 kernels with recent lm_sensors/i2c support and the matching lm_snesors userland bits can be found at ATrpms.net at the cost of breaking powernow-k7.o
*** This bug has been marked as a duplicate of 126342 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.