Louwrentius

I have two systems that use the w83627ehf driver for hardware monitoring. However, if this driver is installed with a regular modprobe like:

modprobe w83627ehf

The result will be:

FATAL: Error inserting w83627ehf
(/lib/modules/2.6.28-1-amd64/kernel/drivers/hwmon/w83627ehf.ko): No such
device

I had this issue with the following mainboards:

Asus P5Q-EM DO (Core 2 duo) Asus: P6T deluxe (Core 7i)

The solution is simple, as I found after googling for some time:

modprobe w83627ehf force_id=0x8860

The result:

w83627ehf-isa-0290
Adapter: ISA adapter
VCore: +0.88 V (min = +0.00 V, max = +1.74 V)
in1: +11.67 V (min = +0.00 V, max = +5.49 V) ALARM
AVCC: +3.34 V (min = +0.40 V, max = +0.03 V) ALARM
3VCC: +3.31 V (min = +1.15 V, max = +0.58 V) ALARM
in4: +1.65 V (min = +0.54 V, max = +0.22 V) ALARM
in5: +2.04 V (min = +0.71 V, max = +0.11 V) ALARM
in6: +3.79 V (min = +0.10 V, max = +2.30 V) ALARM
VSB: +3.38 V (min = +0.45 V, max = +2.43 V) ALARM
VBAT: +3.30 V (min = +0.67 V, max = +0.77 V) ALARM
in9: +0.00 V (min = +1.10 V, max = +0.57 V) ALARM
Case Fan: 0 RPM (min = 104 RPM, div = 128) ALARM
CPU Fan: 0 RPM (min = 42187 RPM, div = 32) ALARM
Aux Fan: 0 RPM (min = 162 RPM, div = 128) ALARM
fan4: 0 RPM (min = 42187 RPM, div = 32) ALARM
fan5: 0 RPM (min = 42187 RPM, div = 32) ALARM
Sys Temp: +40.0°C (high = +4.0°C, hyst = +0.0°C) ALARM sensor = thermistor
CPU Temp: +42.0°C (high = +80.0°C, hyst = +75.0°C) sensor = diode
AUX Temp: +30.5°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor
cpu0_vid: +0.000 V

Sometimes, people are using software that does not support encrypted connections using SSL. To provide SSL-support to such a client, ncat can be used. Ncat is part of nmap, the famous port-scanner.

The main principle is that the non-ssl capable software does not connect to the SSL-based service, but to the local host. Ncat will be listening on the localhost and will setup an SSL-connection with the SSL-based service on behalf of the non-ssl capable software.

This simple command allows an application to browse to port 80, and perform regular HTTP-request, while in fact, they are encapsulated within a SSL- connection:

ncat -l 80 -c "ncat (ip-address) (port) --ssl"

The -l option specifies the local port on which the SSL-tunnel will be listening. The ip-address and port refer to the SSL-based service.

So if the client connects to 127.0.0.1 on port 80 it will actually connect through the SSL-tunnel to the external service.

Often stunnel is used for this job but this software craps out on debian Etch with some error like:

SSL routines:SSL3_GET_RECORD:bad decompression

But ncat is an excellent alternative.