Ein paar Produktfoto Impressionen:

I start with a newly installed Desktop Ubuntu 7.10 with Gnome Desktop in mind.

Basic Steps

1. Install lm-sensors
2. Configure lm-sensors
3. Install sensors-applet
4. Place the Gnome Sensors Applet into a panel and choose your temps to display
5. Configure your fans

Install lm-sensors

This is easy as always. Simply type the following into a terminal. You will be asked for your own password, because installation requires root access.

1. sudo apt-get install lm-sensors

Configure lm-sensors

Please run:

1. sudo sensors-detect

You will be asked some questions. Answer all with “yes”. At the end you will get a listing of kernel modules (drivers) to load for your hardware configuration. My system is an ASUS P5B Deluxe with a Core 2 Duo Processor. The output looks so:

1. To make the sensors modules behave correctly, add these lines to
2. /etc/modules:
3. #----cut here----
4. # I2C adapter drivers
5. # modprobe unknown adapter NVIDIA i2c adapter
6. # modprobe unknown adapter NVIDIA i2c adapter
7. # modprobe unknown adapter NVIDIA i2c adapter
8. # modprobe unknown adapter ISA main adapter
9. # Chip drivers
10. lm90
11. w83627ehf
12. coretemp
13. #----cut here----

Now you can let the script insert this configuration into the /etc/modules. It works without any problems. Now its safest to reboot but you can avoid the reboot if you are familiar with module loading.

Once you are back, you should do a quick check if all is running properly by running

1. sensors

in the terminal. On my system it looks so:

1. w83627dhg-isa-0290
2. Adapter: ISA adapter
3. VCore: +1.57 V (min = +0.00 V, max = +1.74 V)
4. in1: +12.14 V (min = +0.00 V, max = +0.00 V) ALARM
5. AVCC: +3.33 V (min = +0.00 V, max = +2.58 V) ALARM
6. 3VCC: +3.33 V (min = +0.51 V, max = +1.28 V) ALARM
7. in4: +1.34 V (min = +0.00 V, max = +0.03 V) ALARM
8. in5: +1.59 V (min = +0.13 V, max = +1.45 V) ALARM
9. in6: +4.15 V (min = +2.25 V, max = +0.03 V) ALARM
10. VSB: +3.31 V (min = +0.00 V, max = +0.19 V) ALARM
11. VBAT: +1.02 V (min = +1.33 V, max = +2.37 V) ALARM
12. Case Fan: 0 RPM (min = 10546 RPM, div = 128) ALARM
13. CPU Fan: 0 RPM (min = 104 RPM, div = 128) ALARM
14. Aux Fan: 1222 RPM (min = 42187 RPM, div = 8) ALARM
15. fan4: 0 RPM (min = 0 RPM, div = 128) ALARM
16. fan5: 2860 RPM (min = 3497 RPM, div = 2) ALARM
17. Sys Temp: +37°C (high = +2°C, hyst = +68°C)
18. CPU Temp: +31.5°C (high = +80.0°C, hyst = +75.0°C)
19. AUX Temp: +127.0°C (high = +80.0°C, hyst = +75.0°C) ALARM
20. coretemp-isa-0000
21. Adapter: ISA adapter
22. Core 0: +29°C (high = +85°C)
23. coretemp-isa-0001
24. Adapter: ISA adapter
25. Core 1: +30°C (high = +85°C)

If you see some reasonable output, your lm-sensors configuration will work properly. Now we can use some cool GUI tool to display these values.

Install sensors-applet

The package sensors-applet provides a usual Gnome desktop applet. I have chosen this because it integrates very well with the Gnome desktop. It looks an behaves just right. To install it type in the usual:

1. sudo apt-get install sensors-applet

Place the Gnome Sensors Applet into a panel and choose your temps to display

To place the sensors applet into your top panel, right click on it and choose Add to Panel....

Than you will see the Add to Panel Dialog. To get fast access to the Sensors Applet type in “sensors”.

Than drag&drop the Hardware Sensors Monitor onto you top panel. You will see some temperature sensors by default.

After this you are free to configure the applet. Do this by right clicking an chose Preferences. I choose to display only the System and the two Core temps.

Configure your Fans

Normally you would run pwmconfig and use than fancontrol but on my system it does not work. So I can’t write anything about it. I will continue writing if I solved this problem.

Here I have a short description for you which worked for me under Ubuntu 7.10:

• install Tor by running the command sudo apt-get install tor,
• install Privoxy by running the command sudo apt-get install privoxy,
• add the line forward-socks4a / localhost:9050 . (with the point at the end) to the file /etc/privoxy/config to let privoxy talk with tor,
• install the Torbutton extension for Firefox,
• and activate Tor by clicking on the tor button in the status bar of Firefox.

You should test this setup by visiting a website which shows your IP. This IP should be different from yours (as it should be one of a Tor relay) and it should change after a while (about 10 minutes).

For more informations have a look into the Ubuntu Community TOR Documentation.

In the last time I had to install Windows XP on my notebook because its hard disk failed. There I did install Ubuntu first and Windows second and I end up with a Windows installation where the system drive was labeled F. The problem was that the Windows installation detected the first two Linux partitions as something to matter and give them virtually the drive letters C and E (D was assinged to the DVD drive). At the end I hat to repeat the Windows installation with both Linux partitions hidden.

Now, today it was time to reinstall my Windows on my Desktop Computer. The reason was degraded performance. The partitions on my 250 GB hard drive was the following:

1. 30 GB Ubuntu partition
2. 40 GB Windows partition
3. 120 GB data partition
4. free space

So I simply booted from the Windows XP CD. In the setup I deleted the 40 GB Windows partition and created a new on in the same place. I ensure that the 40 GB partition was detected as C: and continue with the installation. As Windows comes up after installation all things seams right. I began to install drivers and the last Windows updates.

But at one point as I would assign a different drive letter to my 120 GB data partition. At my old installation it was O now it was E. But I could not change it because Windows says it is the system partition. I wonder. The 40 GB C partition was the start partition and the 120 GB E partition was the system partition. Why? I discovered that Windows put the boot.ini, NTDETECT.COM and ntldr at the 120 GB partition. This means that the data partition would now majority for the boot process. That is a thing to avoid!

To discover what Windows did with my partition table, I did boot a Linux Live CD and did run fdisk. Windows created a extended partition as second partition (40 GB) and added in this the 40 GB C partition as logical partition. I think because Windows is not able to boot from a logical partition it puts the kernel loader in the 120 GB data partition which was primary. But I never asked Windows to create a logical partition. A primary partition would be without any problems. I have no clue of the reasons Windows created a logical partition.

To recover this mess, I decided to install Windows another time. But this time a created the partition for Windows with fdisk under Linux and did hide the two other partitions. This time all things went good.

The Lesson at the End

Never let Windows create its own partition if you have more than one partition on your disk. Hide all the other partitions before install.

Der Übeltäter war mein Radiator. Dieser war so verstaubt, dass kein Licht mehr durchkam. Auf dem Bild sehr ihr nur noch eine graue Fläche. Selbst als der Lüfter auf 12 V lief, kam keine Luft hinten an.

Jetzt habe ich wieder relativ normale 55° C unter Last und 49° C im normalen Betrieb.

Ich habe die Grafiken und das Perl Script auf dem Snip: W32.Blaster.