Op woensdag 30 april 2003 10:42, schreef Anders Johansson:
On Wednesday 30 April 2003 09:56, Richard Bos wrote:
Should it theoretically work if the the config file is as follows?
.... title linux kernel (hd1,4)/vmlinuz root=/dev/hdb7 hdc=ide-scsi vga=791 initrd (hd1,4)/initrd
title suse kernel (hd1,7)/vmlinuz root=/dev/hdb8 hdc=ide-scsi vga=791 initrd (hd1,7)/initrd
Is there a program /sbin/init on hdb8? Have you tried mounting it from the working installation and check?
No this is located hdb9. Mounting works fine. The "suse" linux boots okay if started from a rescue cd.
What exactly is the error you get? Could there be an "Unable to mount" somewhere? Have you tried rebuilding the initrd?
Does "boot installed system" work on the new install?
Yes. If even did, after the installation => yast has made the menu.lst file and the system therefor booted "suse" linux. So I rebooted the system to go to my work linux and that version stopped with exactly the same error: msg: kernel panic: no init found, try passing init= option to kernel 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 I bet that if I run linux from the newly installed system, that I can get it to boot nicely, but that the work version won't boot in that case.... The work linux has everything on 1 big partition. What should be passed to the kernel via the "init=" option? -- Richard Bos Without a home the journey is endless