I am trying to update from Suse 8.2, kernel 2.4.20 to new kernel 2.6.0-test4.

I downloaded the source tree from mirrors.kernel.org, and followed the instructions to update my mod_utils to 0.9.13, and the other utilities according to the documentation.

After a few tries, I was able to build the kernel and install, but I have a consistent problem.

When I configure reiserfs (the default fs for my primary partition) as a loadable module, there is a kernel panic on startup with a message 'cannot find partition' message.

When I build reiser directly into the kernel, the system boots without complaint.

The mk_initrd tool runs without error, and the other loaded modules are found correctly (eth0, sound), but nogo for reiserfs. The Suse 2.4 kernel seems to use reiserfs as a loadable module without complaint.

Am I missing something obvious?

When I configure reiserfs (the default fs for my primary partition) as a loadable module, there is a kernel panic on startup with a message 'cannot find partition' message.

When I build reiser directly into the kernel, the system boots without complaint.
---------------------------------------------------------------------------

This is the normal behavior. If the module for the / partition file system is made loadable then the kernel has no file system module available to load the file system module.

------------------------------------------------------------------------
"The Suse 2.4 kernel seems to use reiserfs as a loadable module without complaint."

If that is true then either reiserfs is part of the bootable kernel or the / partition is not reiserfs.