Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Stuart Longland <redhatter@gentoo.org>
To: pf@net.alphadv.de
Cc: linux-mips@linux-mips.org
Subject: Re: SGI IP28 Kernels... anyone had any luck lately?
Date: Sat, 10 Dec 2005 21:50:36 +1000	[thread overview]
Message-ID: <439AC10C.7060308@gentoo.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0512091803080.1379-100000@Opal.Peter>

[-- Attachment #1: Type: text/plain, Size: 2402 bytes --]

Hi,

peter fuerst wrote:
> sorry, obviously forgot to "tar" with the "-h" option.  The kernel patch-set
> is now repackaged with README and .config (same location).  I wonder, why no
> one noticed their missing since Oct 17...

Heh, I wondered that myself... Anyways, it's fixed now. :-)

> For exactness' sake: the patches are based on linux-2.6.14-rc2-mipscvs-20050925
> Maybe .config will enable compiling, the error-messages seem to point
> to a misconfiguration, since the compiler didn't touch any of the patched
> files yet.

I did try using the linux-2.6.14-rc2 tag out of git (repository as of
20051204; I didn't bother going to bleeding edge), but found I got the
same errors.

The problems disappeared, however, when I tried 2.6.14-rc1... this seems
to work just fine.

> indigo ~ # uname -a
> Linux indigo 2.6.14-rc1-ip28 #4 Sat Dec 10 18:26:46 EST 2005 mips64 R10000 V2.5  FPU V0.0 SGI Indigo2 GNU/Linux
> indigo ~ # uptime
>  21:49:13 up  3:21,  3 users,  load average: 2.63, 1.38, 0.71

The only glitch I've hit so far, is that booting via the local
framebuffer (okay, I know it isn't a true "framebuffer") causes a fatal
oops.  However, if I specify console=ttyS0,9600, I see a flashing cursor
on the framebuffer, and the bootup proceeds to completion on the serial
console.  Which is good news... it wasn't long ago when I recall merely
sneezing in front of the machine was enough to send it spiralling into a
fatal oops.

> There's still a problem with the Xserver: often, when starting up the Xserver
> first after a cold boot, it likes to hang (in a loop, waiting for "dmabusy"
> to settle down, either in the kernel-driver or the Xserver itself, when
> re-mmapping the dma-buffer). Usually, after a reset the Xserver works okay.
> I couldn't find a solution for this yet, but otherwise (;-) i easily (can) use
> the machine for regular work (no more hangs after the Xserver started up once).

As I say... this Linux port has really bounded ahead in the time I've
had this IP28 of mine... considering the hardware issues that have to be
worked around. :-)

X is my next step... for the moment though, I'm happy to be able to use
a real monitor, and not a serial console. :-)
-- 
Stuart Longland (aka Redhatter)              .'''.
Gentoo Linux/MIPS Cobalt and Docs Developer  '.'` :
. . . . . . . . . . . . . . . . . . . . . .   .'.'
http://dev.gentoo.org/~redhatter             :.'

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

      reply	other threads:[~2005-12-10 11:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-09 14:39 SGI IP28 Kernels... anyone had any luck lately? Stuart Longland
2005-12-09 17:22 ` peter fuerst
2005-12-10 11:50   ` Stuart Longland [this message]

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=439AC10C.7060308@gentoo.org \
    --to=redhatter@gentoo.org \
    --cc=linux-mips@linux-mips.org \
    --cc=pf@net.alphadv.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox