Ik heb nu lekker Gklemm aan de gang, alleen ik wil de temps hebben, maar ik ben tegen 2 dingen (misschien komen er nog meer
) aangelopen, zo heb ik de plugin voor de temp geinstalleerd (gklmsensors), alleen dan komt ie met een hele rij met foutmeldingen en niet gevonden mappen, en uiteindelijk FOUT 1. En als ik sensors-detect doe dan kan ie de viapro module niet vinden/ maken. waardoor ik dus ook geen temps heb. Ik heb alle relevante dingen gedaan, die source is ook al geimplementeerd (ofso) maar ik krijg het niet aan de gang, ik zal wel iets fout doen denk ik 
OS is Debian Unstable ( 90% dan) op een ASUS A7V333 (via kt333 dus) mobo.
Maar hoe krijg ik alles aan de gang??
bijlage1:
foutmelding bij sensorsdetect
OS is Debian Unstable ( 90% dan) op een ASUS A7V333 (via kt333 dus) mobo.
Maar hoe krijg ik alles aan de gang??
bijlage1:
code:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
| 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 installed lm-sensors modules before you can use
some functions of this utility.
Also, you need to be `root', or at least have access to
the /dev/i2c[-/]* files for some things.
If you have patched your kernel and have some drivers built-in you can
safely answer NO if asked to load some modules. In this case, things may
seem a bit confusing, but they will still work.
BIOS vendor (ACPI): ASUS
System vendor (DMI): MAXDATA
BIOS version (DMI): ASUS A7V333 ACPI BIOS Revision 1016
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-viapro' for device 00:11.0: VIA Technologies VT8233A South Bridge
Probe succesfully concluded.
We will now try to load each adapter module in turn.
Load `i2c-viapro' (say NO if built into your kernel)? (YES/no): yes
modprobe: Can't locate module i2c-viapro
Loading failed... skipping.
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.20-xfs/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.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.20-xfs/kernel/drivers/i2c/i2c-elektor.o: insmod /lib/modules/2.4.20-xfs/kernel/drivers/i2c/i2c-elektor.o failed
/lib/modules/2.4.20-xfs/kernel/drivers/i2c/i2c-elektor.o: insmod i2c-elektor failed
Loading failed... skipping.
Load `i2c-elv' (say NO if built into your kernel)? (YES/no): yes
Module loaded succesfully.
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.20-xfs/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.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.20-xfs/kernel/drivers/i2c/i2c-velleman.o: insmod /lib/modules/2.4.20-xfs/kernel/drivers/i2c/i2c-velleman.o failed
/lib/modules/2.4.20-xfs/kernel/drivers/i2c/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).
Next adapter: ELV Parallel port adaptor (Bit-shift algorithm)
Do you want to scan it? (YES/no/selectively): no
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... Failed!
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... Failed!
Probing for `IPMI BMC KCS'
Trying address 0x0ca0... Failed!
Probing for `IPMI BMC SMIC'
Trying address 0x0ca8... Failed!
Sorry, no chips were detected.
Either your sensors are not supported, or they are
connected to an I2C bus adapter that we do not support.
See doc/FAQ, doc/lm_sensors-FAQ.html, or
http://www2.lm-sensors.nu/~lm78/cvs/lm_sensors2/doc/lm_sensors-FAQ.html
(FAQ #4.24.3) for further information.
If you find out what chips are on your board, see
http://secure.netroedge.com/~lm78/newdrivers.html for driver status. |
foutmelding bij sensorsdetect