Depmod error on dist-upgrade

[shamrock_uk]

Ack, just received a scary error on my latest upgrade:

Do you want to continue [Y/n]? Y
Setting up linux-image-2.6.15-16-386 (2.6.15-16.23) ...
There was a problem running depmod. This may be benign,
(You may have versioned symbol names, for instance).
Or this could be an error.
depmod exited with return value 0
depmod got a signal 11
Since this image uses initrd, I am not deleting the file
/lib/modules/2.6.15-16-386/modules.dep. However, there is no
guarantee that the file is valid. I would strongly advice
you to either abort and fix the errors in depmod, or
regenerate the initrd image with a known good modules.dep
file. I repeat, an initrd kernel image with a bad modules.dep
shall fail to boot.
Would you like to abort now? [No] Yes


Not particularly wishing to have to reinstall Dapper again in the event of it not booting, so what would you folks suggest? Both of the solutions listed are a bit beyond my skill levels to fix and I'm short of time to learn at the moment.

[warpforge]

Your existing kernel should still be installed, so I wouldn't worry too much about rebooting and finding a dead system. Also, why are you using the 386 kernel? Are you on something earlier than a Pentium Pro?

[shamrock_uk]

Ah good, that's reassuring. I don't have a huge amount of bandwidth to play with here, so downloading all those Dapper updates again would have been a bit of a headache.

I'm using the 386 kernel largely because that's the one Dapper Flight 4 picked as default. Slightly strange because Breezy always went for the k7 kernel (running an AMD Athlon 2000+ here). I haven't bothered changing it because of time constraints and also because I've had much better success getting the fglrx drivers working with the 386 kernel for some reason.
It's the most annoying thing ever - 3d acceleration works upon the initial install (this goes for Breezy too) but then the moment an updated kernel (eg the 2.6-12-10 in Breezy) installs itself, or the xorg-fglrx drivers update (even when they update at the same time) then it breaks, citing an incompatible kernel module. The annoying this is that they're the same *&@~ versions and even more annoying is that reverting to the previous configuration doesn't restore the status quo. Can't wait 'till I get my hands on an NVidia card!
Thanks for the response!