I installed a 2nd version of suse8.1 on the same system/harddisk. version 1, called linux ;) boots fine version 2, called suse panics during grub stage 2 with the following error msg: kernel panic: no init found, try passing init= option to kernel What does the kernel proposal involve? The version called "suse" boots fine if invoked from suse's rescue disk (boot installed system. And it boots fine if grub is configured from within the version called "suse". However, in this configuration the other suse version called "linux" does panic with the same error. What may be the cause of this trouble? I searched the internet, sdb, experimented with grub's shell. The latter told that /vmlinuz is located at: (hd1,4) and (hd1,7). Below the current configuration of grub. I must say that the entry for suse has been altered by me. The original yast version is: title suse kernel (hd1,4)/vmlinuz root=/dev/hdb8 the init_rd modules have been set to INITRD_MODULES="reiserfs ide-scsi" 1 thing I did not do is to perform an mk_initd. I assume however that yast will take for that if that is required. yast2-bootloader version: :/etc/sysconfig> rpm -q yast2-bootloader yast2-bootloader-2.6.68-1 I hope someone has the golden hint! -- Richard Bos Without a home the journey is endless # Modified by YaST2. Last modification on Tue Apr 29 21:11:45 2003 gfxmenu (hd1,4)/message color white/blue black/light-gray default 0 timeout 8 title linux kernel (hd1,4)/vmlinuz root=/dev/hdb7 hdc=ide-scsi vga=791 initrd (hd1,4)/initrd title windows root (hd0,0) makeactive chainloader +1 title suse kernel (hd1,4)/vmlinuz root=/dev/hdb8 hdc=ide-scsi vga=791 initrd (hd1,7)/initrd title floppy root (fd0) chainloader +1 title failsafe kernel (hd1,4)/vmlinuz.shipped root=/dev/hdb7 ide=nodma apm=off acpi=off vga=normal nosmp maxcpus=0 disableapic 3 initrd (hd1,4)/initrd.shipped