Greetings! I'm running SuSE 10.0 on an AMD64 X2 system. Recently, I did a security update via the YOU updater that took the kernel version from 2.6.13-15.10-smp to 2.6.13-15.11-smp. When I rebooted, however, none of my modules loaded. The boot log showed that the kernel was looking in /lib/modules/2.6.13-15.10-smp/, which no longer exists. Also, uname reports that the kernel version is still 2.6.13-15.10-smp, but vmlinuz and other files in /boot are all appear to be updated to 2.6.13-15.11. If I run 'strings' on vmlinuz, I find "2.6.13-15.11-smp", so there's not much doubt that I'm actually running the new version. So why does it think it's the old version? In the end, I just created a symlink from /lib/modules/2.6.13-15.10-smp to /lib/modules/2.6.13-15.11-smp and rebooted, and all of the modules loaded okay, but I'm still troubled by the thought that the kernel has gone schizoid, and there's something funky with my system. I've trolled a few SuSE forums and such, but haven't run across anyone reporting a similar problem. Any thoughts? Barry -- Barry McLarnon VE3JF Ottawa, ON