I sent you an email a week ago about support and you said soon. I was just wondering can you post a beta. If not its cool, but many ppl would benefit as alot of ppl's bios cannot detect the correct temp.

Yes, I said soon. I've been working and was very busy lately.
I'm working on the final release as we speak.
Current version might not show the proper model number and platform, but the temps it reports should still be accurate (at least by DTS).

I did try and it was reporting temps really low.

Yes, you're not the only one who is reporting a very low temperature.
I have no idea why this happens as the way that the DTS is read in the Brisbane is the same as in the older CPUs. There is not offset field either.
I will try to contact AMD and will see what they have to say about it.

Ok good to know. I really want to know what my true temps are. Bios says 70C+ but its 100% stable at 2850MHZ, but core temps reads 26/36 full load. I am guess its in the low to mid 50's with Orthos

if the bios is reading about 70C that is about right. I mean 100 percent accurate but its gonna be in the +-5C(for extremes)

Hate to break it to you, buts its not. At stock speeds on a good heatsink temps are over 60+ in the bios. Its not right and its probably due to the 65nm changes.

Does the new release include full support for Brisbane 65nm chips?

Yes

I've just tested my Brisbane X2 3600+ (rev G), and core temp shows temperatures of around 0 to 5 C. So it doesn't work for me...

AMD reported that the DTS in Brisbane is broken.

Damn, that is a shame, but at least I am glad there is a logical explanation behind the low temps.

Do you know by any chance that the DTS is completely broken or is a work-around possible?

I don't think there is a workaround for this. There is only one way to get the CPU temperature.

Actually I think there are two ways, the old thermal diode and the new DTS. The old thermal diode is still there, but it seems to read about 10C too low.