Hi, To recap: a) potato install installed 2.2.17. You now want a new kernel b) You moved /lib/modules/2.2.17 to 2.2.17-old c) you installed your own version of 2.2.17 d) You now have one /boot/vmlinuz-2.2.17, and both /vmlinuz and /vmlinuz.old link to it. There is o real way of avoiding this. Even if you moved /boot/vmlinuz-2.2.17 to /boot/vmlinuz-2.2.17.old, that kernel may not be bootable after step (c) since it shall continue to look for its modules in /lib/modules/2.2.17 (which are totally different set of modules).
In these situations I download and create a 2.2.16 version, test and ensure that works, and then install my 2.2.17 version. I know this is suboptimal, but until we can tell a kernel-image at boot time where to find it's modules, that's the best we can do. manoj -- Humor in the Court: Q: ...any suggestions as to what prevented this from being a murder trial instead of an attempted murder trial? A: The victim lived. Manoj Srivastava <[EMAIL PROTECTED]> <http://www.debian.org/%7Esrivasta/> 1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C