Re: [expert] lm sensors
From: Bryan Phinney [EMAIL PROTECTED] [...] I rewrote the lmsensors init script so that it was manually loading the modules rather than pulling them from the /etc/sysconfig/lmsensors file. I ran the script and it loaded the modules, then stopped the script and it unloaded the modules. When I went to restart it, the machine hard locked again. I am currently trying to load only the i2c-viapro, i2c-isa, i2c-it87 and it2-lm75 modules and skipping the adm1021 and eeprom modules since my machine appears to have the most issues with the adm1021 module and I don't really need the eeprom one. in order to solve wich one kills your system, you should use the modprobe command and try to load one module at a time until it hangs... -- Regards Thomas Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] lm sensors
On Wednesday 19 November 2003 12:36 pm, Bryan Phinney wrote: I have recently started trying to install lm sensors on my computer which has a Soyo KT400 Dragon Ultra Platinum motherboard. I have had very mixed results with the sensors including some very hard to diagnose hard locks on the machine when I attempt to load the sensor modules. Does anyone here have any experience working with lmsensors and want to take a crack at helping me figure out the problem. I have a Soyo KT400 DUB and I have got sensors running without trouble. I actually have the lm90 working by installing the version from cvs. It reads the diode off the processor and is a much more accurate temp. Scenario, I installed lmsensors by RPM, ran sensors-detect and let it create the /etc/sysconfig/lmsensors configuration file. When I restarted the computer, the lmsensors init script kicked off, showed loading modules and then nothing, hard lock. I power cycled the machine, booted into failsafe mode, disabled lmsensors init script and went back into Linux. I manually tried to load lmsensors init script and it hard locked again. I rebooted, went back and tried to manually load the modules that are loading from the script and they loaded fine. I then manually unloaded the modules and they also unloaded fine. I only load the it87. The lm75 driver may be causing your problem, there isn;t one on that board. Also, on the Soyo, I only got accurate readings by specifying a socket type when modprobing the driver. the differnet types are in the docs, but I figured out the Soyo is type 38. The voltages are a little messy too. This can be fixed by making a few changes to the sensors.conf file, but I haven't taken the time to figure out the adjustments and do it. Here are the relevant lines that I added to my rc.local file. # I2C adapter drivers modprobe i2c-isa modprobe i2c-viapro # I2C chip drivers modprobe it87 temp_type=0x38 modprobe lm90 I rewrote the lmsensors init script so that it was manually loading the modules rather than pulling them from the /etc/sysconfig/lmsensors file. I ran the script and it loaded the modules, then stopped the script and it unloaded the modules. When I went to restart it, the machine hard locked again. I am currently trying to load only the i2c-viapro, i2c-isa, i2c-it87 and it2-lm75 modules and skipping the adm1021 and eeprom modules since my machine appears to have the most issues with the adm1021 module and I don't really need the eeprom one. I have just edited my modules file to load the i2c-proc module at bootup rather than letting it load from the lmsensors init script. If anyone has any suggestions for me, I would really appreciate it. I would just try without the lm75 loaded. Before I installed the newer version, I was running without any problems. BTW, sensors.conf is stock and I did not add any lines to /etc/modules.conf except the alias for char-major-89 i2c-dev because the other adm1021 line should not be needed since I am not loading adm1021. Yes, that is correct. -- /g Outside of a dog, a man's best friend is a book, inside a dog it's too dark to read -Groucho Marx Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] lm sensors
On Wednesday 19 November 2003 02:03 pm, Thomas Backlund wrote: in order to solve wich one kills your system, you should use the modprobe command and try to load one module at a time until it hangs... Originally, the problem module was the adm1021 module and that was due to the options line included in /etc/modules.conf that was suggested by sensors-detect. However, I removed that module and am no longer trying to load that one. Now, I can manually load all of them and then unload all of them. Running the script, I can also load all and then unload all, it is on the second attempt to load that I get problems. I am going to work on this more tonight, I am beginning to wonder if the problem may stem from trying to unload the i2c-proc module along with the others. For the most part, I don't see a reason to remove the proc module, even if you want to remove the individual sensor modules when shutting the system down. -- Bryan Phinney Software Test Engineer Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] lm sensors
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 19 Nov 2003 12:36:51 -0500, Bryan Phinney [EMAIL PROTECTED] wrote about [expert] lm sensors: Scenario, I installed lmsensors by RPM, ran sensors-detect and let it create the /etc/sysconfig/lmsensors configuration file. When I restarted the computer, the lmsensors init script kicked off, showed loading modules and then nothing, hard lock. I power cycled the machine, booted into failsafe mode, disabled lmsensors init script and went back into Linux. There`s easier ways to tackle that; IMHO. Proberbly failsafe is safe, but why bother, if you`re careful and consider beforehand what you do, go to init 1 and cd to where you want to make your changes. Of course, vi may be the preferred editor for that, but I didn`t have the time to learn it yet. Still mc has a pretty easy editor which will easily access what you need to change. I manually tried to load lmsensors init script and it hard locked again. I rebooted, went back and tried to manually load the modules that are loading from the script and they loaded fine. I then manually unloaded the modules and they also unloaded fine. I rewrote the lmsensors init script so that it was manually loading the modules rather than pulling them from the /etc/sysconfig/lmsensors file. I ran the script and it loaded the modules, then stopped the script and it unloaded the modules. When I went to restart it, the machine hard locked again. I would follow following scenario: a. make sure sensorsd service is not running. b. Run the script provided, don`t allow it to modify your conf.modules or whichever they suggest. You already know which modules the script found, so check no modules are loaded, and if they that they are not added by modules.conf. If no modules are listed in the output of lsmod continue, if they are start service lm_sensors and with, for instance Gkrellm see if you get any readings. That means the kernel gives them direct. Only those modules which the kernel might not provide data output for should be loaded as modules via modules.conf. Before any adjustment to the modules stop the service and restart after added (or removing) any modules which do not show up useful values. Compare your kernel logs, particularly /var/log/kernel/errors. It will show bus collisions, if any. I was lucky I did not get hard locks when I ran too many modules, but the logs filled alright. In 9.0 and 9.1 there were a couple of versions that did not have all sensors for *my* modules, I don`t know your board so PH it could be similar. I have just edited my modules file to load the i2c-proc module at bootup rather than letting it load from the lmsensors init script. If anyone has any suggestions for me, I would really appreciate it. So you appear to be infected by the reboot philosophy of certain O/S`s (sometimes I am guilty of similar behaviours to analyze prob ;-), but with this (unless hardlocked), I see no need to reboot. BTW, sensors.conf is stock and I did not add any lines to /etc/modules.conf You should, that is the only way for the service which this package provides will read any data that are not provided by the kernel. Unless, naturally, the kernel provides *all* for your particular mobo. Best of luck, =Dick Gevers= CDCS; temporarily banking package tester. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) Comment: Encryption is an envelope - the contents are private. iD8DBQE/u/G3wC/zk+cxEdMRAh4JAKCf2sA9i3zOso2edquVK8UYFqoZowCdGyG1 Yw47DfYArilWbn7YL6w/1VY= =qffd -END PGP SIGNATURE- Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] lm sensors
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Bryan, On Wed, 19 Nov 2003 12:36:51 -0500, Bryan Phinney [EMAIL PROTECTED] wrote about [expert] lm sensors: Scenario, I installed lmsensors by RPM, ran sensors-detect and let it create the /etc/sysconfig/lmsensors configuration file. When I restarted the computer, the lmsensors init script kicked off, showed loading modules and then nothing, hard lock. I power cycled the machine, booted into failsafe mode, disabled lmsensors init script and went back into Linux. There`s easier ways to tackle that; IMHO. Proberbly failsafe is safe, but why bother, if you`re careful and consider beforehand what you do, go to init 1 and cd to where you want to make your changes. Of course, vi may be the preferred editor for that, but I didn`t have the time to learn it yet. Still mc has a pretty easy editor which will easily access what you need to change. I manually tried to load lmsensors init script and it hard locked again. I rebooted, went back and tried to manually load the modules that are loading from the script and they loaded fine. I then manually unloaded the modules and they also unloaded fine. I rewrote the lmsensors init script so that it was manually loading the modules rather than pulling them from the /etc/sysconfig/lmsensors file. I ran the script and it loaded the modules, then stopped the script and it unloaded the modules. When I went to restart it, the machine hard locked again. I would follow following scenario: a. make sure sensorsd service is not running. b. Run the script provided, don`t allow it to modify your conf.modules or whichever they suggest; you already know which modules the script found, so check no modules are loaded, and if they are not see if Gkrellm already gets some kernel data. If yes don`t put that stream in modules.conf. If no kernel data is read add any of the modules per the script to modules.conf. Before each step and after each erroneous load of modules that don`t add a data stream that Gkrellm can read you have to stop the service unload the previous set of loaded modules. Compare your kernel logs, particularly /var/log/kernel/errors. It will show bus collisions, if any. I was lucky I did not get hard locks when I ran too many modules, but the logs filled alright. In 9.0 and 9.1 there were a couple of versions of the kernel that did not have all sensors for *my* modules, I don`t know your board so with current kernels it could PH be similar, though I estimate the chances extremely slight, given the activity I read on Cooker of Mr. Thomas Backlund and others with respect to the kernel packages. I have just edited my modules file to load the i2c-proc module at bootup rather than letting it load from the lmsensors init script. If anyone has any suggestions for me, I would really appreciate it. So you appear to be infected by the reboot philosophy of certain O/S`s (sometimes I am guilty of similar behaviours to analyze probs. ;-), but with this (unless hardlocked), I see no need to reboot. BTW, sensors.conf is stock and I did not add any lines to /etc/modules.conf You should, that is the only way for the service which this package provides will read any data that are not provided by the kernel. Unless, naturally, the kernel provides *all* for your particular mobo. Best of luck, =Dick Gevers= CDCS; temporarily banking SW tester. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) Comment: Encryption is an envelope - the contents are private. iD8DBQE/u/P0wC/zk+cxEdMRAi8TAKC3vmCfK/pbYTuPzKU6IiwN/ZNWAACcDqku qZ50ekdWPDCKGlAvVhpqD+A= =SYVR -END PGP SIGNATURE- Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] lm sensors
On Wednesday 19 November 2003 02:52 pm, Greg Meyer wrote: I only load the it87. The lm75 driver may be causing your problem, there isn;t one on that board. Also, on the Soyo, I only got accurate readings by specifying a socket type when modprobing the driver. the differnet types are in the docs, but I figured out the Soyo is type 38. The voltages are a little messy too. This can be fixed by making a few changes to the sensors.conf file, but I haven't taken the time to figure out the adjustments and do it. Here are the relevant lines that I added to my rc.local file. Thanks very much for the info Greg. That must have been it. I removed the lm75 module and now it is starting and stopping fine. Also, I moved the i2c-proc module startup to the actual /etc/modules file so that it is started automatically at bootup. That appears to be much better for the script startup method and whether it helps or not, seems to be a little more elegant. I also added an options line in /etc/modules.conf for the it87 temp_type=0x38 option. I will check later to see how accurate the temps are. Again, thanks much for the info, it has probably saved me from a few more hard boots. -- Bryan Phinney Software Test Engineer Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] lm sensors
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 19 Nov 2003 22:42:00 +, Dick Gevers [EMAIL PROTECTED] wrote about Re: [expert] lm sensors: Aargh, and I thought I cancelled this one just in time. Please waste. The next version is the final. Sorry. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) Comment: Encryption is an envelope - the contents are private. iD8DBQE/u/SJwC/zk+cxEdMRAlCRAJkB9cAD7694CALEz9QgTKsnju+74ACfZCP1 vaM+9gtg3fG9IT+df/OyH1I= =eQIN -END PGP SIGNATURE- Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] lm sensors
On Wednesday 19 November 2003 05:42 pm, Dick Gevers wrote: There`s easier ways to tackle that; IMHO. Proberbly failsafe is safe, but why bother, if you`re careful and consider beforehand what you do, go to init 1 and cd to where you want to make your changes. Of course, vi may be the preferred editor for that, but I didn`t have the time to learn it yet. Still mc has a pretty easy editor which will easily access what you need to change. Well, at the point that the machine hard locks, keyboard doesn't respond, can't SSH into it and it becomes an effective doorstop, there is not much else to do but restart the machine and remove the lm_sensors script from the init process to troubleshoot the problem which is effectively what I did. When manually loading, it still causes the hard lock, again, no choice but to powercycle the machine which involves rebooting. I would follow following scenario: a. make sure sensorsd service is not running. b. Run the script provided, don`t allow it to modify your conf.modules or whichever they suggest. You already know which modules the script found, so check no modules are loaded, and if they that they are not added by modules.conf. If no modules are listed in the output of lsmod continue, if they are start service lm_sensors and with, for instance Gkrellm see if you get any readings. That means the kernel gives them direct. Only those modules which the kernel might not provide data output for should be loaded as modules via modules.conf. Before any adjustment to the modules stop the service and restart after added (or removing) any modules which do not show up useful values. I tried manually loading an unloading one at a time but I might not have done it often enough to get the hard lock. Now it appears that the culprit is linked to one of the modules and since removing it, I no longer have the problem. Compare your kernel logs, particularly /var/log/kernel/errors. It will show bus collisions, if any. I was lucky I did not get hard locks when I ran too many modules, but the logs filled alright. Well, all I got was hard locks and there was nothing in the logs to show what was causing it. I checked and there is nothing from the start until it shows the hard reboot with kernel reloading. I have just edited my modules file to load the i2c-proc module at bootup rather than letting it load from the lmsensors init script. If anyone has any suggestions for me, I would really appreciate it. So you appear to be infected by the reboot philosophy of certain O/S`s (sometimes I am guilty of similar behaviours to analyze prob ;-), but with this (unless hardlocked), I see no need to reboot. Since the only issue that I spoke of was the hardlock, not sure I follow your analysis about my troubleshooting style. I don't reboot my machine on a whim and certainly know how to init 1 and then back to init 3 if all I wanted was to test the init process. BTW, sensors.conf is stock and I did not add any lines to /etc/modules.conf You should, that is the only way for the service which this package provides will read any data that are not provided by the kernel. Unless, naturally, the kernel provides *all* for your particular mobo. Well, I will probably have to edit that eventually to get the temps for Vcore accurately reported but the stock conf file appears to be doing a great job so far on CPU temp, MB temp and fan speed. -- Bryan Phinney Software Test Engineer Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] lm-sensors install/use problems
On Sunday 17 June 2001 01:09 am, David E. Fox wrote: that doesn't work for you, it's a hardware problem. Still, AMD isn't going to fully support temperature monitoring till the Athlon 4's come out Isn't that more of a mainboard issue than a CPU one? Not practically. While decent motherboards socket A boards have monitoring chips/buses, the most important value .. the cpu core temp is bogus. Temps garnered from a thermistor (probe), no matter how well placed on the die, are a guess at best. Like tryin to measure the temperature of the wiring inside a wall, by pressing a thermometer against the sheetrock. With the cpu's core temp jumping 10 to 20°C in a heartbeat under instant load, a probe temp of 50°C from a Tbird or Duron is useless. Even AMD docs now caution to add between 10 to 20°C to the reported probe temp under load to best _approximate_ the actual core temp. Even with this fudge factor, spikes in the core temp will not be seen. Overclockers have long known / used this rule of thumb. Current AMD cpu motherboards are ready, have been for some time, and the Athlon4's will have an internal diode (like Pentium processors have had all along) to accurately and usefully monitor the core temp. The only way to sort'a kind'a accurately tell now if an AMD cpu is experiencing intolerable core temp spikes, is if the system randomly freezes or reboots (assuming everything else is in order). Until AMD implements accurate core monitoring, the best fix if you're concerned about cpu overheating is to underclock. Reduce the FSB about 5% or reduce the multiplier by .5 Of course, case temp should be kept at or near room temp, and a better than AMD 'retail' heatsink and fan with thermal grease (not pad) should be used. Another trick is to try an' reduce Vcore a little, no more than ~5% and increase IO voltage up to ~12%. 'Course now this is a motherboard issue, you havt'a have a decent enough one to support doin' all this ; -- Tom Brinkman [EMAIL PROTECTED] Galveston Bay
Re: [expert] lm-sensors install/use problems
On Saturday 16 June 2001 03:18 pm, David E. Fox wrote: I've rebuilt lm-sensors and installed it, Any suggestions? I was hoping to upgrade to kernel 2.4.5, but in looking into the kernel config file I don't see anything that exactly matches the probe that my mainboard uses. Mandrake 2.2.x kernels have had i2c support patched in even before the 2.4.x kernels. You might need to undo your efforts and just install the appropriate lm_utils ...-mdk rpm. With 8.0 I'm using lm_utils-2.4.3_2.5.5-25mdk Run 'sensors-detect' and it'll give you the lines you'll need to add to rc.local and modules.conf. I suspect if that doesn't work for you, it's a hardware problem. Still, AMD isn't going to fully support temperature monitoring till the Athlon 4's come out. -- Tom Brinkman [EMAIL PROTECTED] Galveston Bay
Re: [expert] lm-sensors install/use problems
Mandrake 2.2.x kernels have had i2c support patched in even before the 2.4.x kernels. You might need to undo your efforts and just install the appropriate lm_utils ...-mdk rpm. With 8.0 I'm using I saw some of the necessary modules in lib/modules/2.2.17/misc but the one I need apparently for this mainboard is via686a.o, which isn't in that directory. Consequently, 'modprobe via686a.o' doesn't work. I did as you suggested: I instaled the lm_utils rpm and there is little difference. The one main difference is if I load the sensors.o modules I get a different line of output from sensors: 'no sensors found' rather than 'cannot read /proc file'. This seems significant. From 'modules-dep' it would seem that sensors.o is dependent on via686a.o - but where is the via686a.o file? that doesn't work for you, it's a hardware problem. Still, AMD isn't going to fully support temperature monitoring till the Athlon 4's come Isn't that more of a mainboard issue than a CPU one? Tom Brinkman [EMAIL PROTECTED] Galveston Bay David E. Fox Thanks for letting me [EMAIL PROTECTED]change magnetic patterns [EMAIL PROTECTED] on your hard disk. ---
Re: [expert] lm sensors and i2c
I use this program to do that on the Abit BP6 system (health) and when you untar the program you will find instructions on how to set it up Don On Friday 02 February 2001 17:41, you wrote: "J . A . Magallon" wrote: On 02.02 PBone wrote: I am trying to get temperature monitoring for my athlon/epox 8kta2/Mandrake 7.2 system. I have been to the lm_sensors site but the latest Mandrake rpms are for Mandrake 7.0. Is there an easy (ie rpm) way to install lm_sensors- (I have had low success rate trying to compile programs under Manrake 7.2) cooker: kernel 2.4 + lm_sensors -- J.A. Magallon $ cd pub mailto:[EMAIL PROTECTED] $ more beer Linux werewolf 2.4.1-ac1 #2 SMP Fri Feb 2 00:19:04 CET 2001 i686 The reason you are having problems compiling packages under Mandrake 7.2 for LM7.0 is because the mandrake packages are compiled with gcc 2.95 and higher while LM7.0 is compiled with gcc 2.72 (or something or other. I refuse to dig up my 7.0 disk to look to be sure. Must move forward... always) or something and egcs. gcc 2.95 was the first implementation of gcc and egcs being combined into one. Cheers, -- Al -- 73 de kk6wj health-0.03.tar.gz
Re: [expert] lm sensors and i2c
On 02.02 PBone wrote: I am trying to get temperature monitoring for my athlon/epox 8kta2/Mandrake 7.2 system. I have been to the lm_sensors site but the latest Mandrake rpms are for Mandrake 7.0. Is there an easy (ie rpm) way to install lm_sensors- (I have had low success rate trying to compile programs under Manrake 7.2) cooker: kernel 2.4 + lm_sensors -- J.A. Magallon $ cd pub mailto:[EMAIL PROTECTED] $ more beer Linux werewolf 2.4.1-ac1 #2 SMP Fri Feb 2 00:19:04 CET 2001 i686
Re: [expert] lm sensors and i2c
"J . A . Magallon" wrote: On 02.02 PBone wrote: I am trying to get temperature monitoring for my athlon/epox 8kta2/Mandrake 7.2 system. I have been to the lm_sensors site but the latest Mandrake rpms are for Mandrake 7.0. Is there an easy (ie rpm) way to install lm_sensors- (I have had low success rate trying to compile programs under Manrake 7.2) cooker: kernel 2.4 + lm_sensors -- J.A. Magallon $ cd pub mailto:[EMAIL PROTECTED] $ more beer Linux werewolf 2.4.1-ac1 #2 SMP Fri Feb 2 00:19:04 CET 2001 i686 The reason you are having problems compiling packages under Mandrake 7.2 for LM7.0 is because the mandrake packages are compiled with gcc 2.95 and higher while LM7.0 is compiled with gcc 2.72 (or something or other. I refuse to dig up my 7.0 disk to look to be sure. Must move forward... always) or something and egcs. gcc 2.95 was the first implementation of gcc and egcs being combined into one. Cheers, -- Al
