From: jwa@fasytek.dk (J. W. Andersen)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] ASUS NCCH-DR confusing 83792 vs. 83627THF
Date: Wed, 14 Jun 2006 16:13:11 +0000 [thread overview]
Message-ID: <44903597.5080609@fasytek.dk> (raw)
In-Reply-To: <44901813.3080703@fasytek.dk>
Hi rudolf, thanks a lot for your quick reply - and for clearing me up
about the chip hidden
in the mulriplexor.
Rudolf Marek wrote:
> It is "hidden" using the multiplexer. Please upgrade to latest BIOS.
> If sensors-detect cannot find it - we have a contact at ASUS and they will fix it.
>
>
BIOS is already version 1005, which is the latest - and presumably
greatest - according to ASUS
download pages. Looks like we need your ASUS contact anyway...
>>
>
> This chip is known to be unused for the fans/temps. You dont need to load this
> driver.
>
>
Duly noted.
>> The other thing that puzzles me: In an X86_64 system, I would expect to
>> find
>> the libsensor libraries in a the /lib64 directory, but they actually get
>> nstalled
>> in /usr/local/lib. What must I do to get these libraries in the proper
>> place ?
>>
>>
>
> # You should not need to change this. It is the directory into which the
>
> # library files (both static and shared) will be installed.
>
> LIBDIR := $(PREFIX)/lib
>
> maybe you can change this to lib64 so the dir will be /usr/local/lib64 but I
> dont know if such directory can exist.
>
> You may also change the PREFIX to / to get it to /lib64 if you like. (all in top
> Makefile)
>
>
Well, I am not sure of the significance of this. Probably the system
will just look in the normal library
path (such as /usr/local/lib) if it cannot find the libraries in
/usr/lib64. Will try to figure that out from here.
Going on standby till you get the news from ASUS - tnx again !
Regards, Joern.
next prev parent reply other threads:[~2006-06-14 16:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-14 14:07 [lm-sensors] ASUS NCCH-DR confusing 83792 vs. 83627THF J. W. Andersen
2006-06-14 15:07 ` Rudolf Marek
2006-06-14 16:04 ` Jean Delvare
2006-06-14 16:13 ` J. W. Andersen [this message]
2006-06-14 16:19 ` J. W. Andersen
2006-06-14 16:20 ` Henrik Brix Andersen
2006-06-26 12:01 ` Rudolf Marek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44903597.5080609@fasytek.dk \
--to=jwa@fasytek.dk \
--cc=lm-sensors@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.