Re: any gui for lm-sensors?

[0...@caiway.net]

On Thu, 9 Jul 2020 02:52:22 + (UTC)
Long Wind  wrote:

> i want a small app that show cpu temperaturewhich package shall i
> install?Thanks!
> 

psensor if you want a graph and/or remote

the packages are:

psensor is 63 kB,
psensor-common is 43 kB and 
psensor-server is 110 kB

Re: any gui for lm-sensors?

[Gene Heskett]

On Wednesday 08 July 2020 22:52:22 Long Wind wrote:

> i want a small app that show cpu temperaturewhich package shall i
> install?Thanks!

gkrellm and helpers. Small, still shows everything.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: any gui for lm-sensors?

[Long Wind]

 
Thank Charles! 
xsensors seems best for me 
On Thursday, July 9, 2020, 12:10:27 AM EDT, Charles Curley 
 wrote:  
 
 On Thu, 9 Jul 2020 02:52:22 + (UTC)
Long Wind  wrote:

> i want a small app that show cpu temperaturewhich package shall i
> install?Thanks!
> 

Your desktop may have a suitable addon. For XFCE, xfce4-sensors-plugin.
Otherwise, run

apt-cache search sensors

and see if any of that gives you ideas.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

  

Re: any gui for lm-sensors?

[Tu Can]

On [4], 2020-07-09 at 02:52 +, Long Wind wrote:
> i want a small app that show cpu temperature
> which package shall i install?
> Thanks!
> 
conky, as a background of desktop. not only cpu informaiton. Here is my
configuration file[1].

[1]https://github.com/bestucan/conky

Re: any gui for lm-sensors?

[Charles Curley]

On Thu, 9 Jul 2020 02:52:22 + (UTC)
Long Wind  wrote:

> i want a small app that show cpu temperaturewhich package shall i
> install?Thanks!
> 

Your desktop may have a suitable addon. For XFCE, xfce4-sensors-plugin.
Otherwise, run

apt-cache search sensors

and see if any of that gives you ideas.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: any gui for lm-sensors?

[David Christensen]

On 2020-07-08 19:52, Long Wind wrote:

i want a small app that show cpu temperaturewhich package shall i 
install?Thanks!


I use Xfce with the CPU Frequency Monitor, CPU Graph, and Sensor panel 
plug-ins.



David

Re: any gui for lm-sensors?

[Joe Pfeiffer]

Long Wind  writes:

> i want a small app that show cpu temperature
> which package shall i install?
> Thanks!

I've been using gkrellm to show quite a bit of system information
(including temperatures) for years and years now.

Re: lm-sensors doesn't see the cpu rpm.....

[Michael Fothergill]

On 28 December 2017 at 18:14, deloptes  wrote:

> Michael Fothergill wrote:
>
> > I am running stretch on an AMD FX8350 box which uses an Arctic Freezer 13
> > cooler.
>
> I'm just wondering if you used the correct switch for the cpu fan - what is
> your mother board?
>
> also from the gentoo link
>
> $ grep CONFIG_SENSORS_FAM15H_POWER /boot/config-4.12.10
> CONFIG_SENSORS_FAM15H_POWER=m
> grep CONFIG_SENSORS_K10TEMP /boot/config-4.12.10
> CONFIG_SENSORS_K10TEMP=m
>
> $ lsmod | grep temp
> k10temp16384  0
> $ lsmod | grep fam15
> fam15h_power   16384  0
>
> does this apply to your kernel?
>

​I am going to suggest to the asus support folks that I might have
misconnected the cpu fan up to the motherboard.

I already told them that I wasn't sure if I was using a 3 pin instead of a
4 pin lead which might be a limitation here.

The Windows software diagnostics might also give clues to an erroneous mobo
hook up here.

I need to use all the divining rods available on this.

Regards

MF







​


>
> regards
>
>

Re: lm-sensors doesn't see the cpu rpm.....

[Michael Fothergill]

On 28 December 2017 at 18:14, deloptes  wrote:

> Michael Fothergill wrote:
>
> > I am running stretch on an AMD FX8350 box which uses an Arctic Freezer 13
> > cooler.
>
> I'm just wondering if you used the correct switch for the cpu fan - what is
> your mother board?
>
> also from the gentoo link
>
> $ grep CONFIG_SENSORS_FAM15H_POWER /boot/config-4.12.10
> CONFIG_SENSORS_FAM15H_POWER=m
> grep CONFIG_SENSORS_K10TEMP /boot/config-4.12.10
> CONFIG_SENSORS_K10TEMP=m
>
> $ lsmod | grep temp
> k10temp16384  0
> $ lsmod | grep fam15
> fam15h_power   16384  0
>
> does this apply to your kernel?


​Here is the output from lsmod on this:​



> mikef@bong:~$ lsmod | grep fam15
> fam15h_power   16384  0
> mikef@bong:~$ lsmod | grep temp
> k10temp16384  0
> mikef@bong:~$
>
>
​Cheers

MF​



>
> regards
>
>

Re: lm-sensors doesn't see the cpu rpm.....

[Michael Fothergill]

On 28 December 2017 at 18:30, Michael Fothergill <
michael.fotherg...@gmail.com> wrote:

>
>
> On 28 December 2017 at 18:14, deloptes  wrote:
>
>> Michael Fothergill wrote:
>>
>> > I am running stretch on an AMD FX8350 box which uses an Arctic Freezer
>> 13
>> > cooler.
>>
>> I'm just wondering if you used the correct switch for the cpu fan - what
>> is
>> your mother board?
>>
>
> ​This is an interesting idea.  I built the PC myself.  Maybe I connected
> up the CPU fan lead incorrectly..
>

​Wait a minute here...

When I said I build the PC, what I mean is I screwed the motherboard into
the PC and then connected up the 3 case fans to it.

