Comment 30 for bug 296478

well this is really silly from a stable sort of release that has been tested for months.
my uname -r is 2.6.31-14-generic I have this issue and further more on jaunty kernel 2.6.28-16 modprobe coretemp worked perfectly after I replaced sensors-detect in /usr/sbin/ with this file http://www.lm-sensors.org/svn/lm-sensors/trunk/prog/detect/sensors-detect chmod 755 this file and added a prepatched coretemp.ko from http://mabene.icomedias.com/coretemp.ko and place it in its path which varies on kernel name but is in my instance /lib/modules/2.6.31-14-generic/kernel/drivers/hwmon/ obviously I renamed the existing files by doing e.g. filename.extension-orig.

when I do # modprobe coretemp or # modprobe -v coretemp I get a silly error FATAL: Error inserting coretemp (/lib/modules/2.6.31-14-generic/kernel/drivers/hwmon/coretemp.ko): Invalid module format

this procedure worked fine in jaunty kernels with no issues and all my cpu temps were posted when doing # sensors

makes anyone wonder if bug reports are addressed or even read in some cases. silly bugs are allowed to travel down for years without being fixed in some cases.

ok I get it its all free and ppl do it in their spare time they have families/jobs/live like most of us do well I do anywho... just dont get it why this is reported and not fixed. or when ppl just add it as a duplicate of e.g. bug #1524614 and so sometimes even having dozens of 'duplicate' bugs that when u read have nothing in relation in the majority of cases. As a obvious result it gets ignored. So much for karmic im back to jaunty. Since Karmic as more kernel issues then I care to spend weeks fixing.