If you still don't want to build your own kernel, have a look at our Documentation section for how to install a prebuilt Linux-VServer kernel for your distribution. Otherwise, read on. You'll need the vanilla kernel sources i. You can find links to both files in our Downloads section.
Note that for recent kernels, only development versions of the vserver patch exist. Now that we have a place to store our sources, we need to fetch them. We start with the vanilla sources. Now it is time to get the Linux-VServer patch and apply it to the sources. While we're at it, I tell you a nice trick I learned from Bertl, that allows you to keep a lot of source trees on your disk without using up lots of disk space and this also speeds up 'diff' a lot, which is really nice if you do kernel-hacking.
What we do is creating a hard-linked copy of our sources and patch this copy with the Linux-VServer patch. That way, only the patched files use additional disk space and because hard-linked files are equal by definition, diff doesn't need to compare them.
Now you have two sources, the vanilla sources for 2. You might ask "Why do I need two source trees at all? I only want one kernel! Here's one answer: Updates! If a new vanilla kernel is released, you can just download the patch from your version to the new version.
Otherwise, if you would have applied the patch to your one and only vanilla source tree, you would not be able to do this. The same applies for new Linux-VServer releases. That is, if a new Linux-VServer patch is available, you can simply create another hardlinked copy of your vanilla sources and apply the new patch using the copy. This can really save you time and bandwidth , since you can keep everything you might need, without wasting a lot of disk space.
But be aware that this needs some discipline when hacking the source. Because hard-linked files share the same data on the disk, you need to make sure that your editor does The Right Thing , otherwise you might mess up all your source trees There have been many scheduler changes in 2. If you continue to run X at a higher priority, it will do exactly what it is supposed to run the display server at a very high priority and you will notice consequences such as sound stuttering and slow application load times because your CPU is spending too long serving X and only X.
Please remove your "niceness" hacks! One of the changes that a default udev configuration introduces is different organisation of the mouse device nodes. An example is shown below:. If you used the gentoo-sources The developer of bootsplash appears to have lost interest in his project, given some design problems.
If you use lm-sensors to monitor system temperatures and power levels, you previously needed to install the i2c package in order to provide hardware support. The I2C hardware drivers are now included in the Linux 2. Remember to compile support for your specific I2C devices into the kernel configuration. You will then be able to use lm-sensors as usual. You will probably be familiar with using menuconfig from configuring 2. Fortunately, the front end has barely changed at all, but you will observe much better organisation of kernel options, plus many new options that weren't present in 2.
Also, remember to enable support for the filesystems that you use, and the hardware present in your system. Be sure to enable support for the IDE controller on your motherboard if you wish to benefit from fast DMA disk access. Wait for the kernel compilation to complete and observe the much more readable compilation output.
You must then update your bootloader config manually. Note that the above instructions are examples only, you should follow your usual procedure of updating kernels by following the instructions in the Gentoo Handbook see the Configuring the Kernel chapter.
When updating your bootloader config, do not remove the old entry pointing at your 2. This way, you will easily be able to switch between the two if something is not working. If you prefer to use genkernel instead of manually configuring your kernel, you will be happy to hear that using genkernel to produce 2. In the above example, we also take advantage of genkernel features to open menuconfig to allow you to customise the kernel configuration if you wish , and to update the grub bootloader configuration after compilation.
You should choose genkernel arguments that suit you, but do not forget to include the --udev argument! If you choose to update your bootloader config yourself, then you must remember to include the udev kernel parameter.
A sample grub config section is shown below, but remember to adjust the root parameter for the system. Many users will additionally rely on kernel modules that are built outside of the kernel tree.
Common examples are the binary ATI and Nvidia graphics drivers. You now need to install those modules, which will compile against the 2. This is the usual case of emerge packagename for all the external modules you are used to using with 2.
Refer again to the Configuring the Kernel chapter of the Gentoo Handbook for more info. You may have decided to compile some kernel components as modules as opposed to compiled directly into the kernel and would like to have them autoloaded on bootup like you did with 2. Also, if you installed any external modules from the portage tree as described above you will probably want to autoload them too. When you reboot, if you followed this document correctly so far, you will have the option of either loading Linux 2.
Choose Linux 2. Once the system has booted, check that things are working. If you made a mistake in the kernel configuration, don't worry, you can skip back to the conf section, make your change, recompile and install new kernel image, reboot, and try again! We will now complete the ALSA configuration and unmute the audio channels.
The ALSA packages provide a useful utility to make this process relatively simple:. You should now add alsasound to your boot runlevel, so that volumes will be saved on shutdown and restored on bootup:. At this stage you should refer back to the pitfalls section which may be helpful with any issues you encounter immediately. By now you are running Linux 2.
You should now update your Linux kernel header files and re-merge glibc so that userspace applications can take advantage of new Linux 2. After updating your headers package, you should generally re-merge glibc. There is a new feature here that you may be interested in - NPTL. NPTL is a new threading model present in Linux 2. This won't make much of a difference to most systems, but you may wish to enable it during this migration process! If you enabled NPTL, existing binaries will not use it until they are recompiled.
However, any binaries compiled from this point onwards will use NPTL. You may wish to recompile all binaries now, e. I had to install an even older kernel 2. VBoot releases their module built in the kernel and I had to match versions to get my other hardware to work.
In the steps below, replace x. Note this is for the generic kernel and not using extra features such as PAE. Rather than going backwards why not try the newer kernel and see if that fixes the problems you seem to be experiencing and at the same time updating your system to a more stable and bug free release?
Ubuntu Community Ask! Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. How do I install an older 2. Ask Question. Asked 10 years ago. Active 5 years, 7 months ago. Viewed 19k times. Note: I have a bit system What is the installation process? Improve this question. Seyed Mohammad Seyed Mohammad 3, 7 7 gold badges 29 29 silver badges 40 40 bronze badges.
Add a comment. Active Oldest Votes. Its perhaps better to consider downloading ubuntu kernels from specific Ubuntu versions For example - 2. Improve this answer.
0コメント