Lately, I have been playing with Apache, MySql, and PHP, the three killer apps in this modern internet world. In order to learn how to use the softwares, I had to install them onto a server. This is when I encountered the ultimate pain of using unix-based applications. On Solaris, I tried to install Apache, then MySql and then PHP. It’s one thing after another. The Apache 2 depends on 5 other packages that need to be installed first. After installing it, configuring it to work takes another day of searching on Google to find tips, which apparently are very different from the standard README. Then MySql depends on a couple of more packages. Finally, the worst of them all, PHP takes 7~9 additional packages to make it work. And I still couldn’t get it installed due to some strange error messages, pointing to a broken build on SunFreeware.com. This means I would need to configure and re-compile it from source code. The entire process took several days and I consider myself pretty savvy. I threw my hands up and decided to give Windows a shot.

I went to each download site and download the corresponding Windows version, there was only one package to download for each application. Though I encountered some difficulties in setting up Apache, the entire process took only a couple hours and it was working right away! Why the Unix folks are making it so difficult for people to use the softwares. By all means, bundle all of the packages together or come out with a way to download all the dependent packages in one shot. I don’t care if it’s a legal issue or an ego issue. Let’s not make it any more difficult than it should be, or we’ll see Microsoft Windows takes over the world.

The time on My Solaris 10 server has drifted off by nearly 10 minutes. I thought there ought to be an automatic way to synchronize the time with the atomic clock on the Internet. The following may work if your server is behind a firewall (not proxy server) that has access to the Internet. Thanks to time.mit.edu who provides the real time clock.

Login as root
run “crontab -e”
add the following lines:

# sync up server time every day 4am
0 4 * * * rdate time.mit.edu

I’ve got my tip from Rich Burrridge’s Weblog.

For the last two weeks since I switched on the new NIS servers, per Sun’s IT mandate, I have not been able to send emails out from my smtp server (my own mail server) running on Solaris 10 x64. Of course, submitting the ticket to our IT department didn’t help because they don’t support “personal” mail servers, due to Sun’s outsourcing effort to cut costs.

Thanks to Google search, I found my clues on the following link:
http://www.sunmanagers.org/pipermail/summaries/2006-September/007532.html

After changing the following line to my /etc/mail/submit.cf , I was able to send mails again.
Amazing! Google may be better than IT support. In fact, I have resolved several installation issues (Apache, MySql) by searching on Google. Why do you need an IT support group when you have Google?

# “Smart” relay host (may be null)
#DS (old setting)
DSmailhost.sfbay.sun.com

Make sure the sendmail server is re-started with the following command:
svcadm restart smtp

Linux is notorious in positioning the horizontal position on your monitor. After installing the Ubuntu on my old Sony Vaio PCV-RX650, which has a Nvidia TNT2 display card, I found the display is shifted to the right, leaving a blank strip on the left and distorted image on the right. This was very annoying. I had to re-adjust the monitor every time. This was one the reasons I gave up on Linux a few years back. You’d never see this kind of problem on Windows. I’m determined to find the fix for this.

So, I ventured into Google and found a few tricks to set the display correctly once and for all.
First, run the “xvidtune” to determine all the parameters needed to adjust the display. See below:

This software is not really intuitive. You’d need to click “left” or “right” and then click “apply” to see the effect. Keep doing this until you get the desired screen fit and then click “show” to show the parameters on the terminal. Copy the output.

Then gedit or vi the following file /etc/X11/xorg.conf, which I append below:
paste the line in between the “Monitor” Section as follows:

Section “Monitor”
Identifier “Generic Monitor”
Option “DPMS”
HorizSync 30-83
VertRefresh 55-76
Modeline “NV1280x1024” 135.00 1280 1312 1456 1688 1024 1025 1028 1066 +hsync +vsync

You’d need to the prefix of “Modeline” in front of the line. Notice that I added “NV” (or any thing to make it unique) in front of “1280×1024”. Well this is really the trick that took me over a couple hours to figure out. This string “NV1280x1024” needs to have a same counter part in the Display Section. In my case, it is as follows:

SubSection “Display”
Depth 24
Modes “NV1280x1024”
# Modes “1280×1024” “1024×768” “800×600” “640×480”
EndSubSection

Notice that I comment out the original lines and all other Display sections so I can force X display
to use this particular mode I just specified. You may want to have more than one mode after you become more familiar with how the file works.

Save the file then refresh the display by doing
CTRL-ALT-BACKSPACE

The display should be what you intended. If not, keep editing the /etc/X11/xorg.conf file until you get what you want.
There it is. A bit tedious.

