Hello,
i had several issues in the past with Debian on IBM Power, please see
the list archives if you have an archeological interest ;-) Some of
those issues were firmware/microcode related, some were related to VIOS
mapped disks and i also had a similar issue to the one your experiencing
due to the rather old v1.3.13 yaboot used in Debian v6.0.x. I also could
imagine, that you're missing the appropriate iSCSI driver in the initrd
image. To rule out the mentioned yaboot issue, could you please try an
install with a current snapshot of the Debian v7.x [1] installer image?
This contains a known working yaboot v1.3.16.
Best regards,
Frank
[1]
http://cdimage.debian.org/cdimage/weekly-builds/powerpc/iso-cd/debian-testing-powerpc-netinst.iso
On Mon, Mar 18, 2013 at 10:57:52PM +0100, Michael Felt wrote:
> p.s. disk types tried: logical volume from a vgClient volume group, iSCSI
> LUN (virtual "physical" disk).
>
> sizes: 10G and 12G (I regularly install AIX on 4 and 6G "disks").
>
> On Mon, Mar 18, 2013 at 10:56 PM, Michael Felt <mamf...@gmail.com> wrote:
>
> > 4 to 5 years ago I was only able to get Linux to boot, (Redhat, Novell,
> > Debian) unless it was a physical disk. I have not tried that yet because I
> > do not have an empty disk to supply. And if that worked I would just
> > uninstall it as that is "too expensive" in terms of resources.
> >
> > I have tried the "install64/export64" options Guided LVM (and I choose as
> > many partitions as possible) and the Guided "one partition" - recommended
> > for new users option.
> >
> > The partitions are created, the install runs fine, but on reboot - nada.
> >
> > IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
> > IBM
> > |
> > Elapsed time since release of system processors: 28 mins 41 secs
> >
> > Config file read, 4096 bytes
> >
> > Welcome to yaboot version 1.3.13
> > Enter "help" to get some basic usage information
> > boot: Linux
> >
> > Please wait, loading kernel...
> > Can't open device </vdevice/v-scsi@30000002/@1:0>
> > /vdevice/v-scsi@30000002/@1:2,/boot/vmlinux: Unable to open file, Invalid
> > device
> > boot: help
> >
> > Press the tab key for a list of defined images.
> > The label marked with a "*" is is the default image, press <return> to
> > boot it.
> >
> > To boot any other label simply type its name and press <return>.
> >
> > To boot a kernel image which is not defined in the yaboot configuration
> > file, enter the kernel image name as [[device:][partno],]/path, where
> > "device:" is the OpenFirmware device path to the disk the image
> > resides on, and "partno" is the partition number the image resides on.
> > Note that the comma (,) is only required if you specify an OpenFirmware
> > device, if you only specify a filename you should not start it with a ","
> >
> >
> > If you omit "device:" and "partno" yaboot will use the values of
> > "device=" and "partition=" in yaboot.conf, right now those are set to:
> > device=/vdevice/v-scsi@30000002/@1
> > partition=2
> >
> > boot:
> >
> >
> > That is all I get. I am willing to spend some time on this - but I do not
> > know the "Linux" way these days.
> > Clear instructions, clear requests for info (e.g., if you can jump out of
> > the install and look at something, manual divvy if you prefer, etc..)
> >
> > just might be a few hours to days between responses as I also have regular
> > work to attend to.
--
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130319131850.gb18...@dyndns.org
