David Hubbard wrote: > Hi Rick, > > Next week I'm going to be out of town. I'm the one who should be > figuring this out, but I'm going to pass the buck (at least until the > 26th). To Jean and Rudolf: what's the next step in debugging this one? > > David Hi David, Thanks for the support Hans de Goede responded to me off list suggesting that, in fact, I probably have a abituguru ver3 chip, not a w83627ehf chip afterall. The problem is that this ver3 abituguru chip is not fully supported by sensors, libsensors, etc. However, he did point me to a userspace utility he wrote that I was able to use to successfully interrogate my uGuru chip. All along I knew this board probably used a uGuru setup. I will forward those messages back to the list under this thread for others' benefit. On the other hand, the problem that lm_sensors still has is that it was the sensors-detect script that originally reported that I had a w83627ehf chip and ultimately led me down this path. Hans suggested this is not a correct identification job and that sensors-detect should be fixed. Correspondence with Hans to follow. Thanks again, Rick (David, sorry you received this post twice) > > On 2/13/07, Rick Wright <riwright at vt.edu> wrote: > >> No, dividers did not change. Fans 1-4 are 128, fan 5 is 8. Note, this >> is the same as below. >> >> However, before adding the "set fan' commands in the sensors.conf file >> and issuing "sensors -s" (as root), I recall running "sensors" >> repeatedly would output different divider values. For example (from >> memory), the on first issue of "sensors" I would get all dividers=8, >> immediately issuing "sensors" again might give all dividers (maybe all >> but #5?) 16. Then 32. Then 64. Then all subsequent "sensors" command >> would top out the dividers at the 128 value seen below. Is this >> expected behavior? It seems that implementing your "set fanX_min" >> commands has eliminated the "climbing divider values". >> >> Thanks for the support, >> Rick >> >> >> David Hubbard wrote: >> >> > Hi Rick, >> > >> > Did the dividers change? In your previous email, they are all 128. >> > >> > David >> > >> > On 2/13/07, Rick Wright <riwright at vt.edu> wrote: >> > >> >> David, >> >> >> >> Thanks for the advice. Tried the set fanX_min 0 commands below. >> There >> >> was no change in behavior. All fan RPM's still reported as 0. Any >> >> other ideas? >> >> >> >> Thanks, >> >> Rick >> >> >> >> David Hubbard wrote: >> >> >> >> > Hi Rick, >> >> > >> >> > The 0 RPM fan speeds are probably due to the minimum fan speed >> limits >> >> > for triggering the alarms. To be brief, add something like this to >> >> > your sensors.conf: >> >> > >> >> > set fan1_min 0 >> >> > set fan2_min 0 >> >> > set fan3_min 0 >> >> > set fan4_min 0 >> >> > set fan5_min 0 >> >> > >> >> > (Note that after you do this, you have changed what will trigger an >> >> > alarm. You should check that your system does not overheat.) >> >> > >> >> > This should get the driver to look "low enough" to find your fan >> RPM. >> >> > You can then modify sensors.conf to have a reasonable minimum >> for your >> >> > fans, or possible even ignore alarms generated by your fans. >> >> > >> >> > Hope that helps, >> >> > David >> >> > >> >> > On 2/12/07, Rick Wright <riwright at vt.edu> wrote: >> >> > >> >> >> Rick Wright wrote: >> >> >> >> >> >> >Hello list, >> >> >> > >> >> >> >I have the Abit AT8 mobo described in the subject line and I'm >> >> >> trying to >> >> >> >get lm_sensors working properly for this board. I see there is >> >> still >> >> >> >very recent activity concerning getting this Winbond chip fully >> >> >> >supported. In the latest 2.10.2 release I see Dave Platt added >> >> these >> >> >> >changes relavent to my board: >> >> >> > >> >> >> >Program sensord: >> >> >> > Add w83627ehf voltage support (Dave >> Platt) >> >> >> > Add k8temp support (Dave Platt) >> >> >> > >> >> >> >These additions appear to be working properly OOTB as the >> "sensors" >> >> >> >command produces the following output: >> >> >> > >> >> >> >[riwright at box ~]$ sensors >> >> >> >k8temp-pci-00c3 >> >> >> >Adapter: PCI adapter >> >> >> >Core0 Temp: >> >> >> > +45 ?C >> >> >> >Core1 Temp: >> >> >> > +46 ?C >> >> >> > >> >> >> >w83627ehf-isa-0290 >> >> >> >Adapter: ISA adapter >> >> >> >VCore: +2.04 V (min = +0.00 V, max = +1.74 V) ALARM >> >> >> >in1: +13.46 V (min = +13.46 V, max = +12.36 V) ALARM >> >> >> >AVCC: +3.22 V (min = +3.02 V, max = +4.08 V) >> >> >> >3VCC: +3.22 V (min = +3.92 V, max = +3.82 V) ALARM >> >> >> >in4: +1.66 V (min = +2.01 V, max = +1.01 V) ALARM >> >> >> >in5: +1.66 V (min = +1.16 V, max = +0.95 V) ALARM >> >> >> >in6: +5.32 V (min = +6.53 V, max = +6.32 V) ALARM >> >> >> >VSB: +3.07 V (min = +4.08 V, max = +3.06 V) ALARM >> >> >> >VBAT: +2.16 V (min = +2.02 V, max = +2.38 V) >> >> >> >in9: +1.56 V (min = +1.98 V, max = +1.75 V) ALARM >> >> >> >Case Fan: 0 RPM (min = 1318 RPM, div = 128) ALARM >> >> >> >CPU Fan: 0 RPM (min = 1757 RPM, div = 128) ALARM >> >> >> >Aux Fan: 0 RPM (min = 10546 RPM, div = 128) ALARM >> >> >> >fan4: 0 RPM (min = 10546 RPM, div = 128) ALARM >> >> >> >fan5: 0 RPM (min = 168750 RPM, div = 8) ALARM >> >> >> >Sys Temp: -48 ?C (high = +45 ?C, hyst = +40 ?C) >> >> >> >CPU Temp: -48.0 ?C (high = +45.0 ?C, hyst = +40.0 ?C) >> >> >> >AUX Temp: -48.0 ?C (high = +80.0 ?C, hyst = +75.0 ?C) >> >> >> > >> >> >> > >> >> >> >So, as advertized, the Voltage support seems to be working. >> >> However, >> >> >> >the fan speeds and temperatures do not. Are these items >> currently >> >> >> >supported yet? Or do I have a configuration problem? If not yet >> >> >> >supported, is this planned for the future? >> >> >> > >> >> >> >Any input/hints/pointers greatly appreciated. >> >> >> > >> >> >> >Thanks, >> >> >> >Rick >> >> >> > >> >> >> >_______________________________________________ >> >> >> >lm-sensors mailing list >> >> >> >lm-sensors at lm-sensors.org >> >> >> >http://lists.lm-sensors.org/mailman/listinfo/lm-sensors >> >> >> > >> >> >> > >> >> >> > >> >> >> >> >> >> >> >> >> _______________________________________________ >> >> >> lm-sensors mailing list >> >> >> lm-sensors at lm-sensors.org >> >> >> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors >> >> >> >> >> > >> >> >> > >> >