The CPU cooler and FAN were actually attached to the motherboard by the
company I bought the entire motherboard bundle from (ie I purchased the
board, 8GB RAM preinstalled plus the Arctic Freezer
cooler thermal pasted (and baisted - its Christmas remember!) the firm here
in the UK offering it as a job lot.

I can't quite remember if the cpu cooler lead was already attached to the
motherboard at that point - I might have done that bit myself (and maybe
bungled it - you could be on the money here).

So some thought and imagination could be required here.​

​MF​


> The motherboard is an ASUS FX 990 Sabertooth R2.0; the bios version is
> 2501.
>
> Here is some of the info sent to the ASUS support folks:
>
> [Product Information]
> Product Type : Motherboard
> Product Model : SABERTOOTH 990FX R2.0
> Product S/N : EAM0BX019177
> Operation System / Firmware or BIOS version : Debian 9 (Linuc) OS/Bios
> that came with product
>
> [Graphics Card Vendor/model/Chipset/Driver]
> Nvidia engt 430 model
>
> [CPU vendor/processor number]
> AMD FX 8350
>
> [Memory vendor/model/specification]
> Memory Vengeance LP Upgrade: Corsair 8GB 1600Mhz Vengeance LP DDR3​
>
>
>>
>> also from the gentoo link
>>
>> $ grep CONFIG_SENSORS_FAM15H_POWER /boot/config-4.12.10
>> CONFIG_SENSORS_FAM15H_POWER=m
>> grep CONFIG_SENSORS_K10TEMP /boot/config-4.12.10
>> CONFIG_SENSORS_K10TEMP=m
>>
>> $ lsmod | grep temp
>> k10temp16384  0
>> $ lsmod | grep fam15
>> fam15h_power   16384  0
>>
>> does this apply to your kernel?
>>
>
> ​I will login to the machine, fire up debian and run
>
> lsmod | grep temp
>
> and
>
> lsmod | grep fam 15
>
> and get you the output.
>
> I think fam15 module is installed - check the lsmod output I already
> posted.
>
> Please let me know any other commands/diagnostics you want running here.
>
> Regards and thanks.
>
> Michael Fothergill
>
> ​
>
>
>
>
>>
>> regards
>>
>>
>

Re: lm-sensors doesn't see the cpu rpm.....

[Michael Fothergill]

On 28 December 2017 at 18:14, deloptes  wrote:

> Michael Fothergill wrote:
>
> > I am running stretch on an AMD FX8350 box which uses an Arctic Freezer 13
> > cooler.
>
> I'm just wondering if you used the correct switch for the cpu fan - what is
> your mother board?
>

​This is an interesting idea.  I built the PC myself.  Maybe I connected up
the CPU fan lead incorrectly..

The motherboard is an ASUS FX 990 Sabertooth R2.0; the bios version is 2501.

Here is some of the info sent to the ASUS support folks:

[Product Information]
Product Type : Motherboard
Product Model : SABERTOOTH 990FX R2.0
Product S/N : EAM0BX019177
Operation System / Firmware or BIOS version : Debian 9 (Linuc) OS/Bios that
came with product

[Graphics Card Vendor/model/Chipset/Driver]
Nvidia engt 430 model

[CPU vendor/processor number]
AMD FX 8350

[Memory vendor/model/specification]
Memory Vengeance LP Upgrade: Corsair 8GB 1600Mhz Vengeance LP DDR3​


>
> also from the gentoo link
>
> $ grep CONFIG_SENSORS_FAM15H_POWER /boot/config-4.12.10
> CONFIG_SENSORS_FAM15H_POWER=m
> grep CONFIG_SENSORS_K10TEMP /boot/config-4.12.10
> CONFIG_SENSORS_K10TEMP=m
>
> $ lsmod | grep temp
> k10temp16384  0
> $ lsmod | grep fam15
> fam15h_power   16384  0
>
> does this apply to your kernel?
>

​I will login to the machine, fire up debian and run

lsmod | grep temp

and

lsmod | grep fam 15

and get you the output.

I think fam15 module is installed - check the lsmod output I already posted.

Please let me know any other commands/diagnostics you want running here.

Regards and thanks.

Michael Fothergill

​




>
> regards
>
>

Re: lm-sensors doesn't see the cpu rpm.....

[deloptes]

Michael Fothergill wrote:

> I am running stretch on an AMD FX8350 box which uses an Arctic Freezer 13
> cooler.

I'm just wondering if you used the correct switch for the cpu fan - what is
your mother board?

also from the gentoo link

$ grep CONFIG_SENSORS_FAM15H_POWER /boot/config-4.12.10
CONFIG_SENSORS_FAM15H_POWER=m
grep CONFIG_SENSORS_K10TEMP /boot/config-4.12.10
CONFIG_SENSORS_K10TEMP=m

$ lsmod | grep temp
k10temp16384  0
$ lsmod | grep fam15
fam15h_power   16384  0

does this apply to your kernel?

regards

Re: lm-sensors doesn't see the cpu rpm.....

[Michael Fothergill]

On 28 December 2017 at 13:55, Greg Wooledge  wrote:

> On Thu, Dec 28, 2017 at 01:11:56PM +, Michael Fothergill wrote:
> > root@bong:/boot#  sudo modprobe coretemp
> > modprobe: ERROR: could not insert 'coretemp': No such device
> >
> >
> > This is odd because coretemp is set as a module option in the config
> file:
> >
> > CONFIG_SENSORS_CORETEMP=m
> >
> > Comments appreciared
>
> Well, it *should* work with a standard Debian kernel and applicable
> hardware.
>

​Dear All,

It's sad but I think I need install Windows 10 on this machine to sort out
the fan control and cpu cooler problems.

This machine overheats when I run pov-ray benchmark on it and shuts down.

see here (first page only)

https://forums.gentoo.org/viewtopic-t-1056576-start-0.html


Then I can install the ASUS Fan Xpert and ROG software etc on top of the FX
990 sabertooth motherboard I have...

I think I might need to change the thermal paste compound between the CPU
and Arctic Freezer 13 heatsink to cure the cooling problem.

I am going to use Artic MX-4 paste.

While Debian and Gentoo are OK to work with here, I cannot tolerate the
machine shutting down now and again due to overheating any longer.

I am corresponding with the ASUS technical folks at present.

I need the extra special bloodhound Passau Cathedral Organ factor here to
help check on the temps and the fan activity once I start doing
surgery on the cpu/fan-heatsink thermal interface...

CPUs cost money.

Thanks for the help to date.

Regards

MF



​


>
> wooledg:~$ /sbin/modinfo coretemp
> filename:   /lib/modules/4.9.0-4-amd64/kernel/drivers/hwmon/coretemp.
> ko
> license:GPL
> description:Intel Core temperature monitor
> author: Rudolf Marek 
> alias:  cpu:type:x86,venfam*mod*:feature:*01C0*
> depends:
> intree: Y
> vermagic:   4.9.0-4-amd64 SMP mod_unload modversions
> parm:   tjmax:TjMax value in degrees Celsius (int)
>
> Your "No such device" error sounds like it probed for hardware and didn't
> find any.  If the module itself were missing from the file system, then
> I would have expected "FATAL: Module coretemp not found in directory ...".
>
> It says "Intel" in the description.  Are you using an Intel CPU?
>
>

Re: lm-sensors doesn't see the cpu rpm.....

[Michael Fothergill]

On 28 December 2017 at 13:55, Greg Wooledge  wrote:

> On Thu, Dec 28, 2017 at 01:11:56PM +, Michael Fothergill wrote:
> > root@bong:/boot#  sudo modprobe coretemp
> > modprobe: ERROR: could not insert 'coretemp': No such device
> >
> >
> > This is odd because coretemp is set as a module option in the config
> file:
> >
> > CONFIG_SENSORS_CORETEMP=m
> >
> > Comments appreciared
>
> Well, it *should* work with a standard Debian kernel and applicable
> hardware.
>

​If you look here:

https://askubuntu.com/questions/748615/lm-sensors-not-returning-cpu-temp-it87

it says that You need to append acpi_enforce_resources=lax at the end of
> the line GRUB_CMDLINE_LINUX
>
​in /etc/default/grub to make e.g. the it87 module work for the FX8350 chip
AFAICT

BUT

If you look at my /etc/default/grub:

root@bong:/etc/default# more grub
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX="initrd=/install/initrd.gz"

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to
Linux
#GRUB_DISABLE_LINUX_UUID=true


# Uncomment to disable generation of recovery mode menu
entries
#GRUB_DISABLE_RECOVERY="true"



# Uncomment to get a beep at grub
start
#GRUB_INIT_TUNE="480 440
1"
root@bong:/etc/default#


​I don't have any acpi command in there but lsmod does list it87 as a
module for my install:

​root@bong:/etc/default# lsmod | grep it87
it87   57344
0
hwmon_vid  16384  1 it87


Does it need to have a 1 not a zero in there for the it87 to actually be
working even if it is installed?

Cheers

MF









>
> wooledg:~$ /sbin/modinfo coretemp
> filename:   /lib/modules/4.9.0-4-amd64/kernel/drivers/hwmon/coretemp.
> ko
> license:GPL
> description:Intel Core temperature monitor
> author: Rudolf Marek 
> alias:  cpu:type:x86,venfam*mod*:feature:*01C0*
> depends:
> intree: Y
> vermagic:   4.9.0-4-amd64 SMP mod_unload modversions
> parm:   tjmax:TjMax value in degrees Celsius (int)
>
> Your "No such device" error sounds like it probed for hardware and didn't
> find any.  If the module itself were missing from the file system, then
> I would have expected "FATAL: Module coretemp not found in directory ...".
>
> It says "Intel" in the description.  Are you using an Intel CPU?
>
>

Re: lm-sensors doesn't see the cpu rpm.....

[Michael Fothergill]

On 28 December 2017 at 13:55, Greg Wooledge  wrote:

> On Thu, Dec 28, 2017 at 01:11:56PM +, Michael Fothergill wrote:
> > root@bong:/boot#  sudo modprobe coretemp
> > modprobe: ERROR: could not insert 'coretemp': No such device
> >
> >
> > This is odd because coretemp is set as a module option in the config
> file:
> >
> > CONFIG_SENSORS_CORETEMP=m
> >
> > Comments appreciared
>
> Well, it *should* work with a standard Debian kernel and applicable
> hardware.
>
> wooledg:~$ /sbin/modinfo coretemp
> filename:   /lib/modules/4.9.0-4-amd64/kernel/drivers/hwmon/coretemp.
> ko
> license:GPL
> description:Intel Core temperature monitor
> author: Rudolf Marek 
> alias:  cpu:type:x86,venfam*mod*:feature:*01C0*
> depends:
> intree: Y
> vermagic:   4.9.0-4-amd64 SMP mod_unload modversions
> parm:   tjmax:TjMax value in degrees Celsius (int)
>
> Your "No such device" error sounds like it probed for hardware and didn't
> find any.  If the module itself were missing from the file system, then
> I would have expected "FATAL: Module coretemp not found in directory ...".
>
> It says "Intel" in the description.  Are you using an Intel CPU?
>

​I now realise that coretemp only works with Intel chips not AMD ones

Ooops!

I will look up module names that work for the FX 8350 and see of I can find
any that are not listed in lsmod and try installing them
with modprobe.

Cheers

MF​

Re: lm-sensors doesn't see the cpu rpm.....

[Michael Fothergill]

On 28 December 2017 at 13:55, Greg Wooledge  wrote:

> On Thu, Dec 28, 2017 at 01:11:56PM +, Michael Fothergill wrote:
> > root@bong:/boot#  sudo modprobe coretemp
> > modprobe: ERROR: could not insert 'coretemp': No such device
> >
> >
> > This is odd because coretemp is set as a module option in the config
> file:
> >
> > CONFIG_SENSORS_CORETEMP=m
> >
> > Comments appreciared
>
> Well, it *should* work with a standard Debian kernel and applicable
> hardware.
>

​The output of lspci is here:
https://pastebin.com/AAXTq8Uh
​


>
> wooledg:~$ /sbin/modinfo coretemp
> filename:   /lib/modules/4.9.0-4-amd64/kernel/drivers/hwmon/coretemp.
> ko
> license:GPL
> description:Intel Core temperature monitor
> author: Rudolf Marek 
> alias:  cpu:type:x86,venfam*mod*:feature:*01C0*
> depends:
> intree: Y
> vermagic:   4.9.0-4-amd64 SMP mod_unload modversions
> parm:   tjmax:TjMax value in degrees Celsius (int)
>
> Your "No such device" error sounds like it probed for hardware and didn't
> find any.  If the module itself were missing from the file system, then
> I would have expected "FATAL: Module coretemp not found in directory ...".
>
> It says "Intel" in the description.  Are you using an Intel CPU?
>
>

Re: lm-sensors doesn't see the cpu rpm.....

[Michael Fothergill]

On 28 December 2017 at 13:55, Greg Wooledge  wrote:

> On Thu, Dec 28, 2017 at 01:11:56PM +, Michael Fothergill wrote:
> > root@bong:/boot#  sudo modprobe coretemp
> > modprobe: ERROR: could not insert 'coretemp': No such device
> >
> >
> > This is odd because coretemp is set as a module option in the config
> file:
> >
> > CONFIG_SENSORS_CORETEMP=m
> >
> > Comments appreciared
>
> Well, it *should* work with a standard Debian kernel and applicable
> hardware.
>

​Perhaps you could suggest some other module names I could try to turn on
using
the modprobe command that I do not have turned on at present based on the
lsmod output.

​Maybe one or to might work.

Cheers

MF



>
> wooledg:~$ /sbin/modinfo coretemp
> filename:   /lib/modules/4.9.0-4-amd64/kernel/drivers/hwmon/coretemp.
> ko
> license:GPL
> description:Intel Core temperature monitor
> author: Rudolf Marek 
> alias:  cpu:type:x86,venfam*mod*:feature:*01C0*
> depends:
> intree: Y
> vermagic:   4.9.0-4-amd64 SMP mod_unload modversions
> parm:   tjmax:TjMax value in degrees Celsius (int)
>
> Your "No such device" error sounds like it probed for hardware and didn't
> find any.  If the module itself were missing from the file system, then
> I would have expected "FATAL: Module coretemp not found in directory ...".
>
> It says "Intel" in the description.  Are you using an Intel CPU?
>

Re: lm-sensors doesn't see the cpu rpm.....

[Michael Fothergill]

On 28 December 2017 at 13:55, Greg Wooledge  wrote:

> On Thu, Dec 28, 2017 at 01:11:56PM +, Michael Fothergill wrote:
> > root@bong:/boot#  sudo modprobe coretemp
> > modprobe: ERROR: could not insert 'coretemp': No such device
> >
> >
> > This is odd because coretemp is set as a module option in the config
> file:
> >
> > CONFIG_SENSORS_CORETEMP=m
> >
> > Comments appreciared
>
> Well, it *should* work with a standard Debian kernel and applicable
> hardware.
>
> wooledg:~$ /sbin/modinfo coretemp
> filename:   /lib/modules/4.9.0-4-amd64/kernel/drivers/hwmon/coretemp.
> ko
> license:GPL
> description:Intel Core temperature monitor
> author: Rudolf Marek 
> alias:  cpu:type:x86,venfam*mod*:feature:*01C0*
> depends:
> intree: Y
> vermagic:   4.9.0-4-amd64 SMP mod_unload modversions
> parm:   tjmax:TjMax value in degrees Celsius (int)
>
> Your "No such device" error sounds like it probed for hardware and didn't
> find any.  If the module itself were missing from the file system, then
> I would have expected "FATAL: Module coretemp not found in directory ...".
>


> It says "Intel" in the description.  Are you using an Intel CPU?
>

​Here is the output of lscpu:​


​root@bong:/home/mikef# lscpu
Architecture:  x86_64
CPU op-mode(s):32-bit, 64-bit
Byte Order:Little Endian
CPU(s):8
On-line CPU(s) list:   0-7
Thread(s) per core:2
Core(s) per socket:4
Socket(s): 1
NUMA node(s):  1
Vendor ID: AuthenticAMD
CPU family:21
Model: 2
Model name:AMD FX(tm)-8350 Eight-Core Processor
Stepping:  0
CPU MHz:   4334.834
BogoMIPS:  8669.66
Virtualization:AMD-V
L1d cache: 16K
L1i cache: 64K
L2 cache:  2048K
L3 cache:  8192K
NUMA node0 CPU(s): 0-7
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt
pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid
aperfmperf eagerfpu pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2
popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic cr8_legacy abm
sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce
nodeid_msr tbm topoext perfctr_core perfctr_nb cpb hw_pstate vmmcall bmi1
arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid
decodeassists pausefilter pfthreshold
root@bong:/home/mikef#
​

​It looks like an FX8350 chip to me.

Comments appreciated

Regards

MF​
​

Re: lm-sensors doesn't see the cpu rpm.....

[Greg Wooledge]

On Thu, Dec 28, 2017 at 01:11:56PM +, Michael Fothergill wrote:
> root@bong:/boot#  sudo modprobe coretemp
> modprobe: ERROR: could not insert 'coretemp': No such device
> 
> 
> This is odd because coretemp is set as a module option in the config file:
> 
> CONFIG_SENSORS_CORETEMP=m
> 
> Comments appreciared

Well, it *should* work with a standard Debian kernel and applicable
hardware.

wooledg:~$ /sbin/modinfo coretemp
filename:   /lib/modules/4.9.0-4-amd64/kernel/drivers/hwmon/coretemp.ko
license:GPL
description:Intel Core temperature monitor
author: Rudolf Marek 
alias:  cpu:type:x86,venfam*mod*:feature:*01C0*
depends:
intree: Y
vermagic:   4.9.0-4-amd64 SMP mod_unload modversions 
parm:   tjmax:TjMax value in degrees Celsius (int)

Your "No such device" error sounds like it probed for hardware and didn't
find any.  If the module itself were missing from the file system, then
I would have expected "FATAL: Module coretemp not found in directory ...".

It says "Intel" in the description.  Are you using an Intel CPU?

Re: lm-sensors doesn't see the cpu rpm.....

[Michael Fothergill]

> CONFIG_SENSORS_ATXP1=m
> CONFIG_SENSORS_DS620=m
> CONFIG_SENSORS_DS1621=m
> CONFIG_SENSORS_DELL_SMM=m
> CONFIG_SENSORS_I5K_AMB=m
> CONFIG_SENSORS_F71805F=m
> CONFIG_SENSORS_F71882FG=m
> CONFIG_SENSORS_F75375S=m
> CONFIG_SENSORS_FSCHMD=m
> CONFIG_SENSORS_FTSTEUTATES=m
> CONFIG_SENSORS_GL518SM=m
> CONFIG_SENSORS_GL520SM=m
> CONFIG_SENSORS_G760A=m
> # CONFIG_SENSORS_G762 is not set
> # CONFIG_SENSORS_GPIO_FAN is not set
> # CONFIG_SENSORS_HIH6130 is not set
> CONFIG_SENSORS_IBMAEM=m
> CONFIG_SENSORS_IBMPEX=m
> # CONFIG_SENSORS_IIO_HWMON is not set
> CONFIG_SENSORS_I5500=m
> CONFIG_SENSORS_CORETEMP=m
> CONFIG_SENSORS_IT87=m
> CONFIG_SENSORS_JC42=m
> # CONFIG_SENSORS_POWR1220 is not set
> CONFIG_SENSORS_LINEAGE=m
> # CONFIG_SENSORS_LTC2945 is not set
> # CONFIG_SENSORS_LTC2990 is not set
> CONFIG_SENSORS_LTC4151=m
> CONFIG_SENSORS_LTC4215=m
> # CONFIG_SENSORS_LTC4222 is not set
> CONFIG_SENSORS_LTC4245=m
> # CONFIG_SENSORS_LTC4260 is not set
> CONFIG_SENSORS_LTC4261=m
> CONFIG_SENSORS_MAX=m
> CONFIG_SENSORS_MAX16065=m
> CONFIG_SENSORS_MAX1619=m
> CONFIG_SENSORS_MAX1668=m
> # CONFIG_SENSORS_MAX197 is not set
> # CONFIG_SENSORS_MAX31722 is not set
> CONFIG_SENSORS_MAX6639=m
> CONFIG_SENSORS_MAX6642=m
> CONFIG_SENSORS_MAX6650=m
> # CONFIG_SENSORS_MAX6697 is not set
> # CONFIG_SENSORS_MAX31790 is not set
> # CONFIG_SENSORS_MCP3021 is not set
> CONFIG_SENSORS_MENF21BMC_HWMON=m
> CONFIG_SENSORS_ADCXX=m
> CONFIG_SENSORS_LM63=m
> CONFIG_SENSORS_LM70=m
> CONFIG_SENSORS_LM73=m
> CONFIG_SENSORS_LM75=m
> CONFIG_SENSORS_LM77=m
> CONFIG_SENSORS_LM78=m
> CONFIG_SENSORS_LM80=m
> CONFIG_SENSORS_LM83=m
> CONFIG_SENSORS_LM85=m
> CONFIG_SENSORS_LM87=m
> CONFIG_SENSORS_LM90=m
> CONFIG_SENSORS_LM92=m
> CONFIG_SENSORS_LM93=m
> # CONFIG_SENSORS_LM95234 is not set
> CONFIG_SENSORS_LM95241=m
> CONFIG_SENSORS_LM95245=m
> CONFIG_SENSORS_PC87360=m
> CONFIG_SENSORS_PC87427=m
> CONFIG_SENSORS_NTC_THERMISTOR=m
> CONFIG_SENSORS_NCT6683=m
> CONFIG_SENSORS_NCT6775=m
> # CONFIG_SENSORS_NCT7802 is not set
> # CONFIG_SENSORS_NCT7904 is not set
> CONFIG_SENSORS_PCF8591=m
> # CONFIG_PMBUS is not set
> # CONFIG_SENSORS_SHT15 is not set
> CONFIG_SENSORS_SHT21=m
> # CONFIG_SENSORS_SHT3x is not set
> # CONFIG_SENSORS_SHTC1 is not set
> CONFIG_SENSORS_SIS5595=m
> CONFIG_SENSORS_DME1737=m
> CONFIG_SENSORS_EMC1403=m
> CONFIG_SENSORS_EMC2103=m
> CONFIG_SENSORS_EMC6W201=m
> CONFIG_SENSORS_SMSC47M1=m
> CONFIG_SENSORS_SMSC47M192=m
> CONFIG_SENSORS_SMSC47B397=m
> CONFIG_SENSORS_SCH56XX_COMMON=m
> CONFIG_SENSORS_SCH5627=m
> CONFIG_SENSORS_SCH5636=m
> CONFIG_SENSORS_SMM665=m
> # CONFIG_SENSORS_ADC128D818 is not set
> CONFIG_SENSORS_ADS1015=m
> CONFIG_SENSORS_ADS7828=m
> CONFIG_SENSORS_ADS7871=m
> CONFIG_SENSORS_AMC6821=m
> # CONFIG_SENSORS_INA209 is not set
> # CONFIG_SENSORS_INA2XX is not set
> # CONFIG_SENSORS_INA3221 is not set
> # CONFIG_SENSORS_TC74 is not set
> CONFIG_SENSORS_THMC50=m
> CONFIG_SENSORS_TMP102=m
> # CONFIG_SENSORS_TMP103 is not set
> CONFIG_SENSORS_TMP401=m
> CONFIG_SENSORS_TMP421=m
> CONFIG_SENSORS_VIA_CPUTEMP=m
> CONFIG_SENSORS_VIA686A=m
> CONFIG_SENSORS_VT1211=m
> CONFIG_SENSORS_VT8231=m
> CONFIG_SENSORS_W83781D=m
> CONFIG_SENSORS_W83791D=m
> CONFIG_SENSORS_W83792D=m
> CONFIG_SENSORS_W83793=m
> CONFIG_SENSORS_W83795=m
> # CONFIG_SENSORS_W83795_FANCTRL is not set
> CONFIG_SENSORS_W83L785TS=m
> CONFIG_SENSORS_W83L786NG=m
> CONFIG_SENSORS_W83627HF=m
> CONFIG_SENSORS_W83627EHF=m
>
> It seems that the kernel is configured with the module m setting
> consistently not the internal y setting so debian does not use the built in
> option by default here it would seem
>
> - see discussion here
>
> https://www.linux.com/learn/intro-to-linux/2017/9/
> advanced-lm-sensors-tips-and-tricks-linux-0
>
> so modifying the /etc/modules file works here.
>
> I notice that
> # CONFIG_SENSORS_W83795_FANCTRL is not set
> has been commented out
>
> and
>
> # CONFIG_SENSORS_GPIO_FAN is not set
>
> is in a similar state
>
> I will continue looking at this in more detail.
>
> Regards
>
> MF
>
>
>
>
>
>
>
>
>
>
>
> On 28 December 2017 at 12:14, Michael Fothergill <
> michael.fotherg...@gmail.com> wrote:
>
>> I have 3 case fans in the box here but lm-sensors only sees two of them
>> apparently as well as not seeing the cpu fan.
>>
>> Funny stuff.
>>
>> Regards
>>
>> MF
>>
>> On 28 December 2017 at 11:50, Michael Fothergill <
>> michael.fotherg...@gmail.com> wrote:
>>
>>> Dear Folks,
>>>
>>>

Re: lm-sensors doesn't see the cpu rpm.....

[Michael Fothergill]

Dear All,

I looked at the config-4.9.0-4-amd64 file for the current kernel:

# Native drivers
#
CONFIG_SENSORS_ABITUGURU=m
CONFIG_SENSORS_ABITUGURU3=m
# CONFIG_SENSORS_AD7314 is not set
CONFIG_SENSORS_AD7414=m
CONFIG_SENSORS_AD7418=m
CONFIG_SENSORS_ADM1021=m
CONFIG_SENSORS_ADM1025=m
CONFIG_SENSORS_ADM1026=m
CONFIG_SENSORS_ADM1029=m
CONFIG_SENSORS_ADM1031=m
CONFIG_SENSORS_ADM9240=m
# CONFIG_SENSORS_ADT7310 is not set
# CONFIG_SENSORS_ADT7410 is not set
CONFIG_SENSORS_ADT7411=m
CONFIG_SENSORS_ADT7462=m
CONFIG_SENSORS_ADT7470=m
CONFIG_SENSORS_ADT7475=m
CONFIG_SENSORS_ASC7621=m
CONFIG_SENSORS_K8TEMP=m
CONFIG_SENSORS_K10TEMP=m
CONFIG_SENSORS_FAM15H_POWER=m
CONFIG_SENSORS_APPLESMC=m
CONFIG_SENSORS_ASB100=m
CONFIG_SENSORS_ATXP1=m
CONFIG_SENSORS_DS620=m
CONFIG_SENSORS_DS1621=m
CONFIG_SENSORS_DELL_SMM=m
CONFIG_SENSORS_I5K_AMB=m
CONFIG_SENSORS_F71805F=m
CONFIG_SENSORS_F71882FG=m
CONFIG_SENSORS_F75375S=m
CONFIG_SENSORS_FSCHMD=m
CONFIG_SENSORS_FTSTEUTATES=m
CONFIG_SENSORS_GL518SM=m
CONFIG_SENSORS_GL520SM=m
CONFIG_SENSORS_G760A=m
# CONFIG_SENSORS_G762 is not set
# CONFIG_SENSORS_GPIO_FAN is not set
# CONFIG_SENSORS_HIH6130 is not set
CONFIG_SENSORS_IBMAEM=m
CONFIG_SENSORS_IBMPEX=m
# CONFIG_SENSORS_IIO_HWMON is not set
CONFIG_SENSORS_I5500=m
CONFIG_SENSORS_CORETEMP=m
CONFIG_SENSORS_IT87=m
CONFIG_SENSORS_JC42=m
# CONFIG_SENSORS_POWR1220 is not set
CONFIG_SENSORS_LINEAGE=m
# CONFIG_SENSORS_LTC2945 is not set
# CONFIG_SENSORS_LTC2990 is not set
CONFIG_SENSORS_LTC4151=m
CONFIG_SENSORS_LTC4215=m
# CONFIG_SENSORS_LTC4222 is not set
CONFIG_SENSORS_LTC4245=m
# CONFIG_SENSORS_LTC4260 is not set
CONFIG_SENSORS_LTC4261=m
CONFIG_SENSORS_MAX=m
CONFIG_SENSORS_MAX16065=m
CONFIG_SENSORS_MAX1619=m
CONFIG_SENSORS_MAX1668=m
# CONFIG_SENSORS_MAX197 is not set
# CONFIG_SENSORS_MAX31722 is not set
CONFIG_SENSORS_MAX6639=m
CONFIG_SENSORS_MAX6642=m
CONFIG_SENSORS_MAX6650=m
# CONFIG_SENSORS_MAX6697 is not set
# CONFIG_SENSORS_MAX31790 is not set
# CONFIG_SENSORS_MCP3021 is not set
CONFIG_SENSORS_MENF21BMC_HWMON=m
CONFIG_SENSORS_ADCXX=m
CONFIG_SENSORS_LM63=m
CONFIG_SENSORS_LM70=m
CONFIG_SENSORS_LM73=m
CONFIG_SENSORS_LM75=m
CONFIG_SENSORS_LM77=m
CONFIG_SENSORS_LM78=m
CONFIG_SENSORS_LM80=m
CONFIG_SENSORS_LM83=m
CONFIG_SENSORS_LM85=m
CONFIG_SENSORS_LM87=m
CONFIG_SENSORS_LM90=m
CONFIG_SENSORS_LM92=m
CONFIG_SENSORS_LM93=m
# CONFIG_SENSORS_LM95234 is not set
CONFIG_SENSORS_LM95241=m
CONFIG_SENSORS_LM95245=m
CONFIG_SENSORS_PC87360=m
CONFIG_SENSORS_PC87427=m
CONFIG_SENSORS_NTC_THERMISTOR=m
CONFIG_SENSORS_NCT6683=m
CONFIG_SENSORS_NCT6775=m
# CONFIG_SENSORS_NCT7802 is not set
# CONFIG_SENSORS_NCT7904 is not set
CONFIG_SENSORS_PCF8591=m
# CONFIG_PMBUS is not set
# CONFIG_SENSORS_SHT15 is not set
CONFIG_SENSORS_SHT21=m
# CONFIG_SENSORS_SHT3x is not set
# CONFIG_SENSORS_SHTC1 is not set
CONFIG_SENSORS_SIS5595=m
CONFIG_SENSORS_DME1737=m
CONFIG_SENSORS_EMC1403=m
CONFIG_SENSORS_EMC2103=m
CONFIG_SENSORS_EMC6W201=m
CONFIG_SENSORS_SMSC47M1=m
CONFIG_SENSORS_SMSC47M192=m
CONFIG_SENSORS_SMSC47B397=m
CONFIG_SENSORS_SCH56XX_COMMON=m
CONFIG_SENSORS_SCH5627=m
CONFIG_SENSORS_SCH5636=m
CONFIG_SENSORS_SMM665=m
# CONFIG_SENSORS_ADC128D818 is not set
CONFIG_SENSORS_ADS1015=m
CONFIG_SENSORS_ADS7828=m
CONFIG_SENSORS_ADS7871=m
CONFIG_SENSORS_AMC6821=m
# CONFIG_SENSORS_INA209 is not set
# CONFIG_SENSORS_INA2XX is not set
# CONFIG_SENSORS_INA3221 is not set
# CONFIG_SENSORS_TC74 is not set
CONFIG_SENSORS_THMC50=m
CONFIG_SENSORS_TMP102=m
# CONFIG_SENSORS_TMP103 is not set
CONFIG_SENSORS_TMP401=m
CONFIG_SENSORS_TMP421=m
CONFIG_SENSORS_VIA_CPUTEMP=m
CONFIG_SENSORS_VIA686A=m
CONFIG_SENSORS_VT1211=m
CONFIG_SENSORS_VT8231=m
CONFIG_SENSORS_W83781D=m
CONFIG_SENSORS_W83791D=m
CONFIG_SENSORS_W83792D=m
CONFIG_SENSORS_W83793=m
CONFIG_SENSORS_W83795=m
# CONFIG_SENSORS_W83795_FANCTRL is not set
CONFIG_SENSORS_W83L785TS=m
CONFIG_SENSORS_W83L786NG=m
CONFIG_SENSORS_W83627HF=m
CONFIG_SENSORS_W83627EHF=m

It seems that the kernel is configured with the module m setting
consistently not the internal y setting so debian does not use the built in
option by default here it would seem

- see discussion here

https://www.linux.com/learn/intro-to-linux/2017/9/advanced-lm-sensors-tips-and-tricks-linux-0

so modifying the /etc/modules file works here.

I notice that
# CONFIG_SENSORS_W83795_FANCTRL is not set
has been commented out

and

# CONFIG_SENSORS_GPIO_FAN is not set

is in a similar state

I will continue looking at this in more detail.

Regards

MF











On 28 December 2017 at 12:14, Michael Fothergill <
michael.fotherg...@gmail.com> wrote:

> I have 3 case fans in the box here but lm-sensors only sees two of them
> apparently as well as not seeing the cpu fan.
>
> Funny stuff.
>
> Regards
>
> MF
>
> On 28 December 2017 at 11:50, Michael Fothergill <
> michael.fotherg...@gmail.com> wrote:
>
>> Dear Folks,
>>
>> I am running stretch on an AMD FX8350 box which uses an Arctic Freezer 13
>> cooler.
>>
>> I inst

Re: lm-sensors doesn't see the cpu rpm.....

[Michael Fothergill]

I have 3 case fans in the box here but lm-sensors only sees two of them
apparently as well as not seeing the cpu fan.

Funny stuff.

Regards

MF

On 28 December 2017 at 11:50, Michael Fothergill <
michael.fotherg...@gmail.com> wrote:

> Dear Folks,
>
> I am running stretch on an AMD FX8350 box which uses an Arctic Freezer 13
> cooler.
>
> I installed lm-sensors and ran the /etc module update command.
>
> The output looks like this:
>
> root@bong:/home/mikef# sensors
> asus-isa-
> Adapter: ISA adapter
> cpu_fan:0 RPM
>
> k10temp-pci-00c3
> Adapter: PCI adapter
> temp1:+21.9°C  (high = +70.0°C)
>(crit = +90.0°C, hyst = +87.0°C)
>
> nouveau-pci-0700
> Adapter: PCI adapter
> GPU core: +0.90 V  (min =  +0.88 V, max =  +1.08 V)
> temp1:+35.0°C  (high = +95.0°C, hyst =  +3.0°C)
>(crit = +105.0°C, hyst =  +5.0°C)
>(emerg = +135.0°C, hyst =  +5.0°C)
>
> fam15h_power-pci-00c4
> Adapter: PCI adapter
> power1:6.75 W  (crit = 125.19 W)
>
>
> it8721-isa-0290
>
> Adapter: ISA adapter
>
> in0:  +2.83 V  (min =  +2.02 V, max =  +2.95
> V)
> in1:  +2.83 V  (min =  +1.68 V, max =  +1.73 V)
> ALARM
> in2:  +0.98 V  (min =  +2.40 V, max =  +1.08 V)
> ALARM
> +3.3V:+3.31 V  (min =  +0.38 V, max =  +0.96 V)
> ALARM
> in4:  +0.25 V  (min =  +0.41 V, max =  +0.20 V)  ALARM
> in5:  +2.51 V  (min =  +0.12 V, max =  +0.00 V)  ALARM
> in6:  +1.98 V  (min =  +1.54 V, max =  +0.59 V)  ALARM
> 3VSB: +3.94 V  (min =  +3.31 V, max =  +0.89 V)  ALARM
> Vbat: +3.29 V
> fan1:1814 RPM  (min =   87 RPM)
> fan2:   0 RPM  (min =   46 RPM)  ALARM
> fan3:1125 RPM  (min =   29 RPM)
> temp1:+37.0°C  (low  = +34.0°C, high = +91.0°C)  sensor =
> thermistor
> temp2:+30.0°C  (low  = +45.0°C, high =  +9.0°C)  ALARM  sensor =
> thermistor
> temp3:   -128.0°C  (low  = -60.0°C, high =  +4.0°C)  sensor = disabled
> intrusion0:  OK
>
> root@bong:/home/mikef#
>
> The cpu fan is running at around 2500 rpm.
>
> If the connector were 3 pin rather than 4 pin could that explain the zero
> here?
>
> Suggestions on a tweak that could awaken the sensor or stimulate
> lm-sensors truffle hound hunting skills here would be appreciated.
>
> Googling around gives quite complex suggestions.
>
> Is there something simple I could try here?
>
> Regards
>
> Michael Fothergill
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>

lm-sensors doesn't see the cpu rpm.....

[Michael Fothergill]

Dear Folks,

I am running stretch on an AMD FX8350 box which uses an Arctic Freezer 13
cooler.

I installed lm-sensors and ran the /etc module update command.

The output looks like this:

root@bong:/home/mikef# sensors
asus-isa-
Adapter: ISA adapter
cpu_fan:0 RPM

k10temp-pci-00c3
Adapter: PCI adapter
temp1:+21.9°C  (high = +70.0°C)
   (crit = +90.0°C, hyst = +87.0°C)

nouveau-pci-0700
Adapter: PCI adapter
GPU core: +0.90 V  (min =  +0.88 V, max =  +1.08 V)
temp1:+35.0°C  (high = +95.0°C, hyst =  +3.0°C)
   (crit = +105.0°C, hyst =  +5.0°C)
   (emerg = +135.0°C, hyst =  +5.0°C)

fam15h_power-pci-00c4
Adapter: PCI adapter
power1:6.75 W  (crit = 125.19 W)


it8721-isa-0290

Adapter: ISA
adapter

in0:  +2.83 V  (min =  +2.02 V, max =  +2.95
V)
in1:  +2.83 V  (min =  +1.68 V, max =  +1.73 V)
ALARM
in2:  +0.98 V  (min =  +2.40 V, max =  +1.08 V)
ALARM
+3.3V:+3.31 V  (min =  +0.38 V, max =  +0.96 V)
ALARM
in4:  +0.25 V  (min =  +0.41 V, max =  +0.20 V)  ALARM
in5:  +2.51 V  (min =  +0.12 V, max =  +0.00 V)  ALARM
in6:  +1.98 V  (min =  +1.54 V, max =  +0.59 V)  ALARM
3VSB: +3.94 V  (min =  +3.31 V, max =  +0.89 V)  ALARM
Vbat: +3.29 V
fan1:1814 RPM  (min =   87 RPM)
fan2:   0 RPM  (min =   46 RPM)  ALARM
fan3:1125 RPM  (min =   29 RPM)
temp1:+37.0°C  (low  = +34.0°C, high = +91.0°C)  sensor = thermistor
temp2:+30.0°C  (low  = +45.0°C, high =  +9.0°C)  ALARM  sensor =
thermistor
temp3:   -128.0°C  (low  = -60.0°C, high =  +4.0°C)  sensor = disabled
intrusion0:  OK

root@bong:/home/mikef#

The cpu fan is running at around 2500 rpm.

If the connector were 3 pin rather than 4 pin could that explain the zero
here?

Suggestions on a tweak that could awaken the sensor or stimulate lm-sensors
truffle hound hunting skills here would be appreciated.

Googling around gives quite complex suggestions.

Is there something simple I could try here?

Regards

Michael Fothergill

lm-sensors控制风扇，不能加载模块

[gmail]

我在x200上面安装了 debian sid，风扇一直在全速运转，想要实现根据温度来调 
节转速。

参考了http://www.linuxidc.com/Linux/2009-02/18270.htm
这篇文章提到lm-sensors，于是到官方网站（http://www.lm- sensors.org/wiki 
/iwizard/Detection）

按照教程设置，最后加载模 块不能成功。
下面是我的操作过程，有知 道的，帮我看看。

PS：1.像这样 的问题应该在哪里的邮件列表去问呢?

2 有哪位朋友也在 thinkpad上面安装了debian之类的linux系统，一起 
交流。怎样实现充放电阈值的控制，以及延长电池使用时间 的方法，以及动态硬 
盘保护


谢 谢！


#+TITLE:
* ref
www.lm-sensors.org/wiki/iwizard/DistroPackageInstall
www.lm-sensors.org/wiki/iwizard/KernelPreparation
www.lm-sensors.org/wiki/iwizard/SensorsOutput

* install
$ apt-get install lm-sensors

* usage

kk@x200:~$  sudo sensors-detect
# sensors-detect revision 6209 (2014-01-14 22:51:58 +0100)
# System: LENOVO 7459X18 [ThinkPad X200] (laptop)

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no):
Module cpuid loaded successfully.
Silicon Integrated Systems SIS5595...   No
VIA VT82C686 Integrated Sensors...  No
VIA VT8231 Integrated Sensors...No
AMD K8 thermal sensors...   No
AMD Family 10h thermal sensors...   No
AMD Family 11h thermal sensors...   No
AMD Family 12h and 14h thermal sensors...   No
AMD Family 15h thermal sensors...   No
AMD Family 15h power sensors... No
AMD Family 16h power sensors... No
Intel digital thermal sensor... Success!
(driver `coretemp')
Intel AMB FB-DIMM thermal sensor... No
VIA C7 thermal sensor...No
VIA Nano thermal sensor...  No

Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no):
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...   No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'...   No
Trying family `ITE'...  No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'...   No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'...   No
Trying family `ITE'...  No

Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no):
Probing for `National Semiconductor LM78' at 0x290...   No
Probing for `National Semiconductor LM79' at 0x290...   No
Probing for `Winbond W83781D' at 0x290...   No
Probing for `Winbond W83782D' at 0x290...   No

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no):
Using driver `i2c-i801' for device :00:1f.3: Intel ICH9
Module i2c-dev loaded successfully.

Next adapter: SMBus I801 adapter at 1c60 (i2c-0)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x5c
Probing for `Analog Devices ADT7462'... No
Probing for `SMSC EMC1072'...   No
Probing for `SMSC EMC1073'...   No
Probing for `SMSC EMC1074'...   No

Next adapter: i915 gmbus ssc (i2c-1)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus vga (i2c-2)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus panel (i2c-3)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus dpc (i2c-4)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus dpb (i2c-5)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus dpd (i2c-6)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: DPDDC-B (i2c-7)
Do you want to scan it? (YES/no/selectively): yes

Next adapter: DPDDC-C (i2c-8)
Do you want to scan it? (YES/no/selectively):

Next adapter: DPDDC-D (i2c-9)
Do you want to scan it? (YES/no/selectively):


Now follows a summary of the probes I have just done.
Just press ENTER to continue:

Driver `coretemp&#x

Re: Trouble getting net-snmp to return lm-sensors data (solved)

[Francois Gouget]

On Fri, 31 May 2013, Francois Gouget wrote:
> 
> So I'm trying to get net-snmp to return lm_sensors data so I can monitor 
> the temperature and fan speed of my PC. But currently it won't return 
> any data:
> 
> $ snmpwalk -v2c -c public localhost lmSensors 
> LM-SENSORS-MIB::lmSensors = No more variables left in this MIB View 
> (It is past the end of the MIB tree)

It turns out this was an access control issue. Uncommenting the 
following line fixed it:

   rocommunity public  localhost


-- 
Francois Gouget   http://fgouget.free.fr/
It really galls me that most of the computer power in the world
  is wasted on screen savers.
 Chris Caldwell from the GIMPS project
   http://www.mersenne.org/prime.htm


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/alpine.DEB.2.10.1306120019490.31015@amboise.dolphin

Trouble getting net-snmp to return lm-sensors data

[Francois Gouget]

So I'm trying to get net-snmp to return lm_sensors data so I can monitor 
the temperature and fan speed of my PC. But currently it won't return 
any data:

$ snmpwalk -v2c -c public localhost lmSensors 
LM-SENSORS-MIB::lmSensors = No more variables left in this MIB View 
(It is past the end of the MIB tree)

Note that it's not saying that it does not know about lmSensors so it 
seems like it found the MIB alright. Also sensors does return what seems 
like suitable data to me:

$ sensors
coretemp-isa-
Adapter: ISA adapter
Core 0:   +50.0°C  (high = +74.0°C, crit = +100.0°C)
Core 1:   +50.0°C  (high = +74.0°C, crit = +100.0°C)
Core 2:   +46.0°C  (high = +74.0°C, crit = +100.0°C)
Core 3:   +50.0°C  (high = +74.0°C, crit = +100.0°C)

it8718-isa-0290
Adapter: ISA adapter
Vcore:+1.12 V  (min =  +0.00 V, max =  +4.08 V)
Vram: +1.87 V  (min =  +0.00 V, max =  +4.08 V)
+3.3V:+3.15 V  (min =  +0.00 V, max =  +4.08 V)
+5V:  +4.70 V  (min =  +0.00 V, max =  +6.85 V)
+12V:+12.16 V  (min =  +0.00 V, max = +16.32 V)
Vbat: +3.26 V  
CPU Fan: 1207 RPM  (min =   10 RPM)
F/Low Fan:  0 RPM  (min =   10 RPM)
F/High Fan:  1300 RPM  (min =0 RPM)
NBr Temp: +45.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor
CPU Temp: +34.0°C  (low  = +127.0°C, high = +80.0°C)  sensor = thermal diode
intrusion0:  OK

In particular notice the 'V' and 'Temp' labels which I believe should 
allow net-snmp to recognize these as voltages and temperaturs.


Here's what I did so far:

 * I'm running Testing so I installed:
   snmp 5.4.3~dfsg-3
   snmpd5.4.3~dfsg-3
   snmp-mibs-downloader 1.1
   libsnmp155.4.3~dfsg-3
   lm-sensors   1:3.3.3-1

 * Commented out the 'export MIBS=' line in /etc/default/snmpd. I also 
   tried pointing it to specific MIB files to no avail.

 * Commented out the 'mibs :' line in /etc/snmp/snmp.conf.

 * Here's a summary of /etc/snmp/snmpd.conf:
   agentAddress  udp:127.0.0.1:161
   view   systemonly  included   .1.3.6.1.2.1.1
   view   systemonly  included   .1.3.6.1.2.1.25.1
   rocommunity public  default-V systemonly
   rouser   authOnlyUser
   sysLocationSitting on the Dock of the Bay
   sysContact Francois Gouget 
   sysServices72
   proc  mountd
   proc  ntalkd4
   proc  sendmail 10 1
   disk   / 1
   disk   /var  5%
   includeAllDisks  10%
   load   12 10 5
   trapsink localhost public
   iquerySecName   internalUser   
   rouser  internalUser
   defaultMonitors  yes
   linkUpDownNotifications  yes
   master  agentx

 * I found a comment that claims that net-snmp 5.5 or greater is 
   required to get integration with lm-sensors. Yet I believe that 
   functionality was present long ago and could not find confirmation. 
   Also net-snmp 5.5 is not available in Testing.
   
http://www.net-snmp.org/wiki/index.php/Net-SNMP_and_lm-sensors_on_Ubuntu_10.04

So has anyone else been able to get net-snmp and lm-sensors to play nice 
together. Any special tricks?


-- 
Francois Gouget   http://fgouget.free.fr/
The nice thing about meditation is that it makes doing nothing quite respectable
  -- Paul Dean

Re: lm-sensors

[lee]

Darac Marjal  writes:

> It might be, for those motherboards that don't report any
> information, that they simply don't have the sensors.

It shows system and CPU temperature, fan speeds and other things in the
BIOS, and the RAID controller now shows me the temperature of the
attached disks which were attached to the on-board controller before.
That would suggest that the sensors are there.


-- 
Debian testing iad96 brokenarch


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/877gqfz3r5@yun.yagibdah.de

Re: lm-sensors

[Darac Marjal]

On Wed, Oct 24, 2012 at 11:13:08AM +0200, lee wrote:
> Darac Marjal  writes:
> 
> > On Tue, Oct 23, 2012 at 02:14:29PM +0200, lee wrote:
> >> 
[cut]
> >
> > (This is a summary of my searching the web for "ACPI: resource
> > f71882fg")
> 
> Yeah I've found the same results, and they don't tell me if it's
> possible to get some more output or not.  I've never seen lmsensors
> really working with any board I've had.  All the information I could
> find for lmsensors with my particular board was old.  The conclusion can
> only be that lmsensors is obsolete because it persistently doesn't work
> and that I'll be better off getting a digital thermometer and attaching
> its sensor to an appropriate place.
> 
> But who knows, perhaps it does work and I only need to find out how to
> get it to work.

It might be, for those motherboards that don't report any
information, that they simply don't have the sensors. Depending on who
the board is targeted at, adding thermal sensors may be seen by the
manufacturer as a needless expense. Most CPUs come with a sensor now, as
do most hard drives and that's probably seen as sufficient. Certainly,
most laptops I've owned have shown nothing of interest in lmsensors. And
with Windows (still, by far, the main target for motherboards) not
reporting temperatures natively, why would they bother?


signature.asc
Description: Digital signature

Re: lm-sensors

[lee]

Darac Marjal  writes:

> On Tue, Oct 23, 2012 at 02:14:29PM +0200, lee wrote:
>> 
>> [   12.509295] f71882fg: Found f71889fg chip at 0x600, revision 21
>> [   12.509364] ACPI: resource f71882fg [io  0x0600-0x0607] conflicts with 
>> ACPI region HMOR [io 0x605-0x606]
>> [   12.509372] ACPI: If an ACPI driver is available for this device, you 
>> should use it instead of the native driver
>> 
>> 
>> Is there an ACPI driver available for this chip, and if so, which one
>> would that be?  Sensors only says:
>
> You can look at this page: http://www.lm-sensors.org/wiki/Devices. You
> want to find a line for your sensor with "ACPI" in the "bus type"
> (fifth) column.
>
> Alternatively, read this FAQ on the subject:
> http://www.lm-sensors.org/wiki/FAQ/Chapter3#Mysensorshavestoppedworkinginkernel2.6.31
>
> (This is a summary of my searching the web for "ACPI: resource
> f71882fg")

Yeah I've found the same results, and they don't tell me if it's
possible to get some more output or not.  I've never seen lmsensors
really working with any board I've had.  All the information I could
find for lmsensors with my particular board was old.  The conclusion can
only be that lmsensors is obsolete because it persistently doesn't work
and that I'll be better off getting a digital thermometer and attaching
its sensor to an appropriate place.

But who knows, perhaps it does work and I only need to find out how to
get it to work.


-- 
Debian testing iad96 brokenarch


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87d308kzbv@yun.yagibdah.de

Re: lm-sensors

[Darac Marjal]

On Tue, Oct 23, 2012 at 02:14:29PM +0200, lee wrote:
> 
> [   12.509295] f71882fg: Found f71889fg chip at 0x600, revision 21
> [   12.509364] ACPI: resource f71882fg [io  0x0600-0x0607] conflicts with 
> ACPI region HMOR [io 0x605-0x606]
> [   12.509372] ACPI: If an ACPI driver is available for this device, you 
> should use it instead of the native driver
> 
> 
> Is there an ACPI driver available for this chip, and if so, which one
> would that be?  Sensors only says:

You can look at this page: http://www.lm-sensors.org/wiki/Devices. You
want to find a line for your sensor with "ACPI" in the "bus type"
(fifth) column.

Alternatively, read this FAQ on the subject:
http://www.lm-sensors.org/wiki/FAQ/Chapter3#Mysensorshavestoppedworkinginkernel2.6.31

(This is a summary of my searching the web for "ACPI: resource
f71882fg")


signature.asc
Description: Digital signature

lm-sensors

[lee]

[   12.509295] f71882fg: Found f71889fg chip at 0x600, revision 21
[   12.509364] ACPI: resource f71882fg [io  0x0600-0x0607] conflicts with ACPI 
region HMOR [io 0x605-0x606]
[   12.509372] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver


Is there an ACPI driver available for this chip, and if so, which one
would that be?  Sensors only says:


k10temp-pci-00c3
Adapter: PCI adapter
temp1:+29.5°C  (high = +70.0°C)


I've never seen lmsensors show any useful values and now it's giving
error messages.  Does that work at all?


-- 
Debian testing iad96 brokenarch


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87pq49mllm@yun.yagibdah.de

Re: smartctl Vs lm-sensors

[Hugo Vanwoerkom]

Brian McKee wrote:


On 18-Apr-08, at 1:22 PM, Bhasker C V wrote:

 I want to monitor the harddisk temperature since I/O task in my system
is very high and usually heatsup the harddisk.

 I get two different values viz. one from lm-sensors and other from
smartctl


smartctl gives me very large values like the one below showing 148
whereas hddtemp or the lm-sensors gives me value



194 Temperature_Celsius 0x0002  148   148   000Old_age   Always
-   37 (Lifetime Min/Max 21/45)
/dev/hda: HTS541010G9AT00: 38



Smartctl is reporting 37  (see it there in the last column?)
The 148 raw value needs to be interpreted, it's not actually in degrees.
See the smartctl man page / website for more info



Too bad that you cannot do that with USB HDD's.

Hugo


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: smartctl Vs lm-sensors

[Brian McKee]

On 18-Apr-08, at 1:22 PM, Bhasker C V wrote:
 I want to monitor the harddisk temperature since I/O task in my  
system

is very high and usually heatsup the harddisk.

 I get two different values viz. one from lm-sensors and other from
smartctl


smartctl gives me very large values like the one below showing 148
whereas hddtemp or the lm-sensors gives me value


194 Temperature_Celsius 0x0002  148   148   000Old_age
Always

-   37 (Lifetime Min/Max 21/45)
/dev/hda: HTS541010G9AT00: 38



Smartctl is reporting 37  (see it there in the last column?)
The 148 raw value needs to be interpreted, it's not actually in degrees.
See the smartctl man page / website for more info

Brian


PGP.sig
Description: This is a digitally signed message part

smartctl Vs lm-sensors

[Bhasker C V]

Hi all,

 I want to monitor the harddisk temperature since I/O task in my system
is very high and usually heatsup the harddisk.

 I get two different values viz. one from lm-sensors and other from
smartctl


smartctl gives me very large values like the one below showing 148
whereas hddtemp or the lm-sensors gives me value 

>>>>
194 Temperature_Celsius 0x0002   148   148   000Old_age   Always
-   37 (Lifetime Min/Max 21/45)
>>>>
/dev/hda: HTS541010G9AT00: 38 C
>>>>

Now, which one am i supposed to believe ?


PS: The output above is indicative that the information is definetly
centigrage and not the 194,10xCelsius value. Even if it had been 10x
value, then, the values of 148/10 and 38 do not match.

Am i missing something ?


thanks

 
-- 
Bhasker C V
Registered Linux user: #306349 (counter.li.org)
The box said "Requires Windows 95, NT, or better", so I installed Linux.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: apt-get problems (lm-sensors)

[Chris Lale]

Florian Kulzer wrote:
> On Thu, Sep 06, 2007 at 12:24:43 +0200, chris wrote:
>> Hi,
>>
>> I just upgraded (partialy) to ETCH from Sarge.
> 
> Does "partially" mean "without reading the release notes"?
> 
>> but some dependencies did not meet.
>>
>> when I try e.g.
>> apt-get install nmap
>>
>> i get following:
> 
> [ snip: signs of an incomplete XFree86 to X.Org transition ]
> 
>> Preparing to replace lm-sensors 1:2.10.1-3 (using .../lm-
>> sensors_1%3a2.10.1-3_i386.deb) ...
>> Unpacking replacement lm-sensors ...
>> /etc/modutils/0keep: line 9: keep: command not found
>> Error while executing /etc/modutils/0keep, aborting
>> dpkg: warning - old post-removal script returned error exit status 1
>> dpkg - trying script from the new package instead ...
>> /etc/modutils/0keep: line 9: keep: command not found
>> Error while executing /etc/modutils/0keep, aborting
>> dpkg: error processing /var/cache/apt/archives/lm-
>> sensors_1%3a2.10.1-3_i386.deb (--unpack):
>>  subprocess new post-removal script returned error exit status 1
>> /etc/modutils/0keep: line 9: keep: command not found
>> Error while executing /etc/modutils/0keep, aborting
>> dpkg: error while cleaning up:
>>  subprocess post-removal script returned error exit status 1
>> Errors were encountered while processing:
>>  /var/cache/apt/archives/lm-sensors_1%3a2.10.1-3_i386.deb
>> E: Sub-process /usr/bin/dpkg returned an error code (1)
>>
>> I really don't understand what it means using .../lm-
>> sensors_1%3a2.10.1-3_i386.deb (I did not want to install it - I
>> already installed lm-sensors 1:2.10.1-3
> 
> Most probably the previous installation attempt was not successful; this
> means that apt has to try again at every opportunity.
> 
>> can anybody suggest anything to try to move forward with this.
> 
> Read
> 
> http://www.debian.org/releases/stable/i386/release-notes/ch-information.en.html
> 
> especially sections 5.2 (kernel upgrade and module-init-tools) and 5.3
> (XFree86 to X.Org). Try to remember exactly what you did so far and
> decide if you think that you can still fix these issues or if it will be
> easier to install Etch "from scratch" (after backing up your $HOME).
> 

You might also find this approach [1] useful. Dates from before Etch became 
stable.

[1]
http://newbiedoc.berlios.de/wiki/Aptitude_-_using_together_with_Synaptic_and_Apt-get#Upgrading_from_Sarge_to_Etch


-- 
Chris.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: apt-get problems (lm-sensors)

[Florian Kulzer]

On Thu, Sep 06, 2007 at 12:24:43 +0200, chris wrote:
> Hi,
> 
> I just upgraded (partialy) to ETCH from Sarge.

Does "partially" mean "without reading the release notes"?

> but some dependencies did not meet.
> 
> when I try e.g.
> apt-get install nmap
> 
> i get following:

[ snip: signs of an incomplete XFree86 to X.Org transition ]

> Preparing to replace lm-sensors 1:2.10.1-3 (using .../lm-
> sensors_1%3a2.10.1-3_i386.deb) ...
> Unpacking replacement lm-sensors ...
> /etc/modutils/0keep: line 9: keep: command not found
> Error while executing /etc/modutils/0keep, aborting
> dpkg: warning - old post-removal script returned error exit status 1
> dpkg - trying script from the new package instead ...
> /etc/modutils/0keep: line 9: keep: command not found
> Error while executing /etc/modutils/0keep, aborting
> dpkg: error processing /var/cache/apt/archives/lm-
> sensors_1%3a2.10.1-3_i386.deb (--unpack):
>  subprocess new post-removal script returned error exit status 1
> /etc/modutils/0keep: line 9: keep: command not found
> Error while executing /etc/modutils/0keep, aborting
> dpkg: error while cleaning up:
>  subprocess post-removal script returned error exit status 1
> Errors were encountered while processing:
>  /var/cache/apt/archives/lm-sensors_1%3a2.10.1-3_i386.deb
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> 
> I really don't understand what it means using .../lm-
> sensors_1%3a2.10.1-3_i386.deb (I did not want to install it - I
> already installed lm-sensors 1:2.10.1-3

Most probably the previous installation attempt was not successful; this
means that apt has to try again at every opportunity.

> can anybody suggest anything to try to move forward with this.

Read

http://www.debian.org/releases/stable/i386/release-notes/ch-information.en.html

especially sections 5.2 (kernel upgrade and module-init-tools) and 5.3
(XFree86 to X.Org). Try to remember exactly what you did so far and
decide if you think that you can still fix these issues or if it will be
easier to install Etch "from scratch" (after backing up your $HOME).

-- 
Regards,| http://users.icfo.es/Florian.Kulzer
  Florian   |


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

apt-get problems (lm-sensors)

[chris]

Hi,

I just upgraded (partialy) to ETCH from Sarge.

but some dependencies did not meet.

when I try e.g.
apt-get install nmap

i get following:

Reading package lists... Done
Building dependency tree... Done
You might want to run `apt-get -f install' to correct these:
The following packages have unmet dependencies:
  libxft1: Depends: xfree86-common but it is not installable
  pm-dev: Depends: xfree86-common but it is not installable
  xfonts-100dpi-transcoded: Depends: xfree86-common but it is not
installable
  xfonts-75dpi: Depends: xfree86-common but it is not installable
  xfonts-75dpi-transcoded: Depends: xfree86-common but it is not
installable
  xfonts-base: Depends: xfree86-common but it is not installable
  xfonts-base-transcoded: Depends: xfree86-common but it is not
installable
  xfonts-scalable: Depends: xfree86-common but it is not installable
  xlibs-static-dev: Depends: xfree86-common but it is not installable
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or
specify a solution).

then I try:
apt-get -f install
Reading package lists... Done
Building dependency tree... Done
Correcting dependencies... Done
The following extra packages will be installed:
  libfontenc-dev libxfont-dev x11proto-fonts-dev xfonts-100dpi-
transcoded
  xfonts-75dpi xfonts-75dpi-transcoded xfonts-base xfonts-scalable
  xlibs-static-dev
The following packages will be REMOVED:
  libxft1 pm-dev xfonts-base-transcoded xlibs xlibs-dev
The following NEW packages will be installed:
  libfontenc-dev libxfont-dev x11proto-fonts-dev
The following packages will be upgraded:
  xfonts-100dpi-transcoded xfonts-75dpi xfonts-75dpi-transcoded xfonts-
base
  xfonts-scalable xlibs-static-dev
6 upgraded, 3 newly installed, 5 to remove and 189 not upgraded.
1 not fully installed or removed.
Need to get 0B/24.6MB of archives.
After unpacking 8937kB disk space will be freed.
Do you want to continue [Y/n]?

pressing Y
i get at the end:
(Reading database ... 110426 files and directories currently
installed.)
Preparing to replace lm-sensors 1:2.10.1-3 (using .../lm-
sensors_1%3a2.10.1-3_i386.deb) ...
Unpacking replacement lm-sensors ...
/etc/modutils/0keep: line 9: keep: command not found
Error while executing /etc/modutils/0keep, aborting
dpkg: warning - old post-removal script returned error exit status 1
dpkg - trying script from the new package instead ...
/etc/modutils/0keep: line 9: keep: command not found
Error while executing /etc/modutils/0keep, aborting
dpkg: error processing /var/cache/apt/archives/lm-
sensors_1%3a2.10.1-3_i386.deb (--unpack):
 subprocess new post-removal script returned error exit status 1
/etc/modutils/0keep: line 9: keep: command not found
Error while executing /etc/modutils/0keep, aborting
dpkg: error while cleaning up:
 subprocess post-removal script returned error exit status 1
Errors were encountered while processing:
 /var/cache/apt/archives/lm-sensors_1%3a2.10.1-3_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

I really don't understand what it means using .../lm-
sensors_1%3a2.10.1-3_i386.deb (I did not want to install it - I
already installed lm-sensors 1:2.10.1-3

can anybody suggest anything to try to move forward with this.

thanks
chris


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: lm-sensors k8temp kernel module for Etch

[Stephen Cormier]

On April 4, 2007 10:39:31 am Siju George wrote:
> Hi,
>
> While Installing lm-sensors package on my Etch using
>
> 2.6.18-4-amd64 #1 SMP Mon Mar 26 11:36:53 CEST 2007 x86_64 GNU/Linux
>
> kernel. I got the following message
>
> ==
>
> To make the sensors modules behave correctly, add these lines to
> /etc/modules:
>
> #cut here
> # I2C adapter drivers
> i2c-piix4
> # Chip drivers
> lm85
> eeprom
> # Warning: the required module k8temp is not currently installed
> # on your system. For status of 2.6 kernel ports check
> # http://www.lm-sensors.org/wiki/Devices. If driver is built
> # into the kernel, or unavailable, comment out the following line.
> k8temp
> #cut here
> 
>
> From
>
> http://www.lm-sensors.org/wiki/Devices
>
> it seems "k8temp" is builtinto the kernel only from version "2.6.19"
>
> As my kernel is "2.6.18-4-amd64 " is there any way to install this driver?
>
> Thankyou so much
>
> Kind Regards
>
> Siju

Get the source (1) for the module follow the instructions on building it, you 
will need to have the kernel headers installed for your kernel for the build 
command to work properly. Once you have the k8temp.ko you can either keep 
using the insmod k8temp on every boot to load or simply copy the the .ko file 
to the /lib/modules/2.6.18-4-amd64/kernel/drivers/hwmon/k8temp.ko and run 
depmod -a then put k8temp on a line by itself in your /etc/modules as 
suggested above and it will be loaded on every boot.

(1) http://assembler.cz/download/amd_digital_temp.tar.gz

Stephen

-- 
GPG Pubic Key: http://users.eastlink.ca/~stephencormier/publickey.asc


pgpJb44CC9rMl.pgp
Description: PGP signature

lm-sensors k8temp kernel module for Etch

[Siju George]

Hi,

While Installing lm-sensors package on my Etch using

2.6.18-4-amd64 #1 SMP Mon Mar 26 11:36:53 CEST 2007 x86_64 GNU/Linux

kernel. I got the following message

==

To make the sensors modules behave correctly, add these lines to
/etc/modules:

#cut here
# I2C adapter drivers
i2c-piix4
# Chip drivers
lm85
eeprom
# Warning: the required module k8temp is not currently installed
# on your system. For status of 2.6 kernel ports check
# http://www.lm-sensors.org/wiki/Devices. If driver is built
# into the kernel, or unavailable, comment out the following line.
k8temp
#cut here


From

http://www.lm-sensors.org/wiki/Devices

it seems "k8temp" is builtinto the kernel only from version "2.6.19"

As my kernel is "2.6.18-4-amd64 " is there any way to install this driver?

Thankyou so much

Kind Regards

Siju


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: [lm-sensors] Intel Core Duo/Solo Temperature Monitoring Working On Intel DG965 Motherboard

[Jean Delvare]

Hi Nicolas,

On Thu, 15 Mar 2007 19:27:21 +0800, Nicolas Boichat wrote:
> I ported this patch to the latest git, I hope this can help to get it
> merged.
> 
> I'm just wondering if it is right to export the functions msr_read and
> msr_write from arch/i386/kernel/msr.c, or if it would be better to put
> these functions in arch/i386/lib/msr-on-cpu.c with rdmsr_on_cpu and
> wrmsr_on_cpu.
> 
> Note the difference between msr_read/msr_write and
> rdmsr_on_cpu/wrmsr_on_cpu is that msr_read/msr_write use "safe" rdmsr
> /wrmsr functions (i.e. test return value), while
> rdmsr_on_cpu/wrmsr_on_cpu does not. Coretemp needs the return value to
> work properly.

I reviewed Rudolf Marek's patches a few days ago and my first comment
was along these lines:
http://lists.lm-sensors.org/pipermail/lm-sensors/2007-March/019169.html

I do indeed believe that the functions in lib/msr-on-cpu.c should be
improved to be suitable for our needs. Others are likely to need the
same feature. Library functions should really return the errors, and
leave it up to the caller to decide whether to ignore them or not,
rather than hiding them.

Could you possibly propose a separate patch fixing lib/msr-on-cpu.c (on
both i386 and x86_64) to reliably report the errors? I guess it's a
simple matter of changing the prototypes of the functions? If we can
get this upstream, this would make the integration of the coretemp
driver easier and faster.

Thanks,
-- 
Jean Delvare


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: udev, lm-sensors and esd

[Felipe Sateler]

Adam Hardy wrote:
> I don't understand how that is connected with udev though. Presumably
> running alsaconf set up the udev rule that tells udev to make a device
> for alsa?
>From the manpage:
Alsaconf will write a module-init-tools (or modutils) snippet which can be 
then  used  by  module-init-tools (or modutils) to load the correct
parameters for your sound card.

-- 

Felipe Sateler


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: udev, lm-sensors and esd

[Adam Hardy]

John O'Hagan on 16/04/06 14:55, wrote:

On Sun, 16 Apr 2006 06:24 pm, Adam Hardy wrote:


Hmm. I have installed all the appropriate alsa packages I could find in
synaptic, but I don't have the command alsaconfig on my system.

Where does it come from?



The command you're after is alsaconf.


Great. Thanks, that was easy.

I don't understand how that is connected with udev though. Presumably 
running alsaconf set up the udev rule that tells udev to make a device 
for alsa?






Adam


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: udev, lm-sensors and esd

[John O'Hagan]

On Sun, 16 Apr 2006 06:24 pm, Adam Hardy wrote:

>
> Hmm. I have installed all the appropriate alsa packages I could find in
> synaptic, but I don't have the command alsaconfig on my system.
>
> Where does it come from?
>

The command you're after is alsaconf.

HTH,

John


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: udev, lm-sensors and esd

[Rodney D. Myers]

On Sun, 16 Apr 2006 09:24:48 +0100
Adam Hardy <[EMAIL PROTECTED]> wrote:

> Felipe Sateler on 15/04/06 22:30, wrote:
> > Adam Hardy wrote:
> >> I have been researching the issues. It looks like the appropriate
> >> drivers have not been created - for instance, the following paths are
> >> empty or non-existent:
> >>
> >> /sys/bus/i2c/devices
> >> /proc/sys/dev/sensors
> >> /proc/acpi/thermal
> > Seems like you are not loading the modules you should. What does lsmod say?
> > Regarding the sound, if you are using alsa (which you should), run
> > dpkg-reconfigure linux-sound-base to ensure the OSS modules aren't loaded
> > during startup (which prevents alsa from working correctly), and then run
> > alsaconfig.
> 
> Hmm. I have installed all the appropriate alsa packages I could find in 
> synaptic, but I don't have the command alsaconfig on my system.
> 
> Where does it come from?
> 
> 
> Thanks
> Adam

the  alsa-utils package

-- 
Rodney D. Myers <[EMAIL PROTECTED]> 
Registered Linux User #96112
ICQ#: AIM#:   YAHOO:
18002350  mailman452  mailman42_5

They that can give up essential liberty to obtain a 
little temporary safety deserve neither liberty nor safety.
Ben Franklin - 1759


signature.asc
Description: PGP signature

Re: udev, lm-sensors and esd

[Adam Hardy]

Felipe Sateler on 15/04/06 22:30, wrote:

Adam Hardy wrote:

I have been researching the issues. It looks like the appropriate
drivers have not been created - for instance, the following paths are
empty or non-existent:

/sys/bus/i2c/devices
/proc/sys/dev/sensors
/proc/acpi/thermal

Seems like you are not loading the modules you should. What does lsmod say?
Regarding the sound, if you are using alsa (which you should), run
dpkg-reconfigure linux-sound-base to ensure the OSS modules aren't loaded
during startup (which prevents alsa from working correctly), and then run
alsaconfig.


Hmm. I have installed all the appropriate alsa packages I could find in 
synaptic, but I don't have the command alsaconfig on my system.


Where does it come from?


Thanks
Adam


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: udev, lm-sensors and esd

[Felipe Sateler]

Adam Hardy wrote:
> I have been researching the issues. It looks like the appropriate
> drivers have not been created - for instance, the following paths are
> empty or non-existent:
> 
> /sys/bus/i2c/devices
> /proc/sys/dev/sensors
> /proc/acpi/thermal
Seems like you are not loading the modules you should. What does lsmod say?
Regarding the sound, if you are using alsa (which you should), run
dpkg-reconfigure linux-sound-base to ensure the OSS modules aren't loaded
during startup (which prevents alsa from working correctly), and then run
alsaconfig.
-- 

Felipe Sateler


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

udev, lm-sensors and esd

[Adam Hardy]

I upgraded my debian testing 2.6.16 udev so that I could use the latest 
hotsynch software for my new phone, but the operation has brought down 
my hardware monitoring and my sound driver.


In gkrellm, the CPU temps & voltages are no longer available.

When I launch KDE, it tells me the sound driver can't connect.

I have been researching the issues. It looks like the appropriate 
drivers have not been created - for instance, the following paths are 
empty or non-existent:


/sys/bus/i2c/devices
/proc/sys/dev/sensors
/proc/acpi/thermal

I have a feeling from my present understanding of udev that perhaps udev 
should be configured to sort out this stuff, but I'm not sure how.


Can anyone help?

Thanks
Adam


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: lm-sensors security update

[Matus UHLAR - fantomas]

On 26.03.06 15:57, Hugo Vanwoerkom wrote:
> Sarge just updated the lm-sensors library.
> 
> That's a bind because I modified that library to support my mobo, which 
> has an unsupported sensor chip.

sorry, security updates fixes only security problems, they do NOT add any
functionality (unless that's the nature of those security fixsex, which
doesn't happen often).

> This has probably been told many times, but where can I find out what 
> the update consists in?

it's described in the security notices. see www.debian.org/security/

-- 
Matus UHLAR - fantomas, [EMAIL PROTECTED] ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Saving Private Ryan...
Private Ryan exists. Overwrite? (Y/N)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

lm-sensors security update

[Hugo Vanwoerkom]

Hi,

Sarge just updated the lm-sensors library.

That's a bind because I modified that library to support my mobo, which 
has an unsupported sensor chip.


This has probably been told many times, but where can I find out what 
the update consists in?


Thanks!

H


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

lm-sensors

[Chris]

Just upgraded an old P3 machine to a new Athlon 3500 on an Asus
motherboard (sarge).

sensors-detect advised to install the modules

i2c-isa
it87

Now - sensors gives the following (as does sensord):

it87-isa-0d00
Adapter: ISA adapter
VCore 1:   +1.44 V  (min =  +1.42 V, max =  +1.57 V)   ALARM
VCore 2:   +4.08 V  (min =  +2.40 V, max =  +2.61 V)   ALARM
+3.3V: +6.59 V  (min =  +3.14 V, max =  +3.46 V)   ALARM
+5V:   +5.13 V  (min =  +4.76 V, max =  +5.24 V)   
+12V: +11.90 V  (min = +11.39 V, max = +12.61 V)   
-12V:  +3.93 V  (min = -12.63 V, max = -11.41 V)   ALARM
-5V:   +4.03 V  (min =  -5.26 V, max =  -4.77 V)   ALARM
Stdby: +6.85 V  (min =  +4.76 V, max =  +5.24 V)   ALARM
VBat:  +3.20 V
fan1:0 RPM  (min =0 RPM, div = 2)  
fan2:0 RPM  (min =   41 RPM, div = 128)  
fan3:0 RPM  (min =  664 RPM, div = 8)  
M/B Temp:+38 C  (low  =   +15 C, high =   +40 C)   sensor = thermistor   
CPU Temp:+44 C  (low  =   +15 C, high =   +45 C)   sensor = thermistor   
Temp3:  +128 C  (low  =   +15 C, high =   +45 C)   sensor = disabled   


Now - everything is running correctly - so I've got a feeling that
there isn't +4v on the -12v , +4v on the -5v etc.

I followed a web howto on how to set it up - but I could really do
with some help debugging/finding out what's going on here. Any
hints/RTFM pointers on how to sort this out?

-- 
Chris


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: lm-sensors bug?

[L.V.Gandhi]

On 9/15/05, wim <[EMAIL PROTECTED]> wrote:
Thanx for your help...I compiled a new kernel 2.6.13 and it is working now... strange...How to get, config while using sarge?-- L.V.Gandhi
http://lvgandhi.tripod.com/linux user No.205042

Re: lm-sensors bug?

[wim]

Thanx for your help...
I compiled a new kernel 2.6.13 and it is working now... strange...


On Thu, Sep 15, 2005 at 09:16:56AM -0500, Hugo Vanwoerkom wrote:
> wim wrote:
> >Hi,
> >
> >I'm trying to get lm-sensors working on my PII 400Mhz
> >The motherboard is an Asus AX6BC
> >
> 
> Why don't you just add
> gl518sl
> i2c-isa
> 
> to /etc/modules and reboot?
> 
> H
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
> with a subject of "unsubscribe". Trouble? Contact 
> [EMAIL PROTECTED]
> 
> 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: lm-sensors bug?

[Hugo Vanwoerkom]

wim wrote:

Hi,

I'm trying to get lm-sensors working on my PII 400Mhz
The motherboard is an Asus AX6BC



Why don't you just add
gl518sm
i2c-isa

to /etc/modules and reboot?

H


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: lm-sensors bug?

[Wang Xu]

2005/9/13, wim <[EMAIL PROTECTED]>:
> 
> I'm also trying to insert the module for the GL518SM Chipset, but tha's
> failing. Could this be a bug in the driver?
> 
> slayer:~# insmod /lib/modules/2.6.8-2-686/kernel/drivers/i2c/chips/gl518sm.ko
> insmod: error inserting 
> '/lib/modules/2.6.8-2-686/kernel/drivers/i2c/chips/gl518sm.ko': -1 Unknown 
> symbol in module
> 
try modprobe instead of insmod, that may help

lm-sensors bug?

[wim]

Hi,

I'm trying to get lm-sensors working on my PII 400Mhz
The motherboard is an Asus AX6BC

This is the output of sensors-detect:

slayer:~# sensors-detect

This program will help you determine which I2C/SMBus modules you need to
load to use lm_sensors most effectively. You need to have i2c and
lm_sensors installed before running this program.
Also, you need to be `root', or at least have access to the /dev/i2c-*
files, for most things.
If you have patched your kernel and have some drivers built in, you can
safely answer NO if asked to load some modules. In this case, things may
seem a bit confusing, but they will still work.

It is generally safe and recommended to accept the default answers to
all
questions, unless you know what you're doing.

 We can start with probing for (PCI) I2C or SMBus adapters.
 You do not need any special privileges for this.
 Do you want to probe now? (YES/no): yes
Probing for PCI bus adapters...
Use driver `i2c-piix4' for device 00:07.3: Intel 82371AB PIIX4 ACPI
Use driver `i2c-voodoo3' for device 01:00.0: 3Dfx Voodoo Banshee
Probe succesfully concluded.

We will now try to load each adapter module in turn.
Load `i2c-piix4' (say NO if built into your kernel)? (YES/no):
Module loaded succesfully.
Load `i2c-voodoo3' (say NO if built into your kernel)? (YES/no):
Module loaded succesfully.
If you have undetectable or unsupported adapters, you can have them
scanned by manually loading the modules before running this script.

 To continue, we need module `i2c-dev' to be loaded.
 If it is built-in into your kernel, you can safely skip this.
 i2c-dev is not loaded. Do you want to load it now? (YES/no):
 Module loaded succesfully.

 We are now going to do the adapter probings. Some adapters may hang
halfway
 through; we can't really help that. Also, some chips will be double
detected;
 we choose the one with the highest confidence value in that case.
 If you found that the adapter hung after probing a certain address, you
can
 specify that address to remain unprobed. That often
 includes address 0x69 (clock chip).

Next adapter: DDC Voodoo3/Banshee adapter
Do you want to scan it? (YES/no/selectively):

Next adapter: I2C Voodoo3/Banshee adapter
Do you want to scan it? (YES/no/selectively):

Next adapter: SMBus PIIX4 adapter at 5000
Do you want to scan it? (YES/no/selectively):
Client found at address 0x2d
Probing for `Myson MTP008'... Failed!
Probing for `National Semiconductor LM78'... Failed!
Probing for `National Semiconductor LM78-J'... Failed!
Probing for `National Semiconductor LM79'... Failed!
Probing for `National Semiconductor LM80'... Failed!
Probing for `National Semiconductor LM85 or LM96000'... Failed!
Probing for `Analog Devices ADM1027, ADT7460 or ADT7463'... Failed!
Probing for `SMSC EMC6D100, EMC6D101 or EMC6D102'... Failed!
Probing for `National Semiconductor LM87'... Failed!
Probing for `National Semiconductor LM93'... Failed!
Probing for `Winbond W83781D'... Failed!
Probing for `Winbond W83782D'... Failed!
Probing for `Winbond W83783S'... Failed!
Probing for `Winbond W83791D'... Failed!
Probing for `Winbond W83792D'... Failed!
Probing for `Winbond W83791SD'... Failed!
Probing for `Winbond W83627HF'... Failed!
Probing for `Winbond W83627EHF'... Failed!
Probing for `Asus AS99127F (rev.1)'... Failed!
Probing for `Asus AS99127F (rev.2)'... Failed!
Probing for `Asus ASB100 Bach'... Failed!
Probing for `Winbond W83L784R/AR'... Failed!
Probing for `Winbond W83L785R'... Failed!
Probing for `Genesys Logic GL518SM Revision 0x00'... Success!
(confidence 6, driver `gl518sm')
Probing for `Genesys Logic GL518SM Revision 0x80'... Failed!
Probing for `Genesys Logic GL520SM'... Failed!
Probing for `Genesys Logic GL525SM'... Failed!
Probing for `Analog Devices ADM9240'... Failed!
Probing for `Dallas Semiconductor DS1780'... Failed!
Probing for `National Semiconductor LM81'... Failed!
Probing for `Analog Devices ADM1026'... Failed!
Probing for `Analog Devices ADM1025'... Failed!
Probing for `Philips NE1619'... Failed!
Probing for `Analog Devices ADM1024'... Failed!
Probing for `Analog Devices ADM1029'... Failed!
Probing for `Analog Devices ADM1030'... Failed!
Probing for `Analog Devices ADM1031'... Failed!
Probing for `Analog Devices ADM1022'... Failed!
Probing for `Texas Instruments THMC50'... Failed!
Probing for `VIA VT1211 (I2C)'... Failed!
Probing for `ITE IT8712F'... Failed!
Probing for `ITE IT8705F / SiS 950'... Failed!
Probing for `ALi M5879'... Failed!

Some chips are also accessible through the ISA bus. ISA probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.

Do you want to scan the ISA bus? (YES/no):
Probing for `National Semiconductor LM78

Re: lm-sensors watching daemon?

[Hugo Vanwoerkom]

Johannes Graumann wrote:
Hello,
I recently got lm-sensors to play along with my stock unstable 2.6.8
kernel. Now I'm looking for a daemon which utilizes the information read
from the Mobo. I have found two which do what I want (shutting down at
certain threshold values):
1) sentinelle (http://denis.corbin.free.fr/software.html)
2) mondo-daemon (http://mondo-daemon.sourceforge.net/)
The former seems quite young, while the latter smells of abandonment.
I wonder what the "debian way" is to accomplish things like shutdown at
a given temperature or fan speed - I found neither of the two
possibilities above or an alternative in the repositories.
If you have experience with this: please let me know what you use.
Thanks, Joh

I wrote my own because I did not like what any of them did. It is 
essentially simple: using the libsensors-dev you get all the data that 
gets collected. I display the data with Qt in a wharf of fvwm that fits 
only the 3 most important datapoints. Left click shows it all in a 
frame. Then if a threshold is reached I sound an alarm with NAS (because 
I did not have a pc speaker for a while). I can test only the fan, 
stopping that for a moment and that works. I could if I wanted to shut 
down the system then. I also collect the CPUtemp in a db and display the 
history of that with Qt. E.g. to show the difference with a different 
casefan I bought. FWIW my CPU temp right now is 38.975 degrees. That 
goes up to about 45 if I run a 3 hour mozilla compile and it gets hot 
here in Oaxaca...

Hugo.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: lm-sensors watching daemon?

[Dave Thayer]

On Sun, Oct 10, 2004 at 03:12:52PM -0700, Johannes Graumann wrote:
> I recently got lm-sensors to play along with my stock unstable 2.6.8
> kernel. Now I'm looking for a daemon which utilizes the information read
> from the Mobo. I have found two which do what I want (shutting down at
> certain threshold values):

Gkrellm can monitor sensors and run commands when thresholds are crossed.
The gotcha here is that it is not a background daemon, it has to be running
in somebody's X session. This may make it unsuitable for your needs.

dt
-- 
Dave Thayer   | WARNING: Persons denying the existence of 
Denver, Colorado USA  | robots may be robots themselves.
[EMAIL PROTECTED] | 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

lm-sensors watching daemon?

[Johannes Graumann]

Hello,

I recently got lm-sensors to play along with my stock unstable 2.6.8
kernel. Now I'm looking for a daemon which utilizes the information read
from the Mobo. I have found two which do what I want (shutting down at
certain threshold values):
1) sentinelle (http://denis.corbin.free.fr/software.html)
2) mondo-daemon (http://mondo-daemon.sourceforge.net/)

The former seems quite young, while the latter smells of abandonment.
I wonder what the "debian way" is to accomplish things like shutdown at
a given temperature or fan speed - I found neither of the two
possibilities above or an alternative in the repositories.

If you have experience with this: please let me know what you use.

Thanks, Joh


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

lm-sensors support for SE7501BR2 ?

[Marcin Owsiany]

Hi!

[ sorry for the cross-post, but both lists seem relevant ]

I have an Intel SE7501BR2 server motherboard, and using lm-sensors
2.6.3-5+ only detects successfully four chips like this: (using eeprom
driver)

  * Bus `SMBus I801 adapter at 0580' (Non-I2C SMBus adapter)
Busdriver `i2c-i801', I2C address 0x51
Chip `Serial EEPROM (PC-100 DIMM)' (confidence: 8)

But does not find any thermal sensors. Has anyone had more luck with
such hardware? The manual says the sensors are managed by Heceta chip
U5F10, for which google finds no good hits.

Marcin
-- 
Marcin Owsiany <[EMAIL PROTECTED]> http://marcin.owsiany.pl/
GnuPG: 1024D/60F41216  FE67 DA2D 0ACA FC5E 3F75  D6F6 3A0D 8AA0 60F4 1216


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: make-kpkg, lm-sensors + i2c ain't work

[Michal R. Hoffmann]

On 07-06-2004 18:01, Chris Metzler wrote:
On Mon, 07 Jun 2004 12:27:01 +0200
"Michal R. Hoffmann" <[EMAIL PROTECTED]> wrote:
I have problem with making debs of kernel modules: i2c and lm-sensors. 
I've downloaded sources of lm_sensors 2.8.6 (tar.gz), not the
source.deb, can it be the reason?
I've unpacked sources into /usr/src/modules/aaa
(aaa = module)
Can you elaborate on what you mean by this?  What was the specific
package that you fetched?  Did you "apt-get install lm-sensors-source"
or did you "apt-get source lm-sensors"?  And what's all this about
hmm, maybe my english is worse then I thought.
I did not downloaded i2c-source nor lm-sensors-source packages. And I did
not installed them.
I have downloaded the source from there:
http://secure.netroedge.com/~lm78/archive/i2c-2.8.4.tar.gz
http://secure.netroedge.com/~lm78/archive/lm_sensors-2.8.6.tar.gz
"aaa"?  The module source tarball should want to unpack into a
subdirectory of /usr/src/modules with the name "lm-sensors", and
put everything there.
And then I've unpacked them into:
/usr/src/modules/aaa
where aaa is properly:
i2c-2.8.4
lm_sensors-2.8.6
I hope now it is clear.
when I try
$ cd /usr/src/linux
$ su
# make-kpkg --revision blah --append-to-version blah modules_image
it ain't work - tries ang gives error message.
Are we supposed to guess what the error message is?  There are
different error messages for a reason; and without knowing what
the error message is, there's no way to help you.
OK, I do not know what is important (it looks like script listing) - so I 
paste it all:

--
cave:/usr/src/linux# make-kpkg --revision .1.02.mrh --append-to-version 
.1.02.mrh modules
for module in  ; do   \
  if test -d  $module; then\
(cd $module;  \
  if ./debian/rules KVERS="2.4.26.1.02.mrh" 
KSRC="/usr/src/linux" \
 KMAINT="Unknown Kernel Package Maintainer" 
KEMAIL="[EMAIL PROTECTED]"  \
 KPKG_DEST_DIR="/usr/src/linux/.."   \
 KPKG_MAINTAINER="Unknown Kernel Package 
Maintainer"\
 ARCH=i386\
 KPKG_EXTRAV_ARG="EXTRAVERSION=.1.02.mrh" 
\
 KDREV=".1.02.mrh" kdist; then  \
  echo "Module $module processed fine";\
  else  \
   echo "Module $module failed.";  \
   if [ "X" != "X" ]; then  \
  echo "Perhaps $module does not understand 
--rootcmd?";  \
  echo "If you see messages that indicate that it is 
not"; \
  echo "in fact being built as root, please file a 
bug ";  \
  echo "against $module."; \
   fi;  \
   echo "Hit return to Continue?";  \
	 read ans;\
  fi;   \
 );\
  fi;  \
done

---
--
misiek
***  Michal R. Hoffmann|<mailto:[EMAIL PROTECTED]>  ***
*** -= member of: KNM, ZUKiH, HCKU =-   ***

--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: make-kpkg, lm-sensors + i2c ain't work

[Chris Metzler]

On Mon, 07 Jun 2004 12:27:01 +0200
"Michal R. Hoffmann" <[EMAIL PROTECTED]> wrote:
>
> I have problem with making debs of kernel modules: i2c and lm-sensors. 
> I've downloaded sources of lm_sensors 2.8.6 (tar.gz), not the
> source.deb, can it be the reason?
> I've unpacked sources into /usr/src/modules/aaa
> (aaa = module)

Can you elaborate on what you mean by this?  What was the specific
package that you fetched?  Did you "apt-get install lm-sensors-source"
or did you "apt-get source lm-sensors"?  And what's all this about
"aaa"?  The module source tarball should want to unpack into a
subdirectory of /usr/src/modules with the name "lm-sensors", and
put everything there.


> when I try
> $ cd /usr/src/linux
> $ su
> # make-kpkg --revision blah --append-to-version blah modules_image
> 
> it ain't work - tries ang gives error message.

Are we supposed to guess what the error message is?  There are
different error messages for a reason; and without knowing what
the error message is, there's no way to help you.

-c


-- 
Chris Metzler   [EMAIL PROTECTED]
(remove "snip-me." to email)

"As a child I understood how to give; I have forgotten this grace since I
have become civilized." - Chief Luther Standing Bear


pgpyYCw0EKuww.pgp
Description: PGP signature

make-kpkg, lm-sensors + i2c ain't work

[Michal R. Hoffmann]

hello,
I have problem with making debs of kernel modules: i2c and lm-sensors. 
I've downloaded sources of lm_sensors 2.8.6 (tar.gz), not the source.deb, 
can it be the reason?
I've unpacked sources into /usr/src/modules/aaa
(aaa = module)
when I try
$ cd /usr/src/linux
$ su
# make-kpkg --revision blah --append-to-version blah modules_image

it ain't work - tries ang gives error message. I've tried
$ cd /usr/src/modules/aaa
$ su
# make all; make install
it works OK. But then I have no package, but modules installed without 
control ;-) . I'd prefer the debian way. So: can I compile with make-kpkg 
the real source, or do I need sources in deb? What am I doing wrong?

Greetings,
--
misiek
***  Michal R. Hoffmann|<mailto:[EMAIL PROTECTED]>  ***
*** -= member of: KNM, ZUKiH, HCKU =-   ***
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

hp desktop VL420 and lm-sensors

[Alexei Chetroi]

 Hi Everybody!

 Does anybody have luck to get a HP VL420 working with lm-sensors?

 I've compiled kernel with lm-sensors support
(kernel-patch-2.4-lm-sensors package version 2.8.6-3), but only eeprom
module is working. I can modprobe maxilife module, but it doesn't appear
in sensors output.

 Regards

--
Alexei Chetroi


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: lm-sensors

[hugo vanwoerkom]

hugo vanwoerkom wrote:
Alex Lorca wrote:

A note on the jpeg images: the jumps in temperature occur because I turn 
an external fan on/off. That makes a huge difference in CPU temps. It 
was noted in this list a while ago: best is to maintain positive 
pressure inside the case with a fan: you keep out dust and you cool the 
case. Where I am the room temp can hit 37 degrees (centigrade) and with 
the external fan the CPU temp is no more than 10 degrees more. But my 
wife cannot stand the fan and so she tuns it off: up goes the temp.

Hugo

--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: lm-sensors

[hugo vanwoerkom]

Alex Lorca wrote:
hi all

i'm trying to install lm-sensors in a debian woody 2.4.25
i made:
- apt-get lm-sensors-source i2c-source
- unpack and make-kpkg modules-image
- install the .debs
- run sensors-detect and detected the following:
# 2C adapter drivers
# modprobe unknown adapter Philips Parallel port adapter using Bit-shift
# algorithm
# modprobe unknown adapter Philips Parallel port adapter using Bit-shift
# algorithm
i2c-viapro
# I2C chip drivers
max6650
saa1064
smbus-arp
asb100
but when i run /etc/init.d/modutils:

Calculating module dependencies... done.
Loading modules: usb-uhci input usbkbd keybdev acm modprobe: Can't
locate module acm
CDCEther modprobe: Can't locate module CDCEther
ntfs cmpci ide-scsi usbnet modprobe: Can't locate module usbnet
ipx i2c-viapro max6650 modprobe: Can't locate module max6650
saa1064 modprobe: Can't locate module saa1064
smbus-arp asb100 modprobe: Can't locate module asb100
where can i find those modules??
is ther other package to install??
I do it manually. I roll my own kernel with the Backstreet Ruby patch, 
so I end up with kernel 2.4.25.

Then I untar lm-sensors.tar. gz into the /usr/src directory. This has 
all the supported modules in it.

Then I run make-kpkg --revision 1 kernel_image modules_image from the 
/usr/src/linux-2.4.25 dir. It runs very quick because I only load the 
modules I need which are very few.

I have set previous to this @gcc->gcc-2.95 because the lm-sensors 
modules have string constants in them that span several lines, to which 
all later compilers complain, but not 2.95.

This produces 2 debs in the /usr/src dir and I just dpkg -i them.
The modules one will spawn a bunch of unresolved symbols but not when 
you boot the kernel.

Then I install:
*   dpkg -i i2c-2.4.25-1-386
*   dpkg -i lm-sensors
*   dpkg -i libsensors1
*   dpkg -i libsnesors-dev
(The reason I do dpkg is because I only have the first 6 Sarge CD's and 
these debs are beyond that... :-()

This gives me access to the data that is generated by the lm-sensors 
modules.

I have written 2 Qt apps that use the data: one a wmmaker style display 
that sits in a fvwm wharf that displays 3 things: fan speed, CPU temp 
and mobo temp.

Second a Qt app that dumps CPU temp to a db and one that digs it out of 
there to display it.

You can see jpeg's of that one here: http colon  slash slash esquipulas 
dot homeunix dot com slash modtempdisp dot nz dot jpeg

and: http colon  slash slash esquipulas dot homeunix dot com slash 
modtempdisp dot zoom dot jpeg

Hugo









































--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

lm-sensors

[Alex Lorca]

hi all

i'm trying to install lm-sensors in a debian woody 2.4.25
i made:

- apt-get lm-sensors-source i2c-source
- unpack and make-kpkg modules-image
- install the .debs
- run sensors-detect and detected the following:

# 2C adapter drivers
# modprobe unknown adapter Philips Parallel port adapter using Bit-shift
# algorithm
# modprobe unknown adapter Philips Parallel port adapter using Bit-shift
# algorithm
i2c-viapro
# I2C chip drivers
max6650
saa1064
smbus-arp
asb100

but when i run /etc/init.d/modutils:

Calculating module dependencies... done.
Loading modules: usb-uhci input usbkbd keybdev acm modprobe: Can't
locate module acm
CDCEther modprobe: Can't locate module CDCEther
ntfs cmpci ide-scsi usbnet modprobe: Can't locate module usbnet
ipx i2c-viapro max6650 modprobe: Can't locate module max6650
saa1064 modprobe: Can't locate module saa1064
smbus-arp asb100 modprobe: Can't locate module asb100

where can i find those modules??
is ther other package to install??


--
Alex


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: a bit (asus!) confused about i2c and lm-sensors

[Paul Morgan]

On Sun, 08 Feb 2004 15:04:21 -0800, Nano Nano wrote:

[snip]

Nano, I don't know anything about compiling the 2.6 kernel, I'm sticking
with 2.4 series for now.  The only problem I had with compiling the
lmsensors modules was that there were two author-related macros which
needed fixing for the stricter gcc 3.3.2 compiler.

-- 
paul

It is important to realize that any lock can be picked with a big
enough hammer.
   -- Sun System & Network Admin manual



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: a bit (asus!) confused about i2c and lm-sensors

[Nano Nano]

On Sun, Feb 08, 2004 at 06:40:26AM -0500, Paul Morgan wrote:
> On Sun, 08 Feb 2004 01:08:40 -0800, Nano Nano wrote:
> 
> > I have an ASUS P4C800.  I have 2.6.2 kernel.  I wish to see my CPU and
> > Mobo temps (and ideally fan speeds) like Asus PC Probe shows in Windows.
[snip]
> The first thing you should do is run sensors-detect to determine which
> modules you'll need.
> 
> You'll have to install lm-sensors-source and compile the modules for your
> kernel.

I think I'm having problems because I'm having problems with modules in 
general in kernel 2.6 series.  Almost everything I used to use with 
hotplug has to be compiled in, which hotplug now warns about.

I tried just enabling everything i2c-related in the kernel as a 
built-in, but the kernel then hanged on startup.  I have 
module-init-tools installed.  What's wrong with me and modules in 2.6?

# make-kpkg --added-modules=i2c modules-image
[snip]
make[3]: *** No rule to make target 
`/usr/src/linux-2.6.2/include/linux/modversions.h', needed by 
`kernel/i2c-pport.d'.  Stop.

# make-kpkg --added-modules=i2c modules-image
[fails with same error]

# egrep -i "module|versi" .config
# Loadable module support
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
CONFIG_MODVERSIONS=y

# sensors-detect
[snip] 
 BIOS vendor (ACPI): ACPIAM
 System vendor (DMI): To Be Filled By O.E.M.
 BIOS version (DMI): 080009
[snip]
Probing for PCI bus adapters...
Use driver `i2c-i801' for device 00:1f.3: Intel 82801EB ICH5
[snip]
Load `i2c-i801' (say NO if built into your kernel)? (YES/no):
FATAL: Module i2c_i801 not found.
[snip]
 i2c-dev is not loaded. Do you want to load it now? (YES/no):
FATAL: Module i2c_dev not found.
[snip]
Couldn't open /proc/bus/i2c?!? at /usr/sbin/sensors-detect line 3970, 
 line 4.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: a bit (asus!) confused about i2c and lm-sensors

[Paul Morgan]

On Sun, 08 Feb 2004 01:08:40 -0800, Nano Nano wrote:

> I have an ASUS P4C800.  I have 2.6.2 kernel.  I wish to see my CPU and
> Mobo temps (and ideally fan speeds) like Asus PC Probe shows in Windows.
> 

I have successfully installed lmsensors, (using 2.2.23 and 2.4.24
kernels) and it works great, especially with gkrellm. Try this for
starters:

http://www2.lm-sensors.nu/~lm78/cvs/lm_sensors2/doc/lm_sensors-FAQ.html

The first thing you should do is run sensors-detect to determine which
modules you'll need.

You'll have to install lm-sensors-source and compile the modules for your
kernel.  Anyway, it's all in the documentation at the site above.
Although everything is in debian, so you should compile and install the
"debian way" where that differs from the documentation.

I didn't actually use the above link, I can't remember what I read (apart
from the kernel source i2c docs.

-- 
paul

It is important to realize that any lock can be picked with a big
enough hammer.
   -- Sun System & Network Admin manual



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

a bit (asus!) confused about i2c and lm-sensors

[Nano Nano]

I have an ASUS P4C800.  I have 2.6.2 kernel.  I wish to see my CPU and 
Mobo temps (and ideally fan speeds) like Asus PC Probe shows in Windows.

(1) Which of the following should I have installed?
$ apt-cache search "sensors|i2c"
i2c-source - sources for drivers for the i2c bus
libsensors2 - Library to read temperature/voltage/fan sensors
lm-sensors-source - Kernel drivers to read temperature/voltage/fan sensors (source)
eep24c - read and write serial I2C eeprom devices
gdesklets - an advanced architecture for desktop applets
gdesklets-data - displays and sensors for gdesklets
ksensors - lm-sensors frontend for KDE
libglui2c102 - GLUI, a C++ GLUT based GUI library - runtime support
libprelude-dev - Hybrid Intrusion Detection System [ Development files ]
libprelude0 - Hybrid Intrusion Detection System [ Base library ]
libsensors-dev - Lm-sensors development kit
lm-sensors - Utilities to read temperature/voltage/fan sensors
phpgroupware-phpsysinfo - phpGroupWare phpSysInfo module
prelude-lml - Hybrid Intrusion Detection System [ Log Monitoring Lackey ]
prelude-manager - Hybrid Intrusion Detection System [ Report Manager ]
prelude-nids - Hybrid Intrusion Detection System [ Network sensor ]
sensord - Hardware sensor information logging daemon
smartcard - A smartcard utility for Linux
wmgtemp - Temperature sensor dockapp for Window Maker
wmsensors - WindowMaker dock applet for lmsensors
xml-rpc-api2cpp - Generate C++ wrapper classes for XML-RPC servers.
xsensors - A hardware health information viewer

(2) Which of the following should I have set in the kernel?
$ egrep -i "sensor|i2c" /boot/config-2.6.2
# I2C support
CONFIG_I2C=y
CONFIG_I2C_CHARDEV=y
# I2C Algorithms
# CONFIG_I2C_ALGOBIT is not set
# CONFIG_I2C_ALGOPCF is not set
# I2C Hardware Bus support
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI15X3 is not set
# CONFIG_I2C_AMD756 is not set
# CONFIG_I2C_AMD8111 is not set
# CONFIG_I2C_ELV is not set
# CONFIG_I2C_I801 is not set
# CONFIG_I2C_I810 is not set
# CONFIG_I2C_ISA is not set
# CONFIG_I2C_NFORCE2 is not set
# CONFIG_I2C_PARPORT_LIGHT is not set
CONFIG_I2C_PIIX4=y
# CONFIG_I2C_PROSAVAGE is not set
# CONFIG_I2C_SAVAGE4 is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
# CONFIG_I2C_VELLEMAN is not set
# CONFIG_I2C_VIA is not set
# CONFIG_I2C_VIAPRO is not set
# CONFIG_I2C_VOODOO3 is not set
# I2C Hardware Sensors Chip support
CONFIG_I2C_SENSOR=y
# CONFIG_SENSORS_ADM1021 is not set
CONFIG_SENSORS_ASB100=y
# CONFIG_SENSORS_EEPROM is not set
# CONFIG_SENSORS_IT87 is not set
# CONFIG_SENSORS_LM75 is not set
# CONFIG_SENSORS_LM78 is not set
# CONFIG_SENSORS_LM83 is not set
# CONFIG_SENSORS_LM85 is not set
# CONFIG_SENSORS_LM90 is not set
# CONFIG_SENSORS_VIA686A is not set
CONFIG_SENSORS_W83781D=y
CONFIG_SENSORS_W83L785TS=y
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_BUS is not set
# CONFIG_I2C_DEBUG_CHIP is not set

(3) What should I do then?

-Thanks


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: LM Sensors

[David Z Maze]

"C" <[EMAIL PROTECTED]> writes:

> Any one got any advice how to get lmsensors working on a 2.4.21-5-k7
> kernel?

My best advice is to build your kernel from source, disable anything
and everything i2c-related in the kernel source, and then install the
lm-sensors-source and i2c-source packages and build those kernel
modules separately using 'make-kpkg modules-image'.  There are
prebuilt modules in unstable for kernel 2.4.22-1, but there are really
bad conflicts with the i2c modules in the kernel, and the best way
around that is probably to delete outright
/lib/modules/2.4.22-1-mumble/kernel/drivers/i2c.  :-/  I'm quite open
to suggestions for good ways to resolve this; please comment on bug
209228.

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


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

LM Sensors

[C]

Any one got any advice how to get lmsensors working on a 2.4.21-5-k7 kernel?

Thanks
 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: booting problems after installing lm-sensors kernel modules from sid / can't mount root fs

[Arnt Karlsen]

On Sun, 21 Sep 2003 09:45:17 +1000, 
Herbert Xu <[EMAIL PROTECTED]> wrote in message 
<[EMAIL PROTECTED]>:

> Manuel Bilderbeek <[EMAIL PROTECTED]> wrote:
> > 
> >> So, I took my older (Woody-beta) installation cd and booted with
> >> "rescue root=/dev/hda6". Also, this didn't work out: again a kernel
> >> panic, because it can't mount the root fs... This time there was
> >> some error about "unsupported optional features".
> > 
> > Any idea about this then?
> 
> It means that your rescue floppy does not support ext3.  ext3
> filesystems requiring a journal recovery cannot be mounted as ext2.

..I lost you here, _I_ mounted my ext3 /var as ext2 upon a dead journal.

..if OP has a problem getting his box going with ext3 because of cooked 
journals, he should try ext2 read-only first, to see WTF is going on.

-- 
..med vennlig hilsen = with Kind Regards from Arnt... ;-)
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: booting problems after installing lm-sensors kernel modules from sid / can't mount root fs

[Herbert Xu]

Manuel Bilderbeek <[EMAIL PROTECTED]> wrote:
> 
>> So, I took my older (Woody-beta) installation cd and booted with "rescue 
>> root=/dev/hda6". Also, this didn't work out: again a kernel panic, 
>> because it can't mount the root fs... This time there was some error 
>> about "unsupported optional features".
> 
> Any idea about this then?

It means that your rescue floppy does not support ext3.  ext3 filesystems
requiring a journal recovery cannot be mounted as ext2.
-- 
Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ )
Email:  Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: booting problems after installing lm-sensors kernel modules from sid / can't mount root fs

[David Z Maze]

Manuel Bilderbeek <[EMAIL PROTECTED]> writes:

> A couple of days ago, I installed these packages from sid:
>   lm-sensors-2.4.21-4-k7 2.8.0-1
>   i2c-2.4.21-4-k7 2.8.0-1
>
> I have done this before many times, to save myself the trouble of
> compiling these kernel modules myself. I'm running a testing system
> with the 2.4.21-4-k7 stock kernel, you see.
>
> Anyway, this time it didn't work out. When I rebooted my system next
> time, there was some error during boot which had at least this text in
> it "S20modutils Segmentation fault".

lm-sensors/i2c 2.8.0 kind of have some, uh, major conflicts with the
stock kernels.  See http://bugs.debian.org/209228.  You either need to
downgrade lm-sensors/i2c or forcibly move the modules in
/lib/modules/2.4.21-4-k7/drivers/i2c out of the way.

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


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: booting problems after installing lm-sensors kernel modules from sid / can't mount root fs

[Manuel Bilderbeek]

Manuel Bilderbeek wrote:
OK, but I still have the LinuxOLD entry in my LILO menu. Since I'm 
running stock kernels, this should be starting my previous kernel 
anytime. So, I chose the option, and it booted until it had to mount the 
root fs. There I got a kernel panic: can't mount root fs. (No clear 
reason was mentioned...) Oops. My root fs is /dev/hda6, which is an ext3 
fs. Even specifying
LinuxOLD root=/dev/hda6
didn't help.
OK, problem is solved, thanks to Mike Dornberger (and sorry for not 
checking this myself, I remembered it worked before, so I assumed it was 
OK):
I forgot this line in my lilo.conf:
initrd=/initrd.img.old

I remember people using a stock kernel for the first time and having 
this problem too. It seems that at least some older version of the 
installation scripts do not adjust the lilo.conf correctly. Someone 
please check if this is done properly now (i.e. addition of the initrd 
option).


So, I took my older (Woody-beta) installation cd and booted with "rescue 
root=/dev/hda6". Also, this didn't work out: again a kernel panic, 
because it can't mount the root fs... This time there was some error 
about "unsupported optional features".
Any idea about this then?

Best regards,

Manuel Bilderbeek

--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

booting problems after installing lm-sensors kernel modules from sid / can't mount root fs

[Manuel Bilderbeek]

Hello all,

A couple of days ago, I installed these packages from sid:
 lm-sensors-2.4.21-4-k7 2.8.0-1
 i2c-2.4.21-4-k7 2.8.0-1
I have done this before many times, to save myself the trouble of 
compiling these kernel modules myself. I'm running a testing system with 
the 2.4.21-4-k7 stock kernel, you see.

Anyway, this time it didn't work out. When I rebooted my system next 
time, there was some error during boot which had at least this text in 
it "S20modutils Segmentation fault". So, my interpretation is that 
during the loading of these new kernel modules, there occured a 
segmentation fault in the module load program. After this message there 
was a little bit more text (about USB), but then a hang.
In other words: I couldn't boot the system anymore.

OK, but I still have the LinuxOLD entry in my LILO menu. Since I'm 
running stock kernels, this should be starting my previous kernel 
anytime. So, I chose the option, and it booted until it had to mount the 
root fs. There I got a kernel panic: can't mount root fs. (No clear 
reason was mentioned...) Oops. My root fs is /dev/hda6, which is an ext3 
fs. Even specifying
LinuxOLD root=/dev/hda6
didn't help.

So, I took my older (Woody-beta) installation cd and booted with "rescue 
root=/dev/hda6". Also, this didn't work out: again a kernel panic, 
because it can't mount the root fs... This time there was some error 
about "unsupported optional features".

I tried some more tricks, like making boot floppies with a bf2.4 flavour 
(of Woody), which I got from some Debian FTP. No go, can't mount root fs.

I tried some more suggestions from people in #debian on 
irc.freenode.net, but nothing worked.

In the mean time, I have fixed my "Linux" boot, by using a Knoppix cd 
and removing the module names from /etc/modules. However, I still can't 
boot my LinuxOLD stuff.

Is there anyone who can tell me what is going wrong?
I know I could boot my LinuxOLD thing in the past. It's just a long time 
ago I needed it.

Best regards,

Manuel Bilderbeek

--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

How to enable beep when a lm-sensors alarm is fired ?

[Geraldo Lopes de souza]

How to enable beep whe a lm-sensors alarm is fired ?

Debian 3.0r1 i686, lm-sensors as module

sensors output :

via686a-isa-6000
Adapter: ISA adapter
Algorithm: ISA algorithm
CPU core:  +1.55 V  (min =  +1.17 V, max =  +1.79 V)
+2.5V: +2.42 V  (min =  +2.24 V, max =  +2.74 V)
I/O:   +3.25 V  (min =  +2.95 V, max =  +3.62 V)
+5V:   +4.75 V  (min =  +4.47 V, max =  +5.49 V)
+12V: +12.16 V  (min = +10.79 V, max = +13.18 V)
CPU Fan:  4891 RPM  (min = 3792 RPM, div = 2)
SYS Temp:  +32.2°C  (limit =  +45°C, hysteresis =  +40°C)
CPU Temp:  +42.7°C  (limit =  +60°C, hysteresis =  +55°C)


Thanks in advance.

Geraldo Lopes de Souza




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: lm-sensors

[David Z Maze]

Menno <[EMAIL PROTECTED]> writes:

>  >> fakeroot debian/rules kdist_image \
>  >> KSRC=/usr/src/kernel-headers-2.4.18-1-686 \
>  >> KVERS=2.4.18-1-686 KDREV=2.4.18-11
>
>  > This ignores the kernel-source package you
>  > installed entirely, incidentally.
>  > But if it works, that's good to hear.
>
> But somehow it is depending on this. I got the following errors
> without the symbolic link to kernel-source-2.4.18, and that is also
> the reason why I made a copy of /boot/config-2.4.18-1-686
>
> grep: /usr/src/linux/Makefile: No such file or directory
> grep: /usr/src/linux/include/linux/autoconf.h: No such file or directory
> grep: /usr/src/linux/.config: No such file or directory
> (last line repeating about 30 times)

Yes, I know; that's an issue with the way the upstream Makefile is
written.  That error message shouldn't actually kill the build, and
you can safely ignore it.

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


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: lm-sensors

[Menno]

>> fakeroot debian/rules kdist_image \
>> KSRC=/usr/src/kernel-headers-2.4.18-1-686 \
>> KVERS=2.4.18-1-686 KDREV=2.4.18-11
> This ignores the kernel-source package you
> installed entirely, incidentally.
> But if it works, that's good to hear.
But somehow it is depending on this. I got the following errors without the 
symbolic link to kernel-source-2.4.18, and that is also the reason why I 
made a copy of /boot/config-2.4.18-1-686

grep: /usr/src/linux/Makefile: No such file or directory
grep: /usr/src/linux/include/linux/autoconf.h: No such file or directory
grep: /usr/src/linux/.config: No such file or directory
   (last line repeating about 30 times)
Thanks again,
Menno.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: lm-sensors

[David Z Maze]

Menno <[EMAIL PROTECTED]> writes:

> David Z Maze <[EMAIL PROTECTED]> writes:
>
>  > I believe unstable's make-kpkg has
>  > some support for building kernel modules given
>
> I use stable, and there is some kind of support in it. According to
> the docs in /usr/share/doc/kernel-package/README.modules is should do
> something like this:
>
> make-kpkg --revision number kernel_image
> make-kpkg modules_image

Note that the first step there builds a custom kernel from unpacked
source; see also
http://newbiedoc.sourceforge.net/system/kernel-pkg.html.  The second
step assumes the kernel tree from the first.

> I suspect that I have to chage something in the Makefile of the
> kernel-source to get this right. Should line 4 look like EXTRAVERSION
> = -1-686 ???

You want to add --append-to-version -1-686 to your make-kpkg flags.

>  > bug 189513 points at
>  > http://lists.debian.org/debian-devel/2002/debian-devel-200203/msg01794.html,
>  > suggests doing this:
>
> Yes, that helped me. In the end I did this, and I was able to installa
> the .deb file:

<*snip*>

>ln -s kernel-source-2.4.18 linux
>cd /usr/src/linux

(I don't generally recommend doing that: at some point you're going to
boot a different kernel, and the symlink is going to be wrong, and
you're going to compile something that sees the symlink and assumes
it's correct.)

>fakeroot debian/rules kdist_image \
>   KSRC=/usr/src/kernel-headers-2.4.18-1-686 \
>   KVERS=2.4.18-1-686 KDREV=2.4.18-11

This ignores the kernel-source package you installed entirely,
incidentally.  But if it works, that's good to hear.

> Is this "standard procedure"? Do it again when kernel 2.4.18-14 is
> released?

Yes, sadly, and yes.

> Or, will this be easier in the next release of Debian (as in unstable?).

I'm making a somewhat vague effort to provide precompiled kernel
modules in unstable, but it's tricky keeping up with the current
kernels.  lm-sensors 2.8.0, with precompiled modules for kernel
2.4.21-4, is in the incoming queue waiting for ftpmaster approval, but
kernel 2.4.21-5 is current in unstable now.

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


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: lm-sensors

[Menno]

David Z Maze <[EMAIL PROTECTED]> writes:

> I believe unstable's make-kpkg has
> some support for building kernel modules given
I use stable, and there is some kind of support in it. According to the 
docs in /usr/share/doc/kernel-package/README.modules is should do something 
like this:

make-kpkg --revision number kernel_image
make-kpkg modules_image
But it keeps complaining about version numbers and dependencies not being 
correct when I try to install the .deb file make-kpkg is producing (only 
installing the lm-sensors-..-.deb).

I suspect that I have to chage something in the Makefile of the 
kernel-source to get this right. Should line 4 look like EXTRAVERSION = 
-1-686 ???

> bug 189513 points at 
http://lists.debian.org/debian-devel/2002/debian-devel-200203/msg01794.html,
> suggests doing this:

Yes, that helped me. In the end I did this, and I was able to installa the 
.deb file:

  cd /tmp
  dpkg -i kernel-image-2.4.18-1-686_2.4.18-11_i386.deb
  dpkg -i kernel-source-2.4.18_2.4.18-13_all.deb
  dpkg -i kernel-headers-2.4.18-1-686_2.4.18-11.deb
  dpkg -i lm-sensors-source-2.6.3-5.deb
  cd /usr/src
  tar xjf kernel-source-2.4.18.tar.bz2
  tar xzf lm-sensors.tar.gz
  ln -s kernel-source-2.4.18 linux
  cd /usr/src/linux
  cp /boot/config-2.4.18-1-686 ./.config
  fakeroot debian/rules kdist_image \
 KSRC=/usr/src/kernel-headers-2.4.18-1-686 \
 KVERS=2.4.18-1-686 KDREV=2.4.18-11
  cd /usr/src;ls -l

  -rw-r--r--  116612 Sep  3 21:10 
lm-sensors-2.4.18-1-686_2.6.3-5+2.4.18-11_i386.deb

  dpkg -i lm-sensors-2.4.18-1-686_2.6.3-5+2.4.18-11_i386.deb

Is this "standard procedure"? Do it again when kernel 2.4.18-14 is released?
Or, will this be easier in the next release of Debian (as in unstable?).
Thanks,
Menno.




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: lm-sensors

[Shyamal Prasad]

"no-spam" == no-spam   writes:

no-spam> Should I compile it from the lm-sensors-source package?
no-spam> What is the easiest way to do this?

It's been two years, but I downloaded the lm-sensors-source package
and built it following the instructions that came with the package
(for the stock 2.4.18-k7 kernel). The only thing I remember was that
the process was quite forgettable. Now, getting the sensors pacakge
configured correctly was a different story ;-)


Relevant output from dpkg is:

ii  libsensors1   2.6.3-5
Library to read temperature/voltage/fan sensors
ii  lm-sensors-2.4.18-k7  2.6.3-1+10.00.Custom 
Kernel drivers to read temperature/voltage/fan sensors
ii  lm-sensors-source 2.6.3-5 
Kernel drivers to read temperature/voltage/fan sensors (source)

The second package is my custom built .deb

Cheers!
Shyamal


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: lm-sensors

[David Z Maze]

Menno <[EMAIL PROTECTED]> writes:

> Until recently I have used the packages:
> kernel-image-2.4.18-686   2.4.18-5
> lm-sensors-2.4.18-686 2.6.3-5+2.4.18-5
>   (from http://people.debian.org/~blade/misc/modules-i386/2.4.18-686/ )
> lm-sensors2.6.3-5
> libsensors1   2.6.3-5
> sensord   2.6.3-5
>
> Because of the kernel upgrade I have now installed:
> kernel-image-2.4.18-1-686 2.4.18-11
> lm-sensors2.6.3-5
> libsensors1   2.6.3-5
> sensord       2.6.3-5
>
> Does anyone know how to get lm-sensors-2.4.18-1-686 .deb files ?
>
> Should I compile it from the lm-sensors-source package? What is the
> easiest way to do this?

Which distribution are you using?  I believe unstable's make-kpkg has
some support for building kernel modules given
kernel-headers-2.4.18-1-686 and lm-sensors-source, but I haven't
actually tried this.  Let's see...otherwise, bug 189513 points at
http://lists.debian.org/debian-devel/2002/debian-devel-200203/msg01794.html,
which suggests doing this:

  cd /usr/src
  tar xzf lm-sensors.tar.gz
  cd modules/lm-sensors
  fakeroot debian/rules kdist_image \
KSRC=/usr/src/kernel-headers-2.4.18-1-686 \
KVERS=2.4.18-686 KDREV=2.4.18-4

which should, given write permission in /usr/src, generate module
packages for you as if you had run 'make-kpkg modules-image'.

If you're tracking unstable, lm-sensors and i2c 2.8.0 have both been
uploaded, but are awaiting approval; the uploaded packages include
prebuilt modules for kernel 2.4.21-4.  I should rebuild these for
2.4.21-5 and repeat.

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


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: lm-sensors

[Andreas Janssen]

Hello

Menno (<[EMAIL PROTECTED]>) wrote:

> Until recently I have used the packages:
> kernel-image-2.4.18-686   2.4.18-5
> lm-sensors-2.4.18-686 2.6.3-5+2.4.18-5
> (from http://people.debian.org/~blade/misc/modules-i386/2.4.18-686/ )
> lm-sensors2.6.3-5
> libsensors1   2.6.3-5
> sensord   2.6.3-5
> 
> Because of the kernel upgrade I have now installed:
> kernel-image-2.4.18-1-686 2.4.18-11
> lm-sensors2.6.3-5
> libsensors1   2.6.3-5
> sensord       2.6.3-5
> 
> Does anyone know how to get lm-sensors-2.4.18-1-686 .deb files ?
> 
> Should I compile it from the lm-sensors-source package? What is the
> easiest way to do this?

I don't know if there are precompiled packages with the lm-sensor
modules for your kernel, but you can compile the modules and create
your own package with make-kpkg from the kernel-package package. There
is some Documentation available here:

<http://newbieDoc.sourceForge.net/system/kernel-pkg.html>

best regards
Andreas Janssen

-- 
Andreas Janssen
[EMAIL PROTECTED]
PGP-Key-ID: 0xDC801674
Registered Linux User #267976


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: lm-sensors

[[EMAIL PROTECTED]]

Hi there!

you may use 'apt-get install kernel-image-2.4.18-686' and you'll install 
 all the needed packages.

Regards

Menno wrote:
Hi,

Until recently I have used the packages:
kernel-image-2.4.18-686    2.4.18-5
lm-sensors-2.4.18-6862.6.3-5+2.4.18-5
(from http://people.debian.org/~blade/misc/modules-i386/2.4.18-686/ )
lm-sensors2.6.3-5
libsensors12.6.3-5
sensord2.6.3-5
Because of the kernel upgrade I have now installed:
kernel-image-2.4.18-1-686    2.4.18-11
lm-sensors2.6.3-5
libsensors12.6.3-5
sensord2.6.3-5
Does anyone know how to get lm-sensors-2.4.18-1-686 .deb files ?

Should I compile it from the lm-sensors-source package? What is the 
easiest way to do this?

Thanks,
Menno.





--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

lm-sensors

[Menno]

Hi,

Until recently I have used the packages:
kernel-image-2.4.18-686 2.4.18-5
lm-sensors-2.4.18-686   2.6.3-5+2.4.18-5
(from http://people.debian.org/~blade/misc/modules-i386/2.4.18-686/ )
lm-sensors  2.6.3-5
libsensors1 2.6.3-5
sensord 2.6.3-5
Because of the kernel upgrade I have now installed:
kernel-image-2.4.18-1-686   2.4.18-11
lm-sensors  2.6.3-5
libsensors1 2.6.3-5
sensord 2.6.3-5
Does anyone know how to get lm-sensors-2.4.18-1-686 .deb files ?

Should I compile it from the lm-sensors-source package? What is the easiest 
way to do this?

Thanks,
Menno.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: lm-sensors i2c-viapro

[David Z Maze]

"Tit \"Black\" Petric" <[EMAIL PROTECTED]> writes:

> im running latest sid (regularely updated), and i installed lm-sensors just
> now. the sensors-detect report that i should load "i2c-viapro" which is
> quite right, but that module doesnt exist under the installed kernel.
>
> is there any way to get the i2c-viapro module without installing kernel
> source and compiling it by hand? (if that would acctually work).
>
> why doesnt i2c-viapro.o come bundled with the kernel-image ?

If memory serves, i2c-viapro is part of the lm-sensors distribution
(not the i2c distribution).  If you're using a stock 2.4.20 kernel,
you should install the relevant lm-sensors and i2c kernel module
package; otherwise, you'll need to build your own from
lm-sensors-source and i2c-source.  With a little bit of effort, you
can build modules against the relevant kernel-headers package; looking
at what debian/rules does to build against a single kernel (I think,
the build-a-module target, or something like that) should help you.

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


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

lm-sensors i2c-viapro

[Tit \"Black\" Petric]

im running latest sid (regularely updated), and i installed lm-sensors just
now. the sensors-detect report that i should load "i2c-viapro" which is
quite right, but that module doesnt exist under the installed kernel.

is there any way to get the i2c-viapro module without installing kernel
source and compiling it by hand? (if that would acctually work).

why doesnt i2c-viapro.o come bundled with the kernel-image ?

regards,
Tit Petric



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: LM-Sensors on an ASUS P4B533

[Mike Dresser]

On Fri, 4 Apr 2003 [EMAIL PROTECTED] wrote:

> Once you've scoped out the lm-sensors situation, go here for hints on
> building that kernel with kernel-package:
>
> http://newbiedoc.sourceforge.net/system/kernel-pkg.html
>
> Kevin

I eventally got bored enough to test out what a make-kpkg would do, and
did all taht listed.  Much more work than my current system,
unfortunately.

Mike


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: LM-Sensors on an ASUS P4B533

[Mike Dresser]

On Fri, 4 Apr 2003, Troy Arnold wrote:

> > Two:
> >
> > Is this ASUS P4B533 supported by the i2c/lmsensors found in Sid?
>
> As the README says, lm-sensors doesn't support /motherboards/, it supports
> /chips/.  To find out for sure you'd need to look in your motherboard

Doh, wrong semantics on my side.  It uses the ASBach100, or something
like that.  It looks like even the version in unstable doesn't support
the chipset yet.

> http://secure.netroedge.com/~lm78/supported.html

Listed there, not listed in the unstable version.

> With your current setup, do any of the base modules successfully load
> into your kernel?

Nothing.  Tried it on another machine (my old gigabyte dual mb, which has
a w83781d) and it works fine there.

Mike


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: LM-Sensors on an ASUS P4B533

[ronin2]

On Fri, 4 Apr 2003 14:21:15 -0500 (EST)
Mike Dresser <[EMAIL PROTECTED]> wrote:

> I looked for various howto's, but they all assume you're running prebuilt
> kernels, unfortunately.

Once you've scoped out the lm-sensors situation, go here for hints on
building that kernel with kernel-package:

http://newbiedoc.sourceforge.net/system/kernel-pkg.html

Kevin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: LM-Sensors on an ASUS P4B533

[David Z Maze]

Mike Dresser <[EMAIL PROTECTED]> writes:

> How are you supposed to install the lm-sensors-source when you compile
> your own kernels.  the resulting file from make-kpkg modules_install
> depends on kernel-image-2.4.20.  I just --force-depends'd it in, I assume
> that's not the proper way.

This works fine if you build your kernel with make-kpkg, which
Everybody Should Do (TM).  Otherwise, try 'debian/rules
modules-nokpkg' as root from your unpacked lm-sensors-source tree.

> Is this ASUS P4B533 supported by the i2c/lmsensors found in Sid?

Well, it's not listed (under that name, anyways) on
http://secure.netroedge.com/~lm78/supported.html.  The lm-sensors in
sid is slightly old; even so, it looks like the newer version doesn't
support it.

> I looked for various howto's, but they all assume you're running prebuilt
> kernels, unfortunately.

/usr/share/doc/lm-sensors-source/README.Debian.gz should tell you how
to build lm-sensors both with and without kernel-package.

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


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: LM-Sensors on an ASUS P4B533

[Troy Arnold]

Interesting... I just battled lm-sensors last night. :)

On Fri, Apr 04, 2003 at 02:21:15PM -0500, Mike Dresser wrote:
> Two questions:
> 
> One:
> 
> How are you supposed to install the lm-sensors-source when you compile
> your own kernels.  the resulting file from make-kpkg modules_install
> depends on kernel-image-2.4.20.  I just --force-depends'd it in, I assume
> that's not the proper way.

I don't know about The Debian Way either.  Since I'm still most
comfortable building my kernels from kernel.org bz2balls, I just grabbed
the i2c and lm-sensors source (from http://secure.netroedge.com/~lm78/)
and built that against my kernel.

> Two:
> 
> Is this ASUS P4B533 supported by the i2c/lmsensors found in Sid?

As the README says, lm-sensors doesn't support /motherboards/, it supports
/chips/.  To find out for sure you'd need to look in your motherboard
manual or google to find out what chips make up your motherboard.  Then
check the supported chips page:
http://secure.netroedge.com/~lm78/supported.html

With your current setup, do any of the base modules successfully load
into your kernel?

One last thing:
This slight mod was needed to get lm-sensors to build with gcc-3.2:
$ diff -u Makefile.orig Makefile

--- Makefile.orig   2003-04-04 12:59:00.0 -0800
+++ Makefile2003-04-04 13:09:59.0 -0800
@@ -178,7 +178,8 @@
 # PROGCPPFLAGS/PROGCFLAGS is to create non-kernel object files (which are linked into 
executables).
 # ARCPPFLAGS/ARCFLAGS are used to create archive object files (static libraries).
 # LIBCPPFLAGS/LIBCFLAGS are for shared library objects.
-ALL_CPPFLAGS := -I. -Ikernel/include -I$(I2C_HEADERS) -I$(LINUX_HEADERS)
+#ALL_CPPFLAGS := -I. -Ikernel/include -I$(I2C_HEADERS) -I$(LINUX_HEADERS)
+ALL_CPPFLAGS := -I. -Ikernel/include -I$(I2C_HEADERS) -idirafter $(LINUX_HEADERS)
 ALL_CFLAGS := -O2 
 
 ifeq ($(DEBUG),1)

Works well now, and even pointed me to a failing videocard fan of which
I was unaware.

-troy


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

LM-Sensors on an ASUS P4B533

[Mike Dresser]

Two questions:

One:

How are you supposed to install the lm-sensors-source when you compile
your own kernels.  the resulting file from make-kpkg modules_install
depends on kernel-image-2.4.20.  I just --force-depends'd it in, I assume
that's not the proper way.

Two:

Is this ASUS P4B533 supported by the i2c/lmsensors found in Sid?

I go through the sensors-detect, and it doesn't find anything, leaving me
high and dry.

I looked for various howto's, but they all assume you're running prebuilt
kernels, unfortunately.

Mike


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: lm-sensors

[mess-mate]

Thakns for the reply, so what I did:

On Mon, 27 Jan 2003 13:42:47 -0500
David Z Maze <[EMAIL PROTECTED]> wrote:

| mess-mate <[EMAIL PROTECTED]> writes:
| > Sorry to post this message twice..
| > I'm unable to get lm-sensors working.
| > MB asus P4T533-R with P4.
| > Installed lm-sensors-source, compiled, patched the kernel and reinstalled 
| > the kernel (2.4.20) inclusif i2c.
| 
| Maybe you could explain in a little more detail what you did?  The
| lm-sensors-source package is intended to be built as a set of add-on
| modules; you should be able to unpack /usr/src/lm-sensors.tar.gz and
| run 'make-kpkg modules-image' from the top of your kernel source tree
| to get the modules, without patching your kernel.
The  source packages unpacked in a /home/user.
Then in this dir :
mkpatch/mkpatch.pl . /usr/src/linux > i2c-patch (for the new i2c package)
cd /usr/src/linu
su
Password : 
patch -p1 -E < /home/user/i2c-2.6.3/i2c-patch
cd /home/user/lm_sensors-2.6.3
mkpatch/mkpatch.pl . /usr/src/linux > lm-patch
patch -p1 -E < /home/user/lm_sensors-2.6.3/lm-patch
cd /usr/src/linux
make xconfig and selected everything as a module sensors/i2c
make dep ; make bzImage ; make modules ; make modules_install (old way)
After that a 'sensors-detect' with nothing detected.
Then a i2c-detect and detected a i2c-0 device.
That's exactly what I did.
I have sensor devices, the bios display temp's and fan's.

| > Setted-up the kernel with all in modules.
| > Sensors-detect detect nothing.
| > I2c-detect detect an i2c-0 device.
| > Modprobed of cource all available mods.( *.dev/*.prog/*.isa/ etc...)
| > Googled and found this info: chip ASB100 , driver AS99127F ???
| 
| Note that it is possible you don't have sensor devices on your
| motherboard.  But the upstream Web site,
| http://secure.netroedge.com/~lm78/supported.html, suggests that that
| chipset should be supported using the w83781d driver, which is pretty
| generic.
| 
| -- 
| David Maze [EMAIL PROTECTED]  http://people.debian.org/~dmaze/
| "Theoretical politics is interesting.  Politicking should be illegal."
|   -- Abra Mitchell
| 
| 
| -- 
| To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
| with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
| 


-- 
Computers are like air conditioners, they are useless when you open
Windows.


msg26713/pgp0.pgp
Description: PGP signature

Re: lm-sensors

[David Z Maze]

mess-mate <[EMAIL PROTECTED]> writes:
> Sorry to post this message twice..
> I'm unable to get lm-sensors working.
> MB asus P4T533-R with P4.
> Installed lm-sensors-source, compiled, patched the kernel and reinstalled 
> the kernel (2.4.20) inclusif i2c.

Maybe you could explain in a little more detail what you did?  The
lm-sensors-source package is intended to be built as a set of add-on
modules; you should be able to unpack /usr/src/lm-sensors.tar.gz and
run 'make-kpkg modules-image' from the top of your kernel source tree
to get the modules, without patching your kernel.

> Setted-up the kernel with all in modules.
> Sensors-detect detect nothing.
> I2c-detect detect an i2c-0 device.
> Modprobed of cource all available mods.( *.dev/*.prog/*.isa/ etc...)
> Googled and found this info: chip ASB100 , driver AS99127F ???

Note that it is possible you don't have sensor devices on your
motherboard.  But the upstream Web site,
http://secure.netroedge.com/~lm78/supported.html, suggests that that
chipset should be supported using the w83781d driver, which is pretty
generic.

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


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

lm-sensors

[mess-mate]

Hi all,
Sorry to post this message twice..
I'm unable to get lm-sensors working.
MB asus P4T533-R with P4.
Installed lm-sensors-source, compiled, patched the kernel and reinstalled 
the kernel (2.4.20) inclusif i2c.
Setted-up the kernel with all in modules.
Sensors-detect detect nothing.
I2c-detect detect an i2c-0 device.
Modprobed of cource all available mods.( *.dev/*.prog/*.isa/ etc...)
Googled and found this info: chip ASB100 , driver AS99127F ???
 
Any help would be very appreciated.
mess-mate

-- 
Computers are like air conditioners, they are useless when you open
Windows.


msg26577/pgp0.pgp
Description: PGP signature

Re: lm-sensors

[Elimar Riesebieter]

On Mon, 16 Dec 2002 the mental interface of 
Kjetil Kjernsmo told:

> On Monday 16 December 2002 19:58, Elimar Riesebieter wrote:

[...]

> >
> > make-kpkg modules_image. The Kernel was built also with make-kpkg.
> 
> Uh-oh, you're saying that if I've got any modules, then I have to run 
> make-kpkg modules_image
> ...?
> 
> Uhm, all I know about kernel-compilation on Debian, I've got from the 
> installation guide, where make-kpkg modules_image is only used if you 

Please open a new thread like "How to compile modules from source"

[...]

On Mon, 16 Dec 2002 the mental interface of 
Travis Crump told:

> Kjetil Kjernsmo wrote:

[...]

> >need PCMCIA, I don't so I skipped that section... I guess there may be 

which is only an example ;-)

[...]

> If you've got any modules in /usr/src/modules than you need to do 
> make-kpkg modules_image.  

and a dpkg -i /usr/src/modules.version+kernel.dpkg

Ciao

Elimar


-- 
  Do you smell something burning or ist it me?



msg19457/pgp0.pgp
Description: PGP signature

Re: lm-sensors

[Travis Crump]

Kjetil Kjernsmo wrote:

On Monday 16 December 2002 19:58, Elimar Riesebieter wrote:


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.


make-kpkg modules_image. The Kernel was built also with make-kpkg.



Uh-oh, you're saying that if I've got any modules, then I have to run 
make-kpkg modules_image
...?

Uhm, all I know about kernel-compilation on Debian, I've got from the 
installation guide, where make-kpkg modules_image is only used if you 
need PCMCIA, I don't so I skipped that section... I guess there may be 
a reason why I can't get power-off do work correctly, if this is the 
case... :-) 

Anywhere this is described in more detail?

Yours Confusedly,

Kjetil


If you've got any modules in /usr/src/modules than you need to do 
make-kpkg modules_image.  If you only have the modules including in the 
kernel tree than you don't.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]