Appendix: My /etc/X11/xorg.conf file contents – your file may be different.
#=====================================================
# /etc/X11/xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf(5) manual page.
# (Type “man xorg.conf” at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section “Files”
FontPath “/usr/share/fonts/X11/misc”
FontPath “/usr/share/fonts/X11/cyrillic”
FontPath “/usr/share/fonts/X11/100dpi/:unscaled”
FontPath “/usr/share/fonts/X11/75dpi/:unscaled”
FontPath “/usr/share/fonts/X11/Type1”
FontPath “/usr/share/fonts/X11/100dpi”
FontPath “/usr/share/fonts/X11/75dpi”
# path to defoma fonts
FontPath “/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType”
EndSection

Section “Module”
Load “i2c”
Load “bitmap”
Load “ddc”
Load “dri”
Load “extmod”
Load “freetype”
Load “glx”
Load “int10”
Load “vbe”
EndSection

Section “InputDevice”
Identifier “Generic Keyboard”
Driver “kbd”
Option “CoreKeyboard”
Option “XkbRules” “xorg”
Option “XkbModel” “pc105”
Option “XkbLayout” “us”
EndSection

Section “InputDevice”
Identifier “Configured Mouse”
Driver “mouse”
Option “CorePointer”
Option “Device” “/dev/input/mice”
Option “Protocol” “ImPS/2”
Option “ZAxisMapping” “4 5”
Option “Emulate3Buttons” “true”
EndSection

Section “InputDevice”
Driver “wacom”
Identifier “stylus”
Option “Device” “/dev/input/wacom”
Option “Type” “stylus”
Option “ForceDevice” “ISDV4” # Tablet PC ONLY
EndSection

Section “InputDevice”
Driver “wacom”
Identifier “eraser”
Option “Device” “/dev/input/wacom”
Option “Type” “eraser”
Option “ForceDevice” “ISDV4” # Tablet PC ONLY
EndSection

Section “InputDevice”
Driver “wacom”
Identifier “cursor”
Option “Device” “/dev/input/wacom”
Option “Type” “cursor”
Option “ForceDevice” “ISDV4” # Tablet PC ONLY
EndSection

Section “Device”
Identifier “Generic Video Card”
Driver “nv”
BusID “PCI:1:0:0”
EndSection

Section “Monitor”
Identifier “Generic Monitor”
Option “DPMS”
HorizSync 30-83
VertRefresh 55-76
Modeline “NV1280x1024” 135.00 1280 1312 1456 1688 1024 1025 1028 1066 +hsync +vsync

EndSection

Section “Screen”
Identifier “Default Screen”
Device “Generic Video Card”
Monitor “Generic Monitor”
DefaultDepth 24
# SubSection “Display”
# Depth 1
# Modes “1280×1024” “1024×768” “800×600” “640×480”
# EndSubSection
# SubSection “Display”
# Depth 4
# Modes “1280×1024” “1024×768” “800×600” “640×480”
# EndSubSection
# SubSection “Display”
# Depth 8
# Modes “1280×1024” “1024×768” “800×600” “640×480”
# EndSubSection
# SubSection “Display”
# Depth 15
# Modes “1280×1024” “1024×768” “800×600” “640×480”
# EndSubSection
# SubSection “Display”
# Depth 16
# Modes “1280×1024” “1024×768” “800×600” “640×480”
# EndSubSection
SubSection “Display”
Depth 24
Modes “NV1280x1024”
# Modes “1280×1024” “1024×768” “800×600” “640×480”
EndSubSection
EndSection

Section “ServerLayout”
Identifier “Default Layout”
Screen “Default Screen”
InputDevice “Generic Keyboard”
InputDevice “Configured Mouse”
InputDevice “stylus” “SendCoreEvents”
InputDevice “cursor” “SendCoreEvents”
InputDevice “eraser” “SendCoreEvents”
EndSection

Section “DRI”
Mode 0666
EndSection

Thanks to the below link, I was able to turn down the annoying fans on my old Sony PCV-RX650 while running Ubuntu:
http://ubuntuforums.org/showthread.php?s=f65942f674eb3572c64c294ca6810608&t=238566&page=2
This problem has been bugging me and preventing me from running Linux on this system. I’m glad I was able to resolve this problem without having to upgrade the BIOS (~ $30) to have the latest ACPI 2.0 feature (currently it has APM).

I first found out that I need to activate the root password on Ubuntu by running “sudo password root”, this allows me to act like root.

