Andrei Popescu on 07/05/09 07:05, wrote:
On Thu,07.May.09, 00:39:51, Adam Hardy wrote:
I had the exact same problem when I upgraded from sarge to etch but I
lost the grey cells storing the memory of what I did to sort it out.
Looking around the net, I'm not getting much beyond the idea that udev
should be creating something for me that it doesn't want to.
I tried removing and purging the lm-sensors package, but a
re-installation didn't help. I read that I should be running
sensors-detect to re-create the missing config, but when I try,
sensor-detect gives me what looks to be a completely obsolete warning to
"run mkdev.sh" which is a script I don't have, or at least it didn't come
with lm-sensors.
The lm-sensors docs tell me I must have an old version of lm-sensors but
I actually have the latest - I just did the lenny upgrade. So I'm not
sure what's going on.
Any advice?
Shot in the dark: do you have the relevant modules for your sensors
loaded?
I'm fairly sure that running sensors-detect is meant to tell you what modules to
load. So you're probably right - but I need sensors-detect to run properly first
- or maybe I'm misinterpreting what it means:
a...@gondor:~$ sudo sensors-detect
[sudo] password for adam:
No i2c device files found. Use prog/mkdev/mkdev.sh to create them.
a...@gondor:~$
mkdev.sh is obsolete, that's according to the lm-sensors website.
Adam
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
