Re: lm_sensors and ASUS P4C800-E Deluxe

From: Dave Serls (serls_at_dashs.denver.co.us)
Date: 04/05/04 

Date: Sun, 4 Apr 2004 16:26:03 -0600

On Sun, 04 Apr 2004 10:05:54 -0400
Brendan McEnaney <mcenaney@MYTROUSERSspeakeasy.net> wrote:

> On Sun, 04 Apr 2004 05:25:39 -0500, Kevin D. Snodgrass wrote:
>
> > Brendan McEnaney wrote:
> >> Has anybody gotten lm_sensors going with the ASUS P4C800-E Deluxe
> >> motherboard? If so, I'd love to hear some pointers as to how you did it,
> >
> > No, but lm_sensors works on pretty much all modern (x86)
> > hardware.
>
> Ok. Well that's encouraging.
>
> >> We will now try to load each adapter module in turn.
> >> Load `i2c-i801' (say NO if built into your kernel)? (YES/no): YES
> >> /lib/modules/2.4.22-1.2174.nptlsmp/kernel/drivers/i2c/i2c-i801.o:
> >> init_module: No such device
> >>
> >> /lib/modules/2.4.22-1.2174.nptlsmp/kernel/drivers/i2c/i2c-i801.o most
> >> certainly does exist. I've tried answering "no" above; I've tried
> >> everything. Help greatly appreciated.
> >
> > init_module didn't say it couldn't find i2c-i801.o, is said
> > "No such device". i2c-i801 tried to load and find its
> > hardware, an i801 I presume, but that chip doesn't exist on
> > your motherboard. So what?
>
> Actually, it does. The motherboard manual confirms this. So does the
> sensors-detect script as I stated in my original post:
>
> >> - Probing for PCI bus adapters...
> >> - Use driver `i2c-i801' for device 00:1f.3: Intel 82801EB ICH5
> >> - Probe succesfully concluded.
>
> > And why are you doing each module individually? I just let
> > sensors-detect do its thing, accepting the defaults all the way. Never
> > had a problem (yet).
>
> Sorry. I should have quoted that "We will now try to load each adapter
> module in turn..." part to indicate that it wasn't _me_ saying that, it
> was the sensors-detect script saying that. I just answered (the
> default) YES and got the "No such device" response.
>
> I just tried it again, as you did, letting "sensors-detect do its thing,
> accepting the defaults all the way". When the script completed, it gave me
> the following:
>
> ============ Output from script ==========================================
>
> To make the sensors modules behave correctly, add these lines to
> /etc/modules.conf:
>
> #----cut here----
> # I2C module options
> alias char-major-89 i2c-dev
> #----cut here----
>
> To load everything that is needed, add this to some /etc/rc* file:
>
> #----cut here----
> # I2C adapter drivers
> modprobe i2c-isa
> # I2C chip drivers
> modprobe w83627hf
> # sleep 2 # optional
> /usr/local/bin/sensors -s # recommended
> #----cut here----
> ============= End Output from script =======================================
>
>
> I did this. And (pardon my display of extreme ignorance but) I wasn't sure
> what /etc/rc* file to add the second part to so I put it in /etc/rc.local.
> Also, at the end of the script it says:
>
>
> =============== More output ============================================
> Do you want to generate /etc/sysconfig/lm_sensors? (YES/no): Copy
> prog/init/lm_sensors.init to /etc/rc.d/init.d/lm_sensors for
> initialization at boot time.
> ========================================================================
>
>
> Ok, I answered YES by just hitting ENTER for the default but it doesn't
> seem to have generated the '/etc/sysconfig/lm_sensors'. Also, where the
> heck is 'prog/init/lm_sensors.init'? Where does the path to that
> begin? I can see that the lm_sensors installation put a copy of that
> file here: /usr/share/doc/lm_sensors-2.8.1/lm_sensors.init but I
> assume that that's just a template. Again, pardon my ignorance but I just
> can't get past this point.
>
> The entire output of the sensors-detect script running with me accepting
> all the defaults can be seen here:
>
> http://www.boston-express.com/sd-output
>
> if it helps someone with less knuckles in their head than myself
> extract some clues.
>
> Again, thanks in advance folks for any help.

  I've got the same board, and everything runs fine here. But I don't recall
  exactly what I did.

  On Mandrake 9.2 the install created an lm_sensors script which does the module
  loading and the /etc/sysconfig/lm_sensors file used by it to identify which modules.
  I'm not sure what the netiquette is for providing these files on a newsgroup.
  I can mail them to you or make them available via ftp.
  
 

Relevant Pages

  • Re: lm_sensors and ASUS P4C800-E Deluxe
    ... > was the sensors-detect script saying that. ... And (pardon my display of extreme ignorance but) I wasn't sure ... which has the template script. ...
    (comp.os.linux.hardware)
  • How to use scripting to secure your Win2K network--some examples
    ... Software Installation script: ... The purpose of this script is to ... Let's see how service packs and hotfixes are handled in the script: ... NT4 in the way the local system account accesses network resources. ...
    (NT-Bugtraq)
  • Re: [RFC] Rewriting sade(8)
    ... optionally saved into an executable script) to reproduce everything you ... The way that this worked was by way of the developer "plugging in" ... separate the GUI front-end from the actual tasks that need to be ... for users to select their installation options, ...
    (freebsd-current)
  • Re: [Info-Ingres] jdbc connection problem
    ... Initially you run a setup on a clean machine with the script recording ... I obtained mixed results where there was already an installation present ... @echo starting OpenROAD installation ... Subject: jdbc connection problem ...
    (comp.databases.ingres)
  • Installation of software, and security. . .
    ... installation in Windows and various package managers. ... A setup.exe program coded by some third party such as Real Networks ... A .msi Microsoft Installer package is unpacked, and a script coded by ...
    (Bugtraq)