Re: Installation - boot after installation fails

[Michael Felt <mamfelt@gmail.com>]

Repeat - to all this time:

Does the info I found here need to go into a bug report, or has someone already collected the key information?

regards,
Michael

On Sun, Mar 24, 2013 at 6:50 PM, Michael Felt <mamfelt@gmail.com> wrote:

The boot list shows:
 Version SF240_418
 SMS 1.6 (c) Copyright IBM Corp. 2000,2005 All rights reserved.
-------------------------------------------------------------------------------
 Select Device
 Device  Current  Device
 Number  Position  Name
 1.        3      Virtual Ethernet
                  ( loc=U9115.505.062C0CA-V5-C4-T1 )
 2.        2      SCSI 10737 MB Harddisk, part=1 ()
                  ( loc=U9115.505.062C0CA-V5-C2-T1-W8100000000000000-L0 )
 3.        1      SCSI CD-ROM
                  ( loc=U9115.505.062C0CA-V5-C2-T1-W8200000000000000-L0 )


Choose #2

System choose "Linux" by itself, and booted :)

So, did I make a typo last time, or what do you suggest? (did it use "old" by accident?)

regards,
Michael

On Sun, Mar 24, 2013 at 6:45 PM, Michael Felt <mamfelt@gmail.com> wrote:

found it, yaboot.conf

The original contents:
## yaboot.conf generated by debian-installer
##
## run: "man yaboot.conf" for details. Do not make changes until you have!!
## see also: /usr/share/doc/yaboot/examples for example configurations.
##
## For a dual-boot menu, add one or more of:
## bsd=/dev/hdaX, macos=/dev/hdaY, macosx=/dev/hdaZ

boot="/dev/disk/by-id/scsi-SAIX_VDASD_0002c0ca0000d300000001134deb16ba.4-part1"
device=/vdevice/v-scsi@30000002/@1
partition=2
root="UUID=c9498eff-1727-4484-93e6-94249972c918"
timeout=50
install=/usr/lib/yaboot/yaboot
enablecdboot

image=/boot/vmlinux
        label=Linux
        read-only
        initrd=/boot/initrd.img

image=/boot/vmlinux.old
        label=old
        read-only
        initrd=/boot/initrd.img.old
==========
~ # chroot /target
# ls boot
System.map-2.6.32-5-powerpc64  initrd.img-2.6.32-5-powerpc64
config-2.6.32-5-powerpc64      vmlinux
initrd.img                     vmlinux-2.6.32-5-powerpc64
# ls -l boot
total 24016
-rw-r--r-- 1 root root  2344890 Feb 25 09:45 System.map-2.6.32-5-powerpc64
-rw-r--r-- 1 root root    93214 Feb 25 09:45 config-2.6.32-5-powerpc64
lrwxrwxrwx 1 root root       29 Mar 24 18:15 initrd.img -> initrd.img-2.6.32-5-powerpc64
-rw-r--r-- 1 root root 10699255 Mar 24 18:18 initrd.img-2.6.32-5-powerpc64
lrwxrwxrwx 1 root root       26 Mar 24 18:15 vmlinux -> vmlinux-2.6.32-5-powerpc64
-rw-r--r-- 1 root root 11403398 Feb 25 09:45 vmlinux-2.6.32-5-powerpc64
========
changed (/target)/etc/yaboot.conf to
...
boot="/dev/disk/by-id/scsi-SAIX_VDASD_0002c0ca0000d300000001134deb16ba.4-part1"
## device=/vdevice/v-scsi@30000002/@1
device=/vdevice/v-scsi@30000002/@8100000000000000:2
partition=2
root="UUID=c9498eff-1727-4484-93e6-94249972c918"
timeout=50
install=/usr/lib/yaboot/yaboot
enablecdboot

image=/boot/vmlinux
        label=Linux
        read-only
        initrd=/boot/initrd.img

deleted this part...
image=/boot/vmlinux.old

...
=========
ybin says:
ybin: Warning: You must manually configure OpenFirmware to boot.

What does this mean?

regards,
Michael

p.s. results follow.

On Thu, Mar 21, 2013 at 9:50 PM, Lennart Sorensen <lsorense@csclub.uwaterloo.ca> wrote:

On Thu, Mar 21, 2013 at 07:09:22PM +0100, Michael Felt wrote:
> Thanks. But not knowing yaboot (yes, such people exist :p@me ) how do I
> verify what exists (I can do an install again, perhaps add the right device
> string as well) and get it installed by ybin?
>
> Note: internet to server is currently down. Maintenance.

I think you can look at the yaboot config file on the boot partition.
It is a text file.

--
Len Sorensen