Re: new kernel problem
On 4/3/07, Daniel Smith <firstname.lastname@example.org> wrote:
I've compiled a new kernel, same version as the old one, and installed
it using make-kpackage. When I try to boot it, however, it says it
can't mount my filesystem, and it freezes. I am booting from
reiserfs. I thought it might need an initrd, so I pointed it at my
old initrd. It told me it couldn't find /lib/modules/2.6.18, so I
opened up the initrd using cpio and moved /lib/modules/2.6.18-4-amd64
(the old kernel name) /lib/modules/2.6.18 to match the new one, put it
all back it, and it got farther in the boot sequence but it still
didn't come up. I am wondering how I can automatically make an initrd
to match my new kernel (the old initrd was automatically installed
when I put debian on) or any other way I can make it work?
Check if you have compiled in support for reiserfs. It must not be
built as a module. About the initrd, use the --initrd option for
make-kpkg. Then the packaging system will take care of the rest.
The only reason I need a new kernel is because when I compile modules
and try to install them it says:
FATAL: Error inserting ndiswrapper
(/lib/modules/2.6.18-4-amd64/misc/ndiswrapper.ko): Invalid module
so alternately, is there a way to get the sources(/headers) that match
my kernel so I can compile the module properly to match my kernel?
This would alleviate the need for a new kernel altogether.
Check the dmesg log to find out why the module loading is failing. You
can find the kernel headers in the package