From: Olaf Hering <olaf@aepfle.de>
To: dtutty@porchlight.ca
Cc: linuxppc-dev@ozlabs.org
Subject: Re: boot problems on pseries
Date: Wed, 23 Aug 2006 00:35:29 +0200 [thread overview]
Message-ID: <20060822223528.GA7546@aepfle.de> (raw)
In-Reply-To: <20060822165023.GA4807@hooton>
On Tue, Aug 22, dtutty@porchlight.ca wrote:
> Boot failures:
>
> 1. CD not recognized as bootable, so use OF manually.
> 2. OF manually will boot yaboot.
> 3. yaboot doesn't find its config in the /etc directory
> of the cd, nor in the / directory of the CD with the
> yaboot executable.
> 4. when manually from yaboot attempt to boot a kernel
> image, get either:
> a) CLAIMED FAILED
> b) incorrect ELF format
> (something like that, I wasn't there
> when the tech got that one)
> c) not a valid kernel image
>
> At no point do I get any indication that the linux kernel has had a
> chance to try booting; it doesn't get that far.
I havent seen that sort of error, maybe a bad burn.
> I'll look at SuSE and see if there's a free-download of a boot floppy.
http://mirrors.kernel.org/opensuse/distribution/SL-stable/iso/SUSE-Linux-10.1-GM-ppc-mini.iso
http://mirrors.kernel.org/opensuse/distribution/SL-OSS-factory/inst-source/boot/boot.ppc.iso
You can try to boot the inst32 file via the network. Make sure to fix
the ARP entry for the H50 on the tftp server, like 'arp -s 1.2.3.4 MAC'
yaboot.ibm can also be used. Rename yaboot.cnf to yaboot.conf so yaboot
will be able to download it.
next prev parent reply other threads:[~2006-08-22 22:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-20 17:00 boot problems on pseries dtutty
2006-08-21 14:56 ` Olaf Hering
2006-08-22 16:50 ` dtutty
2006-08-22 22:35 ` Olaf Hering [this message]
2006-08-23 23:59 ` Linas Vepstas
-- strict thread matches above, loose matches on Subject: below --
2006-08-09 1:36 Mark Fasheh
2006-08-09 11:51 ` Olaf Hering
2006-08-09 15:37 ` Benjamin Herrenschmidt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060822223528.GA7546@aepfle.de \
--to=olaf@aepfle.de \
--cc=dtutty@porchlight.ca \
--cc=linuxppc-dev@ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.