Klaus-Peter Schrage wrote: > Now booting into kernel 2.4.9-31 hangs after the message > "Unkompressing Linux ... Ok, booting the kernel." > is displayed, and my machine can only be resuscitated by pressing the reset > button.
Make sure your /boot images and files in /boot for 2.4.9-31 are like this: -rw-r--r-- 1 root root 456727 Mar 2 19:18 initrd-2.4.9-31.img -rw-r--r-- 1 root root 461444 Mar 2 19:18 initrd-2.4.9-31smp.img lrwxrwxrwx 1 root root 14 Mar 2 19:09 kernel.h -> kernel.h-2.4.9 -rw-r--r-- 1 root root 409 Mar 2 19:09 kernel.h-2.4.9 lrwxrwxrwx 1 root root 20 Mar 2 19:18 module-info -> module-info-2.4.9-31 -rw-r--r-- 1 root root 13599 Feb 26 07:18 module-info-2.4.9-31 -rw-r--r-- 1 root root 13599 Feb 26 07:08 module-info-2.4.9-31smp lrwxrwxrwx 1 root root 22 Mar 2 19:31 System.map -> System.map-2.4.9-31smp -rw-r--r-- 1 root root 438666 Feb 26 07:18 System.map-2.4.9-31 -rw-r--r-- 1 root root 459334 Feb 26 07:08 System.map-2.4.9-31smp lrwxrwxrwx 1 root root 16 Mar 2 19:18 vmlinuz -> vmlinuz-2.4.9-31 -rw-r--r-- 1 root root 975103 Feb 26 07:18 vmlinuz-2.4.9-31 -rw-r--r-- 1 root root 1049060 Feb 26 07:08 vmlinuz-2.4.9-31smp and make sure your /boot/grub setup file info matches the right boot image for kernel 2.4.9-31. I actally downgraded (rpm --oldpackage ) from kernel 2.4.16 rawhide to this newest errata kernel for stability and all is working ok so far. Did you make a boot floppy for k2.4.9-31??? If so try it out. But make sure you have the latest initscripts, mkinitrd and SysVinit or anything else 7.1 might need. I'm upgraded to Enigma 7.2+erratas. Peter _______________________________________________ Seawolf-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/seawolf-list
