Branimir Vasilic
Did yast somehow give me the wrong kernel? It was the only kernel available for download and this was the first kernel upgrade I've done on this system. This system was freshly installed yesterday. Nothing outside of the suse distro is installed on it.
I just finished fixing the same issue on a 32-bit machine. The kernel is fine except the update does not execute mkinitrd which the reiserfs module doesn't like. Just boot off the CD into the rescue system. Create a directory in /tmp
Strange, I just tested on my private system (after testing yesterday at work several system) and did not encounter any problems. We had a first kernel out that was broken indeed but removed that and issued a new update :-(
(for example /tmp/root) and mount your root partition there (for example mount /dev/hda2 /tmp/root). Then chroot to it (for example chroot /tmp/root). Then execute mkinitrd. Reboot and things will work. I also noticed that the new kernels reset the runlevel and powersave configurations to defaults which is really annoying.
That should not happen. I'm confused. If you have some more details and can tell me what exactly is broken, I would appreciate it, Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126