From: Andrew Finley <afinley@gis.umn.edu>
To: gentoo-mips@lists.gentoo.org
Subject: Re: [gentoo-mips] PANIC: Unexpected exception at boot o2 R5000
Date: Wed, 24 Nov 2004 20:16:44 CST [thread overview]
Message-ID: <200411250216.iAP2Gi7m001947@challenge.software.umn.edu> (raw)
Thanks Steve,
Ok, should this kernel go in the volume header then use arcboot? If I
wanted to build a proper kernel, can I still use the kernel that comes from
emerge-source (if so what build options should be used)?
-andy
On 24 Nov 2004, Stephen P. Becker wrote:
>
> > Also, I followed the kernel specs for the Indigo2/Indy, is that still
ok
> > for the o2?
>
> Indy/Indigo2 systems are known as ip22, whereas O2 is ip32. It is
> almost a completely different arch aside from the processor, so if you
> compiled a kernel for ip22, then arcboot won't even save you here.
>
> If you want a kernel that is known to work for O2, check out
> http://dev.gentoo.org/~geoman/vmlinux64-2004-11-06.bz2 for now. It will
> let you boot your system do stuff until you are able to build a proper
> kernel.
>
> Steve
>
> --
> gentoo-mips@gentoo.org mailing list
>
>
--
gentoo-mips@gentoo.org mailing list
next reply other threads:[~2004-11-25 2:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-25 2:16 Andrew Finley [this message]
2004-11-25 2:32 ` [gentoo-mips] PANIC: Unexpected exception at boot o2 R5000 Stephen P. Becker
2004-11-28 18:11 ` [gentoo-mips] please disregard previous question Andrew Finley
-- strict thread matches above, loose matches on Subject: below --
2004-11-25 2:45 [gentoo-mips] PANIC: Unexpected exception at boot o2 R5000 Andrew Finley
2004-11-24 21:35 Andrew Finley
2004-11-25 1:08 ` Kumba
2004-11-25 1:56 ` Andrew Finley
2004-11-25 2:02 ` Stephen P. Becker
2004-11-28 16:52 ` Andrew Finley
2004-11-28 21:05 ` Kumba
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=200411250216.iAP2Gi7m001947@challenge.software.umn.edu \
--to=afinley@gis.umn.edu \
--cc=gentoo-mips@lists.gentoo.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