__color__,__group__,ticket,summary,component,version,milestone,type,owner,status,created,_changetime,_description,_reporter 3,Active Tickets,2311,Support for SiS 550,hardware,2.10.1,,defect,somebody,new,2008-04-09T09:47:17+0200,2008-04-09T09:47:17+0200,"I've got a machine with SiS550 chip inside. There is note on lm-sensors site ""If you would like to help develop and test support for any of these please contact us."". I'm not a programmer, but can i help somehow to make sensors on this piece of HW supported? Some info about HW:[[BR]] It is in box called RB-262: [[BR]] http://www.xtendlan.com/product-solutions/Mini%20PC/TC-261%20(2)%20(1).aspx[[BR]] There is SiS550 chip inside (visually checked)[[BR]] There is chip W83697HG also (visually checked)[[BR]] {{{ voyage:~# sensors -v[[BR]] sensors version 2.10.1 with libsensors version 2.10.1 with latest sensors-detect downloaded from lm-sensors site. }}} {{{ voyage:~# ./sensors-detect # sensors-detect revision $Revision$ This program will help you determine which kernel modules you need to load to use lm_sensors most effectively. It is generally safe and recommended to accept the default answers to all questions, unless you know what you're doing. We can start with probing for (PCI) I2C or SMBus adapters. Do you want to probe now? (YES/no): Probing for PCI bus adapters... Sorry, no known PCI bus adapters found. If you have undetectable or unsupported I2C/SMBus adapters, you can have them scanned by manually loading the modules before running this script. We are now going to do the I2C/SMBus adapter probings. Some chips may be double detected; we choose the one with the highest confidence value in that case. If you found that the adapter hung after probing a certain address, you can specify that address to remain unprobed. Some chips are also accessible through the ISA I/O ports. We have to write to arbitrary I/O ports to probe them. This is usually safe though. Yes, you do have ISA I/O ports even if you do not have any ISA slots! Do you want to scan the ISA I/O ports? (YES/no): Probing for `National Semiconductor LM78' at 0x290... No Probing for `National Semiconductor LM78-J' at 0x290... No Probing for `National Semiconductor LM79' at 0x290... No Probing for `Winbond W83781D' at 0x290... No Probing for `Winbond W83782D' at 0x290... No Probing for `IPMI BMC KCS' at 0xca0... No Probing for `IPMI BMC SMIC' at 0xca8... No Some Super I/O chips may also contain sensors. We have to write to standard I/O ports to probe them. This is usually safe. Do you want to scan for Super I/O sensors? (YES/no): Probing for Super-I/O at 0x2e/0x2f Trying family `National Semiconductor'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Fintek'... Yes Found `Winbond W83697HF/F/HG Super IO Sensors' (but not activated) Probing for Super-I/O at 0x4e/0x4f Trying family `National Semiconductor'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Fintek'... No Trying family `ITE'... No Some south bridges, CPUs or memory controllers may also contain embedded sensors. Do you want to scan for them? (YES/no): Silicon Integrated Systems SIS5595... No VIA VT82C686 Integrated Sensors... No VIA VT8231 Integrated Sensors... No AMD K8 thermal sensors... No AMD K10 thermal sensors... No Intel Core family thermal sensor... No Intel AMB FB-DIMM thermal sensor... No Sorry, no sensors were detected. Either your sensors are not supported, or they are connected to an I2C or SMBus adapter that is not supported. See doc/FAQ, doc/lm_sensors-FAQ.html or http://www.lm-sensors.org/wiki/FAQ (FAQ #4.24.3) for further information. If you find out what chips are on your board, check http://www.lm-sensors.org/wiki/Devices for driver status. }}} ",ticket 3,Active Tickets,2348,"module c7temp shows voltage, but no temperature on HP Mini-Note 2133",kernel,3.0.2,,defect,juergh,new,2008-09-13T07:59:01+0200,2008-09-15T05:47:30+0200,"I am using the new c7temp module with lm-sensors 3.02 on my VIA C7 powered Mini-Note; but, I get a 0.0? temperature value at all times. Following is some system info: [uname, sensors, cpuid, lspci]. Please let me know how I can assist. Thanks ____________________________________________________________ {{{ Linux justin-mininote 2.6.24-19-generic #1 SMP Wed Aug 20 22:56:21 UTC 2008 i686 GNU/Linux ------------- c7temp-isa-0000 Adapter: ISA adapter in0: +0.80 V temp1: +0.0°C ------------- CPU: vendor_id = ""CentaurHauls"" version information (1/eax): processor type = primary processor (0) family = Intel Pentium Pro/II/III/Celeron, AMD Athlon/Duron, Cyrix M2, VIA C3 (6) model = 0xd (13) stepping id = 0x0 (0) extended family = 0x0 (0) extended model = 0x0 (0) (simple synth) = VIA C3 / C3-M / C7 / C7-M / Eden ESP 7000/8000/10000 (unknown model) miscellaneous (1/ebx): process local APIC physical ID = 0x0 (0) cpu count = 0x0 (0) CLFLUSH line size = 0x8 (8) brand index = 0x0 (0) brand id = 0x00 (0): unknown feature information (1/edx): x87 FPU on chip = true virtual-8086 mode enhancement = true debugging extensions = true page size extensions = true time stamp counter = true RDMSR and WRMSR support = true physical address extensions = true machine check exception = true CMPXCHG8B inst. = true APIC on chip = true SYSENTER and SYSEXIT = true memory type range registers = true PTE global bit = true machine check architecture = false conditional move/compare instruction = true page attribute table = true page size extension = false processor serial number = false CLFLUSH instruction = true debug store = false thermal monitor and clock ctrl = true MMX Technology = true FXSAVE/FXRSTOR = true SSE extensions = true SSE2 extensions = true self snoop = false hyper-threading / multi-core supported = false therm. monitor = true IA64 = false pending break event = true feature information (1/ecx): PNI/SSE3: Prescott New Instructions = true MONITOR/MWAIT = false CPL-qualified debug store = false VMX: virtual machine extensions = false Enhanced Intel SpeedStep Technology = true thermal monitor 2 = true context ID: adaptive or shared L1 data = false cmpxchg16b available = false xTPR disable = true extended processor signature (0x80000001/eax): generation = 0x0 (0) model = 0x0 (0) stepping = 0x0 (0) (simple synth) = unknown extended feature flags (0x80000001/edx): x87 FPU on chip = false virtual-8086 mode enhancement = false debugging extensions = false page size extensions = false time stamp counter = false RDMSR and WRMSR support = false physical address extensions = false machine check exception = false CMPXCHG8B inst. = false APIC on chip = false SYSCALL and SYSRET instructions = false memory type range registers = false global paging extension = false machine check architecture = false conditional move/compare instruction = false page attribute table = false page size extension = false multiprocessing capable = false AMD multimedia instruction extensions = false MMX Technology = false extended MMX = false SSE extensions = false AA-64 = false 3DNow! instruction extensions = false 3DNow! instructions = false brand = "" VIA C7-M Processor 1200MHz"" L1 TLB/cache information: 2M/4M pages & L1 TLB (0x80000005/eax): instruction # entries = 0x0 (0) instruction associativity = 0x0 (0) data # entries = 0x0 (0) data associativity = 0x0 (0) L1 TLB/cache information: 4K pages & L1 TLB (0x80000005/ebx): instruction # entries = 0x80 (128) instruction associativity = 0x8 (8) data # entries = 0x80 (128) data associativity = 0x8 (8) L1 data cache information (0x80000005/ecx): line size (bytes) = 0x40 (64) lines per tag = 0x1 (1) associativity = 0x4 (4) size (Kb) = 0x40 (64) L1 instruction cache information (0x80000005/ecx): line size (bytes) = 0x40 (64) lines per tag = 0x1 (1) associativity = 0x4 (4) size (Kb) = 0x40 (64) L2 TLB/cache information: 2M/4M pages & L2 TLB (0x80000006/eax): instruction # entries = 0x0 (0) instruction associativity = L2 off (0) data # entries = 0x0 (0) data associativity = L2 off (0) L2 TLB/cache information: 4K pages & L2 TLB (0x80000006/ebx): instruction # entries = 0x0 (0) instruction associativity = L2 off (0) data # entries = 0x0 (0) data associativity = L2 off (0) L2 unified cache information (0x80000006/ecx): line size (bytes) = 0x40 (64) lines per tag = 0x1 (1) associativity = 0xa (10) size (Kb) = 0x80 (128) 0xc0000001: eax=0x00000000 extended feature flags (0xc0000001/edx): alternate instruction set = false alternate instruction set enabled = false random number generator = true random number generator enabled = true LongHaul MSR 0000_110Ah = false FEMMS = false advanced cryptography engine (ACE) = true advanced cryptography engine (ACE)enabled = true 0xc0000002: eax=0x00000000 ebx=0x04000406 ecx=0x04060609 edx=0x41080000 0xc0000003: eax=0xfc1deab2 ebx=0xc220bebf ecx=0xd40711db edx=0xe9cfcd6a (multi-processing synth): none (synth) = VIA C3 / C3-M / C7 / C7-M / Eden ESP 7000/8000/10000 (unknown model) ------------- CPU: 0x00000000: eax=0x00000001 ebx=0x746e6543 ecx=0x736c7561 edx=0x48727561 0x00000001: eax=0x000006d0 ebx=0x00000800 ecx=0x00004181 edx=0xa7c9bbff 0x80000000: eax=0x80000006 ebx=0x00000000 ecx=0x00000000 edx=0x00000000 0x80000001: eax=0x00000000 ebx=0x00000000 ecx=0x00000000 edx=0x00100000 0x80000002: eax=0x20202020 ebx=0x20202020 ecx=0x20202020 edx=0x20202020 0x80000003: eax=0x20202020 ebx=0x41495620 ecx=0x2d374320 edx=0x7250204d 0x80000004: eax=0x7365636f ebx=0x20726f73 ecx=0x30303231 edx=0x007a484d 0x80000005: eax=0x00000000 ebx=0x08800880 ecx=0x40040140 edx=0x40040140 0x80000006: eax=0x00000000 ebx=0x00000000 ecx=0x0080a140 edx=0x00000000 0x80860000: eax=0x00000000 ebx=0x00000000 ecx=0x00000000 edx=0x00000000 0xc0000000: eax=0xc0000003 ebx=0x00000000 ecx=0x00000000 edx=0x00000000 0xc0000001: eax=0x00000000 ebx=0x00000001 ecx=0x00000000 edx=0x0000ffcc 0xc0000002: eax=0x00000000 ebx=0x04000406 ecx=0x04060609 edx=0x41080000 0xc0000003: eax=0xfc1deab2 ebx=0xc220bebf ecx=0xd40711db edx=0xe9cfcd6a ------------- 00:00.0 Host bridge: VIA Technologies, Inc. P4M900 Host Bridge 00:00.1 Host bridge: VIA Technologies, Inc. P4M900 Host Bridge 00:00.2 Host bridge: VIA Technologies, Inc. P4M900 Host Bridge 00:00.3 Host bridge: VIA Technologies, Inc. P4M900 Host Bridge 00:00.4 Host bridge: VIA Technologies, Inc. P4M900 Host Bridge 00:00.5 PIC: VIA Technologies, Inc. P4M900 I/O APIC Interrupt Controller 00:00.6 Host bridge: VIA Technologies, Inc. P4M900 Security Device 00:00.7 Host bridge: VIA Technologies, Inc. P4M900 Host Bridge 00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge 00:02.0 PCI bridge: VIA Technologies, Inc. P4M900 PCI to PCI Bridge Controller (rev 80) 00:03.0 PCI bridge: VIA Technologies, Inc. P4M900 PCI to PCI Bridge Controller (rev 80) 00:0f.0 IDE interface: VIA Technologies, Inc. Unknown device 5372 00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev b0) 00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev b0) 00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev b0) 00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 90) 00:11.0 ISA bridge: VIA Technologies, Inc. VT8237S PCI to ISA Bridge 00:11.7 Host bridge: VIA Technologies, Inc. VT8251 Ultra VLINK Controller 00:13.0 Host bridge: VIA Technologies, Inc. VT8237A Host Bridge 00:13.1 PCI bridge: VIA Technologies, Inc. VT8237A PCI to PCI Bridge 01:00.0 VGA compatible controller: VIA Technologies, Inc. Chrome9 HC IGP (rev 01) 02:00.0 Network controller: Broadcom Corporation BCM4312 802.11a/b/g (rev 02) 07:03.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5788 Gigabit Ethernet (rev 03) 80:01.0 Audio device: VIA Technologies, Inc. VIA High Definition Audio Controller (rev 10) }}} ",ticket 3,Active Tickets,2359,HP Compaq 6720s no thermal-sensor detected,hardware,3.0.3,,defect,somebody,new,2008-11-07T11:34:12+0100,2009-08-29T13:14:31+0200,"I have encountered following problem. lm-sensors version {{{ map@mp1:~$ sensors -v sensors version 3.0.2 with libsensors version 3.0.2 }}} and it's running on newest packages from ubuntu 8.10. sensors-detect failed to detect the chip under super-i/o smsc and only displaying: {{{ Do you want to scan for Super I/O sensors? (YES/no): Probing for Super-I/O at 0x2e/0x2f Trying family `National Semiconductor'... No Trying family `SMSC'... Yes Found unknown chip with ID 0x3600 Probing for Super-I/O at 0x4e/0x4f Trying family `National Semiconductor'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Fintek'... No Trying family `ITE'... No }}} It's not possible for ACPI to control the Thermal-Zone correctly. I've read, that i should use ""cpqhealth"" in the FAQs on this site. But how should i do that? I would be glad, if somebody could help me out a bit. regards ",ticket 3,Active Tickets,2372,Make fancontrol safer on kernel panic,fancontrol,3.0.3,,defect,somebody,new,2009-03-05T16:32:35+0100,2010-01-20T11:09:01+0100,"It was reported that hardware could be damaged on kernel panic when fancontrol is in use. If the fan speed happens to be low at the time of panic, there is a risk that the system overheats by the time the administrator restarts the system. Possible solutions include: * Writing a non-zero value to /proc/sys/kernel/panic when fancontrol starts and restoring the original value when leaving. $INTERVAL would seem to be an appropriate value to write. * Updating the documentation to recommend the use of a watchdog on any system doing software-based fan speed control. ",khali 3,Active Tickets,2382,Sometimes coretemp fails on Atom CPU,kernel,kernel,,defect,khali,assigned,2011-06-17T21:36:58+0200,2011-06-18T09:39:44+0200,"We had several reports in the past 18 months that the coretemp driver is sometimes unable to get temperature readings from Atom CPU: [http://lists.lm-sensors.org/pipermail/lm-sensors/2010-January/027716.html Atom N330] [[BR]] [http://lists.lm-sensors.org/pipermail/lm-sensors/2010-September/029501.html Atom D510] [[BR]] [http://lists.lm-sensors.org/pipermail/lm-sensors/2010-November/030521.html Atom D525] [[BR]] [http://lists.lm-sensors.org/pipermail/lm-sensors/2011-April/032332.html Atom D525] [[BR]] [http://lists.lm-sensors.org/pipermail/lm-sensors/2011-June/032905.html Atom D525] [[BR]]",khali 3,Active Tickets,2258,Support for changing channel type,libsensors,,,enhancement,somebody,new,2007-09-23T23:37:53+0200,2010-12-11T23:14:34+0100,"The PC-Chips 748MRT motherboard includes a voltage channel with an added temperature diode. Because this channel is registered as a voltage channel (And it technically _is_ a voltage channel..), there is no way to tell sensors to see it as a temperature channel. A sensors.conf option which allows you to select the displayed channel-type can be a welcome addition. Please see http://article.gmane.org/gmane.linux.drivers.sensors/14564/ for more information (Sorry for the late ticket)",ticket 3,Active Tickets,2265,Super I/O SMSC SCH5017 on Tyan Toledo i3100 (S5207),hardware,2.10.1,,enhancement,juergh,new,2007-10-15T21:14:26+0200,2010-01-20T11:47:25+0100,"Hi Developers, I am trying to get sensor information on this Tyan board, on which Tyan only supports M$ Windoze OS, therefore they are not providing a config file for lm-sensors and linux. The sensors-detect detects the Super I/O chip but it is not recognized. This is the output from from sensors-detect: {{{ Some Super I/O chips may also contain sensors. We have to write to standard I/O ports to probe them. This is usually safe. Do you want to scan for Super I/O sensors? (YES/no): Probing for Super-I/O at 0x2e/0x2f Trying family `ITE'... Yes Found unknown chip with ID 0x7803 Trying family `National Semiconductor'... No Trying family `SMSC'... Yes Found unknown chip with ID 0x7803 Trying family `VIA/Winbond/Fintek'... No Probing for Super-I/O at 0x4e/0x4f Trying family `ITE'... No Trying family `National Semiconductor'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Fintek'... No }}} {{{ root@tyan:~# sensors -v sensors version 2.10.1 with libsensors version 2.10.1 root@tyan:~# root@tyan:~# uname -a Linux tyan 2.6.20-16-generic #2 SMP Sun Sep 23 19:50:39 UTC 2007 i686 GNU/Linux root@tyan:~# }}}",ticket 3,Active Tickets,2357,PC8374L support,kernel,kernel,,enhancement,somebody,new,2008-10-15T15:41:33+0200,2008-11-11T01:32:41+0100,"Just want to ask if theres some forthcoming in getting support for PC8374L chip. I have seen some posts regarding this topic: - http://article.gmane.org/gmane.linux.drivers.sensors/15386/match=pc8374l - http://thread.gmane.org/gmane.linux.drivers.sensors/12798/focus=12805 Our partner has a bunch of Dell R200 for which {{{sensors-detect}}} does detect this kind of chipset. {{{ Trying family `National Semiconductor'... Yes Found `Nat. Semi. PC8374L Super IO Sensors' (but not activated) }}} It would be very useful too have sensoring support on them.",ticket 3,Active Tickets,2371,Let sensors-detect pick mainboard configuration files from a local database,sensors-detect,3.1.0,,enhancement,somebody,new,2009-03-02T11:36:22+0100,2010-01-20T11:09:33+0100,"sensors-detect now detects the mainboard based on DMI data. It could easily check in a local filesystem-based database for a suitable configuration file, and copy that file to /etc/sensors.d if found. The configuration files could for example live under /usr/share/libsensors/config. There we would have one subdirectory per manufacturer (matching the DMI manufacturer string after normalization), and in each subdirectory, configuration files for each product (again after name normalization.) We might need to have two top-level subdirectories: by-dmi-system and by-dmi-baseboard, depending on how the mainboard is best identified. I'm not yet sure if this is required or if we can just merge both methods into a single tree for simplicity. This approach seems a good intermediate point between the current situation (no automatic configuration) and the ideal of an online database fed by users. Ultimately we want an online database, but this is a lot more work and nobody has stepped in to achieve it durably so far. One big benefit of the local storage is that the format can evolve until we are happy with what we have. It will be easier to move to an online database if we know what format it needs to have. ",khali 3,Active Tickets,2373,sensors-detect could list the already loaded hwmon drivers,sensors-detect,,,enhancement,somebody,new,2009-03-08T10:36:11+0100,2010-01-20T11:09:56+0100,"Upon starting, sensors-detect could check /sys/class/hwmon for hardware monitoring devices that have drivers loaded already. This would be useful for drivers which auto-load for devices which we do not detect in our script (in particular laptop-specific modules and ACPI thermal zones.) I have no immediate idea of actions sensors-detect could do based on this, but the information would already be useful for both the user and supporters. ",khali 3,Active Tickets,2374,Add ATK0110 detection to sensors-detect,sensors-detect,,,enhancement,somebody,new,2009-04-07T14:04:41+0200,2010-01-20T11:11:09+0100,"We need to think about the integration of the asus_atk0110 driver. The virtual ATK0110 device is not detected by sensors-detect yet, while the physical device backing it up may be detected. This will lead to the confusing situation where sensors-detect tells the user to load one driver but the driver the user actually needs is another one. So we need to add support to sensors-detect. The detection should be done early, so that I/O access to Super-I/O and possibly SMBus is skipped if an ATK0110 device has been detected. ",khali 3,Active Tickets,2375,"Need a way to let ""sensors"" ignore kernel-provided labels",sensors,3.1.0,,enhancement,somebody,new,2009-07-22T14:19:26+0200,2010-01-20T11:11:44+0100,"Kernel-provided sensor labels can be problematic when the user tries to apply a compute or ignore statement. In general, one can comment out all label statements in the configuration file or run ""sensors -c /dev/null"" to see the symbolic names of all inputs (in0, temp1 etc...) However, in the case where kernel-provided labels are available, libsensors will process them nevertheless, so the user has no way to see the symbolic name for the input. See the discussion at: http://lists.lm-sensors.org/pipermail/lm-sensors/2009-May/025831.html ",khali 3,Active Tickets,2367,Push libsensors.so.4 patches upstream,interface,,,task,somebody,new,2009-01-06T11:03:35+0100,2009-01-06T11:03:35+0100,"We have many patches that make monitoring applications compatible with libsensors.so.4 but it seems that most of them are still not upstream, despite the fact that lm-sensors 3.0.1 was released almost one year ago. We must push these patches upstream so that distributions can finally get rid of lm-sensors 2.10. ",khali 3,Active Tickets,2376,Proper support for relative temperature sensors,libsensors,,,task,khali,new,2010-01-15T14:25:42+0100,2010-01-15T14:25:42+0100,"Recent processors include digital thermal sensors, which often report a thermal margin rather than an absolute temperature. This doesn't quite fit in our standard sysfs interface. ",khali 3,Active Tickets,2384,sensors-detect: support for mfd-based SMBus controller drivers,sensors-detect,3.3.1,3.3.4,defect,khali,new,2011-07-22T10:53:27+0200,2012-11-06T21:35:54+0100,"Some SMBus controller drivers are now using the mfd framework, meaning that you have to load two drivers instead of just one. Examples:[[BR]] cs5535-mfd + scx200_acb (since kernel 2.6.38)[[BR]] lpc_sch + i2c-isch (since kernel 2.6.34) sensors-detect currently lacks support for this, and will only load the second driver. If the mfd driver isn't loaded then the SMBus can't be accessed. ",khali 4,Active Tickets,2134,"Intel DG965WH (ICH8) detects OK but sensors says ""no sensors detected""",hardware,,,defect,ruik,assigned,2006-10-22T05:18:58+0200,2007-12-12T12:02:10+0100,"Submitted by: Jim Garrison Sensors version: 2.10.1 Kernel version: 2.6.18-1.2200.fc5smp (Fedora Core) Motherboard: Intel DG965WH http://www.intel.com/products/motherboard/dg965wh/index.htm Detection (see attached file) seems to proceed correctly. Modules are loaded. The ""sensors"" command complains: [jhg@athena ~]$ sudo sensors -s No sensors found! Make sure you loaded all the kernel drivers you need. Try sensors-detect to find out which these are. ",jhg@… 4,Active Tickets,2238,Bus number substitution doesn't affect the device names,libsensors,3.0.0,,enhancement,somebody,new,2007-08-16T09:43:50+0200,2009-02-12T16:30:06+0100,"The ""bus"" statements in sensors.conf only affect the chip statements in that configuration file. Wouldn't it be better if the bus numbers were also substituted in the list of available chips reported by libsensors, so that users and applications can make sure that a given device will always have the same name, regardless of the order in which the i2c bus drivers were loaded? It would also make it possible to reliably select a given chip on sensors' command line. ",khali 4,Active Tickets,2358,Dell Latitude - SMSC - Found unknown chip with ID 0x2803,sensors,,,enhancement,juergh,new,2008-10-16T00:21:03+0200,2008-10-26T17:50:03+0100,"Hello! I've been playing a bit with lm-sensors. I tried detecting sensors and got this bit in the output: Trying family `SMSC'... Yes Found unknown chip with ID 0x2803 (It also detected correctly the processor's sensors which uses coretemp and works perfectly.) I have no idea what to do with that ID 0x2803. I looked on SMSC's page (where they seem to have lots of schematics), but I can't figure out what to look for. Google turned out a few pages of with people who have the same thing in their computers, but otherwise no leads. I read most of the lm-sensors wiki but I couldn't find more ideas (other than writing this ticket). I'm willing to do a bit of searching or hacking, but I have no idea where to start. --- PS. I'm not sure if this is related or not: I _know_ the laptop has some more sensors available. The i8kutils package on Ubuntu for example can read (and set) the fan speed. (AFAIK there's just one fan in the laptop.) I don't know if it's related to the chip detected above. Either way, isn't there a simple way to get lm-sensors to do whatever i8kutils is doing?",ticket 4,Active Tickets,2360,support for dell optiplex 745,hardware,2.10.7,,enhancement,mmh,new,2008-11-17T21:30:01+0100,2008-11-19T01:48:15+0100,"I followed the (almost 1-year old) discussion in the thread: http://lists.lm-sensors.org/pipermail/lm-sensors/2007-December/thread.html#22192 where it was concluded that there was no support for the chip that's inside the optiplex 745. I have another identical machine with Windows XP installed on it. Until recently, Speedfan would not recognize any of the CPU temperature sensors as well (v4.34). Today, I installed speedfan v4.36 and I can see the CPU readings on the dual-core CPU. Here is a cut-and-paste from the ""info"" window of speedfan. {{{ Win9x:NO 64Bit:NO GiveIO:YES SpeedFan:YES I/O properly initialized Linked ISA BUS at $0290 Linked Intel 82801HB ICH8 SMBUS at $ECE0 Scanning ISA BUS at $0290... SuperIO Chip=SCH5514 Scanning Intel SMBus at $ECE0... Address $30 appears to be WRITE ONLY... Address $32 appears to be WRITE ONLY... SMART Enabled for drive 0 Found ST3250820AS (250.0GB) Found Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz End of detection }}} Hope this helps. Anything else I can do?",ticket 4,Active Tickets,2369,Allow user additions to /etc/sysconfig/lm_sensors,sensors-detect,3.0.3,,enhancement,somebody,new,2009-01-26T15:15:47+0100,2010-01-20T11:12:16+0100,"It could be useful to let the user add custom modules to /etc/sysconfig/lm_sensors. Unfortunately, sensors-detect overwrites /etc/sysconfig/lm_sensors when run, so this isn't possible. We should change sensors-detect to update /etc/sysconfig/lm_sensors instead of overwriting it. Then we could define a variable in that file (for example EXTRA_MODULES) where the user could list additional kernel modules to be loaded for the lm_sensors service. Lastly, initialization scripts would have to be updated to handle this new variable. Discussion at:[[BR]] http://lists.lm-sensors.org/pipermail/lm-sensors/2009-January/025200.html",khali 4,Active Tickets,2383,Check for VID bits consistency,kernel,,,enhancement,,new,2011-06-21T13:30:37+0200,2011-06-21T13:37:08+0200,"Sometimes monitoring chips have fewer VID inputs than the CPU would need. In that case it's pretty clear that the VID reading can't be reported properly so it should be disabled by the driver. See for example:[[BR]] http://lists.lm-sensors.org/pipermail/lm-sensors/2011-June/032957.html",khali 4,Active Tickets,2385,User command to clear the chassis intrusion alarm,sensors,3.3.1,,enhancement,,new,2012-02-10T09:26:47+0100,2012-02-10T09:26:47+0100,"We currently [http://lists.lm-sensors.org/pipermail/lm-sensors/2012-January/034780.html lack an easy way for the user to clear the chassis intrusion alarm]. The user has to either add a set statement to his/her configuration file, or access sysfs directly. We could add an option to sensors(3), or even write a separate binary solely dedicated to reporting intrusions and clearing alarms. ",khali 4,Active Tickets,2303,Update references to Analog Devices chips,website,,,task,mroberds,assigned,2008-02-20T09:25:06+0100,2009-08-30T10:30:02+0200,"Most (all?) of the ADM and ADT series of chips by Analog Devices have been sold to ON Semiconductor. We need to update wiki/Devices to mention that change and to link to the right pages on the www.onsemi.com website. Additionally, references in the driver code and documentation should be updated as well. ",khali