Differences between version 20 and revision by previous author of KernelNotes.
Other diffs: Previous Major Revision, Previous Revision, or view the Annotated Edit History
| Newer page: | version 20 | Last edited on Saturday, June 18, 2005 12:04:16 pm | by DanielLawson | Revert |
| Older page: | version 18 | Last edited on Monday, October 4, 2004 6:51:29 am | by JonatanPalsson | Revert |
@@ -1,6 +1,9 @@
-!!In file included from ide-cd.c:318:
-!!
ide-cd.h:440: error: long, short, signed or unsigned used invalidly for `slot_tablelen'
+!!!Compile Problems
+<pre>
+__
In file included from ide-cd.c:318:__
+__
ide-cd.h:440: error: long, short, signed or unsigned used invalidly for `slot_tablelen'__
+</pre>
This occurs if you're using a more recent compiler than the kernel can be compiled for, for example gcc 3.x to compile a kernel (kernels only work with <gcc 3). try:
<verbatim>
make CC=gcc-2.95 bzImage
@@ -50,23 +53,58 @@
Jonte: Good stuff man.. works great :)
I also found out that if you enable the VGA text console, the bootsplash wont be used (so disable it;)
----
+!!!Version 2.6 series LinuxKernel notes
+
+!!ModuleInitTools
+
+Starting with 2.5.51, Linus merged a new way of handling modules. He's added versioning on every symbol inside a module, with the intent that the kernel can read the module and what hooks it uses, compare it to an internal database of whats critical and whats not, and can decide whether the module could be used even if it wasnt compiled specifically for the current running kernel. This adds a lot more flexibility for people forced to run binary-only proprietary modules to support their hardware. What this means for the user is a completely rewritten set of module tools (modprobe(8), insmod(8), lsmod(8)). On [Debian] you can get these with a quick
+
+ apt-get install module-init-tools
+
+Module-init-tools is backwards compatible with 2.4.x kernels, so if you're dual booting between a stable and a beta kernel, you've got module functionality on both. (Read ModuleInitTools for an important caveat!)
+
+__Important:__ module-init-tools no longer reads modules.conf and instead uses a new file called modprobe.conf(5) which has a different syntax. 'man 5 modprobe.conf' will be your friend here. It's possible to set modprobe.conf to handle modules for both 2.4.x and 2.5.x kernels, which is pretty cool if you're a dualbooter.
+
+Also you may notice that the extension of modules has changed from .o to .ko, for kernel object.
+
+
!!Kernel 2.6 on Debian Woody
Add the following lines to your apt/sources.conf:
+
+
+Either do apt-get install kernel-image-2.6 and pick an appropriate image from the list available (ie, kernel-image-2.6-686) or download, compile and install a kernel yourself.
+
+Update your bootloader, and it should just work.
+
+As mentioned above you need at least a new version of module-init-tools - you will need to use backports to get updated
+versions of some important packages. Add the following two lines to your apt sources.list:
<verbatim>
# kernel 2.6 and related things
deb http://www.backports.org/debian woody kernel-2.6
deb http://www.backports.org/debian woody module-init-tools
</verbatim>
do an apt-get dist-update ; apt-get dist-upgrade
make sure that module-init-tools is installed
+and install/update module-init-tools, modutils (if you want to dual-boot with a 2.4 kernel), hdparm, and procinfo.
+
+! dhcp server
+If you install 2.6 on a machine running a dhcp server, then the default woody startup script won't work.
+The "dhcp", version "2.0pl5-11" has two separate binaries, one for 2.0 kernels and one for later kernels.
+Unfortunately, the /usr/sbin/dhcpd shell script tests if your kernel version is either 2.0, or 2.x (where "x"
+is between 1 and 5, inclusive). Edit the shell script and add a "6" to the part that says ~[12345].
+
+(This is an incredibly helpful hint. As far as I know, this is the only place its documented, and it's pretty
+damn important -AS)
+
+! dhcp client
+The dhcp client startup script looks to suffer from the same problem. Edit the shell script /sbin/dhclient and make the same changes - add a "6" to the part that says ~[12345].
+
-Either do apt-get install kernel-image-2.6 and pick an appropriate image from the list available (ie, kernel-image-2.6-686) or download, compile and install a kernel yourself.
-Update your bootloader, and it should just work.
!!Kernel 2.6 on RedHatLinux 9:
@@ -110,10 +148,22 @@
See
* [Upgrading RH9 to 2.6.0-test4|http://www.fearthecow.net/index.pl?section=guest&page=kernel]
* [Migrating to Linux Kernel 2.6|http://thomer.com/linux/migrate-to-2.6.html]
+
+!!Nvidia and 2.6 notes
+
+[NVIDIA drivers|http://www.nvidia.com/linux] version 1.0-6106 and up support all 2.4 and 2.6 kernels, including kernels with the new 2.6 option for 4k stacks.
+
+!!Other Misc 2.6 Notes
+In the 2.4 series, you could read /usr/src/linux-<version>/Documentation/Configure.help
+to see all the help for the entries you'd see in make *config.
+
+In 2.6, this has moved to individual "Kconfig" files in each sub-directory of the
+source tree.
+
----
See TroubleshootingStartUp for some problems while booting kernels. %%%
See KernelTweaking for tuning hints.
----
CategoryKernel
