-
Registrierter Benutzer
CPU-Temperatur
Gibt es ein einfaches (einfacher zu installieren als lm_sensors) Consolen-Programm, dass die CPU-Temperatur anzeigt?
-
überzeugter Linuxuser
eigentlich net!! basieren glaube alle auf den LM-Dingern
-
Premium Mitglied
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°
-
überzeugter Linuxuser
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 :-)
-
Premium Mitglied
das problem ist halt ...
ich weiss nicht was passt ! Asus ist dafür bekannt sicherheits halber so +10C° dazu zu addieren, . 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 ?
-
Registrierter Benutzer
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
-
-
überzeugter Linuxuser
ich hab nen Asus A7V266-E > zeigt bei meinem Duron 800@1000 MHz (1.67 V) 47 Grad an!!
10 weniger wären 37 -> das wär a bissl wenig oder???
Was hast du für ne CPU/Temp. ???
-
Premium Mitglied
laut ml_sensor 44.9 C° muss mal schnell in bios nachschaun.
laut bios 57.5 C°
Geändert von DustPuppy (28.12.02 um 18:30 Uhr)
-
Registrierter Benutzer
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
-
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
-
Premium Mitglied
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 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.
Geändert von DustPuppy (28.12.02 um 22:38 Uhr)
-
Registrierter Benutzer
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?
-
Registrierter Benutzer
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
-
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.
Berechtigungen
- Neue Themen erstellen: Nein
- Themen beantworten: Nein
- Anhänge hochladen: Nein
- Beiträge bearbeiten: Nein
-
Foren-Regeln
Lesezeichen