I have take a look on that. It is almost the same to the step that I compile the kernel except one step which is to upgrade the "module init tools". I followed the step to upgrade these modules and now the problem "QM_MODULES: Function not implemented" was solved. Becase of there are too many similar but different methods to compile the kernel, I just pick up one of them from the search. I don't know which one is right or wrong. Many of them did not mention the difference of compiling 2.4 and 2.6 series kernel. Then I recompile the 2.6.x one again. It used long time about 2 hours to finish such process even if many of unused feature was marked as 'N'. After reboot the system, I still get some error message of "Can't locate module". Some module name was changed form 2.4 to 2.6 such as the network card module "via-rhine" has been changed to "via-ircc". I need to modify the name in "modules.conf" to correct the internet connection. However sound modules still can't load automatically at startup. There is another error about IP tables. I can't remember such message. There are not any file call "var/logs/syslog". I browsed all the log file in "var/logs", but none of them record the load module fail message.
By using the modprobe command, all the modules can be successfully loaded manually after X started. The only problem need to be solved is how to load these module automatically without error at system startup. There are some files such as etc/modules.conf, etc/modprobe.conf, etc/rc0.d, which file and how to use these file or otherwise to solve the problem.
You say that you're not using grubby but LiLo instead. Then how did that error message got there? Messages won't show up out of nowhere.
No. I don't use grub. The only boot loader installed in my hard disk is NT loader from Windows XP. Install lilo to the linux partition can let the NT loader pass the control to lilo to boot linux, so I can dual boot these OS. I don't know how did that error message came out. May be there is a bug on the determinating process of boot loader in the program. It can't find lilo on /dev/hda, may be it think that the user was use grub.