I then followed the instructions of getting and installing the lm_sensors package first by running “sudo apt-get install lm-sensors”
run: sensors-detect (answered “yes” to all of their questions)
This basically add the following lines to /etc/modules:
#====================================
# Generated by sensors-detect on Thu Aug 23 23:44:40 2007
# I2C adapter drivers
i2c-i801
# Chip drivers
eeprom
w83627hf
#====================================
reboot to have the modules loaded

run: pwmconfig
to set the preferences
you can try to run fancontrol at this point as root to see if it is working.

Finally add a line below to to /etc/rc.local (to allow for auto execution upon power up)
/usr/sbin/fancontrol &

Below is the transcript of what I did:
======================================================
dtsai@ubuntu:~$ sensors
w83637hf-isa-0290
Adapter: ISA adapter
VCore: +1.74 V (min = +0.71 V, max = +0.70 V) ALARM
+12V: +11.92 V (min = +0.00 V, max = +3.89 V) ALARM
+3.3V: +3.36 V (min = +2.24 V, max = +0.51 V) ALARM
+5V: +5.15 V (min = +0.00 V, max = +0.21 V) ALARM
-12V: +6.06 V (min = -14.91 V, max = -4.14 V) ALARM
V5SB: +5.08 V (min = +0.00 V, max = +3.44 V) ALARM
VBat: +0.00 V (min = +0.00 V, max = +2.06 V)
fan1: 4530 RPM (min = 16071 RPM, div = 2) ALARM
CPU Fan: 2265 RPM (min = 168750 RPM, div = 4) ALARM
fan3: 0 RPM (min = -1 RPM, div = 2) ALARM
M/B Temp: -48°C (high = +33°C, hyst = -127°C) sensor = thermistor
CPU Temp: +38.5°C (high = +80°C, hyst = +75°C) sensor = diode
temp3: +34.0°C (high = +80°C, hyst = +75°C) sensor = thermistor
vid: +1.550 V (VRM Version 9.0)
alarms:
beep_enable:
Sound alarm enabled

dtsai@ubuntu:~$ pwmconfig
This program will search your sensors for pulse width modulation (pwm)
controls, and test each one to see if it controls a fan on
your motherboard. Note that many motherboards do not have pwm
circuitry installed, even if your sensor chip supports pwm.

We will attempt to briefly stop each fan using the pwm controls.
The program will attempt to restore each fan to full speed
after testing. However, it is ** very important ** that you
physically verify that the fans have been to full speed
after the program has completed.

Found the following PWM controls:
9191-0290/pwm1
9191-0290/pwm2
9191-0290/pwm3

Found the following fan sensors:
9191-0290/fan1_input current speed: 4530 RPM
9191-0290/fan2_input current speed: 2280 RPM
9191-0290/fan3_input current speed: 0 … skipping!

As you are not root, we cannot write the PWM settings.
Please run as root to continue.
dtsai@ubuntu:~$ su root
Password:
root@ubuntu:/home/dtsai# pwmconfig
This program will search your sensors for pulse width modulation (pwm)
controls, and test each one to see if it controls a fan on
your motherboard. Note that many motherboards do not have pwm
circuitry installed, even if your sensor chip supports pwm.

We will attempt to briefly stop each fan using the pwm controls.
The program will attempt to restore each fan to full speed
after testing. However, it is ** very important ** that you
physically verify that the fans have been to full speed
after the program has completed.

Found the following PWM controls:
9191-0290/pwm1
9191-0290/pwm2
9191-0290/pwm3

Found the following fan sensors:
9191-0290/fan1_input current speed: 4470 RPM
9191-0290/fan2_input current speed: 2265 RPM
9191-0290/fan3_input current speed: 0 … skipping!

Warning!!! This program will stop your fans, one at a time,
for approximately 5 seconds each!!!
This may cause your processor temperature to rise!!!
If you do not want to do this hit control-C now!!!
Hit return to continue:

Testing pwm control 9191-0290/pwm1 …
9191-0290/fan1_input … speed was 4470 now 0
It appears that fan 9191-0290/fan1_input
is controlled by pwm 9191-0290/pwm1
Would you like to generate a detailed correlation (y)? y
PWM 255 FAN 4530
PWM 240 FAN 4500
PWM 225 FAN 4272
PWM 210 FAN 4115
PWM 195 FAN 3857
PWM 180 FAN 3688
PWM 165 FAN 3426
PWM 150 FAN 3199
PWM 135 FAN 2973
PWM 120 FAN 2710
PWM 105 FAN 0
Fan Stopped at PWM = 105

9191-0290/fan2_input … speed was 2265 now 2265
no correlation

