** Attachment added: "linux-image.apport" http://launchpadlibrarian.net/35849216/linux-image.apport
** Description changed: This HAPPENS WITH ANY KARMIC KERNEL EVEN 2.6.31.1 ProblemType: Bug Well this is really silly from a stable supposedly release that has been tested for months. AND has been reported FIXED on Bug #296478 I'm here to tell you its not fixed, does not work, period. uname -r is 2.6.31-15-generic ____ KARMIC KOALA 9.10 I have tried this with default files as system is installed with minimal karmic install I get error FATAL: Error inserting coretemp (/lib/modules/2.6.31-15-generic/kernel/drivers/hwmon/coretemp.ko): Invalid module format and I have tried it with the description below. FATAL ERRORS EXIST. dmesg outputs this [ 4563.803572] coretemp: no symbol version for module_layout WTH?? 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 pre-patched 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-15-generic/kernel/drivers/hwmon/ obviously I renamed the existing files by doing e.g. filename.extension-orig. JUST FOR TESTING PURPOSES. This is my sensors-detect output The modules load during that so it has to work but in no obvious way. http://pastebin.com/f2ae9c41b LM-SENSORS is Version: 1:3.1.1-4~ppa0 sensors -s outputs No sensors found! Make sure you loaded all the kernel drivers you need. Try sensors-detect to find out which these are. modprobe fails with errors as described. doing /etc/init.d/lm-sensors start or service lm-sensors start outputs * Setting sensors limits [fail] should say ok - when I do # modprobe coretemp or # modprobe -v coretemp I get the same silly error FATAL: Error inserting coretemp (/lib/modules/2.6.31-15-generic/kernel/drivers/hwmon/coretemp.ko): Invalid module format. + when I do # modprobe coretemp or # modprobe -v coretemp I get the same silly error FATAL: Error inserting coretemp (/lib/modules/2.6.31-15-generic/kernel/drivers/hwmon/coretemp.ko): Invalid module format. This worked fine in Jaunty kernels with no issues in EITHER CASE and all my CPU temps were posted when doing # sensors - I was able to load the modules recognised via sensors-detect which are coretemp, ic2-nforce2, ic2-dev I cannot load any of them in the ic2-nforce2, ic2-dev it says FATAL: Module ic2_dev not found. + Doing sensors-detect is able to see/load modules which are coretemp, ic2-nforce2, ic2-dev I cannot load any of them using modprobe ic2-nforce2, ic2-dev it says FATAL: Module ic2_dev not found. 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 #296478 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 support. The only kernel which fixes this is the 2.6.32rc7 which I have downloaded from mainline for testing. though the system is only accessible via ssh and stays at blinking cursor on machine. -- linux-image https://bugs.launchpad.net/bugs/485234 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
