From: Sven Luther <sven.luther@wanadoo.fr>
To: Marc Dietrich <marvin24@gmx.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [FYI] linux 2.6 still not working with PReP (ppc32)
Date: Wed, 5 Jan 2005 16:47:53 +0100 [thread overview]
Message-ID: <20050105154753.GA26760@pegasos> (raw)
In-Reply-To: <200501051233.25622.marvin24@gmx.de>
On Wed, Jan 05, 2005 at 12:33:25PM +0100, Marc Dietrich wrote:
>
> Hallo Sebastian,
>
> Am Dienstag, 4. Januar 2005 15:47 schrieb Sebastian Heutling:
> > Hello again Marc,
> >
> > > > >Can you put a working zImage.prep somewhere on the web (<1.44 MB, so I
> > > > > can write it to a floppy disk)?
> > > >
> > (...)
> > It is on: http://sengor.ath.cx/~sheutlin/prep/zImage.prep
>
> hehe! It is booting!!!
>
> Different to your setup, I get no timeouts here (boot.log is attached) - this
> makes me wondering if there are different board revisions out there.
>
> Another thing is, I tried to compile a stock 2.6.8 kernel with your config
> from "/proc/config.gz" and the modified irq tables in prep_pci.c (I guess you
> also did this modification). This kernel does not boot! It even doesn't show
> the boot loader - it just hangs after finished loading the kernel from floppy
> disk. Either a) I have a corrupt kernel tree, b) my compiler (gcc 3.3.4,
> debian/sarge) has problems or c) you changed something else in your kernel.
>
> I check a) and I think it is ok.
> for b) I'm currently downloading the 3.3.5 compile from unstable debian (the
> you you are using I guess), and will try it again.
> c) how does you prep_pci.c looks like, any other changes?
>
> I have to leave this machine alone tomorrow, so I won't be able to do any
> testing further. From what we have now here, it seems that something is
> broken for kernels >2.6.8. It would be nice, if someone can double check
> this.
Did you try :
http://people.debian.org/~luther/prep/d-i-2005.01.03-prep
It is the debian kernel with the prep_pci patch, and the debian-installer
(yesterdays or so daily-built) initrd on top of it. I simply boot it from
netboot with :
boot enet:192.168.1.10,d-i-2005.01.03-prep,192.168.1.17
(where .10 is my tftp server, and .17 a random free address on the subnet).
And it works fine. I plan to do a kernel upload soonishly to fix those issues
in debian, but i would like to have also the fixes for the other prep systems
if needed.
Friendly,
Sven Luther
next prev parent reply other threads:[~2005-01-05 15:39 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 [this message]
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
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=20050105154753.GA26760@pegasos \
--to=sven.luther@wanadoo.fr \
--cc=linuxppc-dev@ozlabs.org \
--cc=marvin24@gmx.de \
/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.