Testing pwm control 9191-0290/pwm2 …
9191-0290/fan1_input … speed was 4470 now 4383
no correlation
9191-0290/fan2_input … speed was 2265 now 0
It appears that fan 9191-0290/fan2_input
is controlled by pwm 9191-0290/pwm2
Would you like to generate a detailed correlation (y)?
PWM 255 FAN 2280
PWM 240 FAN 2280
PWM 225 FAN 2265
PWM 210 FAN 2265
PWM 195 FAN 2205
PWM 180 FAN 2149
PWM 165 FAN 2070
PWM 150 FAN 1985
PWM 135 FAN 1896
PWM 120 FAN 1814
PWM 105 FAN 1704
PWM 90 FAN 1607
PWM 75 FAN 1500
PWM 60 FAN 1383
PWM 45 FAN 0
Fan Stopped at PWM = 45

Testing pwm control 9191-0290/pwm3 …
9191-0290/fan1_input … speed was 4470 now 4500
no correlation
9191-0290/fan2_input … speed was 2265 now 2280
no correlation

No correlations were detected.
There is either no fan connected to the output of 9191-0290/pwm3,
or the connected fan has no rpm-signal connected to one of
the tested fan sensors. (Note: not all motherboards have
the pwm outputs connected to the fan connectors,
check out the hardware database on http://www.almico.com/forumindex.php)

Did you see/hear a fan stopping during the above test (n)?

Testing is complete.
Please verify that all fans have returned to their normal speed.

The fancontrol script can automatically respond to temperature changes
of your system by changing fanspeeds.
Do you want to set up its configuration file now (y)?
What should be the path to your fancontrol config file (/etc/fancontrol)?
/etc/fancontrol does not exist, shall I create it now (y)?
Loading configuration from /etc/fancontrol …

Select fan output to configure, or other action:
1) 9191-0290/pwm2 3) Change INTERVAL 5) Save and quit
2) 9191-0290/pwm1 4) Just quit 6) Show configuration
select (1-n): 6

Common Settings:
INTERVAL=10

Settings of 9191-0290/pwm2:
Depends on
Controls
MINTEMP=
MAXTEMP=
MINSTART=
MINSTOP=

Settings of 9191-0290/pwm1:
Depends on
Controls
MINTEMP=
MAXTEMP=
MINSTART=
MINSTOP=

select (1-n): 1

Current temperature readings are as follows:
9191-0290/temp1_input -48
9191-0290/temp2_input 36
9191-0290/temp3_input 34

Select a temperature sensor as source for 9191-0290/pwm2:
1) 9191-0290/temp1_input
2) 9191-0290/temp2_input
3) 9191-0290/temp3_input
4) None (Do not affect this PWM output)
select (1-n): 3

Enter the low temperature (C)
at which the fan should be switched off (0): 32

Enter the high temperature (C)
at which the fan should be switched to full speed (60):

Enter the minimum PWM value (0-255)
at which the fan STARTS spinning (press t to test) (150):

Enter the minimum PWM value (0-255)
at which the fan STOPS spinning (press t to test) (100):

select (1-n): 2

Current temperature readings are as follows:
9191-0290/temp1_input -48
9191-0290/temp2_input 35
9191-0290/temp3_input 34

Select a temperature sensor as source for 9191-0290/pwm1:
1) 9191-0290/temp1_input
2) 9191-0290/temp2_input
3) 9191-0290/temp3_input
4) None (Do not affect this PWM output)
select (1-n): 3

Enter the low temperature (C)
at which the fan should be switched off (0): 32

Enter the high temperature (C)
at which the fan should be switched to full speed (60):

Enter the minimum PWM value (0-255)
at which the fan STARTS spinning (press t to test) (150):

Enter the minimum PWM value (0-255)
at which the fan STOPS spinning (press t to test) (100):

select (1-n):
1) 9191-0290/pwm2 3) Change INTERVAL 5) Save and quit
2) 9191-0290/pwm1 4) Just quit 6) Show configuration
select (1-n): 6

Common Settings:
INTERVAL=10

Settings of 9191-0290/pwm2:
Depends on 9191-0290/temp3_input
Controls 9191-0290/fan2_input
MINTEMP=32
MAXTEMP=60
MINSTART=150
MINSTOP=100

Settings of 9191-0290/pwm1:
Depends on 9191-0290/temp3_input
Controls 9191-0290/fan1_input
MINTEMP=32
MAXTEMP=60
MINSTART=150
MINSTOP=100

select (1-n): 5

Saving configuration to /etc/fancontrol…
Configuration saved