On Tue April 29 2003 5:01 pm, Yongtao Yang wrote:

Richard Bos writes:

...

# Modified by YaST2. Last modification on Tue Apr 29 21:11:45 2003

title linux kernel (hd1,4)/vmlinuz root=/dev/hdb7 hdc=ide-scsi vga=791 initrd (hd1,4)/initrd

...

...

title suse kernel (hd1,4)/vmlinuz root=/dev/hdb8 hdc=ide-scsi vga=791

^^^^^， Here, I am a little surprised, why did you share the same kernel? Is it just a typo?

...

initrd (hd1,7)/initrd

-- Yongtao Yang

email: yongtao.yang@telia.com

You should change the "kernel (hd1,4)" to "kernel (hd1,7)", without the quotes of course, to match the root=/dev/hdb8 and initrd (hd1,7). title suse kernel (hd1,7)/vmlinuz root=/dev/hdb8 hdc=ide-scsi vga=791 initrd (hd1,7)/initrd Stan

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? 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?

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

Op woensdag 30 april 2003 16:49, schreef Anders Johansson:

hdb9? Is that your root partition? Shouldn't you try "root=/dev/hdb9"?

Anders, another point on solution score card! It's indeed that easy! Thanks a lot :)) -- Richard Bos Without a home the journey is endless

Op woensdag 30 april 2003 10:42, schreef Anders Johansson:

What exactly is the error you get? Could there be an "Unable to mount" somewhere? Have you tried rebuilding the initrd?

There is an error before indeed; ... VFS: mounted root (ext2 filesystem) readonly trying to move old root to initrd.... failed unmounting old root Warning: unable to open an initial console Kernel panic: no init found, try passing init= option to kernel -- Richard Bos Without a home the journey is endless

On Wed April 30 2003 2:56 am, Richard Bos wrote:

Op woensdag 30 april 2003 03:08, schreef Stan Glasoe:

...

On Tue April 29 2003 5:01 pm, Yongtao Yang wrote:

...

Richard Bos writes:

...

# Modified by YaST2. Last modification on Tue Apr 29 21:11:45 2003

title linux kernel (hd1,4)/vmlinuz root=/dev/hdb7 hdc=ide-scsi vga=791 initrd (hd1,4)/initrd

...

...

title suse kernel (hd1,4)/vmlinuz root=/dev/hdb8 hdc=ide-scsi vga=791

^^^^^， Here, I am a little surprised, why did you share the same kernel? Is it just a typo?

...

initrd (hd1,7)/initrd

-- Yongtao Yang

email: yongtao.yang@telia.com

You should change the "kernel (hd1,4)" to "kernel (hd1,7)", without the quotes of course, to match the root=/dev/hdb8 and initrd (hd1,7).

title suse kernel (hd1,7)/vmlinuz root=/dev/hdb8 hdc=ide-scsi vga=791 initrd (hd1,7)/initrd

Changed that as well, but that did not help either.

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 .....

Yast made it without the "hdc=ide-scsi vga=791" and the initrd line. for "suse".

-- Richard Bos Without a home the journey is endless

In my theory, no, it shouldn't work. My /boot/grub/menu.lst has absolute path names. Specifying /vmlinuz looks to be a relative path and AFAIK grub don't do relative paths. Change these relative paths to absolutes. On my system I've quit using a separate /boot partition and leave it as a directory off /. My grub then has /boot/vmlinuz and /boot/initrd after the drive/partition designations. Change yours as follows and see what happens. The root=/dev/hd?? is OK. title linux kernel (hd1,4)/boot/vmlinuz root=/dev/hdb7 hdc=ide-scsi vga=791 initrd (hd1,4)/boot/initrd title suse kernel (hd1,7)/boot/vmlinuz root=/dev/hdb8 hdc=ide-scsi vga=791 initrd (hd1,7)/boot/initrd

On Wed April 30 2003 8:32 am, Anders Johansson wrote:

On Wednesday 30 April 2003 15:26, Stan Glasoe wrote:

...

In my theory, no, it shouldn't work. My /boot/grub/menu.lst has absolute path names. Specifying /vmlinuz looks to be a relative path and AFAIK grub don't do relative paths.

grub follows the directory layout on the partition. grub's paths are relative to the partition you specify

My mileage varied greatly with grub under SuSE 8.1 and I had to specify absolute paths because grub didn't follow relative paths on the partitions. grub couldn't find /boot off / by itself. Took me a while to figure that out. grub would error out of the GUI and throw up the text version of its menu where I then had a chance to specify drive, partition and absolute path. Worked for me!

...

Change these relative paths to absolutes. On my system I've quit using a separate /boot partition and leave it as a directory off /. My grub then has /boot/vmlinuz and /boot/initrd after the drive/partition designations. Change yours as follows and see what happens. The root=/dev/hd?? is OK.

title linux kernel (hd1,4)/boot/vmlinuz root=/dev/hdb7 hdc=ide-scsi vga=791

This will work if hd1,4 (hdb5) has a /boot and fail otherwise

Correct. You'd need to adjust both kernel and initrd drive/partition and root=/dev/hdxx for separate /boot and / "root" partitions. Stan