wt/lm-sensors
1
0 Fork 0
mirror of https://github.com/lm-sensors/lm-sensors.git synced 2026-10-31 13:10:30 +00:00
Code Issues Packages Projects Releases Wiki Activity

add module versioning problem help from Frodo

Browse Source 
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@1215 7894878c-1315-0410-8ee3-d5d059ff63e0
This commit is contained in:
Mark D. Studebaker committed 2001-10-31 03:52:05 +00:00
1 parent 3bd1ad7dbd
commit c38697046a
1 file changed
+30 -1
Download Patch File Download Diff File Expand all files Collapse all files
doc/FAQ
+30 -1
View File
@@ -40,6 +40,7 @@ CONTENTS
3.6A 'No rule to make target xxxx needed by xxxx' - how to fix?
3.7 It still does not compile or patch
3.8 'make install' fails on Mandrake kernels
3.9 I get unresolved symbols when I modprobe modules (Red Hat especially)
4. Problems
4.1 Why do my fans report exactly half/double their values by your code
@@ -419,6 +420,34 @@ patches first!
Edit our Makefile on the 'MODDIR :=' line to hard-code the module directory.
3.9 I get unresolved symbols when I modprobe modules (Red Hat especially)
Example:
*** Unresolved symbols in /lib/modules/2.4.5/kernel/drivers/i2c/i2c-i810.o
i2c_bit_add_bus_R8c3bc60e
i2c_bit_del_bus_R92b18f49
You can also run 'depmod -a -e' to see all unresolved symbols.
These are module versioning problems. Generally you did not compile
against the kernel you are running. Sometimes the Red Hat source you
have is not for the kernel you are running.
You must compile our package against the source for the kernel you
are running with something like 'make LINUX=/usr/src/linux-2.4.14'.
Try the following to be sure:
* nm --extern MODULE.o
Filter out the kernel symbols, like kmalloc, printk etc. and note the
number code behind them, like printk_R1b7d4074. If there is no numeric
code after them, note this too.
* grep SYMBOL /proc/ksyms
Substitute SYMBOL by the basename of the symbols above, like kmalloc,
printk etc. Note the number code behind them, or the lack thereof.
* Compare both sets of symbols. Are they the same? If so, the problem
lies somewhere else. Are they different? If so, you have a module
versioning problem.
4 Problems
----------
@@ -1009,7 +1038,7 @@ can not be sure.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
Rev 2.4 (MDS) Minor updates 20010929
Rev 2.4 (MDS) Minor updates 20011030
Rev 2.4 (MDS) Minor updates 20010722
Rev 2.3 (MDS) General update, 20010224, released with lm_sensors 2.6.0.
Rev 2.2 (Frodo) Corrections for lm_sensors 2.4, 19990920