Ticket #152 (closed task)

Opened 7 years ago

misnotification of 3.3v for gl518sm.o driver. (Examined/Solved - lm_sensors 2.4.5 linux 2.2.14)

Reported by: contact Owned by: somebody
Priority: minor Milestone:
Component: hardware Version:
Keywords: Cc:

Description

thank you for the quick reply. I got sensors working.. kind of. The temperature is working, which is what I wanted to begin with. But I think (hope) it is misreporting voltage. here is the output from the sensors script: gl518sm-i2c-0-2d Adapter: VIA i2c Algorithm: Bit-shift algorithm +5V: +5.42 V (min = +4.50 V, max = +5.49 V) +3.3V: +4.57 V (min = +2.96 V, max = +3.62 V) +12V: +0.29 V (min = +10.81 V, max = +13.12 V) Vcore: +2.43 V (min = +2.33 V, max = +2.85 V) fan1: 0 RPM (min = 3000 RPM, div = 2) ALARM fan2: 0 RPM (min = 3000 RPM, div = 2) ALARM temp: +40 C (limit = +60 C, hysteresis = +50 C) beep_enable:

Sound alarm disabled

btw. sound wouldn't be disabled if I had an internal speaker... and I dont have fans pluged in. the +3.3V and the +12v make me uneasy I hope I am doing something wrong. My bios doesn't have the display of voltage and whatnot. I am actually considering installing windows to test it out in windows... maybe it is the hardware... I hope not. thanks Joseph Yarbrough --- It's a GL518SM misfeature. By default, it can't read most voltages, only monitor them (yes, that is crazy. Ask Genesys Logic!). But by monitoring them, we can interpolate them. To enable this, add 'set iterate 1' to your /etc/sensors.conf and run 'sensors -s' (or do simply 'echo 1 > /proc/sys/dev/sensors/gl518*/iterate'). For more information see the information in doc/chips/gl518sm. Unfortunately, the current library code and sensors do not check for the value of iterate before deciding to output bogus voltages. I have changed the driver code to output 0 instead of some bogus value, which should at least help. You can get it from CVS.

Frodo

Note: See TracTickets for help on using tickets.