From: Christian <evilninja@gmx.net>
To: linuxppc-dev@ozlabs.org
Subject: Re: [FYI] linux 2.6 still not working with PReP (ppc32)
Date: Wed, 05 Jan 2005 18:10:22 +0100 [thread overview]
Message-ID: <41DC1F7E.5030003@gmx.net> (raw)
In-Reply-To: <20050105154753.GA26760@pegasos>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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
>>
yes, it's booting, but i get timeouts here on my PReP (however Marc says,
that he does not get errors). would you be so kind and publish the .config
too?
> Did you try :
>
> http://people.debian.org/~luther/prep/d-i-2005.01.03-prep
>
and Sven: nice d-i, really. but i couldn't see any config for this kernel
either. it would be nice if you could put the config somewhere too.
mine are here, now with SCSI enabled too and thus errors showing up:
http://www.nerdbynature.de/bits/hal/daily/configs/config-ppc-2.6.10
http://www.nerdbynature.de/bits/hal/daily/boot/dmesg-2.6.10
(but network is fine now ;-))
thank you both,
Chrisitian.
- --
BOFH excuse #305:
IRQ-problems with the Un-Interruptible-Power-Supply
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFB3B9+C/PVm5+NVoYRAmjiAJ4hrZAtauVVUjR6cWj+7l70+4X+lgCg/RlD
rPCFIAeCt5eiGxTYplSDONk=
=9pzA
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2005-01-05 17:17 UTC|newest]
Thread overview: 37+ 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 [this message]
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-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=41DC1F7E.5030003@gmx.net \
--to=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 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).