From: Sven Luther <sven.luther@wanadoo.fr>
To: Christian <evilninja@gmx.net>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [FYI] linux 2.6 still not working with PReP (ppc32)
Date: Thu, 6 Jan 2005 22:49:27 +0100 [thread overview]
Message-ID: <20050106214927.GA10588@pegasos> (raw)
In-Reply-To: <39090.195.126.66.126.1105046464.squirrel@housecafe.dyndns.org>
On Thu, Jan 06, 2005 at 10:21:04PM +0100, Christian wrote:
> On Thu, January 6, 2005 22:07, Sven Luther said:
> >>
> >> no disks attached, but i will do some more tests on this tonight...
> >
> > Ah, no wonder you don't see a disk then ...
>
> ;-)
>
> > I wonder if d-i is upto installing a NFS-root system, i don't think so.
>
> yes, i can see that. nfsroot is my only way to go here. (will probably get
> a proper scsi-cable soon)
If your NFS server is also powerpc, you could just debootstrap the partition
there :) I guess pure NFS support will have to wait for sarge+1. Now that d-i
is branched, patches are welcome though.
> > See :
> > http://svn.debian.org/wsvn/kernel/trunk/kernel/source/kernel-source-2.6.8-2.6.8/debian/patches/powerpc-prep-powerstack-irq.dpatch?op=file&rev=0&sc=0
>
> ah, ok. will try.
I just moved it to 2.6.9, but these kernel-source are not yet released, and
probably won't be until this WE or something, at which point the official
powerpc kernels will include it. With a bit of luck we will have real prep
support in d-i two weeks from now, depending how i am able to fix the
partman-prep horror story. (Added bunch of logs -> it worked, removed them ->
don't work anymore, altough it works on power4 chrp hardware :/)
Friendly,
Sven Luther
next prev parent reply other threads:[~2005-01-06 21:40 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-26 13:35 [FYI] linux 2.6 still not working with PReP (ppc32) Marc Dietrich
2004-12-27 2:47 ` Christian
2004-12-27 21:37 ` Marc Dietrich
2005-01-02 0:31 ` Sebastian Heutling
2005-01-03 12:26 ` Marc Dietrich
2005-01-04 0:54 ` evilninja
2005-01-04 11:31 ` Sebastian Heutling
2005-01-04 14:04 ` Marc Dietrich
2005-01-04 14:42 ` Sebastian Heutling
[not found] ` <1104850036.6164.25.camel@weizen.left.earth>
2005-01-05 11:33 ` Marc Dietrich
2005-01-05 15:47 ` Sven Luther
2005-01-05 17:10 ` Christian
2005-01-05 17:39 ` Sven Luther
2005-01-06 16:00 ` Christian
2005-01-06 16:27 ` Sven Luther
2005-01-06 20:27 ` Christian
2005-01-06 21:07 ` Sven Luther
2005-01-06 21:21 ` Christian
2005-01-06 21:49 ` Sven Luther [this message]
2004-12-31 9:55 ` Sven Luther
2004-12-31 15:00 ` Sebastian Heutling
2004-12-31 22:28 ` Sven Luther
2005-01-01 23:56 ` Sebastian Heutling
2005-01-02 9:39 ` Sven Luther
2005-01-02 21:33 ` Sebastian Heutling
[not found] ` <200501051733.06350.marvin24@gmx.de>
[not found] ` <20050105165551.GA29287@pegasos>
2005-01-05 20:57 ` Marc Dietrich
2005-01-09 23:17 ` Sebastian Heutling
2005-01-10 6:34 ` Sven Luther
2005-01-10 15:19 ` Sebastian Heutling
2005-01-10 6:54 ` Sven Luther
-- strict thread matches above, loose matches on Subject: below --
2005-01-04 2:12 Christian
2005-01-04 13:23 ` Marc Dietrich
2005-01-04 15:08 ` Christian
2004-12-04 22:45 Christian Kujau
2004-12-05 0:41 ` Sebastian Heutling
2004-12-05 17:41 ` Christian Kujau
2004-12-05 17:41 ` Christian Kujau
2004-12-06 1:46 ` Sebastian Heutling
2004-12-06 1:46 ` Sebastian Heutling
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=20050106214927.GA10588@pegasos \
--to=sven.luther@wanadoo.fr \
--cc=evilninja@gmx.net \
--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.