From: Sven Luther <sven.luther@wanadoo.fr>
To: Ulrich Teichert <krypton@ulrich-teichert.org>
Cc: linuxppc-dev@ozlabs.org, mikemartin@linux.ca,
debian-powerpc@lists.debian.org
Subject: Re: 43p-140 install issues
Date: Sun, 2 Jan 2005 17:41:22 +0100 [thread overview]
Message-ID: <20050102164122.GA6866@pegasos> (raw)
In-Reply-To: <200501021538.j02Fc0Ld013444@arbas.nms.ulrich-teichert.org>
On Sun, Jan 02, 2005 at 04:38:00PM +0100, Ulrich Teichert wrote:
> Hi,
>
> [del]
> >Yes, please, i would greatly appreciate it, preferably the 2.6.8 kernel too.
> >Let' try to get this fixed before the sarge release, which is not so far off
> >now.
>
> OK, 9 hours later I had a current sarge buisnesscard CD image, with
> interesting results. I booted the standard kernel from the cdrom
> with `boot cdrom:`, it came up and failed to load the initrd, so it died
> on the spot as nothing could be mounted. It was detecting that I was using
> a serial console.
You need to boot install/powerpc/vmlinuz-prep.initrd, not the vmlinux one.
> Of course, I forgot to capture that session, so I did it again with logging
> on in kermit. Then I could not boot anything from the CD, but I can still
> boot fine from disk, so it's not a hardware problem. The LED displays F05
> after reading something from the CDROM in this case and the machine hangs.
> Strange.
>
> I will try to boot via tftp, the firmware seems to be unable to boot
> a specific file from CDROM,
Ah, strange. That said, tftp is the prefered boot method for prep hardware.
Friendly,
Sven Luther
prev parent reply other threads:[~2005-01-02 16:33 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <855e88d00412291051792d3daa@mail.gmail.com>
2004-12-31 9:53 ` 43p-140 install issues Sven Luther
2005-01-01 0:54 ` Mike Martin
2005-01-01 13:15 ` Ulrich Teichert
2005-01-01 15:00 ` Sven Luther
2005-01-01 16:30 ` Ulrich Teichert
2005-01-01 16:57 ` Sven Luther
2005-01-02 1:15 ` Mike Martin
2005-01-02 9:43 ` Sven Luther
2005-01-03 4:15 ` Mike Martin
2005-01-03 7:05 ` Sven Luther
2005-01-03 13:39 ` Mike Martin
2005-01-03 14:01 ` Sven Luther
2005-01-03 14:07 ` Mike Martin
2005-01-03 14:30 ` Sven Luther
2005-01-03 14:30 ` Philippe Guyot
2005-01-03 14:43 ` Mike Martin
2005-01-03 15:47 ` vinai
2005-01-03 14:45 ` Sven Luther
2005-01-04 4:03 ` Mike Martin
2005-01-04 8:20 ` Ulrich Teichert
2005-01-04 9:23 ` Philippe Guyot
2005-01-04 11:19 ` Ulrich Teichert
2005-01-04 11:23 ` Mike Martin
2005-01-04 13:41 ` Mike Martin
2005-01-04 15:23 ` Ulrich Teichert
2005-01-04 15:39 ` Mike Martin
2005-01-05 4:36 ` Mike Martin
2005-01-05 8:07 ` Ulrich Teichert
2005-01-05 22:09 ` Ulrich Teichert
2005-01-05 11:17 ` Leigh Brown
2005-01-06 3:35 ` Mike Martin
2005-01-06 8:15 ` Sven Luther
2005-01-07 5:10 ` Mike Martin
2005-01-07 7:57 ` Sven Luther
2005-01-03 15:51 ` Ulrich Teichert
2005-01-03 16:50 ` Leigh Brown
2005-01-03 17:28 ` Sven Luther
2005-01-03 19:32 ` Ulrich Teichert
2005-01-03 19:42 ` Leigh Brown
2005-01-03 22:11 ` Ulrich Teichert
2005-01-04 22:28 ` Sven Luther
2005-01-04 22:39 ` Leigh Brown
2005-01-05 9:03 ` Sven Luther
2005-01-05 9:49 ` Philippe Guyot
2005-01-05 10:00 ` Leigh Brown
2005-01-05 11:47 ` Sven Luther
2005-01-05 14:02 ` Philippe Guyot
2005-01-05 15:45 ` Hollis Blanchard
2005-01-05 16:08 ` Sven Luther
2005-01-05 16:18 ` Philippe Guyot
2005-01-05 16:52 ` Hollis Blanchard
2005-01-05 16:30 ` Leigh Brown
2005-01-05 17:00 ` Sven Luther
2005-01-03 9:56 ` Philippe Guyot
2005-01-03 10:48 ` Sven Luther
2005-01-03 10:56 ` Philippe Guyot
2005-01-03 11:17 ` Sven Luther
2005-01-03 11:57 ` Michael Schmitz
2005-01-03 12:47 ` Sven Luther
2005-01-03 15:24 ` Michael Schmitz
2005-01-03 16:04 ` Sven Luther
2005-01-06 12:19 ` Michael Schmitz
2005-01-06 14:02 ` Sven Luther
2005-01-02 15:38 ` Ulrich Teichert
2005-01-02 16:41 ` Sven Luther [this message]
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=20050102164122.GA6866@pegasos \
--to=sven.luther@wanadoo.fr \
--cc=debian-powerpc@lists.debian.org \
--cc=krypton@ulrich-teichert.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mikemartin@linux.ca \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).