From: "Dominik 'Rathann' Mierzejewski" <rathann@icm.edu.pl>
To: linux-mips@linux-mips.org
Subject: Re: indy r4000FPC kernel?
Date: Thu, 12 Feb 2004 17:42:05 +0100 [thread overview]
Message-ID: <20040212164204.GC7586@icm.edu.pl> (raw)
In-Reply-To: <Pine.LNX.4.58.0402121652410.24037@brilsmurf.chem.tue.nl>
On Thu, Feb 12, 2004 at 05:12:58PM +0100, Joost wrote:
> Hello,
>
> Is this the correct list to be asking about kernel trouble?
> If not, i apologize for this lengthy piece of offtopic ranting :-)
>
> I'm trying to get a working kernel on my indy, but 2.4.16
> seems to be as far as it will go. The 2.4.22 that comes with
> debian testing gives an error while booting so i decided
> to try and be adventurous and downloaded the 2.6 sources
> via cvs. The PROM in this beast is old i gues, it won't
> boot elf kernels, so i used the 'ecoff' tip on linux-mips.com.
Get a current version (branch linux_2_4) from linux-mips.org's CVS
and try that one. There have been some trouble with r4k processors
lately, but they seem to be resolved now. I'm running 2.4.25-pre6
at the moment. Oh, and use arcboot - it saves a lot of hassle.
You don't have to upload your kernel to volume header and you can
boot any ELF kernel image that is on any ext2/3 partition on your
system.
HTH
--
Dominik 'Rathann' Mierzejewski <rathann@icm.edu.pl>
Interdisciplinary Centre for Mathematical and Computational Modelling
Warsaw University | http://www.icm.edu.pl | tel. +48 (22) 5540810
next prev parent reply other threads:[~2004-02-12 16:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-12 16:12 indy r4000FPC kernel? Joost
2004-02-12 16:42 ` Dominik 'Rathann' Mierzejewski [this message]
2004-02-12 17:03 ` Joost
2004-02-12 17:48 ` Guido Guenther
2004-02-12 18:46 ` Joost
2004-02-12 20:10 ` Guido Guenther
2004-02-13 8:37 ` Joost
2004-02-13 14:17 ` Guido Guenther
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=20040212164204.GC7586@icm.edu.pl \
--to=rathann@icm.edu.pl \
--cc=linux-mips@linux-mips.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