[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
Hello Cosmin: * Cosmin Nicolaescu <cos@camelot.homelinux.com> [2005年04月20日 10:53:02 -0400]: > I just purchased a new motherboard, an Abit AI7. The specs look really > good, I've read about the 'wonders' it can do with sensors that have > little to no support in Linux, and with a couple of exceptions it works > fine. Perhaps someone else has this motherboard and/or experienced similar > problems. > > 1. The motherboard, as well as the P4 processor are HT capable. I have > configured SMP and HT capabilities in the kernel, yet I do not have HT. > Why? Not *all* P4s are HT capable. (e.g. my older 1.8GHz Northwood) Is 'ht' included among the flags in /proc/cpuinfo ? > 2. acpi ALWAYS prints out 20C (68F). The BIOS utility has nice sensor > printouts, so the sensors _do_ work. It can read data from the bios, > because the alarms change in /proc as I change them in the BIOS. Why can't > I read the real temperature, and where is acpi reading the 20/68 > temperature?? I can't help you much w/ ACPI temps, sorry. > Another, not-so-urgent question was if anyone get lm-sensors to actually > work with the built-in sensors? After loading the proper modules I receive > the following information, which is pretty much _all_ wrong: One of my machines uses the same driver (w83627hf). It works OK for me. What version of lm_sensors? What kernel version? > root@camelot root # sensors > w83627hf-isa-0290 > Adapter: ISA adapter > VCore 1: +4.08 V (min = +4.08 V, max = +4.08 V) ALARM (beep) > VCore 2: +4.08 V (min = +4.08 V, max = +4.08 V) ALARM (beep) > +3.3V: +4.08 V (min = +4.08 V, max = +4.08 V) ALARM (beep) > +5V: +6.85 V (min = +6.85 V, max = +6.85 V) ALARM (beep) > +12V: +15.50 V (min = +15.50 V, max = +15.50 V) ALARM (beep) > - - - -12V: +6.06 V (min = +6.06 V, max = +6.06 V) ALARM (beep) > - - - -5V: +5.10 V (min = +5.10 V, max = +5.10 V) ALARM (beep) > V5SB: +6.85 V (min = +6.85 V, max = +6.85 V) ALARM (beep) > VBat: +4.08 V (min = +4.08 V, max = +4.08 V) ALARM (beep) Hmmm, it almost looks like the sensor chip is not there... notice all the voltage readings are at the top end of their scales. I bet the chip is responding with all 0xff. Try this as root: 'isadump 0x295 0x296' (very small chance it could crash the machine, sorry) and send me the results. > fan1: 0 RPM (min = 0 RPM, div = 128) ALARM (beep) > fan2: 0 RPM (min = 0 RPM, div = 128) ALARM (beep) > fan3: 0 RPM (min = 0 RPM, div = 128) ALARM (beep) > temp1: -1 C (high = -1 C, hyst = -1 C) sensor = PII/Celeron diode ALARM > (beep) > temp2: +0.0 C (high = +0 C, hyst = +0 C) sensor = PII/Celeron diode ALARM > (beep) > temp3: +0.0 C (high = +0 C, hyst = +0 C) sensor = PII/Celeron diode ALARM > (beep) > ERROR: Can't get VID data! The (VID error) indicates a probable mismatch between lm_sensors version and kernel version. See here: http://secure.netroedge.com/~lm78/kernel26.html (about halfway down) That could be *a* problem, but that's not the whole problem. > alarms: Chassis intrusion detection ALARM > beep_enable: > Sound alarm enabled Also, did you run sensors-detect? Did it identify anything else besides the w83627hf? Can you find the w83627hf on the board, physically? It's roughly postage-stamp sized, and it says "Winbond" on it. Finally, some of the (other) developers hang out on #linux-sensors on freenode. Also, the lm_sensors mailing list is open (no need to subscribe) sensors AT stimpy DOT netroedge DOT com I hope this helps; regards, -- Mark M. Hoffman mhoffman@lightlink.com ___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug