[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: lm-sensors

Elimar Riesebieter <riesebie@lxtec.de> writes:
> i just wanted to use lm-sensors to check voltages, temperatures ..

Do you actually have (supported) sensor hardware?  My laptop, for
example, doesn't, though my desktop machine does.

> 1  I installed lm-sensors, lm-sensors-source and i2c-source
> 2  compiled the modules
> 3  Did a lm-sensors detect

Most people lose on step two, it appears.  If you built modules using
'make-kpkg modules-image', did you install the resulting package?  If
you're using sid, 'sudo debian/rules modules-nokpkg' should Just Work
if you're allergic to kernel-package.  If you do in fact have
lm-sensors modules hiding somewhere under /lib/modules/2.4.20, then
you're doing fine at this point.

> but no LMXX was found.

What version of lm-sensors are you using?  I've had minor issues
keeping sensors-detect up-to-date; the current versions in both sid
and sarge should work, though.

> My chipset:
> 00:07.0 ISA bridge: Acer Laboratories Inc. [ALi] M1533 PCI to ISA
> Bridge [Aladdin IV] (rev c3)

There's a claim on http://secure.netroedge.com/~lm78/supported.html
that this is supported by the i2c-ali15x3 driver...

> modprobe i2c-ali15x3 tells:

...oh, but you found that.

> i2c-ali15x3.o version 2.6.4 (20020719)
> i2c-ali15x3.o: Error: Can't detect ali15x3!
> i2c-ali15x3.o: ALI15X3 not detected, module not inserted.
> /lib/modules/2.4.20/misc/i2c-ali15x3.o: init_module: No such device
> Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
>       You may find more information in syslog or the output from dmesg
> /lib/modules/2.4.20/misc/i2c-ali15x3.o: insmod /lib/modules/2.4.20/misc/i2c-ali15x3.o failed
> /lib/modules/2.4.20/misc/i2c-ali15x3.o: insmod i2c-ali15x3 failed
> What did I wrong?

*frown*  From that output, it looks like you've done everything right;
it's possible that the version in unstable will work better for you,
and also that the latest upstream version will work (the upstream
changelog mentions a change to this particular driver).  I'll see if I
can get the new upstream version packaged soon, maybe while I'm home
sick today, but it'll probably be some time before it sees unstable
since I did some black magic to produce modules for stock kernels,
which means new packages in unstable, which means a manual approval wait.

David Maze         dmaze@debian.org      http://people.debian.org/~dmaze/
"Theoretical politics is interesting.  Politicking should be illegal."
	-- Abra Mitchell

Reply to: