“UbuntuHelp:Kernel/Compile”的版本间的差异
来自Ubuntu中文
小 （New page: {{From|https://help.ubuntu.com/community/Kernel/Compile}} {{Languages|php5}} == Disclaimer == '''Building and using a custom kernel will make it very difficult to get support for your s...） |
小 |
||
| 第35行： | 第35行： | ||
<pre><nowiki> | <pre><nowiki> | ||
sudo apt-get install linux-kernel-devel fakeroot | sudo apt-get install linux-kernel-devel fakeroot | ||
| − | </nowiki></ | + | </nowiki></pre> |
This will install the compiler related packages and kernel packaging tools. It will also install the git-core package, which is the best way to interact with the Ubuntu kernel source. | This will install the compiler related packages and kernel packaging tools. It will also install the git-core package, which is the best way to interact with the Ubuntu kernel source. | ||
| 第50行： | 第50行： | ||
apt-get source linux-image-generic | apt-get source linux-image-generic | ||
apt-get build-dep linux-image-generic | apt-get build-dep linux-image-generic | ||
| − | </nowiki></ | + | </nowiki></pre> |
Another way is to simply: | Another way is to simply: | ||
| 第56行： | 第56行： | ||
<pre><nowiki> | <pre><nowiki> | ||
sudo apt-get install linux-source | sudo apt-get install linux-source | ||
| − | </nowiki></ | + | </nowiki></pre> |
However, that will almost always be out of date. Using git allows you to always stay in sync with the latest Ubuntu kernel source, and using the package source allows you to keep as close as possible to an official release with any private changes. | However, that will almost always be out of date. Using git allows you to always stay in sync with the latest Ubuntu kernel source, and using the package source allows you to keep as close as possible to an official release with any private changes. | ||
| 第79行： | 第79行： | ||
-rw-r--r-- 1 me me 1519 Jun 12 14:59 config.server | -rw-r--r-- 1 me me 1519 Jun 12 14:59 config.server | ||
-rw-r--r-- 1 me me 1867 Jun 12 14:59 config.server-bigiron | -rw-r--r-- 1 me me 1867 Jun 12 14:59 config.server-bigiron | ||
| − | </nowiki></ | + | </nowiki></pre> |
If you need to change a config option, simply modify the file that contains the option. If you modify just the ''config'' file, it will affect all targets for this architecture. If you modify one of the target files, it only affects that target. | If you need to change a config option, simply modify the file that contains the option. If you modify just the ''config'' file, it will affect all targets for this architecture. If you modify one of the target files, it only affects that target. | ||
| 第87行： | 第87行： | ||
<pre><nowiki> | <pre><nowiki> | ||
debian/rules updateconfigs | debian/rules updateconfigs | ||
| − | </nowiki></ | + | </nowiki></pre> |
If you just want to update one architecture, run: | If you just want to update one architecture, run: | ||
| 第93行： | 第93行： | ||
<pre><nowiki> | <pre><nowiki> | ||
debian/bin/oldconfig ARCH | debian/bin/oldconfig ARCH | ||
| − | </nowiki></ | + | </nowiki></pre> |
| 第104行： | 第104行： | ||
<pre><nowiki> | <pre><nowiki> | ||
AUTOBUILD=1 fakeroot debian/rules binary-debs | AUTOBUILD=1 fakeroot debian/rules binary-debs | ||
| − | </nowiki></ | + | </nowiki></pre> |
The ''AUTOBUILD'' environment variable triggers special features in the kernel build. First, it skips normal ABI checks (ABI is the binary compatibility). It can do this because it also creates a unique ABI ID. If you used a git repo, this unique ID is generated from the git HEAD SHA. If not, it is generated from the uuidgen program (which means every time you execute the debian/rules build, the UUID will be different!). Your packages will be named using this ID. | The ''AUTOBUILD'' environment variable triggers special features in the kernel build. First, it skips normal ABI checks (ABI is the binary compatibility). It can do this because it also creates a unique ABI ID. If you used a git repo, this unique ID is generated from the git HEAD SHA. If not, it is generated from the uuidgen program (which means every time you execute the debian/rules build, the UUID will be different!). Your packages will be named using this ID. | ||
| 第112行： | 第112行： | ||
<pre><nowiki> | <pre><nowiki> | ||
AUTOBUILD=1 fakeroot debian/rules binary-debs flavours=k7 | AUTOBUILD=1 fakeroot debian/rules binary-debs flavours=k7 | ||
| − | </nowiki></ | + | </nowiki></pre> |
This will only build the AMD k7 variant of the i386 architecture. | This will only build the AMD k7 variant of the i386 architecture. | ||
| 第125行： | 第125行： | ||
sudo dpkg -i linux-image-2.6.17-2-ef427c-k7_2.6.17-2.2_i386.deb | sudo dpkg -i linux-image-2.6.17-2-ef427c-k7_2.6.17-2.2_i386.deb | ||
sudo dpkg -i linux-headers--2.6.17-2-ef427c-k7_2.6.17-2.2_i386.deb | sudo dpkg -i linux-headers--2.6.17-2-ef427c-k7_2.6.17-2.2_i386.deb | ||
| − | </nowiki></ | + | </nowiki></pre> |
If you use modules from ''linux-restricted-modules'', you will need to recompile this against your new linux-headers package. | If you use modules from ''linux-restricted-modules'', you will need to recompile this against your new linux-headers package. | ||
| 第139行： | 第139行： | ||
<pre><nowiki> | <pre><nowiki> | ||
sudo apt-get source linux-restricted-modules-2.6.20-15-lowlatency | sudo apt-get source linux-restricted-modules-2.6.20-15-lowlatency | ||
| − | </nowiki></ | + | </nowiki></pre> |
and satisfy it's build dependencies | and satisfy it's build dependencies | ||
| 第145行： | 第145行： | ||
<pre><nowiki> | <pre><nowiki> | ||
sudo apt-get build-dep linux-restricted-modules-2.6.20-15-lowlatency | sudo apt-get build-dep linux-restricted-modules-2.6.20-15-lowlatency | ||
| − | </nowiki></ | + | </nowiki></pre> |
and unpack it | and unpack it | ||
| 第151行： | 第151行： | ||
<pre><nowiki> | <pre><nowiki> | ||
dpkg-source -x linux-restricted-modules-2.6.20_2.6.20.5-15.20.dsc | dpkg-source -x linux-restricted-modules-2.6.20_2.6.20.5-15.20.dsc | ||
| − | </nowiki></ | + | </nowiki></pre> |
Then you need to edit the debian/rules file, to add the abi-suffix generated when you built your kernel package. Look for the lines | Then you need to edit the debian/rules file, to add the abi-suffix generated when you built your kernel package. Look for the lines | ||
| 第166行： | 第166行： | ||
cd linux-restricted-modules-2.6.20-2.6.20.5 | cd linux-restricted-modules-2.6.20-2.6.20.5 | ||
debuild -rfakeroot | debuild -rfakeroot | ||
| − | </nowiki></ | + | </nowiki></pre> |
=== Other === | === Other === | ||
2007年5月13日 (日) 12:43的版本
目录
- 1 Disclaimer
- 1.1 Reasons for compiling a custom kernel
- 1.2 Reasons for NOT compiling a custom kernel
- 1.3 What you'll need
- 1.4 How to get the kernel source
- 1.5 Modifying the source for your needs
- 1.6 Building the kernel
- 1.7 When it's done
- 1.8 Rebuilding linux-restricted-modules
- 1.9 Other
- 1.10 External information
Disclaimer
Building and using a custom kernel will make it very difficult to get support for your system. You will not be allowed to file bugs on the custom-built kernel (if you do, they will be Rejected without explanation).
If you have a commercial support contract with Ubuntu/Canonical, this will void such support.
Also note that this page describes how to do things for the Edgy (2.6.17) kernel and newer! Until this kernel source, we did not have any mechanisms in place that would allow people to build their own kernels easily. This was intentional.
This page does NOT describe how to build stock kernels from kernel.org. This is how to rebuild the actual Ubuntu kernel source.
Reasons for compiling a custom kernel
- You are a kernel developer.
- You need the kernel compiled in a special way, that the official kernel is not compiled in (for example, with some experimental feature enabled).
- You are attempting to debug a problem for which you have filed or will file a bug report on the stock Ubuntu kernel.
- You have hardware for which the Ubuntu kernel doesn't include support
Reasons for NOT compiling a custom kernel
- You merely need to compile a special driver. For this, you only need to install the linux-headers packages.
- You have no idea what you are doing, and if you break something, you'll need help fixing it. If you hose your box, reinstall. Don't bother asking for help.
- You got to this page by mistake, but checked it out because it looked interesting. Believe me, this isn't interesting at all :)
What you'll need
To start, you will need to install a few packages.
sudo apt-get install linux-kernel-devel fakeroot
This will install the compiler related packages and kernel packaging tools. It will also install the git-core package, which is the best way to interact with the Ubuntu kernel source.
samtygier: I think you also need the package m4
How to get the kernel source
There are a few ways to obtain the Ubuntu kernel source. Some prefer to use git. Detailed instructions for using git can be found in the Kernel Git Guide.
The simplest was, useful to those who want to rebuild the standard Ubuntu packages with additional patches is:
apt-get source linux-image-generic apt-get build-dep linux-image-generic
Another way is to simply:
sudo apt-get install linux-source
However, that will almost always be out of date. Using git allows you to always stay in sync with the latest Ubuntu kernel source, and using the package source allows you to keep as close as possible to an official release with any private changes.
It seems that it is possible to use this information on 6.06 by running something similar to `apt-get source linux-image-2.6.15-26-386', which will give you kernel source along with the debian folder needed for this guide. However, I'm just a user, proceed with caution.
-- Simon80 DateTime(2006-07-17T02:09:06Z)
After testing it, I must warn you that this documentation doesn't work if you choose the sudo apt-get install linux-source-2.6.17 way.
-- OuattaraAziz DateTime(2007-02-17T21:02:06Z)
Modifying the source for your needs
For most people, simply modifying the configs is enough. If you need to install a patch, read the instructions from the patch provider for how to apply.
The stock Ubuntu configs are located in debian/config/ARCH/ where ARCH is the architecture you are building for. In this directory are several files. The config file is the base for all targets in that architecture. Then there are several config.FLAVOUR files that contain options specific to that target. For example, here are the files for 2.6.17, i386:
$ ls -l debian/config/i386/ total 88 -rw-r--r-- 1 me me 62737 Jun 14 18:31 config -rw-r--r-- 1 me me 1859 Jun 12 14:59 config.386 -rw-r--r-- 1 me me 1394 Jun 12 14:59 config.686 -rw-r--r-- 1 me me 1420 Jun 12 14:59 config.k7 -rw-r--r-- 1 me me 1519 Jun 12 14:59 config.server -rw-r--r-- 1 me me 1867 Jun 12 14:59 config.server-bigiron
If you need to change a config option, simply modify the file that contains the option. If you modify just the config file, it will affect all targets for this architecture. If you modify one of the target files, it only affects that target.
After applying a patch, or adjusting the configs, it is always best to regenerate the config files to ensure they are consistent. There is a helper command for this. To regenerate all architectures run:
debian/rules updateconfigs
If you just want to update one architecture, run:
debian/bin/oldconfig ARCH
Building the kernel
To build the kernel(s) is very simple. Depending on your needs, you may want to build all the kernel targets, or just one specific to your system. However, you also want to make sure that you do not clash with the stock kernels.
Use this command to build all targets for the architecture you are buidling on:
AUTOBUILD=1 fakeroot debian/rules binary-debs
The AUTOBUILD environment variable triggers special features in the kernel build. First, it skips normal ABI checks (ABI is the binary compatibility). It can do this because it also creates a unique ABI ID. If you used a git repo, this unique ID is generated from the git HEAD SHA. If not, it is generated from the uuidgen program (which means every time you execute the debian/rules build, the UUID will be different!). Your packages will be named using this ID.
To build a specific target, use this command:
AUTOBUILD=1 fakeroot debian/rules binary-debs flavours=k7
This will only build the AMD k7 variant of the i386 architecture.
The debs are placed in ubuntu-2.6/debian/build.
When it's done
Now that the build is complete, you can install the generated debs using dpkg:
sudo dpkg -i linux-image-2.6.17-2-ef427c-k7_2.6.17-2.2_i386.deb sudo dpkg -i linux-headers--2.6.17-2-ef427c-k7_2.6.17-2.2_i386.deb
If you use modules from linux-restricted-modules, you will need to recompile this against your new linux-headers package.
Rebuilding linux-restricted-modules
(These instruction are taken from an example using a different kernel to that used in the previous examples))
You will need to install all the linux-headers packages that you build in the previous stage.
Then, download the source to linux-restricted-modules
sudo apt-get source linux-restricted-modules-2.6.20-15-lowlatency
and satisfy it's build dependencies
sudo apt-get build-dep linux-restricted-modules-2.6.20-15-lowlatency
and unpack it
dpkg-source -x linux-restricted-modules-2.6.20_2.6.20.5-15.20.dsc
Then you need to edit the debian/rules file, to add the abi-suffix generated when you built your kernel package. Look for the lines
|| Old text || New Text || || # kernel || # kernel || || abi_version == 15 || abi_version == 15-2be ||
but where 2be is the abi suffix generated for your kernel packages.
Finally build your packages
cd linux-restricted-modules-2.6.20-2.6.20.5 debuild -rfakeroot
Other
How to compile a kernel module
External information
http://www.howtoforge.com/kernel_compilation_ubuntu Compile a kernel from kernel.org source in Ubuntu
CategoryKernel CategoryDocumentation
