From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: David Daney <david.daney@cavium.com>
Cc: Jim Faulkner <jfaulkne@ccs.neu.edu>, linux-mips@linux-mips.org
Subject: Re: booting linux-3.3 or linux 3.4 on an SGI O2?
Date: Thu, 14 Jun 2012 13:02:28 +0200 [thread overview]
Message-ID: <20120614110228.GA10493@alpha.franken.de> (raw)
In-Reply-To: <4FCE593B.10808@cavium.com>
On Tue, Jun 05, 2012 at 12:08:43PM -0700, David Daney wrote:
> On 06/05/2012 12:00 PM, Jim Faulkner wrote:
> >Hi all, I haven't been able to boot any kernels after linux 3.2 on my
> >SGI O2. I've tried linux-3.3.5 and linux-3.4.0, but neither would boot.
> >Unfortunately I don't have further information such as a kernel panic,
> >since I don't get any video output after the kernel is loaded. I've
> >attached my linux-3.4 .config. Anybody know what patches I might need
> >to get the latest kernels booting on this system?
> >
>
> I have had problems as well.
>
> Someone should configure a serial console and early printk to see if
> they can see what is happening.
Linux version 3.5.0-rc2 (tsbogend@solo.franken.de) (gcc version 4.3.1 (Debian 4.3.1-2) ) #1 Thu Jun 14 12:05:29 CEST 2012
this version (current git from two days ago) boots for me with serial console
up to a login prompt:
mips:~# cat /proc/cpuinfo
system type : SGI O2
processor : 0
cpu model : R5000 V2.1 FPU V1.0
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2012-06-14 11:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-05 19:00 booting linux-3.3 or linux 3.4 on an SGI O2? Jim Faulkner
2012-06-05 19:08 ` David Daney
2012-06-14 11:02 ` Thomas Bogendoerfer [this message]
2012-06-14 17:23 ` Ralf Baechle
2012-06-23 19:30 ` Joshua Kinard
2012-06-24 12:18 ` Thomas Bogendoerfer
2012-06-24 16:28 ` Joshua Kinard
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=20120614110228.GA10493@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=david.daney@cavium.com \
--cc=jfaulkne@ccs.neu.edu \
--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