On Wed, Dec 08, 2004 at 08:49:47AM -0700, Matthew B. Brookover wrote: > On Wed, 2004-12-08 at 07:19, Graham Wood wrote: > > On Wed, Dec 08, 2004 at 04:33:12PM +0300, Anatoly Pugachev wrote: > > > Hi > > > help. i'm stuck on the first stage compiling kernel. > > Ahh - my fault. I should have pointed out that patching the kernel > > isn't necessarily going > > to work at the moment - according to someone on the list a few weeks > > back, the patches there > > are not necessarily kept up to date with the code in the module form > > It seems that there is some conflicting information. Patching the > kernel is necessary. Without the patches you will get errors like: > > FATAL: Error inserting gfs (/lib/modules/2.6.9/kernel/fs/gfs/gfs.ko): > Unknown symbol in module, or unknown parameter (see dmesg) > > gfs: no version for "lm_mount" found: kernel tainted. > > gfs: Unknown symbol panic_on_oops" errors in the logs. > > The patches for the 2.6.9 kernel include the panic_on_oops symbol as > well as others. There is now a patch that is required. It wasn't there before. All this patch does is export the panic_on_oops symbol. cluster/gfs-kernel/patches/2.6.9/00006.patch You can either apply the patches to the kernel, or apply 00006.patch and build the modules from their source dirs. Both ways should work. I said a few weeks back that I forget to update the lock_gulm.patch when I make changes to the module's code sometimes. Ken is much better at keeping his patches uptodate. And in either case, you can always make new ones with the make files in the source dirs for the modules. (peek at the Makefile, you need to have the kernel source in the right place for the make patches command to work.) Sorry for confusing things. -- Michael Conrad Tadpol Tilstra Computers are not intelligent. They only think they are.
Description: PGP signature