Commit 2af238e455ef5fd31c2f7a06c2db3f13d843b9bf
Committed by
Sam Ravnborg
1 parent
80a7d1d991
Exists in
master
and in
20 other branches
kbuild: make *config usage docs
Create a kconfig user assistance guide, with a few tips and hints about using menuconfig, xconfig, and gconfig. Mostly contains user interface, environment variables, and search topics, along with mini.config/custom.config usage. Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com> Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
Showing 3 changed files with 210 additions and 12 deletions Inline Diff
Documentation/kbuild/00-INDEX
1 | 00-INDEX | 1 | 00-INDEX |
2 | - this file: info on the kernel build process | 2 | - this file: info on the kernel build process |
3 | kconfig-language.txt | 3 | kconfig-language.txt |
4 | - specification of Config Language, the language in Kconfig files | 4 | - specification of Config Language, the language in Kconfig files |
5 | makefiles.txt | 5 | makefiles.txt |
6 | - developer information for linux kernel makefiles | 6 | - developer information for linux kernel makefiles |
7 | kconfig.txt | ||
8 | - usage help for make *config | ||
7 | modules.txt | 9 | modules.txt |
8 | - how to build modules and to install them | 10 | - how to build modules and to install them |
9 | 11 |
Documentation/kbuild/kconfig.txt
File was created | 1 | This file contains some assistance for using "make *config". | |
2 | |||
3 | Use "make help" to list all of the possible configuration targets. | ||
4 | |||
5 | The xconfig ('qconf') and menuconfig ('mconf') programs also | ||
6 | have embedded help text. Be sure to check it for navigation, | ||
7 | search, and other general help text. | ||
8 | |||
9 | ====================================================================== | ||
10 | General | ||
11 | -------------------------------------------------- | ||
12 | |||
13 | New kernel releases often introduce new config symbols. Often more | ||
14 | important, new kernel releases may rename config symbols. When | ||
15 | this happens, using a previously working .config file and running | ||
16 | "make oldconfig" won't necessarily produce a working new kernel | ||
17 | for you, so you may find that you need to see what NEW kernel | ||
18 | symbols have been introduced. | ||
19 | |||
20 | To see a list of new config symbols when using "make oldconfig", use | ||
21 | |||
22 | cp user/some/old.config .config | ||
23 | yes "" | make oldconfig >conf.new | ||
24 | |||
25 | and the config program will list as (NEW) any new symbols that have | ||
26 | unknown values. Of course, the .config file is also updated with | ||
27 | new (default) values, so you can use: | ||
28 | |||
29 | grep "(NEW)" conf.new | ||
30 | |||
31 | to see the new config symbols or you can 'diff' the previous and | ||
32 | new .config files to see the differences: | ||
33 | |||
34 | diff .config.old .config | less | ||
35 | |||
36 | (Yes, we need something better here.) | ||
37 | |||
38 | |||
39 | ====================================================================== | ||
40 | menuconfig | ||
41 | -------------------------------------------------- | ||
42 | |||
43 | SEARCHING for CONFIG symbols | ||
44 | |||
45 | Searching in menuconfig: | ||
46 | |||
47 | The Search function searches for kernel configuration symbol | ||
48 | names, so you have to know something close to what you are | ||
49 | looking for. | ||
50 | |||
51 | Example: | ||
52 | /hotplug | ||
53 | This lists all config symbols that contain "hotplug", | ||
54 | e.g., HOTPLUG, HOTPLUG_CPU, MEMORY_HOTPLUG. | ||
55 | |||
56 | For search help, enter / followed TAB-TAB-TAB (to highlight | ||
57 | <Help>) and Enter. This will tell you that you can also use | ||
58 | regular expressions (regexes) in the search string, so if you | ||
59 | are not interested in MEMORY_HOTPLUG, you could try | ||
60 | |||
61 | /^hotplug | ||
62 | |||
63 | |||
64 | ______________________________________________________________________ | ||
65 | Color Themes for 'menuconfig' | ||
66 | |||
67 | It is possible to select different color themes using the variable | ||
68 | MENUCONFIG_COLOR. To select a theme use: | ||
69 | |||
70 | make MENUCONFIG_COLOR=<theme> menuconfig | ||
71 | |||
72 | Available themes are: | ||
73 | mono => selects colors suitable for monochrome displays | ||
74 | blackbg => selects a color scheme with black background | ||
75 | classic => theme with blue background. The classic look | ||
76 | bluetitle => a LCD friendly version of classic. (default) | ||
77 | |||
78 | ______________________________________________________________________ | ||
79 | Environment variables in 'menuconfig' | ||
80 | |||
81 | KCONFIG_ALLCONFIG | ||
82 | -------------------------------------------------- | ||
83 | (partially based on lkml email from/by Rob Landley, re: miniconfig) | ||
84 | -------------------------------------------------- | ||
85 | The allyesconfig/allmodconfig/allnoconfig/randconfig variants can | ||
86 | also use the environment variable KCONFIG_ALLCONFIG as a flag or a | ||
87 | filename that contains config symbols that the user requires to be | ||
88 | set to a specific value. If KCONFIG_ALLCONFIG is used without a | ||
89 | filename, "make *config" checks for a file named | ||
90 | "all{yes/mod/no/random}.config" (corresponding to the *config command | ||
91 | that was used) for symbol values that are to be forced. If this file | ||
92 | is not found, it checks for a file named "all.config" to contain forced | ||
93 | values. | ||
94 | |||
95 | This enables you to create "miniature" config (miniconfig) or custom | ||
96 | config files containing just the config symbols that you are interested | ||
97 | in. Then the kernel config system generates the full .config file, | ||
98 | including dependencies of your miniconfig file, based on the miniconfig | ||
99 | file. | ||
100 | |||
101 | This 'KCONFIG_ALLCONFIG' file is a config file which contains | ||
102 | (usually a subset of all) preset config symbols. These variable | ||
103 | settings are still subject to normal dependency checks. | ||
104 | |||
105 | Examples: | ||
106 | KCONFIG_ALLCONFIG=custom-notebook.config make allnoconfig | ||
107 | or | ||
108 | KCONFIG_ALLCONFIG=mini.config make allnoconfig | ||
109 | or | ||
110 | make KCONFIG_ALLCONFIG=mini.config allnoconfig | ||
111 | |||
112 | These examples will disable most options (allnoconfig) but enable or | ||
113 | disable the options that are explicitly listed in the specified | ||
114 | mini-config files. | ||
115 | |||
116 | KCONFIG_NOSILENTUPDATE | ||
117 | -------------------------------------------------- | ||
118 | If this variable has a non-blank value, it prevents silent kernel | ||
119 | config udpates (requires explicit updates). | ||
120 | |||
121 | KCONFIG_CONFIG | ||
122 | -------------------------------------------------- | ||
123 | This environment variable can be used to specify a default kernel config | ||
124 | file name to override the default name of ".config". | ||
125 | |||
126 | KCONFIG_OVERWRITECONFIG | ||
127 | -------------------------------------------------- | ||
128 | If you set KCONFIG_OVERWRITECONFIG in the environment, Kconfig will not | ||
129 | break symlinks when .config is a symlink to somewhere else. | ||
130 | |||
131 | KCONFIG_NOTIMESTAMP | ||
132 | -------------------------------------------------- | ||
133 | If this environment variable exists and is non-null, the timestamp line | ||
134 | in generated .config files is omitted. | ||
135 | |||
136 | KCONFIG_AUTOCONFIG | ||
137 | -------------------------------------------------- | ||
138 | This environment variable can be set to specify the path & name of the | ||
139 | "auto.conf" file. Its default value is "include/config/auto.conf". | ||
140 | |||
141 | KCONFIG_AUTOHEADER | ||
142 | -------------------------------------------------- | ||
143 | This environment variable can be set to specify the path & name of the | ||
144 | "autoconf.h" (header) file. Its default value is "include/linux/autoconf.h". | ||
145 | |||
146 | ______________________________________________________________________ | ||
147 | menuconfig User Interface Options | ||
148 | ---------------------------------------------------------------------- | ||
149 | MENUCONFIG_MODE | ||
150 | -------------------------------------------------- | ||
151 | This mode shows all sub-menus in one large tree. | ||
152 | |||
153 | Example: | ||
154 | MENUCONFIG_MODE=single_menu make menuconfig | ||
155 | |||
156 | ====================================================================== | ||
157 | xconfig | ||
158 | -------------------------------------------------- | ||
159 | |||
160 | Searching in xconfig: | ||
161 | |||
162 | The Search function searches for kernel configuration symbol | ||
163 | names, so you have to know something close to what you are | ||
164 | looking for. | ||
165 | |||
166 | Example: | ||
167 | Ctrl-F hotplug | ||
168 | or | ||
169 | Menu: File, Search, hotplug | ||
170 | |||
171 | lists all config symbol entries that contain "hotplug" in | ||
172 | the symbol name. In this Search dialog, you may change the | ||
173 | config setting for any of the entries that are not grayed out. | ||
174 | You can also enter a different search string without having | ||
175 | to return to the main menu. | ||
176 | |||
177 | |||
178 | ====================================================================== | ||
179 | gconfig | ||
180 | -------------------------------------------------- | ||
181 | |||
182 | Searching in gconfig: | ||
183 | |||
184 | None (gconfig isn't maintained as well as xconfig or menuconfig); | ||
185 | however, gconfig does have a few more viewing choices than | ||
186 | xconfig does. | ||
187 | |||
188 | ### | ||
189 |
README
1 | Linux kernel release 2.6.xx <http://kernel.org/> | 1 | Linux kernel release 2.6.xx <http://kernel.org/> |
2 | 2 | ||
3 | These are the release notes for Linux version 2.6. Read them carefully, | 3 | These are the release notes for Linux version 2.6. Read them carefully, |
4 | as they tell you what this is all about, explain how to install the | 4 | as they tell you what this is all about, explain how to install the |
5 | kernel, and what to do if something goes wrong. | 5 | kernel, and what to do if something goes wrong. |
6 | 6 | ||
7 | WHAT IS LINUX? | 7 | WHAT IS LINUX? |
8 | 8 | ||
9 | Linux is a clone of the operating system Unix, written from scratch by | 9 | Linux is a clone of the operating system Unix, written from scratch by |
10 | Linus Torvalds with assistance from a loosely-knit team of hackers across | 10 | Linus Torvalds with assistance from a loosely-knit team of hackers across |
11 | the Net. It aims towards POSIX and Single UNIX Specification compliance. | 11 | the Net. It aims towards POSIX and Single UNIX Specification compliance. |
12 | 12 | ||
13 | It has all the features you would expect in a modern fully-fledged Unix, | 13 | It has all the features you would expect in a modern fully-fledged Unix, |
14 | including true multitasking, virtual memory, shared libraries, demand | 14 | including true multitasking, virtual memory, shared libraries, demand |
15 | loading, shared copy-on-write executables, proper memory management, | 15 | loading, shared copy-on-write executables, proper memory management, |
16 | and multistack networking including IPv4 and IPv6. | 16 | and multistack networking including IPv4 and IPv6. |
17 | 17 | ||
18 | It is distributed under the GNU General Public License - see the | 18 | It is distributed under the GNU General Public License - see the |
19 | accompanying COPYING file for more details. | 19 | accompanying COPYING file for more details. |
20 | 20 | ||
21 | ON WHAT HARDWARE DOES IT RUN? | 21 | ON WHAT HARDWARE DOES IT RUN? |
22 | 22 | ||
23 | Although originally developed first for 32-bit x86-based PCs (386 or higher), | 23 | Although originally developed first for 32-bit x86-based PCs (386 or higher), |
24 | today Linux also runs on (at least) the Compaq Alpha AXP, Sun SPARC and | 24 | today Linux also runs on (at least) the Compaq Alpha AXP, Sun SPARC and |
25 | UltraSPARC, Motorola 68000, PowerPC, PowerPC64, ARM, Hitachi SuperH, Cell, | 25 | UltraSPARC, Motorola 68000, PowerPC, PowerPC64, ARM, Hitachi SuperH, Cell, |
26 | IBM S/390, MIPS, HP PA-RISC, Intel IA-64, DEC VAX, AMD x86-64, AXIS CRIS, | 26 | IBM S/390, MIPS, HP PA-RISC, Intel IA-64, DEC VAX, AMD x86-64, AXIS CRIS, |
27 | Xtensa, AVR32 and Renesas M32R architectures. | 27 | Xtensa, AVR32 and Renesas M32R architectures. |
28 | 28 | ||
29 | Linux is easily portable to most general-purpose 32- or 64-bit architectures | 29 | Linux is easily portable to most general-purpose 32- or 64-bit architectures |
30 | as long as they have a paged memory management unit (PMMU) and a port of the | 30 | as long as they have a paged memory management unit (PMMU) and a port of the |
31 | GNU C compiler (gcc) (part of The GNU Compiler Collection, GCC). Linux has | 31 | GNU C compiler (gcc) (part of The GNU Compiler Collection, GCC). Linux has |
32 | also been ported to a number of architectures without a PMMU, although | 32 | also been ported to a number of architectures without a PMMU, although |
33 | functionality is then obviously somewhat limited. | 33 | functionality is then obviously somewhat limited. |
34 | Linux has also been ported to itself. You can now run the kernel as a | 34 | Linux has also been ported to itself. You can now run the kernel as a |
35 | userspace application - this is called UserMode Linux (UML). | 35 | userspace application - this is called UserMode Linux (UML). |
36 | 36 | ||
37 | DOCUMENTATION: | 37 | DOCUMENTATION: |
38 | 38 | ||
39 | - There is a lot of documentation available both in electronic form on | 39 | - There is a lot of documentation available both in electronic form on |
40 | the Internet and in books, both Linux-specific and pertaining to | 40 | the Internet and in books, both Linux-specific and pertaining to |
41 | general UNIX questions. I'd recommend looking into the documentation | 41 | general UNIX questions. I'd recommend looking into the documentation |
42 | subdirectories on any Linux FTP site for the LDP (Linux Documentation | 42 | subdirectories on any Linux FTP site for the LDP (Linux Documentation |
43 | Project) books. This README is not meant to be documentation on the | 43 | Project) books. This README is not meant to be documentation on the |
44 | system: there are much better sources available. | 44 | system: there are much better sources available. |
45 | 45 | ||
46 | - There are various README files in the Documentation/ subdirectory: | 46 | - There are various README files in the Documentation/ subdirectory: |
47 | these typically contain kernel-specific installation notes for some | 47 | these typically contain kernel-specific installation notes for some |
48 | drivers for example. See Documentation/00-INDEX for a list of what | 48 | drivers for example. See Documentation/00-INDEX for a list of what |
49 | is contained in each file. Please read the Changes file, as it | 49 | is contained in each file. Please read the Changes file, as it |
50 | contains information about the problems, which may result by upgrading | 50 | contains information about the problems, which may result by upgrading |
51 | your kernel. | 51 | your kernel. |
52 | 52 | ||
53 | - The Documentation/DocBook/ subdirectory contains several guides for | 53 | - The Documentation/DocBook/ subdirectory contains several guides for |
54 | kernel developers and users. These guides can be rendered in a | 54 | kernel developers and users. These guides can be rendered in a |
55 | number of formats: PostScript (.ps), PDF, and HTML, among others. | 55 | number of formats: PostScript (.ps), PDF, HTML, & man-pages, among others. |
56 | After installation, "make psdocs", "make pdfdocs", or "make htmldocs" | 56 | After installation, "make psdocs", "make pdfdocs", "make htmldocs", |
57 | will render the documentation in the requested format. | 57 | or "make mandocs" will render the documentation in the requested format. |
58 | 58 | ||
59 | INSTALLING the kernel: | 59 | INSTALLING the kernel source: |
60 | 60 | ||
61 | - If you install the full sources, put the kernel tarball in a | 61 | - If you install the full sources, put the kernel tarball in a |
62 | directory where you have permissions (eg. your home directory) and | 62 | directory where you have permissions (eg. your home directory) and |
63 | unpack it: | 63 | unpack it: |
64 | 64 | ||
65 | gzip -cd linux-2.6.XX.tar.gz | tar xvf - | 65 | gzip -cd linux-2.6.XX.tar.gz | tar xvf - |
66 | 66 | ||
67 | or | 67 | or |
68 | bzip2 -dc linux-2.6.XX.tar.bz2 | tar xvf - | 68 | bzip2 -dc linux-2.6.XX.tar.bz2 | tar xvf - |
69 | 69 | ||
70 | 70 | ||
71 | Replace "XX" with the version number of the latest kernel. | 71 | Replace "XX" with the version number of the latest kernel. |
72 | 72 | ||
73 | Do NOT use the /usr/src/linux area! This area has a (usually | 73 | Do NOT use the /usr/src/linux area! This area has a (usually |
74 | incomplete) set of kernel headers that are used by the library header | 74 | incomplete) set of kernel headers that are used by the library header |
75 | files. They should match the library, and not get messed up by | 75 | files. They should match the library, and not get messed up by |
76 | whatever the kernel-du-jour happens to be. | 76 | whatever the kernel-du-jour happens to be. |
77 | 77 | ||
78 | - You can also upgrade between 2.6.xx releases by patching. Patches are | 78 | - You can also upgrade between 2.6.xx releases by patching. Patches are |
79 | distributed in the traditional gzip and the newer bzip2 format. To | 79 | distributed in the traditional gzip and the newer bzip2 format. To |
80 | install by patching, get all the newer patch files, enter the | 80 | install by patching, get all the newer patch files, enter the |
81 | top level directory of the kernel source (linux-2.6.xx) and execute: | 81 | top level directory of the kernel source (linux-2.6.xx) and execute: |
82 | 82 | ||
83 | gzip -cd ../patch-2.6.xx.gz | patch -p1 | 83 | gzip -cd ../patch-2.6.xx.gz | patch -p1 |
84 | 84 | ||
85 | or | 85 | or |
86 | bzip2 -dc ../patch-2.6.xx.bz2 | patch -p1 | 86 | bzip2 -dc ../patch-2.6.xx.bz2 | patch -p1 |
87 | 87 | ||
88 | (repeat xx for all versions bigger than the version of your current | 88 | (repeat xx for all versions bigger than the version of your current |
89 | source tree, _in_order_) and you should be ok. You may want to remove | 89 | source tree, _in_order_) and you should be ok. You may want to remove |
90 | the backup files (xxx~ or xxx.orig), and make sure that there are no | 90 | the backup files (xxx~ or xxx.orig), and make sure that there are no |
91 | failed patches (xxx# or xxx.rej). If there are, either you or me has | 91 | failed patches (xxx# or xxx.rej). If there are, either you or me has |
92 | made a mistake. | 92 | made a mistake. |
93 | 93 | ||
94 | Unlike patches for the 2.6.x kernels, patches for the 2.6.x.y kernels | 94 | Unlike patches for the 2.6.x kernels, patches for the 2.6.x.y kernels |
95 | (also known as the -stable kernels) are not incremental but instead apply | 95 | (also known as the -stable kernels) are not incremental but instead apply |
96 | directly to the base 2.6.x kernel. Please read | 96 | directly to the base 2.6.x kernel. Please read |
97 | Documentation/applying-patches.txt for more information. | 97 | Documentation/applying-patches.txt for more information. |
98 | 98 | ||
99 | Alternatively, the script patch-kernel can be used to automate this | 99 | Alternatively, the script patch-kernel can be used to automate this |
100 | process. It determines the current kernel version and applies any | 100 | process. It determines the current kernel version and applies any |
101 | patches found. | 101 | patches found. |
102 | 102 | ||
103 | linux/scripts/patch-kernel linux | 103 | linux/scripts/patch-kernel linux |
104 | 104 | ||
105 | The first argument in the command above is the location of the | 105 | The first argument in the command above is the location of the |
106 | kernel source. Patches are applied from the current directory, but | 106 | kernel source. Patches are applied from the current directory, but |
107 | an alternative directory can be specified as the second argument. | 107 | an alternative directory can be specified as the second argument. |
108 | 108 | ||
109 | - If you are upgrading between releases using the stable series patches | 109 | - If you are upgrading between releases using the stable series patches |
110 | (for example, patch-2.6.xx.y), note that these "dot-releases" are | 110 | (for example, patch-2.6.xx.y), note that these "dot-releases" are |
111 | not incremental and must be applied to the 2.6.xx base tree. For | 111 | not incremental and must be applied to the 2.6.xx base tree. For |
112 | example, if your base kernel is 2.6.12 and you want to apply the | 112 | example, if your base kernel is 2.6.12 and you want to apply the |
113 | 2.6.12.3 patch, you do not and indeed must not first apply the | 113 | 2.6.12.3 patch, you do not and indeed must not first apply the |
114 | 2.6.12.1 and 2.6.12.2 patches. Similarly, if you are running kernel | 114 | 2.6.12.1 and 2.6.12.2 patches. Similarly, if you are running kernel |
115 | version 2.6.12.2 and want to jump to 2.6.12.3, you must first | 115 | version 2.6.12.2 and want to jump to 2.6.12.3, you must first |
116 | reverse the 2.6.12.2 patch (that is, patch -R) _before_ applying | 116 | reverse the 2.6.12.2 patch (that is, patch -R) _before_ applying |
117 | the 2.6.12.3 patch. | 117 | the 2.6.12.3 patch. |
118 | You can read more on this in Documentation/applying-patches.txt | 118 | You can read more on this in Documentation/applying-patches.txt |
119 | 119 | ||
120 | - Make sure you have no stale .o files and dependencies lying around: | 120 | - Make sure you have no stale .o files and dependencies lying around: |
121 | 121 | ||
122 | cd linux | 122 | cd linux |
123 | make mrproper | 123 | make mrproper |
124 | 124 | ||
125 | You should now have the sources correctly installed. | 125 | You should now have the sources correctly installed. |
126 | 126 | ||
127 | SOFTWARE REQUIREMENTS | 127 | SOFTWARE REQUIREMENTS |
128 | 128 | ||
129 | Compiling and running the 2.6.xx kernels requires up-to-date | 129 | Compiling and running the 2.6.xx kernels requires up-to-date |
130 | versions of various software packages. Consult | 130 | versions of various software packages. Consult |
131 | Documentation/Changes for the minimum version numbers required | 131 | Documentation/Changes for the minimum version numbers required |
132 | and how to get updates for these packages. Beware that using | 132 | and how to get updates for these packages. Beware that using |
133 | excessively old versions of these packages can cause indirect | 133 | excessively old versions of these packages can cause indirect |
134 | errors that are very difficult to track down, so don't assume that | 134 | errors that are very difficult to track down, so don't assume that |
135 | you can just update packages when obvious problems arise during | 135 | you can just update packages when obvious problems arise during |
136 | build or operation. | 136 | build or operation. |
137 | 137 | ||
138 | BUILD directory for the kernel: | 138 | BUILD directory for the kernel: |
139 | 139 | ||
140 | When compiling the kernel all output files will per default be | 140 | When compiling the kernel all output files will per default be |
141 | stored together with the kernel source code. | 141 | stored together with the kernel source code. |
142 | Using the option "make O=output/dir" allow you to specify an alternate | 142 | Using the option "make O=output/dir" allow you to specify an alternate |
143 | place for the output files (including .config). | 143 | place for the output files (including .config). |
144 | Example: | 144 | Example: |
145 | kernel source code: /usr/src/linux-2.6.N | 145 | kernel source code: /usr/src/linux-2.6.N |
146 | build directory: /home/name/build/kernel | 146 | build directory: /home/name/build/kernel |
147 | 147 | ||
148 | To configure and build the kernel use: | 148 | To configure and build the kernel use: |
149 | cd /usr/src/linux-2.6.N | 149 | cd /usr/src/linux-2.6.N |
150 | make O=/home/name/build/kernel menuconfig | 150 | make O=/home/name/build/kernel menuconfig |
151 | make O=/home/name/build/kernel | 151 | make O=/home/name/build/kernel |
152 | sudo make O=/home/name/build/kernel modules_install install | 152 | sudo make O=/home/name/build/kernel modules_install install |
153 | 153 | ||
154 | Please note: If the 'O=output/dir' option is used then it must be | 154 | Please note: If the 'O=output/dir' option is used then it must be |
155 | used for all invocations of make. | 155 | used for all invocations of make. |
156 | 156 | ||
157 | CONFIGURING the kernel: | 157 | CONFIGURING the kernel: |
158 | 158 | ||
159 | Do not skip this step even if you are only upgrading one minor | 159 | Do not skip this step even if you are only upgrading one minor |
160 | version. New configuration options are added in each release, and | 160 | version. New configuration options are added in each release, and |
161 | odd problems will turn up if the configuration files are not set up | 161 | odd problems will turn up if the configuration files are not set up |
162 | as expected. If you want to carry your existing configuration to a | 162 | as expected. If you want to carry your existing configuration to a |
163 | new version with minimal work, use "make oldconfig", which will | 163 | new version with minimal work, use "make oldconfig", which will |
164 | only ask you for the answers to new questions. | 164 | only ask you for the answers to new questions. |
165 | 165 | ||
166 | - Alternate configuration commands are: | 166 | - Alternate configuration commands are: |
167 | "make config" Plain text interface. | 167 | "make config" Plain text interface. |
168 | "make menuconfig" Text based color menus, radiolists & dialogs. | 168 | "make menuconfig" Text based color menus, radiolists & dialogs. |
169 | "make xconfig" X windows (Qt) based configuration tool. | 169 | "make xconfig" X windows (Qt) based configuration tool. |
170 | "make gconfig" X windows (Gtk) based configuration tool. | 170 | "make gconfig" X windows (Gtk) based configuration tool. |
171 | "make oldconfig" Default all questions based on the contents of | 171 | "make oldconfig" Default all questions based on the contents of |
172 | your existing ./.config file and asking about | 172 | your existing ./.config file and asking about |
173 | new config symbols. | 173 | new config symbols. |
174 | "make silentoldconfig" | 174 | "make silentoldconfig" |
175 | Like above, but avoids cluttering the screen | 175 | Like above, but avoids cluttering the screen |
176 | with questions already answered. | 176 | with questions already answered. |
177 | "make defconfig" Create a ./.config file by using the default | 177 | "make defconfig" Create a ./.config file by using the default |
178 | symbol values from arch/$ARCH/defconfig. | 178 | symbol values from arch/$ARCH/defconfig. |
179 | "make allyesconfig" | 179 | "make allyesconfig" |
180 | Create a ./.config file by setting symbol | 180 | Create a ./.config file by setting symbol |
181 | values to 'y' as much as possible. | 181 | values to 'y' as much as possible. |
182 | "make allmodconfig" | 182 | "make allmodconfig" |
183 | Create a ./.config file by setting symbol | 183 | Create a ./.config file by setting symbol |
184 | values to 'm' as much as possible. | 184 | values to 'm' as much as possible. |
185 | "make allnoconfig" Create a ./.config file by setting symbol | 185 | "make allnoconfig" Create a ./.config file by setting symbol |
186 | values to 'n' as much as possible. | 186 | values to 'n' as much as possible. |
187 | "make randconfig" Create a ./.config file by setting symbol | 187 | "make randconfig" Create a ./.config file by setting symbol |
188 | values to random values. | 188 | values to random values. |
189 | 189 | ||
190 | The allyesconfig/allmodconfig/allnoconfig/randconfig variants can | 190 | You can find more information on using the Linux kernel config tools |
191 | also use the environment variable KCONFIG_ALLCONFIG to specify a | 191 | in Documentation/kbuild/make-configs.txt. |
192 | filename that contains config options that the user requires to be | 192 | |
193 | set to a specific value. If KCONFIG_ALLCONFIG=filename is not used, | ||
194 | "make *config" checks for a file named "all{yes/mod/no/random}.config" | ||
195 | for symbol values that are to be forced. If this file is not found, | ||
196 | it checks for a file named "all.config" to contain forced values. | ||
197 | |||
198 | NOTES on "make config": | 193 | NOTES on "make config": |
199 | - having unnecessary drivers will make the kernel bigger, and can | 194 | - having unnecessary drivers will make the kernel bigger, and can |
200 | under some circumstances lead to problems: probing for a | 195 | under some circumstances lead to problems: probing for a |
201 | nonexistent controller card may confuse your other controllers | 196 | nonexistent controller card may confuse your other controllers |
202 | - compiling the kernel with "Processor type" set higher than 386 | 197 | - compiling the kernel with "Processor type" set higher than 386 |
203 | will result in a kernel that does NOT work on a 386. The | 198 | will result in a kernel that does NOT work on a 386. The |
204 | kernel will detect this on bootup, and give up. | 199 | kernel will detect this on bootup, and give up. |
205 | - A kernel with math-emulation compiled in will still use the | 200 | - A kernel with math-emulation compiled in will still use the |
206 | coprocessor if one is present: the math emulation will just | 201 | coprocessor if one is present: the math emulation will just |
207 | never get used in that case. The kernel will be slightly larger, | 202 | never get used in that case. The kernel will be slightly larger, |
208 | but will work on different machines regardless of whether they | 203 | but will work on different machines regardless of whether they |
209 | have a math coprocessor or not. | 204 | have a math coprocessor or not. |
210 | - the "kernel hacking" configuration details usually result in a | 205 | - the "kernel hacking" configuration details usually result in a |
211 | bigger or slower kernel (or both), and can even make the kernel | 206 | bigger or slower kernel (or both), and can even make the kernel |
212 | less stable by configuring some routines to actively try to | 207 | less stable by configuring some routines to actively try to |
213 | break bad code to find kernel problems (kmalloc()). Thus you | 208 | break bad code to find kernel problems (kmalloc()). Thus you |
214 | should probably answer 'n' to the questions for | 209 | should probably answer 'n' to the questions for |
215 | "development", "experimental", or "debugging" features. | 210 | "development", "experimental", or "debugging" features. |
216 | 211 | ||
217 | COMPILING the kernel: | 212 | COMPILING the kernel: |
218 | 213 | ||
219 | - Make sure you have at least gcc 3.2 available. | 214 | - Make sure you have at least gcc 3.2 available. |
220 | For more information, refer to Documentation/Changes. | 215 | For more information, refer to Documentation/Changes. |
221 | 216 | ||
222 | Please note that you can still run a.out user programs with this kernel. | 217 | Please note that you can still run a.out user programs with this kernel. |
223 | 218 | ||
224 | - Do a "make" to create a compressed kernel image. It is also | 219 | - Do a "make" to create a compressed kernel image. It is also |
225 | possible to do "make install" if you have lilo installed to suit the | 220 | possible to do "make install" if you have lilo installed to suit the |
226 | kernel makefiles, but you may want to check your particular lilo setup first. | 221 | kernel makefiles, but you may want to check your particular lilo setup first. |
227 | 222 | ||
228 | To do the actual install you have to be root, but none of the normal | 223 | To do the actual install you have to be root, but none of the normal |
229 | build should require that. Don't take the name of root in vain. | 224 | build should require that. Don't take the name of root in vain. |
230 | 225 | ||
231 | - If you configured any of the parts of the kernel as `modules', you | 226 | - If you configured any of the parts of the kernel as `modules', you |
232 | will also have to do "make modules_install". | 227 | will also have to do "make modules_install". |
228 | |||
229 | - Verbose kernel compile/build output: | ||
230 | |||
231 | Normally the kernel build system runs in a fairly quiet mode (but not | ||
232 | totally silent). However, sometimes you or other kernel developers need | ||
233 | to see compile, link, or other commands exactly as they are executed. | ||
234 | For this, use "verbose" build mode. This is done by inserting | ||
235 | "V=1" in the "make" command. E.g.: | ||
236 | |||
237 | make V=1 all | ||
238 | |||
239 | To have the build system also tell the reason for the rebuild of each | ||
240 | target, use "V=2". The default is "V=0". | ||
233 | 241 | ||
234 | - Keep a backup kernel handy in case something goes wrong. This is | 242 | - Keep a backup kernel handy in case something goes wrong. This is |
235 | especially true for the development releases, since each new release | 243 | especially true for the development releases, since each new release |
236 | contains new code which has not been debugged. Make sure you keep a | 244 | contains new code which has not been debugged. Make sure you keep a |
237 | backup of the modules corresponding to that kernel, as well. If you | 245 | backup of the modules corresponding to that kernel, as well. If you |
238 | are installing a new kernel with the same version number as your | 246 | are installing a new kernel with the same version number as your |
239 | working kernel, make a backup of your modules directory before you | 247 | working kernel, make a backup of your modules directory before you |
240 | do a "make modules_install". | 248 | do a "make modules_install". |
241 | Alternatively, before compiling, use the kernel config option | 249 | Alternatively, before compiling, use the kernel config option |
242 | "LOCALVERSION" to append a unique suffix to the regular kernel version. | 250 | "LOCALVERSION" to append a unique suffix to the regular kernel version. |
243 | LOCALVERSION can be set in the "General Setup" menu. | 251 | LOCALVERSION can be set in the "General Setup" menu. |
244 | 252 | ||
245 | - In order to boot your new kernel, you'll need to copy the kernel | 253 | - In order to boot your new kernel, you'll need to copy the kernel |
246 | image (e.g. .../linux/arch/i386/boot/bzImage after compilation) | 254 | image (e.g. .../linux/arch/i386/boot/bzImage after compilation) |
247 | to the place where your regular bootable kernel is found. | 255 | to the place where your regular bootable kernel is found. |
248 | 256 | ||
249 | - Booting a kernel directly from a floppy without the assistance of a | 257 | - Booting a kernel directly from a floppy without the assistance of a |
250 | bootloader such as LILO, is no longer supported. | 258 | bootloader such as LILO, is no longer supported. |
251 | 259 | ||
252 | If you boot Linux from the hard drive, chances are you use LILO which | 260 | If you boot Linux from the hard drive, chances are you use LILO which |
253 | uses the kernel image as specified in the file /etc/lilo.conf. The | 261 | uses the kernel image as specified in the file /etc/lilo.conf. The |
254 | kernel image file is usually /vmlinuz, /boot/vmlinuz, /bzImage or | 262 | kernel image file is usually /vmlinuz, /boot/vmlinuz, /bzImage or |
255 | /boot/bzImage. To use the new kernel, save a copy of the old image | 263 | /boot/bzImage. To use the new kernel, save a copy of the old image |
256 | and copy the new image over the old one. Then, you MUST RERUN LILO | 264 | and copy the new image over the old one. Then, you MUST RERUN LILO |
257 | to update the loading map!! If you don't, you won't be able to boot | 265 | to update the loading map!! If you don't, you won't be able to boot |
258 | the new kernel image. | 266 | the new kernel image. |
259 | 267 | ||
260 | Reinstalling LILO is usually a matter of running /sbin/lilo. | 268 | Reinstalling LILO is usually a matter of running /sbin/lilo. |
261 | You may wish to edit /etc/lilo.conf to specify an entry for your | 269 | You may wish to edit /etc/lilo.conf to specify an entry for your |
262 | old kernel image (say, /vmlinux.old) in case the new one does not | 270 | old kernel image (say, /vmlinux.old) in case the new one does not |
263 | work. See the LILO docs for more information. | 271 | work. See the LILO docs for more information. |
264 | 272 | ||
265 | After reinstalling LILO, you should be all set. Shutdown the system, | 273 | After reinstalling LILO, you should be all set. Shutdown the system, |
266 | reboot, and enjoy! | 274 | reboot, and enjoy! |
267 | 275 | ||
268 | If you ever need to change the default root device, video mode, | 276 | If you ever need to change the default root device, video mode, |
269 | ramdisk size, etc. in the kernel image, use the 'rdev' program (or | 277 | ramdisk size, etc. in the kernel image, use the 'rdev' program (or |
270 | alternatively the LILO boot options when appropriate). No need to | 278 | alternatively the LILO boot options when appropriate). No need to |
271 | recompile the kernel to change these parameters. | 279 | recompile the kernel to change these parameters. |
272 | 280 | ||
273 | - Reboot with the new kernel and enjoy. | 281 | - Reboot with the new kernel and enjoy. |
274 | 282 | ||
275 | IF SOMETHING GOES WRONG: | 283 | IF SOMETHING GOES WRONG: |
276 | 284 | ||
277 | - If you have problems that seem to be due to kernel bugs, please check | 285 | - If you have problems that seem to be due to kernel bugs, please check |
278 | the file MAINTAINERS to see if there is a particular person associated | 286 | the file MAINTAINERS to see if there is a particular person associated |
279 | with the part of the kernel that you are having trouble with. If there | 287 | with the part of the kernel that you are having trouble with. If there |
280 | isn't anyone listed there, then the second best thing is to mail | 288 | isn't anyone listed there, then the second best thing is to mail |
281 | them to me (torvalds@linux-foundation.org), and possibly to any other | 289 | them to me (torvalds@linux-foundation.org), and possibly to any other |
282 | relevant mailing-list or to the newsgroup. | 290 | relevant mailing-list or to the newsgroup. |
283 | 291 | ||
284 | - In all bug-reports, *please* tell what kernel you are talking about, | 292 | - In all bug-reports, *please* tell what kernel you are talking about, |
285 | how to duplicate the problem, and what your setup is (use your common | 293 | how to duplicate the problem, and what your setup is (use your common |
286 | sense). If the problem is new, tell me so, and if the problem is | 294 | sense). If the problem is new, tell me so, and if the problem is |
287 | old, please try to tell me when you first noticed it. | 295 | old, please try to tell me when you first noticed it. |
288 | 296 | ||
289 | - If the bug results in a message like | 297 | - If the bug results in a message like |
290 | 298 | ||
291 | unable to handle kernel paging request at address C0000010 | 299 | unable to handle kernel paging request at address C0000010 |
292 | Oops: 0002 | 300 | Oops: 0002 |
293 | EIP: 0010:XXXXXXXX | 301 | EIP: 0010:XXXXXXXX |
294 | eax: xxxxxxxx ebx: xxxxxxxx ecx: xxxxxxxx edx: xxxxxxxx | 302 | eax: xxxxxxxx ebx: xxxxxxxx ecx: xxxxxxxx edx: xxxxxxxx |
295 | esi: xxxxxxxx edi: xxxxxxxx ebp: xxxxxxxx | 303 | esi: xxxxxxxx edi: xxxxxxxx ebp: xxxxxxxx |
296 | ds: xxxx es: xxxx fs: xxxx gs: xxxx | 304 | ds: xxxx es: xxxx fs: xxxx gs: xxxx |
297 | Pid: xx, process nr: xx | 305 | Pid: xx, process nr: xx |
298 | xx xx xx xx xx xx xx xx xx xx | 306 | xx xx xx xx xx xx xx xx xx xx |
299 | 307 | ||
300 | or similar kernel debugging information on your screen or in your | 308 | or similar kernel debugging information on your screen or in your |
301 | system log, please duplicate it *exactly*. The dump may look | 309 | system log, please duplicate it *exactly*. The dump may look |
302 | incomprehensible to you, but it does contain information that may | 310 | incomprehensible to you, but it does contain information that may |
303 | help debugging the problem. The text above the dump is also | 311 | help debugging the problem. The text above the dump is also |
304 | important: it tells something about why the kernel dumped code (in | 312 | important: it tells something about why the kernel dumped code (in |
305 | the above example it's due to a bad kernel pointer). More information | 313 | the above example it's due to a bad kernel pointer). More information |
306 | on making sense of the dump is in Documentation/oops-tracing.txt | 314 | on making sense of the dump is in Documentation/oops-tracing.txt |
307 | 315 | ||
308 | - If you compiled the kernel with CONFIG_KALLSYMS you can send the dump | 316 | - If you compiled the kernel with CONFIG_KALLSYMS you can send the dump |
309 | as is, otherwise you will have to use the "ksymoops" program to make | 317 | as is, otherwise you will have to use the "ksymoops" program to make |
310 | sense of the dump (but compiling with CONFIG_KALLSYMS is usually preferred). | 318 | sense of the dump (but compiling with CONFIG_KALLSYMS is usually preferred). |
311 | This utility can be downloaded from | 319 | This utility can be downloaded from |
312 | ftp://ftp.<country>.kernel.org/pub/linux/utils/kernel/ksymoops/ . | 320 | ftp://ftp.<country>.kernel.org/pub/linux/utils/kernel/ksymoops/ . |
313 | Alternately you can do the dump lookup by hand: | 321 | Alternately you can do the dump lookup by hand: |
314 | 322 | ||
315 | - In debugging dumps like the above, it helps enormously if you can | 323 | - In debugging dumps like the above, it helps enormously if you can |
316 | look up what the EIP value means. The hex value as such doesn't help | 324 | look up what the EIP value means. The hex value as such doesn't help |
317 | me or anybody else very much: it will depend on your particular | 325 | me or anybody else very much: it will depend on your particular |
318 | kernel setup. What you should do is take the hex value from the EIP | 326 | kernel setup. What you should do is take the hex value from the EIP |
319 | line (ignore the "0010:"), and look it up in the kernel namelist to | 327 | line (ignore the "0010:"), and look it up in the kernel namelist to |
320 | see which kernel function contains the offending address. | 328 | see which kernel function contains the offending address. |
321 | 329 | ||
322 | To find out the kernel function name, you'll need to find the system | 330 | To find out the kernel function name, you'll need to find the system |
323 | binary associated with the kernel that exhibited the symptom. This is | 331 | binary associated with the kernel that exhibited the symptom. This is |
324 | the file 'linux/vmlinux'. To extract the namelist and match it against | 332 | the file 'linux/vmlinux'. To extract the namelist and match it against |
325 | the EIP from the kernel crash, do: | 333 | the EIP from the kernel crash, do: |
326 | 334 | ||
327 | nm vmlinux | sort | less | 335 | nm vmlinux | sort | less |
328 | 336 | ||
329 | This will give you a list of kernel addresses sorted in ascending | 337 | This will give you a list of kernel addresses sorted in ascending |
330 | order, from which it is simple to find the function that contains the | 338 | order, from which it is simple to find the function that contains the |
331 | offending address. Note that the address given by the kernel | 339 | offending address. Note that the address given by the kernel |
332 | debugging messages will not necessarily match exactly with the | 340 | debugging messages will not necessarily match exactly with the |
333 | function addresses (in fact, that is very unlikely), so you can't | 341 | function addresses (in fact, that is very unlikely), so you can't |
334 | just 'grep' the list: the list will, however, give you the starting | 342 | just 'grep' the list: the list will, however, give you the starting |
335 | point of each kernel function, so by looking for the function that | 343 | point of each kernel function, so by looking for the function that |
336 | has a starting address lower than the one you are searching for but | 344 | has a starting address lower than the one you are searching for but |
337 | is followed by a function with a higher address you will find the one | 345 | is followed by a function with a higher address you will find the one |
338 | you want. In fact, it may be a good idea to include a bit of | 346 | you want. In fact, it may be a good idea to include a bit of |
339 | "context" in your problem report, giving a few lines around the | 347 | "context" in your problem report, giving a few lines around the |
340 | interesting one. | 348 | interesting one. |
341 | 349 | ||
342 | If you for some reason cannot do the above (you have a pre-compiled | 350 | If you for some reason cannot do the above (you have a pre-compiled |
343 | kernel image or similar), telling me as much about your setup as | 351 | kernel image or similar), telling me as much about your setup as |
344 | possible will help. Please read the REPORTING-BUGS document for details. | 352 | possible will help. Please read the REPORTING-BUGS document for details. |
345 | 353 | ||
346 | - Alternately, you can use gdb on a running kernel. (read-only; i.e. you | 354 | - Alternately, you can use gdb on a running kernel. (read-only; i.e. you |
347 | cannot change values or set break points.) To do this, first compile the | 355 | cannot change values or set break points.) To do this, first compile the |
348 | kernel with -g; edit arch/i386/Makefile appropriately, then do a "make | 356 | kernel with -g; edit arch/i386/Makefile appropriately, then do a "make |
349 | clean". You'll also need to enable CONFIG_PROC_FS (via "make config"). | 357 | clean". You'll also need to enable CONFIG_PROC_FS (via "make config"). |
350 | 358 | ||
351 | After you've rebooted with the new kernel, do "gdb vmlinux /proc/kcore". | 359 | After you've rebooted with the new kernel, do "gdb vmlinux /proc/kcore". |
352 | You can now use all the usual gdb commands. The command to look up the | 360 | You can now use all the usual gdb commands. The command to look up the |
353 | point where your system crashed is "l *0xXXXXXXXX". (Replace the XXXes | 361 | point where your system crashed is "l *0xXXXXXXXX". (Replace the XXXes |
354 | with the EIP value.) | 362 | with the EIP value.) |