Messages in this thread | | | Subject | Re: [PATCH] hwmon/coretemp: Fix a broken error path - microcode update fix | From | Soeren Sonnenburg <> | Date | Thu, 21 Jun 2007 23:55:16 +0200 |
| |
On Thu, 2007-06-21 at 22:57 +0200, Rudolf Marek wrote: > Hello Soeren, > > Sorry for the delay. > > I'm ccing all lists maybe some other people are interested. There is known > errata AE18 which prevents coretemp from working correctly on some mobile Core > processors (family 6 model e). My driver refuses to load and now thanks to > soeren will not crash ;) However what to do when no microcode update (no new > BIOS) is available? > > Soeren pointed at some T60, T60p BIOS update and luckily, there is a easy way > how to extract the microcode update and even convert it into the .txt format as > microcode update utility (http://www.urbanmyth.org/microcode/) expects. > Attached scripts generates the mcode.txt file which may be used by the update > utility. Please can you give a try?
great! it works:
sensors excerpt :
coretemp-isa-0000 Adapter: ISA adapter temp1: +62°C (high = +100°C)
coretemp-isa-0001 Adapter: ISA adapter temp1: +64°C (high = +100°C)
> It seems that there is microcode update for CPUID 06E8 version 0x39 just as my > driver is checking. So if your CPUID is 06e8 too you should get the coretemp > driver working.
how do I find that out ? I mean sensors seem to work but how do I know which CPUID+version I have ?
> If so I will post a patch and document the script in documentation directory (or > at least some general instructions how to do that) > > Please tell me your stepping: > cat /proc/cpuinfo | grep stepping
$ cat /proc/cpuinfo | grep stepping stepping : 8 stepping : 8
Thank you *very* much! Soeren -- Sometimes, there's a moment as you're waking, when you become aware of the real world around you, but you're still dreaming. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |