CPU-Temperatur

[BLUESCREEN3D]

Gibt es ein einfaches (einfacher zu installieren als lm_sensors) Consolen-Programm, dass die CPU-Temperatur anzeigt?

[Gosch]

eigentlich net!! basieren glaube alle auf den LM-Dingern

[DustPuppy]

habe es zufällig gestern installiert. Soll ich dir ne schritt für schritt anleitung geben ?

edit: spinnt allerdings bissal rum das bios meint 52 C°, lm sensor meint 43C° und der krellm plugin meint 34C° :ugly:

[Gosch]

da musste mal in Datei schaun, wo die Umrechnungsfaktoren drinn stehen! Da musste
die Faktoren eben a bissl anpassen > so hab ich es auch gemacht :-)

[DustPuppy]

das problem ist halt ...
ich weiss nicht was passt ! Asus ist dafür bekannt sicherheits halber so +10C° dazu zu addieren, :ugly: . Aber ich weiss nicht ganz genau ob das schon in bios gemacht wird oder das nur die windows software von asus macht.

achja bin ich eigendlich der einzige der in init script was dabei ist, einbischien da und bischien dort weglöschen und auskommentieren musste das es läuft ?

[BLUESCREEN3D]

Wenn was dazuaddiert wird, dann wird das IMHO schon vom Board aus gemacht - also müsste der BIOS-Wert schon die +10°C haben.
Ich habe auch ein Asus-Board (A7V8X+) und im BIOS hat mein Prozzi nach Vollauslastung ca. 40°C - da sind glaube ich keine 10°C dazugerechnet

Schritt-für-Schritt-Anleitung währe nett - bin von dem Teil etwas überfordert :)

[DustPuppy]

oki

downloade dir das
http://www.lm-sensors.nu/archive/lm_sensors-2.7.0.tar.gz
"wget http://www.lm-sensors.nu/archive/lm_sensors-2.7.0.tar.gz"
und das
http://secure.netroedge.com/~lm78/archive/i2c-2.7.0.tar.gz
"wget http://secure.netroedge.com/~lm78/archive/i2c-2.7.0.tar.gz"

dannach decompremieren.

tar xfvz lm_sensors-2.7.0.tar.gz
tar xfvz i2c-2.7.0.tar.gz

dannach ab ins vergnügen :ugly:

cd i2c-2.7.0
make
make install

cd ../lm_sensors-2.7.0
make
make install

dannach vollgendes ausführen (noch immer in lm_sensors-2.7.0 verzeichnis ;) )

prog/mkdev/mkdev.sh

dannach das hier ausführen und gründlich durchlesen was er dir hinschreibt !

prog/detect/sensors-detect

wirklich gut aufpassen, weil er schreibt dir dann hin welche module du in ein rc.script schreiben musst das sie beim start automatisch geladen werden und einen eintrag in die /etc/modules.conf , auserdem erstellt er dir auch /etc/sysconfig/lm_sensors


wenn du mit den eintrag in die /etc/modules.conf fertig bist ("alias char-major-89 i2c-dev")

noch das runlevel script kopieren.
cp prog/init/lm_sensors.init /etc/init.d/lm_sensors

dannach in /etc/init.d/lm_sensors vollgendes anpassen.
Vor zeile 45 ein #
in zeil 64,67,87 und 90 aus dem _ ein leerzeichen machen
wenn du keine datei hast bei redhat in der die module eingetragen werden die automatisch geladen werden sollen. Kannst du nach start () {
auch noch eintragen
modprobe dasmodulwasdubrauchst
modprobe ... .

Jetzt solltest du das script einen runlevel hinzufügen (weiss aber nicht wie das bei redhat geht)
dann noch ein
"/etc/init.d/lm_sensors start"
dann solltest du mit
"sensors"
dir alles anzeigen lassen können.

[Gosch]

ich hab nen Asus A7V266-E > zeigt bei meinem Duron 800@1000 MHz (1.67 V) 47 Grad an!!
10 weniger wären 37 :D -> das wär a bissl wenig oder???

Was hast du für ne CPU/Temp. ???

[DustPuppy]

laut ml_sensor 44.9 C° muss mal schnell in bios nachschaun.
laut bios 57.5 C°

[BLUESCREEN3D]

ich kriege schon beim ersten "make" endlos viele Fehler... :|

[root@server i2c-2.7.0]# make
grep: /lib/modules/2.4.18-14/build/Makefile: Datei oder Verzeichnis nicht gefunden
grep: /lib/modules/2.4.18-14/build/include/linux/autoconf.h: Datei oder Verzeichnis nicht gefunden
grep: /lib/modules/2.4.18-14/build/.config: Datei oder Verzeichnis nicht gefunden
grep: /lib/modules/2.4.18-14/build/.config: Datei oder Verzeichnis nicht gefunden
grep: /lib/modules/2.4.18-14/build/.config: Datei oder Verzeichnis nicht gefunden
grep: /lib/modules/2.4.18-14/build/.config: Datei oder Verzeichnis nicht gefunden
grep: /lib/modules/2.4.18-14/build/.config: Datei oder Verzeichnis nicht gefunden
grep: /lib/modules/2.4.18-14/build/.config: Datei oder Verzeichnis nicht gefunden
grep: /lib/modules/2.4.18-14/build/.config: Datei oder Verzeichnis nicht gefunden
grep: /lib/modules/2.4.18-14/build/.config: Datei oder Verzeichnis nicht gefunden
grep: /lib/modules/2.4.18-14/build/.config: Datei oder Verzeichnis nicht gefunden
grep: /lib/modules/2.4.18-14/build/.config: Datei oder Verzeichnis nicht gefunden
grep: /lib/modules/2.4.18-14/build/.config: Datei oder Verzeichnis nicht gefunden
gcc -I/lib/modules/2.4.18-14/build/include -O2 -DLM_SENSORS -D__KERNEL__ -DMODULE -fomit-frame-pointer -DEXPORT_SYMTAB -c kernel/i2c-core.c -o kernel/i2c-core.o
In file included from /usr/include/linux/module.h:20,
from kernel/i2c-core.c:26:
/usr/include/linux/modversions.h:1:2: #error Modules should never use kernel-headers system headers,
/usr/include/linux/modversions.h:2:2: #error but rather headers from an appropriate kernel-source package.
/usr/include/linux/modversions.h:3:2: #error Change -I/usr/src/linux/include (or similar) to
/usr/include/linux/modversions.h:4:2: #error -I/lib/modules/$(uname -r)/build/include
/usr/include/linux/modversions.h:5:2: #error to build against the currently-running kernel.
In file included from kernel/i2c-core.c:30:
/usr/include/linux/proc_fs.h:47: parse error before "off_t"
/usr/include/linux/proc_fs.h:51: parse error before "off_t"
/usr/include/linux/proc_fs.h:57: parse error before "mode_t"
/usr/include/linux/proc_fs.h:59: parse error before "uid"
/usr/include/linux/proc_fs.h:60: parse error before "gid"
/usr/include/linux/proc_fs.h:70: parse error before "count"
/usr/include/linux/proc_fs.h:72: parse error before "rdev"
/usr/include/linux/proc_fs.h:176: parse error before "mode_t"
/usr/include/linux/proc_fs.h: In function `proc_net_create':
/usr/include/linux/proc_fs.h:177: `NULL' undeclared (first use in this function)
/usr/include/linux/proc_fs.h:177: (Each undeclared identifier is reported only once
/usr/include/linux/proc_fs.h:177: for each function it appears in.)
/usr/include/linux/proc_fs.h: At top level:
/usr/include/linux/proc_fs.h:181: parse error before "mode_t"
/usr/include/linux/proc_fs.h: In function `create_proc_entry':
/usr/include/linux/proc_fs.h:181: `NULL' undeclared (first use in this function)
/usr/include/linux/proc_fs.h: In function `proc_symlink':
/usr/include/linux/proc_fs.h:185: `NULL' undeclared (first use in this function)
/usr/include/linux/proc_fs.h: At top level:
/usr/include/linux/proc_fs.h:186: parse error before "mode_t"
/usr/include/linux/proc_fs.h: In function `proc_mknod':
/usr/include/linux/proc_fs.h:187: `NULL' undeclared (first use in this function)
/usr/include/linux/proc_fs.h: In function `proc_mkdir':
/usr/include/linux/proc_fs.h:189: `NULL' undeclared (first use in this function)
/usr/include/linux/proc_fs.h: At top level:
/usr/include/linux/proc_fs.h:192: parse error before "mode_t"
/usr/include/linux/proc_fs.h:193: parse error before "off_t"
/usr/include/linux/proc_fs.h:193: `create_proc_read_entry' declared as function returning a function
/usr/include/linux/proc_fs.h:196: parse error before "mode_t"
/usr/include/linux/proc_fs.h: In function `create_proc_info_entry':
/usr/include/linux/proc_fs.h:197: `NULL' undeclared (first use in this function)
/usr/include/linux/proc_fs.h: At top level:
/usr/include/linux/proc_fs.h:203: `NULL' used prior to declaration
In file included from kernel/i2c-core.c:32:
kernel/i2c.h:265: field `lock' has incomplete type
kernel/i2c-core.c:43:25: asm/uaccess.h: Datei oder Verzeichnis nicht gefunden
kernel/i2c-core.c: In function `i2c_add_adapter':
kernel/i2c-core.c:138: `KERN_WARNING' undeclared (first use in this function)
kernel/i2c-core.c:138: parse error before string constant
kernel/i2c-core.c:192: `KERN_DEBUG' undeclared (first use in this function)
kernel/i2c-core.c:192: parse error before string constant
kernel/i2c-core.c:192: parse error before ')' token
kernel/i2c-core.c: In function `i2c_del_adapter':
kernel/i2c-core.c:217: `KERN_WARNING' undeclared (first use in this function)
kernel/i2c-core.c:217: parse error before string constant
kernel/i2c-core.c:232: parse error before string constant
kernel/i2c-core.c:250: `KERN_ERR' undeclared (first use in this function)
kernel/i2c-core.c:250: parse error before string constant
kernel/i2c-core.c:269: `KERN_DEBUG' undeclared (first use in this function)
kernel/i2c-core.c:269: parse error before string constant
kernel/i2c-core.c:269: parse error before ')' token
kernel/i2c-core.c: In function `i2c_add_driver':
kernel/i2c-core.c:296: `KERN_WARNING' undeclared (first use in this function)
kernel/i2c-core.c:296: parse error before string constant
kernel/i2c-core.c:308: `KERN_DEBUG' undeclared (first use in this function)
kernel/i2c-core.c:308: parse error before string constant
kernel/i2c-core.c:308: parse error before ')' token
kernel/i2c-core.c: In function `i2c_del_driver':
kernel/i2c-core.c:333: `KERN_WARNING' undeclared (first use in this function)
kernel/i2c-core.c:333: parse error before string constant
kernel/i2c-core.c:343: `KERN_DEBUG' undeclared (first use in this function)
kernel/i2c-core.c:343: parse error before string constant
kernel/i2c-core.c:354: parse error before string constant
kernel/i2c-core.c:354: parse error before ')' token
kernel/i2c-core.c:362: parse error before string constant
kernel/i2c-core.c:377: parse error before string constant
kernel/i2c-core.c:377: parse error before ')' token
kernel/i2c-core.c:381: `KERN_ERR' undeclared (first use in this function)
kernel/i2c-core.c:381: parse error before string constant
kernel/i2c-core.c:401: parse error before string constant
kernel/i2c-core.c:401: parse error before ')' token
kernel/i2c-core.c: In function `i2c_attach_client':
kernel/i2c-core.c:427: `KERN_WARNING' undeclared (first use in this function)
kernel/i2c-core.c:427: parse error before string constant
kernel/i2c-core.c:437: `KERN_DEBUG' undeclared (first use in this function)
kernel/i2c-core.c:437: parse error before string constant
kernel/i2c-core.c:439: parse error before ')' token
kernel/i2c-core.c:441: parse error before string constant
kernel/i2c-core.c:441: parse error before ')' token
kernel/i2c-core.c: In function `i2c_detach_client':
kernel/i2c-core.c:459: `KERN_WARNING' undeclared (first use in this function)
kernel/i2c-core.c:459: parse error before string constant
kernel/i2c-core.c:471: `KERN_ERR' undeclared (first use in this function)
kernel/i2c-core.c:471: parse error before string constant
kernel/i2c-core.c:479: `KERN_DEBUG' undeclared (first use in this function)
kernel/i2c-core.c:479: parse error before string constant
kernel/i2c-core.c:479: parse error before ')' token
kernel/i2c-core.c: In function `i2c_get_client':
kernel/i2c-core.c:527: `KERN_WARNING' undeclared (first use in this function)
kernel/i2c-core.c:527: parse error before string constant
kernel/i2c-core.c:538: parse error before string constant
kernel/i2c-core.c: In function `i2c_release_client':
kernel/i2c-core.c:595: `KERN_WARNING' undeclared (first use in this function)
kernel/i2c-core.c:595: parse error before string constant
kernel/i2c-core.c: In function `i2c_transfer':
kernel/i2c-core.c:767: `KERN_DEBUG' undeclared (first use in this function)
kernel/i2c-core.c:767: parse error before string constant
kernel/i2c-core.c:767: parse error before ')' token
kernel/i2c-core.c:775: `KERN_ERR' undeclared (first use in this function)
kernel/i2c-core.c:775: parse error before string constant
kernel/i2c-core.c: In function `i2c_master_send':
kernel/i2c-core.c:794: `KERN_DEBUG' undeclared (first use in this function)
kernel/i2c-core.c:794: parse error before string constant
kernel/i2c-core.c:794: parse error before ')' token
kernel/i2c-core.c:805: `KERN_ERR' undeclared (first use in this function)
kernel/i2c-core.c:805: parse error before string constant
kernel/i2c-core.c: In function `i2c_master_recv':
kernel/i2c-core.c:824: `KERN_DEBUG' undeclared (first use in this function)
kernel/i2c-core.c:824: parse error before string constant
kernel/i2c-core.c:824: parse error before ')' token
kernel/i2c-core.c:831: parse error before string constant
kernel/i2c-core.c:831: parse error before ')' token
kernel/i2c-core.c:838: parse error before string constant
kernel/i2c-core.c: In function `i2c_control':
kernel/i2c-core.c:851: `KERN_DEBUG' undeclared (first use in this function)
kernel/i2c-core.c:851: parse error before string constant
kernel/i2c-core.c:851: parse error before ')' token
kernel/i2c-core.c: In function `i2c_probe':
kernel/i2c-core.c:897: `KERN_DEBUG' undeclared (first use in this function)
kernel/i2c-core.c:897: parse error before string constant
kernel/i2c-core.c:897: parse error before ')' token
kernel/i2c-core.c:915: parse error before string constant
kernel/i2c-core.c:915: parse error before ')' token
kernel/i2c-core.c:927: parse error before string constant
kernel/i2c-core.c:927: parse error before ')' token
kernel/i2c-core.c:942: parse error before string constant
kernel/i2c-core.c:942: parse error before ')' token
kernel/i2c-core.c:953: parse error before string constant
kernel/i2c-core.c:953: parse error before ')' token
kernel/i2c-core.c:965: parse error before string constant
kernel/i2c-core.c:965: parse error before ')' token
kernel/i2c-core.c:977: parse error before string constant
kernel/i2c-core.c:977: parse error before ')' token
kernel/i2c-core.c: In function `i2c_smbus_check_pec':
kernel/i2c-core.c:1117: `KERN_DEBUG' undeclared (first use in this function)
kernel/i2c-core.c:1117: parse error before string constant
kernel/i2c-core.c:1117: parse error before ')' token
kernel/i2c-core.c: In function `i2c_smbus_xfer_emulated':
kernel/i2c-core.c:1345: `KERN_ERR' undeclared (first use in this function)
kernel/i2c-core.c:1345: parse error before string constant
kernel/i2c-core.c:1351: parse error before string constant
kernel/i2c-core.c:1364: parse error before string constant
kernel/i2c-core.c:1383: parse error before string constant
kernel/i2c-core.c: In function `i2c_init':
kernel/i2c-core.c:1481: `KERN_INFO' undeclared (first use in this function)
kernel/i2c-core.c:1481: parse error before string constant
kernel/i2c-core.c: At top level:
kernel/i2c-core.c:1625: parse error before "config_must_be_included_before_module"
kernel/i2c-core.c:1625: warning: data definition has no type or storage class
kernel/i2c-core.c:1626: parse error before "config_must_be_included_before_module"
kernel/i2c-core.c:1626: warning: data definition has no type or storage class
kernel/i2c-core.c:1627: parse error before "config_must_be_included_before_module"
kernel/i2c-core.c:1627: warning: data definition has no type or storage class
kernel/i2c-core.c:1628: parse error before "config_must_be_included_before_module"
kernel/i2c-core.c:1628: warning: data definition has no type or storage class
kernel/i2c-core.c:1629: parse error before "config_must_be_included_before_module"
kernel/i2c-core.c:1629: warning: data definition has no type or storage class
kernel/i2c-core.c:1630: parse error before "config_must_be_included_before_module"
kernel/i2c-core.c:1630: warning: data definition has no type or storage class
kernel/i2c-core.c:1631: parse error before "config_must_be_included_before_module"
kernel/i2c-core.c:1631: warning: data definition has no type or storage class
kernel/i2c-core.c:1632: parse error before "config_must_be_included_before_module"
kernel/i2c-core.c:1632: warning: data definition has no type or storage class
kernel/i2c-core.c:1633: parse error before "config_must_be_included_before_module"
kernel/i2c-core.c:1633: warning: data definition has no type or storage class
kernel/i2c-core.c:1634: parse error before "config_must_be_included_before_module"
kernel/i2c-core.c:1634: warning: data definition has no type or storage class
kernel/i2c-core.c:1635: parse error before "config_must_be_included_before_module"
kernel/i2c-core.c:1635: warning: data definition has no type or storage class
kernel/i2c-core.c:1636: parse error before "config_must_be_included_before_module"
kernel/i2c-core.c:1636: warning: data definition has no type or storage class
kernel/i2c-core.c:1639: parse error before "config_must_be_included_before_module"
kernel/i2c-core.c:1639: warning: data definition has no type or storage class
kernel/i2c-core.c:1640: parse error before "config_must_be_included_before_module"
kernel/i2c-core.c:1640: warning: data definition has no type or storage class
kernel/i2c-core.c:1641: parse error before "config_must_be_included_before_module"
kernel/i2c-core.c:1641: warning: data definition has no type or storage class
kernel/i2c-core.c:1642: parse error before "config_must_be_included_before_module"
kernel/i2c-core.c:1642: warning: data definition has no type or storage class
kernel/i2c-core.c:1643: parse error before "config_must_be_included_before_module"
kernel/i2c-core.c:1643: warning: data definition has no type or storage class
kernel/i2c-core.c:1644: parse error before "config_must_be_included_before_module"
kernel/i2c-core.c:1644: warning: data definition has no type or storage class
kernel/i2c-core.c:1646: parse error before "config_must_be_included_before_module"
kernel/i2c-core.c:1646: warning: data definition has no type or storage class
kernel/i2c-core.c:1647: parse error before "config_must_be_included_before_module"
kernel/i2c-core.c:1647: warning: data definition has no type or storage class
kernel/i2c-core.c:1648: parse error before "config_must_be_included_before_module"
kernel/i2c-core.c:1648: warning: data definition has no type or storage class
kernel/i2c-core.c:1649: parse error before "config_must_be_included_before_module"
kernel/i2c-core.c:1649: warning: data definition has no type or storage class
kernel/i2c-core.c:1650: parse error before "config_must_be_included_before_module"
kernel/i2c-core.c:1650: warning: data definition has no type or storage class
kernel/i2c-core.c:1651: parse error before "config_must_be_included_before_module"
kernel/i2c-core.c:1651: warning: data definition has no type or storage class
kernel/i2c-core.c:1652: parse error before "config_must_be_included_before_module"
kernel/i2c-core.c:1652: warning: data definition has no type or storage class
kernel/i2c-core.c:1653: parse error before "config_must_be_included_before_module"
kernel/i2c-core.c:1653: warning: data definition has no type or storage class
kernel/i2c-core.c:1654: parse error before "config_must_be_included_before_module"
kernel/i2c-core.c:1654: warning: data definition has no type or storage class
kernel/i2c-core.c:1655: parse error before "config_must_be_included_before_module"
kernel/i2c-core.c:1655: warning: data definition has no type or storage class
kernel/i2c-core.c:1656: parse error before "config_must_be_included_before_module"
kernel/i2c-core.c:1656: warning: data definition has no type or storage class
kernel/i2c-core.c:1657: parse error before "config_must_be_included_before_module"
kernel/i2c-core.c:1657: warning: data definition has no type or storage class
kernel/i2c-core.c:1658: parse error before "config_must_be_included_before_module"
kernel/i2c-core.c:1658: warning: data definition has no type or storage class
kernel/i2c-core.c:1660: parse error before "config_must_be_included_before_module"
kernel/i2c-core.c:1660: warning: data definition has no type or storage class
kernel/i2c-core.c:1661: parse error before "config_must_be_included_before_module"
kernel/i2c-core.c:1661: warning: data definition has no type or storage class
kernel/i2c-core.c:63: storage size of `adap_lock' isn't known
kernel/i2c-core.c:64: storage size of `driver_lock' isn't known
make: *** [kernel/i2c-core.o] Fehler 1

[isaac]

na hallo
ich hab mich auch versucht mit dem lm sensor und bin auch bis zum ende gekommen.
hatte alldings fehler beim bauen. sone hier

[root@localhost i2c-2.7.0]# make
Makefile:188: kernel/i2c-core.d: Datei oder Verzeichnis nicht gefunden
Makefile:188: kernel/i2c-dev.d: Datei oder Verzeichnis nicht gefunden
Makefile:188: kernel/i2c-algo-bit.d: Datei oder Verzeichnis nicht gefunden
Makefile:188: kernel/i2c-philips-par.d: Datei oder Verzeichnis nicht gefunden
Makefile:188: kernel/i2c-elv.d: Datei oder Verzeichnis nicht gefunden
Makefile:188: kernel/i2c-velleman.d: Datei oder Verzeichnis nicht gefunden
Makefile:188: kernel/i2c-algo-pcf.d: Datei oder Verzeichnis nicht gefunden
Makefile:188: kernel/i2c-elektor.d: Datei oder Verzeichnis nicht gefunden
Makefile:188: kernel/i2c-proc.d: Datei oder Verzeichnis nicht gefunden
Makefile:188: kernel/i2c-pport.d: Datei oder Verzeichnis nicht gefunden
Makefile:188: kernel/i2c-pcf-epp.d: Datei oder Verzeichnis nicht gefunden
gcc -M -MG -I/lib/modules/2.4.18-3/build/include -O2

oder beim lm_sensor

[root@localhost lm_sensors-2.7.0]# make
Makefile:234: kernel/busses/i2c-ali1535.d: Datei oder Verzeichnis nicht gefunden
Makefile:234: kernel/busses/i2c-ali15x3.d: Datei oder Verzeichnis nicht gefunden
Makefile:234: kernel/busses/i2c-amd756.d: Datei oder Verzeichnis nicht gefunden
Makefile:234: kernel/busses/i2c-amd8111.d: Datei oder Verzeichnis nicht gefunden
Makefile:234: kernel/busses/i2c-hydra.d: Datei oder Verzeichnis nicht gefunden
Makefile:234: kernel/busses/i2c-i801.d: Datei oder Verzeichnis nicht gefunden
Makefile:234: kernel/busses/i2c-i810.d: Datei oder Verzeichnis nicht gefunden
Makefile:234: kernel/busses/i2c-isa.d: Datei oder Verzeichnis nicht gefunden
Makefile:234: kernel/busses/i2c-sis5595.d: Datei oder Verzeichnis nich

hab mal nicht alle reingenommen. es ging dann aber erstaunlicherweise doch zuende.
und dann die modul aktion

[root@localhost lm_sensors-2.7.0]# prog/mkdev/mkdev.sh
/dev/i2c-0
mknod: »/dev/i2c-0«: Die Datei existiert bereits
/dev/i2c-1
mknod: »/dev/i2c-1«: Die Datei existiert bereits
/dev/i2c-2
/dev/i2c-3
/dev/i2c-4
/dev/i2c-5
/dev/i2c-6
/dev/i2c-7
/dev/i2c-8
/dev/i2c-9
/dev/i2c-10
/dev/i2c-11
/dev/i2c-12
/dev/i2c-13
/dev/i2c-14
/dev/i2c-15
/dev/i2c-16
/dev/i2c-17
/dev/i2c-18
/dev/i2c-19
/dev/i2c-20
/dev/i2c-21
/dev/i2c-22
/dev/i2c-23
/dev/i2c-24
/dev/i2c-25
/dev/i2c-26
/dev/i2c-27
/dev/i2c-28
/dev/i2c-29
/dev/i2c-30
/dev/i2c-31
[root@localhost lm_sensors-2.7.0]#
[root@localhost lm_sensors-2.7.0]# prog/detect/sensors-detect
This program will help you to determine which I2C/SMBus modules you need to
load to use lm_sensors most effectively.
You need to have done a `make install', issued a `depmod -a' and made sure
`/etc/conf.modules' (or `/etc/modules.conf') contains the appropriate
module path before you can use some functions of this utility. Read
doc/modules for more information.
Also, you need to be `root', or at least have access to the /dev/i2c[-/]* files
for some things. You can use prog/mkdev/mkdev.sh to create these /dev files
if you do not have them already.
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.

BIOS vendor (ACPI): AWARD
Could not find dmidecode, which should have been installed with lm_sensors.
Runing dmidecode would help us determining your system vendor, which allows
safer operations. Please provide one of the following:
/usr/local/sbin/dmidecode
/usr/sbin/dmidecode
You can still go on, but you are encouraged to fix the problem first.

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-sis630' for device 00:00.0: Silicon Integrated Systems SIS730
Use driver `i2c-sis5595' for device 00:01.0: Silicon Integrated Systems SIS5595
Use driver `i2c-riva' for device 01:00.0: GeForce2 MX
Probe succesfully concluded.

We will now try to load each adapter module in turn.
Load `i2c-sis630' (say NO if built into your kernel)? (YES/no): yes
modprobe: Can't locate module i2c-sis630
Loading failed... skipping.
Load `i2c-sis5595' (say NO if built into your kernel)? (YES/no): yes
/lib/modules/2.4.18-3/kernel/drivers/i2c/i2c-sis5595.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
/lib/modules/2.4.18-3/kernel/drivers/i2c/i2c-sis5595.o: insmod /lib/modules/2.4.18-3/kernel/drivers/i2c/i2c-sis5595.o failed
/lib/modules/2.4.18-3/kernel/drivers/i2c/i2c-sis5595.o: insmod i2c-sis5595 failed
Loading failed... skipping.
Load `i2c-riva' (say NO if built into your kernel)? (YES/no): yes
modprobe: Can't locate module i2c-riva
Loading failed... skipping.
** Note: i2c-riva module is available at
** http://drama.obuda.kando.hu/~fero/cgi-bin/rivatv.shtml
Do you now want to be prompted for non-detectable adapters? (yes/NO): yes
Load `i2c-elektor' (say NO if built into your kernel)? (YES/no): yes
/lib/modules/2.4.18-3/kernel/drivers/i2c/i2c-elektor.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
/lib/modules/2.4.18-3/kernel/drivers/i2c/i2c-elektor.o: insmod /lib/modules/2.4.18-3/kernel/drivers/i2c/i2c-elektor.o failed
/lib/modules/2.4.18-3/kernel/i2c-elektor.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
/lib/modules/2.4.18-3/kernel/i2c-elektor.o: insmod /lib/modules/2.4.18-3/kernel/i2c-elektor.o failed
/lib/modules/2.4.18-3/kernel/i2c-elektor.o: insmod i2c-elektor failed
Loading failed... skipping.
Load `i2c-elv' (say NO if built into your kernel)? (YES/no): yes
/lib/modules/2.4.18-3/kernel/drivers/i2c/i2c-elv.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
/lib/modules/2.4.18-3/kernel/drivers/i2c/i2c-elv.o: insmod /lib/modules/2.4.18-3/kernel/drivers/i2c/i2c-elv.o failed
/lib/modules/2.4.18-3/kernel/i2c-elv.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
/lib/modules/2.4.18-3/kernel/i2c-elv.o: insmod /lib/modules/2.4.18-3/kernel/i2c-elv.o failed
/lib/modules/2.4.18-3/kernel/i2c-elv.o: insmod i2c-elv failed
Loading failed... skipping.
Load `i2c-philips-par' (say NO if built into your kernel)? (YES/no): yes
Module loaded succesfully.
Load `i2c-velleman' (say NO if built into your kernel)? (YES/no): yes
/lib/modules/2.4.18-3/kernel/drivers/i2c/i2c-velleman.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
/lib/modules/2.4.18-3/kernel/drivers/i2c/i2c-velleman.o: insmod /lib/modules/2.4.18-3/kernel/drivers/i2c/i2c-velleman.o failed
/lib/modules/2.4.18-3/kernel/i2c-velleman.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
/lib/modules/2.4.18-3/kernel/i2c-velleman.o: insmod /lib/modules/2.4.18-3/kernel/i2c-velleman.o failed
/lib/modules/2.4.18-3/kernel/i2c-velleman.o: insmod i2c-velleman failed
Loading failed... skipping.
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): yes
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).

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. Do you want to scan the ISA bus? (YES/no): yes
Probing for `National Semiconductor LM78'
Trying address 0x0290... Failed!
Probing for `National Semiconductor LM78-J'
Trying address 0x0290... Failed!
Probing for `National Semiconductor LM79'
Trying address 0x0290... Failed!
Probing for `Winbond W83781D'
Trying address 0x0290... Failed!
Probing for `Winbond W83782D'
Trying address 0x0290... Failed!
Probing for `Winbond W83627HF'
Trying address 0x0290... Failed!
Probing for `Winbond W83697HF'
Trying address 0x0290... Failed!
Probing for `Silicon Integrated Systems SIS5595'
Trying general detect... Success!
(confidence 9, driver `sis5595')
Probing for `VIA Technologies VT82C686 Integrated Sensors'
Trying general detect... Failed!
Probing for `VIA Technologies VT8231 Integrated Sensors'
Trying general detect... Failed!
Probing for `ITE IT8705F / IT8712F / SiS 950'
Trying address 0x0290... Success!
(confidence 8, driver `it87')
Probing for `IPMI BMC KCS'
Trying address 0x0ca0... Failed!
Probing for `IPMI BMC SMIC'
Trying address 0x0ca8... Failed!

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

Driver `sis5595' (should be inserted):
Detects correctly:
* ISA bus, undetermined address (Busdriver `i2c-isa')
Chip `Silicon Integrated Systems SIS5595' (confidence: 9)

Driver `it87' (should be inserted):
Detects correctly:
* ISA bus address 0x0290 (Busdriver `i2c-isa')
Chip `ITE IT8705F / IT8712F / SiS 950' (confidence: 8)


I will now generate the commands needed to load the I2C modules.
Sometimes, a chip is available both through the ISA bus and an I2C bus.
ISA bus access is faster, but you need to load an additional driver module
for it. If you have the choice, do you want to use the ISA bus or the
I2C/SMBus (ISA/smbus)? isa

WARNING! If you have some things built into your kernel, the
below list will contain too many modules. Skip the appropriate ones!
To load everything that is needed, add this to some /etc/rc* file:

#----cut here----
# I2C adapter drivers
modprobe i2c-isa
# I2C chip drivers
modprobe sis5595
modprobe it87
#----cut here----

To make the sensors modules behave correctly, add these lines to either
/etc/modules.conf or /etc/conf.modules:

#----cut here----
# I2C module options
alias char-major-89 i2c-dev
#----cut here----

Do you want to generate /etc/sysconfig/lm_sensors? (YES/no): yes
Copy prog/init/lm_sensors.init to /etc/rc.d/init.d/lm_sensors
for initialization at boot time.
[root@localhost lm_sensors-2.7.0]# cp prog/init/lm_sensors.init /etc/rc.d/init.d/lm_sensors
[root@localhost lm_sensors-2.7.0]# /sbin/chkconfig lm_sensors --add
[root@localhost lm_sensors-2.7.0]# service lm_sensors start
Starting up sensors: starting module __i2c-isa__
starting module __sis5595__
starting module __it87__
[ OK ]
[root@localhost lm_sensors-2.7.0]# sensors
Can't access /proc file
/proc/sys/dev/sensors/chips or /proc/bus/i2c unreadable;
Make sure you have done 'modprobe i2c-proc'!
[root@localhost lm_sensors-2.7.0]# modprobe i2c-proc
[root@localhost lm_sensors-2.7.0]# sensors
No sensors found!

Nur warum sagt er dann das er das modul i2c-proc nicht finden kann???
Starte ich es von hand wie zum schluss dann No sensors found! ???

Weis jemand was da schief gerannt ist???

danke isaac


und startmodule in rehat zufügen geht mit /sbin/chkconfig xxxxx --add

[DustPuppy]

bei mir sind folgende module geladen.

i2c-viapro
w83781d

die beiden sind für meine sensoren von asus
die hier sind anscheinend die, die umbeding geladen werden müssen.

i2c-proc
i2c-core

die beiden werden schon während des init scripts gleaden. Allerdings nur wenn ihr meine feinabstimmung :ugly: vorgenommen habt. dann gibts noch i2c-dev davon hab ich aber keine ahnung wozu das gut ist.

bluescreen währe es möglich das du keine kernelsourcen installiert hast ? schau nach ob /usr/src/linux vorhanden ist.

ich sehe das er bei dir aus irgend einen grund nicht die module compiliert hat. Deswegen kann er sie auch nicht laden.

[BLUESCREEN3D]

Es gibt nur /usr/src/redhat und da sind so wie es aussieht keine kernelsourcen drin... wie installiere ich die am einfachsten? Habe die Red Hat 8.0 CDs - auf denen müsste das ja drauf sein, oder?

[BLUESCREEN3D]

Kernel-Sources waren auf einer der CDs

so sieht es jetzt aus:
[root@server i2c-2.7.0]# ls /usr/src
linux-2.4 linux-2.4.18-14 redhat

aber irgendwas stimmt da noch nicht, es fängt schon wieder so an:
[root@server i2c-2.7.0]# make
grep: /lib/modules/2.4.18-14/build/.config: Datei oder Verzeichnis nicht gefunden
grep: /lib/modules/2.4.18-14/build/.config: Datei oder Verzeichnis nicht gefunden
grep: /lib/modules/2.4.18-14/build/.config: Datei oder Verzeichnis nicht gefunden
grep: /lib/modules/2.4.18-14/build/.config: Datei oder Verzeichnis nicht gefunden
grep: /lib/modules/2.4.18-14/build/.config: Datei oder Verzeichnis nicht gefunden
grep: /lib/modules/2.4.18-14/build/.config: Datei oder Verzeichnis nicht gefunden
grep: /lib/modules/2.4.18-14/build/.config: Datei oder Verzeichnis nicht gefunden
grep: /lib/modules/2.4.18-14/build/.config: Datei oder Verzeichnis nicht gefunden
grep: /lib/modules/2.4.18-14/build/.config: Datei oder Verzeichnis nicht gefunden
grep: /lib/modules/2.4.18-14/build/.config: Datei oder Verzeichnis nicht gefunden
grep: /lib/modules/2.4.18-14/build/.config: Datei oder Verzeichnis nicht gefunden
(...)

Das Verzecihnis /lib/modules/2.4.18-14/build existiert, aber die Datei ".config" ist nicht drin :confused:

[Kung]

musste nicht erst über 'make menuconfig' ne .config erstellen und dann mit 'make dep' die abhänigkeiten berechnen lassen um den Kernel || Kernel-Module zu übersetzen.

[DustPuppy]

ja, kung hat recht vorher musst du noch einen link erstellen "ln -s /usr/src/linux-2.4.18-14 /usr/src/linux" du musst erst als root einmal make menuconfig ausführen. Schau nach ob auf der /boot partition irgend eine datei mit config herumschwird wenn ja, musst du die dann einfach nach /usr/src/linux/.config kopieren, dannach noch ein "make menuconfig" oder ein "make oldconfig". Falls keine config auf der boot patition vorhanden ist, schau nach ob /usr/src/linux/.config schon vorhanden ist. Dann reicht wieder ein "make oldconfig" . Falls du keine module magst lm_sensor ist auch als kernel patch erhältlich.

[knallzapzerap]

Meine Freundin hat nen Asus P2B-266 Board. Das Bios zeigt ziemlich genau 10° weniger an, als die mitgelieferte Win-Software. Linux hat sie zur Zeit leider nicht drauf, daher kann ich das ganze mit lmsensors nicht prüfen.

[BLUESCREEN3D]

[root@server root]# ls /boot
boot.0300 config-2.4.18-14 kernel.h message module-info-2.4.18-14 System.map-2.4.18-14 vmlinuz-2.4.18-14
boot.b grub lost+found message.ja os2_d.b vmlinux-2.4.18-14
chain.b initrd-2.4.18-14.img map module-info System.map vmlinuz
[root@server root]# cp /boot/config-2.4.18-14 /usr/src/linux/.config

und dann im lm_sensors-Verzeichnis:
make menuconfig
Makefile:234: kernel/chips/ltc1710.d: Datei oder Verzeichnis nicht gefunden
Makefile:234: kernel/chips/matorb.d: Datei oder Verzeichnis nicht gefunden
Makefile:234: kernel/chips/maxilife.d: Datei oder Verzeichnis nicht gefunden
Makefile:234: kernel/chips/mtp008.d: Datei oder Verzeichnis nicht gefunden
Makefile:234: kernel/chips/pcf8574.d: Datei oder Verzeichnis nicht gefunden
Makefile:234: kernel/chips/pcf8591.d: Datei oder Verzeichnis nicht gefunden
Makefile:234: kernel/chips/sis5595.d: Datei oder Verzeichnis nicht gefunden
Makefile:234: kernel/chips/smsc47m1.d: Datei oder Verzeichnis nicht gefunden
Makefile:234: kernel/chips/thmc50.d: Datei oder Verzeichnis nicht gefunden
Makefile:234: kernel/chips/w83781d.d: Datei oder Verzeichnis nicht gefunden
Makefile:234: kernel/chips/via686a.d: Datei oder Verzeichnis nicht gefunden
Makefile:234: kernel/chips/vt1211.d: Datei oder Verzeichnis nicht gefunden
Makefile:234: lib/data.ld: Datei oder Verzeichnis nicht gefunden
Makefile:234: lib/general.ld: Datei oder Verzeichnis nicht gefunden
Makefile:234: lib/error.ld: Datei oder Verzeichnis nicht gefunden
Makefile:234: lib/chips.ld: Datei oder Verzeichnis nicht gefunden
Makefile:234: lib/proc.ld: Datei oder Verzeichnis nicht gefunden
Makefile:234: lib/access.ld: Datei oder Verzeichnis nicht gefunden
Makefile:234: lib/init.ld: Datei oder Verzeichnis nicht gefunden
Makefile:234: lib/data.ad: Datei oder Verzeichnis nicht gefunden
Makefile:234: lib/general.ad: Datei oder Verzeichnis nicht gefunden
Makefile:234: lib/error.ad: Datei oder Verzeichnis nicht gefunden
Makefile:234: lib/chips.ad: Datei oder Verzeichnis nicht gefunden
Makefile:234: lib/proc.ad: Datei oder Verzeichnis nicht gefunden
Makefile:234: lib/access.ad: Datei oder Verzeichnis nicht gefunden
Makefile:234: lib/init.ad: Datei oder Verzeichnis nicht gefunden
Makefile:234: prog/sensors/main.rd: Datei oder Verzeichnis nicht gefunden
Makefile:234: prog/sensors/chips.rd: Datei oder Verzeichnis nicht gefunden
Makefile:234: prog/dump/isadump.rd: Datei oder Verzeichnis nicht gefunden
Makefile:234: prog/dump/i2cdump.rd: Datei oder Verzeichnis nicht gefunden
Makefile:234: prog/dump/i2cset.rd: Datei oder Verzeichnis nicht gefunden
Makefile:234: prog/detect/i2cdetect.rd: Datei oder Verzeichnis nicht gefunden
gcc -M -MG -I. -Ikernel/include -I/usr/local/include -I/lib/modules/2.4.18-14/build/include -O2 prog/detect/i2cdetect.c | \
sed -e 's@^\(.*\)\.o:@prog/detect/i2cdetect.rd prog/detect/i2cdetect.ro: Makefile '`dirname prog/detect/i2cdetect.rd`/Module.mk' @' > prog/detect/i2cdetect.rd
cpp0: warning: changing search order for system directory "/usr/local/include"
cpp0: warning: as it has already been specified as a non-system directory
gcc -M -MG -I. -Ikernel/include -I/usr/local/include -I/lib/modules/2.4.18-14/build/include -O2 prog/dump/i2cset.c | \
sed -e 's@^\(.*\)\.o:@prog/dump/i2cset.rd prog/dump/i2cset.ro: Makefile '`dirname prog/dump/i2cset.rd`/Module.mk' @' > prog/dump/i2cset.rd
cpp0: warning: changing search order for system directory "/usr/local/include"
cpp0: warning: as it has already been specified as a non-system directory
gcc -M -MG -I. -Ikernel/include -I/usr/local/include -I/lib/modules/2.4.18-14/build/include -O2 prog/dump/i2cdump.c | \
sed -e 's@^\(.*\)\.o:@prog/dump/i2cdump.rd prog/dump/i2cdump.ro: Makefile '`dirname prog/dump/i2cdump.rd`/Module.mk' @' > prog/dump/i2cdump.rd
cpp0: warning: changing search order for system directory "/usr/local/include"
cpp0: warning: as it has already been specified as a non-system directory
gcc -M -MG -I. -Ikernel/include -I/usr/local/include -I/lib/modules/2.4.18-14/build/include -O2 prog/dump/isadump.c | \
sed -e 's@^\(.*\)\.o:@prog/dump/isadump.rd prog/dump/isadump.ro: Makefile '`dirname prog/dump/isadump.rd`/Module.mk' @' > prog/dump/isadump.rd
cpp0: warning: changing search order for system directory "/usr/local/include"
cpp0: warning: as it has already been specified as a non-system directory
gcc -M -MG -I. -Ikernel/include -I/usr/local/include -I/lib/modules/2.4.18-14/build/include -O2 prog/sensors/chips.c | \
sed -e 's@^\(.*\)\.o:@prog/sensors/chips.rd prog/sensors/chips.ro: Makefile '`dirname prog/sensors/chips.rd`/Module.mk' @' > prog/sensors/chips.rd
cpp0: warning: changing search order for system directory "/usr/local/include"
cpp0: warning: as it has already been specified as a non-system directory
gcc -M -MG -I. -Ikernel/include -I/usr/local/include -I/lib/modules/2.4.18-14/build/include -O2 prog/sensors/main.c | \
sed -e 's@^\(.*\)\.o:@prog/sensors/main.rd prog/sensors/main.ro: Makefile '`dirname prog/sensors/main.rd`/Module.mk' @' > prog/sensors/main.rd
cpp0: warning: changing search order for system directory "/usr/local/include"
cpp0: warning: as it has already been specified as a non-system directory
gcc -M -MG -I. -Ikernel/include -I/usr/local/include -I/lib/modules/2.4.18-14/build/include -O2 lib/init.c | \
sed -e 's@^\(.*\)\.o:@lib/init.ad lib/init.ao: Makefile '`dirname lib/init.ad`/Module.mk' @' > lib/init.ad
cpp0: warning: changing search order for system directory "/usr/local/include"
cpp0: warning: as it has already been specified as a non-system directory
gcc -M -MG -I. -Ikernel/include -I/usr/local/include -I/lib/modules/2.4.18-14/build/include -O2 lib/access.c | \
sed -e 's@^\(.*\)\.o:@lib/access.ad lib/access.ao: Makefile '`dirname lib/access.ad`/Module.mk' @' > lib/access.ad
cpp0: warning: changing search order for system directory "/usr/local/include"
cpp0: warning: as it has already been specified as a non-system directory
gcc -M -MG -I. -Ikernel/include -I/usr/local/include -I/lib/modules/2.4.18-14/build/include -O2 lib/proc.c | \
sed -e 's@^\(.*\)\.o:@lib/proc.ad lib/proc.ao: Makefile '`dirname lib/proc.ad`/Module.mk' @' > lib/proc.ad
cpp0: warning: changing search order for system directory "/usr/local/include"
cpp0: warning: as it has already been specified as a non-system directory
gcc -M -MG -I. -Ikernel/include -I/usr/local/include -I/lib/modules/2.4.18-14/build/include -O2 lib/chips.c | \
sed -e 's@^\(.*\)\.o:@lib/chips.ad lib/chips.ao: Makefile '`dirname lib/chips.ad`/Module.mk' @' > lib/chips.ad
cpp0: warning: changing search order for system directory "/usr/local/include"
cpp0: warning: as it has already been specified as a non-system directory
gcc -M -MG -I. -Ikernel/include -I/usr/local/include -I/lib/modules/2.4.18-14/build/include -O2 lib/error.c | \
sed -e 's@^\(.*\)\.o:@lib/error.ad lib/error.ao: Makefile '`dirname lib/error.ad`/Module.mk' @' > lib/error.ad
cpp0: warning: changing search order for system directory "/usr/local/include"
cpp0: warning: as it has already been specified as a non-system directory
gcc -M -MG -I. -Ikernel/include -I/usr/local/include -I/lib/modules/2.4.18-14/build/include -O2 lib/general.c | \
sed -e 's@^\(.*\)\.o:@lib/general.ad lib/general.ao: Makefile '`dirname lib/general.ad`/Module.mk' @' > lib/general.ad
cpp0: warning: changing search order for system directory "/usr/local/include"
cpp0: warning: as it has already been specified as a non-system directory
gcc -M -MG -I. -Ikernel/include -I/usr/local/include -I/lib/modules/2.4.18-14/build/include -O2 lib/data.c | \
sed -e 's@^\(.*\)\.o:@lib/data.ad lib/data.ao: Makefile '`dirname lib/data.ad`/Module.mk' @' > lib/data.ad
cpp0: warning: changing search order for system directory "/usr/local/include"
cpp0: warning: as it has already been specified as a non-system directory
gcc -M -MG -I. -Ikernel/include -I/usr/local/include -I/lib/modules/2.4.18-14/build/include -fpic -O2 lib/init.c | \
sed -e 's@^\(.*\)\.o:@lib/init.ld lib/init.lo: Makefile '`dirname lib/init.ld`/Module.mk' @' > lib/init.ld
cpp0: warning: changing search order for system directory "/usr/local/include"
cpp0: warning: as it has already been specified as a non-system directory
gcc -M -MG -I. -Ikernel/include -I/usr/local/include -I/lib/modules/2.4.18-14/build/include -fpic -O2 lib/access.c | \
sed -e 's@^\(.*\)\.o:@lib/access.ld lib/access.lo: Makefile '`dirname lib/access.ld`/Module.mk' @' > lib/access.ld
cpp0: warning: changing search order for system directory "/usr/local/include"
cpp0: warning: as it has already been specified as a non-system directory
gcc -M -MG -I. -Ikernel/include -I/usr/local/include -I/lib/modules/2.4.18-14/build/include -fpic -O2 lib/proc.c | \
sed -e 's@^\(.*\)\.o:@lib/proc.ld lib/proc.lo: Makefile '`dirname lib/proc.ld`/Module.mk' @' > lib/proc.ld
cpp0: warning: changing search order for system directory "/usr/local/include"
cpp0: warning: as it has already been specified as a non-system directory
gcc -M -MG -I. -Ikernel/include -I/usr/local/include -I/lib/modules/2.4.18-14/build/include -fpic -O2 lib/chips.c | \
sed -e 's@^\(.*\)\.o:@lib/chips.ld lib/chips.lo: Makefile '`dirname lib/chips.ld`/Module.mk' @' > lib/chips.ld
cpp0: warning: changing search order for system directory "/usr/local/include"
cpp0: warning: as it has already been specified as a non-system directory
gcc -M -MG -I. -Ikernel/include -I/usr/local/include -I/lib/modules/2.4.18-14/build/include -fpic -O2 lib/error.c | \
sed -e 's@^\(.*\)\.o:@lib/error.ld lib/error.lo: Makefile '`dirname lib/error.ld`/Module.mk' @' > lib/error.ld
cpp0: warning: changing search order for system directory "/usr/local/include"
cpp0: warning: as it has already been specified as a non-system directory
gcc -M -MG -I. -Ikernel/include -I/usr/local/include -I/lib/modules/2.4.18-14/build/include -fpic -O2 lib/general.c | \
sed -e 's@^\(.*\)\.o:@lib/general.ld lib/general.lo: Makefile '`dirname lib/general.ld`/Module.mk' @' > lib/general.ld
cpp0: warning: changing search order for system directory "/usr/local/include"
cpp0: warning: as it has already been specified as a non-system directory
gcc -M -MG -I. -Ikernel/include -I/usr/local/include -I/lib/modules/2.4.18-14/build/include -fpic -O2 lib/data.c | \
sed -e 's@^\(.*\)\.o:@lib/data.ld lib/data.lo: Makefile '`dirname lib/data.ld`/Module.mk' @' > lib/data.ld
cpp0: warning: changing search order for system directory "/usr/local/include"
cpp0: warning: as it has already been specified as a non-system directory
gcc -M -MG -D__SMP__ -DMODVERSIONS -include /lib/modules/2.4.18-14/build/include/linux/modversions.h -D__KERNEL__ -DMODULE -DEXPORT_SYMTAB -fomit-frame-pointer -I. -Ikernel/include -I/usr/local/include -I/lib/modules/2.4.18-14/build/include -O2 kernel/chips/vt1211.c | \
sed -e 's@^\(.*\)\.o:@kernel/chips/vt1211.d kernel/chips/vt1211.o: Makefile '`dirname kernel/chips/vt1211.d`/Module.mk' @' > kernel/chips/vt1211.d
cpp0: warning: changing search order for system directory "/usr/local/include"
cpp0: warning: as it has already been specified as a non-system directory
gcc -M -MG -D__SMP__ -DMODVERSIONS -include /lib/modules/2.4.18-14/build/include/linux/modversions.h -D__KERNEL__ -DMODULE -DEXPORT_SYMTAB -fomit-frame-pointer -I. -Ikernel/include -I/usr/local/include -I/lib/modules/2.4.18-14/build/include -O2 kernel/chips/via686a.c | \
sed -e 's@^\(.*\)\.o:@kernel/chips/via686a.d kernel/chips/via686a.o: Makefile '`dirname kernel/chips/via686a.d`/Module.mk' @' > kernel/chips/via686a.d
cpp0: warning: changing search order for system directory "/usr/local/include"
cpp0: warning: as it has already been specified as a non-system directory
gcc -M -MG -D__SMP__ -DMODVERSIONS -include /lib/modules/2.4.18-14/build/include/linux/modversions.h -D__KERNEL__ -DMODULE -DEXPORT_SYMTAB -fomit-frame-pointer -I. -Ikernel/include -I/usr/local/include -I/lib/modules/2.4.18-14/build/include -O2 kernel/chips/w83781d.c | \
sed -e 's@^\(.*\)\.o:@kernel/chips/w83781d.d kernel/chips/w83781d.o: Makefile '`dirname kernel/chips/w83781d.d`/Module.mk' @' > kernel/chips/w83781d.d
cpp0: warning: changing search order for system directory "/usr/local/include"
cpp0: warning: as it has already been specified as a non-system directory
gcc -M -MG -D__SMP__ -DMODVERSIONS -include /lib/modules/2.4.18-14/build/include/linux/modversions.h -D__KERNEL__ -DMODULE -DEXPORT_SYMTAB -fomit-frame-pointer -I. -Ikernel/include -I/usr/local/include -I/lib/modules/2.4.18-14/build/include -O2 kernel/chips/thmc50.c | \
sed -e 's@^\(.*\)\.o:@kernel/chips/thmc50.d kernel/chips/thmc50.o: Makefile '`dirname kernel/chips/thmc50.d`/Module.mk' @' > kernel/chips/thmc50.d
cpp0: warning: changing search order for system directory "/usr/local/include"
cpp0: warning: as it has already been specified as a non-system directory
gcc -M -MG -D__SMP__ -DMODVERSIONS -include /lib/modules/2.4.18-14/build/include/linux/modversions.h -D__KERNEL__ -DMODULE -DEXPORT_SYMTAB -fomit-frame-pointer -I. -Ikernel/include -I/usr/local/include -I/lib/modules/2.4.18-14/build/include -O2 kernel/chips/smsc47m1.c | \
sed -e 's@^\(.*\)\.o:@kernel/chips/smsc47m1.d kernel/chips/smsc47m1.o: Makefile '`dirname kernel/chips/smsc47m1.d`/Module.mk' @' > kernel/chips/smsc47m1.d
cpp0: warning: changing search order for system directory "/usr/local/include"
cpp0: warning: as it has already been specified as a non-system directory
gcc -M -MG -D__SMP__ -DMODVERSIONS -include /lib/modules/2.4.18-14/build/include/linux/modversions.h -D__KERNEL__ -DMODULE -DEXPORT_SYMTAB -fomit-frame-pointer -I. -Ikernel/include -I/usr/local/include -I/lib/modules/2.4.18-14/build/include -O2 kernel/chips/sis5595.c | \
sed -e 's@^\(.*\)\.o:@kernel/chips/sis5595.d kernel/chips/sis5595.o: Makefile '`dirname kernel/chips/sis5595.d`/Module.mk' @' > kernel/chips/sis5595.d
cpp0: warning: changing search order for system directory "/usr/local/include"
cpp0: warning: as it has already been specified as a non-system directory
gcc -M -MG -D__SMP__ -DMODVERSIONS -include /lib/modules/2.4.18-14/build/include/linux/modversions.h -D__KERNEL__ -DMODULE -DEXPORT_SYMTAB -fomit-frame-pointer -I. -Ikernel/include -I/usr/local/include -I/lib/modules/2.4.18-14/build/include -O2 kernel/chips/pcf8591.c | \
sed -e 's@^\(.*\)\.o:@kernel/chips/pcf8591.d kernel/chips/pcf8591.o: Makefile '`dirname kernel/chips/pcf8591.d`/Module.mk' @' > kernel/chips/pcf8591.d
cpp0: warning: changing search order for system directory "/usr/local/include"
cpp0: warning: as it has already been specified as a non-system directory
gcc -M -MG -D__SMP__ -DMODVERSIONS -include /lib/modules/2.4.18-14/build/include/linux/modversions.h -D__KERNEL__ -DMODULE -DEXPORT_SYMTAB -fomit-frame-pointer -I. -Ikernel/include -I/usr/local/include -I/lib/modules/2.4.18-14/build/include -O2 kernel/chips/pcf8574.c | \
sed -e 's@^\(.*\)\.o:@kernel/chips/pcf8574.d kernel/chips/pcf8574.o: Makefile '`dirname kernel/chips/pcf8574.d`/Module.mk' @' > kernel/chips/pcf8574.d
cpp0: warning: changing search order for system directory "/usr/local/include"
cpp0: warning: as it has already been specified as a non-system directory
gcc -M -MG -D__SMP__ -DMODVERSIONS -include /lib/modules/2.4.18-14/build/include/linux/modversions.h -D__KERNEL__ -DMODULE -DEXPORT_SYMTAB -fomit-frame-pointer -I. -Ikernel/include -I/usr/local/include -I/lib/modules/2.4.18-14/build/include -O2 kernel/chips/mtp008.c | \
sed -e 's@^\(.*\)\.o:@kernel/chips/mtp008.d kernel/chips/mtp008.o: Makefile '`dirname kernel/chips/mtp008.d`/Module.mk' @' > kernel/chips/mtp008.d
cpp0: warning: changing search order for system directory "/usr/local/include"
cpp0: warning: as it has already been specified as a non-system directory
gcc -M -MG -D__SMP__ -DMODVERSIONS -include /lib/modules/2.4.18-14/build/include/linux/modversions.h -D__KERNEL__ -DMODULE -DEXPORT_SYMTAB -fomit-frame-pointer -I. -Ikernel/include -I/usr/local/include -I/lib/modules/2.4.18-14/build/include -O2 kernel/chips/maxilife.c | \
sed -e 's@^\(.*\)\.o:@kernel/chips/maxilife.d kernel/chips/maxilife.o: Makefile '`dirname kernel/chips/maxilife.d`/Module.mk' @' > kernel/chips/maxilife.d
cpp0: warning: changing search order for system directory "/usr/local/include"
cpp0: warning: as it has already been specified as a non-system directory
gcc -M -MG -D__SMP__ -DMODVERSIONS -include /lib/modules/2.4.18-14/build/include/linux/modversions.h -D__KERNEL__ -DMODULE -DEXPORT_SYMTAB -fomit-frame-pointer -I. -Ikernel/include -I/usr/local/include -I/lib/modules/2.4.18-14/build/include -O2 kernel/chips/matorb.c | \
sed -e 's@^\(.*\)\.o:@kernel/chips/matorb.d kernel/chips/matorb.o: Makefile '`dirname kernel/chips/matorb.d`/Module.mk' @' > kernel/chips/matorb.d
cpp0: warning: changing search order for system directory "/usr/local/include"
cpp0: warning: as it has already been specified as a non-system directory
gcc -M -MG -D__SMP__ -DMODVERSIONS -include /lib/modules/2.4.18-14/build/include/linux/modversions.h -D__KERNEL__ -DMODULE -DEXPORT_SYMTAB -fomit-frame-pointer -I. -Ikernel/include -I/usr/local/include -I/lib/modules/2.4.18-14/build/include -O2 kernel/chips/ltc1710.c | \
sed -e 's@^\(.*\)\.o:@kernel/chips/ltc1710.d kernel/chips/ltc1710.o: Makefile '`dirname kernel/chips/ltc1710.d`/Module.mk' @' > kernel/chips/ltc1710.d
cpp0: warning: changing search order for system directory "/usr/local/include"
cpp0: warning: as it has already been specified as a non-system directory
gcc -M -MG -D__SMP__ -DMODVERSIONS -include /lib/modules/2.4.18-14/build/include/linux/modversions.h -D__KERNEL__ -DMODULE -DEXPORT_SYMTAB -fomit-frame-pointer -I. -Ikernel/include -I/usr/local/include -I/lib/modules/2.4.18-14/build/include -O2 kernel/chips/lm92.c | \
sed -e 's@^\(.*\)\.o:@kernel/chips/lm92.d kernel/chips/lm92.o: Makefile '`dirname kernel/chips/lm92.d`/Module.mk' @' > kernel/chips/lm92.d
cpp0: warning: changing search order for system directory "/usr/local/include"
cpp0: warning: as it has already been specified as a non-system directory
gcc -M -MG -D__SMP__ -DMODVERSIONS -include /lib/modules/2.4.18-14/build/include/linux/modversions.h -D__KERNEL__ -DMODULE -DEXPORT_SYMTAB -fomit-frame-pointer -I. -Ikernel/include -I/usr/local/include -I/lib/modules/2.4.18-14/build/include -O2 kernel/chips/lm87.c | \
sed -e 's@^\(.*\)\.o:@kernel/chips/lm87.d kernel/chips/lm87.o: Makefile '`dirname kernel/chips/lm87.d`/Module.mk' @' > kernel/chips/lm87.d
cpp0: warning: changing search order for system directory "/usr/local/include"
cpp0: warning: as it has already been specified as a non-system directory
gcc -M -MG -D__SMP__ -DMODVERSIONS -include /lib/modules/2.4.18-14/build/include/linux/modversions.h -D__KERNEL__ -DMODULE -DEXPORT_SYMTAB -fomit-frame-pointer -I. -Ikernel/include -I/usr/local/include -I/lib/modules/2.4.18-14/build/include -O2 kernel/chips/lm80.c | \
sed -e 's@^\(.*\)\.o:@kernel/chips/lm80.d kernel/chips/lm80.o: Makefile '`dirname kernel/chips/lm80.d`/Module.mk' @' > kernel/chips/lm80.d
cpp0: warning: changing search order for system directory "/usr/local/include"
cpp0: warning: as it has already been specified as a non-system directory
gcc -M -MG -D__SMP__ -DMODVERSIONS -include /lib/modules/2.4.18-14/build/include/linux/modversions.h -D__KERNEL__ -DMODULE -DEXPORT_SYMTAB -fomit-frame-pointer -I. -Ikernel/include -I/usr/local/include -I/lib/modules/2.4.18-14/build/include -O2 kernel/chips/lm78.c | \
sed -e 's@^\(.*\)\.o:@kernel/chips/lm78.d kernel/chips/lm78.o: Makefile '`dirname kernel/chips/lm78.d`/Module.mk' @' > kernel/chips/lm78.d
cpp0: warning: changing search order for system directory "/usr/local/include"
cpp0: warning: as it has already been specified as a non-system directory
gcc -M -MG -D__SMP__ -DMODVERSIONS -include /lib/modules/2.4.18-14/build/include/linux/modversions.h -D__KERNEL__ -DMODULE -DEXPORT_SYMTAB -fomit-frame-pointer -I. -Ikernel/include -I/usr/local/include -I/lib/modules/2.4.18-14/build/include -O2 kernel/chips/lm75.c | \
sed -e 's@^\(.*\)\.o:@kernel/chips/lm75.d kernel/chips/lm75.o: Makefile '`dirname kernel/chips/lm75.d`/Module.mk' @' > kernel/chips/lm75.d
cpp0: warning: changing search order for system directory "/usr/local/include"
cpp0: warning: as it has already been specified as a non-system directory
gcc -M -MG -D__SMP__ -DMODVERSIONS -include /lib/modules/2.4.18-14/build/include/linux/modversions.h -D__KERNEL__ -DMODULE -DEXPORT_SYMTAB -fomit-frame-pointer -I. -Ikernel/include -I/usr/local/include -I/lib/modules/2.4.18-14/build/include -O2 kernel/chips/it87.c | \
sed -e 's@^\(.*\)\.o:@kernel/chips/it87.d kernel/chips/it87.o: Makefile '`dirname kernel/chips/it87.d`/Module.mk' @' > kernel/chips/it87.d
cpp0: warning: changing search order for system directory "/usr/local/include"
cpp0: warning: as it has already been specified as a non-system directory


wieder nur Fehler

[BLUESCREEN3D]

Falls du keine module magst lm_sensor ist auch als kernel patch erhältlich.

Wo ist der Unterschied und was ist einfacher?

[kleinerchaot]

Ich bin sehr an der Lösung des Problems von BLUESCREEN3D interessiert. Das sieht nämlich genauso aus wie bei mir :confused:

[Sayonara]

@BLUESCREEN3D
hast du etwa "make menuconfig" im lm_sensors Verzeichnis ausgeführt? Das musst du unter /usr/src/linux machen! Lade dann die Konfigurationsdatei rein und beende menuconfig und speichere die Einstellung ab. Dann "make dep".
Und dann versuche nochmal im lm_sensors Verzeichnis: "make"

[DustPuppy]

du hast ja gottseidank die config ;-) nicht make menuconfig in lm_sensor verzeichnis in /usr/src/linux !
also am besten so

cd /usr/src/linux
make menuconfig #oder
make oldconfig
make dep

#dann in
#i2c verzeichnis was du dir gedownloaded hast
make
make install

#dann in
#lm_sensor verzeichnis was du dir gedownloaded hast
make
make install

denn rest habe ich vorher ja ä beschrieben.
der unterschied ist das du dann alles gleich in den kernel eincompilieren kannst, nur falls du ne abneigung gegen module hast.

[BLUESCREEN3D]

zwsichendruch habe ich mal kurz Fehlermeldungen gesehen und bei "make" geht es wieder nicht:

[root@server i2c-2.7.0]# make
Makefile:188: kernel/i2c-philips-par.d: Datei oder Verzeichnis nicht gefunden
gcc -M -MG -I/lib/modules/2.4.18-14/build/include -O2 -DLM_SENSORS -D__KERNEL__ -DMODULE -fomit-frame-pointer -DEXPORT_SYMTAB -DMODVERSIONS -include /lib/modules/2.4.18-14/build/include/linux/modversions.h kernel/i2c-philips-par.c | \
sed -e 's@^\(.*\)\.o:@kernel/i2c-philips-par.d kernel/i2c-philips-par.o: Makefile '`dirname kernel/i2c-philips-par.d`/Module.mk' @' > kernel/i2c-philips-par.d
gcc -I/lib/modules/2.4.18-14/build/include -O2 -DLM_SENSORS -D__KERNEL__ -DMODULE -fomit-frame-pointer -DEXPORT_SYMTAB -DMODVERSIONS -include /lib/modules/2.4.18-14/build/include/linux/modversions.h -c kernel/i2c-core.c -o kernel/i2c-core.o
In file included from /lib/modules/2.4.18-14/build/include/linux/prefetch.h:13,
from /lib/modules/2.4.18-14/build/include/linux/list.h:6,
from /lib/modules/2.4.18-14/build/include/linux/module.h:12,
from kernel/i2c-core.c:26:
/lib/modules/2.4.18-14/build/include/asm/processor.h:51: warning: parameter names (without types) in function declaration
/lib/modules/2.4.18-14/build/include/asm/processor.h:51: field `loops_per_jiffy_R_ver_str' declared as a function
/lib/modules/2.4.18-14/build/include/asm/processor.h:73: invalid suffix on integer constant
/lib/modules/2.4.18-14/build/include/asm/processor.h:73: parse error before numeric constant
/lib/modules/2.4.18-14/build/include/asm/processor.h:256: invalid suffix on integer constant
/lib/modules/2.4.18-14/build/include/asm/processor.h:256: parse error before numeric constant
/lib/modules/2.4.18-14/build/include/asm/processor.h:260: warning: parameter names (without types) in function declaration
/lib/modules/2.4.18-14/build/include/asm/processor.h:436: invalid suffix on floating constant
/lib/modules/2.4.18-14/build/include/asm/processor.h:436: parse error before numeric constant
/lib/modules/2.4.18-14/build/include/asm/processor.h:436: `kernel_thread_R_ver_str' declared as function returning a function
In file included from kernel/i2c-core.c:26:
/lib/modules/2.4.18-14/build/include/linux/module.h:183: invalid suffix on integer constant
/lib/modules/2.4.18-14/build/include/linux/module.h:183: parse error before numeric constant
/lib/modules/2.4.18-14/build/include/linux/module.h:183: `inter_module_register_R_ver_str' declared as function returning a function
/lib/modules/2.4.18-14/build/include/linux/module.h:184: invalid suffix on integer constant
/lib/modules/2.4.18-14/build/include/linux/module.h:184: parse error before numeric constant
/lib/modules/2.4.18-14/build/include/linux/module.h:184: `inter_module_unregister_R_ver_str' declared as function returning a function
/lib/modules/2.4.18-14/build/include/linux/module.h:185: `inter_module_get_R_ver_str' declared as function returning a function
/lib/modules/2.4.18-14/build/include/linux/module.h:185: warning: parameter names (without types) in function declaration
/lib/modules/2.4.18-14/build/include/linux/module.h:186: `inter_module_get_request_R_ver_str' declared as function returning a function
/lib/modules/2.4.18-14/build/include/linux/module.h:186: warning: parameter names (without types) in function declaration
/lib/modules/2.4.18-14/build/include/linux/module.h:187: invalid suffix on integer constant
/lib/modules/2.4.18-14/build/include/linux/module.h:187: parse error before numeric constant
/lib/modules/2.4.18-14/build/include/linux/module.h:187: `inter_module_put_R_ver_str' declared as function returning a function
/lib/modules/2.4.18-14/build/include/linux/module.h:196: `try_inc_mod_count_R_ver_str' declared as function returning a function
/lib/modules/2.4.18-14/build/include/linux/module.h:196: warning: parameter names (without types) in function declaration
make: *** [kernel/i2c-core.o] Fehler 1

[DustPuppy]

vieleicht solltest du aus den sourcen deinen kernel neu baun ... , was anderes fällt mir jetzt wirklich nicht ein.
das geht so

cd /usr/src/linux
make dep && clean bzImage
mount /boot
mv /boot/vmlinuz /boot/vmlinuz.work
cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz

lilo config anpassen (/boot/vmlinuz.work eintragen)
lilo #ausführen

[kleinerchaot]

Original geschrieben von Linuxschrotter
vieleicht solltest du aus den sourcen deinen kernel neu baun ... ,
:eek:
könntest Du das nochmal genauer beschreiben? Ich bin ein echter Newbie und bin mir beim Kernelbraten nicht so ganz sicher (sollte ich das überhaupt?). Ich lade mir die tar.gz aus dem Netz und entpacke sie...und wo muss ich die speichern, damit sie beim Neubau des Kernels eingebunden werden? Bleibt der alte Kernel unter boot (falls etwas schief geht nur in lilo den alten eintragen?)
Aber vielleicht mache ich auch etwas ganz Grundlegendes falsch (wie gesagt ich bin absoluter Newbie) und deshalb habe ich immer die Fehler (wie oben geschrieben sehen die LOGS fast identisch aus)
Ich habe übrigens auch RedHat 8 drauf...

[B43r]

hi,
ich habe die anleitung befolgt, installieren und starten geht auch ohne prob allerdings wenn ich
sensor
eingebe kommt nur:
command not found.

Ich verwende RedHat 8.0!

Woran kann das liegen???



mfg B43R

[BLUESCREEN3D]

@kernel bauen:
dann muss ich ja ne grafikkarte einbauen und monitor und tastatur anschließen... geht es nicht einfacher?

[DustPuppy]

Original geschrieben von B43r
hi,
ich habe die anleitung befolgt, installieren und starten geht auch ohne prob allerdings wenn ich
sensor
eingebe kommt nur:
command not found.

Ich verwende RedHat 8.0!

Woran kann das liegen???



mfg B43R

"sensors" ;)

[DustPuppy]

Original geschrieben von kleinerchaot
:eek:
könntest Du das nochmal genauer beschreiben? Ich bin ein echter Newbie und bin mir beim Kernelbraten nicht so ganz sicher (sollte ich das überhaupt?). Ich lade mir die tar.gz aus dem Netz und entpacke sie...und wo muss ich die speichern, damit sie beim Neubau des Kernels eingebunden werden? Bleibt der alte Kernel unter boot (falls etwas schief geht nur in lilo den alten eintragen?)
Aber vielleicht mache ich auch etwas ganz Grundlegendes falsch (wie gesagt ich bin absoluter Newbie) und deshalb habe ich immer die Fehler (wie oben geschrieben sehen die LOGS fast identisch aus)
Ich habe übrigens auch RedHat 8 drauf...


Guck hier (http://www.linuxforen.de/forums/showthread.php?s=&threadid=20583&highlight=kernel)

übrigens ist es nicht immer sinnvoll auf eine höhere kernel version umzusteigen, da redhat seine kernel sourcen mit sehr vielen patches versehen hat und z.B. der redhat kernel 2.4.4.19 mehr kann als der 2.4.4.20 original kernel .

[DustPuppy]

Original geschrieben von BLUESCREEN3D
@kernel bauen:
dann muss ich ja ne grafikkarte einbauen und monitor und tastatur anschließen... geht es nicht einfacher?

nö, musst du nicht kannst du über ssh oder telnet machen musst halt nur drauf achten, das der neue kernel als default boot einstellung bei lilo eingestellt ist (erster eintrag) so das bei einen reboot der neue kernel gebootet wird.

Hast du vieleicht auf deiner cd schon mal nach i2c und lm_sensor rpms gesucht ?