From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: Intel D845GEBV2 with lm85: config is locked
Date: Thu, 19 May 2005 06:24:20 +0000 [thread overview]
Message-ID: <20031002224923.29b5c1ef.khali@linux-fr.org> (raw)
In-Reply-To: <000501c38918$5f227520$fe0aa8c0@freeman>
> I've got an Intel mainboard D845GEBV2 as replacement for my Asus
> P4B-266SE(that ASB100 mess). I've mounted it, gone through the configs
> and sensors-detect said I should use the lm85 driver. With lm85 it
> seem to work well, except I cannot change anything in the proc
> interface. The values reported seem correct but all changes (e.g.
> echoing values to the pwm# registers) are ignored...
This is a feature of the LM85. I remember I read that some times ago.
(reading again) Yes, here it is. Bit 1 of register 0x40 is lock. Once
set to 1, all limits are read only, and that bit itself becomes read
only. And yes, that bit it set to 1 on your chip. Blame your motherboard
manifacturer for that (I guess).
> Intel claims there is an SMSC LPC47M172 on board.
We don't have support for this one yet, but support some members of the
family in the smsc47m1 driver. Maybe you could give it a try (using CVS
version is recommended). They are ISA chips so they don't appear on the
I2C bus.
> Output of syslog
> -----------------------
> Oct 1 20:34:24 elexis kernel: lm85(0): Client (0,0x2e) config is
> locked.
See, that's what I said.
> elexis:~# i2cdetect 0
> 0 1 2 3 4 5 6 7 8 9 a b c d e f
> 00: XX XX XX XX XX XX XX XX 08 XX XX XX XX XX XX XX
> 10: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
> 20: XX XX XX XX XX XX XX XX XX XX XX XX XX XX 2e XX
> 30: 30 XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
> 40: XX XX XX XX 44 XX XX XX XX XX XX XX XX XX XX XX
> 50: 50 XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
> 60: XX XX XX XX XX XX XX XX XX 69 XX XX XX XX XX XX
> 70: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
You did not dump address 0x08. Maybe there's something interesting
there? (Although I admit we don't know any chip living there yet).
> I had to do a cold reset after the use of i2cdetect/dump.
Yes, that happends, especially after dumping address 0x69 which is a
clock chip you should avoid playing with.
> Do you have an idea how to solve that problem?
I am afraid you can't do anything :(
> PS: sorry if I sent it multiple - my posts didn't appear on the list.
Got only one, so it's OK :)
--
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/
next prev parent reply other threads:[~2005-05-19 6:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 6:24 Intel D845GEBV2 with lm85: config is locked Dimitri Puzin
2005-05-19 6:24 ` Philip Pokorny
2005-05-19 6:24 ` Philip Pokorny
2005-05-19 6:24 ` Philip Pokorny
2005-05-19 6:24 ` Dimitri Puzin
2005-05-19 6:24 ` Jean Delvare [this message]
2005-05-19 6:24 ` Jean Delvare
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=20031002224923.29b5c1ef.khali@linux-fr.org \
--to=khali@linux-fr.org \
--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.