All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jorik Jonker <linux-mips@boeventronie.net>
To: linux-mips@linux-mips.org
Subject: linux 2.4 and Indy
Date: Thu, 29 Jan 2004 11:22:15 +0100	[thread overview]
Message-ID: <20040129102215.GC17760@ballina> (raw)

Hi,

I'm having big trouble getting linux 2.4.* to work on my SGI Indy. I want to
use my indycam, and thus compile a kernel with support for that. The problem
is that all the kernels I built do boot, but freeze some moments after
starting the init process. The only kernels that do not have this problem are 
2.4.16 and 2.4.17, but they do not have proper VINO support (they lack the
i2c algo-sgi part).
Is there some patch flying around to fix this, or do I just have bad luck?

/proc/cpuinfo:
system type             : SGI Indy
processor               : 0
cpu model               : R4600 V1.0  FPU V0.0
BogoMIPS                : 99.73
byteorder               : big endian
wait instruction        : yes
microsecond timers      : yes
extra interrupt vector  : no
hardware watchpoint     : no
VCED exceptions         : not available
VCEI exceptions         : not available

cheers,
-- 
Jorik Jonker
http://boeventronie.net/

             reply	other threads:[~2004-01-29 10:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-29 10:22 Jorik Jonker [this message]
2004-01-29 10:40 ` linux 2.4 and Indy Kumba
2004-01-30 10:59   ` Jorik Jonker
2004-01-30 11:12     ` Dominik 'Rathann' Mierzejewski
2004-01-30 20:49       ` Jorik Jonker
2004-01-30 21:01         ` Jorik Jonker
2004-01-31  3:04   ` Ralf Baechle
2004-01-31 14:10     ` Jorik Jonker
2004-02-01  4:52       ` R4600 V1.7 errata Ralf Baechle
2004-02-03 11:39         ` Ralf Baechle
2004-02-03 11:42           ` Dominik 'Rathann' Mierzejewski
2004-02-03 11:52             ` Ralf Baechle
2004-02-03 15:43               ` Maciej W. Rozycki
2004-02-03 16:12                 ` Ralf Baechle
2004-02-03 16:20                   ` Maciej W. Rozycki
2004-02-04 15:48             ` Dominik 'Rathann' Mierzejewski
2004-02-04 15:59               ` Pete Popov
2004-02-04 20:04                 ` Ralf Baechle

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=20040129102215.GC17760@ballina \
    --to=linux-mips@boeventronie.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.