Summary of errors encountered during kernel Compilation

Summary of errors encountered during kernel compilation-general Linux technology-Linux programming and kernel information. The following is a detailed description. Although linux has been used for a long time, it is not the first time to compile the kernel.
The problem is that I learned something. I have compiled several kernels in the past two days, kernel2.6.8, kernel2.6.9,
Kernel2.6.10; compiled in debian and compiled in fedora3. A lot of problems have occurred, almost
I have almost met all the information I found on the forum.
First, let's talk about my hardware configuration:
KT400 Soltek Motherboard
Athlon xp 2000 +
Nvidia MX440 graphics card
Hitachi hard drive IDE Interface
Logitech usb mouse, keyboard set.
Software Configuration:
Windows XP
Install linux fedora core 3 in the Reiserfs format Partition
(Debian is hiweed debian 0.55 desktop)
Compilation steps:
Make xconfig or make menuconfig...
Make & make modules_install & make install
The error is as follows:
1) Kernel panics
(1) init Error
It is generally grub or lilo error. Here I will give my grub Configuration
Title Fedora Core (2.6.10)
Root (hd0, 7)
Kernel/boot/vmlinuz-2.6.10 ro root =/dev/hda8 rhgb quiet
Initrd/boot/initrd-2.6.10.img
Fedora users should rarely encounter such errors, because fedora does not need to edit grub by themselves.
Debian requires you to edit it yourself.
(2) Other kernel panic
Most of them are because the system file system format does not support compiling into the kernel, the corresponding ext2,
Ext3 and reiserfs cannot be deselected or just select a module.
In addition, a special kernel panic shares the. config file in different linux versions.
Cause, this is met for me.
For example, the. config file obtained by compiling the kernel In debian cannot be directly copied to fc3.
And vice versa.
Kernel panic: VFS, umable to mount root, unknow device block (3,8)
Redsea brother explains this as follows: The initrd format of fedora is ext2, and debian is cramfs,
The kernel config of fedora does not compile cramfs into the kernel, but serves as a module. If
If you use initrd at the same time, you cannot mount initrd.
The opposite is true.
2) cannot start x
It is generally block device-> graphics suport-> suport for frame buffer device
The kernel is not compiled. Based on my situation, the possible reason is that nvidia riva is selected and
It is compiled into the kernel, and the lots of out put debug option of riva is also used. of course, if it is nvidia's
Riva graphics card is not in this range. For this video card, you should not choose the riva option, or nvidia
The driver conflicts with riva.
3) shutdown fails. Neither the shutdown-h command nor the halt-p command can be used.
Generally, the power management is selected into the kernel, and only apm is selected instead of apci.
4) Although the light is on, the mouse cannot be driven.
No usb host controller driver is selected
5) the built-in sound card on the motherboard cannot recognize or output multiple audio streams.
The first reason is of course that no sound card is supported, and the second reason is that no alsa is supported.
It is doubtful that the sound card cannot be enabled if via ac 97 is not selected for pci devices.
Summary: Compile the kernel correctly. Otherwise, some hardware won't be used or can't be used into the system. This is a comparison.
Depressing. The above is just a problem I encountered when compiling the kernel. Not necessarily effective for everyone.
I hope that my brothers and sisters will continue to add this question. If you have any mistakes mentioned above, please correct them! So that you can refer to the problem when compiling the kernel, and you don't need to search so hard, because I searched very hard when I encountered the problem! Not found
It was really painful to solve the problem. I almost had no confidence in the error of kernel panic vfs.
With this, the compilation options that you don't understand are better by default.