alabamas, on Apr 27 2010, 03:41 PM, said:
TJmax of the atom n270 is 90 °C .this is the right tj on fake smc and you will get the same temps you get with RealTemp on windows.
hope it helps
I checked the value for Tjmax for my N280's fakesmc.kext and it was 100ºC.
LeMaurien19, on Apr 27 2010, 07:25 PM, said:
HF5RC3 is basically HF4 with the addition of only VoodooHDA v2.6.1. So we get an experience closer to HF4 but with better more stable audio courtesy of VoodooHDA.
The main reason for HF5 is help people get updated to 10.6.3 - the more immediate concern as of now
Meanwhile, we'll continue polishing our new kexts - ensuring that they're not buggy etc. and researching on better ways to resolve issues (ethernet on wake, etc.) if possible and then they can then be included in HF6
Now I'd like to discuss non verbose vs verbose mode. How is that when I run verbose mode, I have resume from sleep/clamshell sleep working fine with an /EFI/Extra/Ext kextcache? And then when I boot in non verbose, with the same type of kextcache, I have a blank screen when resuming from sleep?...
And then I tried creating a /E/E/E + /S/L/E kextcache (in EFI) and booted non-verbose. Sometimes resume from sleep works ok - no blank screen, and sometimes I get a kernel panic...
(*This is hibernatemode 0)
I just wanna understand more how things work. what's the magic behind verbose mode?
I regularly boot in non-verbose mode which seems to work OK. I've rarely had any problems so it's difficult to know if they were even the result of booting non-verbose.
I do not use any other cache than the normal one required for the /E/E folder - Extensions.mkext. There's really no need to create a cache for /S/L/E as OS X does that. OS X will automatically re-cache if the S/L/E folder has changed since last startup. The process is done either during shutdown prior to restart or after the restart or both.
I think any problems with sleep or SpeedStep are mainly caused by where SleepEnabler.kext and VooDooPowerMini.kext are placed. My experience tends to suggest they work more reliably when put in S/L/E rather than /E/E.
That said they are presently in the /E/E location where HF5RC3 puts them.
As an aside, perhaps the installer should check S/L/E for duplicates of the kexts normally placed in /E/E by the installer. This is a safety precaution in case the user has installed one or more of the needed kexts in /S/L/E. For example I had SleepEnabler and two VooDoo kexts in /S/L/E that needed to be deleted because the installer was putting them in /E/E. Just a thought as this isn't anything urgent or essential.