Differences between version 31 and predecessor to the previous major change of KernelNotes.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 31 | Last edited on Tuesday, June 12, 2007 8:40:44 am | by IanMcDonald | Revert |
| Older page: | version 30 | Last edited on Monday, June 11, 2007 8:53:30 pm | by BenStaz | Revert |
@@ -46,9 +46,9 @@
</verbatim>
OTOH kernels since about 2.6.15 require [GCC] 3.x. Read the file to find the versions of compilers and other tools you need. Make sure to check the <tt>README</tt> and <tt>Documentation/Changes</tt> files to find out which version you need. Of course you always read the compile instructions for software you download, right? :)
-To compile a kernel with a specific compiler, you can say eg. <tt>make CC=gcc-2.95 bzImage</tt> to make the <tt>bzImage</tt> target using the <tt>gcc-2.95</tt> compiler.
+To compile a kernel with a specific compiler, you can say eg. <tt>make CC=gcc-2.95 bzImage</tt> to make the <tt>bzImage</tt> target using the <tt>gcc-2.95</tt> compiler. See also [DistCC]
!!! Linking fails with <tt>bootsplash</tt> compiled into your kernel
Compiling aborts with the following message:
@@ -67,9 +67,9 @@
: undefined reference to `con2fb_map'
make: *** [.tmp_vmlinux1] Error 1
</verbatim>
-You need to have framebuffer console support compiled in. It can't be a module! Set <tt>CONFIG_FRAMEBUFFER_CONSOLE=y</tt> in the <tt>.config</tt>.
+You need to have framebuffer console support compiled in. It can't be a module! Set <tt>CONFIG_FRAMEBUFFER_CONSOLE=y</tt> in the <tt>.config</tt>. NB This sounds like a one off bug that has probably been long fixed
.
!!! ModuleInitTools
Starting with 2.5.51, modules have a different format. The extension has also changed from <tt>.o</tt> to <tt>.ko</tt>, for kernel object. To work with modules, you need a completely rewritten set of module tools (modprobe(8), insmod(8), lsmod(8)), collectively called <tt>module-init-tools</tt>. They can coexist with the 2.4.x-specific tools. __Note, however__ that <tt>module-init-tools</tt> no longer reads <tt>modules.conf</tt> and instead uses a new file called modprobe.conf(5) which has a different syntax. <tt>man 5 modprobe.conf</tt> will be your friend here. It's possible to set <tt>modprobe.conf</tt> to handle modules for both 2.4.x and 2.5.x kernels, which is pretty cool if you're a dual-booter.
@@ -81,11 +81,11 @@
!!! Kconfig files
These are kernel configuration files. When the kernel configuration application is run, it reads the main kernel configuration file, located in /source/dir/arch/<your architecture>/Kconfig. This main configuration file then includes other configuration files from the different subdirectories in the kernel directory tree.
-!!! Other Misc 2
.6 Notes
+Don't edit these Kconfig files directly unless you are doing [KernelDevelopment]. These files are driven from .config file mentioned earlier in this article
.
-In the 2.4 series, you could read <tt>Documentation/Configure.help</tt> to see all
the help for the entries you'd see in <tt>make ''foo''config</tt>. In 2.6, this has moved to individual <tt>Kconfig</tt> files in each sub-directory of the source tree
.
+In the 2.4 series, you could read <tt>Documentation/Configure.help</tt> to get
the equivalent information
.
!!! See also
* TroubleshootingStartUp has help for some problems while booting kernels
