On Wed April 30 2003 9:01 am, Richard Bos wrote:
snip<
Than I booted the work linux (called linux) from rescue disk and run yast in the work linux to create a new grub. Worked fine the work linux now boots okay, but the newly installed linux comes with: msg: kernel panic: no init found, try passing init= option to kernel
snip<
I quit using YaST to edit my boot loader options for SuSE 8.0 and 8.1. YaST would not correctly edit the file whether lilo or grub based. You seem to be suffering the same problem now. YaST just doesn't edit lilo.conf or grub's menu.lst file correctly all the time especially when trying to create a dual boot situation where there are different drives and partitions. This seems to have been fixed very well for v8.2 where you edit the whole file and not just certain lines. You should manually edit /boot/grub/menu.lst on your primary partition where your work linux is located. Also add the absolute path to initrd for your new install. This worked for me and can't hurt even if grub should use relative paths based on the root partition definition. I got the same errors and eventually ended up specifying absolute paths and it works - for me. Stan