Flacycads, chees mate. I'm at work so I cant try this, but I never got this line 
ever...

 modprobe via686a

from doing sensors-detect. I did have a sensors section in gkrellm, but not any more, 
since I tried to get clever and remove all the relevant modules and reinstall them. 
Now I get zip about temps. Yes I definitely have lm_sensors instaled, sensors-detect 
and sensors both exist. I just cant seem to get it to work - your determination to 
help me get this working is _much_ appreciated mate!!!

As for the stuff that should go in rc.local that isn't there, well thats the thing, 
thats what sensors-detect is telling me to put there - nothing, zip, null. I've 
literally copied the output from the terminal. I promise I'm as stumped as you over 
this one.

What I intend to do this evening is whack your suggested lines on my box - I'll try 
them first to see if it goes bang ;o) - then reboot and have another go. I'll let you 
know how it goes. Again thanks so much for your efforts!

Si


----- Original Message -----
From: flacycads <[EMAIL PROTECTED]>
Date: Mon, 27 Jan 2003 13:15:11 -0500
To: [EMAIL PROTECTED]
Subject: Re: [expert] lm_sensors on gigabyte ga-7zxe

> Simon,
> As you posted, your sensors detect output does not list the needed modules for 
> /etc/rc.local. They aren't there. I quote:
> 
> #----cut here----
> > > > # I2C adapter drivers
> > > > # I2C chip drivers
> > > > #----cut here----
> 
> On many a fresh install of Mandrake 9.0 on the KT7-RAID, all I've had to do is 
> add the lines to the /etc files, as shown below. This is the "definitive " 
> list that works on this board. It is what sensor-detect comes up with when 
> run on the KT7 board. You don't even have to run sensors detect- just put 
> these lines into the /etc files. (maybe your sensors-detect is corrupted, or 
> the wrong version?? If need be, I can email you the sensors-detect I used the 
> first time I got this to work)
> 
> For /etc/rc.local:
> 
> # I2C adapter drivers
> modprobe i2c-viapro
> modprobe i2c-isa
> # I2C chip drivers
> modprobe adm1021
> modprobe eeprom
> modprobe via686a
> -------------------------------------
> For /etc/modules:
> 
> # I2C module options
> alias char-major-89 i2c-dev
> -------------------------------------------
> 
> Then after a shutdown/reboot, open gkrellm and the readouts will now include 
> the cpu/chassis temp, and fan speed readouts.  Contrary to what's commonly 
> believed, I have found you sometimes need to shut down and reboot linux when 
> performing some prodedures, to completely flush out the Ram of everything. If 
> you don't, sometimes things simply will not work. While far better than 
> windows, linux is still not perfect in this respect.
> 
> You then press F1 to open the gkrellm config panel, go to builtins-sensors and 
> make your fine-tuning of the offsets so as to match the bios readings, if you 
> need to. That's all there is to it. If it isn't working on a generic 9.0 
> install, you are doing something wrong, like not saving the edited /etc files 
> (as root), or your lm_sensors package is somehow corrupted. If I'm not 
> mistaken, the I2c stuff is compiled into the Mandrake kernel. The only other 
> thing I can think of is that if you did a custom install, you somehow removed 
> an obscure lm_sensors dependency. But this is very unlikely, and I don't know 
> what that would be.
>  
> Another idea:
> Go into Mandrake Control Center, Software Managment, Software Package Removal, 
> alphabetical listings, and see if you really have lm_sensors 2.6.4-4mdk 
> installed. If not, install it. If so, remove it, and shut down the machine. 
> After reboot, reinstall the lm_sensors package, and try again.
> 
> Robert Crawford
> 
> ------------
> 
> On Monday 27 January 2003 04:19 am, Simon Naish wrote:
> > I'm afraid I've tried that, and still no joy. lsmod shows everything loaded
> > that should be according to the results of sensors-detect and yet I get no
> > temps. I just tried rmmod'ing all the listed modules and starting again.
> > With a different outcome. I get a slightly different list of stuff to add
> > (an extra module and line of code for modules.conf) and now when I run
> > sensors I get absolutely no reference to temperatures at all, just the
> > memory. Seems fiddling with it is just breaking it more. So has anyone got
> > a definitive list of modules that does work with an ABIT KT-7 RAID mobo?
> > I'd be greatful ;o)
> >
> > Si
> >
> >
> > ----- Original Message -----
> > From: flacycads <[EMAIL PROTECTED]>
> > Date: Sat, 25 Jan 2003 21:14:11 -0500
> > To: [EMAIL PROTECTED]
> > Subject: Re: [expert] lm_sensors on gigabyte ga-7zxe
> >
> > > Of course, also add the line in modules.conf that sensors-detect did
> > > list.
> > >
> > > Robert
> > >
> > > On Saturday 25 January 2003 05:30 pm, Simon Naish wrote:
> > > > Chuck, went through again selected the ISA stuff, heres my output, (no
> > > > change ) any ideas....
> > > >
> > > > Sorry theres so bl**dy much of it, I'm stumped though I have to say.
> > > >
> > > > # sensors-detect
> > > >  This program will help you to determine which I2C/SMBus modules you
> > > > need to load to use lm_sensors most effectively.
> > > >  You need to have done a `make install', issued a `depmod -a' and made
> > > > sure `/etc/conf.modules' (or `/etc/modules.conf') contains the
> > > > appropriate module path before you can use some functions of this
> > > > utility. Read doc/modules for more information.
> > > >  Also, you need to be `root', or at least have access to the
> > > > /dev/i2c[-/]* files for some things. You can use prog/mkdev/mkdev.sh to
> > > > create these /dev files if you do not have them already.
> > > >  If you have patched your kernel and have some drivers built-in you can
> > > >  safely answer NO if asked to load some modules. In this case, things
> > > > may seem a bit confusing, but they will still work.
> > > >
> > > >  IF THIS IS AN IBM THINKPAD, PRESS CTRL-C NOW!
> > > >  IBM Thinkpads have a severely broken i2c/SMBus implementation,  just
> > > > scanning the bus will break your thinkpad forever!
> > > >
> > > >  We can start with probing for (PCI) I2C or SMBus adapters.
> > > >  You do not need any special privileges for this.
> > > >  Do you want to probe now? (YES/no): YES
> > > > Probing for PCI bus adapters...
> > > > Use driver `i2c-viapro' for device 00:07.4: VIA Technologies VT82C686
> > > > Apollo ACPI Probe succesfully concluded.
> > > >
> > > >  We will now try to load each adapter module in turn.
> > > > Module `i2c-viapro' already loaded.
> > > >  Do you now want to be prompted for non-detectable adapters? (yes/NO):
> > > > yes Load `i2c-elektor' (say NO if built into your kernel)? (YES/no):
> > > > YES /lib/modules/2.4.18-8.1mdk/kernel/drivers/i2c/i2c-elektor.o.gz:
> > > > init_module: No such device Hint: insmod errors can be caused by
> > > > incorrect module parameters, including invalid IO or IRQ parameters
> > > > modprobe: insmod
> > > > /lib/modules/2.4.18-8.1mdk/kernel/drivers/i2c/i2c-elektor.o.gz failed
> > > > modprobe: insmod i2c-elektor failed
> > > > Loading failed ()... skipping.
> > > > Load `i2c-elv' (say NO if built into your kernel)? (YES/no): YES
> > > > /lib/modules/2.4.18-8.1mdk/kernel/drivers/i2c/i2c-elv.o.gz:
> > > > init_module: No such device Hint: insmod errors can be caused by
> > > > incorrect module parameters, including invalid IO or IRQ parameters
> > > > modprobe: insmod
> > > > /lib/modules/2.4.18-8.1mdk/kernel/drivers/i2c/i2c-elv.o.gz failed
> > > > modprobe: insmod i2c-elv failed
> > > > Loading failed ()... skipping.
> > > > Load `i2c-philips-par' (say NO if built into your kernel)? (YES/no):
> > > > YES Module loaded succesfully.
> > > > Load `i2c-velleman' (say NO if built into your kernel)? (YES/no): YES
> > > > /lib/modules/2.4.18-8.1mdk/kernel/drivers/i2c/i2c-velleman.o.gz:
> > > > init_module: No such device Hint: insmod errors can be caused by
> > > > incorrect module parameters, including invalid IO or IRQ parameters
> > > > modprobe: insmod
> > > > /lib/modules/2.4.18-8.1mdk/kernel/drivers/i2c/i2c-velleman.o.gz failed
> > > > modprobe: insmod i2c-velleman failed
> > > > Loading failed ()... skipping.
> > > >  To continue, we need module `i2c-dev' to be loaded.
> > > >  If it is built-in into your kernel, you can safely skip this.
> > > > i2c-dev is already loaded.
> > > >
> > > >  We are now going to do the adapter probings. Some adapters may hang
> > > > halfway through; we can't really help that. Also, some chips will 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. That often
> > > >  includes address 0x69 (clock chip).
> > > >
> > > > Next adapter: SMBus Via Pro adapter at 5000 (Non-I2C SMBus adapter)
> > > > Do you want to scan it? (YES/no/selectively): YES
> > > > Client at address 0x18 can not be probed - unload all client drivers
> > > > first! Client found at address 0x31
> > > > Probing for `National Semiconductor LM78'... Failed!
> > > > Probing for `National Semiconductor LM78-J'... Failed!
> > > > Probing for `National Semiconductor LM79'... Failed!
> > > > Probing for `Winbond W83781D'... Failed!
> > > > Probing for `Winbond W83782D'... Failed!
> > > > Probing for `Winbond W83783S'... Failed!
> > > > Probing for `Winbond W83627HF'... Failed!
> > > > Probing for `Asus AS99127F'... Failed!
> > > > Client at address 0x50 can not be probed - unload all client drivers
> > > > first! Client at address 0x51 can not be probed - unload all client
> > > > drivers first! Client found at address 0x69
> > > >
> > > >  Some chips are also accessible through the ISA bus. ISA probes are
> > > >  typically a bit more dangerous, as we have to write to I/O ports to do
> > > >  this.  Do you want to scan the ISA bus? (YES/no): YES
> > > > Probing for `National Semiconductor LM78'
> > > >   Trying address 0x0290... Failed!
> > > > Probing for `National Semiconductor LM78-J'
> > > >   Trying address 0x0290... Failed!
> > > > Probing for `National Semiconductor LM79'
> > > >   Trying address 0x0290... Failed!
> > > > Probing for `Winbond W83781D'
> > > >   Trying address 0x0290... Failed!
> > > > Probing for `Winbond W83782D'
> > > >   Trying address 0x0290... Failed!
> > > > Probing for `Winbond W83627HF'
> > > >   Trying address 0x0290... Failed!
> > > > Probing for `Winbond W83697HF'
> > > >   Trying address 0x0290... Failed!
> > > > Probing for `Silicon Integrated Systems SIS5595'
> > > >   Trying general detect... Failed!
> > > > Probing for `VIA Technologies VT 82C686 Integrated Sensors'
> > > >   Trying general detect... Failed!
> > > > Probing for `ITE IT8705F / IT8712F / SiS 950'
> > > >   Trying address 0x0290... Failed!
> > > >
> > > >  Now follows a summary of the probes I have just done.
> > > >  Just press ENTER to continue:
> > > >
> > > >
> > > >  I will now generate the commands needed to load the I2C modules.
> > > >  Sometimes, a chip is available both through the ISA bus and an I2C
> > > > bus. ISA bus access is faster, but you need to load an additional
> > > > driver module for it. If you have the choice, do you want to use the
> > > > ISA bus or the I2C/SMBus (ISA/smbus)? ISA
> > > >
> > > > WARNING! If you have some things built into your kernel, the
> > > > below list will contain too many modules. Skip the appropriate ones!
> > > > To load everything that is needed, add this to some /etc/rc* file:
> > > >
> > > > #----cut here----
> > > > # I2C adapter drivers
> > > > # I2C chip drivers
> > > > #----cut here----
> > > >
> > > > To make the sensors modules behave correctly, add these lines to either
> > > > /etc/modules.conf or /etc/conf.modules:
> > > >
> > > > #----cut here----
> > > > # I2C module options
> > > > alias char-major-89 i2c-dev
> > > > #----cut here----
> > > >
> > > > Its failing on everything.
> > > >
> > > > ----- Original Message -----
> > > > From: Chuck Burns <[EMAIL PROTECTED]>
> > > > Date: Fri, 24 Jan 2003 20:21:01 -0600
> > > > To: [EMAIL PROTECTED]
> > > > Subject: Re: [expert] lm_sensors on gigabyte ga-7zxe
> > > >
> > > > > On Fri, January 24 2003 5:20 pm, Simon Naish wrote:
> > > > > > Adapter: SMBus Via Pro adapter at 5000
> > > > > > Algorithm: Non-I2C SMBus adapter
> > > > > > temp:         +0�C  (min =   +4�C, max =   +0�C)
> > > > > > remote_temp:
> > > > > >               +0�C  (min =   +0�C, max =  +60�C)ALARM (N/A)
> > > > > >
> > > > > > eeprom-i2c-0-50
> > > > > > Adapter: SMBus Via Pro adapter at 5000
> > > > > > Algorithm: Non-I2C SMBus adapter
> > > > > > Memory type:            SDRAM DIMM SPD
> > > > > > SDRAM Size (MB):        256
> > > > > >
> > > > > > eeprom-i2c-0-51
> > > > > > Adapter: SMBus Via Pro adapter at 5000
> > > > > > Algorithm: Non-I2C SMBus adapter
> > > > > > Memory type:            SDRAM DIMM SPD
> > > > > > SDRAM Size (MB):        256
> > > > >
> > > > > You aren't loading the ISA drivers.. and you need to.
> > > > >
> > > > > --
> > > > > Chuck Burns, Jr <[EMAIL PROTECTED]
> > > > > -----------==========-----------
> > > > > Thieves respect property; they merely wish the property to become
> > > > > their property that they may more perfectly respect it.
> > > > >               -- G.K. Chesterton, "The Man Who Was Thursday"
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Want to buy your Pack or Services from MandrakeSoft?
> > > > > Go to http://www.mandrakestore.com
> > >
> > > Want to buy your Pack or Services from MandrakeSoft?
> > > Go to http://www.mandrakestore.com
> 
> 

>
> Want to buy your Pack or Services from MandrakeSoft? 
> Go to http://www.mandrakestore.com






-- 
__________________________________________________________
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup

Meet Singles
http://corp.mail.com/lavalife


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com

Reply via email to