The easiest kernel install yet and no xfs patch either!

[SUOrangeman]

Has anyone tried a 2.6 test kernel with these instructions? I'll give it a whirl, if I can find the time.

-SUO

[jduff]

I got and used a vanilla kernel from kernel.org and had no problems upgrading to get to 2.4.22 and it took fewer commands than this.

Maybe I'm just not as paranoid? Whatever, you find what works for you and run with it.

There is also more than one way to do these things, obviously.

[Nigel_Tufnel]

Thanks for the tips. I tried upgrading using the standard Debian method and my system couldn't find the new modules setup. This did the trick.

[dovidbaron]

Having no success with initrd to get ext3 up, decided to follow your procedure and redo the kernel. Downloaded the 2.4.22 package, first tried making a fresh xconfig but had to edit its result anyway since ext3 and jbd were not even choices there so reverted back to the existing config and edited that. All this was not so terrible. After editing it, read it into the xsonfig and then saved.

First tried to make-kpkg with the modules (not necessary, since they were all there--same version as I have, but). This proceded, left a 3meg vmlinuz on the src directory but did produce anything usable. I was no really looking, I suppose. Cleaned and did it again with out the modules (I am not trying to make an initrd but activated the cramfs as well). Where it fails (it took longer this time!!), is that it cannot open a ....\extra\module... file for writing and exited error=255. I was not out of disk space. The "extra" subdirectory was not there. Made it, repeated (without cleaning, it passes everything already done--tell us that!), the same error.

Afraid I was out of diskspace, I removed the package (everything already compiled). Repeat the make-dpkg which failed at the same point. So another 30meg did not help. I ended up deleting the whole business--will try again when I know more, probably with 2.6.

1. There were compiler warnings--long too small for integer constant !!!, deprecated operations, result always true/false because of size of variable, etc. Don't like that.

2. How much disk space IS really needed to do this.

3. How does one recover from the error and procedes.

4. That too-large vmlinuz? What is it? Too big for lilo.